From: Federico Sevilla III <jijo@free.net.ph>
To: Linux-XFS Mailing List <linux-xfs@oss.sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel BUG at page_alloc.c:91 (2.4.19-rc2-xfs)
Date: Sun, 28 Jul 2002 18:02:22 +0800 [thread overview]
Message-ID: <20020728100222.GF1265@leathercollection.ph> (raw)
In-Reply-To: <20020728090336.GD1265@leathercollection.ph>
On Sun, Jul 28, 2002 at 05:03:36PM +0800, Federico Sevilla III wrote:
> Ah, yes, I had forgotten to do that. I hadn't realized that the same
> requirement for reporting oopses held for reporting kernel BUGs.
I had further forgotten to mention that I have the NVidia 2960 binary
module loaded, and that D. Stimits just posted a message on the
Linux-XFS mailing list about a kernel BUG report also on page_alloc.c:91
on a similar 2.4.19-rc2-xfs CVS snapshot, also with the NVdriver module
loaded.
Kjell Randa noted that an upgrade to version 2960 fixed things for him,
and Kjell Randa added that removing "agpgart" support fixes things. I
have agpgart support for my VIA chipset, and it's possible that this is
clashing with the NVdriver.
I realize that I may have wasted people's time, since the NVidia driver
is closed-source binary-only, and my system is tainted. I apologize for
this but hope that my messages will at least help some other people who
may run into this problem and will search the archives.
I am upgrading to 2.4.19-rc3-xfs now, and will remove agpgart support
from the kernel. I am keeping my fingers crossed.
--> Jijo
--
Federico Sevilla III : <http://jijo.free.net.ph/>
Network Administrator : The Leather Collection, Inc.
GnuPG Key ID : 0x93B746BE
next prev parent reply other threads:[~2002-07-28 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 8:25 Kernel BUG at page_alloc.c:91 (2.4.19-rc2-xfs) Federico Sevilla III
[not found] ` <20020728084718.GW1548@niksula.cs.hut.fi>
2002-07-28 9:03 ` Federico Sevilla III
2002-07-28 10:02 ` Federico Sevilla III [this message]
2002-07-28 9:59 ` Christoph Hellwig
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=20020728100222.GF1265@leathercollection.ph \
--to=jijo@free.net.ph \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.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.