Re: mfi(4) IO performance regression, post 8.1
On 7/13/12 9:39 AM, John Baldwin wrote:
On Thursday, July 12, 2012 11:47:28 pm Steve McCoy wrote:
On 7/12/12 4:34 PM, Steve McCoy wrote:
John Baldwin wrote:
Barring that, can you do a binary search of kernels from stable/8
between 8.1
and 8.2 on an 8.1 world to see which commit caused the change in write
performance?
Hi John, I'm working with Charles to narrow this down.
Looks like revision 212229 is the culprit, or at least around the same
time to it, if this change isn't what slowed things down. The change to
sys/kern/vfs_bio.c modifies some synchronization in dev_strategy():
Actually, hold that thought. I had a hunch that I wasn't thorough
enough, so I decided to try 212228 — the performance is the same as with
212229, so vfs_bio seems to be out of the picture. I'm going to binary
search between 209459 and 212229, and see what I find.
Ok. Please let me know what you find. Thanks!
Alright, I've finally narrowed it down to r209897, which only affects
acpi_cpu_idle():
--- stable/8/sys/dev/acpica/acpi_cpu.c 2010/06/23 17:04:42 209471
+++ stable/8/sys/dev/acpica/acpi_cpu.c 2010/07/11 11:58:46 209897
@@ -930,12 +930,16 @@
/*
* Execute HLT (or equivalent) and wait for an interrupt. We can't
- * calculate the time spent in C1 since the place we wake up is an
- * ISR. Assume we slept half of quantum and return.
+ * precisely calculate the time spent in C1 since the place we wake up
+ * is an ISR. Assume we slept no more then half of quantum.
*/
if (cx_next-type == ACPI_STATE_C1) {
- sc-cpu_prev_sleep = (sc-cpu_prev_sleep * 3 + 50 / hz) / 4;
+ AcpiHwRead(start_time, AcpiGbl_FADT.XPmTimerBlock);
acpi_cpu_c1();
+ AcpiHwRead(end_time, AcpiGbl_FADT.XPmTimerBlock);
+end_time = acpi_TimerDelta(end_time, start_time);
+ sc-cpu_prev_sleep = (sc-cpu_prev_sleep * 3 +
+ min(PM_USEC(end_time), 50 / hz)) / 4;
return;
}
My current guess is that AcpiHwRead() is a problem on our hardware. It's
an isolated change and, to my desperate eyes, the commit message implies
that it isn't critical — Do you think we could buy ourselves some time
by pulling it out of our version of the kernel? Or is this essential for
correctness? Any thoughts are appreciated, thanks!
___
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: Why not provide libclang.so in base?
On 2012-07-18 14:54, Yanhui Shen wrote: I'm using clang-complete plugin in vim, it claims with libclang.so instead of bin/clang it works better. However libclang.so is not installed by a default make buildworld make installworld, even with 'WITH_CLANG_EXTRAS=YES' in src.conf. This is because it would add quite a lot of build overhead to produce that .so file: all the object files will need to be recompiled yet again for shared library support. That said, we will probably want to provide at least a shared LLVM lib in the future, since it can be re-used by other programs. When that happens, it would not be too much extra work to provide a shared Clang library. I have to install lang/clang *again* from ports to acquire the libclang.so. Most of the time, people will not need this functionality in base, which is why it is in a port. The same applies if you want the latest version, or if you want to build with any specialized options. So why not provide libclang.so in base directly? I think if it's not a general component, provide a flag something like WITH_LIBCLANG=YES is also fine. It needs to be figured out properly, which costs time and effort. Both of which are currently in short supply, at least for me... :-/ ___ 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
Thinkpad X61s cannot boot 9.1-BETA1
Hi, Did anyone else experience this? With 9.1-BETA1 the boot process freezes, among the last lines with verbose boot are acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times after this, dead. What is supposed to happen in the next stage? This laptop worked fine with 9-STABLE to at least february. //per ___ 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
Job Targeting
How it works? We have a team of resourcers. You post your contract job. Our in house resourcers find matching candidates on our 600,000 strong contractor database for your live role. We send your live job to the top 100-200 matching candidates. You receive only the highest quality applications. We are so confident in this new product that we are offering a 1st month money back guarantee. Call 0203 535 7930 or click here to arrange a free no obligation demonstration http://emarketing.emailjunkies.co.uk/private/jcO4/mVI/o49v7ZE/unsubscribe/16656593 ___ 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_8 tinderbox] failure on mips/mips
TB --- 2012-07-19 12:50:51 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-07-19 12:50:51 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE 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 TB --- 2012-07-19 12:50:51 - starting RELENG_8 tinderbox run for mips/mips TB --- 2012-07-19 12:50:51 - cleaning the object tree TB --- 2012-07-19 12:50:51 - cvsupping the source tree TB --- 2012-07-19 12:50:51 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/mips/mips/supfile TB --- 2012-07-19 12:51:06 - building world TB --- 2012-07-19 12:51:06 - CROSS_BUILD_TESTING=YES TB --- 2012-07-19 12:51:06 - MAKEOBJDIRPREFIX=/obj TB --- 2012-07-19 12:51:06 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-07-19 12:51:06 - SRCCONF=/dev/null TB --- 2012-07-19 12:51:06 - TARGET=mips TB --- 2012-07-19 12:51:06 - TARGET_ARCH=mips TB --- 2012-07-19 12:51:06 - TZ=UTC TB --- 2012-07-19 12:51:06 - __MAKE_CONF=/dev/null TB --- 2012-07-19 12:51:06 - cd /src TB --- 2012-07-19 12:51:06 - /usr/bin/make -B buildworld World build started on Thu Jul 19 12:51:06 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 [...] /src/usr.sbin/flowctl/flowctl.c: At top level: /src/usr.sbin/flowctl/flowctl.c:234: warning: 'struct ngnf_flows' declared inside parameter list /src/usr.sbin/flowctl/flowctl.c:235: error: conflicting types for 'flow_cache_print_verbose' /src/usr.sbin/flowctl/flowctl.c:64: error: previous declaration of 'flow_cache_print_verbose' was here /src/usr.sbin/flowctl/flowctl.c: In function 'flow_cache_print_verbose': /src/usr.sbin/flowctl/flowctl.c:242: error: dereferencing pointer to incomplete type /src/usr.sbin/flowctl/flowctl.c:245: error: dereferencing pointer to incomplete type /src/usr.sbin/flowctl/flowctl.c:246: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /src/usr.sbin/flowctl. *** 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-07-19 13:26:04 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-07-19 13:26:04 - ERROR: failed to build world TB --- 2012-07-19 13:26:04 - 1577.15 user 346.83 system 2112.92 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-mips-mips.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
[releng_8 tinderbox] failure on ia64/ia64
TB --- 2012-07-19 12:45:23 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-07-19 12:45:23 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE 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 TB --- 2012-07-19 12:45:23 - starting RELENG_8 tinderbox run for ia64/ia64 TB --- 2012-07-19 12:45:23 - cleaning the object tree TB --- 2012-07-19 12:45:23 - cvsupping the source tree TB --- 2012-07-19 12:45:23 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/ia64/ia64/supfile TB --- 2012-07-19 12:45:35 - building world TB --- 2012-07-19 12:45:35 - CROSS_BUILD_TESTING=YES TB --- 2012-07-19 12:45:35 - MAKEOBJDIRPREFIX=/obj TB --- 2012-07-19 12:45:35 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-07-19 12:45:35 - SRCCONF=/dev/null TB --- 2012-07-19 12:45:35 - TARGET=ia64 TB --- 2012-07-19 12:45:35 - TARGET_ARCH=ia64 TB --- 2012-07-19 12:45:35 - TZ=UTC TB --- 2012-07-19 12:45:35 - __MAKE_CONF=/dev/null TB --- 2012-07-19 12:45:35 - cd /src TB --- 2012-07-19 12:45:35 - /usr/bin/make -B buildworld World build started on Thu Jul 19 12:45:36 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 [...] /src/usr.sbin/flowctl/flowctl.c: At top level: /src/usr.sbin/flowctl/flowctl.c:234: warning: 'struct ngnf_flows' declared inside parameter list /src/usr.sbin/flowctl/flowctl.c:235: error: conflicting types for 'flow_cache_print_verbose' /src/usr.sbin/flowctl/flowctl.c:64: error: previous declaration of 'flow_cache_print_verbose' was here /src/usr.sbin/flowctl/flowctl.c: In function 'flow_cache_print_verbose': /src/usr.sbin/flowctl/flowctl.c:242: error: dereferencing pointer to incomplete type /src/usr.sbin/flowctl/flowctl.c:245: error: dereferencing pointer to incomplete type /src/usr.sbin/flowctl/flowctl.c:246: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /src/usr.sbin/flowctl. *** 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-07-19 13:42:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-07-19 13:42:15 - ERROR: failed to build world TB --- 2012-07-19 13:42:15 - 2785.02 user 417.74 system 3411.66 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-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
[releng_8 tinderbox] failure on powerpc/powerpc
TB --- 2012-07-19 13:04:28 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-07-19 13:04:28 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE 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 TB --- 2012-07-19 13:04:28 - starting RELENG_8 tinderbox run for powerpc/powerpc TB --- 2012-07-19 13:04:28 - cleaning the object tree TB --- 2012-07-19 13:04:28 - cvsupping the source tree TB --- 2012-07-19 13:04:28 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/powerpc/powerpc/supfile TB --- 2012-07-19 13:04:40 - building world TB --- 2012-07-19 13:04:40 - CROSS_BUILD_TESTING=YES TB --- 2012-07-19 13:04:40 - MAKEOBJDIRPREFIX=/obj TB --- 2012-07-19 13:04:40 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-07-19 13:04:40 - SRCCONF=/dev/null TB --- 2012-07-19 13:04:40 - TARGET=powerpc TB --- 2012-07-19 13:04:40 - TARGET_ARCH=powerpc TB --- 2012-07-19 13:04:40 - TZ=UTC TB --- 2012-07-19 13:04:40 - __MAKE_CONF=/dev/null TB --- 2012-07-19 13:04:40 - cd /src TB --- 2012-07-19 13:04:40 - /usr/bin/make -B buildworld World build started on Thu Jul 19 13:04:40 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 [...] /src/usr.sbin/flowctl/flowctl.c: At top level: /src/usr.sbin/flowctl/flowctl.c:234: warning: 'struct ngnf_flows' declared inside parameter list /src/usr.sbin/flowctl/flowctl.c:235: error: conflicting types for 'flow_cache_print_verbose' /src/usr.sbin/flowctl/flowctl.c:64: error: previous declaration of 'flow_cache_print_verbose' was here /src/usr.sbin/flowctl/flowctl.c: In function 'flow_cache_print_verbose': /src/usr.sbin/flowctl/flowctl.c:242: error: dereferencing pointer to incomplete type /src/usr.sbin/flowctl/flowctl.c:245: error: dereferencing pointer to incomplete type /src/usr.sbin/flowctl/flowctl.c:246: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /src/usr.sbin/flowctl. *** 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-07-19 13:48:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-07-19 13:48:51 - ERROR: failed to build world TB --- 2012-07-19 13:48:51 - 2102.39 user 374.98 system 2662.05 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-powerpc-powerpc.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
[releng_8 tinderbox] failure on sparc64/sparc64
TB --- 2012-07-19 13:26:05 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-07-19 13:26:05 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE 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 TB --- 2012-07-19 13:26:05 - starting RELENG_8 tinderbox run for sparc64/sparc64 TB --- 2012-07-19 13:26:05 - cleaning the object tree TB --- 2012-07-19 13:26:05 - cvsupping the source tree TB --- 2012-07-19 13:26:05 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/sparc64/sparc64/supfile TB --- 2012-07-19 13:26:16 - building world TB --- 2012-07-19 13:26:16 - CROSS_BUILD_TESTING=YES TB --- 2012-07-19 13:26:16 - MAKEOBJDIRPREFIX=/obj TB --- 2012-07-19 13:26:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-07-19 13:26:16 - SRCCONF=/dev/null TB --- 2012-07-19 13:26:16 - TARGET=sparc64 TB --- 2012-07-19 13:26:16 - TARGET_ARCH=sparc64 TB --- 2012-07-19 13:26:16 - TZ=UTC TB --- 2012-07-19 13:26:16 - __MAKE_CONF=/dev/null TB --- 2012-07-19 13:26:16 - cd /src TB --- 2012-07-19 13:26:16 - /usr/bin/make -B buildworld World build started on Thu Jul 19 13:26:17 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 [...] /src/usr.sbin/flowctl/flowctl.c: At top level: /src/usr.sbin/flowctl/flowctl.c:234: warning: 'struct ngnf_flows' declared inside parameter list /src/usr.sbin/flowctl/flowctl.c:235: error: conflicting types for 'flow_cache_print_verbose' /src/usr.sbin/flowctl/flowctl.c:64: error: previous declaration of 'flow_cache_print_verbose' was here /src/usr.sbin/flowctl/flowctl.c: In function 'flow_cache_print_verbose': /src/usr.sbin/flowctl/flowctl.c:242: error: dereferencing pointer to incomplete type /src/usr.sbin/flowctl/flowctl.c:245: error: dereferencing pointer to incomplete type /src/usr.sbin/flowctl/flowctl.c:246: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /src/usr.sbin/flowctl. *** 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-07-19 14:04:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-07-19 14:04:06 - ERROR: failed to build world TB --- 2012-07-19 14:04:06 - 1846.30 user 328.69 system 2280.98 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-sparc64-sparc64.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
Re: mfi(4) IO performance regression, post 8.1
On 07/17/12 15:39, Steve McCoy wrote:
On 7/13/12 9:39 AM, John Baldwin wrote:
On Thursday, July 12, 2012 11:47:28 pm Steve McCoy wrote:
On 7/12/12 4:34 PM, Steve McCoy wrote:
John Baldwin wrote:
Barring that, can you do a binary search of kernels from stable/8
between 8.1
and 8.2 on an 8.1 world to see which commit caused the change in write
performance?
Hi John, I'm working with Charles to narrow this down.
Looks like revision 212229 is the culprit, or at least around the same
time to it, if this change isn't what slowed things down. The change to
sys/kern/vfs_bio.c modifies some synchronization in dev_strategy():
Actually, hold that thought. I had a hunch that I wasn't thorough
enough, so I decided to try 212228 — the performance is the same as with
212229, so vfs_bio seems to be out of the picture. I'm going to binary
search between 209459 and 212229, and see what I find.
Ok. Please let me know what you find. Thanks!
Alright, I've finally narrowed it down to r209897, which only affects
acpi_cpu_idle():
--- stable/8/sys/dev/acpica/acpi_cpu.c 2010/06/23 17:04:42 209471
+++ stable/8/sys/dev/acpica/acpi_cpu.c 2010/07/11 11:58:46 209897
@@ -930,12 +930,16 @@
/*
* Execute HLT (or equivalent) and wait for an interrupt. We can't
- * calculate the time spent in C1 since the place we wake up is an
- * ISR. Assume we slept half of quantum and return.
+ * precisely calculate the time spent in C1 since the place we wake up
+ * is an ISR. Assume we slept no more then half of quantum.
*/
if (cx_next-type == ACPI_STATE_C1) {
- sc-cpu_prev_sleep = (sc-cpu_prev_sleep * 3 + 50 / hz) / 4;
+ AcpiHwRead(start_time, AcpiGbl_FADT.XPmTimerBlock);
acpi_cpu_c1();
+ AcpiHwRead(end_time, AcpiGbl_FADT.XPmTimerBlock);
+ end_time = acpi_TimerDelta(end_time, start_time);
+ sc-cpu_prev_sleep = (sc-cpu_prev_sleep * 3 +
+ min(PM_USEC(end_time), 50 / hz)) / 4;
return;
}
My current guess is that AcpiHwRead() is a problem on our hardware. It's
an isolated change and, to my desperate eyes, the commit message implies
that it isn't critical — Do you think we could buy ourselves some time
by pulling it out of our version of the kernel? Or is this essential for
correctness? Any thoughts are appreciated, thanks!
You might simply try a different idle function. See these sysctls:
machdep.idle: acpi
machdep.idle_available: spin, mwait, mwait_hlt, hlt, acpi,
Eric
___
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: mfi(4) IO performance regression, post 8.1
Hm! A timer related bug?
I'll CC mav@ on this, as it was his commit (and work in his general area.)
I wonder what's going on - is it something to do with the two ACPI
calls inserted there, or is it something to do with the change in
event timer values?
mav? Any ideas?
Adrian
On 17 July 2012 13:39, Steve McCoy smc...@greatbaysoftware.com wrote:
Alright, I've finally narrowed it down to r209897, which only affects
acpi_cpu_idle():
--- stable/8/sys/dev/acpica/acpi_cpu.c 2010/06/23 17:04:42 209471
+++ stable/8/sys/dev/acpica/acpi_cpu.c 2010/07/11 11:58:46 209897
@@ -930,12 +930,16 @@
/*
* Execute HLT (or equivalent) and wait for an interrupt. We can't
- * calculate the time spent in C1 since the place we wake up is an
- * ISR. Assume we slept half of quantum and return.
+ * precisely calculate the time spent in C1 since the place we wake up
+ * is an ISR. Assume we slept no more then half of quantum.
*/
if (cx_next-type == ACPI_STATE_C1) {
- sc-cpu_prev_sleep = (sc-cpu_prev_sleep * 3 + 50 / hz) / 4;
+ AcpiHwRead(start_time, AcpiGbl_FADT.XPmTimerBlock);
acpi_cpu_c1();
+ AcpiHwRead(end_time, AcpiGbl_FADT.XPmTimerBlock);
+end_time = acpi_TimerDelta(end_time, start_time);
+ sc-cpu_prev_sleep = (sc-cpu_prev_sleep * 3 +
+ min(PM_USEC(end_time), 50 / hz)) / 4;
return;
}
My current guess is that AcpiHwRead() is a problem on our hardware. It's an
isolated change and, to my desperate eyes, the commit message implies that
it isn't critical — Do you think we could buy ourselves some time by pulling
it out of our version of the kernel? Or is this essential for correctness?
Any thoughts are appreciated, thanks!
___
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
___
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: mfi(4) IO performance regression, post 8.1
Oh, and would you please file a PR for this? I've been looking into ACPI related slowdowns for a while and I'm glad you found a culprit. Adrian ___ 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
Checksum errors across ZFS array
I have a ZFS server on which I've seen periodic checksum errors on almost every drive. While scrubbing the pool last night, it began to report unrecoverable data errors on a single file. I compared an md5 of the supposedly corrupted file to an md5 of the original copy, stored on different media. They were the same, suggesting no corruption. A large file was being written to the pool while the scrub was in progress, and the entire array became unresponsive. The OS was still up, but 'zpool status' showed the scrub progress stuck at the same spot, with the throughput rate falling. 'shutdown -r now' stalled. Eventually I hard power cycled the system. Now, attempting to read the file that ZFS reports errors on yields Input/output error. The scrub completed, with the following result: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 7 mirror-0 ONLINE 0 0 0 aacd0p1 ONLINE 0 0 0 aacd4p1 ONLINE 0 0 1 mirror-1 ONLINE 0 0 0 aacd1p1 ONLINE 0 0 0 aacd5p1 ONLINE 0 0 0 mirror-2 ONLINE 0 014 aacd2p1 ONLINE 0 014 aacd6p1 ONLINE 0 014 mirror-3 ONLINE 0 0 0 aacd3p1 ONLINE 0 0 0 aacd7p1 ONLINE 0 0 0 The system configuration is as follows: Controller: Adaptec 2805 Motherboard: Supermicro X8STE Drive Cage: 2x Supermicro CSE-M35T-1 Memory: 2x Kingston 12GB ECC (KVR1066D3E7SK3/12G) PSU: Nexus RX-7000 OS: 9.0-RELEASE-p3 ZFS: ZFS filesystem version 5, ZFS storage pool version 28 The Adaptec card has 2 ports, each of which uses a 4-port fan-out cable. The cables are routed as shown: /--- aacd0 (ST1000DM003-9YN1 CC4D) / /-- aacd1 (ST1000DM003-9YN1 CC4D) p1- \ \-- aacd2 (WDC WD1001FALS-0 05.0) \--- aacd3 (WDC WD1001FALS-0 05.0) /--- aacd4 (ST1000DM003-9YN1 CC4D) / /-- aacd5 (ST1000DM003-9YN1 CC4D) p2- \ \-- aacd6 (WDC WD1002FAEX-0 05.0) \--- aacd7 (WDC WD1002FAEX-0 05.0) You can see that each ZFS mirror device is comprised of one drive from each drive carrier, on separate ports, on separate cables. Since I have seen periodic checksum errors on almost every drive but the only common component is the Adapter controller and the motherboard, I suspect the controller. (Or the motherboard, but I'm starting with the controller since it's much simpler to swap out.) Could it be something else? What else I should be looking at? Any input greatly appreciated. -Snow ___ 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
branch 9 and uefi
It took me by surprise. The mobo I have on my mind for new desktop has uefi instead of bios. It is asus m5a97, with 970 chipset, well priced among users on the net. How would it behave with 9.1? After all reading, I plan to boot it as memory stick and go with simple guided install. Someone could comment on the topic? At the moment, I see I have to avoid manual partition and mbr. Or not? If it sounds bad, any other option for motherboard and amd 8120 cpu? Best regards Zoran ___ 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: Checksum errors across ZFS array
Hi James, It's almost definitely a memory problem. I'd change it ASAP if I were you. I lost about 70mb from my zfs pool for this very reason just a few weeks ago. Luckily I had enough snapshots from before the rot set in to recover most of what I lost. Joe -- Dr Joe Karthauser On 19 Jul 2012, at 16:29, James Snow s...@teardrop.org wrote: I have a ZFS server on which I've seen periodic checksum errors on almost every drive. While scrubbing the pool last night, it began to report unrecoverable data errors on a single file. I compared an md5 of the supposedly corrupted file to an md5 of the original copy, stored on different media. They were the same, suggesting no corruption. A large file was being written to the pool while the scrub was in progress, and the entire array became unresponsive. The OS was still up, but 'zpool status' showed the scrub progress stuck at the same spot, with the throughput rate falling. 'shutdown -r now' stalled. Eventually I hard power cycled the system. Now, attempting to read the file that ZFS reports errors on yields Input/output error. The scrub completed, with the following result: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 7 mirror-0 ONLINE 0 0 0 aacd0p1 ONLINE 0 0 0 aacd4p1 ONLINE 0 0 1 mirror-1 ONLINE 0 0 0 aacd1p1 ONLINE 0 0 0 aacd5p1 ONLINE 0 0 0 mirror-2 ONLINE 0 014 aacd2p1 ONLINE 0 014 aacd6p1 ONLINE 0 014 mirror-3 ONLINE 0 0 0 aacd3p1 ONLINE 0 0 0 aacd7p1 ONLINE 0 0 0 The system configuration is as follows: Controller: Adaptec 2805 Motherboard: Supermicro X8STE Drive Cage: 2x Supermicro CSE-M35T-1 Memory: 2x Kingston 12GB ECC (KVR1066D3E7SK3/12G) PSU: Nexus RX-7000 OS: 9.0-RELEASE-p3 ZFS: ZFS filesystem version 5, ZFS storage pool version 28 The Adaptec card has 2 ports, each of which uses a 4-port fan-out cable. The cables are routed as shown: /--- aacd0 (ST1000DM003-9YN1 CC4D) / /-- aacd1 (ST1000DM003-9YN1 CC4D) p1- \ \-- aacd2 (WDC WD1001FALS-0 05.0) \--- aacd3 (WDC WD1001FALS-0 05.0) /--- aacd4 (ST1000DM003-9YN1 CC4D) / /-- aacd5 (ST1000DM003-9YN1 CC4D) p2- \ \-- aacd6 (WDC WD1002FAEX-0 05.0) \--- aacd7 (WDC WD1002FAEX-0 05.0) You can see that each ZFS mirror device is comprised of one drive from each drive carrier, on separate ports, on separate cables. Since I have seen periodic checksum errors on almost every drive but the only common component is the Adapter controller and the motherboard, I suspect the controller. (Or the motherboard, but I'm starting with the controller since it's much simpler to swap out.) Could it be something else? What else I should be looking at? Any input greatly appreciated. -Snow ___ 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 ___ 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: Checksum errors across ZFS array
On Thu, Jul 19, 2012 at 06:05:32PM +0100, Dr Joe Karthauser wrote: Hi James, It's almost definitely a memory problem. I'd change it ASAP if I were you. I lost about 70mb from my zfs pool for this very reason just a few weeks ago. Luckily I had enough snapshots from before the rot set in to recover most of what I lost. Thanks for the input. I will run a memory test against it. If I may, why almost definitely a memory problem and not an issue with the controller? (Or did you mean the controller memory?) -Snow ___ 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: Checksum errors across ZFS array
- Original Message - From: James Snow s...@teardrop.org I have a ZFS server on which I've seen periodic checksum errors on almost every drive. While scrubbing the pool last night, it began to report unrecoverable data errors on a single file. I compared an md5 of the supposedly corrupted file to an md5 of the original copy, stored on different media. They were the same, suggesting no corruption. ... Had this before, has always turned out to be failing hardware. Its been a mixture of faults for us:- 1. Memory, even though ECC and not reporting failures in use or via memtest. 2. CPU / Northbridge on old AMD's, not 100% sure which. This started as ZFS checksum issues and then weeks / months later resulting in random untraceable panic and watchdog timeouts in bge nic. Disabling the cores on the second CPU fixed this for us on two separate machines e.g. /boot/loader.conf hint.lapic.2.disabled=1 hint.lapic.3.disabled=1 So while ZFS can report errors on files, that aren't errors on the disks themselves and hence the data, as you confirmed, is fine don't ignore it. Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ 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: Checksum errors across ZFS array
- Original Message - From: James Snow s...@teardrop.org On Thu, Jul 19, 2012 at 06:05:32PM +0100, Dr Joe Karthauser wrote: Hi James, It's almost definitely a memory problem. I'd change it ASAP if I were you. I lost about 70mb from my zfs pool for this very reason just a few weeks ago. Luckily I had enough snapshots from before the rot set in to recover most of what I lost. Thanks for the input. I will run a memory test against it. If I may, why almost definitely a memory problem and not an issue with the controller? (Or did you mean the controller memory?) I wouldn't say definitely, its likely, but other hardware as per my previous mail can be the cause. Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ 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: Thinkpad X61s cannot boot 9.1-BETA1
Per olof Ljungmark peo at intersonic.se writes: Hi, Did anyone else experience this? With 9.1-BETA1 the boot process freezes, among the last lines with verbose boot are acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times after this, dead. What is supposed to happen in the next stage? This laptop worked fine with 9-STABLE to at least february. Try Google search: acpi_acad0: acline initialization done, tried 1 times for example http://forums.freebsd.org/archive/index.php/t-12194.html ... boot with disable acpi selection jb ___ 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: Thinkpad X61s cannot boot 9.1-BETA1
On 07/19/12 20:22, jb wrote: Per olof Ljungmarkpeoat intersonic.se writes: Hi, Did anyone else experience this? With 9.1-BETA1 the boot process freezes, among the last lines with verbose boot are acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times after this, dead. What is supposed to happen in the next stage? This laptop worked fine with 9-STABLE to at least february. Try Google search: acpi_acad0: acline initialization done, tried 1 times for example http://forums.freebsd.org/archive/index.php/t-12194.html ... boot with disable acpi selection Tried ALL boot options, none worked. For example, if I try disable acpi it will stop at no event timer available. ___ 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
motherboard
Hello list
I have a problem with my motherboard, with four 82573L Gigabit Ethernet
Controller integrated,
with freebsd 8.1 only work one ethernet em1 , em0 , em2 and em3 not work
dmesg info
[5.301681] e1000e :03:00.0: Disabling ASPM L1
[5.301706] e1000e :03:00.0: PCI-APIC IRQ transform: INT A - IRQ 18
[5.301727] e1000e :03:00.0: setting latency timer to 64
[5.301963] e1000e :03:00.0: irq 41 for MSI/MSI-X
[5.302457] e1000e :03:00.0: Disabling ASPM L0s
[5.371770] e1000e :03:00.0: (unregistered net_device): The NVM
Checksum Is Not Valid
[5.389922] e1000e: probe of :03:00.0 failed with error -5
the problem its the same in linux and freebsd, /Windows simply doesn't
check the NVM checksum and work fine :(
I probe install new driver, fix the eeprom //fixeep-82573-dspd.sh /
/
lemon@pfSense:~$ sudo sh fixeep-82573-dspd.sh eth0
eth0: is a 82573L Gigabit Ethernet Controller
This fixup is applicable to your hardware
fixeep-82573-dspd.sh: 34: Bad substitution
fixeep-82573-dspd.sh: 39: Bad substitution
I probe edit netdev.c in the driver and eliminate check NVM checksum
/
if (i == 2) {
e_err(The NVM Checksum Is Not Valid\n);
err = -EIO;
goto err_eeprom;
}
change to
if (i == 2) {
e_err(The NVM Checksum Is Not Valid\n);
return;
}
and recompile but nothing
Probe bootutil of Intel tool
Flasheable enable :(
lemon@pfSense:~/Intel/APPS/BootUtil/Linux32$ sudo ./bootutil32 -NIC=1
-FLASHENABLE
Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.3.27.0
Copyright (C) 2003-2012 Intel Corporation
Enabling boot ROM on port 1...Unsupported feature
Port Network Address Series WOL Flash Firmware Version
=== === === = ===
1 80014C362E39 Gigabit NO LOM,UEFI,PXE Enabled,FCOE
2 00E04C362E3A Gigabit YES LOM,PXE
3 00E04C362E3B Gigabit NO LOM,UEFI,PXE Enabled,FCOE
4 00E04C362E3C Gigabit NO LOM,UEFI,PXE Enabled,FCOE
New firmware
lemon@pfSense:~/Intel/APPS/BootUtil/Linux32$ sudo ./bootutil32 -UP=PXE -ALL
Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.3.27.0
Copyright (C) 2003-2012 Intel Corporation
Flash on LOM device not supported on port 1
Flash on LOM device not supported on port 2
Flash on LOM device not supported on port 3
Flash on LOM device not supported on port 4
Port Network Address Series WOL Flash Firmware Version
=== === === = ===
1 80014C362E39 Gigabit NO LOM,UEFI,PXE Enabled,FCOE
2 00E04C362E3A Gigabit YES LOM,PXE
3 00E04C362E3B Gigabit NO LOM,UEFI,PXE Enabled,FCOE
4 00E04C362E3C Gigabit NO LOM,UEFI,PXE Enabled,FCOE
is very hard this work any idea please i need help
thanks in advance
___
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: motherboard
sorry i forget add file with motherboard config
thanks again :)
El 19/07/12 14:40, Pablo Saldivia escribió:
Hello list
I have a problem with my motherboard, with four 82573L Gigabit
Ethernet Controller integrated,
with freebsd 8.1 only work one ethernet em1 , em0 , em2 and em3 not work
dmesg info
[5.301681] e1000e :03:00.0: Disabling ASPM L1
[5.301706] e1000e :03:00.0: PCI-APIC IRQ transform: INT A -
IRQ 18
[5.301727] e1000e :03:00.0: setting latency timer to 64
[5.301963] e1000e :03:00.0: irq 41 for MSI/MSI-X
[5.302457] e1000e :03:00.0: Disabling ASPM L0s
[5.371770] e1000e :03:00.0: (unregistered net_device): The NVM
Checksum Is Not Valid
[5.389922] e1000e: probe of :03:00.0 failed with error -5
the problem its the same in linux and freebsd, /Windows simply doesn't
check the NVM checksum and work fine :(
I probe install new driver, fix the eeprom //fixeep-82573-dspd.sh /
/
lemon@pfSense:~$ sudo sh fixeep-82573-dspd.sh eth0
eth0: is a 82573L Gigabit Ethernet Controller
This fixup is applicable to your hardware
fixeep-82573-dspd.sh: 34: Bad substitution
fixeep-82573-dspd.sh: 39: Bad substitution
I probe edit netdev.c in the driver and eliminate check NVM checksum
/
if (i == 2) {
e_err(The NVM Checksum Is Not Valid\n);
err = -EIO;
goto err_eeprom;
}
change to
if (i == 2) {
e_err(The NVM Checksum Is Not Valid\n);
return;
}
and recompile but nothing
Probe bootutil of Intel tool
Flasheable enable :(
lemon@pfSense:~/Intel/APPS/BootUtil/Linux32$ sudo ./bootutil32 -NIC=1
-FLASHENABLE
Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.3.27.0
Copyright (C) 2003-2012 Intel Corporation
Enabling boot ROM on port 1...Unsupported feature
Port Network Address Series WOL Flash Firmware Version
=== === === =
===
1 80014C362E39 Gigabit NO LOM,UEFI,PXE Enabled,FCOE
2 00E04C362E3A Gigabit YES LOM,PXE
3 00E04C362E3B Gigabit NO LOM,UEFI,PXE Enabled,FCOE
4 00E04C362E3C Gigabit NO LOM,UEFI,PXE Enabled,FCOE
New firmware
lemon@pfSense:~/Intel/APPS/BootUtil/Linux32$ sudo ./bootutil32 -UP=PXE
-ALL
Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.3.27.0
Copyright (C) 2003-2012 Intel Corporation
Flash on LOM device not supported on port 1
Flash on LOM device not supported on port 2
Flash on LOM device not supported on port 3
Flash on LOM device not supported on port 4
Port Network Address Series WOL Flash Firmware Version
=== === === =
===
1 80014C362E39 Gigabit NO LOM,UEFI,PXE Enabled,FCOE
2 00E04C362E3A Gigabit YES LOM,PXE
3 00E04C362E3B Gigabit NO LOM,UEFI,PXE Enabled,FCOE
4 00E04C362E3C Gigabit NO LOM,UEFI,PXE Enabled,FCOE
is very hard this work any idea please i need help
thanks in advance
___
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
pfsense
description: Computer
product: Lakeport
vendor: Intel
width: 32 bits
capabilities: smbios-2.3 dmi-2.3 smp-1.4 smp
configuration: cpus=1
*-core
description: Motherboard
physical id: 0
*-cpu
product: Intel(R) Xeon(TM) CPU 2.60GHz
vendor: Intel Corp.
physical id: 0
bus info: cpu@0
version: 15.2.9
size: 2600MHz
width: 32 bits
capabilities: boot fpu fpu_exception wp vme de pse tsc msr pae mce
cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht
tm pbe up pebs bts cid xtpr
configuration: id=0
*-logicalcpu:0
description: Logical CPU
physical id: 0.1
width: 32 bits
capabilities: logical
*-logicalcpu:1
description: Logical CPU
physical id: 0.2
width: 32 bits
capabilities: logical
*-cache:0
description: L1 cache
physical id: 0
size: 8KiB
*-cache:1
description: L2 cache
physical id: 1
size: 512KiB
*-memory
description: System memory
physical id: 1
size: 2003MiB
*-pci
description: Host bridge
product: Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory
Controller Hub
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 03
width: 32 bits
clock: 33MHz
configuration: driver=agpgart-intel
resources: irq:0
*-display:0 UNCLAIMED
description: VGA compatible controller
product: Mobile 945GM/GMS, 943/940GML Express Integrated Graphics
Re: branch 9 and uefi
Hi, I had a hard time booting FreeBSD 8.2 on an IBM X3550M3 which is also an UEFI maniac one. I could only boot FreeBSD from an USB DVD and install it from there. Maybe some legacy fallback boot options are availabe for this mobo. I think they have its user manual on their website. Regards, Andras On Thu, 19 Jul 2012 18:08:31 +0200, Zoran Kolic wrote: It took me by surprise. The mobo I have on my mind for new desktop has uefi instead of bios. It is asus m5a97, with 970 chipset, well priced among users on the net. How would it behave with 9.1? After all reading, I plan to boot it as memory stick and go with simple guided install. Someone could comment on the topic? At the moment, I see I have to avoid manual partition and mbr. Or not? If it sounds bad, any other option for motherboard and amd 8120 cpu? Best regards Zoran ___ 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 ___ 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
kernel panic caused by zfs/sa.c
Hello,
I'm experiencing a kernel panic that appears to be caused by zfs.
No errors are making it into /var/log/messages, but here is the error
message that appears on my screen after panic (transcribed):
panic solaris assert BSWAP_32(sa_hdr_phys-sa_magic) == SA_MAGIC,
file:
/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c,
line 1262
I can reproduce this by running cd /usr/ports/www/webkit-ghtk2; make
clean
I looked at line 1262 in sa.c and it's part of a bit of code that checks
if byte swapping is necessary. The code starting at line 1260:
if (IS_SA_BONUSTYPE(bonustype) sa_hdr_phys-sa_magic != SA_MAGIC
sa_hdr_phys-sa_magic != 0) {
VERIFY(BSWAP_32(sa_hdr_phys-sa_magic) == SA_MAGIC);
sa_byteswap(hdl, buftype);
}
As far as I can tell, my source is up to date and this code is the same
as what is in 9-STABLE.
I'm not sure what's causing the panic, does anyone have a suggestion?
Thanks for the help.
--Greg
___
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: kernel panic caused by zfs/sa.c
2012/7/19 Greg Bonett g...@bonett.org:
Hello,
I'm experiencing a kernel panic that appears to be caused by zfs.
No errors are making it into /var/log/messages, but here is the error
message that appears on my screen after panic (transcribed):
panic solaris assert BSWAP_32(sa_hdr_phys-sa_magic) == SA_MAGIC,
file:
/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c,
line 1262
I can reproduce this by running cd /usr/ports/www/webkit-ghtk2; make
clean
If that's some sort of filesystem corruption, and you use portsnap, do
you still have a panic after portsnap extract www/webkit-gtk2 cd
/usr/ports/www/webkit-gtk2 make clean ?
I looked at line 1262 in sa.c and it's part of a bit of code that checks
if byte swapping is necessary. The code starting at line 1260:
if (IS_SA_BONUSTYPE(bonustype) sa_hdr_phys-sa_magic != SA_MAGIC
sa_hdr_phys-sa_magic != 0) {
VERIFY(BSWAP_32(sa_hdr_phys-sa_magic) == SA_MAGIC);
sa_byteswap(hdl, buftype);
}
As far as I can tell, my source is up to date and this code is the same
as what is in 9-STABLE.
I'm not sure what's causing the panic, does anyone have a suggestion?
Thanks for the help.
--Greg
___
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
--
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org- against HTML email vCards X
www: http://www.gid0.org- against proprietary attachments / \
Il y a seulement 10 sortes de gens dans le monde :
ceux qui comprennent le binaire,
et ceux qui ne le comprennent pas.
___
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: branch 9 and uefi
Hi, let me make it very short. UEFI worked for me during my first installation on a UEFI machine. I moved then to 10 and still have no problems. So, if you really fail, install CURRENT and it will work. Of course you are not running then a release system with all the consequences. Erich On Friday 20 July 2012 11:48:32 Thomas Mueller wrote: from Zoran Kolic zko...@sbb.rs: It took me by surprise. The mobo I have on my mind for new desktop has uefi instead of bios. It is asus m5a97, with 970 chipset, well priced among users on the net. How would it behave with 9.1? After all reading, I plan to boot it as memory stick and go with simple guided install. Someone could comment on the topic? At the moment, I see I have to avoid manual partition and mbr. Or not? If it sounds bad, any other option for motherboard and amd 8120 cpu? G�t Andrفs and...@antiszoc.hu responded: I had a hard time booting FreeBSD 8.2 on an IBM X3550M3 which is also an UEFI maniac one. I could only boot FreeBSD from an USB DVD and install it from there. Maybe some legacy fallback boot options are availabe for this mobo. I think they have its user manual on their website. I installed FreeBSD last summer (2011) on a UEFI system, beginning with 9.0-BETA1 after having big problems with NetBSD. My hard drive is Western Digital Caviar Green 3 TB, practically forcing me to use GPT as opposed to MBR. I was able to boot, and remain able to boot using System Rescue CD (sysresccd.org) and selecting the Super Grub Disk from menus. Then I can boot as described in /usr/ports/sysutils/grub2 , which is where I got that information. You don't say how big your hard drive is, and if you want to run any OS besides FreeBSD. You can go into the guided installer to see what it wants to do but are better off selecting partition sizes outside the guided installer. bsdinstall's boot partition is useful if you run FreeBSD as the only OS on the hard disk, as I have done successfully installing FreeBSD to a USB stick. I was able to boot the FreeBSD installer USB stick using the memstick image, and am able to boot the USB-stick FreeBSD installations I've created. Tom ___ 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 ___ 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
