|Summary:||Kernel panic unless Return is hit at LILO prompt|
|Product:||[Retired] Red Hat Linux||Reporter:||david_cook|
|Component:||lilo||Assignee:||David Lawrence <dkl>|
|Status:||CLOSED NOTABUG||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||1999-07-13 20:17:13 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description david_cook 1999-06-23 15:13:10 UTC
I've seen this on two customer machines: if the user lets LILO timeout there is a kernel panic; if RETURN is typed it boots normally. A workaround is to add an empty append line to lilo.conf: append=" "
Comment 1 Jay Turner 1999-06-23 17:34:59 UTC
Can you get me the details of these machines. We have not seen this behavior in the test lab, so any help that you can give would be greatly appreciated.
Comment 2 diamond 1999-08-12 15:42:59 UTC
I have the same problem. If LILO times out, there's a kernel panic. VFS reports: "Cannot open root device 00:30." There is no default boot command line, no fallback and the lilo options line is "ro root=308" -- it seems as if the "8" is being ignored. David Cook's workaround (APPEND = " ") solves the problem here. Thanks!