[2.6.27] overlapping early reservations [was: early exception - lockdep related?]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 3 lines · Ingo Molnar
In any case it would make sense to turn that particular overlap situation into a warning message and disable initrd decompress - and try to boot with whatever is built-in the kernel.
If I explicitely tell my system to load a ramdisk, ignoring it is a bug.
I had a similar bug in PAM: One of these modules has a parameter to invert the check. I copied the tested configuration to an old debian system, which did not have this parameter, and it decided to ignore it (as if I were just joking while writing the config files of a security system). Therefore the system was open for everybody who was not supposed to use it.
I don't think ignoring an intrd will be as serious, but having a panic (and a timeout) is preferable to starting the wrong configuration.
Quoted 4 lines · Bodo Eggert
I don't think ignoring an intrd will be as serious, but having a panic (and a timeout) is preferable to starting the wrong configuration.
Most of the time, ignoring the initrd would result in a panic anyway, and arguably the times it wouldn't, it's going to do something wrong.
-hpa
Quoted 8 lines · Bodo Eggert
Quoted 3 lines · Ingo Molnar
In any case it would make sense to turn that particular overlap situation into a warning message and disable initrd decompress - and try to boot with whatever is built-in the kernel.
If I explicitely tell my system to load a ramdisk, ignoring it is a bug.
we dont really ignore it - we detect that it got corrupted by the bootloader. (it got overwritten by the kernel image - information has been destroyed irrevocably)
how we react to that breakage we detect is up to debate: it's fine to try to continue (presumably a huge vmlinux means it has all the drivers already) - and if a system relies on an initrd it wont get fast in bootup anyway.
that's why i suggested to print a warning, do a 5 seconds delay after that warning via mdelay(5000) so that the user has a chance to notice what is wrong, and then try to continue. Panicking is just as fine.
Ingo