seduction
 Language:
Welcome, Guest. Please login or register.
Did you miss your activation email?
2020/10/25, 22:30:35


Help

Author [EN] [PL] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: 160-seconds delay while booting Lenovo Yoga x390 (siduction installed to hdd)  (Read 365 times)

0 Members and 1 Guest are viewing this topic.

Offline Spike_DE

  • User
  • Posts: 48
Hi,

booting my Yoga stalls for aprox 2.5 minutes before the login-Screen (console & gui) appears.

dmesg -d delivers:

Code: [Select]
[   13.283411 <    0,001022>] wlp0s20f3: associate with 70:18:a7:0e:7e:42 (try 1/3)
[   13.287074 <    0,003663>] wlp0s20f3: RX AssocResp from 70:18:a7:0e:7e:42 (capab=0x1421 status=0 aid=5)
[   13.290433 <    0,003359>] wlp0s20f3: associated
[   13.291970 <    0,001537>] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready
[   13.443305 <    0,151335>] wlp0s20f3: Limiting TX power to 17 (20 - 3) dBm as advertised by 70:18:a7:0e:7e:42
[  177.955379 <  164,512074>] usb 1-3: new high-speed USB device number 8 using xhci_hcd
[  178.082261 <    0,126882>] usb 1-3: New USB device found, idVendor=0781, idProduct=5567, bcdDevice= 1.26
[  178.082268 <    0,000007>] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  178.082273 <    0,000005>] usb 1-3: Product: Cruzer Blade
[  178.082276 <    0,000003>] usb 1-3: Manufacturer: SanDisk
[  178.082279 <    0,000003>] usb 1-3: SerialNumber: 20054963401B1A704F7C

Can't see any errors. After resuming, everything works fine.

Problem exists ever since installation on this machine. (apt dist-upgrade "up-to-date" every 1-2 weeks)

Current:
Linux x390y 5.8.11-towo.1-siduction-amd64 #1 SMP PREEMPT siduction 5.8-11 (2020-09-23) x86_64 GNU/Linux

Just Dist-Upgrading... Will report.

Any ideas?


some Infos:


Code: [Select]
System:    Host: x390y Kernel: 5.8.11-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: Xfce 4.14.2
           Distro: siduction 18.3.0 Patience - xfce - (201909231834)
Machine:   Type: Convertible System: LENOVO product: 20NN002EGE v: ThinkPad X390 Yoga serial: R90VB078
           Mobo: LENOVO model: 20NN002EGE v: SDK0J40697 WIN serial: xxx UEFI: LENOVO v: N2LET76W (1.76 )
           date: 06/16/2020
Battery:   ID-1: BAT0 charge: 40.4 Wh condition: 51.5/50.5 Wh (102%)
CPU:       Info: Quad Core Intel Core i5-8265U [MT MCP] speed: 1288 MHz min/max: 400/3900 MHz
Graphics:  Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
           Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
           Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.9
Network:   Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi
           Device-2: Intel Ethernet I219-V driver: e1000e
Drives:    Local Storage: total: 476.94 GiB used: 11.26 GiB (2.4%)
Info:      Processes: 260 Uptime: 42m Memory: 15.30 GiB used: 1.39 GiB (9.1%) Shell: Bash inxi: 3.1.07
« Last Edit: 2020/10/11, 09:48:09 by Spike_DE »
--
Spike_DE

type cat /vmlinuz > /dev/audio to hear the voice of god.

Offline Spike_DE

  • User
  • Posts: 48
same behaviour after dist-upgrade. but without USB-stick the last entry is:

Code: [Select]
[    4.825122 <    0,000041>] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input29
[   12.608388 <    7,783266>] wlp0s20f3: authenticate with d4:ad:71:67:c8:2d
[   12.609979 <    0,001591>] wlp0s20f3: send auth to d4:ad:71:67:c8:2d (try 1/3)
[   12.650728 <    0,040749>] wlp0s20f3: authenticated
[   12.651572 <    0,000844>] wlp0s20f3: associate with d4:ad:71:67:c8:2d (try 1/3)
[   12.656717 <    0,005145>] wlp0s20f3: RX AssocResp from d4:ad:71:67:c8:2d (capab=0x1101 status=0 aid=43)
[   12.658618 <    0,001901>] wlp0s20f3: associated
[   12.659907 <    0,001289>] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready
[   12.666642 <    0,006735>] wlp0s20f3: Limiting TX power to 20 (23 - 3) dBm as advertised by d4:ad:71:67:c8:2d
« Last Edit: 2020/10/11, 09:46:26 by Spike_DE »
--
Spike_DE

type cat /vmlinuz > /dev/audio to hear the voice of god.

Offline paxmark2

  • User
  • Posts: 83
not a pro here by any means, but  output of
sudo systemd-analyze blame
and

sudo journalctl -b -0 | grep ailed                         ## gives results for Failed and failed   - among others.   

sometimes gives good information

Offline Spike_DE

  • User
  • Posts: 48
During the first delay, the mouse-coursor is visible and moveable, but no login-screen / cli-login-prompt appears.
After log-in it hangs again for about 1-2 minutes in the login-screen, until the desktop / cli-prompt appears without error message.
result for "journalctl -b -0 | grep ailed" below. (thanks for the tip!)

The date now is 10:33 CEST, bit confusing to read 12:29...

this failure looks interesting (and extends 2,5 minutes):
Code: [Select]
Okt 09 10:30:34 x390y systemd[1]: user@113.service: Failed with result 'exit-code'.
Okt 09 10:30:34 x390y systemd[1]: Failed to start User Manager for UID 113.
Okt 09 10:33:04 x390y systemd[1]: user@1000.service: Failed with result 'exit-code'.


Will google that problem... some tips anyway?


Full output:
Code: [Select]
Okt 09 12:29:02 x390y kernel: iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
Okt 09 12:29:02 x390y kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwl-debug-yoyo.bin failed with error -2
Okt 09 12:29:02 x390y kernel: thermal thermal_zone10: failed to read out thermal zone (-61)
Okt 09 12:29:02 x390y udisksd[669]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Okt 09 12:29:02 x390y udisksd[669]: Failed to load the 'mdraid' libblockdev plugin
Okt 09 12:29:02 x390y colord[752]: failed to get session [pid 650]: Keine Daten verfügbar
Okt 09 12:29:03 x390y blueman-mechani[648]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Okt 09 12:29:03 x390y wpa_supplicant[670]: nl80211: kernel reports: Attribute failed policy validation
Okt 09 12:29:03 x390y wpa_supplicant[670]: Failed to create interface p2p-dev-wlp0s20f3: -22 (Invalid argument)
Okt 09 12:29:03 x390y wpa_supplicant[670]: nl80211: Failed to create a P2P Device interface p2p-dev-wlp0s20f3
Okt 09 12:29:03 x390y wpa_supplicant[670]: P2P: Failed to enable P2P Device interface
Okt 09 12:29:03 x390y wpa_supplicant[670]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failed
Okt 09 12:29:03 x390y NetworkManager[652]: <warn>  [1602239343.7262] sup-iface[b13461865272736b,0,wlp0s20f3]: call-p2p-cancel: failed with P2P cancel failed
Okt 09 12:29:04 x390y bluetoothd[649]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Okt 09 12:29:12 x390y wpa_supplicant[670]: wlp0s20f3: SME: Deauth request to the driver failed
Okt 09 12:29:12 x390y wpa_supplicant[670]: wlp0s20f3: SME: Deauth request to the driver failed
Okt 09 12:29:12 x390y wpa_supplicant[670]: wlp0s20f3: SME: Deauth request to the driver failed
Okt 09 12:29:17 x390y ModemManager[731]: <info>  [modem0] state changed (unknown -> failed)
Okt 09 12:29:18 x390y NetworkManager[652]: <info>  [1602239358.2530] device (cdc-wdm0): modem state 'failed'
Okt 09 12:29:18 x390y NetworkManager[652]: <info>  [1602239358.2534] modem-broadband[cdc-wdm0]: failed to retrieve SIM object: No SIM object available
Okt 09 12:29:46 x390y dbus-daemon[651]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Okt 09 10:30:34 x390y systemd[1]: user@113.service: Failed with result 'exit-code'.
Okt 09 10:30:34 x390y systemd[1]: Failed to start User Manager for UID 113.
Okt 09 10:33:04 x390y systemd[1]: user@1000.service: Failed with result 'exit-code'.
Okt 09 10:33:04 x390y systemd[1]: Failed to start User Manager for UID 1000.
Okt 09 10:33:04 x390y dbus-daemon[22890]: [session uid=1000 pid=22888] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Okt 09 10:33:04 x390y dbus-daemon[22910]: [session uid=1000 pid=22908] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Okt 09 10:33:04 x390y dbus-daemon[22910]: [session uid=1000 pid=22908] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Okt 09 10:33:04 x390y dbus-daemon[22910]: [session uid=1000 pid=22908] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Okt 09 10:33:06 x390y blueman-mechani[23192]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Okt 09 10:33:06 x390y dbus-daemon[22910]: [session uid=1000 pid=22908] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory
--
Spike_DE

type cat /vmlinuz > /dev/audio to hear the voice of god.


Offline Spike_DE

  • User
  • Posts: 48
hi devil,
thx, already found that article and tried all.

light-dm not installed. (sddm)

login at console (ctrl-alt-f2) also stalled for 1-2 minutes. Every login for root or users (even through ssh) stalls aprox. 90 seconds.

disk not full
no upgrade-errors
can't switch gfx-card (notebook)
rights of passwd ok

tried to install lightdm as replacement for sddm... same behaviour.

maybe some problem with the login-scripts... will take further looks.
--
Spike_DE

type cat /vmlinuz > /dev/audio to hear the voice of god.

Offline der_bud

  • User
  • Posts: 948
  • member
Just wild guessing, but indeed your time jumping from 12:29 to 10:30 looks strange. Perhaps Network Time Sync not working, could that mean during boot 'something' ist waiting too long for network ready? What does
Code: [Select]
systemctl status systemd-timesyncdsay? And still what paxmark2 mentioned would be interesting as well as one other status option, so look at
Code: [Select]
systemd-analyze blame
systemd-analyze critical-chain
Du lachst? Wieso lachst du? Das ist doch oft so, Leute lachen erst und dann sind sie tot.

Offline Spike_DE

  • User
  • Posts: 48
many further errors occurs during next Dist-Upgrade. Just newly installed from image and now everything is ok.
always fine to have a separate home-partition ;)
--
Spike_DE

type cat /vmlinuz > /dev/audio to hear the voice of god.