Bug#535571: kernel unaligned access copy_to_user_state with IPSec

2012-01-03 Thread ja nein
Hi Jonathan, ok, it took a while, but finally I've tested wheezy with latest kernel (linux-image-3.1.0-1-sparc64-smp) and the error's gone. It seems that somewhere to 3.x kernel the error was fixed. Regards, Sebastian On 27.09.2011 22:26, Jonathan Nieder wrote: ja nein wrote:

Bug#535571: kernel unaligned access copy_to_user_state with IPSec

2011-09-27 Thread ja nein
Just to make sure, is the kernel you are reading symbols from the same build as the one that produced the message in dmesg? Yes, that's true. I've used the sources of debian via "apt-get source linux-image-2.6.32-5-sparc64-smp" and followed your instructions from there. I just had to activate th

Bug#535571: kernel unaligned access copy_to_user_state with IPSec

2011-09-27 Thread ja nein
The kernel modules gdb can use will be in .ko files scattered under the linux/ source dir which you can find with commands like $ find . -name .git -prune -o -name \*.ko -print Jonathan sorry, last gdb entry was incomplete: (gdb) list *(copy_to_user_state+0x9c0) 0x132c is in xfrm_add_sa_expire

Bug#535571: kernel unaligned access copy_to_user_state with IPSec

2011-09-27 Thread ja nein
The kernel modules gdb can use will be in .ko files scattered under the linux/ source dir which you can find with commands like $ find . -name .git -prune -o -name \*.ko -print Jonathan I finally managed to compile some debug symbols into the kernel. Here we go: dmesg: [3179998.695837] Kernel

Bug#535571: AW: AW: kernel unaligned access copy_to_user_state with IPSec

2010-03-06 Thread ja nein
maybe this email/thread is related to the problem...: http://markmail.org/message/2d3u2hkg26pilehm Regards, Sebastian Von: ja nein An: Moritz Muehlenhoff CC: 535...@bugs.debian.org Gesendet: Samstag, den 6. März 2010, 12:42:03 Uhr Betreff: AW: kernel

Bug#535571: AW: kernel unaligned access copy_to_user_state with IPSec

2010-03-06 Thread ja nein
Hi Moritz, I just tested with latest Squeeze (and latest kernel). Same problem, another state though: [1046073.600266] Kernel unaligned access at TPC[104ea7fc] copy_to_user_state+0x54/0x9c [xfrm_user] [1046073.715755] Kernel unaligned access at TPC[104ea7fc] copy_to_user_state+0x54/0x9c [xfrm_