usr/sbin/config assumes that the kernel config file
lives in ${src_base}/sys/${arch}/conf , which means that
if you need to build a custom kernel one needs RW
access to that directory.
Any idea on how we can enable config to work in a
generic directory ?
I scanned the source code usr.sbin/config
Hey,
after two years I had the opportunity to run the build option survey,
initially done by phk, again. The number of options seems to have grown
quite a bit it felt. I have not even looked at the results yet but here
they are fresh off the machine:
http://people.freebsd.org/~bz/build_optio
Hi,
Can you use a USB3.0 hub?
I tried a USB3.0 hub (BUFFALO BSH4A04U3BK).
And I used 8-stable and PCI-E card (BUFFALO IFC-PCIE2U3)
The hub is for only japanese market.
The card is NEC’s 720200 chip
http://www.buffalotech.com/products/accessories/interface-card-adapters/usb-30-pci-express-interfa
In the last episode (Jan 11), Martin Cracauer said:
> Rick Macklem wrote on Wed, Jan 11, 2012 at 08:42:25PM -0500:
> > Also, if you can reproduce the problem fairly easily, capture a packet
> > trace via
> > # tcpdump -s 0 -w xxx host
> > running on the client (or similar). Then email me "xxx" a
On Wed, Jan 04, 2012 at 21:53:11 -0700, Kenneth D. Merry wrote:
>
> The CAM Target Layer (CTL) is now available for testing. I am planning to
> commit it to to head next week, barring any major objections.
>
> CTL is a disk and processor device emulation subsystem originally written
> for Copan
Rick Macklem wrote on Wed, Jan 11, 2012 at 08:42:25PM -0500:
> Martin Cracauer wrote:
> > Stefan Bethke wrote on Wed, Jan 11, 2012 at 07:14:44PM +0100:
> > > Am 11.01.2012 um 17:57 schrieb Martin Cracauer:
> > >
> > > > I'm sorry for the unspecific bug report but I thought a heads-up
> > > > is
>
Martin Cracauer wrote:
> Stefan Bethke wrote on Wed, Jan 11, 2012 at 07:14:44PM +0100:
> > Am 11.01.2012 um 17:57 schrieb Martin Cracauer:
> >
> > > I'm sorry for the unspecific bug report but I thought a heads-up
> > > is
> > > better than none.
> > >
> > > $ uname -a
> > > FreeBSD wings.cons.org
On 11 Jan, Dag-Erling Smørgrav wrote:
> 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
[snip]
building shared library libpam.so.5
make: don'
on 12/01/2012 00:22 Andriy Gapon said the following:
[snip]
> /usr/include/xlocale.h:160:3: error: unknown type name 'va_list'
> /usr/include/xlocale.h:162:3: error: unknown type name 'va_list'
[snip]
> Back to the main problem. I am not sure where the difference between the base
> GCC and GCC 4.6
Hello, Chuck.
You wrote 11 января 2012 г., 3:47:08:
> If it were me, I would also try with the older 44BSD scheduler, just to
> see what happens.
It helps both with mpd5.5 and mpd5.6.
Now under network load top lines in `top' are
PID USERNAME PRI NICE SIZERES STATETIME WCPU COMMAN
on 11/01/2012 19:18 Andriy Gapon said the following:
> Actually, I think that on x86 we don't have to do anything special for any
> memory
> allocations that we do, including the bounce pages, as the page zero is
> excluded
> from phys_avail and is not available for normal use.
After some additi
Hi.
I would like request for testing of my work on further HDA sound driver
improvement.
List of changes done this time:
- Huge old hdac driver was split into three independent pieces: HDA
controller driver (hdac), HDA CODEC driver (hdacc) and HDA sudio
function driver (hdaa). All drivers a
On Jan 11, 2012, at 10:10 AM, Ian Lepore wrote:
> On Wed, 2012-01-11 at 09:59 -0700, Scott Long wrote:
>>
>> Where barriers _are_ needed is in interrupt handlers, and I can
>> discuss that if you're interested.
>>
>> Scott
>>
>
> I'd be interested in hearing about that (and in general I'm lov
Stefan Bethke wrote on Wed, Jan 11, 2012 at 07:14:44PM +0100:
> Am 11.01.2012 um 17:57 schrieb Martin Cracauer:
>
> > I'm sorry for the unspecific bug report but I thought a heads-up is
> > better than none.
> >
> > $ uname -a
> > FreeBSD wings.cons.org 10.0-CURRENT FreeBSD 10.0-CURRENT #2: Wed
Am 11.01.2012 um 17:57 schrieb Martin Cracauer:
> I'm sorry for the unspecific bug report but I thought a heads-up is
> better than none.
>
> $ uname -a
> FreeBSD wings.cons.org 10.0-CURRENT FreeBSD 10.0-CURRENT #2: Wed Dec
> 28 12:19:21 EST 2011
> craca...@wings.cons.org:/usr/src/sys/amd64/compi
On Wed, Jan 11, 2012 at 10:30:39AM +0100, Yamagi Burmeister wrote:
> Hello,
> I've done some tests to verify that the problem only occures when SU+J
> is used, but not SU without J. In fact, I did run the following two
> loops on different TTYs in parallel:
I also confirm this using a similar tech
on 11/01/2012 18:02 Scott Long said the following:
> An old controller in the aac driver family had a variation of this problem
> back
> when the FreeBSD contigmalloc algorithm started from the bottom of memory
> instead of the top. I worked around it at driver init time by basically
> assuring t
on 11/01/2012 17:01 John Baldwin said the following:
> I think this is fine, but you should just always exclude page zero when
> allocating
> bounce pages. Bounce pages are assigned to zones that can be shared by
> multiple
> tags, so other tags that map to the same zone can alloc bounce pages t
On Wed, 2012-01-11 at 09:59 -0700, Scott Long wrote:
>
> Where barriers _are_ needed is in interrupt handlers, and I can
> discuss that if you're interested.
>
> Scott
>
I'd be interested in hearing about that (and in general I'm loving the
details coming out in your explanations -- thanks!).
On Jan 11, 2012, at 10:00 AM, Ian Lepore wrote:
>
> I've wished (in the ARM world) for the ability to sync a portion of a
> map. I've even kicked around the idea of proposing an API extension to
> do so, but I guess if FreeBSD went out of its way to remove that
> functionality that idea probabl
On Wed, 2012-01-11 at 11:49 -0500, John Baldwin wrote:
> On Wednesday, January 11, 2012 11:29:44 am Luigi Rizzo wrote:
> > On Wed, Jan 11, 2012 at 10:05:28AM -0500, John Baldwin wrote:
> > > On Tuesday, January 10, 2012 5:41:00 pm Luigi Rizzo wrote:
> > > > On Tue, Jan 10, 2012 at 01:52:49PM -0800,
On Jan 11, 2012, at 9:29 AM, Luigi Rizzo wrote:
> On Wed, Jan 11, 2012 at 10:05:28AM -0500, John Baldwin wrote:
>> On Tuesday, January 10, 2012 5:41:00 pm Luigi Rizzo wrote:
>>> On Tue, Jan 10, 2012 at 01:52:49PM -0800, Adrian Chadd wrote:
On 10 January 2012 13:37, Luigi Rizzo wrote:
>
I'm sorry for the unspecific bug report but I thought a heads-up is
better than none.
$ uname -a
FreeBSD wings.cons.org 10.0-CURRENT FreeBSD 10.0-CURRENT #2: Wed Dec
28 12:19:21 EST 2011
craca...@wings.cons.org:/usr/src/sys/amd64/compile/WINGS amd64
I see filesystem corruption on NFS filesystems
On Wednesday, January 11, 2012 11:29:44 am Luigi Rizzo wrote:
> On Wed, Jan 11, 2012 at 10:05:28AM -0500, John Baldwin wrote:
> > On Tuesday, January 10, 2012 5:41:00 pm Luigi Rizzo wrote:
> > > On Tue, Jan 10, 2012 at 01:52:49PM -0800, Adrian Chadd wrote:
> > > > On 10 January 2012 13:37, Luigi Ri
On Wed, Jan 11, 2012 at 10:05:28AM -0500, John Baldwin wrote:
> On Tuesday, January 10, 2012 5:41:00 pm Luigi Rizzo wrote:
> > 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 implementation
An old controller in the aac driver family had a variation of this problem back
when the FreeBSD contigmalloc algorithm started from the bottom of memory
instead of the top. I worked around it at driver init time by basically
assuring that page 0 (and page 1) were allocated and thrown away; it
On Jan 10, 2012, at 2:37 PM, 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 bu
On Tuesday, January 10, 2012 5:41:00 pm Luigi Rizzo wrote:
> 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 part
On Tuesday, January 10, 2012 3:18:28 pm 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
Hello,
I've done some tests to verify that the problem only occures when SU+J
is used, but not SU without J. In fact, I did run the following two
loops on different TTYs in parallel:
while 1
cp -r /usr/src /root
rm -Rf /root/src
end
while 1
mksnap_ffs / /.snap/snap
rm -f /.snap/snap
end
With
30 matches
Mail list logo