RE: witness panic on Alpha
On 23-Mar-2002 Wilko Bulte wrote: Fri Mar 22 19:06:37 CET 2002 FreeBSD/alpha (ds10.wbnet) (ttyd0) login: syslogd: /var/log/auth.log: No such file or directory syslogd: /var/log/auth.log: No such file or directory Mar 22 21:55:23 ds10 kernel: pid 27885 (telnetd), uid 0: exited on signal 11 (co re dumped) Mar 22 21:55:30 ds10 kernel: pid 28342 (telnetd), uid 0: exited on signal 11 (co re dumped) syslogd: /var/log/auth.log: No such file or directory syslogd: /var/log/auth.log: No such file or directory panic: blockable sleep lock (sleep mutex) vnode_free_list @ /usr/src/sys/kern/vf s_subr.c:2678 panic Stopped at Debugger+0x34: zapnot v0,#0xf,a0 v0=0x7,a0=0x6 db db tb No such command db bt No such command db st Stopped at Debugger+0x38: call_pal osf1_swpipl db stack No such command db trace Debugger() at Debugger+0x3c panic() at panic+0x100 witness_lock() at witness_lock+0xb4 _mtx_lock_flags() at _mtx_lock_flags+0xd8 vfree() at vfree+0x30 vm_page_free_toq() at vm_page_free_toq+0x200 vm_page_free() at vm_page_free+0x2c vm_page_alloc() at vm_page_alloc+0x1ac pmap_growkernel() at pmap_growkernel+0x3e8 vm_map_findspace() at vm_map_findspace+0x144 kmem_alloc() at kmem_alloc+0x9c _zget() at _zget+0x244 zalloc() at zalloc+0x78 getnewvnode() at getnewvnode+0x470 ffs_vget() at ffs_vget+0x168 ufs_lookup() at ufs_lookup+0xf78 ufs_vnoperate() at ufs_vnoperate+0x2c vfs_cache_lookup() at vfs_cache_lookup+0x3cc ufs_vnoperate() at ufs_vnoperate+0x2c lookup() at lookup+0x4d0 namei() at namei+0x308 lstat() at lstat+0x50 syscall() at syscall+0x318 XentSys() at XentSys+0x64 --- syscall (190, FreeBSD ELF, lstat) --- --- user mode --- db Is this reproducible? If so, can you do a 'show locks'? -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: witness panic on Alpha
On Mon, Mar 25, 2002 at 11:40:30AM -0500, John Baldwin wrote: lstat() at lstat+0x50 syscall() at syscall+0x318 XentSys() at XentSys+0x64 --- syscall (190, FreeBSD ELF, lstat) --- --- user mode --- db Is this reproducible? If so, can you do a 'show locks'? Sofar it happened once. But I'll try to catch it again. -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: witness panic on Alpha
On Mon, Mar 25, 2002 at 11:40:30AM -0500, John Baldwin wrote: Looks like a different one: db trace siointr1() at siointr1+0x17c siointr() at siointr+0x40 isa_handle_fast_intr() at isa_handle_fast_intr+0x28 alpha_dispatch_intr() at alpha_dispatch_intr+0xdc interrupt() at interrupt+0x108 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- --- user mode --- db and db show locks exclusive (spin mutex) sio (0xfc648d20) locked @ /usr/src/sys/dev/sio/sio.c:1634 db This is a serial console Wilko No such command db trace Debugger() at Debugger+0x3c panic() at panic+0x100 witness_lock() at witness_lock+0xb4 _mtx_lock_flags() at _mtx_lock_flags+0xd8 vfree() at vfree+0x30 vm_page_free_toq() at vm_page_free_toq+0x200 vm_page_free() at vm_page_free+0x2c vm_page_alloc() at vm_page_alloc+0x1ac pmap_growkernel() at pmap_growkernel+0x3e8 vm_map_findspace() at vm_map_findspace+0x144 kmem_alloc() at kmem_alloc+0x9c _zget() at _zget+0x244 zalloc() at zalloc+0x78 getnewvnode() at getnewvnode+0x470 ffs_vget() at ffs_vget+0x168 ufs_lookup() at ufs_lookup+0xf78 ufs_vnoperate() at ufs_vnoperate+0x2c vfs_cache_lookup() at vfs_cache_lookup+0x3cc ufs_vnoperate() at ufs_vnoperate+0x2c lookup() at lookup+0x4d0 namei() at namei+0x308 lstat() at lstat+0x50 syscall() at syscall+0x318 XentSys() at XentSys+0x64 --- syscall (190, FreeBSD ELF, lstat) --- --- user mode --- db Is this reproducible? If so, can you do a 'show locks'? -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: witness panic on Alpha
On 25-Mar-2002 Wilko Bulte wrote: On Mon, Mar 25, 2002 at 11:40:30AM -0500, John Baldwin wrote: Looks like a different one: db trace siointr1() at siointr1+0x17c siointr() at siointr+0x40 isa_handle_fast_intr() at isa_handle_fast_intr+0x28 alpha_dispatch_intr() at alpha_dispatch_intr+0xdc interrupt() at interrupt+0x108 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- --- user mode --- db and db show locks exclusive (spin mutex) sio (0xfc648d20) locked @ /usr/src/sys/dev/sio/sio.c:1634 db This is a serial console Hummm, and you got a blockable lock panic here? -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: witness panic on Alpha
On Mon, Mar 25, 2002 at 04:21:23PM -0500, John Baldwin wrote: On 25-Mar-2002 Wilko Bulte wrote: On Mon, Mar 25, 2002 at 11:40:30AM -0500, John Baldwin wrote: Looks like a different one: db trace siointr1() at siointr1+0x17c siointr() at siointr+0x40 isa_handle_fast_intr() at isa_handle_fast_intr+0x28 alpha_dispatch_intr() at alpha_dispatch_intr+0xdc interrupt() at interrupt+0x108 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- --- user mode --- db and db show locks exclusive (spin mutex) sio (0xfc648d20) locked @ /usr/src/sys/dev/sio/sio.c:1634 db This is a serial console Hummm, and you got a blockable lock panic here? Well.. I lost the system for a reboot that served as the console display so I cannot tell unfortunately what the panic message said. W/ -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
