Hi.
On 24.03.2013 0:05, Eugene M. Zheganin wrote:
Hi.
On 19.03.2013 12:03, YongHyeon PYUN wrote:
I have no idea how this change can freeze your box. It would be
even better to know whether the issue was triggered by bge(4)
changes. I think you can use bge(4)/brgphy(4) of 8.3-RELEASE on
your
Hi.
On 19.03.2013 12:03, YongHyeon PYUN wrote:
I have no idea how this change can freeze your box. It would be
even better to know whether the issue was triggered by bge(4)
changes. I think you can use bge(4)/brgphy(4) of 8.3-RELEASE on
your stable/8. Copy required files from 8.3-RELEASE to
On Mon, Mar 18, 2013 at 10:45:24AM +0600, Eugene M. Zheganin wrote:
Hi.
On 14.03.2013 13:29, YongHyeon PYUN wrote:
I thought you were using stable/8 but it seems you have slightly
older stable/8. The bge(4) code difference between CURRENT and
stable9/stable8 is very minor.
Nah, I really
Hi.
On 19.03.2013 12:03, YongHyeon PYUN wrote:
I have no idea how this change can freeze your box. It would be
even better to know whether the issue was triggered by bge(4)
changes. I think you can use bge(4)/brgphy(4) of 8.3-RELEASE on
your stable/8. Copy required files from 8.3-RELEASE to
Hi.
On 14.03.2013 13:29, YongHyeon PYUN wrote:
I thought you were using stable/8 but it seems you have slightly
older stable/8. The bge(4) code difference between CURRENT and
stable9/stable8 is very minor.
Nah, I really am running recent 8/stable. My mistake was to try to apply
the whole code
Hi.
On 13.03.2013 07:57, YongHyeon PYUN wrote:
If your controller supports ASF/IPMI access please apply r248226
to stable/8 and let me know whether that makes any difference.
I believe ignoring ASF/IPMI firmware is not good idea since the
ASF/IPMI firmware will run regardless of
On Thu, Mar 14, 2013 at 12:44:33PM +0600, Eugene M. Zheganin wrote:
Hi.
On 13.03.2013 07:57, YongHyeon PYUN wrote:
If your controller supports ASF/IPMI access please apply r248226
to stable/8 and let me know whether that makes any difference.
I believe ignoring ASF/IPMI firmware is not
On Thu, Feb 28, 2013 at 12:37:03PM +0100, Miroslav Lachman wrote:
YongHyeon PYUN wrote:
On Wed, Feb 27, 2013 at 12:09:28PM +0100, Miroslav Lachman wrote:
[...]
I can provide you full access to this machine (if you want) or let me
know, what version I should check. Older versions (6.x -
On Thu, Mar 07, 2013 at 05:15:48PM +0900, YongHyeon PYUN wrote:
On Thu, Mar 07, 2013 at 01:14:03PM +0600, Eugene M. Zheganin wrote:
Hi.
On 07.03.2013 12:23, YongHyeon PYUN wrote:
On Thu, Mar 07, 2013 at 11:08:50AM +0600, Eugene M. Zheganin wrote:
It was definitely older than months.
On Thu, Mar 07, 2013 at 01:14:03PM +0600, Eugene M. Zheganin wrote:
Hi.
On 07.03.2013 12:23, YongHyeon PYUN wrote:
On Thu, Mar 07, 2013 at 11:08:50AM +0600, Eugene M. Zheganin wrote:
It was definitely older than months. It was running something similar
to FreeBSD 8.2-STABLE #0: Mon Sep
Hi.
Hi.
On 06.03.2013 12:26, YongHyeon PYUN wrote:
If you were using latest stable/8, the result would be same on
CURRENT.
How frequently do you see the watchdog timeouts? Is there way to
reproduce it?
Would you show me the output of dmesg (bge(4) and brgphy(4) only)
and pciconf -lcbv?
I
Hi.
On 06.03.2013 12:26, YongHyeon PYUN wrote:
If you were using latest stable/8, the result would be same on
CURRENT.
How frequently do you see the watchdog timeouts? Is there way to
reproduce it?
Would you show me the output of dmesg (bge(4) and brgphy(4) only)
and pciconf -lcbv?
I just
On Wed, Mar 06, 2013 at 04:00:34PM +0600, Eugene M. Zheganin wrote:
Hi.
Hi.
On 06.03.2013 12:26, YongHyeon PYUN wrote:
If you were using latest stable/8, the result would be same on
CURRENT.
How frequently do you see the watchdog timeouts? Is there way to
reproduce it?
Would you
Hi.
On 07.03.2013 8:24, YongHyeon PYUN wrote:
What was previous SVN revision number on that machine?
The support for 5718/5719/5720 was merged to stable/8 about 3
months ago.
It was definitely older than months. It was running something similar
to FreeBSD 8.2-STABLE #0: Mon Sep 19 08:10:00
On Thu, Mar 07, 2013 at 11:08:50AM +0600, Eugene M. Zheganin wrote:
Hi.
On 07.03.2013 8:24, YongHyeon PYUN wrote:
What was previous SVN revision number on that machine?
The support for 5718/5719/5720 was merged to stable/8 about 3
months ago.
It was definitely older than months. It was
Hi,
here is my situation, much like the issue
On 06.03.2013 12:26, YongHyeon PYUN wrote:
If you were using latest stable/8, the result would be same on
CURRENT.
I use FreeBSD 9.1-RELEASE #0 r243825: amd65 + ZFS
on HP ProLiant DL360e Gen8
the box has two 4 headed cards igb(4) I350 and bge(4)
On Thu, Mar 07, 2013 at 08:22:51AM +0300, Zeus Panchenko wrote:
Hi,
here is my situation, much like the issue
No, your issue is completely different one.
On 06.03.2013 12:26, YongHyeon PYUN wrote:
If you were using latest stable/8, the result would be same on
CURRENT.
I use FreeBSD
Hi.
On 07.03.2013 12:23, YongHyeon PYUN wrote:
On Thu, Mar 07, 2013 at 11:08:50AM +0600, Eugene M. Zheganin wrote:
It was definitely older than months. It was running something similar
to FreeBSD 8.2-STABLE #0: Mon Sep 19 08:10:00 YEKST 2011, this is the
uname from a neighbor machine.
I
Hi.
On 28.02.2013 11:35, YongHyeon PYUN wrote:
The reporter said the machine was Sun Fire X2200 M2 so I guess you
may see the same issue on both stable/9 and stable/8. Ideally the
loader tunable hw.bge.allow_asf should not be there and driver
should take care of it by checking the existence
On Wed, Mar 06, 2013 at 11:48:13AM +0600, Eugene M. Zheganin wrote:
Hi.
On 28.02.2013 11:35, YongHyeon PYUN wrote:
The reporter said the machine was Sun Fire X2200 M2 so I guess you
may see the same issue on both stable/9 and stable/8. Ideally the
loader tunable hw.bge.allow_asf should
YongHyeon PYUN wrote:
On Wed, Feb 27, 2013 at 12:09:28PM +0100, Miroslav Lachman wrote:
[...]
I can provide you full access to this machine (if you want) or let me
know, what version I should check. Older versions (6.x - 8.3) are
working fine with hw.bge.allow_asf=1 in loader.conf. I didn't
On Wed, Feb 27, 2013 at 12:09:28PM +0100, Miroslav Lachman wrote:
YongHyeon PYUN wrote:
On Wed, Feb 27, 2013 at 12:05:47AM +0600, Eugene M. Zheganin wrote:
[...]
bge(4)'s IPMI support for old controllers had many issues and
didn't work well. Only some of users had luck to enjoy it.
Hi.
On 25.02.2013 14:20, YongHyeon PYUN wrote:
On Sun, Feb 24, 2013 at 11:06:42AM +0100, Kajetan Staszkiewicz wrote:
Dnia sobota, 23 lutego 2013 o 04:54:07 Marc Fournier napisał(a):
We just picked up 5 new HP DL 360p Gen8 E5-2630 2P servers … just installed
9.1-RELEASE, and it looks like all
On Wed, Feb 27, 2013 at 12:05:47AM +0600, Eugene M. Zheganin wrote:
Hi.
On 25.02.2013 14:20, YongHyeon PYUN wrote:
On Sun, Feb 24, 2013 at 11:06:42AM +0100, Kajetan Staszkiewicz wrote:
Dnia sobota, 23 lutego 2013 o 04:54:07 Marc Fournier napisał(a):
We just picked up 5 new HP DL 360p Gen8
On Fri, Feb 22, 2013 at 07:54:07PM -0800, Marc Fournier wrote:
We just picked up 5 new HP DL 360p Gen8 E5-2630 2P servers … just installed
9.1-RELEASE, and it looks like all of the hardware is detected properly, and
being configured …
After reboot, I start getting the 'watchdog
On Sun, Feb 24, 2013 at 11:06:42AM +0100, Kajetan Staszkiewicz wrote:
Dnia sobota, 23 lutego 2013 o 04:54:07 Marc Fournier napisał(a):
We just picked up 5 new HP DL 360p Gen8 E5-2630 2P servers … just installed
9.1-RELEASE, and it looks like all of the hardware is detected properly,
and
Dnia sobota, 23 lutego 2013 o 04:54:07 Marc Fournier napisał(a):
We just picked up 5 new HP DL 360p Gen8 E5-2630 2P servers … just installed
9.1-RELEASE, and it looks like all of the hardware is detected properly,
and being configured …
After reboot, I start getting the 'watchdog timeout -
We just picked up 5 new HP DL 360p Gen8 E5-2630 2P servers … just installed
9.1-RELEASE, and it looks like all of the hardware is detected properly, and
being configured …
After reboot, I start getting the 'watchdog timeout - resetting' message on
bge0 … I've searched the web, and found
28 matches
Mail list logo
