Bug 27872

Summary: [sysinstall] "Load Config" hangs Compaq DL360 when used during installation
Product: Base System Reporter: jguard <jguard>
Component: binAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description jguard 2001-06-04 13:00:15 UTC
When attempting to use the "Load Config" option on a Compaq DL360
sysinstall "hangs" and stops responding.  The following is output on
the second tty:

DEBUG: Init floppy called for install.cfg distribution
fdc0: direction bit not set
fdc0: cmd 3 failed at out byte 1 of 3
fdc0: direction bit not set
fdc0: cmd 13 failed at out byte 1 of 4
fdc0: Re-enable FIFO failed
fdc0: direction bit not set
fdc0: cmd 8 failed at out byte 1 of 1
fdc0: sense intr err reading stat reg 0
fdc0: direction bit not set
fdc0: cmd 8 failed at out byte 1 of 1
fdc0: sense intr err reading stat reg 0
fdc0: direction bit not set
fdc0: cmd 8 failed at out byte 1 of 1
fdc0: sense intr err reading stat reg 0
fdc0: direction bit not set
fdc0: cmd 8 failed at out byte 1 of 1
fdc0: sense intr err reading stat reg 0
fdc0: direction bit not set
fdc0: cmd 7 failed at out byte 1 of 2
fdc0: direction bit not set
fdc0: cmd 3 failed at out byte 1 of 3
fdc0: direction bit not set
fdc0: cmd 13 failed at out byte 1 of 4


The same occurs if an attempt is made to use a repair floppy.

This occurs on more than one Compaq DL360.  The floppy drive does not
appear to be accessed at all (no seek, or motor spin noticeable).

The floppy disk used is an MSDOS format floppy that can be mounted and
modifiied on the same computer once the OS has been installed.  However
as the floppy does not appear to be accessed, any floppy disk gives 
the above symptoms

Fix: 

None known
How-To-Repeat: On a Compaq DL360 boot from the 4.3 Release, put a floppy disk 
(any floppy disk will do) and select the "Load Config" option at the
sysinstall Main Menu.

sysinstall will hang, and the second tty will display the fdc errors.
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2003-07-19 00:00:43 UTC
Responsible Changed
From-To: freebsd-bugs->qa

Assign to qa group
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2005-12-19 02:25:32 UTC
State Changed
From-To: open->feedback

Is this still a problem with modern versions of FreeBSD?
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2007-06-14 07:08:47 UTC
State Changed
From-To: feedback->closed

Feedback timeout (> 1 year).