Date: Wed, 10 Sep 1997 17:21:22 +0200 From: Tor Egge <Tor.Egge@idi.ntnu.no> To: joerg_wunsch@interface-business.de, j@ida.interface-business.de Cc: bugs@FreeBSD.ORG, dfr@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: Yet another 2.2-stable NFS (client) panic Message-ID: <199709101521.RAA20192@pat.idi.ntnu.no> In-Reply-To: Your message of "Wed, 10 Sep 1997 12:22:02 %2B0200" References: <19970910122202.WS38344@ida.interface-business.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x87654371 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf013476f > stack pointer = 0x10:0xefbffdb0 > frame pointer = 0x10:0xefbffdc0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 3 > current process = 7004 (hpscan) > interrupt mask = bio > > 0xf013476f <reassignbuf+147>: movl 0x50(%edx),%eax > > Register %edx had the fairly suspicious value 0x87654321. Alas, the > register values seem to have been clobbered when taking the coredump > from within DDB. Here's the stack trace (modulo the frames that were > caused by the DDB `panic' command, and a subsequent page fault inside > DDB): This is the probably the same error as reported in PR#3438 The PR is closed, but the fix is only in 3.0-current, not in 2.2-stable. - Tor Egge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709101521.RAA20192>