Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Sep 2009 12:04:05 +0300
From:      Dan Naumov <dan.naumov@gmail.com>
To:        "C. C. Tang" <hiyorin@gmail.com>
Cc:        Attilio Rao <attilio@freebsd.org>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: 7.2-release/amd64: panic, spin lock held too long
Message-ID:  <cf9b1ee00909190204q33ded00dyb86a4b53ed5194be@mail.gmail.com>
In-Reply-To: <4AB36E1F.6080401@gmail.com>
References:  <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com> <3bbf2fe10909121432x7bd4f7es497e9431c4e520d6@mail.gmail.com> <cf9b1ee00909121502v66566b46p754ed2f2e549555@mail.gmail.com> <4AB1A838.2040406@gmail.com> <3bbf2fe10909170216u29d994aj55c21efdfbc26ba5@mail.gmail.com> <4AB21005.6040104@gmail.com> <4AB36E1F.6080401@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 18, 2009 at 2:25 PM, C. C. Tang <hiyorin@gmail.com> wrote:
>> Attilio Rao wrote:
>>>
>>> 2009/9/17 C. C. Tang <hiyorin@gmail.com>:
>>>>>>
>>>>>> Dan, is that machine equipped with Hyperthreading?
>>>>>>
>>>>>> Attilio
>>>>>
>>>>> Yes. It's an Intel Atom 330, which is a dualcore CPU with HT (4 cores
>>>>> visible in "top" as a result)
>>>>
>>>> Yes, mine is also Atom 330.
>>>>
>>>> I cannot test the patch because my machine is also in production now.
>>>> But I
>>>> have tested it with hyperthreading.
>>>> powerd with HyperThreading -> spin lock hold too long
>>>> powerd without HyperThreading -> no problem
>>>> no powerd with/without HyperThreading -> no problem
>>>
>>> But these are with the last patch I posted in?
>>> (specifically, for 7.2:
>>> http://www.freebsd.org/~attilio/sched_ule.diff
>>> )
>>>
>>> So with the patch in, powerd and hyperthreading on you still get a
>>> deadlock?
>>>
>>> Attilio
>>>
>>>
> I have patched the sched_ule.c and did a make buildkernel & make
> installkernel (is buildworld and installworld necessary?), rebooted and the
> machine is running now.
> I will post here again if there is any update.

Considering we are at RC1 right now, is there any chance this patch
makes it into 8.0 release if the patch fixes the issue and doesn't
cause any regressions? Unfortunately I can't test it myself right now,
so I have to rely on other people experiencing the same issue to see
if the patch fixes it.

- Dan



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