All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Repeated firmware crash when admin down.
Date: Fri, 20 Mar 2015 14:46:33 -0700	[thread overview]
Message-ID: <550C9539.50805@candelatech.com> (raw)

Someone reported this bug to me.  It is repeatable on various firmware,
including my own and official QCA firmware.

I am not certain of the hardware platform, but I think it might be a Ventana
imx6 board.

Kernel is based on 3.19-mumble.

I cannot reproduce on x86 (but testing on 3.17 kernel and different flavour of
Linux, so who knows.)

They simply admin-down wlanX, and then the firmware crashes over and over.
They cannot get any register dump.
When they admin up the interface, the crashes stop and system resumes normally.

I had them try it with my firmware and a driver patch
which will attempt to do ping-pong register dump
over pci register reads in case the firmware's normal PCI messaging transport
is down, but the register value always reads as '0xdeadbeef'.

Driver patch is linked below, 'val' is 0xdeadbeef after the million read attempts.

(Need a few additional patches to define CT firmware flag and such, but you can
 see the logic easily enough.)
http://dmz2.candelatech.com/?p=linux-3.17.dev.y/.git;a=commit;h=52333b889f0c818d2766d0d514ac31e5c53ce0ab

Any ideas what might be the problem?

Thanks,
Ben

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


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

             reply	other threads:[~2015-03-20 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 21:46 Ben Greear [this message]
2015-03-23  6:37 ` Repeated firmware crash when admin down Michal Kazior
2015-03-24  0:30   ` 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=550C9539.50805@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.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 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.