2012/1/19 John Baldwin <j...@freebsd.org>: > On Thursday, January 19, 2012 11:02:57 am Glen Barber wrote: >> On Thu, Jan 19, 2012 at 10:50:45AM -0500, John Baldwin wrote: >> > On Wednesday, January 18, 2012 5:01:37 pm Glen Barber wrote: >> > > Hi, >> > > >> > > I'm running -CURRENT from about 5 days ago: >> > > >> > > nucleus# uname -a >> > > FreeBSD nucleus 10.0-CURRENT FreeBSD 10.0-CURRENT #3 r230037M: Fri Jan >> > > 13 17:48:14 EST 2012 gjb@nucleus:/usr/obj/usr/src/sys/NUCLEUS amd64 >> > > >> > > (The 'M' is kib's DRM patches for Intel GPU.) >> > > >> > > So far, I haven't had much problem with this laptop, but just had the >> > > machine panic. >> > > >> > > I have kgdb output attached, and I'll be happy to provide whatever >> > > additional information that may be needed. >> > > >> > > I have core.txt.N available here: >> > > >> > > http://people.freebsd.org/~gjb/core.txt >> > >> > In kgdb, can you go to frame 6 and 'p td->td_lock'. If that is non-null, >> > can >> > you do 'p *td->td_lock'? >> > >> >> Sure, script(1) output is attached. > > Hmm, I don't think td->td_lock is ever supposed to be NULL.
No, never, it is initialized in sched_fork_thread() and can point to containers lock or blocked_lock. I think the memory page of the pointer could have been zeroed or it is an hw bug. Attilio -- Peace can only be achieved by understanding - A. Einstein _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
