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

To: kern-bug-people%netbsd.org@localhost,gnats-admin%netbsd.org@localhost,netbsd-bugs%netbsd.org@localhost,joernc%gmail.com@localhost
Subject: Re: kern/55628: inserting blank disk into USB Floppy drive panics NetBSD 9.0/amd64
From: Jörn Clausen <joernc%googlemail.com@localhost>
Date: Sun, 30 Aug 2020 20:05:02 +0000 (UTC)

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 22:04:34 +0200

 --00000000000018626a05ae1dccc8
 Content-Type: text/plain; charset="UTF-8"
 
 On Sun, Aug 30, 2020 at 9:25 PM Martin Husemann <martin%duskware.de@localhost> wrote:
 
 > Are there any kernel messages printed when inserting the disk?
 >
 
 No. There is brief access to the disk, but no messages are logged.
 
 You quoted the dmesg from the empty drive at attack time, but that did
 > not have any geometry data yet.
 >
 
 Without a disk inserted, disklabel shows
 
 disklabel: /dev/rsd1: Operation not supported by device
 
 Booting with a disk inserted results again in a crash. Right after sd1 is
 detected, the message
 
 sd1: unformatted media
 
 is shown. Although the kernel debugger is started, I cannot use it with my
 USB keyboard (which normally is the case). It looks as if USB is borked at
 that point.
 
 When I boot without the drive and attach it with a disk inserted, the same
 message as above is shown.
 
 According to the box the disks should be "IBM formatted". I just tried it
 on a Windows box, and the disk was shown as unformatted. After formatting
 it there, it is now usable under NetBSD:
 
 [ 867.6658131] sd1 at atapibus0 drive 0: <TEAC, FD-05PUW, 3000> disk
 removable
 [ 868.7570577] sd1: 1440 KB, 80 cyl, 2 head, 18 sec, 512 bytes/sect x 2880
 sectors
 
 $ disklabel sd1
 # /dev/rsd1:
 type: ATAPI
 disk: FD-05PUW
 label: default label
 flags: removable
 bytes/sector: 512
 sectors/track: 18
 tracks/cylinder: 2
 sectors/cylinder: 36
 cylinders: 80
 total sectors: 2880
 rpm: 7680
 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:      2880         0     4.2BSD      0     0     0  # (Cyl.      0 -
 79)
  d:      2880         0     unused      0     0        # (Cyl.      0 -
 79)
 disklabel: boot block size 0
 disklabel: super block size 0
 
 $ mount_msdos /dev/sd1a /mnt
 
 $ df -k /mnt
 Filesystem    1K-blocks       Used      Avail %Cap Mounted on
 /dev/sd1a          1423          1       1422   0% /mnt
 
 And dd'ing the boot image to /dev/rsd1d now also works.
 
 I then tried "fdformat" on all combinations (sd1 and rsd1, partition a and
 d), but always got
 
 fdformat: Device `/dev/rsd1a' does not support floppy formatting:
 Inappropriate ioctl for device
 
 -- 
 Joern Clausen
 https://www.oe-files.de/photography/
 
 --00000000000018626a05ae1dccc8
 Content-Type: text/html; charset="UTF-8"
 Content-Transfer-Encoding: quoted-printable
 
 <div dir=3D"ltr">On Sun, Aug 30, 2020 at 9:25 PM Martin Husemann &lt;<a hre=
 f=3D"mailto:martin%duskware.de@localhost"; target=3D"_blank">martin%duskware.de@localhost</a>&gt=
 ; wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" st=
 yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
 ing-left:1ex">Are there any kernel messages printed when inserting the disk=
 ?<br></blockquote><div><br></div><div>No. There is brief access to the disk=
 , but no messages are logged.</div><div> <br></div><blockquote class=3D"gma=
 il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
 04,204);padding-left:1ex">
 You quoted the dmesg from the empty drive at attack time, but that did<br>
 not have any geometry data yet.<br></blockquote><div><br></div><div>Without=
  a disk inserted, disklabel shows</div><div><br></div><div> disklabel: /dev=
 /rsd1: Operation not supported by device</div><div><br></div><div>Booting w=
 ith a disk inserted results again in a crash. Right after sd1 is detected, =
 the message</div><div><br></div><div>sd1: unformatted media</div><div><br><=
 /div><div>is shown. Although the kernel debugger is started, I cannot use i=
 t with my USB keyboard (which normally is the case). It looks as if USB is =
 borked at that point.<br></div><div><br></div><div>When I boot without the =
 drive and attach it with a disk inserted, the same message as above is show=
 n.</div><div><br></div><div>According to the box the disks should be &quot;=
 IBM formatted&quot;. I just tried it on a Windows box, and the disk was sho=
 wn as unformatted. After formatting it there, it is now usable under NetBSD=
 :</div><div><br></div><div>[ 867.6658131] sd1 at atapibus0 drive 0: &lt;TEA=
 C, FD-05PUW, 3000&gt; disk removable<br>[ 868.7570577] sd1: 1440 KB, 80 cyl=
 , 2 head, 18 sec, 512 bytes/sect x 2880 sectors</div><div><br></div><div>$ =
 disklabel sd1<br># /dev/rsd1:<br>type: ATAPI<br>disk: FD-05PUW<br>label: de=
 fault label<br>flags: removable<br>bytes/sector: 512<br>sectors/track: 18<b=
 r>tracks/cylinder: 2<br>sectors/cylinder: 36<br>cylinders: 80<br>total sect=
 ors: 2880<br>rpm: 7680<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 fs=
 type [fsize bsize cpg/sgs]<br>=C2=A0a: =C2=A0 =C2=A0 =C2=A02880 =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 =C2=A0# (Cyl. =C2=A0 =C2=A0 =C2=A00 - =C2=A0 =C2=A0 7=
 9)<br>=C2=A0d: =C2=A0 =C2=A0 =C2=A02880 =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 =C2=A0# (Cyl. =C2=A0 =C2=A0 =C2=A00 - =C2=A0 =C2=A0 79)<br>disklabel: b=
 oot block size 0<br>disklabel: super block size 0</div><div><br></div><div>=
 $ mount_msdos /dev/sd1a /mnt</div><div><br></div><div>$ df -k /mnt<br>Files=
 ystem =C2=A0 =C2=A01K-blocks =C2=A0 =C2=A0 =C2=A0 Used =C2=A0 =C2=A0 =C2=A0=
 Avail %Cap Mounted on<br>/dev/sd1a =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01423 =
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01 =C2=A0 =C2=A0 =C2=A0 1422 =C2=A0 0% /mn=
 t</div><div><br></div><div>And dd&#39;ing the boot image to /dev/rsd1d now =
 also works.</div><div><br></div><div>I then tried &quot;fdformat&quot; on a=
 ll combinations (sd1 and rsd1, partition a and d), but always got</div><div=
 ><br></div><div>fdformat: Device `/dev/rsd1a&#39; does not support floppy f=
 ormatting: Inappropriate ioctl for device<br></div><div></div></div><div><b=
 r></div>-- <br><div dir=3D"ltr">Joern Clausen<br><a href=3D"https://www.oe-=
 files.de/photography/" target=3D"_blank">https://www.oe-files.de/photograph=
 y/</a></div></div>
 
 --00000000000018626a05ae1dccc8--

Prev by Date: NetBSD Nightly Trouble Ticket Report
Next by Date: kern/55629: execsnoop + t_origin = panic
Previous by Thread: Re: kern/55628: inserting blank disk into USB Floppy drive panics NetBSD 9.0/amd64
Next by Thread: kern/55629: execsnoop + t_origin = panic
Indexes:

Home | Main Index | Thread Index | Old Index