From: Andy Whitcroft <apw@shadowen.org>
To: Martin Bligh <mbligh@mbligh.org>
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
jgarzik@pobox.com, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
sukadev@us.ibm.com
Subject: Re: Panic in pci_call_probe from 2.6.18-mm2 and 2.6.18-mm3
Date: Fri, 20 Oct 2006 18:07:39 +0100 [thread overview]
Message-ID: <4539025B.301@shadowen.org> (raw)
In-Reply-To: <452A85D8.70806@mbligh.org>
Martin Bligh wrote:
> Badari Pulavarty wrote:
>> On Sun, 2006-10-08 at 00:02 -0700, Martin J. Bligh wrote:
>>
>>> Not sure if you've seen this already ... catching up on test results.
>>>
>>> This was on NUMA-Q, on both -mm2 and -mm3. -mm1 didn't suffer from this
>>> problem.
>>>
>>> Full logs:
>>>
>>> mm2 - http://test.kernel.org/abat/50727/debug/console.log
>>> mm3 - http://test.kernel.org/abat/51442/debug/console.log
>>>
>>> config - http://test.kernel.org/abat/51442/build/dotconfig
>>>
>>> I'm guessing from the 00000004 that the pcibus_to_node(dev->bus)
>>> is failing because bus->sysdata is NULL. The disassembly and
>>> structure offsets seem to line up for that.
>>>
>>> #define pcibus_to_node(bus) (
>>> (struct pci_sysdata *)((bus)->sysdata))->node
>>>
>>> struct pci_sysdata {
>>> int domain; /* PCI domain */
>>> int node; /* NUMA node */
>>> };
>>>
>>
>>
>> Martin,
>>
>> Jeff moved "node" to a proper field in sysdata, instead
>> of overloading sysdata itself. I think this is causing the
>> problem. I guess we could end up with sysdata = NULL in some
>> cases ? Since you are the NUMA-Q expert, where does sysdata gets set
>> for NUMA-Q ? :)
>>
>> -mm2 changed:
>>
>> #define pcibus_to_node(bus) ((long) (bus)->sysdata)
>>
>> to
>> #define pcibus_to_node(bus) ((struct pci_sysdata *)((bus)->sysdata))-
>>
>>> node
>
> Buggered if I know, that's some strange pci thing ;-)
>
> But can we revert whatever patch that was until it gets fixed, please?
Unless I am going very very mad, this has came up once before some
months ago. We went through lots of pain finding the cause of this for
NUMA-Q and fixing it. Something about not having a sysdata and needing
to initialise it.
Thought so, this was all discussed back in December 2005.
http://lkml.org/lkml/2005/12/20/226
I'll go see if I can forward port the patch and address the remaining
issues with it.
-apw
next prev parent reply other threads:[~2006-10-20 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-08 7:02 Panic in pci_call_probe from 2.6.18-mm2 and 2.6.18-mm3 Martin J. Bligh
2006-10-08 7:49 ` Andrew Morton
2006-10-09 17:19 ` Badari Pulavarty
2006-10-09 17:24 ` Martin Bligh
2006-10-09 17:34 ` Jeff Garzik
2006-10-09 18:46 ` Sukadev Bhattiprolu
2006-10-20 17:07 ` Andy Whitcroft [this message]
2006-10-20 17:37 ` Greg KH
2006-11-01 14:37 ` [PATCH] pci device ensure sysdata initialised v2 Andy Whitcroft
2006-11-08 11:22 ` Jeff Garzik
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=4539025B.301@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=pbadari@us.ibm.com \
--cc=sukadev@us.ibm.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