From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.molgen.mpg.de (mx3.molgen.mpg.de [141.14.17.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1BFDC3594A for ; Fri, 10 Oct 2025 13:13:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=141.14.17.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760102013; cv=none; b=h5fIIDMBQP999rbltW0l6KJQtqcXJMJ/26M9CeRdZ3sZdk37HmcZcmNXkHnqcQW1f5vAh1bHTK3P1BuYMGhJGOydrA/aUTCf6VVhHtX8UISuexj9agfCX2dBIu7qu7D6Q/5i8tdpZuqkjNa3KJ6TieH4XyA0q+glPhBJhxuULrM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760102013; c=relaxed/simple; bh=2nEOD+5PfY8a3pV8dWjkubyvytfepFoxPqi7Eh8twUA=; h=Message-ID:Date:MIME-Version:From:Subject:To:Cc:References: In-Reply-To:Content-Type; b=V9+zGTqLgUNG24TGUP2d2yVwwCn03z0T8VBSBWpWjEtY7m8zDXzDghYmQGKf7Eo/byUz2xtpEXgGbqZAZQsp9fqjwb7FHL6YlxKlEJfa0suozXNdPj84B6rpc7NYJP2qXZ8SorgQKAHZ4R69ON5nmtRXsbVPjsE65opE5q6jMpI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=molgen.mpg.de; spf=pass smtp.mailfrom=molgen.mpg.de; arc=none smtp.client-ip=141.14.17.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=molgen.mpg.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=molgen.mpg.de Received: from [141.14.220.42] (g42.guest.molgen.mpg.de [141.14.220.42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id AC6066028F35A; Fri, 10 Oct 2025 15:12:50 +0200 (CEST) Message-ID: Date: Fri, 10 Oct 2025 15:12:50 +0200 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Paul Menzel Subject: Re: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff: firmware crashed! To: Baochen Qiang , Jeff Johnson Cc: ath10k@lists.infradead.org, LKML , jamie@stimulussoft.com References: <5aa2dae4-94ba-45cb-b138-bb40c89a85eb@molgen.mpg.de> <486e9f27-3b03-4317-a1fc-1bd92235db1c@molgen.mpg.de> <90a764d0-c230-43bb-b7e5-189544839f8d@quicinc.com> <82b9e966-5e12-4a13-98d4-0ffa88505f97@molgen.mpg.de> <8354f613-692e-4f6b-933c-3434a5ae90b2@oss.qualcomm.com> Content-Language: en-US In-Reply-To: <8354f613-692e-4f6b-933c-3434a5ae90b2@oss.qualcomm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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?