| To: | Federico Sevilla III <jijo@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Kernel BUG at page_alloc.c:91 (2.4.19-rc2-xfs) |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Sun, 28 Jul 2002 10:59:17 +0100 |
| Cc: | Linux-XFS Mailing List <linux-xfs@xxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx> |
| In-reply-to: | <20020728082542.GC1265@leathercollection.ph>; from jijo@free.net.ph on Sun, Jul 28, 2002 at 04:25:42PM +0800 |
| Mail-followup-to: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, Federico Sevilla III <jijo@xxxxxxxxxxx>, Linux-XFS Mailing List <linux-xfs@xxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx> |
| References: | <20020728082542.GC1265@leathercollection.ph> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5.1i |
On Sun, Jul 28, 2002 at 04:25:42PM +0800, Federico Sevilla III wrote: > Hi everyone, > > I apologize for sending this to both the Linux kernel mailing list as > well as the Linux-XFS mailing list. I am sending this to the lkml > because it's a kernel bug report. I'm sending this to the Linux-XFS > mailing list because I do not know if "try_to_free_buffers+130/240" in > the Call Trace has anything to do with changes that the XFS team has > done on the Linux kernel. Let me guess: you're using nvidia's binary only module? if so please go and complain to them, this oops is characteristic for their buggy driver. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 2.4.19rc2 XFS oops trace, Knut J Bjuland |
|---|---|
| Next by Date: | Re: Kernel BUG at page_alloc.c:91 (2.4.19-rc2-xfs), Federico Sevilla III |
| Previous by Thread: | Re: Kernel BUG at page_alloc.c:91 (2.4.19-rc2-xfs), Federico Sevilla III |
| Next by Thread: | Re: Kernel BUG at page_alloc.c:91 (2.4.19-rc2-xfs), D. Stimits |
| Indexes: | [Date] [Thread] [Top] [All Lists] |