Date: Tue, 10 Feb 2009 20:14:12 -0800 From: Sean Bruno <sean.bruno@dsl-only.net> To: Chris Ruiz <chris@young-alumni.com> Cc: freebsd-current@freebsd.org, freebsd-firewire <freebsd-firewire@FreeBSD.org> Subject: Re: fwohci0: panic: blockable sleep lock (sleep mutex ) Giant @ /usr/src/sys/dev/kbdmux/kbdmux.c:1103 Message-ID: <1234325652.14556.9.camel@localhost.localdomain> In-Reply-To: <A1D83E0F-7253-45F8-9080-D92577BFCFDC@young-alumni.com> References: <A1D83E0F-7253-45F8-9080-D92577BFCFDC@young-alumni.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2009-02-10 at 20:48 -0600, Chris Ruiz wrote: > > After 11 days of uptime, I typed 'fwcontrol -p' from a ssh session and > my system rebooted. This is all the information I could obtain. > After reboot, fwcontrol did not cause another panic. I do no have any > swap nor did I get a chance to enter the debugger before the reboot. > I'm currently in the process of updating to 188474 and will report > back if this happens again. > Ah ... finally, an AMD64 reporter. <grins evilly> Let's break this down a bit, what Firewire card do you have(pciconf -lv) What Firewire device was attached to the box? What is the output of "fwcontrol -p" and "fwcontrol"? Also, let's move this over to freebsd-firewire for the time being. Sean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1234325652.14556.9.camel>