linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: jingai@shell.faradic.net
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 3COM 3c905c-TX-M.... works, or not?
Date: Sun, 3 Dec 2000 08:44:50 +0100 (CET)	[thread overview]
Message-ID: <200012030744.IAA00755@piglet.grunz.lu> (raw)
In-Reply-To: <200012030028.eB30SHR04153@shell.faradic.net>


Hi there,

On   2 Dec, this message from Jonathan Lane echoed through cyberspace:
> A 'cat /proc/interrupts' shows that there have
> been no interrupts serviced for the card:
>
>            CPU0
>   1:          0   PMAC-PIC      eth1

Hmmm, IRQ 1? Weird for a PCI device....

>  20:          0   PMAC-PIC      NMI - XMON
>  24:       9202   PMAC-PIC      usb-ohci

I suppose your USB is on a PCI card in a PCI slot? I'd expect the other
PCI slot's interrupts to be next to this one, then.

> eth1: 3Com 3c905C Tornado at 0x1000,  00:01:02:c1:88:c2, IRQ 1

Everything OK, except IRQ1...

> eth1: transmit timed out, tx_status 00 status e601.
> eth1: Interrupt posted but not delivered -- IRQ blocked by another device?

Yes, IRQ problem.... Could you send a complete lspci -vv along, together
with lspci -bvv (bus view)?

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-12-03  7:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-03  0:28 3COM 3c905c-TX-M.... works, or not? Jonathan Lane
2000-12-03  7:44 ` Michel Lanners [this message]

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=200012030744.IAA00755@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=jingai@shell.faradic.net \
    --cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).