Hello all: I've found out some upstream bugs that lead me to promising results so far, although I'll need some more testing to make sure this is the correct fix.
Basically, I've followed this bug: https://bugs.freedesktop.org/show_bug.cgi?id=40241 The outcome patch[0] was only recently applied to linux kernel on 3.3.1 and I think also on 3.2.14, neither of those are in Debian AFAIK. In my case, I proceeded without uswsusp, I kept plymouth though. Yes, I thought this was a kernel bug from the begginning, just that I had no time to show it off. This scenario hasn't been the same as the one that originally brought me here, since I've been trying to go for a simple testcase. Anyway, I got the hang then with both custom build 3.2.13 and also with stock 3.3 (from experimental) by then I was using uswsusp. I always use plymouth. I first managed to reproduce a crash with a custom build 3.2.13. Then I applied the patch[0] and so far I've been unable to reproduce the hang. I'm going now into building a "stock" experimental kernel, with the patch applied, but I guess the same results could come with a 3.3.1. HTH, [0] http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm- fixes&id=3fa016a0b5c5237e9c387fc3249592b2cb5391c6 -- Raúl Sánchez Siles ----->Proud Debian user<----- Linux registered user #416098
signature.asc
Description: This is a digitally signed message part.
