From owner-freebsd-current Sat Jan 23 18:09:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20617 for freebsd-current-outgoing; Sat, 23 Jan 1999 18:09:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20611 for ; Sat, 23 Jan 1999 18:09:29 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA14692; Sat, 23 Jan 1999 21:07:40 -0500 (EST) Date: Sat, 23 Jan 1999 21:07:39 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon cc: N , Peter Wemm , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: <199901240102.RAA53285@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Jan 1999, Matthew Dillon wrote: > Yes, we're working on it in a sub-group. > > Since the panic message is a new one -- it's one I added that never existed > in -3.x, it is possible that the bug is not related to my VM stuff but > related to something else going on. > > I've found a number of other bugs in the greater VM system which I am > comitting fixes for, *BUT* I don't think any of them are related to this > particular panic. > > I am also comitting some very strict KASSERT checking to try to catch > the problem earlier. Everyone running 4.x kernels should add the following Ahem, would you kindly define 'everyone'? > options to your kernel config: > > options INVARIANTS > options INVARIANT_SUPPORT > > > -Matt > Matthew Dillon > > > :On Sun, 24 Jan 1999, Peter Wemm wrote: > : > :[..] > :> Oh, one other thing that occurred to me.. Under 4.0-current, I regularly > :> (ie: within 30 seconds of boot) get if_de tranmitter underflows. My > :> console corruption was happening at the instant that de0 was being > :> configured with ifconfig. exmh is running to a remote display over that > :> de0 interface. > : > :Here too... pretty quickly after boot on a SMP machine (current as of Jan > :12) that pushes quite a bit of traffic, the following messages appear: > : > :de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) > :de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) > :de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) > : > :The card is: > : > :de0: rev 0x22 int a irq 16 on pci0.12.0 > :de0: 21140A [10-100Mb/s] pass 2.2 > :de0: address 00:c0:f0:1f:5d:0d > :de0: enabling Full Duplex 100baseTX port > : > :Actually a Kingston clone, not a real DEC (so 1/5th of the price - but the > :receiver doesn't go audibly *click* when it's autosensing). > : > :So far I've gotten this message once: > : > :de0: abnormal interrupt: transmit underflow (switching to store-and-forward mode) > : > :Any harm in them, or can I safely ignore them? Would it be a good idea to > :raise the TX threshold by default, if only to avoid the messages? > :It's plugged into a Catalyst switch, if it makes any difference... > : > : > : -- Niels. > : > : > :To Unsubscribe: send mail to majordomo@FreeBSD.org > :with "unsubscribe freebsd-current" in the body of the message > : > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message