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
James Long wrote:
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.
On Tue, Mar 13, 2007 at 01:06:12AM -0700, James Long wrote:
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
On Tue, Mar 13, 2007 at 01:50:34PM -0400, Kris Kennaway wrote:
On Tue, Mar 13, 2007 at 01:06:12AM -0700, James Long wrote:
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
On Tue, Mar 13, 2007 at 12:12:26PM -0700, James Long wrote:
On Tue, Mar 13, 2007 at 01:50:34PM -0400, Kris Kennaway wrote:
On Tue, Mar 13, 2007 at 01:06:12AM -0700, James Long wrote:
With regard to the recent thread about looking for GIANT-LOCKs in
dmesg, why would one system say:
