On Sat, 2013-02-02 at 23:27 +0100, Rafael J. Wysocki wrote: > On Saturday, February 02, 2013 08:28:01 PM Steven Newbury wrote: > > > > Tried merging with linux-pm/bleeding-edge, same behaviour: > > > > > > > > [ 3589.013578] ACPI: \_SB_.PCI0.PCIE.GDCK: undocking > > > > [ 3589.585356] vgaarb: device changed decodes: > > > > PCI:0000:00:02.0,olddecodes=none,decodes=io+mem:owns=none [ > > > > 3589.585422] ACPI: Delete PCI Interrupt Routing Table for 0000:04 [ > > > > 3589.585426] pci 0000:03:08.0: Oops, 'acpi_handle' corrupt [ > > > > 3589.585446] pci_bus 0000:04: busn_res: [bus 04] is released > > > > > > > > 03:08.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI > > > > Express-to-PCI Bridge (rev aa) > > > > 04:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI > > > > Manhattan [Mobility Radeon HD 5430 Series] > > > > 04:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Cedar HDMI > > > > Audio [Radeon HD 5400/6300 Series] > > > > > > That's because of a bug in the dock code I believe. > > > > > > If you're willing to test patches, I can try to cook up something to > > > debug/fix this. > > Sure, I'm always willing to test patches. > > Can you please test this one in addition to the $subject one: > > https://patchwork.kernel.org/patch/2068621/ > > and see if that helps? No change wrt the "Oops, 'acpi_handle' corrupt". Just to be clear, this happens during the logical undock phase after writing to "/sys/devices/platform/dock.0/undock". Right now I manually tear down the seat associated with the dock gfx card (waiting for the X server to terminate and requiring SIGSTOPing the gdm process to stop it respawning!) then attempt radeon module unload, if it succeeds I write to the undock file, otherwise I fail the undock; I saw there is intention to put it infrastructure to have drivers prepare themselves for removal on 'eject' request, that would be really helpful. A couple of other things regarding the dock system: Making an undock/eject request with the dock eject button results in an ACPI 'undock' event, same ACPI event happens when the electrical/physical undock occurs. The IDE docks seem not to be working; maybe I need to turn on some debugging. This used to work at some point. Feb 2 23:51:28 infinity kernel: ACPI: \_SB_.PCI0.IDE1.PRI_.MAST: docking Feb 2 23:51:28 infinity kernel: ACPI: \_SB_.PCI0.IDE1.PRI_.MAST: Unable to dock! -- 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
