Good day.
Sorry for cross-posting, but this question is really belongs to all
three lists.
Crawling over the rc.d scripts I had found the rc_fast_and_loose variable
that affects the way rc.d scripts are processed inside /etc/rc script.
There are some problems with certain rc.d script and this va
Le mar 10/01/12 19:30, "Kirk McKusick" mckus...@mckusick.com a écrit:
> > Date: Mon, 9 Jan 2012 18:30:51 +0100
> > From: Yamagi Burmeister .org>
> To: jeff@freebsd
> .org, mckusick
> @freebsd.org
> Cc: f
> reebsd-curr...@freebsd.org, bryce@bryce.n
> et
> Subject: Re: FS hang when creating snap
Could you please try this:
# cd /usr/src/contrib
# mv openpam openpam.orig
# svn export svn://svn.des.no/openpam/trunk@526 openpam
# cd ../lib/libpam
# make depend && make all && make install
In addition to the pam.conf issue, the major changes relative to head
are reduced log spam, improved log
Hi,
I'd suggest verifying that it's _just_ a kernel update that messes with it.
And once you've verified that, what about doing some kernel source
version bisecting to narrow down when the relevant change went in
that's caused your regression?
Adrian
Hello, Alexander.
You wrote 11 января 2012 г., 3:35:44:
> I remember no changes in mpd-5.6 that I would expect to cause this. Any
> way it should be trivial to check -- just build 5.5.
I'll try tomorrow.
> What do you have configured in mpd configuration and netgraph at all?
> AFAIR for plain
On 01/10/12 17:21, Lev Serebryakov wrote:
Hello, Lev.
You wrote 11 января 2012 г., 3:05:29:
OH! I have top running right now, when it "hangs". 0% idle time, LA
becomes 20 when it have only 35 processes at all, but there is no specific
process consuming CPU.
Ok, it seems, that here is
On 01/11/12 01:21, Lev Serebryakov wrote:
Hello, Lev.
You wrote 11 января 2012 г., 3:05:29:
OH! I have top running right now, when it "hangs". 0% idle time, LA
becomes 20 when it have only 35 processes at all, but there is no specific
process consuming CPU.
Ok, it seems, that here is
Hello, Lev.
You wrote 11 января 2012 г., 3:05:29:
> OH! I have top running right now, when it "hangs". 0% idle time, LA
> becomes 20 when it have only 35 processes at all, but there is no specific
> process consuming CPU.
Ok, it seems, that here is a problem (CPU time :
PID USERNAME PRI NICE
On 10 Jan, Dag-Erling Smørgrav wrote:
> If at any point in this conversation I seemed to make _no sense at all_,
> it was because I conflated it with a completely different OpenPAM issue
> (error reporting in openpam_dynamic.c) which has been on my mind lately.
> Sorry about that. I will attempt t
Hello, FreeBSD.
I have home router+AP based on Soekris net5501 (500Mhz GEODE CPU,
512MiB of RAM).
It is equipped with vrX NICs (4 of them on-board, one is used as
upstream to my ISP, other are unconnectd), em0 PCI board (legacy
driver, downstream to my home network) and PCI ath0 (WiFi, for
On Jan 10, 2012, at 4:04 PM, FreeBSD Tinderbox wrote:
> cc -O2 -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil
> -I/src/lib/libutil/../libc/gen/ -std=gnu99 -fstack-protector -Wsystem-headers
> -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
> -Wmissing-prototypes -Wpoi
on 11/01/2012 00:23 Matthew Jacob said the following:
>>> At the very least, require bounce buffers.
>>
>> Not sure if I got this suggestion in this terse form.
>> Could you please explain?
>
> Physical address zero can be DMA'd, but via bounce buffers.
> bcopy from address zero up through a pages
On Tue, Jan 10, 2012 at 01:52:49PM -0800, Adrian Chadd wrote:
> On 10 January 2012 13:37, Luigi Rizzo wrote:
> > I was glancing through manpages and implementations of bus_dma(9)
> > and i am a bit unclear on what this API (in particular, bus_dmamap_sync() )
> > does in terms of memory barriers.
>
At the very least, require bounce buffers.
Not sure if I got this suggestion in this terse form.
Could you please explain?
Physical address zero can be DMA'd, but via bounce buffers.
bcopy from address zero up through a pagesize to a bounce buffer, do the
dma from there (read case), write cas
on 10/01/2012 23:27 Ian Lepore said the following:
> On Tue, 2012-01-10 at 23:15 +0200, Andriy Gapon wrote:
>> This has still some problems:
>> - filter func is called for the range (lowaddr, hiaddr], that is lowadr is
>> not
>> inclusive, as such there is no way to filter page zero
>> - a bounce
TB --- 2012-01-10 21:38:04 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-10 21:38:04 - starting HEAD tinderbox run for powerpc64/powerpc
TB --- 2012-01-10 21:38:04 - cleaning the object tree
TB --- 2012-01-10 21:38:24 - cvsupping the source tree
TB --- 2012-01-10 21:38:24 - /u
TB --- 2012-01-10 21:32:00 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-10 21:32:00 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2012-01-10 21:32:00 - cleaning the object tree
TB --- 2012-01-10 21:32:19 - cvsupping the source tree
TB --- 2012-01-10 21:32:19 - /usr
On 10 January 2012 13:37, Luigi Rizzo wrote:
> I was glancing through manpages and implementations of bus_dma(9)
> and i am a bit unclear on what this API (in particular, bus_dmamap_sync() )
> does in terms of memory barriers.
>
> I see that the x86/amd64 and ia64 code only does the bounce buffers
On Tue, 2012-01-10 at 22:37 +0100, Luigi Rizzo wrote:
> I was glancing through manpages and implementations of bus_dma(9)
> and i am a bit unclear on what this API (in particular, bus_dmamap_sync() )
> does in terms of memory barriers.
>
> I see that the x86/amd64 and ia64 code only does the bounc
If at any point in this conversation I seemed to make _no sense at all_,
it was because I conflated it with a completely different OpenPAM issue
(error reporting in openpam_dynamic.c) which has been on my mind lately.
Sorry about that. I will attempt to address both issues in the next
release, whi
TB --- 2012-01-10 21:11:12 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-10 21:11:12 - starting HEAD tinderbox run for mips/mips
TB --- 2012-01-10 21:11:12 - cleaning the object tree
TB --- 2012-01-10 21:11:19 - cvsupping the source tree
TB --- 2012-01-10 21:11:19 - /usr/bin/c
On Tue, 2012-01-10 at 23:15 +0200, Andriy Gapon wrote:
> on 10/01/2012 22:53 Ian Lepore said the following:
> > On Tue, 2012-01-10 at 22:18 +0200, Andriy Gapon wrote:
> >>
> >> Some hardware interfaces may reserve a special meaning for a (physical)
> >> memory
> >> address value of zero. One exam
on 10/01/2012 22:54 Matthew Jacob said the following:
>
> I think it would be just simpler to disallow page zero usage period.
That would be simpler indeed.
> Can you
> think of any case where physical page 0 is ever a valid DMA address?
Not sure if I got your question right. I think that it's
I was glancing through manpages and implementations of bus_dma(9)
and i am a bit unclear on what this API (in particular, bus_dmamap_sync() )
does in terms of memory barriers.
I see that the x86/amd64 and ia64 code only does the bounce buffers.
The mips seems to do some coherency-related calls.
H
on 10/01/2012 22:53 Ian Lepore said the following:
> On Tue, 2012-01-10 at 22:18 +0200, Andriy Gapon wrote:
>>
>> Some hardware interfaces may reserve a special meaning for a (physical)
>> memory
>> address value of zero. One example is the OHCI specification where a zero
>> value
>> in CurrentB
TB --- 2012-01-10 20:46:40 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2012-01-10 20:46:40 - starting HEAD tinderbox run for ia64/ia64
TB --- 2012-01-10 20:46:40 - cleaning the object tree
TB --- 2012-01-10 20:47:04 - cvsupping the source tree
TB --- 2012-01-10 20:47:04 - /usr/bin/c
On Tue, 2012-01-10 at 22:18 +0200, Andriy Gapon wrote:
>
> Some hardware interfaces may reserve a special meaning for a (physical) memory
> address value of zero. One example is the OHCI specification where a zero
> value
> in CurrentBufferPointer doesn't mean a physical address, but has a reser
I think it would be just simpler to disallow page zero usage period. Can
you think of any case where physical page 0 is ever a valid DMA address?
At the very least, require bounce buffers.
On Tue, 10 Jan 2012, Andriy Gapon wrote:
Some hardware interfaces may reserve a special meaning for
Some hardware interfaces may reserve a special meaning for a (physical) memory
address value of zero. One example is the OHCI specification where a zero value
in CurrentBufferPointer doesn't mean a physical address, but has a reserved
meaning. To be honest I don't have another example :) but do
On Tue, Jan 10, 2012 at 7:12 PM, Fischer Markus wrote:
>
>
> Hello,
>
> I habe a BIG Problem with the ACPI Interface.
> The problem is the "reboot" command. The Shutdown command works.
I don't think ``reboot`` is the command you want. If you want the
computer to shut down, and then restart, you s
> Date: Mon, 9 Jan 2012 18:30:51 +0100
> From: Yamagi Burmeister
> To: j...@freebsd.org, mckus...@freebsd.org
> Cc: freebsd-current@freebsd.org, br...@bryce.net
> Subject: Re: FS hang when creating snapshots on a UFS SU+J setup
>
> Hello,
>
> I'm sorry to bother you, but you may not be aware of
31 matches
Mail list logo
