All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Michal Kazior <michal.kazior@tieto.com>, ath10k@lists.infradead.org
Subject: Re: 3.11.0-rc1: Crash on rmmod of ath10k_pci
Date: Fri, 19 Jul 2013 13:41:22 +0300	[thread overview]
Message-ID: <87mwpi4yst.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <51E7FBF7.2070102@candelatech.com> (Ben Greear's message of "Thu,  18 Jul 2013 07:30:15 -0700")

Ben Greear <greearb@candelatech.com> writes:

>> You seem to have been lucky to trigger a race. CE is teared down
>> before we really stop interrupts and there's very small chance for an
>> interrupt to come in. This is strange, since CE interrupts are
>> disabled and only firmware (i.e. crash) interrupt may come in. I've
>> never seen firmware crash during module unloading. I have a patch for
>> this but it's based upon my recovery patchset and it's not trivial to
>> rebase the fix.
>
> I plan to do further testing on the 'ath' repository, so hopefully
> no need for porting patches around.  If/when that is stable, can see
> about testing mainline.

Yes, please base your work on the ath.git repository instead of mainline
(=Linus' releases). At this stage when we don't have that many users we
would not want to use time on the mainline, the time is much better
spent on improving the driver itself.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

      reply	other threads:[~2013-07-19 10:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 20:30 3.11.0-rc1: Crash on rmmod of ath10k_pci Ben Greear
2013-07-18  5:25 ` Michal Kazior
2013-07-18 14:30   ` Ben Greear
2013-07-19 10:41     ` Kalle Valo [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=87mwpi4yst.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=greearb@candelatech.com \
    --cc=michal.kazior@tieto.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.