Re: iichb0: I2C error
Francis Little <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.ppc |
|---|---|
| Message-ID | <CAGSRtz5ss5TUp5oiLChr2nxxE=o+egODQ-a6VY-MFC7jC+k5Xg@mail.gmail.com> |
Hi, I get loud fans on my G5 after a few mins (running 13-CURRENT). When the fans rev up, If you run something like: sysctl -a | grep temp: do they calm down? On mine it does so I have it in my crontab every 60 secs at the moment! Regards On Sun, 4 Aug 2019 at 14:38, Jason Bacon <[email protected]> wrote: > 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 <[email protected]> > wrote: > >>> > >>> 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 more > >>> in dmesg: > >>> > >>> FreeBSD powermacg5.acadix 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? Would you be able to bisect > >> 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 > > always been an issue on the PowerMac. I just recently established the > > pattern that it only happens after a cold boot, though. I also have > > an iMac G5 that does not exhibit this issue. Both are running > > 12.0-RELEASE. If you think it might help, I can try a 13 snapshot at > > some point. > > > > Cheers, > > > > JB > > > Cancel that pattern claim. I've now seen it occur after a couple of > warm boots as well. If I keep rebooting the problem eventually stops. > > 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 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 bacon ~ 835: > > No fan issues. > > -- > Earth is a beta site. > > > _______________________________________________ > [email protected] mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "[email protected]" > _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ppc To unsubscribe, send any mail to "[email protected]"