You are not logged in.
Anyone has experience with something like that?:
I have a Toshiba Portégé Z30. Yesterday when I finished my work with it, it had about 20% = 2 hours battery left (That's a little less than usually).
As usually, I closed the lid in order to suspend the laptop. About 2 hours later I was at home and connected the suspended Laptop to AC power. As usually.
This morning (6:30), I was not able to switch it on. Opening the lid resulted in: nothing. Pressing the power button: nothing.
Only the power and wlan LED were flashing about every 4s. (I've never seen them doing that before)
When I hold the power button a long time, that LED flashing stopped as long as I pressed the power button.
I really thought my device has crashed and I only took it with my to exchange it on guaranty.
But, some hours later, without me doing anything, it started normally. With lid closed, it was still in my case!
So - as I said - has anyone experience with situations like that?
What could have caused that issue?
How can I avoid it of happening again?
Is there a way to get the machine starting again sooner if it happens again?
Here's my journalctl around that time:
Dez 09 15:20:33 portz30 logger[5808]: ACPI action undefined: PNP0C0A:00
Dez 09 15:20:33 portz30 systemd-logind[255]: Lid closed.
Dez 09 15:20:33 portz30 kernel: i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
Dez 09 15:20:33 portz30 NetworkManager[248]: <info> sleep requested (sleeping: no enabled: yes)
Dez 09 15:20:33 portz30 NetworkManager[248]: <info> sleeping...
Dez 09 15:20:33 portz30 NetworkManager[248]: <info> (wlp2s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Dez 09 15:20:33 portz30 NetworkManager[248]: <info> (wlp2s0): deactivating device (reason 'sleeping') [37]
Dez 09 15:20:33 portz30 dhcpcd[19910]: received signal TERM from PID 248, stopping
Dez 09 15:20:33 portz30 dhcpcd[19910]: wlp2s0: removing interface
Dez 09 15:20:33 portz30 NetworkManager[248]: dhcpcd[19910]: received signal TERM from PID 248, stopping
Dez 09 15:20:33 portz30 NetworkManager[248]: dhcpcd[19910]: wlp2s0: removing interface
Dez 09 15:20:33 portz30 logger[5812]: LID closed
Dez 09 15:20:33 portz30 NetworkManager[248]: <warn> (wlp2s0): DHCP client pid 19910 didn't exit, will kill it.
Dez 09 15:20:33 portz30 NetworkManager[248]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 19910
Dez 09 15:20:33 portz30 avahi-daemon[259]: Withdrawing address record for fe80::facd:2811:2d70:ecff on wlp2s0.
Dez 09 15:20:33 portz30 avahi-daemon[259]: Withdrawing address record for 10.31.255.18 on wlp2s0.
Dez 09 15:20:33 portz30 avahi-daemon[259]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.31.255.18.
Dez 09 15:20:33 portz30 avahi-daemon[259]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Dez 09 15:20:33 portz30 kernel: wlp2s0: deauthenticating from 00:1d:7e:27:a8:5e by local choice (Reason: 3=DEAUTH_LEAVING)
Dez 09 15:20:33 portz30 NetworkManager[248]: <info> Removing DNS information from /usr/bin/resolvconf
Dez 09 15:20:33 portz30 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Dez 09 15:20:33 portz30 kernel: cfg80211: Calling CRDA to update world regulatory domain
Dez 09 15:20:33 portz30 NetworkManager[248]: <info> NetworkManager state is now ASLEEP
Dez 09 15:20:33 portz30 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Dez 09 15:20:33 portz30 NetworkManager[248]: <info> (enp0s25): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Dez 09 15:20:33 portz30 dbus[260]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Dez 09 15:20:33 portz30 systemd[1]: Cannot add dependency job for unit acpid.socket, ignoring: Unit acpid.socket failed to load: No such file or directory.
Dez 09 15:20:33 portz30 systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory.
Dez 09 15:20:33 portz30 dbus[260]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dez 09 15:20:34 portz30 kernel: e1000e: enp0s25 NIC Link is Down
Dez 09 15:20:34 portz30 kernel: IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
Dez 09 15:20:34 portz30 NetworkManager[248]: <warn> (pid 19910) unhandled DHCP event for interface wlp2s0
Dez 09 15:20:34 portz30 systemd-sleep[5850]: Suspending system...
-- Reboot --
Dez 10 12:46:51 portz30 systemd-journal[137]: Runtime journal is using 8.0M (max allowed 395.7M, trying to leave 593.5M free of 3.8G available → current limit 395.7M).
Dez 10 12:46:51 portz30 systemd-journal[137]: Permanent journal is using 848.0M (max allowed 4.0G, trying to leave 4.0G free of 159.9G available → current limit 4.0G).
Dez 10 12:46:51 portz30 systemd-journal[137]: Time spent on flushing to /var is 1.057ms for 2 entries.
Dez 10 12:46:51 portz30 kernel: CPU0 microcode updated early to revision 0x1c, date = 2014-07-03
Dez 10 12:46:51 portz30 kernel: Initializing cgroup subsys cpuset
Dez 10 12:46:51 portz30 kernel: Initializing cgroup subsys cpu
Dez 10 12:46:51 portz30 kernel: Initializing cgroup subsys cpuacct
Dez 10 12:46:51 portz30 kernel: Linux version 3.17.4-1-ARCH (builduser@tobias) (gcc version 4.9.2 (GCC) ) #1 SMP PREEMPT Fri Nov 21 21:14:42 CET 2014
Dez 10 12:46:51 portz30 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=097d293a-128d-4444-ade3-c587b667db3f rw quiet
Dez 10 12:46:51 portz30 kernel: e820: BIOS-provided physical RAM map:
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000dbfb8fff] usable
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000dbfb9000-0x00000000dbfb9fff] ACPI NVS
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000dbfba000-0x00000000dbfccfff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000dbfcd000-0x00000000dc0b8fff] ACPI NVS
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000dc0b9000-0x00000000dc0e8fff] ACPI data
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000dc0e9000-0x00000000df9fffff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000fe101000-0x00000000fe112fff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed87fff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x00000000ffc00000-0x00000000ffffffff] reserved
Dez 10 12:46:51 portz30 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021f5fffff] usable
Dez 10 12:46:51 portz30 kernel: NX (Execute Disable) protection: active
Dez 10 12:46:51 portz30 kernel: SMBIOS 2.6 present.
Dez 10 12:46:51 portz30 kernel: DMI: TOSHIBA PORTEGE Z30-A/PORTEGE Z30-A, BIOS Version 3.50 04/15/2014Offline
Hello! Maybe it's a hardware issue but maybe it's suspend issue. Can you try other distro or other operating system? What CPU you have? I have little trouble with my ThinkPad X201 with suspend about one month ago. My problem has been solved, when I generate new config file for grub (sudo grub-mkconfig -o /boot/grub/grub.cfg) because, one month ago microcodes for intel cpu required manuall intervention, so maybe its resolve your problem. Sorry for my bad english
I'm from Poland and I still learn English
EDIT: Before you generate new file, check whether you have intel-ucode installed in your system ![]()
Last edited by blackrat (2014-12-10 17:44:42)
Offline
We have different laptops here at work, but sometimes they won't come back on. Our procedure is the following:
1) Unplug all power cords
2) Remove battery
3) Wait 1 minute
4) Re-install battery and plug in power cord
5) Turn on
Again, these are not the same kind of laptops you have. Word has it that it's the batteries or battery status circuitry that causes the issue. It happens to me about 2 times per year, so it's not an every day thing.
Last edited by mrunion (2014-12-10 19:24:03)
Matt
"It is very difficult to educate the educated."
Offline
Thanks for your answers!
@blackrat:
Yes, I use Intel-ucode, but I am aware of the new boot necessaries. Normally, it works flawlessly.
(an ucode issue would have appeared after grub, for me, not even BIOS was visible.)
@mrunion:
That's what I did, too. It didn't help. But good to know it can sometimes happen without serious issues...
Offline
there is a suspend bug on the i686 platform, one way is to downgrade the kernel the other is to add a comand to the linux kernel at boot, both worked for me.
Offline
@archer108:
It led to the same symptoms? Not even switching on possible? If yes: what bug is it specifically?
Offline
People are advicing to downgrade to kernel 3.17.2-1, However, someone said on the forum this thing is fixed with kernel 3.17.6:
Offline
@phairland:
Thanks for your answer. If I wasn't an atheist, I'd pray it won't happen again. ;-) At least it didn't with 3.17.6-1, however valid this is for an event only occurred once...
Offline