From: Jacob Myers [mailto:ja...@whotookspaz.org]
Jaime Bozza wrote:
From: Arnaud Houdelette [mailto:arnaud.houdele...@tzim.net]
I haven't tried larger files - Maybe the boundary is different on amd64?
Doing some quick tests
right now, I was able to upload a 100MB file without a
2009/10/23 Jaime Bozza jbo...@mindsites.com:
I believe I found a problem with the ULE scheduler - At least the fact that
there is a problem, but I'm not sure where to go from here. The system
locks all processes, but doesn't panic, so I have no output to give.
I was able to duplicate this
Jaime Bozza wrote:
From: Arnaud Houdelette [mailto:arnaud.houdele...@tzim.net]
I haven't tried larger files - Maybe the boundary is different on amd64?
Doing some quick tests
right now, I was able to upload a 100MB file without a problem, but this is
an AMD64 system with SMP,
plus the
Jaime Bozza a écrit :
The additional information I have (over the PR) is that:
1) Files over 64K cause the problem, not just larger files
I thought it was over 1 MB or so. But maybe I'm wrong. ISTR that I
couldn't trigger it with some images of around 70K.
I discovered it
Arnaud Houdelette wrote:
I had the same issue using 7.1 amd64, with ZFS, no SMP.
Not really sure what is the size boundary. I can't really test either,
as the machine is remote.
But I confirm that each tentative upload of certain relatively 'big'
files (around 1MB) with wordpress hanged the
From: Jacob Myers [mailto:ja...@whotookspaz.org]
Arnaud Houdelette wrote:
I had the same issue using 7.1 amd64, with ZFS, no SMP.
Not really sure what is the size boundary. I can't really test
either,
as the machine is remote.
But I confirm that each tentative upload of certain
Sincerely,
Jaime Bozza
MindSites Group, LLC
From: Dylan Cochran [mailto:heliocent...@gmail.com]
Superficially, this seams identical to a deadlock I reported for
7.1-RC1. Would you mind compiling a kernel with these options:
snip
KDB: stack backtrace:
From: Kostik Belousov [mailto:kostik...@gmail.com]
Can you look up the source line for kern_sendfile+0x90d in your
kernel ? Do kgdb kernel.debug, then execute list *(kern_sendfile+0x90d).
In my case, it was kern_sendfile+0x6ad (rebuilt with RELENG_7 this weekend).
Here's the output:
(kgdb)
From: Arnaud Houdelette [mailto:arnaud.houdele...@tzim.net]
I haven't tried larger files - Maybe the boundary is different on amd64?
Doing some quick tests
right now, I was able to upload a 100MB file without a problem, but this is
an AMD64 system with SMP,
plus the filesystem is all ZFS,
The additional information I have (over the PR) is that:
1) Files over 64K cause the problem, not just larger files
I thought it was over 1 MB or so. But maybe I'm wrong. ISTR that I
couldn't trigger it with some images of around 70K.
I discovered it originally with a 72K file. After some
I believe I found a problem with the ULE scheduler - At least the fact that
there is a problem, but I'm not sure where to go from here. The system locks
all processes, but doesn't panic, so I have no output to give.
I was able to duplicate this on three different machines and solved it by
On Fri, Oct 23, 2009 at 2:46 PM, Jaime Bozza jbo...@mindsites.com wrote:
I believe I found a problem with the ULE scheduler - At least the fact that
there is a problem, but I'm not sure where to go from here. The system
locks all processes, but doesn't panic, so I have no output to give.
On 10/23/09, Jaime Bozza jbo...@mindsites.com wrote:
I believe I found a problem with the ULE scheduler - At least the fact that
there is a problem, but I'm not sure where to go from here. The system
locks all processes, but doesn't panic, so I have no output to give.
I was able to
Try adding this or changing these items in lighttpd.conf:
## FreeBSD!
server.event-handler = freebsd-kqueue
server.network-backend= writev
Scott,
Lighttpd was already using freebsd-kqueue, but I added the writev
network-backend and the problem went away. With this additional
On Fri, Oct 23, 2009 at 04:28:59PM -0400, Dylan Cochran wrote:
On 10/23/09, Jaime Bozza jbo...@mindsites.com wrote:
I believe I found a problem with the ULE scheduler - At least the fact that
there is a problem, but I'm not sure where to go from here. The system
locks all processes, but
Jaime Bozza wrote:
[snip]
The additional information I have (over the PR) is that:
1) Files over 64K cause the problem, not just larger files
I thought it was over 1 MB or so. But maybe I'm wrong. ISTR that I
couldn't trigger it with some images of around 70K.
2) switching over to SCHED_4BSD
16 matches
Mail list logo
