From: Karsten Keil <kkeil@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Adam Belay <abelay@novell.com>,
greg@kroah.com,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] fix tulip suspend/resume
Date: Thu, 9 Jun 2005 10:27:10 +0200 [thread overview]
Message-ID: <20050609082710.GA9847@pingi3.kke.suse.de> (raw)
In-Reply-To: <20050609000402.GA2694@elf.ucw.cz>
Hi,
On Thu, Jun 09, 2005 at 02:04:02AM +0200, Pavel Machek wrote:
...
>
> > > You passed invalid argument; I see no reason why you should paper over
> > > it and risk continuing. This happens during system suspend; it is
> > > quite possible that user will not see your printk when machine powers
> > > off just after that; and remember that it will not be in syslog after
> > > resume.
> >
> > Crap. I don't think a BUG() makes any useful help neither in this place,
> > and when I locally turn PMSG_FREEZE to something sane I suddenly blow up
> > in there (and I wonder in how many other places).
>
> At least you can see & report that error... That would not be a case
> for simple printk.
>
Yes, but BUG() should not used for that, IMHO BUG() should be used only for
critical situation, in which you cannot do anything and here is danger to
lost data, I don't think this is the case here, but the BUG() will crash the
machine and so you might be loose data, which is not nice to do, for only to
request a report. Yes printk only is ignored by many people, but here are
always some, who will report it.
--
Karsten Keil
SuSE Labs
ISDN development
next prev parent reply other threads:[~2005-06-09 8:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 22:46 Karsten Keil
2005-06-07 0:04 ` Linus Torvalds
2005-06-07 2:50 ` Adam Belay
2005-06-07 3:34 ` Benjamin Herrenschmidt
2005-06-07 3:58 ` Adam Belay
2005-06-07 4:26 ` Benjamin Herrenschmidt
2005-06-07 5:34 ` Adam Belay
2005-06-07 5:50 ` Benjamin Herrenschmidt
2005-06-07 10:55 ` Karsten Keil
2005-06-07 20:58 ` Adam Belay
2005-06-08 0:26 ` Benjamin Herrenschmidt
2005-06-08 2:16 ` Adam Belay
2005-06-08 12:23 ` Pavel Machek
2005-06-08 23:00 ` Benjamin Herrenschmidt
2005-06-09 0:04 ` Pavel Machek
2005-06-09 0:38 ` Adam Belay
2005-06-09 10:51 ` Pavel Machek
2005-06-09 2:49 ` Nigel Cunningham
2005-06-09 8:27 ` Karsten Keil [this message]
2005-06-08 12:19 ` Pavel Machek
2005-06-08 6:39 ` Karsten Keil
2005-06-08 18:11 ` Davide Rossetti
2005-06-09 1:48 ` Adam Belay
2005-06-07 11:52 ` Stefan Seyfried
2005-06-07 2:15 ` Benjamin Herrenschmidt
2005-06-07 2:57 ` Adam Belay
2005-06-07 3:32 ` Benjamin Herrenschmidt
2005-06-07 3:42 ` Adam Belay
2005-06-07 4:29 ` Benjamin Herrenschmidt
2005-06-07 5:03 ` Adam Belay
2005-06-07 5:51 ` Nigel Cunningham
2005-06-07 5:55 ` Benjamin Herrenschmidt
2005-06-07 15:10 ` 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=20050609082710.GA9847@pingi3.kke.suse.de \
--to=kkeil@suse.de \
--cc=abelay@novell.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@osdl.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
Powered by JetHome