From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 53FE6C0015E for ; Sun, 25 Jun 2023 18:17:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229636AbjFYSR3 (ORCPT ); Sun, 25 Jun 2023 14:17:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60450 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229448AbjFYSR1 (ORCPT ); Sun, 25 Jun 2023 14:17:27 -0400 Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4F0C6FF; Sun, 25 Jun 2023 11:17:26 -0700 (PDT) Received: by mail-oi1-x233.google.com with SMTP id 5614622812f47-39ecf031271so2250024b6e.1; Sun, 25 Jun 2023 11:17:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687717045; x=1690309045; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=ZAA+VrbO9krgfzrzDGzCg+M3T3IjPa2ks+yrz5EWc4o=; b=jDPKWbld2lNsNaTcg4vgnyBxkoEwQs8+Osrvz7LiEQsvL2fEjMXk7L0nL9S3AWZRzm iq07s4nJv+KzxSeuGy9Csco1w8GqHv02h9VIC5zikekCrnI7K8dx6gmLthIYk8fNF666 MkkzYsbedQzt2u6y84BAdETMidChRNtxpXImfXO1UsunzeGM752eB3BV5FUGO5YSSexZ bCkAf3n03b6yj7TNesbLhAx5iq1FvoQHujaBdW61Sv0rApLHtia9JDRMvS7ZLLTn8Brx 4BODOfI6WlV9AdUguunYz55357/+0tBWrM4a35mrOZVGq9dlL99PXlsp9K5CuXqUwPT5 Zthg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687717045; x=1690309045; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ZAA+VrbO9krgfzrzDGzCg+M3T3IjPa2ks+yrz5EWc4o=; b=K3ezvjtHD+AJKcUCGsMtrgQTJUDv/lxF8zie2ItOLrMLY37q72nrw+DKT4w38usn1W piRWE4obPTxz7SZ6i5qXyq14E79a0k9oKq/nNrE19s+XdzjcaZ4Xs4lDYzX3t+MKGwyl 5kQx13bcbHlX24dbROuVNugPCzc0JJ2iy2Yi0qFVp7op46wDBLje3/vhjtBUZeS179IU uoFcutnj2qXOzWrrL2awTsMf2cO+7BCiPODDauX8niEsckDN1SoNf9fpRe2C2e8LcnI+ B0l+wA4+lyIzRB8DR5g7cquoyGBcT1/KlZg0Z9zAqvwBh7pWZakYzck6zAVwTuqJn4Ex 20Iw== X-Gm-Message-State: AC+VfDyQcuLB2qgc93aAbgShAjPI0RSwW8ct10gGU6yisO2B6Xrpu0hY +pA4NXF79S606bvRNhSqXPk= X-Google-Smtp-Source: ACHHUZ5H32ckcsK1zBfyNZceMELsMtOPJ905PuQ8Afi9/aItnS8mT3KegO0GWvzYKc6z2xmQQkC4EQ== X-Received: by 2002:a05:6808:2810:b0:398:4761:20d with SMTP id et16-20020a056808281000b003984761020dmr27571840oib.19.1687717045532; Sun, 25 Jun 2023 11:17:25 -0700 (PDT) Received: from [192.168.1.119] ([216.130.59.33]) by smtp.gmail.com with ESMTPSA id u3-20020a056808000300b0039cc917d0b9sm1697342oic.16.2023.06.25.11.17.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 25 Jun 2023 11:17:25 -0700 (PDT) Sender: Larry Finger Message-ID: Date: Sun, 25 Jun 2023 13:17:23 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: Fwd: After kernel 6.3.7 or 6.3.8 b43 driver fails To: Arnd Bergmann , "Sardonimous ." , Bagas Sanjaya , Linux Kernel Mailing List , Linux Regressions , Linux Wireless , Netdev Cc: =?UTF-8?Q?Michael_B=c3=bcsch?= , kernel test robot , Simon Horman , Kalle Valo References: <27829c69-515c-36a6-4beb-3210225f8936@gmail.com> <69b98eb4-2c4e-fe75-90b4-4b08505a595a@lwfinger.net> Content-Language: en-US From: Larry Finger In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/25/23 13:12, Arnd Bergmann wrote: > On Sun, Jun 25, 2023, at 18:58, Sardonimous wrote: >> I have been unable to get DMA to work in the past.  So I have been >> configuring it with PIO=1 (/etc/modprobe,d/b43.conf): >> >>     options b43 pio=1 qos=0 >> > > I think the qos=0 parameter is what causes the WARN_ON(), as that > causes the use of only one queue, while the warning happens when > tx function iterates over all the queues and warns that they don't > exist. I agree and suggest running with no options. If we need debug, we can turn it on later. Larry