Cette newsletter vous a été envoyée au format graphique HTML.
Si vous lisez cette version, alors votre logiciel de messagerie préfère les
e-mails au format texte.
Vous pouvez lire la version originale en ligne:
http:/
- Original Message -
> Bezüglich Bryan Venteicher's Nachricht vom 05.08.2013 02:12 (localtime):
> > Hi,
> >
> > I've ported the OpenBSD vmxnet3 ethernet driver to FreeBSD. I did a
> > lot of cleanup, bug fixes, new features, etc (+2000 new lines) along
> > the way so there is not much of
On Mon, Aug 26, 2013 at 07:11:48PM -0400, Rick Macklem wrote:
> Matthias Schuendehuette wrote:
> > Hello,
> >
> > yesterday I got a kernel crash on my server (a ProLiant DL380 G5):
> >
> > "panic: stack overflow detected; backtrace may be corrupted"
> >
> > Kernel is "9.2-PRERELEASE FreeBSD 9.2-
Matthias Schuendehuette wrote:
> Hello,
>
> yesterday I got a kernel crash on my server (a ProLiant DL380 G5):
>
> "panic: stack overflow detected; backtrace may be corrupted"
>
> Kernel is "9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #7 r254683"
>
>
> The stack trace reads:
>
> #0 doadump (textdu
On 08/26/13 14:21, Glen Barber wrote:
On Mon, Aug 26, 2013 at 02:16:39PM -0700, Dave Hayes wrote:
On 08/26/13 13:16, Glen Barber wrote:
On Mon, Aug 26, 2013 at 01:01:06PM -0700, Dave Hayes wrote:
I've been trying to get emulators/virtualbox-ose-kmod to compile
>from ports on a clang built 9-S
On Mon, Aug 26, 2013 at 02:16:39PM -0700, Dave Hayes wrote:
> On 08/26/13 13:16, Glen Barber wrote:
> >On Mon, Aug 26, 2013 at 01:01:06PM -0700, Dave Hayes wrote:
> >>I've been trying to get emulators/virtualbox-ose-kmod to compile
> >>from ports on a clang built 9-STABLE:
> >>
> >> # uname -v
> >
On 08/26/13 13:16, Glen Barber wrote:
On Mon, Aug 26, 2013 at 01:01:06PM -0700, Dave Hayes wrote:
I've been trying to get emulators/virtualbox-ose-kmod to compile
from ports on a clang built 9-STABLE:
# uname -v
FreeBSD 9.1-STABLE #0 r251391M: Tue Jun 4 09:47:42 PDT 2013
Daniel Braniss wrote:
> I upgraded our web server, and only after 3 hours it hung :-(
> (as a side note, I have 2 other web servers, also running 9.2 doing
> great :-)
> go figure.
>
> anyways, in
> ftp://ftp.cs.huji.ac.il/users/danny/freebsd/core.txt/0
>
> is the info after a forced panic.
On 8/26/2013 3:59 PM, Schaich Alonso wrote:
> On Mon, 26 Aug 2013 15:07:42 -0400
> Mike Tancsa wrote:
>
>>
>> Does anyone have any idea how to correct this issue ? Already blew away
>> /usr/src and /usr/obj in case something got corrupted.
>>
>>
>
> Taking it you mean stable/9 by RELENG_9, it c
On Mon, Aug 26, 2013 at 01:01:06PM -0700, Dave Hayes wrote:
> I've been trying to get emulators/virtualbox-ose-kmod to compile
> from ports on a clang built 9-STABLE:
>
> # uname -v
> FreeBSD 9.1-STABLE #0 r251391M: Tue Jun 4 09:47:42 PDT 2013
> r...@fb9build.jetcafe.org:/usr/obj/usr/src.amd64/
I've been trying to get emulators/virtualbox-ose-kmod to compile from
ports on a clang built 9-STABLE:
# uname -v
FreeBSD 9.1-STABLE #0 r251391M: Tue Jun 4 09:47:42 PDT 2013
r...@fb9build.jetcafe.org:/usr/obj/usr/src.amd64/sys/GENERIC amd64
# cc -v
FreeBSD clang version 3.2 (tags/RELEASE
On Sun, Aug 25, 2013 at 03:35:06PM -0700, Thomas Mueller wrote:
> > On Sat, Aug 24, 2013 at 08:53:31PM -0700, Thomas Mueller wrote:
> > > Some updates:
>
> > > I could see what happens if I try to boot the FreeBSD boot partition on
> > > the hard drive using the Super Grub Disk with chainloader.
On Mon, 26 Aug 2013 15:07:42 -0400
Mike Tancsa wrote:
>
> Does anyone have any idea how to correct this issue ? Already blew away
> /usr/src and /usr/obj in case something got corrupted.
>
>
Taking it you mean stable/9 by RELENG_9, it can be ``fixed'' by updating your
sources, to any revisio
On Mon, 26 Aug 2013 15:07:42 -0400
Mike Tancsa wrote:
> Does anyone have any idea how to correct this issue ? Already blew away
> /usr/src and /usr/obj in case something got corrupted.
I think I've resolved this issue by rebuilding and reinstalling yacc
from /usr/src/usr.bin/yacc before runnin
Does anyone have any idea how to correct this issue ? Already blew away
/usr/src and /usr/obj in case something got corrupted.
cc -O2 -pipe -DDES -std=gnu99 -fstack-protector -Wsystem-headers
-Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter
-Wstrict-prototypes -Wmissing-prototypes -Wpoin
Am 26.08.2013 11:28, schrieb Harald Schmalzbauer:
> Bezüglich Adrian Chadd's Nachricht vom 26.08.2013 10:34
> (localtime):
>> Hi,
>>
>> There's bus limits on how much data you can push over a PCI bus.
>> You can look around online to see what 32/64 bit, 33/66MHz PCI
>> throughput estimates are.
>>
Hello,
yesterday I got a kernel crash on my server (a ProLiant DL380 G5):
"panic: stack overflow detected; backtrace may be corrupted"
Kernel is "9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #7 r254683"
The stack trace reads:
#0 doadump (textdump=1) at pcpu.h:249
249 pcpu.h: No such file or directo
I upgraded our web server, and only after 3 hours it hung :-(
(as a side note, I have 2 other web servers, also running 9.2 doing great :-)
go figure.
anyways, in
ftp://ftp.cs.huji.ac.il/users/danny/freebsd/core.txt/0
is the info after a forced panic.
my guts say its running out of resou
Updated via svnup from releng/9.0 to releng/9.2 (r254910) and I got this
in buildworld:
cc1: warnings being treated as errors
/usr/src/usr.bin/xinstall/xinstall.c: In function 'metadata_log':
/usr/src/usr.bin/xinstall/xinstall.c:1331: warning: implicit declaration
of function 'strsvis'
/usr/src/us
The third release candidate builds of the 9.2-RELEASE release cycle
are now available on the FTP servers for the amd64, i386, ia64, powerpc,
powerpc64, and sparc64 architectures.
This is expected to be the final release candidate for the 9.2-RELEASE
cycle.
The image checksums follow at the end of
On 24/07/2013 13.19, Ronald Klop wrote:
On Thu, 18 Jul 2013 09:52:13 +0200, Maurizio Vairani
wrote:
On 17/07/2013 17:29, Julian H. Stacey wrote:
Maurizio Vairani wrote:
On 17/07/2013 11:50, Ronald Klop wrote:
On Wed, 17 Jul 2013 10:27:09 +0200, Maurizio Vairani
wrote:
Hi all,
on a Co
Bezüglich Adrian Chadd's Nachricht vom 26.08.2013 10:34 (localtime):
> Hi,
>
> There's bus limits on how much data you can push over a PCI bus. You
> can look around online to see what 32/64 bit, 33/66MHz PCI throughput
> estimates are.
>
> It changes massively if you use small versus large frames
Hi,
There's bus limits on how much data you can push over a PCI bus. You can
look around online to see what 32/64 bit, 33/66MHz PCI throughput estimates
are.
It changes massively if you use small versus large frames as well.
The last time I tried it i couldn't hit gige on PCI; I only managed to
On 24/08/2013 17:57, Victor Balada Diaz wrote:
> On Mon, Aug 19, 2013 at 12:27:04AM +0200, Dominic Fandrey wrote:
>> On 19/08/2013 00:13, Adrian Chadd wrote:
>>> That's really odd. But then, it's a firmware driven NIC, who knows what
>>> kind of weird crap is going on under the hood.
>>
>> Yes, it'
Hello,
I recycled an older box and put an i350-2 together with a second 82541GI
(PCI-slot, one already on-board) into it.
The two i350-ports are used with VMDq for ESXi5.1.
The two 82541GI are used as lagg-nics by a 9.2-RC (amd64) guest as
passthrou PCI device.
Always had good results with such s
25 matches
Mail list logo
