From owner-freebsd-arm@freebsd.org Tue May 4 03:50:03 2021 Return-Path: Delivered-To: freebsd-arm@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 A6AE0624E2A for ; Tue, 4 May 2021 03:50:03 +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 4FZ5T74DQBz4Ygb for ; Tue, 4 May 2021 03:50:03 +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 84B472722 for ; Tue, 4 May 2021 03:50:03 +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 1443o3vF038221 for ; Tue, 4 May 2021 03:50:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 1443o3Vh038220 for freebsd-arm@FreeBSD.org; Tue, 4 May 2021 03:50:03 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 255584] freebsd-release13.0 for arm64 could not enter multi-user mode Date: Tue, 04 May 2021 03:50:03 +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 Only Me X-Bugzilla-Who: ohata9870@gmail.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 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 MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting FreeBSD to ARM processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2021 03:50:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255584 Bug ID: 255584 Summary: freebsd-release13.0 for arm64 could not enter multi-user mode Product: Base System Version: 13.0-RELEASE Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: ohata9870@gmail.com My env. windows10 host, and using QEMU aarch64 system emulation, QEMU is executed under cygwin-terminal Release 13.0 was booted and can enter single user mode ,but could not enter multi-user mode. QEMU is quit. startup script: # for freebsd arm imgfile=3D'.\\FreeBSD-13.0-RELEASE-arm64-aarch64.qcow2' #imgfile=3D'.\\FreeBSD-12.2-RELEASE-arm64-aarch64.qcow2' fmt=3Dqcow2 biosf=3D'.\\QEMU_EFI.fd' #biosf=3Dedk2-aarch64-code.fd $qemusys \ -m 4096M -cpu cortex-a72 -M virt,highmem=3Doff -k ja -smp 2 \ -bios $biosf \ -drive if=3Dnone,file=3D$imgfile,format=3D$fmt,id=3Dhd0 \ -device virtio-blk-device,drive=3Dhd0 \ -device qemu-xhci \ -device usb-kbd \ -netdev tap,id=3Dnet0,ifname=3D$tap -net nic,macaddr=3D$mymac,netde= v=3Dnet0 \ -serial mon:stdio \ -nographic \ --------------- Under single user mode, there is no ttyv(0...) virtual terminal device file. During boot sequence to multi-user mode, following cons message found, ... Starting devd. eval: cannot open /dev/ttyv0: No such file or directory eval: cannot open /dev/ttyv0: No such file or directory Starting dhclient. ... I think due to lack of ttyv? device file, init could not open virtual termi= nal by getty. Is there any workaround? regards; --=20 You are receiving this mail because: You are the assignee for the bug.=