From: Andrew Morton <akpm@linux-foundation.org>
To: rct@gherkin.frus.com (Bob Tracy)
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: [BUG] 2.6.23-rc3 can't see sd partitions on Alpha
Date: Sat, 24 Nov 2007 22:38:35 -0800 [thread overview]
Message-ID: <20071124223835.ddd5f6e4.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071118052036.11B45DBA2@gherkin.frus.com>
On Sat, 17 Nov 2007 23:20:36 -0600 (CST) rct@gherkin.frus.com (Bob Tracy) wrote:
> Completely reproducible... 2.6.23-rc3 kernel boots, and normal messages
> are seen on console as far as disks found and partitions on each. However,
> once /dev is populated and the boottime scripts attempt to check filesystem
> status, no partitions on either of the two disks attached to the SCSI
> controller are seen. Dropping into a single-user root shell confirms
> the sudden "blindness": fdisk can't open /dev/sda.
>
> When I reboot on 2.6.24-rc2, everything works normally.
>
> System environment is Debian Etch. Both 2.6.24-rc2 and -rc3 were built
> from the respective unaltered kernel.org source trees, using the same
> kernel configuration modulo saying "no" to CONFIG_SENSORS_I5K_AMB and
> CONFIG_PID_NS in -rc3. No problems with -rc3 on a x86 box.
Could be something change in sysfs. Please double-check the config
options, make sure that something important didn't get disabled.
Failing that, it would be great if you could bisect this down to the
offending commit. http://www.kernel.org/doc/local/git-quick.html has help.
Richard, Ivan: have you seen anything like this?
Meanwhile, I guess we should track this as another post-2.6.23 regression
please.
Thanks.
next prev parent reply other threads:[~2007-11-25 6:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 5:20 [BUG] 2.6.23-rc3 can't see sd partitions on Alpha Bob Tracy
2007-11-25 6:38 ` Andrew Morton [this message]
2007-11-25 12:15 ` Rafael J. Wysocki
2007-11-26 13:48 ` Bob Tracy
2007-11-30 22:30 ` Michael Cree
2007-11-30 22:42 ` Andrew Morton
2007-11-30 23:26 ` Rafael J. Wysocki
2007-12-02 20:53 ` Michael Cree
2007-12-03 1:17 ` Bob Tracy
2007-12-04 12:16 ` Ingo Molnar
2007-12-04 15:36 ` Bob Tracy
2007-12-05 17:30 ` Bob Tracy
2007-12-07 0:16 ` Bob Tracy
2007-12-07 0:33 ` Andrew Morton
2007-12-07 5:07 ` Bob Tracy
2007-12-07 10:26 ` Andrew Morton
2007-12-07 11:37 ` Ingo Molnar
2007-12-07 13:39 ` Bob Tracy
2007-12-07 14:55 ` Bob Tracy
2007-12-07 15:05 ` Ingo Molnar
2007-12-07 16:59 ` Bob Tracy
2007-12-07 18:06 ` Ingo Molnar
2007-12-07 18:19 ` Kay Sievers
2007-12-07 19:36 ` Bob Tracy
2007-12-07 20:43 ` Michael Cree
2007-12-07 21:19 ` Kay Sievers
2007-12-07 22:39 ` Bob Tracy
2007-12-08 4:53 ` Bob Tracy
2007-12-08 5:05 ` Bob Tracy
2007-12-08 15:48 ` Kay Sievers
2007-12-09 0:51 ` Michael Cree
2007-12-09 4:19 ` Bob Tracy
2007-12-09 18:07 ` Ivan Kokshaysky
2007-12-10 15:08 ` Bob Tracy
2007-12-10 23:12 ` Ivan Kokshaysky
2007-12-10 15:05 ` Bob Tracy
2007-12-07 11:40 ` Ingo Molnar
2007-12-07 5:42 ` Bob Tracy
2007-12-07 9:33 ` Ingo Molnar
2007-12-07 0:44 ` Rafael J. Wysocki
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=20071124223835.ddd5f6e4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rct@gherkin.frus.com \
--cc=rjw@sisk.pl \
--cc=rth@twiddle.net \
/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).