Date: Sun, 4 Aug 2019 09:05:49 -0500 From: Jason Bacon <bacon4000@gmail.com> To: Francis Little <oggy@farscape.co.uk> Cc: Justin Hibbits <jrh29@alumni.cwru.edu>, "freebsd-ppc@freebsd.org" <freebsd-ppc@freebsd.org> Subject: Re: iichb0: I2C error Message-ID: <a7f296d6-e076-0a51-b526-77304bf9271b@gmail.com> In-Reply-To: <4f028f90-cb0f-1369-f8c8-bcf4f52185fe@gmail.com> References: <bde639cb-bfab-3da3-f896-538c540b25b7@gmail.com> <CAHSQbTDDaJ0c%2B_E4T0YGbAdVka3bnFP9Rec71j2c2qToYFqLuQ@mail.gmail.com> <7cd57279-ee80-ef46-13e5-aa7f02f14bfa@gmail.com> <bd85cb86-d742-5382-ae32-4cff6ca7c1d7@gmail.com> <CAGSRtz5ss5TUp5oiLChr2nxxE=o%2BegODQ-a6VY-MFC7jC%2Bk5Xg@mail.gmail.com> <4f028f90-cb0f-1369-f8c8-bcf4f52185fe@gmail.com>
index | next in thread | previous in thread | raw e-mail
Just rebooted again and now everything is fine. No I2C issues, sysctl works fine. The seemingly random nature of the problem suggests a to me an uninitialized variable. I don't know much about FreeBSD I2C drivers, though, so that's just a quasi-educated guess. On 2019-08-04 08:54, Jason Bacon wrote: > > sysctl just hangs here: > > root@powermacg5:/home/bacon # sysctl -a|grep temp > net.inet6.ip6.use_tempaddr: 0 > net.inet6.ip6.temppltime: 86400 > net.inet6.ip6.tempvltime: 604800 > net.inet6.ip6.prefer_tempaddr: 0 > hw.usb.template: -1 > > Then dmesg shows: > > iichb0: I2C error > ad74171: iicbus write failed > ad74171: iicbus write failed > ad74171: iicbus write failed > ad74171: iicbus write failed > ad74171: iicbus write failed > ad74171: iicbus read failed > ad74171: iicbus read failed > ad74171: iicbus write failed > ad74171: iicbus write failed > ad74171: iicbus write failed > ad74171: iicbus write failed > ad74171: iicbus read failed > ad74171: iicbus write failed > ad74171: iicbus write failed > ad74171: iicbus write failed > ad74171: iicbus read failed > > Again, this is on 12.0-RELEASE and I use it only for ports testing. > > Thanks, > > JB > > On 2019-08-04 08:46, Francis Little wrote: >> 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 <bacon4000@gmail.com >> <mailto:bacon4000@gmail.com>> 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 >> <bacon4000@gmail.com <mailto:bacon4000@gmail.com>> 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. >> >> >> _______________________________________________ >> freebsd-ppc@freebsd.org <mailto:freebsd-ppc@freebsd.org> mailing >> list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc >> To unsubscribe, send any mail to >> "freebsd-ppc-unsubscribe@freebsd.org >> <mailto:freebsd-ppc-unsubscribe@freebsd.org>" >> > > -- Earth is a beta site.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a7f296d6-e076-0a51-b526-77304bf9271b>