Comment 2 for bug 263959

Hi Quinn,

We'll actually continue to use your original bug report to track this bug. I'm sorry if it wasn't clear in my other message but you only need to open a new bug report for bugs which appear in 2.6.27 and not in 2.6.26 or previous kernels. Ie 2.6.27 regressions. If a report already exist for the bug in question, please continue to use that existing bug report and post 2.6.27 comment updates there. Sorry again for the confusion. I'll go ahead and mark this as a duplicate of your original bug report. Thanks.