From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from server-vie001.gnuweeb.org (server-vie001.gnuweeb.org [89.58.62.56]) (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 E0C3EEC4; Thu, 7 Aug 2025 01:37:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=89.58.62.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1754530663; cv=none; b=Dk0JLkpb12/r9D5o1l5GUwHZ5PYIdTSpXiUae4ag7GoC/MU8hEGYvP/ROSWgH+eowLfgsxyYp+2QHphqXjHnMfT3BuMlXB3n9axv+VMK8eqHBSxBp1HHt/ObCdCDyV6wjCqt4FjjL1F7dhvfOhpWzCl4Ib6yxJrXf/2rU+B/sUc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1754530663; c=relaxed/simple; bh=ce65IqiN2VyqeISLJNiRFdmLyT7oo1QL65dXx6+DtR8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=cR5V3WJrLRz9fBn41oywVgeUwYOeoX1Sv4fGyrzdz+/GKobP19q41BNFHosBfnexnrL+rlGhJJ4Xjh8NcyczWzjom7ccOgUahE3h9EL5Sqb3xAAg9JZh+9xvb0WmDdhZqYSBRYSy8YLt+gieY0foDU0UnnOy/GoL6LYv3A8z+WQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=gnuweeb.org; spf=pass smtp.mailfrom=gnuweeb.org; dkim=pass (2048-bit key) header.d=gnuweeb.org header.i=@gnuweeb.org header.b=oJCW887q; arc=none smtp.client-ip=89.58.62.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=gnuweeb.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gnuweeb.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gnuweeb.org header.i=@gnuweeb.org header.b="oJCW887q" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=new2025; t=1754530653; bh=ce65IqiN2VyqeISLJNiRFdmLyT7oo1QL65dXx6+DtR8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To:Message-ID:Date:From:Reply-To:Subject:To: Cc:In-Reply-To:References:Resent-Date:Resent-From:Resent-To: Resent-Cc:User-Agent:Content-Type:Content-Transfer-Encoding; b=oJCW887qTh75G6bKT8AkskQKWDq5I394sVFXgJxcRQlDOFBbKOmaZLu1+c8YDFzwP g5hhi+5tLzUqXFqE53vK5Bl78/c9XxnmOpKUafIlS5WU7JQvp1z3/NCkrfgTSpUtam PjcDbaY4KBj2ZcvFAlDjEi25rOX8T5xmowiOEvc52mj/fnB56E6IXsngj/jKRy575Z 009c+xVYceZLs0Hfs6APlA4+m1yv/PayC0WnnUXrXfCRcekP/Due8fQHIP9LmdgZy9 dX71rpkwIv80eHPlgdcGISIoee1XSJZb4A19XXvZZTxiO9NW+5yTxHoWiEO602IWWC KhEgX4qj2QaPg== Received: from linux.gnuweeb.org (unknown [182.253.126.227]) by server-vie001.gnuweeb.org (Postfix) with ESMTPSA id 7E4CD3127C48; Thu, 7 Aug 2025 01:37:30 +0000 (UTC) X-Gw-Bpl: wU/cy49Bu1yAPm0bW2qiliFUIEVf+EkEatAboK6pk2H2LSy2bfWlPAiP3YIeQ5aElNkQEhTV9Q== Date: Thu, 7 Aug 2025 08:37:27 +0700 From: Ammar Faizi To: Linus Torvalds Cc: Simon Horman , Oliver Neukum , Andrew Lunn , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Greg Kroah-Hartman , Linux Netdev Mailing List , Linux USB Mailing List , Linux Kernel Mailing List , Armando Budianto , gwml@vger.gnuweeb.org, stable@vger.kernel.org, John Ernberg Subject: Re: [PATCH net v2] net: usbnet: Fix the wrong netif_carrier_on() call placement Message-ID: References: <20250801190310.58443-1-ammarfaizi2@gnuweeb.org> <20250804100050.GQ8494@horms.kernel.org> <20250805202848.GC61519@horms.kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Machine-Hash: hUx9VaHkTWcLO7S8CQCslj6OzqBx2hfLChRz45nPESx5VSB/xuJQVOKOB1zSXE3yc9ntP27bV1M1 On Wed, Aug 06, 2025 at 04:54:36AM +0300, Linus Torvalds wrote: > Anyway, I've applied Ammar's v3 that ended up the same patch that I also tested, Yesterday, I synced with your tree, but couldn't boot. Crashed with this call trace: https://gist.githubusercontent.com/ammarfaizi2/3ba41f13517be4bae70cde869347d259/raw/0ac09b3e1d90d51c3fed14ca9f837f45d7730f0a/crash.jpg This morning, I synced with your tree again, still the same result. I'll try to bisect it and report to approriate subsystem once I get the first bad commit. I suspect it's related to pci or nvme (based on that call trace). -- Ammar Faizi