From owner-freebsd-hackers Fri Oct 8 7:12:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by hub.freebsd.org (Postfix) with ESMTP id 4A2A71500B for ; Fri, 8 Oct 1999 07:12:10 -0700 (PDT) (envelope-from scott@avantgo.com) Received: from river ([10.0.128.30]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with SMTP id 192; Fri, 8 Oct 1999 07:06:55 -0700 Message-ID: <0edb01bf1197$014caf80$1e80000a@avantgo.com> From: "Scott Hess" To: , "Mike Smith" Cc: References: <199910080016.RAA02524@dingo.cdrom.com> Subject: Re: SMP + fxp0 wierdness Date: Fri, 8 Oct 1999 07:11:24 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote, in response to stevan@avantgo.com: > > We're running 3.3-REL on dual processor PII-450's, with a N440BX > > motherboard, using the onboard EtherExpress Pro (fxp) NIC and 512MB RAM. > > > > These machines are running custom software that excercises the disk, CPU > > and network quite heavily. The SMP machines seem to have both "fxp0: > > device timeout" problems, and spontaneous reboots. > > Could this be a problem with SMP + fxp combination? Any other thoughts > > or ideas? > > This is a known problem, insofar as it's been seen on a wide range of > systems. It's not SMP specific, but it does appear to be very sensitive > to your hardware configuration (eg. we were seeing it repeatedly in > combination with an ncr SCSI card, and when we switched to an Adaptec it > went away). Just a bit of additional info. We haven't yet seen the 'fxp0: device timeout' message on the machines that are running 3.3, even though at least one of the 3.3 machines used to throw many timeout messages under 3.1. On that machine, we were seeing 4 or 5 of the timeout messages per high-volume hour - until I dropped it back to a uniprocessor kernel, at which point those messages stopped completely. Also, excepting a single machine, the rebooting problem only seems to happen after around a week or runtime, and that period has been falling in proportion to the volume the machines are servicing (it used to take two weeks, and earlier almost a month). Thanks, scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message