[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=Ys4mb4pc28cH4NMdtMgb2KewJbkXEGJmEP4J0@mail.gmail.com>
Date: Wed, 23 Feb 2011 08:32:04 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Anca Emanuel <anca.emanuel@...il.com>,
Dave Airlie <airlied@...hat.com>, linux-fbdev@...r.kernel.org,
Ben Skeggs <bskeggs@...hat.com>,
dri-devel@...ts.freedesktop.org
Cc: Borislav Petkov <bp@...64.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.38-rc6
On Tue, Feb 22, 2011 at 9:42 PM, Anca Emanuel <anca.emanuel@...il.com> wrote:
> General protection fault:
> http://i.imgur.com/TBJ6y.jpg
>
> dmesg: http://pastebin.com/qD8pR8QH
> config: http://pastebin.com/XEurtHWi
That's drivers/video/fbmem.c: fb_release(), and the "Code:"
disassembly shows that it is
1b: e8 f7 c0 29 00 callq xyz
20: 48 8b 93 b8 03 00 00 mov 0x3b8(%rbx),%rdx
27:* 48 8b 42 10 mov 0x10(%rdx),%rax <-- trapping instruction
which corresponds to
mutex_lock(&info->lock);
if (info->fbops->fb_release)
info->fbops->fb_release(info,1);
so it looks like 'info->fbops' is invalid. It's in %rdx, and is
0x00d000ae00b500c2, which is definitely not a valid pointer. Looks
like some bad corruption (looks like a sequence of 16-bit numbers, but
it could be anything).
Looks like nouveafb took over from vesafb. Did you do anything special
to trigger this?
Also, you do seem to have some extra patches (yama at the least). Anything else?
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists