From: Jeff D. <jd...@ka...> - 2002-12-15 18:12:59
|
br...@cl... said: > root_fs is the root file system and using this command boots 2.5.44 > UML and all 2.4 UML's we use. So what has changed around 2.5.50? If you can't boot 2.5.50, then how did you get the msg2 log: Checking for the skas3 patch in the host...not found Checking for /proc/mm...not found Linux version 2.5.50-1um (root@hitao) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Tue Dec 10 22:11:13 CST 2002 [snip] EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Mounted devfs on /dev [snip] Remounting root filesystem in read-write mode: [ OK ] Activating swap partitions: [ OK ] Kernel panic: Kernel mode fault at addr 0x5a5a5b7e, ip 0xa00a27bb That's what lead me to conclude that root_fs didn't exist and this was a case of not bothering to read the documentation. In any case, I didn't get 2.5.50 to boot until I disabled devfs in the config ('devfs=nomount' wasn't good enough). And, BTW, I still haven't seen a stack trace from that panic... Jeff |