Opened 5 years ago

Closed 3 years ago

#15895 closed bug (fixed)

Desktop occasionally does not start

Reported by: Maxis Owned by: axeld
Priority: normal Milestone: R1/beta4
Component: Servers/launch_daemon Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

hrev54047

Sometimes Haiku doesn't boot to desktop in VirtualBox 5.2.36. After instaling it on serial disk and give OS a 512MiB. Haiku sometimes boot only to blue screen with no tracker. Also this was happen even with 4096MiB once.

Attachments (6)

syslog_no boot to desktop​ (122.0 KB ) - added by Maxis 5 years ago.
Haiku.vbox​ (4.7 KB ) - added by Maxis 5 years ago.
VirtualBox_Haiku_22_04_2020_09_53_41_No Tracker.png​ (4.8 KB ) - added by Maxis 5 years ago.
VirtualBox_Haiku_22_04_2020_09_55_37_No Tracker KDL.png​ (26.2 KB ) - added by Maxis 5 years ago.
syslog_Only blue Desktop no Tracker​ (484.0 KB ) - added by Maxis 5 years ago.
Haiku_No Tracker.vbox​ (4.6 KB ) - added by Maxis 5 years ago.

Download all attachments as: .zip

Change History (22)

by Maxis, 5 years ago

Attachment: syslog_no boot to desktop​ added

by Maxis, 5 years ago

Attachment: Haiku.vbox​ added

comment:1 by waddlesplash, 5 years ago

It's possible this is due to the use of the PCnet device. See if this still occurs after using an Intel one instead.

comment:2 by Maxis, 5 years ago

I caught it twice this morning with Intel NIC. One when boot Live CD. Second, when boot installed on disk Haiku. Those happens with 2048MiB RAM limit.

by Maxis, 5 years ago

Attachment: VirtualBox_Haiku_22_04_2020_09_53_41_No Tracker.png​ added

by Maxis, 5 years ago

Attachment: VirtualBox_Haiku_22_04_2020_09_55_37_No Tracker KDL.png​ added

by Maxis, 5 years ago

Attachment: syslog_Only blue Desktop no Tracker​ added

by Maxis, 5 years ago

Attachment: Haiku_No Tracker.vbox​ added

comment:3 by diver, 5 years ago

I had something similar in #15563. Does pressing Ctrl+Alt+Del and Restart Desktop work?

comment:4 by Maxis, 5 years ago

diver I don't know. I never tried that.

comment:5 by X512, 5 years ago

Can you move cursor when issue occurred?

comment:6 by Maxis, 5 years ago

X512

Yes. I can move cursor when this issue happens.

comment:7 by X512, 5 years ago

Can be a problem in launch_daemon.

comment:8 by diver, 5 years ago

Could you try to reproduce it and in Input menu of VirtualBox select Keyboard->Send Ctrl-Alt-Del and see if you get Team monitor.

comment:9 by Maxis, 5 years ago

I reproduced the problem and after sending a CAD signal i have got Team monitor and after pressing "Restart the desktop" button i have got working desktop.

comment:10 by waddlesplash, 5 years ago

I have seen this before too, but only on 32-bit. It seems there is some sort of race condition.

comment:11 by waddlesplash, 5 years ago

Component: - General → Servers/launch_daemon
Owner: changed from nobody to axeld
Platform: x86-64 → All
Summary: Sometimes Haiku doesn't boot to desktop in VirtualBox → Desktop occasionally does not start

comment:12 by waddlesplash, 3 years ago

I can reproduce this with some significant frequency on QEMU using Windows Hypervisor acceleration (and only 1 virtual core) on x86_64. I entered KDL and determined that launch_roster was jammed in the kernel on user_mutex_wait_locked from a heap free (the only other thread was not blocked.)

comment:13 by waddlesplash, 3 years ago

Got it again. This time, both launch_daemons's "main worker" threads are waiting for their respective "have runnable job" semaphores (two different semaphores, 1194 and 1543) while the main threads are waiting for messages in BLooper.

Version 1, edited 3 years ago by waddlesplash (previous) (next) (diff)

comment:14 by waddlesplash, 3 years ago

This may be improved by hrev55460.

comment:15 by Maxis, 3 years ago

I tested hrev55482 and bug seems fixed. After many test attempts i never occured the bug.

comment:16 by pulkomandy, 3 years ago

Milestone: Unscheduled → R1/beta4
Resolution: → fixed
Status: new → closed
Note: See TracTickets for help on using tickets.