Skip to contentSkip to conversation

need contact of via-rhine developers

DISCUSSION H.Rosmanith (Kernel Mailing List) 1 participant 1 message Aug 20, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 2 lines

You will probably need more log information than the driver can provide.

e.g. like this:

: Aug 21 07:37:22 samiel kernel: > via_rhine_tx
: Aug 21 07:37:22 samiel kernel: Tx scavenge 11 status 80000000. : Aug 21 07:37:22 samiel kernel: eth0: exiting interrupt, status=0000. : Aug 21 07:37:22 samiel kernel: > via_rhine_start_tx
: Aug 21 07:37:22 samiel kernel: stopping netif_queue
: Aug 21 07:37:22 samiel kernel: eth0: Transmit frame #36 queued in slot 4. : Aug 21 07:37:22 samiel kernel: eth0: Interrupt, status 0002. : Aug 21 07:37:22 samiel kernel: > via_rhine_tx
: Aug 21 07:37:22 samiel kernel: Tx scavenge 11 status 80000000. : Aug 21 07:37:22 samiel kernel: eth0: exiting interrupt, status=0000. : Aug 21 07:37:26 samiel kernel: eth0: VIA Rhine monitor tick, status 0000. : Aug 21 07:37:26 samiel kernel: NETDEV WATCHDOG: eth0: transmit timed out : Aug 21 07:37:26 samiel kernel: > via_rhine_tx_timeout

this indicates that the netif_queue is stopped, but never started again, allthough:

        if ((np->cur_tx - np->dirty_tx) < TX_QUEUE_LEN - 4)
                netif_wake_queue (dev);

maybe something is wrong with that one?

I'll add more debugs...

regards,
h.rosmanith