On Thu, Nov 29, 2007 at 06:19:41PM -0700, Alex Chiang wrote: < snip > > > [<ffffffff802499bc>] kthread+0x47/0x73 > > [<ffffffff8020cc98>] child_rip+0xa/0x12 > > [<ffffffff80249975>] kthread+0x0/0x73 > > [<ffffffff8020cc8e>] child_rip+0x0/0x12 > > Maybe we're trying to kick off a hotplug event on the wrong slot? > I really have no idea... One hotplug event related difference that I believe I noticed between the x3850 were I did not see the problem and the x3950 is the hotplug event arrival location. On the x3850 the handler receives the handle for the transparent p2p bridge above the slot. On the x3950 I believe the handler is receiving the handle for the root bridge (directly above the transparent p2p bridge). acpiphp installs a handler for each of these possible arrival locations. pci_slot installs a handler for neither location which seems like it should be okay. I notice that acpi_pci_register_driver() was only being used by acpiphp before pci_slot. Perhaps your changes are flushing out some sort of ACPI core coexistence issue not seen previously because there was only a single user? My silly idea is probably no better than your no idea. :) > > > Code: ff ff ff ff 40 23 2c 88 ff ff ff ff 00 c8 c6 3b 10 81 ff ff > > RIP [<ffffffff882c2344>] :pci_slot:__this_module+0x21c4/0xfffffffffffff204 > > RSP <ffff81103fa43ea8> > > Can you apply this debug patch on top of your tree, and send me > the output? > > I'd be curious to see the output for your failure case: > > # modprobe pci_slot debug=1 > # modprobe acpiphp debug=1 Someone else is using the system right now so I may not be able to do this until next week. Gary -- Gary Hade System x Enablement IBM Linux Technology Center 503-578-4503 IBM T/L: 775-4503 garyhade@xxxxxxxxxx http://www.ibm.com/linux/ltc - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
