Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Dec 2008 00:29:33 -0600
From:      "Sam Fourman Jr." <sfourman@gmail.com>
To:        "Ian FREISLICH" <ianf@clue.co.za>
Cc:        pyunyh@gmail.com, current@freebsd.org
Subject:   Re: msk(4) stops working.
Message-ID:  <11167f520812232229g5ee1d475kdd92fd6511c50c29@mail.gmail.com>
In-Reply-To: <E1LFMVU-0001fB-Mz@clue.co.za>
References:  <E1LF7Oc-000Djt-C1@clue.co.za> <20081224021016.GF95088@cdnetworks.co.kr> <E1LFMVU-0001fB-Mz@clue.co.za>

next in thread | previous in thread | raw e-mail | index | archive | help
>>
>> About 2-3 months ago I committed workaround for Yukon silicon bug.
>> Do you use latest CURRENT?
>
> Yes, this is on yesterday's sources.  It was better for a month or
> so, but over the last month it's been really bad.  Now I can provoke
> this condition in under 1 minute of uptime.
>
I have a few msk cards, and I could stand to install -CURRENT on a system
how do I reproduce your problem?

Sam Fourman Jr.
Fourman Networks



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11167f520812232229g5ee1d475kdd92fd6511c50c29>