aha152x_cs: non-functional + locking error

DISCUSSION Randy Dunlap 2 participants 3 messages Jun 26, 2009 – Jun 29, 2009 SCSI

lore

Share & tools

lore

Randy Dunlap

author

2009-06-26 19:27 UTC #0 lore raw

When I try to use aha152x_cs on any recent kernel, I get messages like

(scsi2:4:0) cannot abort running or disconnected command (scsi2:4:0) cannot reset current device

so I enabled lots of debugging (in 2.6.30) and get (end of message log):

busy: unknown(seldo) SCSISEQ( ); SCSISIG(MESSAGE OUT); INTSTAT (lo); SSTAT( SELDO ); SSTAT( ); SXFRCTL0( CH1 ); SIGNAL( ATNI BSYI ); SELID (e7), STCNT (0), SSTAT2( SEMPTY ); SFCNT (0); SCSICNT (0), OFFCNT(0), SSTAT4( ); DMACNTRL0( 16BIT PIO READ INTEN ); DMASTAT( DFIFOEMP ) enabled interrupts ( ENPHASEMIS ENBUSFREE ENSCSIPERR )
(scsi2:4:0) (aha152x_abort:1111) locking
(scsi2:4:0) (aha152x_abort:1111) locked
(scsi2:4:0) (aha152x_abort:1129) unlocking (locked at aha152x_abort:1111)
(scsi2:4:0) (aha152x_abort:1129) unlocked
(scsi2:4:0) cannot abort running or disconnected command
(scsi2:4:0) aha152x_device_reset(dfa82a40)<7>(scsi2:4:0) (show_queues:2952) locking
(scsi2:4:0) (show_queues:2952) locked

queue status:
issue_SC:
(scsi2:4:0) (show_queues:2956) unlocking (locked at show_queues:2952) (scsi2:4:0) (show_queues:2956) unlocked
current_SC:
scsi 2:0:4:0: dfa82a40: cmnd=(cdb[0]=0x12 12 00 00 00 24 00 ); request_bufflen=36; resid=36; phase |syncneg|; next=0x(null) disconnected_SC:

busy: unknown(seldo) SCSISEQ( ); SCSISIG(MESSAGE OUT); INTSTAT (lo); SSTAT( SELDO ); SSTAT( ); SXFRCTL0( CH1 ); SIGNAL( ATNI BSYI ); SELID (e7), STCNT (0), SSTAT2( SEMPTY ); SFCNT (0); SCSICNT (0), OFFCNT(0), SSTAT4( ); DMACNTRL0( 16BIT PIO READ INTEN ); DMASTAT( DFIFOEMP ) enabled interrupts ( ENPHASEMIS ENBUSFREE ENSCSIPERR )
(scsi2:4:0) cannot reset current device
(scsi2:4:0) (aha152x_bus_reset_host:1247) locking
(scsi2:4:0) (aha152x_bus_reset_host:1247) locked
scsi2: bus reset<7>(scsi2:4:0) (show_queues:2952) locking

BUG: spinlock trylock failure on UP on CPU#0, scsi_eh_2/7012
 lock: d6d97b94, .magic: dead4ead, .owner: scsi_eh_2/7012, .owner_cpu: 0
Pid: 7012, comm: scsi_eh_2 Not tainted 2.6.30 #7
Call Trace:
 [<c0439076>] ? printk+0xf/0x11
 [<c0210f02>] spin_bug+0x75/0x80
 [<c0210fad>] _raw_spin_trylock+0x36/0x3b
 [<c043b7b2>] _spin_lock_irqsave+0x29/0x55
 [<e1acfc7a>] ? show_queues+0xbe/0x35b [aha152x_cs]
 [<e1acfc7a>] show_queues+0xbe/0x35b [aha152x_cs]
 [<e1ad02ba>] aha152x_bus_reset_host+0x136/0x295 [aha152x_cs]
 [<e1ad048a>] aha152x_bus_reset+0xc/0xe [aha152x_cs]
 [<c02ba6cc>] scsi_try_bus_reset+0x25/0xa0
 [<c02bb251>] scsi_eh_ready_devs+0x2fa/0x4ad
 [<c02bb66a>] scsi_error_handler+0x1a7/0x32e
 [<c02bb4c3>] ? scsi_error_handler+0x0/0x32e
 [<c012c8a0>] kthread+0x42/0x67
 [<c012c85e>] ? kthread+0x0/0x67
 [<c0103053>] kernel_thread_helper+0x7/0x10
BUG: spinlock lockup on CPU#0, scsi_eh_2/7012, d6d97b94
Pid: 7012, comm: scsi_eh_2 Not tainted 2.6.30 #7
Call Trace:
 [<c0439076>] ? printk+0xf/0x11
 [<c0211073>] _raw_spin_lock+0xc1/0xe4
 [<c043b7ca>] _spin_lock_irqsave+0x41/0x55
 [<e1acfc7a>] show_queues+0xbe/0x35b [aha152x_cs]
 [<e1ad02ba>] aha152x_bus_reset_host+0x136/0x295 [aha152x_cs]
 [<e1ad048a>] aha152x_bus_reset+0xc/0xe [aha152x_cs]
 [<c02ba6cc>] scsi_try_bus_reset+0x25/0xa0
 [<c02bb251>] scsi_eh_ready_devs+0x2fa/0x4ad
 [<c02bb66a>] scsi_error_handler+0x1a7/0x32e
 [<c02bb4c3>] ? scsi_error_handler+0x0/0x32e
 [<c012c8a0>] kthread+0x42/0x67
 [<c012c85e>] ? kthread+0x0/0x67
 [<c0103053>] kernel_thread_helper+0x7/0x10

Does anyone successfully use aha152x_cs now?
If not, maybe it should just be removed from the kernel tree.

Signature · 3 lines

~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/

Jürgen E. Fischer

2009-06-28 20:44 UTC #1 lore raw

Hi Randy,

Quoted 6 lines · Randy Dunlap

When I try to use aha152x_cs on any recent kernel, I get messages like
(scsi2:4:0) cannot abort running or disconnected command (scsi2:4:0) cannot reset current device
so I enabled lots of debugging (in 2.6.30) and get (end of message log):

IIRC that might trigger lockups.

Quoted 1 line

Does anyone successfully use aha152x_cs now?

Just occasionally, when I need to scan something. I tried 2.6.30 using that scanner and an old disk. Still works for me.

Jürgen

Signature · 8 lines

norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Randy Dunlap

author

2009-06-29 15:08 UTC #2 lore raw

Quoted 11 lines · Jürgen E. Fischer

Hi Randy,
Quoted 6 lines · Randy Dunlap
When I try to use aha152x_cs on any recent kernel, I get messages like
(scsi2:4:0) cannot abort running or disconnected command (scsi2:4:0) cannot reset current device
so I enabled lots of debugging (in 2.6.30) and get (end of message log):
IIRC that might trigger lockups.

It's non-functional for me without debugging as well. But not due to locking errors.

Quoted 4 lines

Quoted 1 line
Does anyone successfully use aha152x_cs now?
Just occasionally, when I need to scan something. I tried 2.6.30 using that scanner and an old disk. Still works for me.

Thanks.

Signature · 8 lines

~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html