4.9-RC and bge
zeph at damon.com
Tue Sep 30 17:15:50 PDT 2003
you are correct. There is a slew of devices on the same IRQ:
ahc0: <Adaptec aic7890/91 Ultra2 SCSI adapter> port 0xe800-0xe8ff mem
0xfe203000-0xfe203fff irq 10 at device 6.0 on pci0
bge0: <Broadcom BCM5700 Gigabit Ethernet, ASIC rev. 0x7104> mem
0xfcf00000-0xfcf0ffff irq 10 at device 6.0 on pci1
pci2: <unknown card> (vendor=0x9005, dev=0x00c5) at 6.1 irq 10
isp0: <Qlogic ISP 2200 PCI FC-AL Adapter> port 0xbc00-0xbcff mem
0xeff00000-0xeff00fff irq 10 at device 8.0 on pci3
bge1: <Broadcom BCM5701 Gigabit Ethernet, ASIC rev. 0x105> mem
0xead00000-0xead0ffff irq 10 at device 6.0 on pci14
However, prior to 220.127.116.11, I had zero spurious "link up" messages, and
I have made no
h/w changes in the last 12 months.
I applied the patch to 18.104.22.168, and rebooted, and I am still suffering
spurious messages and intermittent lost packets. Unfortunately, I have
no idea what
version of if_bge.c I was running prior to the cvsup which landed me in
I have just reverted to 22.214.171.124, sans patch, and am about to boot
On Wednesday, Oct 1, 2003, at 01:21 Australia/Brisbane, John Polstra
> 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.
More information about the freebsd-stable