You are not logged in.
Hi everybody! I have a problem when exit from suspend mode on my desktop. My cooler starts running very fast and don't stop after time. If I reboot it's running very quiet. How can I solve this problem? Any suggestions? Thanks.
Offline
Hey! Perhaps this is helping you: https://bugs.archlinux.org/task/32025
Offline
Hello pesh1983,
I believe that I am having the same problem.
before suspend:
cheap% sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +46.0°C (crit = +256.0°C)
temp2: +50.0°C (crit = +105.0°C)
temp3: +45.0°C (crit = +105.0°C)
temp4: +32.0°C (crit = +105.0°C)
temp5: +0.0°C (crit = +110.0°C)coretemp-isa-0000
Adapter: ISA adapter
Core 0: +55.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +55.0°C (high = +100.0°C, crit = +100.0°C)
After suspend:
cheap% sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +55.0°C (crit = +256.0°C)
temp2: +47.0°C (crit = +105.0°C)
temp3: +45.0°C (crit = +105.0°C)
temp4: +32.0°C (crit = +105.0°C)
temp5: +90.0°C (crit = +110.0°C)coretemp-isa-0000
Adapter: ISA adapter
Core 0: +51.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +52.0°C (high = +100.0°C, crit = +100.0°C)
I am confident that temp5 is not 90 degrees. After suspend my system fan runs non-stop. I edited /etc/sensors3.conf and added the lines to ignore temp5. Now sensors will not show output for temp5, but my fan still runs all the time after resume.
Offline
On most desktop motherboards, fans are controlled by SuperIO chip which is also connected to few temperature sensors deployed on the motherboard. Typical SuperIO can be configured to run each fan at constant speed or to vary its speed according to some temperature input, e.g. CPU fan can be controlled by thermal sensor installed under CPU socket.
This configuration is performed by BIOS during boot-up. OS's have little control over this part of SuperIO because it's often accessed concurrently by ACPI code (e.g. this ACPI temperature reader you have). This means that post-suspend restoration of fan settings needs to be performed by BIOS, before resuming the OS. However, BIOSes are the most buggy pieces of software ever seen on this planet, so ...
Your options are:
1. Try modprobe fan and see if there is some ACPI interface for controlling the fans manually. Probably there's none.
2. If the problem happens after hibernation (not sleep), try hibernating with echo shutdown >/sys/power/disk ; echo disk >/sys/power/state . This will run normal "shutdown" ACPI code after hibernating and will trick the BIOS to perform full power-on procedure when you turn the machine on again, including SuperIO configuration.
3. Update BIOS.
4. Complain to your motherboard's vendor
5. Boot with acpi_enforce_resources=lax and run sensors-detect to find out if there is a Linux driver for your SuperIO. This will give you manual control over SuperIO configuration at the cost of potential problems if ACPI code and linux driver ever decide to poke SuperIO registers at the same time.
Last edited by mich41 (2013-01-23 17:41:15)
Offline
mich41,
Thank you for your reply. I am still trying to fix this. It is interesting that this started the first time I boot to the 3.7.3 kernel. I suspect that this is caused by a change in software/config. I will try to roll back to my previous kernel when I get some time this evening to see if that will resolve the problem.
cheap% uname -a
Linux cheap 3.7.3-1-ARCH #1 SMP PREEMPT Thu Jan 17 18:52:30 CET 2013 x86_64 GNU/Linux
Offline
This is very frustrating. It would seem that this is a known bug with the 3.7.* kernels. So far there is no fix except to run an older kernel.
Offline
Known bug? Did you find a bug report or something? I'm not trying to say you're wrong, I a genuinely interested.
Offline
Did you find a bug report or something?
Yes, I found "something".
https://lkml.org/lkml/2012/12/19/166
Offline
Same problem here... Any news on this issue?
Linux arch 3.7.4-1-ARCH #1 SMP PREEMPT Mon Jan 21 23:05:29 CET 2013 x86_64 GNU/Linux
Last edited by GNRS (2013-01-28 18:14:26)
Offline
GNRS,
I Still have this problem with the latest kernel. However, I am able to use my laptop (HP tc4400) without this problem by using the LTS kernel provided through pacman.
# pacman -S linux-lts linux-lts-headers
To be able to boot the "new" old kernel, you will need to regenerate your grub.cfg file.
# cp /boot/grub/grub.cfg /boot/grub/grub.cfg.backup
# grub-mkconfig -o /boot/grub/grub.cfg
On my system this generated 4 boot enteries in grub. Two for the LTS kernel (default), and two for the original latest kernel.
My system is currently running the LTS kernel without any problems.
cheap% uname -a
Linux cheap 3.0.60-1-lts #1 SMP Mon Jan 21 22:58:04 CET 2013 x86_64 GNU/Linux
I hope this helps you and I hope this problem gets resolved soon.
Last edited by reasterling (2013-01-29 05:26:21)
Offline
I confirm the bug. I had this problem also with linux-lqx since 3.7.1 and now with the core kernel, so I am sure this is a regression on 3.7.* kernel. However if not suspended the kernel is usable as well.
Offline
Is the any solution in this case. My fan running very fast after hibernation.
My option is to hibernate with
echo shutdown >/sys/power/disk ; echo disk >/sys/power/state
but i can do it temporarily.
Is it any way to put this script in /usr/lib/pm-utils/module.d/hibernate?
Offline
What graphics hardware are you using? I was experiencing this with my nVidia GPU. The fix in this post is specific to nVidia hardware and the nouveau driver.
I recently bisected nouveau git master upon realizing fan control is busted with newer kernels (3.3+) and could no longer control my GTX 260 (nv50 gpu) fan. When resuming from suspend, the fan would run at full speed. Loud and unnecessary!
Here's my bug report and patch: https://bugs.freedesktop.org/show_bug.cgi?id=60704
Note: due to restructuring of the nouveau driver in recent kernels there are separate patches for 3.4.x series and 3.7.x. I applied against 3.4.30 and can confirm it resolves the problem. I've ported the patch for upstream stable 3.7.x and git master 3.8-rc7. After building all 3 aforementioned kernels patched, sensors detect my fan controller successfully. Peace and quiet has been restored!
I am hoping to see this merged into stable!
Offline
My graphic is Radeon X2300.
I am not sure what kind of patch I have to use (seek).
Offline
I have nVidia GTX275 and I used nuveau-dri since ten months ago. I didn't have this issue with 3.6.* kernel. I will try to downgrade kernel so to confirm this.
Offline
Hi guys, I have same symptoms, but my graphics is an integrated intel.
Offline
Same bug as 32025. Same as https://bbs.archlinux.org/viewtopic.php?id=158465
Basically, the bug report has a fix. Use lts kernel or manually install kernel 3.8+
Last edited by frank604 (2013-03-01 02:20:04)
Offline
Hello,
I have the same problem on my HP ProBook 5310m laptop. I run the following after resume from suspend to fix the fan speed:
for i in {1..15}; do echo 0 > /sys/class/thermal/cooling_device$i/cur_state; done
echo 1 > /sys/class/thermal/cooling_device15/cur_state
If you have a different machine, you may need to change which cooling_devices you tinker with. Check the correct values after a reboot when the fan is running at the correct speed.
Offline
Same bug as 32025. Same as https://bbs.archlinux.org/viewtopic.php?id=158465
Basically, the bug report has a fix. Use lts kernel or manually install kernel 3.8+
Lts kernel is OK and for me this is just a trick, it is not a fix. The bug is still present on 3.8.+ (from testing at moment) kernel. My hardware as wrote before is GTX275 with nouveau.
Last edited by Yagi858 (2013-03-12 10:39:57)
Offline
Having this problem aswell with 3.8.3 from stable, will try the echo fix and see if it works for me.
Offline
I just started having this problem after upgrading to 3.8.3-2 from 3.7.10. Of course, I didn't suspend for some time after I upgrade so I already cleared my cache. Hope someone finds a fix. I'm seeing this pop up in dmesg, but I don't know if it's related or if it was there before
$ dmesg | grep Warning
[ 6.270643] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20121018/utaddress-251)
[ 6.270650] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \_SB_.PCI0.LPCB.PMBS 2 (20121018/utaddress-251)
[ 6.270658] ACPI Warning: 0x0000000000000740-0x000000000000074f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 6.270662] ACPI Warning: 0x0000000000000730-0x000000000000073f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 6.270665] ACPI Warning: 0x0000000000000730-0x000000000000073f SystemIO conflicts with Region \_SB_.PCI0.LPCB.GPIO 2 (20121018/utaddress-251)
[ 6.270669] ACPI Warning: 0x0000000000000700-0x000000000000072f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 6.270674] ACPI Warning: 0x0000000000000700-0x000000000000072f SystemIO conflicts with Region \_SB_.PCI0.LPCB.GPIO 2 (20121018/utaddress-251)
[ 6.549609] ACPI Warning: 0x0000000000004040-0x000000000000405f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20121018/utaddress-251)
Offline
Are you booting with acpi_enforce_resources set to 'no' or 'lax'? What's printed immediately before and after these warnings?
What modules are loaded?
Offline
Here's a more complete output. For what it's worth, the reported behavior stopped on my machine once I removed laptop-mode-tools. I replaced it with powerdown, but i don't think that's relevant.
$ dmesg | grep -A 5 -B 5 Warning
[ 6.177445] ACPI: Power Button [PWRF]
[ 6.178998] thermal LNXTHERM:00: registered as thermal_zone0
[ 6.179001] ACPI: Thermal Zone [TZ00] (33 C)
[ 6.179633] thermal LNXTHERM:01: registered as thermal_zone1
[ 6.179636] ACPI: Thermal Zone [TZ01] (0 C)
[ 6.215316] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20121018/utaddress-251)
[ 6.215324] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \_SB_.PCI0.LPCB.PMBS 2 (20121018/utaddress-251)
[ 6.215327] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 6.215331] ACPI Warning: 0x0000000000000740-0x000000000000074f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 6.215334] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 6.215336] ACPI Warning: 0x0000000000000730-0x000000000000073f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 6.215339] ACPI Warning: 0x0000000000000730-0x000000000000073f SystemIO conflicts with Region \_SB_.PCI0.LPCB.GPIO 2 (20121018/utaddress-251)
[ 6.215341] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 6.215343] ACPI Warning: 0x0000000000000700-0x000000000000072f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 6.215345] ACPI Warning: 0x0000000000000700-0x000000000000072f SystemIO conflicts with Region \_SB_.PCI0.LPCB.GPIO 2 (20121018/utaddress-251)
[ 6.215348] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 6.215349] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 6.285009] ACPI: AC Adapter [AC] (off-line)
[ 6.286120] cfg80211: Calling CRDA to update world regulatory domain
[ 6.341485] atl1c 0000:08:00.0: version 1.0.1.1-NAPI
[ 6.389512] wmi: Mapper loaded
[ 6.540828] ACPI: Requesting acpi_cpufreq
[ 6.582939] ACPI Warning: 0x0000000000004040-0x000000000000405f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20121018/utaddress-251)
[ 6.582946] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 6.621268] lib80211: common routines for IEEE802.11 drivers
[ 6.621271] lib80211_crypt: registered algorithm 'NULL'
[ 6.680311] mei 0000:00:16.0: setting latency timer to 64
[ 6.680386] mei 0000:00:16.0: irq 41 for MSI/MSI-X
Again, not sure if this will help solve anything. I no longer have the fan control problem and am still getting these warnings.
here's lsmod
Module Size Used by
msr 2704 0
cpufreq_stats 3826 0
michael_mic 2074 4
arc4 2007 2
ecb 2105 0
cpufreq_powersave 1278 4
snd_hda_codec_hdmi 27848 1
snd_hda_codec_idt 55567 1
joydev 9727 0
coretemp 6198 0
kvm 392222 0
crc32c_intel 14313 0
lib80211_crypt_tkip 9082 0
acpi_cpufreq 10630 1
mperf 1267 1 acpi_cpufreq
ghash_clmulni_intel 4597 0
cryptd 8741 1 ghash_clmulni_intel
hp_accel 16520 0
lis3lv02d 11603 1 hp_accel
hp_wmi 8058 0
snd_hda_intel 34194 0
i915 558806 2
snd_hda_codec 102453 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
wl 2557001 0
intel_agp 10872 1 i915
intel_gtt 12566 2 i915,intel_agp
snd_hwdep 6428 1 snd_hda_codec
snd_pcm 78146 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
drm_kms_helper 35517 1 i915
snd_page_alloc 7426 2 snd_pcm,snd_hda_intel
snd_timer 18934 1 snd_pcm
drm 226103 3 i915,drm_kms_helper
snd 60156 7 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_idt,snd_pcm,snd_hda_codec,snd_hda_intel
i2c_algo_bit 5391 1 i915
iTCO_wdt 5447 0
soundcore 5442 1 snd
iTCO_vendor_support 1929 1 iTCO_wdt
microcode 14465 0
psmouse 76175 0
mei 59991 0
lib80211 3949 2 wl,lib80211_crypt_tkip
i2c_i801 11077 0
i2c_core 23171 5 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit
evdev 10136 11
input_polldev 2914 1 lis3lv02d
sparse_keymap 3088 1 hp_wmi
processor 27431 1 acpi_cpufreq
serio_raw 5105 0
wmi 8379 1 hp_wmi
atl1c 36302 0
ac 2568 0
cfg80211 433688 1 wl
lpc_ich 11601 0
thermal 8577 0
video 11363 1 i915
button 4701 1 i915
battery 7098 0
fan 2785 0
rfkill 15996 3 cfg80211,hp_wmi
ext4 478274 3
crc16 1359 1 ext4
jbd2 77917 1 ext4
mbcache 6026 1 ext4
sr_mod 14823 0
cdrom 35520 1 sr_mod
sd_mod 31258 4
ahci 22160 3
libahci 20906 1 ahci
libata 168683 2 ahci,libahci
ehci_pci 4120 0
ehci_hcd 47423 1 ehci_pci
sdhci_pci 11412 0
sdhci 28375 1 sdhci_pci
scsi_mod 130797 3 libata,sd_mod,sr_mod
mmc_core 91956 2 sdhci,sdhci_pci
usbcore 175061 2 ehci_hcd,ehci_pci
usb_common 954 1 usbcore
and kernel parameter
GRUB_CMDLINE_LINUX_DEFAULT="quiet nmi_watchdog=0"
Offline
These warnings indicate that some driver wanted to access some device which is already controlled by ACPI.
They are harmless, but if you were booting with acpi_enforce_resources disabled they would get ignored and the conflicting driver would get enabled anyway.
Offline
Hello,
I have the same problem on my HP ProBook 5310m laptop. I run the following after resume from suspend to fix the fan speed:
for i in {1..15}; do echo 0 > /sys/class/thermal/cooling_device$i/cur_state; done echo 1 > /sys/class/thermal/cooling_device15/cur_state
If you have a different machine, you may need to change which cooling_devices you tinker with. Check the correct values after a reboot when the fan is running at the correct speed.
That really helps!
Before suspend I have
mininote ~ % for i in {0..9};do echo "/sys/class/thermal/cooling_device$i"; cat /sys/class/thermal/cooling_device$i/cur_state; done
/sys/class/thermal/cooling_device0
0
/sys/class/thermal/cooling_device1
0
/sys/class/thermal/cooling_device2
0
/sys/class/thermal/cooling_device3
0
/sys/class/thermal/cooling_device4
0
/sys/class/thermal/cooling_device5
0
/sys/class/thermal/cooling_device6
1
/sys/class/thermal/cooling_device7
0
/sys/class/thermal/cooling_device8
0
/sys/class/thermal/cooling_device9
0
After resume from suspend:
mininote ~ % for i in {0..9};do echo "/sys/class/thermal/cooling_device$i"; cat /sys/class/thermal/cooling_device$i/cur_state; done
/sys/class/thermal/cooling_device0
1
/sys/class/thermal/cooling_device1
1
/sys/class/thermal/cooling_device2
1
/sys/class/thermal/cooling_device3
1
/sys/class/thermal/cooling_device4
1
/sys/class/thermal/cooling_device5
0
/sys/class/thermal/cooling_device6
1
/sys/class/thermal/cooling_device7
0
/sys/class/thermal/cooling_device8
0
/sys/class/thermal/cooling_device9
0
Here are events on suspend:
апр 03 00:08:02 mininote systemd-logind[263]: Lid closed.
апр 03 00:08:02 mininote systemd-logind[263]: Suspending...
апр 03 00:08:02 mininote systemd[1]: Starting Sleep.
апр 03 00:08:02 mininote systemd[1]: Reached target Sleep.
апр 03 00:08:02 mininote systemd[1]: Starting Suspend...
апр 03 00:08:02 mininote systemd-sleep[1655]: Suspending system...
апр 03 00:08:03 mininote kernel: PM: Syncing filesystems ... done.
апр 03 00:08:03 mininote kernel: PM: Preparing system for mem sleep
апр 03 00:08:16 mininote kernel: Freezing user space processes ... (elapsed 0.01 seconds) done.
апр 03 00:08:16 mininote systemd[1]: Time has been changed
апр 03 00:08:16 mininote systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
After resume from suspend:
апр 03 00:08:16 mininote systemd-logind[263]: Lid opened.
апр 03 00:08:16 mininote kernel: Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
апр 03 00:08:16 mininote kernel: PM: Entering mem sleep
апр 03 00:08:16 mininote kernel: Suspending console(s) (use no_console_suspend to debug)
апр 03 00:08:16 mininote kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
апр 03 00:08:16 mininote kernel: sd 0:0:0:0: [sda] Stopping disk
апр 03 00:08:16 mininote kernel: e1000e 0000:00:19.0: System wakeup enabled by ACPI
апр 03 00:08:16 mininote kernel: snd_hda_intel 0000:00:1b.0: power state changed by ACPI to D3hot
апр 03 00:08:16 mininote kernel: ACPI: Cannot transition to non-D0 state from D3
апр 03 00:08:16 mininote kernel: PM: suspend of devices complete after 564.432 msecs
апр 03 00:08:16 mininote kernel: PM: late suspend of devices complete after 0.488 msecs
апр 03 00:08:16 mininote kernel: ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1d.2: System wakeup enabled by ACPI
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI
апр 03 00:08:16 mininote kernel: ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1a.1: System wakeup enabled by ACPI
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1a.0: System wakeup enabled by ACPI
апр 03 00:08:16 mininote kernel: PM: noirq suspend of devices complete after 38.190 msecs
апр 03 00:08:16 mininote kernel: ACPI: Preparing to enter system sleep state S3
апр 03 00:08:16 mininote kernel: PM: Saving platform NVS memory
апр 03 00:08:16 mininote kernel: Disabling non-boot CPUs ...
апр 03 00:08:16 mininote kernel: smpboot: CPU 1 is now offline
апр 03 00:08:16 mininote kernel: Extended CMOS year: 2000
апр 03 00:08:16 mininote kernel: ACPI: Low-level resume complete
апр 03 00:08:16 mininote kernel: PM: Restoring platform NVS memory
апр 03 00:08:16 mininote kernel: Extended CMOS year: 2000
апр 03 00:08:16 mininote kernel: CPU0: Thermal monitoring handled by SMI
апр 03 00:08:16 mininote kernel: Enabling non-boot CPUs ...
апр 03 00:08:16 mininote kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
апр 03 00:08:16 mininote kernel: Initializing CPU#1
апр 03 00:08:16 mininote kernel: CPU1: Thermal monitoring handled by SMI
апр 03 00:08:16 mininote kernel: CPU1 is up
апр 03 00:08:16 mininote kernel: ACPI: Waking up from system sleep state S3
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1a.0: System wakeup disabled by ACPI
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1a.1: System wakeup disabled by ACPI
апр 03 00:08:16 mininote kernel: ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI
апр 03 00:08:16 mininote kernel: snd_hda_intel 0000:00:1b.0: power state changed by ACPI to D0
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI
апр 03 00:08:16 mininote kernel: ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI
апр 03 00:08:16 mininote kernel: PM: noirq resume of devices complete after 121.565 msecs
апр 03 00:08:16 mininote kernel: PM: early resume of devices complete after 0.381 msecs
апр 03 00:08:16 mininote kernel: i915 0000:00:02.0: setting latency timer to 64
апр 03 00:08:16 mininote kernel: ata_generic 0000:00:03.2: setting latency timer to 64
апр 03 00:08:16 mininote kernel: e1000e 0000:00:19.0: System wakeup disabled by ACPI
апр 03 00:08:16 mininote kernel: e1000e 0000:00:19.0: irq 42 for MSI/MSI-X
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1a.0: setting latency timer to 64
апр 03 00:08:16 mininote kernel: usb usb2: root hub lost power or was reset
апр 03 00:08:16 mininote systemd-sleep[1655]: System resumed.
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1a.1: setting latency timer to 64
апр 03 00:08:16 mininote kernel: usb usb3: root hub lost power or was reset
апр 03 00:08:16 mininote kernel: ehci-pci 0000:00:1a.7: setting latency timer to 64
апр 03 00:08:16 mininote kernel: snd_hda_intel 0000:00:1b.0: irq 43 for MSI/MSI-X
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
апр 03 00:08:16 mininote kernel: usb usb4: root hub lost power or was reset
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
апр 03 00:08:16 mininote kernel: usb usb5: root hub lost power or was reset
апр 03 00:08:16 mininote kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
апр 03 00:08:16 mininote kernel: usb usb6: root hub lost power or was reset
апр 03 00:08:16 mininote kernel: ehci-pci 0000:00:1d.7: setting latency timer to 64
апр 03 00:08:16 mininote kernel: pci 0000:00:1e.0: setting latency timer to 64
апр 03 00:08:16 mininote kernel: ata_piix 0000:00:1f.1: setting latency timer to 64
апр 03 00:08:16 mininote kernel: ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000000000005) is beyond end of object (20121018/exoparg2-418)
апр 03 00:08:16 mininote kernel: ACPI Error: Method parse/execution failed [\_SB_.C2C3] (Node f5c32a38), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
апр 03 00:08:16 mininote kernel: ACPI Error: Method parse/execution failed [\_SB_.C003.C0F6.C3F3._STM] (Node f5c36dc8), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
апр 03 00:08:16 mininote kernel: ata1: ACPI set timing mode failed (status=0x300b)
апр 03 00:08:16 mininote kernel: ata2: port disabled--ignoring
апр 03 00:08:16 mininote kernel: psmouse serio1: hgpk: ID: 10 00 64
апр 03 00:08:16 mininote kernel: ata1.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
апр 03 00:08:16 mininote kernel: ata1.01: ACPI cmd ef/03:40:00:00:00:b0 (SET FEATURES) filtered out
апр 03 00:08:16 mininote kernel: ata1.00: ACPI cmd ef/03:01:00:00:00:a0 (SET FEATURES) filtered out
апр 03 00:08:16 mininote kernel: ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
апр 03 00:08:16 mininote kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
апр 03 00:08:16 mininote kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
апр 03 00:08:16 mininote kernel: ata1.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
апр 03 00:08:16 mininote kernel: ata1.00: configured for UDMA/100
апр 03 00:08:16 mininote kernel: ata1.01: configured for MWDMA2
апр 03 00:08:16 mininote kernel: sd 0:0:0:0: [sda] Starting disk
апр 03 00:08:16 mininote kernel: PM: resume of devices complete after 2786.068 msecs
апр 03 00:08:16 mininote kernel: PM: Finishing wakeup.
апр 03 00:08:16 mininote kernel: Restarting tasks ... done.
апр 03 00:08:16 mininote kernel: video LNXVIDEO:00: Restoring backlight state
апр 03 00:08:16 mininote systemd[1]: Started Suspend.
апр 03 00:08:16 mininote systemd[1]: Service sleep.target is not needed anymore. Stopping.
апр 03 00:08:16 mininote systemd[1]: Stopping Sleep.
апр 03 00:08:16 mininote systemd[1]: Stopped target Sleep.
апр 03 00:08:16 mininote systemd[1]: Starting Suspend.
апр 03 00:08:16 mininote systemd[1]: Reached target Suspend.
апр 03 00:08:16 mininote systemd-logind[263]: Operation finished.
Offline