Date: Thu, 4 Mar 1999 12:27:38 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Ulf Zimmermann <ulf@Alameda.net> Cc: Bob Bishop <rb@gid.co.uk>, Ulf Zimmermann <ulf@Alameda.net>, hackers@FreeBSD.ORG Subject: Re: vm problems in 3.1-RELEASE and -STABLE Message-ID: <199903042027.MAA31748@apollo.backplane.com> References: <Pine.BSF.3.96.990304123921.6947A-100000@seagoon> <199903041733.JAA30220@apollo.backplane.com> <19990304121414.A3659@TelcoSucks.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:> :> 3.1-RELEASE and then 3.1-STABLE (SNAP 19990218) I get panics. Mostly with
:> :> wire count already 0, for which Jordan took the panic out. But I am still
:> :> getting other panics, like page fault.
:>
:> Someone took a panic out in the VM system? Where?
:
:He only took out the call to trap/panic for these kinds of messages:
:
:Mar 4 00:47:10 PacHell /kernel: vm_page_free: freeing wired page
:Mar 4 00:47:10 PacHell /kernel: vm_page_unwire: invalid wire count: 0
These are pretty serious panics. You would not want to allow the
system to run after such conditions occur. Taking out the panics is not
going to solve the problem.
A backtrace from the core dump would be useful. It's hard to tell
what the cause of the crash is - it could be the BT848, it could the
SBPRO. It could be something else. You might have to mess around
disabling various bits to figure out the cause.
-Matt
Matthew Dillon
<dillon@backplane.com>
:Regards, Ulf.
:
:---------------------------------------------------------------------
:Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936
:Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903042027.MAA31748>