NetBSD Problem Report #33047

From www@netbsd.org  Fri Mar 10 08:44:44 2006
Return-Path: <www@netbsd.org>
Received: by narn.netbsd.org (Postfix, from userid 31301)
	id E008663B848; Fri, 10 Mar 2006 08:44:43 +0000 (UTC)
Message-Id: <20060310084443.E008663B848@narn.netbsd.org>
Date: Fri, 10 Mar 2006 08:44:43 +0000 (UTC)
From: timo.schoeler@riscworks.net
Reply-To: timo.schoeler@riscworks.net
To: gnats-bugs@netbsd.org
Subject: fxp NICs are not useable on IBM Netfinity 4000R (no link)
X-Send-Pr-Version: www-1.0

>Number:         33047
>Category:       kern
>Synopsis:       fxp NICs are not useable on IBM Netfinity 4000R (no link)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 10 08:45:00 +0000 2006
>Last-Modified:  Fri Mar 10 16:20:01 +0000 2006
>Originator:     Timo Schoeler
>Release:        NetBSD 3.0-STABLE
>Organization:
RISCworks
>Environment:
NetBSD netbsd.riscworks.net 3.0_STABLE NetBSD 3.0_STABLE (GENERIC.MP) #0: Sun Jan 29 18:31:53 CET 2006  root@deneb.ts39-bln.riscworks.net:/usr/obj/sys/arch/i386/compile/GENERIC.MP i386
>Description:
unfortunately, i discovered that when trying fetch the install sets from ftp a device timeout for the ethernet interface occurs. even worse: the switch (managed Nortel 450; also tried with Cisco 1924) says 'no link', as does the LEDs on the machines back.

i gave Fedora Core 4 a shot, and it runs fine on that machine.

dmesg output for the NIC from Fedora Core 4:

e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
e100: Copyright(c) 1999-2004 Intel Corporation
e100: eth0: e100_probe: addr 0xfebff000, irq 9, MAC addr 00:06:29:DE:7C:29
e100: eth1: e100_probe: addr 0xfebfe000, irq 10, MAC addr 00:06:29:DE:7C:28

---

NetBSD specific information (gathered via serial console, no typos! :)

*** ifconfig -a output ***

netbsd# ifconfig -a
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:06:29:de:87:39
        media: Ethernet autoselect (none flowcontrol,rxpause,txpause)
        status: no carrier
        inet6 fe80::206:29ff:fede:8739%fxp0 prefixlen 64 scopeid 0x1

-----

*** dmesg ***

NetBSD 3.0_STABLE (GENERIC.MP) #0: Sun Jan 29 18:31:53 CET 2006

Welcome to NetBSD!

Terminal type is vt100.                                                 
We recommend creating a non-root account and using su(1) for root
access.
netbsd# dmesg
NetBSD 3.0_STABLE (GENERIC.MP) #0: Sun Jan 29 18:31:53 CET 2006
        root@deneb.ts39-bln.riscworks.net:/usr/obj/sys/arch/i386/compile/GENERIC
.MP
total memory = 1023 MB
avail memory = 991 MB
BIOS32 rev. 0 found at 0xfd6b1
mainbus0 (root)
mainbus0: Intel MP Specification (Version 1.1) (IBM ENSW Kiowa SMP   )
cpu0 at mainbus0: apid 1 (boot processor)
cpu0: Intel Pentium III (686-class), 745.03 MHz, id 0x681
cpu0: features 387fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
cpu0: features 387fbff<PGE,MCA,CMOV,PAT,PSE36,PN,MMX>
cpu0: features 387fbff<FXSR,SSE>
cpu0: I-cache 16 KB 32B/line 4-way, D-cache 16 KB 32B/line 4-way
cpu0: L2 cache 256 KB 32B/line 8-way
cpu0: ITLB 32 4 KB entries 4-way, 2 4 MB entries fully associative
cpu0: DTLB 64 4 KB entries 4-way, 8 4 MB entries 4-way
cpu0: serial number 0000-0681-0001-518D-B1BE-950F
cpu0: calibrating local timer
cpu0: apic clock running at 99 MHz
cpu0: 8 page colors
cpu1 at mainbus0: apid 0 (application processor)
cpu1: starting
cpu1: Intel Pentium III (686-class), 745.00 MHz, id 0x681
cpu1: features 387fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
cpu1: features 387fbff<PGE,MCA,CMOV,PAT,PSE36,PN,MMX>
cpu1: features 387fbff<FXSR,SSE>
cpu1: I-cache 16 KB 32B/line 4-way, D-cache 16 KB 32B/line 4-way
cpu1: L2 cache 256 KB 32B/line 8-way
cpu1: ITLB 32 4 KB entries 4-way, 2 4 MB entries fully associative
cpu1: DTLB 64 4 KB entries 4-way, 8 4 MB entries 4-way
cpu1: serial number 0000-0681-0001-D85E-E93F-4833
mpbios: bus 0 is type PCI   
mpbios: bus 1 is type PCI   
mpbios: bus 2 is type PCI   
mpbios: bus 3 is type ISA   
ioapic0 at mainbus0 apid 14 (I/O APIC)
ioapic0: pa 0xfec00000, version 11, 24 pins
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0
pchb0: Intel 82443GX Host Bridge/Controller (rev. 0x00)
agp0 at pchb0: aperture at 0xf0000000, size 0x4000000
ppb0 at pci0 dev 1 function 0: Intel 82443GX AGP Interface (rev. 0x00)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
vga1 at pci1 dev 0 function 0: Chips and Technologies 69000 (rev. 0x64)
wsdisplay0 at vga1 kbdmux 1
wsmux1: connecting to wsdisplay0
pcib0 at pci0 dev 7 function 0
pcib0: Intel 82371AB (PIIX4) PCI-ISA Bridge (rev. 0x02)
piixide0 at pci0 dev 7 function 1
piixide0: Intel 82371AB IDE controller (PIIX4) (rev. 0x01)
piixide0: bus-master DMA support present
piixide0: primary channel wired to compatibility mode
piixide0: primary channel ignored (disabled)
piixide0: secondary channel wired to compatibility mode
piixide0: secondary channel interrupting at ioapic0 pin 15 (irq 15)
atabus0 at piixide0 channel 1
uhci0 at pci0 dev 7 function 2: Intel 82371AB (PIIX4) USB Host
Controller (rev. 0x01)
pci_intr_map: no mapping for pin D (line=ff)
uhci0: couldn't map interrupt
Intel 82371AB (PIIX4) Power Management Controller (miscellaneous
bridge, revisio n 0x02) at pci0 dev 7 function 3 not configured
fxp0 at pci0 dev 17 function 0: i82559 Ethernet, rev 8
fxp0: interrupting at ioapic0 pin 18 (irq 10)
fxp0: Ethernet address 00:06:29:de:87:39
inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1 at pci0 dev 18 function 0: i82559 Ethernet, rev 8
fxp1: interrupting at ioapic0 pin 17 (irq 11)
fxp1: Ethernet address 00:06:29:de:87:38
inphy1 at fxp1 phy 1: i82555 10/100 media interface, rev. 4
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ppb1 at pci0 dev 20 function 0: Digital Equipment DC21152 PCI-PCI
Bridge (rev. 0 x03)
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled, rd/line, wr/inv ok
pdcsata0 at pci2 dev 14 function 0
pdcsata0: Promise PDC40718 SATA300 controller (rev. 0x02)
pdcsata0: interrupting at ioapic0 pin 17 (irq 11)
pdcsata0: bus-master DMA support present
atabus1 at pdcsata0 channel 0
atabus2 at pdcsata0 channel 1
atabus3 at pdcsata0 channel 2
atabus4 at pdcsata0 channel 3
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com0: console
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff: using exception 16
isapnp0: no ISA Plug 'n Play devices found
ioapic0: enabling
Kernelized RAIDframe activated
atapibus0 at atabus0: 2 targets
cd0 at atapibus0 drive 0: <CRN-8241B, 1999/09/04, 1.22> cdrom removable
cd0: 32-bit data port
cd0: drive supports PIO mode 4, DMA mode 2
cd0(piixide0:1:0): using PIO mode 4, DMA mode 2 (using DMA)
wd0 at atabus4 drive 0: <WDC WD3200SD-01KNB0>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 298 GB, 620181 cyl, 16 head, 63 sec, 512 bytes/sect x 625142448
sectors wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5
(Ultra/100) wd0(pdcsata0:3:0): using PIO mode 4, Ultra-DMA mode 5
(Ultra/100) (using DMA) boot device: wd0
root on wd0a dumps on wd0b
root file system type: ffs
cpu1: CPU 0 running
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)
wsdisplay0: screen 4 added (80x25, vt100 emulation)

-----

*** pcictl output ***

netbsd# pcictl /dev/pci0 dump -d 17
PCI configuration registers:
  Common header:
    0x00: 0x12298086 0x02900157 0x02000008 0x00006408

    Vendor Name: Intel (0x8086)
    Device Name: 82557 Fast Ethernet LAN Controller (0x1229)
    Command register: 0x0157
      I/O space accesses: on
      Memory space accesses: on
      Bus mastering: on
      Special cycles: off
      MWI transactions: on
      Palette snooping: off
      Parity error checking: on
      Address/data stepping: off
      System error (SERR): on
      Fast back-to-back transactions: off
    Status register: 0x0290
      Capability List support: on
      66 MHz capable: off
      User Definable Features (UDF) support: off
      Fast back-to-back capable: on
      Data parity error detected: off
      DEVSEL timing: medium (0x1)
      Slave signaled Target Abort: off
      Master received Target Abort: off
      Master received Master Abort: off
      Asserted System Error (SERR): off
      Parity error detected: off
    Class Name: network (0x02)
    Subclass Name: ethernet (0x00)
    Interface: 0x00
    Revision ID: 0x08
    BIST: 0x00
    Header Type: 0x00 (0x00)
    Latency Timer: 0x64
    Cache Line Size: 0x08

  Type 0 ("normal" device) header:
    0x10: 0xfebff000 0x00003041 0xfea00000 0x00000000
    0x20: 0x00000000 0x00000000 0x00000000 0x105c1014
    0x30: 0x00000000 0x000000dc 0x00000000 0x38080100

    Base address register at 0x10
      type: 32-bit nonprefetchable memory
      base: 0xfebff000, not sized
    Base address register at 0x14
      type: i/o
      base: 0x00003040, not sized
    Base address register at 0x18
      type: 32-bit nonprefetchable memory
      base: 0xfea00000, not sized
    Base address register at 0x1c
      not implemented(?)
    Base address register at 0x20
      not implemented(?)
    Base address register at 0x24
      not implemented(?)
    Cardbus CIS Pointer: 0x00000000
    Subsystem vendor ID: 0x1014
    Subsystem ID: 0x105c
    Expansion ROM Base Address: 0x00000000
    Capability list pointer: 0xdc
    Reserved @ 0x38: 0x00000000
    Maximum Latency: 0x38
    Minimum Grant: 0x08
    Interrupt pin: 0x01 (pin A)
    Interrupt line: 0x00

  Capability register at 0xdc
    type: 0x01 (Power Management, rev. 1.0)

  Device-dependent header:
    0x40: 0x00000000 0x00000000 0x00000000 0x00000000
    0x50: 0x00000000 0x00000000 0x00000000 0x00000000
    0x60: 0x00000000 0x00000000 0x00000000 0x00000000
    0x70: 0x00000000 0x00000000 0x00000000 0x00000000
    0x80: 0x00000000 0x00000000 0x00000000 0x00000000
    0x90: 0x00000000 0x00000000 0x00000000 0x00000000
    0xa0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xc0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xd0: 0x00000000 0x00000000 0x00000000 0x7e220001
    0xe0: 0x3a004000 0x00000000 0x00000000 0x00000000
    0xf0: 0x00000000 0x00000000 0x00000000 0x00000000

--

netbsd# pcictl /dev/pci0 dump -d 18
PCI configuration registers:
  Common header:
    0x00: 0x12298086 0x02900157 0x02000008 0x00006408

    Vendor Name: Intel (0x8086)
    Device Name: 82557 Fast Ethernet LAN Controller (0x1229)
    Command register: 0x0157
      I/O space accesses: on
      Memory space accesses: on
      Bus mastering: on
      Special cycles: off
      MWI transactions: on
      Palette snooping: off
      Parity error checking: on
      Address/data stepping: off
      System error (SERR): on
      Fast back-to-back transactions: off

    Status register: 0x0290
      Capability List support: on
      66 MHz capable: off
      User Definable Features (UDF) support: off
      Fast back-to-back capable: on
      Data parity error detected: off
      DEVSEL timing: medium (0x1)
      Slave signaled Target Abort: off
      Master received Target Abort: off
      Master received Master Abort: off
      Asserted System Error (SERR): off
      Parity error detected: off
    Class Name: network (0x02)
    Subclass Name: ethernet (0x00)
    Interface: 0x00
    Revision ID: 0x08
    BIST: 0x00
    Header Type: 0x00 (0x00)
    Latency Timer: 0x64
    Cache Line Size: 0x08

  Type 0 ("normal" device) header:
    0x10: 0xfebfe000 0x00003081 0xfe900000 0x00000000
    0x20: 0x00000000 0x00000000 0x00000000 0x105c1014
    0x30: 0x00000000 0x000000dc 0x00000000 0x3808010b

    Base address register at 0x10
      type: 32-bit nonprefetchable memory
      base: 0xfebfe000, not sized
    Base address register at 0x14
      type: i/o
      base: 0x00003080, not sized
    Base address register at 0x18
      type: 32-bit nonprefetchable memory
      base: 0xfe900000, not sized
    Base address register at 0x1c
      not implemented(?)
    Base address register at 0x20
      not implemented(?)
    Base address register at 0x24
      not implemented(?)
    Cardbus CIS Pointer: 0x00000000
    Subsystem vendor ID: 0x1014
    Subsystem ID: 0x105c
    Expansion ROM Base Address: 0x00000000
    Capability list pointer: 0xdc
    Reserved @ 0x38: 0x00000000
    Maximum Latency: 0x38
    Minimum Grant: 0x08
    Interrupt pin: 0x01 (pin A)
    Interrupt line: 0x0b

  Capability register at 0xdc
    type: 0x01 (Power Management, rev. 1.0)

  Device-dependent header:
    0x40: 0x00000000 0x00000000 0x00000000 0x00000000
    0x50: 0x00000000 0x00000000 0x00000000 0x00000000
    0x60: 0x00000000 0x00000000 0x00000000 0x00000000
    0x70: 0x00000000 0x00000000 0x00000000 0x00000000
    0x80: 0x00000000 0x00000000 0x00000000 0x00000000
    0x90: 0x00000000 0x00000000 0x00000000 0x00000000
    0xa0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xc0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xd0: 0x00000000 0x00000000 0x00000000 0x7e220001
    0xe0: 0x3a004003 0x00000000 0x00000000 0x00000000
    0xf0: 0x00000000 0x00000000 0x00000000 0x00000000
>How-To-Repeat:
try to access the network.
>Fix:
yes, please. :)

>Audit-Trail:
From: christos@zoulas.com (Christos Zoulas)
To: gnats-bugs@netbsd.org, kern-bug-people@netbsd.org,
	gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc: 
Subject: Re: kern/33047: fxp NICs are not useable on IBM Netfinity 4000R (no link)
Date: Fri, 10 Mar 2006 10:48:23 -0500

 On Mar 10,  8:45am, timo.schoeler@riscworks.net (timo.schoeler@riscworks.net) wrote:
 -- Subject: kern/33047: fxp NICs are not useable on IBM Netfinity 4000R (no l

 | e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
 | e100: Copyright(c) 1999-2004 Intel Corporation
 | e100: eth0: e100_probe: addr 0xfebff000, irq 9, MAC addr 00:06:29:DE:7C:29
 | e100: eth1: e100_probe: addr 0xfebfe000, irq 10, MAC addr 00:06:29:DE:7C:28
 | 
 | ---
 | 
 | NetBSD specific information (gathered via serial console, no typos! :)
 | 
 | *** ifconfig -a output ***
 | 
 | netbsd# ifconfig -a
 | fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 |         address: 00:06:29:de:87:39
 |         media: Ethernet autoselect (none flowcontrol,rxpause,txpause)
                                       ^^^^
 |         status: no carrier
 |         inet6 fe80::206:29ff:fede:8739%fxp0 prefixlen 64 scopeid 0x1
 | 
 | fxp0 at pci0 dev 17 function 0: i82559 Ethernet, rev 8
 | fxp0: interrupting at ioapic0 pin 18 (irq 10)
 | fxp0: Ethernet address 00:06:29:de:87:39
 | inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
 | inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 | fxp1 at pci0 dev 18 function 0: i82559 Ethernet, rev 8
 | fxp1: interrupting at ioapic0 pin 17 (irq 11)
 | fxp1: Ethernet address 00:06:29:de:87:38
 | inphy1 at fxp1 phy 1: i82555 10/100 media interface, rev. 4
 | inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

 Is your ifconfig program old? What happens if you try to set the
 media manually?

 christos

From: Timo Schoeler <timo.schoeler@riscworks.net>
To: gnats-bugs@netbsd.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: kern/33047: fxp NICs are not useable on IBM Netfinity 4000R (no
 link)
Date: Fri, 10 Mar 2006 16:56:59 +0100

 Christos Zoulas schrieb:
 > The following reply was made to PR kern/33047; it has been noted by GNATS.
 > 
 > From: christos@zoulas.com (Christos Zoulas)
 > To: gnats-bugs@netbsd.org, kern-bug-people@netbsd.org,
 > 	gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
 > Cc: 
 > Subject: Re: kern/33047: fxp NICs are not useable on IBM Netfinity 4000R (no link)
 > Date: Fri, 10 Mar 2006 10:48:23 -0500
 > 
 >  On Mar 10,  8:45am, timo.schoeler@riscworks.net (timo.schoeler@riscworks.net) wrote:
 >  -- Subject: kern/33047: fxp NICs are not useable on IBM Netfinity 4000R (no l
 >  
 >  | e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
 >  | e100: Copyright(c) 1999-2004 Intel Corporation
 >  | e100: eth0: e100_probe: addr 0xfebff000, irq 9, MAC addr 00:06:29:DE:7C:29
 >  | e100: eth1: e100_probe: addr 0xfebfe000, irq 10, MAC addr 00:06:29:DE:7C:28
 >  | 
 >  | ---
 >  | 
 >  | NetBSD specific information (gathered via serial console, no typos! :)
 >  | 
 >  | *** ifconfig -a output ***
 >  | 
 >  | netbsd# ifconfig -a
 >  | fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 >  |         address: 00:06:29:de:87:39
 >  |         media: Ethernet autoselect (none flowcontrol,rxpause,txpause)
 >                                        ^^^^
 >  |         status: no carrier
 >  |         inet6 fe80::206:29ff:fede:8739%fxp0 prefixlen 64 scopeid 0x1
 >  | 
 >  | fxp0 at pci0 dev 17 function 0: i82559 Ethernet, rev 8
 >  | fxp0: interrupting at ioapic0 pin 18 (irq 10)
 >  | fxp0: Ethernet address 00:06:29:de:87:39
 >  | inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
 >  | inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 >            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 >  | fxp1 at pci0 dev 18 function 0: i82559 Ethernet, rev 8
 >  | fxp1: interrupting at ioapic0 pin 17 (irq 11)
 >  | fxp1: Ethernet address 00:06:29:de:87:38
 >  | inphy1 at fxp1 phy 1: i82555 10/100 media interface, rev. 4
 >  | inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 >  
 >  Is your ifconfig program old?

 it's a NetBSD3-STABLE with patch for the Promise SATA300 HBA. ifconfig 
 is not older than the build. (i made an iso for this one.)

 > What happens if you try to set the
 >  media manually?

 i tried on both sides, on the switch and on the machine itself: same result.

 today i put another fxp interface into the machine (into one of the two 
 PCI slots; the is populated by the SATA card) and turned off the second 
 serial port, thus freeing IRQ3. i pointed both onboard NICs to IRQ3 (as 
 they do when set to autoconfigure, which i also tried) and tried to use 
 the now as fxp2 known (pci) card.

 interestingly, the handshake works and it has a link (Cisco 1924, 10MBit).

 but it doesn't work: ping 192.9.50.99 (the machines' IP) goes into 
 nowhere, pinging the default gateway dito.

 i then tried setting the same IP (192.9.50.99) on another machine in the 
 same subnet, which got recognized on the console!

 regards,

 timo

From: christos@zoulas.com (Christos Zoulas)
To: gnats-bugs@netbsd.org, kern-bug-people@netbsd.org,
	gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
	timo.schoeler@riscworks.net
Cc: 
Subject: Re: kern/33047: fxp NICs are not useable on IBM Netfinity 4000R (no link)
Date: Fri, 10 Mar 2006 11:04:36 -0500

 On Mar 10,  4:00pm, timo.schoeler@riscworks.net (Timo Schoeler) wrote:
 -- Subject: Re: kern/33047: fxp NICs are not useable on IBM Netfinity 4000R (

 |  >  | e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
 |  >  | e100: Copyright(c) 1999-2004 Intel Corporation
 |  >  | e100: eth0: e100_probe: addr 0xfebff000, irq 9, MAC addr 00:06:29:DE:7C:29
 |  >  | e100: eth1: e100_probe: addr 0xfebfe000, irq 10, MAC addr 00:06:29:DE:7C:28
 |  >  | fxp0 at pci0 dev 17 function 0: i82559 Ethernet, rev 8
 |  >  | fxp0: interrupting at ioapic0 pin 18 (irq 10)
 |  >  | fxp0: Ethernet address 00:06:29:de:87:39
 |  >  | inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
 |  >  | inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 |  >  | fxp1 at pci0 dev 18 function 0: i82559 Ethernet, rev 8
 |  >  | fxp1: interrupting at ioapic0 pin 17 (irq 11)
 |  >  | fxp1: Ethernet address 00:06:29:de:87:38
 |  >  | inphy1 at fxp1 phy 1: i82555 10/100 media interface, rev. 4
 |  >  | inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 |  >  

 I think I see what is wrong. The mac addresses are different. I don't
 understand how that can be. Maybe there are two places to read the
 mac address from and linux gets it right and we get it wrong.

 christos

From: Timo Schoeler <timo.schoeler@riscworks.net>
To: gnats-bugs@netbsd.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: kern/33047: fxp NICs are not useable on IBM Netfinity 4000R (no
 link)
Date: Fri, 10 Mar 2006 17:18:34 +0100

 thus Christos Zoulas spake:
 > The following reply was made to PR kern/33047; it has been noted by GNATS.
 > 
 > From: christos@zoulas.com (Christos Zoulas)
 > To: gnats-bugs@netbsd.org, kern-bug-people@netbsd.org,
 > 	gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,
 > 	timo.schoeler@riscworks.net
 > Cc: 
 > Subject: Re: kern/33047: fxp NICs are not useable on IBM Netfinity 4000R (no link)
 > Date: Fri, 10 Mar 2006 11:04:36 -0500
 > 
 >  On Mar 10,  4:00pm, timo.schoeler@riscworks.net (Timo Schoeler) wrote:
 >  -- Subject: Re: kern/33047: fxp NICs are not useable on IBM Netfinity 4000R (
 >  
 >  |  >  | e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
 >  |  >  | e100: Copyright(c) 1999-2004 Intel Corporation
 >  |  >  | e100: eth0: e100_probe: addr 0xfebff000, irq 9, MAC addr 00:06:29:DE:7C:29
 >  |  >  | e100: eth1: e100_probe: addr 0xfebfe000, irq 10, MAC addr 00:06:29:DE:7C:28
 >  |  >  | fxp0 at pci0 dev 17 function 0: i82559 Ethernet, rev 8
 >  |  >  | fxp0: interrupting at ioapic0 pin 18 (irq 10)
 >  |  >  | fxp0: Ethernet address 00:06:29:de:87:39
 >  |  >  | inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
 >  |  >  | inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 >  |  >  | fxp1 at pci0 dev 18 function 0: i82559 Ethernet, rev 8
 >  |  >  | fxp1: interrupting at ioapic0 pin 17 (irq 11)
 >  |  >  | fxp1: Ethernet address 00:06:29:de:87:38
 >  |  >  | inphy1 at fxp1 phy 1: i82555 10/100 media interface, rev. 4
 >  |  >  | inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 >  |  >  
 >  
 >  I think I see what is wrong. The mac addresses are different. I don't
 >  understand how that can be. Maybe there are two places to read the
 >  mac address from and linux gets it right and we get it wrong.
 >  
 >  christos

 i just scanned the whole /24 here, the MAC addresses NetBSD figures out 
 are not known on the net -- so no collisions may occur when it really 
 'uses' them. however, it seems it doesn't even get that far.

 would it be of any help making the appropriate source more verbose to 
 see what happens (or not)?

 timo

Home	PR Database Search