Andrew Morton wrote:
> On Tue, 19 Sep 2006 07:45:06 -0700
> "Martin J. Bligh" <[email protected]> wrote:
>
>>> - It took maybe ten hours solid work to get this dogpile vaguely
>>> compiling and limping to a login prompt on x86, x86_64 and powerpc.
>>> I guess it's worth briefly testing if you're keen.
>> PPC64 blades shit themselves in a strange way. Possibly the udev
>> breakage you mentioned? Hard to tell really if people are going to
>> go around breaking userspace compatibility ;-(
>
> What version of udev is it running?
Ok, this is not a blade, but a ppc lpar. Its running the following
version of udev:
udevinfo, version 021_bk
(Assuming of course the help for udev info -V is not lying when it says
"-V print udev version".)
>> http://test.kernel.org/abat/48127/debug/console.log
>>
>> ..
>>
>> sda: Write Protect is off
>> sda: cache data unavailable
>> sda: assuming drive cache: write through
>> SCSI device sda: 143374000 512-byte hdwr sectors (73407 MB)
>> sda: Write Protect is off
>> sda: cache data unavailable
>> sda: assuming drive cache: write through
>> sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
>> sd 0:0:1:0: Attached scsi disk sda
>> creating device nodes .[: [0-9]*: bad number
I was assuming this message was from udev? I can't find it in the
kernel anyhow. Might just be noise on the initrd.
>> 0:0:1:0: sg_io failed status 0x8 0x0 0x0 0x2
>> 0:0:1:0: sense key 0x5 ASC 0x24 ASCQ 0x0
>> [: [0-9]*: bad number
>> 0:0:1:0: sg_io failed status 0x8 0x0 0x0 0x2
>> 0:0:1:0: sense key 0x5 ASC 0x24 ASCQ 0x0
>> [: [0-9]*: bad number
>> 0:0:1:0: sg_io failed status 0x8 0x0 0x0 0x2
>> 0:0:1:0: sense key 0x5 ASC 0x24 ASCQ 0x0
>> [: [0-9]*: bad number
>> 0:0:1:0: sg_io failed status 0x8 0x0 0x0 0x2
>> 0:0:1:0: sense key 0x5 ASC 0x24 ASCQ 0x0
>> [: [0-9]*: bad number
>>
>>
>
> That all looks rather bad.
>
>> ReiserFS: sda2: Using r5 hash to sort names
>> looking for init ...
>> found /sbin/init
>> /init: cannot open .//dev//console: no such file
>
> Bizarrely-formed pathname. Does it always do that?
>
>> Kernel panic - not syncing: Attempted to kill init!
>> <0>Rebooting in 180 seconds..-- 0:conmux-control -- time-stamp --
>> Sep/19/06 4:18:52 --
>> (bot:conmon-payload) disconnected
>
> Has udev actually attempted to do anything by this stage?
>
> I wasn't seeing anything that spectacular. It used to be the case that
> udev simply hung. But in rc7-mm1 the symptoms are that incoming ssh
> sessions hang, but most other things work OK.
>
> Oh well - Greg has split that tree apart and I shall not be pulling the
> more problematic bits henceforth.
/me pins his hopes on rc7-mm2.
-apw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
