FS#57582 - [linux] "No irq handler for vector" errors after resume (Lenovo P50)

Attached to Project: Arch Linux
Opened by Max Pray (synthead) - Tuesday, 20 February 2018, 15:51 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 03 April 2018, 18:31 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

On a Lenovo P50, after resuming from suspend, these lines are seen in dmesg:

[12058.061512] do_IRQ: 4.34 No irq handler for vector
[12058.087043] do_IRQ: 4.34 No irq handler for vector
[12058.112558] do_IRQ: 4.34 No irq handler for vector
[12058.138017] do_IRQ: 4.34 No irq handler for vector
[12058.163514] do_IRQ: 4.34 No irq handler for vector
[12062.957782] do_IRQ: 187 callbacks suppressed
[12062.957786] do_IRQ: 4.34 No irq handler for vector
[12062.983084] do_IRQ: 4.34 No irq handler for vector
[12063.008589] do_IRQ: 4.34 No irq handler for vector
[12063.034102] do_IRQ: 4.34 No irq handler for vector
[12063.059591] do_IRQ: 4.34 No irq handler for vector
[12063.085092] do_IRQ: 4.34 No irq handler for vector
[12063.110594] do_IRQ: 4.34 No irq handler for vector
[12063.136097] do_IRQ: 4.34 No irq handler for vector
[12063.161594] do_IRQ: 4.34 No irq handler for vector
[12063.187100] do_IRQ: 4.34 No irq handler for vector
[12067.981364] do_IRQ: 187 callbacks suppressed
[12067.981369] do_IRQ: 4.34 No irq handler for vector
[12068.006667] do_IRQ: 4.34 No irq handler for vector
[12068.032205] do_IRQ: 4.34 No irq handler for vector
[12068.057674] do_IRQ: 4.34 No irq handler for vector
[12068.083204] do_IRQ: 4.34 No irq handler for vector
[12068.108675] do_IRQ: 4.34 No irq handler for vector
[12068.134205] do_IRQ: 4.34 No irq handler for vector
[12068.159677] do_IRQ: 4.34 No irq handler for vector
[12068.185177] do_IRQ: 4.34 No irq handler for vector
[12068.210734] do_IRQ: 4.34 No irq handler for vector
[12073.004975] do_IRQ: 187 callbacks suppressed
[12073.004978] do_IRQ: 4.34 No irq handler for vector
[12073.030249] do_IRQ: 4.34 No irq handler for vector
[12073.055759] do_IRQ: 4.34 No irq handler for vector
[12073.081253] do_IRQ: 4.34 No irq handler for vector
[12073.106754] do_IRQ: 4.34 No irq handler for vector
[12073.132254] do_IRQ: 4.34 No irq handler for vector
[12073.157754] do_IRQ: 4.34 No irq handler for vector
[12073.183255] do_IRQ: 4.34 No irq handler for vector
[12073.208756] do_IRQ: 4.34 No irq handler for vector
[12073.234257] do_IRQ: 4.34 No irq handler for vector
[12078.028373] do_IRQ: 187 callbacks suppressed
[12078.028392] do_IRQ: 4.34 No irq handler for vector
[12078.053860] do_IRQ: 4.34 No irq handler for vector
[12078.079334] do_IRQ: 4.34 No irq handler for vector
[12078.104835] do_IRQ: 4.34 No irq handler for vector
[12078.130339] do_IRQ: 4.34 No irq handler for vector
[12078.155889] do_IRQ: 4.34 No irq handler for vector
[12078.181378] do_IRQ: 4.34 No irq handler for vector
[12078.206839] do_IRQ: 4.34 No irq handler for vector
[12078.232340] do_IRQ: 4.34 No irq handler for vector
[12078.257841] do_IRQ: 4.34 No irq handler for vector

While this is going on, the system feels unresponsive for about 20 seconds about every 10 seconds. Restarting the system seems to correct the issue. This is on linux 4.15.3-2.

Steps to reproduce:
1. Acquire a Lenovo P50 with an up-to-date version of Arch (might be reproducible on other systems)
2. Suspend
3. Resume
4. Observe that the system is writing the above messages to the ring buffer and that the system is unresponsive in ~10 second intervals
This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 03 April 2018, 18:31 GMT
Reason for closing:  Fixed
Comment by Sergio Correia (sergio.correia) - Friday, 30 March 2018, 04:26 GMT
Does adding pci=nomsi to your boot parameters help?
Comment by Max Pray (synthead) - Monday, 02 April 2018, 19:55 GMT
Actually, it seems as if the bug has been fixed somehow. I am not experiencing these issues anymore on linux 4.15.13-1.

Loading...