dmesg and GIANT-LOCK

[James Long]

With regard to the recent thread about looking for GIANT-LOCKs in
dmesg, why would one system say:

ns : 00:56:29 /home/james> uname -v ;dmesg | grep fxp
FreeBSD 6.2-STABLE #0: Tue Feb 20 15:47:09 PST 2007
fxp0: <Intel 82559 Pro/100 Ethernet> port 0x2400-0x243f mem 0xc4fff000-0xc4ffffff,0xc4e00000-0xc4efffff irq 10 at device 2.0 on pci0
miibus0: <MII bus> on fxp0
fxp0: Ethernet address: 00:02:a5:0a:57:73


while a more recent build says:

t30 : 00:56:19 /home/james> uname -v ;dmesg | grep fxp
FreeBSD 6.2-STABLE #2: Thu Mar  8 08:23:11 PST 2007
fxp0: <Intel 82801CAM (ICH3) Pro/100 VE Ethernet> port 0x7400-0x743f mem 0xd0200000-0xd0200fff irq 11 at device 8.0 on pci2
miibus0: <MII bus> on fxp0
fxp0: Ethernet address: 00:09:6b:86:82:a6
fxp0: [GIANT-LOCKED]



Is it just the difference in chipset/controller type that requires
the fxp driver to use GIANT on the second machine, but not the first? 
I also note that on the first machine, irq 10 is solely assigned to
fxp0.  On t30, irq 11 is shared with a number of other devices.  Dunno
if that matters.


Thanks!