| What | Removed | Added |
|---|---|---|
| Assignee | xorg-driver-ati@lists.x.org | dri-devel@lists.freedesktop.org |
| QA Contact | xorg-team@lists.x.org | |
| Product | xorg | DRI |
| Component | Driver/Radeon | DRM/Radeon |
| What | Removed | Added |
|---|---|---|
| Summary | [ATI RV710] r600_pcie_gart_tlb_flush+0xf5/0x110 | [r600g][kms][ATI RV710] r600_pcie_gart_tlb_flush+0xf5/0x110 |
| What | Removed | Added |
|---|---|---|
| See Also | https://bugzilla.kernel.org/show_bug.cgi?id=3D49531 |
| What | Removed | Added |
|---|---|---|
| See Also | https://launchpad.net/bugs/1170917 |
A commit in 3.17-rc6 is causing this kernel panic to occur whe= n switching off the dedicated GPU for the first time after booting the system. This is still reproducible with 4.1-rcX and radeon.runpm=3D0 (plus radeon.d= pm=3D0).
| What | Removed | Added |
|---|---|---|
| Severity | normal | major |
Created attachment 116867 [details] [review] drm/radeon: Don't flush the GART TLB if rdev->gart.ptr =3D=3D NULL Does this patch fix the problem?
I will test your patch as soon as possible. Meanwhile, I just finished bisecting the kernel with the result: b440bde74f043c8ec31081cb59c9a53ade954701 is the first bad commit
Created attachment 116881 [details]
dmesg snippet
I have applied radeon-gart_tlb_flush-NULL.diff to git master and it does fix
the hard lockup.
However, powering off the dedicated GPU still triggers some kernel panics (see
attached log file).
You are probably seeing this bug (bug is in the pci hotplug system): https://bugzilla.kernel.org/show_bug.cgi?id=61891 See if the latest patch there helps.
Alex, do you mean the patch from comment #83? The previous one from comment #78 was already applied -> 0824965140fff1bf640a987dc790d1594a8e0699.
(In reply to Thaddaeus Tintenfisch from comment #6) > Alex, do you mean the patch from comment #83? > The previous one from comment #78 was already applied -> > 0824965140fff1bf640a987dc790d1594a8e0699. I didn't realize it had already been applied.
The warnings (not panics) would need to be tracked in separate= reports, but at least the first one is harmless.
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
(In reply to Thaddaeus Tintenfisch from comment #9) > 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: https://bugzilla.kernel.org/show_bug.cgi?id=61891 or adding a comment to that bug that there are still cases that are broken.
I have added a comment to the linked report. Also, the patch from comment #2 for this bug can be forwarded then. Thanks.
Is anything missing? Does the patch need more testing?
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | FIXED |
Oh, 4.2-rc3 includes the patch. Thanks. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=233709d2cd6bbaaeda0aeb8d11f6ca7f98563b39