Date: Mon, 11 Sep 2000 11:37:34 +0700 (ALMST) From: Boris Popov <bp@butya.kz> To: John Baldwin <jhb@pike.osd.bsdi.com> Cc: Manfred Antar <null@pozo.com>, current@FreeBSD.ORG Subject: Re: New Fatal trap in Current SMP (random.dev changes ??) Message-ID: <Pine.BSF.4.10.10009111134358.26670-100000@lion.butya.kz> In-Reply-To: <200009110316.UAA31476@pike.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 10 Sep 2000, John Baldwin wrote: > > I think the random dev kicks in at this point > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 1; lapic.id = 0c000000 > > fault virtual address = 0x2c > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xc014f280 > > stack pointer = 0x10:0xc9a74f84 > > frame pointer = 0x10:0xc9a74f9c > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1,def 32 1,gran 1 > > processor flags = interrupt enabled, resume, IOPL = 0 > > current process = 2 (random) > > trap number = 12 > > panic: page fault > > cpuid = 1; lapic.id = 0x000000 > > boot() called on cpu#1 > > > > syncing disks....... > > > > The machine then is frozen and needs a reset to work again > > the debugger is unavailable > > ddb works fine here with this new trap, but I can't get remote gdb to work > to save my life. I think that remote gdb must not like me or something. Yes, after trap is occured ddb works. But it is impossible to continue from ddb because after typing 'c<enter>' machine becomes frozen. The same thing occur after any other panic (this is with SMP kernel). -- Boris Popov http://www.butya.kz/~bp/ 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?Pine.BSF.4.10.10009111134358.26670-100000>