From: Jeremy Johnathan Rodent <rat.o.drat@gmail.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Random lock-ups (?) of Centrino Ultimate-N 6300 (iwlwifi)
Date: Thu, 12 Dec 2013 16:18:17 +0100 [thread overview]
Message-ID: <52A9D3B9.7040707@gmail.com> (raw)
In-Reply-To: <CANUX_P1VC80TAexTJfR8EQWBGfOXpQOdj75piKaaJ=to9tuRuQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
On 12.12.2013 06:58, Emmanuel Grumbach wrote:
>>> can you please apply this and report back?
>>>
>>> diff --git a/drivers/net/wireless/iwlwifi/pcie/tx.c
>>> b/drivers/net/wireless/iwlwifi/pcie/tx.c
>>> index c5746ed..0a1f39c 100644
>>> --- a/drivers/net/wireless/iwlwifi/pcie/tx.c
>>> +++ b/drivers/net/wireless/iwlwifi/pcie/tx.c
>>> @@ -708,10 +708,6 @@ void iwl_pcie_tx_start(struct iwl_trans *trans,
>>> u32 scd_base_addr)
>>> reg_val = iwl_read_direct32(trans, FH_TX_CHICKEN_BITS_REG);
>>> iwl_write_direct32(trans, FH_TX_CHICKEN_BITS_REG,
>>> reg_val | FH_TX_CHICKEN_BITS_SCD_AUTO_RETRY_EN);
>>> -
>>> - /* Enable L1-Active */
>>> - iwl_clear_bits_prph(trans, APMG_PCIDEV_STT_REG,
>>> - APMG_PCIDEV_STT_VAL_L1_ACT_DIS);
>>> }
>>>
>>> void iwl_trans_pcie_tx_reset(struct iwl_trans *trans)
>> Sorry it took so long.
>> I've built 3.12.3 with this patch applied. What now?
> Does it help?
> Do you still the same issues?
> If yes - please share the log again.
I booted with it today, being on battery, and got the lock-up after an
hour. I've attached the dmesg output.
[-- Attachment #2: dmesg.log.gz --]
[-- Type: application/gzip, Size: 27843 bytes --]
prev parent reply other threads:[~2013-12-12 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 6:21 Random lock-ups (?) of Centrino Ultimate-N 6300 (iwlwifi) Jeremy Johnathan Rodent
2013-12-08 7:19 ` Emmanuel Grumbach
2013-12-11 19:18 ` Jeremy Johnathan Rodent
2013-12-12 5:58 ` Emmanuel Grumbach
2013-12-12 15:18 ` Jeremy Johnathan Rodent [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=52A9D3B9.7040707@gmail.com \
--to=rat.o.drat@gmail.com \
--cc=egrumbach@gmail.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).