Messages in this thread |  | | Date | Mon, 9 Sep 2002 16:15:16 -0400 | From | Daniel Jacobowitz <> | Subject | Re: do_syslog/__down_trylock lockup in current BK |
| |
On Mon, Sep 09, 2002 at 10:02:11PM +0200, Ingo Molnar wrote: > > the lockup, on both CPUs: > > >>EIP; c01200b1 <zap_thread+21/16d> <===== > Trace; c0120092 <zap_thread+2/16d> > Trace; c011f00c <exit_notify+10c/230> > Trace; c011f41a <do_exit+2ea/370> > Trace; c0125755 <schedule_timeout+b5/c0> > Trace; c0126686 <sig_exit+36/40> > Trace; c0127c54 <get_signal_to_deliver+2d4/360> > Trace; c0107cf3 <do_signal+c3/100> > Trace; c012d572 <sys_futex+182/1b0> > Trace; c0107fce <work_notifysig+13/15> > > >>EIP; c0106c5f <__write_lock_failed+f/20> <===== > Trace; c0120316 <.text.lock.exit+119/133> > Trace; c011ef16 <exit_notify+16/230> > Trace; c011f41a <do_exit+2ea/370> > Trace; c0125755 <schedule_timeout+b5/c0> > Trace; c0126686 <sig_exit+36/40> > Trace; c0127c54 <get_signal_to_deliver+2d4/360> > Trace; c0107cf3 <do_signal+c3/100> > Trace; c012d572 <sys_futex+182/1b0> > Trace; c0107fce <work_notifysig+13/15> > > ie. either the 'zap_again' produces an infinite loop, or one of the lists > became corrupted. I suspect the former.
How do you reproduce this? It's probably my fault, if it's stuck in zap_thread... but that's a pretty suspicious looking trace to me, if it goes from schedule_timeout to do_exit. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |