Date: Wed, 10 Feb 2021 18:30:56 -0700 From: Warner Losh <imp@bsdimp.com> To: Jesper Schmitz Mouridsen <jsm@freebsd.org> Cc: Emmanuel Vadot <manu@bidouilliste.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: newfs segfault (was:nvme dma returns EFBIG (27)) Message-ID: <CANCZdfpKPLvOG8CYOHyKiaZO5WidkYdvSEERYUs_JjM3Det0bQ@mail.gmail.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 Wed, Feb 10, 2021 at 4:01 PM Jesper Schmitz Mouridsen <jsm@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: > > > >> Hi > >> > >> I can dd blocks from /dev/nda0p0 but I cannot run newfs. > >> > >> It prints nvme0: nvme_payload_map: err 27. and ctrl+t shows it is > >> stuck in physwri > >> > >> > https://github.com/freebsd/freebsd-src/blob/a6dc68c0e0f8a24ffaf0b4e78e58141ef7897047/sys/dev/nvme/nvme_qpair.c#L1003 > >> > >> > https://github.com/freebsd/freebsd-src/blob/c6c70c074633569447be4bfd2b694a1c294015bd/sys/dev/nvme/nvme_qpair.c#L567 > >> > >> I could format as ext4 under Linux. > >> > >> Any hints or pointers are welcome. > >> > >> Thanks > >> > >> Jesper > > What board ? > > What version of FreeBSD ? > > dmesg ? > > > > Any of the above is *always* required for trying to reproduce and > > finding bugs. > > > > Cheers, > > > I was on FreeBSD generic 13.0-ALPHA1 on > > on FreeBSD generic 13.0-ALPHA2 FreeBSD 13.0-ALPHA2 #0 c256201-g02611ef8ee9 > > newfs /dev/nda0p1v now core dumps. > > Program terminated with signal SIGSEGV, Segmentation fault. > #0 isblock (cp=0x100247f9f <error: Cannot access memory at address > 0x100247f9f>, h=0, fs=<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=0x100247f9f <error: Cannot access memory at address > 0x100247f9f>, h=0, fs=<optimized out>) at /usr/src/sbin/newfs/mkfs.c:1085 > #1 alloc (size=4096, mode=mode@entry=16893) at > /usr/src/sbin/newfs/mkfs.c:1001 > #2 0x0000000000215d20 in fsinit (utime=<optimized out>) at > /usr/src/sbin/newfs/mkfs.c:948 > #3 mkfs (pp=<optimized out>, pp@entry=0x0, fsys=<optimized out>, > fsys@entry=0xffffffffee26 "/dev/nda0p1") at /usr/src/sbin/newfs/mkfs.c:611 > #4 0x00000000002133ec in main (argc=<optimized out>, argv=<optimized > out>) at /usr/src/sbin/newfs/newfs.c:405 > > It is on my pinebookpro. nvmecontrol devlist > nvme0: KINGSTON SA2000M8250G > nvme0ns1 (238475MB) > What does 'nvmecontrol identify nvme0' say? And what's kern.maxphys? Warner > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpKPLvOG8CYOHyKiaZO5WidkYdvSEERYUs_JjM3Det0bQ>