I should be able to get the shared code part into 6.3 once problems
are wrung out.
Jack
On Fri, Mar 7, 2008 at 8:17 AM, George V. Neville-Neil
<[EMAIL PROTECTED]> wrote:
> At Mon, 3 Mar 2008 13:43:45 -0800,
>
> Jack Vogel wrote:
> >
> > The fix to this problem is in the new shared code that got
At Mon, 3 Mar 2008 13:43:45 -0800,
Jack Vogel wrote:
>
> The fix to this problem is in the new shared code that got checked into
> CURRENT on Friday. I will be MFCing the changes eventually but
> if you want to test now you'll need to go with CURRENT.
>
Rockin. Will this go into 6 as well or is
t; But Jack gave me another hope.
>> >
>> > WBR
>> >
>> > --
>> > Vladimir Ivanov
>> > Network Operations Center
>> > OOO "Yandex"
>> > t: +7 495 739-7000
>> > f: +7 495 739-7070
>> > @: [EM
WBR
> >
> > --
> > Vladimir Ivanov
> > Network Operations Center
> > OOO "Yandex"
> > t: +7 495 739-7000
> > f: +7 495 739-7070
> > @: [EMAIL PROTECTED] (corporate)
> > [EMAIL PROTECTED] (personal)
> > www: www.yandex.ru
> > --
> >
> >
[EMAIL PROTECTED] (personal)
> www: www.yandex.ru
> --
>
> ___
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
--
View
>
> Any suggestions?
>
>
> Regards,
>
> - Andrew
> ___
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
Jack Vogel wrote:
But I do not think we need more debugging at this point, when the
new code is checked in it will be great to have everyone that has seen
the issue test it though.
Will look forward to testing it, though its intermittent nature for me
means I might have trouble reproducing it.
On Jan 26, 2008 7:21 AM, Steven Hartland <[EMAIL PROTECTED]> wrote:
> Also seeing this here, if we can help debug this please shout.
>
> Regards
> Steve
Kris was seeing this problem, and he has been testing with our latest
shared code which had what I thought was a fix for the problem.
It
Also seeing this here, if we can help debug this please shout.
Regards
Steve
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is
Andrew Snow wrote:
Vladimir Ivanov wrote:
We've same issue w/Supermicro boards if IPMI daughterboard installed.
A problem looks as PHY reg reads/writes fails.
Ahh, that explains it, thanks.
The management cards seem to cause multiple problems with the FreeBSD em
driver over time. I don't wan
Vladimir Ivanov wrote:
We've same issue w/Supermicro boards if IPMI daughterboard installed. A
problem looks as PHY reg reads/writes fails.
Ahh, that explains it, thanks.
The management cards seem to cause multiple problems with the FreeBSD em
driver over time. I don't want to give up the IPM
Hi, All
Jack Vogel wrote:
Hi Andrew,
Someone else has already reported this to me and in fact he is testing
a shared code
fix to see if it resolves it. I will be updating the driver if it does.
Jack
We've same issue w/Supermicro boards if IPMI daughterboard installed. A
problem looks as PH
Hi Andrew,
Someone else has already reported this to me and in fact he is testing
a shared code
fix to see if it resolves it. I will be updating the driver if it does.
Jack
On Jan 20, 2008 12:32 AM, Andrew Snow <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have a recent Supermicro board (Super X7DWT
Hi,
I have a recent Supermicro board (Super X7DWT
Intel 5400 chipset) with two onboard NICs - Intel (ESB2/Gilgal) 82563EB
Dual-Port Gigabit Ethernet Controller
Usually boot up looks like this:
em0: port
0x3000-0x301f mem 0xda02-0xda03,0xda00-0xda01 irq 44 at
device 0.0
14 matches
Mail list logo
