Date: Thu, 18 Nov 2021 14:26:39 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 135690] [panic] [ata] ufs_dirbad: /backuphd: bad dir ino 22259126 at offset 0: mangled entry Message-ID: <bug-135690-227-uWIzHFXofL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-135690-227@https.bugs.freebsd.org/bugzilla/> References: <bug-135690-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D135690 Karel Gardas <karel.gardas@centrum.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karel.gardas@centrum.cz --- Comment #7 from Karel Gardas <karel.gardas@centrum.cz> --- Not sure if I may report here too, but I'm able to see the same panic quite reguralry on RISC-V platform with latest FreeBSD VM image and while running= in qemu 5.2.0 on top of FreeBSD 13-p5 on x64 host. My panic looks: FreeBSD/riscv (freebsd) (ttyu0)=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20 login: panic: ufs_dirbad: /: bad dir ino 739685 at offset 0: mangled entry cpuid =3D 3 time =3D 1637242167 KDB: stack backtrace: db_trace_self() at db_trace_self db_trace_self_wrapper() at db_trace_self_wrapper+0x38 kdb_backtrace() at kdb_backtrace+0x2c vpanic() at vpanic+0x148 panic() at panic+0x2a ufs_lookup_ino() at ufs_lookup_ino+0xb18 ufs_lookup() at ufs_lookup+0x16 VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0x30 vfs_cache_lookup() at vfs_cache_lookup+0xae VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x30 lookup() at lookup+0x45e namei() at namei+0x35c kern_statat() at kern_statat+0xe8 sys_fstatat() at sys_fstatat+0x1e do_trap_user() at do_trap_user+0x208 cpu_exception_handler_user() at cpu_exception_handler_user+0x72 --- exception 8, tval =3D 0 KDB: enter: panic [ thread pid 779 tid 100087 ] Stopped at kdb_enter+0x4c: sd zero,0(a0) db> where Tracing pid 779 tid 100087 td 0xffffffc0957c7100 kdb_enter() at kdb_enter+0x4a vpanic() at vpanic+0x18c panic() at panic+0x2a ufs_lookup_ino() at ufs_lookup_ino+0xb18 ufs_lookup() at ufs_lookup+0x16 VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0x30 vfs_cache_lookup() at vfs_cache_lookup+0xae VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x30 vfs_cache_lookup() at vfs_cache_lookup+0xae VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x30 lookup() at lookup+0x45e namei() at namei+0x35c kern_statat() at kern_statat+0xe8 sys_fstatat() at sys_fstatat+0x1e do_trap_user() at do_trap_user+0x208 cpu_exception_handler_user() at cpu_exception_handler_user+0x72 --- exception 8, tval =3D 0 db> and it usually happen after some time of using risc-v vm. When using it I usually do: - pkg install git - git clone latest src - buildworld - buildkernel sometimes I'm not able to complete, sometimes I'm and the panic happen more later. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-135690-227-uWIzHFXofL>