Opened 8 years ago
Last modified 4 years ago
#13321 new enhancement
Enhance kernel bluescreen setting
| Reported by: | kallisti5 | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | System/Kernel | Version: | R1/Development |
| Keywords: | KDL bluescreen | Cc: | ttcoder |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
This is related to the buildslaves (and honestly any kind of headless Haiku installation). This ticket is the result of a conversation with pulkomandy in irc.
Config: /boot/home/config/settings/kernel/drivers/kernel
Finer control is needed over KDL events. The "bluescreen" setting allows you to disable the full screen kdl, however the system still locks up and prompts on the serial port.
A more reasonable setting would be:
kdl = bluescreen,serial-only,reboot
- bluescreen = normal behavior. KDL shown and serial prompted (== bluescreen true)
- serial-only = no KDL shown, serial prompted (== bluescreen false)
- reboot = when KDL is encountered, reboot (new, and maybe sync to disk if possible???)
Change History (10)
comment:1 by , 5 years ago
| Component: | - General → System/Kernel |
|---|
comment:2 by , 5 years ago
| Cc: | added |
|---|
comment:3 by , 4 years ago
comment:4 by , 4 years ago
Why it is called bluescreen? Haiku kernel crash screen is white, not blue.
comment:5 by , 4 years ago
For historical reasons that's what most people are familiar with. Amiga had a black and orange guru meditation alert. Unix has kernel panics in ordinary text. See https://en.wikipedia.org/wiki/Blue_Screen_of_Death
comment:6 by , 4 years ago
It was called bluescreen in BeOS already (source: https://www.haiku-os.org/legacy-docs/benewsletter/Issue5-13.html). I guess as an inside joke about feature parity with Windows or something.
comment:7 by , 4 years ago
I took this thread and motivation to update the Wikipedia article at https://en.wikipedia.org/wiki/Screen_of_death to include Haiku/BeOS
follow-up: 10 comment:8 by , 4 years ago
anyway, i'm so far off topic :-)
a reboot on KDL would indeed be nice. I expect mmlr has to kick his package builders pretty often.
comment:9 by , 4 years ago
On a related note, I've added a pull request for a screen shot of a KDL to the Haiku web site. https://github.com/haiku/website/pull/398 Now you'll have something to cite for Wikipedia.
Of course, this feature request's purpose is to get rid of the KDL screen :-)
comment:10 by , 4 years ago
Replying to kallisti5:
a reboot on KDL would indeed be nice. I expect mmlr has to kick his package builders pretty often.
Actually, since the latest kernel work they are exceptionally stable. After 55 and 40 days uptime, they are still almost at their initial RAM usage even though they were pretty busy with all kinds of builds since then.
As for this ticket, shouldn't bluescreen = false just be made to reboot? When KDL is entered, it will already put that on the serial line if that is enabled, why would "hiding" the screen itself be useful?
Yes, reboot on KDL crash would be quite useful for long running things like radio stations. Possibly log the crash to in-memory syslog (in case the file systems aren't working) and reboot?