linux-kernel - Re: The change "PCI: assign ioapic resource at hotplug" breaks my system

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: <45234ABF.5030107@jp.fujitsu.com>
Date:	Wed, 04 Oct 2006 14:46:39 +0900
From:	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>
To:	Stephen Hemminger <shemminger@...l.org>,
	Roland Dreier <rdreier@...co.com>
Cc:	linux-kernel@...r.kernel.org,
	MUNEDA Takahiro <muneda.takahiro@...fujitsu.com>,
	Satoru Takeuchi <takeuchi_satoru@...fujitsu.com>,
	Kristen Carlson Accardi <kristen.c.accardi@...el.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Andrew Morton <akpm@...l.org>, ak@...e.de, davem@...emloft.net
Subject: Re: The change "PCI: assign ioapic resource at hotplug" breaks my
 system

Stephen, Roland,

Thank you very much for testing the patch.

Thanks,
Kenji Kaneshige


Stephen Hemminger wrote:
> On Tue, 03 Oct 2006 21:32:54 +0900
> Kenji Kaneshige <kaneshige.kenji@...fujitsu.com> wrote:
> 
>> Roland Dreier wrote:
>>> The change "PCI: assign ioapic resource at hotplug" (commit
>>> 23186279658cea6d42a050400d3e79c56cb459b4 in Linus's tree) makes
>>> networking stop working on my system (SuperMicro H8QC8 with four
>>> dual-core Opteron 885 CPUs).  In particular, the on-board NIC stops
>>> working, probably because it gets assigned the wrong IRQ (225 in the
>>> non-working case, 217 in the working case)
>>>
>>> With that patch applied, e1000 doesn't work.  Reverting just that
>>> patch (shown below) from Linus's latest tree fixes things for me.
>>>
>>> Please let me know what other debug information might be useful.
>>>
>> The cause of this problem might be an wrong assumption that the 'start'
>> member of resource structure for ioapic device has non-zero value if the
>> resources are assigned by firmware. The 'start' member of ioapic device
>> seems not to be set even though the resources were actually assigned to
>> ioapic devices by firmware.
>>
>> I made a patch to fix this problem against 2.6.18-git18. This patch
>> checks command register instead of checking 'start' member to see if
>> the ioapic is already enabled by firmware. Unfortunately, I don't have
>> any system to reproduce this problem. Could you please try it and let
>> me know whether the problem is fixed? If the patch below fixes the
>> problem, I'll resend it with description and Signed-off-by.
>>
>> Thanks,
>> Kenji Kaneshige
>>
> 
> This also fixes my problems with the built in tg3 on the dual CPU Opteron
> IBM workstation.
> 
> 


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