Hi,

Tyan Tiger S2466-4M, 2xAthlon MP, Adaptec 29160, Adaptec 2940u2w,
software RAID 5, gcc 2.95.4. The core drives are on the 29160. Works
fine under 2.4.19.

2.5.44 panics during boot with SCSI problems; I didn't catch what the
error was.

2.5.44-ac5 boots but bugs after a few seconds.

Attached: config, syslog, lspci (under 2.4.19)

Oct 28 12:36:09 badb kernel: Incorrect number of segments after building list
Oct 28 12:36:09 badb kernel: counted 2, received 1
Oct 28 12:36:09 badb kernel: req nr_sec 8, cur_nr_sec 8
Oct 28 12:36:09 badb kernel: end_request: I/O error, dev 08:40, sector 6784528
Oct 28 12:36:09 badb kernel: raid5: Disk failure on scsi/host0/bus0/target4/lun0/part7, disabling device. Operation continuing on 4 devices
Oct 28 12:36:09 badb kernel: blk: request botched
Oct 28 12:36:09 badb kernel: ------------[ cut here ]------------
Oct 28 12:36:09 badb kernel: kernel BUG at drivers/scsi/scsi_lib.c:819!
Oct 28 12:36:09 badb kernel: invalid operand: 0000
Oct 28 12:36:09 badb kernel: mousedev hid nfs lockd sunrpc ohci-hcd usbcore parport_pc lp parport sg st sr_mod cdrom floppy iptable_filter ip_tables emu10k1 sound soundcore ac97_codec 3c59x rtc
Oct 28 12:36:09 badb kernel: CPU:    1
Oct 28 12:36:09 badb kernel: EIP:    0060:[scsi_init_io+279/304]    Not tainted
Oct 28 12:36:09 badb kernel: EFLAGS: 00010286
Oct 28 12:36:09 badb kernel: EIP is at scsi_init_io+0x117/0x130
Oct 28 12:36:09 badb kernel: eax: f5bcda00   ebx: f5bcda00   ecx: 00000001   edx: f7f51580
Oct 28 12:36:09 badb kernel: esi: 00000002   edi: f7ed62c0   ebp: f78c9f90   esp: f78c9f60
Oct 28 12:36:09 badb kernel: ds: 0068   es: 0068   ss: 0068
Oct 28 12:36:09 badb kernel: Process raid5d (pid: 17, threadinfo=f78c8000 task=f7e0cd00)
Oct 28 12:36:09 badb kernel: Stack: f7ed62c0 f5bcda00 f7ef3400 c01aa8bb f5bcda00 f7ef34c8 f7ef3428 f7ea3680
Oct 28 12:36:09 badb kernel:        f7f56800 f78c8000 c031fb20 c019d88e 00000001 c019eb5d f7ef3428 f7df434c
Oct 28 12:36:09 badb kernel:        f78c9fb4 c019ed80 f7ef3428 f78c8000 f78c8000 f78c9fb4 f78c9fb4 c01d6abf
Oct 28 12:36:09 badb kernel: Call Trace:
Oct 28 12:36:09 badb kernel:  [scsi_request_fn+779/1136] scsi_request_fn+0x30b/0x470
Oct 28 12:36:09 badb kernel:  [elv_queue_empty+14/32] elv_queue_empty+0xe/0x20
Oct 28 12:36:09 badb kernel:  [generic_unplug_device+141/192] generic_unplug_device+0x8d/0xc0
Oct 28 12:36:09 badb kernel:  [blk_run_queues+176/192] blk_run_queues+0xb0/0xc0
Oct 28 12:36:09 badb kernel:  [md_thread+415/528] md_thread+0x19f/0x210
Oct 28 12:36:09 badb kernel:  [md_thread+0/528] md_thread+0x0/0x210
Oct 28 12:36:09 badb kernel:  [default_wake_function+0/64] default_wake_function+0x0/0x40
Oct 28 12:36:09 badb kernel:  [kernel_thread_helper+5/24] kernel_thread_helper+0x5/0x18
Oct 28 12:36:09 badb kernel:
Oct 28 12:36:09 badb kernel: Code: 0f 0b 33 03 42 b0 24 c0 90 31 c0 5b 5e 5f c3 8d 76 00 8d bc
Oct 28 12:36:09 badb kernel:  <6>md: updating md2 RAID superblock on device
Oct 28 12:36:09 badb kernel: md: (skipping faulty scsi/host0/bus0/target4/lun0/part7 )
Oct 28 12:36:09 badb kernel: md: scsi/host0/bus0/target3/lun0/part7 [events: 000000ac]<6>(write) scsi/host0/bus0/target3/lun0/part7's sb offset: 4200896
Oct 28 12:36:09 badb kernel: md: scsi/host0/bus0/target2/lun0/part7 [events: 000000ac]<6>(write) scsi/host0/bus0/target2/lun0/part7's sb offset: 4200896
Oct 28 12:36:09 badb kernel: md: scsi/host0/bus0/target1/lun0/part7 [events: 000000ac]<6>(write) scsi/host0/bus0/target1/lun0/part7's sb offset: 4200896
Oct 28 12:36:09 badb kernel: md: scsi/host0/bus0/target0/lun0/part7 [events: 000000ac]<6>(write) scsi/host0/bus0/target0/lun0/part7's sb offset: 4200896

I trust that the 'disk failure' is just a side-effect of the bug; the
system runs fine on 2.4.19 after I raidhotadd it back.

merlin