Robb,
Thanks for testing. I actually included the patch for bug #276990 in the modules I posted in comment #52, which is why they fix both bugs.
Robb Topolski wrote: > Tom, > > I got the kern.log entry mentioned at > https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990/comments/92 > which is the patched (comment 85) behavior of that bug. The news is that > I didn't use that patch, I used the patch from comment 52 in this bug. > > The patch at > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52 > has eased both problems, the scheduling report churning into kern.log > and turns the wrong command queue hang into a log event. >
Robb,
Thanks for testing. I actually included the patch for bug #276990 in
the modules I posted in comment #52, which is why they fix both bugs.
Robb Topolski wrote: /bugs.launchpad .net/ubuntu/ intrepid/ +source/ linux/+ bug/276990/ comments/ 92 /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/286285/ comments/ 52
> Tom,
>
> I got the kern.log entry mentioned at
> https:/
> which is the patched (comment 85) behavior of that bug. The news is that
> I didn't use that patch, I used the patch from comment 52 in this bug.
>
> The patch at
> https:/
> has eased both problems, the scheduling report churning into kern.log
> and turns the wrong command queue hang into a log event.
>