NetBSD Problem Report #10550

Received: (qmail 21053 invoked from network); 9 Jul 2000 17:24:59 -0000
Message-Id: <200007091722.e69HMPG08486@rumolt.teuto.de>
Date: Sun, 9 Jul 2000 19:22:25 +0200 (MEST)
From: Martin Husemann <martin@rumolt.teuto.de>
Reply-To: martin@rumolt.teuto.de
To: gnats-bugs@gnats.netbsd.org
Subject: can't netboot from fxp0 any more
X-Send-Pr-Version: 3.95

>Number:         10550
>Category:       kern
>Synopsis:       fxp card does not work with -current
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 09 17:25:00 +0000 2000
>Closed-Date:    Thu Jul 27 22:16:28 +0000 2000
>Last-Modified:  Thu Jul 27 22:16:28 +0000 2000
>Originator:     Martin Husemann
>Release:        1.5B, cvs updated July 8
>Organization:

>Environment:

System: NetBSD rumolt.teuto.de 1.5B NetBSD 1.5B (RUMOLT) #1: Sat Jul 8 16:59:11 MEST 2000 martin@rumolt.teuto.de:/usr/src/sys-i4b/arch/i386/compile/RUMOLT i386


>Description:

I tried upgrading a 1.4 machine to current. This machine (fxp0 wiht nsphy)
boots from the network via dhcp/nfs. Now that our dhcpd is fixed, I tried
to compile a -current kernel for it and boot it, but it failed.

The server does not receive any bootp/dhcp request. The lights on the hub
blink a few times, but not packet seems to leave the booting machine.

The fxp0 is connected to a 100/10 MBit switch, autonegotiation always worked
for it (and when the lights blink, they always show 100MBit, full-duplex, which
is correct).

>How-To-Repeat:

Try to netboot a -current machine via fxp0 with nsphy.

>Fix:
n/a
>Release-Note:
>Audit-Trail:

From: Martin Husemann <martin@rumolt.teuto.de>
To: gnats-bugs@NetBSD.ORG
Cc:  
Subject: Re: kern/10550
Date: Sun, 9 Jul 2000 19:56:23 +0200 (MEST)

 Sorry, just realized my description was incomplete.

 Actually what I'm doing is: dosboot a kernel, wich has "root on ? type nfs"
 hardcoded. This kernel can't mount it's root because it doesn't find a
 server for it.

From: John Hawkinson <jhawk@MIT.EDU>
To: Martin Husemann <martin@rumolt.teuto.de>
Cc: gnats-bugs@gnats.netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/10550: can't netboot from fxp0 any more
Date: Mon, 10 Jul 2000 08:19:52 -0400 (EDT)

 Could you please try booting an INSTALL kernel and confirm
 whether fxp0 functions normally?

 Do you have any idea when this last worked in -current?

 --jhawk

From: Martin Husemann <martin@rumolt.teuto.de>
To: jhawk@MIT.EDU (John Hawkinson)
Cc: gnats-bugs@gnats.netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/10550: can't netboot from fxp0 any more
Date: Mon, 10 Jul 2000 19:00:25 +0200 (MEST)

 > Could you please try booting an INSTALL kernel and confirm
 > whether fxp0 functions normally?

 Good idea. Did so: did not work. So it's not a netbooting problem,
 but the fxp driver does not support my card currently.

 > Do you have any idea when this last worked in -current?

 No, sorry, though I seem to recall the latest MP test kernel still worked.

 When booting the install kernel I got hold of the kernel output (below)
 and checked the autonegotiation stuff: 

 fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 	address: 00:a0:c9:25:13:84
 	media: Ethernet autoselect (100baseTX full-duplex)
 	status: active
 	inet 212.8.203.83 netmask 0xfffffff8 broadcast 212.8.203.87
 	inet6 fe80:1::2a0:c9ff:fe25:1384 prefixlen 64

 100baseTX/full duplex is correct and the same is indicated by the switch.

 Dmesg is:

     martin@rumolt.teuto.de:/usr/src/sys/arch/i386/compile/INSTALL
 cpu0: family 6 model 5 step 2
 cpu0: Intel Pentium II (Deschutes) (686-class)
 total memory = 255 MB
 avail memory = 232 MB
 using 3296 buffers containing 13184 KB of memory
 BIOS32 rev. 0 found at 0xfb2e0
 mainbus0 (root)
 pci0 at mainbus0 bus 0: configuration mode 1
 pci0: i/o space, memory space enabled
 pchb0 at pci0 dev 0 function 0
 pchb0: vendor 0x8086 product 0x7190 (rev. 0x03)
 ppb0 at pci0 dev 1 function 0: vendor 0x8086 product 0x7191 (rev. 0x03)
 pci1 at ppb0 bus 1
 pci1: i/o space, memory space enabled
 vendor 0x121a product 0x0003 (VGA display, revision 0x03) at pci1 dev 0 function 0 not configured
 pcib0 at pci0 dev 7 function 0
 pcib0: vendor 0x8086 product 0x7110 (rev. 0x02)
 pciide0 at pci0 dev 7 function 1: Intel 82371AB IDE controller (PIIX4) (rev. 0x01)
 pciide0: bus-master DMA support present
 pciide0: primary channel wired to compatibility mode
 wd0 at pciide0 channel 0 drive 0: <IBM-DTTA-351010>
 wd0: drive supports 16-sector pio transfers, lba addressing
 wd0: 9671 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 19807200 sectors
 wd0: 32-bit data port
 wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2
 wd1 at pciide0 channel 0 drive 1: <WDC WD205AA>
 wd1: drive supports 16-sector pio transfers, lba addressing
 wd1: 19569 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 40079088 sectors
 wd1: 32-bit data port
 wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4
 pciide0: primary channel interrupting at irq 14
 wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (using DMA data transfers)
 wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 (using DMA data transfers)
 pciide0: secondary channel wired to compatibility mode
 atapibus0 at pciide0 channel 1
 cd0 at atapibus0 drive 1: <CRD-8322B, 1998/07/17, 1.02> type 5 cdrom removable
 cd0: 32-bit data port
 cd0: drive supports PIO mode 4, DMA mode 2
 pciide0: secondary channel interrupting at irq 15
 cd0(pciide0:1:1): using PIO mode 4, DMA mode 2 (using DMA data transfers)
 vendor 0x8086 product 0x7112 (USB serial bus, revision 0x01) at pci0 dev 7 function 2 not configured
 vendor 0x8086 product 0x7113 (miscellaneous bridge, revision 0x02) at pci0 dev 7 function 3 not configured
 vendor 0x1102 product 0x0002 (audio multimedia, revision 0x05) at pci0 dev 9 function 0 not configured
 vendor 0x1102 product 0x7002 (miscellaneous input, revision 0x05) at pci0 dev 9 function 1 not configured
 fxp0 at pci0 dev 11 function 0: Intel i82557 Ethernet, rev 1
 fxp0: interrupting at irq 12
 fxp0: Ethernet address 00:a0:c9:25:13:84, 10/100 Mb/s
 nsphy0 at fxp0 phy 1: DP83840 10/100 media interface, rev. 0
 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 isa0 at pcib0
 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
 com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
 isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
 npx0 at isa0 port 0xf0-0xff: using exception 16
 pc0 at isa0 port 0x60-0x6f irq 1: color
 pc0: console
 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
 fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
 isapnp0: no ISA Plug 'n Play devices found
 biomask efe5 netmask ffe5 ttymask ffe7
 md0: internal 2048K image area
 boot device: <unknown>
 root on md0a dumps on md0b
 root file system type: ffs


From: John Hawkinson <jhawk@MIT.EDU>
To: Martin Husemann <martin@rumolt.teuto.de>
Cc: gnats-bugs@gnats.netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/10550: can't netboot from fxp0 any more
Date: Tue, 11 Jul 2000 08:24:52 -0400

 Do you have the resources to debug this yourself? I'm not
 sure what to suggest other than instrumenting the fxp driver
 or backing out recent changes.

 In message <200007101700.e6AH0P422508@rumolt.teuto.de>, Martin Husemann writes:
 >> Could you please try booting an INSTALL kernel and confirm
 >> whether fxp0 functions normally?
 >
 >Good idea. Did so: did not work. So it's not a netbooting problem,
 >but the fxp driver does not support my card currently.

 Could you give more data about how it does not work?
 Can it see packets on the network? Can it it transmit them, etc.?

 I don't have a lot of other suggestions.

 >No, sorry, though I seem to recall the latest MP test kernel still worked.

 D'you know when that was?

 --jhawk

From: Martin Husemann <martin@rumolt.teuto.de>
To: martin@rumolt.teuto.de (Martin Husemann)
Cc: jhawk@MIT.EDU (John Hawkinson), gnats-bugs@gnats.netbsd.org,
        netbsd-bugs@netbsd.org
Subject: Re: kern/10550: can't netboot from fxp0 any more
Date: Tue, 11 Jul 2000 19:25:10 +0200 (MEST)

 Ok, seems like a nway negotiation problem: the card works fine when connected
 to a 10baseT hub, but does not work with a 100baseTX full-duplex switch.

 The ifconfig shows the right medium in both cases, but no packets leave the
 card in the 100baseTX case. The card works fine when I force it to 10baseT
 half duplex mode, but not with 10baseT full-duplex (the switch doesn't lit
 the full-duplex led in this case).

 I'm not sure if I had connected this card to the 100 MBit switch when I used
 it regularily with NetBSD 1.4, so it might be this has never realy worked.


 Martin
State-Changed-From-To: open->closed 
State-Changed-By: martin 
State-Changed-When: Thu Jul 27 15:15:29 PDT 2000 
State-Changed-Why:  
Fixed in revision 1.28 of sys/dev/mii/nsphy.c, pullup to branches pending. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.