openSUSE 13.2: Unable to wake successfully from suspend. No interrupt handler

English Hardware
#1

I’m having an issue with a new openSUSE 13.2 install with GNOME on my desktop where I’m unable to successfully wake from suspend. My desktop will physically act like it’s resuming normally, but then a single message is displayed on screen. The message is:

  • do_IRQ: 2.140 No irq handler vector irq -1

I’ve been using this desktop for years, and the suspend function has always worked with previous versions of openSUSE.

I don’t see anything immediately problematic in the journald log, but this seems to be the relevant section of the log for the suspend and resume:
16531-Nov 05 22:54:23 linux-q5s7 kernel: PM: Syncing filesystems … done. 16532-Nov 05 22:54:23 linux-q5s7 kernel: PM: Preparing system for mem sleep
16533-Nov 06 06:44:10 linux-q5s7 kernel: Freezing user space processes … (elapsed 0.001 seconds) done.
16534-Nov 06 06:44:10 linux-q5s7 kernel: Freezing remaining freezable tasks … (elapsed 0.001 seconds) done.
16535-Nov 06 06:44:10 linux-q5s7 kernel: PM: Entering mem sleep
16536:Nov 06 06:44:10 linux-q5s7 kernel: Suspending console(s) (use no_console_suspend to debug)
16537-Nov 06 06:44:10 linux-q5s7 kernel: sd 4:0:1:0: [sdb] Synchronizing SCSI cache
16538-Nov 06 06:44:10 linux-q5s7 kernel: sd 4:0:1:0: [sdb] Stopping disk
16539-Nov 06 06:44:10 linux-q5s7 kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
16540-Nov 06 06:44:10 linux-q5s7 kernel: serial 00:05: disabled
16541-Nov 06 06:44:10 linux-q5s7 kernel: serial 00:05: System wakeup disabled by ACPI
16542-Nov 06 06:44:10 linux-q5s7 kernel: sd 4:0:0:0: [sda] Stopping disk
16543:Nov 06 06:44:10 linux-q5s7 kernel: PM: suspend of devices complete after 832.903 msecs
16544:Nov 06 06:44:10 linux-q5s7 kernel: PM: late suspend of devices complete after 0.297 msecs
16545-Nov 06 06:44:10 linux-q5s7 kernel: pcieport 0000:00:1c.0: System wakeup enabled by ACPI
16546-Nov 06 06:44:10 linux-q5s7 kernel: pcieport 0000:00:1c.7: System wakeup enabled by ACPI
16547-Nov 06 06:44:10 linux-q5s7 kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
16548-Nov 06 06:44:10 linux-q5s7 kernel: ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
16549:Nov 06 06:44:10 linux-q5s7 kernel: PM: noirq suspend of devices complete after 11.663 msecs
16550-Nov 06 06:44:10 linux-q5s7 kernel: ACPI: Preparing to enter system sleep state S3
16551-Nov 06 06:44:10 linux-q5s7 kernel: PM: Saving platform NVS memory
16552-Nov 06 06:44:10 linux-q5s7 kernel: Disabling non-boot CPUs …
16553-Nov 06 06:44:10 linux-q5s7 kernel: Broke affinity for irq 41
16554-Nov 06 06:44:10 linux-q5s7 kernel: kvm: disabling virtualization on CPU1
16555-Nov 06 06:44:10 linux-q5s7 kernel: smpboot: CPU 1 is now offline
16556-Nov 06 06:44:10 linux-q5s7 kernel: Broke affinity for irq 42
16557-Nov 06 06:44:10 linux-q5s7 kernel: Broke affinity for irq 50
16558-Nov 06 06:44:10 linux-q5s7 kernel: kvm: disabling virtualization on CPU2
16559-Nov 06 06:44:10 linux-q5s7 kernel: smpboot: CPU 2 is now offline
16560-Nov 06 06:44:10 linux-q5s7 kernel: Broke affinity for irq 21
16561-Nov 06 06:44:10 linux-q5s7 kernel: Broke affinity for irq 43
16562-Nov 06 06:44:10 linux-q5s7 kernel: kvm: disabling virtualization on CPU3
16563-Nov 06 06:44:10 linux-q5s7 kernel: smpboot: CPU 3 is now offline
16564-Nov 06 06:44:10 linux-q5s7 kernel: ACPI: Low-level resume complete
16565-Nov 06 06:44:10 linux-q5s7 kernel: PM: Restoring platform NVS memory
16566-Nov 06 06:44:10 linux-q5s7 kernel: Enabling non-boot CPUs …
16567-Nov 06 06:44:10 linux-q5s7 kernel: x86: Booting SMP configuration:
16568-Nov 06 06:44:10 linux-q5s7 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
16569-Nov 06 06:44:10 linux-q5s7 kernel: kvm: enabling virtualization on CPU1
16570-Nov 06 06:44:10 linux-q5s7 kernel: hpet: hpet3 irq 41 for MSI
16571-Nov 06 06:44:10 linux-q5s7 kernel: CPU1 is up
16572-Nov 06 06:44:10 linux-q5s7 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
16573-Nov 06 06:44:10 linux-q5s7 kernel: kvm: enabling virtualization on CPU2
16574-Nov 06 06:44:10 linux-q5s7 kernel: hpet: hpet4 irq 42 for MSI
16575-Nov 06 06:44:10 linux-q5s7 kernel: CPU2 is up
16576-Nov 06 06:44:10 linux-q5s7 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
16577-Nov 06 06:44:10 linux-q5s7 kernel: kvm: enabling virtualization on CPU3
16578-Nov 06 06:44:10 linux-q5s7 kernel: hpet: hpet5 irq 43 for MSI
16579-Nov 06 06:44:10 linux-q5s7 kernel: CPU3 is up
16580-Nov 06 06:44:10 linux-q5s7 kernel: ACPI: Waking up from system sleep state S3
16581-Nov 06 06:44:10 linux-q5s7 kernel: ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
16582-Nov 06 06:44:10 linux-q5s7 kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
16583-Nov 06 06:44:10 linux-q5s7 kernel: pata_jmicron 0000:03:00.1: Refused to change power state, currently in D3
16584-Nov 06 06:44:10 linux-q5s7 kernel: PM: noirq resume of devices complete after 62.756 msecs
16585-Nov 06 06:44:10 linux-q5s7 kernel: PM: early resume of devices complete after 0.209 msecs
16586-Nov 06 06:44:10 linux-q5s7 kernel: snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
16587-Nov 06 06:44:10 linux-q5s7 kernel: pcieport 0000:00:1c.0: System wakeup disabled by ACPI
16588-Nov 06 06:44:10 linux-q5s7 kernel: pcieport 0000:00:1c.7: System wakeup disabled by ACPI
16589-Nov 06 06:44:10 linux-q5s7 kernel: sd 4:0:0:0: [sda] Starting disk
16590-Nov 06 06:44:10 linux-q5s7 kernel: sd 4:0:1:0: [sdb] Starting disk
16591-Nov 06 06:44:10 linux-q5s7 kernel: serial 00:05: activated
16592-Nov 06 06:44:10 linux-q5s7 kernel: e1000e 0000:06:00.0: irq 46 for MSI/MSI-X
16593-Nov 06 06:44:10 linux-q5s7 kernel: e1000e 0000:06:00.0: irq 47 for MSI/MSI-X
16594-Nov 06 06:44:10 linux-q5s7 kernel: e1000e 0000:06:00.0: irq 49 for MSI/MSI-X
16595-Nov 06 06:44:10 linux-q5s7 kernel: usb 2-1.7: reset high-speed USB device number 6 using ehci-pci
16596-Nov 06 06:44:10 linux-q5s7 kernel: ata1: SATA link down (SStatus 0 SControl 300)
16597-Nov 06 06:44:10 linux-q5s7 kernel: ata2: SATA link down (SStatus 0 SControl 300)
16598-Nov 06 06:44:10 linux-q5s7 kernel: ata7: SATA link down (SStatus 0 SControl 300)
16599-Nov 06 06:44:10 linux-q5s7 kernel: ata8: SATA link down (SStatus 0 SControl 300)
16600-Nov 06 06:44:10 linux-q5s7 kernel: firewire_core 0000:07:03.0: rediscovered device fw0
16601-Nov 06 06:44:10 linux-q5s7 kernel: ata6.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
16602-Nov 06 06:44:10 linux-q5s7 kernel: ata6.01: SATA link down (SStatus 0 SControl 300)
16603-Nov 06 06:44:10 linux-q5s7 kernel: ata6.01: link offline, clearing class 3 to NONE
16604-Nov 06 06:44:10 linux-q5s7 kernel: ata6.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
16605-Nov 06 06:44:10 linux-q5s7 kernel: ata6.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
16606-Nov 06 06:44:10 linux-q5s7 kernel: ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
16607-Nov 06 06:44:10 linux-q5s7 kernel: ata6.00: configured for UDMA/100
16608-Nov 06 06:44:10 linux-q5s7 kernel: do_IRQ: 2.140 No irq handler for vector (irq -1)

I’m happy to provide any additional information. Thanks

#2

Hi
What graphics card are you using? A google on part of the error ‘No irq handler vector irq -1’ shows shows bugs, so maybe a kernel regression?

This one talks about gpu lockups http://ubuntuforums.org/archive/index.php/t-2231402.html maybe it just comes to light after coming out from suspend.

#3

I had this problem with 13.2, RC1. The solution was to replace nouveau with the 13.1 Nvidia driver. The first thing I did with the 13.2 final release was to install the Nvidia driver and I don’t have a problem with resuming from sleep/hibernate.

#4

I have the same problem with wake up from suspend. I see only the black screen. I can not even start a terminal by Ctrl+Alt+n…:frowning:
Videocard - AMD Radeon HD7970. Help!

#5

I am getting the same message, System wakeup disabled by ACPI, on 13.2 with a Radeon 5450 graphics card.

#6

So what driver?

#7

The only Radeon driver available in 13.2 at this time is the open source driver. Fglrx has a conflict with the new XORG system and isn’t useable yet.

#8

I have the same problem. Mostly I can’t resume. The screen is black, no interaction possible. So, a power off is needed.

I run the radeon driver. Hardware: On Board, ATI Radeon HD 4200 (RV620).

I also tried to set following in /etc/pm/config.d/radeon:

SUSPEND_MODULES="radeon";

But that did not help. How can this be debugged?

On openSUSE 13.1 I had no problem with suspend to RAM.

#9

AMD fixed the compatibility issue with the new XORG at some point this summer for Catalyst drivers downloaded from its website. Is there some reason not to download the latest Catalyst beta driver from AMD and try it?

#10

Hey again,

My graphics card is “01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] (rev a2)”, and I’m using the Nvidia driver. This is the only graphics card on my system, so it shouldn’t be an issue of blacklisting another card/driver.

I did just receive a graphics card update. I’m about to test to see if that did the trick. It just updated to “340.58-31.1” through the “ftp://download.nvidia.com/opensuse/13.2/” repo.

#11

Well, the graphics driver update at least lets me wake from suspend successfully. I do still have a small issue that the background is screwed up (black and white static pattern) when it resumes, but it’s completely usable other than that. Still seems like there’s something weird going on with this Linux kernel if other people were having these kinds of issues with both Nvidia and AMD cards.

#12

The incompatibility problem with AMD video cards and the new XORG also caused problems for Canonical’s Ubuntu family of distros this spring. As far as I know they still don’t have a fixed driver in their repository.

#13

confirmed. Radeon HD 7850 on OpenSUSE 13.2 (default everything-fresh install)

Strange, but I have to have admin privileges to use lspci :sarcastic:


dragonslayer@linux-muel:~> sudo lspci | grep VGA
root's password:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850]
#14

There is now a Radeon FGLRX driver for 13.2. See https://lizards.opensuse.org/tag/fglrx/ . At least on my computer it runs fine but makes resume from suspend worse. The screen no longer powers up on resume so there are no diagnostic messages at all. Used pm-suspend and checked the log. All messages show a successful suspend process but no sign of a resume start. Anyone having any success with this problem?

#15

I have two graphics cards (Intel embedded + Nvidia GeForce, using bumblebee with nvidia proprietary drivers from bumblebee repo) and I also have problems with resume from suspend to disk. Usually when I resume from suspend to disk the screen blocking works OK, but when I enter password and enter desktop the system hangs up. Mouse cursor moves, but all other functionality is hanged up. Ctrl+Alt+n doesn’t work too.

Sometimes (very seldom, however) the system is resumed OK, but primusrun fails to work (the discrete card fails to wake up).

Does someone else have the same problems?