From: Brad Laue <brad@brad-x.com>
To: James Morris <jmorris@intercode.com.au>
Cc: Marc Giger <gigerstyle@gmx.ch>,
jt@hpl.hp.com, linux-kernel@vger.kernel.org,
breed@users.sourceforge.net, achirica@users.sourceforge.net
Subject: Re: Cisco Aironet 340 oops with 2.4.20
Date: Sun, 02 Mar 2003 12:01:34 -0500 [thread overview]
Message-ID: <3E6238EE.7050802@brad-x.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303022210400.6149-100000@blackbird.intercode.com.au>
James Morris wrote:
>The latter two are still happening with a tainted kernel. Are you able to
>generate the crash if these modules have never been loaded?
>
>
>- James
>
>
I'm not sure I follow - the NVdriver module had not been loaded at all
for the other two. How is the kernel tainted?
Brad
--
// -- http://www.BRAD-X.com/ -- //
next prev parent reply other threads:[~2003-03-02 16:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 11:53 Cisco Aironet 340 oops with 2.4.20 Marc Giger
2003-02-13 0:18 ` Tim Pepper
2003-02-13 0:21 ` Jean Tourrilhes
2003-02-13 2:16 ` Tim Pepper
2003-02-13 2:18 ` Jean Tourrilhes
2003-02-13 6:47 ` Marc Giger
2003-02-13 17:20 ` Tim Pepper
2003-02-13 0:54 ` Tomas Szepe
2003-02-13 6:57 ` Marc Giger
2003-02-28 21:46 ` Brad Laue
2003-03-01 21:10 ` Marc Giger
2003-03-01 23:27 ` Brad Laue
2003-03-01 23:54 ` James Morris
2003-03-02 0:32 ` Brad Laue
2003-03-02 11:13 ` James Morris
2003-03-02 17:01 ` Brad Laue [this message]
2003-03-02 19:11 ` Marc Giger
2003-03-02 22:14 ` achirica
2003-03-12 13:54 ` Marc Giger
2003-03-15 2:58 ` Tim Pepper
2003-03-04 4:52 ` Tim Pepper
2003-03-01 17:14 ` airo.o + kfree_skb crash - 2.4.20 Brad Laue
2003-03-15 18:11 Cisco Aironet 340 oops with 2.4.20 Thomas Hood
2003-03-17 0:33 ` Tim Pepper
2003-03-17 1:28 ` Javier Achirica
2003-03-17 14:29 ` Marc Giger
2003-03-18 1:46 ` Tim Pepper
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=3E6238EE.7050802@brad-x.com \
--to=brad@brad-x.com \
--cc=achirica@users.sourceforge.net \
--cc=breed@users.sourceforge.net \
--cc=gigerstyle@gmx.ch \
--cc=jmorris@intercode.com.au \
--cc=jt@hpl.hp.com \
--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).