Re: lance32.c vs pcnet32.c and troubles with AMD 79C970
Alan Cox (alan@lxorguk.ukuu.org.uk)
Wed, 2 Sep 1998 15:20:40 +0100 (BST)
> eth0: transmit timed out, status 0072, resetting.
> Ring data dump: dirty_tx 0 cur_tx 16 (full) cur_rx 0.
> 80fd7018 0608 0000 80fd7810 0608 0000 80fd6018 0608 0000 80fd6810 0608 0000
> 80fd5018 0608 0000 80fd5810 0608 0000 80fd4018 0608 0000 80fd4810 0608 0000
> 80fd3018 0608 0000 80fd3810 0608 0000 80fd2018 0608 0000 80fd2810 0608 0000
> 80fd1018 0608 0000 80fd1810 0608 0000 80fd0018 0608 0000 80fd0810 0608 0000
> 83091edc 002a 0000 83091be8 002a 0000 830919f0 002a 0000 83091aec 002a 0000
> 83091ce4 002a 0000 83091de0 002a 0000 8308a448 002a 0000 8308aa50 002a 0000
> 8308b058 002a 0000 8308b660 002a 0000 8308bc68 002a 0000 8308c270 002a 0000
> 8308c878 002a 0000 8308ce80 002a 0000 8308d488 002a 0000 8308da90 002a 0000
That normally indicates a busy lan or a momentary break from it
> alloc_skb called nonatomically from interrupt 00000608
> last message repeated 3 times
> kmalloc called nonatomically from interrupt 000006a4
> last message repeated 3 times
> gfp called nonatomically from interrupt 00000003
> last message repeated 3 times
(and these are a known bug)
Alan
-
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.altern.org/andrebalsa/doc/lkml-faq.html