https://bugs.freedesktop.org/show_bug.cgi?id=106671
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #36 from Alan W. Irwin ---
(In reply to fin4478 from comment #35)
> To prevent random kernel lock ups with Ryzen, enable RCU_NOCB_CPU in the
> kernel configuration and boot the kernel with the rcu_nocbs=0-X command
> line parameter.
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #35 from fin4...@hotmail.com ---
To prevent random kernel lock ups with Ryzen, enable RCU_NOCB_CPU in the kernel
configuration and boot the kernel with the rcu_nocbs=0-X command line
parameter. X is the cpu thread count -1. To fix th
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #34 from Alan W. Irwin ---
I have discovered this box became significantly less stable when there were two
users displaying X directly on it (one with startx , one with startx -- :1) and
using ctrl-alt-F1 and ctrl-alt-F2 to switch be
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #33 from Alan W. Irwin ---
Created attachment 142358
--> https://bugs.freedesktop.org/attachment.cgi?id=142358&action=edit
tarball containing log information concerning latest lockup
--
You are receiving this mail because:
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #32 from Alan W. Irwin ---
I had another lockup today after ~3 days of uptime. Please see the most recent
attachment for the relevant log files and dmesg output corresponding to this
lockup. These logs contain NMI messages and refe
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #31 from Alan W. Irwin ---
Created attachment 142114
--> https://bugs.freedesktop.org/attachment.cgi?id=142114&action=edit
tarball containing log information concerning latest lockup
--
You are receiving this mail because:
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #30 from Alan W. Irwin ---
This time the system lasted almost 14 days before the lockup. See the latest
attachment for the log details which contain NMI messages followed by a burst
of ascii null characters (which in my experience c
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #29 from Alan W. Irwin ---
Created attachment 142075
--> https://bugs.freedesktop.org/attachment.cgi?id=142075&action=edit
tarball containing daemon.log, messages, kern.log, syslog, and dmesg output
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #28 from Alan W. Irwin ---
(In reply to Michel Dänzer from comment #27)
> (In reply to Alan W. Irwin from comment #26)
> > Debian Jessie = oldstable had debug packages for libgl1-mesa-dri, but I
> > can find nothing equivalent for De
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #27 from Michel Dänzer ---
(In reply to Alan W. Irwin from comment #26)
> Debian Jessie = oldstable had debug packages for libgl1-mesa-dri, but I
> can find nothing equivalent for Debian Stretch
Debugging symbol packages are in a se
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #26 from Alan W. Irwin ---
(In reply to Michel Dänzer from comment #25)
> (In reply to Alan W. Irwin from comment #24)
> > Just now the direct X server failed with a segfault (see the attached log
> > file for the details).
>
> Look
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #25 from Michel Dänzer ---
(In reply to Alan W. Irwin from comment #24)
> Just now the direct X server failed with a segfault (see the attached log
> file for the details).
Looks like a Mesa bug. Please install the libgl1-mesa-dri-d
https://bugs.freedesktop.org/show_bug.cgi?id=106671
Michel Dänzer changed:
What|Removed |Added
Attachment #141904|application/x-trash |text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #24 from Alan W. Irwin ---
Created attachment 141904
--> https://bugs.freedesktop.org/attachment.cgi?id=141904&action=edit
X log file showing segfault
Just now the direct X server failed with a segfault (see the attached log file
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #23 from Alan W. Irwin ---
Created attachment 141872
--> https://bugs.freedesktop.org/attachment.cgi?id=141872&action=edit
tarball containing daemon.log, messages, kern.log, syslog, and dmesg output
The previously described uptime
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #22 from Alan W. Irwin ---
This last stability test lasted only 17.5 hours before the lockup. See the
latest attached tarball for the relevant log files (which capture everything
during this short up time) and dmesg output. As far
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #21 from Alan W. Irwin ---
Created attachment 141724
--> https://bugs.freedesktop.org/attachment.cgi?id=141724&action=edit
tarball containing kern.log, syslog, and dmesg output
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #20 from Alan W. Irwin ---
I started a new stability test as of 2018-09-23 15:34:19 right after a Debian
Buster dist-upgrade. The graphics stack versions for this test are as follows:
ii amd64-microcode
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #19 from Alan W. Irwin ---
Despite a new kernel, this instability issue has continued. Kernel 4.18.6
locked up after 8+ days of up time on our principal computer that has the RX
550 graphics card installed. (I will refer to this co
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #18 from Alan W. Irwin ---
Created attachment 141706
--> https://bugs.freedesktop.org/attachment.cgi?id=141706&action=edit
tarball containing log information concerning latest lockup
--
You are receiving this mail because:
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #17 from Alan W. Irwin ---
I terminated the last test immediately because it turns out a new kernel (Linux
merlin 4.18.0-1-amd64 #1 SMP Debian 4.18.6-1 (2018-09-06) x86_64 GNU/Linux) has
propagated from Debian Unstable to Debian Test
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #16 from Alan W. Irwin ---
I was beginning to have some hope that the latest direct access experiment
would prove to be stable. However, just now it locked up again after almost 7
days. So the stability is substantially improved co
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #15 from Alan W. Irwin ---
Created attachment 141567
--> https://bugs.freedesktop.org/attachment.cgi?id=141567&action=edit
log files from latest logup
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #14 from Alan W. Irwin ---
Created attachment 141479
--> https://bugs.freedesktop.org/attachment.cgi?id=141479&action=edit
compressed dmesg output from current direct graphics experiment
--
You are receiving this mail because:
Yo
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #13 from Alan W. Irwin ---
Well, after 1.5 (successful) days with the remote graphics experiment, I
decided instead it made more sense to go after the quicker acting instability
that I have previously experienced in direct graphics m
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #12 from Alan W. Irwin ---
(In reply to Michel Dänzer from comment #10)
> [T]hat looks like an RCU or other core kernel issue, not directly
> related to the graphics drivers.
Hi Michel:
If so, should I report that probable non-graph
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #11 from Alan W. Irwin ---
Thanks for that idle=nomwait suggestion which I have now just tried (verified
by
irwin@merlin> cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.17.0-3-amd64
root=UUID=1e45a1ee-a5d6-4327-9a7b-2663ffc0b157 ro ro
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #10 from Michel Dänzer ---
(In reply to Alan W. Irwin from comment #9)
> So the current lockup could be due to an entirely different bug than in the
> lockups I have encountered for the direct use case.
Yeah, that looks like an RCU
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #9 from Alan W. Irwin ---
We (there are two of us using this machine) just got yet another kernel lockup
(no remote access possible with ssh, direct keyboard not working), but this is
a case when we were remotely accessing this box w
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #8 from Alan W. Irwin ---
Created attachment 141451
--> https://bugs.freedesktop.org/attachment.cgi?id=141451&action=edit
tarball containing kern.log, syslog, and dmesg output
--
You are receiving this mail because:
You are the a
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #7 from Alan W. Irwin ---
Please remove the resolution of this bug as FIXED.
The reason for this request is subsequent kernel-4.16.x use after the initial
success I reported continued to show lock ups whenever this graphics card was
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #6 from Alan W. Irwin ---
Edit of previous comment:
of the 3D game, -> of the 3D game, foobillard,
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #5 from Alan W. Irwin ---
Hi Michel:
Since the lock ups occurred during ordinary (KDE) desktop use when I wasn't
running 3D games I ignored mesa upgrades and instead concentrated first on
trying a new kernel version (from 4.16.5 to 4
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #3 from Alan W. Irwin ---
Created attachment 139817
--> https://bugs.freedesktop.org/attachment.cgi?id=139817&action=edit
dmesg output as requested
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #4 from Alan W. Irwin ---
Hi Michel:
I have added your requested attachments. And if there are other data you need
or other tests I can run, let me know.
Meanwhile, all else seems well with this new computer (e.g., the lock ups ar
https://bugs.freedesktop.org/show_bug.cgi?id=106671
Michel Dänzer changed:
What|Removed |Added
Component|Driver/AMDgpu |Drivers/Gallium/radeonsi
Assi
37 matches
Mail list logo
