messages
To: matthew green <mrg@eterna.com.au>
From: john heasley <heas@shrubbery.net>
List: port-sparc64
Date: 10/02/2001 03:05:31
does anyone's hme actually autoneg with a switch properly? it doesnt
work with foundry or hp procurve. perhaps that is contributing.
ifconfig doesnt appear to indicate which duplex it is running
media: Ethernet autoselect (100baseTX)
nor does there appear to be a knob to specify the duplex.
Tue, Oct 02, 2001 at 12:54:31PM +1000, matthew green:
>
> | hme0: status=20001<GOTFRAME,NORXD>
> | hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> | hme0: status=20001<GOTFRAME,NORXD>
>
> NORXD means the hme is unable to find any available
> ring descriptors for the frames it's receiving.
>
> The last modification to hme was on Jul 7, so that's
> unlikely to be the problem.
>
> Make sure you do a clean build. If that doesn't work,
> you can try reverting to version 1.39 of sparc64/dev/iommu.c
> and see if that solves your problem.
>
>
>
> FWIW, i've seen these sort of messages from my hme in the ultra5
> since basically it started working. i've talked to pk about this
> in the past and we were unable to determine the cause. i'm not
> sure pk is on port-sparc64.
>
>
> i don't get them regularly, but the do seem to come more often
> with heavy load. i've seen exactly 729 of these status messages
> since 20010203 (when my /var/log/kern starts) to today. this is
> not a new problem. i do not see this on the sbus machines with
> hme, but i've only had them active for a few days now. the
> messages range from:
>
>
> hme0: status=1000020<RFIFOVF,HOSTTOTX>
> hme0: status=1000021<GOTFRAME,RFIFOVF,HOSTTOTX>
> hme0: status=1000120<RFIFOVF,SENTFRAME,HOSTTOTX>
> hme0: status=1000121<GOTFRAME,RFIFOVF,SENTFRAME,HOSTTOTX>
> hme0: status=10020<RFIFOVF,RXTOHOST>
> hme0: status=10021<GOTFRAME,RFIFOVF,RXTOHOST>
> hme0: status=1010021<GOTFRAME,RFIFOVF,RXTOHOST,HOSTTOTX>
> hme0: status=1010120<RFIFOVF,SENTFRAME,RXTOHOST,HOSTTOTX>
> hme0: status=1010121<GOTFRAME,RFIFOVF,SENTFRAME,RXTOHOST,HOSTTOTX>
> hme0: status=10120<RFIFOVF,SENTFRAME,RXTOHOST>
> hme0: status=10121<GOTFRAME,RFIFOVF,SENTFRAME,RXTOHOST>
> hme0: status=120<RFIFOVF,SENTFRAME>
> hme0: status=121<GOTFRAME,RFIFOVF,SENTFRAME>
> hme0: status=20001<GOTFRAME,NORXD>
> hme0: status=20<RFIFOVF>
> hme0: status=21<GOTFRAME,RFIFOVF>
> hme0: status=3000120<RFIFOVF,SENTFRAME,HOSTTOTX,TXALL>
> hme0: status=3000121<GOTFRAME,RFIFOVF,SENTFRAME,HOSTTOTX,TXALL>
> hme0: status=30001<GOTFRAME,RXTOHOST,NORXD>
> hme0: status=3010120<RFIFOVF,SENTFRAME,RXTOHOST,HOSTTOTX,TXALL>
> hme0: status=3010121<GOTFRAME,RFIFOVF,SENTFRAME,RXTOHOST,HOSTTOTX,TXALL>
> hme0: status=30101<GOTFRAME,SENTFRAME,RXTOHOST,NORXD>
> hme0: status=8000<DTIMEXP>
> hme0: status=8001<GOTFRAME,DTIMEXP>
> hme0: status=8100<SENTFRAME,DTIMEXP>