From: Dave Jones <davej@codemonkey.org.uk>
To: Kendrick Hamilton <hamilton@sedsystems.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux crashes after installing a module. (Please CC hamilton@sedsystems.ca)
Date: Tue, 20 May 2003 23:18:59 +0100 [thread overview]
Message-ID: <20030520221859.GA8567@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0305201601040.2041-100000@sw-55.sedsystems.ca>
On Tue, May 20, 2003 at 04:07:07PM -0600, Kendrick Hamilton wrote:
> Hi,
> We are developping a module for a custom built card. The module
> installs fine on some computers and not on others. All computers are
> running 2.4.18 or 2.4.20 kernel. Here is a dump of installing the module
> and linux crashing. The module is tainting the kernel (I plan on GPLing
> the module and if you want code for it, I can send it to you, I just don't
> know how to flag it as GPLed).
The tainting is easily fixed with a one liner..
MODULE_LICENSE("GPL");
Why your code crashes however, is impossible for anyone to tell without
seeing the code.
Dave
prev parent reply other threads:[~2003-05-20 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 22:07 Linux crashes after installing a module. (Please CC hamilton@sedsystems.ca) Kendrick Hamilton
2003-05-20 22:18 ` Dave Jones [this message]
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=20030520221859.GA8567@suse.de \
--to=davej@codemonkey.org.uk \
--cc=hamilton@sedsystems.ca \
--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 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.