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-next>] [day] [month] [year] [list]
Date:	Sat, 17 Apr 2010 22:04:56 -0400 (EDT)
From:	Parag Warudkar <parag.lkml@...il.com>
To:	jglisse@...hat.com
cc:	linux-kernel@...r.kernel.org, airlied@...hat.com
Subject: Atombios Execution timeout

Hi Jerome,

On my laptop with a HD3650 GPU, during resume from RAM I get the 
below errors -

[   80.484213] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more 
than 1sec aborting
[   80.484218] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing FA30 (len 493, WS 0, PS 4) @ 0xFA71
[   81.497547] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more 
than 1sec aborting
[   81.497552] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
executing FA30 (len 493, WS 0, PS 4) @ 0xFA71
[   81.548053] PM: resume of devices complete after 2129.312 msecs
[   81.746649] PM: Finishing wakeup.
[   81.746651] Restarting tasks ... done.

Since this happens only during resume may be the current 1 second time is 
not sufficient for the resume case? I bumped it to 2 sec and it stopped 
complaining. 

May be we should increase the timeout for only the resume case?

Thanks,

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