Re: lock order reversal on Alpha
On Fri, Oct 19, 2001 at 01:02:50PM -0700, John Baldwin wrote: > > On 19-Oct-01 Wilko Bulte wrote: > > Fresh -current kernel on an DS10 Alpha box: > > I have untested patches to fix this. Unfortunately they involve fixing the > locking in teh clock code and I've only done i386 and alpha so far, but the > same changes need to be replicated into all the otehr arch's. Alternatively, > we should have MI devices for the RTC and i8254 timers so that this code > wouldn't be duplicated all over the place. *sigh* > > If this is a UP box you should be able to just continue from this for now. DS10 is UP yes. Tonight it ran a successful buildworld so it is not always panicing ;) -- | / o / /_ _ email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: lock order reversal on Alpha
On 19-Oct-01 Wilko Bulte wrote: > Fresh -current kernel on an DS10 Alpha box: I have untested patches to fix this. Unfortunately they involve fixing the locking in teh clock code and I've only done i386 and alpha so far, but the same changes need to be replicated into all the otehr arch's. Alternatively, we should have MI devices for the RTC and i8254 timers so that this code wouldn't be duplicated all over the place. *sigh* If this is a UP box you should be able to just continue from this for now. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "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
lock order reversal on Alpha
Fresh -current kernel on an DS10 Alpha box: System shutdown time has arrived Writing entropy file:. lock order reversal 1st 0xfc7574b0 clk @ ../../../alpha/alpha/clock.c:702 2nd 0xfc7526b0 callout @ ../../../kern/kern_timeout.c:225 witness_lock Stopped at Debugger+0x34: zapnot v0,#0xf,a0 db> db> db> panic panic: from debugger panic Stopped at Debugger+0x34: zapnot v0,#0xf,a0 db> trace Debugger() at Debugger+0x34 panic() at panic+0x100 db_panic() at db_panic+0x1c db_command() at db_command+0x2d4 db_command_loop() at db_command_loop+0xa4 db_trap() at db_trap+0x10c kdb_trap() at kdb_trap+0xe0 trap() at trap+0x21c XentIF() at XentIF+0x2c --- instruction fault (from ipl 6) --- Debugger() at Debugger+0x34 witness_lock() at witness_lock+0x80c _mtx_lock_spin_flags() at _mtx_lock_spin_flags+0x118 timeout() at timeout+0x44 sysbeep() at sysbeep+0x180 sc_bell() at sc_bell+0xb8 sc_switch_scr() at sc_switch_scr+0x374 scgetc() at scgetc+0x894 sckbdevent() at sckbdevent+0x2b8 atkbd_intr() at atkbd_intr+0x40 atkbd_isa_intr() at atkbd_isa_intr+0x30 isa_handle_intr() at isa_handle_intr+0x20 ithread_loop() at ithread_loop+0x1e8 fork_exit() at fork_exit+0x90 exception_return() at exception_return --- root of call graph --- db> Unfortunate side effect: it switches on its (loud) speaker beep while in de debugger :-/ W/ -- | / o / /_ _ email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
