Comment 38 for bug 965863
Revision history for this message
| Matthew Stapleton (matthew4196) wrote | #38 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
It looks like the timeout only occurs with CONFIG_HZ set to 250 which is what most/all? of the Ubuntu kernels use, although the timeout also occurs with mainline kernel as well without all of the Ubuntu patches applied, and it is 'fixed' by changing CONFIG_HZ to 100 or 1000 (Haven't tried 300 yet).