From: Jarek Poplawski <jarkao2@o2.pl>
To: Kirill Kuvaldin <kuvkir@epsmu.com>
Cc: netdev@vger.kernel.org, rl@hellgate.ch, linux-kernel@vger.kernel.org
Subject: Re: via-rhine: Transmit timed out problem
Date: Wed, 4 Jul 2007 11:03:05 +0200 [thread overview]
Message-ID: <20070704090305.GA2737@ff.dom.local> (raw)
In-Reply-To: <20070622121804.GB14554@zetta.epsmu.com>
On 22-06-2007 14:18, Kirill Kuvaldin wrote:
> Hi,
>
> I'm experiencing a strange problem with a via rhine network card on Ubuntu
> 7.04 (2.6.20-16-generic #2 SMP). The hardware seemed to come into an
> inconsistent state, since rmmod'ing and modprobe'ing the via-rhine driver
> back didn't help.
>
> After the problem had appeared, I could see the following in dmesg:
>
> [ 8601.971189] irq 21: nobody cared (try booting with the "irqpoll"
> option)
> [ 8601.971214] [<c01543a4>] __report_bad_irq+0x24/0x80
...
> [ 8601.971291] handlers:
> [ 8601.971293] [<f887ff10>] (usb_hcd_irq+0x0/0x60 [usbcore])
> [ 8601.971311] [<f88a7dd0>] (rhine_interrupt+0x0/0xb80 [via_rhine])
> [ 8601.971324] Disabling IRQ #21
...
> The interrupt seemed to be unhandled and got disabled by the kernel
> then. The transmission seemed to time out for some reason (probably, the
> hardware got into an inconsistent state?).
...
> Is that information sufficient for debug? Let me know if you need
> any additional data.
Your diagnose seems right but there are at least 2 suspects.
I doubt I can debug this, but maybe trying this "irqpoll" could
really tell more to somebody.
You could probably try to check this without USB (e.g. with kernel
parameter "nousb"), too.
Regards,
Jarek P.
prev parent reply other threads:[~2007-07-04 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 12:18 via-rhine: Transmit timed out problem Kirill Kuvaldin
2007-07-04 9:03 ` Jarek Poplawski [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=20070704090305.GA2737@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=kuvkir@epsmu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rl@hellgate.ch \
/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).