THAT BSOD was caused by a driver *crashing*, not a driver *returning an error code*, which is a very different thing because a crash is uncontrolled and cannot be safely handled, while an error code return *is* a safe and controlled condition.
Linux actually tries to prevent a full system panic, and only terminates the current process if the context is a user process. If you're lucky that means the machine keeps working as normal, if the crash didn't corrupt memory. More often than not, even in that case, the faulty driver had some mutexes locked and your system will slowly deadlock into oblivion as other processes try to lock the same mutex. There is no reasonable way around this. This is why uncontrolled crashes are bad and error returns are not.
Hector Martin /
npub1qk…9azpx
2024-07-20 14:59:13
in reply to nevent1q…xr2v
Author Public Key
npub1qk9x6yrvten3jqyvundn7exggm90fxf9yfarj5eaz25yd7aty8hqe9azpxPublished at
2024-07-20 14:59:13Event JSON
{
"id": "25eb5741a3112f742f17241a31b80bf70304d418b08d5abf7fd65af390c16ff4",
"pubkey": "058a6d106c5e6719008ce4db3f64c846caf49925227a39533d12a846fbab21ee",
"created_at": 1721487553,
"kind": 1,
"tags": [
[
"p",
"058a6d106c5e6719008ce4db3f64c846caf49925227a39533d12a846fbab21ee"
],
[
"e",
"81f10c6eb4fae45047e3ea1225c63b1b378d2a71db6b4070f9a3dba20b076fcf",
"",
"reply"
],
[
"e",
"fa9d6ef9ac8552ce088e83926f2a2e750a20fe430f71755e0498db3a059fabda",
"",
"root"
],
[
"p",
"2ceb75c8271582855ec79d56c3f90da020e88de9f98dd6e76a1c7e436d5da02a"
],
[
"proxy",
"https://social.treehouse.systems/@marcan/112819408301878919",
"web"
],
[
"p",
"b907aa0bc5d09107b3070e8b392e2bd310cc538c34c3cbd86a76fb059b2cd073"
],
[
"proxy",
"https://social.treehouse.systems/users/marcan/statuses/112819408301878919",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://social.treehouse.systems/users/marcan/statuses/112819408301878919",
"pink.momostr"
],
[
"-"
]
],
"content": "THAT BSOD was caused by a driver *crashing*, not a driver *returning an error code*, which is a very different thing because a crash is uncontrolled and cannot be safely handled, while an error code return *is* a safe and controlled condition.\n\nLinux actually tries to prevent a full system panic, and only terminates the current process if the context is a user process. If you're lucky that means the machine keeps working as normal, if the crash didn't corrupt memory. More often than not, even in that case, the faulty driver had some mutexes locked and your system will slowly deadlock into oblivion as other processes try to lock the same mutex. There is no reasonable way around this. This is why uncontrolled crashes are bad and error returns are not.",
"sig": "5360a64c830048ec7774798f205f954e9e6774e773aea12b13bbb5ecf8ad3604298311909bbb4f1e6c43711eb5d208b856f4e540255a3c8253848a900d16a4b1"
}