From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: windfarm_fcu_controls: cpu-pump-0 <HW FAULT>
Date: Sat, 03 Aug 2013 18:44:53 +1000 [thread overview]
Message-ID: <1375519493.15999.83.camel@pasglop> (raw)
In-Reply-To: <m2vc3nnp01.fsf@linux-m68k.org>
On Sat, 2013-08-03 at 10:43 +0200, Andreas Schwab wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
>
> > Can you add some more printk's in there to check what's going on inside
> > wf_fcu_get_pump_minmax() ?
>
> All values from mpu->processor_part_num are 0xffff.
>
> > Also is it getting faults for both pumps ?
>
> Yes.
>
> > Does it work with the older driver ? (both the minmax and the reading of
> > the pump).
>
> The minmax situation is the same, but otherwise appears to work (no fan
> reading errors logged). Here is an example debug output:
Odd. Can you try to trace if there is any significant difference in the
i2c messages used ? Some typo I might have done somewhere ?
Something I might do at init time that puts them into a faulty state ?
I don't have one of these anymore (mine died) so I can't really test.
Cheers,
Ben.
> ** CPU 1 RPM: 300 Ex, 300, Pump: 1250, In, overtemp: 0
> cpu 0, exhaust RPM: 300
> cpu 0, temp raw: 023c, m_diode: 9982, b_diode: fffff799
> temp: 52.139
> cpu 0, current: 8.789, voltage: 1.286, power: 11.308 W
> cpu 1, exhaust RPM: 300
> cpu 1, temp raw: 021c, m_diode: a047, b_diode: fffff777
> temp: 50.380
> cpu 1, current: 8.666, voltage: 1.281, power: 11.108 W
> power target: 55.000, error: 43.691
> integral: 00f42f8d
> integ_p: 10
> adj_in_target: 65.011, ttarget: 74
> deriv_p: -15
> prop_p: -103
> sum: -118
>
> > What is the "failures" bitmask value ?
>
> 3 for both.
>
> Andreas.
>
next prev parent reply other threads:[~2013-08-03 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 19:08 windfarm_fcu_controls: cpu-pump-0 <HW FAULT> Andreas Schwab
2013-08-02 22:10 ` Benjamin Herrenschmidt
[not found] ` <1375481448.15999.47.camel__48019.1930350431$1375481501$gmane$org@pasglop>
2013-08-03 8:43 ` Andreas Schwab
2013-08-03 8:44 ` Benjamin Herrenschmidt [this message]
[not found] ` <1375519493.15999.83.camel__49452.0221990117$1375519543$gmane$org@pasglop>
2013-08-03 13:49 ` Andreas Schwab
2013-08-04 2:20 ` Benjamin Herrenschmidt
[not found] ` <87r4eahoka.fsf__2165.9838072539$1375537818$gmane$org@igel.home>
2013-08-03 14:33 ` Andreas Schwab
2013-08-04 2:21 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1375519493.15999.83.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).