date:20160802

Build failed in Jenkins: FreeBSD_stable_10 #349

2016-08-02 Thread jenkins-admin

See 

--
[...truncated 205596 lines...]
--- _lshrdi3.So ---
--- _ashldi3.So ---
--- _ashrdi3.So ---
--- _negdi2.So ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config
 
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc 
-I.  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools
 -std=gnu99 -Qunused-arguments -fpic -DSHARED  -DL_negdi2 -o _negdi2.So 
/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc2.c
--- _lshrdi3.So ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config
 
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc 
-I.  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools
 -std=gnu99 -Qunused-arguments -fpic -DSHARED  -DL_lshrdi3 -o _lshrdi3.So 
/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc2.c
--- _ashldi3.So ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config
 
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc 
-I.  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools
 -std=gnu99 -Qunused-arguments -fpic -DSHARED  -DL_ashldi3 -o _ashldi3.So 
/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc2.c
--- _ashrdi3.So ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config
 
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc 
-I.  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools
 -std=gnu99 -Qunused-arguments -fpic -DSHARED  -DL_ashrdi3 -o _ashrdi3.So 
/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc2.c
--- _cmpdi2.So ---
--- _ucmpdi2.So ---
--- _enable_execute_stack.So ---
--- _cmpdi2.So ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config

FYI: amd64 FreeBSD 11.0-BETA3 running under VirtualBox on Mac OS X 10.11.6 : using qemu-system-sparc64 from emulators/qemu-devel in such a FreeBSD results in...

2016-08-02 Thread Mark Millard

My first try at building qemu (really emulators/qemu-devel ) and trying to use 
it. What I tried turns out to not work:

CAM status: Command timeout

and related material result.

Context for the below amd64 FreeBSD 11.0-BETA3 -r303469 running under 
VirtualBox 5.0.26 r108824 on Mac OS X 10.11.6 .

(Nested contexts when qemu is then started from inside FreeBSD: So I was not 
hopeful. But I only have slow hardware running FreeBSD directly as stands so I 
figured I'd try the below.)

> # truncate -s 4g IMGs/sparc64_FreeBSD.img

> # qemu-system-sparc64 -nographic -m 2048 -cdrom 
> ISOs/FreeBSD-11.0-BETA3-sparc64-disc1.iso -drive 
> file=IMGs/sparc64_FreeBSD.img,format=raw -boot d
> OpenBIOS for Sparc64
> Configuration device id QEMU version 1 machine id 0
> kernel cmdline 
> CPUs: 1 x SUNW,UltraSPARC-IIi
> UUID: ----
> Welcome to OpenBIOS v1.1 built on Apr 18 2016 08:20
>   Type 'help' for detailed information
> Trying cdrom:f...
> Not a bootable ELF image
> Loading a.out image...
> Loaded 7680 bytes
> entry point is 0x4000
> 
> Jumping to entry point 4000 for type 0005...
> switching to new context: entry point 0x4000 stack 0xffe84a09
>  
> >> FreeBSD/sparc64 boot block
>Boot path:   /pci@1fe,0/pci-ata@5/ide1@8200/cdrom@0:f
>Boot loader: /boot/loader
> Consoles: Open Firmware console  
> 
> FreeBSD/sparc64 bootstrap loader, Revision 1.0
> (r...@releng2.nyi.freebsd.org, Fri Jul 29 09:00:35 UTC 2016)
> bootpath="/pci@1fe,0/pci-ata@5/ide1@8200/cdrom@0:a"
> Loading /boot/defaults/loader.conf
> /boot/kernel/kernel data=0xcb8b40+0x1edfd8 syms=[0x8+0xd5468+0x8+0xc61f0]
> \
> Hit [Enter] to boot immediately, or any other key for command prompt.
> Booting [/boot/kernel/kernel]...   
> jumping to kernel entry at 0xc00b.
> Copyright (c) 1992-2016 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 11.0-BETA3 #0 r303469: Fri Jul 29 09:02:50 UTC 2016
> r...@releng2.nyi.freebsd.org:/usr/obj/sparc64.sparc64/usr/src/sys/GENERIC 
> sparc64
> gcc version 4.2.1 20070831 patched [FreeBSD]
> VT: init without driver.
> real memory  = 2147483648 (2048 MB)
> avail memory = 2076041216 (1979 MB)
> cpu0: Sun Microsystems UltraSparc-IIi Processor (100.00 MHz CPU)
> random: entropy device external interface
> kbd0 at kbdmux0
> nexus0: 
> nexus0: : incomplete
> pcib0:  mem 0x1fe-0x1fe01ff irq 
> 2032,2030,2031,2021 on nexus0
> pcib0: Sabre, impl 0, version 0, IGN 0x1f, bus A, 33MHz
> pcib0: DVMA map: 0xc000 to 0xc3ff 8192 entries
> pcib0: [GIANT-LOCKED]
> pci0:  on pcib0
> pcib1:  at device 1.0 on pci0
> pci1:  on pcib1
> pcib2:  at device 1.1 on pci0
> pci2:  on pcib2
> ebus0:  port 0x4000-0x7fff mem 0x300-0x3ff at 
> device 3.0 on pci0
> vgapci0:  mem 0x100-0x1ff,0x200-0x2000fff 
> at device 2.0 on pci0
> vgapci0: Boot video device
> eeprom0:  addr 0x142000-0x143fff on ebus0
> eeprom0: model mk48t59
> ebus0:  addr 0 (no driver attached)
> uart0: <16550 or compatible> addr 0x1403f8-0x1403ff irq 43 on ebus0
> uart0: console (9600,n,8,1)
> ebus0:  addr 0x140060-0x140067 (no driver attached)
> pci0:  at device 4.0 (no driver attached)
> atapci0:  port 
> 0x8100-0x8107,0x8180-0x8183,0x8200-0x8207,0x8280-0x8283,0x8300-0x830f at 
> device 5.0 on pci0
> ata2:  at channel 0 on atapci0
> ata3:  at channel 1 on atapci0
> cryptosoft0:  on nexus0
> nexus0:  type unknown (no driver attached)
> Timecounter "tick" frequency 1 Hz quality 1000
> Event timer "tick" frequency 1 Hz quality 1000

> Timecounters tick every 1.000 msec
> ada0 at ata2 bus 0 scbus0 target 0 lun 0
> ada0:  ATA-7 device
> ada0: Serial Number QM1
> ada0: 33.300MB/s transfers (UDMA2, PIO 8192bytes)
> ada0: 4096MB (8388608 512 byte sectors)
> cd0 at ata3 bus 0 scbus1 target 0 lun 0
> cd0:  Removable CD-ROM SCSI device
> cd0: Serial Number QM3
> cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes)
> cd0: 528MB (270720 2048 byte sectors)
> taskqgroup_adjust failed cnt: 1 stride: 1 mp_ncpus: 1 smp_started: 0
> taskqgroup_adjust failed cnt: 1 stride: 1 mp_ncpus: 1 smp_started: 0
> Trying to mount root from cd9660:/dev/iso9660/11_0_BETA3_SPARC64_CD [ro]...
> Starting file system checks:
> Mounting local filesystems:.
> random: unblocking device.
> ELF ldconfig path: /lib /usr/lib /usr/lib/compat
> /etc/rc: WARNING: $hostname is not set -- see rc.conf(5).
> Setting up harvesting: 
> [UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,NET_ETHER,NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED
> Feeding entropy: eval: cannot create /entropy: Read-only file system
> (aprobe0:ata3:0:0:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 00 00
> (aprobe0:ata3:0:0:0): CAM status: Command timeout
> (aprobe0:ata3:0:0:0):

Build failed in Jenkins: FreeBSD_stable_10 #348

2016-08-02 Thread jenkins-admin

See 

--
[...truncated 203267 lines...]
--- unwind-dw2-fde-glibc.po ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config
 
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc 
-I.  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools
 -std=gnu99 -Qunused-arguments-fvisibility=hidden -DHIDE_EXPORTS -p -fPIC 
-fexceptions -D__GLIBC__=3 -DElfW=__ElfN -o unwind-dw2-fde-glibc.po 
/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/
 libgcc/../../../contrib/gcc/unwind-dw2-fde-glibc.c
--- unwind-sjlj.po ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config
 
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc 
-I.  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools
 -std=gnu99 -Qunused-arguments-fvisibility=hidden -DHIDE_EXPORTS -p -fPIC 
-fexceptions -D__GLIBC__=3 -DElfW=__ElfN -o unwind-sjlj.po 
/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/..
 /../../contrib/gcc/unwind-sjlj.c
--- gthr-gnat.po ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config
 
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc 
-I.  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools
 -std=gnu99 -Qunused-arguments-fvisibility=hidden -DHIDE_EXPORTS -p -fPIC 
-fexceptions -D__GLIBC__=3 -DElfW=__ElfN -o gthr-gnat.po 
/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../.
 ./../contrib/gcc/gthr-gnat.c
--- unwind-c.po ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config
 
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc 
-I.  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools
 -std=gnu99 -Qunused-arguments-fvisibility=hidden -DHIDE_EXPORTS -p -fPIC 
-fexceptions -D__GLIBC__=3 -DElfW=__ElfN -o unwind-c.po 
/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../..
 /../contrib/gcc/unwind-c.c--- libgcc_eh_p.a ---
building profiled gcc_eh library
ar -crD libgcc_eh_p.a `lorder unwind-dw2.po unwind-dw2-fde-glibc.po 
unwind-sjlj.po gthr-gnat.po unwind-c.po | tsort -q`
ranlib -D libgcc_eh_p.a
--- _negdi2.So ---
--- _lshrdi3.So ---
--- _ashldi3.So ---
--- _ashrdi3.So ---
--- _negdi2.So ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/

Re: Call for testing: VM bugs in 10.3

2016-08-02 Thread Konstantin Belousov

On Tue, Aug 02, 2016 at 01:57:49PM -0600, Ian Lepore wrote:
> On Tue, 2016-08-02 at 22:25 +0300, Konstantin Belousov wrote:
> > Below is the merge of some high-profile virtual memory subsystem bug
> > fixes from stable/10 to 10.3.

> I run 10-stable on my everyday desktop/build machine, but my mail
> client ruined the format of the patches.  Can I just 'svn up' on the 10
> -stable branch and then MFC the revs you list above, or are there hand
> -tweaks to the patches you attached?
If you svn up stable/10, or if your existing sources are already past
r303291, then you already have that patches.

The first sentence of my mail stated that the backport is from stable/10
to 10.3.

Anyway, I put the patch at https://kib.kiev.ua/kib/vm-10.3-bp.1.patch .
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Call for testing: VM bugs in 10.3

2016-08-02 Thread Konstantin Belousov

On Tue, Aug 02, 2016 at 12:47:23PM -0700, pete wright wrote:
> On Aug 2, 2016 12:26 PM, "Konstantin Belousov"  wrote:
> >
> > Below is the merge of some high-profile virtual memory subsystem bug
> > fixes from stable/10 to 10.3. I merged fixes for bugs reported by
> > users, issues which are even theoretically unlikely to occur in real
> > world loads, are not included into the patch set. The later is mostly
> > corrections for the handling of radix insertion failures. Included fixes
> > are for random SIGSEGV delivered to processes, hangs on "vodead" state
> > on filesystem operations, and several others.
> >
> > List of the merged revisions:
> > r301184 prevent parallel object collapses, fixes object lifecycle
> > r301436 do not leak the vm object lock, fixes overcommit disable
> > r302243 avoid the active object marking for vm.vmtotal sysctl, fixes
> > "vodead" hangs
> > r302513 vm_fault() race with the vm_object_collapse(), fixes spurious
> SIGSEGV
> > r303291 postpone BO_DEAD, fixes panic on fast vnode reclaim
> >
> > I am asking for some testing, it is not necessary for your system to
> > exhibit the problematic behaviour for your testing to be useful. I am
> > more looking for smoke-testing kind of confirmation that patch is fine.
> > Neither I nor people who usually help me with testing,  run 10.3 systems.
> >
> 
> Is testing on 10.3-RELEASE useful, or is this only for people tracking
> STABLE?
This is only for people running 10.3.  The list of merged revisions is from
stable/10, where the fixes were already merged for month or more.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Call for testing: VM bugs in 10.3

2016-08-02 Thread Ian Lepore

On Tue, 2016-08-02 at 22:25 +0300, Konstantin Belousov wrote:
> Below is the merge of some high-profile virtual memory subsystem bug
> fixes from stable/10 to 10.3. I merged fixes for bugs reported by
> users, issues which are even theoretically unlikely to occur in real
> world loads, are not included into the patch set. The later is mostly
> corrections for the handling of radix insertion failures. Included
> fixes
> are for random SIGSEGV delivered to processes, hangs on "vodead"
> state
> on filesystem operations, and several others.
> 
> List of the merged revisions:
> r301184 prevent parallel object collapses, fixes object lifecycle
> r301436 do not leak the vm object lock, fixes overcommit disable
> r302243 avoid the active object marking for vm.vmtotal sysctl, fixes
>   "vodead" hangs
> r302513 vm_fault() race with the vm_object_collapse(), fixes spurious
> SIGSEGV
> r303291 postpone BO_DEAD, fixes panic on fast vnode reclaim
> 
> I am asking for some testing, it is not necessary for your system to
> exhibit the problematic behaviour for your testing to be useful. I am
> more looking for smoke-testing kind of confirmation that patch is
> fine.
> Neither I nor people who usually help me with testing,  run 10.3
> systems.
> 
> If everything appear to be fine, my intent is to ask re/so to issue
> Errata Notice with these changes in about a week from now.
> 
> Index: sys/kern/vfs_subr.c
> [...]

I run 10-stable on my everyday desktop/build machine, but my mail
client ruined the format of the patches.  Can I just 'svn up' on the 10
-stable branch and then MFC the revs you list above, or are there hand
-tweaks to the patches you attached?

-- Ian

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Call for testing: VM bugs in 10.3

2016-08-02 Thread pete wright

On Aug 2, 2016 12:26 PM, "Konstantin Belousov"  wrote:
>
> Below is the merge of some high-profile virtual memory subsystem bug
> fixes from stable/10 to 10.3. I merged fixes for bugs reported by
> users, issues which are even theoretically unlikely to occur in real
> world loads, are not included into the patch set. The later is mostly
> corrections for the handling of radix insertion failures. Included fixes
> are for random SIGSEGV delivered to processes, hangs on "vodead" state
> on filesystem operations, and several others.
>
> List of the merged revisions:
> r301184 prevent parallel object collapses, fixes object lifecycle
> r301436 do not leak the vm object lock, fixes overcommit disable
> r302243 avoid the active object marking for vm.vmtotal sysctl, fixes
> "vodead" hangs
> r302513 vm_fault() race with the vm_object_collapse(), fixes spurious
SIGSEGV
> r303291 postpone BO_DEAD, fixes panic on fast vnode reclaim
>
> I am asking for some testing, it is not necessary for your system to
> exhibit the problematic behaviour for your testing to be useful. I am
> more looking for smoke-testing kind of confirmation that patch is fine.
> Neither I nor people who usually help me with testing,  run 10.3 systems.
>

Is testing on 10.3-RELEASE useful, or is this only for people tracking
STABLE?

Thanks!
-pete
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Call for testing: VM bugs in 10.3

2016-08-02 Thread Konstantin Belousov

Below is the merge of some high-profile virtual memory subsystem bug
fixes from stable/10 to 10.3. I merged fixes for bugs reported by
users, issues which are even theoretically unlikely to occur in real
world loads, are not included into the patch set. The later is mostly
corrections for the handling of radix insertion failures. Included fixes
are for random SIGSEGV delivered to processes, hangs on "vodead" state
on filesystem operations, and several others.

List of the merged revisions:
r301184 prevent parallel object collapses, fixes object lifecycle
r301436 do not leak the vm object lock, fixes overcommit disable
r302243 avoid the active object marking for vm.vmtotal sysctl, fixes
"vodead" hangs
r302513 vm_fault() race with the vm_object_collapse(), fixes spurious SIGSEGV
r303291 postpone BO_DEAD, fixes panic on fast vnode reclaim

I am asking for some testing, it is not necessary for your system to
exhibit the problematic behaviour for your testing to be useful. I am
more looking for smoke-testing kind of confirmation that patch is fine.
Neither I nor people who usually help me with testing,  run 10.3 systems.

If everything appear to be fine, my intent is to ask re/so to issue
Errata Notice with these changes in about a week from now.

Index: sys/kern/vfs_subr.c
===
--- sys/kern/vfs_subr.c (revision 303659)
+++ sys/kern/vfs_subr.c (working copy)
@@ -2934,7 +2934,13 @@ vgonel(struct vnode *vp)
TAILQ_EMPTY(>v_bufobj.bo_clean.bv_hd) &&
vp->v_bufobj.bo_clean.bv_cnt == 0,
("vp %p bufobj not invalidated", vp));
-   vp->v_bufobj.bo_flag |= BO_DEAD;
+
+   /*
+* For VMIO bufobj, BO_DEAD is set in vm_object_terminate()
+* after the object's page queue is flushed.
+*/
+   if (vp->v_bufobj.bo_object == NULL)
+   vp->v_bufobj.bo_flag |= BO_DEAD;
BO_UNLOCK(>v_bufobj);
 
/*
Index: sys/vm/vm_fault.c
===
--- sys/vm/vm_fault.c   (revision 303659)
+++ sys/vm/vm_fault.c   (working copy)
@@ -286,7 +286,7 @@ vm_fault_hold(vm_map_t map, vm_offset_t vaddr, vm_
vm_prot_t prot;
long ahead, behind;
int alloc_req, era, faultcount, nera, reqpage, result;
-   boolean_t growstack, is_first_object_locked, wired;
+   boolean_t dead, growstack, is_first_object_locked, wired;
int map_generation;
vm_object_t next_object;
vm_page_t marray[VM_FAULT_READ_MAX];
@@ -423,11 +423,18 @@ fast_failed:
fs.pindex = fs.first_pindex;
while (TRUE) {
/*
-* If the object is dead, we stop here
+* If the object is marked for imminent termination,
+* we retry here, since the collapse pass has raced
+* with us.  Otherwise, if we see terminally dead
+* object, return fail.
 */
-   if (fs.object->flags & OBJ_DEAD) {
+   if ((fs.object->flags & OBJ_DEAD) != 0) {
+   dead = fs.object->type == OBJT_DEAD;
unlock_and_deallocate();
-   return (KERN_PROTECTION_FAILURE);
+   if (dead)
+   return (KERN_PROTECTION_FAILURE);
+   pause("vmf_de", 1);
+   goto RetryFault;
}
 
/*
Index: sys/vm/vm_meter.c
===
--- sys/vm/vm_meter.c   (revision 303659)
+++ sys/vm/vm_meter.c   (working copy)
@@ -93,30 +93,32 @@ SYSCTL_PROC(_vm, VM_LOADAVG, loadavg, CTLTYPE_STRU
 CTLFLAG_MPSAFE, NULL, 0, sysctl_vm_loadavg, "S,loadavg",
 "Machine loadaverage history");
 
+/*
+ * This function aims to determine if the object is mapped,
+ * specifically, if it is referenced by a vm_map_entry.  Because
+ * objects occasionally acquire transient references that do not
+ * represent a mapping, the method used here is inexact.  However, it
+ * has very low overhead and is good enough for the advisory
+ * vm.vmtotal sysctl.
+ */
+static bool
+is_object_active(vm_object_t obj)
+{
+
+   return (obj->ref_count > obj->shadow_count);
+}
+
 static int
 vmtotal(SYSCTL_HANDLER_ARGS)
 {
-   struct proc *p;
struct vmtotal total;
-   vm_map_entry_t entry;
vm_object_t object;
-   vm_map_t map;
-   int paging;
+   struct proc *p;
struct thread *td;
-   struct vmspace *vm;
 
bzero(, sizeof(total));
+
/*
-* Mark all objects as inactive.
-*/
-   mtx_lock(_object_list_mtx);
-   TAILQ_FOREACH(object, _object_list, object_list) {
-   VM_OBJECT_WLOCK(object);
-   vm_object_clear_flag(object, OBJ_ACTIVE);
-   VM_OBJECT_WUNLOCK(object);
-   }
-   mtx_unlock(_object_list_mtx);
-   /*
 *

Build failed in Jenkins: FreeBSD_stable_10 #347

2016-08-02 Thread jenkins-admin

See 

--
[...truncated 205889 lines...]
ranlib -D libgcc_eh_p.a
--- _negdi2.So ---
--- _lshrdi3.So ---
--- _ashldi3.So ---
--- _ashrdi3.So ---
--- _negdi2.So ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config
 
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc 
-I.  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools
 -std=gnu99 -Qunused-arguments -fpic -DSHARED  -DL_negdi2 -o _negdi2.So 
/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc2.c
--- _lshrdi3.So ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config
 
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc 
-I.  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools
 -std=gnu99 -Qunused-arguments -fpic -DSHARED  -DL_lshrdi3 -o _lshrdi3.So 
/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc2.c
--- _ashldi3.So ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config
 
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc 
-I.  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools
 -std=gnu99 -Qunused-arguments -fpic -DSHARED  -DL_ashldi3 -o _ashldi3.So 
/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc2.c
--- _ashrdi3.So ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config
 
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc 
-I.  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools
 -std=gnu99 -Qunused-arguments -fpic -DSHARED  -DL_ashrdi3 -o _ashrdi3.So 
/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc2.c
--- _cmpdi2.So ---
--- _ucmpdi2.So ---
--- _enable_execute_stack.So ---
--- _cmpdi2.So ---
cc -m32 -march=i686 -mmmx -msse -msse2 -DCOMPAT_32BIT  -isystem 
/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/include/
  
-L/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
  
-B/builds/workspace/FreeBSD_stable_10@2/obj/builds/workspace/FreeBSD_stable_10@2/src/lib32/usr/lib32
 -c -O2 -pipe  -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  
-DHAVE_GTHR_DEFAULT  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcclibs/include
  
-I/builds/workspace/FreeBSD_stable_10@2/src/gnu/lib/libgcc/../../../contrib/gcc/config

Re: 11-BETA3 Panic with ip6+ESP, Fatal trap 12, severe outage

2016-08-02 Thread Harald Schmalzbauer

 Bezüglich Harry Schmalzbauer's Nachricht vom 01.08.2016 08:41 (localtime):
>  Hello,
>
> unfortunately my upgrade from 10.3 to 11-BETA3 caused machine outage.
> ESP encrypted IPv6-traffic acauses a immediate crash.

Andrey V. Elsukov rapidly analysed and corrected that in HEAD with r303657.
This solved my problems on stable/11, as updated here 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211486


Thank you very much!

-Harry



signature.asc
Description: OpenPGP digital signature

Re: mfi driver performance too bad on LSI MegaRAID SAS 9260-8i

2016-08-02 Thread Borja Marcos

> On 01 Aug 2016, at 19:30, Michelle Sullivan  wrote:
> 
> There are reasons for using either…

Indeed, but my decision was to run ZFS. And getting a HBA in some 
configurations can be difficult because vendors insist on using 
RAID adapters. After all, that’s what most of their customers demand.

Fortunately, at least some Avago/LSI cards can work as HBAs pretty well. An 
example is the now venerable LSI2008.

> Nowadays its seems the conversations have degenerated into those like Windows 
> vs Linux vs Mac where everyone thinks their answer is the right one (just as 
> you suggested you (Borja Marcos) did with the Dell salesman), where in 
> reality each has its own advantages and disadvantages.

I know, but this is not the case. But it’s quite frustrating to try to order a 
server with a HBA rather than a RAID and receiving an answer such as
“the HBA option is not available”. That’s why people are zapping, flashing and, 
generally, torturing HBA cards rather cruelly ;)

So, in my case, it’s not about what’s better or worse. It’s just a simpler 
issue. Customer (myself) has made a decision, which can be right or wrong. 
Manufacturer fails to deliver what I need. If it was only one manufacturer, 
well, off with them, but the issue is widespread in industry. 

> Eg: I'm running 2 zfs servers on 'LSI 9260-16i's... big mistake! (the ZFS, 
> not LSI's)... one is a 'movie server' the other a 'postgresql database' 
> server...  The latter most would agree is a bad use of zfs, the die-hards 
> won't but then they don't understand database servers and how they work on 
> disk.  The former has mixed views, some argue that zfs is the only way to 
> ensure the movies will always work, personally I think of all the years 
> before zfs when my data on disk worked without failure until the disks 
> themselves failed... and RAID stopped that happening...  what suddenly 
> changed, are disks and ram suddenly not reliable at transferring data? .. 
> anyhow back to the issue there is another part with this particular hardware 
> that people just throw away…

Well, silent corruption can happen. I’ve seen it once caused by a flaky HBA and 
ZFS saved the cake. Yes. there were reliable replicas. Still, rebuilding would 
be a pain in the ass. 

> The LSI 9260-* controllers have been designed to provide on hardware RAID.  
> The caching whether using the Cachecade SSD or just oneboard ECC memory is 
> *ONLY* used when running some sort of RAID set and LVs... this is why LSI 
> recommend 'MegaCli -CfgEachDskRaid0' because it does enable caching..  A good 
> read on how to setup something similar is here: 
> https://calomel.org/megacli_lsi_commands.html (disclaimer, I haven't parsed 
> it all so the author could be clueless, but it seems to give generally good 
> advice.)  Going the way of 'JBOD' is a bad thing to do, just don't, 
> performance sucks. As for the recommended command above, can't comment 
> because currently I don't use it nor will I need to in the near future... but…

Actually it’s not a good idea to use heavy disk caching when running ZFS. Its 
reliability depends on being able to commit metadata to disk. So I don’t care 
about that caching option. Provided you have enough RAM, ZFS is very effective 
caching data itself.

> If you (O Hartmann) want to use or need to use ZFS with any OS including 
> FreeBSD don't go with the LSI 92xx series controllers, its just the wrong 
> thing to do..  Pick an HBA that is designed to give you direct access to the 
> drives not one you have to kludge and cajole.. Including LSI controllers with 
> caches that use the mfi driver, just not those that are not designed to work 
> in a non RAID mode (with or without the passthru command/mode above.)

As I said, the problem is, sometimes it’s not so easy to find the right HBA. 

> So moral of the story/choices.  Don't go with ZFS because people tell you its 
> best, because it isn't, go with ZFS if it suits your hardware and 
> application, and if ZFS suits your application, get hardware for it.

Indeed, I second this. But really, "hardware for it" covers a rather broad 
cathegory ;) ZFS can even manage to work on hardware _against_ it.

Borja.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Build failed in Jenkins: FreeBSD_stable_10 #349

FYI: amd64 FreeBSD 11.0-BETA3 running under VirtualBox on Mac OS X 10.11.6 : using qemu-system-sparc64 from emulators/qemu-devel in such a FreeBSD results in...

Build failed in Jenkins: FreeBSD_stable_10 #348

Re: Call for testing: VM bugs in 10.3

Re: Call for testing: VM bugs in 10.3

Re: Call for testing: VM bugs in 10.3

Re: Call for testing: VM bugs in 10.3

Call for testing: VM bugs in 10.3

Build failed in Jenkins: FreeBSD_stable_10 #347

Re: 11-BETA3 Panic with ip6+ESP, Fatal trap 12, severe outage

Re: mfi driver performance too bad on LSI MegaRAID SAS 9260-8i

11 matches

Site Navigation

Mail list logo

Footer information