From nobody Tue Nov 30 12:22:18 2021 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5B75B18C2160 for ; Tue, 30 Nov 2021 12:22:28 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from fry.fubar.geek.nz (fry.fubar.geek.nz [139.59.165.16]) by mx1.freebsd.org (Postfix) with ESMTP id 4J3LvQ0M9Bz4pDg for ; Tue, 30 Nov 2021 12:22:26 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from [192.168.42.21] (cpc91232-cmbg18-2-0-cust554.5-4.cable.virginm.net [82.2.126.43]) by fry.fubar.geek.nz (Postfix) with ESMTPSA id 6E6F94E687 for ; Tue, 30 Nov 2021 12:22:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fubar.geek.nz; s=mail; t=1638274939; bh=gA5I4QnvK1dWzF0mfZZsZ3MEv1zTC6l16+DdSoQqxFU=; h=From:Subject:Date:References:To:In-Reply-To; b=cYsApG+cqg012aruzwe6a/b2JXA96ZUtXHV7+JrjMBw5FuMMoTKZ6wM77cyf5ldur Iuhb02FmaFBMgzgv/mz8Yr2AQo0Mre4zfyvM7nrVwr/tnh0BRJKUr7SICyfpa7vcLU D5T1/X9r6Y2iCGygng59yjDkhorcX7aruPecFoQ3i6Ah/aShRgo7Oprg0C3XvolO2c 5aoX6GJfC08mMn2oQwB7Bk8P4YLQ9FU1vKtUvnByC8U8UOLnlfbGmkbBHA1OM3XrOR D7e6IeR3MVITU1j1o1FRVmHTZp1fcPot7e9qRMvcHNlATyZCSnMuw8YCUtXq+C8j0P RPUZeTCgQddmMOdCGNQli0ozS3eHs/eQl5bIrfYyAUxdoZn0pNlv/W5t2wQ3NW1JYh QWC7mx+dfCPQFW5kbd/QSCumBacp1zsXWq5/eDVK6PKbbDlW8Gy25o0IHfvsB2vq30 Oabkf4PCpkOA8gHtKTnZTd82oS/kcJP81oWSytQBv/UntUZhNTN+m8pypZZusRXzdi pElx4FYx0rDyq/VOuwHglVKBUw/3z7rKsQUVjQgwOH6kfCxF+DK4jni7lTBbrg+HCR IDKMjMKQzOyqsWlRI+urm7cOVvAZWl536jIBHpkAUwc1hi+mNEvZGx9hcm/dXMALmq hCTxwAHKGiCDYhK79AREjOLc= From: Andrew Turner Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\)) Subject: Re: 14-CURRENT Kernel Panic due to USB hub? Date: Tue, 30 Nov 2021 12:22:18 +0000 References: <2b555ef9-12fe-6214-79a0-cebce1933771@selasky.org> <5bfb1865-8033-0da6-27e4-3c25fb067cee@morante.net> <6F2AD5E1-5AB1-4D08-97F4-84E2905D592B@fubar.geek.nz> To: freebsd-arm@freebsd.org In-Reply-To: <6F2AD5E1-5AB1-4D08-97F4-84E2905D592B@fubar.geek.nz> Message-Id: X-Mailer: Apple Mail (2.3445.104.21) X-Rspamd-Queue-Id: 4J3LvQ0M9Bz4pDg X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=fubar.geek.nz header.s=mail header.b=cYsApG+c; dmarc=pass (policy=none) header.from=fubar.geek.nz; spf=pass (mx1.freebsd.org: domain of andrew@fubar.geek.nz designates 139.59.165.16 as permitted sender) smtp.mailfrom=andrew@fubar.geek.nz X-Spamd-Result: default: False [-2.40 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[fubar.geek.nz:s=mail]; FREEFALL_USER(0.00)[andrew]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; R_SPF_ALLOW(-0.20)[+mx]; DKIM_TRACE(0.00)[fubar.geek.nz:+]; DMARC_POLICY_ALLOW(-0.50)[fubar.geek.nz,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:14061, ipnet:139.59.160.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N I bisected the detached messages back to 601ee53858f6 [1]. If I revert = this change I no longer see this on the console. I am also unable to reproduce the panic with this change reverted. As = the panic can be difficult to reproduce I am unsure if reverting this = change is enough to fix it, or if it=E2=80=99s just making it less = likely to be triggered. Andrew [1] https://cgit.freebsd.org/src/commit/?id=3D601ee53858f6 > On 23 Nov 2021, at 17:34, Andrew Turner wrote: >=20 > Can you create a bug for this in bugzilla so we can keep track of it? >=20 > Andrew >=20 >> On 21 Nov 2021, at 07:18, Daniel Morante via freebsd-arm = wrote: >>=20 >> Here's the bt: >>=20 >> ugen0.2: at usbus0 (disconnected) >> uhub5: at uhub0, port 1, addr 1 (disconnected) >> uhub5: detached >> ugen0.2: at usbus0 >> uhub5 numa-domain 0 on uhub0 >> uhub5: on usbus0 >> uhub5: 4 ports with 4 removable, self powered >> ugen0.2: at usbus0 (disconnected) >> uhub5: at uhub0, port 1, addr 1 (disconnected) >> uhub5: detached >> panic: data abort with spinlock held >> cpuid =3D 108 >> time =3D 1637478997 >> KDB: stack backtrace: >> db_trace_self() at db_trace_self >> KDB: enter: panic >> [ thread pid 11 tid 100111 ] >> Stopped at kdb_enter+0x44: undefined f901411f >> db> bt >> Tracing pid 11 tid 100111 td 0xffffa00005619580 >> db_trace_self() at db_trace_self >> db> >>=20 >> On 11/12/2021 5:52 AM, Hans Petter Selasky wrote: >>> On 11/12/21 00:43, Daniel Morante via freebsd-arm wrote: >>>> ugen0.2: at usbus0 (disconnected) >>>> uhub5: at uhub0, port 1, addr 1 (disconnected) >>>> uhub5: detached >>>> ugen0.2: at usbus0 >>>> uhub5 numa-domain 0 on uhub0 >>>> uhub5: on usbus0 >>>> uhub5: 4 ports with 4 removable, self powered >>>>=20 >>>> I suspect these problems are caused by the above = detaching/reattaching. >>>=20 >>> Can you type "bt" in the panic prompt? >>>=20 >>> --HPS >>>=20 >=20 >=20