public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexandre P. Nunes" <alex@PolesApart.dhs.org>
To: Markus Schoder <markus_schoder@yahoo.de>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.19-pre10-ac2 bug in page_alloc.c:131
Date: Mon, 24 Jun 2002 09:23:19 -0300	[thread overview]
Message-ID: <3D170F37.7000900@PolesApart.dhs.org> (raw)
In-Reply-To: 200206231945.27717.markus_schoder@yahoo.de

Markus Schoder wrote:

>Hi Alexandre,
>
>you are using the proprietary nVidia module (NVdriver), so you would have
>to address any kernel problems to nVidia since they are the ones who have the
>source.
>
>However lots of people (including myself) have seen the same problem when 
>using the nVidia module.  For me it went away when upgrading to the 1.0-2960 
>drivers.  If you haven't done so yet this would be the first thing to try.
>
>Hope this helps,
>Markus
>
>  
>
I'm already using the 1.0-2960 version, and that's the version in the 
report. It's possible that the NVdriver module is the cause of the 
problem, but the bug spots in kernel's vm, in a place which it's no 
supposed to, at the point I understand. So, or the module does something 
very ugly, or the kernel really have a bug, or yet it's nothing related 
to the nvdriver. Unfortunately, the backtrace don't help me figuring 
that out, since I'm no vm expert, but perhaps someone will. I may 
attempt to forward this to Nvidia folks, but reporting a bug which only 
spotted once and in a "pre" series kernel may hurt their feelings...

Thanks,

Alexandre



       reply	other threads:[~2002-06-24 12:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200206231945.27717.markus_schoder@yahoo.de>
2002-06-24 12:23 ` Alexandre P. Nunes [this message]
2002-06-24 14:17   ` PROBLEM: 2.4.19-pre10-ac2 bug in page_alloc.c:131 Alan Cox
2002-06-24 15:06     ` Alexandre P. Nunes
2002-06-24 15:04       ` David S. Miller
2002-06-24 16:47         ` Alexandre P. Nunes
2002-07-01  2:18         ` Pavel Machek
2002-07-02  1:39           ` Horst von Brand
2002-07-02 16:29         ` Bill Davidsen
2002-07-02 17:04           ` Alexandre P. Nunes
2002-07-02 23:25             ` Matthias Andree
2002-06-24 15:18       ` Zwane Mwaikambo
2002-06-23  1:13 Alexandre Pereira Nunes
2002-06-23 11:07 ` Diego Calleja
2002-06-23 11:40   ` Alexandre Pereira Nunes
2002-06-26 20:47 ` William Lee Irwin III
2002-06-26 21:00   ` Bongani
2002-06-26 21:45     ` khromy
2002-06-26 21:54     ` Robert Love
2002-06-26 22:12       ` Bongani
2002-06-26 22:08         ` Robert Love
2002-06-27  0:54       ` William Lee Irwin III
2002-06-27 15:40         ` Robert Love
2002-06-27 15:47           ` William Lee Irwin III
2002-06-27 18:29             ` Alexandre P. Nunes
2002-06-27 18:31               ` Robert Love
2002-06-27 18:53                 ` Alexandre P. Nunes
2002-06-27 20:05                   ` J Sloan

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=3D170F37.7000900@PolesApart.dhs.org \
    --to=alex@polesapart.dhs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus_schoder@yahoo.de \
    /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