[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#426705: cciss: kernel BUG at drivers/block/cciss.c:2479



Package: linux-image-2.6.21-1-686
Version: 2.6.21-4

The trace written to the console:
=================================

kernel BUG at drivers/block/cciss.c:2479!
invalid opcode: 0000 [#1]
SMP 
Modules linked in: mptctl sg nfsd exportfs lockd nfs_acl sunrpc ipv6 8021q raw dm_snapshot shpchp pci_hotplug psmouse serio_raw pcspkr ext3 jbd mbcache raid1 md_mod dm_mod ide_generic ide_cd usbhid hid piix tg3 cciss bnx2 generic ehci_hcd ide_core uhci_hcd usbcore thermal processor fan sr_mod cdrom mptscsih mptbase aic7xxx sym53c8xx scsi_transport_spi BusLogic scsi_mod
CPU:    0
EIP:    0060:[<f894c119>]    Not tainted VLI
EFLAGS: 00010012   (2.6.21-1-686 #1)
EIP is at do_cciss_request+0x44/0x349 [cciss]
eax: f693b350   ebx: dfb7dbac   ecx: 00000000   edx: 00000000
esi: 00000800   edi: f5ff99c0   ebp: f693b350   esp: dfcafbec
ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
Process md0_raid1 (pid: 6108, ti=dfcae000 task=df981a90 task.ti=dfcae000)
Stack: 00000000 dfd6004c dfb7dbac 00000c00 dfd10000 00000001 00000001 00000001 
       dfcafc2c c17430e0 00000c00 00000000 00000200 c16bad80 00000000 00000000 
       c195a24c dfebaadc 00000000 00000040 00000040 dfcafc9c dfd60250 dfc97bec 
Call Trace:
 [<c01bd25b>] elv_next_request+0x10d/0x11c
 [<f894a105>] start_io+0x7b/0xe1 [cciss]
 [<f894c413>] do_cciss_request+0x33e/0x349 [cciss]
 [<c016438a>] cache_alloc_refill+0x58/0x466
 [<c01c6dfc>] cfq_set_request+0x299/0x315
 [<c01bd54a>] elv_rb_add+0x65/0x6d
 [<c01c63e8>] cfq_add_rq_rb+0x5c/0x6b
 [<c01c6421>] cfq_insert_request+0x2a/0x3ae
 [<c0129e5f>] lock_timer_base+0x15/0x2f
 [<c012a15d>] del_timer+0x48/0x4e
 [<c01bfa97>] blk_remove_plug+0x57/0x63
 [<c0129f73>] __mod_timer+0x9c/0xa6
 [<c01bfac0>] __generic_unplug_device+0x1d/0x1f
 [<c01c0c02>] __make_request+0x34c/0x46c
 [<c01bedfa>] generic_make_request+0x1a9/0x1b9
 [<c012a15d>] del_timer+0x48/0x4e
 [<c01bfa97>] blk_remove_plug+0x57/0x63
 [<f8961ba9>] raid1d+0xbf/0xd0e [raid1]
 [<c0102ff1>] __switch_to+0xfe/0x131
 [<c011b0fe>] __activate_task+0x1c/0x29
 [<c029d6d9>] schedule_timeout+0x13/0x8d
 [<c0124b9c>] do_exit+0x6c2/0x6c6
 [<f89a1a71>] md_thread+0xc6/0xdd [md_mod]
 [<c01328e5>] autoremove_wake_function+0x0/0x35
 [<f89a19ab>] md_thread+0x0/0xdd [md_mod]
 [<c013281a>] kthread+0xb2/0xdc
 [<c0132768>] kthread+0x0/0xdc
 [<c01049a7>] kernel_thread_helper+0x7/0x10
 =======================
Code: 44 24 10 8b 82 dc 00 00 00 84 c0 0f 88 0b 03 00 00 8b 44 24 08 e8 46 10 87 c7 85 c0 89 c5 0f 84 f8 02 00 00 66 83 78 68 1f 76 04 <0f> 0b eb fe 8b 44 24 10 ba 01 00 00 00 e8 a2 f9 ff ff 85 c0 89 
EIP: [<f894c119>] do_cciss_request+0x44/0x349 [cciss] SS:ESP 0068:dfcafbec


How to reproduce:
=================

I have an ML-350-G5 with an E200i raid controller. There are 2 logical drives
defined that map 1-1 on a physical drive. Those disks are part of a software
RAID-1 array. When initializing an oracle database on the system, the
system panics.


Leo.

Attachment: signature.asc
Description: Digital signature


Reply to: