LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-16-2013, 08:40 AM   #1
firedrake
Member
 
Registered: May 2013
Posts: 59

Rep: Reputation: Disabled
Suspend / Resume takes to much time and generates errors - Kernel 3.12-rc5


Hi,

I'm compiling new kernel and trying to update my slackware 13.37 and go to current.
Previous kernel version I used, was 3.9.9 and everything was working ok. After kernel change to 3.11.x/3.12.x I had problems with NVIDIA so I went to 331.13 just to have some fixes.
Now I have kernel 3.12-rc5 and everything looks promising except the suspend/resume prcedure.

After Resume my screen stays black for 3-5 seconds and than desktop (KDE) shows up.
If I rmmod iwldvm and iwlwifi, everything works without any problem. So I don't know if it's problem with a new iwlwifi driver and firmware 18.168.6.1 or sth else like bios command, power management, etc.

This is the info I can find in my syslog:

Code:
Oct 14 01:22:35 matsu kernel: [ 4476.750384] Freezing user space processes ... (elapsed 0.001 seconds) done.
Oct 14 01:22:35 matsu kernel: [ 4476.751709] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 14 01:22:35 matsu kernel: [ 4476.752996] Suspending console(s) (use no_console_suspend to debug)
Oct 14 01:22:35 matsu kernel: [ 4476.929647] mei_me 0000:00:16.0: suspend
Oct 14 01:22:35 matsu kernel: [ 4477.249131] Disabling non-boot CPUs ...
Oct 14 01:22:35 matsu kernel: [ 4477.505848] iwlwifi 0000:08:00.0: RF_KILL bit toggled to enable radio.
Oct 14 01:22:35 matsu kernel: [ 4477.506674] sdhci-pci 0000:09:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Oct 14 01:22:35 matsu kernel: [ 4477.506691] sdhci-pci 0000:09:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Oct 14 01:22:35 matsu kernel: [ 4477.511435] ------------[ cut here ]------------
Oct 14 01:22:35 matsu kernel: [ 4477.511440] WARNING: CPU: 1 PID: 17649 at drivers/base/firmware_class.c:1082 _request_firmware+0x212/0x6cd()
Oct 14 01:22:35 matsu kernel: [ 4477.511456] Modules linked in: nvidia(PO) pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ppdev parport_pc parport joydev uvcvideo videobuf2_core videobuf2_vmalloc videobuf2_memops snd_hda_codec_hdmi btusb rtsx_pci_sdmmc rtsx_pci_ms iwldvm snd_hda_codec_ca0132 iwlwifi psmouse snd_hda_intel snd_hda_codec serio_raw sdhci_pci rtsx_pci snd_hwdep sdhci xhci_hcd dell_wmi mxm_wmi wmi mac_hid
Oct 14 01:22:35 matsu kernel: [ 4477.511458] CPU: 1 PID: 17649 Comm: kworker/u16:5 Tainted: P        W  O 3.12.0-rc4MatsuDotPl #8
Oct 14 01:22:35 matsu kernel: [ 4477.511458] Hardware name: Alienware M17xR4/M17xR4, BIOS A11 01/31/2013
Oct 14 01:22:35 matsu kernel: [ 4477.511463] Workqueue: events_unbound async_run_entry_fn
Oct 14 01:22:35 matsu kernel: [ 4477.511466]  00000000 00000000 ea745d10 c18306c4 c1aa8caa ea745d40 c106c69c c1a37cba
Oct 14 01:22:35 matsu kernel: [ 4477.511468]  00000001 000044f1 c1aa8caa 0000043a c1470e8c c1470e8c ea538060 fffffff5
Oct 14 01:22:35 matsu kernel: [ 4477.511470]  eded32d0 ea745d50 c106c6d0 00000009 00000000 ea745dac c1470e8c ea745d78
Oct 14 01:22:35 matsu kernel: [ 4477.511471] Call Trace:
Oct 14 01:22:35 matsu kernel: [ 4477.511475]  [<c18306c4>] dump_stack+0x4b/0x7f
Oct 14 01:22:35 matsu kernel: [ 4477.511477]  [<c106c69c>] warn_slowpath_common+0x79/0x90
Oct 14 01:22:35 matsu kernel: [ 4477.511479]  [<c1470e8c>] ? _request_firmware+0x212/0x6cd
Oct 14 01:22:35 matsu kernel: [ 4477.511480]  [<c1470e8c>] ? _request_firmware+0x212/0x6cd
Oct 14 01:22:35 matsu kernel: [ 4477.511482]  [<c106c6d0>] warn_slowpath_null+0x1d/0x1f
Oct 14 01:22:35 matsu kernel: [ 4477.511483]  [<c1470e8c>] _request_firmware+0x212/0x6cd
Oct 14 01:22:35 matsu kernel: [ 4477.511490]  [<f86542f7>] ? snd_hda_power_save+0x195/0x1cd [snd_hda_codec]
Oct 14 01:22:35 matsu kernel: [ 4477.511494]  [<f865443f>] ? codec_exec_verb+0xf0/0x1a1 [snd_hda_codec]
Oct 14 01:22:35 matsu kernel: [ 4477.511496]  [<c14713c7>] request_firmware+0x32/0x43
Oct 14 01:22:35 matsu kernel: [ 4477.511499]  [<f8838553>] ca0132_init+0x1a0/0xec1 [snd_hda_codec_ca0132]
Oct 14 01:22:35 matsu kernel: [ 4477.511504]  [<f8654f6c>] ? snd_hda_codec_read+0x31/0x42 [snd_hda_codec]
Oct 14 01:22:35 matsu kernel: [ 4477.511509]  [<f8655177>] hda_call_codec_resume+0x10a/0x149 [snd_hda_codec]
Oct 14 01:22:35 matsu kernel: [ 4477.511511]  [<f86e6f22>] ? azx_init_chip+0x1fe/0x225 [snd_hda_intel]
Oct 14 01:22:35 matsu kernel: [ 4477.511516]  [<f86551cd>] snd_hda_resume+0x17/0x2a [snd_hda_codec]
Oct 14 01:22:35 matsu kernel: [ 4477.511518]  [<f86e70d4>] azx_resume+0xc8/0xf6 [snd_hda_intel]
Oct 14 01:22:35 matsu kernel: [ 4477.511521]  [<c13b531a>] pci_pm_resume+0x53/0x63
Oct 14 01:22:35 matsu kernel: [ 4477.511523]  [<c146b796>] dpm_run_callback+0x29/0x61
Oct 14 01:22:35 matsu kernel: [ 4477.511525]  [<c13b52c7>] ? pci_pm_thaw+0x65/0x65
Oct 14 01:22:35 matsu kernel: [ 4477.511526]  [<c146ba69>] device_resume+0xfa/0x119
Oct 14 01:22:35 matsu kernel: [ 4477.511528]  [<c146baa1>] async_resume+0x19/0x3d
Oct 14 01:22:35 matsu kernel: [ 4477.511530]  [<c1089e2d>] async_run_entry_fn+0x69/0x128
Oct 14 01:22:35 matsu kernel: [ 4477.511533]  [<c10800e5>] process_one_work+0x156/0x25c
Oct 14 01:22:35 matsu kernel: [ 4477.511534]  [<c107e8c4>] ? start_worker+0x1f/0x22
Oct 14 01:22:35 matsu kernel: [ 4477.511536]  [<c107f636>] ? manage_workers.clone.18+0x17f/0x189
Oct 14 01:22:35 matsu kernel: [ 4477.511539]  [<c1080551>] worker_thread+0x133/0x1be
Oct 14 01:22:35 matsu kernel: [ 4477.511541]  [<c1084abe>] kthread+0x6b/0x70
Oct 14 01:22:35 matsu kernel: [ 4477.511543]  [<c108041e>] ? rescuer_thread+0x212/0x212
Oct 14 01:22:35 matsu kernel: [ 4477.511545]  [<c1833e77>] ret_from_kernel_thread+0x1b/0x28
Oct 14 01:22:35 matsu kernel: [ 4477.511547]  [<c1084a53>] ? kthread_freezable_should_stop+0x31/0x31
Oct 14 01:22:35 matsu kernel: [ 4477.511548] ---[ end trace 63116b775aa65f4c ]---
Oct 14 01:22:35 matsu kernel: [ 4477.511550] snd_hda_intel 0000:00:1b.0: firmware: ctefx.bin will not be loaded
Oct 14 01:22:35 matsu kernel: [ 4477.706697] dpm_run_callback(): pnp_bus_resume+0x0/0x6f returns -19
Oct 14 01:22:35 matsu kernel: [ 4477.706699] PM: Device 00:07 failed to resume: error -19
Oct 14 01:22:35 matsu kernel: [ 4480.561708] Restarting tasks ... done.
Oct 14 01:22:37 matsu dhcpcd[18258]: dhcpcd not running
Oct 14 01:22:38 matsu pmacctd[14170]: WARN ( default/core ): wlan0 has become unavailable; throttling ... 
Oct 14 01:22:38 matsu dhcpcd[18264]: dhcpcd not running
Oct 14 01:22:38 matsu dhcpcd[18271]: dhcpcd not running
Oct 14 01:29:16 matsu pulseaudio[9112]: alsa-sink.c: Error opening PCM device front:0: Urządzenie lub zasoby zajęte
Oct 14 01:29:16 matsu pulseaudio[9112]: sink-input.c: Failed to create sink input: sink is suspended.
Oct 14 01:29:16 matsu pulseaudio[9112]: alsa-sink.c: Error opening PCM device front:0: Urządzenie lub zasoby zajęte
See other files attached to this post.
Attached Files
File Type: txt dmesg_long_resume.txt (100.8 KB, 13 views)
File Type: txt debug2_long_resume.txt (176.9 KB, 17 views)
File Type: txt syslog_long_resume.txt (242.8 KB, 8 views)
 
Old 10-18-2013, 04:49 PM   #2
firedrake
Member
 
Registered: May 2013
Posts: 59

Original Poster
Rep: Reputation: Disabled
Hello,

I still have a problem with new kernel. Now I noticed that there is a problem with hard drive access time or something like this, because when I'm trying to save website or youtube movie in Firefox I'm waiting 5-10 seconds till it reads my folder content. I have to wait for every folder I'm trying to open.
Copying files doesn't show any kind of problem.

Can anybody tell me where should I look for any kind of solution. I would like to find out what is causing this problem.

Thanks in advance for any help.
 
  


Reply

Tags
kernel, power management, resume, suspend



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 (from suspend) only works 95% of the time Lop3 Linux - Software 3 10-10-2013 05:06 AM
Measure the time it takes to resume after hibernation linkaran Linux - General 3 03-10-2013 08:48 AM
Long resume time (from suspend) with AMD Fusion DavidBanner Linux - General 1 07-09-2012 07:01 AM
TuxOnIce, device resume from suspend takes way too long whoopie Linux - Software 3 08-08-2011 07:35 AM
Lenovo Thinkpad T61p - Takes a long time to resume from suspend kwesadilo Linux - Laptop and Netbook 5 07-26-2008 12:53 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:52 PM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration