lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADnq5_NyYA3pkUPxHPp8LzDJ3HnEWD1oJ2r93E2n-urBaLWm7w@mail.gmail.com>
Date:	Tue, 18 Dec 2012 12:29:54 -0500
From:	Alex Deucher <alexdeucher@...il.com>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Christian König <deathsimple@...afone.de>,
	Jerome Glisse <jglisse@...hat.com>,
	linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH] [RFC] drm/radeon: return 0 on successful gpu reset

On Tue, Dec 18, 2012 at 12:28 PM, Paul Bolle <pebolle@...cali.nl> wrote:
> On Tue, 2012-12-18 at 10:22 -0500, Alex Deucher wrote:
>> On Tue, Dec 18, 2012 at 5:36 AM, Christian König
>> <deathsimple@...afone.de> wrote:
>> > On 17.12.2012 22:31, Paul Bolle wrote:
>> >> 1) Sent as an RFC because I do not understand why this laptop (almost
>> >> always) prints the "crtc 1" message on first resume. Note that another
>> >> workaround for this hang is simply booting with "radeon.tv=0".
>> >
>> > Alex should probably take a look into this, since he probably is the one
>> > with the deepest knowledge of the display engine. My best guess is that it
>> > is just some error while probing for an attached TV and actually isn't so
>> > bad after all.
>>
>> TV detection is always a bit flakey.  I suspect some register or gpio
>> related to TV out doesn't get restored properly on resume which
>> results in a false positive.  What asic is this?
>
> It's an RV250, which makes the asic r200, doesn't it?

Yes, it's an r2xx variant.

>
>> > You should definitely try Alex latest drm-fixes-3.8 branch
>> > (git://people.freedesktop.org/~agd5f/linux) since the possibility is quite
>> > high that we already have fixed that bug. If that doesn't helps then please
>> > open a bug report and leave me a note so that I can investigate further.
>>
>> I don't have a 3.8 fixes branch up just yet, but will soon.
>
> I see. I'll watch that repository, but I would appreciate it if you
> notify me if that branch pops up.

Will do.

Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ