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: <20080413190556.69ed0dde.akpm@linux-foundation.org>
Date:	Sun, 13 Apr 2008 19:05:56 -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, Steven French <sfrench@...ibm.com>
Subject: Re: 2.6.25-rc8-mm1: Intel SATA boot failure

On Mon, 14 Apr 2008 02:28:40 +0200 Tilman Schmidt <tilman@...p.cc> wrote:

> Final report, seeing -mm2 is out:
> 
> - Netconsole works. (grumblestupidsusefirewallgrumble)
> 
> - The hang during boot only happens with kernels compiled with
>   CONFIG_CIFS_EXPERIMENTAL=y
>   It also doesn't always happen at the same point in the boot sequence.
>   I'm suspecting it might be triggered by some network packet.
>   Anyway, it's obviously *not* a SATA problem.
>   (That was just me jumping to conclusions, because ...)

I don't remember seeing a report of the CIFS hang.

It might be caused by
bkl-removal-convert-cifs-over-to-unlocked_ioctl.patch, but it's hard to see
how that could affect things before userspace has started.

> - That leaves only the messages
> 
>   ata1: port is slow to respond, please be patient (Status 0x80)
>   ata1: COMRESET failed (errno=-16)
> 
>   and accompanying delays during boot, for each installed SATA disk.
>   I'll try to find the time to retest this with 2.6.25-rc8-mm2.

That would be good, 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/