linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Vasanthakumar Thiagarajan <vasanth@Atheros.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k doesn't clean up virtual wifis on rmmod, and crashes.
Date: Sat, 03 Jul 2010 09:34:09 -0700	[thread overview]
Message-ID: <4C2F6681.7070202@candelatech.com> (raw)
In-Reply-To: <20100703070259.GA15479@vasanth-laptop>

On 07/03/2010 12:02 AM, Vasanthakumar Thiagarajan wrote:
> On Sat, Jul 03, 2010 at 11:56:14AM +0530, Ben Greear wrote:
>> It seems to me that in 2.6.34, there is no code to clean up
>> virtual wiphys in ath9k on rmmod.  Also, ath9k mailing list
>> is returning error about mis-configured DNS server.
>>
>> This is with un-modified ath9k driver and is repeatable
>> every time on my system (crash is often different, but
>> it always crashes very quickly).
>>
>> [root@atom ~]# echo add=5>  /debug/ath9k/phy1/wiphy
>> -bash: /debug/ath9k/phy1/wiphy: No such file or directory
>> [root@atom ~]# echo add=5>  /debug/ath9k/phy0/wiphy
>> Jul  2 23:22:19 atom kernel: phy1: Selected rate control algorithm 'ath9k_rate_control'
>> [root@atom ~]# Jul  2 23:22:19 atom kernel: ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> rmmod ath9k
>> Jul  2 23:22:24 atom kernel: ath9k 0000:05:00.0: PCI INT A disabled
>> Jul  2 23:22:24 atom kernel: ath9k: Driver unloaded
>> [root@atom ~]# BUG: spinlock bad magic on CPU#1, iw/2877
>>    lock: f8a476c0, .magic: 00000000, .owner:<none>/-1, .owner_cpu: 0
>> Pid: 2877, comm: iw Not tainted 2.6.34 #7
>> Call Trace:
>>    [<c0730e34>] ? printk+0xf/0x13
>>    [<c05710d6>] spin_bug+0x7b/0x86
>>    [<c0440b76>] ? delayed_work_timer_fn+0x0/0x30
>>    [<c0571171>] do_raw_spin_lock+0x1e/0x125
>>    [<c042f91e>] ? scheduler_tick+0xd6/0x1c9
>>    [<c0440b76>] ? delayed_work_timer_fn+0x0/0x30
>>    [<c0732a6d>] _raw_spin_lock_irqsave+0x1b/0x20
>>    [<c0440b59>] __queue_work+0x12/0x2f
>>    [<c0440b76>] ? delayed_work_timer_fn+0x0/0x30
>>    [<c0440ba4>] delayed_work_timer_fn+0x2e/0x30
>>
>> I'm new to hacking on this driver..but would love to test
>> patches, and if someone wants to suggest a good point in
>> the code to remove the virtual phys, I'll make the attempt.
>
> Can you please try this patch?

It still crashes for me, and backtraces look similar.

Were you able to reproduce the crash?

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2010-07-03 16:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-03  6:26 ath9k doesn't clean up virtual wifis on rmmod, and crashes Ben Greear
2010-07-03  7:02 ` Vasanthakumar Thiagarajan
2010-07-03 16:34   ` Ben Greear [this message]
2010-07-03 17:57     ` Ben Greear
2010-07-04  9:35     ` Vasanthakumar Thiagarajan
2010-07-04 15:59       ` Ben Greear
2010-07-05 18:57         ` Ben Greear
2010-07-06  8:36           ` Rajkumar Manoharan
2010-07-06 12:05             ` Ben Greear

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=4C2F6681.7070202@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vasanth@Atheros.com \
    /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).