Opened 2 years ago

Last modified 2 years ago

#13902 new bug

app_server preventing boot on live USB (hrev51702 x86)

Reported by: geminiman112 Owned by: axeld
Priority: normal Milestone: Unscheduled
Component: Servers/app_server Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

https://lh6.googleusercontent.com/hyUryKblBfFgONDZL5S7xLDNTZw063cPdCVc77cGDVZyMotaiIfBvgKxoGP4L51wjAMFa0wEeCRmbMv03317=w767-h826

This KDL screen appeared when trying to boot from a Haiku live USB on one of my computers. However, on my main computer, this USB boots just fine.

I had Haiku installed on this computer before. Weirdly, it was using the USB device as a bootloader. I was going to fix it today, but then this error occurred.

Later, I deleted all of the partitions on my hard drive using a Linux live CD, but this error persisted.

Attachments (1)

20171223_170428.jpg (3.0 MB ) - added by geminiman112 2 years ago.

Change History (14)

comment:1 by waddlesplash, 2 years ago

Component: - GeneralServers/app_server
Owner: changed from nobody to axeld

I get "Error 403" when trying to view the image. Could you just attach it here?

Also, if it's actually an app_server crash, it's not a KDL but a Debugger prompt. If you type save-report at the prompt it will write a report to ~/Desktop and you can fetch it on next reboot.

by geminiman112, 2 years ago

Attachment: 20171223_170428.jpg added

comment:2 by geminiman112, 2 years ago

Has a Patch: set

comment:3 by geminiman112, 2 years ago

It does not have a patch. I'm sorry, this site is new to me.

Edit: It was an app_server crash. Here is the report: https://pastebin.com/MEHuVC6i

Last edited 2 years ago by geminiman112 (previous) (diff)

comment:4 by pulkomandy, 2 years ago

Has a Patch: unset

comment:5 by geminiman112, 2 years ago

I have looked back into this bug and it appears to be very similar to #2350.

Edit: I changed my graphics card setting to default to the integrated graphics and this error persists, except app_server stops on thread 340 as opposed to 342.

Last edited 2 years ago by geminiman112 (previous) (diff)

comment:6 by waddlesplash, 2 years ago

Indeed it does. Can you extract a syslog from the failed boot? (It will be in /var/log/syslog).

comment:7 by geminiman112, 2 years ago

I can.

https://pastebin.com/sABgm6fd

Edit: For some strange reason, while this bug does occur on my Sansui television, on my Dell computer monitor, the computer boots up just fine.

When I boot the machine using the Dell monitor and switch to the Sansui television, the screen goes black.

My LG television also doesn't crash, although the screen isn't fully shown and there is a glitchy bar at the bottom of the screen.

Last edited 2 years ago by geminiman112 (previous) (diff)

comment:8 by waddlesplash, 2 years ago

It looks like the TV does not support any video modes that the VESA chipset on your computer also does (there is a 1024x768 mode in both but the chipset has it only in 60Hz while the TV has 75Hz.) So, not a whole lot we can do here I think, aside from #10570.

comment:9 by geminiman112, 2 years ago

If that is the case, then why does the Haiku boot screen still load?

comment:10 by waddlesplash, 2 years ago

Hmm, not sure, I'm not very familiar with how we output graphics at that stage. Depending on how your BIOS works we may be reusing a framebuffer from that.

in reply to:  10 comment:11 by geminiman112, 2 years ago

Replying to waddlesplash:

Hmm, not sure, I'm not very familiar with how we output graphics at that stage. Depending on how your BIOS works we may be reusing a framebuffer from that.

I don't know if that's the case. I can change screen resolutions on the boot screen (for example, I can get 640x480 graphics mode and 16 bit color as opposed to the default to work).

comment:12 by pulkomandy, 2 years ago

The boot screen uses vesa, and kdl and debugger prompt both use the framebuffer as app_server. So it seems we do manage to display something in a sane video mode.

in reply to:  8 comment:13 by geminiman112, 2 years ago

Replying to waddlesplash:

It looks like the TV does not support any video modes that the VESA chipset on your computer also does (there is a 1024x768 mode in both but the chipset has it only in 60Hz while the TV has 75Hz.) So, not a whole lot we can do here I think, aside from #10570.

My TV only does 60Hz.

Note: See TracTickets for help on using tickets.