Upgraded today the kernel to 3.2.0-4-686-pae, and the bug is still
present. 3.2.0-2-686-pae works. If I can provide any additional
information on this, pleas let me know.

Winfried


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]

Reply via email to