On Jan 20, 5:41pm, Alfred Perlstein wrote:
} Subject: half-fix for stream.c
} you can find it at:
}
} http://www.freebsd.org/~alfred/tcp_fix.diff
Don't you want to defer the checksum even further (after the bogus
packets have been dropped)? It doesn't look like the change you
made will save an
On Jan 22, 5:04pm, Alex Zepeda wrote:
} Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip
} What if we began to use bzip2 instead of gzip for things like man pages,
} or releases, etc?
Doesn't bzip2 require a lot more memory for decompression? As I
recall, someone ment
On Feb 21, 7:51pm, Alex Le Heux wrote:
} Subject: Crashing netscape?
} Hi,
}
} Am I the only one who's experiencing an amzing amount of crashes on
} Netscape?
}
} It's been going on for quite some time now (months), upgrading Netscape or
} switching from the Linux to the FreeBSD to the BSDI ver
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 pro
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 and
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 floppi
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 requireme
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 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
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
} > +
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 .. ]
} }
} } On
On Mar 3, 9:20pm, John Baldwin wrote:
} Subject: RE: Using serial console to debug system hangs ...
}
} On 04-Mar-01 The Hermit Hacker wrote:
} >
} > Wow, that was painful ... after 2 hrs, I got as far as:
}
} Yeah, it spews out a lot of crap. :-/ You prolly want to use a 115200 serial
} cons
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
../../kern/kern_shutdown.c:
On Nov 4, 11:54am, Kent Stewart wrote:
} Subject: Re: installworld failure - libsdbm.a
}
}
} Steven Farmer wrote:
} >
} > After this morning's cvsup and buildworld, installworld failed trying
} > to build libsdbm.a. I worked around the problem by adding chmod to
} > Makefile.inc1 as shown belo
On Jan 21, 9:40pm, Warner Losh wrote:
} Subject: Re: keymaps
} In message <199901220043.laa22...@lightning.itga.com.au> Gregory Bond writes:
} : my vote: A version of the standard keymap with CapsLock and LeftCtl
} : functions swapped so the control key is under my left finger like
} : God intende
On Jan 26, 12:20pm, Dag-Erling Smorgrav wrote:
} Subject: Re: Heads up! New swapper and VM changes have been committed to -
} Brian Feldman writes:
} > On 24 Jan 1999, Dag-Erling Smorgrav wrote:
} > > These are dynamically linked, and will automatically pick up the new
} > > libkvm.
} > But (most
On Jan 29, 12:05pm, Sheldon Hearn wrote:
} Subject: Re: btokup().. patch to STYLE(9) (fwd)
} The reason I'm interested in this (now tiresome) thread is that I'd much
} rather have to read
}
} /*
}* Bail out if the time left to next transaction is less than
}* the duration of
On Jan 29, 9:13am, Poul-Henning Kamp wrote:
} Subject: Re: btokup().. patch to STYLE(9) (fwd)
}
} On the other hand style(9) should still firmly outlaw stuff like:
}
} /* wait 10 ms */
} if (((error = tsleep((caddr_t)dev, PPBPRI | PCATCH,
} "ppbpoll", hz/100)) != EWOULDBLOC
On Jan 29, 8:34am, Brian Somers wrote:
} Subject: Re: btokup().. patch to STYLE(9) (fwd)
}
} My argument is that this sort of thing gets out of hand. I've seen
} things such as
}
} if (((a == b) || (c == d)))
}
} where a, b, c & d are just simple variables - there are so many
} redundant b
On Feb 19, 2:15pm, "Kenneth D. Merry" wrote:
} Subject: Re: Slow seq. write on Seagate ST36530N
}
} The Write Cache Enable (WCE) bit is in mode page 8. To check it:
}
} camcontrol modepage -n da -u 1 -v -m 8
}
} To edit the mode page:
}
} camcontrol modepage -n da -u 1 -v -m 8 -e
To make thi
21660,0) at ithread_loop+0x11c
> fork_exit(c0221660,c0b87180,c891ad48) at fork_exit+0xab
> fork_trampoline() at fork_trampoline+0x8
> --- trap 0x1, eip = 0, esp = 0xc891ad7c, ebp = 0 ---
> Debugger("witness_lock")
> Stopped at Debugger+0x45: xchgl %ebx,in_Debugger.
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:
Inde
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 proble
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 faili
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_FUNCTION
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
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 -I/usr/src/
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 usefu
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 abo
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
> th
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
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.
I don't believe I've seen any reports of this particular lock order
reversal. I got it by pointing truss at syslogd. My kernel and world
were built from a cvsup run slightly before Fri Nov 7 14:50:18 PST
2003.
Sleeping on "stopevent" with the following non-sleepable locks held:
exclusive slee
I've been seeing some wierd things for many months when using a serial
console on my -CURRENT box. I finally had a chance to take a closer
look today.
It looks like the problem is some sort of interference between kernel
output to the console and userland writes to /dev/console. I typically
see
On 9 Nov, Bruce Evans wrote:
> On Sat, 8 Nov 2003, Don Lewis wrote:
>
>> I've been seeing some wierd things for many months when using a serial
>> console on my -CURRENT box. I finally had a chance to take a closer
>> look today.
>>
>> It looks like
On 9 Nov, Bruce Evans wrote:
> For a non-half-baked fix, do somethng like:
> - never block in ttymsg(), but always wait for output to drain using
> tcdrain() in a single child process. It's probably acceptable for
> this to not report errors to ttymsg()'s caller.
> - limit children better.
On 9 Nov, Don Lewis wrote:
> On 9 Nov, Bruce Evans wrote:
>> On Sat, 8 Nov 2003, Don Lewis wrote:
>>> This is totally consistent until I "kill
>>> -HUP" syslogd, which I believe causes syslogd to close and open
>>> /dev/console, after which the sy
I just got one of these shortly after I rebooted my November 7th
-CURRENT box. DDB doesn't show much interesting.
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xbc04d753
fault code = supervi
On 9 Nov, I wrote:
> I just got one of these shortly after I rebooted my November 7th
> -CURRENT box. DDB doesn't show much interesting.
>
> kernel trap 12 with interrupts disabled
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address = 0xbc04
On 10 Nov, Lukas Ertl wrote:
> Hi,
>
> is there a known problem with named pipes in -CURRENT?
>
> The following shell script freezes a machine in several minutes and needs
> a power cycle. You can see the increasing memory in vmstat -z (unpcb) and
> netstat -u. The kernel is FreeBSD 5.1-CURRENT
On 10 Nov, Lukas Ertl wrote:
> On Mon, 10 Nov 2003, Don Lewis wrote:
>
>> On 10 Nov, Lukas Ertl wrote:
>> >
>> > The following shell script freezes a machine in several minutes and needs
>> > a power cycle. You can see the increasing memory in vmstat -z (
On 11 Nov, Lukas Ertl wrote:
> On Tue, 11 Nov 2003, Lukas Ertl wrote:
>
>> Unfortunately, we are still seeing a problem here: we are running uvscan
>> (virus scanner), and while running it we are still seeing increasing unpcb
>> usage and orphaned unix domain sockets.
>>
>> We added some debug pri
On 11 Nov, Don Lewis wrote:
> On 11 Nov, Lukas Ertl wrote:
>> Sorry, I probably missed an important part: we're creating the FIFOs on
>> nullfs mounts - the test script works great on plain UFS mounts, but the
>> null layer seems to VREF the vnode once again, so v_us
On 31 Oct, Kelley Reynolds wrote:
> --- Original Message ---
> From: Matt Smith <[EMAIL PROTECTED]>
> Sent: Fri, 31 Oct 2003 08:55:49 +
> To: Robert Watson <[EMAIL PROTECTED]>
> Subject: Re: Still gettnig NFS client locking up
>
>> Robert Watson wrote:
>> > On Tue, 28 Oct 2003, Soren Schmidt w
On 15 Nov, Robert Watson wrote:
>
> On Sat, 15 Nov 2003, Andy Farkas wrote:
>
>> These messages spew onto my console and into syslogd once every second:
>
> Heh. Sounds like your box is having a really bad day, we'll see if we
> can't get it fixed up over the next couple of weeks as things sett
On 11 Nov, Lukas Ertl wrote:
> On Tue, 11 Nov 2003, Lukas Ertl wrote:
>
>> Unfortunately, we are still seeing a problem here: we are running uvscan
>> (virus scanner), and while running it we are still seeing increasing unpcb
>> usage and orphaned unix domain sockets.
>>
>> We added some debug pri
I just ran into this while running portupgrade.
VOP_GETATTR: 0xc741e000 is not locked but should be
Debugger("Lock violation.
")
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
db> tr
Debugger(c08bf9aa,c9749c78,c741e000,c08bf9eb,e820c984) at Debugger+0x55
vfs_badlock(c08bf9eb,c9749c78,c
On 18 Nov, Lukas Ertl wrote:
> On Tue, 18 Nov 2003, Nate Lawson wrote:
>> This excerpt from truckman@'s asl shows that 4 Cx states are only
>> available when the AC adapter is not attached. (The C*NA memory addresses
>> appear to be managed by the BIOS and not the AML but the PSR access is
>> cle
On 18 Nov, Garance A Drosihn wrote:
> At 8:07 AM -0500 11/18/03, [EMAIL PROTECTED] wrote:
>
>> If there hadn't been a noticed increase in cost by using
>> all-shared-libs, then the measurements were done
>> incorrectly. If the decision is made based upon allowing
>> for 1.5X (
On 18 Nov, Robert Watson wrote:
> (2) Shells again, because they will be fork()d and exec()d frequently
> during heavily scripted activities, such as system boot, periodic
> events, large make jobs, etc. And presumably the only shell of
> interest is sh, although some of the supportin
I was trying to figure out why the VOP_UNLOCK() call in null_lookup()
was violating a vnode locking assertion, so I tossed a bunch of
ASSERT_VOP_LOCKED() calls into null_lookup(). I found something I don't
understand ...
ASSERT_VOP_LOCKED(dvp, "null_lookup 1");
if ((flags & ISLAST
On 23 Nov, I wrote:
> I was trying to figure out why the VOP_UNLOCK() call in null_lookup()
> was violating a vnode locking assertion, so I tossed a bunch of
> ASSERT_VOP_LOCKED() calls into null_lookup(). I found something I don't
> understand ...
>
> ASSERT_VOP_LOCKED(dvp, "null_lookup
On 25 Nov, Daniel O'Connor wrote:
> On Tuesday 25 November 2003 11:52, Dan Nelson wrote:
> > > I'd greatly prefer that the the dynamic root default be backed out
>> > > until a substantial amount of this performance can be recovered.
>> >
>> > What _REAL WORLD_ task does this slow down?
>>
>> Try
On 25 Nov, Artur Poplawski wrote:
> Artur Poplawski <[EMAIL PROTECTED]> wrote:
>
>> Hello,
>>
>> On a 5.1-RELEASE and 5.2-BETA machines I have
On 25 Nov, Don Lewis wrote:
> On 25 Nov, Artur Poplawski wrote:
>> Artur Poplawski <[EMAIL PROTECTED]> wrote:
>>
>>> Hello,
>>>
On 26 Nov, Stefan Ehmann wrote:
> I got the following panic twice when starting xawtv using 5.2 BETA (CVS
> from Oct 23)
> panic: blockable sleep lock (sleep mutex) sellck
> @/usr/src/sys/kern/sys_generic.c:1145
>
> I don't think it is directly related to bktr since the last commit there
> was ~3
On 27 Nov, Stefan Ehmann wrote:
> On Wed, 2003-11-26 at 08:33, Don Lewis wrote:
>> The problem is that selrecord() wants to lock a MTX_DEF mutex, which can
>> cause a context switch if the mutex is already locked by another thread.
>> This is contrary to what bktr_poll() w
It's a good thing that the value of MTX_DEF is 0 ;-)
This isn't a critical fix, but it probably should be done soon after the
code freeze is lifted to prevent the spread if infection via cut and
paste programming.
Index: dev/ata/ata-all.c
==
On 27 Nov, masta wrote:
> I'm able to reproduce a panic on demand. I simply insert my IBM Microdrive
> CF card into the PCM/CIA slot of the laptop, which is a Dell CPi, and
> panic! I build a kernel.debug in the hope somebody can help me analyze the
> back-trace.
>
> Oh by the way, the sources fro
On 30 Nov, Stefan Ehmann wrote:
> On Fri, 2003-11-28 at 01:02, Don Lewis wrote:
>> On 27 Nov, Stefan Ehmann wrote:
>> > On Wed, 2003-11-26 at 08:33, Don Lewis wrote:
>> >> The problem is that selrecord() wants to lock a MTX_DEF mutex, which can
>> >> caus
On 30 Nov, Stefan Ehmann wrote:
> On Sun, 2003-11-30 at 11:13, Stefan Ehmann wrote:
>> This happens to me several times a day (cvsup from yesterday didn't
>> change anything). The panic message is always the same, the backtrace is
>> different though (but always seems to be file system related in s
Can you reproduce this problem without bktr?
> #6 0xc06743d8 in calltrap () at {standard input}:94
> #7 0xc0505b53 in _mtx_lock_flags (m=0x0, opts=0,
> file=0xc06bfc1d "/usr/src/sys/kern/kern_lock.c", line=228)
> at /usr/src/sys/kern/kern_mutex.c:214
> #8 0xc0502b54 in lockmgr (lkp=0xc
On 1 Dec, Stefan Ehmann wrote:
> On Mon, 2003-12-01 at 01:10, Don Lewis wrote:
>> Can you reproduce this problem without bktr?
>>
>
>> You are getting a double panic, with the second happening during the
>> file system sync. The code seems to be be tripping ove
On 1 Dec, Roger Hardiman wrote:
> Hi
>
> Please can someone commit the bktr patch for me to fix 5.2-BETA
> (as long as re@ approve). I don't have the resources.
If you're happy with the patch, I'll pursue re@ approval for the commit.
>> I'm not suprised that I haven't heard from him because thi
On 1 Dec, Roger Hardiman wrote:
> Hi
>
> Please can someone commit the bktr patch for me to fix 5.2-BETA
> (as long as re@ approve). I don't have the resources.
The patch has been committed with re@ approval.
___
[EMAIL PROTECTED] mailing list
http://l
On 1 Dec, Stefan Ehmann wrote:
> On Mon, 2003-12-01 at 01:10, Don Lewis wrote:
>> Can you reproduce this problem without bktr?
>>
>
>> You are getting a double panic, with the second happening during the
>> file system sync. The code seems to be be tripping ove
On 2 Dec, Josh Paetzel wrote:
> I'm trying to install FreeBSD on a Dual Pentium Pro 200mhz 512K cache system and I
> am getting the
> following error:
>
> CD Loader 1.01
>
> Building the boot loader arguements
> Looking up /BOOT/LOADER... Found
> Relocating the loader and the BTX
> Starting th
On Apr 15, 12:14pm, Peter Jeremy wrote:
} Subject: Re: swap-related problems
} Mikhail Teterin wrote:
} > Worse then that,
} >it may be possible to use it at malloc time, but unless your program
} >runs and touches every page, the memory may not be available later.
}
} If you run and touch every
On Apr 14, 4:40pm, Chuck Robey wrote:
} Subject: Re: swap-related problems
} On Wed, 14 Apr 1999, Anthony Kimball wrote:
} > Well, it's only needed if you want to be able to reliably execute ANSI
} > C code according to spec. I personally don't care. I'd be surprised
} > if core didn't though.
On Apr 29, 7:41pm, Mike Smith wrote:
} Subject: Re: ppbus causes hangs?
}
} Try setting the flags on the 'ppc' device to 0x40 and _please_ report
} the results.
I also ran into this problem with a 4/30/1999 version of 3.1-stable
on a Dell Dimension XPS R400. The 0x40 flag fixed the problem.
B
On May 2, 11:58pm, Don Lewis wrote:
} Subject: Re: ppbus causes hangs?
} On Apr 29, 7:41pm, Mike Smith wrote:
} } Subject: Re: ppbus causes hangs?
} }
} } Try setting the flags on the 'ppc' device to 0x40 and _please_ report
} } the results.
}
} I also ran into this problem with a
Could someone give the attached patch a try in -current? It fixes the
file descriptor leak that the KKIS.05051999.003b exploit causes. This
fix seems to work fine in -stable. I'd like to commit it to the current
tree and merge it into -stable before the 3.2 code freeze.
Index: uipc_usrreq.c
=
On Jun 5, 5:43pm, John-Mark Gurney wrote:
} Subject: Re: RE: net.inet.tcp.always_keepalive on as default ?
} Garrett Wollman scribbled this message on Jun 5:
} > < said:
} >
} > > FWIW, I think only a fool would want a computer to NOT drop dead
connections.
} > > Any "connection" that doesn't re
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,
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 assert_vop_locked
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%
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
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 proble
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 t
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
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/0
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 b
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
&g
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 5.1-C
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 vi
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
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 F
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
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_
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 s
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 "ma
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
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 be
1 - 100 of 401 matches
Mail list logo
