Date: Mon, 08 Jul 2019 09:47:04 -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: <2cb61449e11644c2758c9bf75434f424c042f7cb.camel@freebsd.org> In-Reply-To: <575189220.318858.1562577407386.JavaMail.yahoo@jws704003.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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> > Can you post a backtrace of this panic please? (enter 'bt' at the db> prompt). Also, if you need a quick fix, try reverting r348164. it is most likely the cause of the problem. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2cb61449e11644c2758c9bf75434f424c042f7cb.camel>