RE: HEADS UP: fxp breakage

Ok. Here's the information requested. This is taken from the boxes running a
working, older kernel (otherwise wouldn't be able to get to them remotely). I
can get the same info with the broken kernel come Monday should that be
necessary. Hope this helps!
 
1) dell poweredge 4350
fxp0: flags=18843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.10.10.253 netmask 0xffff0000 broadcast 10.10.255.255
        ether 00:90:27:5a:22:7b
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active

fxp0_at_pci0:12:0: class=0x020000 card=0x000c8086 chip=0x12298086 rev=0x08
hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82557/8/9 EtherExpress PRO/100(B) Ethernet Adapter'
    class    = network
    subclass = ethernet
fxp0: <Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet> port 0xdcc0-0xdcff
mem 0xfe000000-0xfe0fffff,0xfe100000-0xfe100fff irq 14 at device 12.0 on pci0

2) asus kg7
fxp0: flags=18843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.10.10.201 netmask 0xffff0000 broadcast 10.10.255.255
        ether 00:90:27:66:62:1a
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
fxp0_at_pci0:11:0: class=0x020000 card=0x000c8086 chip=0x12298086 rev=0x08
hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82557/8/9 EtherExpress PRO/100(B) Ethernet Adapter'
    class    = network
    subclass = ethernet
fxp0: <Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet> port 0xe000-0xe03f
mem 0xf9000000-0xf90fffff,0xf9101000-0xf9101fff irq 10 at device 11.0 on pci0
 
both machines are running the following kernel config:
 
options         INCLUDE_CONFIG_FILE
machine         i386
cpu             I686_CPU
ident           "fbsd5-uni"
makeoptions     DEBUG=-g
options         KTRACE
options         DDB
options         DDB_UNATTENDED
options         ALT_BREAK_TO_DEBUGGER
#options        SCHED_4BSD
options         SCHED_ULE
options         COMPAT_43
options         COMPAT_FREEBSD4
options         INET
options         TCP_DROP_SYNFIN
options         RANDOM_IP_ID
options         FFS
options         SOFTUPDATES
options         UFS_DIRHASH
#options                GEOM_APPLE
#options                UFS_EXTATTR
#options                UFS_EXTATTR_AUTOSTART
#options        UFS_ACL
options         SYSVSHM
options         SYSVMSG
options         SYSVSEM
#options                P1003_1B_SEMAPHORES
options         _KPOSIX_PRIORITY_SCHEDULING
options         KBD_INSTALL_CDEV
device          isa
device          pci
device          agp
device          fdc
device          npx
device          atkbdc
device          atkbd
device          psm
device          vga
device          sc
options         SC_NORM_ATTR=(FG_GREEN|BG_BLACK)
options         SC_NORM_REV_ATTR=(FG_YELLOW|BG_GREEN)
options         SC_KERNEL_CONS_ATTR=(FG_RED|BG_BLACK)
options         SC_KERNEL_CONS_REV_ATTR=(FG_BLACK|BG_RED)
device          sio
options         CONSPEED=19200
device          ppc
device          ppbus
device          lpt
device          plip
device          ppi
device          vpo
# SCSI / RAID
options         SCSI_DELAY=5000
device          ahc
device          amr
device          scbus
device          ch
device          da
device          sa
device          cd
device          pt
device          targ
device          targbh
device          pass
device          ses
options         SES_ENABLE_PASSTHROUGH
# ATAPI
device          ata
device          atadisk
device          atapicd
device          atapifd
device          atapist
device          atapicam
options         ATA_STATIC_ID
# NICs
device          miibus
device          fxp
options         DEVICE_POLLING
options         HZ=1000
# Pseudo devices
device          random
device          loop
device          ether
device          tun
device          pty
device          gif
device          bpf

Robin P. Blanchard wrote:
> Following sources still yield unresponsive fxp interface. The same
behavious
> occurs on both of my test boxes (dell 4350 and home-grown athlon xp), each
> having identical Intel Pro 100+M nics with v4.1.0.9 intel PXE rom.
>
> # fgrep -h \*\ \$FreeBSD /usr/src/sys/dev/fxp/*
>
>  * $FreeBSD: src/sys/dev/fxp/if_fxp.c,v 1.154 2003/04/03 20:39:43 mux Exp $
>  * $FreeBSD: src/sys/dev/fxp/if_fxpreg.h,v 1.30 2003/04/03 18:39:48 mux Exp
$
>  * $FreeBSD: src/sys/dev/fxp/if_fxpvar.h,v 1.24 2003/04/02 16:47:16 mux Exp
$
>  * $FreeBSD: src/sys/dev/fxp/rcvbundl.h,v 1.1 2001/10/25 05:23:31 jlemon
Exp
> $

Could everyone which has problems with the fxp(4) driver mail me some
informations ?  I'd need the exact symptoms, the output of ifconfig on
the interface, the part of pciconf -lv relevant to your fxp card, your
kernel configuration file and the output of dmesg.  That would be help
me a lot to understand what's going on, since I can't reproduce these
problems on any of my fxp(4) cards.

Since this is a commonly used driver in the FreeBSD community, I've put
a kernel module for fxp online, built with the sources prior to the
busdma commit.  It's at http://people.freebsd.org/~mux/if_fxp.ko.gz.


> Reverting back to kernel sources from 11 April yield functional interface.
11 April ?  Did you make a typo ?