Bug 2211784
| Summary: | fedora 38 kernel 6.3.4 boot fail upon upgrade | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robert Koppelhuber <robert.koppelhuber> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 38 | CC: | acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, huupoke12, jarodwilson, jforbes, josef, kernel-maint, kjell.m.randa, lgoncalv, linville, masami256, mchehab, mcornea, nikita, ptalbert, py0xc3, steved, vincent |
| Target Milestone: | --- | Keywords: | Desktop, FastFix, Regression, Upgrades |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://discussion.fedoraproject.org/t/fedora-hangs-on-boot-after-upgrading-to-kernel-6-3-4/83605/4 | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-6.3.6-100.fc37 kernel-6.3.6-200.fc38 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-06-09 01:38:06 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Robert Koppelhuber
2023-06-01 22:58:19 UTC
Created attachment 1968441 [details]
infostate & journalctl for pre&post upgrade to F38 but without 6.3.4 as unable to boot. So used 6.2.14
Infostat and journalctl for 1st June 2023 ~ 8am Australian Eastern std time when upgrade process was started. Can only provide journalctl with kernel 6.2.14 as 6.3.4 upgrade will not boot or provide diagnostics.
Pls note that I have now a different email. Attempted to change but was unable to. Refer email received when reporting below: Hello! RITM1501812 (Unable to change email re bugzilla) has been created. Requested for: Guest Thank you for contacting the RH Bugzilla team. Your request is in our system. Item contains my new email. I have new account which initially raised the issue (see link of thread) with my content details as well. Ignore last re email. All sorted bugzilla email servers was down. See if https://koji.fedoraproject.org/koji/taskinfo?taskID=101713227 works for you. This might be the nvidia issue with simpledrm that was supposed to be fixed in the nvidia driver a couple of months ago, but seems it is not. This is linked to https://discussion.fedoraproject.org/t/fedora-hangs-on-boot-after-upgrading-to-kernel-6-3-4/83605/20 and https://bugzilla.redhat.com/show_bug.cgi?id=2212012 (In reply to Christopher Klooz from comment #5) > This is linked to > https://discussion.fedoraproject.org/t/fedora-hangs-on-boot-after-upgrading- > to-kernel-6-3-4/83605/20 and > https://bugzilla.redhat.com/show_bug.cgi?id=2212012 It may or it may not be, but none of this is helpful, there are exactly 2 bugs where I put up the link to the scratch build to test a fix. This is one of them. Linking people away from this bug does nothing to get it resolved, I just need someone to actually test the fix and let me know if it solves it or not. Rather than linking away from one of the bugs where I posted a possible solution, it would be much more helpful to close dups as dups of a bug with the solution. If anyone would bother testing at all, we might even have a fix pushed with 6.3.6 when I build it in the next day or so. (In reply to Justin M. Forbes from comment #4) > See if https://koji.fedoraproject.org/koji/taskinfo?taskID=101713227 works > for you. This might be the nvidia issue with simpledrm that was supposed to > be fixed in the nvidia driver a couple of months ago, but seems it is not. This works for me. (In reply to Justin M. Forbes from comment #6) I do not link them away but led them here. The ask.fedora topic is actually the reason for this bug report to exist. Both users started there and then filed separated bug reports. Average users tend to end up at ask.fedora and not on bugzilla, which is why I link it. Some may be experienced and check out carefully all links and elaborations in both ask.fedora and the bug reports, but many less experienced users we have just click through "link by link" while hoping it leads at some point to an easy-to-implement solution. This is why I linked the reports. I cannot test your build since I do not experience this issue, but I can lead people here and ensure that those who accidentally end up on the wrong of the two bug reports, which have risen from the ask.fedora topic, are then led to the respective other one, but it is also to avoid that one issue is treated twice or even more often. If users miss the report that is relevant for them, they open another topic at ask.fedora, which might end up at another supporter who doesn't know of the other one (including the related bug reports), and so on... This shall be in your interest, and shall avoid that you need to paste your solution in the end to 10 reports, but also that all users at ask.fedora end up asap at your solution (so that one may gives feedback). (In reply to Justin M. Forbes from comment #4) > See if https://koji.fedoraproject.org/koji/taskinfo?taskID=101713227 works > for you. This might be the nvidia issue with simpledrm that was supposed to > be fixed in the nvidia driver a couple of months ago, but seems it is not. Thank you, this works for me. Created attachment 1969151 [details]
Another sudo journalctl -r --boot=-1 after 6.3.4-201 fail then boot 6.2.15-300
Another sudo journalctl -r --boot=-1 after 6.3.4-201 fail then boot 6.2.15-300
Proceeding now to try https://koji.fedoraproject.org/koji/taskinfo?taskID=101713227 Please bear with me. Inexperienced in doing these experiemental kernel installs. Never done this before and very anxious about breaking system. Done all my backups and time shift though. Proceeding to do ... sudo dnf update https://kojipkgs.fedoraproject.org//work/tasks/3237/101713237/kernel-6.3.5-201.fc38.x86_64.rpm https://kojipkgs.fedoraproject.org//work/tasks/3237/101713237/kernel-core-6.3.5-201.fc38.x86_64.rpm https://kojipkgs.fedoraproject.org//work/tasks/3237/101713237/kernel-modules-6.3.5-201.fc38.x86_64.rpm https://kojipkgs.fedoraproject.org//work/tasks/3237/101713237/kernel-modules-core-6.3.5-201.fc38.x86_64.rpm https://kojipkgs.fedoraproject.org//work/tasks/3237/101713237/kernel-modules-extra-6.3.5-201.fc38.x86_64.rpm (In reply Robert Koppelhuber from comment #12) It's explained in the ask.fedora topic: https://discussion.fedoraproject.org/t/fedora-hangs-on-boot-after-upgrading-to-kernel-6-3-4/83605/24 Just use it to test if the bug is solved. Then everything should be fine. Created attachment 1969155 [details]
6.3.5-Successfull test
Thank you success full test but per attachment https://bugzilla.redhat.com/attachment.cgi?id=1969155 did remove 6.3.4 before hand which included removal of dependies akmod-nivida. $ uname -a Linux earth 6.3.5-201.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jun 1 15:13:15 UTC 2023 x86_64 GNU/Linux Given This might be the nvidia issue with simpledrm that was supposed to be fixed in the nvidia driver a couple of months ago, but seems it is not any relationship with that? Further since F38 upgrade a few weeks ago I note that Plasma desktop on login screen choosing Plasma X11 or Xorg cause it the come back to login inscreen. Unable to login. Can with Plasma Wayland desktop. Can also login with Gnome. Since F36 have been forced to use Nvidia drivers due to Plasma wayland desktop being unstable with irregular sudden complete freeze with control including alt sequences. Powerdown only solution. With nvidia drivers rock solid. Under F38 for the short while under wayland have been getting less often but still same freeze requiring power off. Would prefer to use Plasma Xorg. Wayland re nvidia is just not quiet right. Where are we up to re the nvidia story, open source, wayland drivers???? FEDORA-2023-ed3bcae7e8 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-ed3bcae7e8 FEDORA-2023-70b0935c41 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-70b0935c41 Created attachment 1969412 [details]
Journalctl for 6.3.5-test-201
Previous attachment F38-kernel-6.3.5-test-201-Success.txt uploaded the log for journalctl -r boot=-1 which effectively was 6.2.5.
This upload is for the booting
$ uname -a
Linux earth 6.3.5-201.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jun 1 15:13:15 UTC 2023 x86_64 GNU/Linux
Sorry!
FEDORA-2023-70b0935c41 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-70b0935c41` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-70b0935c41 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-ed3bcae7e8 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-ed3bcae7e8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-ed3bcae7e8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. The new kernel fixes the missing console and /proc/fb now contains 0 VESA VGA instead of beeing empty. Tested on two machines using the proprietary Nvidia driver. FEDORA-2023-70b0935c41 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-ed3bcae7e8 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. Just confirming, installed kernel 6.3.6 with complete update from std repo for F38. Boot and functions OK. |