[PATCH 0/2] console_lock debug improvements

2012-08-22 Thread Alan Cox
On Wed, 22 Aug 2012 00:34:30 +0200 Daniel Vetter wrote: > Hi all, > > After Dave Airlie blew through a few days to track down a deadlock at boot-up > when handing over from the firmware fb to the kms/drm framebuffer driver (1), > I've > figured that lockdep /should/ have caught this. > > And i

Re: [PATCH 0/2] console_lock debug improvements

2012-08-22 Thread Alan Cox
On Wed, 22 Aug 2012 00:34:30 +0200 Daniel Vetter wrote: > Hi all, > > After Dave Airlie blew through a few days to track down a deadlock at boot-up > when handing over from the firmware fb to the kms/drm framebuffer driver (1), > I've > figured that lockdep /should/ have caught this. > > And i

[PATCH 0/2] console_lock debug improvements

2012-08-22 Thread Daniel Vetter
Hi all, After Dave Airlie blew through a few days to track down a deadlock at boot-up when handing over from the firmware fb to the kms/drm framebuffer driver (1), I've figured that lockdep /should/ have caught this. And indeed, by adding proper annotations to the console_lock it complains about

[PATCH 0/2] console_lock debug improvements

2012-08-21 Thread Daniel Vetter
Hi all, After Dave Airlie blew through a few days to track down a deadlock at boot-up when handing over from the firmware fb to the kms/drm framebuffer driver (1), I've figured that lockdep /should/ have caught this. And indeed, by adding proper annotations to the console_lock it complains about