Bug 1312178
Summary: | Kernel 4.4.2 does not boot on DELL PRECISION T7610 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sammy <umar> | ||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 23 | CC: | gansalmon, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-02-29 22:07:43 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: | |||||||
Attachments: |
|
Description
Sammy
2016-02-26 00:51:10 UTC
Can you share full journalctl output for both working and non-working cases? How do I do this on the non-working case? It does not boot! If there is a way I will do this tomorrow morning when I am at work. If you're seeing a dracut message that means it's booting enough. Can you set it up to drop into a dracut shell? https://fedoraproject.org/wiki/How_to_debug_Dracut_problems#Using_the_dracut_shell Sorry but need more direction....I am at the dracut shell prompt. I insert a usb stick in. The light of the stick stays on. Where is the device name and how do I mount it? I boot with the usb stick in and the dracut log shows that it was recognized but I can't find how to mount it. blkid gives nothing. Created attachment 1131571 [details]
Screen shot from journalctl
This is from 4.4.3-300 installed this morning. The problem persists. I'm wondering if this is the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1313025 . Can you run the following commands and see if it gives you any output: # lsinitrd -k 4.3.5-300.fc23.x86_64 | grep mpt3sas # lsinitrd -k 4.3.5-300.fc23.x86_64 | grep mpt2sas This is checking the initrd of the last kernel version that worked for you (4.3.5 which was mentioned in the other thread) to see if it contains a particular kernel module. If I didn't get the kernel version correct, please change the version to the actual last version that worked for you. On the 4.3.5-300: # lsinitrd -k 4.3.5-300.fc23.x86_64 | grep mpt3sas # lsinitrd -k 4.3.5-300.fc23.x86_64 | grep mpt2sas drwxr-xr-x 2 root root 0 Feb 1 08:43 usr/lib/modules/4.3.5-300.fc23.x86_64/kernel/drivers/scsi/mpt2sas -rw-r--r-- 1 root root 81284 Jan 31 22:08 usr/lib/modules/4.3.5-300.fc23.x86_64/kernel/drivers/scsi/mpt2sas/mpt2sas.ko.xz I do believe this system uses one of these. Thanks for checking. I'm almost certain this is a duplicate of that bug based on the output. The issue is in dracut and not the kernel. For a workaround you can do # dracut --force --add-drivers mpt3sas --kver=4.4.2-300.fc23.x86_64 and then run the lsinitrd command to confirm that mpt3sas driver is being included in your initrd. You will need to run this dracut command to add the driver every time you change the kernel or put add_drivers+="mpt3sas" in your /etc/dracut.conf *** This bug has been marked as a duplicate of bug 1313025 *** I will do this as soon as a job ends. But it makes sense since one of the working systems have the Fusion-MPT SAS-3 but the non working system has Fusion-MPT SAS-2. If the name changed to SAS3 then the working system pick to correct one but since there is no sas2 it fails. |