context switches,
which is why the Linux approach does what it does.
I have not spent time with that issue, its good to know that there
could be problems
lurking with it. But if you can simply go with MSIX I would do that
for now.
Jack
On Thu, Jan 13, 2011 at 1:42 PM, Charles
es
On 1/13/11 1:27 PM, Jack Vogel wrote:
The 8.2 latest does have the latest igb, so using that should be
indicative...
Jack
On Thu, Jan 13, 2011 at 7:56 AM, Charles Owens
mailto:cow...@greatbaysoftware.com>> wrote:
Ok... I got my wires crossed: our first time testing 8.1 on
due to having MSIX interrupts disabled
on the system, I doubt that
is going to be the "issue" for others.
Get the latest version of the igb code and see if that helps you as a
first step.
Jack
On Wed, Jan 12, 2011 at 6:43 PM, Charles Owens
mailto:cow...@greatbaysoftware.com>&
ou had any luck?
Thanks,
Charles
Charles Owens
Great Bay Software, Inc.
On 1/3/11 4:02 PM, Robin Sommer wrote:
Hello all,
quite a while ago I asked about the problem below. Unfortunately, I
haven't found a solution yet and I'm actually still seeing these
timeouts after just upgra
, Charles Owens
mailto:cow...@greatbaysoftware.com>> wrote:
Well, I believe we have an answer:
http://www.intel.com/support/network/adapter/pro100/sb/CS-030873.htm
The motherboard definitely is PCIe 2.0 . The page suggests these
cards for use with a PCIe2.0 system:
# Inte
n also send me all the details
about the board, just to
make sure I can get the exact one and then I'll try it here. This is
quad port fiber, right? I was
thinking this was PCI ID 0x1527, 82580 adapter. The support is in
HEAD now.
Regards,
Jack
On Mon, Nov 15, 2010 at
ng this was PCI ID 0x1527, 82580 adapter. The support is in
HEAD now.
Regards,
Jack
On Mon, Nov 15, 2010 at 1:45 PM, Charles Owens
mailto:cow...@greatbaysoftware.com>> wrote:
Jack, I'm afraid that with the card _not_ installed we get
identical pciconf output. We'
s I see are in the 0x3XXX range and those
are not
network devices.
Maybe its a bad slot?
Jack
On Mon, Nov 15, 2010 at 11:59 AM, Charles Owens
wrote:
Great... thanks! Please see attached. BTW, the system is running
8.0-RELEASE-p2 i386 (PAE).
Charles
On 11/13/10 2:24 AM, Jack Vogel wrote:
p
27;ve been fighting a bug in
the header split
code.
Show me what the output looks like, and I'll get ya fixed up, dont
worry :)
Jack
On Fri, Nov 12, 2010 at 2:08 PM, Charles Owens
mailto:cow...@greatbaysoftware.com>> wrote:
Hello,
We're trying to work with newly purcha
- is there a known
issue with the 4-port version?
We've tried three different cards of this model, all with same result.
Thanks in advance for any help.
Charles
--
Charles Owens
Great Bay Software, Inc.
___
freebsd-net@freebsd.org ma
relies
on somehow, such that this is an iffy proposition?
* Has the e1000 driver in -STABLE now mostly stabilized... or is
additional engineering expected in the near term?
Any and all assistance is greatly appreciated!
Thanks,
Charles
--
Charles
]
igb0: [ITHREAD]
igb0: Ethernet address: 00:15:17:b4:cf:e4
igb1: port 0x3000-0x301f
mem 0xb1b0-0xb1b1,0xb1b4-0xb1b43fff irq 28 at device 0.1 on pci1
igb1: Using MSIX interrupts with 3 vectors
igb1: [ITHREAD]
igb1: [ITHREAD]
igb1: [ITHREAD]
igb1: Ethernet address: 00:15:17:b4:cf:e5
I've dug around in the source repo... it appears the new code is just
shy of being MFC'd. Any known caveats with the new code or is it by
all accounts good to go?
I'm going to try testing it in 8.0. Thanks
Charles Owens
Great Bay Software, Inc.
Charles Owens wrot
up/down/up), but I'm
concerned that we might fall victim to other symptoms mentioned if we
put the system under load.
Would you recommend we apply the igb patch you've mentioned? Is it in
RELENG_8 yet, or is it still under development?
Thanks very much,
Charles
Charles Owens
Great Bay Soft
Charles Owens wrote:
> Hello,
>
> I'm working with some code (snippet below) that fails with
> libnet_get_hwaddr() function (it returns false). The code works fine
> under 7.x but not with 8.0 .
>
> Any thoughts as to what might be going on?
>
Issue solved. I
octet, 6);
return 0;
}
--
Charles Owens
Great Bay Software, Inc.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Pyun YongHyeon wrote:
> On Mon, Jan 18, 2010 at 10:40:55AM -0500, Charles Owens wrote:
>> Hello,
>>
>> I'm working with a system (IBM System x3550 M2) that has four onboard
>> bce(4) NICs. Using FreeBSD 8.0, the first two seem to function fine,
>> but the sec
Pyun YongHyeon wrote:
> On Mon, Jan 18, 2010 at 10:40:55AM -0500, Charles Owens wrote:
>> Hello,
>>
>> I'm working with a system (IBM System x3550 M2) that has four onboard
>> bce(4) NICs. Using FreeBSD 8.0, the first two seem to function fine,
>> but the sec
src/sys/dev/bce/if_bce.c(1533):
Error: PHY read timeout!
phy = 1, reg = 0x0001
What's are the best next steps to take in figuring this out? Thanks in
advance for any assistance. Kernel boot log appending below.
Charles
--
Charles Owens
Great Bay Software, Inc.
Copyright (c) 1992-2
19 matches
Mail list logo
