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: <CAPVoSvQYaCC9WcYBeZJtQ++DQhq4QCS8D=nChNjhVNKUHefYdg@mail.gmail.com>
Date:	Mon, 23 Jan 2012 19:01:41 +0100
From:	Torsten Kaiser <just.for.lkml@...glemail.com>
To:	Jerome Glisse <j.glisse@...il.com>
Cc:	linux-kernel@...r.kernel.org,
	Alex Deucher <alexander.deucher@....com>,
	Dave Airlie <airlied@...hat.com>,
	dri-devel@...ts.freedesktop.org
Subject: Re: [3.3-rc1]radeon 0000:07:00.0: GPU lockup CP stall for more than 10000msec

On Mon, Jan 23, 2012 at 5:57 PM, Jerome Glisse <j.glisse@...il.com> wrote:
> On Sat, Jan 21, 2012 at 08:03:37PM +0100, Torsten Kaiser wrote:
>> After updating to kernel 3.3-rc1 I have experienced a lockup of my GPU.
>> I left my KDE desktop running until the screensaver turned off the
>> monitors. But on key presses it would not turn back on. Ctrl+Alt+F1 to
>> switch to another virtual console also did not work.
>> Alt+SysRq magic still worked, so I was able to force the syslog to
>> disk and restart the system.
>>
>
> Can you test if attached patch help your case ?

Patch is installed, but I can't reproduce the hang on demand.
It did happen a second time yesterday while letting the screensaver
kick in, but only at around the third or fourth try. Just using "xset
dpms force standby/suspend/off" did not trigger it.

> Of course it would be best if we did not lockup in the first place.

Not sure if this is important: I also upgraded to mesa 8.0-rc1 before
the first hang, but after switching back to 3.2 but still using mesa
8.0 I did not have any problems.
Except the KDE desktop effects there should not have been any OpenGL
programs running.
The screen saver itself is just turning the screens off via the KDE
power profile.

I will report again, when I succeeded in triggering the GPU lockup again...

Torsten
--
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