You are not logged in.

#1 2020-12-16 00:02:05

Roken
Member
From: South Wales, UK
Registered: 2012-01-16
Posts: 1,193

[SOLVED] Linux 5.10.1 prevents boot

Dunno if this is a question or a warning. On my Desktop, no problems (that I can see). However, my Laptop (HP) Linux 5.10.1 and the zen 5.10.1 kernel prevent booting. It does get so far, and since I need my laptop for work I haven't spent time analysing, but it will certainly not complete a boot to a desktop, rather instead hanging at a black screen.

The primary difference between the two (general architecture notwithstanding) is that my desktop rocks an NVidia gfx card, whilst the laptop is an AMD iGPU. If I had to guess, I'd guess that was the issue.

Downgrading back to 5.9.14 gets me working again.

No warnings on the front page.

So have I missed a step/announcement or have I just been unlucky.

For info, after downgrading the kernel and booting successfully, I tried again with the same black screen issue. Downgraded again, and working again, so it's definitely something in the kernel package.

Last edited by Roken (2020-12-16 22:29:31)


Ryzen 1800x 8 core/16 thread - 2 x GTX 1070 8Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703

Offline

#2 2020-12-16 00:11:21

loqs
Member
Registered: 2014-03-06
Posts: 15,092

Re: [SOLVED] Linux 5.10.1 prevents boot

Post the journal from the failed boot if you can not determine the cause.

Offline

#3 2020-12-16 14:12:40

Mortimer Houghton
Member
Registered: 2014-09-28
Posts: 77

Re: [SOLVED] Linux 5.10.1 prevents boot

Same problem with me with 5.10.1.  There will be no journalctl log from the failed boot.  There is a brief flash of the initial systemd version message that is part of my normal quiet boot, then a blank screen.  I checked the whole journalctl log and there is nothing between my last successful session and the new one after downgrading back to 5.9.14.

---
EDIT: I should add that I too am using a laptop with an AMD iGPU.

Last edited by Mortimer Houghton (2020-12-16 14:23:12)

Offline

#4 2020-12-16 15:51:07

mcloaked
Member
From: Yorkshire, UK
Registered: 2012-02-02
Posts: 1,121

Re: [SOLVED] Linux 5.10.1 prevents boot

I am running an AMD laptop with 4500U APU with an integrated amdgpu which is working fine with kernel 5.10.1, so perhaps it is specific to the particular iGPU that you have?  For booting I include the kernel parameter acpi_backlight=vendor which could be a difference that is important? I am also booting with refind, and again is it possible that different boot managers might have an effect?

My integtrated graphics chip is:

04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev c2)

Mike C

Offline

#5 2020-12-16 16:17:47

progandy
Member
Registered: 2012-05-17
Posts: 5,003

Re: [SOLVED] Linux 5.10.1 prevents boot

Roken wrote:

So have I missed a step/announcement or have I just been unlucky.

You use the testing repository and a kernel not booting is unlucky. If that was known to be widespread it would probably not even be in testing.


| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Online

#6 2020-12-16 16:20:13

Roken
Member
From: South Wales, UK
Registered: 2012-01-16
Posts: 1,193

Re: [SOLVED] Linux 5.10.1 prevents boot

This is the last few 100 lines of journalctl before I did a hard reset and booted a known good kernel.

https://pastebin.com/LrpDGJP9

EDIT: In case it's important, the 4 automount entries immediately before it stops are all NFS mounts.

Last edited by Roken (2020-12-16 16:26:07)


Ryzen 1800x 8 core/16 thread - 2 x GTX 1070 8Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703

Offline

#7 2020-12-16 16:29:17

Roken
Member
From: South Wales, UK
Registered: 2012-01-16
Posts: 1,193

Re: [SOLVED] Linux 5.10.1 prevents boot

progandy wrote:
Roken wrote:

So have I missed a step/announcement or have I just been unlucky.

You use the testing repository and a kernel not booting is unlucky. If that was known to be widespread it would probably not even be in testing.

I get that, and I use testing because I like cutting edge and I'm sufficiently proficient to be able to recover when things do go wrong (such as now). Nevertheless, that doesn't alter the fact that I may have missed an announcement somewhere. More to the point, this is an incremental upgrade, and so I wouldn't expect any catastrophic breakages of something so fundamental as the kernel.

And, of course, by posting here I either find out whether I'm unique in this (in which case I must look elsewhere) or whether others meet the same fate, in which case it's probably a bug to be reported.

Last edited by Roken (2020-12-16 16:30:33)


Ryzen 1800x 8 core/16 thread - 2 x GTX 1070 8Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703

Offline

#8 2020-12-16 16:58:26

seth
Member
Registered: 2012-09-03
Posts: 30,861

Re: [SOLVED] Linux 5.10.1 prevents boot

https://wiki.archlinux.org/index.php/Ke … _KMS_start ?
"amdgpu.dc=0" ?

Does the multi-user.target work?

ftr, The timestamps in the posted journal are a bit unsorted and it *looks* like crng is late.

Offline

#9 2020-12-16 19:53:03

jonathon
Member
Registered: 2016-09-19
Posts: 128

Re: [SOLVED] Linux 5.10.1 prevents boot

I'm finding the same thing, 5.10.1 does not boot on my Ryzen-based laptop with amdgpu. Initial initramfs loads up the point of mounting /boot, then screen blanks (black, with backlight) and no further boot progress is made. I previously tested `linux-mainline` and found the same with 5.10rc7 and 5.10rc6 but put it down to RC status.

However, adding amdgpu.dc=0 to the GRUB boot line lets boot continue to graphical target.

Last edited by jonathon (2020-12-16 21:46:40)

Offline

#10 2020-12-16 20:02:12

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 6,419

Re: [SOLVED] Linux 5.10.1 prevents boot

A similar problem has already been reported here: https://bbs.archlinux.org/viewtopic.php … 3#p1943813

Answer seth's question (in the last post) and perhaps use the "Report" button on your OP to request a merge.

Offline

#11 2020-12-16 22:29:10

Roken
Member
From: South Wales, UK
Registered: 2012-01-16
Posts: 1,193

Re: [SOLVED] Linux 5.10.1 prevents boot

Adding amdgpu to the MODULES array of mkinitcpio.conf and regenerating makes no difference, but amdgpu.dc=0 seems to fix it.

Thank you. Marking as solved.


Ryzen 1800x 8 core/16 thread - 2 x GTX 1070 8Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703

Offline

#12 2020-12-16 23:10:29

progandy
Member
Registered: 2012-05-17
Posts: 5,003

Re: [SOLVED] Linux 5.10.1 prevents boot

A note for others with this issue: Disabling amdgpu.dc is not a fix, but a workaround. "dc" (Display Core) is a newer display stack that brings features like atomic modesetting and should be preferred if it works.

The bug should probably be reported here: https://gitlab.freedesktop.org/drm/amd/-/issues

Last edited by progandy (2020-12-16 23:15:07)


| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Online

#13 2020-12-16 23:20:34

2ManyDogs
Forum Moderator
Registered: 2012-01-15
Posts: 4,043

Re: [SOLVED] Linux 5.10.1 prevents boot

Topics merged.


How to post. A sincere effort to use modest and proper language and grammar is a sign of respect toward the community.

Offline

#14 2020-12-17 01:09:14

jonathon
Member
Registered: 2016-09-19
Posts: 128

Re: [SOLVED] Linux 5.10.1 prevents boot

Looking at the bugs already reported, the one which looks closest is https://gitlab.freedesktop.org/drm/amd/-/issues/1388 but that one refers to all 5.* series kernels as having an issue.

This probably needs a bisect...

Offline

#15 2020-12-17 05:02:17

seth
Member
Registered: 2012-09-03
Posts: 30,861

Re: [SOLVED] Linux 5.10.1 prevents boot

Stack doesn't look that similar, do you also use the zen kernel?

Offline

#16 2020-12-17 12:15:43

jonathon
Member
Registered: 2016-09-19
Posts: 128

Re: [SOLVED] Linux 5.10.1 prevents boot

I haven't looked that much into the above bug report, I don't think the issue from this thread is specifically covered so I don't think any traces there apply (I don't know how I'd even get dmesg output at the point the issue is triggered).

But, just to confirm, I'm seeing the same symptoms with both `linux` and `linux-zen`.

Even with (or possibly because of?) amdgpu.dc=0, the laptop won't correctly resume from sleep (with 5.10.1). Screen remains dark, though keyboard input works and I can switch to a TTY and CTRL-ALT-DEL to reboot cleanly.

Last edited by jonathon (2020-12-17 12:19:17)

Offline

#17 2020-12-17 16:23:10

seth
Member
Registered: 2012-09-03
Posts: 30,861

Re: [SOLVED] Linux 5.10.1 prevents boot

Can you post a journal from a failing boot (incl. the amdgpu backtrace)

Offline

#18 2020-12-17 17:01:01

domx93
Member
Registered: 2020-11-30
Posts: 25

Re: [SOLVED] Linux 5.10.1 prevents boot

Same problem, I had to downgrade to linux-5.9

edit: no, I have this problem with linux-5.9.14 and I downgraded to 5.9.11.I don't know about 5.9.12 and 5.9.12

Last edited by domx93 (2020-12-17 17:12:36)

Offline

#19 2020-12-17 17:22:42

jonathon
Member
Registered: 2016-09-19
Posts: 128

Re: [SOLVED] Linux 5.10.1 prevents boot

With Early KMS enabled there isn't journal entry to check, removing `amdgpu` from modules in `/etc/mkinitcpio.conf` and rebuilding the initramfs will let you get a trace.

seth wrote:

Can you post a journal from a failing boot (incl. the amdgpu backtrace)

The important part seems to be this:

Dec 17 16:50:02 strix kernel: [drm] amdgpu kernel modesetting enabled.
Dec 17 16:50:02 strix kernel: amdgpu: Ignoring ACPI CRAT on non-APU system
Dec 17 16:50:02 strix kernel: Virtual CRAT table created for CPU
Dec 17 16:50:02 strix kernel: amdgpu: Topology: Add CPU node
Dec 17 16:50:02 strix kernel: checking generic (e0000000 7f0000) vs hw (e0000000 10000000)
Dec 17 16:50:02 strix kernel: fb0: switching to amdgpudrmfb from EFI VGA
Dec 17 16:50:02 strix kernel: Console: switching to colour dummy device 80x25
Dec 17 16:50:02 strix kernel: amdgpu 0000:0c:00.0: vgaarb: deactivate vga console
Dec 17 16:50:02 strix kernel: amdgpu 0000:0c:00.0: enabling device (0006 -> 0007)
Dec 17 16:50:02 strix kernel: [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67DF 0x1043:0x1A60 0xC1).
Dec 17 16:50:02 strix kernel: amdgpu 0000:0c:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Dec 17 16:50:02 strix kernel: [drm] register mmio base: 0xFE900000
Dec 17 16:50:02 strix kernel: [drm] register mmio size: 262144
Dec 17 16:50:02 strix kernel: [drm] add ip block number 0 <vi_common>
Dec 17 16:50:02 strix kernel: [drm] add ip block number 1 <gmc_v8_0>
Dec 17 16:50:02 strix kernel: [drm] add ip block number 2 <tonga_ih>
Dec 17 16:50:02 strix kernel: [drm] add ip block number 3 <gfx_v8_0>
Dec 17 16:50:02 strix kernel: [drm] add ip block number 4 <sdma_v3_0>
Dec 17 16:50:02 strix kernel: [drm] add ip block number 5 <powerplay>
Dec 17 16:50:02 strix kernel: [drm] add ip block number 6 <dm>
Dec 17 16:50:02 strix kernel: [drm] add ip block number 7 <uvd_v6_0>
Dec 17 16:50:02 strix kernel: [drm] add ip block number 8 <vce_v3_0>
Dec 17 16:50:02 strix kernel: amdgpu 0000:0c:00.0: amdgpu: Fetched VBIOS from VFCT
Dec 17 16:50:02 strix kernel: amdgpu: ATOM BIOS: SWBRT25190.001
Dec 17 16:50:02 strix kernel: [drm] UVD is enabled in VM mode
Dec 17 16:50:02 strix kernel: [drm] UVD ENC is enabled in VM mode
Dec 17 16:50:02 strix kernel: [drm] VCE enabled in VM mode
Dec 17 16:50:02 strix kernel: [drm] vm size is 128 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
Dec 17 16:50:02 strix kernel: amdgpu 0000:0c:00.0: amdgpu: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used)
Dec 17 16:50:02 strix kernel: amdgpu 0000:0c:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
Dec 17 16:50:02 strix kernel: [drm] Detected VRAM RAM=4096M, BAR=256M
Dec 17 16:50:02 strix kernel: [drm] RAM width 256bits GDDR5
Dec 17 16:50:02 strix kernel: [TTM] Zone  kernel: Available graphics memory: 16407296 KiB
Dec 17 16:50:02 strix kernel: [TTM] Zone   dma32: Available graphics memory: 2097152 KiB
Dec 17 16:50:02 strix kernel: [TTM] Initializing pool allocator
Dec 17 16:50:02 strix kernel: [TTM] Initializing DMA pool allocator
Dec 17 16:50:02 strix kernel: [drm] amdgpu: 4096M of VRAM memory ready
Dec 17 16:50:02 strix kernel: [drm] amdgpu: 4096M of GTT memory ready.
Dec 17 16:50:02 strix kernel: [drm] GART: num cpu pages 65536, num gpu pages 65536
Dec 17 16:50:02 strix kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F4007E9000).
Dec 17 16:50:02 strix kernel: [drm] Chained IB support enabled!
Dec 17 16:50:02 strix kernel: amdgpu: hwmgr_sw_init smu backed is polaris10_smu
Dec 17 16:50:02 strix kernel: [drm] Found UVD firmware Version: 1.130 Family ID: 16
Dec 17 16:50:02 strix kernel: [drm] Found VCE firmware Version: 53.26 Binary ID: 3
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB: values for Engine clock
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:         300000
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:         608000
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:         910000
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:         1077000
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:         1077000
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:         1077000
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:         1077000
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:         1077000
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB: Validation clocks:
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:    engine_max_clock: 107700
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:    memory_max_clock: 200000
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:    level           : 8
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB: values for Memory clock
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:         300000
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:         2000000
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB: Validation clocks:
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:    engine_max_clock: 107700
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:    memory_max_clock: 200000
Dec 17 16:50:02 strix kernel: [drm] DM_PPLIB:    level           : 8
Dec 17 16:50:02 strix kernel: [drm] Display Core initialized with v3.2.104!
Dec 17 16:50:02 strix kernel: EDAC amd64: F17h detected (node 0).
Dec 17 16:50:02 strix kernel: EDAC amd64: Node 0: DRAM ECC disabled.
Dec 17 16:50:02 strix kernel: snd_hda_intel 0000:0c:00.1: enabling device (0000 -> 0002)
Dec 17 16:50:02 strix kernel: snd_hda_intel 0000:0c:00.1: Force to non-snoop mode
Dec 17 16:50:02 strix kernel: snd_hda_intel 0000:12:00.3: enabling device (0000 -> 0002)
Dec 17 16:50:02 strix kernel: snd_hda_intel 0000:0c:00.1: bound 0000:0c:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Dec 17 16:50:02 strix kernel: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:0c:00.1/sound/card0/input8
Dec 17 16:50:02 strix kernel: input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:0c:00.1/sound/card0/input9
Dec 17 16:50:02 strix kernel: [drm] UVD and UVD ENC initialized successfully.
Dec 17 16:50:02 strix kernel: EDAC amd64: F17h detected (node 0).
Dec 17 16:50:02 strix kernel: EDAC amd64: Node 0: DRAM ECC disabled.
Dec 17 16:50:02 strix kernel: libphy: Fixed MDIO Bus: probed
Dec 17 16:50:02 strix kernel: snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Dec 17 16:50:02 strix kernel: snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Dec 17 16:50:02 strix kernel: snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Dec 17 16:50:02 strix kernel: snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
Dec 17 16:50:02 strix kernel: snd_hda_codec_realtek hdaudioC1D0:    inputs:
Dec 17 16:50:02 strix kernel: snd_hda_codec_realtek hdaudioC1D0:      Headset Mic=0x19
Dec 17 16:50:02 strix kernel: snd_hda_codec_realtek hdaudioC1D0:      Internal Mic=0x12
Dec 17 16:50:02 strix kernel: [drm] VCE initialized successfully.
Dec 17 16:50:02 strix kernel: kfd kfd: Allocated 3969056 bytes on gart
Dec 17 16:50:03 strix kernel: Virtual CRAT table created for GPU
Dec 17 16:50:03 strix kernel: amdgpu: Topology: Add dGPU node [0x67df:0x1002]
Dec 17 16:50:03 strix kernel: kfd kfd: added device 1002:67df
Dec 17 16:50:03 strix kernel: amdgpu 0000:0c:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 9, active_cu_number 36
Dec 17 16:50:03 strix kernel: [drm] fb mappable at 0xE0D19000
Dec 17 16:50:03 strix kernel: [drm] vram apper at 0xE0000000
Dec 17 16:50:03 strix kernel: [drm] size 8294400
Dec 17 16:50:03 strix kernel: [drm] fb depth is 24
Dec 17 16:50:03 strix kernel: [drm]    pitch is 7680
Dec 17 16:50:03 strix kernel: fbcon: amdgpudrmfb (fb0) is primary device
Dec 17 16:50:03 strix kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
Dec 17 16:50:03 strix kernel: #PF: supervisor instruction fetch in kernel mode
Dec 17 16:50:03 strix kernel: #PF: error_code(0x0010) - not-present page
Dec 17 16:50:03 strix kernel: PGD 0 P4D 0 
Dec 17 16:50:03 strix kernel: Oops: 0010 [#1] PREEMPT SMP NOPTI
Dec 17 16:50:03 strix kernel: CPU: 3 PID: 474 Comm: systemd-udevd Tainted: P           OE     5.10.1-arch1-1 #1
Dec 17 16:50:03 strix kernel: Hardware name: ASUSTeK COMPUTER INC. GL702ZC/GL702ZC, BIOS GL702ZC.306 07/05/2019
Dec 17 16:50:03 strix kernel: RIP: 0010:0x0
Dec 17 16:50:03 strix kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
Dec 17 16:50:03 strix kernel: RSP: 0018:ffff98c1037ff270 EFLAGS: 00010286
Dec 17 16:50:03 strix kernel: RAX: 0000000000000000 RBX: ffff8887609801b8 RCX: ffff888751f03800
Dec 17 16:50:03 strix kernel: RDX: 0000000000000000 RSI: 00000000000005cf RDI: ffff88875c6fb420
Dec 17 16:50:03 strix kernel: RBP: ffff888760980000 R08: ffff98c1037ff264 R09: 0000000000000001
Dec 17 16:50:03 strix kernel: R10: 0000000000000006 R11: 0000000000000005 R12: 0000000000000000
Dec 17 16:50:03 strix kernel: R13: ffff88875c5d1000 R14: ffff88874f4ac400 R15: ffff888758480000
Dec 17 16:50:03 strix kernel: FS:  00007f07e1701ec0(0000) GS:ffff888e3eec0000(0000) knlGS:0000000000000000
Dec 17 16:50:03 strix kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 17 16:50:03 strix kernel: CR2: ffffffffffffffd6 CR3: 0000000114460000 CR4: 00000000003506e0
Dec 17 16:50:03 strix kernel: Call Trace:
Dec 17 16:50:03 strix kernel:  dc_commit_state+0x839/0xa70 [amdgpu]
Dec 17 16:50:03 strix kernel:  amdgpu_dm_atomic_commit_tail+0x57b/0x2450 [amdgpu]
Dec 17 16:50:03 strix kernel:  ? __free_one_page+0x58/0x3f0
Dec 17 16:50:03 strix kernel:  ? free_one_page+0x5f/0xd0
Dec 17 16:50:03 strix kernel:  ? _raw_spin_unlock+0x16/0x30
Dec 17 16:50:03 strix kernel:  ? kfree+0x3e1/0x430
Dec 17 16:50:03 strix kernel:  commit_tail+0x94/0x130 [drm_kms_helper]
Dec 17 16:50:03 strix kernel:  drm_atomic_helper_commit+0x113/0x140 [drm_kms_helper]
Dec 17 16:50:03 strix kernel:  drm_client_modeset_commit_atomic+0x1fc/0x240 [drm]
Dec 17 16:50:03 strix kernel:  drm_client_modeset_commit_locked+0x56/0x150 [drm]
Dec 17 16:50:03 strix kernel:  drm_client_modeset_commit+0x24/0x40 [drm]
Dec 17 16:50:03 strix kernel:  drm_fb_helper_set_par+0xa5/0xd0 [drm_kms_helper]
Dec 17 16:50:03 strix kernel:  fbcon_init+0x2ba/0x580
Dec 17 16:50:03 strix kernel:  visual_init+0xce/0x130
Dec 17 16:50:03 strix kernel:  do_bind_con_driver.isra.0+0x1db/0x2e0
Dec 17 16:50:03 strix kernel:  do_take_over_console+0x116/0x180
Dec 17 16:50:03 strix kernel:  do_fbcon_takeover+0x5c/0xc0
Dec 17 16:50:03 strix kernel:  register_framebuffer+0x1f6/0x310
Dec 17 16:50:03 strix kernel:  __drm_fb_helper_initial_config_and_unlock+0x333/0x4b0 [drm_kms_helper]
Dec 17 16:50:03 strix kernel:  amdgpu_fbdev_init+0xb9/0xf0 [amdgpu]
Dec 17 16:50:03 strix kernel:  amdgpu_device_init.cold+0x16b7/0x1a99 [amdgpu]
Dec 17 16:50:03 strix kernel:  amdgpu_driver_load_kms+0x2b/0x1f0 [amdgpu]
Dec 17 16:50:03 strix kernel:  amdgpu_pci_probe+0x129/0x1b0 [amdgpu]
Dec 17 16:50:03 strix kernel:  local_pci_probe+0x42/0x80
Dec 17 16:50:03 strix kernel:  ? cpu_hotplug_disable+0x5/0x30
Dec 17 16:50:03 strix kernel:  pci_device_probe+0xfa/0x1b0
Dec 17 16:50:03 strix kernel:  really_probe+0x205/0x460
Dec 17 16:50:03 strix kernel:  driver_probe_device+0xe1/0x150
Dec 17 16:50:03 strix kernel:  device_driver_attach+0xa1/0xb0
Dec 17 16:50:03 strix kernel:  __driver_attach+0x8a/0x150
Dec 17 16:50:03 strix kernel:  ? device_driver_attach+0xb0/0xb0
Dec 17 16:50:03 strix kernel:  ? device_driver_attach+0xb0/0xb0
Dec 17 16:50:03 strix kernel:  bus_for_each_dev+0x89/0xd0
Dec 17 16:50:03 strix kernel:  bus_add_driver+0x12b/0x1e0
Dec 17 16:50:03 strix kernel:  driver_register+0x8b/0xe0
Dec 17 16:50:03 strix kernel:  ? 0xffffffffc0f10000
Dec 17 16:50:03 strix kernel:  do_one_initcall+0x57/0x220
Dec 17 16:50:03 strix kernel:  do_init_module+0x5c/0x260
Dec 17 16:50:03 strix kernel:  load_module+0x22d7/0x2490
Dec 17 16:50:03 strix kernel:  __do_sys_init_module+0x136/0x1b0
Dec 17 16:50:03 strix kernel:  do_syscall_64+0x33/0x40
Dec 17 16:50:03 strix kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Dec 17 16:50:03 strix kernel: RIP: 0033:0x7f07e1ff1e4e
Dec 17 16:50:03 strix kernel: Code: 48 8b 0d 25 10 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d f2 0f 0c 00 f7 d8 64 89 01 48
Dec 17 16:50:03 strix kernel: RSP: 002b:00007fff94baa4b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
Dec 17 16:50:03 strix kernel: RAX: ffffffffffffffda RBX: 000055c802baec20 RCX: 00007f07e1ff1e4e
Dec 17 16:50:03 strix kernel: RDX: 00007f07e212995d RSI: 0000000000b3feb1 RDI: 000055c8034ed1b0
Dec 17 16:50:03 strix kernel: RBP: 000055c8034ed1b0 R08: fffffffffffffff0 R09: 00007fff94baa211
Dec 17 16:50:03 strix kernel: R10: 000055c802ac1010 R11: 0000000000000246 R12: 00007f07e212995d
Dec 17 16:50:03 strix kernel: R13: 0000000000000001 R14: 000055c802ac9fb0 R15: 000055c802baec20
Dec 17 16:50:03 strix kernel: Modules linked in: of_mdio(+) snd_hda_codec_realtek(+) fixed_phy snd_hda_codec_generic libphy libarc4 ledtrig_audio zunicode(POE) snd_hda_codec_hdmi snd_hda_intel zzstd(OE) snd_intel_dspcfg soundwire_intel soundwire_generic_allocation zlua(OE) soundwire_cadence zavl(POE) snd_hda_codec icp(POE) edac_mce_amd amdgpu(+) usbhid kvm_amd snd_hda_core ccp snd_hwdep soundwire_bus gpu_sched i2c_algo_bit snd_soc_core kvm zcommon(POE) ttm snd_compress asus_nb_wmi znvpair(POE) ac97_bus snd_pcm_dmaengine irqbypass crct10dif_pclmul asus_wmi drm_kms_helper crc32_pclmul ghash_clmulni_intel snd_pcm sparse_keymap spl(OE) aesni_intel cec i8042 rc_core snd_timer crypto_simd syscopyarea cryptd serio sysfillrect snd sp5100_tco glue_helper sysimgblt tpm_crb rapl rfkill wmi_bmof pcspkr k10temp i2c_piix4 fb_sys_fops soundcore ac tpm_tis tpm_tis_core i2c_hid tpm hid rng_core evdev gpio_amdpt asus_wireless pinctrl_amd mac_hid acpi_cpufreq vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) drm msr crypto_user fuse
Dec 17 16:50:03 strix kernel:  agpgart ip_tables x_tables btrfs blake2b_generic libcrc32c xor raid6_pq xhci_pci xhci_pci_renesas xhci_hcd wmi battery crc32c_generic crc32c_intel
Dec 17 16:50:03 strix kernel: CR2: 0000000000000000
Dec 17 16:50:03 strix kernel: ---[ end trace df0726ebe1e5c210 ]---
Dec 17 16:50:03 strix kernel: RIP: 0010:0x0
Dec 17 16:50:03 strix kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
Dec 17 16:50:03 strix kernel: RSP: 0018:ffff98c1037ff270 EFLAGS: 00010286
Dec 17 16:50:03 strix kernel: RAX: 0000000000000000 RBX: ffff8887609801b8 RCX: ffff888751f03800
Dec 17 16:50:03 strix kernel: RDX: 0000000000000000 RSI: 00000000000005cf RDI: ffff88875c6fb420
Dec 17 16:50:03 strix kernel: RBP: ffff888760980000 R08: ffff98c1037ff264 R09: 0000000000000001
Dec 17 16:50:03 strix kernel: R10: 0000000000000006 R11: 0000000000000005 R12: 0000000000000000
Dec 17 16:50:03 strix kernel: R13: ffff88875c5d1000 R14: ffff88874f4ac400 R15: ffff888758480000
Dec 17 16:50:03 strix kernel: FS:  00007f07e1701ec0(0000) GS:ffff888e3eec0000(0000) knlGS:0000000000000000
Dec 17 16:50:03 strix kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 17 16:50:03 strix kernel: CR2: ffffffffffffffd6 CR3: 0000000114460000 CR4: 00000000003506e0
Dec 17 16:50:03 strix kernel: EDAC amd64: F17h detected (node 0).
Dec 17 16:50:03 strix kernel: EDAC amd64: Node 0: DRAM ECC disabled.
Dec 17 16:50:03 strix kernel: input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:12:00.3/sound/card1/input10
Dec 17 16:50:03 strix systemd-udevd[423]: Worker [474] terminated by signal 9 (KILL)
Dec 17 16:50:03 strix systemd-udevd[423]: 0000:0c:00.0: Worker [474] failed

Null pointer in amdgpu?

Dec 17 16:50:03 strix kernel: fbcon: amdgpudrmfb (fb0) is primary device
Dec 17 16:50:03 strix kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
Dec 17 16:50:03 strix kernel: #PF: supervisor instruction fetch in kernel mode
Dec 17 16:50:03 strix kernel: #PF: error_code(0x0010) - not-present page

Full boot log here: https://bin.garudalinux.org/?4233de9fc7 … mJod4C5jNE. (Note: I'm not running Garuda, just using their pastebin)

domx93 wrote:

Same problem, I had to downgrade to linux-5.9

edit: no, I have this problem with linux-5.9.14 and I downgraded to 5.9.11.I don't know about 5.9.12 and 5.9.12

I'm not sure it's the same problem - all 5.9 kernel releases work fine for me (including 5.9.14-arch, 5.9.14-zen, and 5.9.15-lqx).

Last edited by jonathon (2020-12-17 17:40:06)

Offline

#20 2020-12-17 20:40:33

seth
Member
Registered: 2012-09-03
Posts: 30,861

Re: [SOLVED] Linux 5.10.1 prevents boot

Same backtrace as Roken, can you also get a stack trace from a failed S3 resume (w/ dc=0)?
One of you should file an upstream bug.

Offline

#21 2020-12-17 21:05:12

jonathon
Member
Registered: 2016-09-19
Posts: 128

Re: [SOLVED] Linux 5.10.1 prevents boot

seth wrote:

can you also get a stack trace from a failed S3 resume (w/ dc=0)?

Yes, though there's very little there which is related (longer log output below). The main bit is this:

Dec 17 20:47:48 strix kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
Dec 17 20:47:48 strix kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed

Laptop's internal panel is "eDP" - there are some DP bug reports on the upstream tracker, but this may also just be a result of setting `amdgpu.dc=0` for my GPU.

There's a lot of e.g. network config details which I've cut from this longer journal output:

Dec 17 20:47:27 strix systemd[1]: Reached target Sleep.
Dec 17 20:47:27 strix systemd[1]: Starting Suspend...
Dec 17 20:47:27 strix systemd-sleep[3406]: Suspending system...
Dec 17 20:47:27 strix kernel: PM: suspend entry (deep)
Dec 17 20:47:27 strix systemd[1]: systemd-hostnamed.service: Succeeded.
Dec 17 20:47:30 strix systemd[1]: blueman-mechanism.service: Succeeded.
Dec 17 20:47:39 strix kernel: Filesystems sync: 2.566 seconds
Dec 17 20:47:39 strix kernel: Freezing user space processes ... (elapsed 0.014 seconds) done.
Dec 17 20:47:39 strix kernel: OOM killer disabled.
Dec 17 20:47:39 strix kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Dec 17 20:47:39 strix kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 17 20:47:39 strix kernel: r8169 0000:06:00.0 enp6s0: Link is Down
Dec 17 20:47:39 strix kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dec 17 20:47:39 strix kernel: sd 11:0:0:0: [sdb] Synchronizing SCSI cache
Dec 17 20:47:39 strix kernel: sd 11:0:0:0: [sdb] Stopping disk
Dec 17 20:47:39 strix kernel: sd 0:0:0:0: [sda] Stopping disk
Dec 17 20:47:39 strix kernel: ACPI: EC: interrupt blocked
Dec 17 20:47:39 strix kernel: ACPI: Preparing to enter system sleep state S3
Dec 17 20:47:39 strix kernel: ACPI: EC: event blocked
Dec 17 20:47:39 strix kernel: ACPI: EC: EC stopped
Dec 17 20:47:39 strix kernel: PM: Saving platform NVS memory
Dec 17 20:47:39 strix kernel: Disabling non-boot CPUs ...
Dec 17 20:47:39 strix kernel: smpboot: CPU 1 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 2 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 3 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 4 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 5 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 6 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 7 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 8 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 9 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 10 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 11 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 12 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 13 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 14 is now offline
Dec 17 20:47:39 strix kernel: smpboot: CPU 15 is now offline
Dec 17 20:47:39 strix kernel: ACPI: Low-level resume complete
Dec 17 20:47:39 strix kernel: ACPI: EC: EC started
Dec 17 20:47:39 strix kernel: PM: Restoring platform NVS memory
Dec 17 20:47:39 strix kernel: Enabling non-boot CPUs ...
Dec 17 20:47:39 strix kernel: x86: Booting SMP configuration:
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Dec 17 20:47:39 strix kernel: microcode: CPU1: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P001: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU1 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Dec 17 20:47:39 strix kernel: microcode: CPU2: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P002: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU2 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Dec 17 20:47:39 strix kernel: microcode: CPU3: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P003: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU3 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 4 APIC 0x4
Dec 17 20:47:39 strix kernel: microcode: CPU4: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P004: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU4 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 5 APIC 0x5
Dec 17 20:47:39 strix kernel: microcode: CPU5: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P005: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU5 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 6 APIC 0x6
Dec 17 20:47:39 strix kernel: microcode: CPU6: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P006: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU6 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Dec 17 20:47:39 strix kernel: microcode: CPU7: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P007: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU7 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 8 APIC 0x8
Dec 17 20:47:39 strix kernel: microcode: CPU8: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P008: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU8 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 9 APIC 0x9
Dec 17 20:47:39 strix kernel: microcode: CPU9: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P009: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU9 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 10 APIC 0xa
Dec 17 20:47:39 strix kernel: microcode: CPU10: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P00A: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU10 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Dec 17 20:47:39 strix kernel: microcode: CPU11: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P00B: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU11 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 12 APIC 0xc
Dec 17 20:47:39 strix kernel: microcode: CPU12: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P00C: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU12 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 13 APIC 0xd
Dec 17 20:47:39 strix kernel: microcode: CPU13: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P00D: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU13 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 14 APIC 0xe
Dec 17 20:47:39 strix kernel: microcode: CPU14: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P00E: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU14 is up
Dec 17 20:47:39 strix kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf
Dec 17 20:47:39 strix kernel: microcode: CPU15: patch_level=0x08001137
Dec 17 20:47:39 strix kernel: ACPI: \_PR_.P00F: Found 2 idle states
Dec 17 20:47:39 strix kernel: CPU15 is up
Dec 17 20:47:39 strix kernel: ACPI: Waking up from system sleep state S3
Dec 17 20:47:39 strix kernel: ACPI: EC: interrupt unblocked
Dec 17 20:47:39 strix kernel: ACPI: EC: event unblocked
Dec 17 20:47:39 strix kernel: usb usb1: root hub lost power or was reset
Dec 17 20:47:39 strix kernel: usb usb2: root hub lost power or was reset
Dec 17 20:47:39 strix kernel: sd 0:0:0:0: [sda] Starting disk
Dec 17 20:47:39 strix kernel: sd 11:0:0:0: [sdb] Starting disk
Dec 17 20:47:39 strix kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
Dec 17 20:47:39 strix kernel: r8169 0000:06:00.0 enp6s0: Link is Down
Dec 17 20:47:39 strix kernel: [drm] UVD and UVD ENC initialized successfully.
Dec 17 20:47:39 strix kernel: [drm] VCE initialized successfully.
Dec 17 20:47:39 strix kernel: ata6: SATA link down (SStatus 0 SControl 330)
Dec 17 20:47:39 strix kernel: ata2: SATA link down (SStatus 0 SControl 300)
Dec 17 20:47:39 strix kernel: usb 1-9: reset full-speed USB device number 4 using xhci_hcd
Dec 17 20:47:39 strix kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 17 20:47:39 strix kernel: ata12.00: configured for UDMA/133
Dec 17 20:47:39 strix kernel: usb 1-8: reset high-speed USB device number 3 using xhci_hcd
Dec 17 20:47:39 strix kernel: usb 1-10: reset full-speed USB device number 5 using xhci_hcd
Dec 17 20:47:39 strix kernel: ata5: failed to resume link (SControl 0)
Dec 17 20:47:39 strix kernel: ata5: SATA link down (SStatus 0 SControl 0)
Dec 17 20:47:39 strix kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
Dec 17 20:47:39 strix kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
Dec 17 20:47:39 strix kernel: usb 1-3: reset high-speed USB device number 2 using xhci_hcd
Dec 17 20:47:39 strix kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
Dec 17 20:47:39 strix kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
Dec 17 20:47:39 strix kernel: OOM killer enabled.
Dec 17 20:47:39 strix kernel: Restarting tasks ... 
Dec 17 20:47:39 strix kernel: usb 4-1: Failed to suspend device, error -19
Dec 17 20:47:39 strix kernel: Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8822
Dec 17 20:47:39 strix kernel: done.
Dec 17 20:47:39 strix kernel: Bluetooth: hci0: RTL: rom_version status=0 version=2
Dec 17 20:47:39 strix kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_fw.bin
Dec 17 20:47:39 strix kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_config.bin
Dec 17 20:47:39 strix kernel: Bluetooth: hci0: RTL: cfg_sz 14, total sz 20270
Dec 17 20:47:39 strix kernel: PM: suspend exit
...
Dec 17 20:47:41 strix systemd[1]: systemd-suspend.service: Succeeded.
Dec 17 20:47:41 strix systemd[1]: Finished Suspend.
Dec 17 20:47:41 strix systemd[1]: Stopped target Sleep.
Dec 17 20:47:41 strix systemd[1]: Reached target Suspend.
Dec 17 20:47:41 strix systemd-logind[1592]: Operation 'sleep' finished.
Dec 17 20:47:41 strix systemd[1]: Stopped target Suspend.
Dec 17 20:47:41 strix ModemManager[1653]: <info>  [sleep-monitor] system is resuming
...
Dec 17 20:47:47 strix NetworkManager[1587]: <info>  [1608238067.3025] device (enp6s0): carrier: link connected
Dec 17 20:47:48 strix kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
Dec 17 20:47:48 strix kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
Dec 17 20:47:48 strix systemd[1]: Started Getty on tty2.

Edit: Yes, this failure to resume is caused (on my system) by amdgpu.dc=0 as it occurs with 5.9.15-lqx too:

Dec 17 21:09:03 strix kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
Dec 17 21:09:03 strix kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed
Dec 17 21:09:03 strix kernel: ata5: failed to resume link (SControl 0)
Dec 17 21:09:03 strix kernel: ata5: SATA link down (SStatus 0 SControl 0)
Dec 17 21:09:03 strix kernel: usb 1-10: reset full-speed USB device number 5 using xhci_hcd
Dec 17 21:09:03 strix kernel: usb 1-8: reset high-speed USB device number 3 using xhci_hcd
Dec 17 21:09:03 strix kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* displayport link status failed
Dec 17 21:09:03 strix kernel: [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed

Last edited by jonathon (2020-12-17 21:13:32)

Offline

#22 2020-12-17 21:18:31

DRFK
Member
Registered: 2020-12-17
Posts: 3

Re: [SOLVED] Linux 5.10.1 prevents boot

Offline

#23 2020-12-17 21:21:19

jonathon
Member
Registered: 2016-09-19
Posts: 128

Re: [SOLVED] Linux 5.10.1 prevents boot

That's a pretty handy first post... big_smile

I'll try a kernel build and confirm whether the patch works.

Edit: OK, so I did an unsystematic thing and applied both patches referred to in the bug report. However, one or both resolves the immediate issue with linux-zen-5.10.1 - boot works correctly again (and suspend works correctly again, though I have not yet tested suspend with amdgpu.dc=0).

Last edited by jonathon (2020-12-18 01:59:05)

Offline

#24 2020-12-18 06:49:08

Roken
Member
From: South Wales, UK
Registered: 2012-01-16
Posts: 1,193

Re: [SOLVED] Linux 5.10.1 prevents boot

So hopefully 5.10.2 will have the patches applied with no more workaround necessary (though amdgpu.dc=0 has given me no problems, but I can't do much testing until tomorrow. As I said, I need this laptop for work, so don't have the luxury Monday - Friday of testing and breaking).


Ryzen 1800x 8 core/16 thread - 2 x GTX 1070 8Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703

Offline

#25 2020-12-21 16:06:16

jonathon
Member
Registered: 2016-09-19
Posts: 128

Re: [SOLVED] Linux 5.10.1 prevents boot

This patch does not seem to be included in 5.10.2:

https://git.kernel.org/pub/scm/linux/ke … .10.1&dt=2

Is it worth filing a bug and requesting this to be picked up as a patch until it reaches the kernel proper?

Offline

Board footer

Powered by FluxBB