From: "Carlos Martín" <carlos@cmartin.tk>
To: Andrew Morton <akpm@osdl.org>
Cc: Doug McNaught <doug@mcnaught.org>,
marc@osknowledge.org, mrmacman_g4@mac.com, adobriyan@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [BUG GIT] Unable to handle kernel paging request at virtual address e1380288
Date: Sat, 11 Feb 2006 23:54:02 +0100 [thread overview]
Message-ID: <200602112354.03198.carlos@cmartin.tk> (raw)
In-Reply-To: <20060211131008.55f19bb6.akpm@osdl.org>
On Saturday 11 February 2006 22:10, Andrew Morton wrote:
> Doug McNaught <doug@mcnaught.org> wrote:
> > 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.
> >
>
> Probability this bug was caused by the nvidia module: 0.1%
> Probability this bug was caused by USB or SCSI: 99.9%
>
> SCSI and USB device management remain quite buggy and we need all the help
> we can get in finding and fixing these problems.
I once had a PCI probe function OOPS with the nvidia module loaded. Previous
run was alright, and rebooting with exact same setup worked the next time and
never failed again for the time I was using the nvidia module on that
computer.
I can't be positive that it was the nvidia module, but the probability of it
having to do with it is quite high. It at least triggered something.
cmn
--
Carlos Martín Nieto | http://www.cmartin.tk
Hobbyist programmer |
prev parent reply other threads:[~2006-02-11 22:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 21:41 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
2006-02-11 21:10 ` Andrew Morton
2006-02-11 22:54 ` Carlos Martín [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=200602112354.03198.carlos@cmartin.tk \
--to=carlos@cmartin.tk \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=doug@mcnaught.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®