Comment 50 for bug 294667

This problem does _not_ happen for kernel 2.6.27-9 from intrepid-updates. It still does for 2.6.27-10 from intrepid-proposed. This suggests that the updates repository is better looked into than the proposed one, which is somewhat encouraging.

Also, my dirty trick 2b of comment 23 can be used again (with 2.6.27-9 and 2.6.27-10 instead of 2.6.27-7 and 2.6.27-8, respectively), should you want to use 2.6.27-10 for any reason. Hopefully this problem will go away with the next proposed kernel...