panic on 13-CURRENT

[Ian Lepore]

On Tue, 2019-07-09 at 04:10 +0900, Mori Hiroki wrote:
> Hi
> 
> Thanks for your reply.
> 
> I do comment out device_busy() and device_unbusy() then work fine.
> 
> http://dmesgd.nycbug.org/index.cgi?do=view&id=5050
> 
> Hiroki Mori
> 
> ----- Original Message -----
> > From: Ian Lepore <ian at freebsd.org>
> > To: Mori Hiroki <yamori813 at yahoo.co.jp>; "freebsd-mips at freebsd.org" <freebsd-mips at freebsd.org>
> > Cc: 
> > Date: 2019/7/9, Tue 01:15
> > Subject: Re: panic on 13-CURRENT
> > 
> > On Mon, 2019-07-08 at 18:16 +0900, Mori Hiroki wrote:
> > >   Hi
> > > 
> > >   I try to 13-CURRENT today.
> > > 
> > >   I have panic on Atheros target.
> > > 
> > >   [...]
> > >   gpioiic0: <GPIO I2C bit-banging driver> at pins 19-20 on gpiobus0
> > >   gpioiic0: SCL pin: 20, SDA pin: 19
> > >   iicbb0: <I2C bit-banging driver> on gpioiic0
> > >   iicbus0: <Philips I2C bus> on iicbb0 master-only
> > >   iic0: <I2C generic I/O> on iicbus0
> > >   panic: device_busy: called for unattached device
> > >   time = 1
> > >   KDB: enter: panic
> > >   [ thread pid 0 tid 100000 ]
> > >   Stopped at      _DYNAMIC_LINKING+0x3:
> > >   db>
> > > 
> > 
> > I think I figured it out... the rtl8366rb driver is doing IO in its
> > probe routine, which means the device isn't attached yet.  Now I just
> > have to figure out how to fix it.  Reverting r348164 will get you past
> > the error and let you test other things while I work on it.
> > 
> > -- Ian
> > 
> 

This should now be fixed in r349850.  Sorry for the breakage.

-- Ian