You are not logged in.
I have an Asus x503m laptop that I upgraded to the latest kernel. Now at boot I get :
ms_block: read of pba x page 0 failed with error -5https://ibb.co/m48P7a,
a few random kernel workers hang and the system slows to a crawl. It takes a full 10 minutes to login when I actually get to that point.
The last kernel that works is the 4.10 kernel.
Edit:system is really bricked with this kernel, can't even finish booting now
Last edited by yungtrizzle (2017-06-09 17:58:13)
Offline
ms_block is "Sony MemoryStick block device driver" and there's obviously trouble to probe memstick0
a) do you have such thing at all?
b) is it crucial or can you remove it from the system?
c) add "modprobe.blacklist=ms_block" to the kernel parameters in the grub menu and see what happens.
Offline
My laptop does has a card reader slot that I use occasionally, but it's non removable, it's part of the motherboard.
The modprobe blacklist didn't have any effect, I had chroot in and downgrade.
Offline
If you successfully blacklisted the module, the error message in the screenshot should have disappeared, ie. is a red herring. Confirmed?
Offline
You might want to blacklist some other module instead, ms_block does not provide support for any hardware so it is most probably a dependency for some other module. You might be able to find out which module by looking at the output of lsmod from a kernel that boots.
That said, I have a laptop with a card reader that supports memory sticks and it never worked very well with memory sticks, even having the memory stick driver and support modules loaded could interfere with SD cards so if you don't need support for memory sticks just blacklist everything memory stick related. If you use the modconf hook you could even do that from a simple .conf file, when you regenerate the initramfs it will be included and block the modules from loading even if some find their way into the initramfs.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
"modinfo ms_block" prints a line "depends: memstick". Perhaps try to blacklist that "memstick" module. It has a description "Sony MemoryStick core driver".
Last edited by Ropid (2017-06-01 15:36:17)
Offline
If you successfully blacklisted the module, the error message in the screenshot should have disappeared, ie. is a red herring. Confirmed?
The message didn't disappear, literally zero net change.
@ROOKIE I'll poke around the 4.10 kernel and see what I can find.
Offline
@ropid, this means ms_block depends on memstick ie. the former pulls in the latter.
According to "grep ms_block /usr/lib/modules/`uname -r`/modules.dep" nothing depends on ms_block, so we'll have to wait for yungtrizzle to check why it's loaded.
@yungtrizzle
you might use the "install ms_block /bin/false" trick to keep it unloaded (and see whether that makes a difference)
https://wiki.archlinux.org/index.php/Ke … obe.d.2F_2
Offline
I never figured out what was loading ms_block at boot time, however the last kernel update seems to repaired the culprit. I am marking this solved/closed
Offline