On Die, 2013-04-23 at 10:08 -0700, Andy Lutomirski wrote: > On Mon, Apr 22, 2013 at 10:55 PM, Michel Dänzer <michel@xxxxxxxxxxx> wrote: > > On Mon, 2013-04-22 at 16:19 -0700, Andy Lutomirski wrote: > > > >> I'm not convinced there's an actual hang. 40 seconds is a long time, > >> and I've only ever seen this when clicking something, and when this > >> happens, the screen goes blank immediately (not after a 40 second > >> delay). > > > > Hmm, now that you mention this, I notice in your original report it > > claims that the CP stalled for 'more than 5102593msec', which is clearly > > bogus. Looks like something's wrong with the lockup detection. > > Did this start after a kernel update or something like that? > > It's recent. It may have been when F18 switched from 3.7 to 3.8. Can you reproduce it with an upstream kernel? Can you bisect? I realize it'll probably take a long time, but unless someone has an idea which change might have introduced the problem... > I think there are bugs in the lockup detection and in the lockup > recovery. Firefox, in particular, is *really* slow afterwards. Are > interrupts possibly getting dropped or misconfigured during the reset? Let's not get ahead of ourselves and focus on the lockup detection issue for now. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
