netdev - Re: 3c59x: shared interrupt 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090312143930.GA17955@newton.mathematik.tu-chemnitz.de>
Date:	Thu, 12 Mar 2009 15:39:30 +0100
From:	Steffen Klassert <klassert@...hematik.tu-chemnitz.de>
To:	Gerhard Pircher <gerhard_pircher@....net>
Cc:	akpm@...ux-foundation.org, netdev@...r.kernel.org,
	shemminger@...tta.com
Subject: Re: 3c59x: shared interrupt problem

On Wed, Mar 11, 2009 at 11:42:40PM +0100, Gerhard Pircher wrote:
> 
> > Your first report showed dnComplete as a pending interrupt source.
> > Since the driver uses tx_interrupt_mitigation, this happens just if the 
> > tx ring is full. Could you please test the patch below? This disables
> > tx_interrupt_mitigation, so the dnComplete interrupt will be triggered 
> > with every packet.
> I disabled tx_interrupt_mitigation and tested it with and w/o the patch
> for boomerang_interrupt(). The network transfer stalls in both cases
> sooner or later.
> 
> Here are two photos from the kernel output:
> - no tx_interrupt_mitigation and patch for booomerang_interrupt():
> http://boot.homelinux.org:8080/kernel/oops_boomerang_irq_tx_irq_mitig.jpg
> - no tx_interrupt_mitigation only:
> http://boot.homelinux.org:8080/kernel/oops_tx_irq_mitig.jpg
> 

Your pictures show just a message at shutdown. Are there any other unusual
messages from the 3c59x driver in your logs? In particular I'm interested in 
"transmit timed out" messages.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html