On Wed, Mar 27, 2013 at 10:40:16PM -0700, m...@freebsd.org wrote:
> On Wed, Mar 27, 2013 at 10:32 PM, Konstantin Belousov
> wrote:
> > On Wed, Mar 27, 2013 at 06:37:51PM -0700, m...@freebsd.org wrote:
> >> VOP_GETEXTATTR is currently called with an exclusive lock, which seems
> >> like overkill fo
On Wed, Mar 27, 2013 at 10:32 PM, Konstantin Belousov
wrote:
> On Wed, Mar 27, 2013 at 06:37:51PM -0700, m...@freebsd.org wrote:
>> VOP_GETEXTATTR is currently called with an exclusive lock, which seems
>> like overkill for what is essentially a read operation. I had a look
>> over the various in
On Wed, Mar 27, 2013 at 06:37:51PM -0700, m...@freebsd.org wrote:
> VOP_GETEXTATTR is currently called with an exclusive lock, which seems
> like overkill for what is essentially a read operation. I had a look
> over the various in-tree filesystems and it didn't look like any of
> them will have a
On Wed, Mar 27, 2013 at 2:03 AM, Attilio Rao wrote:
> On Wed, Mar 27, 2013 at 4:00 AM, Marcelo/Porks wrote:
>>
>> On Mar 22, 2013 1:02 AM, "Attilio Rao" wrote:
>>>
>>> On Fri, Mar 22, 2013 at 2:02 AM, Marcelo/Porks
>>> wrote:
>>> > Hi, I'm facing an error compiling the sysutils/fusefs-kmod.
>>>
VOP_GETEXTATTR is currently called with an exclusive lock, which seems
like overkill for what is essentially a read operation. I had a look
over the various in-tree filesystems and it didn't look like any of
them will have a problem if a shared-mode lock is used for
vop_getextattr.
Does anyone kn
My main concern with the new stuff is that it requires CAM and that's
reasonably big compared to the standalone ATA code.
It'd be nice if we could slim down the CAM stack a bit first; it makes
embedding it on the smaller devices really freaking painful.
Thanks,
adrian
_
Just curious if anyone has any scripts for managing fail-over of multiple
interfaces using the new CARP setup in 10-CURRENT.
Fail-over of all CARP vhids associated with a single interface is working
correctly. But, I have 2 separate, physical interfaces running with CARP,
and want to fail-over ev
On Thu, Mar 28, 2013 at 12:22:11AM +0200, Alexander Motin wrote:
> On 28.03.2013 00:05, Steve Kargl wrote:
> >
> > Last time I tested the new one, and this was several months
> > ago, the system (a Dell Latitude D530 laptop) would not boot.
>
> Probably we should just fix that. Any more info?
>
On Wed, Mar 20, 2013 at 12:24 PM, Maksim Yevmenkin wrote:
> hello,
>
> would anyone object to the following small patch?
>
>
Yes, I don't think that we should entirely disable vm_lowmem events or
uma_reclaim() on pass == 0 calls to vm_pageout_scan(). However, I do
think it's reasonable to signi
On 28.03.2013 00:05, Steve Kargl wrote:
On Wed, Mar 27, 2013 at 11:35:35PM +0200, Alexander Motin wrote:
On 27.03.2013 23:32, Steve Kargl wrote:
On Wed, Mar 27, 2013 at 11:22:14PM +0200, Alexander Motin wrote:
Hi.
Since FreeBSD 9.0 we are successfully running on the new CAM-based ATA
stack, u
On 3/27/2013 2:22 PM, Alexander Motin wrote:
Hi.
Since FreeBSD 9.0 we are successfully running on the new CAM-based ATA
stack, using only some controller drivers of old ata(4) by having
`options ATA_CAM` enabled in all kernels by default. I have a wish to
drop non-ATA_CAM ata(4) code, unused
Is there any known magic involved in getting DTrace to do its thing on
9.1-release?
I am trying to use it to debug a memory leak problem with the radeonkms
driver under 9.x.
Firstly, the following sequence works normally:
boot system
kldload drm2
kldload radeonkms
On Wed, Mar 27, 2013 at 11:35:35PM +0200, Alexander Motin wrote:
> On 27.03.2013 23:32, Steve Kargl wrote:
> > On Wed, Mar 27, 2013 at 11:22:14PM +0200, Alexander Motin wrote:
> >> Hi.
> >>
> >> Since FreeBSD 9.0 we are successfully running on the new CAM-based ATA
> >> stack, using only some contr
Dnia 2013-03-27, o godz. 16:54:40
Michael Butler napisał(a):
>Rebuild whichever port of gcc you're using (gcc46?); it copies (and
>"fixes") some of the default include files for its own purposes. If
>it's behind, it'll be missing the addition of the sbintime_t typedef
>in types.h,
That was it. A
On Wed, Mar 27, 2013 at 2:32 PM, Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:
> On Wed, Mar 27, 2013 at 11:22:14PM +0200, Alexander Motin wrote:
> > Hi.
> >
> > Since FreeBSD 9.0 we are successfully running on the new CAM-based ATA
> > stack, using only some controller drivers of old at
On 27.03.2013 23:32, Steve Kargl wrote:
On Wed, Mar 27, 2013 at 11:22:14PM +0200, Alexander Motin wrote:
Hi.
Since FreeBSD 9.0 we are successfully running on the new CAM-based ATA
stack, using only some controller drivers of old ata(4) by having
`options ATA_CAM` enabled in all kernels by defau
On Wed, Mar 27, 2013 at 11:22:14PM +0200, Alexander Motin wrote:
> Hi.
>
> Since FreeBSD 9.0 we are successfully running on the new CAM-based ATA
> stack, using only some controller drivers of old ata(4) by having
> `options ATA_CAM` enabled in all kernels by default. I have a wish to
> drop no
Figure it out. :(
Was an IPFW rule. Seems the following two rules block CARP traffic:
# Check for spoofed packets
# Anti-spoof rules
# These do roughly the same things:
# verrevpath checks all incoming packets to see if the source IP matches
any route on that interface
# antispoof checks a
Hi.
Since FreeBSD 9.0 we are successfully running on the new CAM-based ATA
stack, using only some controller drivers of old ata(4) by having
`options ATA_CAM` enabled in all kernels by default. I have a wish to
drop non-ATA_CAM ata(4) code, unused since that time from the head
branch to allow
On Wed, Mar 27, 2013 at 9:28 PM, Pawel Pekala wrote:
> For some time now (about month?) ports using sys/time.h include fail to
> build and I`m sure they were building ok before. At least those seems
> affected by this:
>
> math/atlas
> math/openblas
> x11-toolkits/c++-gtk-utils
>
> All fail with s
Two systems running identical hardware and software (one system actually
rsync'd from the other). Running 10-CURRENT just after the new CARP
implementation went in:
FreeBSD nexus2.sd73.bc.ca 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r245195: Thu
Jan 10 10:29:16 PST 2013 r...@nexus2.sd73.bc.ca:/usr
On Wed, Mar 27, 2013 at 09:28:19PM +0100 I heard the voice of
Pawel Pekala, and lo! it spake thus:
>
> For some time now (about month?) ports using sys/time.h include fail to
> build and I`m sure they were building ok before. At least those seems
> affected by this:
>
> math/atlas
> math/openblas
On 03/27/13 16:28, Pawel Pekala wrote:
> For some time now (about month?) ports using sys/time.h include fail to
> build and I`m sure they were building ok before. At least those seems
> affected by this:
>
> math/atlas
> math/openblas
> x11-toolkits/c++-gtk-utils
>
> All fail with similar errors
Hello,
i would like to get some reviews, opinions and/or comments on the patch below.
a little bit background, as far as i understand, cluster_read() can
initiate two disk i/o's: one for exact amount of data being requested
(rounded up to a filesystem block size) and another for a configurable
re
For some time now (about month?) ports using sys/time.h include fail to
build and I`m sure they were building ok before. At least those seems
affected by this:
math/atlas
math/openblas
x11-toolkits/c++-gtk-utils
All fail with similar errors:
/usr/include/sys/time.h:134:17: error: unknown type na
Am 2013-03-27 14:32, schrieb Konstantin Belousov:
On Wed, Mar 27, 2013 at 01:56:29PM +0100, m...@kernel32.de wrote:
Am 2013-03-27 06:54, schrieb Andriy Gapon:
> on 27/03/2013 00:00 m...@kernel32.de said the following:
>> Hi Ho,
>>
>> I'm trying to install FreeBSD 10.0-CURRENT snapshot from
23.0
On Wed, Mar 27, 2013 at 01:56:29PM +0100, m...@kernel32.de wrote:
> Am 2013-03-27 06:54, schrieb Andriy Gapon:
> > on 27/03/2013 00:00 m...@kernel32.de said the following:
> >> Hi Ho,
> >>
> >> I'm trying to install FreeBSD 10.0-CURRENT snapshot from 23.03.2013
> >> on a Dell
> >> M620 blade.
> >>
Am 2013-03-27 06:54, schrieb Andriy Gapon:
on 27/03/2013 00:00 m...@kernel32.de said the following:
Hi Ho,
I'm trying to install FreeBSD 10.0-CURRENT snapshot from 23.03.2013
on a Dell
M620 blade.
However, I'm getting a panic and drop to db while booting.
Looks like that:
Root mount waiting
28 matches
Mail list logo
