You are not logged in.
Pages: 1
Recently (I noticed a couple of days ago), when I return from suspend, my mouse and keyboard behave very slow. When I move the mouse, it lags behind and takes some time to catch up. It also misses some events (i.e., if I drag it across the whole pad it won't reach the edge of the screen, which it does if everything is normal). The keyboard also takes some time to type letters and also misses them if I type to fast.
The only two things I changed are running an update (pacman -Syu) and installing a new hard drive that replaced another one. When looking at my syslog I noticed the following lines:
Aug 13 12:44:50 archdesktop kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Aug 13 12:44:50 archdesktop kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: P O 3.15.8-1-ARCH #1
Aug 13 12:44:50 archdesktop kernel: Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7583/P55-GD65 (MS-7583) , BIOS V1.3 09/03/2009
Aug 13 12:44:50 archdesktop kernel: 0000000000000000 ab8c312356cab162 ffff88023fc03e60 ffffffff815087fe
Aug 13 12:44:50 archdesktop kernel: ffff880233415000 ffff88023fc03e88 ffffffff810ca8c2 ffff880233415000
Aug 13 12:44:50 archdesktop kernel: 0000000000000000 0000000000000010 ffff88023fc03ec0 ffffffff810cac77
Aug 13 12:44:50 archdesktop kernel: Call Trace:
Aug 13 12:44:50 archdesktop kernel: <IRQ> [<ffffffff815087fe>] dump_stack+0x4d/0x6f
Aug 13 12:44:50 archdesktop kernel: [<ffffffff810ca8c2>] __report_bad_irq+0x32/0xd0
Aug 13 12:44:50 archdesktop kernel: [<ffffffff810cac77>] note_interrupt+0x257/0x2a0
Aug 13 12:44:50 archdesktop kernel: [<ffffffff810c81ce>] handle_irq_event_percpu+0xae/0x1f0
Aug 13 12:44:50 archdesktop kernel: [<ffffffff810c834d>] handle_irq_event+0x3d/0x60
Aug 13 12:44:50 archdesktop kernel: [<ffffffff810cb8b1>] handle_fasteoi_irq+0x81/0x170
Aug 13 12:44:50 archdesktop kernel: [<ffffffff81016bce>] handle_irq+0x1e/0x40
Aug 13 12:44:50 archdesktop kernel: [<ffffffff8151854d>] do_IRQ+0x4d/0xe0
Aug 13 12:44:50 archdesktop kernel: [<ffffffff8150e1ed>] common_interrupt+0x6d/0x6d
Aug 13 12:44:50 archdesktop kernel: <EOI> [<ffffffff8101d479>] ? sched_clock+0x9/0x10
Aug 13 12:44:50 archdesktop kernel: [<ffffffff813d4539>] ? cpuidle_enter_state+0x49/0xc0
Aug 13 12:44:50 archdesktop kernel: [<ffffffff813d45e7>] cpuidle_enter+0x17/0x20
Aug 13 12:44:50 archdesktop kernel: [<ffffffff810b2275>] cpu_startup_entry+0x385/0x4f0
Aug 13 12:44:50 archdesktop kernel: [<ffffffff814fd7f4>] rest_init+0x84/0x90
Aug 13 12:44:50 archdesktop kernel: [<ffffffff818f5ea6>] start_kernel+0x448/0x469
Aug 13 12:44:50 archdesktop kernel: [<ffffffff818f5120>] ? early_idt_handlers+0x120/0x120
Aug 13 12:44:50 archdesktop kernel: [<ffffffff818f54d7>] x86_64_start_reservations+0x2a/0x2c
Aug 13 12:44:50 archdesktop kernel: [<ffffffff818f5626>] x86_64_start_kernel+0x14d/0x170
Aug 13 12:44:50 archdesktop kernel: handlers:
Aug 13 12:44:50 archdesktop kernel: [<ffffffffa003c2d0>] usb_hcd_irq [usbcore]
Aug 13 12:44:50 archdesktop kernel: [<ffffffffa025f840>] ata_bmdma_interrupt [libata]
Aug 13 12:44:50 archdesktop kernel: Disabling IRQ #16Looking at /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
0: 50 0 0 13358 0 0 0 0 IO-APIC-edge timer
1: 1 0 0 2 0 0 0 0 IO-APIC-edge i8042
8: 0 0 0 1 0 0 0 0 IO-APIC-edge rtc0
9: 0 0 0 0 0 0 0 0 IO-APIC-fasteoi acpi
12: 0 0 0 4 0 0 0 0 IO-APIC-edge i8042
16: 0 15140 0 0 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb1, pata_jmicron
17: 0 0 0 419 0 0 0 0 IO-APIC-fasteoi snd_hda_intel
18: 0 0 0 0 2 0 0 0 IO-APIC-fasteoi firewire_ohci, i801_smbus
19: 0 0 0 0 0 31547 0 0 IO-APIC-fasteoi ahci, ata_piix, ata_piix
23: 0 0 83 0 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb2
40: 18987 0 0 0 0 0 0 0 HPET_MSI-edge hpet2
41: 0 21641 0 0 0 0 0 0 HPET_MSI-edge hpet3
42: 0 0 19633 0 0 0 0 0 HPET_MSI-edge hpet4
43: 0 0 0 19291 0 0 0 0 HPET_MSI-edge hpet5
44: 0 0 0 0 10683 0 0 0 HPET_MSI-edge hpet6
45: 0 0 563 0 0 0 0 0 PCI-MSI-edge snd_hda_intel
47: 0 0 0 0 0 6633 0 0 PCI-MSI-edge eth1
48: 0 0 0 0 0 0 25957 0 PCI-MSI-edge nvidia
NMI: 27 26 30 29 31 33 38 31 Non-maskable interrupts
LOC: 68 57 51 44 38 11295 11915 9361 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 27 26 30 29 31 33 38 31 Performance monitoring interrupts
IWI: 0 1 0 0 1 0 1 1 IRQ work interrupts
RTR: 5 0 0 0 0 0 0 0 APIC ICR read retries
RES: 2050 1341 1135 1494 1758 1443 3024 1868 Rescheduling interrupts
CAL: 274 288 273 245 245 304 262 325 Function call interrupts
TLB: 1823 2238 1380 4096 1362 1959 1245 1470 TLB shootdowns
TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 2 2 2 2 2 2 2 2 Machine check polls
THR: 0 0 0 0 0 0 0 0 Hypervisor callback interrupts
ERR: 0
MIS: 0The jmicron part in the IRQ#16 row seems to hint that this might be the new drive having problems after suspend. The drive is a Seagate Barracuda 7200.14 1TB 3,5" SATA 6 Gb/s ST1000DM003. It also contains the swap partition required for hibernate mode (if that's relevant). The problem occurrs on suspend-to-ram and suspend-to-disk. Since there is also USB on the same interrupt this would seem to be the logical source of the problem.
However, I have no idea how to tackle it from here: Where does this problem come from? Is my drive broken? Does Linux have problems with it? I could probably just use different USB ports to switch the controller but I suppose if there is a real problem with suspending the disk, I'd like to know now and fix it.
Any help will be greatly appreciated. Thank you in advance.
Regards
javex
Offline
Pages: 1