linux-kernel - Re: 2.6.25-rc8-mm1: Intel SATA boot failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080403161733.c05dac53.akpm@linux-foundation.org>
Date:	Thu, 3 Apr 2008 16:17:33 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Tilman Schmidt <tilman@...p.cc>
Cc:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org,
	jgarzik@...ox.com
Subject: Re: 2.6.25-rc8-mm1: Intel SATA boot failure

On Fri, 04 Apr 2008 01:08:19 +0200
Tilman Schmidt <tilman@...p.cc> wrote:

> Andrew Morton schrieb:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc8/2.6.25-rc8-mm1/
> 
> This fails to come up on my development machine, apparently because it
> has trouble accessing the SATA hard disks.
> Hardware: Intel Pentium D940, Intel DQ965GF board, two SATA hard disks.
> Some unusual things I noticed during the boot process:
> 
> - a message "doing fast boot" that looked unfamiliar; unfortunately
>   it scrolled off too quickly to note its context
> 
> - for each of the two SATA ports in use, a message
>   "SATA port is slow to respond, please be patient"
>   accompanied by about 10 secs wait
> 
> - it actually got past the point where it mounts the root file system,
>   so it must have thought it could access the disks
> 
> - finally, the system hung completely after the SUSE startup messages
> 
>   Setting current sysctl status from /etc/sysctl.conf
>   net.ipv4.icmp_echo_ignore_broadcasts = 1
> 
>   with a dead keyboard and I had to hit the Win^Wreset button.
> 
> - After rebooting into 2.6.24-rc8 (which works fine), nothing had been
>   written to the disks, not even the dmesg output which SUSE usually
>   dumps into /var/log/boot.msg early during startup.
> 
> Before I try booting that kernel again, any instructions on what to
> watch out for? Is netconsole usable again?

Yes, netconsole is usable again ;)

> Other ideas?

Usual stuff: `diff -u dmesg-2.6.25-rc8 dmesg-2.6.25-rc8-mm1'.  Bisection.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/