Three fixes that turn unconditional panics into recoverable errors:
1. drivers/graphics/vesad/src/main.rs: replaced bare 'panic!()' at
line 132 (unconditional if the event loop exits) with a clean
exit so init can restart vesad or fall back to a different
display driver.
2. drivers/storage/nvmed/src/main.rs: replaced the
'panic!("timeout on init")' timeout with a structured error:
log a message, then process::exit(1) so init can fall back to
another block driver (virtio-blkd, ahcid, etc.). nvmed_init
future still races against the timer future, but a timeout is
no longer a kernel-visible panic.
3. drivers/storage/nvmed/src/nvme/mod.rs: deleted two commented-out
match arms (lines 372-377 and 401-406) that contained
panic!("invalid queue ...") inside /* */ comments. The panics
were correctly disabled to avoid kernel crashes, but the
comments are stale and the queue-error path now silently
continues. Removing the dead comments so a future audit doesn't
resurrect them; the underlying issue (queue errors not
propagated) is tracked for a follow-up.
Found by the Round 13 audit (local/docs/3D-DESKTOP-COMPREHENSIVE-
PLAN.md §10).
Red Bear OS
c5b32f9f6b