From: Mohammed Shafi <shafi.wireless@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: MR <g7af0ec1e3ea1e7b1@nextmail.ru>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: ath9k crash 3.2-rc7
Date: Thu, 5 Jan 2012 11:59:16 +0530 [thread overview]
Message-ID: <CAD2nsn05O3e1ZnaK9ZMNk=qFFvLiB7oE-D+zfzofhVgosKibtg@mail.gmail.com> (raw)
In-Reply-To: <20120104212808.GI2540@tuxdriver.com>
Hi John,
we will take a look at this.
i can later come up with few debug patches to narrow down the panic.
looks like a problem in ath_update_survey_stats(survey pointer). full
stack trace will be helpful
thanks.
On Thu, Jan 5, 2012 at 2:58 AM, John W. Linville <linville@tuxdriver.com> wrote:
> You probably want to try linux-wireless@vger.kernel.org for maximum exposure...
>
> On Thu, Jan 05, 2012 at 01:18:09AM +0400, MR wrote:
>> Hello.
>>
>> I have noticed a complete crash (forced switch to console and Alt-SysRq-B
>> doesn't work) when I use ath9k driver for my WiFi card. The problem is that
>> the crash occurs after a few hours of use, so blind bissecting doesn't look
>> like a short-term plan.
>>
>> My card is (as lspci says):
>>
>> 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless
>> Network Adapter (PCI-Express) (rev 01)
>> Subsystem: Device 1a3b:1089
>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>> Stepping- SERR- FastB2B- DisINTx-
>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
>> <TAbort- <MAbort- >SERR- <PERR- INTx-
>> Latency: 0, Cache Line Size: 64 bytes
>> Interrupt: pin A routed to IRQ 17
>> Region 0: Memory at d7400000 (64-bit, non-prefetchable) [size=64K]
>>
>> I use an Asus N53JN notebook, if that matters.
>>
>> I have photos of two instances of the crash. The backtrace goes as follows (I
>> typed this in, so maybe there is a typo somewhere - I hope there is none,
>> though):
>>
>> wq_worker_sleeping+0x10/0xa0
>> __schedule+0x427/0x7b0
>> ? call_rcu_sched+0x10/0x20
>> schedule+0x3a/0x50
>> do_exit+0x57c/0x840
>> ? kmsg_dump+0x45/0xe0
>> oops_end+0xa5/0xf0
>> no_context+0xf2/0x270
>> __bad_area_no_semaphore+0xe/0x10
>> do_page_fault+0x2ba/0x450
>> ? up+0x2d/0x50
>> ? console_unlock+0x1df/0x250
>> ? select_task_rq_fair+0x5be/0x970
>> page_fault+0x25/0x30
>> ? ath_update_survey_stats+0xb7/0x1c0 [ath9k]
>> ath9k_config+0x115/0x780 [ath9k]
>> ? queue_work+0x1a/0x20
>> ? queue_delayed_work+0x25/0x30
>> ? ieee80211_queue_delayed_work+0x46/0x60 [mac80211]
>> ? ath9k_flush+0x155/0x1d0 [ath9k]
>> ieee80211_hw_config+0xe2/0x160 [mac80211]
>> ieee80211_scan_work+0x243/0x5c0 [mac80211]
>> ? ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
>> process_one_work+0x111/0x390
>> worker_thread+0x162/0x340
>> manage_workers.clone.26+0x240/0x240
>> kthread+0x96/0xa0
>> kernel_thread_helper+0x4/0x10
>> ? kthread_worker_fn+0x190/0x190
>> ? gs_change+0x13/0x13
>>
>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
> --
> John W. Linville Someday the world will need a hero, and you
> linville@tuxdriver.com might be all we have. Be ready.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
shafi
next prev parent reply other threads:[~2012-01-05 6:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 21:18 ath9k crash 3.2-rc7 MR
2012-01-04 21:28 ` John W. Linville
2012-01-05 6:29 ` Mohammed Shafi [this message]
2012-01-05 6:59 MR
2012-01-05 15:30 ` Mohammed Shafi
2012-01-05 16:32 MR
2012-01-05 18:52 MR
[not found] <NEXT-4f069dda9267d2.27061318@nextmail.ru>
[not found] ` <CAD2nsn3i=HTP6zOEADMx35rOYXDofo7YG+0zCGH36XgZFLfOww@mail.gmail.com>
2012-01-06 7:49 ` Mohammed Shafi
2012-01-06 8:01 MR
2012-01-06 9:02 ` Mohammed Shafi
2012-01-06 8:10 MR
2012-01-06 12:51 MR
2012-01-06 14:35 ` Mohammed Shafi
2012-01-06 14:41 ` Mohammed Shafi
2012-01-06 14:46 MR
2012-01-06 14:50 ` Mohammed Shafi
2012-01-06 20:55 MR
2012-01-07 11:48 ` Mohammed Shafi
2012-01-07 12:11 MR
2012-01-08 7:19 MR
2012-01-09 5:11 ` Mohammed Shafi
2012-01-09 7:05 MR
2012-01-09 7:30 ` Mohammed Shafi
2012-01-09 7:40 MR
2012-01-09 7:57 ` Mohammed Shafi
2012-01-09 11:11 MR
2012-01-10 18:14 MR
2012-01-11 15:26 ` Mohammed Shafi
2012-01-11 17:20 MR
2012-01-12 6:06 ` Mohammed Shafi
2012-01-12 18:04 MR
2012-01-16 15:52 MR
2012-01-17 18:53 MR
2012-01-18 5:32 ` Mohammed Shafi
2012-01-18 17:30 MR
2012-01-20 4:42 MR
2012-01-20 5:16 ` Mohammed Shafi
2012-01-26 22:19 MR
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='CAD2nsn05O3e1ZnaK9ZMNk=qFFvLiB7oE-D+zfzofhVgosKibtg@mail.gmail.com' \
--to=shafi.wireless@gmail.com \
--cc=g7af0ec1e3ea1e7b1@nextmail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).