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
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)
Change History (22)
by , 5 years ago
Attachment: | syslog_no boot to desktop added |
---|
by , 5 years ago
Attachment: | Haiku.vbox added |
---|
comment:1 by , 5 years ago
comment:2 by , 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 , 5 years ago
Attachment: | VirtualBox_Haiku_22_04_2020_09_53_41_No Tracker.png added |
---|
by , 5 years ago
Attachment: | VirtualBox_Haiku_22_04_2020_09_55_37_No Tracker KDL.png added |
---|
by , 5 years ago
Attachment: | syslog_Only blue Desktop no Tracker added |
---|
by , 5 years ago
Attachment: | Haiku_No Tracker.vbox added |
---|
comment:3 by , 5 years ago
I had something similar in #15563. Does pressing Ctrl+Alt+Del and Restart Desktop work?
comment:8 by , 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 , 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 , 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 , 5 years ago
Component: | - General → Servers/launch_daemon |
---|---|
Owner: | changed from | to
Platform: | x86-64 → All |
Summary: | Sometimes Haiku doesn't boot to desktop in VirtualBox → Desktop occasionally does not start |
comment:12 by , 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 , 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.
Also, app_server seems also stuck, waiting for cursor data; input_server's cursor thread is stuck waiting for the app_server link lock.
comment:15 by , 3 years ago
I tested hrev55482 and bug seems fixed. After many test attempts i never occured the bug.
comment:16 by , 3 years ago
Milestone: | Unscheduled → R1/beta4 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
It's possible this is due to the use of the PCnet device. See if this still occurs after using an Intel one instead.