All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Liang <stephenliang7@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k: QCA6390 on Dell XPS 13 and kernel crashes
Date: Wed, 9 Dec 2020 23:37:15 -0800	[thread overview]
Message-ID: <CAE+mCOGxEhwnB6m56uvck-ocFdj7PW15hOwVsXE_1X4nZZR-iQ@mail.gmail.com> (raw)
In-Reply-To: <CAE+mCOEZed9Wa8CxHv9dkuyB_-5YukjNPLQTjXv4pK8fc1ev6Q@mail.gmail.com>

Okay, I installed ath11k-qca6390-bringup (6244933dd) and did notice
lockups occurring. In fact, I found a reproducible way to lock up the
system:

1. Turn off WiFi
2. Reboot system
3. Login
4. Turn on WiFi

If you perform those steps, the system will lock on
ath11k-qca6390-bringup, dmesg: https://i.imgur.com/0XExack.jpg

On 59c6d02 + revert of 7fef431be9c9, the firmware will crash but the
system will not lock up. dmesg: https://pastebin.com/raw/hH0HyWVx

If you keep WiFi on, i.e. the system is automatically connected to
WiFi on boot, then on the ath11k-qca6390-bringup tag, it randomly
freezes. On 59c6d02, it seems to be fairly stable so long as I do not
turn off/turn on WiFi. I can bisect based on the reproducible steps in
the next couple days if nobody else comes up with something first.

On Wed, Dec 9, 2020 at 7:07 PM Stephen Liang <stephenliang7@gmail.com> wrote:
>
> > Thanks, good to know. On what platform is this, can you share more details? Is it the new Dell XPS 13 9310 or something else?
>
> Yes, this is the XPS 13 9310.
>
> > I recommend using ath11k-qca6390-bringup branch, it has quite a few
> fixes:
>
> Let me give that a shot, perhaps if I can reproduce the same issues
> the others have been seeing I could start a bisect as well.
>
> My uptime is now at 2 days with Fedora Rawhide kernel 5.10.0-0.rc6
> with commit 59c6d022df8efb450f82d33dd6a6812935bd022f and a revert of
> 7fef431be9c9 patched in. I'm not experiencing any of the stalls or
> crashes that others have been mentioning and I have been able to
> suspend/resume consistently. No issues with power being plugged and
> unplugged either. Happy to help provide details if anybody needs any.
>
> > You mean that the reboot stalls and you need to turn off the laptop using power button?
>
> Actually, with the previously mentioned commit combination, I was able
> to shutdown and reboot successfully as well.

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  reply	other threads:[~2020-12-10  7:37 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 23:49 Re: ath11k: QCA6390 on Dell XPS 13 and kernel crashes Stephen Liang
2020-12-09 15:09 ` Kalle Valo
2020-12-10  3:07   ` Stephen Liang
2020-12-10  7:37     ` Stephen Liang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-06 17:38 Mitchell Nordine
2020-12-06 17:53 ` wi nk
2020-12-06 21:45   ` wi nk
2020-12-07  1:17     ` wi nk
2020-12-07 14:45       ` Mitchell Nordine
2020-12-07 17:01         ` wi nk
2020-12-09  1:52           ` wi nk
2020-12-09  9:43             ` wi nk
2020-12-09 15:28               ` wi nk
2020-12-09 15:35     ` Kalle Valo
2020-12-09 15:39       ` wi nk
2020-12-09 15:50         ` wi nk
2020-12-09 15:50         ` Kalle Valo
2020-12-09 15:55           ` wi nk
2020-12-09 21:46             ` wi nk
2020-12-11 12:28               ` wi nk
2020-12-12  5:37                 ` Kalle Valo
2020-12-12 11:46                   ` wi nk
2020-12-12 23:29                     ` wi nk
2020-12-13  0:03                       ` wi nk
2020-12-13  0:59                         ` Mitchell Nordine
2020-12-13 22:09                           ` Stephen Liang
2020-12-16  8:50                           ` Kalle Valo
2020-11-30 16:55 Kalle Valo
2020-11-30 17:02 ` wi nk
2020-12-01 10:17   ` wi nk
2020-12-05 19:17     ` wi nk
2020-12-06  8:05       ` wi nk

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=CAE+mCOGxEhwnB6m56uvck-ocFdj7PW15hOwVsXE_1X4nZZR-iQ@mail.gmail.com \
    --to=stephenliang7@gmail.com \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@codeaurora.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.