Date: Fri, 19 Feb 1999 11:17:56 -0500 From: Chris Johnson <cjohnson@palomine.net> To: me <onemo@jps.net> Cc: Michael Larsen <mlarsen@tech-nic.net>, stable@FreeBSD.ORG Subject: Re: fxp0 with 3.1-stable Message-ID: <19990219111756.A28822@palomine.net> In-Reply-To: <36CD7CC1.E985F1CC@jps.net>; from me on Fri, Feb 19, 1999 at 07:01:21AM -0800 References: <36CD4A39.32D8DCF3@tech-nic.net> <36CD7CC1.E985F1CC@jps.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 19, 1999 at 07:01:21AM -0800, me wrote: > Michael Larsen wrote: > > > Hi > > > > I know This has been mentioned previosly on the list, but I can't find any > > answers in the list arcrives. > > > > So.. After upgrading from 2.2.8 to RELENG_3 with cvsup .... learning from > > Jordan's nice discription.... everything seems to work ok... ...except > > from my NIC (fxp0 / Intel EtherExpress Pro/100 ).. Evertime i use : > > ifconfig fxp0 inet 123.234.123.234 netmask 255.255.255.240 it freezes, and > > only a reboot, can call it back to life :). Is this a know isue in 3.1?? > > or an I the isue ?? :) > > > > Any help appriciated..... > > > > I've not had a problem using this driver at all in well over a year. Check > and make sure IRQ sharing is not the culprit. I've found similar problems > using this adapter and BeOS on a Compaq which defaults to all PCI devices on > the same interrupt. I had to manually set each card to a different IRQ and > all was well. Just as a data point, I've got an Intel PR440FX motherboard with onboard fxp0 and ahc0. They're sharing IRQ 11, and everything is working peachily with 3.1-STABLE as of about a week ago. Chris > > Good luck! MO! > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe > freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990219111756.A28822>