Re: 3c59x problem

Chris Wedgwood (chris@cybernet.co.nz)
Sat, 23 Jan 1999 18:40:05 +1300


On Sat, Jan 23, 1999 at 05:29:40AM +0000, Mike wrote:

> > eth0: 3Com 3c905 Boomerang 100baseTx at 0xff00, 00:60:08:15:9b:dc,IRQ 11
> > 8K word-wide RAM 3:5 Rx:Tx split, autoselect/NWay Autonegotiation interface.
> > MII transceiver found at address 24, status 7869.
> > Enabling bus-master transmits and whole-frame receives.
> >

> eth1: 3Com 3c905 Boomerang 100baseTx at 0xe400, 00:60:08:55:1a:73, IRQ 9
> 8K word-wide RAM 3:5 Rx:Tx split, autoselect/MII interface.
> MII transceiver found at address 24, status 786d.
> Enabling bus-master transmits and whole-frame receives.
>
> Appears to behave normally, but occasionally I get things like:
>
> eth1: transmit timed out, tx_status 00
> status e000.
> Flags; bus-master 1, full 1; dirty 91590
> current 91606.
> Transmit list 00000000 vs. c79fba60.
> 0: @c79fba00 length 80000082 status 00000082
> 1: @c79fba10 length 8000002a status 0000002a
> 2: @c79fba20 length 800000a2 status 000000a2
> 3: @c79fba30 length 800000a2 status 000000a2
> 4: @c79fba40 length 8000002a status 8000002a
> 5: @c79fba50 length 8000002a status 8000002a
> 6: @c79fba60 length 80000057 status 00000057
> 7: @c79fba70 length 80000073 status 00000073
> 8: @c79fba80 length 80000073 status 00000073
> 9: @c79fba90 length 80000082 status 00000082
> 10: @c79fbaa0 length 80000082 status 00000082
> 11: @c79fbab0 length 80000082 status 00000082
> 12: @c79fbac0 length 80000082 status 00000082
> 13: @c79fbad0 length 80000082 status 00000082
> 14: @c79fbae0 length 80000057 status 00000057
> 15: @c79fbaf0 length 80000057 status 00000057
> eth1: Resetting the Tx ring pointer.

That _ALL_ I get with the new driver (0.99H). I noticed the new
driver says 'autoselect/MII interface' whereas the old (0.99E) one
said 'autoselect/NWay Autonegotiation'.

I tried futzing options here, forcing the media type to one of other,
but alas, still didn't work.

I'm back to using 0.99E which whilst isn't really a problem as I
don't run stock kernels anyhow, does leave me wondering how many
other people this might affect.....

-Chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/