linux-ext4 - [Bug 118401] Lenovo A740 gave up waiting for root device with kernels >= 4.3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-118401-13602-Po7WnQkevD@https.bugzilla.kernel.org/>
Date:	Sat, 04 Jun 2016 13:45:15 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 118401] Lenovo A740 gave up waiting for root device with
 kernels >= 4.3

https://bugzilla.kernel.org/show_bug.cgi?id=118401

--- Comment #23 from Navin <navinp1912@...il.com> ---
1) First is 

Why does these lines get printed in 4.2
[    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

where as in 4.4 and 4.6 you don't get to see even the "version 3.0".

In your initramfs shell , you should try to see if ahci is actually loaded in
/proc/modules


2)

One more thing is i see in 4.2 you have this in dmesg
libata version 3.00 loaded.

I hope in 4.6 also you get that message.

You can find it out in your initramfs scripts by doing dmesg | grep -i libata


That should tell you that your modules are not loaded/good because of some
changes or some other reason like corruption?

At the end of initramfs you can do modprobe ahci and see that it prints
lsmod | grep ahci


That should tell you the reason why it is not printing those messages in dmesg.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html