https://bugzilla.kernel.org/show_bug.cgi?id=200621
Jon (jon...@gmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #30 from Jon (jon...@gmail.com) ---
After upgrading to 4.8.18 I believe this issue is resolved for me. My current
uptime is >7 days. I had to reboot about a week ago but before that it was
also >7 days. Normally it would crash withi
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #29 from Richard Smith (smit...@gmx.co.uk) ---
Scratch that, it is actually still happening. For some reason, I was able to
lock Gnome, let my monitor sleep, and then successfully resume. However, the
problem returned on a subsequent l
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #28 from Richard Smith (smit...@gmx.co.uk) ---
I think the problem may have been Wayland related because, following an update
to Wayland this morning, the issue no longer happens for me. I'm still running
the same kernel as in my previ
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #27 from Jon (jon...@gmail.com) ---
After upgrading to 4.18.8 it certainly seems more stable. Normally an uptime
of about two to three days was the best I could hope for. Current uptime is
just shy of six days.
--
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #26 from Jon (jon...@gmail.com) ---
I wanted to add some additional information. I had a freeze the other day and
all audio continued, both the microphone and speaker output continued to
function but X was totally frozen and I could n
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #25 from Jon (jon...@gmail.com) ---
Here are the newest:
id 3dd692e5e80f6bac71c1f4caa570bd449b68a752
reason: WARNING: CPU: 12 PID: 2159 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:254
generic_reg_wait+0xe7/0x160 [a
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #24 from Jon (jon...@gmail.com) ---
Had another crash again today. Here's some output from abrt-cli that I thought
might be helpful. (there are dozens of theses):
id 50200875b8db5b1f4a2a8e9e1b4b9cbf28370c7c
reason: WARNING: C
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #21 from Jon (jon...@gmail.com) ---
I have 3 monitors and when this happens the entire system freezes but still
responds to icmp.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #22 from Jon (jon...@gmail.com) ---
So this is interesting. I'm still getting these errors occasionally but the
computer hasn't frozen in a day (1d 13h, specifically). Sometimes it will make
it two or even three days without a total
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #20 from Richard Smith (smit...@gmx.co.uk) ---
According to this Debian bug report, the issue may be due to the latest edition
of the GPU firmware:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908313
--
You are receiving this m
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #23 from Jon (jon...@gmail.com) ---
That previous post should have said 4.18.5-200, not 4.18.4-200
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #19 from Richard Smith (smit...@gmx.co.uk) ---
Additional: I should probably have mentioned that I am running Debian testing.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #18 from Richard Smith (smit...@gmx.co.uk) ---
Created attachment 278497
--> https://bugzilla.kernel.org/attachment.cgi?id=278497&action=edit
dmesg
The dmesg output for the last time it happened.
--
You are receiving this mail bec
https://bugzilla.kernel.org/show_bug.cgi?id=200621
Richard Smith (smit...@gmx.co.uk) changed:
What|Removed |Added
CC||smit...@gmx.co.uk
---
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #16 from Jon (jon...@gmail.com) ---
This is what I got upon logging back in:
https://i.imgur.com/g3tLOQr.png
Problem Reporting
Name: kernel-core
Version: 4.17.19-200
First Detected: a minute ago (17:58)
Report: cannot be reported
A
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #15 from Jon (jon...@gmail.com) ---
Last night I installed a new m.2 SSD. Installed a fresh copy of Fedora 28
Workstation and ran all updates then locked the screen. Came back this morning
and computer was frozen again. I will post
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #14 from Jon (jon...@gmail.com) ---
Just had another crash. Moved the mouse to wake it from sleep, hdmi and dvi-d
monitors came on, displayport monitor never did, mouse frozen and num lock
light frozen on keyboard. I was able to stil
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #13 from Jon (jon...@gmail.com) ---
Alex:
Thanks for the reply. I just added that parameter and rebooted. Here's my
/proc/cmdline now:
BOOT_IMAGE=/boot/vmlinuz-4.18.5-pc003 root=/dev/mapper/fedora_ssd_vg00-root ro
resume=/dev/mappe
https://bugzilla.kernel.org/show_bug.cgi?id=200621
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #11 from Jon (jon...@gmail.com) ---
Still frequent freezing. Two so far today, one time everything froze but audio
from youtube in firefox continued to play. Numlock light frozen on keyboard,
no input would work from mouse, etc, but
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #10 from Jon (jon...@gmail.com) ---
Upgraded to 4.18.5 and have been running that since 8/29. I've had the same
amount of freezing, but no more errors in the journal. This morning it was a
complete freeze while using Firefox. Nothi
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #9 from Jon (jon...@gmail.com) ---
Thanks for your input, I appreciate you taking the time to look into this.
This system was 100% stable for months, but somewhere around 4.17.X the issue
started and has persisted through several kern
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #8 from Michel Dänzer (mic...@daenzer.net) ---
Comment 4 looks similar to the following reports, both of which have comments
saying current kernels work better:
https://bugs.freedesktop.org/105684
https://bugs.freedesktop.org/106225
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #7 from Jon (jon...@gmail.com) ---
Created attachment 278177
--> https://bugzilla.kernel.org/attachment.cgi?id=278177&action=edit
dmesg output
--
You are receiving this mail because:
You are watching the assignee of the bug.
__
https://bugzilla.kernel.org/show_bug.cgi?id=200621
Andrey Grodzovsky (andrey.grodzov...@amd.com) changed:
What|Removed |Added
CC||andrey.gro
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #5 from Jon (jon...@gmail.com) ---
Is there any other information I can provide to help diagnose? I'm not even
sure if I have this bug filed in the right place.
--
You are receiving this mail because:
You are watching the assignee o
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #4 from Jon (jon...@gmail.com) ---
Here's another example of a crash
Aug 11 20:46:59 pc003 kernel: [drm] DM_MST: stopping TM on aconnector:
cd25cb02 [id: 52]
Aug 11 20:47:
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #3 from Jon (jon...@gmail.com) ---
Still experiencing this issue with the latest fedora kernel (4.17.12). Not
sure if this is helpful (from journalctl):
Aug 11 10:10:14 pc003 kernel: [drm] DM_MST: stopping TM on aconnector:
b
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #2 from Jon (jon...@gmail.com) ---
Updated, using amdgpu.dc=0 had no effect, still crashes every 1-2 days,
sometimes in just a few hours. Seems to happen most frequently when waking up,
specifically the monitor attached via displaypor
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #1 from Jon (jon...@gmail.com) ---
I believe this may be related to the new AMD DC that was enabled by default for
all GPU as of 4.17. I have disabled it via amdgpu.dc=0 in the boot parameters
and I will report back.
--
You are rece
31 matches
Mail list logo
