Subject: Re[2]: Update to i386: 'ex0: uplistptr was 0'
To: None <>
From: Simon Hitzemann <>
List: current-users
Date: 09/26/2002 13:57:33

> We've seen those "uplistptr" messages earlier, too. A quick count
> shows six separate messages for just *one* of the ex0/ex1 between
> 2001/11/01 and 2002/08/26. But after 9/23 the machine has lost network
> connectivity three times (twice yesterday, once today), each time
> functionality was restored by logging in from the console, and checking
> whether things work. Each time there has been the same "uplistptr" message
> for *both* interfaces.

I've got:

ex0 at pci0 dev 9 function 0: 3Com 3c905B-TX 10/100 Ethernet (rev. 0x30)
ex0: interrupting at irq 11
ex0: MAC address 00:50:da:37:bb:d7
exphy0 at ex0 phy 24: 3Com internal media interface
exphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

ex1 at pci0 dev 11 function 0: 3Com 3c905-TX 10/100 Ethernet (rev. 0x0)
ex1: interrupting at irq 10
ex1: MAC address 00:60:08:55:8e:e2
nsphy0 at ex1 phy 24: DP83840 10/100 media interface, rev. 1
nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

I always have those uplistptr messages for ex1 no matter to which
network it is connected to, now while I was writing this messages I
noticed, that ex0 is using exphy while ex1 is using nsphy. Might that
be the reason for it? Those messages only appear when there's much
traffic on that interface, but I think an Athlon 800 should be able to
handle it.
For some testing purposes I mounted a 20GB Windows NFS share, scanned
it for virii and got 24 of those messages while scanning it.

Best regards,