2010/4/20 Erik Cederstrand :
>
> Den 19/04/2010 kl. 17.03 skrev Attilio Rao:
>
>> 2010/4/19 Erik Cederstrand :
>>> Hi
>>>
>>> I'm testing ClangBSD in a VirtualBox client and ran into a panic on the
>>> client, but I don't think it's clang-related. I haven't tried kernel
>>> debugging before. I tr
Den 19/04/2010 kl. 17.03 skrev Attilio Rao:
> 2010/4/19 Erik Cederstrand :
>> Hi
>>
>> I'm testing ClangBSD in a VirtualBox client and ran into a panic on the
>> client, but I don't think it's clang-related. I haven't tried kernel
>> debugging before. I tried getting a backtrace as described i
On 04/19/2010 08:03 AM, Attilio Rao wrote:
2010/4/19 Erik Cederstrand:
Hi
I'm testing ClangBSD in a VirtualBox client and ran into a panic on the client,
but I don't think it's clang-related. I haven't tried kernel debugging before.
I tried getting a backtrace as described in
http://old.
2010/4/19 Erik Cederstrand :
> Hi
>
> I'm testing ClangBSD in a VirtualBox client and ran into a panic on the
> client, but I don't think it's clang-related. I haven't tried kernel
> debugging before. I tried getting a backtrace as described in
> http://old.nabble.com/Re%3A-ia64--%3E-panic%3A-de
Hi
I'm testing ClangBSD in a VirtualBox client and ran into a panic on the client,
but I don't think it's clang-related. I haven't tried kernel debugging before.
I tried getting a backtrace as described in
http://old.nabble.com/Re%3A-ia64--%3E-panic%3A-deadlkres%3A-possible-deadlock-detected-fo
On Apr 2, 2010, at 3:55 PM, Anton Shterenlikht wrote:
> Hi Marcel
>
> I got this panic while trying to build some port
> on -current (csup'ed on 1-APR-2010)
>
> panic: deadlkres: possible deadlock detected for 0xe0001187d880, blocked
> for 1801437 ticks
>
&g
Hi Marcel
I got this panic while trying to build some port
on -current (csup'ed on 1-APR-2010)
panic: deadlkres: possible deadlock detected for 0xe0001187d880, blocked
for 1801437 ticks
cpuid = 1
KDB: enter: panic
[ thread pid 0 tid 100046 ]
Stopped at kdb_enter+0x92: [I2]add
