On Wed, 2 Apr 2003, Bosko Milekic wrote:
BM For what concerns DONTWAIT, you should theoretically be allowed to
BM hold a driver lock. But again, there may be a problem. Specifically,
BM I see that UMA code has some explicit Giant acquires/frees in certain
BM places. When the UMA code gets
The following patches at http://people.freebsd.org/~mtm
remove process resource limits out from under Giant. I have been bouncing
them off jhb for a while now, and I think they are ready. I would appreciate
a review/testing
There are 4 incremental patches for your reviewing pleasure :-)
err http://people.freebsd.org/~mtm/limits
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Thu, Apr 03, 2003 at 02:31:01AM -0500, Jeff Roberson
[EMAIL PROTECTED] wrote:
Interactivity is still worse under ULE. It's quite noticeable and I
tested it on two SMP boxes by running two simple loops in kind of:
for ((;;)); do let $((4+4)); done # this is bash specific
The loops ran
How to fix problem with floppies 1457664 bytes?
P.S. please, CC me
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
I just got a panic. As I have never had one before, I don't know what to
do. It's on another system so I don't have to reboot immediately (that
would solve the problem temporarily, wouldn't it?) if someone would give
me some advice, I could try to help debug it; however, as I'm not a
coder
+ Anton Yudin [EMAIL PROTECTED]:
| How to fix problem with floppies 1457664 bytes?
By not downloading a new release before it's announced. Just wait, a
corrected version of 4.8-RELEASE without this problem will appear.
Wait a little longer, for the official announcement. Then get it.
+ Anton Yudin [EMAIL PROTECTED]:
| How to fix problem with floppies 1457664 bytes?
By not downloading a new release before it's announced. Just wait, a
corrected version of 4.8-RELEASE without this problem will appear.
Wait a little longer, for the official announcement. Then get it.
Hi all,
Just a note. Apache2 in per-child mode now works
with freebsd, while it deadlocked in the old libc_r
on STABLE and CURRENT.
Thank you very much !
Martin
___
[EMAIL PROTECTED] mailing list
I'm looking at creating a machine for backing up/archiving other
FreeBSD servers. One of the requirements will be burning DVDs
(as some archives are 2-3g directories - difficult to break up)
So the question I'm asking is:
Is anyone actually using DVD burning under FreeBSD 5? If so,
what
I'm considering setting up a FreeBSD 5 machine as a dedicated
backup/archive computer on a network I administer.
I'm curious to hear some opinions on how wise this is. I know
that 5 is still in a -CURRENT status and I've seen (and repeated)
the warnings that it's not really production quality
From: Matthew Emmerton [EMAIL PROTECTED]
From: Bill Moran [EMAIL PROTECTED]
I'm considering setting up a FreeBSD 5 machine as a dedicated
backup/archive computer on a network I administer.
I'm curious to hear some opinions on how wise this is. I know
that 5 is still in a -CURRENT
Nate Lawson writes:
I was testing some changes to make fxp MPSAFE and got a LOR in allocating
the mbuf cluster and then finally a panic when trying to dereference the
cluster header. Is the mbuf system MPSAFE? Is it ok to call m_getcl
with a device lock held (but not Giant)?
The
- Original Message -
From: Bill Moran [EMAIL PROTECTED]
To: Matthew Emmerton [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, April 03, 2003 1:26 PM
Subject: Re: Overall feel for the stability of FreeBSD 5
From: Matthew Emmerton [EMAIL PROTECTED]
From: Bill Moran [EMAIL
From: Matthew Emmerton [EMAIL PROTECTED]
From: Bill Moran [EMAIL PROTECTED]
From: Matthew Emmerton [EMAIL PROTECTED]
From: Bill Moran [EMAIL PROTECTED]
I'm considering setting up a FreeBSD 5 machine as a dedicated
backup/archive computer on a network I administer.
I'm curious
I'd say this is a video card driver issue, because with my geforce3 and
the nvidia drivers I could run q3 for as long as I wanted without any
issues.
Ken
On Thu, 3 Apr 2003, Matthias Buelow wrote:
Hi folks,
I'm running 5.0-RELEASE-p7 on i386 and investigated how quake3 (linux)
would be
On Wed, Apr 02, 2003 at 03:18:18PM -0700, Nate Williams wrote:
evantd Sendmail has not been working on my system for some time now. I
evantd can't say exactly how long, but my guess is that it broke when I
evantd upgraded to RELENG_5_0. This is how sendmail is invoked (by
evantd
- Original Message -
From: Bill Moran [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, April 03, 2003 10:30 AM
Subject: Overall feel for the stability of FreeBSD 5
I'm considering setting up a FreeBSD 5 machine as a dedicated
backup/archive computer on a network I administer.
Matthew Emmerton wrote:
- Original Message -
From: Bill Moran [EMAIL PROTECTED]
To: Matthew Emmerton [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, April 03, 2003 1:26 PM
Subject: Re: Overall feel for the stability of FreeBSD 5
From: Matthew Emmerton [EMAIL PROTECTED]
From: Bill
I wrote:
Using XFree86-VidModeExtension Version 2.2
XFree86-VidModeExtension Activated at 640x480
libGL error: failed to open DRM: Operation not permitted
Ok, I hadn't seen so far the instructions for 5.0 on Eric
Anholts website... in fact, I needed to include a few
lines into the kernel config
This may be just my infamous vaio acting up again, but since the
recent commit to fxp driver (Monday?) I get a panic on device probe
(page fault in kernel mode).
That and the way the pccbb act up (always return 0 for event and
status register reads, and don't reset pending interrupt on event reg
[ moved to net@; current@ bcc'ed ]
Hi Craig,
I think I saw the same behaviour while developing a path-mtu discovery
tool. As I'm quite busy right now I didn't really dig into it, but I will
at some point.
I took the liberty to reply to freebsd-net@, because this is not only a
-CURRENT problem.
Bill Moran writes:
2) For a dedicated backup server, that can tolerate the
performance problems that folks have been reporting, and
won't upset the entire office if it panics on occasion, is 5
good enough at this point?
If the system isn't really too critical, I'd go for it. I'm
It seems recent current doesn't like my fxp. A current from some 10
hours ago keeps complaining about device timeout and dma timeout. I
don't *know* it's fxp fault (for one thing, because it says unknown),
but...
So, two hours ago, I cvsupped and tried a new world. This one panics on
boot,
Daniel C. Sobral wrote:
It seems recent current doesn't like my fxp. A current from some 10
hours ago keeps complaining about device timeout and dma timeout. I
don't *know* it's fxp fault (for one thing, because it says unknown),
but...
So, two hours ago, I cvsupped and tried a new
Peter Wemm wrote:
Daniel C. Sobral wrote:
It seems recent current doesn't like my fxp. A current from some 10
hours ago keeps complaining about device timeout and dma timeout. I
don't *know* it's fxp fault (for one thing, because it says unknown),
but...
So, two hours ago, I cvsupped and
Daniel C. Sobral wrote:
Peter Wemm wrote:
Daniel C. Sobral wrote:
It seems recent current doesn't like my fxp. A current from some 10
hours ago keeps complaining about device timeout and dma timeout. I
don't *know* it's fxp fault (for one thing, because it says unknown),
but...
So,
I'm seeing the same thing. A kernel from first thing this morning paniced the
kernel whilst attempting to probe the device. I saw a commit go in shortly
after 15.00 and rebuilt the kernel. Kernel built on that commit allows the
box to boot, but the device simply doesn't pass (or see) any
Pete Carah wrote:
This may be just my infamous vaio acting up again, but since the
recent commit to fxp driver (Monday?) I get a panic on device probe
(page fault in kernel mode).
This should be fixed in revision 1.30 of if_fxpreg.h that I committed
some time ago. Sorry for the
--- Pete Carah [EMAIL PROTECTED] wrote:
This may be just my infamous vaio acting up again,
but since the
recent commit to fxp driver (Monday?) I get a panic
on device probe
(page fault in kernel mode).
That and the way the pccbb act up (always return 0
for event and
status register
Ok. Hopefully some useful information hereUsing a kernel built against
the below fxp sources, the interface simply does not pass or see any traffic.
Reverting back to kernel from 01 April permits the intrace to function
properly.
fxp0: flags=18843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu
On 03-Apr-2003 Dr Daniel Flickinger wrote:
Secondly, I add the following to /etc/rc.conf:
mta_start_script= # 2917: block their startup stealth attack
sendmail_enable=NO
sendmail_outbound_enable=NO
sendmail_msp_queue_enable=NO
On Thu, Apr 03, 2003 at 04:10:04PM -0500, Robin P. Blanchard wrote:
# ls -ltr /usr/src/sys/dev/fxp/
total 116
-rw-r--r-- 1 root wheel 21318 Oct 25 2001 rcvbundl.h
-rw-r--r-- 1 root wheel 8190 Apr 2 13:00 if_fxpvar.h
-rw-r--r-- 1 root wheel 73326 Apr 3 11:46 if_fxp.c
-rw-r--r--
I got a userland core dump while using privoxy linked against libthr.
I don't know if this is libthr specific, but I thought I would report
it anyway. This might also explain why kde apps always crash on exit
(possibly, not really sure).
-gordon
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free
I forgot to mention, this is on a dual Athlon MP 1900+. Here's the
appropriate part of the dmesg:
CPU: AMD Athlon(TM) MP 1900+ (1600.07-MHz 686-class CPU)
Origin = AuthenticAMD Id = 0x662 Stepping = 2
On Thu, 03 Apr 2003 17:08:46 -0500 (EST)
John Baldwin [EMAIL PROTECTED] wrote:
On 03-Apr-2003 Dr Daniel Flickinger wrote:
Secondly, I add the following to /etc/rc.conf:
mta_start_script= # 2917: block their startup stealth attack
sendmail_enable=NO
I'm just hitting all the fun bugs today.
No core dump from this one. Privoxy seems to be a good app to test
multiple io threads and is simple enough to be debug.
Here's what I got this time:
$ /usr/local/sbin/privoxy --no-daemon /usr/local/etc/privoxy/config
Apr 03 15:50:49
Gordon Tetlow wrote:
No core dump from this one. Privoxy seems to be a good app to test
multiple io threads and is simple enough to be debug.
The source is also pretty Linux-centric, so some issues you finds may be
related to that.
(But I am all for fixing privoxy on -current, so I can start
On 2003-04-03 22:05, Oleg V. Nauman [EMAIL PROTECTED] wrote:
On Wed, Apr 02, 2003 at 03:18:18PM -0700, Nate Williams wrote:
This happened on one of my -stable boxes lately when doing a upgrade
using buildworld. For some (unknown) reason m4 bombed out and created
an empty .cf file.
I fixed it
I have gotten fxp running with MPSAFE and did a large scp transfer. It
ran for a few minutes and then paniced. It was trap 12 (page fault) at
address 0x24. Here is where it crashed:
fxp_start+0xcc
0xc0194a4c is in fxp_start (../../../dev/fxp/if_fxp.c:1263).
1258 * been
40 matches
Mail list logo
