From: Ingo Molnar <mingo@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Keith Owens <kaos@ocs.com.au>,
Nathan Walp <faceprint@faceprint.com>,
Hans Grobler <grobh@sun.ac.za>, <linux-kernel@vger.kernel.org>
Subject: Re: Oops in 2.4.0-ac5
Date: Wed, 10 Jan 2001 17:41:06 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.30.0101101737240.30973-100000@devserv.devel.redhat.com> (raw)
In-Reply-To: <E14GTro-00019E-00@the-village.bc.nu>
On Wed, 10 Jan 2001, Alan Cox wrote:
> > it. I could never persuade Ingo to use wrmsr_eio() and check the
> > return code, maybe this will change his mind. Extract from kdb v1.7.
>
> I have a patch from Ingo to fix this one properly. Its just getting tested
i prefer clear oopses and bug reports instead of ignoring them. A failed
MSR write is not something to be taken easily. MSR writes if fail mean
that there is a serious kernel bug - we want to stop the kernel and
complain ASAP. And correct code will be much more readable that way.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-10 22:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 20:00 Nathan Walp
2001-01-10 20:17 ` Hans Grobler
2001-01-10 20:23 ` Nathan Walp
2001-01-10 20:48 ` Hans Grobler
2001-01-10 21:00 ` Nathan Walp
2001-01-10 22:29 ` Keith Owens
2001-01-10 22:37 ` Alan Cox
2001-01-10 22:41 ` Ingo Molnar [this message]
2001-01-11 11:15 ` David Woodhouse
2001-01-11 11:41 ` Ingo Molnar
2001-01-11 12:56 Mikael Pettersson
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=Pine.LNX.4.30.0101101737240.30973-100000@devserv.devel.redhat.com \
--to=mingo@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=faceprint@faceprint.com \
--cc=grobh@sun.ac.za \
--cc=kaos@ocs.com.au \
--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®