Date: Tue, 29 Dec 1998 11:19:35 +0000 (GMT) From: Doug Rabson <dfr@nlsystems.com> To: Hidetoshi Shimokawa <simokawa@sat.t.u-tokyo.ac.jp> Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: panic in pmap_remove_all Message-ID: <Pine.BSF.4.01.9812291116270.1813-100000@herring.nlsystems.com> In-Reply-To: <19981228205122M.simokawa@sat.t.u-tokyo.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 28 Dec 1998, Hidetoshi Shimokawa wrote: > I got the following panice twice. I used MFS intensively. > Sorry, I have no coredump. > > panic: pmap_remove_all: pv_table for 858a000 is inconsistent > db> trace > Debugger..ng() at Debugger..ng+0x24 > panic..ng() at panic..ng+0xf0 > pmap_remove_all..ng() at pmap_remove_all..ng+0x144 > pmap_page_protect..ng() at pmap_page_protect..ng+0x2c > vm_page_cache..ng() at vm_page_cache..ng+0xd4 > vm_pageout_scan..ng() at vm_pageout_scan..ng+0x3ac > vm_pageout..ng() at vm_pageout..ng+0x2e0 > kproc_start..ng() at kproc_start..ng+0x54 > exception_return() at exception_return These bugs are extremely hard to find (it usually involves adding extra instrumentation to pmap and spending long periods of time in the debugger). I doubt if I can fix it without being able to reproduce it locally. Can you give me an idea of what kind of workload triggers the panic? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" 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.01.9812291116270.1813-100000>