public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alex Chiang <achiang@hp.com>,
	linux-kernel@vger.kernel.org, anton@au1.ibm.com
Subject: Re: 2.6.25-rc8-mm1 panic in rpaphp_register_slot()
Date: Tue, 15 Apr 2008 20:08:56 -0700	[thread overview]
Message-ID: <48056DC8.6040909@us.ibm.com> (raw)
In-Reply-To: <20080415173656.218a6080.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Mon, 7 Apr 2008 17:42:55 -0600
> Alex Chiang <achiang@hp.com> wrote:
>
>   
>> Hi Badari,
>>
>>     
>>>>> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
>>>>> rpaphp: RPA HOT Plug PCI Controller Driver version: 0.1
>>>>> rpaphp_register_slot registering slot:path[/pci@800000020000003/pci@2,4] index[22010003], name[U787E.001.AAA3015-P2-C1] pdomain[22010003] type[16]
>>>>> Unable to handle kernel paging request for data at address 0x00000070
>>>>>           
>>>> Hrm, this is a little more information, but still not quite
>>>> enough. I'm going to take a stab in the dark and say I'm probably
>>>> doing something wrong on this line, maybe dereferencing a pointer
>>>> incorrectly:
>>>>
>>>>         retval = pci_hp_register(php_slot, slot->bus,
>>>> 				 PCI_SLOT(PCI_DN(slot->dn->child)->devfn));
>>>>         
>>> Sorry. I thought you knew this already. Disassembly clearly showed
>>> that slot->dn->child is NULL. 
>>>
>>> I confirmed it by adding printk also.
>>>       
>> This patch is a complete guess on my part (since I've not been
>> able to understand pseries architecture) but I think it should
>> fix your issue.
>>
>> Can you give it a try and let me know? It applies on top of the
>> -mm tree that includes my physical pci_slot series.
>>
>> Also, I'm hoping Linas will speak up and let me know what the
>> real answer might be. ;)
>>
>> Thanks.
>>
>> /ac
>>
>> From: Alex Chiang <achiang@hp.com>
>> Subject: rpaphp: correctly call pci_hp_register for empty PCI slots
>>
>> Unpopulated device_node slots do not have children, and
>> attempting to dereference them will result in a panic.
>>
>> Instead, attempt to derive the PCI slot number from the bus
>> itself, and failing that, default to 0.
>>
>> Signed-off-by: Alex Chiang <achiang@hp.com>
>> ---
>> diff --git a/drivers/pci/hotplug/rpaphp_slot.c b/drivers/pci/hotplug/rpaphp_slot.c
>> index 0d4cfc7..91ce6a6 100644
>> --- a/drivers/pci/hotplug/rpaphp_slot.c
>> +++ b/drivers/pci/hotplug/rpaphp_slot.c
>> @@ -121,6 +121,7 @@ int rpaphp_register_slot(struct slot *slot)
>>  {
>>  	struct hotplug_slot *php_slot = slot->hotplug_slot;
>>  	int retval;
>> +	int slot_nr;
>>  
>>  	dbg("%s registering slot:path[%s] index[%x], name[%s] pdomain[%x] type[%d]\n", 
>>  		__FUNCTION__, slot->dn->full_name, slot->index, slot->name, 
>> @@ -132,8 +133,11 @@ int rpaphp_register_slot(struct slot *slot)
>>  		return -EAGAIN;
>>  	}	
>>  
>> -	retval = pci_hp_register(php_slot, slot->bus,
>> -				 PCI_SLOT(PCI_DN(slot->dn->child)->devfn));
>> +	if (slot->bus->self)
>> +		slot_nr = PCI_SLOT(slot->bus->self->devfn);
>> +	else
>> +		slot_nr = 0;
>> +	retval = pci_hp_register(php_slot, slot->bus, slot_nr);
>>  	if (retval) {
>>  		err("pci_hp_register failed with error %d\n", retval);
>>  		return retval;
>>     
>
> Did we hear back from Badari on this?
>
> Thanks.
>   
No. It didn't help. I had to hack "slot_nr = 0" all the time to boot my 
machine.

I was trying to get some ppc expert to review the patch, as Alex was not
comfortable with the fix/hack. Linas is no longer with IBM :(

Thanks,
Badari


  parent reply	other threads:[~2008-04-16  3:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 17:53 2.6.25-rc8-mm1 panic in rpaphp_register_slot() Badari Pulavarty
2008-04-04 18:05 ` Alex Chiang
2008-04-04 20:19   ` Badari Pulavarty
2008-04-04 22:42     ` Alex Chiang
2008-04-04 23:35       ` Badari Pulavarty
2008-04-07 23:42         ` Alex Chiang
2008-04-16  0:36           ` Andrew Morton
2008-04-16  2:13             ` Alex Chiang
2008-04-16  3:08             ` Badari Pulavarty [this message]
2008-04-16  3:18               ` Alex Chiang
2008-04-16  3:20                 ` Badari Pulavarty
2008-04-16 19:32                 ` Badari Pulavarty
2008-04-16 19:59                   ` Alex Chiang
2008-04-16  3:17           ` Alex Chiang
2008-04-16  7:45             ` Benjamin Herrenschmidt
2008-04-16 17:11               ` Alex Chiang
2008-04-16 20:03                 ` Andrew Morton
2008-04-16 22:16                   ` Benjamin Herrenschmidt
2008-04-19  6:38                     ` Alex Chiang
2008-04-19  7:03                       ` Benjamin Herrenschmidt
2008-04-22  4:05                         ` Alex Chiang
2008-04-22  5:07                           ` Benjamin Herrenschmidt
2008-04-16 22:15                 ` Benjamin Herrenschmidt

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=48056DC8.6040909@us.ibm.com \
    --to=pbadari@us.ibm.com \
    --cc=achiang@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton@au1.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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