Bug#406640: marked as done (arcmsr driver, abort device command of id=0 lun=0)
Your message dated Wed, 8 Aug 2007 11:36:43 +0200
with message-id <20070808093643.GC6137@stro.at>
and subject line arcmsr driver, abort device command of id=0 lun=0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: linux-image-2.6.18-3-amd64
Version: 2.6.18-7
Severity: important
The arcmsr driver (ARC-1230 SATA-RAID controller) throws some error
messages since adding 2 76GB Western Digital Raptor disks (WDC
WD740ADFD-00NLR1) to the controller. The 2 disks are configured as RAID1
(Channel: 00 Id: 00 Lun: 04, Raid Set # 01).
Raid Set # 00 is a RAID5 containing 7 Segate 750GB disks in 4 1.1 TB Volumes.
I have never seen any error messages for this device (Channel: 00 Id: 00 Lun:
00-03). Even with a full drbd sync there has never been an error message.
With the Raid1 I can reproduce the error. It's triggerd every time I start a
disk benchmark, for example tiobench.
tiobench --numruns 3 --threads 1 --threads 2 --block 4096 --size 8000
Jan 12 14:55:14 VU0EM005 kernel: arcmsr4: abort device command of scsi id=0 lun=4
Jan 12 14:55:15 VU0EM005 kernel: arcmsr4: ccb='0xffff8100dfe9fc80' isr got aborted command
Jan 12 15:00:18 VU0EM005 kernel: arcmsr4: abort device command of scsi id=0 lun=4
Jan 12 15:01:03 VU0EM005 kernel: arcmsr4: abort device command of scsi id=0 lun=4
Jan 12 15:01:13 VU0EM005 kernel: arcmsr4: ccb='0xffff8100dfe9b480' isr got aborted command
Jan 12 15:02:10 VU0EM005 kernel: arcmsr4: abort device command of scsi id=0 lun=4
Jan 12 15:02:19 VU0EM005 kernel: arcmsr4: ccb='0xffff8100dfe89d80' isr got aborted command
Jan 12 15:12:23 VU0EM005 kernel: arcmsr4: abort device command of scsi id=0 lun=4
Jan 12 15:12:26 VU0EM005 kernel: arcmsr4: ccb='0xffff8100dfe9b480' isr got aborted command
I already tried to boot with noapi and acpi=off, this didn't help. I also
removed all Raid Sets an created them from scratch.
Some more system info:
Raid Set Hierarchy (Areca Admin Tool):
Raid Set # 00 Ch04 ARC-1230 R5-V1 (0/0/0) Normal 1125.0GB
Ch03 ARC-1230 R5-V2 (0/0/1) Normal 1125.0GB
Ch06 ARC-1230 R5-V3 (0/0/2) Normal 1125.0GB
Ch05 ARC-1230 R5-V4 (0/0/3) Normal 1125.0GB
Ch08
Ch07
Ch09
Raid Set # 01 Ch02 ARC-1230 R1-V1 (0/0/4) Normal 68.0GB
Ch01 ARC-1230 R1-V2 (0/0/5) Normal 2.0GB
modinfo arcmsr:
filename: /lib/modules/2.6.18-3-amd64/kernel/drivers/scsi/arcmsr/arcmsr.ko
author: Erich Chen <erich@areca.com.tw>
description: ARECA (ARC11xx/12xx) SATA RAID HOST Adapter
license: Dual BSD/GPL
version: Driver Version 1.20.00.13
vermagic: 2.6.18-3-amd64 SMP mod_unload gcc-4.1
depends: scsi_mod
Areca ARC-1230 Firmware: Firmware Version V1.42 2006-10-13
Core 2 Duo Conroe 6600 CPU
4GB RAM
Supermicro MB
4x Intel e1000 NIC
2 80GB SATA Disks connected to onboard controller
2 250GB SATA Disks connected to onboard controller
Adaptec AIC-7901 U320 SCSI HBA
NEC-T40A changer with LTO3 Ultruim drive
/proc/interrupts
CPU0 CPU1
0: 1538887 0 IO-APIC-edge timer
6: 3 0 IO-APIC-edge floppy
8: 0 0 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
14: 64 0 IO-APIC-edge ide0
50: 14345 0 PCI-MSI libata
58: 6274099 0 IO-APIC-level arcmsr, uhci_hcd:usb3
66: 226 0 IO-APIC-level aic79xx
74: 23 0 IO-APIC-level uhci_hcd:usb1, ehci_hcd:usb5
82: 10733179 0 IO-APIC-level eth2
90: 10922405 0 IO-APIC-level eth3
98: 13281 0 PCI-MSI eth0
106: 3194 0 PCI-MSI eth1
169: 48 0 IO-APIC-level uhci_hcd:usb4
233: 0 0 IO-APIC-level uhci_hcd:usb2
NMI: 55 31
LOC: 1516969 1516986
ERR: 0
--- End Message ---
--- Begin Message ---
- To: 406640-done@bugs.debian.org
- Subject: Re: arcmsr driver, abort device command of id=0 lun=0
- From: maximilian attems <max@stro.at>
- Date: Wed, 8 Aug 2007 11:36:43 +0200
- Message-id: <20070808093643.GC6137@stro.at>
Version: 2.6.20-1
> I performed a new test with the latest driver from 2006-11-07.
> This solves the problem.
closing as fixes merged upstream.
--
maks
--- End Message ---
Reply to: