Bug 1462421
Summary: | kernel-4.11.5-200 x86_64 fail to boot on Thinkpad T510 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jonathan Baron <jonathanbaron7> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 25 | CC: | gansalmon, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-12 10:36:28 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jonathan Baron
2017-06-17 12:40:19 UTC
Can you boot with quiet removed from the kernel command line and see if you can get a picture of the full backtrace? (In reply to Laura Abbott from comment #1) > Can you boot with quiet removed from the kernel command line and see if you > can get a picture of the full backtrace? Can't figure out how to do this. First I trued stopping the boot and editing the command line. This used to work, but now it shows a whole bunch of stuff, many lines, not one, and none containing the word "quiet". I found the word in /etc/grub.conf, in the listing for this kernel (in a line that looked like what I used to see), and I removed it and booted, but the screen looked the same as it did before. No additional information. Any hints appreciated. (In reply to Laura Abbott from comment #1) > Can you boot with quiet removed from the kernel command line and see if you > can get a picture of the full backtrace? I figured out how to do this, I think. There was a LOT of stuff scrolling down the screen. Some of it looked like backtrace, but even that was too long to fit on one screen. I had trouble making photos with my phone. Would a video be better? I put a few of the legible ones (sometimes barely legible) in http://finzi.psych.upenn.edu/~baron/bootpics.tar. (Very large file, so I didn't attach it here.) Maybe you can use this to tell me what to look for next time and I can try to catch it. I was able to boot the 4.11.6-201.fc25.x86_64 kernel by setting two options: nouveau.noaccel=1 pci=noacpi The first may not be necessary, but it is harmless on this old (but still extremely useful, and extensively used) computer. The second is necessary. I also tried edd=off, but that was not necessary. In the course of doing all this, on one of the times this kernel did not boot, I got a few more pictures. The screen had slowed down considerably, and it looked like it was providing more information than before. However, I see that nobody has looked at my earlier pictures, so I won't bother posting these unless someone asks. It occurs to me that this problem results from the fact that I remove the cdrom drive. It was broken and spinning around all the time for no purpose. And not needed anymore. This would explain why nobody else has reported this problem or found this bug report. In the kernel boot record that I get by hitting "e" on the initial boot screen, it has an option like search --no-floppy Perhaps if I add one for "--no-cdrom" it will work, but I can't find any list of such options. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |