Re: AVA-1505 trouble

[Alan Cox]

> (scsi0:6:0) cannot abort running or disconnected command
> 
> followed by an Oops (NULL pointer) and hard lockup.  EIP=c01c3892 points
> inside internal_done as you can see from this piece of System.map:
> 
> c01c386c T aha152x_queue
> c01c3888 T internal_done
> c01c38a4 T aha152x_command
> c01c3910 T aha152x_abort
> 
> This is a hard lockup (followed by a few minutes of fsck...) so the Oops

Aha - try

--- drivers/scsi/aha152x.c~ Tue Apr  3 17:55:01 2001
+++ drivers/scsi/aha152x.c  Sun Jun 10 19:54:02 2001
@@ -1494,7 +1494,7 @@
 
DPRINTK(debug_eh, INFO_LEAD "internal_done called\n", CMDINFO(SCpnt));
 #endif
-   if(SCSEM(SCpnt))
+   if(SCDATA(SCpnt) && SCSEM(SCpnt))
up(SCSEM(SCpnt));
 }


It doesnt explain why you got a hang - maybe IRQ problems for one, but it 
does explain the oops. The abort freed the host scribble buffer and then
said it failed. internal_done was called as the command completed and tried
to check a dead semaphore.

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]

AVA-1505 trouble

[Marek Michalkiewicz]

Hello,

my SCSI scanner (Microtek Phantom636, which came with a piece of 
called AVA-1505AE) worked with 2.2.19, and doesn't work with 2.4.5.
Using the statically compiled aha152x driver, aha152x=0x140,10,7,1,1,0,100
on the kernel command line, soon after starting "scanimage" I'm getting
this error:

(scsi0:6:0) cannot abort running or disconnected command

followed by an Oops (NULL pointer) and hard lockup.  EIP=c01c3892 points
inside internal_done as you can see from this piece of System.map:

c01c386c T aha152x_queue
c01c3888 T internal_done
c01c38a4 T aha152x_command
c01c3910 T aha152x_abort

This is a hard lockup (followed by a few minutes of fsck...) so the Oops
didn't get written to syslog, but it is 100% reproducible so I can write
all of it down from the screen next time if that helps to fix the bug.

After reboot, there is some trouble with resetting the SCSI bus with the
scanner (the same "cannot abort running or disconnected command" error),
fixed by power cycling the scanner.

I can see the aha152x driver had some changes between 2.2 and 2.4
kernels, perhaps there is some new bug?

I also have a real SCSI controller (AHA-2940AU, used for my CD writer),
does anyone know if it will work with this scanner if I get the cable?
I could just try it instead of asking, but getting the right type of
SCSI cable (DB25/HD50) seems to be difficult here, I can only see it
offered by one (quite expensive) mail order company, so I'd like to be
reasonably sure it will help before ordering it.

The scanner is detected like this:

  Vendor:   Model: scanner V636A4Rev: 1.30
  Type:   ScannerANSI SCSI revision: 02
Detected scsi generic sg1 at scsi0, channel 0, id 6, lun 0, type 6

There is nothing else on the same SCSI bus.  Works on 2.2.19 and NT 4.0
(with the same "freezing everything for a second every few seconds"
busy loops when scanning under both OSs).  If you need more information
to help fix the bug, just ask.

Thanks,
Marek

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]