All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ludootje <ludootje@linux.be>
To: linux-kernel@vger.kernel.org
Subject: Re: what's an OOPS
Date: 08 Mar 2003 19:37:48 +0100	[thread overview]
Message-ID: <1047148667.1428.1.camel@libranet> (raw)
In-Reply-To: <200303081654.h28Gskpk002027@81-2-122-30.bradfords.org.uk>

Op za 08-03-2003, om 17:54 schreef John Bradford:
> > > The number of the oops, (I.E. whether it was the first, second, third,
> > > etc, starting with 0000).
> > 
> > Urban myth (at least on i386). The "Oops:" part can be decoded on i386 as,
> > 
> >  *      bit 0 == 0 means no page found, 1 means protection fault
> >  *      bit 1 == 0 means read, 1 means write
> >  *      bit 2 == 0 means kernel, 1 means user-mode
> 
> Interesting - I wasn't aware of that.
> 
> Maybe we should note this in Documentation/oops-tracing.txt?
> 
> Infact, overall there must be quite a lot that isn't documented at
> all, except in this mailing list's archives - I think an overhaul of
> Documentation/* is more than slightly overdue...
> 
> John.

Thanks a lot for the very good explanatiosn everyone, I really
appreciate it!

Thanks,
Ludootje

-- 

 The Grasshoppers' Linux Journal - a free, online distributed magazine about GNU/Linux / Open Source / ... oriented towards newbies. Check it out @ http://ghj.sunsite.dk !


      reply	other threads:[~2003-03-08 18:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-08 13:47 what's an OOPS Ludootje
2003-03-08 14:05 ` bert hubert
2003-03-08 14:20 ` John Bradford
2003-03-08 16:01   ` Szakacsits Szabolcs
2003-03-08 16:54     ` John Bradford
2003-03-08 18:37       ` Ludootje [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=1047148667.1428.1.camel@libranet \
    --to=ludootje@linux.be \
    --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 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.