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  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]
Date:	Wed, 10 Jul 2013 03:43:53 +0000
From:	"Fujinaka, Todd" <>
To:	"Brandeburg, Jesse" <>,
	Pavel Machek <>
CC:	"" 
	"Allan, Bruce W" <>,
	"Brandeburg, Jesse" <>,
	"Ronciak, John" <>,
	"" <>
Subject: RE: [E1000-devel] e1000e on thinkpad x60: interrupt problem

The latest kernel should turn off ASPM as well, but you should be able to check by looking at lspci -vvv. I think LnkCtl should say "ASPM disabled."

Sorry for top-posting.

Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
(503) 712-4565

-----Original Message-----
From: Jesse Brandeburg [] 
Sent: Tuesday, July 09, 2013 2:41 PM
To: Pavel Machek
Cc:; Allan, Bruce W; Brandeburg, Jesse; Ronciak, John;
Subject: Re: [E1000-devel] e1000e on thinkpad x60: interrupt problem

On Tue, 9 Jul 2013 22:48:54 +0200
Pavel Machek <> wrote:

> Yeah, of course you need to ask e1000e if it generated the interrupt. 
> That part works. The part that actually generates the interrupt does 
> not. Take a look at original mail...
> packet comes
> e1000e sets E1000_ICR_INT_ASSERTED bit e1000e tries to generate an 
> interrupt and fails 50msec passes

^^ thats the ASPM timeout length.

> AHCI generates interrupt
> all the handlers are called
>     AHCI processes its interrupt, handles disk read
>     e1000_intr notices E1000_ICR_INT_ASSERTED bit, delivers the packet.
> Network still works, only slowly. Ping goes lower when I use the disk. 
> That matches what I see.
> Do you have other explanation?

Regardless of what others are saying I believe you have an issue with ASPM being enabled.  All the discussion about shared interrupts, is just a distraction.  This issue would still occur (and just be worse) without a shared interrupt.

You already mentioned that a kernel hack to disable ASPM fixes it, but you can just boot with different options to turn off ASPM.


There are known issues with ASPM on this part, and it definitely needs to be off.  If your bios has the option to turn it off, that is the best way to disable it, second choice is to turn it off using the kernel option.

Hope this helps,

See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
E1000-devel mailing list
To learn more about Intel&#174; Ethernet, visit
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists