From owner-freebsd-hackers Thu Mar 4 12:28:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4D04E14D82 for ; Thu, 4 Mar 1999 12:27:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA31748; Thu, 4 Mar 1999 12:27:38 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Mar 1999 12:27:38 -0800 (PST) From: Matthew Dillon Message-Id: <199903042027.MAA31748@apollo.backplane.com> To: Ulf Zimmermann Cc: Bob Bishop , Ulf Zimmermann , hackers@FreeBSD.ORG Subject: Re: vm problems in 3.1-RELEASE and -STABLE References: <199903041733.JAA30220@apollo.backplane.com> <19990304121414.A3659@TelcoSucks.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> 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 :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