Matheus Izvekov wrote:
On 5/24/06, Alexander E. Patrakov <[email protected]> wrote:
Jon Smirl wrote:
> You can't change the mode, instead you have to track it and use the
> one that is already set.
OK, this doesn't change my other point: use in-kernel text output
facility for
panics only.
It would be a good idea to allow oopses to be shown too. For example,
your main disk controller driver may oops, and then you have no way to
tell what happened, because if you try to run dmesg it may deadlock,
and obviously the oops message wont be logged either.
So a BSOD which allows you to hit enter to continue after an oops is
not a bad idea.
Now suppose this.
The kernel has to save the video memory contents somewhereto restore it after
pressing Enter. This may swap something out. Whoops, swap is on that failed disk.
Or: lock the memory in advance, to avoid the use of swap. But this is not better
than doing the same thing from a userspace application that shows a pop-up
ballon with the contents of this oops. And it won't be affected by a disk
failure, because it has everything already in memory.
--
Alexander E. Patrakov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
