Created attachment 76461 [details] dmesg [ 7.620987] Call Trace: [ 7.621375] [<ffffffffa013bee3>] sony_nc_add+0x836/0xd6a [sony_laptop] [ 7.621768] [<ffffffff81279035>] acpi_device_probe+0x49/0x117 [ 7.622160] [<ffffffff812d4a0a>] driver_probe_device+0xb0/0x1bf [ 7.622546] [<ffffffff812d4b6f>] __driver_attach+0x56/0x7a [ 7.622933] [<ffffffff812d4b19>] ? driver_probe_device+0x1bf/0x1bf [ 7.623322] [<ffffffff812d3335>] bus_for_each_dev+0x54/0x80 [ 7.623707] [<ffffffff812d45a8>] driver_attach+0x19/0x1b [ 7.624094] [<ffffffff812d419c>] bus_add_driver+0xb7/0x20a [ 7.624483] [<ffffffffa0142000>] ? 0xffffffffa0141fff [ 7.624869] [<ffffffff812d4fd5>] driver_register+0x8c/0xf9 [ 7.625253] [<ffffffffa0142000>] ? 0xffffffffa0141fff [ 7.625638] [<ffffffff81279783>] acpi_bus_register_driver+0x3e/0x40 [ 7.626028] [<ffffffffa0142057>] sony_laptop_init+0x57/0x86 [sony_laptop] [ 7.626417] [<ffffffff810001fa>] do_one_initcall+0x7a/0x12c [ 7.626807] [<ffffffff81075b56>] sys_init_module+0x1556/0x17ba [ 7.627193] [<ffffffff81071ad8>] ? sys_getegid16+0x45/0x45 [ 7.627581] [<ffffffff810c7499>] ? vm_mmap_pgoff+0x66/0x73 [ 7.627971] [<ffffffff81596062>] system_call_fastpath+0x16/0x1b
I have a similar problem since kernel 3.5. 3.4.x series works fine, so this is definitively a regression. I'm running Arch Linux x64 on a Sony Vaio S VPCS11C5E. In the attached dmesg I had blacklisted sony_laptop, booted up, logged into tty1 and ran "modprobe sony_laptop debug=1" which causes the crash.
Created attachment 78331 [details] dmesg output
[ 22.368218] [<ffffffffa03aae03>] ? sony_nc_buffer_call.constprop.14+0x43/0xa0 [sony_laptop] [ 22.368236] [<ffffffffa03ab759>] sony_nc_add+0x789/0x1180 [sony_laptop] [ 22.368251] [<ffffffff811e8aa2>] ? sysfs_do_create_link+0xe2/0x220 [ 22.368265] [<ffffffff812aacd5>] acpi_device_probe+0x50/0x11d
Could you add DSDT and the kernel config?
Created attachment 79411 [details] DSDT from /sys/firmware/acpi/tables/DSDT
Created attachment 79421 [details] kernel config
same problem with 3.6, any update on this?
Not really, if you can do some C programming could you try to print some debug statement about what is in the acpi buffer before calling memcpy at line 904 memcpy(buffer, object->buffer.pointer, len); Else I can try to instrument to code a bit and send you a patch to find out more information (but you may need be patient...) Thanks
Hi, could you try the patch attached here: https://bugzilla.kernel.org/show_bug.cgi?id=48671
please follow up on the other bug report that contains a bisection of the problem as well as a tentative patch. *** This bug has been marked as a duplicate of bug 48671 ***