Comment 12 for bug 642555

Indeed, it doesn't appear that anyone has been able to provide the requested logs that would enable us to reproduce this issue and debug it. Since this has not been broadly reported in 10.04 after the previous fixes were applied, this is somehow specific to the configuration of the machines where it's been seen. Nick, you said you *tried* setting --verbose on the kernel command line, but didn't indicate if that enabled you to reproduce the issue with more verbose logs - from your comment I got the impression that you were looking to this as a workaround for the issue, when as Colin says, it's meant to get us more logging information we can use to debug this.