megaraid2 driver update

[Jim Greene]

Actually I went back to kernel 2.4 (latest that comes with RH AS 3).  Seems 
they will not support a system if it is running a custom kernel.  I have not 
tried any kernel debugging options. How would one go about turning them on ?

Jim
----- Original Message ----- 
From: "Will Dyson" <will.dyson at gmail.com>
To: "Jim Greene" <jwgreene at megalink.net>
Cc: "Matt Domsch" <matt_domsch at dell.com>; "Jens Bergmann" 
<jens.bergmann at ewetel.de>; <linux-poweredge at dell.com>
Sent: Thursday, October 21, 2004 1:29 PM
Subject: Re: megaraid2 driver update


> On Wed, 20 Oct 2004 08:07:27 -0400, Jim Greene <jwgreene at megalink.net> 
> wrote:
>> Now a question.  I am currently running kernel 2.6.8.1  Does the below 
>> crash
>> look like it could be related to the megaraid driver?
>
>
>> Oct 19 15:17:11 pop1 kernel: Call Trace:
>> Oct 19 15:17:11 pop1 kernel:  [<0211f0bf>] 
>> autoremove_wake_function+0x0/0x2d
>> Oct 19 15:17:11 pop1 kernel:  [<0211cd90>] load_balance+0x4b/0x1f9
>> Oct 19 15:17:11 pop1 kernel:  [<0211f0bf>] 
>> autoremove_wake_function+0x0/0x2d
>> Oct 19 15:17:11 pop1 kernel:  [<0211d5c0>] scheduler_tick+0x3b9/0x3c1
>> Oct 19 15:17:11 pop1 kernel:  [<c2827f33>] kjournald+0x10d/0x329 [jbd]
>> Oct 19 15:17:11 pop1 kernel:  [<0211f0bf>] 
>> autoremove_wake_function+0x0/0x2d
>> Oct 19 15:17:11 pop1 kernel:  [<0211f0bf>] 
>> autoremove_wake_function+0x0/0x2d
>> Oct 19 15:17:11 pop1 kernel:  [<0211bfe9>] finish_task_switch+0x6c/0x8c
>> Oct 19 15:17:11 pop1 kernel:  [<c2827e20>] commit_timeout+0x0/0x5 [jbd]
>> Oct 19 15:17:11 pop1 kernel:  [<c2827e26>] kjournald+0x0/0x329 [jbd]
>> Oct 19 15:17:11 pop1 kernel:  [<021041f1>] kernel_thread_helper+0x5/0xb
>
> Nothing in the stack trace particularly suggests the megaraid driver.
> A problem in megaraid _could_ set kjournald (or whoever else hits the
> disk next) up for a failure, however.
>
> Have you tried turning on the various kernel debugging options?
>
> -- 
> Will Dyson - Consultant
> http://www.lucidts.com/
>