All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@venema.h4ckr.net
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath10k:  Fix crash when using v1 hardware.
Date: Tue, 02 Jul 2013 16:08:08 -0700	[thread overview]
Message-ID: <51D35D58.5090507@candelatech.com> (raw)
In-Reply-To: <1372804925-1701-1-git-send-email-greearb@candelatech.com>

Actually, I have no idea what type of hardware this is.  It was
suggested earlier to me that this AP had a v1 hardware in it, but
lspci shows this fairly unpromising thing, and the ath10k driver
appears to call 003c the V2 hardware....

05:00.0 Network controller: Atheros Communications Inc. Device 003c (rev ff) (prog-if ff)
	!!! Unknown header type 7f
	Kernel modules: ath10k_pci


On 07/02/2013 03:42 PM, greearb@candelatech.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> I put a v1 NIC from an TP-LINK AC 1750 AP in
> a 64-bit PC, and the OS crashes on bootup.  I'm not
> sure how broken my hardware is (possibly completely non
> functional), but at least with this patch it will no longer
> crash the OS.  Not sure it ever got far enough to try,
> but I also do not have firmware for the NIC.
>
> With this patch I get this info on module load:
>
> ath10k_pci 0000:05:00.0: BAR 0: assigned [mem 0xf4400000-0xf45fffff 64bit]
> ath10k_pci 0000:05:00.0: BAR 0: error updating (0xf4400004 != 0xffffffff)
> ath10k_pci 0000:05:00.0: BAR 0: error updating (high 0x000000 != 0xffffffff)
> ath10k_pci 0000:05:00.0: Refused to change power state, currently in D3
> ath10k: MSI-X interrupt handling (8 intrs)
> ath10k: Unable to wakeup target
> ath10k: target takes too long to wake up (awake count 1)
> ath10k: src_ring ffff88020c0d0a00:  write_index is out of bounds: 4294967295  nentries_mask: 15.
> ath10k: dest_ring ffff88020db2c000:  write_index is out of bounds: 4294967295  nentries_mask: 511.
> ath10k: dest_ring ffff880210d56400:  write_index is out of bounds: 4294967295  nentries_mask: 31.
> ath10k: src_ring ffff880210d57600:  write_index is out of bounds: 4294967295  nentries_mask: 31.
> ath10k: src_ring ffff88020fe70000:  write_index is out of bounds: 4294967295  nentries_mask: 2047.
> ath10k: src_ring ffff880212989b40:  write_index is out of bounds: 4294967295  nentries_mask: 1.
> ath10k: dest_ring ffff880212989960:  write_index is out of bounds: 4294967295  nentries_mask: 1.
> ath10k: Failed to get pcie state addr: -5
> ath10k: early firmware event indicated
> ------------[ cut here ]------------
> WARNING: at /home/greearb/git/linux.wireless-testing/drivers/net/wireless/ath/ath10k/ce.c:771 ath10k_ce_per_engine_service+0x53/0x1b4 [ath10k_pci]()
> ....
> (it hits the warning case about 5-6 times and then seems to quiesce OK).
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
> ---
>   drivers/net/wireless/ath/ath10k/ce.c |   32 +++++++++++++++++++++++++++++++-
>   1 files changed, 31 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath10k/ce.c b/drivers/net/wireless/ath/ath10k/ce.c
> index 61a8ac7..56669f8 100644
> --- a/drivers/net/wireless/ath/ath10k/ce.c
> +++ b/drivers/net/wireless/ath/ath10k/ce.c
> @@ -756,13 +756,23 @@ void ath10k_ce_per_engine_service(struct ath10k *ar, unsigned int ce_id)
>   {
>   	struct ath10k_pci *ar_pci = ath10k_pci_priv(ar);
>   	struct ce_state *ce_state = ar_pci->ce_id_to_state[ce_id];
> -	u32 ctrl_addr = ce_state->ctrl_addr;
> +	u32 ctrl_addr;
>   	void *transfer_context;
>   	u32 buf;
>   	unsigned int nbytes;
>   	unsigned int id;
>   	unsigned int flags;
>
> +	/* On v1 hardware at least, setup can fail, causing ce_id_state to
> +	 * be cleaned up, but this method is still called a few times.  Check
> +	 * for NULL here so we don't crash.  Probably a better fix is to stop
> +	 * the ath10k_pci_ce_tasklet sooner.
> +	 */
> +	if (WARN_ONCE(!ce_state, "ce_id_to_state[%i] is NULL\n", ce_id))
> +		return;
> +
> +	ctrl_addr = ce_state->ctrl_addr;
> +
>   	ath10k_pci_wake(ar);
>   	spin_lock_bh(&ar_pci->ce_lock);
>
> @@ -954,6 +964,16 @@ static int ath10k_ce_init_src_ring(struct ath10k *ar,
>
>   	src_ring->write_index =
>   		ath10k_ce_src_ring_write_index_get(ar, ctrl_addr);
> +	/* Make sure the value above is sane.  Can get 0xFFFFFFFF
> +	 * on a v1 board.
> +	 */
> +	if (src_ring->write_index > src_ring->nentries_mask) {
> +		ath10k_err("src_ring %p:  write_index is out of bounds: %u  nentries_mask: %u.\n",
> +			   src_ring, src_ring->write_index,
> +			   src_ring->nentries_mask);
> +		src_ring->write_index = 0;
> +	}
> +
>   	ath10k_pci_sleep(ar);
>
>   	src_ring->per_transfer_context = (void **)ptr;
> @@ -1037,6 +1057,16 @@ static int ath10k_ce_init_dest_ring(struct ath10k *ar,
>   	dest_ring->sw_index = ath10k_ce_dest_ring_read_index_get(ar, ctrl_addr);
>   	dest_ring->write_index =
>   		ath10k_ce_dest_ring_write_index_get(ar, ctrl_addr);
> +	/* Make sure the value above is sane.  Can get 0xFFFFFFFF
> +	 * on a v1 board.
> +	 */
> +	if (dest_ring->write_index > dest_ring->nentries_mask) {
> +		ath10k_err("dest_ring %p:  write_index is out of bounds: %u  nentries_mask: %u.\n",
> +			   dest_ring, dest_ring->write_index,
> +			   dest_ring->nentries_mask);
> +		dest_ring->write_index = 0;
> +	}
> +
>   	ath10k_pci_sleep(ar);
>
>   	dest_ring->per_transfer_context = (void **)ptr;
>


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


WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath10k: Fix crash when using v1 hardware.
Date: Tue, 02 Jul 2013 16:08:08 -0700	[thread overview]
Message-ID: <51D35D58.5090507@candelatech.com> (raw)
In-Reply-To: <1372804925-1701-1-git-send-email-greearb@candelatech.com>

Actually, I have no idea what type of hardware this is.  It was
suggested earlier to me that this AP had a v1 hardware in it, but
lspci shows this fairly unpromising thing, and the ath10k driver
appears to call 003c the V2 hardware....

05:00.0 Network controller: Atheros Communications Inc. Device 003c (rev ff) (prog-if ff)
	!!! Unknown header type 7f
	Kernel modules: ath10k_pci


On 07/02/2013 03:42 PM, greearb at candelatech.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> I put a v1 NIC from an TP-LINK AC 1750 AP in
> a 64-bit PC, and the OS crashes on bootup.  I'm not
> sure how broken my hardware is (possibly completely non
> functional), but at least with this patch it will no longer
> crash the OS.  Not sure it ever got far enough to try,
> but I also do not have firmware for the NIC.
>
> With this patch I get this info on module load:
>
> ath10k_pci 0000:05:00.0: BAR 0: assigned [mem 0xf4400000-0xf45fffff 64bit]
> ath10k_pci 0000:05:00.0: BAR 0: error updating (0xf4400004 != 0xffffffff)
> ath10k_pci 0000:05:00.0: BAR 0: error updating (high 0x000000 != 0xffffffff)
> ath10k_pci 0000:05:00.0: Refused to change power state, currently in D3
> ath10k: MSI-X interrupt handling (8 intrs)
> ath10k: Unable to wakeup target
> ath10k: target takes too long to wake up (awake count 1)
> ath10k: src_ring ffff88020c0d0a00:  write_index is out of bounds: 4294967295  nentries_mask: 15.
> ath10k: dest_ring ffff88020db2c000:  write_index is out of bounds: 4294967295  nentries_mask: 511.
> ath10k: dest_ring ffff880210d56400:  write_index is out of bounds: 4294967295  nentries_mask: 31.
> ath10k: src_ring ffff880210d57600:  write_index is out of bounds: 4294967295  nentries_mask: 31.
> ath10k: src_ring ffff88020fe70000:  write_index is out of bounds: 4294967295  nentries_mask: 2047.
> ath10k: src_ring ffff880212989b40:  write_index is out of bounds: 4294967295  nentries_mask: 1.
> ath10k: dest_ring ffff880212989960:  write_index is out of bounds: 4294967295  nentries_mask: 1.
> ath10k: Failed to get pcie state addr: -5
> ath10k: early firmware event indicated
> ------------[ cut here ]------------
> WARNING: at /home/greearb/git/linux.wireless-testing/drivers/net/wireless/ath/ath10k/ce.c:771 ath10k_ce_per_engine_service+0x53/0x1b4 [ath10k_pci]()
> ....
> (it hits the warning case about 5-6 times and then seems to quiesce OK).
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
> ---
>   drivers/net/wireless/ath/ath10k/ce.c |   32 +++++++++++++++++++++++++++++++-
>   1 files changed, 31 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath10k/ce.c b/drivers/net/wireless/ath/ath10k/ce.c
> index 61a8ac7..56669f8 100644
> --- a/drivers/net/wireless/ath/ath10k/ce.c
> +++ b/drivers/net/wireless/ath/ath10k/ce.c
> @@ -756,13 +756,23 @@ void ath10k_ce_per_engine_service(struct ath10k *ar, unsigned int ce_id)
>   {
>   	struct ath10k_pci *ar_pci = ath10k_pci_priv(ar);
>   	struct ce_state *ce_state = ar_pci->ce_id_to_state[ce_id];
> -	u32 ctrl_addr = ce_state->ctrl_addr;
> +	u32 ctrl_addr;
>   	void *transfer_context;
>   	u32 buf;
>   	unsigned int nbytes;
>   	unsigned int id;
>   	unsigned int flags;
>
> +	/* On v1 hardware at least, setup can fail, causing ce_id_state to
> +	 * be cleaned up, but this method is still called a few times.  Check
> +	 * for NULL here so we don't crash.  Probably a better fix is to stop
> +	 * the ath10k_pci_ce_tasklet sooner.
> +	 */
> +	if (WARN_ONCE(!ce_state, "ce_id_to_state[%i] is NULL\n", ce_id))
> +		return;
> +
> +	ctrl_addr = ce_state->ctrl_addr;
> +
>   	ath10k_pci_wake(ar);
>   	spin_lock_bh(&ar_pci->ce_lock);
>
> @@ -954,6 +964,16 @@ static int ath10k_ce_init_src_ring(struct ath10k *ar,
>
>   	src_ring->write_index =
>   		ath10k_ce_src_ring_write_index_get(ar, ctrl_addr);
> +	/* Make sure the value above is sane.  Can get 0xFFFFFFFF
> +	 * on a v1 board.
> +	 */
> +	if (src_ring->write_index > src_ring->nentries_mask) {
> +		ath10k_err("src_ring %p:  write_index is out of bounds: %u  nentries_mask: %u.\n",
> +			   src_ring, src_ring->write_index,
> +			   src_ring->nentries_mask);
> +		src_ring->write_index = 0;
> +	}
> +
>   	ath10k_pci_sleep(ar);
>
>   	src_ring->per_transfer_context = (void **)ptr;
> @@ -1037,6 +1057,16 @@ static int ath10k_ce_init_dest_ring(struct ath10k *ar,
>   	dest_ring->sw_index = ath10k_ce_dest_ring_read_index_get(ar, ctrl_addr);
>   	dest_ring->write_index =
>   		ath10k_ce_dest_ring_write_index_get(ar, ctrl_addr);
> +	/* Make sure the value above is sane.  Can get 0xFFFFFFFF
> +	 * on a v1 board.
> +	 */
> +	if (dest_ring->write_index > dest_ring->nentries_mask) {
> +		ath10k_err("dest_ring %p:  write_index is out of bounds: %u  nentries_mask: %u.\n",
> +			   dest_ring, dest_ring->write_index,
> +			   dest_ring->nentries_mask);
> +		dest_ring->write_index = 0;
> +	}
> +
>   	ath10k_pci_sleep(ar);
>
>   	dest_ring->per_transfer_context = (void **)ptr;
>


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

  reply	other threads:[~2013-07-02 23:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 22:42 [PATCH] ath10k: Fix crash when using v1 hardware greearb
2013-07-02 22:42 ` [ath9k-devel] " greearb at candelatech.com
2013-07-02 23:08 ` Ben Greear [this message]
2013-07-02 23:08   ` Ben Greear
2013-07-11  9:37   ` Kalle Valo
2013-07-11  9:37     ` Kalle Valo
2013-07-11 15:06     ` Ben Greear
2013-07-11 15:06       ` Ben Greear
2013-07-11  9:36 ` Kalle Valo
2013-07-11  9:36   ` Kalle Valo
2013-07-11 15:05   ` Ben Greear
2013-07-11 15:05     ` Ben Greear
2013-07-12 14:51     ` Kalle Valo
2013-07-12 14:51       ` Kalle Valo
2013-07-12 15:34       ` Ben Greear
2013-07-12 15:34         ` Ben Greear
2013-07-15  6:55   ` Michal Kazior
2013-07-15  6:55     ` Michal Kazior

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=51D35D58.5090507@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath9k-devel@venema.h4ckr.net \
    --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 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.