mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
	Jeff Johnson <jjohnson@kernel.org>
Cc: ath10k@lists.infradead.org, LKML <linux-kernel@vger.kernel.org>,
	jamie@stimulussoft.com
Subject: Re: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff: firmware crashed!
Date: Fri, 10 Oct 2025 15:12:50 +0200	[thread overview]
Message-ID: <e02b3b8b-78a3-41c7-864e-caba6f1a8c0b@molgen.mpg.de> (raw)
In-Reply-To: <8354f613-692e-4f6b-933c-3434a5ae90b2@oss.qualcomm.com>

Dear Baochen,


Am 21.07.25 um 05:21 schrieb Baochen Qiang:

> On 7/20/2025 4:43 PM, Paul Menzel wrote:

>> Am 14.05.25 um 10:08 schrieb Paul Menzel:

[…]

>>> Were you or the firmware team able to pinpoint the problem, and
>>> come up with a fix? Is there any logging I can enable to help
>>> with debugging?
>> 
>> It also happens with a Telekom Speedport Smart 3 (Arcadyan
>> Corporation) router. The firmware crashed five more times since
>> June. A reliable Wi-Fi connection would be really appreciated.
>> Could you send me a debug firmware, so the firmware developers
>> have it easier to fix it?
> 
> Paul, we are working on getting legal approval on collecting
> necessary information, such as firmware dump etc, from community.
> Once done we will share guides to collect them to debug further.

I just wanted to know, if there was a conclusion yet.


Kind regards,

Paul


PS: I set debug_mask to 0xffffffff a while back, and it logged so much, 
that my old boot logs are gone from the systemd journal now. ;-)

     echo 0xffffffff | sudo tee 
/sys/module/ath10k_core/parameters/debug_mask

Any hint on what to set, when the crashes happen?

  reply	other threads:[~2025-10-10 13:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-08 22:21 Paul Menzel
2025-03-23 11:41 ` Paul Menzel
2025-03-24  3:29   ` Baochen Qiang
2025-03-25  7:01     ` Paul Menzel
2025-05-14  8:08       ` Paul Menzel
     [not found]         ` <1909038a-bde9-4def-bcb8-0f67bff5c62d@stimulussoft.com>
2025-05-14  8:23           ` Paul Menzel
2025-07-20  8:43         ` Paul Menzel
2025-07-21  3:21           ` Baochen Qiang
2025-10-10 13:12             ` Paul Menzel [this message]
2025-10-13  1:49               ` Baochen Qiang

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=e02b3b8b-78a3-41c7-864e-caba6f1a8c0b@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=ath10k@lists.infradead.org \
    --cc=baochen.qiang@oss.qualcomm.com \
    --cc=jamie@stimulussoft.com \
    --cc=jjohnson@kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®