public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* 2.6.1 oops w/ reiserfs + deadline elevator
@ 2004-01-14 21:15 markw
  2004-01-15  9:36 ` Jens Axboe
  0 siblings, 1 reply; 2+ messages in thread
From: markw @ 2004-01-14 21:15 UTC (permalink / raw)
  To: linux-kernel

I'm getting the following oops with our DBT-2 workload.  It appears that
I can only reproduce the problem with a combination of an aacraid
controller, reiserfs, and the deadline elevator.  I'm also using lvm2
but I can't really try to do the same test without lvm2 though.  I have
seen everything behave properly with the AS elevator or without an
aacraid controller.

Let me know if there's anything else I can provide.

Unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:                                                              
00000000      
*pde = 373ce001
*pte = 00000000
Oops: 0000 [#1]
CPU:    2      
EIP:    0060:[<00000000>]    Not tainted
EFLAGS: 00010046                        
EIP is at 0x0   
eax: f782e820   ebx: f7f9c000   ecx: f6f0c800   edx: c3afa6a0
esi: f782e800   edi: 00000086   ebp: 00000096   esp: f7f9ded0
ds: 007b   es: 007b   ss: 0068                               
Process swapper (pid: 0, threadinfo=f7f9c000 task=c38d2ca0)
Stack: f8919c7a c3afa6a0 f6fa1db0 f6f0c800 f782e9d0 f891df6d c3afa6a0 f6fa1db0 
       00000004 f782e800 f7f9c000 f7f9c000 f7f9c000 00000001 00000000 f6fbab88 
       f782e9d0 24000001 00000000 f7f9df80 f891e88b f7a9f180 c011c496 f71c8980 
Call Trace:                                                                    
 [<f8919c7a>] aac_io_done+0x3a/0x80 [aacraid]
 [<f891df6d>] aac_response_normal+0x18d/0x240 [aacraid]
 [<f891e88b>] aac_sa_intr+0x9b/0x120 [aacraid]         
 [<c011c496>] rebalance_tick+0x46/0xe0        
 [<c010bad9>] handle_IRQ_event+0x49/0x80
 [<c010becf>] do_IRQ+0xbf/0x1b0         
 [<c0106e70>] default_idle+0x0/0x40
 [<c0109f38>] common_interrupt+0x18/0x20
 [<c0106e70>] default_idle+0x0/0x40     
 [<c0106e9d>] default_idle+0x2d/0x40
 [<c0106f36>] cpu_idle+0x46/0x50    
 [<c0122768>] printk+0x178/0x1d0
 [<c040f0e6>] print_cpu_info+0x86/0xe0
                                      
Code:  Bad EIP value.
 <0>Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing


-- 
Mark Wong - - markw@osdl.org
Open Source Development Lab Inc - A non-profit corporation
12725 SW Millikan Way - Suite 400 - Beaverton, OR 97005
(503) 626-2455 x 32 (office)
(503) 626-2436      (fax)
http://developer.osdl.org/markw/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: 2.6.1 oops w/ reiserfs + deadline elevator
  2004-01-14 21:15 2.6.1 oops w/ reiserfs + deadline elevator markw
@ 2004-01-15  9:36 ` Jens Axboe
  0 siblings, 0 replies; 2+ messages in thread
From: Jens Axboe @ 2004-01-15  9:36 UTC (permalink / raw)
  To: markw; +Cc: linux-kernel

On Wed, Jan 14 2004, markw@osdl.org wrote:
> I'm getting the following oops with our DBT-2 workload.  It appears that
> I can only reproduce the problem with a combination of an aacraid
> controller, reiserfs, and the deadline elevator.  I'm also using lvm2
> but I can't really try to do the same test without lvm2 though.  I have
> seen everything behave properly with the AS elevator or without an
> aacraid controller.

I don't believe this has anything to do with the io scheduler, it looks
clearly like a problem deep inside the aac driver (and thus completely
io scheduler independent). The fact that it triggers with deadline is
likely completely coincidental.

Looks like scsicmd->scsi_done == NULL which is very odd. You may want to
try and add some debug prints checking that (and dumping scsicmd state)
fact.

-- 
Jens Axboe


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-01-15  9:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-01-14 21:15 2.6.1 oops w/ reiserfs + deadline elevator markw
2004-01-15  9:36 ` Jens Axboe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox