On 5/10/10, Brandon Gooch wrote:
>
> Is there a final "target state" regarding the work and/or a time-frame
> for completion? Perhaps a "heads-up" e-mail to the freebsd-current
> mailing list when the first round of commits have settled in? I'm
> wondering, due to the Nvidia issue stated in this
On Sat, May 8, 2010 at 4:44 PM, Kip Macy wrote:
> On Sat, May 8, 2010 at 2:39 PM, Brandon Gooch
> wrote:
>> On Sat, May 8, 2010 at 4:20 PM, b. f. wrote:
>>> On 05/08/10 13:36, Alan Cox wrote:
Doug Barton wrote:
> On 05/05/10 11:56, Alan Cox wrote:
>
>> I'm afraid that I would ad
On Sat, May 8, 2010 at 2:20 PM, b. f. wrote:
> On 05/08/10 13:36, Alan Cox wrote:
>> Doug Barton wrote:
>>> On 05/05/10 11:56, Alan Cox wrote:
>>>
I'm afraid that I would advise waiting a few days. This round of
changes
are not yet complete.
>
> What performance differences, if any
On 5/8/10, Kip Macy wrote:
> On Sat, May 8, 2010 at 2:39 PM, Brandon Gooch
> wrote:
>> On Sat, May 8, 2010 at 4:20 PM, b. f. wrote:
>>> On 05/08/10 13:36, Alan Cox wrote:
Doug Barton wrote:
> On 05/05/10 11:56, Alan Cox wrote:
>
>> I'm afraid that I would advise waiting a few da
On Sat, May 8, 2010 at 2:39 PM, Brandon Gooch
wrote:
> On Sat, May 8, 2010 at 4:20 PM, b. f. wrote:
>> On 05/08/10 13:36, Alan Cox wrote:
>>> Doug Barton wrote:
On 05/05/10 11:56, Alan Cox wrote:
> I'm afraid that I would advise waiting a few days. This round of
> changes
>
On 08.05.2010 22:30 (UTC+1), Doug Barton wrote:
On 05/05/10 11:56, Alan Cox wrote:
I'm afraid that I would advise waiting a few days. This round of changes
are not yet complete.
Is the coast clear yet? :) I have been holding off on updating -current
due to the SUJ stuff, but that seems to h
On Sat, May 8, 2010 at 4:20 PM, b. f. wrote:
> On 05/08/10 13:36, Alan Cox wrote:
>> Doug Barton wrote:
>>> On 05/05/10 11:56, Alan Cox wrote:
>>>
I'm afraid that I would advise waiting a few days. This round of
changes
are not yet complete.
>
> What performance differences, if any
Doug Barton wrote:
On 05/08/10 13:36, Alan Cox wrote:
Doug Barton wrote:
On 05/05/10 11:56, Alan Cox wrote:
I'm afraid that I would advise waiting a few days. This round of
changes
are not yet complete.
Is the coast clear yet? :) I have been holding off on upd
On 05/08/10 13:36, Alan Cox wrote:
> Doug Barton wrote:
>> On 05/05/10 11:56, Alan Cox wrote:
>>
>>> I'm afraid that I would advise waiting a few days. This round of
>>> changes
>>> are not yet complete.
What performance differences, if any, can we expect on uniprocessors
from the vm page lock-re
On 05/08/10 13:36, Alan Cox wrote:
> Doug Barton wrote:
>> On 05/05/10 11:56, Alan Cox wrote:
>>
>>> I'm afraid that I would advise waiting a few days. This round of
>>> changes
>>> are not yet complete.
>>>
>>
>> Is the coast clear yet? :) I have been holding off on updating -current
>> d
Doug Barton wrote:
On 05/05/10 11:56, Alan Cox wrote:
I'm afraid that I would advise waiting a few days. This round of changes
are not yet complete.
Is the coast clear yet? :) I have been holding off on updating -current
due to the SUJ stuff, but that seems to have mostly settled dow
On 05/05/10 11:56, Alan Cox wrote:
>
> I'm afraid that I would advise waiting a few days. This round of changes
> are not yet complete.
Is the coast clear yet? :) I have been holding off on updating -current
due to the SUJ stuff, but that seems to have mostly settled down now, so
I'm hoping that
On Wed, May 5, 2010 at 11:19 AM, Yuri Pankov wrote:
> Hi,
>
> After recent changes to sys/vm/ by alc@, I'm getting panics as soon as I
> start xorg-server with nvidia-driver (both 195.22 and 195.36.15):
>
> panic: mutex page lock not owned at
> /home/yuri/src/FreeBSD/head/sys/vm/vm_page.c:1547
>
Hi,
After recent changes to sys/vm/ by alc@, I'm getting panics as soon as I
start xorg-server with nvidia-driver (both 195.22 and 195.36.15):
panic: mutex page lock not owned at
/home/yuri/src/FreeBSD/head/sys/vm/vm_page.c:1547
(sorry, can't get kernel to dump correctly to provide more info:
C
14 matches
Mail list logo
