|
Bugzilla – Full Text Bug Listing |
| Summary: | Lenovo B570 does not power off after shutdown | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Bob Vickers <bob> |
| Component: | Kernel | Assignee: | openSUSE Kernel Bugs <kernel-bugs> |
| Status: | NEW --- | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | bob, spidertux.alternativo, tiwai |
| Version: | Leap 15.6 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | /var/log/messages | ||
|
Description
Bob Vickers
2024-06-19 08:06:25 UTC
Do you see any kernel trace or such while hanging at shutdown? Also, please check whether the issue is seen on the recent upstream kernel, too. You can install 6.9.x kernel-default from OBS Kernel:stable:Backport repo http://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/ Thanks for the suggestions. (1) I didn't notice any unusual messages at shutdown (2) I installed kernel-default-6.9.7-lp155.2.1.ga5efffa and the problem still happened. (3) I also checked the kernel which came out a few days ago (6.4.0-150600.23.7-default ) and that also gives the problem. Thanks for confirmation. As it happens with 6.9.x kernel, it looks like an upstream regression. Could you check with the latest Leap 15.5 kernel in OBS Kernel:SLE15-SP5 repo, too? http://download.opensuse.org/repositories/Kernel:/SLE15-SP5/pool/ I've tried kernel 5.14.21-150500.307.gf3bb6e6-default and the problem still occurs. So the problem isn't something new, as it seems. You can try older kernels from my OBS repos, e.g. home:tiwai:kernel:5.11, home:tiwai:kernel:5.10, ... http://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.11/standard/ http://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.10/standard/ And it'd be helpful if you can find out any old working kernel (in this regard). Then we can narrow down the regression range. Hi, I'm having exactly same issue in OpenSuse LEAP 15.5 x86_64, using 5.14.21-150500.55.68-default kernel. It was correctly working with the previous 5.14.21-150500.55.65-default kernel. Kernel is updated from this repository: http://download.opensuse.org/update/leap/15.5/sle/x86_64/ Best regards. (In reply to Eduardo Barambio from comment #6) > Hi, > > I'm having exactly same issue in OpenSuse LEAP 15.5 x86_64, using > 5.14.21-150500.55.68-default kernel. > > It was correctly working with the previous 5.14.21-150500.55.65-default > kernel. So if you boot with the previous kernel while keeping the rest new, it's working? > Kernel is updated from this repository: > http://download.opensuse.org/update/leap/15.5/sle/x86_64/ > > Best regards. Bob, please verify whether the kernel above works for you (and the newer one actually breaks), too. (In reply to Takashi Iwai from comment #7) > (In reply to Eduardo Barambio from comment #6) > > Hi, > > > > I'm having exactly same issue in OpenSuse LEAP 15.5 x86_64, using > > 5.14.21-150500.55.68-default kernel. > > > > It was correctly working with the previous 5.14.21-150500.55.65-default > > kernel. > > So if you boot with the previous kernel while keeping the rest new, it's > working? > > > Kernel is updated from this repository: > > http://download.opensuse.org/update/leap/15.5/sle/x86_64/ > > > > Best regards. > > Bob, please verify whether the kernel above works for you (and the newer one > actually breaks), too. Yes it is, if I boot with previous 5.14.21-150500.55.65-default kernel, it correctly works. Best regards. Sorry to muddy the waters when it looked like you were close to a solution, but my experience is not the same as Eduardo's. The URL above does not seem to be a valid repository, so instead I installed kernel-default-5.14.21-150500.55.65.1 from repository http://cdn.opensuse.org/update/leap/15.5/sle Unfortunately the problem still occurs with this kernel. Thanks for confirmation. So the original from Bob is a different issue. Eduardo, please open another bug for tracking your bug. |