Segmentation fault with /bin/su on linux-image-2.6.26-2-orion5x 2.6.26-21lenny3
I just upgraded my Debian kernel on a TS-209 to the following
(2.6.26-21lenny3):
Linux 2.6.26-2-orion5x #1 Fri Feb 12 01:56:06 UTC 2010 armv5tel GNU/Linux
I now am getting a segfault when I attempt to sudo or su to a user defined in
my LDAP directory. Local users are fine. An "strace" of "su - $user" shows
the process contacting the LDAP server with the PAM credentials, and the data
is all accessible in the LDAP directory. I can log into another QNAP TS-209
as an LDAP-based user; that machine is still running the old kernel
(2.6.26-21):
Linux 2.6.26-2-orion5x #1 Wed Jan 13 03:20:19 UTC 2010 armv5tel GNU/Linux
and su - $user still works fine on that machine. A diff of the config for each
kernel seems to show no config changes. The changelog did mention a number of
bug fixes.
Apache/PHPLDAPAdmin is working fine; it authenticates directly to LDAP. SSH
will allow a login with an LDAP-based account using passwordAuthentication.
SMB mounts and accesses are successful, but unusually slow.
dpkg.log shows the following packages changed on 23-feb:
2010-02-23 09:39:12 status installed linux-image-2.6.26-2-orion5x
2.6.26-21lenny3
2010-02-23 09:39:12 status installed php5-common 5.2.6.dfsg.1-1+lenny6
2010-02-23 09:39:34 status installed libapache2-mod-php5 5.2.6.dfsg.1-1+lenny6
2010-02-23 09:39:35 status installed php5-ldap 5.2.6.dfsg.1-1+lenny6
2010-02-23 09:39:35 status installed mysql-common 5.0.51a-24+lenny3
2010-02-23 09:39:36 status installed libmysqlclient15off 5.0.51a-24+lenny3
2010-02-23 09:39:36 status installed linux-libc-dev 2.6.26-21lenny3
I did a dpkg --purge of linux-libc-dev just in case it was the culprit, but
that didn't seem to help. I do notice php5-ldap was updated, but that doesn't
seem to install anything that should interfere with PAM or NSS. That leaves
me with the impression it's the new kernel that's got a problem. ?
I am reasonably facile with Linux, so let me know what other information would
help to diagnose the problem. I will likely go back to the 2.6.26-21 kernel
in a few days if I can't fix this.
Thanks;
Luigi Bai
Reply to: