Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 05 Mar 2002 10:51:53 -0500 (EST)
From:      John Baldwin <jhb@FreeBSD.org>
To:        Wilko Bulte <wkb@freebie.xs4all.nl>
Cc:        murray@freebsd.org, freebsd-alpha@freebsd.org, freebsd-current@freebsd.org
Subject:   RE: blockable sleep panic on Alpha / current
Message-ID:  <XFMail.020305105153.jhb@FreeBSD.org>
In-Reply-To: <20020304191303.A2288@freebie.xs4all.nl>

next in thread | previous in thread | raw e-mail | index | archive | help

On 04-Mar-02 Wilko Bulte wrote:
> During a make release I just got a panic. The build progressed until:
> 
> gzip -cn /usr/src/lib/libc/../libc/stdlib/imaxabs.3 > imaxabs.3.gz
> gzip -cn /usr/src/lib/libc/../libc/stdlib/imaxdiv.3 > imaxdiv.3.gz
> gzip -cn /usr/src/lib/libc/../libc/stdlib/labs.3 > labs.3.gz
> 
> The running system is a -current as of today.
> 
> The panic:
> 
> login: 
> FreeBSD/alpha (ds10.wbnet) (ttyd0)
> 
> login: panic: blockable sleep lock (sleep mutex) Giant @
> ../../../alpha/alpha/tr
> ap.c:482
> cpuid = 0; panic
> Stopped at      Debugger+0x34:  zapnot  v0,#0xf,a0      <v0=0x7,a0=0x6>
> db> 
> db> trace
> Debugger() at Debugger+0x34
> panic() at panic+0x188
> witness_lock() at witness_lock+0xb4
> _mtx_lock_flags() at _mtx_lock_flags+0xd8
> trap() at trap+0x4c8
> XentMM() at XentMM+0x2c
> --- memory management fault (from ipl 7) ---
> statclock_process() at statclock_process+0x1d4

We did something stupid like dereference a NULL pointer here.  Can you pull up
gdb on kernel.debug and do 'l *statclock_process+0x1d4'?

> XentMM() at XentMM+0x2c
> --- memory management fault ---
> ithread_schedule() at ithread_schedule+0xa4

Eww, we have another one here.

> alpha_dispatch_intr() at alpha_dispatch_intr+0x130
> interrupt() at interrupt+0x138
> XentInt() at XentInt+0x28
> --- interrupt (from ipl 0) ---
> critical_exit() at critical_exit+0x1c
> _mtx_unlock_spin_flags() at _mtx_unlock_spin_flags+0xd4
> vm_fault1() at vm_fault1+0x110c
> vm_fault() at vm_fault+0x64
> trap() at trap+0x6d8
> XentMM() at XentMM+0x2c
> --- memory management fault ---
> pmap_enter_quick() at pmap_enter_quick+0x1d4

Ugh, this is probably the real bug. :(  Can you do a list on this address?

> pmap_object_init_pt() at pmap_object_init_pt+0x1a4
> vm_map_insert() at vm_map_insert+0x35c
> elf_load_section() at elf_load_section+0x190
> exec_elf_imgact() at exec_elf_imgact+0x278
> execve() at execve+0x324
> syscall() at syscall+0x338
> XentSys() at XentSys+0x64
> --- syscall (59, FreeBSD ELF, execve) ---
> --- user mode ---
> db> 
> 
> 
> -- 
>|   / o / /_  _                wilko@FreeBSD.org
>|/|/ / / /(  (_)  Bulte                Arnhem, the Netherlands
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-alpha" in the body of the message

-- 

John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.020305105153.jhb>