I updated yesterday this faulty machine with latest linux-image-3.2.0-1-amd64 (version 3.2.2-1) and I can confirm that this bug is still present.
Is there a boot option I can try to get rid of this messages and what is causing them? TIA. Antonio Corbi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
