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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C04AF52.1070009@crca.org.au>
Date:	Tue, 01 Jun 2010 16:57:22 +1000
From:	Nigel Cunningham <ncunningham@...a.org.au>
To:	Dave Airlie <airlied@...il.com>
CC:	LKML <linux-kernel@...r.kernel.org>,
	dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: 2.6.35 Radeon KMS power management regression?

Hi again.

On 01/06/10 16:33, Dave Airlie wrote:
> On Tue, Jun 1, 2010 at 4:23 PM, Nigel Cunningham
> <ncunningham@...a.org.au>  wrote:
>> Hi all.
>>
>> Just wondering if anyone else has tried to hibernate while using Radeon KMS
>> and a tree with Dave's post 2.6.34 patches? My 32 bit P4 based system (with
>> an RV250 card) is hanging at the atomic copy, with the following backtrace
>>
>> hibernation_snapshot
>> dpm_suspend_start
>> async_synchronize_full
>> async_synchronize_cookie
>> async_synchronize_cookie_domain

Just tried with the agp_suspend invocation commented out - no 
difference. But it did lead to me realising I'd forgotten to mention the 
other part of the issue: the above backtrace is from the thread doing 
the hibernating. In addition, there's an async work thread with the 
following backtrace. (I love having kdb in vanilla!)

async_thread
async_suspend
__device_suspend
device_for_each_child
pm_op
pci_pm_freeze
pci_legacy_suspend
radeon_pci_suspend
radeon_suspend_kms
radeon_pm_suspend
del_timer_sync
try_to_del_timer_sync

>> I've been trying to bisect, but this computer is being painfully slow, so I
>> haven't been making much progress. 2.6.34 with the same config is fine, and
>> my bisection progress so far seems to be pointing at the merge I mentioned
>> above.
>
> The only thing I can think off might be the output polling task, or
> the fix from Jerome for AGP suspend/resume
> 10b06122afcc78468bd1d009633cb71e528acdc5 is AGP one to test
>
> disabling output polling is a messier revert, might be easier to just edit
> drivers/gpu/drm/drm_crtc_helper.c:drm_kms_helper_poll_init and remove
> the delayed_slow_work_enqueue call, also forcing repoll to false
> inside output_poll_execute which should in theory stop the polling
> from starting or being kicked off later.

Will try this now. Given the above, I guess it sounds more likely?

> I'll try and recreate if I get a chance, cc'ing dri-devel also for Alex/Jerome.

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