advansys SCSI driver works on x86_64 but is disabled

Bug #140993 reported by Olly Betts
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

In drivers/scsi/Kconfig:

config SCSI_ADVANSYS

is marked as:

        depends on BROKEN || X86_32

I have a card which uses this driver - lspci reports it as:

01:07.0 SCSI storage controller: Advanced System Products, Inc ABP940-U / ABP960-U (rev 03)

My machine is x86_64 (and running 64 bit). If I unpack the Ubuntu kernel sources, delete that line from drivers/scsi/Kconfig, and rebuild the kernel, then insmod the new advansys.ko module that this builds into my running kernel, the driver seems to operate correctly - it's certainly adequate for using my SCSI scanner. I don't see any errors mentioning advansys in /var/log/{kern.log,messages,syslog} - the only message I see is this one (from when I insmod the module):

Sep 18 22:38:11 ubuntu kernel: [11313.689097] scsi8 : AdvanSys SCSI 3.3K: PCI Ultra: IO 0x7000-0x700F, IRQ 0x13

My suggestion is that this driver should be enabled for x86-64 as well. I'm happy to do further testing - just let me know what you want me to try.

Revision history for this message
Olly Betts (ojwb) wrote :

Reenabling and rebuilding the advansys module also works for me with gutsy (kernel 2.6.22-14-generic).

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Olly,

Thank you for your report. I believe this should be fixed in the upcoming Hardy kernel - which should be released for testing relatively soon. If you don't mind, would you be willing to test against the Hardy kernel to verify this is fixed? I'll tag this report as hardy-kernel-candidate to make sure we carry this forward. Thanks!

Changed in linux-source-2.6.22:
status: New → Incomplete
Revision history for this message
Olly Betts (ojwb) wrote :

Thanks for looking at this. I'm happy to test a fix.

Should it work OK to just install the hardy kernel package on gutsy and reboot to use that kernel for testing? If not, any suggestions for how best to go about this?

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Yes, to test you'll do just as you've described. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Olly,

I just wanted to let you know the Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2. However, here are the instructions to install (if you choose to do so):

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

Changed in linux:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Olly Betts (ojwb) wrote :

Thanks for letting me know - I hope I'll be able to test it this coming weekend.

Revision history for this message
Olly Betts (ojwb) wrote :

I've tested with linux-image-2.6.24-1-generic and I can successfully use my scanner with the advansys module. Excellent - thank you for sorting this out.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Olly,

Thanks for the update. I'm marking this as "Fix Released" against the actively developed hardy kernel.

Changed in linux:
status: Incomplete → Fix Released
Changed in linux-source-2.6.20:
status: New → Won't Fix
Changed in linux-source-2.6.22:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.