LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: gregkh@suse.de
Cc: linux-kernel@vger.kernel.org, kay.sievers@vrfy.org
Subject: Re: partition sysfs OOPS in current GIT
Date: Wed, 06 Feb 2008 16:29:04 -0800 (PST) [thread overview]
Message-ID: <20080206.162904.187464710.davem@davemloft.net> (raw)
In-Reply-To: <20080207000959.GA16601@suse.de>
From: Greg KH <gregkh@suse.de>
Date: Wed, 6 Feb 2008 16:09:59 -0800
> On Wed, Feb 06, 2008 at 04:02:31PM -0800, David Miller wrote:
> > From: Greg KH <gregkh@suse.de>
> > Date: Wed, 6 Feb 2008 15:59:02 -0800
> >
> > > What block drivers are you using for sparc? Scsi? Or something else?
> > > What could make sparc64 different from x86 in regards to block device
> > > structure, odd...
> >
> > Only Fusion SAS on this system, therefore scsi.
>
> Can you send me the output of 'tree /sys/block/' on 2.6.24?
>
> Are there a lot of partitions here? Anything different you can think of
> from x86 that I can have a chance to try to narrow things down with? :)
It's a pretty simple partitioning scheme.
[ 0.307823] sda: sda1 sda2 sda3 sda4
> I don't know if you can boot without udev, but if you could, can you
> send the 'tree' output of the offending kernel too?
It actually is able to continue booting after udevd gets
killed off by the OOPS.
I'm going to run a bisect again and get some other info
for you...
Here is the tree output with current GIT:
/sys/block/
|-- loop0 -> ../devices/virtual/block/loop0
|-- loop1 -> ../devices/virtual/block/loop1
|-- loop2 -> ../devices/virtual/block/loop2
|-- loop3 -> ../devices/virtual/block/loop3
|-- loop4 -> ../devices/virtual/block/loop4
|-- loop5 -> ../devices/virtual/block/loop5
|-- loop6 -> ../devices/virtual/block/loop6
|-- loop7 -> ../devices/virtual/block/loop7
|-- ram0 -> ../devices/virtual/block/ram0
|-- ram1 -> ../devices/virtual/block/ram1
|-- ram10 -> ../devices/virtual/block/ram10
|-- ram11 -> ../devices/virtual/block/ram11
|-- ram12 -> ../devices/virtual/block/ram12
|-- ram13 -> ../devices/virtual/block/ram13
|-- ram14 -> ../devices/virtual/block/ram14
|-- ram15 -> ../devices/virtual/block/ram15
|-- ram2 -> ../devices/virtual/block/ram2
|-- ram3 -> ../devices/virtual/block/ram3
|-- ram4 -> ../devices/virtual/block/ram4
|-- ram5 -> ../devices/virtual/block/ram5
|-- ram6 -> ../devices/virtual/block/ram6
|-- ram7 -> ../devices/virtual/block/ram7
|-- ram8 -> ../devices/virtual/block/ram8
|-- ram9 -> ../devices/virtual/block/ram9
|-- sda -> ../devices/pci0000:02/0000:02:00.0/0000:03:02.0/0000:0a:00.0/host0/port-0:0/end_device-0:0/target0:0:0/0:0:0:0/block/sda
`-- sr0 -> ../devices/pci0000:02/0000:02:00.0/0000:03:01.0/0000:04:00.0/0000:05:01.0/0000:06:00.0/0000:07:00.2/usb3/3-2/3-2:1.0/host1/target1:0:0/1:0:0:0/block/sr0
26 directories, 0 files
next prev parent reply other threads:[~2008-02-07 0:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 23:26 David Miller
2008-02-06 23:31 ` Greg KH
2008-02-06 23:37 ` David Miller
2008-02-06 23:48 ` David Miller
2008-02-06 23:59 ` Greg KH
2008-02-07 0:02 ` David Miller
2008-02-07 0:09 ` Greg KH
2008-02-07 0:29 ` David Miller [this message]
2008-02-07 4:06 ` David Miller
2008-02-07 5:47 ` Greg KH
2008-02-07 6:05 ` David Miller
2008-02-07 6:38 ` Greg KH
2008-02-07 6:38 ` David Miller
2008-02-07 6:42 ` Greg KH
2008-02-07 6:39 ` David Miller
2008-02-07 6:58 ` Greg KH
2008-02-07 7:00 ` Greg KH
2008-02-07 7:11 ` David Miller
2008-02-07 7:18 ` Greg KH
2008-02-07 7:33 ` David Miller
2008-02-07 7:43 ` Greg KH
2008-02-07 7:20 ` Greg KH
2008-02-07 7:24 ` David Miller
2008-02-07 7:42 ` Greg KH
2008-02-07 6:44 ` Greg KH
2008-02-07 6:42 ` David Miller
2008-02-06 23:57 ` Andrew Morton
2008-02-07 0:07 ` Greg KH
2008-02-06 23:42 ` Oops figures Jan Engelhardt
2008-02-06 23:47 ` David Miller
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=20080206.162904.187464710.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: partition sysfs OOPS in current GIT' \
/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
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).