From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Anthony Russo., a.k.a. " Stupendous Man <anthony.russo@verizon.net>
Cc: Willy Tarreau <willy@w.ods.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 BUG in page_alloc.c:91
Date: 08 Aug 2002 21:04:03 +0100 [thread overview]
Message-ID: <1028837043.28883.75.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <3D52B7D3.2000209@verizon.net>
On Thu, 2002-08-08 at 19:26, Anthony Russo., a.k.a. Stupendous Man
wrote:
> It's a national semi chip ... the module name is natsemi.o,
> and indeed I am using it without incident now in place of fa312.o.
>
> All of my modules are now GPL according to modinfo, so if the problem
> reoccurs now that I've rebooted we'll know if it's real.
Not only is it real, but I have every line of code on your box in front
of me if it does happen with that module. That helps no end in bug
hunting
next prev parent reply other threads:[~2002-08-08 18:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 2:45 Anthony Russo., a.k.a. Stupendous Man
2002-08-08 2:50 ` Rik van Riel
2002-08-08 2:54 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 7:55 ` Willy Tarreau
2002-08-08 15:42 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 19:43 ` Alan Cox
2002-08-08 18:26 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 20:04 ` Alan Cox [this message]
2002-08-08 12:38 ` Alan Cox
2002-08-08 12:19 ` [OT] " Andreas Steinmetz
2002-08-08 13:41 ` Alan Cox
2002-08-09 9:14 ` Keith Owens
2002-08-08 15:45 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 16:07 ` Willy Tarreau
2002-08-08 16:15 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 15:56 ` 2.4.19 BUG in page_alloc.c:91 -- NOT NVidia driver! Anthony Russo., a.k.a. Stupendous Man
2002-08-14 15:19 ` 2.4.19 BUG in page_alloc.c:91 Ingo Saitz
2002-08-27 12:47 Salvador Eduardo Tropea
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=1028837043.28883.75.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=anthony.russo@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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
all inboxes | Powered by JetHome®