All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug McNaught <doug@mcnaught.org>
To: Marc Koschewski <marc@osknowledge.org>
Cc: Kyle Moffett <mrmacman_g4@mac.com>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Linux-LKLM <linux-kernel@vger.kernel.org>
Subject: Re: [BUG GIT] Unable to handle kernel paging request at virtual address e1380288
Date: Sat, 11 Feb 2006 10:39:17 -0500	[thread overview]
Message-ID: <87psltsy56.fsf@asmodeus.mcnaught.org> (raw)
In-Reply-To: <20060211152930.GC5721@stiffy.osknowledge.org> (Marc Koschewski's message of "Sat, 11 Feb 2006 16:29:30 +0100")

Marc Koschewski <marc@osknowledge.org> writes:

> But the trace I sent didn't (directly) do any memory allocation so
> the case was clear to me.
>
> From a developers point of view I totally agree that doing some bad
> code 'here' might crash us 'there'. But the backtrace didn't look
> like this to me...

You have no idea what might have happened a second ago, or a minute
ago, or five minutes ago.  Corrupted memory is like a
time-bomb--things don't always break right away.

-Doug

  reply	other threads:[~2006-02-11 15:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10 21:41 [BUG GIT] Unable to handle kernel paging request at virtual address e1380288 Marc Koschewski
2006-02-10 22:25 ` Alexey Dobriyan
2006-02-10 22:42   ` Marc Koschewski
2006-02-11  9:01     ` Kyle Moffett
2006-02-11 15:10       ` Marc Koschewski
2006-02-11 15:19         ` Doug McNaught
2006-02-11 15:29           ` Marc Koschewski
2006-02-11 15:39             ` Doug McNaught [this message]
2006-02-11 21:10               ` Andrew Morton
2006-02-11 22:54                 ` Carlos Martín

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=87psltsy56.fsf@asmodeus.mcnaught.org \
    --to=doug@mcnaught.org \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@osknowledge.org \
    --cc=mrmacman_g4@mac.com \
    /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.