From: Mohammed Shafi <shafi.wireless@gmail.com>
To: MR <g7af0ec1e3ea1e7b1@nextmail.ru>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: ath9k crash 3.2-rc7
Date: Fri, 6 Jan 2012 14:32:55 +0530 [thread overview]
Message-ID: <CAD2nsn1-Oo=n8CY97sXW=kfsEeE2oknpXLayMtyxRA7VMMkHmQ@mail.gmail.com> (raw)
In-Reply-To: <NEXT-4f06aa69274cf6.26578607@nextmail.ru>
2012/1/6 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> > > > :) no problem. i hope for you can recreate the issue consistently ,
> > > > can you please test with the attached patch and another debug patch.
> >> > please let me know if there is no panic but there are warnings (or)
> >if
> > > > there are no warnings (or) the issue still appears(also the trace
> > > > thanks) , also if you need any help
> > > Should I apply the patch to Linux 3.2-rc7 or 3.2 release?
> >Oh, I see. 3.2 release has this fix already. I will build it with
> debugging
> > patch and report warnings now.
>
> I have some unpleasant news: it looks like it takes slightly longer with the
> fix, but the crash still managed to occur with 3.2 and I lack ESP to check
> for warnings immediately before that. I thought that 8 hours is enough
> testing, heh. It simply took 9 and a half under nigh-ideal conditions
> (stable signal from fixed AP with notebook also steadily in one place).
:( i had put those warnings to prevent the crash itself and what's causing it.
may be i had missed that pos can be < 0 in addition to (pos > 37).
i am just looking at those areas of code for some other issue. hope i
can a find a fix
for both of them
>
> Good news is that I remembered to decrease console font size before the
> crash. So now I could see that the long stack trace was just a decoy to
> ensure that the first Oops scrolls too far up. I now have photos of the
> first one, too.
>
> Process: kworker/u:2 (pid: 1419, threadinfo ffff88013dc38000, task
> ffff8800891020d0)
> Stack:
> ffff88013dc39c10 ffff880136111ae0 ffff880136110460 0000000000000040
> ffff880136114000 0000000000000000 ffff88013dc39d20 ffffffffa0560a35
> 0000000000000001 0000000000000202 ffff8801361140f0 ffff88013ed3ea48
> Call trace:
> 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]
> ? __schedule+0x2d7/0x7b0
> ? ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
> process_one_work+0x111/0x390
>
> Only after this happens "unable to complete kernel paging request" in
> ath_update_survey_stats
> 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
>
>
--
shafi
next prev parent reply other threads:[~2012-01-06 9:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 8:01 ath9k crash 3.2-rc7 MR
2012-01-06 9:02 ` Mohammed Shafi [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-26 22:19 MR
2012-01-20 4:42 MR
2012-01-20 5:16 ` Mohammed Shafi
2012-01-18 17:30 MR
2012-01-17 18:53 MR
2012-01-18 5:32 ` Mohammed Shafi
2012-01-16 15:52 MR
2012-01-12 18:04 MR
2012-01-11 17:20 MR
2012-01-12 6:06 ` Mohammed Shafi
2012-01-10 18:14 MR
2012-01-11 15:26 ` Mohammed Shafi
2012-01-09 11:11 MR
2012-01-09 7:40 MR
2012-01-09 7:57 ` Mohammed Shafi
2012-01-09 7:05 MR
2012-01-09 7:30 ` Mohammed Shafi
2012-01-08 7:19 MR
2012-01-09 5:11 ` Mohammed Shafi
2012-01-07 12:11 MR
2012-01-06 20:55 MR
2012-01-07 11:48 ` Mohammed Shafi
2012-01-06 14:46 MR
2012-01-06 14:50 ` Mohammed Shafi
2012-01-06 12:51 MR
2012-01-06 14:35 ` Mohammed Shafi
2012-01-06 14:41 ` Mohammed Shafi
2012-01-06 8:10 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-05 18:52 MR
2012-01-05 16:32 MR
2012-01-05 6:59 MR
2012-01-05 15:30 ` Mohammed Shafi
2012-01-04 21:18 MR
2012-01-04 21:28 ` John W. Linville
2012-01-05 6:29 ` Mohammed Shafi
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='CAD2nsn1-Oo=n8CY97sXW=kfsEeE2oknpXLayMtyxRA7VMMkHmQ@mail.gmail.com' \
--to=shafi.wireless@gmail.com \
--cc=g7af0ec1e3ea1e7b1@nextmail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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).