Comment 101 for bug 661294

Wow. Just wow. This bug has been open for nearly 2 years, and 100 comments later the bug report is closed because one guy recently claimed to experience the same problem with an Intel card instead of a Realtek - who should have just opened a separate bug report. This bug has *always* been about specific Realtek chipsets, so opening up other bug reports would be pointless.

I myself have previously experienced this same issue on 3 different computers (all different motherboards) all with the same Realtek hardware. I did not mention the other two because one is now critical work machine I cannot readily test since they are now in production with the driver from the Realtek website, and the other I don't have any more. It's unbelievable that Canonical Q/A have been unable to reproduce. You even have some specific motherboard models with the problem mentioned.

> Someone needs to make sure that it does not break when the rest of the kernel changes
It was already broken. It doesn't get much worse than a complete system lock-up.

As previously mentioned, I don't even run Ubuntu any more. I don't get paid from Canonical. Here I was going to spend my time over the weekend to try and help you guys out, but now I don't think I'll bother.