From owner-freebsd-current@freebsd.org Sat Dec 19 18:17:24 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9DAF34CD58F for ; Sat, 19 Dec 2020 18:17:24 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cyv8h3vlLz4Tll for ; Sat, 19 Dec 2020 18:17:24 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: from mail-yb1-f170.google.com (mail-yb1-f170.google.com [209.85.219.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: mhorne) by smtp.freebsd.org (Postfix) with ESMTPSA id 73F45C6DF for ; Sat, 19 Dec 2020 18:17:24 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: by mail-yb1-f170.google.com with SMTP id y128so5057540ybf.10 for ; Sat, 19 Dec 2020 10:17:24 -0800 (PST) X-Gm-Message-State: AOAM533/ZYo+exL4OSouZzwg16FLXI6tUKuYv6hFWuhhS+u3IG8uzl5Y sHQV1jjGW29ZKOkCHpzpDwhfqJXwGs/tEqhejq4= X-Google-Smtp-Source: ABdhPJz95EtVxl7a78JA9fa0xmd5H7nsn8kV0HnXf91fqgCtd2UB84hGHLBPGGMV2yObNwG3OJjuiD2B863MhrFss64= X-Received: by 2002:a25:d24a:: with SMTP id j71mr13094313ybg.13.1608401844019; Sat, 19 Dec 2020 10:17:24 -0800 (PST) MIME-Version: 1.0 References: <4fcf5f35-481b-a321-cb52-7264fc10d1d4@callfortesting.org> In-Reply-To: From: Mitchell Horne Date: Sat, 19 Dec 2020 14:17:14 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: RISC-V root device question -> Panic To: Michael Dexter Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2020 18:17:24 -0000 On Mon, Dec 14, 2020 at 6:03 PM Michael Dexter wrote: > > Mitchell, > > On 12/7/20 1:56 PM, Mitchell Horne wrote: > > You can also override it using the QEMU commandline, which is simpler > > since you won't need to recompile anything. Adding the following > > argument should suffice: > > This works great but riscv 12-STABLE using last week's snapshot revision > throws the panic output included below under QEMU and leaves nothing in > /var/crash > > What expectations should I set for RISC-V STABLE and CURRENT? > Hi Michael, sorry for my delayed reply. Development and testing has been almost entirely focused on CURRENT. I believe riscv64 may have been functional on stable/12 at some point (and we even made an effort to MFC changes there), but it is not used anymore as far as I know. The expectations I would set going forward are that 13.0 will be the first functional release for the architecture (including stable/13 when it is branched), and stable/12 will remain unsupported. Also, to follow up on earlier items in this thread, I have documented how to generate a bootable RISC-V image containing an EFI partition with loader.efi. If you encounter any issues with the instructions, please let me know. https://wiki.freebsd.org/riscv/QEMU#Generate_a_root_filesystem Cheers, Mitchell > All the best, > > Michael > > t[0] == 0xffffffc0006c9d98 > t[1] == 0x0000000040c50000 > t[2] == 0x0000000040c65000 > t[3] == 0x0000000000000001 > t[4] == 0x0000000000000000 > t[5] == 0x0000000000000001 > t[6] == 0x0000000000000001 > s[0] == 0xffffffd0b1600248 > s[1] == 0x0000000040e49000 > s[2] == 0xfffffffffffff000 > s[3] == 0x00000000000000ff > s[4] == 0x0000000041000000 > s[5] == 0x0000000000000001 > s[6] == 0xffffffc000aff988 > s[7] == 0x00000000410a1000 > s[8] == 0x0000000000000280 > s[9] == 0x0000000000000000 > s[10] == 0x0000000000001000 > s[11] == 0xffffffffffffff73 > a[0] == 0x0000000000000000 > a[1] == 0xffffffd00297d560 > a[2] == 0x0000000000000000 > a[3] == 0x0000000000000021 > a[4] == 0x0000000000000000 > a[5] == 0x0000000000000021 > a[6] == 0x000000000000003f > a[7] == 0xffffffc000aff900 > sepc == 0xffffffc0004ce414 > sstatus == 0x0000000000000120 > panic: Fatal page fault at 0xffffffc0004ce414: 0x00000000000065 > cpuid = 1 > time = 1607915275 > KDB: stack backtrace: > #0 0xffffffc00023f2d4 at kdb_backtrace+0x50 > Uptime: 2d1h40m41s > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting...