> On Wed, Jan 19, 2000 at 05:42:36PM +0100, Leos Bitto wrote:
>> this is a basic information:
>>
>> eepro100.c:v1.09j-t 9/29/99 Donald Becker
>> http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
>> eepro100.c: $Revision: 1.18 $ 1999/12/29 Modified by Andrey V. Savochkin <saw@msu.ru>
>> eth0: Intel PCI EtherExpress Pro100 at 0xc8037000, 00:90:27:09:24:F8, IRQ 9.
>> Board assembly 701738-003, Physical connectors present: RJ45
>> Primary interface chip i82555 PHY #1.
>> General self-test: passed.
>> Serial sub-system self-test: passed.
>> Internal registers self-test: passed.
>> ROM checksum self-test: passed (0x24c9f043).
>> Receiver lock-up workaround activated.
>>
>> and this is the debug info I get when upload stops:
>>
>> eth0: Transmit timed out: status 0050 0000 at 2071/2099 command 000c0000.
>[snip]
>>
>> Then there's a few seconds pause, then:
>>
>> eth0: Transmit timed out: status 0050 0000 at 3765/3793 command 000c0000.
>
>Well, I don't see anything in the data which may explain temporary hangs.
>What debug level you ran the driver at?
>The most interesting (but not very boring) level is 3.
>
>Have you seen any other reports from the driver?
>If the transmit timeout messages are the only messages you see on debug level
>3 I'll prepare a special version of the driver with extra debug output for
>you.
I too have experienced this problem but I found that moving the PCI
card from a shared ISA/PCI slot to an alternative PCI slot solved the
problem. The Intel card would occasionally boot up reporting that
bus-mastering didn't work.
Regards,
Nick.
-
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/
This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:22 EST