"Bug 1255441 - Cannot shutdown or reboot" — only a few people affected?

Dear all,

I am referring to “Bug 1255441 - Cannot shutdown or reboot” https://bugzilla.opensuse.org/show_bug.cgi?id=1255441 .

I migrated very late from 15.6 to 16.0 — but I am affected, indeed.

I wonder if just some people are…? As this is really annoying but it doen’t seem to be of much impact…

Many posable reasons but top one is NVIDIA involved? If so what card

I reported that bug. And, no, I do not have NVIDIA graphics. This is a Intel system.

My current work-around is to install the kernel from Tumbleweed. Shutdown and reboot work as they should with the Tumbleweed kernel, but not with the Leap 16 kernel.

2 Likes

Yes, here too: no NVIDIA, just Intel.

I am thinking whether to leave swap (instead of using a TW kernel).

I’m not sure what you mean by that.

No issue here. Mesa Intel UHD Graphics 620

It happens to me, Intel graphics

swapoff -a.

gunnersson@tulicube:~> my_inxi -G
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: Gigabyte
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: HDMI-A-2 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:3e91
    class-ID: 0300
  Display: wayland server: Xwayland v: 24.1.6 compositor: LabWC driver:
    gpu: i915 display-ID: 0
  Monitor-1: HDMI-A-2 model: EIZO NANAO EV2450 serial: <filter> built: 2016
    res: 1920x1080 dpi: 92 gamma: 1.2 size: 528x297mm (20.79x11.69")
    diag: 606mm (23.9") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: de: xfce4-display-settings
gunnersson@tulicube:~> 

UHD Graphics 630

Great if that solves the problem for you.

I use swap whenever I boot up a Win11 VM. I’m inclined to keep the swap. But maybe I’ll try that as an experiment.

Not actually tried, yet. This is just my humble guess due to your bug report / the entire discussion there.

I have observed:

  • used swap=0 → shutdown OK
  • used swap>0 → issues…!

I am not yet so deep into it. I just wondered about the “bug” on my system. Then I googled around. Your report rather fits, so far.

1 Like

@nrickert

Maybe we should ask for the graphics built-in/used…? As, so far, it occurs on Intel?

(Just an idea. I don’t know. It’s just annoying. I have my Leap 16.0 since about 2 months. And do experience this bug.)

Ooops … I specified the Graphics hardware, but I failed to mention:
I do not use wayland. It’s too problematic on my machine(s).

From the discussion in the bug, it seems that there might be two different problems involved. For some people it has to do with whether swap is properly released. If you look at comment #47 in that bug report, my problem seemed to be different and freeing up the swap before shutdown did not help in my case.

https://bugzilla.opensuse.org/show_bug.cgi?id=1255441#c47

Yes, it seems to be a different problem. Maybe this bug report needs to be split into two.

When I first googled for this issue, I stumbled over several systemd-related problems in issue similar to this one. What has been notable: that/those systemd issue(-s) has/have been solved/closed in the past (several times) — but occurred again (in a similar way).

Well, yes: maybe for me, this would help

https://bugzilla.opensuse.org/show_bug.cgi?id=1255441#c54

Indeed, that i915 related change smells funny. Have you tested with the kernel linked in comment #42?

Also, could you give us the output of swaptop (in https://build.opensuse.org/package/show/home:vbabka/mmdebug-tools) when swapoff hangs? Hopefully you can switch VTs by that point.

It would be sad to revert that change - it has some attractive performance benefits. But having broken shutdown is much worse. I’m afraid we might have to revert this if we cannot figure it out. Or maybe we revert first and start testing later.

I agree with the sentiment that broken shutdown is worse.

That’s why I have been staying with the Tumbleweed kernel.

Hmm, I see that the Tumbleweed kernel is now at 7.0.12. So I’ll install before I next reboot.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.