> What happens if you set hw.bge.allow_asf to 0 and use auto-negotiation
> on both sides?
it works! the switch was already auto-neg, and i forced auto-neg on the
server side.
thanks. this was not pleasant. did i remember to whine that i am in
tokyo and the server is on the beast coast of the s
There is a bug in the Tyan S4881/S4882 PCI-X bridges that was fixed with a
patch in 7.x (thank you very much). This patch is not present in the
8.2-STABLE code and the symptoms (watchdog timeouts) have recurred.
The watchdog timeouts do not appear to be present after I switched to an
Intel gi
Hi,
On Sat, Jan 28, 2012 at 04:45:01PM -0800, Eric Bullen wrote:
> Hi All,
>
> I'm running the following:
>
> FreeBSD x 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC
> 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
>
> I couldn't figure out why SOME of r
On 01/28/2012 16:45, Eric Bullen wrote:
/user/local/bin
--
It's always a long day; 86400 doesn't fit into a short.
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
_
Hi All,
I'm running the following:
FreeBSD x 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC
2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
I couldn't figure out why SOME of root's cronjobs weren't running, and
others were. Here's my test crontab for root:
Hi,
On Wed, 18 Jan 2012 20:23:25 +0200 Artem Kajalainen wrote:
AK> Hello,
AK> I'm trying to setup hastd on two servers and got error, which I can't
AK> understand. Box is running as primary, then i reboot it, another box
AK> get primary role by carp events, then 1st box at boot tries to se
On Sun, Jan 29, 2012 at 04:56:28AM +0900, Randy Bush wrote:
> > Hrm, the problem apparently is that while when probing, the PHY
> > still knows about the media it supports, it just has forgotten
> > about it after the reset during attach. There was a change prior
> > to 8.2 which would turn this fr
>> Have you tried to set the loader-tunable hw.bge.allow_asf to 0?
>> The default for that option still is different between 8 and 9+.
> it no longer panics when booting, but the interface comes up not
> seeing carrier
an additional datum.
o with hw.bge.allow_asf untouched, i.e. default
o with
> Hrm, the problem apparently is that while when probing, the PHY
> still knows about the media it supports, it just has forgotten
> about it after the reset during attach. There was a change prior
> to 8.2 which would turn this from silently being ignored (which
> generally might or might not work
Thank you to all of you for your replies. I'll try next week
and let you know.
My mail server was down for a few hours, but everything should
be ok now...
Giulio.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
Giulio Ferro wrote:
> I forgot to mentioned that I compiled both servers with
> option KGSSAPI and device crypto, and I enabled gssd
> on both.
>
> Is there anyone who was able to configure this setup?
>
I had a server at the nfsv4 testing event last June and it
worked ok. I haven't tried one sinc
On Sat, Jan 28, 2012 at 09:34:04PM +0900, Randy Bush wrote:
> >> ok, i
> >> o used device.hints to disable both bge interfaces
> >> o booted successfully
> >> o used serial console
> >> o ifconfiged bge0 to the normal addresses
> >> o and it is working
> >>
> >> i suspect that something
>> ok, i
>> o used device.hints to disable both bge interfaces
>> o booted successfully
>> o used serial console
>> o ifconfiged bge0 to the normal addresses
>> o and it is working
>>
>> i suspect that something sucks in bge initialization at startup.
>> insightful, i know. sorry.
>
>
On Thu, Jan 26, 2012 at 12:24:11PM +0900, Randy Bush wrote:
> ok, i
> o used device.hints to disable both bge interfaces
> o booted successfully
> o used serial console
> o ifconfiged bge0 to the normal addresses
> o and it is working
>
> i suspect that something sucks in bge initializa
On Tuesday 17 January 2012 22.52, Patrick M. Hausen wrote:
> Hi, all,
>
> Am 17.01.2012 um 18:59 schrieb peter h :
>
> > I have been beating on of these a few days, i have udes freebsd 9.0 and 8.2
> > Both fails when i engage > 10 disks, the system craches and messages :
> > "Hyper transport sync
I forgot to mentioned that I compiled both servers with
option KGSSAPI and device crypto, and I enabled gssd
on both.
Is there anyone who was able to configure this setup?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
16 matches
Mail list logo
