On 12/3/11 5:45 PM, Garrett Cooper wrote:
> Just to back up that point: until CVS is completely unused by
> releng (docs, ports are still done via CVS),
Ah - I am indeed mistaken. Not all that surprising.
> it really shouldn't be
> removed from base (no matter how broken or undeveloped it is).
In the past, I've used the ftp cdrtools pkg (made from the
port of course) and it failed to work. It's a popular tool so my
machine was probably out of sync. Same with burncd. However,
compiling the current cdrtools source worked fine. So I'd try
that first, compare, and send up a bug if need be.
On 08/12/2011, at 10:55, Thomas Mueller wrote:
> I can't get cdrtools (cdrecord or readcd) to work on FreeBSD 9.0-RC2, and now
> I see RC3 is available.
>
> I tried "options ATA_CAM" in kernel config, removing "device atapicam", but
> still
> readcd -scanbus or
> cdrecord -scanbus
> refuses t
I can't get cdrtools (cdrecord or readcd) to work on FreeBSD 9.0-RC2, and now I
see RC3 is available.
I tried "options ATA_CAM" in kernel config, removing "device atapicam", but
still
readcd -scanbus or
cdrecord -scanbus
refuses to work, running as root.
"camcontrol devlist" shows my DVD driv
On Wed, Dec 07, 2011 at 09:58:31PM +0200, Daniel Kalchev wrote:
>
> On Dec 7, 2011, at 8:08 PM, Luigi Rizzo wrote:
>
> > Summary:
> >
> > - with default interrupt mitigation, the fastest configuration
> > is with checksums enabled on both sender and receiver, lro
> > enabled on the receiver. T
On Dec 7, 2011, at 8:08 PM, Luigi Rizzo wrote:
> Summary:
>
> - with default interrupt mitigation, the fastest configuration
> is with checksums enabled on both sender and receiver, lro
> enabled on the receiver. This gets about 8.0 Gbit/s
I do not observe this. With defaults:
# nuttcp -t -T
on 07/12/2011 19:33 Andriy Gapon said the following:
>
> A detail that may or may not be useful.
> It seems that the panic happened when tried to resume a vim process. The
> process
> was suspended, its current directory and a file being edited/viewed may have
> been
> already removed.
And an
On Wed, Dec 07, 2011 at 11:59:43AM +0100, Andre Oppermann wrote:
> On 06.12.2011 22:06, Luigi Rizzo wrote:
...
> >Even in my experiments there is a lot of instability in the results.
> >I don't know exactly where the problem is, but the high number of
> >read syscalls, and the huge impact of settin
A detail that may or may not be useful.
It seems that the panic happened when tried to resume a vim process. The
process
was suspended, its current directory and a file being edited/viewed may have
been
already removed.
on 07/12/2011 18:50 Andriy Gapon said the following:
>
> (kgdb) bt
> #0
Hi,
If someone want to look at I've added support for VIA south bridge watchdog.
It has been tested on VX900 but should works with VX800, VX855, CX700.
http://people.freebsd.org/~fabient/patch-watchdog-via-rev1
Fabien
___
freebsd-current@freeb
2011/12/7 Andriy Gapon :
> on 07/12/2011 00:11 Attilio Rao said the following:
>> I'd just change this check on panicstr:
>> @@ -606,9 +603,13 @@ kdb_trap(int type, int code, struct trapframe *tf)
>> intr = intr_disable();
>>
>> #ifdef SMP
>> - other_cpus = all_cpus;
>> - CPU_CLR(PCP
(kgdb) bt
#0 doadump (textdump=1) at pcpu.h:224
#1 0x804f6d3b in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:447
#2 0x804f63e9 in panic (fmt=0x104 ) at
/usr/src/sys/kern/kern_shutdown.c:635
#3 0x80585f46 in cache_enter (dvp=0xfe003d4763c0,
vp=0x
on 06/12/2011 22:22 Andriy Gapon said the following:
>
> Could you please change that line as follows?
> vm_page_t pPage = pPages +iPage;
>
Additionally the patch has another bug. Here is a patch on top of the previous
patch:
--- src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c.ori
> Am 07.12.2011 09:32, schrieb Dimitry Andric:
> > That said, you are most likely running into an issue with the fix for
> > FreeBSD 10-CURRENT in bsd.port.mk, causing the lto-plugin stage
> > configure script to fail.
> >
> > This is because the gcc ports unpack their source code into
> > ${WRKDIR
On 06.12.2011 22:06, Luigi Rizzo wrote:
On Tue, Dec 06, 2011 at 07:40:21PM +0200, Daniel Kalchev wrote:
I see significant difference between number of interrupts on the Intel and the
AMD blades. When performing a test between the Intel and AMD blades, the Intel
blade generates 20,000-35,000 in
"O. Hartmann" writes:
> .././../gcc-4.6-20111202/libcpp/charset.c:1371:1: error: conflicting
> types for 'cpp_interpret_string'
> cpp_interpret_string (cpp_reader *pfile, const cpp_string *from, size_t
> count,
> ^
> .././../gcc-4.6-20111202/libcpp/include/cpplib.h:742:13: note: previous
> declar
On 7. Dec 2011, at 09:29 , Pawel Jakub Dawidek wrote:
> On Tue, Jun 28, 2011 at 03:32:41PM -0700, Xin LI wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Hi,
>>
>> I'd like to request for comments on the attached driver, which supports
>> watchdogs on several Winbond super I/O
On Tue, Jun 28, 2011 at 03:32:41PM -0700, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi,
>
> I'd like to request for comments on the attached driver, which supports
> watchdogs on several Winbond super I/O chip models and have been tested
> on a few of recent Supermicro
Am 07.12.2011 09:32, schrieb Dimitry Andric:
> That said, you are most likely running into an issue with the fix for
> FreeBSD 10-CURRENT in bsd.port.mk, causing the lto-plugin stage
> configure script to fail.
>
> This is because the gcc ports unpack their source code into
> ${WRKDIR}/gcc-${VERSI
On 2011-12-07 05:56, O. Hartmann wrote:
On FreeBSD 10.0-CURRENT/amd64 I run into the error shown below when
updating the installation of the gcc46 compiler suite.
If you report port compilation errors, always use DISABLE_MAKE_JOBS,
otherwise the actual error message will drown in multithreaded
20 matches
Mail list logo
