Date: Sat, 29 Sep 2001 17:39:06 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: John Baldwin <jhb@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: panic: blockable sleep lock (sx) ... Message-ID: <20010929173906.A1359@dhcp01.pn.xcllnt.net> In-Reply-To: <XFMail.010929125248.jhb@FreeBSD.org> References: <20010929013818.A407@athlon.pn.xcllnt.net> <XFMail.010929125248.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 29, 2001 at 12:52:48PM -0700, John Baldwin wrote: > > could figure out the faulting address that it trapp'd one that would help. You > could add KTR tracepoints or some such to store the log message to do that and > then examin the KTR buffer to get the actual faulting address. Ok. In the remote debugger I got a lot more data. In fact, it brought me to linux_alarm() in /sys/compat/linux_misc.c First some data about the trapping thread: td = curthread = 0xcbb89304 looks ok kg = td->ksegrp = 0xcbb89230 looks ok td->td_proc->p_comm = "swi6: tty:sio clock" The LTP test that seems to be causing this is doing an alarm(). In linux_alarm() I see: : s = splsoftclock(); old_it = td->td_proc->p_realtimer; : td->td_proc->p_realtimer = it; splx(s); : Is the splsoftclock() acceptable locking to access td->td_proc? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net 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?20010929173906.A1359>