<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [r600g][kms][ATI RV710] r600_pcie_gart_tlb_flush+0xf5/0x110" href="https://bugs.freedesktop.org/show_bug.cgi?id=61529#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [r600g][kms][ATI RV710] r600_pcie_gart_tlb_flush+0xf5/0x110" href="https://bugs.freedesktop.org/show_bug.cgi?id=61529">bug 61529</a> from <a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> Alex Deucher</a> <pre>(In reply to Thaddaeus Tintenfisch from <a href="show_bug.cgi?id=61529#c9">comment #9</a>) > The first two warnings are pretty much identical (3 warnings in total). > Should I create two new reports which reference the patch from this report? > > The main issue here is that the vgaswitcheroo interface is no longer > available after powering off the dGPU > (/sys/kernel/debug/vgaswitcheroo/switch is gone). > > From the log: > > [ 60.462677] vga_switcheroo: disabled It's still an acpi hotplug bug: [ 60.454402] [<ffffffffc022c295>] radeon_pci_remove+0x15/0x20 [radeon] [ 60.454407] [<ffffffff813e470f>] pci_device_remove+0x3f/0xc0 [ 60.454414] [<ffffffff814e6a86>] __device_release_driver+0x96/0x130 [ 60.454418] [<ffffffff814e6b43>] device_release_driver+0x23/0x30 [ 60.454423] [<ffffffff813df012>] pci_stop_bus_device+0x92/0xa0 [ 60.454427] [<ffffffff813df136>] pci_stop_and_remove_bus_device+0x16/0x30 [ 60.454432] [<ffffffff813fbf23>] disable_slot+0x53/0xa0 [ 60.454436] [<ffffffff813fc642>] acpiphp_check_bridge.part.8+0xd2/0xf0 [ 60.454440] [<ffffffff813fcec2>] acpiphp_hotplug_notify+0xd2/0x220 [ 60.454445] [<ffffffff813fcdf0>] ? acpiphp_post_dock_fixup+0xc0/0xc0 [ 60.454450] [<ffffffff81429fb7>] acpi_device_hotplug+0x3b0/0x3f8 [ 60.454454] [<ffffffff814233ae>] acpi_hotplug_work_fn+0x1f/0x2b The acpiphp driver is trying to remove the driver after switcheroo has turned it off. It should not not kicking in and removing the driver. It looks like there is some other broken case in the acpiphp code. I'd suggest filing a new acpiphp bug on bugzilla.kernel.org and referencing this bug: <a href="https://bugzilla.kernel.org/show_bug.cgi?id=61891">https://bugzilla.kernel.org/show_bug.cgi?id=61891</a> or adding a comment to that bug that there are still cases that are broken.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>