All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Habersack <grendel@caudium.net>
To: linux-kernel@vger.kernel.org
Subject: [BUG] 2.5.70-mm8 and the 3com NIC driver
Date: Thu, 12 Jun 2003 23:46:26 +0200	[thread overview]
Message-ID: <20030612214626.GA1770@thanes.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]

Hello,

  As mentioned in the subject, the kernel doesn't work with a 3Com 3c905
card. Here's what's shown on the screen and in the logs on both startup and
in intervals during normal system run:

NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out, tx_status 00 status e601.
diagnostics: net 0cc0 media 8802 dma 0000003b fifo 0000
eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
Flags; bus-master 1, dirty 240(0) current 240(0)
Transmit list 00000000 vs. efce2200.
0: @efce2200  length 8000002a status 0000002a
1: @efce22a0  length 80000050 status 00000050
2: @efce2340  length 8000002a status 0000002a
3: @efce23e0  length 8000002a status 0000002a
4: @efce2480  length 8000002a status 0000002a
5: @efce2520  length 80000036 status 00000036
6: @efce25c0  length 80000036 status 00000036
7: @efce2660  length 80000036 status 00000036
8: @efce2700  length 80000050 status 00000050
9: @efce27a0  length 80000050 status 00000050
10: @efce2840  length 80000050 status 00000050
11: @efce28e0  length 80000050 status 00000050
12: @efce2980  length 80000050 status 00000050
13: @efce2a20  length 80000050 status 00000050
14: @efce2ac0  length 80000050 status 80000050
15: @efce2b60  length 80000050 status 80000050
eth0: Resetting the Tx ring pointer.

All the earlier -mm kernels worked fine in this regard,

marek

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-06-12 21:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-12 21:46 Marek Habersack [this message]
2003-06-13  7:27 ` [BUG] 2.5.70-mm8 and the 3com NIC driver Thomas Schlichter
2003-06-13 17:07   ` Marek Habersack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030612214626.GA1770@thanes.org \
    --to=grendel@caudium.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.