Date: Fri, 23 Jan 2009 13:47:25 -0800 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Lars Engels <lme@freebsd.org> Cc: Ed Schouten <ed@80386.nl>, current@freebsd.org Subject: Re: panic: mutex Giant not owned at /usr/src/sys/kern/tty_ttydisc.c:1127 Message-ID: <bb4a86c70901231347i233b6a98pec94749d70e890a5@mail.gmail.com> In-Reply-To: <20090123213142.GN60948@e.0x20.net> References: <20090123154336.GJ60948@e.0x20.net> <20090123162920.GT41248@hoeg.nl> <20090123213142.GN60948@e.0x20.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 23, 2009 at 1:31 PM, Lars Engels <lme@freebsd.org> wrote: > On Fri, Jan 23, 2009 at 05:29:20PM +0100, Ed Schouten wrote: >> Hello Lars, >> >> As HPS said, the issue seems to be related to ubt, but there's still >> something else that is interesting to see here: >> >> * Lars Engels <lme@FreeBSD.org> wrote: >> > #2 0xc0859512 in panic (fmt=Variable "fmt" is not available. >> > ) at /usr/src/sys/kern/kern_shutdown.c:576 >> > #3 0xc0849fc7 in _mtx_assert (m=0xc0d76e90, what=4, file=0xc0c30b4c "/usr/src/sys/kern/tty_ttydisc.c", line=1127) at /usr/src/sys/kern/kern_mutex.c:639 >> > #4 0xc08aebad in ttydisc_getc (tp=0xc4650c00, buf=0xf12ea920, len=128) at /usr/src/sys/kern/tty_ttydisc.c:1127 >> > #5 0xc0740604 in sctty_outwakeup (tp=0xc4650c00) at /usr/src/sys/dev/syscons/syscons.c:323 >> > #6 0xc0740b6c in scgetc (sc=0xc0f11f20, flags=3) at /usr/src/sys/dev/syscons/syscons.c:3281 >> > #7 0xc0741190 in sc_cngetc (cd=0xc0cc9be0) at /usr/src/sys/dev/syscons/syscons.c:1607 >> > #8 0xc0821a28 in cncheckc () at /usr/src/sys/kern/kern_cons.c:379 >> > #9 0xc0821a66 in cngetc () at /usr/src/sys/kern/kern_cons.c:357 >> > #10 0xc04bfb15 in db_readline (lstart=0xc0d45cc0 "\n", lsize=120) at /usr/src/sys/ddb/db_input.c:326 >> >> Sam Leffler also reported this issue to me privately. I'll see what I >> can do to fix this. > > Thanks a lot. BTW it doesn't panic on every boot but only from time to > time. does the system panics if you remove usb2_bluetooth_ng? in other words, i'm interested to know if usb2_bluetooth_ng is somehow still causing the panic. thanks, max >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c70901231347i233b6a98pec94749d70e890a5>