[Bug 199157] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
https://bugzilla.kernel.org/show_bug.cgi?id=199157 --- Comment #5 from Kyle De'Vir (kyle.de...@mykolab.com) --- This is the first time I've seen it happening on DC, so I decided to just throw it up as bug report. At the time, I was browsing on Firefox Nightly, while listening to some music with MPV. My desktop is Plasma Shell with KWin on X11, which is heavy on OpenGL usage. I've been running the git versions of Radeon Profile and Radeon Profile Daemon, which autostart when Plasma Shell does. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 199157] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
https://bugzilla.kernel.org/show_bug.cgi?id=199157 --- Comment #4 from Harry Wentland (harry.wentl...@amd.com) --- I have one of the first R7 1700 at home on have only seen the marginality problem affecting gcc and bash while compiling something multi-threaded. Never noticed it crashing the kernel. I think what you see might be a legit issue in DC. Does it happen randomly? On boot? During normal usage? Gaming? How frequently do you see this? -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 199157] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
https://bugzilla.kernel.org/show_bug.cgi?id=199157 --- Comment #3 from Kyle De'Vir (kyle.de...@mykolab.com) --- GPU-wise, I have an RX580 8GB. This morning, I started to wonder whether the issue was not even be a driver bug, but actually related to the whole "Performance Marginality Problem", as my AMD 1600X is one of the CPUs affected by Ryzen hardware bug. A while ago, I started getting random MCEs, which I suspected were related to the Ryzen bug. They stopped a while later, mysteriously... then it was occasional hard-lockups, then this issue. I'm trying to save up money for Ryzen 2, so hopefully this issue won't pop up again. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 199157] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
https://bugzilla.kernel.org/show_bug.cgi?id=199157 --- Comment #2 from Kyle De'Vir (kyle.de...@mykolab.com) --- Created attachment 274891 --> https://bugzilla.kernel.org/attachment.cgi?id=274891=edit dmesg log -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 199157] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
https://bugzilla.kernel.org/show_bug.cgi?id=199157 Harry Wentland (harry.wentl...@amd.com) changed: What|Removed |Added CC||harry.wentl...@amd.com --- Comment #1 from Harry Wentland (harry.wentl...@amd.com) --- Can you give details of your HW and attach the entire dmesg log? In what scenario does the NULL pointer dereference happen? -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
