[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Panic in mem_poison_check on,shutdown
On Fri, Jun 13, 2008 at 12:45:11PM -0400, Liz Libby wrote:
> Hi -
> I'm getting a panic in kmem_poison_check on
> It was first noticed with a shutdown -p on command line of domU.
> But also occurs with shutdown of dom0.
> System is running:
> NetBSD udp.ir.bbn.com 4.99.64 NetBSD 4.99.64 (XEN3_DOM0) #2: Tue Jun 10
> 21:11:09 EDT 2008
> shutdown -p now returns :
> Jun 11 14:06:43 shutdown: reboot by root:
> System shutdown time has arrived
> About to run shutdown hooks...
> Stopping cron.
> Stopping inetd.
> Waiting for PIDS: 260.
> Removing block-type swap devices
> swapctl: removing /dev/xbd0b as swap device
> Wed Jun 11 14:06:48 EDT 2008
> Done running shutdown hooks.
> Jun 11 14:06:53 syslogd: Exiting on signal 15
> panic: kmem_poison_check: 0xffffa0000f4726a8: 0xa3 != 0xa4
> fatal breakpoint trap in supervisor mode
> trap type 1 code 0 rip ffffffff80363535 cs e030 rflags 246 cr2
> 7f7ffd983b70 cpl 0 rsp ffffa0000f4768b0
> Stopped in pid 152.1 (mount_mfs) at netbsd:breakpoint+0x5: leave
> breakpoint() at netbsd:breakpoint+0x5
> panic() at netbsd:panic+0x255
> kmem_poison_check() at netbsd:kmem_poison_check+0x82
> kmem_backend_free() at netbsd:kmem_backend_free+0x3d
> amap_free() at netbsd:amap_free+0x64
> uvm_unmap_detach() at netbsd:uvm_unmap_detach+0x4f
> uvmspace_free() at netbsd:uvmspace_free+0x11d
> exit1() at netbsd:exit1+0x215
> sigexit() at netbsd:sigexit+0x183
> postsig() at netbsd:postsig+0x120
> lwp_userret() at netbsd:lwp_userret+0x129
> syscall() at netbsd:syscall+0x128
I think this has already been reported somewhere else. It's a mfs issue.
I'm not using mfs anymore on current myself, until the issues with it
have been fixed (last time I used it, the system would hang umounting
mfs on reboot - it seems things now go a bit further).
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
Main Index |
Thread Index |