Форум русскоязычного сообщества Ubuntu


За новостями русскоязычного сообщества и Ubuntu в целом можно следить на нашей страничке в Google+

Автор Тема: Ubuntu 14.04 - не работает ждущий режим.  (Прочитано 987 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн AlLie

  • Автор темы
  • Новичок
  • *
  • Сообщений: 7
    • Просмотр профиля
День добрый. После обновления до версии 14.04 перестал работать ждущий режим по команде Suspend. Система гаснет, но питание на устройства подается: крутятся вентиляторы, диск, светится светодиод. Если выключать комп - "Poweroff", все выключается, но при следующем включении загрузка начинается с сообщений о системных ошибках, каких именно не написано. До обновления, в версии 13.10, все работало нормально. Может какие настройки нужно сделать ?

Оффлайн ivanich352012

  • Участник
  • *
  • Сообщений: 141
    • Просмотр профиля
Re: Ubuntu 14.04 - не работает ждущий режим.
« Ответ #1 : 08 Июнь 2014, 15:19:35 »
Я спрашивал, мне не ответили https://forum.ubuntu.ru/index.php?topic=244839.msg1932203#msg1932203

Оффлайн hon

  • Старожил
  • *
  • Сообщений: 1044
  • Ubuntu 12.04 LTS
    • Просмотр профиля
Re: Ubuntu 14.04 - не работает ждущий режим.
« Ответ #2 : 08 Июнь 2014, 16:44:47 »
Перейди в ждущий режим, потом вернись, открой терминал, выполни команды:
dmesg | tail -n 100
cat /var/log/syslog | tail -n 100
Скопируй вывод и вставь сюда.

Оффлайн AlLie

  • Автор темы
  • Новичок
  • *
  • Сообщений: 7
    • Просмотр профиля
Re: Ubuntu 14.04 - не работает ждущий режим.
« Ответ #3 : 08 Июнь 2014, 18:55:20 »
Вот интересный факт: для выполнения рекомендаций от hon, перешел в ждущий режим, на удивление операция завершилась успешно, комп уснул полностью. Включился тоже нормально. Выполнил команды. После решил повторить попытку перехода в ждущий режим, итог печальный. Монитор потух, система выключилась, но питание шло, как и прежде. Просыпать не хотел. Пришлось насильно выключать. Ниже результат выполнения команд в первом и втором случае.

1. После успешного перехода в ждущий режим

dmesg | tail -n 100

[30468.380333] ---[ end trace 9e3dfc944c44bdab ]---
[30468.380366] CPU1 is up
[30468.380687] ACPI: Waking up from system sleep state S3
[30468.396037] ohci-pci 0000:00:02.0: System wakeup disabled by ACPI
[30468.412049] ehci-pci 0000:00:02.1: System wakeup disabled by ACPI
[30468.412100] pci 0000:00:00.0: Found enabled HT MSI Mapping
[30468.428072] pci 0000:00:00.0: Found enabled HT MSI Mapping
[30468.460076] pci 0000:00:00.0: Found enabled HT MSI Mapping
[30468.476073] pci 0000:00:00.0: Found enabled HT MSI Mapping
[30468.492073] pci 0000:00:00.0: Found enabled HT MSI Mapping
[30468.492143] pci 0000:00:00.0: Found enabled HT MSI Mapping
[30468.524161] PM: noirq resume of devices complete after 143.287 msecs
[30468.524333] PM: early resume of devices complete after 0.133 msecs
[30468.524545] forcedeth 0000:00:07.0: System wakeup disabled by ACPI
[30468.525928] serial 00:07: activated
[30468.526360] serial 00:08: activated
[30468.526774] parport_pc 00:09: activated
[30468.527153] snd_hda_intel 0000:02:00.1: irq 42 for MSI/MSI-X
[30468.528268] ata2: port disabled--ignoring
[30468.624354] [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000).
[30468.624428] radeon 0000:02:00.0: WB enabled
[30468.624430] radeon 0000:02:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8800d8bf2c00
[30468.624432] radeon 0000:02:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8800d8bf2c0c
[30468.625169] radeon 0000:02:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0xffffc90002f1c418
[30468.641142] [drm] ring test on 0 succeeded in 1 usecs
[30468.641198] [drm] ring test on 3 succeeded in 1 usecs
[30468.692310] ata1.00: ACPI cmd ef/03:44:00:00:00:a0 (SET FEATURES) filtered out
[30468.692312] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[30468.692321] ata1: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc5000000) ACPI=0x1f01f (30:600:0x13)
[30468.708245] ata1.00: configured for UDMA/66
[30468.846728] [drm] ring test on 5 succeeded in 1 usecs
[30468.846731] [drm] UVD initialized successfully.
[30468.846732] [drm] Enabling audio 0 support
[30468.846775] [drm] ib test on ring 0 succeeded in 0 usecs
[30468.846774] HDMI ATI/AMD: no speaker allocation for ELD
[30468.846803] [drm] ib test on ring 3 succeeded in 1 usecs
[30468.996039] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[30469.004108] ata4.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out
[30469.016923] [drm] ib test on ring 5 succeeded
[30469.020239] ata4.00: configured for UDMA/133
[30469.020300] sd 4:0:0:0: [sda] Starting disk
[30469.144027] HDMI ATI/AMD: no speaker allocation for ELD
[30469.262237] ata5: SATA link down (SStatus 0 SControl 300)
[30469.262239] ata3: SATA link down (SStatus 0 SControl 300)
[30469.352075] psmouse serio1: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64
[30469.444031] HDMI ATI/AMD: no speaker allocation for ELD
[30469.744026] HDMI ATI/AMD: no speaker allocation for ELD
[30470.044027] HDMI ATI/AMD: no speaker allocation for ELD
[30470.344028] HDMI ATI/AMD: no speaker allocation for ELD
[30470.644026] HDMI ATI/AMD: no speaker allocation for ELD
[30470.944027] HDMI ATI/AMD: no speaker allocation for ELD
[30471.124043] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[30471.132122] ata6.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out
[30471.172844] ata6.00: configured for UDMA/133
[30471.172905] sd 6:0:0:0: [sdd] Starting disk
[30471.181482] PM: resume of devices complete after 2657.146 msecs
[30471.181852] PM: Finishing wakeup.
[30471.181901] pci 0000:00:04.0: PCI bridge to [bus 01]
[30471.181908] pci 0000:00:04.0:   bridge window [io  0xb000-0xbfff]
[30471.181912] pci 0000:00:04.0:   bridge window [mem 0xfbe00000-0xfbefffff]
[30471.181915] pci 0000:00:04.0:   bridge window [mem 0xfbd00000-0xfbdfffff pref]
[30471.181931] pci 0000:00:00.0: no hotplug settings from platform
[30471.181933] pci 0000:00:00.0: using default PCI settings
[30471.181943] pci 0000:00:01.0: no hotplug settings from platform
[30471.181945] pci 0000:00:01.0: using default PCI settings
[30471.181951] nForce2_smbus 0000:00:01.1: no hotplug settings from platform
[30471.181952] nForce2_smbus 0000:00:01.1: using default PCI settings
[30471.181958] pci 0000:00:01.2: no hotplug settings from platform
[30471.181959] pci 0000:00:01.2: using default PCI settings
[30471.181965] ohci-pci 0000:00:02.0: no hotplug settings from platform
[30471.181967] ohci-pci 0000:00:02.0: using default PCI settings
[30471.181972] ehci-pci 0000:00:02.1: no hotplug settings from platform
[30471.181974] ehci-pci 0000:00:02.1: using default PCI settings
[30471.181979] pci 0000:00:04.0: no hotplug settings from platform
[30471.181980] pci 0000:00:04.0: using default PCI settings
[30471.181987] snd_hda_intel 0000:00:05.0: no hotplug settings from platform
[30471.181989] snd_hda_intel 0000:00:05.0: using default PCI settings
[30471.181994] pata_amd 0000:00:06.0: no hotplug settings from platform
[30471.181996] pata_amd 0000:00:06.0: using default PCI settings
[30471.182001] forcedeth 0000:00:07.0: no hotplug settings from platform
[30471.182003] forcedeth 0000:00:07.0: using default PCI settings
[30471.183203] sata_nv 0000:00:08.0: no hotplug settings from platform
[30471.183210] sata_nv 0000:00:08.0: using default PCI settings
[30471.183218] sata_nv 0000:00:08.1: no hotplug settings from platform
[30471.183219] sata_nv 0000:00:08.1: using default PCI settings
[30471.183224] pcieport 0000:00:09.0: no hotplug settings from platform
[30471.183233] radeon 0000:02:00.0: no hotplug settings from platform
[30471.183240] snd_hda_intel 0000:02:00.1: no hotplug settings from platform
[30471.183243] pci 0000:00:18.0: no hotplug settings from platform
[30471.183245] pci 0000:00:18.0: using default PCI settings
[30471.183249] pci 0000:00:18.1: no hotplug settings from platform
[30471.183251] pci 0000:00:18.1: using default PCI settings
[30471.183255] pci 0000:00:18.2: no hotplug settings from platform
[30471.183257] pci 0000:00:18.2: using default PCI settings
[30471.183261] k8temp 0000:00:18.3: no hotplug settings from platform
[30471.183263] k8temp 0000:00:18.3: using default PCI settings
[30471.181854] Restarting tasks ... done.
[30471.244051] HDMI ATI/AMD: no speaker allocation for ELD
[30471.642748] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
[30471.642788] forcedeth 0000:00:07.0 eth0: MSI enabled


cat /var/log/syslog | tail -n 100

Jun  8 18:28:38 Vitaly-PC kernel: [30471.181994] pata_amd 0000:00:06.0: no hotplug settings from platform
Jun  8 18:28:38 Vitaly-PC kernel: [30471.181996] pata_amd 0000:00:06.0: using default PCI settings
Jun  8 18:28:38 Vitaly-PC kernel: [30471.182001] forcedeth 0000:00:07.0: no hotplug settings from platform
Jun  8 18:28:38 Vitaly-PC kernel: [30471.182003] forcedeth 0000:00:07.0: using default PCI settings
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183203] sata_nv 0000:00:08.0: no hotplug settings from platform
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183210] sata_nv 0000:00:08.0: using default PCI settings
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183218] sata_nv 0000:00:08.1: no hotplug settings from platform
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183219] sata_nv 0000:00:08.1: using default PCI settings
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183224] pcieport 0000:00:09.0: no hotplug settings from platform
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183233] radeon 0000:02:00.0: no hotplug settings from platform
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183240] snd_hda_intel 0000:02:00.1: no hotplug settings from platform
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183243] pci 0000:00:18.0: no hotplug settings from platform
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183245] pci 0000:00:18.0: using default PCI settings
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183249] pci 0000:00:18.1: no hotplug settings from platform
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183251] pci 0000:00:18.1: using default PCI settings
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183255] pci 0000:00:18.2: no hotplug settings from platform
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183257] pci 0000:00:18.2: using default PCI settings
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183261] k8temp 0000:00:18.3: no hotplug settings from platform
Jun  8 18:28:38 Vitaly-PC kernel: [30471.183263] k8temp 0000:00:18.3: using default PCI settings
Jun  8 18:28:38 Vitaly-PC kernel: [30471.181854] Restarting tasks ... done.
Jun  8 18:28:38 Vitaly-PC kernel: [30471.244051] HDMI ATI/AMD: no speaker allocation for ELD
Jun  8 18:28:38 Vitaly-PC anacron[4736]: Anacron 2.3 started on 2014-06-08
Jun  8 18:28:38 Vitaly-PC anacron[4736]: Normal exit (0 jobs run)
Jun  8 18:28:38 Vitaly-PC anacron[4791]: Anacron 2.3 started on 2014-06-08
Jun  8 18:28:38 Vitaly-PC anacron[4791]: Normal exit (0 jobs run)
Jun  8 18:28:38 Vitaly-PC kernel: [30471.642748] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
Jun  8 18:28:38 Vitaly-PC kernel: [30471.642788] forcedeth 0000:00:07.0 eth0: MSI enabled
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> wake requested (sleeping: yes  enabled: yes)
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> waking up and re-enabling...
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> WWAN now enabled by management service
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> (eth0): bringing up device.
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> (eth0): carrier now ON (device state 20)
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> (eth0): preparing device.
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> (eth0): deactivating device (reason 'managed') [2]
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> NetworkManager state is now DISCONNECTED
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> (eth0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Auto-activating connection 'Wired connection 1'.
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) starting connection 'Wired connection 1'
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> NetworkManager state is now CONNECTING
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> dhclient started with pid 4862
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jun  8 18:28:38 Vitaly-PC dhclient: Internet Systems Consortium DHCP Client 4.2.4
Jun  8 18:28:38 Vitaly-PC dhclient: Copyright 2004-2012 Internet Systems Consortium.
Jun  8 18:28:38 Vitaly-PC dhclient: All rights reserved.
Jun  8 18:28:38 Vitaly-PC dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun  8 18:28:38 Vitaly-PC dhclient:
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Jun  8 18:28:38 Vitaly-PC dhclient: Listening on LPF/eth0/00:1a:4d:9e:2d:74
Jun  8 18:28:38 Vitaly-PC dhclient: Sending on   LPF/eth0/00:1a:4d:9e:2d:74
Jun  8 18:28:38 Vitaly-PC dhclient: Sending on   Socket/fallback
Jun  8 18:28:38 Vitaly-PC dhclient: DHCPREQUEST of 192.168.27.75 on eth0 to 255.255.255.255 port 67 (xid=0xfed28e5)
Jun  8 18:28:38 Vitaly-PC dhclient: DHCPACK of 192.168.27.75 from 192.168.27.111
Jun  8 18:28:38 Vitaly-PC dhclient: bound to 192.168.27.75 -- renewal in 20154 seconds.
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> (eth0): DHCPv4 state changed preinit -> reboot
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info>   address 192.168.27.75
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info>   prefix 24 (255.255.255.0)
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info>   gateway 192.168.27.111
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info>   hostname 'Vitaly-PC'
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info>   nameserver '192.168.27.111'
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Jun  8 18:28:38 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
Jun  8 18:28:38 Vitaly-PC avahi-daemon[4324]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.27.75.
Jun  8 18:28:38 Vitaly-PC avahi-daemon[4324]: New relevant interface eth0.IPv4 for mDNS.
Jun  8 18:28:38 Vitaly-PC avahi-daemon[4324]: Registering new address record for 192.168.27.75 on eth0.IPv4.
Jun  8 18:28:39 Vitaly-PC NetworkManager[744]: <info> (eth0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Jun  8 18:28:39 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
Jun  8 18:28:39 Vitaly-PC NetworkManager[744]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Jun  8 18:28:39 Vitaly-PC NetworkManager[744]: <info> NetworkManager state is now CONNECTED_GLOBAL
Jun  8 18:28:39 Vitaly-PC NetworkManager[744]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
Jun  8 18:28:39 Vitaly-PC NetworkManager[744]: <info> Writing DNS information to /sbin/resolvconf
Jun  8 18:28:39 Vitaly-PC dnsmasq[1064]: setting upstream servers from DBus
Jun  8 18:28:39 Vitaly-PC dnsmasq[1064]: using nameserver 192.168.27.111#53
Jun  8 18:28:40 Vitaly-PC avahi-daemon[4324]: Got SIGTERM, quitting.
Jun  8 18:28:40 Vitaly-PC avahi-daemon[4324]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.27.75.
Jun  8 18:28:40 Vitaly-PC avahi-daemon[4324]: avahi-daemon 0.6.31 exiting.
Jun  8 18:28:40 Vitaly-PC avahi: Avahi detected that your currently configured local DNS server serves
Jun  8 18:28:40 Vitaly-PC avahi: a domain .local. This is inherently incompatible with Avahi and thus
Jun  8 18:28:40 Vitaly-PC avahi: Avahi disabled itself. If you want to use Avahi in this network, please
Jun  8 18:28:40 Vitaly-PC avahi: contact your administrator and convince him to use a different DNS domain,
Jun  8 18:28:40 Vitaly-PC avahi: since .local should be used exclusively for Zeroconf technology.
Jun  8 18:28:40 Vitaly-PC avahi: For more information, see http://avahi.org/wiki/AvahiAndUnicastDotLocal
Jun  8 18:28:40 Vitaly-PC NetworkManager[744]: <info> Activation (eth0) successful, device activated.
Jun  8 18:28:40 Vitaly-PC whoopsie[1167]: message repeated 4 times: [ offline]
Jun  8 18:28:40 Vitaly-PC whoopsie[1167]: online
Jun  8 18:28:44 Vitaly-PC ntpdate[4972]: step time server 91.189.89.199 offset -2.044488 sec
Jun  8 18:29:02 Vitaly-PC dbus[656]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out




Пользователь решил продолжить мысль 08 Июнь 2014, 19:07:59:
Вторую часть добавить не получилось из-за :
Следующие ошибки возникли при попытке отправки сообщения:
Сообщение превышает максимально допустимую длину (30000 знаков).

Предлагаю вторую часть во вложении:

2. Незавершенный переход в ждущий режим
« Последнее редактирование: 08 Июнь 2014, 19:08:00 от AlLie »

 

Страница сгенерирована за 0.062 секунд. Запросов: 24.