https://bugs.freedesktop.org/show_bug.cgi?id=108464
Duncan Roe changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #24 from Duncan Roe ---
(In reply to Duncan Roe from comment #23)
> Here are some notes for anyone trying to reproduce this problem.
> By "this problem" I mean failure to reboot after "reboot" command issued.
>
> 1. On my system (Sl
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #23 from Duncan Roe ---
Here are some notes for anyone trying to reproduce this problem.
By "this problem" I mean failure to reboot after "reboot" command issued.
1. On my system (Slackware, no systemd) I am triggering a reboot by C
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #22 from Duncan Roe ---
Created attachment 143346
--> https://bugs.freedesktop.org/attachment.cgi?id=143346&action=edit
dmesg o/p showing output from Attachment 143344
This is a typical BUG occurrence. Stack trace looks similar to
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #21 from Duncan Roe ---
Restarting investigations at Linux 5.0.0-rc5. Modified attachment 143055 to
check whether the patch would trigger. It never would. New patch is attachment
143344.
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #20 from Duncan Roe ---
Created attachment 143344
--> https://bugs.freedesktop.org/attachment.cgi?id=143344&action=edit
Display connectors_num & res_cap->num_ddc before compare
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #19 from Duncan Roe ---
Comment on attachment 143011
--> https://bugs.freedesktop.org/attachment.cgi?id=143011
[PATCH] drm/amd/display: Limit number of links to num_ddc
Review of attachment 143011:
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #18 from Duncan Roe ---
Mixed results on applying this patch.
IN BRIEF: If you could eliminate this second Oops then we can see what works
and what doesn't.
In the meantime with the patch applied to v4.20 in the stable repository:
re
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #17 from Duncan Roe ---
Created attachment 143055
--> https://bugs.freedesktop.org/attachment.cgi?id=143055&action=edit
dmesg o/p with diags after applying attachment 143011
The line before the BUG line shows a null pointer
--
Y
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #16 from Harry Wentland ---
Created attachment 143011
--> https://bugs.freedesktop.org/attachment.cgi?id=143011&action=edit
[PATCH] drm/amd/display: Limit number of links to num_ddc
Can you see if this patch helps you?
--
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #15 from Duncan Roe ---
Further to attachment 143008: there are lots of calls to dm_dp_aux_transfer
with aux=f0bfdb41, but the first call with aux=74cc4227 fails
(because the aux_engine pointer is NULL). Then a few mo
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #14 from Duncan Roe ---
Created attachment 143008
--> https://bugs.freedesktop.org/attachment.cgi?id=143008&action=edit
dmesg o/p with attachment 143007
The exception occurs in dc_link_aux_transfer, which is called by
dm_dp_aux_tr
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #13 from Duncan Roe ---
Created attachment 143007
--> https://bugs.freedesktop.org/attachment.cgi?id=143007&action=edit
Diagnostic patches to determine which pointer is null
These patches are against Linux 4.19.12, commit
2a7cb228
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #12 from Duncan Roe ---
Created attachment 142354
--> https://bugs.freedesktop.org/attachment.cgi?id=142354&action=edit
Patch for Linux-19.0 to revert e1cb3e4
Revert commit e1cb3e4801e6896ba93d63222b1052199d2a8c9b (drm/amd/display
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #11 from Duncan Roe ---
There is a kernel Oops associated with this problem. I only just discovered it
started on the same commit as reboot failure did. You can see the BUG line in
attachment 142063 at time 5.075194
--
You are rece
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #10 from Duncan Roe ---
(In reply to Alex Deucher from comment #1)
> Are you sure the bisect is correct? This commit just changes debugfs which
> shouldn't be triggered unless you actually write to the file in question.
> Please at
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #9 from Duncan Roe ---
(In reply to Alex Deucher from comment #7)
> (In reply to Duncan Roe from comment #6)
> > (In reply to Duncan Roe from comment #3)
> > > halt is fine btw, it's only reboot that breaks.
> > > Do you want extra d
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #8 from Duncan Roe ---
(In reply to Alex Deucher from comment #1)
> Are you sure the bisect is correct? This commit just changes debugfs which
> shouldn't be triggered unless you actually write to the file in question.
> Please att
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #7 from Alex Deucher ---
(In reply to Duncan Roe from comment #6)
> (In reply to Duncan Roe from comment #3)
> > halt is fine btw, it's only reboot that breaks.
> > Do you want extra debug turned on for dmesg?
>
> At Linux 19.0-rc8,
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #6 from Duncan Roe ---
(In reply to Duncan Roe from comment #3)
> halt is fine btw, it's only reboot that breaks.
> Do you want extra debug turned on for dmesg?
At Linux 19.0-rc8, power button / halt command also fails. The backligh
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #5 from Duncan Roe ---
Still present at 4.19.0-rc8. Is there any other info I can provide?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing l
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #4 from Duncan Roe ---
Created attachment 142063
--> https://bugs.freedesktop.org/attachment.cgi?id=142063&action=edit
dmesg o/p as requested
No Xorg involvement - boot up to command line only
--
You are receiving this mail beca
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #3 from Duncan Roe ---
halt is fine btw, it's only reboot that breaks.
Do you want extra debug turned on for dmesg?
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #2 from Duncan Roe ---
Yes I thought that was weird (debug fs). But adjacent commit
30cdbfaa6aa469347db7fcda5949f1ccf7559ecf does not show the problem
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=108464
Alex Deucher changed:
What|Removed |Added
CC||harry.wentl...@amd.com,
https://bugs.freedesktop.org/show_bug.cgi?id=108464
Bug ID: 108464
Summary: System fails to reboot after Ctrl-Alt-Del
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Seve
26 matches
Mail list logo
