From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ej1-f48.google.com (mail-ej1-f48.google.com [209.85.218.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 18887136E01 for ; Thu, 31 Oct 2024 06:33:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.218.48 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730356419; cv=none; b=KM5pZGwmH5MxAFtV7l4gNEK+tSgXJM3ODIcIILJsaq0OOL6Pxns1LqIGAQK+QvBbTk3icJL4GNc1f0dW4zGacV5EIVCez+5+2f8f4RYl6z5SkKrd+NF2dhAx+xhfFa85pPe6qySwNuKPjFo7L9ap5YHVfvRoNSaebJ4ETiI4xJM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730356419; c=relaxed/simple; bh=h3A6usIImJggTbl8niN7j54dxWCAOrho3c/gOkpI1Us=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=KrZl9EsXv9IRRQX7oaE66qUt7rhzjOH1Wq0h1cKluBsES5j/Vm0y5Dd+n6ox1zq4/KBrZCFyxnd6vOW46Hp3G7Ku+jnL10AvlWNXAAl7PrLhkXhnpUxmv2muYXxWAkyijoW4rIR/nChxSm+HjWGw41D67haGcpCO0dH32330Hk4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=debian.org; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=ULKN6MJG; arc=none smtp.client-ip=209.85.218.48 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=debian.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="ULKN6MJG" Received: by mail-ej1-f48.google.com with SMTP id a640c23a62f3a-a99eb8b607aso62147066b.2 for ; Wed, 30 Oct 2024 23:33:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1730356415; x=1730961215; darn=lists.linux.dev; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=UK1H6ntBFGD6fnCHyPbd1B/5kd3XON3dNEEHD/SIHWc=; b=ULKN6MJGjEmOJVNrd4DaKUgz33YWTfLVt1DUCgKwEpMe2AIiPR+EV5A2iQACv4blLV G4ZdCYgWjg48iIqaiV/J12EMYUtZpdaLcSp2aGS70xeCfNBCjB/pyPJzPbjMHIIH53Jn A3fKbDI6PwxgDoXiEjDva5lxbFyKrIGRfkaOpaFY7oVMVD1jL5lZgkwkf5OWgh7drFBe BOS72lowZIyZtOcb+tLsdzO5BVm+SOlAtQ10vbadGC5bwoourwjs4cNk1nnjmqhyursF xVGRs/04cMYgc5gN6hQH+73Brh0EaGdw7V5a+JqbcYVSOJFE60ShJie7u/nasFHh8NyA WINg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730356415; x=1730961215; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=UK1H6ntBFGD6fnCHyPbd1B/5kd3XON3dNEEHD/SIHWc=; b=ezCaM8+5yI44fw69/Xp6NKwKoW+eXVutudaGrJKZ8PkC0uQJl/gzmRYeSYVd7ple+R RytajqEkBR5tnPv4lZoaZcZLigWuEcREny2n9ToDceypPO+rjDxcbsf9J+H8gyEtZHIt MDER1qQ6Dr157BKQq6MB/SUv5KLOBH/miDcoxmv5SVDMqM9U2u4yjYrL3YSRn+cCwwo2 njQLL50QnaXyCFfv+oy6KrNSbILH5/U6IGTYST9UmeeS02acyckQ46wE1Hgin1spewKn INiMbLe8iy4HDqRJu0Ji4Wtp2M9knl7jdx/eC1FJZ3kN8K43UWToqtUuxq3gFSWLWXar ZzkQ== X-Forwarded-Encrypted: i=1; AJvYcCV3YXGtRHJOM/X5Z/H5Fxip8skJG5PqGMXrZSVdXLFKm4homHqKVB7rOM33hiaqoDwNmmXtmtVdvskvAA==@lists.linux.dev X-Gm-Message-State: AOJu0YyJQMGaWmgetZppkdVhO1FMfLCB5xdL+TZ4YPMI9AWGZYT5rvhC WtlUV53nWTLO4hyDE57SpZEWmx6NABjWThSfUXXY9Nx2Dfft2xbG X-Google-Smtp-Source: AGHT+IEud6sFVvRQfjPRKYoT1QQQ7MC58Q7hm9R5LyKZCEEoGoTjBeuZh+oWNPsz07OaOLim9cB1lA== X-Received: by 2002:a17:907:7ba2:b0:a9a:2afc:e4e3 with SMTP id a640c23a62f3a-a9de61d5d26mr1793382666b.50.1730356415186; Wed, 30 Oct 2024 23:33:35 -0700 (PDT) Received: from eldamar.lan (c-82-192-242-114.customer.ggaweb.ch. [82.192.242.114]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a9e5664bb9dsm31886866b.161.2024.10.30.23.33.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 30 Oct 2024 23:33:34 -0700 (PDT) Sender: Salvatore Bonaccorso Received: by eldamar.lan (Postfix, from userid 1000) id DED09BE2DE0; Thu, 31 Oct 2024 07:33:32 +0100 (CET) Date: Thu, 31 Oct 2024 07:33:32 +0100 From: Salvatore Bonaccorso To: Thorsten Leemhuis Cc: Mike , "stable@vger.kernel.org" , Marcel Holtmann , Johan Hedberg , Luiz Augusto von Dentz , linux-bluetooth@vger.kernel.org, Paul Menzel , Sasha Levin , Jeremy =?iso-8859-1?Q?Lain=E9?= , Linux regressions mailing list , Greg KH Subject: Re: Bluetooth kernel BUG with Intel AX211 (regression in 6.1.83) Message-ID: References: <30f4b18f-4b96-403c-a0ab-d81809d9888a@gmail.com> <2024061258-boxy-plaster-7219@gregkh> Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Hi, On Tue, Jun 18, 2024 at 12:30:18PM +0200, Thorsten Leemhuis wrote: > On 12.06.24 14:04, Greg KH wrote: > > On Thu, Jun 06, 2024 at 12:18:18PM +0200, Thorsten Leemhuis wrote: > >> On 03.06.24 22:03, Mike wrote: > >>> On 29.05.24 11:06, Thorsten Leemhuis wrote: > >>> [...] > >>> I understand that 6.9-rc5[1] worked fine, but I guess it will take some > >>> time to be > >>> included in Debian stable, so having a patch for 6.1.x will be much > >>> appreciated. > >>> I do not have the time to follow the vanilla (latest) release as is > >>> likely the case for > >>> many other Linux users. > >>> > >> Still no reaction from the bluetooth developers. Guess they are busy > >> and/or do not care about 6.1.y. In that case: > >> > >> @Greg: do you might have an idea how the 6.1.y commit a13f316e90fdb1 > >> ("Bluetooth: hci_conn: Consolidate code for aborting connections") might > >> cause this or if it's missing some per-requisite? If not I wonder if > >> reverting that patch from 6.1.y might be the best move to resolve this > >> regression. Mike earlier in > >> https://lore.kernel.org/all/c947e600-e126-43ea-9530-0389206bef5e@gmail.com/ > >> confirmed that this fixed the problem in tests. Jeremy (who started the > >> thread and afaics has the same problem) did not reply. > > > > How was this reverted? I get a bunch of conflicts as this commit was > > added as a dependency of a patch later in the series. > > > > So if this wants to be reverted from 6.1.y, can someone send me the > > revert that has been tested to work? > > Mike, can you help out here, as you apparently managed a revert earlier? > Without you or someone else submitting a revert I fear this won't be > resolved... Trying to reboostrap this, as people running 6.1.112 based kernel seems still hitting the issue, but have not asked yet if it happens as well for 6.114. https://bugs.debian.org/1086447 Mike, since I guess you are still as well affected as well, does the issue trigger on 6.1.114 for you and does reverting changes from a13f316e90fdb1 still fix the issue? Can you send your backport/changes? Regards, Salvatore