From: Steven Barnhart <sbarn03@softhome.net>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.54] OOPS: unable to handle kernel paging request
Date: 03 Jan 2003 16:05:53 -0500 [thread overview]
Message-ID: <1041627959.1862.2.camel@sbarn.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0301031046100.25684-100000@coffee.psychology.mcmaster.ca>
On Fri, 2003-01-03 at 10:48, Mark Hahn wrote:
> it's not very meaningful: some part of the kernel tried dereferencing
> a null pointer (as it happens, with a negative offset, such as you might
> expect from a variable sitting in the stack).
> the negativeness is not surprising, and the value of the offset would
> depend on your cpu/compiler/config.
Well I have a Intel Celeron 1.06 GHz (i686). 384MB ram, gcc 3.2 (redhat
8 release). I don't really know how to decode it since I have no serial
console hookups...anything paticualr I could get from the oops report
during bootup? i.e. what sections to copy?
--
Steven
sbarn03@softhome.net
GnuPG Fingerprint: 9357 F403 B0A1 E18D 86D5 2230 BB92 6D64 D516 0A94
next parent reply other threads:[~2003-01-03 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0301031046100.25684-100000@coffee.psychology.mcmaster.ca>
2003-01-03 21:05 ` Steven Barnhart [this message]
2003-01-05 9:25 ` [2.5.54 - Oops] CPUFreq [Was: Re: [2.5.54] OOPS: unable to handle kernel paging request] Paul Rolland
2003-01-05 10:43 ` Paul Rolland
2003-01-05 16:47 ` Steven Barnhart
2003-01-03 8:33 [2.5.54] OOPS: unable to handle kernel paging request Aniruddha M Marathe
2003-01-03 9:28 ` Paul Rolland
2003-01-03 15:00 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2003-01-02 17:18 Linux v2.5.54 Adrian Bunk
2003-01-02 17:31 ` Jaroslav Kysela
2003-01-02 13:26 ` Adam Belay
2003-01-03 0:08 ` [2.5.54] OOPS: unable to handle kernel paging request Steven Barnhart
2003-01-03 6:49 ` Paul Rolland
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=1041627959.1862.2.camel@sbarn.net \
--to=sbarn03@softhome.net \
--cc=hahn@physics.mcmaster.ca \
--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