On Sep 17, 2:03pm, Brad Knowles wrote:
} Subject: Re: More benchmarking stuff...
}
} Sadly, when I go to the second set of tests (20,000 files and
} 50,000 transactions), my performance goes into the crapper. I know
} that softupdates trades memory for speed, and I guess this PPro 200
On Sep 30, 11:24pm, Marcel Moolenaar wrote:
} Subject: Re: HEADS UP: sigset_t changes committed
} As for me, I'm trying to define the problem as detailed and consise as
} possible. I already have some specific thoughts and ideas. I'm thinking
} large here: real cross-compilation capabilities and
On Sep 30, 4:14pm, John-Mark Gurney wrote:
} Subject: Re: HEADS UP: sigset_t changes committed
}
} In this particular case, the only thing cross-compilation would buy us
} is the ability to build (but not install) 4.x binaries on a machine
} running 3.x. It sounds like some folks would be
I happened to try to install 4.0-CURRENT on a box that has an
Emerging Technologies ET/5025-16 ISA card installed and found that
the kernel wedges during boot. It hangs hard and won't respond to
anything except the reset switch. The motherboard is an Asus P3B-F
and I believe I have the BIOS
On Mar 2, 4:09am, Don Lewis wrote:
} Subject: current hangs during boot if ET/5025-16 card is installed
}
} I happened to try to install 4.0-CURRENT on a box that has an
} Emerging Technologies ET/5025-16 ISA card installed and found that
} the kernel wedges during boot. It hangs hard
On Mar 3, 11:16am, "Matthew N. Dodd" wrote:
} Subject: Re: 4.0-CURRENT hangs in ex_isa_identify() (was: current hangs du
} On Fri, 3 Mar 2000, Don Lewis wrote:
} What really sucks is that there is no way to disable the ex driver
} at boot time, so the standard install floppies can
On Mar 15, 9:03am, Kris Kennaway wrote:
} Subject: Re: Why not gzip iso images?
} On Wed, 15 Mar 2000, Alfred Perlstein wrote:
}
} I feel pretty confident assuming that most people that burn ISOs probably
} keep enough disk space free to hold one and not much more, going from
} a requirement
On Mar 17, 6:27pm, Alfred Perlstein wrote:
} Subject: Re: kern/8324
} * Archie Cobbs [EMAIL PROTECTED] [000317 17:55] wrote:
} This bug has been around since at least 2.2.6 and is still present
} in RELENG_3, RELENG_4, and -current.
}
}http://www.freebsd.org/cgi/query-pr.cgi?pr=8324
}
On Mar 20, 11:00am, Archie Cobbs wrote:
} Subject: Re: kern/8324
} Don Lewis writes:
} This patch (vs the 3.4-STABLE version of tty.c) causes SIGIO to be
} sent when a regular or pseudo tty becomes writeable.
}
}
} --- tty.c.orig Sun Aug 29 09:26:09 1999
} +++ tty.c Sat Mar 18 03
On Jun 22, 10:30am, Adrian Chadd wrote:
} Subject: Re: cvs commit: src/sys/contrib/softupdates softdep.h ffs_softdep
}
} [shifting conversation to -current .. ]
}
} On Thu, Jun 22, 2000, Anders Andersson wrote:
} on Tor, Jun 22, 2000 at 01:46:34pm +0900, Akinori -Aki- MUSHA wrote:
}
}
On Jun 22, 2:21am, Don Lewis wrote:
} Subject: Re: cvs commit: src/sys/contrib/softupdates softdep.h ffs_softdep
} On Jun 22, 10:30am, Adrian Chadd wrote:
} } Subject: Re: cvs commit: src/sys/contrib/softupdates softdep.h ffs_softdep
} }
} } [shifting conversation to -current
)
Stopped at Debugger+0x45: xchgl %ebx,in_Debugger.0
This is a known issue.
-- Forwarded message --
From: Don Lewis [EMAIL PROTECTED]
Subject: Re: LOR in NFS server
Date: Thu, 24 Apr 2003 21:20:56 -0700 (PDT)
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
On 24
On 19 Aug, Mark Sergeant wrote:
Hi All,
When trying to compile a kernel for my 8 cpu DELL 8450's I recieve an
extremly puzzling error, I get a bunch of errors when compiling a kernel
that has the following options in it...
options WITNESS
options NETSMB
options
On 3 Sep, Michael Bretterklieber wrote:
Hi,
buildworld fails (cvsup some minutes ago):
In file included from /usr/src/sys/cam/scsi/scsi_da.c:51:
/usr/src/sys/sys/taskqueue.h:33:2: #error no user-servicable parts
inside
mkdep: compile failed
The following patch works for me:
Index:
I just upgraded to a fresh version of -current and started getting a lot
of these vnode lock violation messages when running with the
DEBUG_VFS_LOCKS kernel option.
I only ever saw the stack trace below, but it is not obvious to me that
other callers of getdirtybuf() would not have the same
I've got an IBM ThinkPad R40 that hangs when I do a shutdown -p. It s
wedges after printing Powering system off using ACPI. The display
stays on, and judging by the heat, it seems that the CPU is on as well.
It doesn't respond to the keyboard, so I haven't been able to get into
DDB. The only
On 25 Sep, Nate Lawson wrote:
I've got an IBM ThinkPad R40 that hangs when I do a shutdown -p. It
wedges after printing Powering system off using ACPI.
Attempting to use 'acpiconf -s to suspend produces similar hangs.
Your system is halting correctly but powering off is failing. A cursory
On 26 Sep, To: [EMAIL PROTECTED] wrote:
On 25 Sep, Nate Lawson wrote:
To debug this, please boot a newer kernel with the ACPI_DEBUG option with
the following options in loader.conf:
debug.acpi.layer=ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS
debug.acpi.level=ACPI_LV_FUNCTIONS
You'll
On 2 Oct, Terry Lambert wrote:
Jens Rehsack wrote:
Kevin Oberman wrote:
Current has two major changes re speeding up fsck.
The most significant is the background operation of fsck on file
system with soft updates enabled. Because of the way softupdates
works, you are assured of
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstric
t-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fforma
t-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contri
b/dev/acpica -I/usr/src/sys/contrib/ipfilter
On 10 Oct, Dag-Erling Smørgrav wrote:
Doug White [EMAIL PROTECTED] writes:
On Fri, 10 Oct 2003, Garance A Drosihn wrote:
For the past week or so, I have been having a frustrating time
with my freebsd-current/i386 system. It is a dual Athlon
system. [...]
It would be useful to isolate
On 11 Oct, Steve Kargl wrote:
Upgrade tonight (7pm PST) and received the following
on rebooting
panic: pmap_zero_page: CMAP3 busy
Unfortunately, this system does not have a serial
console and the panic locked it up tight. Only
a hard reset brought the system back.
I was just about to
On 12 Oct, Anish Mistry wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I finally recvsupped today as some problems with my ata stuff was
fixed. Went through the normal buildworld/kernel progress and on
reboot of loading the new kernel, it loads the kernel and modules and
then as
On 14 Oct, Michal wrote:
Hello,
I have a problem with samba 3.0.
I had to reinstall FreeBSD-CURRENT after known problems with ATAng and
atapicam (beginning of September(?)), since then I can't set
net.inet.tcp.blackhole=2 in /etc/sysctl.conf. If I add the option to
sysctl then
samba will
On 21 Oct, Peter Jeremy wrote:
On Mon, Oct 20, 2003 at 11:45:21PM -0700, Terry Lambert wrote:
I've noticed a lot of bad problems with Hynix memory lately; your
mileage may vary. At Whistle we had a problem with memory with Gold
contacts, and didn't have any problems with the ones with Tin.
A
On 28 May, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Daniel O'Connor [EMAIL PROTECTED] writes:
: 2) You can't control where the module gets put - arguably this isn't a
: calamity, but I think it makes more sense for the modules to end up in
: /boot/modules, or some
I just stumbled across this vnode locking problem in procfs()
db tr
Debugger(c05215d4,c0520b94,c669b000,c0521615,e6d77764) at Debugger+0x54
vfs_badlock(c0521615,c0520b94,c669b000,c05b4340,c669b000) at vfs_badlock+0x45
assert_vop_locked(c669b000,c0520b94,c0520adf,358,c6a35400) at
On 16 Jun, Thorsten Schroeder wrote:
Hi,
On Mon, 15 Jun 2003, Chris Shenton wrote:
[...] qmail is run under daemontools and all work fine (the configuration
is 2 years old!), but when I delivery the first mail (localy or remote)
the qmail-send process fire up to 100% of CPU
On 16 Jun, Tim Robbins wrote:
On Mon, Jun 16, 2003 at 04:09:51PM +1000, Tim Robbins wrote:
On Sun, Jun 15, 2003 at 08:43:15PM -0400, Chris Shenton wrote:
I've been running qmail for years and like it, installed pretty much
per www.LifeWithQmail.org. My main system was running FreeBSD
On 16 Jun, I wrote:
On 16 Jun, Tim Robbins wrote:
This looks like a bug in the named pipe code. Reverting
sys/fs/fifofs/fifo_vnops.c to the RELENG_5_0 version makes the problem go
away. I haven't tracked down exactly what change between RELENG_5_0 and
RELENG_5_1 caused the problem.
Looks
On 16 Jun, Bruce Evans wrote:
On Mon, 16 Jun 2003, Don Lewis wrote:
On 16 Jun, I wrote:
On 16 Jun, Tim Robbins wrote:
This looks like a bug in the named pipe code. Reverting
sys/fs/fifofs/fifo_vnops.c to the RELENG_5_0 version makes the problem go
away. I haven't tracked down exactly
On 16 Jun, Thorsten Schroeder wrote:
Hi,
On Sun, 15 Jun 2003, Don Lewis wrote:
I don't know what it could be - perhaps a problem with named pipes
(lock/trigger)?
You can find my ktrace output here: http://cs.so36.net/~ths/kdump.txt
Which version of fifo_vnops.c? If the problem
On 16 Jun, Thorsten Schroeder wrote:
Hi,
On Mon, 16 Jun 2003, Don Lewis wrote:
FreeBSD 5.1-CURRENT #1: Thu Jun 5 19:29:29 CEST 2003
fifo_vnops.c:
$FreeBSD: src/sys/fs/fifofs/fifo_vnops.c,v 1.87 2003/06/01 06:24:32 truckman Exp $
Try upgrading to 1.88 and applying this patch
On 16 Jun, Jesse Guardiani wrote:
I run qmail on my 4.8 servers.
For my sanity, is this a problem in 5.1-RELEASE, or in code after 5.1-RELEASE?
We haven't upgraded to 5.1 yet (and don't intend to for a while), but I thought
I'd ask since this bug would cripple our mail server.
It was
On 16 Jun, Bruce Evans wrote:
On Mon, 16 Jun 2003, Don Lewis wrote:
On 16 Jun, Bruce Evans wrote:
In my review of 1.87, I forgot to ask you how atomic the close is with part
of it moved out to fifo_inactive(). I think it's important that all
traces of the old open have gone away (as far
On 16 Jun, Chris Shenton wrote:
(I don't know if this has any relation to the problems I reported
yesterday with qmail-send consuming 100% cpu after 5.0 to 5.1 upgrade.)
I doubt it. I checked in a fix for this problem today so you should get
the fix when you next cvsup.
After booting
The FILE_LOCK() implementation uses pool mutex under the hood, which
means it should only be used as a leaf level mutex. The fdrop_locked()
code wants to be called with FILE_LOCK() held, but the fdrop_locked()
implementation calls mtx_lock(Giant) before calling FILE_UNLOCK(). In
addition to
On 17 Jun, Alfred Perlstein wrote:
* Don Lewis [EMAIL PROTECTED] [030617 12:00] wrote:
It's not legal to attempt to aquire Giant in fdrop_locked(), while
FILE_LOCK() is held. The problem is that FILE_LOCK uses the mutex pool,
which should only be used for leaf mutexes.
It also looks like
On 17 Jun, Robert Watson wrote:
On Tue, 17 Jun 2003, Don Lewis wrote:
The FILE_LOCK() implementation uses pool mutex under the hood, which
means it should only be used as a leaf level mutex. The fdrop_locked()
code wants to be called with FILE_LOCK() held, but the fdrop_locked
On 17 Jun, Chris Shenton wrote:
Don Lewis [EMAIL PROTECTED] writes:
I doubt it. I checked in a fix for this problem today so you should get
the fix when you next cvsup.
Yup, many thanks.
Can you break into ddb and do a ps to find out what state all the
processes are in?
I'm
On 17 Jun, Alfred Perlstein wrote:
* Don Lewis [EMAIL PROTECTED] [030617 13:06] wrote:
On 17 Jun, Alfred Perlstein wrote:
* Don Lewis [EMAIL PROTECTED] [030617 12:00] wrote:
It's not legal to attempt to aquire Giant in fdrop_locked(), while
FILE_LOCK() is held. The problem
On 17 Jun, Chris Shenton wrote:
Don Lewis [EMAIL PROTECTED] writes:
If you have another machine and a null modem cable you can redirect the
system console of the machine to be debugged to a serial port and run
some comm software on the other machine so that you can capture all the
output
When I was attempting to debug a system deadlock problem where the
culprit process was sleeping on a pool mutex, I noticed that show
witness in ddb doesn't report anything about this particular mutex
flavor. I discovered that witness doesn't monitor these mutexes because
mtx_pool_setup() calls
On 18 Jun, Chris Shenton wrote:
Don Lewis [EMAIL PROTECTED] writes:
Try the very untested patch below ...
RCS file: /home/ncvs/src/sys/kern/uipc_syscalls.c,v
When I do the patch, how much of the OS do I need to rebuild, just do
a make install in the .../src/sys/kern dir? Rebuild the OS
On 18 Jun, Chris Shenton wrote:
Don Lewis [EMAIL PROTECTED] writes:
Try the very untested patch below ...
RCS file: /home/ncvs/src/sys/kern/uipc_syscalls.c,v
retrieving revision 1.150
Try the very untested patch below ...
diff -u -r1.150 uipc_syscalls.c
--- uipc_syscalls.c 12 Jun 2003
On 18 Jun, I wrote:
When I was attempting to debug a system deadlock problem where the
culprit process was sleeping on a pool mutex, I noticed that show
witness in ddb doesn't report anything about this particular mutex
flavor. I discovered that witness doesn't monitor these mutexes because
On 19 Jun, Stefan Eßer wrote:
On 2003-06-18 20:41 -0700, Don Lewis [EMAIL PROTECTED] wrote:
On 18 Jun, Chris Shenton wrote:
Don Lewis [EMAIL PROTECTED] writes:
Try the very untested patch below ...
[ snip ]
Tried it, rebuilt kernel, rebooted, no affect :-(
You were correct about
I've been running with the patch below for a little while now. It
helped me find a situation where a thread attemped to grab a pool
mutex while it already held one, which I suspect could have caused a
deadlock in certain circumstances. In any case, this was illegal
because these mutexes are only
The patch below enhances the mutex pool code to support the creation and
use of multiple mutex pools. It creates one pool of sleep mutexes with
the MTX_NOWITNESS flag for use in building higher level (sx and lockmgr)
locks. It also creates another pool without MTX_NOWITNESS for general
purpose
I've been updating my current system a lot recently, and twice in the
last couple of weeks, the disks have not been properly synced before the
system reboots. I've been doing the usual
make buildworld
make buildkernel
make installkernel
shutdown -r now
make
On 13 Jul, Jeff Walters wrote:
On Saturday 12 July 2003 11:24 pm, Sean Kelly wrote:
syncing disks, buffers remaining... 54 54 54 54 54 54 54 54 54 54 54 54
54 54 54 54 54 54 54 54 giving up on 54 buffers
Uptime: 6m42s
Terminate ACPI
Rebooting...
Each time this has happened, fsck
On Sep 9, 12:05am, Matthew Thyer wrote:
} Subject: Re: /usr/local/etc/rc.d and /etc/rc.d
} Neil Blakey-Milner wrote:
} I'd prefer a dependency based system. (cf. Eivind Eklund's newrc, at
} http://people.FreeBSD.org/~eivind/newrc.tar.gz)
How does this compare with what NetBSD implemented?
}
On Sep 29, 11:30am, Greg Lehey wrote:
} Subject: Repeated panic out of chgsbsize
} In the past couple of days, I've had a couple of panics out of chgsbsize:
}
} (kgdb) bt
[ snip ]
} #12 0xc01cbac9 in panic (fmt=0xc0356920 "reducing sbsize: lost count, uid = %d") at
On 18 Jun, Alfred Perlstein wrote:
* Nate Lawson [EMAIL PROTECTED] [020618 12:17] wrote:
As with others on the list, I've been getting a lot of witness complaints:
../../../vm/uma_core.c:1327: could sleep with process lock locked from
../../../kern/kern_prot.c:511
On 6 Jul, Paul Richards wrote:
Let's start with a premise: No-one running current is using it for
anything other than developing FreeBSD.
Given that premise, then there shouldn't be anything in /usr outside of
/usr/local, that wasn't put there by make world. Likewise the same
should be
On 5 Jul, Georg-W. Koltermann wrote:
Am Mi, 2002-07-03 um 17.31 schrieb David O'Brien:
On a 27-June-2002 23:02:00 UTC system (just before ipfw2 went in,
pre-KSE3), dump will not complete dumping more than 5GB. At that point
it stops responding properly to ^T, which should give DUMP: 47.52%
On 5 Jul, Georg-W. Koltermann wrote:
Am Mi, 2002-07-03 um 17.31 schrieb David O'Brien:
On a 27-June-2002 23:02:00 UTC system (just before ipfw2 went in,
pre-KSE3), dump will not complete dumping more than 5GB. At that point
it stops responding properly to ^T, which should give DUMP: 47.52%
On 7 Jul, Jeff Roberson wrote:
On Sat, 6 Jul 2002, Jeff Roberson wrote:
- Use 'options DEBUG_VFS_LOCKS' instead of the DEBUG_ALL_VFS_LOCKS
environment variable to enable the lock verifiction code.
This was previously disabled because our locking was so bad that we could
not boot
Sshd on my current box is logging messsages about
sshd[pid]: /var/log/lastlog: permission denied on my recently updated
-current box. The permission on this file are the defaults. Could this
be a side effect of the new privilege separation stuff?
To Unsubscribe: send mail to [EMAIL PROTECTED]
On 7 Jul, Ian Dowse wrote:
In message [EMAIL PROTECTED], Don Lewis writes:
I was finally finally able to reproduce this by creating a large file
before doing the dump. Dump(8) is *very* hosed. The UFS2 import broke
it's ability to follow multiple levels of indirect blocks.
Thanks
This error showed up in my logs this morning while I was building some
ports on a uni-processor box. I'm running a version of -current from
July 7 about 1 AM PDT.
Jul 7 07:47:09 scratch kernel: lock order reversal
Jul 7 07:47:09 scratch kernel: 1st 0xcabf7980 pipe mutex (pipe mutex) @
This should be lots of fun for someone to fix ...
=== bin/ps
cc -O -pipe -DLAZY_PS -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wformat=2
-Wno-format-extra-args -Werror -c /usr/src/bin/ps/fmt.c
cc -O -pipe -DLAZY_PS -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wformat=2
On 7 Jul, Jeff Roberson wrote:
On Sat, 6 Jul 2002, Jeff Roberson wrote:
Log:
- Use 'options DEBUG_VFS_LOCKS' instead of the DEBUG_ALL_VFS_LOCKS
environment variable to enable the lock verifiction code.
If you have a crash test box I would appreciate it if you would enable
this
On 8 Jul, Anthony Jenkins wrote:
I've been looking at the pcm code and I can see where it locks, then allocates
memory with the M_WAITOK flag thing. I'm wondering if there's a standard
procedure for fixing these... would I just nail down the malloc to a
non-sleepable one?
Only if the
I was studying the following DEBUG_VFS_LOCKS panic and noticed something
bothersome about the ordering of the code in coredump(). It looked to
me like it made more sense to verify that the file was something that
was valid to dump to before doing the vn_start_write() stuff.
Rearranging the code
On 10 Jul, Alex Zepeda wrote After the rude awakening that I was after all running
current, I've
finally turned on the WITNESS related options for my kernel (and boy is it
wickedly unstable as of now).
I haven't had any instability problems in a while on my UP box.
Anyways.. is there any
On 9 Jul, John Baldwin wrote:
On 09-Jul-2002 Don Lewis wrote:
I recently started seeing the warning message:
/usr/src/sys/vm/uma_core.c:1332: could sleep with kernel linker locked
from /usr/src/sys/kern/kern_linker.c:1797
at boot time on my -current box. It appears to be related
A box running this morning's -current compiled with DEBUG_VFS_LOCKS
coughed up this error part way through a cvs update of the ports tree.
VOP_GETVOBJECT: x is not locked but should be
The stack trace is:
getnewvnode() + 0x182
ffs_vget() + 0x73
ufs_lookup() + 0x10df
vfs_vnoperate() + 0x13
On 10 Jul, Dan Nelson wrote:
I see this one once every 10 seconds or so:
../../../vm/uma_core.c:1332: could sleep with inp locked from
../../../netinet/tcp_subr.c:935
../../../vm/uma_core.c:1332: could sleep with tcp locked from
../../../netinet/tcp_subr.c:928
I've never seen that one.
On 10 Jul, Alex Zepeda wrote:
On Wed, Jul 10, 2002 at 02:43:54AM -0700, Don Lewis wrote:
I haven't had any instability problems in a while on my UP box.
Seems like the UP kernels are more unstable for me. Go figure.
../../../vm/uma_core.c:1332: could sleep with process lock locked
On 10 Jul, Alex Zepeda wrote:
On Wed, Jul 10, 2002 at 01:34:50PM -0700, Don Lewis wrote:
../../../vm/uma_core.c:1332: could sleep with inp locked from
../../../netinet/tcp_subr.c:935
../../../vm/uma_core.c:1332: could sleep with tcp locked from
../../../netinet/tcp_subr.c:928
I've
On 11 Jul, Josef Karthauser wrote:
On Thu, Jul 11, 2002 at 11:35:46AM +0100, Josef Karthauser wrote:
I tracked it down to tcp_getcred() calling SYSCTL_OUT(), which can
potentially block, before releasing the locks tcp_getcred() is holding.
This routine is used by the net.inet.tcp.getcred
On 11 Jul, Josef Karthauser wrote:
On Thu, Jul 11, 2002 at 04:01:08AM -0700, Don Lewis wrote:
On 11 Jul, Josef Karthauser wrote:
I get it whenever cron kicks of a cvsup also.
The cvsup server may also be making ident queries.
If it is, it is making lots and lots of them, at a rate
On 7 Jul, Don Lewis wrote:
This error showed up in my logs this morning while I was building some
ports on a uni-processor box. I'm running a version of -current from
July 7 about 1 AM PDT.
Jul 7 07:47:09 scratch kernel: lock order reversal
Jul 7 07:47:09 scratch kernel: 1st 0xcabf7980
On 11 Jul, walt wrote:
I just finished compiling and installing openoffice on yesterday's
-current, thanks to the stat.h patch from Bruce.
It even runs properly for me if I access my previously setup home
directory NFS mounted from a stable box. Also, it successfully reads a
Word document
On 11 Jul, Don Lewis wrote:
On 7 Jul, Don Lewis wrote:
Jul 7 07:47:09 scratch kernel: lock order reversal
Jul 7 07:47:09 scratch kernel: 1st 0xcabf7980 pipe mutex (pipe mutex) @
/usr/src/sys/kern/sys_pipe.c:451
Jul 7 07:47:09 scratch kernel: 2nd 0xc0474300 sigio lock (sigio lock
On 11 Jul, Don Lewis wrote:
On 10 Jul, Alex Zepeda wrote:
On Wed, Jul 10, 2002 at 01:34:50PM -0700, Don Lewis wrote:
../../../vm/uma_core.c:1332: could sleep with inp locked from
../../../netinet/tcp_subr.c:935
../../../vm/uma_core.c:1332: could sleep with tcp locked from
On 12 Jul, Alex Zepeda wrote:
On Wed, Jul 10, 2002 at 01:36:46PM -0700, Don Lewis wrote:
It'll drop into ddb every time you get a witness error and you'll have
to tell ddb to continue. This could be a might annoying if you are
getting errors ever ten seconds ...
I'm seeing
What was the original panic message, the one where uma_core.c prints the
name of the lock being held and where it was locked?
On 12 Jul, Alex Zepeda wrote:
* $FreeBSD: src/sys/kern/vfs_bio.c,v 1.319 2002/07/10 17:02:28 dillon Exp $
* $FreeBSD: src/sys/kern/vfs_syscalls.c,v 1.267 2002/07/02
On 13 Jul, zipzippy wrote:
On Sat, Jul 13, 2002 at 07:28:43PM -0700, Don Lewis wrote:
What was the original panic message, the one where uma_core.c prints the
name of the lock being held and where it was locked?
Any way to determine this post-mortem? I woke up and the system had
On 16 Jul, Dag-Erling Smorgrav wrote:
Andrew Gallatin [EMAIL PROTECTED] writes:
Just clear panicstr (w panicstr 0) when you drop into
the debugger on a panic.
No luck. However, I added an ASSERT_VOP_LOCKED() to vn_statfile(),
and confirmed that vn_lock() fails to lock the vnode.
The tcp_getcred(), tcp6_getcred(), udp_getcred(), udp6_getcred() look
like a bad example of mostly duplicated code caused by cut and paste
programming. By passing a pointer to the inpcbinfo structure as an
argument to the sysctl hander it is possible to combine the use a common
handler for the
On 19 Aug, Alex Zepeda wrote:
../../../kern/kern_synch.c:454: sleeping with mntvnode locked from
../../../kern/vfs_subr.c:2789
panic: from debugger
cpuid = 0; lapic.id =
---
GNU gdb 5.2.0 (FreeBSD) 20020627
This GDB was configured as i386-undermydesk-freebsd...
#10
On 21 Aug, Martin Blapp wrote:
Hi,
Try to compile the entire system on another box, install it then
on the CURRENT target box, and try again !
Bye the way, after 6 rounds, I see now SIG4 and SIG11 too :-/
To bad - so it's definitly data corruption in CURRENT.
Asus Board P4B533-V,
On 21 Aug, Don Lewis wrote:
On 21 Aug, Martin Blapp wrote:
Hi,
Try to compile the entire system on another box, install it then
on the CURRENT target box, and try again !
Bye the way, after 6 rounds, I see now SIG4 and SIG11 too :-/
To bad - so it's definitly data corruption
On 22 Aug, Mark Santcroos wrote:
On Thu, Aug 22, 2002 at 09:43:45AM +0200, Martin Blapp wrote:
Thats memory corruption. I'm also not able anymore
to make 10 buildworlds (without -j, that triggers
panics in pmap code).
Bye the way, I'm experiencing this since about 4-5 months.
All
On 22 Aug, Soeren Schmidt wrote:
However, this kind of problem in most cases spells bad HW to me,
ie subspec RAM, poor powersupply, badly cooled CPU, overclocking etc etc...
My motherboard chipset supports ECC RAM and I have ECC RAM installed. I
upgraded to an expensive Antec power supply
On 22 Aug, Terry Lambert wrote:
Alternatively, rather than those options, try losing 512M of
the RAM... I note they are all 1G boxes.
When I first put this system together several months ago, I only
installed the first 512M of RAM and the problem was much worse. I only
had about a 50% chance
On 31 Aug, Kris Kennaway wrote:
panic: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x4
Looks like a NULL structure pointer dereference. It looks like the
access is four bytes into the structure.
#7 0xc021d91f in
On 31 Aug, Kris Kennaway wrote:
Another page fault in umount
I haven't seen any reports of this one before.
#6 0xc0399a48 in calltrap () at {standard input}:98
#7 0xc029198d in vflush (mp=0xc5e6, rootrefs=0, flags=2) at vnode_if.h:309
#8 0xc0200eaa in devfs_unmount (mp=0xc5e6,
On 1 Sep, Alexander Kabaev wrote:
GCC 3.2.1-pre is now in the tree. Please let me know if you see any
problems recompiling your world/kernel.
I haven't seen any other reports of this problem. I'm upgrading from
a September 1st version of -current.
cc -O -pipe -DIN_GCC -DHAVE_CONFIG_H
On 31 Aug, Kris Kennaway wrote:
Another one. I have the cores if anyone needs to look at
them..otherwise I'll stop posting these for now.
Kris
panic: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x4
fault code =
, Don Lewis wrote:
On 1 Sep, Alexander Kabaev wrote:
GCC 3.2.1-pre is now in the tree. Please let me know if you see any
problems recompiling your world/kernel.
I haven't seen any other reports of this problem. I'm upgrading from
a September 1st version of -current.
cc -O -pipe -DIN_GCC
On 7 Sep, Manfred Antar wrote:
At 12:23 AM 9/7/2002 -0700, Terry Lambert wrote:
Peter Wemm wrote:
You will need to either add:
options COMPAT_AOUT
to your kernel config when you next rebuild, or do a 'kldload aout'
when you want to run an old a.out binary.
Is this going to be turned on be
nfs_link() contains the following code:
/*
* Push all writes to the server, so that the attribute cache
* doesn't get out of sync with the server.
* XXX There should be a better way!
*/
VOP_FSYNC(vp, cnp-cn_cred, MNT_WAIT, cnp-cn_thread);
The
On 9 Sep, Don Lewis wrote:
nfs_link() contains the following code:
/*
* Push all writes to the server, so that the attribute cache
* doesn't get out of sync with the server.
* XXX There should be a better way!
*/
VOP_FSYNC(vp, cnp
On 9 Sep, Robert Watson wrote:
On Mon, 9 Sep 2002, Don Lewis wrote:
I think we can probably just lock and unlock vp around the call to
VOP_FSYNC() ...
What I'd actually like to do is lock vp on going in to the VOP. I need to
grab the lock in the link() code anyway to do the MAC check
On 9 Sep, Robert Watson wrote:
What I'd actually like to do is lock vp on going in to the VOP. I need to
grab the lock in the link() code anyway to do the MAC check. UFS and
others all immediately lock the vnode on entry anyway...
Here's a patch to implement this. It compiles and seems
On 10 Sep, Bruce Evans wrote:
The locking changes in union_link() need a thorough review,
though the light testing of that I performed didn't turn up any
glaring problems.
The changes are obviously just cleanups for leaf file systems, but I
wonder why everything wasn't
On 10 Sep, Bruce Evans wrote:
On Tue, 10 Sep 2002, Don Lewis wrote:
On 10 Sep, Bruce Evans wrote:
The changes are obviously just cleanups for leaf file systems, but I
wonder why everything wasn't always locked at the top. Could it have
been because locking all the way down is harmful
1 - 100 of 388 matches
Mail list logo
