LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 01-15-2013, 12:14 AM   #1
jms89
Member
 
Registered: Jan 2013
Posts: 37

Rep: Reputation: Disabled
PM: Device 00:08 failed to resume: error -19


Hi, I'm not 100% sure where this best belongs, but I think this forum is the best fit. I'm running linux Mint and when the system thaws from suspend, the following error message is displayed:

Code:
[97616.379490] dpm_run_callback(): pnp_bus_resume+0x0/0x80 returns -19
[97616.379492] PM: Device 00:08 failed to resume: error -19
So far everything on the system seems to be running fine, but I'd like to understand what this means and how to fix it if possible. Any ideas what to do?

The error message was retrieved with the following command:

Code:
dmesg -l err
If you're not able to help, maybe you know how to find out what "Device 00:08" is, and I can start from there? Any advice on how to troubleshoot this is welcome (I'm mostly a newbie still).

Thanks!
 
Old 01-15-2013, 04:53 PM   #2
Kustom42
Senior Member
 
Registered: Mar 2012
Distribution: Red Hat
Posts: 1,565

Rep: Reputation: 410Reputation: 410Reputation: 410Reputation: 410Reputation: 410
Quote:
Originally Posted by jms89 View Post
when the system thaws from suspend
When it thaws?! how long are you leaving it in your freezer?


Well this is saying that a plug and play device can't be re-initialized. This could be by design of the the pnp device you are using or could be a firmware issue not understanding the system call correctly.

Either way, if you aren't having any troubles with your periphials then its not much to worry about. If you want to figure out exactly what device it is complaining about you can look at:

Code:
lspci
And compare the bus mapping in the lspci output to the 00:08 map that you are given in your error message.
 
Old 01-16-2013, 01:55 AM   #3
jms89
Member
 
Registered: Jan 2013
Posts: 37

Original Poster
Rep: Reputation: Disabled
Thanks for the reply. I'm not really concerned about this error, I'm mainly interested in it for educational purposes.

I tried using lspci, but no "00:08" seems to be in the output:

Code:
jared@j-bot / $ lspci -v -b
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
	Subsystem: Dell Device 0569
	Flags: bus master, fast devsel, latency 0
	Capabilities: <access denied>

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
	Subsystem: Dell Device 0569
	Flags: bus master, fast devsel, latency 0, IRQ 7
	Memory at c0000000 (64-bit, non-prefetchable)
	Memory at b0000000 (64-bit, prefetchable)
	I/O ports at 3000
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915

00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI])
	Subsystem: Dell Device 0569
	Flags: bus master, medium devsel, latency 0
	Memory at c0600000 (64-bit, non-prefetchable)
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd

00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
	Subsystem: Dell Device 0569
	Flags: bus master, fast devsel, latency 0, IRQ 7
	Memory at c0614000 (64-bit, non-prefetchable)
	Capabilities: <access denied>
	Kernel driver in use: mei
	Kernel modules: mei

00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI])
	Subsystem: Dell Device 0569
	Flags: bus master, medium devsel, latency 0, IRQ 7
	Memory at c0619000 (32-bit, non-prefetchable)
	Capabilities: <access denied>
	Kernel driver in use: ehci_hcd

00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
	Subsystem: Dell Device 0569
	Flags: bus master, fast devsel, latency 0, IRQ 10
	Memory at c0610000 (64-bit, non-prefetchable)
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd-hda-intel

00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Prefetchable memory behind bridge: 00000000c0400000-00000000c04fffff
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	Memory behind bridge: c0500000-c05fffff
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) (prog-if 20 [EHCI])
	Subsystem: Dell Device 0569
	Flags: bus master, medium devsel, latency 0, IRQ 11
	Memory at c0618000 (32-bit, non-prefetchable)
	Capabilities: <access denied>
	Kernel driver in use: ehci_hcd

00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
	Subsystem: Dell Device 0569
	Flags: bus master, medium devsel, latency 0
	Capabilities: <access denied>
	Kernel modules: lpc_ich

00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0])
	Subsystem: Dell Device 0569
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 10
	I/O ports at 3088
	I/O ports at 3094
	I/O ports at 3080
	I/O ports at 3090
	I/O ports at 3060
	Memory at c0617000 (32-bit, non-prefetchable)
	Capabilities: <access denied>
	Kernel driver in use: ahci

00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
	Subsystem: Dell Device 0569
	Flags: medium devsel, IRQ 10
	Memory at c0615000 (64-bit, non-prefetchable)
	I/O ports at 3040
	Kernel modules: i2c-i801

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)
	Subsystem: Dell Device 0569
	Flags: bus master, fast devsel, latency 0, IRQ 7
	I/O ports at 2000
	Memory at c0404000 (64-bit, prefetchable)
	Memory at c0400000 (64-bit, prefetchable)
	Capabilities: <access denied>
	Kernel driver in use: r8169
	Kernel modules: r8169

02:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
	Subsystem: Intel Corporation Centrino Wireless-N 2230 BGN
	Flags: bus master, fast devsel, latency 0, IRQ 11
	Memory at c0500000 (64-bit, non-prefetchable)
	Capabilities: <access denied>
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
Any other suggestions?
 
Old 01-16-2013, 10:51 AM   #4
Kustom42
Senior Member
 
Registered: Mar 2012
Distribution: Red Hat
Posts: 1,565

Rep: Reputation: 410Reputation: 410Reputation: 410Reputation: 410Reputation: 410
Do a

Code:
dmidecode | grep "0x80"
and see if it provides you with a bios output of the device.

---------- Post added 01-16-13 at 09:52 AM ----------

Also do a

Code:
lsusb
This looks more like a usb device the more I look at the error.
 
Old 02-26-2013, 10:15 PM   #5
etdoughe
LQ Newbie
 
Registered: Feb 2013
Posts: 1

Rep: Reputation: Disabled
Possible fix:

I had the same exact error and this seemed to fix it:

Change: GRUB_CMDLINE_LINUX=""
to: GRUB_CMDLINE_LINUX="i8042.nopnp"

in /etc/default/grub

Then do a sudo update-grub, and then a restart.

Something to do with the trackpad. My trackpad had always worked. But now it still works, with no error message!


Also, I was told by tech support that the fact that I was seeing this message meant that the display manager may have been crashing. Apparently, when the display manager is going, we should not see error messages upon resuming (they could be there, we just should not see them). This could be a problem with a SSD. For me, I ran memtest and had RAM errors. You may want to check out these components on your machine also.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
resume: could not stat the resume device file Zaskar Debian 17 03-29-2012 10:10 PM
Device 00:0a failed to resume: error -19 samineru Linux - Newbie 1 10-06-2011 11:47 AM
libata error "failed to resume link (Scontrol 0)" page_seven Linux - Kernel 1 09-14-2010 04:20 PM
Cant resume device...booting error.. shady_Dev Linux - Hardware 1 10-13-2008 08:51 AM
resume: cannot stat resume device file sixerjman Linux - Kernel 0 05-27-2007 03:09 PM


All times are GMT -5. The time now is 03:45 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration