On Aug 16, 2010, at 11:39 PM, Kostik Belousov wrote:
> On Mon, Aug 16, 2010 at 11:35:36PM +0400, Alexey Tarasov wrote:
>>
>> On Aug 16, 2010, at 11:31 PM, Kostik Belousov wrote:
>>
>>> On Mon, Aug 16, 2010 at 11:21:15PM +0400, Alexey Tarasov wrote:
Hello Kostik!
On Aug 16, 2010,
On Mon, Aug 16, 2010 at 11:35:36PM +0400, Alexey Tarasov wrote:
>
> On Aug 16, 2010, at 11:31 PM, Kostik Belousov wrote:
>
> > On Mon, Aug 16, 2010 at 11:21:15PM +0400, Alexey Tarasov wrote:
> >> Hello Kostik!
> >>
> >> On Aug 16, 2010, at 10:48 PM, Kostik Belousov wrote:
> >>
>
> >>> The
On Aug 16, 2010, at 11:31 PM, Kostik Belousov wrote:
> On Mon, Aug 16, 2010 at 11:21:15PM +0400, Alexey Tarasov wrote:
>> Hello Kostik!
>>
>> On Aug 16, 2010, at 10:48 PM, Kostik Belousov wrote:
>>
>>> The backtrace make absolutely no sense. I would not trust kgdb anyway.
>>>
>>> Compile
On Mon, Aug 16, 2010 at 11:21:15PM +0400, Alexey Tarasov wrote:
> Hello Kostik!
>
> On Aug 16, 2010, at 10:48 PM, Kostik Belousov wrote:
>
> >>
> > The backtrace make absolutely no sense. I would not trust kgdb anyway.
> >
> > Compile ddb in and do backtrace in console on the panic. Also, disas
Hello Kostik!
On Aug 16, 2010, at 10:48 PM, Kostik Belousov wrote:
>>
> The backtrace make absolutely no sense. I would not trust kgdb anyway.
>
> Compile ddb in and do backtrace in console on the panic. Also, disassemble
> the kernel at the fault address. I am very curious which instruction ca
On Mon, Aug 16, 2010 at 07:15:16PM +0400, Alexey Tarasov wrote:
> Hello.
>
> I have a couple of Supermicro servers which got the similar kernel panic with
> all FreeBSD versions I tried since 6.4.
> Now I want to investigate into the problem.
> The servers get into panic with similar workload: fi
