linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Benton <b3nton@gmail.com>
To: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [drm:radeon_dp_i2c_aux_ch] *ERROR* aux i2c too many retries, giving up
Date: Wed, 19 Oct 2011 19:28:55 +0100	[thread overview]
Message-ID: <20111019192855.73e45b54.b3nton@gmail.com> (raw)

Hello,

Please cc me in any replies as I'm not subscribed.

When booting a 3.1.0-rc10 kernel, right at the start I get an error
message printed to the screen:

[drm:radeon_dp_i2c_aux_ch] *ERROR* aux i2c too many retries, giving up

It's a quad core computer and it prints it 4 times. On another computer
which is a dual core it prints the message twice. Both computers have
Radeon graphics cards which need firmware compiled into the kernel to
work. This computer uses BARTS_mc.bin, BARTS_me.bin, BARTS_pfp.bin and
BTC_rlc.bin. The kitchen computer uses REDWOOD_rlc.bin, REDWOOD_pfp.bin
and REDWOOD_me.bin. Both computers seem to be working fine as far as I
can see. Is this error message something to be concerned about? I
thought the radeon driver uses i2c to enable sensors to report the
temperature of the card, but that seems to be working fine. I boot with
the quite command line argument and it gets rid of most kernel output,
but not these error messages. Is there some way I can get rid of these
alarming messages? Some kernel option that will make them just complain
to the kernel log? Or is there some option I should enable to keep the
radeon i2c whatever it is happy?

Andy

             reply	other threads:[~2011-10-19 18:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 18:28 Andrew Benton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-24 12:35 [drm:radeon_dp_i2c_aux_ch] *ERROR* aux i2c too many retries, giving up Andrew Benton

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=20111019192855.73e45b54.b3nton@gmail.com \
    --to=b3nton@gmail.com \
    --cc=linux-kernel@vger.kernel.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).