[opensuse] delay on boot
Hello, I'm still on research to understand why I have a 10/20s delay at the end of the kde plasma load. At some time I suspected IPV6, but finally no, it's not. then I find in the boot messages some about a large usb disk (5Tb, archives) that is connected but do not have to be mounted at boot (do not live in fstab), because it's known to be extremely so when mounting. so, why is there this dmesg entry? May be it was mounted when I switched off the computer? thanks jdd dmesg: [ 36.177914] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) [ 38.276709] Bluetooth: RFCOMM ver 1.11 [ 115.782681] sd 5:0:0:0: [sdc] Synchronizing SCSI cache [ 116.021030] sd 5:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 116.106323] usb 2-2.2: USB disconnect, device number 3 journalctl -b0: sept. 01 07:54:22 linux-tivq udisksd[2328]: Unmounted /dev/sdc1 on behalf of uid 1000 sept. 01 07:54:23 linux-tivq kernel: sd 5:0:0:0: [sdc] Synchronizing SCSI cache sept. 01 07:54:24 linux-tivq udisksd[2328]: Powered off /dev/sdc - successfully wrote to sysfs path /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.2/r> -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/09/2019 08.12, jdd@dodin.org wrote:
Hello,
I'm still on research to understand why I have a 10/20s delay at the end of the kde plasma load. At some time I suspected IPV6, but finally no, it's not.
then I find in the boot messages some about a large usb disk (5Tb, archives) that is connected but do not have to be mounted at boot (do not live in fstab), because it's known to be extremely so when mounting.
Sorry, this paragraph I don't understand.
so, why is there this dmesg entry? May be it was mounted when I switched off the computer?
thanks jdd
dmesg:
[ 36.177914] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
[ 38.276709] Bluetooth: RFCOMM ver 1.11 [ 115.782681] sd 5:0:0:0: [sdc] Synchronizing SCSI cache [ 116.021030] sd 5:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 116.106323] usb 2-2.2: USB disconnect, device number 3
Please use "dmesg -T --time-format iso ..." so that we can match the timestamps on both logs.
journalctl -b0:
sept. 01 07:54:22 linux-tivq udisksd[2328]: Unmounted /dev/sdc1 on behalf of uid 1000
sept. 01 07:54:23 linux-tivq kernel: sd 5:0:0:0: [sdc] Synchronizing SCSI cache
sept. 01 07:54:24 linux-tivq udisksd[2328]: Powered off /dev/sdc - successfully wrote to sysfs path /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.2/r>
-- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Le 01/09/2019 à 13:57, Carlos E. R. a écrit :
then I find in the boot messages some about a large usb disk (5Tb, archives) that is connected but do not have to be mounted at boot (do not live in fstab), because it's known to be extremely so when mounting.
Sorry, this paragraph I don't understand.
this disk is extremely long to mount (one have to wait to the plates to spin at sufficient speed), so it's plugged but not mounted anywhere, not even referenced in fstab, so why I don't understand [ 116.106323] usb 2-2.2: USB disconnect, device number 3 I have to reboot to find the info and give it with time code, so later :-( thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
well. I should have tested this before: I removed completely the usb disk. I still have the boot delay. more exactly a plasma delay after login, I can see a faded light bulb (openSUSE logo) sight :-( thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd@dodin.org wrote:
well. I should have tested this before: I removed completely the usb disk.
I still have the boot delay. more exactly a plasma delay after login, I can see a faded light bulb (openSUSE logo)
Just poking in the blind - would systemd-analyze critical-chain or systemd-analyze blame give any helpful hints? Is it only on boot, or for every login? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 02/09/2019 à 12:27, Peter Suetterlin a écrit :
Is it only on boot, or for every login?
good question. Seems to be only on boot. I just disconnect and reconnect twice, very fast. I have an xrandr script on plasma load and I can see it run and finish, the delay is after, I can see a dimmed bulb on screen during the wait :-( thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 02/09/2019 à 12:27, Peter Suetterlin a écrit : I have to save these commands somewhere, I never remember the syntax :-(
Just poking in the blind - would systemd-analyze critical-chain
graphical.target @4.605s └─display-manager.service @1.669s +2.935s └─systemd-user-sessions.service @1.646s +20ms └─remote-fs.target @1.645s (rets under 20ms)
or systemd-analyze blame
over 1000 ms time are: 7min 10.820s fstrim.service 10.157s backup-rpmdb.service 2.935s display-manager.service 2.402s plymouth-quit-wait.service 1.362s mandb.service 1.340s btrfsmaintenance-refresh.service will do again after next reboot thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
well, I finally got a (partial) answer, thanks to the various commands indicated here. since more than two years, I run a startup script to make my display full HD 1920x1080. No major problem since recently, so why I didn't suspect it at first. I only noticed with 15.1 an option in kde setup to start the script *before* the session begin and not after. It was this that sort of failed. Sort of, because it do the job but then gives the delay. The script is pretty simple (three xrandr lines): xrandr --newmode "1920x1080_60.00" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync xrandr --addmode VIRTUAL1 1920x1080_60.00 xrandr --fb 1920x1080_60.00 --dpi 96 --output eDP1 --pos 0x0 --scale-from 1920x1080 --same-as VIRTUAL1 the problem showed in journalctl -b0 like this: sept. 03 08:48:09 linux-tivq plasmashell[3001]: org.kde.plasmaquick: Applet "Menu des applications" loaded after 60 msec sept. 03 08:48:35 linux-tivq kwin_x11[2992]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1573, resource id: 6291487, major code: 18 (ChangeProperty), minor code: 0 sept. 03 08:48:37 linux-tivq plasmashell[3001]: plasma-pk-updates: Transaction status changed: "finished" "(100%)" it's the "badwindow" that made me think of the problem, added to the fact it happens very far in the login process and there are no visible error in boot. Why is this only at boot time and not after disconnect/reconnect may be related to X? May be it's related to the fact I setup bumblebee (working OK)? Well, for now I wont do more. I can start the script after session... thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd@dodin.org wrote:
Hello,
I'm still on research to understand why I have a 10/20s delay at the end of the kde plasma load. At some time I suspected IPV6, but finally no, it's not.
then I find in the boot messages some about a large usb disk (5Tb, archives) that is connected but do not have to be mounted at boot (do not live in fstab), because it's known to be extremely so when mounting.
so, why is there this dmesg entry? May be it was mounted when I switched off the computer?
What is your setting of 'On Login' in Settings->Startup and Shutdown->Desktop Session? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 01/09/2019 à 14:10, Peter Suetterlin a écrit :
What is your setting of 'On Login' in Settings->Startup and Shutdown->Desktop Session?
for what I know, only defaults :-( jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd@dodin.org wrote:
Le 01/09/2019 à 14:10, Peter Suetterlin a écrit :
What is your setting of 'On Login' in Settings->Startup and Shutdown->Desktop Session?
for what I know, only defaults :-(
I'm not sure what the defaults are. But mine is set to start with a clean new session. But if it was set to restore the previous session, and you had the disk mounted there, that might explain it. Therefore the question *what* the setting is. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 02/09/2019 à 12:24, Peter Suetterlin a écrit :
session. But if it was set to restore the previous session, and you had the disk mounted there, that might explain it. Therefore the question *what* the setting is.
ah, this one. I start with empty session thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Carlos E. R. -
jdd＠dodin.org -
Peter Suetterlin