On Wed, Nov 28, 2012 at 8:21 AM, Zdenek Kabelac <zkabelac@xxxxxxxxxx> wrote: > > I've opened https://bugzilla.kernel.org/show_bug.cgi?id=51071 > and attached picture there which is all I have. > > I'll try to decode exact code line. Uhhuh. It's missing much of the relevant parts of the code line, in particular the actual oopsing instruction. But what is there decodes to 41 b8 10 00 00 00 mov $0x10,%r8d 48 c7 c1 88 52 64 81 mov $0xffffffff81645288,%rcx 31 c0 xor %eax,%eax 48 c7 c2 98 52 64 81 mov $0xffffffff81645298,%rdx bf 00 04 00 0. mov $0x0.00400,%edi .. oops in here .. 74 33 je 0x50 48 89 df mov %rbx,%rdi e8 4d c9 00 00 callq ? <offset 0xc972> 48 89 d9 mov %rbx,%rcx 48 c7 c2 0a .. .. .. mov $0x......0a,%rdx which isn't really very obvious. Do you have that kernel around (or at least the same compiler and configuration)? Doing a objdump --disassemble drivers/acpi/acpica/nsaccess.o might help pinpoint where that is.. > It's probably not a regression from 3.6 - since this problem was there for > much longer - but now it has just become much more visible. Ok. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
