[releng_5 tinderbox] failure on amd64/amd64
TB --- 2005-02-19 09:11:05 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-02-19 09:11:05 - starting RELENG_5 tinderbox run for amd64/amd64 TB --- 2005-02-19 09:11:05 - checking out the source tree TB --- 2005-02-19 09:11:05 - cd /home/tinderbox/RELENG_5/amd64/amd64 TB --- 2005-02-19 09:11:05 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-02-19 09:24:20 - building world (CFLAGS=-O -pipe) TB --- 2005-02-19 09:24:20 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-02-19 09:24:20 - /usr/bin/make -B buildworld 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 TB --- 2005-02-19 10:23:07 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-02-19 10:23:07 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-02-19 10:23:07 - /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Sat Feb 19 10:23:08 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/amd64/amd64/src/sys -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/altq -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/pf -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_mib.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/amd64/amd64/src/sys -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/altq -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/pf -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:441: warning: struct freebsd32_modstat_args declared inside parameter list /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:441: warning: its scope is only this definition or declaration, which is probably not what you want /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:442: warning: no previous prototype for 'freebsd32_modstat' /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c: In function `freebsd32_modstat': /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:451: error: dereferencing pointer to incomplete type /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:465: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/obj/amd64/tinderbox/RELENG_5/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. TB --- 2005-02-19 10:27:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-02-19 10:27:23 - ERROR: failed to build generic kernel TB --- 2005-02-19 10:27:23 - tinderbox aborted ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Hard lockups using 5.3-RELEASE..
We have a Celestica dual-Opteron system w/ 4GB RAM running
5.3-RELEASE/i386 (32-bit), and a SMP-aware kernel, which is experiencing
hard lockups. Debugging results below.
-=-
[BREAK]
KDB: enter: Line break on console
[thread 100104]
Stopped at kdb_enter+0x2b: nop
db where
kdb_enter(c084e4c6) at kdb_enter+0x2b
siointr1(c507d800,c0946700,0,c084e28e,6ad) at siointr1+0xce
siointr(c507d800) at siointr+0x21
intr_execute_handlers(c4f5d490,e9826b80,4,e9826bd0,c07b2ae3) at
intr_execute_han
dlers+0x89
lapic_handle_intr(34) at lapic_handle_intr+0x2e
Xapic_isr1() at Xapic_isr1+0x33
--- interrupt, eip = 0xc0604456, esp = 0xe9826bc4, ebp = 0xe9826bd0 ---
_mtx_lock_sleep(c08f67c0,c5698640,0,c084a0b3,126) at _mtx_lock_sleep+0xc6
_mtx_lock_flags(c08f67c0,0,c084a0b3,126,c6a82738) at _mtx_lock_flags+0x48
vm_fault(c5bbd5dc,81ae000,2,8,c5698640) at vm_fault+0x1fe
trap_pfault(e9826d48,1,81ae000,81ae000,0) at trap_pfault+0xf2
trap(2f,2f,2f,2000,81ae000) at trap+0x1df
calltrap() at calltrap+0x5
--- trap 0xc, eip = 0x2809bd8d, esp = 0xbfbfb7b0, ebp = 0xbfbfb7e8 ---
db panic
panic: from debugger
cpuid = 3
boot() called on cpu#3
Uptime: 2h50m29s
-=-
(then resetting the system causes a panic, and the system locks up for
good, and a power reset is required)
We were able to get a coredump, and the resulting kgdb output is below:
-=-
(kgdb) up
#45 0xc05f9bda in fork_exit (callout=0xc05fa5dc ithread_loop,
arg=0xc4fe7a00, frame=0xe8daed48) at ../../../kern/kern_fork.c:811
811 callout(arg, frame);
(kgdb) l
806 * cpu_set_fork_handler intercepts this function call to
807 * have this call a non-return function to stay in
kernel mode.
808 * initproc has its own fork handler, but it does return.
809 */
810 KASSERT(callout != NULL, (NULL callout in fork_exit));
811 callout(arg, frame);
812
813 /*
814 * Check if a kernel thread misbehaved and returned from
its main
815 * function.
(kgdb) down
#44 0xc05fa6e8 in ithread_loop (arg=0xc4fe7a00)
at ../../../kern/kern_intr.c:547
547 ih-ih_handler(ih-ih_argument);
(kgdb) l
542 mtx_unlock(ithd-it_lock);
543 goto restart;
544 }
545 if ((ih-ih_flags IH_MPSAFE) == 0)
546 mtx_lock(Giant);
547 ih-ih_handler(ih-ih_argument);
548 if ((ih-ih_flags IH_MPSAFE) == 0)
549 mtx_unlock(Giant);
550 }
551 if (ithd-it_enable != NULL) {
(kgdb) down
#43 0xc0615dfa in softclock (dummy=0x0) at ../../../kern/kern_timeout.c:247
247 mtx_lock(Giant);
(kgdb) l
242 (c-c_flags
~CALLOUT_PENDING);
243 }
244 curr_callout = c;
245 mtx_unlock_spin(callout_lock);
246 if (!(c_flags CALLOUT_MPSAFE)) {
247 mtx_lock(Giant);
248 gcalls++;
249 CTR1(KTR_CALLOUT,
callout %p, c_func);
250 } else {
251 mpcalls++;
-=-
It looks like it's trying to lock Giant while it already has Giant. In
any case, we have rebuilt a uniprocessor kernel for now. If this is
already fixed in 5-STABLE, then let me know. ;)
Best Wishes - Peter
--
[EMAIL PROTECTED] | ISC | OpenPGP 0xE8048D08 | The bits must flow
signature.asc
Description: OpenPGP digital signature
Re: Hard lockups using 5.3-RELEASE..
On Sat, 19 Feb 2005, Peter Losher wrote: We have a Celestica dual-Opteron system w/ 4GB RAM running 5.3-RELEASE/i386 (32-bit), and a SMP-aware kernel, which is experiencing hard lockups. Debugging results below. Hmm. So just to summarize: - The system appears to wedge - Serial break can get into the debugger Have you tried updating to the latest RELENG_5_3 patch level? That includes at least one significant SMP stability fix. You can rebuild along the RELENG_5_3 branch, or just use freebsd-update to pull it in. It looks like it's trying to lock Giant while it already has Giant. In any case, we have rebuilt a uniprocessor kernel for now. If this is already fixed in 5-STABLE, then let me know. ;) Generally speaking, recursing Giant is fine, as Giant is a recursible mutex; however, an ithread shouldn't already hold Giant at that point. This may be fixed in 5-STABLE, but it's hard to say. I think the order of operations here is: - First, slide to RELENG_5_3 head (p5?) to make sure you have the IPI stability fix. See if the problem goes away. - Generate the following information: when the box is wedged, does it... (1) Respond to pings (2) Does the num lock light go on and off when the num lock key is hit (3) If it responds to pings, what happens when you build a new TCP connection to an open TCP port (a) once (b) twice (c) the 100'd (or so) time. - Generate the following DDB output using your serial console: show pcpu show pcpu 0 show pcpu 1 ps show lockedvnods I may then ask you to generate stack traces of the processes that appear interesting. The definition of interesting is a little bit context-specifi so it's hard to say what it is just now. If there are a lot of processes wedged in VM and VFS, then I'll ask you to trace each process that appears in the lockedvnods output. - Next, recompile with INVARIANTS and see if the problem triggers an assertion failure when it occurs. - Next, recompile with WITNESS and see if WITNESS creates a warning or assertion failure when it occurs. Break to the debugger and generate the above DDB output, but also show allocks (5-STABLE only), or show locks for interesting processes if 5-RELEASE-*. Also, I don't think you mentioned what sort of workload is present on the box. Thanks! Robert N M Watson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Mozilla Flash Plugin
I have just recently installed the flash plugin for Firefox and every site i have been to that has sound in the flash plays the sound very jerkily ... any ideas as to why this is happening ? -- Yours Sincerely Shinjii http://www.shinji.nq.nu ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
How to remove vestigial gmirror device?
Installed 5.3-Stable from the February ISO Snapshot on an old Pentium Pro 600MH ATX box with 256MB memory and two WD UDMA33 6.4GB drives. After several false starts with GMirror (guided by Ralf S. Engelschal's excellent How-To http://people.freebsd.org/~rse/mirror/) the system is now stable and has survived many kernel recompiles without incident. One problem, one of the original test GMirror devices refused to go away. It did not respond to the remove or forget parameters. The deactivate parameter seemed to do the trick, however, upon boot-up the following message is generated: GEOM_MIRROR: Device gmusr: provider ad4 marked as inactive, skipping. The list parameter does not list the gmusr device as being active. When gmirror activate gmusr ad4 is invoked the response is: Cannot write metadata from ad4: Operation not permitted. Not fully done. Although the vestigial device does not seem to cause any trouble, it is annoying to get the message at boot-up. I there a configuration file that can be edited or a specific disk sector where the device entry can be deleted with a disk editor? If not, any other way to remove the device permanently other than a system reinstall. Thank you. -- Remo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_5 tinderbox] failure on ia64/ia64
TB --- 2005-02-19 13:19:56 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-02-19 13:19:56 - starting RELENG_5 tinderbox run for ia64/ia64 TB --- 2005-02-19 13:19:56 - checking out the source tree TB --- 2005-02-19 13:19:56 - cd /home/tinderbox/RELENG_5/ia64/ia64 TB --- 2005-02-19 13:19:56 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-02-19 13:28:00 - building world (CFLAGS=-O -pipe) TB --- 2005-02-19 13:28:00 - cd /home/tinderbox/RELENG_5/ia64/ia64/src TB --- 2005-02-19 13:28:00 - /usr/bin/make -B buildworld 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 TB --- 2005-02-19 14:30:51 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-02-19 14:30:51 - cd /home/tinderbox/RELENG_5/ia64/ia64/src TB --- 2005-02-19 14:30:51 - /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Sat Feb 19 14:30:52 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for GENERIC completed on Sat Feb 19 14:44:26 UTC 2005 TB --- 2005-02-19 14:44:26 - generating LINT kernel config TB --- 2005-02-19 14:44:26 - cd /home/tinderbox/RELENG_5/ia64/ia64/src/sys/ia64/conf TB --- 2005-02-19 14:44:26 - /usr/bin/make -B LINT TB --- 2005-02-19 14:44:26 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2005-02-19 14:44:26 - cd /home/tinderbox/RELENG_5/ia64/ia64/src TB --- 2005-02-19 14:44:26 - /usr/bin/make buildkernel KERNCONF=LINT Kernel build for LINT started on Sat Feb 19 14:44:26 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/ia64/ia64/src/sys -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/altq -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/pf -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/ngatm -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/ia64/libuwx/src -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata -ffreestanding -Werror /tinderbox/RELENG_5/ia64/ia64/src/sys/kern/kern_mib.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/ia64/ia64/src/sys -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/altq -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/pf -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/ngatm -I/tinderbox/RELENG_5/ia64/ia64/src/sys/contrib/ia64/libuwx/src -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata -ffreestanding -Werror /tinderbox/RELENG_5/ia64/ia64/src/sys/kern/kern_module.c /tinderbox/RELENG_5/ia64/ia64/src/sys/kern/kern_module.c:441: warning: struct freebsd32_modstat_args declared inside parameter list /tinderbox/RELENG_5/ia64/ia64/src/sys/kern/kern_module.c:441: warning: its scope is only this definition or declaration, which is probably not what you want /tinderbox/RELENG_5/ia64/ia64/src/sys/kern/kern_module.c:442: warning: no previous prototype for 'freebsd32_modstat' /tinderbox/RELENG_5/ia64/ia64/src/sys/kern/kern_module.c: In function `freebsd32_modstat': /tinderbox/RELENG_5/ia64/ia64/src/sys/kern/kern_module.c:451: error: dereferencing pointer to incomplete type /tinderbox/RELENG_5/ia64/ia64/src/sys/kern/kern_module.c:465: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /tinderbox/RELENG_5/ia64/ia64/obj/ia64/tinderbox/RELENG_5/ia64/ia64/src/sys/LINT. *** Error code 1 Stop in
re: 5.3 on IBM/Intel Blade server?
On Fri, 18 Feb 2005, Paul Dlug wrote: Just a follow up to my message from the other week, it looks like we are experiencing the same problem as described in this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=68445 Only the suggested fix in the PR doesn't work for me. Does anyone have more information on this issue? The PR is still open. Is the suggested fix the patch that was applied to -current? -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to remove vestigial gmirror device?
On Sat, 19 Feb 2005, Remo Lacho wrote: Installed 5.3-Stable from the February ISO Snapshot on an old Pentium Pro 600MH ATX box with 256MB memory and two WD UDMA33 6.4GB drives. After several false starts with GMirror (guided by Ralf S. Engelschal's excellent How-To http://people.freebsd.org/~rse/mirror/) the system is now stable and has survived many kernel recompiles without incident. One problem, one of the original test GMirror devices refused to go away. It did not respond to the remove or forget parameters. The deactivate parameter seemed to do the trick, however, upon boot-up the following message is generated: GEOM_MIRROR: Device gmusr: provider ad4 marked as inactive, skipping. The list parameter does not list the gmusr device as being active. When gmirror activate gmusr ad4 is invoked the response is: Cannot write metadata from ad4: Operation not permitted. Not fully done. If ad4 is your root device, GEOM prohibits changes to the device configuration on a mounted device. You can either: a) boot into the fixit CD, finagle some symlinks to make 'gmirror' work (I think you need to symlink /dist/usr/lib to /usr/lib) and remove it from there; or b) set 'sysctl kern.geom.debugflags=16' which disables the protection. You activate this at your own risk, since it makes it possible to destroy the root volume while it is mounted. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Several problems with 5.3 STABLE
Hello and good evening. Today I made an update of my FreeBSD-System with cvs as discribed in the manual. After this procedure I made some ugly experiences: (*) Using my compact-flash-reader (Siemens-Fujtsu) shows strange results: # mount -t msdos /dev/da14s1 /dist Result: === Feb 19 22:56:01 primergy470 kernel: umass0: Get Max Lun not supported (STALLED) Feb 19 22:56:01 primergy470 kernel: da14 at umass-sim0 bus 0 target 0 lun 0 Feb 19 22:56:01 primergy470 kernel: da14:Removable Direct Access SCSI-2 device Feb 19 22:56:01 primergy470 kernel: da14: 1.000MB/s transfers Feb 19 22:56:01 primergy470 kernel: da14: 122MB (250369 512 byte sectors: 64H 32S/T 122C) # umount /dist Result: === Feb 19 22:57:55 primergy470 kernel: umass0: BBB reset failed, TIMEOUT Feb 19 22:57:55 primergy470 kernel: umass0: BBB bulk-in clear stall failed, STALLED Feb 19 22:57:55 primergy470 kernel: umass0: BBB bulk-out clear stall failed, STALLED This was shown in /var/log/messages about twenty times (*) Connecting my DigiKam (Canon Powershot G2) and identifying it is no problem: it is shown as ugen0-device. But when gphoto2 is started (gphoto2 --auto-detect -P) the system hangs and after two minutes it reboots. (*) X.ORG 6.8.1 needs about 20% of CPU-capacity, with only one() open Gnome-Terminal. Before system update it was only 5% (under FreeBSD 4.10 it needs 1%, it is a P2-266MHz notebook) (*) mplayer core dumps with signal 11 (*) opening windows on Gnome-Desktop is very slow and needs about 10 seconds. Here is the output from uname -a FreeBSD primergy470.juergendankoweit.net 5.3-STABLE FreeBSD 5.3-STABLE #1: Sat Feb 19 18:19:23 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PRIMERGY470 i386 It is a dual processor machine with 2 x 450MHz P3 and 2GB RAM. What is wrong with the new update? Is it better to change to FBSD 4.11? Many thanks for your advice. Best regards Jrgen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: Fatal trap 12: page fault while in kernel mode
On Thu, 17 Feb 2005, Rong-En Fan wrote: On Wed, 16 Feb 2005 15:36:25 -0800 (PST), Doug White [EMAIL PROTECTED] wrote: On Wed, 16 Feb 2005, Rong-En Fan wrote: Hello, This is a 5.3-RELEASE-p5/amd64 on IBM X236 (EM64T) with 2GB RAM and a LSI 21320 rmpt(4) running at 160MB/s with a hardware RAID (da0, da1). HTT is enabled. When I run benchmark/blogbench on /da0/ I can *reproduce* this panic again and again: (I'm getting a dump now, let me fsck first) kernel conf dmesg (boot -v) are at http://rafan.infor.org/tmp/236/ I only have an 2x244 Opteron box so I'm not sure if this is a problem with KSE or with hyperthreading. I'll try the benchmark anyway and see if I can reproduce. Looks like I'll need to rebuild first, I'm getting the exiting from __thread_start error... I got a good -CURRENT build and run this test. It appears to get stuck in an endless loop at the end but no panics result. I also ran it on a i386 -CURRENT machine for comparison and that completed, so this program appears to have 64-bit cleanliness problems. I'll see if I can build a RELENG_5 or 5.3 amd64 box and run the same diagnostic. Its possible its a bug thats been fixed in CURRENT but not backported yet. If I use machdep.hlt_logical_cpus=1, I got the same panic. And when I use kgdb to read the kernel dump, I see only #1 ?? (??) in backtrace. I just reinstall the system to 5.3-p5, i386. It does not panic and finsih the test two times. I'll run more to see if is panics. Regards, Rong-En Fan -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: {Spam?} Re: can't get a crash dump
Kris Kennaway wrote: On Thu, Feb 17, 2005 at 12:40:56PM +0100, Roberto Nunnari wrote: another crash.. and in /var/log/messages I see: Feb 17 12:20:50 jupiter savecore: no dumps found Any hints, please? If you watch it panic (or trigger one; break to ddb and use call doadump), does it dump? Yes. Once in ddb, if I call doadump it dumps! But I have not yet been that lucky to see it crash.. Kris -- Roberto Nunnari -software engineer- mailto:[EMAIL PROTECTED] Scuola Universitaria Professionale della Svizzera Italiana Dipartimento Tecnologie Innovative http://www.dti.supsi.ch SUPSI-DTI Via Cantonaletel: +41-91-6108561 6928 Mannofax: +41-91-6108570 Switzerland (o o) ===oOO==(_)==OOo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: {Spam?} Re: can't get a crash dump
On Sun, Feb 20, 2005 at 12:34:42AM +0100, Roberto Nunnari wrote: Kris Kennaway wrote: On Thu, Feb 17, 2005 at 12:40:56PM +0100, Roberto Nunnari wrote: another crash.. and in /var/log/messages I see: Feb 17 12:20:50 jupiter savecore: no dumps found Any hints, please? If you watch it panic (or trigger one; break to ddb and use call doadump), does it dump? Yes. Once in ddb, if I call doadump it dumps! But I have not yet been that lucky to see it crash.. You can remove KDB_UNATTENDED from your kernel configuration, and it should drop to DDB when it panics, so you can catch the panic then. Kris pgpTAHGmtrWI5.pgp Description: PGP signature
Re: {Spam?} Re: can't get a crash dump
Kris Kennaway wrote: On Sun, Feb 20, 2005 at 12:34:42AM +0100, Roberto Nunnari wrote: Kris Kennaway wrote: On Thu, Feb 17, 2005 at 12:40:56PM +0100, Roberto Nunnari wrote: another crash.. and in /var/log/messages I see: Feb 17 12:20:50 jupiter savecore: no dumps found Any hints, please? If you watch it panic (or trigger one; break to ddb and use call doadump), does it dump? Yes. Once in ddb, if I call doadump it dumps! But I have not yet been that lucky to see it crash.. You can remove KDB_UNATTENDED from your kernel configuration, and it should drop to DDB when it panics, so you can catch the panic then. I don't have KDB_UNATTENDED in my kernel configuration.. if you would like to give it a look you'll find it here: http://www.nunnisoft.ch/JUPITER and here is my rc.conf: http://www.nunnisoft.ch/rc.conf but I just found out something was wrong with perl.. I had perl 5.6.2 and perl-5.8.6_2.. but calling use.perl system would let me without any soft links in /usr/bin and /usr/local/bin, while use.perl port would create links for 5.6.2.. so I deinstalled 5.6.2 and portupgrade -f 5.8.6.. hope that fixes something.. I'll let you know. I'm going to get some sleep now.. Thank you for your time, Kris. Best regards. Kris -- Roberto Nunnari -software engineer- mailto:[EMAIL PROTECTED] Scuola Universitaria Professionale della Svizzera Italiana Dipartimento Tecnologie Innovative http://www.dti.supsi.ch SUPSI-DTI Via Cantonaletel: +41-91-6108561 6928 Mannofax: +41-91-6108570 Switzerland (o o) ===oOO==(_)==OOo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Tarpitting Spam Traffic using PF...
I read about the spamd redirect in pf.conf. However, I wonder if it might be useful to set up a redirect to something like this: http://www.fresh.files2.serveftp.net/smtarpit/ I suppose it doesn't make a difference, but I do want to make it extremely painful for any spammers. What are other people doing on this part? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_5 tinderbox] failure on amd64/amd64
TB --- 2005-02-20 06:21:36 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-02-20 06:21:36 - starting RELENG_5 tinderbox run for amd64/amd64 TB --- 2005-02-20 06:21:36 - checking out the source tree TB --- 2005-02-20 06:21:36 - cd /home/tinderbox/RELENG_5/amd64/amd64 TB --- 2005-02-20 06:21:36 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-02-20 06:39:08 - building world (CFLAGS=-O -pipe) TB --- 2005-02-20 06:39:08 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-02-20 06:39:08 - /usr/bin/make -B buildworld 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 TB --- 2005-02-20 07:36:39 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-02-20 07:36:39 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-02-20 07:36:39 - /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Sun Feb 20 07:36:40 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/amd64/amd64/src/sys -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/altq -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/pf -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_mib.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/amd64/amd64/src/sys -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/altq -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/pf -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:441: warning: struct freebsd32_modstat_args declared inside parameter list /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:441: warning: its scope is only this definition or declaration, which is probably not what you want /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:442: warning: no previous prototype for 'freebsd32_modstat' /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c: In function `freebsd32_modstat': /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:451: error: dereferencing pointer to incomplete type /tinderbox/RELENG_5/amd64/amd64/src/sys/kern/kern_module.c:465: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/obj/amd64/tinderbox/RELENG_5/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. TB --- 2005-02-20 07:40:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-02-20 07:40:55 - ERROR: failed to build generic kernel TB --- 2005-02-20 07:40:55 - tinderbox aborted ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
