Re: 2.6.25-rc8-mm1 panic in rpaphp_register_slot()

From: Badari Pulavarty
Date: Fri Apr 04 2008 - 19:35:45 EST



On Fri, 2008-04-04 at 16:42 -0600, Alex Chiang wrote:
> * Badari Pulavarty <pbadari@xxxxxxxxxx>:
> >
> > On Fri, 2008-04-04 at 12:05 -0600, Alex Chiang wrote:
> > > Hi Badari,
> > >
> > > * Badari Pulavarty <pbadari@xxxxxxxxxx>:
> > > > Hi Andrew & Alex,
> > > >
> > > > I get following panic in rpaphp_register_slot() on
> > > > 2.6.25-rc8-mm1. Known issue ?
> > >
> > > I know about it now... :-/
> > >
> > > Any chance you could turn debugging on for both rpaphp and
> > > pci_hotplug?
> > >
> >
> > I did set "debug" variables in rpaphp_core.c and pci_hotplug_core.c
> > to 1. But it didn't give any more information. How do I enable
> > the debug ?
>
> If those modules are built into your kernel, then you'll need to
> modify the kernel command line to add:
>
> rpaphp.debug=1 pci_hotplug.debug=1
>
> If you're manually modprobing them:
>
> $ modprobe pci_hotplug debug=1
> $ modprobe rpaphp debug=1
>
> > I just changed dbg() to printk() in rpaphp_register_slot() to
> > print out more information.
> >
> > Thanks,
> > 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.

Thanks,
Badari

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/