Subject: Re: kern/18395
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: Freidank, Kenneth <Kenneth.Freidank@delta.com>
List: netbsd-bugs
Date: 11/21/2005 19:33:02
The following reply was made to PR kern/18395; it has been noted by GNATS.
From: "Freidank, Kenneth" <Kenneth.Freidank@delta.com>
To: <gnats-bugs@NetBSD.org>
Cc:
Subject: Re: kern/18395
Date: Mon, 21 Nov 2005 14:32:28 -0500
This is a multi-part message in MIME format.
------_=_NextPart_001_01C5EED2.4F101081
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
External USB 1.4 M floppy on GENERIC Kernel release 2.1 works on an IBM
Thinkpad 1160 (laptop Kernel would not boot). Floppy part number
specifications are IBM p/n 19308800-09, ASM p/n 05K9282, FRU pn 05K9283,
Teac model FD-05PUB.
Use the following mount command and it works fine as file system /mnt
mount -t msdos /dev/sd0d /mnt
It does not matter into which port I hot plug my drive.
'dmesg' brings up the following which makes it seem as though there is a
problem, but there isn't after using the above mount command.
(the following is repeated 3 times by dmesg)
....
sd0 at atapibus1 drive 0: <TEAC, FD-05PUB, 1026> disk removable
sd0: drive offline
sd0(umass0:0:0): Check Condition on CDB: 0x00 00 00 00 00 00
SENSE KEY: Not Ready
ASC/ASCQ: Medium Not Present
....
However.....
Do NOT remove the floppy while mounted!! You risk crashing the kernel
to the DB> prompt. After placing the following line "/dev/sd0d /floppy
msdos rw 0 0" in /etc/fstab, I tried several times to recreate the
crash, but I could not. I could only corrupt the file system /floppy,
and then repair it by "umount /floppy" followed by "mount /floppy".
After corrupting and correcting the /floppy file system with a
umount/mount sequence, the command "dmesg" appended the same above
sequence (sd0 at atapibus....) to its output, reporting sd0 as being
offline, even though I can read and write to the floppy.
------_=_NextPart_001_01C5EED2.4F101081
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7226.0">
<TITLE>Re: kern/18395</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=3D2 FACE=3D"Arial">External USB 1.4 M floppy on GENERIC =
Kernel release 2.1 works on an IBM Thinkpad 1160 (laptop Kernel would =
not boot). Floppy part number specifications are IBM p/n =
19308800-09, ASM p/n 05K9282, FRU pn 05K9283, Teac model =
FD-05PUB.</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Use the following mount command and it =
works fine as file system /mnt</FONT>
<BR> <FONT SIZE=3D2 =
FACE=3D"Arial">mount -t msdos /dev/sd0d /mnt</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">It does not matter into which port I =
hot plug my drive.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">'dmesg' brings up the following which =
makes it seem as though there is a problem, but there isn't after using =
the above mount command.</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">(the following is repeated 3 times by =
dmesg)</FONT>
<BR> <FONT SIZE=3D2 =
FACE=3D"Arial">….</FONT>
<BR> <FONT SIZE=3D2 =
FACE=3D"Arial">sd0 at atapibus1 drive 0: <TEAC, FD-05PUB, 1026> =
disk removable</FONT>
<BR> <FONT SIZE=3D2 =
FACE=3D"Arial">sd0: drive offline</FONT>
<BR> <FONT SIZE=3D2 =
FACE=3D"Arial">sd0(umass0:0:0): Check Condition on CDB: 0x00 00 00 =
00 00 00</FONT>
<BR> <FONT SIZE=3D2 =
FACE=3D"Arial"> SENSE KEY: Not Ready</FONT>
<BR> <FONT SIZE=3D2 =
FACE=3D"Arial"> ASC/ASCQ: Medium Not =
Present</FONT>
<BR> <FONT SIZE=3D2 =
FACE=3D"Arial">….</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">However…..</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Do NOT remove the floppy while =
mounted!! You risk crashing the kernel to the DB> prompt. =
After placing the following line "/dev/sd0d /floppy msdos rw 0 =
0" in /etc/fstab, I tried several times to recreate the crash, but =
I could not. I could only corrupt the file system /floppy, and =
then repair it by "umount /floppy" followed by "mount =
/floppy". After corrupting and correcting the /floppy file =
system with a umount/mount sequence, the command "dmesg" =
appended the same above sequence (sd0 at atapibus….) to its =
output, reporting sd0 as being offline, even though I can read and write =
to the floppy.</FONT></P>
</BODY>
</HTML>
------_=_NextPart_001_01C5EED2.4F101081--