[SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

lpr1 · 2019-10-09 09:32:53

As title says, reverting kernel back to 5.3.4-arch1-1-ARCH would "solve" an issue. After initiating shutdown/reboot, system shuts down properly according to the journalctl, it reaches target 'reboot' and stops journaling, nothing really out of the ordinary in there, display turns off, however computer stays turned on indefinitely (tested up to 5-7 hours, after I've gone to sleep, script shut the computer down after some time, and when I woke up it was still working as described above).

Does anyone have similar issue and potential solution for it?

It might be related to this, but I've opened new thread because hardware is different (non-Intel) and issue did not appear at the time that topic was created:
https://bbs.archlinux.org/viewtopic.php?id=249544

Last edited by lpr1 (2019-10-19 22:18:53)

bwidlar · 2019-10-09 13:46:26

Same problem here since some weeks ago, but my monitor stay on.

lpr1 · 2019-10-09 14:13:48

bwidlar wrote:

Same problem here since some weeks ago, but my monitor stay on.

Do you happen to use UEFI installation with GOP enabled?

bwidlar · 2019-10-09 15:49:47

No UEFI.

My problem is intermittent, about 50% of boots something crash in the kernel,
but the pc is ok, all works fine.

The only problem is that the shutdown/reboot doesnt works.
I need to study it, I was waiting some days to some kernel update that magically fix the issue.

loqs · 2019-10-09 16:01:03

@lpr1 if you rebuild 5.3.4-arch1-1-ARCH with the current gcc toolchain does that still work?
If so could you bisect 5.3.4 to 5.3.5 to locate the cause and report it upstream please?

lpr1 · 2019-10-09 16:14:10

bwidlar wrote:

No UEFI.
My problem is intermittent, about 50% of boots something crash in the kernel,
but the pc is ok, all works fine.
The only problem is that the shutdown/reboot doesnt works.
I need to study it, I was waiting some days to some kernel update that magically fix the issue.

Ok, I have no issues with crashes, but same as you, shutdown and reboot doesn't work.

@loqs
I will try it now and report back, thanks for suggestion.

ratcheer · 2019-10-10 21:17:40

My system shuts down successfully, according to the journal, but it just sits there with the power on, but not rebooting (this is after "systemctl reboot"). If I press the hardware reset button, the system then reboots. I'm also NOT on UEFI.

lpr1 · 2019-10-10 22:05:03

ratcheer wrote:

My system shuts down successfully, according to the journal, but it just sits there with the power on, but not rebooting (this is after "systemctl reboot"). If I press the hardware reset button, the system then reboots. I'm also NOT on UEFI.

Same exact issue, I'm now testing to find a commint that created a problem, I'm having issues managing those commits and how linux kernel is structured, for example tagged commit for 5.3.4 (that works fine for me) is 7a82e3fa28f174ba23c9faca544c65986e3025f1, and tagged commit for 5.3.5 (that doesn't work well) is d0dea733f60efe94257d08ae6eba81d0b511d0a9, but it seems that included commits in the tree are not all commits to the specific date, so I'm trying to figure that out.

lpr1 · 2019-10-11 14:54:22

loqs wrote:

@lpr1 if you rebuild 5.3.4-arch1-1-ARCH with the current gcc toolchain does that still work?
If so could you bisect 5.3.4 to 5.3.5 to locate the cause and report it upstream please?

Bisected and commit to blame (in my case) is 894c414129a8d9ef1b2de443015e4dde6085f64f

Removing that specific commit in master branch (5.4-rc2) would make kernel work as expected. Not sure where should I report the issue, also, can you guys (who ahve same problem) test it without that commit as well to see if it's the same issue?

894c414129a8d9ef1b2de443015e4dde6085f64f is the first bad commit
commit 894c414129a8d9ef1b2de443015e4dde6085f64f
Author: KyleMahlkuch <kmahlkuc@linux.vnet.ibm.com>
Date:   Wed Jul 31 17:10:14 2019 -0500

    drm/radeon: Fix EEH during kexec
    
    [ Upstream commit 6f7fe9a93e6c09bf988c5059403f5f88e17e21e6 ]
    
    During kexec some adapters hit an EEH since they are not properly
    shut down in the radeon_pci_shutdown() function. Adding
    radeon_suspend_kms() fixes this issue.
    
    Signed-off-by: KyleMahlkuch <kmahlkuc@linux.vnet.ibm.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 drivers/gpu/drm/radeon/radeon_drv.c | 8 ++++++++
 1 file changed, 8 insertions(+)

@loqs, sorry I reported you by accident with the text above..., moderators please ignore that report, I clicked it by mistake instead of 'quote' and when I saw what I did I've already clicked submit...

Last edited by lpr1 (2019-10-11 14:56:10)

ewaller · 2019-10-11 15:24:33

lpr1 wrote:

moderators please ignore that report, I clicked it by mistake instead of 'quote' and when I saw what I did I've already clicked submit...

Yep, saw that It happens more often than one might imagine.

lpr1 · 2019-10-11 15:34:21

ewaller wrote:

lpr1 wrote:
moderators please ignore that report, I clicked it by mistake instead of 'quote' and when I saw what I did I've already clicked submit...
Yep, saw that It happens more often than one might imagine.

Never happened to me before , but I apologize, my bad, no harm done hopefully .

loqs · 2019-10-11 15:47:57

You can report it upstream https://bugs.freedesktop.org/ product=DRI component=DRM/Radeon
If you prefer using mailing lists

perl scripts/get_maintainer.pl drivers/gpu/drm/radeon/radeon_drv.c
Alex Deucher <alexander.deucher@amd.com> (supporter:RADEON and AMDGPU DRM DRIVERS)
"Christian König" <christian.koenig@amd.com> (supporter:RADEON and AMDGPU DRM DRIVERS)
"David (ChunMing) Zhou" <David1.Zhou@amd.com> (supporter:RADEON and AMDGPU DRM DRIVERS)
David Airlie <airlied@linux.ie> (maintainer:DRM DRIVERS)
Daniel Vetter <daniel@ffwll.ch> (maintainer:DRM DRIVERS)
amd-gfx@lists.freedesktop.org (open list:RADEON and AMDGPU DRM DRIVERS)
dri-devel@lists.freedesktop.org (open list:DRM DRIVERS)
linux-kernel@vger.kernel.org (open list)

lpr1 · 2019-10-11 15:56:02

loqs wrote:

You can report it upstream https://bugs.freedesktop.org/ product=DRI component=DRM/Radeon
If you prefer using mailing lists

perl scripts/get_maintainer.pl drivers/gpu/drm/radeon/radeon_drv.c
Alex Deucher <alexander.deucher@amd.com> (supporter:RADEON and AMDGPU DRM DRIVERS)
"Christian König" <christian.koenig@amd.com> (supporter:RADEON and AMDGPU DRM DRIVERS)
"David (ChunMing) Zhou" <David1.Zhou@amd.com> (supporter:RADEON and AMDGPU DRM DRIVERS)
David Airlie <airlied@linux.ie> (maintainer:DRM DRIVERS)
Daniel Vetter <daniel@ffwll.ch> (maintainer:DRM DRIVERS)
amd-gfx@lists.freedesktop.org (open list:RADEON and AMDGPU DRM DRIVERS)
dri-devel@lists.freedesktop.org (open list:DRM DRIVERS)
linux-kernel@vger.kernel.org (open list)

Cool, thank you, I think I have account there. Sorry again for that mistake above .

Arch Linux

#1 2019-10-09 09:32:53

[SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

#2 2019-10-09 13:46:26

Re: [SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

#3 2019-10-09 14:13:48

Re: [SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

#4 2019-10-09 15:49:47

Re: [SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

#5 2019-10-09 16:01:03

Re: [SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

#6 2019-10-09 16:14:10

Re: [SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

#7 2019-10-10 21:17:40

Re: [SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

#8 2019-10-10 22:05:03

Re: [SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

#9 2019-10-11 14:54:22

Re: [SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

#10 2019-10-11 15:24:33

Re: [SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

#11 2019-10-11 15:34:21

Re: [SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

#12 2019-10-11 15:47:57

Re: [SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

#13 2019-10-11 15:56:02

Re: [SOLVED] Can't reboot or shutdown after kernel upgrade to 5.3.5

Board footer