From: Samium Gromoff <_deepfire@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: OOPS handling proposal
Date: Thu, 13 Sep 2001 06:11:40 +0000 (UTC) [thread overview]
Message-ID: <200109130611.f8D6BfV01791@vegae.deep.net> (raw)
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?
cheers, Sam
next reply other threads:[~2001-09-13 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 6:11 Samium Gromoff [this message]
2001-09-13 6:12 ` Andreas Dilger
2001-09-13 13:45 ` Samium Gromoff
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=200109130611.f8D6BfV01791@vegae.deep.net \
--to=_deepfire@mail.ru \
--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®