Date: Wed, 25 Jul 2001 15:51:25 -1000 (HST) From: Vincent Poy <vince@oahu.WURLDLINK.NET> To: FreeBSD-gnats-submit@freebsd.org Subject: i386/29237: Message-ID: <200107260151.f6Q1pP401953@pele.WURLDLINK.NET>
next in thread | raw e-mail | index | archive | help
>Number: 29237
>Category: i386
>Synopsis:
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Jul 25 19:00:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Vincent Poy
>Release: FreeBSD 5.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD pele.WURLDLINK.NET 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Jul 25 14:22:50 HST 2001 vince@pele.WURLDLINK.NET:/usr/obj/usr/src/sys/PELE i386
Pentium III 850 with 384 megs of RAM
>Description:
/usr/bin/passwd in the latest -current world build with kernel
build seems to do the following:
# passwd joeuser
Changing local password for joeuser.
New password:
Retype new password:
passwd: updating the database...
passwd: done
#
and 5 seconds later, the machine would just freeze solid. With
yesterday's buildworld, it would do the same thing except
it would panic the kernel and go into the db> prompt. So
the only way is to hard reboot which will goto single user mode
where fsck would have to be done and then somehow the passwd
database is corrupted which requires copying master.passwd.bak
from /var/backups to /etc/master.passwd and then run and exit
vipw with :wq to rebuild the passwd database. Otherwise, all
users besides root will be able to logon and /etc/passwd and
/etc/master.passwd will be a bunch of garbled characters.
vipw works fine when manually entering the encrypted passwd as
a cut and paste from another system. It isn't a hardware issue
since I have tried everything from make -j 4 buildworld to
running dnetc to even running cpuburn from the /usr/ports/misc
collection which had no effect. Only when running passwd would
it hang the machine solid 5 seconds later each time and corrupt
the password database. The 6/18/2001 current binary snapshot
from current.freebsd.org worked without any problems.
>How-To-Repeat:
# passwd joeuser
Changing local password for joeuser.
New password:
Retype new password:
passwd: updating the database...
passwd: done
#
>Fix:
No solution.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107260151.f6Q1pP401953>