Date: Thu, 09 Jun 2005 16:34:12 -0400 From: Stephan Uphoff <ups@tree.com> To: Kris Kennaway <kris@obsecurity.org> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: mutex still spinning while in DDB on UP machine Message-ID: <1118349252.27369.42716.camel@palm> In-Reply-To: <20050609183835.GA9451@xor.obsecurity.org> References: <20050609183835.GA9451@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2005-06-09 at 14:38, Kris Kennaway wrote: > I've seen the following a couple of times recently on UP machines > running up-to-date current (the panic may not be important, I'm > referring to the behaviour of DDB): > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor write, page not present > instruction pointer = 0x20:0xc054cc77 > stack pointer = 0x28:0xd4222c9c > frame pointer = 0x28:0xd4222cb4 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 37 (vnlru) > [thread pid 37 tid 100035 ] > Stopped at vnlru_free+0x87: movl %eax,0(%edx) > db> stray irq7 > stray irq7 > stray irq7 > stray irq7 > too many stray irq 7's: not logging anymore > > At this point, the keyboard only works sporadically (i.e. I have to > press keys multiple times for DDB to receive the input). I will try to fix it. We should really not have interrupts enabled at this point. Stephan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1118349252.27369.42716.camel>