geninitrd nie wie co to 0ede

[Elan Ruusamäe]

On 04/16/12 20:58, Lukasz Glebicki wrote:
> On Monday 16 of April 2012 20:41:09 Elan Ruusamäe wrote:
>
>> afaik, earlier root= which was not parsed properly, was just ignored,
>> like you hadn't specified it at all (and burned in default was used)
>>
>> i'm pretty sure you could boot that same kernel/initrd (successfully)
>> also with:
>>
>> root=i_hate_mondays ramdisk_size=6144 resume=/dev/datavg/swaplv
> So why I have to replace 0edc to /dev/datavg/rootlv to boot ?
because as i said earlier mails:
  recent geninitrd changes do not ignore invalid root=xxx param

> http://dug.im/44f7d
>
> This is screenshot from latest geninitrd taken from trunk.
>
> I'm using this configuration since:
> Linux version 2.6.31.7-1 (builder at ymir-builder) (gcc version 4.4.2 20091026
> (release) (PLD-Linux) ) #1 SMP Wed Dec 9 10:09:49 CET 2009
> Dec 16 18:15:23 inhell kernel: [    0.000000] Command line: auto
> BOOT_IMAGE=pld ro root=803 resume2=swap:/dev/sda2 silent
> video=vesafb:1024x768-32 at 100
>
>
> egrep -o "root=[0-Z]{3,4}" /var/log/kernel |uniq -c
> Look at this grep:
>
>    1190 root=803
>        4 root=fe04
>       68 root=fe01
>      130 root=1901
>       60 root=1902
>      110 root=1904
>       84 root=1905
>      126 root=1907
>       22 root=1908
>       52 root=1909
>       28 root=fe01
>       48 root=1909
>       40 root=190a
>        2 root=0701
>       38 root=0edc
>       18 root=0702
>       91 root=0703
>       61 root=0edc
this just shows how random values lilo passes there

-- 
glen