laptop won't finish reboot or shutdown, KDE

English Install/Boot/Login
#1

When I installed the opensuse 15 dvd to the laptop, I erased all the old partitions for a full install. The install completes with “reboot: ok”. I click on ‘ok’. It reboots to ‘setting up virtual console’. After 10 mins, it was still frozen. I use the motherboard shutdown(hold the power button).

I clicked on the power button. The screen shows ‘failed to setup virtual console’. The boot completes normally. I use the start button to shutdown. The screen reads ‘shutting down’ and freezes. Reboot shows the same thing. I use motherboard shutdown to power off.

In opensuse 42.3, it would shut down normally.

Need help. I’m working on another hardware issue. So, only enough time for this info.

#2

Laptop model? Graphics hardware details?

#3

TOSHIBA.Satellite A215

2.3ghz cpu 4 gb of memory. Max memory and speed.

Recieved it as payment for software help. Can’t afford a modern laptop.

I have the hwinfo file. What from it then? It won’t fit on the forum.

[FAILED] Failed to start Setup Virtual Console.
See ‘systemctl status systemd-vconsole-setup.service’ for details.

● systemd-vconsole-setup.service - Setup Virtual Console
Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static; vendor preset: disabled)
Active: inactive (dead) since Mon 2018-10-08 21:39:37 PDT; 2h 1min ago
Docs: man:systemd-vconsole-setup.service(8)
man:vconsole.conf(5)
Main PID: 734 (code=exited, status=0/SUCCESS)

Oct 08 21:39:37 linux-cydu systemd[1]: Starting Setup Virtual Console…
Oct 08 21:39:37 linux-cydu systemd[1]: Started Setup Virtual Console.

#4

Graphics hardware details can be got using

/usr/sbin/hwinfo --gfxcard

or

/sbin/lspci -nnk|egrep -iA3 "vga|graphics"

inxi -Gxx
#5

hwinfo --gfxcard
18: PCI 105.0: 0300 VGA compatible controller (VGA)
[Created at pci.378]
Unique ID: ul7N.ys8N7TjCnJ6
Parent ID: vSkL.CcQvSpBG0f3
SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:05.0
SysFS BusID: 0000:01:05.0
Hardware Class: graphics card
Model: “ATI RS690M [Radeon Xpress 1200/1250/1270]”
Vendor: pci 0x1002 “ATI Technologies Inc”
Device: pci 0x791f “RS690M [Radeon Xpress 1200/1250/1270]”
SubVendor: pci 0x1179 “Toshiba America Info Systems”
SubDevice: pci 0xff1a
Driver: “radeon”
Driver Modules: “radeon”
Memory Range: 0xf0000000-0xf7ffffff (ro,non-prefetchable)
Memory Range: 0xf8100000-0xf810ffff (rw,non-prefetchable)
I/O Ports: 0x9000-0x9fff (rw)
Memory Range: 0xf8000000-0xf80fffff (rw,non-prefetchable)
Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
IRQ: 27 (56159 events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: “pci:v00001002d0000791Fsv00001179sd0000FF1Abc03sc00i00”
Driver Info #0:
Driver Status: radeon is active
Driver Activation Cmd: “modprobe radeon”
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #28 (PCI bridge)

Primary display adapter: #18

Note: Even when this came out. The video card was considered low-grade.

#6

Ok, thanks for that info. The graphics hardware shouln’t be presenting an issue here.

Returning to your opening comments…

I clicked on the power button. The screen shows ‘failed to setup virtual console’. The boot completes normally. I use the start button to shutdown. The screen reads ‘shutting down’ and freezes. Reboot shows the same thing. I use motherboard shutdown to power off.

You mention the the boot completes normally. So you get a display manager login, and get a working KDE desktop after that? It’s only when you attempt to shutdown that problems occur again?

#7

Meaning two separate problems? Or are they connected?

Boot:
click power button
[various boot messages}
(red) failed to initialize virtual console
[various boot messages}
[boot completes to desktop]

Start firefox. surf web. done. exit firefox

click → start menu → power/session → shutdown or reboot option
{various shutdown messages]

reboot. [freezes] 5mins+
shutdown. [freezes] 5mins+

opensuse leap 42.3 will shutdown after about 10 seconds at this point.

I think you use var/log/messages to get the shutdown logs.

#8

The boot repeats this cycle every time.

#9

Show us

sudo systemd-analyze critical-chain

click → start menu → power/session → shutdown or reboot option
{various shutdown messages]

reboot. [freezes] 5mins+
shutdown. [freezes] 5mins+

I think you use var/log/messages to get the shutdown logs.

Yes, if syslog is running then you can examine /var/log/mesages. Otherwise, inspect the systemd journal…

sudo journalctl -b
#10

To examine a previous boot…

sudo journalctl -b -1

This may be of value to you…
https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs

#11

[QUOTE=deano_ferrari;2882872]Show us

sudo systemd-analyze critical-chain

Yes, if syslog is running then you can examine /var/log/mesages. Otherwise, inspect the systemd journal…

sudo journalctl -b

[/QUOTE]

systemd-analyze critical-chain
The time after the unit is active or started is printed after the “@” character.
The time the unit takes to start is printed after the “+” character.

graphical.target @7.787s
└─display-manager.service @5.697s +2.089s
└─systemd-user-sessions.service @5.674s +18ms
└─remote-fs.target @5.673s
└─iscsi.service @5.596s +75ms
└─network.target @5.595s
└─wpa_supplicant.service @5.842s +133ms
└─dbus.service @3.062s
└─basic.target @2.972s
└─sockets.target @2.972s
└─dbus.socket @2.972s
└─sysinit.target @2.968s
└─apparmor.service @1.526s +1.442s
└─var.mount @1.365s +115ms
└─local-fs-pre.target @1.287s
└─lvm2-monitor.service @308ms +965ms
└─lvm2-lvmetad.service @372ms
└─lvm2-lvmetad.socket @306ms
└─-.slice

I’v only the shown the red lines. It’s over 2000 lines.

journalctl -b [red lines}

Oct 10 13:21:48 linux-cydu kernel: Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic retpoline

Oct 10 13:21:48 linux-cydu kernel: …MP-BIOS bug: 8254 timer not connected to IO-APIC

Oct 10 13:21:48 linux-cydu kernel: mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 0: fe17e10000000175
Oct 10 13:21:48 linux-cydu kernel: mce: [Hardware Error]: TSC 0 ADDR fff3ff17fff3
Oct 10 13:21:48 linux-cydu kernel: mce: [Hardware Error]: PROCESSOR 2:60f82 TIME 1539202904 SOCKET 0 APIC 1 microcode 0
Oct 10 13:21:48 linux-cydu kernel: mce: [Hardware Error]: Machine check events logged
Oct 10 13:21:48 linux-cydu kernel: mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 1: ffffffffffffffff
Oct 10 13:21:48 linux-cydu kernel: mce: [Hardware Error]: TSC 0 ADDR ffffffffffffffff
Oct 10 13:21:48 linux-cydu kernel: mce: [Hardware Error]: PROCESSOR 2:60f82 TIME 1539202904 SOCKET 0 APIC 1 microcode 0
Oct 10 13:21:48 linux-cydu kernel: mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: f600000000002bc8
Oct 10 13:21:48 linux-cydu kernel: mce: [Hardware Error]: TSC 0 ADDR e02d17fd81
Oct 10 13:21:48 linux-cydu kernel: mce: [Hardware Error]: PROCESSOR 2:60f82 TIME 1539202904 SOCKET 0 APIC 1 microcode 0

[White]
Oct 10 13:21:48 linux-cydu systemd-sysctl[147]: Couldn’t write ‘0’ to ‘dev/cdrom/autoclose’, ignoring: No such file or directory
Oct 10 13:21:48 linux-cydu systemd[1]: Started dracut ask for additional cmdline parameters.
Oct 10 13:21:48 linux-cydu systemd[1]: Starting dracut cmdline hook…
Oct 10 13:21:48 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:48 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu dracut-cmdline[158]: dracut-15.0 dracut-044-lp150.14.3.1
Oct 10 13:21:49 linux-cydu dracut-cmdline[158]: Using kernel command line parameters: rd.lvm.lv=system/swap rd.lvm.lv=system/root resume=/dev/mapper/system-swap root=/dev/mapper/>
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd[1]: Started dracut cmdline hook.
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd[1]: Starting dracut pre-udev hook…
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:49 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:50 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:50 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:50 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:50 linux-cydu systemd[1]: Started dracut pre-udev hook.

Oct 10 13:21:51 linux-cydu systemd-vconsole-setup[134]: Input/output error
Oct 10 13:21:51 linux-cydu kernel: ata3: softreset failed (device not ready) [red line]
Oct 10 13:21:51 linux-cydu kernel: ata3: applying PMP SRST workaround and retrying
Oct 10 13:21:51 linux-cydu systemd-vconsole-setup[134]: Input/output error

[red line]
Oct 10 13:22:08 linux-cydu /hp-systray[2298]: hp-systray[2298]: error: option -s not recognized

Oct 10 13:22:10 linux-cydu /hp-upgrade[2403]: hp-upgrade[2403]: error: HPLIP upgrade is disabled by openSUSE for security reasons, see https://bugzilla.novell.com/show_bug.cgi?id>

Oct 10 13:22:31 linux-cydu dbus-daemon[1245]: [system] Failed to activate service ‘org.bluez’: timed out (service_start_timeout=25000ms) [white]
Oct 10 13:22:31 linux-cydu pulseaudio[2203]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service ‘org.bluez’: > [red line]
Oct 10 13:22:31 linux-cydu kdeinit5[1964]: org.kde.bluez: PendingCall Error: “Failed to activate service ‘org.bluez’: timed out (service_start_timeout=25000ms)” [white]

#12

Please use

 [/COD.] tags when posting output. Refer to the '#' button in the forum editor.
#13

I think you’re going to need to submit a bug report for this.

#14

I know about

. I forgot to include it.


 Report to who?    I'm also getting a kwin crash and a firefox crash on trying to login to yahoo mail. Turned off addons same crash.

username ->username --> click -->crash

There are many system errors in the 2000 line log. Tell me what I should be looking for.
#15

Start by reviewing the advice here
https://en.opensuse.org/openSUSE:Submitting_bug_reports

I’m also getting a kwin crash and a firefox crash on trying to login to yahoo mail. Turned off addons same crash./.

username ->username → click -->crash

Very strange. I can’t imagine that these are related, but clearly your KDE environment is unstable. In your case it may be worth considering reinstalling Leap 15 again.

#16

DUCKDUCKGO SEARCH: linux “shutdown log”

https://superuser.com/questions/167281/is-there-a-log-that-records-shutdowns-in-linux

https://www.linuxquestions.org/questions/linux-general-1/shutdown-log-file-516291/

https://unix.stackexchange.com/questions/9819/how-to-find-out-from-the-logs-what-caused-system-shutdown

https://askubuntu.com/questions/58625/where-is-the-shutdown-log

https://unix.stackexchange.com/questions/53252/how-to-read-the-messages-during-power-off

Last line of power off:

powering off. [freeze]

It looks like linux shutdowns successfully. The final command to the shutdown the hardware is failing. I read something about acpi bios bug.

#17

Kwin did start crashing until about 1 week ago.

…

For my laptop sudo halt will do software shutdown not hardware. i.e the screen and other hardware remain running. The last message in the screen will be
System halted

At this point I just press the Power button and everything off. You can try this. You may also try sudo halt --verbose

#18

Not sure what you’re to convey with all the links in your last post. Your install seems to have a lot more issues going on than just a shutdown problem?

Last line of power off:

powering off. [freeze]

It looks like linux shutdowns successfully. The final command to the shutdown the hardware is failing. I read something about acpi bios bug.

Anything interesting reported by the following?

dmesg|grep acpi
#19 
# dmesg|grep acpi
    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    0.150094] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    0.445252] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    0.445261] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
    0.445278] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-18] only partially covers this bridge
    0.451394] acpiphp: Slot [1] registered
    0.510274] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
    7.927468] acpi device:3c: registered as cooling_device3
    8.096811] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.24
    8.214284] toshiba_acpi: Supported laptop features: hotkeys touchpad cooling-method

Yes, are they related? I don’t think so. I’ll save those other bugs for another post.

The links are all the info I could find on the subject.

https://www.linuxquestions.org/questions/linux-newbie-8/mint-18-3-shutdown-and-restart-freeze-4175623172/

#20

I would submit a bug report for the vconsole errors encountered during boot. I note that the laptop model is quite an old (10 years?) and the shutdown errors could well be BIOS related. Have you investigated any power-related settings in the BIOS?