From: Stephen Hemminger <shemminger@osdl.org>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: Roland Dreier <rdreier@cisco.com>,
linux-kernel@vger.kernel.org,
MUNEDA Takahiro <muneda.takahiro@jp.fujitsu.com>,
Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>,
Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Andrew Morton <akpm@osdl.org>,
ak@suse.de, davem@davemloft.net
Subject: Re: The change "PCI: assign ioapic resource at hotplug" breaks my system
Date: Tue, 3 Oct 2006 11:02:17 -0700 [thread overview]
Message-ID: <20061003110217.5ea3e152@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <45225876.1080705@jp.fujitsu.com>
On Tue, 03 Oct 2006 21:32:54 +0900
Kenji Kaneshige <kaneshige.kenji@jp.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.
next prev parent reply other threads:[~2006-10-03 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 17:05 Roland Dreier
2006-10-02 17:28 ` Roland Dreier
2006-10-03 12:32 ` Kenji Kaneshige
2006-10-03 17:51 ` Roland Dreier
2006-10-03 18:02 ` Stephen Hemminger [this message]
2006-10-04 5:46 ` Kenji Kaneshige
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061003110217.5ea3e152@dxpl.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muneda.takahiro@jp.fujitsu.com \
--cc=rdreier@cisco.com \
--cc=takeuchi_satoru@jp.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®