[uml-devel] Any progress on kernel panic after shutdown?

[<lis...@os...>]

~
~
sh-2.02# halt
System halted.
nbd: module cleaned up.
VFS: Busy inodes after unmount. Self-destruct in 5 seconds.  Have a nice day...
Kernel panic: Kernel mode fault at addr 0x5a5a5aba, ip 0x1004657f

ps says:

[uml@possum uml]$ ps x
  PID TTY      STAT   TIME COMMAND
 1678 ttyp4    S      0:00 -bash
 1714 ttyp4    S      0:01 /home/uml/bin/linux [(tracing thread)]
 1724 ttyp4    T      0:00 /home/uml/bin/linux
 1725 ttyp4    T      0:00 /home/uml/bin/linux
 1916 ttyp4    R      3:12 /home/uml/bin/linux [halt]
 1976 ttyp8    S      0:00 -bash
 2012 ttyp8    R      0:00 ps x
[uml@possum uml]$

I accidently ran my RHL 4.2 filesystem rather than 7.0 - don't ask
how;-)

Howver, RHL 7.0 doesn't work either.

I had to fix a filesystem corruption that followed a previous
failure. Here's what happened:
ree inodes count wrong (73113, counted=73122).
Fix? yes
 
 
/dev/ubd/0: ***** FILE SYSTEM WAS MODIFIED *****
/dev/ubd/0: 34398/107520 files (0.1% non-contiguous), 82512/107520 blocks
(Repair filesystem) 2 # exit
Unmounting file systems
can't create lock file /etc/mtab~48: Read-only file system (use -n flag to override)
Automatic reboot in progress.
Restarting system.
Kernel panic: Kernel mode fault at addr 0x5a5a5aba, ip 0x1004657f


[summer@possum summer]$ ps xa | grep um[l]
 1674 ttyp2    S      0:00 ssh -t -l uml possum
 1917 ?        S      0:03 konsole -e /home/uml/tools/bin/uml.run
 1920 ttyp5    S      0:01 /home/uml/bin/linux [(tracing thread)]
 1972 ttyp7    S      0:00 ssh -t -l uml possum
 2023 ttyp5    T      0:00 /home/uml/bin/linux
 2024 ttyp5    T      0:00 /home/uml/bin/linux
 2199 ttyp5    R      1:20 /home/uml/bin/linux [reboot]
[summer@possum summer]$