User-mode Linux kernel port

Email Archive: user-mode-linux-devel (read-only)

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

From: <listreader@os...> - 2001-05-21 03:28

~
~
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@... 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@... 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@... 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@... summer]$

Thread View

Thread	Author	Date
[uml-devel] Any progress on kernel panic after shutdown?	<listreader@os...>

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

From: Jeff Dike <jdike@ka...> - 2001-05-21 03:39

listreader@... said:
> Kernel panic: Kernel mode fault at addr 0x5a5a5aba, ip 0x1004657f 

No, I haven't been worrying about that.  I'm been working on the networking 
stuff instead.  That's a lower-priority panic than usual because it happens at 
halt, so it doesn't upset anything you were in the middle of, and I don't 
think it even leaves you with dirty filesystems that need fscking on the next 
boot.

When I get the networking straightened out, I'll start banging on these bugs.

				Jeff

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

From: <listreader@os...> - 2001-05-21 03:58

Jeff Dike writes:
 > listreader@... said:
 > > Kernel panic: Kernel mode fault at addr 0x5a5a5aba, ip 0x1004657f 
 > 
 > No, I haven't been worrying about that.  I'm been working on the networking 
 > stuff instead.  That's a lower-priority panic than usual because it happens at 
 > halt, so it doesn't upset anything you were in the middle of, and I don't 
 > think it even leaves you with dirty filesystems that need fscking on the next 
 > boot.
 > 
 > When I get the networking straightened out, I'll start banging on these bugs.

 >

I'd not worried about it for a couple of CVS releases because it fell
over during startup.Which it still does.

I have reported this previously w/o respose that I noticed. The host
doesn't have the support in place (and as of today I'm on RHL 7.1 and
NONE of the UML support is in place).


Starting anacron: [  OK  ]
+ export PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/mnt/updates/utils/bin
+ PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/mnt/updates/utils/bin
+ ping -c4 192.168.1.1
connect: Network is unreachable
+ /mnt/config/etc/setup
+ um_eth_tool -i eth0 -a tap0
eth0 will connect to TUNTAP interface tap0
ioctl: Invalid argument
+ ifconfig eth0 192.168.1.153 netmask 255.255.255.0


I have these UML processes running:
[uml@... uml]$ ps tttyp8
  PID TTY      STAT   TIME COMMAND
 1976 ttyp8    S      0:00 -bash
 5709 ttyp8    S      0:06 /home/uml/bin/linux [(tracing thread)]
 5742 ttyp8    T      0:00 /home/uml/bin/linux
 5743 ttyp8    T      0:00 /home/uml/bin/linux
 5744 ttyp8    T      0:01 /home/uml/bin/linux [(idle thread)]
 5752 ttyp8    T      0:00 /home/uml/bin/linux [(kernel thread)]
 5753 ttyp8    T      0:00 /home/uml/bin/linux [(kernel thread)]
 5754 ttyp8    T      0:00 /home/uml/bin/linux [(kernel thread)]
 5755 ttyp8    T      0:00 /home/uml/bin/linux [(kernel thread)]
 5756 ttyp8    T      0:00 /home/uml/bin/linux [(kernel thread)]
 5758 ttyp8    T      0:00 /home/uml/bin/linux [init]
 6650 ttyp8    T      0:00 /home/uml/bin/linux [syslogd]
 6688 ttyp8    T      0:00 /home/uml/bin/linux [klogd]
 6737 ttyp8    T      0:00 /home/uml/bin/linux [portmap]
 6932 ttyp8    T      0:00 /home/uml/bin/linux [identd]
 6934 ttyp8    T      0:00 /home/uml/bin/linux [identd]
 6936 ttyp8    T      0:00 /home/uml/bin/linux [identd]
 6938 ttyp8    T      0:00 /home/uml/bin/linux [identd]
 6940 ttyp8    T      0:00 /home/uml/bin/linux [identd]
 6998 ttyp8    T      0:00 /home/uml/bin/linux [xinetd]
 7057 ttyp8    T      0:01 /home/uml/bin/linux [/usr/sbin/sshd]
 7159 ttyp8    T      0:00 /home/uml/bin/linux [crond]
 7214 ttyp8    T      0:00 /home/uml/bin/linux [anacron]
 7263 ttyp8    T      0:00 /home/uml/bin/linux [/sbin/update]
 7267 ttyp8    T      0:00 /home/uml/bin/linux [/bin/bash]
 7275 ttyp8    T      0:00 /home/uml/bin/linux [/bin/bash]
 7284 ttyp8    T      0:00 /home/uml/bin/linux [ifconfig]
 7285 ttyp8    Z      0:00 [linux <defunct>]
[uml@... uml]$

Presumably the Zombie's the problem here.