YongHyeon PYUN wrote:
On Fri, Feb 08, 2013 at 08:27:55PM +0100, Oliver Fromme wrote:
re0: CMD 0x0c
re0: link state changed to UP
re0: link state changed to DOWN
re1: link state changed to UP
re1: link state changed to DOWN
re1: CMD 0x0c
re1: link state changed to UP
re0:
On Fri, Feb 08, 2013 at 08:27:55PM +0100, Oliver Fromme wrote:
I'm sorry for the late reply. I didn't have much time
this week to investigate this issue. At the moment I
implemented a work-around with an additional switch using
VLANs, but I'd really like to get the second NIC working.
John-Mark Gurney j...@funkthat.com wrote:
Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 23:04 +0100:
John-Mark Gurney wrote:
Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 19:15 +0100:
I'm running a recent stable/9 (about 14 days old).
What's the best way to
I'm sorry for the late reply. I didn't have much time
this week to investigate this issue. At the moment I
implemented a work-around with an additional switch using
VLANs, but I'd really like to get the second NIC working.
YongHyeon PYUN wrote:
On Mon, Feb 04, 2013 at 07:15:51PM +0100, Oliver
John-Mark Gurney wrote:
Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 23:04 +0100:
John-Mark Gurney wrote:
Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 19:15 +0100:
I'm running a recent stable/9 (about 14 days old).
What's the best way to debug this
On Mon, Feb 04, 2013 at 07:15:51PM +0100, Oliver Fromme wrote:
Hello,
I need some advice how to debug this issue ...
Recently I got a new mainboard for a router, it's a
Gigabyte GA-H77N-WIFI with two onboard re(4) NICs.
The problem is that re0 works fine and re1 doesn't:
It doesn't
Hello,
I need some advice how to debug this issue ...
Recently I got a new mainboard for a router, it's a
Gigabyte GA-H77N-WIFI with two onboard re(4) NICs.
The problem is that re0 works fine and re1 doesn't:
It doesn't receive any packets. Tcpdump displays all
outgoing packets, but no
Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 19:15 +0100:
I'm running a recent stable/9 (about 14 days old).
What's the best way to debug this problem? At the
moment I'm not even sure if it's the hardware, or if
it's FreeBSD's fault (or my fault) ...
Have you tried to disable msi
John-Mark Gurney wrote:
Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 19:15 +0100:
I'm running a recent stable/9 (about 14 days old).
What's the best way to debug this problem? At the
moment I'm not even sure if it's the hardware, or if
it's FreeBSD's fault (or my fault)
Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 23:04 +0100:
John-Mark Gurney wrote:
Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 19:15 +0100:
I'm running a recent stable/9 (about 14 days old).
What's the best way to debug this problem? At the
moment I'm not
10 matches
Mail list logo