Your message dated Tue, 3 Jan 2012 12:39:38 -0600
with message-id <[email protected]>
and subject line Re: kernel unaligned access copy_to_user_state with IPSec
has caused the Debian Bug report #535571,
regarding kernel unaligned access copy_to_user_state with IPSec
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
535571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535571
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-2.6.26-2-sparc64-smp
Version: 2.6.26-17
Severity: important
I'm continiously getting these kernel messages while running several IPSec
tunnels:
[3881706.284682] Kernel unaligned access at TPC[10276320]
copy_to_user_state+0x50/0x9c [xfrm_user]
[3881706.403493] Kernel unaligned access at TPC[10276330]
copy_to_user_state+0x60/0x9c [xfrm_user]
It doesn't seem to affect any functionality, as tunnels are up and running.
-- System Information:
Debian Release: 5.0.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: sparc (sparc64)
Kernel: Linux 2.6.26-2-sparc64-smp (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-2-sparc64-smp depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
linux-image-2.6.26-2-sparc64-smp recommends no packages.
Versions of packages linux-image-2.6.26-2-sparc64-smp suggests:
pn fdutils <none> (no description available)
pn linux-doc-2.6.26 <none> (no description available)
ii silo 1.4.13a+git20070930-3 Sparc Improved LOader
-- debconf information:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.26-2-sparc64-smp/preinst/overwriting-modules-2.6.26-2-sparc64-smp:
true
linux-image-2.6.26-2-sparc64-smp/postinst/bootloader-error-2.6.26-2-sparc64-smp:
linux-image-2.6.26-2-sparc64-smp/postinst/kimage-is-a-directory:
linux-image-2.6.26-2-sparc64-smp/preinst/initrd-2.6.26-2-sparc64-smp:
linux-image-2.6.26-2-sparc64-smp/postinst/create-kimage-link-2.6.26-2-sparc64-smp:
true
linux-image-2.6.26-2-sparc64-smp/postinst/old-initrd-link-2.6.26-2-sparc64-smp:
true
linux-image-2.6.26-2-sparc64-smp/preinst/abort-overwrite-2.6.26-2-sparc64-smp:
linux-image-2.6.26-2-sparc64-smp/preinst/failed-to-move-modules-2.6.26-2-sparc64-smp:
*
linux-image-2.6.26-2-sparc64-smp/preinst/already-running-this-2.6.26-2-sparc64-smp:
linux-image-2.6.26-2-sparc64-smp/preinst/lilo-initrd-2.6.26-2-sparc64-smp:
true
linux-image-2.6.26-2-sparc64-smp/postinst/old-system-map-link-2.6.26-2-sparc64-smp:
true
linux-image-2.6.26-2-sparc64-smp/postinst/depmod-error-initrd-2.6.26-2-sparc64-smp:
false
linux-image-2.6.26-2-sparc64-smp/preinst/abort-install-2.6.26-2-sparc64-smp:
linux-image-2.6.26-2-sparc64-smp/postinst/bootloader-test-error-2.6.26-2-sparc64-smp:
linux-image-2.6.26-2-sparc64-smp/preinst/elilo-initrd-2.6.26-2-sparc64-smp:
true
linux-image-2.6.26-2-sparc64-smp/preinst/bootloader-initrd-2.6.26-2-sparc64-smp:
true
linux-image-2.6.26-2-sparc64-smp/prerm/removing-running-kernel-2.6.26-2-sparc64-smp:
true
linux-image-2.6.26-2-sparc64-smp/preinst/lilo-has-ramdisk:
linux-image-2.6.26-2-sparc64-smp/postinst/depmod-error-2.6.26-2-sparc64-smp:
false
linux-image-2.6.26-2-sparc64-smp/prerm/would-invalidate-boot-loader-2.6.26-2-sparc64-smp:
true
linux-image-2.6.26-2-sparc64-smp/postinst/old-dir-initrd-link-2.6.26-2-sparc64-smp:
true
--- End Message ---
--- Begin Message ---
Version: 3.1.6-1
ja nein wrote:
> 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.
Thanks; marking accordingly.
Would you be able to try some kernels from in between from
http://snapshot.debian.org/ to narrow down which version introduced
the fix? E.g., a test with a v2.6.33 kernel would be interesting
already. Once we find the relevant patch, we can try applying it to
squeeze.
Happy new year,
Jonathan
--- End Message ---
