From: Samium Gromoff <_deepfire@mail.ru>
To: adilger@turbolabs.com (Andreas Dilger)
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS handling proposal
Date: Thu, 13 Sep 2001 13:45:09 +0000 (UTC) [thread overview]
Message-ID: <200109131345.f8DDj9c30736@vegae.deep.net> (raw)
In-Reply-To: <20010913001218.E1541@turbolinux.com> from "Andreas Dilger" at Sep 13, 2001 12:12:18 AM
" 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
prev parent reply other threads:[~2001-09-13 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 6:11 Samium Gromoff
2001-09-13 6:12 ` Andreas Dilger
2001-09-13 13:45 ` Samium Gromoff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200109131345.f8DDj9c30736@vegae.deep.net \
--to=_deepfire@mail.ru \
--cc=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®