On Tue, Jun 12, 2012 at 9:25 AM, Alex Gershgorin <alexg at meprolight.com> wrote: > I applied this patch, but unfortunately I got the same result Could you please run git bisect to figure out the commit that is causing the oops?