Comment 8 for bug 209346

Revision history for this message
nicobrainless (nicoseb) wrote :

Well, the only solution I found was to keep booting on 2.6.28-9 instead of 2.6.28-11 and I did not get any trouble since then!
Yesterday I updated my kernel going straight to 2.6.29... works like a charm!