From: Lee Revell <rlrevell@joe-job.com>
To: Daniel Bonekeeper <thehazard@gmail.com>
Cc: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
Pavel Machek <pavel@ucw.cz>, Adrian Bunk <bunk@stusta.de>,
linux-kernel@vger.kernel.org
Subject: Re: Automatic Kernel Bug Report
Date: Mon, 10 Jul 2006 19:41:28 -0400 [thread overview]
Message-ID: <1152574888.19047.44.camel@mindpipe> (raw)
In-Reply-To: <e1e1d5f40607101505peb27581n729bcb14842d2956@mail.gmail.com>
On Mon, 2006-07-10 at 18:05 -0400, Daniel Bonekeeper wrote:
> That's a good example. Another example: a little while ago
> (http://lkml.org/lkml/2006/7/1/70) Daniel Drake from Gentoo was
> reporting a problem where page_mapcount(page) was getting negative. As
> it turned out, it was related with a nVidia proprietary driver that
> the machine was running. With the system, we just needed to search for
> "Eeek! page_mapcount(page) went negative! (-1)" on kernels 2.6.16.19
> (maybe too generic), and he would see that lots of people reporting
> that has, between other things, nVidia drivers running. It's already a
> clue on where to start looking for. The same applies for lots of other
> stuff.
That sounds backwards to me - any kernel bug reporting system should
immediately discard bug reports with the nvidia driver loaded, as such a
kernel is not debuggable.
Lee
next prev parent reply other threads:[~2006-07-10 23:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 8:45 Automatic Kernel Bug Report Daniel Bonekeeper
2006-07-09 9:45 ` Michal Piotrowski
2006-07-09 10:29 ` Daniel Bonekeeper
2006-07-09 12:58 ` Adrian Bunk
2006-07-09 18:46 ` Daniel Bonekeeper
2006-07-09 19:11 ` Adrian Bunk
2006-07-09 20:01 ` Daniel Bonekeeper
2006-07-09 20:19 ` Valdis.Kletnieks
2006-07-09 20:27 ` Daniel Bonekeeper
2006-07-10 8:11 ` Pavel Machek
2006-07-10 17:40 ` Daniel Bonekeeper
2006-07-10 17:59 ` Valdis.Kletnieks
2006-07-10 22:05 ` Daniel Bonekeeper
2006-07-10 23:41 ` Lee Revell [this message]
2006-07-11 1:15 ` Daniel Bonekeeper
2006-07-10 18:41 ` Horst von Brand
2006-07-10 21:34 ` Daniel Bonekeeper
2006-07-11 14:16 ` Horst von Brand
2006-07-09 20:24 ` Diego Calleja
2006-07-09 20:37 ` Daniel Bonekeeper
2006-07-09 22:19 ` Diego Calleja
2006-07-09 22:49 ` Daniel Bonekeeper
2006-07-09 20:25 ` Jesper Juhl
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=1152574888.19047.44.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=thehazard@gmail.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