cvs commit: src/sys/dev/fdc fdc.c fdc_isa.c fdc_pccard.c fdcvar.h

[M. Warner Losh]

In message: <20040920005727.GA3513 at VARK.MIT.EDU>
            David Schultz <das at FreeBSD.ORG> writes:
: On Sun, Sep 19, 2004, Nate Lawson wrote:
: > David Schultz wrote:
: > >On Tue, Sep 14, 2004, Warner Losh wrote:
: > >
: > >>imp         2004-09-14 07:06:49 UTC
: > >>
: > >> FreeBSD src repository
: > >>
: > >> Modified files:
: > >>   sys/dev/fdc          fdc.c fdc_isa.c fdc_pccard.c fdcvar.h 
: > >> Log:
: > >> Checkpoint the fdc resource changes:
: > >> 
: > >> o Allow for up to 3 resource I/O ranges to be given for the floppy
: > >>   controller, rather than just two that are allowed for now.
: > >> o Make sure that we can work with either a base address of 0x3f0 or 
: > >> 0x3f2.
: > >> o Create new inline functions to access the YE DATA's unique BDCR 
: > >> register.
: > >> o Update pccard attachment to add the fd device.
: > >> o Do some minor style(9) polishing.
: > >
: > >
: > >Hmm...this causes my system to hang immediately before the point
: > >where I would expect GEOM to report that it had tasted ad0.  Any
: > >ideas what's going on?  Below is the resulting kernel message
: > >buffer, truncated due to ata(4) verbosity.  This is with
: > >bootverbose, geom.debugflags=7, and debug.fdc.debugflags=0xff.  If
: > >you need any other information (e.g. ps output) please let me
: > >know and I'll try to dig up a serial cable.
: > 
: > It's likely the geom probe of the floppy media.  [...]
: 
: Yep.  With this commit, fdc gets confused about whether there's a
: disk in there or not, which causes it to deadlock against the
: g_event thread.  I've been discussing this with phk and Warner,
: and I believe Warner is working on the problem.  Thanks for the hints.

Actually, it only does for the even weirder resource stuff that you
have.

Warner