Error in /usr/src/release/release.sh

2017-08-12 Thread Bryce Edwards
When trying to build a set of RELENG/11.1 release files, I'm getting the
following error (tail end of output) in the release.sh run:
--
>>> Kernel build for ALLWINNER completed on Fri Aug 11 22:24:02 UTC 2017
--
make -C /usr/src/release  obj
make -C /usr/src/release  ftp
`ftp' is up to date.
make -C /usr/src/release  release-done
touch release
true
mkdir -p /R
cp -a ftp /R/
cd /R && sha512 FreeBSD-11.1-RELEASE-p1-arm-armv6* > /R/CHECKSUM.SHA512
sha512: FreeBSD-11.1-RELEASE-p1-arm-armv6*: No such file or directory
*** Error code 1

Stop.
make: stopped in /usr/src/release

Here's the contents of my release.conf:
CHROOTDIR="/usr/local/build/chroot"
SRCBRANCH="base/releng/11.1"

TARGET="arm"
TARGET_ARCH="armv6"
KERNEL="ALLWINNER"

NOSRC=yes
NODOC=yes
NOPORTS=yes

And the contents of the R/ directory after the run:
bryce@tahiti /usr/local/build $find chroot/R/
chroot/R/
chroot/R/ftp
chroot/R/ftp/kernel-dbg.txz
chroot/R/ftp/tests.txz
chroot/R/ftp/doc.txz
chroot/R/ftp/base.txz
chroot/R/ftp/MANIFEST
chroot/R/ftp/kernel.txz
chroot/R/ftp/base-dbg.txz
chroot/R/CHECKSUM.SHA512

Thanks in advance for any insight.  I'm not having luck with make
distributeworld in /usr/src either - The use of DESTDIR & DISTDIR in the
Makefiles seem to alternate between absolute & relative use of those and it
isn't cooperating with me (which is why I was trying to just go with
/usr/src/release/release.sh)

Bryce
___
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: ACPI Warning, then hang

2013-06-13 Thread Bryce Edwards
On Mon, Jun 10, 2013 at 9:32 PM, Jeremy Chadwick j...@koitsu.org wrote:
 On Mon, Jun 10, 2013 at 09:18:47PM -0500, Bryce Edwards wrote:
 Verbose boot:

 https://www.dropbox.com/s/obm8rtavro68ea8/acpi-verbose.jpg


 On Mon, Jun 10, 2013 at 11:27 AM, Bryce Edwards br...@bryce.net wrote:
  On Mon, Jun 10, 2013 at 11:19 AM, John Baldwin j...@freebsd.org wrote:
  On Monday, June 10, 2013 10:35:07 am Jeremy Chadwick wrote:
  On Mon, Jun 10, 2013 at 09:18:14AM -0500, Bryce Edwards wrote:
   I'm getting the following warning, and then the system locks:
  
   ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 0x29,
   should be 0x48
  
   Here's a pic: http://db.tt/O6dxONzI
  
   System is on a SuperMicro C7X58 motherboard that I just upgraded to
   BIOS 2.0a, which I would like to stay on if possible.  I tried
   adjusting all the ACPI related BIOS settings without success.
 
  The message in question refers to hard-coded data in one of the many
  ACPI tables (see acpidump(8) for the list -- there are many).  ACPI
  tables are stored within the BIOS -- the motherboard/BIOS vendor has
  full control over all of them and is fully 100% responsible for their
  content.
 
  It looks to me like they severely botched their BIOS, or somehow it got
  flashed wrong.
 
  You need to contact Supermicro Technical Support and tell them of the
  problem.  They need to either fix their BIOS, or help figure out what's
  become corrupted.  You can point them to this thread if you'd like.
 
  I should note that the corruption/issue is major enough that you are
  missing very key/important lines from your dmesg (after avail memory
  but before kdbX at kdbmuxX, which come from pure reliance upon ACPI.
  Lines such as:
 
  Event timer LAPIC quality 400
  ACPI APIC Table: PTLTDAPIC  
  FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
  FreeBSD/SMP: 1 package(s) x 4 core(s)
   cpu0 (BSP): APIC ID:  0
   cpu1 (AP): APIC ID:  1
   cpu2 (AP): APIC ID:  2
   cpu3 (AP): APIC ID:  3
  ioapic0 Version 2.0 irqs 0-23 on motherboard
  ioapic1 Version 2.0 irqs 24-47 on motherboard
 
  In the meantime, you can try booting without ACPI support (there should
  be a boot-up menu option for that) and pray that works.  If it doesn't,
  then your workaround is to roll back to an older BIOS version and/or put
  pressure on Supermicro.  You will find their Technical Support folks are
  quite helpful/responsive to technical issues.
 
  Good luck and keep us posted on what transpires.
 
  Actually, that message is mostly harmless.  All sorts of vendors ship
  tables with busted checksums that are in fact fine. :(  However, the table
  name looks very odd which is more worrying.  Booting without ACPI enabled
  would be a good first step.  Trying a verbose boot to capture the last
  message before the hang would also be useful.
 
  --
  John Baldwin
 
  Booting without ACPI did not work for me, although I might be able to
  hack away at lots of BIOS setting to make it work.  It didn't assign
  IRQ's to things like the storage controller, etc. soI thought it was
  probably not worth the effort.
 
  I did contact SuperMicro support as well, so we'll see what they have to 
  say.
 
  I'll get a verbose boot posted up in a bit.

 A screenshot of a verbose boot is insufficient; as I'm sure you noticed
 there are pages upon pages of information before the lock-up/crash.
 Those pages are what folks are interested in.

 Because the system is hung, I doubt hitting Scroll Lock + using
 PageUp/PageDown to go through the kernel message scrollback will work.

 You're going to need a serial-based console (i.e. hook something up to
 COM1 on the motherboard, and get a null modem cable to connect to
 another system where you use a serial port/terminal emulator (ex. PuTTY
 for Windows, etc.) that has a scrollback buffer which you can copy-paste
 or save.  Set your serial port for 9600 baud, 8 bits, no parity, and 1
 stop bit (9600bps, 8N1).  You'll need to have physical access to both
 systems simultaneously.

 At the VGA console, boot FreeBSD then escape to the loader prompt
 (ok) and issue the following commands:

 set boot_multicons=YES
 set boot_serial=YES
 set console=comconsole,vidconsole
 boot

 You should begin seeing output on the serial port, and the system will
 eventually hang/etc..  Then provide the captured output from the serial
 port here.  :-)

 --
 | Jeremy Chadwick   j...@koitsu.org |
 | UNIX Systems Administratorhttp://jdc.koitsu.org/ |
 | Making life hard for others since 1977. PGP 4BD6C0CB |


I'm having a heck of a time getting the serial console working...

FWIW, I'm getting the following when trying to boot into the most
recent snapshot (memstick) from -current:

https://dl.dropboxusercontent.com/u/141097/acpi-10-boot.jpg

Bryce
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable

Re: ACPI Warning, then hang

2013-06-13 Thread Bryce Edwards
On Thu, Jun 13, 2013 at 5:50 PM, Jeremy Chadwick j...@koitsu.org wrote:
 On Thu, Jun 13, 2013 at 05:32:21PM -0500, Bryce Edwards wrote:
 On Mon, Jun 10, 2013 at 9:32 PM, Jeremy Chadwick j...@koitsu.org wrote:
  On Mon, Jun 10, 2013 at 09:18:47PM -0500, Bryce Edwards wrote:
  Verbose boot:
 
  https://www.dropbox.com/s/obm8rtavro68ea8/acpi-verbose.jpg
 
 
  On Mon, Jun 10, 2013 at 11:27 AM, Bryce Edwards br...@bryce.net wrote:
   On Mon, Jun 10, 2013 at 11:19 AM, John Baldwin j...@freebsd.org wrote:
   On Monday, June 10, 2013 10:35:07 am Jeremy Chadwick wrote:
   On Mon, Jun 10, 2013 at 09:18:14AM -0500, Bryce Edwards wrote:
I'm getting the following warning, and then the system locks:
   
ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 
0x29,
should be 0x48
   
Here's a pic: http://db.tt/O6dxONzI
   
System is on a SuperMicro C7X58 motherboard that I just upgraded to
BIOS 2.0a, which I would like to stay on if possible.  I tried
adjusting all the ACPI related BIOS settings without success.
  
   The message in question refers to hard-coded data in one of the many
   ACPI tables (see acpidump(8) for the list -- there are many).  ACPI
   tables are stored within the BIOS -- the motherboard/BIOS vendor has
   full control over all of them and is fully 100% responsible for their
   content.
  
   It looks to me like they severely botched their BIOS, or somehow it 
   got
   flashed wrong.
  
   You need to contact Supermicro Technical Support and tell them of the
   problem.  They need to either fix their BIOS, or help figure out 
   what's
   become corrupted.  You can point them to this thread if you'd like.
  
   I should note that the corruption/issue is major enough that you are
   missing very key/important lines from your dmesg (after avail memory
   but before kdbX at kdbmuxX, which come from pure reliance upon ACPI.
   Lines such as:
  
   Event timer LAPIC quality 400
   ACPI APIC Table: PTLTDAPIC  
   FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
   FreeBSD/SMP: 1 package(s) x 4 core(s)
cpu0 (BSP): APIC ID:  0
cpu1 (AP): APIC ID:  1
cpu2 (AP): APIC ID:  2
cpu3 (AP): APIC ID:  3
   ioapic0 Version 2.0 irqs 0-23 on motherboard
   ioapic1 Version 2.0 irqs 24-47 on motherboard
  
   In the meantime, you can try booting without ACPI support (there 
   should
   be a boot-up menu option for that) and pray that works.  If it 
   doesn't,
   then your workaround is to roll back to an older BIOS version and/or 
   put
   pressure on Supermicro.  You will find their Technical Support folks 
   are
   quite helpful/responsive to technical issues.
  
   Good luck and keep us posted on what transpires.
  
   Actually, that message is mostly harmless.  All sorts of vendors ship
   tables with busted checksums that are in fact fine. :(  However, the 
   table
   name looks very odd which is more worrying.  Booting without ACPI 
   enabled
   would be a good first step.  Trying a verbose boot to capture the last
   message before the hang would also be useful.
  
   --
   John Baldwin
  
   Booting without ACPI did not work for me, although I might be able to
   hack away at lots of BIOS setting to make it work.  It didn't assign
   IRQ's to things like the storage controller, etc. soI thought it was
   probably not worth the effort.
  
   I did contact SuperMicro support as well, so we'll see what they have 
   to say.
  
   I'll get a verbose boot posted up in a bit.
 
  A screenshot of a verbose boot is insufficient; as I'm sure you noticed
  there are pages upon pages of information before the lock-up/crash.
  Those pages are what folks are interested in.
 
  Because the system is hung, I doubt hitting Scroll Lock + using
  PageUp/PageDown to go through the kernel message scrollback will work.
 
  You're going to need a serial-based console (i.e. hook something up to
  COM1 on the motherboard, and get a null modem cable to connect to
  another system where you use a serial port/terminal emulator (ex. PuTTY
  for Windows, etc.) that has a scrollback buffer which you can copy-paste
  or save.  Set your serial port for 9600 baud, 8 bits, no parity, and 1
  stop bit (9600bps, 8N1).  You'll need to have physical access to both
  systems simultaneously.
 
  At the VGA console, boot FreeBSD then escape to the loader prompt
  (ok) and issue the following commands:
 
  set boot_multicons=YES
  set boot_serial=YES
  set console=comconsole,vidconsole
  boot
 
  You should begin seeing output on the serial port, and the system will
  eventually hang/etc..  Then provide the captured output from the serial
  port here.  :-)
 
  --
  | Jeremy Chadwick   j...@koitsu.org |
  | UNIX Systems Administratorhttp://jdc.koitsu.org/ |
  | Making life hard for others since 1977. PGP 4BD6C0CB |
 

 I'm having a heck of a time getting the serial console working...

 Come to think of it, depending

ACPI Warning, then hang

2013-06-10 Thread Bryce Edwards
I'm getting the following warning, and then the system locks:

ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 0x29,
should be 0x48

Here's a pic: http://db.tt/O6dxONzI

System is on a SuperMicro C7X58 motherboard that I just upgraded to
BIOS 2.0a, which I would like to stay on if possible.  I tried
adjusting all the ACPI related BIOS settings without success.

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


Re: ACPI Warning, then hang

2013-06-10 Thread Bryce Edwards
On Mon, Jun 10, 2013 at 11:19 AM, John Baldwin j...@freebsd.org wrote:
 On Monday, June 10, 2013 10:35:07 am Jeremy Chadwick wrote:
 On Mon, Jun 10, 2013 at 09:18:14AM -0500, Bryce Edwards wrote:
  I'm getting the following warning, and then the system locks:
 
  ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 0x29,
  should be 0x48
 
  Here's a pic: http://db.tt/O6dxONzI
 
  System is on a SuperMicro C7X58 motherboard that I just upgraded to
  BIOS 2.0a, which I would like to stay on if possible.  I tried
  adjusting all the ACPI related BIOS settings without success.

 The message in question refers to hard-coded data in one of the many
 ACPI tables (see acpidump(8) for the list -- there are many).  ACPI
 tables are stored within the BIOS -- the motherboard/BIOS vendor has
 full control over all of them and is fully 100% responsible for their
 content.

 It looks to me like they severely botched their BIOS, or somehow it got
 flashed wrong.

 You need to contact Supermicro Technical Support and tell them of the
 problem.  They need to either fix their BIOS, or help figure out what's
 become corrupted.  You can point them to this thread if you'd like.

 I should note that the corruption/issue is major enough that you are
 missing very key/important lines from your dmesg (after avail memory
 but before kdbX at kdbmuxX, which come from pure reliance upon ACPI.
 Lines such as:

 Event timer LAPIC quality 400
 ACPI APIC Table: PTLTDAPIC  
 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
 FreeBSD/SMP: 1 package(s) x 4 core(s)
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP): APIC ID:  1
  cpu2 (AP): APIC ID:  2
  cpu3 (AP): APIC ID:  3
 ioapic0 Version 2.0 irqs 0-23 on motherboard
 ioapic1 Version 2.0 irqs 24-47 on motherboard

 In the meantime, you can try booting without ACPI support (there should
 be a boot-up menu option for that) and pray that works.  If it doesn't,
 then your workaround is to roll back to an older BIOS version and/or put
 pressure on Supermicro.  You will find their Technical Support folks are
 quite helpful/responsive to technical issues.

 Good luck and keep us posted on what transpires.

 Actually, that message is mostly harmless.  All sorts of vendors ship
 tables with busted checksums that are in fact fine. :(  However, the table
 name looks very odd which is more worrying.  Booting without ACPI enabled
 would be a good first step.  Trying a verbose boot to capture the last
 message before the hang would also be useful.

 --
 John Baldwin

Booting without ACPI did not work for me, although I might be able to
hack away at lots of BIOS setting to make it work.  It didn't assign
IRQ's to things like the storage controller, etc. soI thought it was
probably not worth the effort.

I did contact SuperMicro support as well, so we'll see what they have to say.

I'll get a verbose boot posted up in a bit.

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


Re: ACPI Warning, then hang

2013-06-10 Thread Bryce Edwards
Verbose boot:

https://www.dropbox.com/s/obm8rtavro68ea8/acpi-verbose.jpg


On Mon, Jun 10, 2013 at 11:27 AM, Bryce Edwards br...@bryce.net wrote:
 On Mon, Jun 10, 2013 at 11:19 AM, John Baldwin j...@freebsd.org wrote:
 On Monday, June 10, 2013 10:35:07 am Jeremy Chadwick wrote:
 On Mon, Jun 10, 2013 at 09:18:14AM -0500, Bryce Edwards wrote:
  I'm getting the following warning, and then the system locks:
 
  ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 0x29,
  should be 0x48
 
  Here's a pic: http://db.tt/O6dxONzI
 
  System is on a SuperMicro C7X58 motherboard that I just upgraded to
  BIOS 2.0a, which I would like to stay on if possible.  I tried
  adjusting all the ACPI related BIOS settings without success.

 The message in question refers to hard-coded data in one of the many
 ACPI tables (see acpidump(8) for the list -- there are many).  ACPI
 tables are stored within the BIOS -- the motherboard/BIOS vendor has
 full control over all of them and is fully 100% responsible for their
 content.

 It looks to me like they severely botched their BIOS, or somehow it got
 flashed wrong.

 You need to contact Supermicro Technical Support and tell them of the
 problem.  They need to either fix their BIOS, or help figure out what's
 become corrupted.  You can point them to this thread if you'd like.

 I should note that the corruption/issue is major enough that you are
 missing very key/important lines from your dmesg (after avail memory
 but before kdbX at kdbmuxX, which come from pure reliance upon ACPI.
 Lines such as:

 Event timer LAPIC quality 400
 ACPI APIC Table: PTLTDAPIC  
 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
 FreeBSD/SMP: 1 package(s) x 4 core(s)
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP): APIC ID:  1
  cpu2 (AP): APIC ID:  2
  cpu3 (AP): APIC ID:  3
 ioapic0 Version 2.0 irqs 0-23 on motherboard
 ioapic1 Version 2.0 irqs 24-47 on motherboard

 In the meantime, you can try booting without ACPI support (there should
 be a boot-up menu option for that) and pray that works.  If it doesn't,
 then your workaround is to roll back to an older BIOS version and/or put
 pressure on Supermicro.  You will find their Technical Support folks are
 quite helpful/responsive to technical issues.

 Good luck and keep us posted on what transpires.

 Actually, that message is mostly harmless.  All sorts of vendors ship
 tables with busted checksums that are in fact fine. :(  However, the table
 name looks very odd which is more worrying.  Booting without ACPI enabled
 would be a good first step.  Trying a verbose boot to capture the last
 message before the hang would also be useful.

 --
 John Baldwin

 Booting without ACPI did not work for me, although I might be able to
 hack away at lots of BIOS setting to make it work.  It didn't assign
 IRQ's to things like the storage controller, etc. soI thought it was
 probably not worth the effort.

 I did contact SuperMicro support as well, so we'll see what they have to say.

 I'll get a verbose boot posted up in a bit.

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


Re: 8-STABLE buildworld failure

2010-11-11 Thread Bryce Edwards
On Tue, Nov 9, 2010 at 11:48 PM, Jeremy Chadwick
free...@jdc.parodius.com wrote:
 On Tue, Nov 09, 2010 at 06:09:08PM -0600, Bryce Edwards wrote:
 After updating source today, I am receiving the following error when
 running make NOCCACHE=YES -j16 buildkernel

 Please re-run the buildkernel without any -j or -jXX flags to see where
 the actual error happened.  The below doesn't show the actual error due
 to the nature of the parallel build.

 I doubt this has anything to do with ccache.


Thanks Jeremy, I forgot to disable paralllel builds.  It is very clear
now that it is related to the following in make.conf:

PORTS_MODULES=emulators/virtualbox-ose-kmod

Looks like the path of the make environment for the port doesn't find
yasm (which is indeed installed and located in /usr/local/bin/yasm).

cd ${PORTSDIR:-/usr/ports}/emulators/virtualbox-ose-kmod;
SYSDIR=/usr/src/sys /usr/obj/usr/src/make.amd64/make -B all
===   virtualbox-ose-kmod-3.2.10 depends on executable: yasm - not found
===Verifying install for yasm in /usr/ports/devel/yasm
===  Installing for yasm-1.1.0
===   yasm-1.1.0 depends on shared library: iconv.3 - found
===   yasm-1.1.0 depends on shared library: intl - found
===   Generating temporary packing list
===  Checking if devel/yasm already installed
===   yasm-1.1.0 is already installed
  You may wish to ``make deinstall'' and install this port again
  by ``make reinstall'' to upgrade it properly.
  If you really wish to overwrite the old port of devel/yasm
  without deleting it first, set the variable FORCE_PKG_REGISTER
  in your environment or the make install command line.
*** Error code 1

Stop in /usr/ports/devel/yasm.
*** Error code 1

Stop in /usr/ports/emulators/virtualbox-ose-kmod.
*** Error code 1

Stop in /usr/ports/emulators/virtualbox-ose-kmod.
*** Error code 1

Stop in /usr/obj/usr/src/sys/GENERIC.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.


 === zlib (all)
 cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
 -nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include
 /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
 -finline-limit=8000 --param inline-unit-growth=100 --param
 large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer
 -I/usr/obj/usr/src/sys/GENERIC -mcmodel=kernel -mno-red-zone
 -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow
 -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
 -fstack-protector -std=iso9899:1999 -fstack-protector -Wall
 -Wredundant-decls -Wnested-externs -Wstrict-prototypes
 -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
 -Wno-pointer-sign -fformat-extensions -c
 /usr/src/sys/modules/zlib/../../net/zlib.c
 ld  -d -warn-common -r -d -o zlib.ko.debug zlib.o
 : export_syms
 awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.debug  export_syms |
 xargs -J% objcopy % zlib.ko.debug
 objcopy --only-keep-debug zlib.ko.debug zlib.ko.symbols
 objcopy --strip-debug --add-gnu-debuglink=zlib.ko.symbols zlib.ko.debug 
 zlib.ko
 1 error
 *** Error code 2
 1 error
 *** Error code 2

 --
 | Jeremy Chadwick                                   j...@parodius.com |
 | Parodius Networking                       http://www.parodius.com/ |
 | UNIX Systems Administrator                  Mountain View, CA, USA |
 | Making life hard for others since 1977.              PGP: 4BD6C0CB |


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


8-STABLE buildworld failure

2010-11-09 Thread Bryce Edwards
After updating source today, I am receiving the following error when
running make NOCCACHE=YES -j16 buildkernel


=== zlib (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
-nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
-finline-limit=8000 --param inline-unit-growth=100 --param
large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer
-I/usr/obj/usr/src/sys/GENERIC -mcmodel=kernel -mno-red-zone
-mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow
-msoft-float -fno-asynchronous-unwind-tables -ffreestanding
-fstack-protector -std=iso9899:1999 -fstack-protector -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions -c
/usr/src/sys/modules/zlib/../../net/zlib.c
ld  -d -warn-common -r -d -o zlib.ko.debug zlib.o
: export_syms
awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.debug  export_syms |
xargs -J% objcopy % zlib.ko.debug
objcopy --only-keep-debug zlib.ko.debug zlib.ko.symbols
objcopy --strip-debug --add-gnu-debuglink=zlib.ko.symbols zlib.ko.debug zlib.ko
1 error
*** Error code 2
1 error
*** Error code 2

Here's make.conf:

SUP_UPDATE=yes
SUPFILE=/usr/share/examples/cvsup/stable-supfile
PORTSSUPFILE=/usr/share/examples/cvsup/ports-supfile
SUPHOST=cvsup5.us.freebsd.org

#WITHOUT_X11=yes

PORTS_MODULES=emulators/virtualbox-ose-kmod

# ccache
.if (!empty(.CURDIR:M/usr/src*) || !empty(.CURDIR:M/usr/obj*)) 
!defined(NOCCACHE)
#CC=/usr/local/libexec/ccache/world-cc
#CXX=/usr/local/libexec/ccache/world-c++
.endif

# added by use.perl 2010-11-09 09:32:27
PERL_VERSION=5.10.1

And src.conf:

WITHOUT_PROFILE=true# Avoid compiling profiled libraries
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org


Re: 8-STABLE buildworld failure

2010-11-09 Thread Bryce Edwards
On Tue, Nov 9, 2010 at 11:04 PM, jhell jh...@dataix.net wrote:
 On 11/09/2010 19:09, Bryce Edwards wrote:
 After updating source today, I am receiving the following error when
 running make NOCCACHE=YES -j16 buildkernel


 === zlib (all)
 cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
 -nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include
 /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
 -finline-limit=8000 --param inline-unit-growth=100 --param
 large-function-growth=1000 -fno-common -g -fno-omit-frame-pointer
 -I/usr/obj/usr/src/sys/GENERIC -mcmodel=kernel -mno-red-zone
 -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow
 -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
 -fstack-protector -std=iso9899:1999 -fstack-protector -Wall
 -Wredundant-decls -Wnested-externs -Wstrict-prototypes
 -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
 -Wno-pointer-sign -fformat-extensions -c
 /usr/src/sys/modules/zlib/../../net/zlib.c
 ld  -d -warn-common -r -d -o zlib.ko.debug zlib.o
 : export_syms
 awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.debug  export_syms |
 xargs -J% objcopy % zlib.ko.debug
 objcopy --only-keep-debug zlib.ko.debug zlib.ko.symbols
 objcopy --strip-debug --add-gnu-debuglink=zlib.ko.symbols zlib.ko.debug 
 zlib.ko
 1 error
 *** Error code 2
 1 error
 *** Error code 2

 Here's make.conf:

 SUP_UPDATE=yes
 SUPFILE=/usr/share/examples/cvsup/stable-supfile
 PORTSSUPFILE=/usr/share/examples/cvsup/ports-supfile
 SUPHOST=cvsup5.us.freebsd.org

 #WITHOUT_X11=yes

 PORTS_MODULES=emulators/virtualbox-ose-kmod

 # ccache
 .if (!empty(.CURDIR:M/usr/src*) || !empty(.CURDIR:M/usr/obj*)) 
 !defined(NOCCACHE)
 #CC=/usr/local/libexec/ccache/world-cc
 #CXX=/usr/local/libexec/ccache/world-c++
 .endif

 # added by use.perl 2010-11-09 09:32:27
 PERL_VERSION=5.10.1

 And src.conf:

 WITHOUT_PROFILE=true    # Avoid compiling profiled libraries

 This is a log from a buildkernel and not like the subject insists as a
 buildworld. Can you please rebuild world and then try a buildkernel

 cd /usr/src
 make -DNOCCACHE -DALWAYS_CHECK_MAKE buildworld
 make -DNOCCACHE -DALWAYS_CHECK_MAKE buildkernel
 make -DNOCCACHE -DALWAYS_CHECK_MAKE installkernel

 Reboot  then:
 cd /usr/src
 make -DNOCCACHE installworld
 make -DNOCCACHE delete-old
 make -DNOCCACHE delete-old-libs


My apologies!  The subject is wrong and it was during the buildkernel.
 The buildworld was done just prior just like your example and
completed OK.  The only difference is that I did not define
ALWAYS_CHECK_MAKE.


 You may also want to adjust that example ccache make.conf example
 sometime too as that will not always do what you expect it to do.

 --

  jhell,v

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


SuperMicro i7 (UP) - very slow performance

2010-09-18 Thread Bryce Edwards
I have a Supermicro with the C7X58 motherboard and an i7 930 cpu, and
it is nowhere near the performance it should be.  A buildworld just
took 22.5 hours!

br...@tahiti[~]uname -a
FreeBSD tahiti.bryce.net 8.1-STABLE FreeBSD 8.1-STABLE #0: Tue Sep  7
22:45:38 CDT 2010
r...@tahiti.bryce.net:/usr/obj/usr/src/sys/GENERIC  amd64

I have disabled Legacy USB Support in the BIOS and that helped, but
I'm not finding any other setting that are getting things where they
need to be.

I have tested the two system drives independently (currently a zfs
mirror), so it is not likely to be an hdd issue.

Here's the verbose dmesg boot details - http://www.bryce.net/files/dmesg.boot

And, the IPMI ASL in case that is of any value -
http://www.bryce.net/files/tahiti.asl

Currently, I'm not running powerd, performance is not better with it running.

r...@tahiti[/usr/src]#cat /boot/loader.conf
ahci_load=YES
coretemp_load=YES

zfs_load=YES
vfs.root.mountfrom=zfs:system
#vfs.zfs.prefetch_disable=1

kern.maxfiles=16384

# async i/o
aio_load=YES

# VirtualBox
#vboxdrv_load=YES

# SMB
#ichsmb_load=YES
#smb_load=YES

# Power Saving
#kern.hz=100

# Disable APIC subsystem - no longer needed when disabling lapic below
#hint.apic.0.disabled=1

# Disable local APIC (LAPIC) timer - for C3 state
#hint.apic.0.clock=0

# Avoid 128 interrupts/sec per core, at cost of scheduling precision
#hint.atrtc.0.clock=0

# Disable throttle control (and rely on EIST)
hint.p4tcc.0.disabled=1
hint.acpi_throttle.0.disabled=1

Thanks in advance for your time!

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


Re: 8-STABLE performance issues on Supermicro Core i7

2010-05-03 Thread Bryce Edwards
I have tried both drives independently (two system drives currently
in ZFS mirror), but the interrupts was something that caught my
attention as well.  I haven't yet tried polling yet on the em
interface, but I still have interrupts like what you are seeing (minus
the em ones) when I'm just compiling and not really using the network,
so I was going to wait before going down that path.

Bryce

On Sun, May 2, 2010 at 11:20 PM, Adam Vande More amvandem...@gmail.com wrote:
 On Sun, May 2, 2010 at 9:40 PM, Bryce Edwards br...@bryce.net wrote:

 Hello,

 I've got a new Supermicro X58 system with an Intel Core i7 930 with 6
 GB ram that is not performing nearly as fast as it should in many ways
 (compiling, network transfers).  To give an example, it has been
 building the gcc44 port for about 10 hours now and at the same time
 rsync'ing from a Linux box on the same Gigabit network is only getting
 throughput of between 10-25 MB/sec.  When I did a buildkernel for
 8-STABLE, it took 17 hours!  My investigations have shown inhibited
 performance on compute, network and storage activities.


 Have you investigated potential faulty HD?  I have an i7 870 and your ahci
 interrupts are an order of magintude greater than mine.  That could be many
 other things too, but I think a SMART scan could help.

 --
 Adam Vande More

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


8-STABLE performance issues on Supermicro Core i7

2010-05-02 Thread Bryce Edwards
Hello,

I've got a new Supermicro X58 system with an Intel Core i7 930 with 6
GB ram that is not performing nearly as fast as it should in many ways
(compiling, network transfers).  To give an example, it has been
building the gcc44 port for about 10 hours now and at the same time
rsync'ing from a Linux box on the same Gigabit network is only getting
throughput of between 10-25 MB/sec.  When I did a buildkernel for
8-STABLE, it took 17 hours!  My investigations have shown inhibited
performance on compute, network and storage activities.

In the BIOS, I have played with a few settings and some actually made
it worse.  What I have done now is disabled Hyperthreading and Turbo
Boost.

Thanks in advance for any ideas.  Here's some system info and stats:

br...@tahiti[~]uname -a
FreeBSD tahiti.bryce.net 8.0-STABLE FreeBSD 8.0-STABLE #0: Wed Apr 28
10:53:37 CDT 2010
r...@tahiti.bryce.net:/usr/obj/usr/src/sys/GENERIC  amd64


br...@tahiti[~]cat /boot/loader.conf
ahci_load=YES
ichsmb_load=YES
smb_load=YES
coretemp_load=YES

zfs_load=YES
vfs.root.mountfrom=zfs:system

hint.p4tcc.0.disabled=1
hint.acpi_throttle.0.disabled=1


br...@tahiti[~]cat /etc/sysctl.conf
kern.timecounter.hardware=HPET


br...@tahiti[~]vmstat 1
 procs      memory      page                    disks     faults         cpu
 r b w     avm    fre   flt  re  pi  po    fr  sr ad0 ad1   in   sy
cs us sy id
 5 0 0   1068M  3478M   572   1   1   0   862   0   0   0 9370 16514
16157 71 22  7
 5 0 0   1068M  3478M     2   0   0   0     0   0   0   0 8008 14504
11716 81 17  2
 5 0 0   1068M  3478M     0   0   0   0     0   0   0   0 12429 22323
18125 77 23  0
 5 0 0   1068M  3478M     0   0   0   0     0   0   0   0 12348 22125
17988 73 27  0


br...@tahiti[~]vmstat -i
interrupt                          total       rate
irq1: atkbd0                        9291          0
irq17: fwohci0                         1          0
cpu0: timer                     75416246       2000
irq256: em0                    137590284       3649
irq257: em0                    206367605       5473
irq260: em0                            1          0
irq266: ahci0                    9892384        262
cpu2: timer                     75415653       2000
cpu3: timer                     75415702       2000
cpu1: timer                     75415561       2000
Total                          655522728      17385


br...@tahiti[~]netstat -I em0 -h 1
           input          (em0)           output
  packets  errs idrops      bytes    packets  errs      bytes colls
     7.7K     0     0        11M       7.2K     0       475K     0
     8.1K     0     0        12M       7.4K     0       491K     0
     7.8K     0     0        11M       7.2K     0       476K     0

br...@tahiti[/usr/adm]iostat 1
      tty            ada0             ada1             ada2             cpu
 tin  tout  KB/t tps  MB/s   KB/t tps  MB/s   KB/t tps  MB/s  us ni sy in id
  0   108 22.35   3  0.07  20.61   3  0.07  58.60   0  0.00  71  0  4 17  7
  0   222 64.00   1  0.06  128.00   1  0.12   0.00   0  0.00  87  0  2 11  0


Dmesg output:

Copyright (c) 1992-2010 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 8.0-STABLE #0: Wed Apr 28 10:53:37 CDT 2010
r...@tahiti.bryce.net:/usr/obj/usr/src/sys/GENERIC amd64
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM) i7 CPU 930  @ 2.80GHz (2786.02-MHz K8-class CPU)
  Origin = GenuineIntel  Id = 0x106a5  Family = 6  Model = 1a  Stepping = 5
  
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=0x98e3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
  AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM
  AMD Features2=0x1LAHF
  TSC: P-state invariant
real memory  = 6446645248 (6148 MB)
avail memory = 6169243648 (5883 MB)
ACPI APIC Table: 021210 APIC1519
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  2
 cpu2 (AP): APIC ID:  4
 cpu3 (AP): APIC ID:  6
ioapic0: Changing APIC ID to 1
ioapic0 Version 2.0 irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: SMCI  on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a (3) failed
acpi0: reservation of 10, cbf0 (3) failed
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0
cpu0: ACPI CPU on acpi0
ACPI Warning: Incorrect checksum in table [OEMB] - 0x7B, should be
0x74 (20100331/tbutils-354)
cpu1: ACPI CPU on acpi0
cpu2: ACPI CPU on acpi0
cpu3: ACPI CPU on acpi0
acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0
Timecounter HPET frequency 14318180 Hz quality 900
pcib0: ACPI