Re: 10.0-BETA1 i386 on VirtualBox
On Tue, Nov 05, 2013 at 12:15:35PM +0400, Boris Bobrov wrote: B В сообщении от Tuesday 05 of November 2013 11:06:09 Gleb написал: B On Tue, Nov 05, 2013 at 09:02:22AM +0200, Konstantin Belousov wrote: B K First, all reported instances have ata attachment for the ada0, B except K of milu (possibly). So this means that kernel does transient B remapping, K and very different code path is executed comparing with B what I thought K initially. The path is simpler than the pure B unmapped i/o. B K B K Second, I use QEMU with the ata0 attachment for the disks regularly, B and K I do not have an issue. I also did not see a report from the B real h/w. K B K Third point is that all reports are i386. Is there anybody with B amd64, K vbox, ata and the same corruption hiddent by disabling B unmapped i/o ? K B K In what way the non-working images were installed ? Is it possible B to K produce the problematic installs by doing it one way, and B non-problematic K by another ? B B The only known way to get FreeBSD working is to turn off unmapped io B in loader. Any tweaking of hardware in VB or changes in the install B process do not affect. B B Disabling VT-x in VB helps too. Doesn't help with my issue. This could mean that my issue and the one that Boris and Maciej encountered are different. -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On Tue, Nov 05, 2013 at 01:09:04PM +0400, Gleb Smirnoff wrote: T B The only known way to get FreeBSD working is to turn off unmapped io T B in loader. Any tweaking of hardware in VB or changes in the install T B process do not affect. T B T B Disabling VT-x in VB helps too. T T Doesn't help with my issue. This could mean that my issue and the one T that Boris and Maciej encountered are different. P.S. Just to confirm that turning off unmapped io in loader fixes my issue with random buildworld failures. -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05.11.2013 08:02, Konstantin Belousov wrote: On Mon, Nov 04, 2013 at 08:53:41PM +0400, Gleb Smirnoff wrote: On Mon, Nov 04, 2013 at 06:38:25PM +0200, Konstantin Belousov wrote: K Also please show me the CPU features banner from the boot in the VB, K like this: I have already collected them all. See attaches. Legend: dmesg.bbpwd_mkdb crashes during install dmesg.milu.pngpwd_mkdb crashes during install dmesg.thinkinstallation succeeds, but world build crashes instantly dmesg.ruall works dmesg.morannonall works First, all reported instances have ata attachment for the ada0, except of milu (possibly). So this means that kernel does transient remapping, and very different code path is executed comparing with what I thought initially. The path is simpler than the pure unmapped i/o. I wasn't able to finish installation in both cases: nor IDE nor SATA emulated VBox disk. Second, I use QEMU with the ata0 attachment for the disks regularly, and I do not have an issue. I also did not see a report from the real h/w. Third point is that all reports are i386. Is there anybody with amd64, vbox, ata and the same corruption hiddent by disabling unmapped i/o ? I'll try amd64 when BETA3 iso arrives to my HDD. In what way the non-working images were installed ? Is it possible to produce the problematic installs by doing it one way, and non-problematic by another ? In my case it was just idiot-proof: enter,enter,enter (except installing ports/src/games), enter password, enter password again...Error...Start over installation. Every case of installation was like that. I tried turning off SU+J, SU. Didn't helped. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ4wKMACgkQPQ1pa2ELkNnA2wCfY4sgXlI09CDDCS6ZrenAzra5 hQcAoIXQmlhunbgF539JwVYMUiw1Kb08 =b5Pq -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05.11.2013 09:15, Boris Bobrov wrote: Disabling VT-x in VB helps too. I can confirm that. - --hwvirtex off and things are working again. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ4wakACgkQPQ1pa2ELkNk0mwCeOh4R3Q/yymyqkAxfui8bRIIR UucAniyLb0mnsdkNu39W+stjdtvxrvfT =cXrv -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05.11.2013 08:02, Konstantin Belousov wrote: Third point is that all reports are i386. Is there anybody with amd64, vbox, ata and the same corruption hiddent by disabling unmapped i/o ? In what way the non-working images were installed ? Is it possible to produce the problematic installs by doing it one way, and non-problematic by another ? FreeBSD-10.0-BETA3-amd64-disc1.iso have no such problems - it works and installs fine(after enabling ioapic, which was disabled by default in my case). The only thing which I've changed was --ioapic on and medium for VBox. Rest was the same in both cases. I suspect no big differences between BETA2 and BETA3. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ4yq4ACgkQPQ1pa2ELkNmJRwCffkycWLFe2LMcNE/NBrTCMCcm IfkAn0riY03NO9e+h6bKeHFRLkRfJ/e8 =3PEf -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
В сообщении от Tuesday 05 of November 2013 11:06:09 Gleb написал: On Tue, Nov 05, 2013 at 09:02:22AM +0200, Konstantin Belousov wrote: K First, all reported instances have ata attachment for the ada0, except K of milu (possibly). So this means that kernel does transient remapping, K and very different code path is executed comparing with what I thought K initially. The path is simpler than the pure unmapped i/o. K K Second, I use QEMU with the ata0 attachment for the disks regularly, and K I do not have an issue. I also did not see a report from the real h/w. K K Third point is that all reports are i386. Is there anybody with amd64, K vbox, ata and the same corruption hiddent by disabling unmapped i/o ? K K In what way the non-working images were installed ? Is it possible to K produce the problematic installs by doing it one way, and non-problematic K by another ? The only known way to get FreeBSD working is to turn off unmapped io in loader. Any tweaking of hardware in VB or changes in the install process do not affect. Disabling VT-x in VB helps too. -- С наилучшими пожеланиями, Boris signature.asc Description: This is a digitally signed message part.
Re: 10.0-BETA1 i386 on VirtualBox
On Tue, Nov 05, 2013 at 01:24:33PM +0400, Gleb Smirnoff wrote: On Tue, Nov 05, 2013 at 01:09:04PM +0400, Gleb Smirnoff wrote: T B The only known way to get FreeBSD working is to turn off unmapped io T B in loader. Any tweaking of hardware in VB or changes in the install T B process do not affect. T B T B Disabling VT-x in VB helps too. T T Doesn't help with my issue. This could mean that my issue and the one T that Boris and Maciej encountered are different. Verify that VT-x is indeed turned off. Try to turn it off in BIOS, than check for the VMX bit in the features2 line on the host. P.S. Just to confirm that turning off unmapped io in loader fixes my issue with random buildworld failures. This is not the fix, it is rather a masking for a bug. Right now, I am even more sure that the issue is in vbox. And still, anybody able to get the problem on amd64 guest ? pgpVYf4ipCQWf.pgp Description: PGP signature
Re: 10.0-BETA1 i386 on VirtualBox
On 11/05/13 12:45, Konstantin Belousov wrote: This is not the fix, it is rather a masking for a bug. Right now, I am even more sure that the issue is in vbox. And still, anybody able to get the problem on amd64 guest ? I have run numerous versions of 10 (64bit) inside VirtualBox without any issues, the only problem I have is that virtualbox additions don't compile on 10. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03.11.2013 15:41, Konstantin Belousov wrote: On Sun, Nov 03, 2013 at 05:46:01PM +0400, Gleb Smirnoff wrote: Maciej, Boris, On Sun, Nov 03, 2013 at 04:29:11PM +0400, Boris Bobrov wrote: B I traced this down to r248521: B svn log -r248521 B --- B - r248521 | kib | 2013-03-19 16:08:15 +0100 (Tue, 19 Mar 2013) | 5 B lines B B UFS support of the unmapped i/o for the user data buffers. B B Sponsored by: The FreeBSD Foundation B Tested by: pho, scottl, jhb, bf B B --- B - B B The last working revision is 248520. B B Yes, I confirm that. Thanks for you help! Can you please now try unpatched vanilla 10.0-BETA2 iso file and when it boots set in loader (before kernel): OK set vfs.unmapped_buf_allowed=0 OK boot Show what disk driver is used, also show the output of hw.ncpu, both from the guest. Konstantin, do you need any other/more info from guest host? Other than hw.ncpu=1 Disk is ada0 at ahcich0 bus 0 scbus2 target 0 lun 0 and second test instance is ada0 at ata0 bus 0 scbus0 target 0 lun 0 Is Gleb's loader hint the final right solution for this problem? - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ3hUEACgkQPQ1pa2ELkNl26wCdG0wsFWMxu+iN4Xig/I4lQ5pv i+gAn1OAVEvf0vXAZu4PRmr9+oEkW+jA =9+kM -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On Mon, Nov 04, 2013 at 12:30:09PM +0100, Maciej Milewski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03.11.2013 15:41, Konstantin Belousov wrote: On Sun, Nov 03, 2013 at 05:46:01PM +0400, Gleb Smirnoff wrote: Maciej, Boris, On Sun, Nov 03, 2013 at 04:29:11PM +0400, Boris Bobrov wrote: B I traced this down to r248521: B svn log -r248521 B --- B - r248521 | kib | 2013-03-19 16:08:15 +0100 (Tue, 19 Mar 2013) | 5 B lines B B UFS support of the unmapped i/o for the user data buffers. B B Sponsored by: The FreeBSD Foundation B Tested by: pho, scottl, jhb, bf B B --- B - B B The last working revision is 248520. B B Yes, I confirm that. Thanks for you help! Can you please now try unpatched vanilla 10.0-BETA2 iso file and when it boots set in loader (before kernel): OK set vfs.unmapped_buf_allowed=0 OK boot Show what disk driver is used, also show the output of hw.ncpu, both from the guest. Konstantin, do you need any other/more info from guest host? Other than hw.ncpu=1 Disk is ada0 at ahcich0 bus 0 scbus2 target 0 lun 0 and second test instance is ada0 at ata0 bus 0 scbus0 target 0 lun 0 So both ahci and ata attached disks show the bug ? Also please show me the CPU features banner from the boot in the VB, like this: CPU: Intel(R) Core(TM) i7-4770S CPU @ 3.10GHz (2993.13-MHz K8-class CPU) Origin = GenuineIntel Id = 0x306c3 Family = 0x6 Model = 0x3c Stepping = 3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x7ffafbffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,b11,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND AMD Features=0x2c100800SYSCALL,NX,Page1GB,RDTSCP,LM AMD Features2=0x21LAHF,ABM Standard Extended Features=0x2fbbGSFSBASE,TSCADJ,BMI1,HLE,AVX2,SMEP,BMI2,ENHMOVSB,INVPCID,RTM TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) Is Gleb's loader hint the final right solution for this problem? Probably not. This smells like a bug in the vbox. It is especially suspicious that only some i/o transfers cause corruption. pgpIHt1IrS9yS.pgp Description: PGP signature
Re: 10.0-BETA1 i386 on VirtualBox
On Mon, Nov 04, 2013 at 06:38:25PM +0200, Konstantin Belousov wrote: K Also please show me the CPU features banner from the boot in the VB, K like this: I have already collected them all. See attaches. Legend: dmesg.bbpwd_mkdb crashes during install dmesg.milu.png pwd_mkdb crashes during install dmesg.think installation succeeds, but world build crashes instantly dmesg.ruall works dmesg.morannon all works -- Totus tuus, Glebius. Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-BETA2 #0 r257166: Sat Oct 26 21:52:30 UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: Intel(R) Core(TM)2 Duo CPU T6570 @ 2.10GHz (1727.60-MHz 686-class CPU) Origin = GenuineIntel Id = 0x1067a Family = 0x6 Model = 0x17 Stepping = 10 Features=0x783fbbfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2 Features2=0x209SSE3,MON,SSSE3 real memory = 268369920 (255 MB) avail memory = 239337472 (228 MB) kbd1 at kbdmux0 random: Software, Yarrow initialized acpi0: VBOX VBOXXSDT on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) attimer0: AT timer port 0x40-0x43,0x50-0x53 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 32-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci_link2: BIOS IRQ 9 for 0.7.INTA does not match previous BIOS IRQ 10 pci0: ACPI PCI bus on pcib0 isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xd000-0xd00f at device 1.1 on pci0 ata0: ATA channel at channel 0 on atapci0 ata1: ATA channel at channel 1 on atapci0 vgapci0: VGA-compatible display mem 0xe000-0xe07f irq 11 at device 2.0 on pci0 em0: Intel(R) PRO/1000 Legacy Network Connection 1.0.6 port 0xd010-0xd017 mem 0xf000-0xf001 irq 10 at device 3.0 on pci0 em0: Ethernet address: 08:00:27:e4:ea:db pci0: base peripheral at device 4.0 (no driver attached) pcm0: Intel ICH (82801AA) port 0xd100-0xd1ff,0xd200-0xd23f irq 5 at device 5.0 on pci0 pcm0: SigmaTel STAC9700/83/84 AC97 Codec ohci0: OHCI (generic) USB controller mem 0xf0804000-0xf0804fff irq 11 at device 6.0 on pci0 usbus0 on ohci0 pci0: bridge at device 7.0 (no driver attached) battery0: ACPI Control Method Battery on acpi0 acpi_acad0: AC Adapter on acpi0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xc7fff,0xe2000-0xe7fff pnpid ORM on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 atrtc0: AT realtime clock at port 0x70 irq 8 on isa0 Event timer RTC frequency 32768 Hz quality 0 ppc0: parallel port not found. Timecounters tick every 10.000 msec pcm0: measured ac97 link rate at 27783 Hz usbus0: 12Mbps Full Speed USB v1.0 ugen0.1: Apple at usbus0 uhub0: Apple OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0 ada0 at ata0 bus 0 scbus0 target 0 lun 0 ada0: VBOX HARDDISK 1.0 ATA-6 device ada0: Serial Number VB7ab20517-23848df6 ada0: 33.300MB/s transfers (UDMA2, PIO 65536bytes) ada0: 4096MB (8388608 512 byte sectors: 16H 63S/T 8322C) ada0: Previously was known as ad0 cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: VBOX CD-ROM 1.0 Removable CD-ROM SCSI-0 device cd0: Serial Number VB2-01700376 cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: cd present [301071 x 2048 byte records] uhub0: 8 ports with 8 removable, self powered random: unblocking device. Timecounter TSC frequency 1727604551 Hz quality 800 Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]... pid 901 (less), uid 0: exited on signal 11 pid 957 (less), uid 0: exited on signal 11 Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-BETA2 #0 r257166: Sat Oct 26 21:52:30 UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz (1637.34-MHz 686-class CPU) Origin = GenuineIntel Id = 0x306a9 Family = 0x6 Model = 0x3a
Re: 10.0-BETA1 i386 on VirtualBox
On Mon, Nov 04, 2013 at 08:53:41PM +0400, Gleb Smirnoff wrote: On Mon, Nov 04, 2013 at 06:38:25PM +0200, Konstantin Belousov wrote: K Also please show me the CPU features banner from the boot in the VB, K like this: I have already collected them all. See attaches. Legend: dmesg.bb pwd_mkdb crashes during install dmesg.milu.pngpwd_mkdb crashes during install dmesg.think installation succeeds, but world build crashes instantly dmesg.ru all works dmesg.morannonall works First, all reported instances have ata attachment for the ada0, except of milu (possibly). So this means that kernel does transient remapping, and very different code path is executed comparing with what I thought initially. The path is simpler than the pure unmapped i/o. Second, I use QEMU with the ata0 attachment for the disks regularly, and I do not have an issue. I also did not see a report from the real h/w. Third point is that all reports are i386. Is there anybody with amd64, vbox, ata and the same corruption hiddent by disabling unmapped i/o ? In what way the non-working images were installed ? Is it possible to produce the problematic installs by doing it one way, and non-problematic by another ? pgpqGG70LZE0H.pgp Description: PGP signature
Re: 10.0-BETA1 i386 on VirtualBox
On Tue, Nov 05, 2013 at 09:02:22AM +0200, Konstantin Belousov wrote: K First, all reported instances have ata attachment for the ada0, except K of milu (possibly). So this means that kernel does transient remapping, K and very different code path is executed comparing with what I thought K initially. The path is simpler than the pure unmapped i/o. K K Second, I use QEMU with the ata0 attachment for the disks regularly, and K I do not have an issue. I also did not see a report from the real h/w. K K Third point is that all reports are i386. Is there anybody with amd64, K vbox, ata and the same corruption hiddent by disabling unmapped i/o ? K K In what way the non-working images were installed ? Is it possible to K produce the problematic installs by doing it one way, and non-problematic K by another ? The only known way to get FreeBSD working is to turn off unmapped io in loader. Any tweaking of hardware in VB or changes in the install process do not affect. -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.11.2013 08:06, Boris Bobrov wrote: В сообщении от Thursday 31 of October 2013 17:54:32 Gleb написал: On Thu, Oct 31, 2013 at 05:48:43PM +0400, Gleb Smirnoff wrote: T B 1. The bug disappeares if I disable VT-x/AMD-V in my virtual machine T B settings (Settings - System - Acceleration) and appeares if I enable it T B (thanks to Gleb for inspiration yesterday). It disappeares everywhere, on T B all revisions. T B T B 2. r244315 seems to be not buggy even with VT-x enabled. So we have to T B look somewhere between r244315 and r248935. T T Good news! Thanks Boris. T T Can you track this down to a particular revision? I have suspision that it is very close to the bhyve checkin: --- - r245652 | neel | 2013-01-19 08:18:52 +0400 (сб, 19 янв 2013) | 9 lines Merge projects/bhyve to head. 'bhyve' was developed by grehan@ and myself at NetApp (thanks!). Special thanks to Peter Snyder, Joe Caradonna and Michael Dexter for their support and encouragement. Obtained from: NetApp --- - since this is the code that started to utilize VT-x. Can you please check this revision and -1 revision to it? r245652 is not buggy. I traced this down to r248521: svn log -r248521 - r248521 | kib | 2013-03-19 16:08:15 +0100 (Tue, 19 Mar 2013) | 5 lines UFS support of the unmapped i/o for the user data buffers. Sponsored by: The FreeBSD Foundation Tested by: pho, scottl, jhb, bf - The last working revision is 248520. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ2HUwACgkQPQ1pa2ELkNngDwCgg7lwWXyK5gIsL1i1HssddtlA QocAniNQENn9nGAj7uOYxYRB90Ch5quR =+YaO -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
В сообщении от Sunday 03 of November 2013 13:54:20 Maciej написал: On 02.11.2013 08:06, Boris Bobrov wrote: В сообщении от Thursday 31 of October 2013 17:54:32 Gleb написал: On Thu, Oct 31, 2013 at 05:48:43PM +0400, Gleb Smirnoff wrote: T B 1. The bug disappeares if I disable VT-x/AMD-V in my virtual machine T B settings (Settings - System - Acceleration) and appeares if I enable it T B (thanks to Gleb for inspiration yesterday). It disappeares everywhere, on T B all revisions. T B T B 2. r244315 seems to be not buggy even with VT-x enabled. So we have to T B look somewhere between r244315 and r248935. T T Good news! Thanks Boris. T T Can you track this down to a particular revision? I have suspision that it is very close to the bhyve checkin: --- - r245652 | neel | 2013-01-19 08:18:52 +0400 (сб, 19 янв 2013) | 9 lines Merge projects/bhyve to head. 'bhyve' was developed by grehan@ and myself at NetApp (thanks!). Special thanks to Peter Snyder, Joe Caradonna and Michael Dexter for their support and encouragement. Obtained from: NetApp --- - since this is the code that started to utilize VT-x. Can you please check this revision and -1 revision to it? r245652 is not buggy. I traced this down to r248521: svn log -r248521 --- - r248521 | kib | 2013-03-19 16:08:15 +0100 (Tue, 19 Mar 2013) | 5 lines UFS support of the unmapped i/o for the user data buffers. Sponsored by: The FreeBSD Foundation Tested by: pho, scottl, jhb, bf --- - The last working revision is 248520. Yes, I confirm that. -- С наилучшими пожеланиями, Boris signature.asc Description: This is a digitally signed message part.
Re: 10.0-BETA1 i386 on VirtualBox
Maciej, Boris, On Sun, Nov 03, 2013 at 04:29:11PM +0400, Boris Bobrov wrote: B I traced this down to r248521: B svn log -r248521 B --- B - r248521 | kib | 2013-03-19 16:08:15 +0100 (Tue, 19 Mar 2013) | 5 B lines B B UFS support of the unmapped i/o for the user data buffers. B B Sponsored by: The FreeBSD Foundation B Tested by: pho, scottl, jhb, bf B B --- B - B B The last working revision is 248520. B B Yes, I confirm that. Thanks for you help! Can you please now try unpatched vanilla 10.0-BETA2 iso file and when it boots set in loader (before kernel): OK set vfs.unmapped_buf_allowed=0 OK boot -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On Sun, Nov 03, 2013 at 05:46:01PM +0400, Gleb Smirnoff wrote: Maciej, Boris, On Sun, Nov 03, 2013 at 04:29:11PM +0400, Boris Bobrov wrote: B I traced this down to r248521: B svn log -r248521 B --- B - r248521 | kib | 2013-03-19 16:08:15 +0100 (Tue, 19 Mar 2013) | 5 B lines B B UFS support of the unmapped i/o for the user data buffers. B B Sponsored by: The FreeBSD Foundation B Tested by: pho, scottl, jhb, bf B B --- B - B B The last working revision is 248520. B B Yes, I confirm that. Thanks for you help! Can you please now try unpatched vanilla 10.0-BETA2 iso file and when it boots set in loader (before kernel): OK set vfs.unmapped_buf_allowed=0 OK boot Show what disk driver is used, also show the output of hw.ncpu, both from the guest. pgpPrD73ZgtJ3.pgp Description: PGP signature
Re: 10.0-BETA1 i386 on VirtualBox
On guest hw.ncpu=1 and disk is connected to emulated Intel ahci sata controller visible as ada0. Konstantin Belousov kostik...@gmail.com napisał: On Sun, Nov 03, 2013 at 05:46:01PM +0400, Gleb Smirnoff wrote: Maciej, Boris, On Sun, Nov 03, 2013 at 04:29:11PM +0400, Boris Bobrov wrote: B I traced this down to r248521: B svn log -r248521 B --- B - r248521 | kib | 2013-03-19 16:08:15 +0100 (Tue, 19 Mar 2013) | 5 B lines B B UFS support of the unmapped i/o for the user data buffers. B B Sponsored by: The FreeBSD Foundation B Tested by: pho, scottl, jhb, bf B B --- B - B B The last working revision is 248520. B B Yes, I confirm that. Thanks for you help! Can you please now try unpatched vanilla 10.0-BETA2 iso file and when it boots set in loader (before kernel): OK set vfs.unmapped_buf_allowed=0 OK boot Show what disk driver is used, also show the output of hw.ncpu, both from the guest. -- Wysłane z Androida za pomocą K-9 Mail. Prosze wybaczyć lakoniczność. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On 03.11.2013 14:46, Gleb Smirnoff wrote: Maciej, Boris, On Sun, Nov 03, 2013 at 04:29:11PM +0400, Boris Bobrov wrote: B I traced this down to r248521: B svn log -r248521 B --- B - r248521 | kib | 2013-03-19 16:08:15 +0100 (Tue, 19 Mar 2013) | 5 B lines B B UFS support of the unmapped i/o for the user data buffers. B B Sponsored by: The FreeBSD Foundation B Tested by: pho, scottl, jhb, bf B B --- B - B B The last working revision is 248520. B B Yes, I confirm that. Thanks for you help! Can you please now try unpatched vanilla 10.0-BETA2 iso file and when it boots set in loader (before kernel): OK set vfs.unmapped_buf_allowed=0 OK boot Gleb, that seems to work fine. I can end installation without problems. Thank you for this solution. -- Pozdrawiam, Maciej Milewski ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.11.2013 08:06, Boris Bobrov wrote: В сообщении от Thursday 31 of October 2013 17:54:32 Gleb написал: On Thu, Oct 31, 2013 at 05:48:43PM +0400, Gleb Smirnoff wrote: T B 1. The bug disappeares if I disable VT-x/AMD-V in my virtual machine T B settings (Settings - System - Acceleration) and appeares if I enable it T B (thanks to Gleb for inspiration yesterday). It disappeares everywhere, on T B all revisions. T B T B 2. r244315 seems to be not buggy even with VT-x enabled. So we have to T B look somewhere between r244315 and r248935. T T Good news! Thanks Boris. T T Can you track this down to a particular revision? I have suspision that it is very close to the bhyve checkin: --- - r245652 | neel | 2013-01-19 08:18:52 +0400 (сб, 19 янв 2013) | 9 lines Merge projects/bhyve to head. 'bhyve' was developed by grehan@ and myself at NetApp (thanks!). Special thanks to Peter Snyder, Joe Caradonna and Michael Dexter for their support and encouragement. Obtained from: NetApp --- - since this is the code that started to utilize VT-x. Can you please check this revision and -1 revision to it? r245652 is not buggy. It's somewhere between r248500(passwd works) and r248556(passwd don't work). I haven't yet traced this down. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ05jAACgkQPQ1pa2ELkNlKRgCfUDUUYSE2WAUF3icb9xkaL4HW /mEAn1ohyDuvU+lsEw0DI7iCtktyMYj6 =LC84 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
В сообщении от Thursday 31 of October 2013 17:54:32 Gleb написал: On Thu, Oct 31, 2013 at 05:48:43PM +0400, Gleb Smirnoff wrote: T B 1. The bug disappeares if I disable VT-x/AMD-V in my virtual machine T B settings (Settings - System - Acceleration) and appeares if I enable it T B (thanks to Gleb for inspiration yesterday). It disappeares everywhere, on T B all revisions. T B T B 2. r244315 seems to be not buggy even with VT-x enabled. So we have to T B look somewhere between r244315 and r248935. T T Good news! Thanks Boris. T T Can you track this down to a particular revision? I have suspision that it is very close to the bhyve checkin: --- - r245652 | neel | 2013-01-19 08:18:52 +0400 (сб, 19 янв 2013) | 9 lines Merge projects/bhyve to head. 'bhyve' was developed by grehan@ and myself at NetApp (thanks!). Special thanks to Peter Snyder, Joe Caradonna and Michael Dexter for their support and encouragement. Obtained from: NetApp --- - since this is the code that started to utilize VT-x. Can you please check this revision and -1 revision to it? r245652 is not buggy. -- С наилучшими пожеланиями, Boris signature.asc Description: This is a digitally signed message part.
Re: 10.0-BETA1 i386 on VirtualBox
On Wed, Oct 30, 2013 at 09:31:22PM -0400, Glen Barber wrote: G Can any of you suggest a way to reproduce the bug on a livecd reliably? G G I'll rephrase that: G G Can anybody suggest a way to reproduce the bug on a livecd reliably, if G you ever met the bug before? G G G I have not been able to. I have been able to also do full G buildworld/buildkernel within the VM, whereas Gleb would observe random G crashes, in addition to other oddities. G G I'm baffled, but I have a (unconfirmed) suspicion this is a Virtualbox G bug somewhere... :\ I have analyzed dmesgs from Boris, Maciej and mine VS a dmesg from box where 10.0-BETA2 i386 works flawlessly in VB. I failed to find any clue. It looks like we need Boris or Maciej to perform binary search through last two years of head development. :( -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On Thu, Oct 31, 2013 at 03:35:06PM +0400, Boris Bobrov wrote: B В сообщении от Thursday 31 of October 2013 13:49:38 Gleb написал: B I have analyzed dmesgs from Boris, Maciej and mine VS a dmesg from box B where 10.0-BETA2 i386 works flawlessly in VB. I failed to find any B clue. B B It looks like we need Boris or Maciej to perform binary search through B last two years of head development. :( B B 20130330-r248935 is buggy, so I've cut 7 months. B B I am not sure how to perform the search. snv up -r, build, copy to mounted B .vdi, test? Or install 9.2 and start from there? Better install 9.2 and start from there. Chances that new kernel would work with old userland are much higher, than vice versa. B Should I checkout base repository or something else/more? You need to checkout base/head, somewhere near date of 9.0-RELEASE, and bisect between that revision and r248935. -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On 31.10.2013 01:08, Boris Bobrov wrote: 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: ^A at the end But the same file copied through disk - network shows no ^A at the end. as /var and /tmp ar on md0 I suspect some kind of memory corruption. -- Pozdrawiam, Maciej Milewski messages Description: Binary data ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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@think:~:|pkg info -x virtual virtualbox-ose-4.2.18_1 virtualbox-ose-kmod-4.2.18 glebius@think:~:|uname -a FreeBSD think.nginx.com 11.0-CURRENT FreeBSD 11.0-CURRENT #13 r257045: Thu Oct 24 15:16:04 MSK 2013 gleb...@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 the end The same file copied through disk - network shows no ^@ at the end. As /var and /tmp ar on md0/md1 I suspect some kind of memory corruption. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJyRswACgkQPQ1pa2ELkNll/wCfeqN8k4ZW+E57tDohFGelCGTs E8IAoIB+pRVVQpugIlYEoGj7dnj5HkgX =JRp8 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31.10.2013 13:31, Boris Bobrov wrote: 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. I got the same with less. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJyVrIACgkQPQ1pa2ELkNkDNACeJKj/7tJUjQ3yCusIZEFQlNJ9 NvoAn0S/zFhRNxuOf+yLcRUlDI9N6u/3 =d0l5 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On Thu, Oct 31, 2013 at 09:16:34AM -0400, Glen Barber wrote: http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-BETA1/amd64/20131007/ Wrong arch, sorry. http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-BETA1/i386/20131007/ Glen pgplZzsjmMRlF.pgp Description: PGP signature
Re: 10.0-BETA1 i386 on VirtualBox
В сообщении от Thursday 31 of October 2013 13:49:38 Gleb написал: I have analyzed dmesgs from Boris, Maciej and mine VS a dmesg from box where 10.0-BETA2 i386 works flawlessly in VB. I failed to find any clue. It looks like we need Boris or Maciej to perform binary search through last two years of head development. :( 20130330-r248935 is buggy, so I've cut 7 months. I am not sure how to perform the search. snv up -r, build, copy to mounted .vdi, test? Or install 9.2 and start from there? Should I checkout base repository or something else/more? -- С наилучшими пожеланиями, Boris signature.asc Description: This is a digitally signed message part.
Re: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31.10.2013 14:26, Glen Barber wrote: On Thu, Oct 31, 2013 at 09:16:34AM -0400, Glen Barber wrote: http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-BETA1/amd64/20131007/ Wrong arch, sorry. http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-BETA1/i386/20131007/ Glen No worries, found corect one myself :) - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJyXAAACgkQPQ1pa2ELkNnwOwCfYTUev/zs7E3sIslsCuCqZ7o+ ie4AmgK8AikXVbfIIeT2kSsZDmXarVGv =rIpl -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On Thu, Oct 31, 2013 at 02:10:10PM +0100, Maciej Milewski wrote: On 31.10.2013 13:31, Boris Bobrov wrote: 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. I got the same with less. Can you try 10.0-ALPHA5? I have VM images here: http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-BETA1/amd64/20131007/ You should be able to just attach the vmdk to a Vbox VM. Glen pgpyy_o3K3Mla.pgp Description: PGP signature
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@think:~:|pkg info -x virtual virtualbox-ose-4.2.18_1 virtualbox-ose-kmod-4.2.18 glebius@think:~:|uname -a FreeBSD think.nginx.com 11.0-CURRENT FreeBSD 11.0-CURRENT #13 r257045: Thu Oct 24 15:16:04 MSK 2013 gleb...@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 the end The same file copied through disk - network shows no ^@ 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 signature.asc Description: This is a digitally signed message part.
Re: 10.0-BETA1 i386 on VirtualBox
On Thu, Oct 31, 2013 at 05:45:32PM +0400, Boris Bobrov wrote: B Two good news! B B 1. The bug disappeares if I disable VT-x/AMD-V in my virtual machine B settings (Settings - System - Acceleration) and appeares if I enable it B (thanks to Gleb for inspiration yesterday). It disappeares everywhere, on B all revisions. B B 2. r244315 seems to be not buggy even with VT-x enabled. So we have to B look somewhere between r244315 and r248935. Good news! Thanks Boris. Can you track this down to a particular revision? -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On Thu, Oct 31, 2013 at 05:48:43PM +0400, Gleb Smirnoff wrote: T B 1. The bug disappeares if I disable VT-x/AMD-V in my virtual machine T B settings (Settings - System - Acceleration) and appeares if I enable it T B (thanks to Gleb for inspiration yesterday). It disappeares everywhere, on T B all revisions. T B T B 2. r244315 seems to be not buggy even with VT-x enabled. So we have to T B look somewhere between r244315 and r248935. T T Good news! Thanks Boris. T T Can you track this down to a particular revision? I have suspision that it is very close to the bhyve checkin: r245652 | neel | 2013-01-19 08:18:52 +0400 (сб, 19 янв 2013) | 9 lines Merge projects/bhyve to head. 'bhyve' was developed by grehan@ and myself at NetApp (thanks!). Special thanks to Peter Snyder, Joe Caradonna and Michael Dexter for their support and encouragement. Obtained from: NetApp since this is the code that started to utilize VT-x. Can you please check this revision and -1 revision to it? -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31.10.2013 14:26, Glen Barber wrote: On Thu, Oct 31, 2013 at 09:16:34AM -0400, Glen Barber wrote: http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-BETA1/amd64/20131007/ Wrong arch, sorry. http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-BETA1/i386/20131007/ Glen Glen, Simple less /var/log/messages works fine but passwd: in pam_sm_chauthtok(): pw_mkdb() failed passwd: pam_chauthtok(): error in service module - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJyYWAACgkQPQ1pa2ELkNkq0gCggFX1KeU9TyF5s46hjDSdSQDV 5WAAoIn56n9r83RV0kVd4QOQDJNSZQ/Q =7vZS -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
В сообщении от Tuesday 29 of October 2013 15:09:57 вы написали: 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. ... Boris and Maciej, if you use non-default configuration, can you please provide more details? Two good news! 1. The bug disappeares if I disable VT-x/AMD-V in my virtual machine settings (Settings - System - Acceleration) and appeares if I enable it (thanks to Gleb for inspiration yesterday). It disappeares everywhere, on all revisions. 2. r244315 seems to be not buggy even with VT-x enabled. So we have to look somewhere between r244315 and r248935. -- С наилучшими пожеланиями, Boris signature.asc Description: This is a digitally signed message part.
Re: 10.0-BETA1 i386 on VirtualBox
В сообщении от 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@think:~:|pkg info -x virtual virtualbox-ose-4.2.18_1 virtualbox-ose-kmod-4.2.18 glebius@think:~:|uname -a FreeBSD think.nginx.com 11.0-CURRENT FreeBSD 11.0-CURRENT #13 r257045: Thu Oct 24 15:16:04 MSK 2013 gleb...@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? -- С наилучшими пожеланиями, Boris signature.asc Description: This is a digitally signed message part.
Re: 10.0-BETA1 i386 on VirtualBox
В сообщении от 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@think:~:|pkg info -x virtual virtualbox-ose-4.2.18_1 virtualbox-ose-kmod-4.2.18 glebius@think:~:|uname -a FreeBSD think.nginx.com 11.0-CURRENT FreeBSD 11.0-CURRENT #13 r257045: Thu Oct 24 15:16:04 MSK 2013 gleb...@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 signature.asc Description: This is a digitally signed message part.
Re: 10.0-BETA1 i386 on VirtualBox
On Thu, Oct 31, 2013 at 04:08:17AM +0400, Boris Bobrov wrote: 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? I have not been able to. I have been able to also do full buildworld/buildkernel within the VM, whereas Gleb would observe random crashes, in addition to other oddities. I'm baffled, but I have a (unconfirmed) suspicion this is a Virtualbox bug somewhere... :\ Glen pgpDetkhF89d3.pgp Description: PGP signature
Re: 10.0-BETA1 i386 on VirtualBox
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@think:~:|pkg info -x virtual virtualbox-ose-4.2.18_1 virtualbox-ose-kmod-4.2.18 glebius@think:~:|uname -a FreeBSD think.nginx.com 11.0-CURRENT FreeBSD 11.0-CURRENT #13 r257045: Thu Oct 24 15:16:04 MSK 2013 gleb...@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? -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On 29.10.2013 12:09, Gleb Smirnoff wrote:
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@think:~:|pkg info -x virtual
virtualbox-ose-4.2.18_1
virtualbox-ose-kmod-4.2.18
glebius@think:~:|uname -a
FreeBSD think.nginx.com 11.0-CURRENT FreeBSD 11.0-CURRENT #13 r257045: Thu Oct
24 15:16:04 MSK 2013
gleb...@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?
No - in my case it's the same with 10-BETA2 :(
$ pkg_version -vs virtualbox
virtualbox-ose-4.2.18_1 = up-to-date with port
virtualbox-ose-kmod-4.2.18 = up-to-date with port
$ uname -a
FreeBSD intranet.tup.com.pl 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0
r255613: Mon Sep 16 20:25:59 CEST 2013
m...@intranet.tup.com.pl:/usr/obj/usr/src/sys/intranet amd64
I'm using script:
$ cat create_BSD.sh
#!/bin/sh
NAME=FreeBSD10BETA2
DVDMEDIUM=/data/iso/FreeBSD-10.0-BETA2-i386-disc1.iso
VBoxManage createvm -name ${NAME} -register
VBoxManage modifyvm ${NAME} --memory 1024 --acpi on --boot1 dvd
--nictype1 82540EM --nic1 bridged --bridgeadapter1 rl0
VBoxManage createhd --filename ${NAME} --size 3
VBoxManage storagectl ${NAME} --name SATA Controller --add sata
--controller IntelAhci --sataportcount 4
VBoxManage storageattach ${NAME} --storagectl SATA Controller --port
0 --device 0 --type hdd --medium ${NAME}.vdi
VBoxManage storagectl ${NAME} --name IDE Controller --add ide
--controller PIIX4
VBoxManage storageattach ${NAME} --storagectl IDE Controller --port
0 --device 0 --type dvddrive --medium ${DVDMEDIUM}
VBoxManage modifyvm ${NAME} --vrdeproperty VNCPassword=password
and starting via:
VBoxHeadless -s FreeBSD10BETA2
and connecting through vnc(from krdc) on port 3389
Gleb are you on some irc channel?
--
Pozdrawiam,
Maciej Milewski
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On 29.10.2013 12:09, Gleb Smirnoff wrote: 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@think:~:|pkg info -x virtual virtualbox-ose-4.2.18_1 virtualbox-ose-kmod-4.2.18 glebius@think:~:|uname -a FreeBSD think.nginx.com 11.0-CURRENT FreeBSD 11.0-CURRENT #13 r257045: Thu Oct 24 15:16:04 MSK 2013 gleb...@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? I've tried default install without any games,ports and src. With guided disk organization, with simple password qaz123 or longer one, results are tha same: error in service module. -- Pozdrawiam, Maciej Milewski ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
Maciej, 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? Can you please tell version of VirtualBox and host OS? -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On 27.10.2013 09:03, Gleb Smirnoff wrote: Maciej, 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? Can you please tell version of VirtualBox and host OS? One of them is: FreeBSD 9.2-PRERELEASE #0 r255613: Mon Sep 16 20:25:59 CEST 2013 $ VBoxManage -v 4.2.18_OSEr88780 # pkg_version -vs virtualbox virtualbox-ose-4.2.18_1 = up-to-date with port virtualbox-ose-kmod-4.2.18 = up-to-date with port And the same is with % VBoxManage -v 4.2.18_OSEr88780 Under ArchLinux. -- Pozdrawiam, Maciej Milewski ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
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 have received same problem report in private email. I'll try to setup VirtualBox and reproduce. -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On Thu, Oct 24, 2013 at 11:16 AM, Maciej Milewski m...@dat.pl wrote: I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under VirtualBox. The problem is with setting/changing root password during install process. After entering password twice there is: passwd: pam_chauthtok(): error in service module Then there shows pwd_mkdb.core in current directory. The same VirtualBox machine has no problems with installing FreeBSD-9.2-RELEASE Has anyone any clues? Regards, Maciej Milewski I have seen that error when the password database in /etc is not writeable (in my case, / was mounted read-only). ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On 24.10.2013 17:34, Ryan Stone wrote: On Thu, Oct 24, 2013 at 11:16 AM, Maciej Milewski m...@dat.pl wrote: I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under VirtualBox. The problem is with setting/changing root password during install process. After entering password twice there is: passwd: pam_chauthtok(): error in service module Then there shows pwd_mkdb.core in current directory. The same VirtualBox machine has no problems with installing FreeBSD-9.2-RELEASE Has anyone any clues? Regards, Maciej Milewski I have seen that error when the password database in /etc is not writeable (in my case, / was mounted read-only). I don't think that's the case as during install I went to another console to check how is mounted future / and it's: /dev/ada0p2 on /mnt (ufs, local, journaled soft-updates) and /mnt/etc/pwd.db, group, passwd are 644 and spwd.db,master.passwd are 600 The same as in running 9.2-RELEASE Anyway, thanks for the hint. Regards, Maciej Milewski ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-BETA1 i386 on VirtualBox
On 24.10.2013 17:47, Maciej Milewski wrote: On 24.10.2013 17:34, Ryan Stone wrote: On Thu, Oct 24, 2013 at 11:16 AM, Maciej Milewski m...@dat.pl wrote: I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under VirtualBox. The problem is with setting/changing root password during install process. After entering password twice there is: passwd: pam_chauthtok(): error in service module Then there shows pwd_mkdb.core in current directory. The same VirtualBox machine has no problems with installing FreeBSD-9.2-RELEASE Has anyone any clues? Regards, Maciej Milewski I have seen that error when the password database in /etc is not writeable (in my case, / was mounted read-only). I don't think that's the case as during install I went to another console to check how is mounted future / and it's: /dev/ada0p2 on /mnt (ufs, local, journaled soft-updates) and /mnt/etc/pwd.db, group, passwd are 644 and spwd.db,master.passwd are 600 The same as in running 9.2-RELEASE Anyway, thanks for the hint. Regards, Maciej Milewski I've managed to make another simple test: chroot from 9.2-RELEASE kernel and I can change the password without a problem, chroot from 10.0-BETA1 kernel and error appears. No matter if I use 10.0-BETA1 kernel on 9.2-RELEASE userland or boot from CD image. For tests I turned off journal, left only soft-updates. Regards, Maciej Milewski ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
