From: Martin Michlmayr <tbm@cyrius.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Pavel Machek <pavel@suse.cz>,
rmk+lkml@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Convert serial_core oopses to BUG_ON
Date: Tue, 28 Feb 2006 22:01:28 +0000 [thread overview]
Message-ID: <20060228220128.GA4254@unjust.cyrius.com> (raw)
In-Reply-To: <20060228101713.6fd44027.akpm@osdl.org>
* Andrew Morton <akpm@osdl.org> [2006-02-28 10:17]:
> > It will oops in hard-to-guess, place, anyway.
> Will it? Where? Unfixably?
http://www.linux-mips.org/archives/linux-mips/2006-02/msg00241.html is
one example we just had on MIPS. On SGI IP22, using the serial
console, you'd get the following on shutdown:
The system is going down for reboot NOW!
INIT: Sending processes the TERM signal
INIT: Sending proces
and then nothing at all. I'd never have suspected the serial driver,
had not users reported that the machine shutdowns properly when using
the framebuffer.
For the record, I don't mind whether it's BUG_ON or WARN_ON, but I
just wanted to give this as an example of an "oops in hard-to-guess,
place".
--
Martin Michlmayr
tbm@cyrius.com
next prev parent reply other threads:[~2006-02-28 22:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 10:05 [PATCH] Convert serial_core oopses to BUG_ON Russell King
2006-02-26 10:14 ` Andrew Morton
2006-02-26 10:18 ` Nick Piggin
2006-02-26 18:17 ` Russell King
2006-02-26 20:00 ` Russell King
2006-02-27 14:13 ` Pavel Machek
2006-02-28 18:17 ` Andrew Morton
2006-02-28 22:01 ` Martin Michlmayr [this message]
2006-02-28 23:32 ` Andrew Morton
2006-03-01 17:10 ` Russell King
2006-03-01 19:47 ` Pavel Machek
2006-03-01 22:32 ` Andrew Morton
[not found] <5Kr1a-6MF-15@gated-at.bofh.it>
[not found] ` <5KraE-6XP-15@gated-at.bofh.it>
[not found] ` <5KyFv-RL-15@gated-at.bofh.it>
2006-02-26 22:34 ` Karol Kozimor
2006-02-26 22:41 ` Russell King
[not found] <20060227162827.GC2389@ucw.cz>
2006-03-01 19:00 ` Pavel Machek
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=20060228220128.GA4254@unjust.cyrius.com \
--to=tbm@cyrius.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rmk+lkml@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.