From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3
Date: Sat, 04 Jun 2016 06:28:04 +0000 [thread overview]
Message-ID: <bug-118401-13602-mEy9tVmvOc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-118401-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=118401
--- Comment #21 from Navin <navinp1912@gmail.com> ---
Can youou have ahci modules present in your initramfs ?
Mine returns like
1) lsinitramfs /boot/initrd.img-4.7.0-rc1+ | grep -i ahci
lib/modules/4.7.0-rc1+/kernel/drivers/ata/ahci_platform.ko
lib/modules/4.7.0-rc1+/kernel/drivers/ata/ahci.ko
lib/modules/4.7.0-rc1+/kernel/drivers/ata/libahci.ko
lib/modules/4.7.0-rc1+/kernel/drivers/ata/libahci_platform.ko
lib/modules/4.7.0-rc1+/kernel/drivers/ata/acard-ahci.ko
2) If the above returns that it is present and loaded confirmed by grep -i ahci
/proc/modules from your initramfs
grep -i ahci /proc/modules
ahci 36864 2 - Live 0xffffffffc0044000
libahci 32768 1 ahci, Live 0xffffffffc0015000
If (1) and (2) work as expected like described ie they are loaded and present.
Please post the output of (1) and (2) what it returns in your case.
3)
Then maybe something related to irq like described in
https://bugzilla.kernel.org/show_bug.cgi?id=111211
where comment 7 says "It works with 'pci=routeirq' parameter" in kernel command
line.
I asked for this because your 4.2 dmesg showed something like
[ 0.716610] ahci 0000:00:1f.2: version 3.0
[ 0.716620] ahci 0000:00:1f.2: can't find IRQ for PCI INT B; probably buggy
MP table
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-06-04 6:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 11:41 [Bug 118401] New: Lenovo A740 gave up waiting for root device with kernels >= 4.3 bugzilla-daemon
2016-05-18 16:02 ` [Bug 118401] " bugzilla-daemon
2016-05-19 8:40 ` bugzilla-daemon
2016-05-19 8:42 ` bugzilla-daemon
2016-05-19 8:43 ` bugzilla-daemon
2016-05-19 8:56 ` bugzilla-daemon
2016-05-24 13:07 ` bugzilla-daemon
2016-05-24 14:37 ` bugzilla-daemon
2016-05-24 17:46 ` bugzilla-daemon
2016-05-31 5:51 ` bugzilla-daemon
2016-06-01 15:26 ` bugzilla-daemon
2016-06-01 16:02 ` bugzilla-daemon
2016-06-01 18:53 ` bugzilla-daemon
2016-06-01 21:50 ` bugzilla-daemon
2016-06-02 10:28 ` bugzilla-daemon
2016-06-02 12:52 ` bugzilla-daemon
2016-06-02 18:19 ` bugzilla-daemon
2016-06-03 19:03 ` bugzilla-daemon
2016-06-03 19:04 ` bugzilla-daemon
2016-06-03 19:07 ` bugzilla-daemon
2016-06-03 19:08 ` bugzilla-daemon
2016-06-04 6:28 ` bugzilla-daemon [this message]
2016-06-04 9:36 ` bugzilla-daemon
2016-06-04 13:45 ` bugzilla-daemon
2016-06-04 22:05 ` bugzilla-daemon
2016-06-05 1:46 ` bugzilla-daemon
2016-06-05 11:12 ` bugzilla-daemon
2016-06-05 11:14 ` bugzilla-daemon
2016-06-05 12:21 ` bugzilla-daemon
2016-06-05 13:43 ` bugzilla-daemon
2016-06-06 7:27 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-118401-13602-mEy9tVmvOc@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox