Re: Complete hang on 9.0-RELEASE
Hi, On Mon, Apr 16, 2012 at 5:50 PM, Arnaud Lacombe lacom...@gmail.com wrote: Hi, [for the record...] On Tue, Feb 14, 2012 at 11:41 AM, Arnaud Lacombe lacom...@gmail.com wrote: Hi folks, For the records, I was running some tests yesterday on top of a 9.0-RELEASE, amd64, kernel when the box hanged. At the time of the hang, the box was running a process with about 2800 threads with heavy IPC between 1400 writers and 1400 readers. The box was in single user mode (/bin/sh coming from FreeBSD 7.4-STABLE). Here is the beginning of the dmesg: Copyright (c) 1992-2012 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 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 CPU: Intel(R) Atom(TM) CPU D510 @ 1.66GHz (1666.70-MHz K8-class CPU) Origin = GenuineIntel Id = 0x106ca Family = 6 Model = 1c Stepping = 10 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=0x40e31dSSE3,DTES64,MON,DS_CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE AMD Features=0x2800SYSCALL,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 2137587712 (2038 MB) avail memory = 2037841920 (1943 MB) Event timer LAPIC quality 400 ACPI APIC Table: 070611 APIC1125 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP/HT): APIC ID: 3 I will restart the test and see if this happens again. I reproduced the previous problem on 10-CURRENT from r233917, on the following platform (here running 8.2-RELEASE): FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Atom(TM) CPU D525 @ 1.80GHz (1800.01-MHz K8-class CPU) Origin = GenuineIntel Id = 0x106ca Family = 6 Model = 1c Stepping = 10 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=0x40e31dSSE3,DTES64,MON,DS_CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 2136539136 (2037 MB) avail memory = 2043772928 (1949 MB) ACPI APIC Table: 010312 APIC0947 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP/HT): APIC ID: 3 Complete system freeze while running about 2400 threads. I had to power cycle the system to get it back alive. I discussed a way to debug this with attilio@ on freebsd-stable@, but still did not had time to implement it. 10-CURRENT from r233917 hanged again today while running 3600 threads. I enabled WITNESS and INVARIANTS on that specific kernel, secretly hoping that they would trigger some meaningful information, but they did not. I would guess my last attempt is to enable SW_WATCHDOG, and gather some state information out of DDB when the watchdog trigger, if it does... Btw, this issue seems to be specifically happening on Atom/ICH8M platform running amd64 kernel, as I've never seen it on other platforms, and yet ran extensive tests. I am not entirely sure it happens on i386. I would need to check. - Arnaud ___ 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: FreeBSD 8.3-R sysinstall does not see disks that are recognized during boot
On 17/04/2012 23:02, Andy Dills wrote: However, once the system finishes booting and loads into sysinstall, and I go to partition the drives, I get No disks found! Please verify that your disk controller is being properly loaded at boot time. If you boot into 'Live CD' rather than the installer, can you still see the drives in /dev ? If so, you should be able to go ahead and install the system manually -- it takes a little knowledge of some of the low level management commands, but it isn't particularly difficult. If you wanted to use ZFS for instance, you'ld have to do a manual install anyhow, and there are many recipes around the web. If the drives appear in the dmesg output and then disappear that's a whole different kettle of fish. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: FreeBSD 8.3-R sysinstall does not see disks that are recognized during boot
On 18/04/2012, at 7:32, Andy Dills wrote: I've got a new supermicro server I'm trying to get FreeBSD on. It uses the Intel c602 chipset, and it's my understanding that support for that chipset (c60X) was recently added via the isci driver. Ok, great, that explains why 8.2-R and 9.0-R didn't see the drives. So, I grabbed the memstick image of 8.3-RELEASE that is on the ftp server, booted it up, and sure enough, as the dmesg scrolls I see it now properly recognizes da0 and da1, as it should (the memstick is da2). It sees the disks fine at this point, everything looks good. However, once the system finishes booting and loads into sysinstall, and I go to partition the drives, I get No disks found! Please verify that your disk controller is being properly loaded at boot time. Any suggestions for avenues to troubleshoot this? I have pictures to document if it helps. Seems very odd. I confirmed the behavior with the SATA set to IDE, AHCI, and RAID modes. (The drives were recognized as da0 and da1 during bootup in all three modes, but not by sysinstall.) That does seem very odd - if they appear as daX then sysinstall should see them. Can you go into the holographic shell (or livecd if you have it) and run.. echo /dev/da* echo /dev/da0 echo /dev/da1 (this will trash the first sector of da0 and da1 but I assume that's OK since you're installing on those). If you could obtain a KLD for isci built for 9.0 you could load it in the loader and see if that installer sees it, you might not have the facilities for that though.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ 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
pcre-related problem to compile HipHop in FreeBSD9-RELEASE
Hi:
I am having problem while trying to compile HipHop similar to what has
been discussed here
(https://github.com/facebook/hiphop-php/issues/480#pull_comment_form)
My environments are:
setenv CC /usr/local/bin/gcc44
setenv CXX /usr/local/bin/g++44
setenv HPHP_HOME `pwd`
setenv HPHP_LIB `pwd`/bin
setenv CMAKE_PREFIX_PATH `pwd`/../libs
and I got the following pcre-related errors, when checked the lines
specified in the error it seems to be associated with pcre flushing
cache. Summary of error is:
[ 15%] Building CXX object
src/CMakeFiles/hphp_runtime_static.dir/runtime/base/preg.cpp.o
/root/hhbuild/hiphop-php/src/runtime/base/preg.cpp: In function
'HPHP::pcre_cache_entry* HPHP::pcre_get_compiled_regex_cache(const
HPHP::String)':
/root/hhbuild/hiphop-php/src/runtime/base/preg.cpp:138: error:
'pcre_info' was not declared in this scope
*** Error code 1
I checked the specific line 138 which reads like:
if (pcre_info(pce-re, NULL, NULL) == PCRE_ERROR_BADMAGIC) {
pcre_cache.cleanup();
Any hints? Could not figure out whether it is FreeBSD9-, pcre- or
HipHop-related?
Thanks!
/z
The entire make output is as of below:
# make
Scanning dependencies of target xhp
[ 0%] Building CXX object
src/third_party/xhp/xhp/CMakeFiles/xhp.dir/code_rope.cpp.o
[ 0%] Building CXX object
src/third_party/xhp/xhp/CMakeFiles/xhp.dir/xhp_preprocess.cpp.o
[ 0%] Building CXX object
src/third_party/xhp/xhp/CMakeFiles/xhp.dir/xhpize.cpp.o
[ 0%] Building CXX object
src/third_party/xhp/xhp/CMakeFiles/xhp.dir/fastpath.cpp.o
[ 0%] Building CXX object
src/third_party/xhp/xhp/CMakeFiles/xhp.dir/parser.yacc.cpp.o
[ 1%] Building CXX object
src/third_party/xhp/xhp/CMakeFiles/xhp.dir/scanner.lex.cpp.o
scanner.lex.cpp: In function 'yy_state_type
yy_try_NUL_trans(yy_state_type, void*)':
scanner.lex.cpp:9714: warning: unused variable 'yyg'
Linking CXX static library ../../../../bin/libxhp.a
[ 1%] Built target xhp
Scanning dependencies of target afdt
[ 1%] Building C object
src/third_party/libafdt/CMakeFiles/afdt.dir/src/lowlevel.c.o
[ 1%] Building C object
src/third_party/libafdt/CMakeFiles/afdt.dir/src/strlcpy.c.o
[ 1%] Building C object
src/third_party/libafdt/CMakeFiles/afdt.dir/src/sync.c.o
[ 1%] Building C object
src/third_party/libafdt/CMakeFiles/afdt.dir/src/util.c.o
[ 1%] Building C object
src/third_party/libafdt/CMakeFiles/afdt.dir/src/async.c.o
Linking C static library ../../../bin/libafdt.a
[ 1%] Built target afdt
Scanning dependencies of target mbfl
[ 2%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/mbfilter.c.o
[ 2%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/mbfl_string.c.o
[ 2%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/mbfl_language.c.o
[ 2%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/mbfl_encoding.c.o
[ 2%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/mbfl_convert.c.o
[ 2%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/mbfl_ident.c.o
[ 2%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/mbfl_memory_device.c.o
[ 3%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/mbfl_allocators.c.o
[ 3%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/mbfl_filter_output.c.o
[ 3%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/mbfilter_pass.c.o
[ 3%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/mbfilter_wchar.c.o
[ 3%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/mbfilter_8bit.c.o
[ 3%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_cp936.c.o
[ 3%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_hz.c.o
[ 4%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_euc_tw.c.o
[ 4%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_big5.c.o
[ 4%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_euc_jp.c.o
[ 4%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_jis.c.o
[ 4%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_iso8859_1.c.o
[ 4%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_iso8859_2.c.o
[ 4%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_cp1254.c.o
[ 5%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_cp1252.c.o
[ 5%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_cp1251.c.o
[ 5%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_ascii.c.o
[ 5%] Building C object
src/third_party/libmbfl/mbfl/CMakeFiles/mbfl.dir/__/filters/mbfilter_iso8859_3.c.o
[ 5%] Building C object
Re: kernel panic while detecting cpu in FreeBSD 9
On Wed, Apr 18, 2012 at 12:24:17AM -0400, Chad C wrote: Updated the mainboard UEFI to latest version but am still getting the same kernel page fault. I compiled options DDB and options GDB into the generic kernel. After rebooting and entering DDB I get the following from various commands: On bootup I am now getting the following: real memory = 8589934592 (8192 MB) avail memory = 8198332416 (7818 MB) Event timer LAPIC quality 600 ACPI APIC Table: ALASKA A M I panic: AP #2 (PHY# 4) failed! cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at KDB_backtrace+0x37 panic() at panic+0x187 cpu_mp_start() at cpu_mp_start+0x589 mp_start() at mp_start+0x85 mi_startup() at mi_startup+0x77 btext() at btext+0x2c KDB: enter: panic [ thread pid 0 tid 0 ] Stopped atkdb_enter+0x3b: movq$0,0x905dc2(%rip) db So your other core failed to start. You might try a lack posting exact model/bios version of the machine and mainboard. But indeed, this is most often BIOS bugs. Sometimes in the strange areas like USB, e.g. SMI handler for emulating legacy PS/2 keyboard. As a shot in the dark, try to fiddle with this setting. pgpkNyhmBXRh6.pgp Description: PGP signature
RE: FreeBSD 8.3-R sysinstall does not see disks that are recognized during boot
-- Forwarded message -- Date: Tue, 17 Apr 2012 18:02:31 -0400 (EDT) From: Andy Dills a...@xecu.net To: freebsd-stable@freebsd.org Subject: FreeBSD 8.3-R sysinstall does not see disks that are recognized during boot I've got a new supermicro server I'm trying to get FreeBSD on. It uses the Intel c602 chipset, and it's my understanding that support for that chipset (c60X) was recently added via the isci driver. Ok, great, that explains why 8.2-R and 9.0-R didn't see the drives. So, I grabbed the memstick image of 8.3-RELEASE that is on the ftp server, booted it up, and sure enough, as the dmesg scrolls I see it now properly recognizes da0 and da1, as it should (the memstick is da2). It sees the disks fine at this point, everything looks good. However, once the system finishes booting and loads into sysinstall, and I go to partition the drives, I get No disks found! Please verify that your disk controller is being properly loaded at boot time. Any suggestions for avenues to troubleshoot this? I have pictures to document if it helps. Seems very odd. I confirmed the behavior with the SATA set to IDE, AHCI, and RAID modes. (The drives were recognized as da0 and da1 during bootup in all three modes, but not by sysinstall.) Andy and I worked this out offline - workaround was to go to Options|Re-scan which caused the devices to show up in the sysinstall menu. I'm adding details here for future reference. 1) C60x chipsets have the 6 traditional SATA ports, plus 4 or 8 SAS ports. Only the latter are controlled by the isci(4) driver. 2) The IDE/AHCI/RAID modes apply only to the traditional SATA ports. 3) In Andy's case, going to Options|Re-scan Devices caused the disks to show up. This problem seems to be system or platform-dependent, as I was not able to reproduce with 8.3 memstick image on my C600 systems. 4) There was a problem with initial device scan using isci(4) on 7-STABLE, which necessitated r233371. This was MFC'd back to 8-STABLE, but after 8.3 was released. I'm fairly convinced this is the root cause of Andy's problem, but don't have any easy way to verify. Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 --- ___ 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: FreeBSD 8.3-R sysinstall does not see disks that are recognized during boot
On Wed, 18 Apr 2012, Harris, James R wrote: Andy and I worked this out offline - workaround was to go to Options|Re-scan which caused the devices to show up in the sysinstall menu. I'm adding details here for future reference. 1) C60x chipsets have the 6 traditional SATA ports, plus 4 or 8 SAS ports. Only the latter are controlled by the isci(4) driver. 2) The IDE/AHCI/RAID modes apply only to the traditional SATA ports. 3) In Andy's case, going to Options|Re-scan Devices caused the disks to show up. This problem seems to be system or platform-dependent, as I was not able to reproduce with 8.3 memstick image on my C600 systems. 4) There was a problem with initial device scan using isci(4) on 7-STABLE, which necessitated r233371. This was MFC'd back to 8-STABLE, but after 8.3 was released. I'm fairly convinced this is the root cause of Andy's problem, but don't have any easy way to verify. First, I want to thank James and the other responders for help getting me squared away. Something that may be of specific use for others (James has covered the most relevant points...at blazing speed, what an asset to the community), is that the isci support in 8.3-R will now enable FreeBSD compatibility with most of the new Supermicro server platforms. And a new lesson was learnedfirst thing to try when sysinstall fails to recognize hardware is to re-scan devices. Never needed that across thousands of installs (dating to 2.2.8), and didn't even know it existed. Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 --- ___ 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
[releng_9 tinderbox] failure on ia64/ia64
TB --- 2012-04-18 18:44:01 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-04-18 18:44:01 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-04-18 18:44:01 - starting RELENG_9 tinderbox run for ia64/ia64 TB --- 2012-04-18 18:44:01 - cleaning the object tree TB --- 2012-04-18 18:44:01 - cvsupping the source tree TB --- 2012-04-18 18:44:01 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_9/ia64/ia64/supfile TB --- 2012-04-18 18:45:14 - building world TB --- 2012-04-18 18:45:14 - CROSS_BUILD_TESTING=YES TB --- 2012-04-18 18:45:14 - MAKEOBJDIRPREFIX=/obj TB --- 2012-04-18 18:45:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-04-18 18:45:14 - SRCCONF=/dev/null TB --- 2012-04-18 18:45:14 - TARGET=ia64 TB --- 2012-04-18 18:45:14 - TARGET_ARCH=ia64 TB --- 2012-04-18 18:45:14 - TZ=UTC TB --- 2012-04-18 18:45:14 - __MAKE_CONF=/dev/null TB --- 2012-04-18 18:45:14 - cd /src TB --- 2012-04-18 18:45:14 - /usr/bin/make -B buildworld World build started on Wed Apr 18 18:45:15 UTC 2012 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] gzip -cn /src/usr.sbin/mergemaster/mergemaster.8 mergemaster.8.gz === usr.sbin/mfiutil (all) cc -O2 -pipe -fno-builtin-strftime -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/mfiutil/mfiutil.c cc -O2 -pipe -fno-builtin-strftime -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/mfiutil/mfi_cmd.c cc -O2 -pipe -fno-builtin-strftime -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/mfiutil/mfi_config.c cc1: warnings being treated as errors /src/usr.sbin/mfiutil/mfi_config.c: In function 'parse_array': /src/usr.sbin/mfiutil/mfi_config.c:307: warning: comparison is always true due to limited range of data type *** Error code 1 Stop in /src/usr.sbin/mfiutil. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-04-18 20:26:53 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-04-18 20:26:53 - ERROR: failed to build world TB --- 2012-04-18 20:26:53 - 4069.87 user 649.61 system 6172.87 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-ia64-ia64.full ___ 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
