For what it's worth, the issue has cleared itself up (again) for me, and the only relevant change I can think of is using the 2.6.35-23 kernel (a relatively recent update over 2.6.35-22).
For what it's worth, the issue has cleared itself up (again) for me, and the only relevant change I can think of is using the 2.6.35-23 kernel (a relatively recent update over 2.6.35-22).