Date: Mon, 08 Jul 2019 14:28:15 -0600 From: Ian Lepore <ian@freebsd.org> To: Mori Hiroki <yamori813@yahoo.co.jp>, "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: panic on 13-CURRENT Message-ID: <9b79447e8b6311ea5a1bc7843b589dd6bb0e61f8.camel@freebsd.org> In-Reply-To: <509265059.344183.1562613041849.JavaMail.yahoo@jws704001.mail.kks.yahoo.co.jp> References: <575189220.318858.1562577407386.JavaMail.yahoo.ref@jws704003.mail.kks.yahoo.co.jp> <575189220.318858.1562577407386.JavaMail.yahoo@jws704003.mail.kks.yahoo.co.jp> <76d35d595aa4b1ede98157b8b4210dd7e60ca52e.camel@freebsd.org> <509265059.344183.1562613041849.JavaMail.yahoo@jws704001.mail.kks.yahoo.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
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@freebsd.org> > > To: Mori Hiroki <yamori813@yahoo.co.jp>; "freebsd-mips@freebsd.org" <freebsd-mips@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9b79447e8b6311ea5a1bc7843b589dd6bb0e61f8.camel>