Comment 6 for bug 1940154

Thanks Daniel. I've had on-and-off problems with both the nouveau and NVidia closed-source drivers pretty much since I got this thing and at some point vowed that my next machine would use an AMD card, since I've heard the open-source AMD driver is good.

I'll take a look at those links and see if I can do some debugging, since there might be other people out there who are affected by this too, and it'd be a shame to have to stop upgrading their Linux systems as a result. Unless a machine breaks down completely, I don't see why it shouldn't run Linux for more than 11 years.

I've noticed at least two flavours of error stacktrace that happen, so there may be two separate bugs. The first (as in the opening report) starts with "refcount_t: underflow; use-after-free" in lib/refcount.c:28 refcount_warn_saturate+0xae/0xf0, and the second starts with "Trying to vfree() bad address" in mm/vmalloc.c:2263 __vunmap+0x263/0x280.

The rest of the stack trace is somewhat different, although they both pass through "ttm_bo_put". They both look to be memory management errors (use-after-free and possibly a double-free?).