From: Michael Cree <email@example.com>
To: Andrew Morton <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org, email@example.com,
firstname.lastname@example.org, Kay Sievers <email@example.com>,
Greg KH <firstname.lastname@example.org>
Subject: Re: [BUG] 2.6.23-rc3 can't see sd partitions on Alpha
Date: Mon, 3 Dec 2007 09:53:53 +1300 [thread overview]
Message-ID: <6A73BEE8-9D45-4B75-8756-3008A4B1FDF4@orcon.net.nz> (raw)
On 1/12/2007, at 11:42 AM, Andrew Morton wrote:
> On Sat, 01 Dec 2007 11:30:01 +1300
> Michael Cree <email@example.com> wrote:
>> Bob Tracy wrote:
>>> Andrew Morton wrote:
>>>> Could be something change in sysfs. Please double-check the config
>>>> options, make sure that something important didn't get disabled.
>>> hoping someone else is seeing this or can replicate it in the
>> 2.6.24-rc2 works fine. 2.6.24-rc3 boots on Alpha but once /dev is
>> populated no partitions of the scsi sub-system are seen. Looks
>> like ide
>> sub-system similarly affected.
>> eth0: Digital DS21142/43 Tulip rev 65 at Port 0x200009400,
>> 08:00:2b:87:4c:b0, IRQ 45.
>> Linux video capture interface: v2.00
>> scsi_id: scsi_id: unable to access '/block'
> I guess this is where things go bad.
Yes, that is what I thought too.
> scsi_id is part of udev. Perhaps some sysfs nodes aren't being
> Random guess: what is your setting of CONFIG_SCSI_SCAN_ASYNC and what
> happens if you invert it?
Is set to Y. Changed it to N and recompiled kernel and restarted.
No change. Same problems remain.
I now realise that not only SCSI drive device nodes are not appearing
in /dev, but all disc nodes are not appearing.
In my case all of fd0, hde (IDE disc), hdf (CD/DVD), sda (SCSI disc),
sdb (SATA disc), sdc (memory card reader), and their accompanying
partition nodes, do not get made in /dev.
I'm not familiar with sysfs so don't know what what I should be
looking for in particular, but I did have a quick noisy around /sys
and noted that the above mentioned devices are all appearing at /sys/
block with what appeared to be sensible information in the
Sorry, but it is unlikely that I'll be able to look further into this
problem at the moment as I am running a conference this week and the
storm is about to hit...
next prev parent reply other threads:[~2007-12-02 20:54 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
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 [this message]
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).