NetBSD-Bugs archive

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

Re: kern/56701: panic 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: panic on ufs2 while running on QEMU 6.2.0
Date: Thu, 17 Feb 2022 10:43:47 -0300

 --=-nOg+dZnFAflE3mo85tgM
 Content-Type: text/plain; charset="UTF-8"
 Content-Transfer-Encoding: 8bit
 
 Em seg, 2022-02-14 às 22:30 +0000, David Holland escreveu:
 >  
 >  My guess would be a 32-bit issue in the virtio disk code, since that's
 >  probably rarely used with 32-bit kernels.
 >  
 tracked down to probably is the processor the distribution was
 created....  I did the sequence using an amd64 8350 running HEAD amd64
 1) download the HEAD i386  iso from netbsd.org
 2) install the head in  the VM
 3) make the test, it works, no problem  (so the qemu, and host OS
 netbsd HEAD amd64)  is ok
 
 4) download the netbsd HEAD src in /usr/src
 5) build a custom kernel  with users=128 no npf, pppoe server....
 6) copy the netbsd to /netbsd.NEW
 7) boot from the new kernel, .... the system works OK...
 
 Conclusion, the kernel built in an amd8350 using NetBSD amd64 HEAD,
 does not work 
 it will only work if built on a i386 machine (can be a vm on qemu) with
 a i386 gcc native compiler... using build.sh
 
 probably the gcc compiler on amd64 produces wrong i386 code... atomic
 OP issues???
 
 well you can consider the PR close with this advice...
 
 Thank you
 
 --=-nOg+dZnFAflE3mo85tgM
 Content-Type: text/html; charset="utf-8"
 Content-Transfer-Encoding: quoted-printable
 
 <html><head></head><body><div>Em seg, 2022-02-14 =C3=A0s 22:30 +0000, David=
  Holland escreveu:</div><blockquote type=3D"cite" style=3D"margin:0 0 0 .8e=
 x; border-left:2px #729fcf solid;padding-left:1ex"><pre>&nbsp;</pre><pre>&n=
 bsp;My guess would be a 32-bit issue in the virtio disk code, since that's<=
 /pre><pre>&nbsp;probably rarely used with 32-bit kernels.</pre><pre>&nbsp;<=
 /pre></blockquote><div>tracked down to probably is the processor the distri=
 bution was created.... &nbsp;I did the sequence using an amd64 8350 running=
  HEAD amd64</div><div>1) download the HEAD i386 &nbsp;iso from netbsd.org</=
 div><div>2) install the head in &nbsp;the VM</div><div>3) make the test, it=
  works, no problem &nbsp;(so the qemu, and host OS netbsd HEAD amd64) &nbsp=
 ;is ok</div><div><br></div><div>4) download the netbsd HEAD src in /usr/src=
 </div><div>5) build a custom kernel &nbsp;with users=3D128 no npf, pppoe se=
 rver....</div><div>6) copy the netbsd to /netbsd.NEW</div><div>7) boot from=
  the new kernel, .... the system works OK...</div><div><br></div><div>Concl=
 usion, the kernel built in an amd8350 using NetBSD amd64 HEAD, does not wor=
 k&nbsp;</div><div>it will only work if built on a i386 machine (can be a vm=
  on qemu) with a i386 gcc native compiler... using build.sh</div><div><br><=
 /div><div>probably the gcc compiler on amd64 produces wrong i386 code... at=
 omic OP issues???</div><div><br></div><div>well you can consider the PR clo=
 se with this advice...</div><div><br></div><div>Thank you</div><div class=
 =3D"-x-evo-signature-wrapper"><span class=3D"-x-evo-signature" id=3D"none">=
 </span></div></body></html>
 
 --=-nOg+dZnFAflE3mo85tgM--
 



Home | Main Index | Thread Index | Old Index