linux-kernel - Areca driver 2.6.19 on x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <3193.213.203.144.13.1165423892.squirrel@mailserver.omnibit.it>
Date:	Wed, 6 Dec 2006 17:51:32 +0100 (CET)
From:	filip@...oweb97.com
To:	support@...ca.com.tw
Cc:	linux-kernel@...r.kernel.org, erich@...ca.com.tw
Subject: Areca driver 2.6.19 on x86_64

We have a problem with the new areca driver included
in kernel tree 2.6.19.

During the boot sequence we get this
output:

........................
Loading arcmsr.ko module
ACPI: PCI Interrupt 0000:05:0e.0[A] -> Link
[LINKC] -> GSI 5 (level, low) -> IRQ 5
ARECA RAID ADAPTER0: FIRMWARE VERSION V1.41
2006-5-24
scsi0:  Areca SATA Host Adapter RAID
Controller

Driver Version 1.20.00.13
arcmsr0: abort device command of scsi id=0
lun=0
arcmsr0: scsi id=0 lun=0 ccb='0xffff810037f00000'
poll command abort successfully
arcmsr0: abort device command of scsi id=1
lun=0
arcmsr0: scsi id=0 lun=0 ccb='0xffff810037f00000'
poll command abort successfully
arcmsr0: abort device command of scsi id=2
lun=0
arcmsr0: scsi id=0 lun=0 ccb='0xffff810037f00000'
poll command abort successfully
scsi 0:0:0:0: scsi: Device offlined - not ready after
error recovery
........................
and keeps looping through all luns with different
values of ccd at each loop.
Till kernel panics because of the lack of root
device.

Here is our specs:
HW used:
ARC1220
ARC1110
on Supermicro X6DH8-XG2, Dual Xeon
3.0GHz

OS distro used:
CentOS 4.4 x86_64
Kernel 2.6.19 with hand-crafted config, that we are
able to use successfully with kernel 2.6.16.20.

Have you any suggestions to resolve this issue ?

Thanks in advance,
Filip Majewski

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/