Package: linux-image-2.6.21-2-vserver-sparc64
Version: 2.6.21-5
Severity: normal


Booting 2.6.21-2-vserver-sparc64 will not start vservers with dlimits in
place, complaining "vdu: readdir(): Bad address" (meaning a return of
EFAULT).  Further, vserver-stat produces its header but no servers,
despite that servers without dlimits were successfully started by the
init scripts.

Some stracing makes it look like the root cause is a getdents64() call
with its data pointer only aligned mod 4, not mod 8.  However, booting
2.6.18-4-vserver-sparc64 works but gives a host of dmesg output like

Kernel unaligned access at TPC[4b72d0] filldir64+0x54/0x134
Kernel unaligned access at TPC[4b72ec] filldir64+0x70/0x134
Kernel unaligned access at TPC[4b72b8] filldir64+0x3c/0x134

when starting vservers.  Despite these warnings it _works_, which is
key.  This bug may be inappropriately filed -- I have no idea if the
important package is the kernel, glibc, or util-vserver, though from a
bit of code groveling I'd bet against the latter.

Requesting the attention of some guru.  Thanks much.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: sparc (sparc64)

Kernel: Linux 2.6.18-4-vserver-sparc64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.21-2-vserver-sparc64 depends on:
ii  coreutils                    5.97-5.4    The GNU core utilities
ii  debconf [debconf-2.0]        1.5.14      Debian configuration management sy
ii  initramfs-tools [linux-initr 0.90a       tools for generating an initramfs
ii  module-init-tools            3.3-pre11-4 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.21-2-vserver-sparc64 recommends:
ii  libc6-sparc64                 2.6.1-2    GNU C Library: 64bit Shared librar
ii  util-vserver                  0.30.213-1 user-space tools for Linux-VServer

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to