[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2019-11-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 Martin Peres changed: What|Removed |Added Resolution|--- |MOVED Status|NEW

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2018-06-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #16 from Sverd Johnsen --- hmm this is new [41889.542562] Console: switching to colour dummy device 80x25 [41890.859216] [drm] amdgpu: finishing device. [41891.096266] [TTM] Finalizing pool allocator [41891.100313] [TTM] Finalizing

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2018-06-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #15 from Sverd Johnsen --- Seems to be much better or completly (well almost, bug 106820) solved with 4.17 according to my preliminary tests. Still a problem in 4.16: [16981.789980] [drm] amdgpu: finishing device. [16981.901013] BUG

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2018-04-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #14 from Sverd Johnsen --- I just looked at the comments again and based on Comment 2 this seems like expected behavior for now. So my update was kind of pointless. -- You are receiving this mail because: You are the assignee for t

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2018-04-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #13 from Sverd Johnsen --- Still seen with 4.15.15 and dc=1. Not sure if this always reproduces or not, havn't tested this in a while. [13342.285357] [drm] amdgpu: finishing device. [13342.288330] amdgpu: [powerplay]

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2018-02-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #12 from Jordan L --- Thanks. Just to clarify, you aren't able to enable DC with your current Kconfig configuration, which prevents you from retrying on this ticket? If so, please just open a new bug rather than conflate the issue h

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2018-02-27 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 Luke McKee changed: What|Removed |Added CC||hojur...@gmail.com --- Comment #11 from Lu

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2018-02-26 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #10 from Jordan L --- Hi Luke, it actually looks like you're running with DC disabled. Can you also try with amdgpu.dc=1 explicitly set? Potentially there are issues in multiple IP blocks, though we fixed a driver unload issue recent

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2018-02-26 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #9 from Luke McKee --- Using Polairs 11 I get the same error message btw when loading the latest (today) amd-drm-staging-next. I'll include debugging symbols and try again. Feb 26 14:56:18 hojuruku kernel: Linux agpgart interface v0

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2018-02-25 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #8 from Luke McKee --- I commented because the user here had the error relating to powerplay failing that I have seen in other threads. https://forum-en.msi.com/index.php?topic=298468.0 [46667.236028] kernel: amdgpu: [powerplay]

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2018-02-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #7 from Harry Wentland --- Luke, does your comment relate to driver unload, specifically driver unload throwing NULL pointer dereference? If not, please open a separate ticket so as not to confuse two issues. -- You are receiving

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2018-02-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #6 from Luke McKee --- Harry I have tried the latest staging next 2 days ago. Suggest you see there is a long standing issue with powerplay and buggy AMI bioses that don't properly set up MMIO BAR regiions that need to be worked aro

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2018-01-29 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #5 from Harry Wentland --- Can you try with the latest amd-staging-drm-next from https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next We just fixed a bunch of driver unload issues. It should be fixed now. -- You a

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2017-12-21 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #4 from mikita.lip...@amd.com --- Encountering a deadlock in DRM while trying to force disable CRTCs. If no displays connected - system hard hangs. If DC is disabled (any number of displays) - system hard hangs. Currently investigat

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2017-12-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #3 from Sverd Johnsen --- Thanks for pointing me to that. Seems like it should have gone to stable Alright. Here is what I do now: boot with intel gpu, amdgpu is blacklisted in modules so it doesn't get autoloaded then i load amdgp

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2017-12-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 Michel Dänzer changed: What|Removed |Added CC||harry.wentl...@amd.com,

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2017-12-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #1 from Sverd Johnsen --- with 4.15rc (linus tree from today) [ 78.807441] [drm] amdgpu: finishing device. [ 78.887439] amdgpu: [powerplay] [ 78.887454] amdgpu: [powerplay] [ 78.968349] BUG: unable to handle kernel NULL po

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

2017-12-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104274 Bug ID: 104274 Summary: Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0258 (mutex_lock) Product: DRI