Created attachment 24377 [details]
Some very buggy ARCMSR drivers are included in the kernels dating from early 2008.
The new drivers with the same version number, but a later date exists and should be included instead.
This is the latest ftp://ftp.areca.com.tw/RaidCards/AP_Drivers/Linux/DRIVER/SourceCode/arcmsr.1.20.0X.15-90605.zip
With the older .15 driver i had several system lockups under heavy load.
On Wed, 30 Dec 2009 12:38:06 GMT
> Summary: Very old and buggy ARCMSR drivers are included
> Product: SCSI Drivers
> Version: 2.5
> Kernel Version: 2.6.18 etc
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: email@example.com
> ReportedBy: firstname.lastname@example.org
> Regression: No
> Created an attachment (id=24377)
> --> (http://bugzilla.kernel.org/attachment.cgi?id=24377)
> Latest arcmsr
> Some very buggy ARCMSR drivers are included in the kernels dating from early
> The new drivers with the same version number, but a later date exists and
> should be included instead.
> This is the latest
> With the older .15 driver i had several system lockups under heavy load.
Well that's bad. I'm not seeing any commits against that driver from
Areca staff since February 2008.
So it may be that the manufacturer has abandoned this driver. If so,
then it would be useful if someone who has the hardware could pick
apart the differences between the above driver and the in-kernel
version, and send the updates into the mainline kernel.
Areca does not abandon this driver.
We will still keep maintaining it.
Originally I plan to update the driver in the middle of last year.
But there is a lot of emergency to postpone the plan again and again.
I will make time to do it ASAP.
Sorry for you inconvenience.
This has still not been done from what I can see.
Continuing to let a _very_ buggy driver stay in the dist when you know it causes trouble and not keeping promises is something I dont expect for someone providing missioncritical equipment.
nick: any ETA on your update?
I have updated driver to bugzilla several times.
I have no idea why you still ask this.
Do you lost something?
If you have updated the driver please close the ticket Nick.
This bug is not opened by me.
No but if you resolved it mark it as resolved. Its hard for me to know if you as a vendor solved the issue.