Date: Sun, 4 Aug 2019 08:37:42 -0500 From: Jason Bacon <bacon4000@gmail.com> To: Justin Hibbits <jrh29@alumni.cwru.edu> Cc: "freebsd-ppc@freebsd.org" <freebsd-ppc@freebsd.org> Subject: Re: iichb0: I2C error Message-ID: <bd85cb86-d742-5382-ae32-4cff6ca7c1d7@gmail.com> In-Reply-To: <7cd57279-ee80-ef46-13e5-aa7f02f14bfa@gmail.com> References: <bde639cb-bfab-3da3-f896-538c540b25b7@gmail.com> <CAHSQbTDDaJ0c%2B_E4T0YGbAdVka3bnFP9Rec71j2c2qToYFqLuQ@mail.gmail.com> <7cd57279-ee80-ef46-13e5-aa7f02f14bfa@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-07-14 20:58, Jason Bacon wrote: > On 2019-07-14 19:46, Justin Hibbits wrote: >> On Sat, Jul 13, 2019 at 9:32 AM Jason Bacon <bacon4000@gmail.com> wrot= e: >>> >>> On my PowerMac G5, I consistently get this error after a cold boot: >>> >>> iichb0: I2C error >>> >>> After a minute or so, the fans ramp up to maximum. >>> >>> The error also consistently goes away after a warm reboot. Nothing mo= re >>> in dmesg: >>> >>> FreeBSD powermacg5.acadix=C2=A0 bacon ~ 211: dmesg|grep iichb0 >>> iichb0: <Keywest I2C controller> mem 0xf8001000-0xf8001fff irq 42 on = >>> unin0 >>> iicbus0: <OFW I2C bus> on iichb0 >>> iichb0: I2C error >>> iichb0: <Keywest I2C controller> mem 0xf8001000-0xf8001fff irq 42 on = >>> unin0 >>> iicbus0: <OFW I2C bus> on iichb0 >>> >>> No more runaway fans. >>> >>> Does this provide any clues about the cause? >> Hi Jason, >> >> How recently did this start occurring?=C2=A0 Would you be able to bise= ct >> the builds from a known-good starting point? >> >> Thanks. >> >> - Justin > I've never run a powerpc system until a few months ago, and this has=20 > always been an issue on the PowerMac.=C2=A0 I just recently established= the=20 > pattern that it only happens after a cold boot, though.=C2=A0 I also ha= ve=20 > an iMac G5 that does not exhibit this issue. Both are running=20 > 12.0-RELEASE.=C2=A0 If you think it might help, I can try a 13 snapshot= at=20 > some point. > > Cheers, > > =C2=A0=C2=A0=C2=A0 JB > Cancel that pattern claim.=C2=A0 I've now seen it occur after a couple of= =20 warm boots as well.=C2=A0 If I keep rebooting the problem eventually stop= s. Always seems to follow I2C error in dmesg, though. Trying to mount root from ufs:/dev/ada0s3 [rw]... SMP: 2 CPUs found; 2 CPUs usable; 1 CPUs woken lo0: link state changed to UP gem0: link state changed to DOWN gem0: link state changed to UP Security policy loaded: MAC/ntpd (mac_ntpd) iichb0: I2C error FreeBSD powermacg5.acadix=C2=A0 bacon ~ 835: Fans go nuts after a few minutes. Reboot... Trying to mount root from ufs:/dev/ada0s3 [rw]... SMP: 2 CPUs found; 2 CPUs usable; 1 CPUs woken lo0: link state changed to UP gem0: link state changed to DOWN gem0: link state changed to UP Security policy loaded: MAC/ntpd (mac_ntpd) FreeBSD powermacg5.acadix=C2=A0 bacon ~ 835: No fan issues. --=20 Earth is a beta site.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bd85cb86-d742-5382-ae32-4cff6ca7c1d7>