| To: | "D. Stimits" <stimits@xxxxxxxxxx> |
|---|---|
| Subject: | Re: 2.4.19rc2 XFS oops trace |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Sat, 27 Jul 2002 23:52:56 +0100 |
| Cc: | "XFS: linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <3D431AA8.4010306@xxxxxxxxxx>; from stimits@xxxxxxxxxx on Sat, Jul 27, 2002 at 04:11:52PM -0600 |
| References: | <3D431AA8.4010306@xxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5.1i |
On Sat, Jul 27, 2002 at 04:11:52PM -0600, D. Stimits wrote:
> I do not know if this is related to XFS or not, perhaps someone could
> tell me if this needs to go elsewhere.
You have nvidia's binary-only driver loaded and this is the typical
nvidia oops. We get this reports about one time all two weeks on this
list :P
Steve, Eric, what do you think about installing the following patch
(adopted from Red Hat rawhide) in CVS?
--- linux/mm/page_alloc.c~ Thu Jul 4 16:33:28 2002
+++ linux/mm/page_alloc.c Thu Jul 4 16:33:28 2002
@@ -123,8 +123,12 @@
return;
if (page->buffers)
BUG();
- if (page->mapping)
+ if (page->mapping) {
+ printk(KERN_CRIT "Page has mapping still set. This is a serious
situation. However if you \n");
+ printk(KERN_CRIT "are using the NVidia binary only module
please report this bug to \n");
+ printk(KERN_CRIT "NVidia and not to the linux-xfs or linux
kernel mailinglists.\n");
BUG();
+ }
if (!VALID_PAGE(page))
BUG();
if (PageSwapCache(page))
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Evms-devel] Re: "Invalid client ID" after system lockup and subsequent reset ?, Seth Mos |
|---|---|
| Next by Date: | Re: 2.4.19rc2 XFS oops trace, D. Stimits |
| Previous by Thread: | 2.4.19rc2 XFS oops trace, D. Stimits |
| Next by Thread: | Re: 2.4.19rc2 XFS oops trace, Kjell Randa |
| Indexes: | [Date] [Thread] [Top] [All Lists] |