Comment 2 for bug 715865

I'm confused. There are a lot of issues describing the same problem, but when I commented on one of them, I was told that I had to open a new bug, because kernel issues are specific to every hardware combination and the policy is that every single person experimenting the problem should open a new bug - that's what i was told. So I opened a new bug and now it is marked as duplicate...