Date: Thu, 5 Jun 2003 23:20:11 +0200 From: Shaun Jurrens <shaun.jurrens@skoleetaten.oslo.no> To: Nate Lawson <nate@root.org> Cc: Palle Girgensohn <girgen@pingpong.net> Subject: Re: fxp0: device timeout | SCB already complete (me too) Message-ID: <20030605212011.GQ98443@nevada.skoleetaten.oslo.no> In-Reply-To: <20030605095126.B27684@root.org> References: <20030603152123.GM98443@nevada.skoleetaten.oslo.no> <46490000.1054744366@rambutan.pingpong.net> <20030605091532.GO98443@nevada.skoleetaten.oslo.no> <20030605095126.B27684@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--25rOlkxR6a4U87uN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 05, 2003 at 09:56:27AM -0700, Nate Lawson wrote: #> On Thu, 5 Jun 2003, Shaun Jurrens wrote: #> > On Wed, Jun 04, 2003 at 06:32:46PM +0200, Palle Girgensohn wrote: #> > #> Hi Shaun, #> > #> #> > #> Thanks for the input! Glad to hear I'm not the only one #> > #> #> > #> In my case, both the SCSI and NIC are integrated on the motherboard= , so I #> > #> cannot really move them around... :) #> > #> #> > #> Also, as I mentioned, I tried a de0 (PCI card, not onboard, and it #> > #> literally stopped the machine). Is the de0 driver also a problem? #> > #> > Jun 4 16:57:50 nol33n0x /kernel: fxp1: SCB timeout: 0x80 0xe0 0x50 0x0 #> > Jun 4 16:57:51 nol33n0x last message repeated 4 times #> > Jun 4 16:57:58 nol33n0x last message repeated 3 times #>=20 #> This doesn't mention SCSI anywhere. Your problem is almost certainly a #> PCI/interrupt problem. I'm redirecting this thread to -stable. I found the printf finally in /usr/src/sys/dev/fxp/if_fxp.c . Excuse the -scsi pollution. I've just seen the combination=20 very often of an ahc controller and the fxp nic being at the=20 scene of the problem, even from others on IRC. #>=20 #> > #> >The only suggestion I can offer at the moment is to try various ca= rd #> > #> >placements over your PCI slots. I've found stability using one of = the #> > #> >first two slots for my Adaptec controller (2940U[2]W, 29160[N]) an= d the #> > #> >rest for the Intel nics. #>=20 #> I got panics on boot with my BP6 (SMP) when I had an ahc controller in a #> PCI slot that didn't support bus mastering. I suggest you do what the #> above message says and try different combinations of cards in slots (i.e. #> keep removing one until you no longer get the messages and move around #> which slot is free). This will help people track down the problem. Also #> get your mobo manual and check if any slots force interrupt sharing or #> don't support bus mastering. Since I wrote the original message, it's something I've had to=20 do an incredible amount of, quite frankly. In fact, so much that it can't be normal. An identical box running linux with 8 nics,=20 2 of which are dual intel nic's has no problems whatsoever. The generic 3com (xl) nic's don't display this problem either.=20 Either the 3com's are more generous in what they accept for=20 interrupt routing or DMA failures, or the fxp driver is a little b0rked somewhere. I won't rule out that PC hardware sucks, etc., because I've worked on enough of it to already know that. BIOS's have been updated or not, same problems show up on at=20 least 3 different mainboards from two different manufacturers on both VIA and Intel chipsets. To the best of my knowledge, this began late last year. I wish I had some more modern hardware and some decent Serverworks boards to work on, but that stuff only sees windblows terminal servers here. I'll see if I can track this down somehow, but my time, like the rest of yours, is limited. I'm trying to keep this show running on a rubberband and a=20 shoestring.=20 #>=20 #> -Nate --=20 Med vennlig hilsen/Sincerely, Shaun D. Jurrens Drift og Sikkerhetskonsulent IKT-Avdeling Oslo Skoleetaten gpg key fingerprint: 007A B6BD 8B1B BAB9 C583 2D19 3A7F 4A3E F83E 84AE --25rOlkxR6a4U87uN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+37QLOn9KPvg+hK4RAkDDAJ4xdBCBUa8xd2D6Tv6gjgOo1kMTeACgnnBU kOVSfbXWC5qNggArO4S8qdI= =nkJ5 -----END PGP SIGNATURE----- --25rOlkxR6a4U87uN--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030605212011.GQ98443>