Comment 27 for bug 607399

Bitten. Wasted my weekend on it.

I've been running various kernels & nvidia drivers for a long time, even switching hardware along the way, without any issue whatsoever and out of the blue i get that oops. The funniest part is i cannot get rid of it: i've tried every available kernels (from 2.6.32 up to 2.6.37) and drivers (from 195.* up to 270.*), then downgraded every remotely related packages (xorg*, libs and more), yet it still oops. It's infuriating.

As i knew my hardware & system were just fine, out of desperation, i've given a fresh ubuntu 10.10 live cd a try... booted, jockeyed and no fuss, no muss, got a working 260.19.06. Revived by such wondrous sight, i've exported its magic list of package/version and applied that (well, part of it) to my dysfunctional system. No luck, still oopsing. Noticed that now almost similar systems produced different binaries. So i went medieval and simply grafted the live-cd's module binary. Success.

Conclusion: apparently some maverick update screws the build system for that module, even if the exact reason/culprit still escapes me right now (and i have downgraded just about everything at this point...).

TL; DR: for a quick fix, use a fresh live cd to produce a sane module.