NetBSD-Bugs archive

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

Re: kern/55628: inserting blank disk into USB Floppy drive panics NetBSD 9.0/amd64



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

From: =?UTF-8?Q?J=C3=B6rn_Clausen?= <joernc%googlemail.com@localhost>
To: Martin Husemann <martin%duskware.de@localhost>
Cc: gnats-bugs%netbsd.org@localhost
Subject: Re: kern/55628: inserting blank disk into USB Floppy drive panics
 NetBSD 9.0/amd64
Date: Sun, 30 Aug 2020 21:21:11 +0200

 --000000000000fc71fe05ae1d30f9
 Content-Type: text/plain; charset="UTF-8"
 Content-Transfer-Encoding: quoted-printable
 
 Okay, the machine does not crash immediately! I can insert a floppy and get
 
 $ disklabel sd1
 # /dev/rsd1:
 type: ATAPI
 disk: FD-05PUW
 label: default label
 flags: removable
 bytes/sector: 512
 sectors/track: 0
 tracks/cylinder: 0
 sectors/cylinder: 0
 cylinders: 0
 total sectors: 536870911
 rpm: 0
 interleave: 1
 trackskew: 0
 cylinderskew: 0
 headswitch: 0           # microseconds
 track-to-track seek: 0  # microseconds
 drivedata: 0
 
 4 partitions:
 #        size    offset     fstype [fsize bsize cpg/sgs]
  a: 536870911         0     4.2BSD      0     0     0
  d: 536870911         0     unused      0     0
 
 Is it okay that sectors/track, tracks/cylinder and so on are 0 because they
 make no sense on a floppy?
 
 Trying to format the disk (newfs or newfs_msdos on /dev/sd1a or /dev/rsd1a)
 causes newfs* to core. Trying to copy the NetBSD install floppy with
 
 $ dd if=3Dboot1.fs of=3D/dev/rsd1d
 
 results in the same crash as before:
 
 [   273.925000] fatal integer divide fault in supervisor mode
 [   273.925000] trap type 8 code 0 rip 0xffffffff809fb829 cs 0x8 rflags
 0x10246 cr2 0x7e4a38da5000 ilevel 0 rsp 0xffffbf0063c16c90
 [   273.925000] curlwp 0xffff9e11ac420160 pid 2119.1 lowest kstack
 0xffffbf0063c142c0
 [   273.925000] panic: trap
 [   273.925000] cpu0: Begin traceback...
 [   273.925000] vpanic() at netbsd:vpanic+0x160
 [   273.925000] snprintf() at netbsd:snprintf
 [   273.925000] startlwp() at netbsd:startlwp
 [   273.925000] alltraps() at netbsd:alltraps+0xbb
 [   273.935009] dk_strategy1() at netbsd:dk_strategy1+0x17
 [   273.935009] dk_strategy() at netbsd:dk_strategy+0x12
 [   273.935009] physio() at netbsd:physio+0x2c8
 [   273.935009] spec_write() at netbsd:spec_write+0x58
 [   273.935009] VOP_WRITE() at netbsd:VOP_WRITE+0x50
 [   273.945016] vn_write() at netbsd:vn_write+0xfb
 [   273.945016] dofilewrite() at netbsd:dofilewrite+0x96
 [   273.945016] sys_write() at netbsd:sys_write+0x49
 [   273.945016] syscall() at netbsd:syscall+0x157
 
 On Sun, Aug 30, 2020 at 9:01 PM Martin Husemann <martin%duskware.de@localhost> wrote:
 
 > On Sun, Aug 30, 2020 at 08:58:22PM +0200, J=C3=B6rn Clausen wrote:
 > > Where would I find this kernel? Temporarily replacing the kernel is no
 > > problem, but updating the complete system is not an option for me.
 >
 >         http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/
 >
 > I suspect this will make it work and you can use that kernel with your
 > 9.0 userland w/o problems.
 >
 > We usually are quite carefull with changes on release branches, so a
 > userland
 > update is quite low risc too (but I can understand avoiding it if
 > everything
 > just works).
 >
 > Martin
 >
 
 
 --=20
 Joern Clausen
 https://www.oe-files.de/photography/
 
 --000000000000fc71fe05ae1d30f9
 Content-Type: text/html; charset="UTF-8"
 Content-Transfer-Encoding: quoted-printable
 
 <div dir=3D"ltr"><div>Okay, the machine does not crash immediately! I can i=
 nsert a floppy and get</div><div><br></div><div>$ disklabel sd1<br># /dev/r=
 sd1:<br>type: ATAPI<br>disk: FD-05PUW<br>label: default label<br>flags: rem=
 ovable<br>bytes/sector: 512<br>sectors/track: 0<br>tracks/cylinder: 0<br>se=
 ctors/cylinder: 0<br>cylinders: 0<br>total sectors: 536870911<br>rpm: 0<br>=
 interleave: 1<br>trackskew: 0<br>cylinderskew: 0<br>headswitch: 0 =C2=A0 =
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 # microseconds<br>track-to-track seek: 0 =C2=A0=
 # microseconds<br>drivedata: 0 <br><br>4 partitions:<br># =C2=A0 =C2=A0 =C2=
 =A0 =C2=A0size =C2=A0 =C2=A0offset =C2=A0 =C2=A0 fstype [fsize bsize cpg/sg=
 s]<br>=C2=A0a: 536870911 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 4.2BSD=
  =C2=A0 =C2=A0 =C2=A00 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 0 <br>=C2=A0d: 5368709=
 11 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 unused =C2=A0 =C2=A0 =C2=A00=
  =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 =C2=A0 <br></div><div><br></div><div>Is it o=
 kay that sectors/track, tracks/cylinder and so on are 0 because they make n=
 o sense on a floppy?<br></div><div><br></div><div>Trying to format the disk=
  (newfs or newfs_msdos on /dev/sd1a or /dev/rsd1a) causes newfs* to core. T=
 rying to copy the NetBSD install floppy with</div><div><br></div><div>$ dd =
 if=3Dboot1.fs of=3D/dev/rsd1d</div><div><br></div><div>results in the same =
 crash as before:</div><div><br></div><div>[ =C2=A0 273.925000] fatal intege=
 r divide fault in supervisor mode<br>[ =C2=A0 273.925000] trap type 8 code =
 0 rip 0xffffffff809fb829 cs 0x8 rflags 0x10246 cr2 0x7e4a38da5000 ilevel 0 =
 rsp 0xffffbf0063c16c90<br>[ =C2=A0 273.925000] curlwp 0xffff9e11ac420160 pi=
 d 2119.1 lowest kstack 0xffffbf0063c142c0<br>[ =C2=A0 273.925000] panic: tr=
 ap<br>[ =C2=A0 273.925000] cpu0: Begin traceback...<br>[ =C2=A0 273.925000]=
  vpanic() at netbsd:vpanic+0x160<br>[ =C2=A0 273.925000] snprintf() at netb=
 sd:snprintf<br>[ =C2=A0 273.925000] startlwp() at netbsd:startlwp<br>[ =C2=
 =A0 273.925000] alltraps() at netbsd:alltraps+0xbb<br>[ =C2=A0 273.935009] =
 dk_strategy1() at netbsd:dk_strategy1+0x17<br>[ =C2=A0 273.935009] dk_strat=
 egy() at netbsd:dk_strategy+0x12<br>[ =C2=A0 273.935009] physio() at netbsd=
 :physio+0x2c8<br>[ =C2=A0 273.935009] spec_write() at netbsd:spec_write+0x5=
 8<br>[ =C2=A0 273.935009] VOP_WRITE() at netbsd:VOP_WRITE+0x50<br>[ =C2=A0 =
 273.945016] vn_write() at netbsd:vn_write+0xfb<br>[ =C2=A0 273.945016] dofi=
 lewrite() at netbsd:dofilewrite+0x96<br>[ =C2=A0 273.945016] sys_write() at=
  netbsd:sys_write+0x49<br>[ =C2=A0 273.945016] syscall() at netbsd:syscall+=
 0x157<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
 =3D"gmail_attr">On Sun, Aug 30, 2020 at 9:01 PM Martin Husemann &lt;<a href=
 =3D"mailto:martin%duskware.de@localhost";>martin%duskware.de@localhost</a>&gt; wrote:<br></div><=
 blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
 eft:1px solid rgb(204,204,204);padding-left:1ex">On Sun, Aug 30, 2020 at 08=
 :58:22PM +0200, J=C3=B6rn Clausen wrote:<br>
 &gt; Where would I find this kernel? Temporarily replacing the kernel is no=
 <br>
 &gt; problem, but updating the complete system is not an option for me.<br>
 <br>
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://nycdn.netbsd.org/pub/NetBSD-d=
 aily/netbsd-9/latest/" rel=3D"noreferrer" target=3D"_blank">http://nycdn.ne=
 tbsd.org/pub/NetBSD-daily/netbsd-9/latest/</a><br>
 <br>
 I suspect this will make it work and you can use that kernel with your<br>
 9.0 userland w/o problems.<br>
 <br>
 We usually are quite carefull with changes on release branches, so a userla=
 nd<br>
 update is quite low risc too (but I can understand avoiding it if everythin=
 g<br>
 just works).<br>
 <br>
 Martin<br>
 </blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g=
 mail_signature">Joern Clausen<br><a href=3D"https://www.oe-files.de/photogr=
 aphy/" target=3D"_blank">https://www.oe-files.de/photography/</a></div>
 
 --000000000000fc71fe05ae1d30f9--
 


Home | Main Index | Thread Index | Old Index