From: "Toke Høiland-Jørgensen" <toke@kernel.org>
To: Gregg Wonderly <greggwonderly@seqtechllc.com>,
linux-wireless@vger.kernel.org
Subject: Re: shift exponent 35 is too large @ ath/ath9k/ar9003_hw.c:1147
Date: Wed, 22 Mar 2023 22:33:30 +0100 [thread overview]
Message-ID: <87cz5079p1.fsf@toke.dk> (raw)
In-Reply-To: <E3A9C354-0CB7-420C-ADEF-F0177FB722F4@seqtechllc.com>
Gregg Wonderly <greggwonderly@seqtechllc.com> writes:
> I am receiving a console error message from this driver that appears to be in the following function. In this function, the chk_dbg variable is 32bits and there is logic that seems to attempt to select from 1 of 2 different 32bit values to get a 64bit wide mask value into chk_dbg from dma_dbg_4 or dmc_dbg_5.
>
> The problem is that the (5*i) shift count should be have i adjusted by the 6 limit used to make the check for which dma_dbg_[45] value selected.
>
>
> static bool ar9003_hw_detect_mac_hang(struct ath_hw *ah)
> {
> u32 dma_dbg_4, dma_dbg_5, dma_dbg_6, chk_dbg;
> u8 dcu_chain_state, dcu_complete_state;
> bool dcu_wait_frdone = false;
> unsigned long chk_dcu = 0;
> unsigned int i = 0;
> dma_dbg_4 = REG_READ(ah, AR_DMADBG_4);
> dma_dbg_5 = REG_READ(ah, AR_DMADBG_5);
> dma_dbg_6 = REG_READ(ah, AR_DMADBG_6);
> dcu_complete_state = dma_dbg_6 & 0x3;
> if (dcu_complete_state != 0x1)
> goto exit;
> for (i = 0; i < ATH9K_NUM_TX_QUEUES; i++) {
> if (i < 6)
> chk_dbg = dma_dbg_4;
> else
> chk_dbg = dma_dbg_5;
> dcu_chain_state = (chk_dbg >> (5 * i)) & 0x1f;
> if (dcu_chain_state == 0x6) {
> dcu_wait_frdone = true;
> chk_dcu |= BIT(i);
> }
> }
> if ((dcu_complete_state == 0x1) && dcu_wait_frdone) {
> for_each_set_bit(i, &chk_dcu, ATH9K_NUM_TX_QUEUES) {
> if (ath9k_hw_verify_hang(ah, i))
> return true;
> }
> }
> exit:
> return false;
> }
>
> The for loop seems to need to look like the following:
>
> for (i = 0; i < ATH9K_NUM_TX_QUEUES; i++) {
> int off=i;
> if (i < 6) {
> chk_dbg = dma_dbg_4;
> } else {
> chk_dbg = dma_dbg_5;
> off = i - 6;
> }
> dcu_chain_state = (chk_dbg >> (5 * off)) & 0x1f;
> if (dcu_chain_state == 0x6) {
> dcu_wait_frdone = true;
> chk_dcu |= BIT(i);
> }
> }
>
Did you test this? Please send a proper patch :)
-Toke
next prev parent reply other threads:[~2023-03-22 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 19:57 shift exponent 35 is too large @ ath/ath9k/ar9003_hw.c:1147 Gregg Wonderly
2023-03-22 21:33 ` Toke Høiland-Jørgensen [this message]
2023-03-30 13:44 ` Gregg Wonderly
2023-03-30 16:11 ` Peter Seiderer
2023-03-30 16:56 ` Gregg Wonderly
2023-04-13 22:17 ` Toke Høiland-Jørgensen
2023-04-18 21:14 ` Peter Seiderer
2023-04-18 23:03 ` Toke Høiland-Jørgensen
2023-04-18 23:53 ` Gregg Wonderly
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=87cz5079p1.fsf@toke.dk \
--to=toke@kernel.org \
--cc=greggwonderly@seqtechllc.com \
--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).