From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] softlockup in hacked 2.6.34 kernel
Date: Fri, 02 Jul 2010 13:55:41 -0700 [thread overview]
Message-ID: <4C2E524D.6080501@candelatech.com> (raw)
In-Reply-To: <4C2E4535.5050208@candelatech.com>
On 07/02/2010 12:59 PM, Ben Greear wrote:
> I'm doing a bit of hacking on ath9k, but I don't _think_ I did something
> to cause this. I'm just curious if someone has seen something similar.
>
> This was after rmmod and I had previously added a virtual wiphy before
> rmmod'ing it.
Nevermind..it appearantly was my fault...I had only coppied one of
the 3 ath9k.ko files over to the target system.
Sorry for the noise.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2010-07-02 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 19:59 [ath9k-devel] softlockup in hacked 2.6.34 kernel Ben Greear
2010-07-02 20:55 ` Ben Greear [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=4C2E524D.6080501@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@lists.ath9k.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