Re: 10.0-BETA1 i386 on VirtualBox

В сообщении от Thursday 31 of October 2013 16:02:20 Maciej написал:
> On 31.10.2013 01:08, Boris Bobrov wrote:
> > В сообщении от Thursday 31 of October 2013 02:01:41 Boris написал:
> >> В сообщении от Tuesday 29 of October 2013 15:09:57 Gleb написал:
> >>>   Hello,
> >>>   
> >>>   [adding Boris to Cc, who reported same issue in private email]
> >>> 
> >>> On Thu, Oct 24, 2013 at 05:16:15PM +0200, Maciej Milewski wrote:
> >>> M> I've encountered problems with installing FreeBSD-10.0-BETA1
> >>> i386 under M> VirtualBox.
> >>> M> The problem is with setting/changing root password during
> >>> install M> process. After entering password twice there is:
> >>> M>
> >>> M> passwd: pam_chauthtok(): error in service module
> >>> M>
> >>> M> Then there shows pwd_mkdb.core in current directory.
> >>> M> The same VirtualBox machine has no problems with installing
> >>> M> FreeBSD-9.2-RELEASE
> >>> M>
> >>> M> Has anyone any clues?
> >>> 
> >>> I failed to reproduce this with FreeBSD-10.0-BETA2 i386 image :(
> >>> It installed and booted successfully.
> >>> 
> >>> Here is my host environment:
> >>> 
> >>> glebius_at_think:~:|>pkg info -x virtual
> >>> virtualbox-ose-4.2.18_1
> >>> virtualbox-ose-kmod-4.2.18
> >>> glebius_at_think:~:|>uname -a
> >>> FreeBSD think.nginx.com 11.0-CURRENT FreeBSD 11.0-CURRENT #13
> >>> r257045: Thu Oct 24 15:16:04 MSK 2013
> >>> glebius_at_think.nginx.com:/usr/obj/usr/src/head/sys/THINKPAD_X1 
> >>> amd64
> >>> 
> >>> When trying to reproduce I used VirtualBox GUI and choosed defaults
> >>> in every dialog window.
> >>> 
> >>> Boris and Maciej, if you use non-default configuration, can you
> >>> please provide more details?
> >> 
> >> Hi.
> >> 
> >> Can any of you suggest a way to reproduce the bug on a livecd
> >> reliably?
> > 
> > I'll rephrase that:
> > 
> > Can anybody suggest a way to reproduce the bug on a livecd reliably,
> > if you ever met the bug before?
> 
> Boris what error do you have on the livecd?
> tail /var/log/messages ? I see some oddity in view /var/log/messages:
> ^_at_ at the end
> The same file copied through disk -> network shows no ^_at_ at the end.
> As /var and /tmp ar on md0/md1 I suspect some kind of memory
> corruption.

When I do "less /var/log/messages", "less" fails with segmentation fault. 
It happens on BETA1 and BETA2, but not on older 10.0 releases.

-- 
С наилучшими пожеланиями, 
Boris