acquiring duplicate lock of same type: vnode interlock

I think I've read somewhere about panic during early root mount, fsck etc.. Perhaps this might be related: Full dmesg: http://people.freebsd.org/~ariff/misc/dmesg.boot.amd64 [] acquiring duplicate lock of same type: vnode interlock 1st vnode interlock @ kern/vfs_vnops.c:791 2nd vnode

SETFEATURES SET TRANSFER MODE semaphore timeout on FreeBSD 6.0 RELEASE

Hi I have a newly installed FreeBSD 6.0 release machine on which I am getting the following error on the console: ad4: req=0xc23bc258 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! This is generally associated with heightened disk activity, but it happens

Re: acquiring duplicate lock of same type: vnode interlock

On Fri, Mar 17, 2006 at 06:51:42PM +0800, Ariff Abdullah wrote: I think I've read somewhere about panic during early root mount, fsck etc.. Perhaps this might be related: Full dmesg: http://people.freebsd.org/~ariff/misc/dmesg.boot.amd64 [] acquiring duplicate lock of same type: vnode

Re: too much spam (Was: no subject)

On 3/17/06, J. Buck Caldwell [EMAIL PROTECTED] wrote: Andrew Pantyukhin wrote: On 3/16/06, J. Buck Caldwell [EMAIL PROTECTED] wrote: You know, I tried printing it out, but I still can't see the naked lady... :-) Beware, by answering spam messages like that you get your address

QUARANTINED: Delivery reports about your e-mail

The message Delivery reports about your e-mail from Automatic Email Delivery Software, sent on 3/17/2006 11:58 was quarantined because it contained either an executable file, a batch file or a screen saver file. All of these types of attachments are considered security risks. Please consult

Fatal trap 12: page fault while in kernel mode / current process=12 (swi1: net)

this is 6.0-STABLE as for Mar 17. KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-PRERELEASE

Re: Fatal trap 12: page fault while in kernel mode / current process=12 (swi1: net)

On Fri, Mar 17, 2006 at 10:59:40AM -0600, Vlad wrote: this is 6.0-STABLE as for Mar 17. Are you using kernel mode ppp? If so, don't. Kris pgp3tycV8zjpL.pgp Description: PGP signature

Re: Fatal trap 12: page fault while in kernel mode / current process=12 (swi1: net)

no, nothing like that. and it reboots several times a day. also, I have my swap twice less than physical mem, so I can't get a dump (btw, there was a patch for to gzip core before it stores it into swap, so it can be fit in swap of smaller size - anyone has it?) On 3/17/06, Kris Kennaway [EMAIL

Re: Fatal trap 12: page fault while in kernel mode / current process=12 (swi1: net)

On Fri, Mar 17, 2006 at 11:41:58AM -0600, Vlad wrote: no, nothing like that. and it reboots several times a day. Where do the online/offline messages come from? Kris pgptmL30y88dA.pgp Description: PGP signature

Re: Fatal trap 12: page fault while in kernel mode / current process=12 (swi1: net)

I have Putty logging stuff and I guess it's either part of its keepalive packets. On 3/17/06, Kris Kennaway [EMAIL PROTECTED] wrote: On Fri, Mar 17, 2006 at 11:41:58AM -0600, Vlad wrote: no, nothing like that. and it reboots several times a day. Where do the online/offline messages come

Re: Fatal trap 12: page fault while in kernel mode / current process=12 (swi1: net)

On Fri, Mar 17, 2006 at 11:46:03AM -0600, Vlad wrote: I have Putty logging stuff and I guess it's either part of its keepalive packets. OK, thanks. Kris pgp9bQOumoHeI.pgp Description: PGP signature

Re: SETFEATURES SET TRANSFER MODE semaphore timeout on FreeBSD 6.0 RELEASE

On Fri, Mar 17, 2006 at 02:13:59PM +0200, Peter van Heusden wrote: Hi I have a newly installed FreeBSD 6.0 release machine on which I am getting the following error on the console: ad4: req=0xc23bc258 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! Update to

Re: SETFEATURES SET TRANSFER MODE semaphore timeout on FreeBSD 6.0 RELEASE

Ok, but the machine is not stable enough to run cvsup / buildworld on. I guess I need to do a binary install of one of the FreeBSD 6.1 betas. Thanks for the advice. Peter Ruslan Ermilov wrote: On Fri, Mar 17, 2006 at 02:13:59PM +0200, Peter van Heusden wrote: Hi I have a newly installed

Re: SETFEATURES SET TRANSFER MODE semaphore timeout on FreeBSD 6.0 RELEASE

At 01:34 PM 17/03/2006, Peter van Heusden wrote: Ok, but the machine is not stable enough to run cvsup / buildworld on. I guess I need to do a binary install of one of the FreeBSD 6.1 betas. Thanks for the advice. You might be able to just grab the kernel off a newer Beta and install the

Re: SETFEATURES SET TRANSFER MODE semaphore timeout on FreeBSD 6.0 RELEASE

On Fri, Mar 17, 2006 at 03:03:27PM -0500, Mike Tancsa wrote: At 01:34 PM 17/03/2006, Peter van Heusden wrote: Ok, but the machine is not stable enough to run cvsup / buildworld on. I guess I need to do a binary install of one of the FreeBSD 6.1 betas. Thanks for the advice. You might be

Re: Temperature monitoring in FreeBSD 4/5/6

Hello, try /usr/ports/sysutils/mbmon. It is HW specific supports LM78/79, WINBond 83781D/83782D/83783S, ASUS 991227F, and VIA VT82C686A/B PC-health chips via 3 methods: ISA-I/O, SMBus, VIA-direct. to get the HD`s temperature (and other info about HD as well) you can use

Re: SETFEATURES SET TRANSFER MODE semaphore timeout on FreeBSD 6.0 RELEASE

On Fri, Mar 17, 2006 at 03:35:39PM -0500, Kris Kennaway wrote.. On Fri, Mar 17, 2006 at 03:03:27PM -0500, Mike Tancsa wrote: At 01:34 PM 17/03/2006, Peter van Heusden wrote: Ok, but the machine is not stable enough to run cvsup / buildworld on. I guess I need to do a binary install of one

Re: Fatal trap 12: page fault while in kernel mode / current process=12 (swi1: net)

On Fri, Mar 17, 2006 at 11:41:58AM -0600, Vlad wrote: no, nothing like that. and it reboots several times a day. also, I have my swap twice less than physical mem, so I can't get a dump (btw, there was a patch for to gzip core before it stores it into swap, so it can be fit in swap of

Re: Temperature monitoring in FreeBSD 4/5/6

Vladimir Botka wrote: Hello, try /usr/ports/sysutils/mbmon. It is HW specific supports LM78/79, WINBond 83781D/83782D/83783S, ASUS 991227F, and VIA VT82C686A/B PC-health chips via 3 methods: ISA-I/O, SMBus, VIA-direct. Problem with mbmon is that its support for the various chipsets is

Welcome to Chase Online

[1]Chase Welcome to the New Chase Online Activate Free Alerts [2]Activate Free Alerts Pay your Chase credit card bill [3]Pay your Chase credit card bill Set up Automatic Payments [4]Set up Automatic Payments Update your address and phone number [5]Update your address

Re: panic: ffs_valloc: dup alloc in 6.1-BETA4

[moved to -current due to lack of response] Eric Anderson wrote: Mike Tancsa wrote: At 04:48 PM 13/03/2006, Eric Anderson wrote: I get the above panic after nfs clients attach to this nfs server and being I do have dumps from two crashes so far. This is FreeBSD-6.1-PRERELEASE from

Re: Fatal trap 12: page fault while in kernel mode / current process=12 (swi1: net)

Ok, thanks for Joe's hint I was able to get stuff captured: # kgdb kernel.debug /var/crash/vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free

Re: Fatal trap 12: page fault while in kernel mode / current process=12 (swi1: net)

and here comes another fresh one # kgdb kernel.debug /var/crash/vmcore.1 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU