Comment 3 for bug 1042903
Revision history for this message
| Leann Ogasawara (leannogasawara) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I wanted to relay the following here in the bug report...I was notified of a commit in the latest upstream v3.5.3 release. I thought it would be interesting to test the latest Ubuntu 3.5.0-13.13 which was rebased to this latest v3.5.3 upstream stable release. Narinder and I didn't originally test this latest Ubuntu kernel as I only uploaded it yesterday. Anyways, I see the following commit included there:
commit be67f30591ffe86
Author: Dave Airlie <email address hidden>
Date: Thu Aug 9 15:00:15 2012 +1000
drm/mgag200: fix G200ER pll picking algorithm
commit 9830605d4c070b1
The original code was misported from the X driver,
a) an int went to unsigned int, breaking the downward counting testm code
b) the port did the vco/computed clock bits completely wrong.
This fixes an infinite loop on modprobe on some Dell servers with the G200ER
chipset variant.
Found in internal testing.
Signed-off-by: Dave Airlie <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
So the issue which was being seen might be the fix with the above and thus allow us to keep the mgag200 driver enabled. I figured it wouldn't hurt to test anyways. Thanks.