[lkml]   [2001]   [Sep]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: OOPS handling proposal
"  Andreas Dilger wrote:"
> On Sep 13, 2001 06:11 +0000, Samium Gromoff wrote:
> > Hello folks!
> > People most likely needs first oops most of the time, so
> > it would be great to make a kernel boot option to stop after
> > first oops, so in the situations when its neede life can be made easy.
> > Actually afaics this is being done each time by hand, so
> > panic() in BUG() as Rik proposed would be nice.
> > What do you folks think?
> Absolutely NOT. If you panic() in BUG() then you DO have to copy the oops
> by hand each time, whereas the normal situation is that you can keep
> running after an oops - to decode it, see what the symptoms are, check
> memory, etc.
Hmm... I propose to make it a boot option.
Else sometimes you wont be able to retrieve info at all, as like
in the situation i have right now: oops in kupdated which i even
cant post and it remains there all 2.4.8 and 2.4.9.

Cheers, Sam

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:03    [W:0.112 / U:1.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site