Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#33106 - New block hook in mkinitcpio 0.12 causes kernel dump during boot

Attached to Project: Arch Linux
Opened by Al T. (alfmel) - Sunday, 16 December 2012, 15:45 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 16 December 2012, 16:54 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


I have a weird situation where loading PATA modules during the initrd process causes my machine to crash (I have no PATA devices on my system). The workaround was easy until mkinitcpio-0.12: remove the pata hook. However, in version 0.12 that is not longer an option.

I really like the new, simpler block hook. However, I've had several cases (like I do now) where a particular kernel and hardware combination doesn't behave well during boot and I have to remove hooks and blacklist modules. Would it be possible to keep the original sata, pata, etc. hooks for such cases, or somehow blacklist certain groups of modules from the new block hook?
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 16 December 2012, 16:54 GMT
Reason for closing:  Won't fix
Comment by Dave Reisner (falconindy) - Sunday, 16 December 2012, 16:07 GMT
No, it isn't possible. Find out what the faulty module is get it fixed (and temporarily blacklisted). I'm not reintroducing a rat's nest of hooks just to work around problems.

This sounds a lot like:
Comment by Al T. (alfmel) - Sunday, 16 December 2012, 16:51 GMT
I intend to file the bug report to the kernel folks and hopefully it will be fixed soon. I understand why you don't want to maintain a rat's nest, but that rat's nest provided me with the flexibility to work around hardware/driver issues. :-/

Thanks for the link.
Comment by Dave Reisner (falconindy) - Sunday, 16 December 2012, 16:54 GMT
Yes, work around. Not fix. That isn't how we operate here.