Date: Wed, 10 Feb 2021 19:13:42 -0800 From: Mark Millard <marklmi@yahoo.com> To: Jesper Schmitz Mouridsen <jsm@FreeBSD.org> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: newfs segfault (was:nvme dma returns EFBIG (27)) Message-ID: <2AAF8FF6-F4F1-4221-BA88-FBDD5463B84F@yahoo.com> In-Reply-To: <e4110cb3-8c11-7bbc-506d-3375406cac1c@FreeBSD.org> References: <15cc2f1d-b8e5-5df3-a05a-4f3014074918@FreeBSD.org> <20210210230833.d8ed42bcdf4707ebf0d2aea6@bidouilliste.com> <e4110cb3-8c11-7bbc-506d-3375406cac1c@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Feb-10, at 15:01, Jesper Schmitz Mouridsen <jsm at FreeBSD.org> = wrote: > On 10.02.2021 23.08, Emmanuel Vadot wrote: >> On Wed, 10 Feb 2021 22:55:27 +0100 >> Jesper Schmitz Mouridsen <jsm@FreeBSD.org> wrote: >>=20 >>> Hi >>>=20 >>> I can dd blocks from /dev/nda0p0 but I cannot run newfs. >>>=20 >>> It prints nvme0: nvme_payload_map: err 27. and ctrl+t shows it is >>> stuck in physwri >>>=20 >>> = https://github.com/freebsd/freebsd-src/blob/a6dc68c0e0f8a24ffaf0b4e78e5814= 1ef7897047/sys/dev/nvme/nvme_qpair.c#L1003 >>>=20 >>> = https://github.com/freebsd/freebsd-src/blob/c6c70c074633569447be4bfd2b694a= 1c294015bd/sys/dev/nvme/nvme_qpair.c#L567 >>>=20 >>> I could format as ext4 under Linux. >>>=20 >>> Any hints or pointers are welcome. >>>=20 >>> Thanks >>>=20 >>> Jesper >> What board ? >> What version of FreeBSD ? >> dmesg ? >>=20 >> Any of the above is *always* required for trying to reproduce and >> finding bugs. >>=20 >> Cheers, >>=20 > I was on FreeBSD generic 13.0-ALPHA1 on >=20 > on FreeBSD generic 13.0-ALPHA2 FreeBSD 13.0-ALPHA2 #0 = c256201-g02611ef8ee9 >=20 > newfs /dev/nda0p1v now core dumps. >=20 > Program terminated with signal SIGSEGV, Segmentation fault. > #0 isblock (cp=3D0x100247f9f <error: Cannot access memory at address = 0x100247f9f>, h=3D0, fs=3D<optimized out>) at = /usr/src/sbin/newfs/mkfs.c:1085 > 1085 /usr/src/sbin/newfs/mkfs.c: No such file or directory. > (gdb) bt > #0 isblock (cp=3D0x100247f9f <error: Cannot access memory at address = 0x100247f9f>, h=3D0, fs=3D<optimized out>) at = /usr/src/sbin/newfs/mkfs.c:1085 > #1 alloc (size=3D4096, mode=3Dmode@entry=3D16893) at = /usr/src/sbin/newfs/mkfs.c:1001 > #2 0x0000000000215d20 in fsinit (utime=3D<optimized out>) at = /usr/src/sbin/newfs/mkfs.c:948 > #3 mkfs (pp=3D<optimized out>, pp@entry=3D0x0, fsys=3D<optimized = out>, fsys@entry=3D0xffffffffee26 "/dev/nda0p1") at = /usr/src/sbin/newfs/mkfs.c:611 > #4 0x00000000002133ec in main (argc=3D<optimized out>, = argv=3D<optimized out>) at /usr/src/sbin/newfs/newfs.c:405 >=20 > It is on my pinebookpro. nvmecontrol devlist > nvme0: KINGSTON SA2000M8250G > nvme0ns1 (238475MB) Care to try somehting like . . . # gdb newfs . . . Reading symbols from newfs... Reading symbols from /usr/lib/debug//sbin/newfs.debug... (gdb) start /dev/nda0p1v Temporary breakpoint 1 at 0x2129f8: file = /usr/fbsd/mm-src/sbin/newfs/newfs.c, line 142. . . . Temporary breakpoint 1, main (argc=3D1, argv=3D0xffffffffeb80) at = /usr/fbsd/mm-src/sbin/newfs/newfs.c:142 142 reserved =3D 0; (gdb) print &disk.d_sbunion.d_fs ??? (gdb) print (&disk.d_sbunion.d_fs)+1 ??? I'm curious about the ??? figures reports vs. the 0x100247f9f in your backtrace. (Not that I'm sure what to do with the reported information.) The start causes some libraries to load, which is why I indicated to use it. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2AAF8FF6-F4F1-4221-BA88-FBDD5463B84F>