From: David Raufeisen <david@fortyoz.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.3pre1: kernel BUG at page_alloc.c:73!
Date: Sat, 10 Mar 2001 23:12:50 -0800 [thread overview]
Message-ID: <20010310231250.A5391@fortyoz.org> (raw)
In-Reply-To: <20010310221427.A5415@fortyoz.org> <15189.984293663@ocs3.ocs-net>
In-Reply-To: <15189.984293663@ocs3.ocs-net>; from "Keith Owens" on Sunday, 11 March 2001, at 17:54:23 (+1100)
Well, the kernel module is open source..
On Suday, 11 March 2001, at 17:54:23 (+1100),
Keith Owens wrote:
> On Sat, 10 Mar 2001 22:14:27 -0800,
> David Raufeisen <david@fortyoz.org> wrote:
> >Mar 10 21:34:30 prototype kernel: [free_pages+36/48] [NVdriver:osFreeContigPages+79/84] [<cda1d004>] [NVdriver:RmTeardownAGP+156/176] [<cfa70000>] [NVdriver:nv_devices+0/384] [NVdriver:nvExtEscape+2888/3100] [<
>
> Bug caused by binary only driver. Complain to nvidia, not linux-kernel.
--
David Raufeisen <david@fortyoz.org>
Cell: (604) 818-3596
next prev parent reply other threads:[~2001-03-11 7:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-11 6:14 2.4.3pre1: kernel BUG at page_alloc.c:73! David Raufeisen
2001-03-11 6:54 ` Keith Owens
2001-03-11 7:12 ` David Raufeisen [this message]
2001-03-11 7:19 ` Keith Owens
2001-03-11 7:25 ` David Raufeisen
2001-03-11 14:28 ` Alan Cox
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=20010310231250.A5391@fortyoz.org \
--to=david@fortyoz.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).