netdev - Re: quirk_e100_interrupt() called too early

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: <46894BFF.70405@intel.com>
Date:	Mon, 02 Jul 2007 12:03:27 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	Nils Rennebarth <nils.rennebarth@...kwerk-ec.com>
CC:	Bjorn Helgaas <bjorn.helgaas@...com>,
	"Kok, Auke" <auke-jan.h.kok@...el.com>,
	Marian Balakowicz <m8@...ihalf.com>,
	"linux-pci@...ey.karlin.mff.cuni.cz" 
	<linux-pci@...ey.karlin.mff.cuni.cz>,
	"len.brown@...el.com" <len.brown@...el.com>,
	NetDev <netdev@...r.kernel.org>
Subject: Re: quirk_e100_interrupt() called too early

Nils Rennebarth wrote:
> Bjorn Helgaas wrote:
>> On Thursday 28 June 2007 10:01:08 am Kok, Auke wrote:
>> I copied Nils Rennebarth, who originally reported the bug:
>>   http://bugzilla.kernel.org/show_bug.cgi?id=5918
>> in case he can test your patch.
 >
> Most of the embedded boards we now work with appear to exhibit the same 
> behaviour: During boot the
> 
> Firmware left 0000:01:05.0 e100 interrupts enabled, disabling
> 
> message appears for all four e100 nics. (The mainboard is a em-8510A 
> btw.) When I have time I could try if the quirk still works with the
> mentioned patch, but I am quite busy with other things at the moment.

well, we're too late for 2.6.22 I think so you have some time. However I'd like 
to make sure we can get this in with 2.6.23. Alternatively, someone could always 
send me one of these boards ;)

Thanks for taking the time to test

Auke
-
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