Problem booting linux 2.6.19-rc5, 2.6.19-rc5-git6, 2.6.19-rc5-mm2 with md raid 1 over lvm root

Problem booting linux 2.6.19-rc5, 2.6.19-rc5-git6, 2.6.19-rc5-mm2 with md raid 1 over lvm root

[Nicolas Mailhot]

[-- Attachment #1: Type: text/plain, Size: 2280 bytes --]

[Please CC me on answers as I'm not an LKML subscriber]

Hi,

I have the following problem : based on the news that a working alsa
driver had just been published and pushed 2.6.19-way, I bought a new sound
card (expensive pro, if used one). Unfortunately using the out-of-tree
driver fails, so its author suggested to just try building one of the
2.6.19 rcs.

I used to do it a year ago or so when I had more free time. Since then my
hardware changed quite a lot (so did the core kernel) and it took me a few
evenings to re-assemble my build pipeline and configure a custom kernel.

Unfortunately the result does not boot. Since I haven't been using
anything but distro kernels for quite a long time I have no vanilla kernel
reference for this system.

It seems the failure occurs at md inspection time. The working distro
kernel startup messages look like this:

%<----
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised:
dm-devel@redhat.com
md: Autodetecting RAID arrays.
md: autorun ...
md: considering sdb3 ...
md:  adding sdb3 ...
md: sdb1 has different UUID to sdb3
md:  adding sda3 ...
md: sda1 has different UUID to sdb3
md: created md1
md: bind<sda3>
md: bind<sdb3>
md: running: <sdb3><sda3>
raid1: raid set md1 active with 2 out of 2 mirrors
md: considering sdb1 ...
md:  adding sdb1 ...
md:  adding sda1 ...
md: created md0
md: bind<sda1>
md: bind<sdb1>
md: running: <sdb1><sda1>
raid1: raid set md0 active with 2 out of 2 mirrors
md: ... autorun DONE.
%<----

The failing kernels (I tried -rc5, -rc5-git6, -rc5-mm2 only print :

%<----
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised:
dm-devel@redhat.com
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
%<-----

(I didn't bother copying the rest of the failing kernel dmesg, as sata
initialisation fills the first half of the screen, then dm is initialised,
then you only get the logical consequences of failing to detect the /
volume. The sata part seems fine – it prints the name of the hard drives
we want to use)

I'm attaching the dmesg for the working distro kernel (yes I know not 100%
distro kernel, but very close to one), distro config , and the config I
used in my test. If anyone could help me to figure what's wrong I'd be
grateful.

Regards,

-- 
Nicolas Mailhot

[-- Attachment #2: working-dmesg.bz2 --]
[-- Type: application/x-bzip2, Size: 8645 bytes --]

[-- Attachment #3: working-config.bz2 --]
[-- Type: application/x-bzip2, Size: 15679 bytes --]

[-- Attachment #4: config-2.6.19-0.3.rc5.git6.fc7.bz2 --]
[-- Type: application/x-bzip2, Size: 10271 bytes --]

Re: Problem booting linux 2.6.19-rc5, 2.6.19-rc5-git6, 2.6.19-rc5-mm2 with md raid 1 over lvm root

[Tejun Heo]

Nicolas Mailhot wrote:
> The failing kernels (I tried -rc5, -rc5-git6, -rc5-mm2 only print :
> 
> %<----
> device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised:
> dm-devel@redhat.com
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> %<-----
> 
> (I didn't bother copying the rest of the failing kernel dmesg, as sata
> initialisation fills the first half of the screen, then dm is initialised,
> then you only get the logical consequences of failing to detect the /
> volume. The sata part seems fine – it prints the name of the hard drives
> we want to use)
> 
> I'm attaching the dmesg for the working distro kernel (yes I know not 100%
> distro kernel, but very close to one), distro config , and the config I
> used in my test. If anyone could help me to figure what's wrong I'd be
> grateful.

Say 'y' not 'm' to SCSI disk support.

-- 
tejun

Re: Problem booting linux 2.6.19-rc5, 2.6.19-rc5-git6, 2.6.19-rc5-mm2 with md raid 1 over lvm root

[Bill Davidsen]

Tejun Heo wrote:
> Nicolas Mailhot wrote:
>> The failing kernels (I tried -rc5, -rc5-git6, -rc5-mm2 only print :
>>
>> %<----
>> device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised:
>> dm-devel@redhat.com
>> md: Autodetecting RAID arrays.
>> md: autorun ...
>> md: ... autorun DONE.
>> %<-----
>>
>> (I didn't bother copying the rest of the failing kernel dmesg, as sata
>> initialisation fills the first half of the screen, then dm is 
>> initialised,
>> then you only get the logical consequences of failing to detect the /
>> volume. The sata part seems fine – it prints the name of the hard drives
>> we want to use)
>>
>> I'm attaching the dmesg for the working distro kernel (yes I know not 
>> 100%
>> distro kernel, but very close to one), distro config , and the config I
>> used in my test. If anyone could help me to figure what's wrong I'd be
>> grateful.
>
> Say 'y' not 'm' to SCSI disk support.
>
That will probably work, but just building a new initrd is probably a 
lot easier. Although I thought the SCSI modules were included if built 
and installed if present.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979

Re: Problem booting linux 2.6.19-rc5, 2.6.19-rc5-git6, 2.6.19-rc5-mm2 with md raid 1 over lvm root

[Nicolas Mailhot]

Le lundi 20 novembre 2006 à 14:33 -0500, Bill Davidsen a écrit :
> Tejun Heo wrote:

> >> I'm attaching the dmesg for the working distro kernel (yes I know not 
> >> 100%
> >> distro kernel, but very close to one), distro config , and the config I
> >> used in my test. If anyone could help me to figure what's wrong I'd be
> >> grateful.
> >
> > Say 'y' not 'm' to SCSI disk support.
> >
> That will probably work, but just building a new initrd is probably a 
> lot easier. Although I thought the SCSI modules were included if built 
> and installed if present.

Absolutely no idea why the inird-ing works on distro kernels but not
this one. Probably confused by the full-sata config

Regards,

-- 
Nicolas Mailhot

Re: Problem booting linux 2.6.19-rc5, 2.6.19-rc5-git6, 2.6.19-rc5-mm2 with md raid 1 over lvm root

[Lee Revell]

On Wed, 2006-11-15 at 23:54 +0100, Nicolas Mailhot wrote:
> I have the following problem : based on the news that a working alsa
> driver had just been published and pushed 2.6.19-way, I bought a new
> sound card (expensive pro, if used one). Unfortunately using the
> out-of-tree driver fails, so its author suggested to just try building
> one of the 2.6.19 rcs. 

Just out of curiosity, which soundcard/driver?  I'm not aware of any pro
soundcards that got ALSA support recently, just cheap consumer stuff.

Lee

Re: Problem booting linux 2.6.19-rc5, 2.6.19-rc5-git6, 2.6.19-rc5-mm2 with md raid 1 over lvm root

[Nicolas Mailhot]

Le lundi 20 novembre 2006 à 13:49 -0500, Lee Revell a écrit :
> On Wed, 2006-11-15 at 23:54 +0100, Nicolas Mailhot wrote:
> > I have the following problem : based on the news that a working alsa
> > driver had just been published and pushed 2.6.19-way, I bought a new
> > sound card (expensive pro, if used one). Unfortunately using the
> > out-of-tree driver fails, so its author suggested to just try building
> > one of the 2.6.19 rcs. 
> 
> Just out of curiosity, which soundcard/driver?  I'm not aware of any pro
> soundcards that got ALSA support recently, just cheap consumer stuff.

E-MU 1820m

-- 
Nicolas Mailhot

Re: Problem booting linux 2.6.19-rc5, 2.6.19-rc5-git6, 2.6.19-rc5-mm2 with md raid 1 over lvm root

[Nicolas Mailhot]

[-- Attachment #1: Type: text/plain, Size: 430 bytes --]

> [Please CC me on answers as I'm not an LKML subscriber]

So "Say 'y' not 'm' to SCSI disk support." as Tejun Heo suggests works.
isn't it kind'of a regression though ? Distro 2.6.18.1 kernel works with
modular disk support.

Also why does it want to load both ata_generic and pata_amd ? Shouldn't
pata_amd be sufficient if it works on my chipset ?

Attaching new dmesg & config in the interest of science :)

-- 
Nicolas Mailhot

[-- Attachment #2: dmesg.bz2 --]
[-- Type: application/x-bzip2, Size: 6570 bytes --]

[-- Attachment #3: config-2.6.19-0.5.rc5.git6.fc7.bz2 --]
[-- Type: application/x-bzip2, Size: 9949 bytes --]