Re: Non-responsive 8.0-RC1 (now 8.0-STABLE)
Peter Jeremy wrote: On 2009-Nov-30 19:13:30 +1100, Peter Jeremy wrote: On 2009-Nov-29 08:56:55 +0100, Thomas Backman wrote: On Nov 28, 2009, at 10:22 PM, Peter Jeremy wrote: My main server is running 8.0/amd64 from between RC1 and RC2 and I've recently had a couple of long-duration hangs on it during which time processes doing I/O will stop responding. ... It actually "hung" again just after I sent the original mail. This time I managed to get console access and could check the kernel state. This showed that a number of processes were blocked on ZFS locks. The most commonly reported state was 'tx->tx_quiesce_done_cv)'. I've upgraded to 8-STABLE from 30-Nov and the problem is still present, even after disabling the boinc processes. This seems to leave race conditions inside ZFS as the only option. Has anyone else seen anything like this? I got the same issue since I upgraded to 8.0-RELEASE. I happens during high I/O operation such a buildworld. Since I run top in an ssh session, I can say that before the hung [zfskern] process shows high CPU usage, global system usage is 99%. Sometimes I can get back to normal breaking the build with Ctrl-C. Sometimes I don't. If enabled, the watchdog kicks in and the machine reboots (else, I just ssh control over it). The machine is low (512MB) memory, with same tuning as I used in 7.2 (arc reduced to 60M, device cache to 5M, which gave me a stable machine). I enabled crashdumps. I can investigate if somebody give me pointers of where to look. 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"
freebsd update for 8.0-REL-p1 ?
Hi! Now that the rtld patch is available, how do I upgrade using freebsd-update ? freebsd-update -r 8.0-RELEASE-p1 upgrade says: [...] Fetching metadata signature for 8.0-RELEASE-p1 from update4.FreeBSD.org... failed. Fetching metadata signature for 8.0-RELEASE-p1 from update5.FreeBSD.org... failed. Fetching metadata signature for 8.0-RELEASE-p1 from update2.FreeBSD.org... failed. No mirrors remaining, giving up. So it does not upgrade 8-( -- p...@opsec.eu+49 171 310137211 years to go ! ___ 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 update for 8.0-REL-p1 ?
Kurt Jaeger wrote: Hi! Now that the rtld patch is available, how do I upgrade using freebsd-update ? freebsd-update -r 8.0-RELEASE-p1 upgrade says: [...] Fetching metadata signature for 8.0-RELEASE-p1 from update4.FreeBSD.org... failed. Fetching metadata signature for 8.0-RELEASE-p1 from update5.FreeBSD.org... failed. Fetching metadata signature for 8.0-RELEASE-p1 from update2.FreeBSD.org... failed. No mirrors remaining, giving up. So it does not upgrade 8-( Hi. Just do : freebsd-update fetch then : freebsd-update install 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: Areca Disk Adapter Question
On 06/12/2009 02:26, Karl Denninger wrote: BUT BUT BUT - there is no way to clear the devices nodes from FreeBSD! If I attempt a "camcontrol rescan all" after pulling a set the machine instantly panics with uncompleted I/Os to the disks I did not tamper with - whether I tell the adapter I did it first or not. With the 3ware drivers this is propagated through properly. Not so with the Areca drivers. This is a fairly major problem in that it appears that anything you do that causes a "da" device served by these boards to disappear causes an instant panic. While this is expected behavior if the device is in active use, it really, really sucks if it's not, as it makes it flatly impossible to, for example, pull a disk carrier that has a big drive on it you just ran a dump to. It may be worth you taking this up with Areca support also. I have a handful of their cards at work and one at home and had some issues with the HTTP interface on amd64 recently. They'd got back to me with a solution within a couple of days. Richard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
8-STABLE broken on amd64
Hi,
I've cvsuped my 8-STABLE yesterday und successfully upgraded my i386
machines.
Now I tried to upgrade my amd64 system but it failes with:
/usr/local/libexec/ccache/world-cc -O2 -pipe
-I/usr/src/lib/csu/i386-elf/../common
-I/usr/src/lib/csu/i386-elf/../../libc/include -std=gnu99 -Wsystem-headers
-Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings
-Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline
-Wnested-externs -Wredundant-decls -Wno-pointer-sign -c
/usr/src/lib/csu/i386-elf/crt1.c
{standard input}: Assembler messages:
{standard input}:27: Error: suffix or operands invalid for `mov'
*** Error code 1
Stop in /usr/src/lib/csu/i386-elf.
*** Error code 1
Is this known or has it already been fixed?
I also tried /usr/bin/cc if someone might think that ccache could
have caused this - same error.
Line 24-30 of crt1.s
movl(%rsp), %ebx
leaq8(%rsp), %r12
#APP
movl %edx,%rdi
#NO_APP
movslq %ebx,%rax
testl %ebx, %ebx
--
Oliver Lehmann
http://www.pofo.de/
http://wishlist.ans-netz.de/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 8-STABLE broken on amd64
Oliver Lehmann wrote:
> /usr/local/libexec/ccache/world-cc -O2 -pipe
> -I/usr/src/lib/csu/i386-elf/../common
> -I/usr/src/lib/csu/i386-elf/../../libc/include -std=gnu99 -Wsystem-headers
> -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
> -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter
> -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
> -Wno-pointer-sign -c /usr/src/lib/csu/i386-elf/crt1.c
> {standard input}: Assembler messages:
> {standard input}:27: Error: suffix or operands invalid for `mov'
> *** Error code 1
Compiling without any optimization (removing -O2) makes the error
go away by the way
Then the asm part gets to:
#APP
movl %edx,-8(%rbp)
--
Oliver Lehmann
http://www.pofo.de/
http://wishlist.ans-netz.de/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 8-STABLE broken on amd64
On Sun, Dec 06, 2009 at 04:52:57PM +0100, Oliver Lehmann wrote:
> Oliver Lehmann wrote:
>
> > /usr/local/libexec/ccache/world-cc -O2 -pipe
> > -I/usr/src/lib/csu/i386-elf/../common
> > -I/usr/src/lib/csu/i386-elf/../../libc/include -std=gnu99 -Wsystem-headers
> > -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
> > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
> > -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter
> > -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
> > -Wno-pointer-sign -c /usr/src/lib/csu/i386-elf/crt1.c
> > {standard input}: Assembler messages:
> > {standard input}:27: Error: suffix or operands invalid for `mov'
> > *** Error code 1
>
> Compiling without any optimization (removing -O2) makes the error
> go away by the way
>
> Then the asm part gets to:
>
> #APP
> movl %edx,-8(%rbp)
Does this happen if you remove ccache from the picture, and/or remove
/usr/obj/* prior to building?
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 8-STABLE broken on amd64
Hi, Jeremy Chadwick writes: On Sun, Dec 06, 2009 at 04:52:57PM +0100, Oliver Lehmann wrote: Compiling without any optimization (removing -O2) makes the error go away by the way Then the asm part gets to: #APP movl %edx,-8(%rbp) Does this happen if you remove ccache from the picture, and/or remove /usr/obj/* prior to building? As said in my intial posting, using base cc causes the same error. Except when I remove -O2 - then both, ccache and base-cc works. And since the error is in the generated asm code I'm not sure how anything in /usr/obj would affect this It seems to be just gcc's optimizer which creates invalid ASM code here... for whatever reason. ___ 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 7.1: QUOTA: kernel panics in jailed()
On Sun, Dec 06, 2009 at 01:21:24AM +0200, Mikolaj Golub wrote:
> Hi,
>
> Today we have observed the panic on our FreeBSD7.1 box build with QUOTA
> support.
>
> According to backtrace ffs_truncate() called chkdq() with NOCRED but later
> jailed() was called and the system crashed dereferencing cred->cr_prison.
>
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "i386-marcel-freebsd"...
>
> Unread portion of the kernel message buffer:
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 7; apic id = 07
> fault virtual address = 0x64
> fault code = supervisor read, page not present
> instruction pointer = 0x20:0xc07a1d26
> stack pointer = 0x28:0xedb2d8b8
> frame pointer = 0x28:0xedb2d8b8
> code segment= base 0x0, limit 0xf, type 0x1b
> = DPL 0, pres 1, def32 1, gran 1
> processor eflags= interrupt enabled, resume, IOPL = 0
> current process = 9742 (icoms_agent_cox476)
> trap number = 12
> panic: page fault
> cpuid = 7
> Uptime: 19h54m4s
> Physical memory: 3315 MB
> Dumping 326 MB: 311 295 279 263 247 231 215 199 183 167 151 135 119 103 87 71
> 55 39 23 7
>
> Reading symbols from /boot/kernel/if_lagg.ko...Reading symbols from
> /boot/kernel/if_lagg.ko.symbols...done.
> done.
> Loaded symbols for /boot/kernel/if_lagg.ko
> Reading symbols from /boot/kernel/acpi.ko...Reading symbols from
> /boot/kernel/acpi.ko.symbols...done.
> done.
> Loaded symbols for /boot/kernel/acpi.ko
> #0 doadump () at pcpu.h:196
> 196 pcpu.h: No such file or directory.
> in pcpu.h
> (kgdb) bt
> #0 doadump () at pcpu.h:196
> #1 0xc07c2b27 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
> #2 0xc07c2df9 in panic (fmt=Variable "fmt" is not available.
> ) at /usr/src/sys/kern/kern_shutdown.c:574
> #3 0xc0ada1ec in trap_fatal (frame=0xedb2d878, eva=100) at
> /usr/src/sys/i386/i386/trap.c:939
> #4 0xc0ada470 in trap_pfault (frame=0xedb2d878, usermode=0, eva=100) at
> /usr/src/sys/i386/i386/trap.c:852
> #5 0xc0adae2c in trap (frame=0xedb2d878) at /usr/src/sys/i386/i386/trap.c:530
> #6 0xc0ac0c9b in calltrap () at /usr/src/sys/i386/i386/exception.s:159
> #7 0xc07a1d26 in jailed (cred=0x0) at /usr/src/sys/kern/kern_jail.c:465
> #8 0xc07a1da5 in prison_priv_check (cred=0x0, priv=320) at
> /usr/src/sys/kern/kern_jail.c:581
> #9 0xc07b62ce in priv_check_cred (cred=0x0, priv=320, flags=0) at
> /usr/src/sys/kern/kern_priv.c:86
> #10 0xc09e742d in chkdq (ip=0xcb55c980, change=28, cred=0x0, flags=Variable
> "flags" is not available.
> )
> at /usr/src/sys/ufs/ufs/ufs_quota.c:188
> #11 0xc09c24f7 in ffs_truncate (vp=0xcac04cf0, length=0, flags=2048,
> cred=0xc9871d00, td=0xc95d28c0)
> at /usr/src/sys/ufs/ffs/ffs_inode.c:276
> #12 0xc09ed372 in ufs_setattr (ap=0xedb2db64) at
> /usr/src/sys/ufs/ufs/ufs_vnops.c:600
> #13 0xc0af0582 in VOP_SETATTR_APV (vop=0xc0c2ff80, a=0xedb2db64) at
> vnode_if.c:583
> #14 0xc084c446 in kern_open (td=0xc95d28c0, path=0x4890e68c 0x4890e68c out of bounds>,
> pathseg=UIO_USERSPACE, flags=Variable "flags" is not available.
> ) at vnode_if.h:315
> #15 0xc084c5b0 in open (td=0xc95d28c0, uap=0xedb2dcfc) at
> /usr/src/sys/kern/vfs_syscalls.c:999
> #16 0xc0ada7c5 in syscall (frame=0xedb2dd38) at
> /usr/src/sys/i386/i386/trap.c:1090
> #17 0xc0ac0d00 in Xint0x80_syscall () at
> /usr/src/sys/i386/i386/exception.s:255
> #18 0x0033 in ?? ()
> Previous frame inner to this frame (corrupt stack?)
> (kgdb) fr 11
> #11 0xc09c24f7 in ffs_truncate (vp=0xcac04cf0, length=0, flags=2048,
> cred=0xc9871d00, td=0xc95d28c0)
> at /usr/src/sys/ufs/ffs/ffs_inode.c:276
> 276 (void) chkdq(ip, -datablocks, NOCRED, 0);
> (kgdb) list
> 271 if (ip->i_flag & IN_SPACECOUNTED)
> 272 fs->fs_pendingblocks -= datablocks;
> 273 UFS_UNLOCK(ump);
> 274 } else {
> 275 #ifdef QUOTA
> 276 (void) chkdq(ip, -datablocks, NOCRED, 0);
> 277 #endif
The kernel paniced because chkdq was supplied NULL credentials and
_positive_ blocks use count change. Line 276 calls chkdq with
-datablocks as the change. This could happen if you have problems
either with hardware (e.g. memory or CPU cache), or your fs
is damaged.
Another possibility is random corruption of the kernel memory, but
I recommend to start with fsck and then continue with memory testers
if fsck have shown no problems.
> 278 softdep_setup_freeblocks(ip, length,
> needextclean ?
> 279
Re: 8-STABLE broken on amd64
One more /usr/local/libexec/ccache/world-cc -O2 -pipe -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386 -DNLS -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/lib32/usr/src/lib/libc -I/usr/src/lib/libc/resolv -D_ACL_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c fork.S fork.S: Assembler messages: fork.S:3: Error: invalid character '_' in mnemonic *** Error code 1 Stop in /usr/src/lib/libc. Is maybe WITH_LIB32= yes in my make.cfg causing this? I have it a long time in it and it worked at least with 7 -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ 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.0 system freeze
On Wed, 2 Dec 2009, Peter Pieczora wrote: Hi, You're absolutely right, adding dumpdev="AUTO" solved generating dump files. I may be totally wrong, but it seems that wlan0 causes system panic: I remember when using ndis device (linksys pcmcia wifi card) similar situation took place. Thanks for your help. local dumped core - see /var/crash/vmcore.3 Can you run "crashinfo -n 3" and (after verifying there's nothing confidential in the output) post the output online somewhere please? Thanks, Gavin ___ 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 update for 8.0-REL-p1 ?
[r...@argos /home/op]# uname -a FreeBSD argos 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 22:40:34 UTC 2009 r...@araz.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC sparc64 [r...@argos /home/op]# freebsd-update fetch Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from update5.FreeBSD.org... failed. Fetching public key from update4.FreeBSD.org... failed. Fetching public key from update2.FreeBSD.org... failed. No mirrors remaining, giving up. when manualy fetch pub.ssl and place its dir, then become this error message: Fetching metadata signature for 8.0-RELEASE-p1 from update4.FreeBSD.org... failed. Fetching metadata signature for 8.0-RELEASE-p1 from update5.FreeBSD.org... failed. Fetching metadata signature for 8.0-RELEASE-p1 from update2.FreeBSD.org... failed. On 12/6/09, Arnaud Houdelette wrote: > Kurt Jaeger wrote: >> Hi! >> >> Now that the rtld patch is available, how do I upgrade using >> freebsd-update ? >> >> freebsd-update -r 8.0-RELEASE-p1 upgrade >> >> says: >> >> [...] >> Fetching metadata signature for 8.0-RELEASE-p1 from update4.FreeBSD.org... >> failed. >> Fetching metadata signature for 8.0-RELEASE-p1 from update5.FreeBSD.org... >> failed. >> Fetching metadata signature for 8.0-RELEASE-p1 from update2.FreeBSD.org... >> failed. >> No mirrors remaining, giving up. >> >> So it does not upgrade 8-( >> > Hi. > Just do : > freebsd-update fetch > then : > freebsd-update install > > 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" > ___ 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"
Cannot allocate system-mode PMC with spec. "instructions"
Hi list, Joseph, __ Please Cc: me when replying, as I'm not subscribed. __ I've tried to sample my system while performing a big copy between UFS to ZFS using the following command: % # pmcstat -v -S instructions -O $PWD/sample.out % pmcstat: ERROR: Cannot allocate system-mode pmc with specification "instructions": Invalid argument Oddly, other generic events lead to different errors: % obiwan:~/tmp# pmcstat -vv -S cycles -O $PWD/sample.out % pmcstat: ERROR: Cannot allocate system-mode pmc with specification "cycles": Operation not supported But for instance the following works: % obiwan:~/tmp# pmcstat -vv -S branches -O $PWD/sample.out % ^Cobiwan:~/tmp# pmcstat -R sample.out -g % CONVERSION STATISTICS: % #samples/total 3110 % #samples/unclaimed 87 % #callchain/dubious-frames87 Additional useful informations are: % CPU: Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz (1869.87-MHz 686-class CPU) % Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 % Features=0xbfebfbff % Features2=0xe3bd % AMD Features=0x2000 % AMD Features2=0x1 % TSC: P-state invariant % hwpmc: TSC/1/64/0x20 IAP/2/40/0x3ff IAF/0/0/0x61 Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot 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: 8-STABLE broken on amd64
Oliver Lehmann wrote:
> {standard input}: Assembler messages:
> {standard input}:27: Error: suffix or operands invalid for `mov'
> *** Error code 1
>
> Stop in /usr/src/lib/csu/i386-elf.
> *** Error code 1
I deinstalled ccache, ran a make clean cleandepend, removed any .o file
below /usr/src, ran a new cvsup and now the error is gone.
--
Oliver Lehmann
http://www.pofo.de/
http://wishlist.ans-netz.de/
___
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"
root partition too small
Label from freebsd sysinstall in auto mode, make root partition 500mb For update OS (kernel + kernel.old) need about 700mb Howto rebild kernel with litsted in kldstat modules? -- alexs pgpsDGIM8IKhj.pgp Description: PGP signature
