Created attachment 469560 [details] dmesg of kernel 2.6.35.9-65, which boots fine Description of problem: Since kernel 2.6.35.10-67, my laptop (Compal JFL92) hangs on boot. I'm not able to login or ssh to it, so I cannot provide much information, however it seems related to the loading of the driver for the IR device, which uses the ene_ir driver. Blacklisting the driver doesn't help. It might also be an error on how udev handles the process. The error I see in text console is this: udevd-work[517] '/sbin/modprobe -bv acpi:ENE0100:' unexpected exit with status 0x0009 I cannot obtain a kernel log of the boot process, however I attach that of kernel 2.6.35.9-65, which is the last version that works fine on my system. I'm available for further information if required! Version-Release number of selected component (if applicable): kernel-2.6.35.10-67.fc14.x86_64 How reproducible: Always on boot Steps to Reproduce: 1. Just boot with kernel-2.6.35.10-67.fc14.x86_64 Actual results: System hangs with error from udevd-work Expected results: System boots fine
kernel-2.6.35.10-69.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kernel-2.6.35.10-69.fc14
Hrm, don't have any ene hardware myself, will have to point the driver author towards this bug, see if he has any ideas... I presume if you move ene_ir.ko out of the kernel module path entirely, the system boots fine?
see bug 664145, for x86 systems
Sorry I'm having some plane misadventures right now, however I should be able to try that this evening (Central Europe time).
*** This bug has been marked as a duplicate of bug 664145 ***
kernel-2.6.35.10-72.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kernel-2.6.35.10-72.fc14
kernel-2.6.35.10-72.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
Problem still persists with kernel-2.6.35.10-72.fc14
Yeah, I'll try to sort out a workaround unless Jarod beats me to it. (Probably just restore the 'classic' driver which worked.)
This would seem to be a duplicate of bug 664145.