NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/56701: paninc on ufs2 while running on QEMU 6.2.0



The following reply was made to PR kern/56701; it has been noted by GNATS.

From: nervoso <nervoso%k1.com.br@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/56701: paninc on ufs2 while running on QEMU 6.2.0
Date: Sun, 13 Feb 2022 17:02:51 -0300

 --=-BFRwdO7DIaWCpdG8Qm8o
 Content-Type: text/plain; charset="UTF-8"
 Content-Transfer-Encoding: 8bit
 
 Em dom, 2022-02-13 às 16:25 +0000, Martin Husemann escreveu:
 > The following reply was made to PR kern/56701; it has been noted by GNATS.
 > 
 > From: Martin Husemann <martin%duskware.de@localhost>
 > To: nervoso <nervoso%k1.com.br@localhost>
 > Cc: gnats-bugs%netbsd.org@localhost
 > Subject: Re: kern/56701: paninc on ufs2 while running on QEMU 6.2.0
 > Date: Sun, 13 Feb 2022 17:24:00 +0100
 > 
 >  System panicked: /: bad dir ino 11444433 at offset 376: NUL in name [.extract_mak] i=12, namlen=20
 >  #0  0xc011b67d in cpu_reboot ()
 >  #1  0xc0c1976a in kern_reboot ()
 >  #2  0xc0c558e1 in vpanic ()
 >  #3  0xc0c5596f in panic ()
 >  #4  0xc0baefe5 in ufs_lookup ()
 >  #5  0xc0cbf92c in VOP_LOOKUP ()
 >  #6  0xc0ca174f in lookup_once ()
 >  #7  0xc0ca2647 in namei_tryemulroot ()
 >  #8  0xc0ca4153 in namei ()
 >  #9  0xc0caacc1 in do_sys_unlinkat ()
 >  #10 0xc041f39a in syscall ()
 >  #11 0xc01007f8 in Xsyscall ()
 >  
 >  This means: something corrupted your disk contents in a directory.
 >  
 >  Martin
 >  
 correct, but only happens in the i386 version and only in qemu and only
 using HEAD  9.99.93
 if I change the /netbsd kernel in the SAME filesystem  for a /netbsd
 9.2_STABLE from the original ISO,,  the system boots,
 runs fsck finds no problems,  marks the filesystem clean and  runs fine
 if I change back the /netbsd kernel to the 9.99.93,  the system panics
 
 Something have changed in the ufs2 in the 9.99.93 and only in the
 i386... perhaps some .asm code???  or inline???
 
 thanks 
 
 
 
 --=-BFRwdO7DIaWCpdG8Qm8o
 Content-Type: text/html; charset="utf-8"
 Content-Transfer-Encoding: quoted-printable
 
 <html><head></head><body><div>Em dom, 2022-02-13 =C3=A0s 16:25 +0000, Marti=
 n Husemann escreveu:</div><blockquote type=3D"cite" style=3D"margin:0 0 0 .=
 8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>The following rep=
 ly was made to PR kern/56701; it has been noted by GNATS.</pre><pre><br></p=
 re><pre>From: Martin Husemann &lt;<a href=3D"mailto:martin%duskware.de@localhost";>mar=
 tin%duskware.de@localhost</a>&gt;</pre><pre>To: nervoso &lt;<a href=3D"mailto:nervoso=
 @k1.com.br">nervoso%k1.com.br@localhost</a>&gt;</pre><pre>Cc: <a href=3D"mailto:gnats=
 -bugs%netbsd.org@localhost">gnats-bugs%netbsd.org@localhost</a></pre><pre>Subject: Re: kern/567=
 01: paninc on ufs2 while running on QEMU 6.2.0</pre><pre>Date: Sun, 13 Feb =
 2022 17:24:00 +0100</pre><pre><br></pre><pre> System panicked: /: bad dir i=
 no 11444433 at offset 376: NUL in name [.extract_mak] i=3D12, namlen=3D20</=
 pre><pre> #0  0xc011b67d in cpu_reboot ()</pre><pre> #1  0xc0c1976a in kern=
 _reboot ()</pre><pre> #2  0xc0c558e1 in vpanic ()</pre><pre> #3  0xc0c5596f=
  in panic ()</pre><pre> #4  0xc0baefe5 in ufs_lookup ()</pre><pre> #5  0xc0=
 cbf92c in VOP_LOOKUP ()</pre><pre> #6  0xc0ca174f in lookup_once ()</pre><p=
 re> #7  0xc0ca2647 in namei_tryemulroot ()</pre><pre> #8  0xc0ca4153 in nam=
 ei ()</pre><pre> #9  0xc0caacc1 in do_sys_unlinkat ()</pre><pre> #10 0xc041=
 f39a in syscall ()</pre><pre> #11 0xc01007f8 in Xsyscall ()</pre><pre> </pr=
 e><pre> This means: something corrupted your disk contents in a directory.<=
 /pre><pre> </pre><pre> Martin</pre><pre> </pre></blockquote><div>correct, b=
 ut only happens in the i386 version and only in qemu and only using HEAD &n=
 bsp;9.99.93</div><div>if I change the /netbsd kernel in the SAME filesystem=
  &nbsp;for a /netbsd 9.2_STABLE from the original ISO,, &nbsp;the system bo=
 ots,</div><div>runs fsck finds no problems, &nbsp;marks the filesystem clea=
 n and &nbsp;runs fine</div><div>if I change back the /netbsd kernel to the =
 9.99.93, &nbsp;the system panics</div><div><br></div><div>Something have ch=
 anged in the ufs2 in the 9.99.93 and only in the i386... perhaps some .asm =
 code??? &nbsp;or inline???</div><div><br></div><div>thanks&nbsp;</div><div>=
 <br></div><div><br></div><div class=3D"-x-evo-signature-wrapper"><span clas=
 s=3D"-x-evo-signature" id=3D"none"></span></div></body></html>
 
 --=-BFRwdO7DIaWCpdG8Qm8o--
 



Home | Main Index | Thread Index | Old Index