linux-kernel - Re: via-rhine: Transmit timed out problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070704090305.GA2737@ff.dom.local>
Date:	Wed, 4 Jul 2007 11:03:05 +0200
From:	Jarek Poplawski <jarkao2@...pl>
To:	Kirill Kuvaldin <kuvkir@...mu.com>
Cc:	netdev@...r.kernel.org, rl@...lgate.ch,
	linux-kernel@...r.kernel.org
Subject: Re: via-rhine: Transmit timed out problem

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/