Date: Wed, 1 Oct 2003 11:20:19 +1000 From: Damon Permezel <zeph@damon.com> To: John Polstra <jdp@polstra.com> Cc: freebsd-stable@freebsd.org Subject: Re: 4.9-RC and bge Message-ID: <6BEF2D56-F3AD-11D7-A85B-000A957C9058@damon.com> In-Reply-To: <XFMail.20030930082116.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I regressed all the way back to: * $FreeBSD: src/sys/dev/bge/if_bge.c,v 1.3.2.20 2003/02/06 21:36:40 ps Exp $ * $FreeBSD: src/sys/dev/bge/if_bgereg.h,v 1.1.2.9 2003/02/06 21:36:40 ps Exp $ * $FreeBSD: src/sys/dev/mii/brgphy.c,v 1.1.2.6 2002/12/11 21:26:56 ps Exp $ and the problem went away. I moved forward all the way back to the present, but modified the brgphy.c so as not to enable Wirespeed ethernet, and that was not an issue. I am moving back again so that I can get some work done. I am willing to try whatever experiments you want. Cheers. On Wednesday, Oct 1, 2003, at 01:21 Australia/Brisbane, John Polstra wrote: > On 30-Sep-2003 Damon Anton Permezel wrote: >> Recent SUP. >> Installed on Dell PowerEdge 4600. >> Getting tons of: >> >> Sep 30 12:23:16 zige /kernel: bge0: gigabit link up >> Sep 30 12:23:46 zige last message repeated 98 times > > Check your dmesg output, and I bet you'll see that bge0 is sharing an > IRQ with another device. (If not, I'd like to hear about it.) This > bug was fixed in -current in revision 1.41 of if_bge.c, but it never > got merged to -stable. I have a patch for -stable that I am planning > to commit after the source freeze lifts. It is attached to this mail. > Please let me know whether it solves your problem or not. > > John > <if_bge.c.patch>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6BEF2D56-F3AD-11D7-A85B-000A957C9058>