Hello,
updating to r294020 solves the issue for me. Thank you. :)
Regards,
Yamagi
On Thu, 14 Jan 2016 19:31:45 +0300
Alexander V. Chernikov wrote:
> 14.01.2016, 19:16, "Alexander V. Chernikov" :
> > 14.01.2016, 18:29, "Yamagi Burmeister" :
> >> Hello
Hello,
with 11-CURRENT at r293913 I'm seeing this panic as soon as I'm trying
to connect through SSH:
Unread portion of the kernel message buffer:
panic: _mtx_lock_sleep: recursed on non-recursive mutex rtentry
@ /usr/src/sys/net/route.c:579
(kgdb) bt
#0 doadump (textdump=-2122574672) at pcpu.h
Hello,
it's been a while since I tested VIMAGE, but at the last time somewhere
in 10-CURRENT some UMA memory leaks were left when destroying vnets.
They weren't showstoppers for most workloads, but pretty anoying...
Have those been fixed?
Regards,
Yamagi
On Sat, 11 Oct 2014 10:58:13 -0700
Craig
On Fri, 1 Apr 2011, YongHyeon PYUN wrote:
On Thu, Mar 31, 2011 at 09:59:12PM +0200, Yamagi Burmeister wrote:
On Thu, 31 Mar 2011, YongHyeon PYUN wrote:
Thanks a lot! It seems the L1 controller has data corruption issue
when 64bit DMA addressing is used. Try this one.
Oops, there was a bug
On Thu, 31 Mar 2011, YongHyeon PYUN wrote:
Thanks a lot! It seems the L1 controller has data corruption issue
when 64bit DMA addressing is used. Try this one.
Oops, there was a bug in previous patch.
Try this instead.
Okay, that patch seems to do the trick. This was just a short test run
of
On Thu, 31 Mar 2011, YongHyeon PYUN wrote:
All boxes are quadcore machines with 8GB RAM, running FreeBSD/amd64.
After limiting the memory via hw.physmem to 3GB the problems are gone.
The box is running crashfree for more than 6 hours and has served over
300GB of data via age(4).
Thanks for te
On Wed, 30 Mar 2011, YongHyeon PYUN wrote:
Okay, I did a test run with RX checksum, TX checksum and both disabled.
In all three cases the crash occurs within about 20 minutes. I'm either
not sure that age(4) is the problem but it has definedly something to do
with the problem, since with another
On Wed, 30 Mar 2011, YongHyeon PYUN wrote:
On Wed, Mar 30, 2011 at 04:22:23PM +0200, Yamagi Burmeister wrote:
All for boxes are unstable if the Attansic NIC is in use, no one of them
survived more than 60 minutes of ~20mb/s network traffic. I managed to
get some coredumps and extracted the
Hi,
I recently got four about two years old Asus M3A-H/HDMI mainboards with
an integrated Attansic L2 ethernet controller. This NIC is supported by
age(4) and recognized by freebsd:
age0:
mem 0xfeac-0xfeaf irq 18 at device 0.0 on pci2
age0: 1280 Tx FIFO, 2364 Rx FIFO
age0: U
On Tue, 11 Jan 2011, Bjoern A. Zeeb wrote:
I've got several Hetzner EQ4 and on all these machines FreeBSD 8.1 runs
just fine. I've never seen this strange negotiation problem myself. But
maybe I was just lucky and got working mainboard and nic combinations.
So if further information is needed, I
On Tue, 11 Jan 2011, Lev Serebryakov wrote:
Very large and famous (due to very attractive prices) hosting
provider Hetzner.de discards FreeBSD support on dedicated servers,
because these servers can niot negotiate 100Mbit/DUPLEX when
switches' ports are limited to 100Mbit (1Gbit connection cost
On Wed, 10 Nov 2010, Pyun YongHyeon wrote:
On Tue, Nov 09, 2010 at 01:34:21PM -0800, Pyun YongHyeon wrote:
On Tue, Nov 09, 2010 at 10:01:36PM +0100, Yamagi Burmeister wrote:
On Tue, 9 Nov 2010, Pyun YongHyeon wrote:
No, the link stays at 1000Mbps so the driver must manually switch back
to
On Wed, 10 Nov 2010, Ian Smith wrote:
On Tue, 9 Nov 2010, Pyun YongHyeon wrote:
> On Tue, Nov 09, 2010 at 10:01:36PM +0100, Yamagi Burmeister wrote:
> > On Tue, 9 Nov 2010, Pyun YongHyeon wrote:
[..]
> > >You can switch to suspend mode with "acpiconf -s1". If all
On Tue, 9 Nov 2010, Pyun YongHyeon wrote:
No, the link stays at 1000Mbps so the driver must manually switch back
to 10/100Mbps.
Hmm, this is real problem for WOL. Establishing 1000Mbps link to
accept WOL frames is really bad idea since it can draw more power
than 375mA. Consuming more power t
Thanks for your reply.
On Mon, 8 Nov 2010, Pyun YongHyeon wrote:
Thanks for the patch. I attached slightly modified the code to
better match other WOL capable drivers in tree. Because data sheet
is not available I blindly made a patch based on your code. I have
a couple of questions which I ca
Hi,
some time ago we migrated a lot of boxes from Linux to FreeBSD. Those
machines have a "NVIDIA nForce4 CK804 MCP4" network adapter, supported
by nfe(4). Even if nfe(4) at least tries to enable the WOL capability of
the NIC it doesn't work and nfe(4) doesn't integrate with FreeBSDs (new)
WOL fr
16 matches
Mail list logo
