Date: Sat, 3 Jun 2006 09:38:57 -0400 From: John Baldwin <jhb@freebsd.org> To: Ralf Folkerts <ralf.folkerts@gmx.de> Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/96516: FreeBSD/amd64 intermittent Network-Problems Message-ID: <200606030938.57553.jhb@freebsd.org> In-Reply-To: <1149337928.1022.5.camel@beaster> References: <200605011700.k41H0W55054176@freefall.freebsd.org> <200605021618.17308.jhb@freebsd.org> <1149337928.1022.5.camel@beaster>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 03 June 2006 08:32, Ralf Folkerts wrote: > Am Dienstag, den 02.05.2006, 16:18 -0400 schrieb John Baldwin: > > Hi John, > > > On Tuesday 02 May 2006 14:02, Ralf Folkerts wrote: > > > Am Montag, den 01.05.2006, 14:11 -0400 schrieb John Baldwin: > > > > > > Hi John, > > > > > > > On Monday 01 May 2006 13:00, Ralf Folkerts wrote: > > > > > The following reply was made to PR amd64/96516; it has been noted by GNATS. > > > > > > > > > > From: Ralf Folkerts <ralf.folkerts@gmx.de> > > > > > To: bug-followup@FreeBSD.org, ralf.folkerts@gmx.de > > > > > Cc: > > > > > Subject: Re: amd64/96516: FreeBSD/amd64 intermittent Network-Problems > > > > > Date: Mon, 01 May 2006 18:52:40 +0200 > > > > > > > > > > This is a cryptographically signed message in MIME format. > > > > > > > > > > --------------ms080403000000010307050905 > > > > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > > Content-Transfer-Encoding: 7bit > > > > > > > > > > Hi John, > > > > > > > > > > thanks for your reply! Here's an excerpt from Linux' lspci -v: > > > > > > > > > > 05:07.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] > > > > > (rev 30 > > > > > ) > > > > > Subsystem: 3Com Corporation 3C905B Fast Etherlink XL 10/100 > > > > > Flags: bus master, medium devsel, latency 32, IRQ 22 > > > > > I/O ports at c880 [size=128] > > > > > Memory at feaffc00 (32-bit, non-prefetchable) [size=128] > > > > > Expansion ROM at 50000000 [disabled] [size=128K] > > > > > Capabilities: [dc] Power Management version 1 > > > > > > > > Ok, so it's on IRQ 22. Does linux have any other devices on IRQ 21? > > > > > > > > > When I put the "hw.pci5.7.INTA.irq=21" in the Loader I don't get any > > > > > Network at all: > > > > > > > > Ok, so it's not that xl0 is actually on irq 21. > > > > > > > > It would be helpful to know which device is suddently spouting > > > > interrupts. Can you make it go away by removing the sound or > > > > USB drivers? > > > > > > ok, I'll give that a try! Will it be sufficient to just remove the > > > Driver or should I remove the Sound Card and disable USB in BIOS? Also, > > > will Sound and USB be all? Should I also try another Graphics Card? > > > > Just removing the driver should be fine. Mostly I want to see if turning > > off the other devices listening on IRQ 21 helps. If it does then I'd like > > you to try just turning one of them off at a time to see if it is related > > to one of the devices. > > > > > However, as the problem just occurs intermittent (sometimes it doesn't > > > show for 2 - 3 weeks, then again it happens 3 times a day) it may take a > > > bit for me to get back to this; I'll try to run some "heavy" tests at > > > latest over this weekend... > > > > > > Cheers, > > > _ralf_ > > well, I turned off Sound on the 2nd May and it seems it "cured" the > Problem; at least, also I ran several "stress"-tests, the machine ran > fine and didn't show the "Interrupt Storm" Error. > > Now, how should I go on? I could enable Sound again and raise the > "Storm-Limit" via sysctl and close the PR. However, as I already > exchanged Sound Card, NIC and Mainboard (and all these Components > (except for the Mainboard) work fine in a i386 FreeBSD-machine) it seems > there is either something wrong woth the Chipset-Support in > FreeBSD/amd64 OR the Chipset itself may be buggy, the Board's Design > could be crap or something like this. What this tells me is that it may be a bug in the driver for your sound device. Can you work with the folks on multimedia@ to debug this further? Specifically, they probably need to verify what the interrupt status register for the sound card says when it starts storming. It may be that the driver isn't handling some specific interrupt condition. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200606030938.57553.jhb>