When I try to login to the system as non-root user the computer deadly hangs-up
and reboot is the only solution. Login as root behaves quite normally. Also if I
login as root, term the devfsd (killall -TERM devfsd), start it again (devfsd
/dev) and then try to login as non-root user it works perfectly.
Steps to Reproduce:
1. boot the system
2. try to login as non-root user
3. ...computer freezes
pc is completely dead
login me to the system :-)
running the latest versions of:
metalog (also tried sysklogd)
Portage 2.0.49-r7 (default-x86-1.4, gcc-3.3.1-r3, glibc-2.3.2-r5, 2.4.22-ac4)
System uname: 2.4.22-ac4 i586
CFLAGS="-O3 -mcpu=pentium-mmx -funroll-loops -pipe"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
CXXFLAGS="-O2 -mcpu=i686 -pipe"
FEATURES="sandbox ccache autoaddcvs"
USE="x86 oss apm arts avi crypt cups encode foomaticdb gif jpeg kde gnome libg++
libwww mad mikmod mmx motif mpeg ncurses nls pdflib png qt quicktime sdl spell
svga truetype xml2 xmms xv zlib gdbm berkdb slang readline java X gpm tcpd pam
ssl perl python esd imlib oggvorbis gtk opengl mozilla"
... Can you explicitly point this to a kernel problem, i.e. if you try a
different kernel [such as vanilla/gentoo-sources] do you get this?
choice of kernel doesn's matter. i've already tried vanilla, original gentoo,
ac and ck.
I must say that here is happening the same on PPC. Unfortunately killing/restarting
devfsd don-t work for me. Also tried multiple kerneles without success.
Not a kernel bug: this seems to happen on a variety of kernels and even PPC,
reassigning to bug-wranglers...
I also have the bug 30478 about keyboard mapping
Just in case is related...
(Those are my only two problems with gentoo installation)
Do you use utf8 support in console ?
sorry, but what does it mean exactly to use utf8 support in cpnsole?
This bug has been inactive for 30 days, or more.
Can this bug still be reproduced? Please reopen if it's still relevant.
I have a workaround, comment all references to console pam module in all the pam.d config files.
I suppose it's a problem with pam console module verification.
I've done this and all works OK.
Closing this bug, as there is a workaround.