![]() | ||||||||||
Messages in this thread |
>
> On Mon, 19 Jan 1998, MOLNAR Ingo wrote:
>
> > an OOPS 100% tells you where and why the oops happened. Now, to determine
> > what the real reason for the oops was is quite complex, and in many cases
> > a crashdump doesnt help much. I would say the existance of a crashdump
> > hinders development more than the nonexistance of it ...
>
> My problem with OOPs's is that usually, when one happens.. it is > 25
> lines, and scrolls off the screen before the machine is at a dead halt. Of
> course, when this happens, that oops sure isn't going to be written to the
> logs.
A solution for this is called serial console with some logging facility on
the other end.
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
Ultralinux - first 64bit OS to take full power of the UltraSparc
Linux version 2.0.32 on a sparc machine (291.64 BogoMips).
___________________________________________________________________
| |||||||||
| Last update: 2005-03-22 12:41 [from the cache] ©2003-2008 | ||||||||||