From: Andrew Morton <akpm@linux-foundation.org>
To: Tilman Schmidt <tilman@imap.cc>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
jgarzik@pobox.com, Steven French <sfrench@us.ibm.com>
Subject: Re: 2.6.25-rc8-mm1: Intel SATA boot failure
Date: Sun, 13 Apr 2008 19:05:56 -0700 [thread overview]
Message-ID: <20080413190556.69ed0dde.akpm@linux-foundation.org> (raw)
In-Reply-To: <4802A538.9040107@imap.cc>
On Mon, 14 Apr 2008 02:28:40 +0200 Tilman Schmidt <tilman@imap.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.
next prev parent reply other threads:[~2008-04-14 2:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080401213214.8fbb6d6b.akpm@linux-foundation.org>
2008-04-03 23:08 ` 2.6.25-rc8-mm1: Intel SATA boot failure Tilman Schmidt
2008-04-03 23:17 ` Andrew Morton
2008-04-09 14:29 ` Tilman Schmidt
2008-04-14 0:28 ` Tilman Schmidt
2008-04-14 2:05 ` Andrew Morton [this message]
2008-04-15 23:33 ` Tilman Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080413190556.69ed0dde.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@us.ibm.com \
--cc=tilman@imap.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).