From nobody Wed Aug 11 00:26:26 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 BC796174E9A9 for ; Wed, 11 Aug 2021 00:26:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GkrGV4bK5z3JW3 for ; Wed, 11 Aug 2021 00:26:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8621B2525C for ; Wed, 11 Aug 2021 00:26:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 17B0QQdh085083 for ; Wed, 11 Aug 2021 00:26:26 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 17B0QQle085082 for freebsd-arm@FreeBSD.org; Wed, 11 Aug 2021 00:26:26 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 257750] lldb p command crashes on Raspberry Pi 4 Date: Wed, 11 Aug 2021 00:26:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 13.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: bc979@lafn.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257750 Bug ID: 257750 Summary: lldb p command crashes on Raspberry Pi 4 Product: Base System Version: 13.0-RELEASE Hardware: arm64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: bc979@lafn.org The following code - compile with cc -g #include #include #include #include int main (int argc, char *argv[]) { int i, randx, k, p; int initial; initial =3D atoi (argv[1]); randx =3D initial; k =3D atoi (argv[2]); p =3D atoi (argv[3]); i =3D 1; randx =3D (k * randx) % p; while (randx !=3D initial) { if (i < 5) printf ("count =3D %d randx =3D %d\n", i, randx); randx =3D (k * randx) % p; i++; } printf ("count =3D %d\n", i); } when run with lldb on Raspberry Pi 4 gives: test% lldb rand (lldb) target create "rand" Current executable set to '/home/doug/rand/rand' (aarch64). (lldb) b main Breakpoint 1: where =3D rand`main + 24 at rand.c:11:18, address =3D 0x000000000021089c (lldb) r 2357 109 100000 Process 1673 launching Process 1673 launched: '/home/doug/rand/rand' (aarch64) Process 1673 stopped * thread #1, name =3D 'rand', stop reason =3D breakpoint 1.1 frame #0: 0x000000000021089c rand`main(argc=3D4, argv=3D0x0000ffffffffe= a68) at rand.c:11:18 8 int i, randx, k, p; 9 int initial; 10=20=20=20 -> 11 initial =3D atoi (argv[1]); 12 randx =3D initial; 13 k =3D atoi (argv[2]); 14 p =3D atoi (argv[3]); (lldb) n Process 1673 stopped * thread #1, name =3D 'rand', stop reason =3D step over frame #0: 0x00000000002108ac rand`main(argc=3D4, argv=3D0x0000ffffffffe= a68) at rand.c:12:10 9 int initial; 10=20=20=20 11 initial =3D atoi (argv[1]); -> 12 randx =3D initial; 13 k =3D atoi (argv[2]); 14 p =3D atoi (argv[3]); 15=20=20=20 (lldb) p initial PLEASE submit a bug report to https://bugs.freebsd.org/submit/ and include = the crash backtrace. Stack dump: 0. Program arguments: lldb rand=20 1. HandleCommand(command =3D "p initial") #0 0x00000000034d9a4c PrintStackTrace /usr/src/contrib/llvm-project/llvm/lib/Support/Unix/Signals.inc:564:13 #1 0x00000000034d7fb0 __cxx_atomic_store /usr/obj/usr/src/arm64.aarch64/tmp/usr/include/c++/v1/atomic:985:5 #2 0x00000000034d7fb0 store /usr/obj/usr/src/arm64.aarch64/tmp/usr/include/c++/v1/atomic:1594:10 #3 0x00000000034d7fb0 RunSignalHandlers /usr/src/contrib/llvm-project/llvm/lib/Support/Signals.cpp:70:16 #4 0x00000000034da070 SignalHandler /usr/src/contrib/llvm-project/llvm/lib/Support/Unix/Signals.inc:0:3 #5 0x000000004457e994 handle_signal /usr/src/lib/libthr/thread/thr_sig.c:0:3 Segmentation fault (core dumped) test%=20 When run on amd64 yields: master% lldb rand (lldb) target create "rand" Current executable set to '/home/doug/rand/rand' (x86_64). (lldb) b main Breakpoint 1: where =3D rand`main + 22 at rand.c:11:25, address =3D 0x0000000000201906 (lldb) r 2357 109 100000 Process 60280 launching Process 60280 launched: '/home/doug/rand/rand' (x86_64) Process 60280 stopped * thread #1, name =3D 'rand', stop reason =3D breakpoint 1.1 frame #0: 0x0000000000201906 rand`main(argc=3D4, argv=3D0x00007fffffffe= a68) at rand.c:11:25 8 int i, randx, k, p; 9 int initial; 10=20=20=20 -> 11 initial =3D atoi (argv[1]); 12 randx =3D initial; 13 k =3D atoi (argv[2]); 14 p =3D atoi (argv[3]); (lldb) n Process 60280 stopped * thread #1, name =3D 'rand', stop reason =3D step over frame #0: 0x0000000000201916 rand`main(argc=3D4, argv=3D0x00007fffffffe= a68) at rand.c:12:17 9 int initial; 10=20=20=20 11 initial =3D atoi (argv[1]); -> 12 randx =3D initial; 13 k =3D atoi (argv[2]); 14 p =3D atoi (argv[3]); 15=20=20=20 (lldb) p initial (int) $0 =3D 2357 (lldb)=20 This appears to be the same as 248745 which is marked as Closed FIXED. fr v works fine on both architectures. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Wed Aug 11 16:38:44 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 24C8A11FACE8 for ; Wed, 11 Aug 2021 16:38:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GlFrM71l4z3QKj for ; Wed, 11 Aug 2021 16:38:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D8B5412BA3 for ; Wed, 11 Aug 2021 16:38:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 17BGchh8000470 for ; Wed, 11 Aug 2021 16:38:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 17BGchRF000469 for freebsd-arm@FreeBSD.org; Wed, 11 Aug 2021 16:38:43 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 257771] M.2 pcie/nvme device can't mount root and panics on Rock960 rk3399 Date: Wed, 11 Aug 2021 16:38:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: maciphone2@googlemail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257771 Bug ID: 257771 Summary: M.2 pcie/nvme device can't mount root and panics on Rock960 rk3399 Product: Base System Version: CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: maciphone2@googlemail.com Created attachment 227116 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D227116&action= =3Dedit u-boot, loader & dmesg well,=20 on cold boot nvme (directly attached to M.2-slot on Rock960) isn't detected= by u-boot . seems to be something with power cycling that it will be detected by u-boot= =20 AFTER REBOOT while machine was booted from eMMC before .... rock960 =3D> nvme info Device 0: Vendor: 0x15b7 Rev: 211070WD Prod: 20251C807274=20=20=20=20=20=20= =20=20 Type: Hard Disk Capacity: 238475.1 MB =3D 232.8 GB (488397168 x 512) ... well on loader prompt the nvme`s root filesystem is now detected as disk1p2= ( was previously installed by memstick.img) : OK lsdev disk devices: disk0: 59768832 X 512 blocks (removable) disk0p1: EFI disk0p2: FreeBSD UFS disk1: 488397168 X 512 blocks disk1p1: EFI disk1p2: FreeBSD UFS disk1p3: FreeBSD swap http: (unknown) net devices: OK show currdev disk0p2: OK set currdev=3Ddisk1p2 OK show currdev disk1p2 ... OK boot -v ... results in panic because pci/nvme driver never detects any /dev/nda0 or similar.. . .... cib0: mem 0xf8000000-0xf9ffffff,0xfd000000-0xfdffffff irq 6,7,8 on ofwbus0 pcib0: Bus is not cache-coherent pcib0: Gen1 link training timeouted: 0x00180001. pci0: on pcib0 pci0: domain=3D0, physical bus=3D0 found-> vendor=3D0x1d87, dev=3D0x0100, revid=3D0x00 domain=3D0, bus=3D0, slot=3D0, func=3D0 class=3D06-04-00, hdrtype=3D0x01, mfdev=3D0 cmdreg=3D0x0106, statreg=3D0x0010, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Da, irq=3D255 powerspec 3 supports D0 D1 D3 current D0 MSI supports 1 message, 64 bit, vector masks MSI-X supports 1 message in map 0x10 secbus=3D1, subbus=3D31 pcib1: at device 0.0 on pci0 pcib0: failed to reserve resource for pcib1 pcib1: failed to allocate initial memory window: 0-0xfffff pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 31 pci1: on pcib1 pcib1: allocated bus range (1-1) for rid 0 of pci1 pci1: domain=3D0, physical bus=3D1 ... same result if bootable system was removed from eMMC and machine booted directly from nvme, so nvme is bootable but panics. same panic regardless if UFS or ZFS formatted disk. full dmesg in attachment(UFS in this example). Regards K. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Wed Aug 11 18:25:45 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 BDC70137B329 for ; Wed, 11 Aug 2021 18:25:59 +0000 (UTC) (envelope-from kamalpr@gmail.com) Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GlJD65LLvz3qft for ; Wed, 11 Aug 2021 18:25:58 +0000 (UTC) (envelope-from kamalpr@gmail.com) Received: by mail-wm1-x330.google.com with SMTP id w21-20020a7bc1150000b02902e69ba66ce6so2621187wmi.1 for ; Wed, 11 Aug 2021 11:25:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:from:date:message-id:subject:to; bh=pwAbrjuEOdIQa0yz/V7qJlxnums0nxYY4YUIQl4juKE=; b=lKkgCu0Ff8ZnEyD5JOXKRpBmv7Q09wSSMZw909tdy9RQRowim/KWCJbldIulO8FB3r VfbNOTB6ox7vsiqRDltaPritYevJJCzWh0H+m3tPGJLZb3fkTFkVURc+0T2e7J7o+934 Q8dS9ewp6ZFmTD1z/DbATErGoSD+qBBdGdJsC9FixpLqRrv6TLnpIkF2vAA/qi+hNb5E R3v0pckZIiJpJgVaUIqgUApF5R3c89PY1vsdCY0nHGHFVfGYV4qQqvcHygWdS9X5XGDy q0VKcwWgU1dQsFHTS+2iy4jA7g0b4rTZ829+7uXfUF3qmoiUSg/W5HOK9wm3eyv7UPzd IrlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:from:date:message-id :subject:to; bh=pwAbrjuEOdIQa0yz/V7qJlxnums0nxYY4YUIQl4juKE=; b=ZRw2+CCMCEVH6YmB+xpN/dGFUDb7KphMMCfTeTn040mRS6J5by435GM1pdkqiOqtS3 2V3wzf2YC0H9QeKkR4RudoaXKbtEhsMVy1qk5TycuTyGb6HN4VvEUQ9AvpqQt8aFMkcI ruMrZ6rLkj5iu1zOGmvFqVnnbuCpv7tr4+BwBUp0NBmsukIpDg5aUtMVH9r6cFib3Ubk pEst6PT/VNe3HoEmHR6Q8jsaCQIg2MuzJkNU63JoweniSXObY+MnWjBcfA+9XVcppcXE 0ot8skK32SllICS9cI9sprJjClTdRfancFNC49uEaxja0nOSCOCjDQk6Axjq1WjIntqw ZpzA== X-Gm-Message-State: AOAM530EyyB7fULqaM09zBsQlv7Jy6NAcikkBPPmRcEB6FffZTPoC9hh p8gbF/f0YCDbnPjhgIe5dKMekEXG0wYAtFrSEGgU5XZjyw== X-Google-Smtp-Source: ABdhPJwGiQB6vzrO/cdmd5+LOseysACg6yPNNUukQj4hGtceN3tZi94uLcXPz+Emj3ccp/gY8xKpzYDccm41dbAxuyM= X-Received: by 2002:a05:600c:28b:: with SMTP id 11mr11017625wmk.6.1628706357577; Wed, 11 Aug 2021 11:25:57 -0700 (PDT) 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 Reply-To: kamalpr@gmail.com From: "Kamal R. Prasad" Date: Wed, 11 Aug 2021 23:55:45 +0530 Message-ID: Subject: reset sdhci device To: freebsd-arm Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4GlJD65LLvz3qft X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=lKkgCu0F; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of kamalpr@gmail.com designates 2a00:1450:4864:20::330 as permitted sender) smtp.mailfrom=kamalpr@gmail.com X-Spamd-Result: default: False [-1.96 / 15.00]; HAS_REPLYTO(0.00)[kamalpr@gmail.com]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[gmail.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::330:from]; NEURAL_HAM_SHORT(-0.96)[-0.959]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N hello, i am trying to reset sdhci device but i see interrupts are not cleared. do i need to reset the bus too like they do in linux? here is my code. thanks -kamal static void sdhci_resethw(struct sdhci_slot* slot) { uint32_t clock = slot->clock; uint16_t hostctrl2 = RD2(slot, SDHCI_HOST_CONTROL2); u_char hostctrl = slot->hostctrl; u_char power = slot->power; sdhci_set_power(slot, 0); DELAY(10); sdhci_init(slot); sdhci_set_power(slot, power); DELAY(10); sdhci_set_clock(slot, clock); slot->hostctrl = hostctrl; WR1(slot, SDHCI_HOST_CONTROL, slot->hostctrl); WR2(slot, SDHCI_HOST_CONTROL2, hostctrl2); DELAY(10); From nobody Thu Aug 12 04:01:57 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 18F9315E89BE for ; Thu, 12 Aug 2021 04:01:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GlY0j06zDz3Pb0 for ; Thu, 12 Aug 2021 04:01:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E18971C207 for ; Thu, 12 Aug 2021 04:01:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 17C41ulk056971 for ; Thu, 12 Aug 2021 04:01:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 17C41uHt056970 for freebsd-arm@FreeBSD.org; Thu, 12 Aug 2021 04:01:56 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 257771] M.2 pcie/nvme device can't mount root and panics on Rock960 rk3399 Date: Thu, 12 Aug 2021 04:01:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: maciphone2@googlemail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257771 Klaus K=C3=BCchemann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Not A Bug --- Comment #1 from Klaus K=C3=BCchemann --- since compiling rk3399-rock960.dts into the kernel and additionally loading= the resulting dtb from the loader prompt didn't also make any difference,=20 I realized that this seems to be an hardware errata of the board revision 1= .2 I own. This was seemingly fixed in manufacturer`s board rev. 1.3 by an additional added pcie high power-peak hw component. I close this bugreport as a hardware errata and non-fbsd-bug. K. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Sat Aug 14 09:15:37 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 3D0191752F3D for ; Sat, 14 Aug 2021 09:15:51 +0000 (UTC) (envelope-from sanpei.ml@gmail.com) Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Gmvsy5CdHz3H1L for ; Sat, 14 Aug 2021 09:15:50 +0000 (UTC) (envelope-from sanpei.ml@gmail.com) Received: by mail-io1-xd2f.google.com with SMTP id q16so14125680ioj.0 for ; Sat, 14 Aug 2021 02:15:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=+qBT/9VURnZZl6kzutGtMIn9ppC4kBdVW5EEiVE/5UE=; b=GMfnxjDgRgHpRRl4cIXBlbwHtudmbNAFnmnhe5CeT4FogQvO7AWCFpbaE/AAt8G4xI dAUHvrsdmwcuUtlVUqrYkPoTKjBQ3j08gzT/3eWxzcJI3lpUBRlAvuD1yxnQiBp9cvws ISgv53yY119a8o5VH++D3ITMaVrdQ/6YkRDZRgvr0NOueKONifAHOWFCKeD9yH5h3/yD eToCZNlZ5SdpEshg4DvHu2MurZke65S7B9Xxw0UpcR/0fGdwkIk+SNFFH+Dr9jvjAhUy /BCaSyFOC9L0mGOY3igbUIqSs0x3A8ea91YCrAR0bx3gHQg1MNj6H67G64aTGlIu7qle ZLHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=+qBT/9VURnZZl6kzutGtMIn9ppC4kBdVW5EEiVE/5UE=; b=HW98j8y3bIG41Rc29ScwN2vSMff02uMsN+QXCouksKg7iWzV1HlnZBzkv45JqMPH6j ohSm0PJkZnFKpXeAYllzJUWVhhaeeyVLvKtUhboSJXPvifAl3whRJUHW6kvKFes5zM/l YufI09fF2218YGRw51kd0S2zm3ktIomUo+8XVyL1eUvO2ikCKqCftLmiaO2TWaellrnk rlT2XkKv0FPTp79iCqe5Qiitr4aCHQK6m+Ve26as1TBPrFGK0+yImMlLpbZ6q9tOOxJv N7VryDS2B0NfzHHnb+a5benlwcBhP6ujRmkJvu9Z9AvLAdo+3P4Tge7y7xVPj55/bSUM 4uZQ== X-Gm-Message-State: AOAM533L+hl2C9Mtkzga4hczHySj5Weo7r6w24UNrLdjVXMg2lEV9q60 zgD9vmoIZHYcuBn4NGNZ7Gphi0zdTwTr0x1XdUyHMv7Ll/YU5g== X-Google-Smtp-Source: ABdhPJwrn4nLWZ1LwWuluTYw8aoPe0bIyAwECLjW2tFcD7pPuepimt9vbEXjjN7TSMIlJLInCOYZ35pZ4kIJr8DkeKk= X-Received: by 2002:a5e:c302:: with SMTP id a2mr5272775iok.83.1628932549944; Sat, 14 Aug 2021 02:15:49 -0700 (PDT) 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 From: Yoshiro MIHIRA Date: Sat, 14 Aug 2021 18:15:37 +0900 Message-ID: Subject: [14-CURRENT]BBB can't boot 14-CURRENT GENERICSD-20210805 To: freebsd-arm Content-Type: multipart/alternative; boundary="00000000000000a92005c9816a5e" X-Rspamd-Queue-Id: 4Gmvsy5CdHz3H1L X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=GMfnxjDg; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of sanpeiml@gmail.com designates 2607:f8b0:4864:20::d2f as permitted sender) smtp.mailfrom=sanpeiml@gmail.com X-Spamd-Result: default: False [-2.30 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.36)[-0.356]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; NEURAL_HAM_LONG(-0.30)[-0.296]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::d2f:from]; NEURAL_HAM_SHORT(-0.65)[-0.650]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: Y --00000000000000a92005c9816a5e Content-Type: text/plain; charset="UTF-8" I can use 13.0-STABLE-arm-armv7-GENERICSD-20210812 on Beaglebone Black[OK]. However, I tested 14-CURRENT GENERICSD-20210805 on Beaglebone Black. It can't boot with the below message[NG]. Please let me know to solve this issue. If I use the same microSD on Raspberry PI2, it can boot without issue. I put all boot console messages. https://people.freebsd.org/~sanpei/20210814-boot-NG-14-GENERICSD-20210805 < mem: ofwbus0: ti_sysc0: on ofwbus0 panic: Assertion size > 0 failed at /usr/src/sys/kern/subr_vmem.c:1332 <----- PANIC!! cpuid = 0 time = 1 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc05aa35c lr = 0xc007ab68 (db_trace_self_wrapper+0x30) sp = 0xc0e16a98 fp = 0xc0e16bb0 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc007ab68 lr = 0xc02d8ac0 (vpanic+0x17c) sp = 0xc0e16bb8 fp = 0xc0e16bd8 r4 = 0x00000100 r5 = 0x00000000 r6 = 0xc06ff53d r7 = 0xc08db4a8 vpanic() at vpanic+0x17c pc = 0xc02d8ac0 lr = 0xc02d8864 (doadump) sp = 0xc0e16be0 fp = 0xc0e16be4 r4 = 0xc1e1b000 r5 = 0x00000000 r6 = 0x00000000 r7 = 0xc0e16c50 r8 = 0xc0b29d80 r9 = 0x00000002 r10 = 0xc0e16c2c doadump() at doadump pc = 0xc02d8864 lr = 0xc0346514 (vmem_xalloc) sp = 0xc0e16bec fp = 0xc0e16c20 r4 = 0xc0e16c2c r5 = 0xc0e16be4 r6 = 0xc02d8864 r10 = 0xc0e16bec vmem_xalloc() at vmem_xalloc pc = 0xc0346514 lr = 0xc0571a74 (kmem_malloc_domainset+0x9c) sp = 0xc0e16c28 fp = 0xc0e16c70 r4 = 0x00000006 r5 = 0x000000cc r6 = 0xc0ddc108 r7 = 0xc1e1b000 r8 = 0x00000000 r9 = 0x00000000 r10 = 0xc0e16c50 kmem_malloc_domainset() at kmem_malloc_domainset+0x9c pc = 0xc0571a74 lr = 0xc02b3ba0 (malloc_large+0x2c) sp = 0xc0e16c78 fp = 0xc0e16c90 r4 = 0x00000002 r5 = 0xffffffff r6 = 0x00000d90 r7 = 0x00000000 r8 = 0xc08ac904 r9 = 0xc0766709 r10 = 0x80000803 malloc_large() at malloc_large+0x2c pc = 0xc02b3ba0 lr = 0xc067c37c (ti_sysc_attach+0x19c) sp = 0xc0e16c98 fp = 0xc0e16cd0 r4 = 0xd11d3e00 r5 = 0xffffffff r6 = 0x00000d90 r7 = 0xd11d3e28 r8 = 0x00000d90 r10 = 0x80000803 ti_sysc_attach() at ti_sysc_attach+0x19c pc = 0xc067c37c lr = 0xc0316678 (device_attach+0x50c) sp = 0xc0e16cd8 fp = 0xc0e16d20 r4 = 0xc25e4680 r5 = 0xc25e4a80 r6 = 0x36a26d7e r7 = 0x00000000 r8 = 0xc0b2e824 r9 = 0x80040001 r10 = 0x80000803 --00000000000000a92005c9816a5e-- From nobody Sat Aug 14 10:46:36 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 89C651757A69 for ; Sat, 14 Aug 2021 10:46:49 +0000 (UTC) (envelope-from sanpei.ml@gmail.com) Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Gmxtx3GLSz3NPf for ; Sat, 14 Aug 2021 10:46:49 +0000 (UTC) (envelope-from sanpei.ml@gmail.com) Received: by mail-il1-x129.google.com with SMTP id j18so13470780ile.8 for ; Sat, 14 Aug 2021 03:46:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=X+mu/dewk+Zi0encmX+aezU/LDjd40K7jzI5XvTHuUA=; b=qDowQpy6AlyAu3ro8Kn+ZCP4vDL1IJrWokTbFh9ufZP0ftgfDTFr8a8zpjngy/GNOa TOwi+EDzJxAiA8GDrdQJ6p6NmupxARYoe8pfjNyxmPuC6H7leVMMgKwI16hiuYGB+CRU ZiSP6uYbM+sfxVbriNCO4E+u3qQN3Czak18Rwef5uA5p3ssWqCkRzMpyRhfbWaesLv05 YRpipa+FzmCnNiXIsQ4rvS+S9II0c+gIFtG9qAiak4psIf8yp+o3bVMileV1lnz1oBfK GnVnnlIfwNH3CZ47wUL5XiO91baVFspoo53j6ewBx1fy04IaH2n5EUUpeTW6tWYUq8uO zn5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=X+mu/dewk+Zi0encmX+aezU/LDjd40K7jzI5XvTHuUA=; b=cHOFhYOgzo5wy8oMIDFGN/HKPpCHNjPLAg3sTY/o64AVAk5Lc3z99o6EwmjRZbODW+ Kh+nQrT9WJnCMg89a38CKjanU5gfsEdzo+gF263V9zRJWAHc/GJiih09n5F1DJmGxVwL PZCcKSp1/WqkMrQNY4cuSxmjjXzMI5QXje+AQaLAqCaWwORbcK9z1d5VHcCMebT19SN9 gs4k9iC2EB2ymcbfb3TK933ve6sHW0WwDLklGkdSMAwRR60/DF1/8Vuy5FQ/0Q+3kcty NixBn/T7uHFM2Ar1zkEpa+iDk08ORTm88qzIv39PcfOP6Aq4uU07/0AGagZmI+sPQl20 Q2Fw== X-Gm-Message-State: AOAM531DBoumqisGth2NUnMELwx/wlEA4nozrT2ggXHiO2ef9pfuZ9/b AiMZ3TQ4+WPHkEt0MFQq8l7tmfvfvgifkFLd0Rew1EEj3cScDA== X-Google-Smtp-Source: ABdhPJzNronFCLM13YVOsEA1/vtzo1N/bgokBrhRS/PF9SmXk683VwiSo68SLovbR4KFiZ/NW/ZtrYz3gA5sXHKu5aE= X-Received: by 2002:a92:b711:: with SMTP id k17mr2219109ili.247.1628938008835; Sat, 14 Aug 2021 03:46:48 -0700 (PDT) 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 References: In-Reply-To: From: Yoshiro MIHIRA Date: Sat, 14 Aug 2021 19:46:36 +0900 Message-ID: Subject: Re: [14-CURRENT]BBB can't boot 14-CURRENT GENERICSD-20210805 To: freebsd-arm Content-Type: multipart/alternative; boundary="00000000000060bb8e05c982af0e" X-Rspamd-Queue-Id: 4Gmxtx3GLSz3NPf X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: Y --00000000000060bb8e05c982af0e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If I manually build 14-CURRENT kernel(main-n248700-288e553623d3) and replace /boot/kernel directory on 13.0-STABLE-arm-armv7-GENERICSD-20210812= . It can boot without panic. 2021=E5=B9=B48=E6=9C=8814=E6=97=A5(=E5=9C=9F) 18:15 Yoshiro MIHIRA : > I can use 13.0-STABLE-arm-armv7-GENERICSD-20210812 on Beaglebone Black[OK= ]. > > However, I tested 14-CURRENT GENERICSD-20210805 on Beaglebone Black. > It can't boot with the below message[NG]. > > Please let me know to solve this issue. > > If I use the same microSD on Raspberry PI2, it can boot without issue. > I put all boot console messages. > https://people.freebsd.org/~sanpei/20210814-boot-NG-14-GENERICSD-20210805 > > < > mem: > ofwbus0: > ti_sysc0: on ofwbus0 > panic: Assertion size > 0 failed at /usr/src/sys/kern/subr_vmem.c:1332 > <----- PANIC!! > cpuid =3D 0 > time =3D 1 > KDB: stack backtrace: > db_trace_self() at db_trace_self > pc =3D 0xc05aa35c lr =3D 0xc007ab68 (db_trace_self_wrapper+0x30= ) > sp =3D 0xc0e16a98 fp =3D 0xc0e16bb0 > db_trace_self_wrapper() at db_trace_self_wrapper+0x30 > pc =3D 0xc007ab68 lr =3D 0xc02d8ac0 (vpanic+0x17c) > sp =3D 0xc0e16bb8 fp =3D 0xc0e16bd8 > r4 =3D 0x00000100 r5 =3D 0x00000000 > r6 =3D 0xc06ff53d r7 =3D 0xc08db4a8 > vpanic() at vpanic+0x17c > pc =3D 0xc02d8ac0 lr =3D 0xc02d8864 (doadump) > sp =3D 0xc0e16be0 fp =3D 0xc0e16be4 > r4 =3D 0xc1e1b000 r5 =3D 0x00000000 > r6 =3D 0x00000000 r7 =3D 0xc0e16c50 > r8 =3D 0xc0b29d80 r9 =3D 0x00000002 > r10 =3D 0xc0e16c2c > doadump() at doadump > pc =3D 0xc02d8864 lr =3D 0xc0346514 (vmem_xalloc) > sp =3D 0xc0e16bec fp =3D 0xc0e16c20 > r4 =3D 0xc0e16c2c r5 =3D 0xc0e16be4 > r6 =3D 0xc02d8864 r10 =3D 0xc0e16bec > vmem_xalloc() at vmem_xalloc > pc =3D 0xc0346514 lr =3D 0xc0571a74 (kmem_malloc_domainset+0x9c= ) > sp =3D 0xc0e16c28 fp =3D 0xc0e16c70 > r4 =3D 0x00000006 r5 =3D 0x000000cc > r6 =3D 0xc0ddc108 r7 =3D 0xc1e1b000 > r8 =3D 0x00000000 r9 =3D 0x00000000 > r10 =3D 0xc0e16c50 > kmem_malloc_domainset() at kmem_malloc_domainset+0x9c > pc =3D 0xc0571a74 lr =3D 0xc02b3ba0 (malloc_large+0x2c) > sp =3D 0xc0e16c78 fp =3D 0xc0e16c90 > r4 =3D 0x00000002 r5 =3D 0xffffffff > r6 =3D 0x00000d90 r7 =3D 0x00000000 > r8 =3D 0xc08ac904 r9 =3D 0xc0766709 > r10 =3D 0x80000803 > malloc_large() at malloc_large+0x2c > pc =3D 0xc02b3ba0 lr =3D 0xc067c37c (ti_sysc_attach+0x19c) > sp =3D 0xc0e16c98 fp =3D 0xc0e16cd0 > r4 =3D 0xd11d3e00 r5 =3D 0xffffffff > r6 =3D 0x00000d90 r7 =3D 0xd11d3e28 > r8 =3D 0x00000d90 r10 =3D 0x80000803 > ti_sysc_attach() at ti_sysc_attach+0x19c > pc =3D 0xc067c37c lr =3D 0xc0316678 (device_attach+0x50c) > sp =3D 0xc0e16cd8 fp =3D 0xc0e16d20 > r4 =3D 0xc25e4680 r5 =3D 0xc25e4a80 > r6 =3D 0x36a26d7e r7 =3D 0x00000000 > r8 =3D 0xc0b2e824 r9 =3D 0x80040001 > r10 =3D 0x80000803 > > --00000000000060bb8e05c982af0e-- From nobody Sat Aug 14 15:12:03 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 B43E9137E11A for ; Sat, 14 Aug 2021 15:12:09 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Gn3n54SPTz3v1r for ; Sat, 14 Aug 2021 15:12:09 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qv1-xf29.google.com with SMTP id js7so6900079qvb.4 for ; Sat, 14 Aug 2021 08:12:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=ybvLRFUK4o0XUpmsMyABrsCaxi0s5pHosPXcwTaSWiA=; b=dj7jjnqNv5kiuFmDZsiyyuARYRXk3peYZXKpfPkeOJEWpHetjerwb+0WAeBQ0+yig3 cUBOdzXVC8WTHNzk9AwNJGpSFRHN7X+c8F7Vh0+6DFU7H0piAOp8G2nuAKqh0rCycnGe lGwE7IhJ92CoYkGCeJZXmS5N+boh+6ynZG2xCFGPAQBE3werXQggPcnqkOuiXkrUEixZ Ze4YwT82qW8cFr3w0LBZ3vte5CfJ2tZ35SGNdNBkbN0BM+pHvePMLU7VrIq0kA4K4vV/ 0SjBan0XKnU9Q6xQkPkrGUACLj6hNh9LFi6/cAVcp3BCs3VeD8CuxRWoYs9nzY4nM5Dk hjAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=ybvLRFUK4o0XUpmsMyABrsCaxi0s5pHosPXcwTaSWiA=; b=HKQMS99gxAWIqRI4yfWxs99Ml4d5CU0KilkPILoUAgDrtB5srpNw+eo9ycG91xSSzk L74NVWfBjgE6MVVEXUSVch0kcqNCacsQzXLYFzCqDqQEMfArb5TxemHeV0za8Q/LZjWL YB1EJffHP1reIy36BnSNjv6EXjp7LjigzY7KlgM0vRHzFdJawr/w3AXGvnm5EobhbZ+T ygdYzLNx33V7RQhVbaVHFobYiVkBoYve2uggVKMlYjRXuxSSZD6JJQTp3RQtrvyNZCb8 iLX6UUnvxD3rG37kTMmIrO46IHYHDqX19ztmjWKECneAt0NsOJAXOudVJkXkntV3M45W +aUw== X-Gm-Message-State: AOAM530cttNRJ1ECbp9Ew8jovJLtbPXcGcUDopT1fZJfABxlbO7VQgVG UaTvd1HAUqLDQDHjN9TBxW8= X-Google-Smtp-Source: ABdhPJwxjOD8q3MKSNlL0iJ3KSAoPsd7OIxruP5buOpf5lV/SQabVq8u+IFLIWGRs+9NK+eeFNj1JA== X-Received: by 2002:a05:6214:15c1:: with SMTP id p1mr7995611qvz.9.1628953929157; Sat, 14 Aug 2021 08:12:09 -0700 (PDT) Received: from nuc ([142.126.162.193]) by smtp.gmail.com with ESMTPSA id p4sm2968380qkk.12.2021.08.14.08.12.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 14 Aug 2021 08:12:08 -0700 (PDT) Date: Sat, 14 Aug 2021 11:12:03 -0400 From: Mark Johnston To: Yoshiro MIHIRA Cc: freebsd-arm Subject: Re: [14-CURRENT]BBB can't boot 14-CURRENT GENERICSD-20210805 Message-ID: References: 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4Gn3n54SPTz3v1r X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Sat, Aug 14, 2021 at 06:15:37PM +0900, Yoshiro MIHIRA wrote: > I can use 13.0-STABLE-arm-armv7-GENERICSD-20210812 on Beaglebone Black[OK]. > > However, I tested 14-CURRENT GENERICSD-20210805 on Beaglebone Black. > It can't boot with the below message[NG]. > > Please let me know to solve this issue. > > If I use the same microSD on Raspberry PI2, it can boot without issue. > I put all boot console messages. > https://people.freebsd.org/~sanpei/20210814-boot-NG-14-GENERICSD-20210805 > > < > mem: > ofwbus0: > ti_sysc0: on ofwbus0 > panic: Assertion size > 0 failed at /usr/src/sys/kern/subr_vmem.c:1332 I guess that the DTB has changed somehow such that this error path is getting exercised. This patch should allow you to boot without panicking, at least. diff --git a/sys/arm/ti/ti_sysc.c b/sys/arm/ti/ti_sysc.c index b16158aa5d83..4fda12f05725 100644 --- a/sys/arm/ti/ti_sysc.c +++ b/sys/arm/ti/ti_sysc.c @@ -306,6 +306,8 @@ parse_regfields(struct ti_sysc_softc *sc) { /* Grab the content of reg properties */ nreg = OF_getproplen(node, "reg"); + if (nreg == -1) + return (ENXIO); reg = malloc(nreg, M_DEVBUF, M_WAITOK); OF_getencprop(node, "reg", reg, nreg); From nobody Sun Aug 15 07:59:54 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 9A6F01761E3B for ; Sun, 15 Aug 2021 08:00:11 +0000 (UTC) (envelope-from sanpei.ml@gmail.com) Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GnV8C3LbYz4jDS; Sun, 15 Aug 2021 08:00:11 +0000 (UTC) (envelope-from sanpei.ml@gmail.com) Received: by mail-il1-x129.google.com with SMTP id z2so15423249iln.0; Sun, 15 Aug 2021 01:00:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6fkVLUe/gY09KHQ/JTEkJCZPU5gkRslzk+dKLowkHEg=; b=bapSzSFGAFHbQ5gAZhsiT1TN/9UI9uqzy62EnCxrZLjYiBoPZhHFDAwL5ynYSgVna0 +KoGDvvyj3IvT2UkGwYD3mk+b1//HZ4oG7cgaZAi++Spc4PfxOkj3gPMI81mwfmOPqHV 7QZ19NGjX3mlk2rHtflmIERysUPPim+cBcP2rap8eygDeHTtu1tbwRC5RrQHjUDvZXsZ b9qJ2xbJimCkXmVCKMjR9E/3k+cZvmBk2tehWttvxUrU8bbzwUqkp3gJCSuDB9SB6rHo V8hyUwBGaKATQ2gPSzMxMXig7SOtl6Gycmr+eA7CXQZKLCaFKMGevXmGngQoKd0pEE29 qGwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6fkVLUe/gY09KHQ/JTEkJCZPU5gkRslzk+dKLowkHEg=; b=JM2BOfk/2k+Q5p3r77w/VppH0Kh308Cw3wl9+olEDv3vBSK7J8Z74bPGeMixoOvBGS 6fu6UMSB8lamTuRn2A/DxIC22/eJQyx7aZ/TlPA2ErtKLqUHSRnlCbe+vIe2LxPex0Qb 4WHqYKEDHuTsJUgelWfQl+sbHcWyDkR2IDJ4LxLTZlJJonNxgQAM4TuDevFb3Rtuq9PI 6eCgzmsNlLBqEbNB1GxDp+BtKcNz0KmMXHKqWssKQ8GUTDAq/aeFUdFodUTnaYzbQRsl 2X4f1DkOGJF4AeazvgTzLcBjAnmvP1IYpBYadKp+Yq56+eb0gp/ESBCiHdfjG+k2ZYvy nv/w== X-Gm-Message-State: AOAM533YAvQsPBPCzwYDYZ2/v13LLA89onbNcjA/xs+cW29wTsusTAwW Z9aj7N2eBQsmQW/XGTg40hehei7+zj6yMuPbcntmPZEtZ6kY6g== X-Google-Smtp-Source: ABdhPJxvSl3OEGk1KVfWjsTNh2YPzg6DZ0GyR1s5soXByvJK6hyNCNq4xZbEKU1deunRcVfDYY7m9C9jFjYmUefl9YQ= X-Received: by 2002:a05:6e02:12a2:: with SMTP id f2mr7630524ilr.222.1629014405303; Sun, 15 Aug 2021 01:00:05 -0700 (PDT) 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 References: In-Reply-To: From: Yoshiro MIHIRA Date: Sun, 15 Aug 2021 16:59:54 +0900 Message-ID: Subject: Re: [14-CURRENT]BBB can't boot 14-CURRENT GENERICSD-20210805 To: Mark Johnston Cc: freebsd-arm Content-Type: multipart/alternative; boundary="000000000000f652f405c9947855" X-Rspamd-Queue-Id: 4GnV8C3LbYz4jDS X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; TAGGED_FROM(0.00)[]; REPLY(-4.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: Y --000000000000f652f405c9947855 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I applied ti_sysc.c patch with 14.0-CURRENT-arm-armv7-GENERICSD-20210805. Unfortunately, I got another panic(No usable event timer found!) ofwbus0: ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 regfix0: on ofwbus0 clk_fixed0: on ofwbus0 ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 ti_sysc0: on ofwbus0 ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 cpulist0: on ofwbus0 cpu0: on cpulist0 cpufreq_dt0: on cpu0 cpufreq_dt0: no regulator for cpu@0 device_attach: cpufreq_dt0 attach returned 6 ti_sysc0: on ofwbus0 device_attach: ti_sysc0 attach returned 6 gpioled0: on ofwbus0 gpioled0: failed to map pin gpioled0: failed to map pin gpioled0: failed to map pin gpioled0: failed to map pin panic: No usable event timer found! <-----------------------------PANIC I compared between13-stable and 14-current. 14-current kernel can't attach clock management. ti_prcm0: mem 0-0x1fff on ti_sysc0 If I replace dtb directory(I got from 13-stable dtb directory and I put FAT partition dtb and /boot/dtb), 14-GENERICSD can't boot.... 2021=E5=B9=B48=E6=9C=8815=E6=97=A5(=E6=97=A5) 0:12 Mark Johnston : > On Sat, Aug 14, 2021 at 06:15:37PM +0900, Yoshiro MIHIRA wrote: > > I can use 13.0-STABLE-arm-armv7-GENERICSD-20210812 on Beaglebone > Black[OK]. > > > > However, I tested 14-CURRENT GENERICSD-20210805 on Beaglebone Black. > > It can't boot with the below message[NG]. > > > > Please let me know to solve this issue. > > > > If I use the same microSD on Raspberry PI2, it can boot without issue. > > I put all boot console messages. > > > https://people.freebsd.org/~sanpei/20210814-boot-NG-14-GENERICSD-20210805 > > > > < > > mem: > > ofwbus0: > > ti_sysc0: on ofwbus0 > > panic: Assertion size > 0 failed at /usr/src/sys/kern/subr_vmem.c:1332 > > I guess that the DTB has changed somehow such that this error path > is getting exercised. This patch should allow you to boot without > panicking, at least. > > diff --git a/sys/arm/ti/ti_sysc.c b/sys/arm/ti/ti_sysc.c > index b16158aa5d83..4fda12f05725 100644 > --- a/sys/arm/ti/ti_sysc.c > +++ b/sys/arm/ti/ti_sysc.c > @@ -306,6 +306,8 @@ parse_regfields(struct ti_sysc_softc *sc) { > > /* Grab the content of reg properties */ > nreg =3D OF_getproplen(node, "reg"); > + if (nreg =3D=3D -1) > + return (ENXIO); > reg =3D malloc(nreg, M_DEVBUF, M_WAITOK); > OF_getencprop(node, "reg", reg, nreg); > > --000000000000f652f405c9947855-- From nobody Sun Aug 15 08:59:57 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 D62161765B22 for ; Sun, 15 Aug 2021 08:56:59 +0000 (UTC) (envelope-from info@ohdata.se) Received: from mail01.ohdata.se (46-22-124-5.ip.axbyte.se [46.22.124.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4GnWPh3XJ9z4lq6; Sun, 15 Aug 2021 08:56:56 +0000 (UTC) (envelope-from info@ohdata.se) Received: from localhost (localhost [127.0.0.1]) by mail01.ohdata.se (Postfix) with ESMTP id 0DDC92138D; Sun, 15 Aug 2021 10:55:33 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail01.ohdata.se Received: from mail01.ohdata.se ([127.0.0.1]) by localhost (mail01.ohdata.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lhlSfNgkezvF; Sun, 15 Aug 2021 10:55:32 +0200 (CEST) Received: from webmail.ohdata.se (unknown [10.0.38.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail01.ohdata.se (Postfix) with ESMTPSA id 52D0B2137B; Sun, 15 Aug 2021 10:55:32 +0200 (CEST) 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 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Sun, 15 Aug 2021 10:59:57 +0200 From: Oskar Holmlund To: Yoshiro MIHIRA Cc: Mark Johnston , freebsd-arm , owner-freebsd-arm@freebsd.org Subject: Re: [14-CURRENT]BBB can't boot 14-CURRENT GENERICSD-20210805 Organization: OH Data In-Reply-To: References: Message-ID: <4897b349a728a5f63498338f2adb63e7@ohdata.se> X-Sender: info@ohdata.se User-Agent: Roundcube Webmail/1.3.6 X-Rspamd-Queue-Id: 4GnWPh3XJ9z4lq6 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N 2021-08-15 09:59 skrev Yoshiro MIHIRA: > I applied ti_sysc.c patch with > 14.0-CURRENT-arm-armv7-GENERICSD-20210805. > > Unfortunately, I got another panic(No usable event timer found!) > > ofwbus0: > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > regfix0: on ofwbus0 > clk_fixed0: on ofwbus0 > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > ti_sysc0: on ofwbus0 > > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > cpulist0: on ofwbus0 > cpu0: on cpulist0 > cpufreq_dt0: on cpu0 > cpufreq_dt0: no regulator for cpu@0 > device_attach: cpufreq_dt0 attach returned 6 > ti_sysc0: on ofwbus0 > device_attach: ti_sysc0 attach returned 6 > gpioled0: on ofwbus0 > gpioled0: failed to map pin > gpioled0: failed to map pin > gpioled0: failed to map pin > gpioled0: failed to map pin > panic: No usable event timer found! <-----------------------------PANIC > > I compared between13-stable and 14-current. > 14-current kernel can't attach clock management. > ti_prcm0: mem 0-0x1fff on ti_sysc0 > > If I replace dtb directory(I got from 13-stable dtb directory and I put > FAT > partition dtb and /boot/dtb), 14-GENERICSD can't boot.... > > > 2021年8月15日(日) 0:12 Mark Johnston : > >> On Sat, Aug 14, 2021 at 06:15:37PM +0900, Yoshiro MIHIRA wrote: >> > I can use 13.0-STABLE-arm-armv7-GENERICSD-20210812 on Beaglebone >> Black[OK]. >> > >> > However, I tested 14-CURRENT GENERICSD-20210805 on Beaglebone Black. >> > It can't boot with the below message[NG]. >> > >> > Please let me know to solve this issue. >> > >> > If I use the same microSD on Raspberry PI2, it can boot without issue. >> > I put all boot console messages. >> > >> https://people.freebsd.org/~sanpei/20210814-boot-NG-14-GENERICSD-20210805 >> > >> > < >> > mem: >> > ofwbus0: >> > ti_sysc0: on ofwbus0 >> > panic: Assertion size > 0 failed at /usr/src/sys/kern/subr_vmem.c:1332 >> >> I guess that the DTB has changed somehow such that this error path >> is getting exercised. This patch should allow you to boot without >> panicking, at least. >> >> diff --git a/sys/arm/ti/ti_sysc.c b/sys/arm/ti/ti_sysc.c >> index b16158aa5d83..4fda12f05725 100644 >> --- a/sys/arm/ti/ti_sysc.c >> +++ b/sys/arm/ti/ti_sysc.c >> @@ -306,6 +306,8 @@ parse_regfields(struct ti_sysc_softc *sc) { >> >> /* Grab the content of reg properties */ >> nreg = OF_getproplen(node, "reg"); >> + if (nreg == -1) >> + return (ENXIO); >> reg = malloc(nreg, M_DEVBUF, M_WAITOK); >> OF_getencprop(node, "reg", reg, nreg); >> >> Hi, You will probably need these two reviews to get AM335x to boot on the latest device-tree import. https://reviews.freebsd.org/D27889 https://reviews.freebsd.org/D31311 -- Bästa Hälsningar Oskar Holmlund Tel 070-3220292 From nobody Sun Aug 15 21:00:46 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 5FA88174E970 for ; Sun, 15 Aug 2021 21:00:49 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GnqSv6G76z4X4c for ; Sun, 15 Aug 2021 21:00:47 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 167B61C579 for ; Sun, 15 Aug 2021 21:00:47 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 17FL0kA7010545 for ; Sun, 15 Aug 2021 21:00:46 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 17FL0kqG010544 for freebsd-arm@FreeBSD.org; Sun, 15 Aug 2021 21:00:46 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202108152100.17FL0kqG010544@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: freebsd-arm@FreeBSD.org Subject: Problem reports for freebsd-arm@FreeBSD.org that need special attention Date: Sun, 15 Aug 2021 21:00:46 +0000 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 Content-Type: multipart/alternative; boundary="16290612469.5dada9A3.9300" Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: Y --16290612469.5dada9A3.9300 Date: Sun, 15 Aug 2021 21:00:46 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 238576 | Raspberry Pi 3B+ "shutdown -p" does not shut off Open | 239673 | Spurious Interrupt message from /dev/led/led1 2 problems total for which you should take action. --16290612469.5dada9A3.9300--