All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian McMenamin <adrian@newgolddream.dyndns.info>
To: linux-sh@vger.kernel.org
Subject: Re: oops I get on booting
Date: Sun, 08 Feb 2009 17:29:38 +0000	[thread overview]
Message-ID: <1234114178.6673.1.camel@localhost.localdomain> (raw)
In-Reply-To: <1233967281.6893.3.camel@localhost.localdomain>

On Sat, 2009-02-07 at 00:41 +0000, Adrian McMenamin wrote:
> I am getting this error every so often on boot -as it is not every time
> it seems to be a race condition of some sort. With the latest git the
> frequency of the problem seems to have increased, but it has been there
> for a while.
> 
> Anybody have any suggestions as to what it might be? Naturally I'd
> suspect my own code, though nothing I've written is in the stack:
> 
> [   42.893155] Unable to handle kernel NULL pointer dereference at virtual address 0000000c
> [   42.909100] pc = 8c0874ea

I think I've identified the source of this - some memory corruption in
my code that was causing oopses elsewhere. A patch to follow.


      reply	other threads:[~2009-02-08 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07  0:41 oops I get on booting Adrian McMenamin
2009-02-08 17:29 ` Adrian McMenamin [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=1234114178.6673.1.camel@localhost.localdomain \
    --to=adrian@newgolddream.dyndns.info \
    --cc=linux-sh@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.