public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathias Klein <ma_klein@gmx.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: oops in kernel 2.6.15-rc6
Date: Wed, 28 Dec 2005 15:55:03 +0100	[thread overview]
Message-ID: <20051228145502.GB9777@sidney> (raw)
In-Reply-To: <43B2A122.7030203@thinrope.net>

[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

On Wed, Dec 28, 2005 at 11:28:50PM +0900, Kalin KOZHUHAROV wrote:
> Mathias Klein wrote:
> > Hello all,
> > 
> > [please CC me on replies, I'm not subscribed to this list]
> > 
> > I had this following kernel oops while compiling a new kernel. 
> > 
> > Dec 27 19:02:00 sidney kernel: [14896.995613] Unable to handle kernel paging request at virtual address 76f7104d
> > Dec 27 19:02:00 sidney kernel: [14896.995665]  printing eip:
> > Dec 27 19:02:00 sidney kernel: [14896.995682] c013a392
> > Dec 27 19:02:00 sidney kernel: [14896.995692] *pde = 00000000
> > Dec 27 19:02:00 sidney kernel: [14896.995711] Oops: 0002 [#1]
> 
> I might be wrong, but that is the second oops for this run, probably the first [#0] is more
> interesting...

Probably yes but there is no [#0] Oops in the logs.
(Indeed I do have another [#1] Oops in another run with that kernel without
an [#0] Oops)

Mathias

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-12-28 14:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-28 13:50 oops in kernel 2.6.15-rc6 Mathias Klein
2005-12-28 14:28 ` Kalin KOZHUHAROV
2005-12-28 14:55   ` Mathias Klein [this message]
2005-12-28 15:15     ` Pekka Enberg
2005-12-29  7:50       ` Mathias Klein
2005-12-28 16:28     ` Randy.Dunlap
2005-12-30 22:37 ` Adrian Bunk
2006-01-02 12:28   ` Mathias Klein

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=20051228145502.GB9777@sidney \
    --to=ma_klein@gmx.de \
    --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