From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Dave Airlie <airlied@gmail.com>, Dave Airlie <airlied@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
dri-devel@lists.sourceforge.net
Subject: Re: [Regression, post-rc1] Multiple issues after enabling SetVoltage on rs780m
Date: Mon, 7 Jun 2010 23:37:17 +0200 [thread overview]
Message-ID: <201006072337.17778.rjw@sisk.pl> (raw)
In-Reply-To: <AANLkTilerIhYtHlX0vNAg_pfG_1100OymKV4aaGv-VSE@mail.gmail.com>
On Monday 07 June 2010, Alex Deucher wrote:
> On Mon, Jun 7, 2010 at 6:15 AM, Dave Airlie <airlied@gmail.com> wrote:
> > On Mon, Jun 7, 2010 at 7:29 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >> Hi Alex,
> >>
> >> Your commit 9349d5cc920c10845693f906ebd67f394f1d0d04
> >> (drm/radeon/kms/pm: enable SetVoltage on r7xx/evergreen) has caused my test-bed
> >> Acer Ferrari One to behave quite unreliably. The symptoms are:
> >>
> >> - the system hangs hard (~ 50% of the time) when starting Xorg
> >> - the system hangs hard (~ 50% of the time) when stopping Xorg during system
> >> reboot
> >> - the system sometimes hangs hard during suspend to RAM
> >>
> >> These problems are not reproducible with the commit above reverted.
> >>
> >> Below is the information about the graphics adapter from lspci.
> >
> > Reverting that commit on master fixes it?
> >
> > that commit touches code paths in rv770 and evergreen that in no way
> > should affect that chipset which is an rs780, so takes the r600 paths.
> >
> > are you sure its not 7ac9aa5a1f1b87adb69bcbec2b89e228f074103a?
>
> It should be that commit if it is indeed the voltage adjust. That
> said, I just took a closer look at the voltage adjust on newer IGPs
> and unfortunately, it doesn't work the same as the discrete cards, so
> for now we should disable it. The attached patch should do the trick.
> There weren't any problems on my IGP chips, but they don't have a
> SetVoltage table, so nothing is touching the hw.
I'm not sure if the adapter is a discrete one.
Anyway, my testing was done before commit
386f40c86d6c8d5b717ef20620af1a750d0dacb4 and I'm unable to reproduce the
problems with current -git, so they might be a fallout of the bug fixed by that
commit.
Thanks,
Rafael
next prev parent reply other threads:[~2010-06-07 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 9:29 Rafael J. Wysocki
2010-06-07 10:15 ` Dave Airlie
2010-06-07 15:50 ` Alex Deucher
2010-06-07 21:37 ` Rafael J. Wysocki [this message]
2010-06-07 22:37 ` Dave Airlie
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=201006072337.17778.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome