lkml.org 
[lkml]   [2006]   [Feb]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [BUG GIT] Unable to handle kernel paging request at virtual address e1380288
From
Date
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-02-11 16:41    [W:0.474 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site