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 X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1F4B7C43603 for ; Sat, 21 Dec 2019 00:55:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D5A522082E for ; Sat, 21 Dec 2019 00:55:36 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=kernel-dk.20150623.gappssmtp.com header.i=@kernel-dk.20150623.gappssmtp.com header.b="X4Pyb0kG" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726666AbfLUAzf (ORCPT ); Fri, 20 Dec 2019 19:55:35 -0500 Received: from mail-pf1-f194.google.com ([209.85.210.194]:43770 "EHLO mail-pf1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726514AbfLUAzf (ORCPT ); Fri, 20 Dec 2019 19:55:35 -0500 Received: by mail-pf1-f194.google.com with SMTP id x6so5048040pfo.10 for ; Fri, 20 Dec 2019 16:55:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=BdaxFGwLgb3ce+3JHrcpofvonJrHt7G075X1rJRTfqI=; b=X4Pyb0kG9JhqiofSFpF4O5ug0nVfRFr17lP0LuuTKj6cvSVbroDqczfXHaygtk5ga7 Ytx5jM1VjgoIx6RXWfTQON23VeL75R4+S4UUlAvTEjTvtEoMDDW+qBt8XgEllNsXJTbO y4BHJQns5ZhwPGIi/p83oMCFrpEsYk6bKfFoqR/InuQR+7o48qJyHRKFAs0fXtaZsqJE uakUemmPKvJBsKdfCv4TSiup7Atzj3s2BSCt8ec17sol3ZJ7pEm4dAgo9QPpWNHKKJxj RhMix6wKjxR7XH16O8p6p+pUygvr1lpiECRN+de31cWN3/69XUsBpn1+Cuic1dJEoMGd aDXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=BdaxFGwLgb3ce+3JHrcpofvonJrHt7G075X1rJRTfqI=; b=NGQCBkpjEgl3K1QG45llJTYPguV/FhrIDliS1QJnOgyvZmweRTixoagTR0zC7BYokI S5tGSfsC3edrZgWI9iG9xJlTr9OBkeu51M+/UBBj1rn9FRlywZqiRIAlTxFX7x+vNrIL UMtvQeC97wW5NAObvEJoAV5A72QhVCXyAOHX2iD3umkmej3Xa2vN1FwcFnYtdTEsVHtU iayqTJsSy/+zj3RMI691krNm5aaaro8OQo8YyRopM4ZHNA+mZZ107091HpeyBLsWOlEg NF1sEhi9JKzXH82MF34TlzQ175eZoePO8TgVQPlII1VLPEXxtjrdE7eSZuzPmjjA4OUX FFCQ== X-Gm-Message-State: APjAAAW6nzrVz9ffDpPW90P+3iv0rzGJkeFEYlUU5C7HTP/DJZEnrS0u 2QIojom0dlML/mt20y2zRm/kZKVZAY8qAg== X-Google-Smtp-Source: APXvYqyZ5b58i52oeWaiD+dp1ujiQyr9UneppuCJYxgIzSLDLp2DPb60Jd0BdDcJcm6MVhylPusQQw== X-Received: by 2002:a63:360a:: with SMTP id d10mr17492475pga.366.1576889734748; Fri, 20 Dec 2019 16:55:34 -0800 (PST) Received: from [192.168.1.188] ([66.219.217.145]) by smtp.gmail.com with ESMTPSA id c68sm14988644pfc.156.2019.12.20.16.55.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 20 Dec 2019 16:55:34 -0800 (PST) Subject: Re: iwlwifi warnings in 5.5-rc1 To: Johannes Berg , Emmanuel Grumbach , Luca Coelho Cc: "linux-wireless@vger.kernel.org" , Networking References: <9727368004ceef03f72d259b0779c2cf401432e1.camel@sipsolutions.net> From: Jens Axboe Message-ID: Date: Fri, 20 Dec 2019 17:55:32 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <9727368004ceef03f72d259b0779c2cf401432e1.camel@sipsolutions.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On 12/11/19 1:36 AM, Johannes Berg wrote: > On Tue, 2019-12-10 at 13:46 -0700, Jens Axboe wrote: >> Hi, >> >> Since the GRO issue got fixed, iwlwifi has worked fine for me. >> However, on every boot, I get some warnings: >> >> ------------[ cut here ]------------ >> STA b4:75:0e:99:1f:e0 AC 2 txq pending airtime underflow: 4294967088, 208 > > Yeah, we've seen a few reports of this. > > I guess I kinda feel responsible for this since I merged the AQL work, > I'll take a look as soon as I can. Still the case in -git, as of right now. Just following up on this to ensure that a patch is merged to fix this up. I'd be happy to test, if you need something tested. -- Jens Axboe