From: Michael Cree <mcree@orcon.net.nz>
To: Bob Tracy <rct@frus.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
mingo@elte.hu, linux-kernel@vger.kernel.org, rjw@sisk.pl,
rth@twiddle.net, ink@jurassic.park.msu.ru,
linux-scsi@vger.kernel.org, kay.sievers@vrfy.org, greg@kroah.com
Subject: Re: [BUG] 2.6.23-rc3 can't see sd partitions on Alpha
Date: Sat, 08 Dec 2007 09:43:27 +1300 [thread overview]
Message-ID: <4759B06F.60108@orcon.net.nz> (raw)
In-Reply-To: <20071207145526.B561CDBA2@gherkin.frus.com>
Bob Tracy wrote:
> That was quick :-). Backing out the sysctl_check.c diff gives me a
> working kernel. Beats the #$%@! out of me how/why, though.
>
> Michael Cree: could you try backing out the diff below from your
> 2.6.24-rc3 tree and see if things are now working for you?
Yes (conference is now over). I backed out the sysctl_check patch from
2.6.24-rc3 and, indeed, got a working kernel.
The working kernel (was probably 2.6.24-rc3 less sysctl_check patch, but
might have been a 2.6.23 variant) has the following in /sys/block
alpha:~# ls -l /sys/block/
total 0
drwxr-xr-x 5 root root 0 2007-12-08 08:55 fd0
drwxr-xr-x 6 root root 0 2007-12-08 08:55 hde
drwxr-xr-x 5 root root 0 2007-12-08 08:55 hdf
drwxr-xr-x 10 root root 0 2007-12-08 08:55 sda
drwxr-xr-x 9 root root 0 2007-12-08 08:55 sdb
alpha:~# ls -l /sys/block/sda
total 0
-r--r--r-- 1 root root 8192 2007-12-08 08:55 capability
-r--r--r-- 1 root root 8192 2007-12-08 08:55 dev
lrwxrwxrwx 1 root root 0 2007-12-08 08:55 device ->
../../devices/pci0001:01/0001:01:06.0/host0/target0:0:1/0:0:1:0
drwxr-xr-x 2 root root 0 2007-12-08 08:55 holders
drwxr-xr-x 3 root root 0 2007-12-08 08:55 queue
-r--r--r-- 1 root root 8192 2007-12-08 08:55 range
-r--r--r-- 1 root root 8192 2007-12-08 08:55 removable
drwxr-xr-x 3 root root 0 2007-12-08 08:55 sda1
drwxr-xr-x 3 root root 0 2007-12-08 08:55 sda2
drwxr-xr-x 3 root root 0 2007-12-08 08:55 sda3
drwxr-xr-x 3 root root 0 2007-12-08 08:55 sda4
drwxr-xr-x 3 root root 0 2007-12-08 08:55 sda5
-r--r--r-- 1 root root 8192 2007-12-08 08:55 size
drwxr-xr-x 2 root root 0 2007-12-08 08:55 slaves
-r--r--r-- 1 root root 8192 2007-12-08 08:55 stat
lrwxrwxrwx 1 root root 0 2007-12-08 08:55 subsystem -> ../../block
--w------- 1 root root 8192 2007-12-08 08:55 uevent
alpha:~# grep . /sys/block/sda/*/dev
/sys/block/sda/sda1/dev:8:1
/sys/block/sda/sda2/dev:8:2
/sys/block/sda/sda3/dev:8:3
/sys/block/sda/sda4/dev:8:4
/sys/block/sda/sda5/dev:8:5
The broken kernel (2.6.24-rc3) has the following in /sys/block
alpha:~# ls -l /sys/block/
total 0
drwxr-xr-x 5 root root 0 Dec 8 09:22 fd0
drwxr-xr-x 6 root root 0 Dec 8 09:22 hde
drwxr-xr-x 5 root root 0 Dec 8 09:23 hdf
drwxr-xr-x 10 root root 0 Dec 8 09:22 sda
drwxr-xr-x 9 root root 0 Dec 8 09:23 sdb
alpha:~# ls -l /sys/block/sda
total 0
-r--r--r-- 1 root root 8192 Dec 8 09:22 capability
-r--r--r-- 1 root root 8192 Dec 8 09:22 dev
lrwxrwxrwx 1 root root 0 Dec 8 09:23 device ->
../../devices/pci0001:01/0001:01:06.0/host0/target0:0:1/0:0:1:0
drwxr-xr-x 2 root root 0 Dec 8 09:22 holders
drwxr-xr-x 3 root root 0 Dec 8 09:22 queue
-r--r--r-- 1 root root 8192 Dec 8 09:22 range
-r--r--r-- 1 root root 8192 Dec 8 09:22 removable
drwxr-xr-x 3 root root 0 Dec 8 09:22 sda1
drwxr-xr-x 3 root root 0 Dec 8 09:22 sda2
drwxr-xr-x 3 root root 0 Dec 8 09:22 sda3
drwxr-xr-x 3 root root 0 Dec 8 09:22 sda4
drwxr-xr-x 3 root root 0 Dec 8 09:22 sda5
-r--r--r-- 1 root root 8192 Dec 8 09:22 size
drwxr-xr-x 2 root root 0 Dec 8 09:22 slaves
-r--r--r-- 1 root root 8192 Dec 8 09:22 stat
lrwxrwxrwx 1 root root 0 Dec 8 09:22 subsystem -> ../../block
--w------- 1 root root 8192 Dec 8 09:22 uevent
alpha:~# grep . /sys/block/sda/*/dev
/sys/block/sda/sda1/dev:8:1
/sys/block/sda/sda2/dev:8:2
/sys/block/sda/sda3/dev:8:3
/sys/block/sda/sda4/dev:8:4
/sys/block/sda/sda5/dev:8:5
I failed to spot any difference (other than the formatting of the dates)
between the two!
Cheers
Michael.
next prev parent reply other threads:[~2007-12-07 20:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071126134819.8FE56DBA2@gherkin.frus.com>
[not found] ` <47508EE9.9030304@orcon.net.nz>
2007-11-30 22:42 ` [BUG] 2.6.23-rc3 can't see sd partitions on Alpha 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 [this message]
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=4759B06F.60108@orcon.net.nz \
--to=mcree@orcon.net.nz \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=ink@jurassic.park.msu.ru \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rct@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).