Sometimes I get a "disabling IRQ#16" at boot
by vladimir1986 from LinuxQuestions.org on (#5N18F)
Hello. I am having a bit of a problem which happens (sometimes) at boot.
Randomly I get an error (I guess it is an IRQ conflict?) and I am told that IRQ #16 has been disabled. this happens upon boot. IRQ#16 is assigned to my pointing device, and seems to be shared between my touchpad and my trackpoint (the red mousey button in the middle of the keyboard in Thinkpads).
When it happens, most of the time the computer freezes and I need to force reboot it, but rarely it manages to boot. Just that I got no mouse. I get this problem, say 45% of the times I try to start the computer with Arch Linux.
I tough for a long time it was a bad firmware update (after an update now I also got a MeSliLock error every time I boot), but after getting a second drive for my computer and installing FreeBSD, Gentoo and Slackware on different partitions, I noticed I only got this IRQ#16 problem in Arch.
I am not sure what can cause it, but I am wondering if it isn't a systemD problem (thinking about it, happens just after loading the Kernel, while it boots, and it is the only OS in my computer who uses systemd), but maybe it could also be some oddity on the binary kernel package.
I would love to know what really causes it, and if it can be avoided. In any case, thanks for reading!
Randomly I get an error (I guess it is an IRQ conflict?) and I am told that IRQ #16 has been disabled. this happens upon boot. IRQ#16 is assigned to my pointing device, and seems to be shared between my touchpad and my trackpoint (the red mousey button in the middle of the keyboard in Thinkpads).
When it happens, most of the time the computer freezes and I need to force reboot it, but rarely it manages to boot. Just that I got no mouse. I get this problem, say 45% of the times I try to start the computer with Arch Linux.
I tough for a long time it was a bad firmware update (after an update now I also got a MeSliLock error every time I boot), but after getting a second drive for my computer and installing FreeBSD, Gentoo and Slackware on different partitions, I noticed I only got this IRQ#16 problem in Arch.
I am not sure what can cause it, but I am wondering if it isn't a systemD problem (thinking about it, happens just after loading the Kernel, while it boots, and it is the only OS in my computer who uses systemd), but maybe it could also be some oddity on the binary kernel package.
I would love to know what really causes it, and if it can be avoided. In any case, thanks for reading!