* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
@ 2009-09-11 9:23 ` bugzilla-daemon
2009-09-11 23:27 ` [Bug 14159] New: " James Bottomley
` (16 subsequent siblings)
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-11 9:23 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
g.giorgetti@teamsystem.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|All |i386
--- Comment #1 from g.giorgetti@teamsystem.com 2009-09-11 09:23:40 ---
Previous log for kernel 2.6.30 was missing characters because of a cut/paste
problem with text wrap, repasting :
Kernel 2.6.30
Aug 3 06:25:04 svil kernel: aic79xx 0000:41:01.0: PCI INT A -> GSI 19 (level,
low) -> IRQ 19
Aug 3 06:25:04 svil kernel: scsi5 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev
3.0
Aug 3 06:25:04 svil kernel: <Adaptec 29320ALP PCIx Ultra320 SCSI
adapter>
Aug 3 06:25:04 svil kernel: aic7901: Ultra320 Wide Channel A, SCSI
Id=7, PCI-X 101-133MHz, 512 SCBs
Aug 3 06:25:04 svil kernel: scsi 5:0:0:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:04 svil kernel: scsi 5:0:0:0: Command already completed
Aug 3 06:25:04 svil kernel: scsi 5:0:0:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:04 svil kernel: scsi 5:0:0:0: Command already completed
Aug 3 06:25:04 svil kernel: scsi 5:0:0:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:04 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:04 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:04 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:04 svil kernel: Recovery SCB completes
Aug 3 06:25:04 svil kernel: scsi 5:0:0:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:04 svil kernel: scsi 5:0:0:0: Command already completed
Aug 3 06:25:04 svil kernel: scsi 5:0:0:0: Device offlined - not ready after
error recovery
Aug 3 06:25:04 svil kernel: scsi 5:0:1:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:04 svil kernel: scsi 5:0:1:0: Command already completed
Aug 3 06:25:04 svil kernel: scsi 5:0:1:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:04 svil kernel: scsi 5:0:1:0: Command already completed
Aug 3 06:25:04 svil kernel: scsi 5:0:1:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:04 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:04 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:04 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:04 svil kernel: Recovery SCB completes
Aug 3 06:25:04 svil kernel: scsi 5:0:1:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:04 svil kernel: scsi 5:0:1:0: Command already completed
Aug 3 06:25:04 svil kernel: scsi 5:0:1:0: Device offlined - not ready after
error recovery
Aug 3 06:25:04 svil kernel: scsi 5:0:2:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:04 svil kernel: scsi 5:0:2:0: Command already completed
Aug 3 06:25:04 svil kernel: scsi 5:0:2:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:04 svil kernel: scsi 5:0:2:0: Command already completed
Aug 3 06:25:04 svil kernel: scsi 5:0:2:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:04 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:04 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:05 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:05 svil kernel: Recovery SCB completes
Aug 3 06:25:05 svil kernel: scsi 5:0:2:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:05 svil kernel: scsi 5:0:2:0: Command already completed
Aug 3 06:25:05 svil kernel: scsi 5:0:2:0: Device offlined - not ready after
error recovery
Aug 3 06:25:05 svil kernel: scsi 5:0:3:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:05 svil kernel: scsi5: At time of recovery, card was paused
Aug 3 06:25:05 svil kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins
<<<<<<<<<<<<<<<<<
Aug 3 06:25:05 svil kernel: scsi5: Dumping Card State at program address 0x127
Mode 0x11
Aug 3 06:25:05 svil kernel: Card was paused
Aug 3 06:25:05 svil kernel: INTSTAT[0x0] SELOID[0x3] SELID[0x0]
HS_MAILBOX[0x0]
Aug 3 06:25:05 svil kernel: INTCTL[0x0] SEQINTSTAT[0x0] SAVED_MODE[0x0]
DFFSTAT[0x19]
Aug 3 06:25:05 svil kernel: SCSISIGI[0xe6] SCSIPHASE[0x8] SCSIBUS[0x2]
LASTPHASE[0xe0]
Aug 3 06:25:05 svil kernel: SCSISEQ0[0x0] SCSISEQ1[0x12] SEQCTL0[0x0]
SEQINTCTL[0x0]
Aug 3 06:25:05 svil kernel: SEQ_FLAGS[0x0] SEQ_FLAGS2[0x4] QFREEZE_COUNT[0x0]
Aug 3 06:25:05 svil kernel: KERNEL_QFREEZE_COUNT[0x0] MK_MESSAGE_SCB[0xff00]
Aug 3 06:25:05 svil kernel: MK_MESSAGE_SCSIID[0xff] SSTAT0[0x2] SSTAT1[0x1]
Aug 3 06:25:05 svil kernel: SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0]
SIMODE1[0xac]
Aug 3 06:25:05 svil kernel: LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0]
LQOSTAT0[0x0]
Aug 3 06:25:05 svil kernel: LQOSTAT1[0x0] LQOSTAT2[0x0]
Aug 3 06:25:05 svil kernel:
Aug 3 06:25:05 svil kernel: SCB Count = 4 CMDS_PENDING = 1 LASTSCB 0xffff
CURRSCB 0x3 NEXTSCB 0x0
Aug 3 06:25:05 svil kernel: qinstart = 13 qinfifonext = 13
Aug 3 06:25:05 svil kernel: QINFIFO:
Aug 3 06:25:05 svil kernel: WAITING_TID_QUEUES:
Aug 3 06:25:05 svil kernel: Pending list:
Aug 3 06:25:05 svil kernel: 3 FIFO_USE[0x0] SCB_CONTROL[0x40]
SCB_SCSIID[0x37]
Aug 3 06:25:05 svil kernel: Total 1
Aug 3 06:25:05 svil kernel: Kernel Free SCB list: 2 1 0
Aug 3 06:25:05 svil kernel: Sequencer Complete DMA-inprog list:
Aug 3 06:25:05 svil kernel: Sequencer Complete list:
Aug 3 06:25:05 svil kernel: Sequencer DMA-Up and Complete list:
Aug 3 06:25:05 svil kernel: Sequencer On QFreeze and Complete list:
Aug 3 06:25:05 svil kernel:
Aug 3 06:25:05 svil kernel:
Aug 3 06:25:05 svil kernel: scsi5: FIFO0 Free, LONGJMP == 0x80ff, SCB 0x0
Aug 3 06:25:05 svil kernel: SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0]
DFSTATUS[0x89]
Aug 3 06:25:05 svil kernel: SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0]
Aug 3 06:25:05 svil kernel: SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT =
0x0
Aug 3 06:25:05 svil kernel: HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]
Aug 3 06:25:05 svil kernel:
Aug 3 06:25:05 svil kernel: scsi5: FIFO1 Active, LONGJMP == 0x8063, SCB 0x3
Aug 3 06:25:05 svil kernel: SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x4]
DFSTATUS[0x89]
Aug 3 06:25:05 svil kernel: SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0]
Aug 3 06:25:05 svil kernel: SOFFCNT[0x0] MDFFSTAT[0x14] SHADDR = 0x06, SHCNT =
0x0
Aug 3 06:25:05 svil kernel: HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]
Aug 3 06:25:05 svil kernel: LQIN: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:05 svil kernel: scsi5: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE
= 0x52
Aug 3 06:25:05 svil kernel: scsi5: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x0
Aug 3 06:25:05 svil kernel: scsi5: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0
Aug 3 06:25:05 svil kernel: SIMODE0[0xc]
Aug 3 06:25:05 svil kernel: CCSCBCTL[0x4]
Aug 3 06:25:05 svil kernel: scsi5: REG0 == 0x3, SINDEX = 0x1e0, DINDEX = 0xe1
Aug 3 06:25:05 svil kernel: scsi5: SCBPTR == 0x3, SCB_NEXT == 0xffc0,
SCB_NEXT2 == 0xff65
Aug 3 06:25:05 svil kernel: CDB 12 0 0 0 24 0
Aug 3 06:25:05 svil kernel: STACK: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:05 svil kernel: <<<<<<<<<<<<<<<<< Dump Card State Ends
>>>>>>>>>>>>>>>>>>
Aug 3 06:25:05 svil kernel: scsi 5:0:3:0: Device is active, asserting ATN
Aug 3 06:25:05 svil kernel: scsi5: Recovery code sleeping
Aug 3 06:25:05 svil kernel: scsi5: Timer Expired (active 1)
Aug 3 06:25:05 svil kernel: Recovery code awake
Aug 3 06:25:05 svil kernel: scsi5: Command abort returning 0x2003
Aug 3 06:25:06 svil kernel: scsi 5:0:3:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:06 svil kernel: scsi5: Device reset timer expired (active 2)
Aug 3 06:25:06 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:06 svil kernel: Recovery SCB completes
Aug 3 06:25:06 svil kernel: Recovery SCB completes
Aug 3 06:25:06 svil kernel: scsi 5:0:3:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi5: At time of recovery, card was not paused
Aug 3 06:25:06 svil kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins
<<<<<<<<<<<<<<<<<
Aug 3 06:25:06 svil kernel: scsi5: Dumping Card State at program address 0x34
Mode 0x22
Aug 3 06:25:06 svil kernel: Card was paused
Aug 3 06:25:06 svil kernel: INTSTAT[0x0] SELOID[0x3] SELID[0x0]
HS_MAILBOX[0x0]
Aug 3 06:25:06 svil kernel: INTCTL[0x80] SEQINTSTAT[0x0] SAVED_MODE[0x0]
DFFSTAT[0x33]
Aug 3 06:25:06 svil kernel: SCSISIGI[0x0] SCSIPHASE[0x0] SCSIBUS[0x0]
LASTPHASE[0x1]
Aug 3 06:25:06 svil kernel: SCSISEQ0[0x0] SCSISEQ1[0x12] SEQCTL0[0x0]
SEQINTCTL[0x0]
Aug 3 06:25:06 svil kernel: SEQ_FLAGS[0xc0] SEQ_FLAGS2[0x4] QFREEZE_COUNT[0x1]
Aug 3 06:25:06 svil kernel: KERNEL_QFREEZE_COUNT[0x1] MK_MESSAGE_SCB[0xff00]
Aug 3 06:25:06 svil kernel: MK_MESSAGE_SCSIID[0xff] SSTAT0[0x0] SSTAT1[0x8]
Aug 3 06:25:06 svil kernel: SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0]
SIMODE1[0xa4]
Aug 3 06:25:06 svil kernel: LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0]
LQOSTAT0[0x0]
Aug 3 06:25:06 svil kernel: LQOSTAT1[0x0] LQOSTAT2[0x0]
Aug 3 06:25:06 svil kernel:
Aug 3 06:25:06 svil kernel: SCB Count = 4 CMDS_PENDING = 0 LASTSCB 0xffff
CURRSCB 0x3 NEXTSCB 0x0
Aug 3 06:25:06 svil kernel: qinstart = 14 qinfifonext = 15
Aug 3 06:25:06 svil kernel: QINFIFO: 0x3
Aug 3 06:25:06 svil kernel: WAITING_TID_QUEUES:
Aug 3 06:25:06 svil kernel: Pending list:
Aug 3 06:25:06 svil kernel: 3 FIFO_USE[0x3] SCB_CONTROL[0x48]
SCB_SCSIID[0x37]
Aug 3 06:25:06 svil kernel: Total 1
Aug 3 06:25:06 svil kernel: Kernel Free SCB list: 2 1 0
Aug 3 06:25:06 svil kernel: Sequencer Complete DMA-inprog list:
Aug 3 06:25:06 svil kernel: Sequencer Complete list:
Aug 3 06:25:06 svil kernel: Sequencer DMA-Up and Complete list:
Aug 3 06:25:06 svil kernel: Sequencer On QFreeze and Complete list:
Aug 3 06:25:06 svil kernel:
Aug 3 06:25:06 svil kernel:
Aug 3 06:25:06 svil kernel: scsi5: FIFO0 Free, LONGJMP == 0x80ff, SCB 0x0
Aug 3 06:25:06 svil kernel: SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0]
DFSTATUS[0x89]
Aug 3 06:25:06 svil kernel: SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0]
Aug 3 06:25:06 svil kernel: SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT =
0x0
Aug 3 06:25:06 svil kernel: HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]
Aug 3 06:25:06 svil kernel:
Aug 3 06:25:06 svil kernel: scsi5: FIFO1 Free, LONGJMP == 0x8063, SCB 0x3
Aug 3 06:25:06 svil kernel: SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x4]
DFSTATUS[0x89]
Aug 3 06:25:06 svil kernel: SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0]
Aug 3 06:25:06 svil kernel: SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT =
0x0
Aug 3 06:25:06 svil kernel: HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]
Aug 3 06:25:06 svil kernel: LQIN: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi5: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE
= 0x52
Aug 3 06:25:06 svil kernel: scsi5: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x0
Aug 3 06:25:06 svil kernel: scsi5: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0
Aug 3 06:25:06 svil kernel: SIMODE0[0xc]
Aug 3 06:25:06 svil kernel: CCSCBCTL[0x0]
Aug 3 06:25:06 svil kernel: scsi5: REG0 == 0x3, SINDEX = 0x119, DINDEX = 0xe1
Aug 3 06:25:06 svil kernel: scsi5: SCBPTR == 0x3, SCB_NEXT == 0xff00,
SCB_NEXT2 == 0xffa4
Aug 3 06:25:06 svil kernel: CDB 0 0 0 0 0 0
Aug 3 06:25:06 svil kernel: STACK: 0x20 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: <<<<<<<<<<<<<<<<< Dump Card State Ends
>>>>>>>>>>>>>>>>>>
Aug 3 06:25:06 svil kernel: scsi5:0:3:0: Cmd aborted from QINFIFO
Aug 3 06:25:06 svil kernel: scsi 5:0:3:0: Device offlined - not ready after
error recovery
Aug 3 06:25:06 svil kernel: scsi 5:0:4:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:4:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:4:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:4:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:4:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:06 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:06 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:06 svil kernel: Recovery SCB completes
Aug 3 06:25:06 svil kernel: scsi 5:0:4:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:4:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:4:0: Device offlined - not ready after
error recovery
Aug 3 06:25:06 svil kernel: scsi 5:0:5:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:5:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:5:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:5:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:5:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:06 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:06 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:06 svil kernel: Recovery SCB completes
Aug 3 06:25:06 svil kernel: scsi 5:0:5:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:5:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:5:0: Device offlined - not ready after
error recovery
Aug 3 06:25:06 svil kernel: scsi 5:0:6:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:6:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:6:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:6:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:6:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:06 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:06 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:06 svil kernel: Recovery SCB completes
Aug 3 06:25:06 svil kernel: scsi 5:0:6:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:6:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:6:0: Device offlined - not ready after
error recovery
Aug 3 06:25:06 svil kernel: scsi 5:0:8:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:8:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:8:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:8:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:8:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:06 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:06 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:06 svil kernel: Recovery SCB completes
Aug 3 06:25:06 svil kernel: scsi 5:0:8:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:8:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:8:0: Device offlined - not ready after
error recovery
Aug 3 06:25:06 svil kernel: scsi 5:0:9:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:9:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:9:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:9:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:9:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:06 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:06 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:06 svil kernel: Recovery SCB completes
Aug 3 06:25:06 svil kernel: scsi 5:0:9:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:9:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:9:0: Device offlined - not ready after
error recovery
Aug 3 06:25:06 svil kernel: scsi 5:0:10:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:10:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:10:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:10:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:10:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:06 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:06 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:06 svil kernel: Recovery SCB completes
Aug 3 06:25:06 svil kernel: scsi 5:0:10:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:10:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:10:0: Device offlined - not ready after
error recovery
Aug 3 06:25:06 svil kernel: scsi 5:0:11:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:11:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:11:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:11:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:11:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:06 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:06 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:06 svil kernel: Recovery SCB completes
Aug 3 06:25:06 svil kernel: scsi 5:0:11:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:11:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:11:0: Device offlined - not ready after
error recovery
Aug 3 06:25:06 svil kernel: scsi 5:0:12:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:12:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:12:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:12:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:12:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:06 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:06 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:06 svil kernel: Recovery SCB completes
Aug 3 06:25:06 svil kernel: scsi 5:0:12:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:12:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:12:0: Device offlined - not ready after
error recovery
Aug 3 06:25:06 svil kernel: scsi 5:0:13:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:13:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:13:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:13:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:13:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:06 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:06 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:06 svil kernel: Recovery SCB completes
Aug 3 06:25:06 svil kernel: scsi 5:0:13:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:13:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:13:0: Device offlined - not ready after
error recovery
Aug 3 06:25:06 svil kernel: scsi 5:0:14:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:14:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:14:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:06 svil kernel: scsi 5:0:14:0: Command already completed
Aug 3 06:25:06 svil kernel: scsi 5:0:14:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:06 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:07 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:07 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:07 svil kernel: Recovery SCB completes
Aug 3 06:25:07 svil kernel: scsi 5:0:14:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:07 svil kernel: scsi 5:0:14:0: Command already completed
Aug 3 06:25:07 svil kernel: scsi 5:0:14:0: Device offlined - not ready after
error recovery
Aug 3 06:25:07 svil kernel: scsi 5:0:15:0: Attempting to queue an ABORT
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:07 svil kernel: scsi 5:0:15:0: Command already completed
Aug 3 06:25:07 svil kernel: scsi 5:0:15:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:07 svil kernel: scsi 5:0:15:0: Command already completed
Aug 3 06:25:07 svil kernel: scsi 5:0:15:0: Attempting to queue a TARGET RESET
message:CDB: 0x12 0x0 0x0 0x0 0x24 0x0
Aug 3 06:25:07 svil kernel: scsi5: Device reset code sleeping
Aug 3 06:25:07 svil kernel: scsi5: Device reset timer expired (active 1)
Aug 3 06:25:07 svil kernel: scsi5: Device reset returning 0x2003
Aug 3 06:25:07 svil kernel: Recovery SCB completes
Aug 3 06:25:07 svil kernel: scsi 5:0:15:0: Attempting to queue an ABORT
message:CDB: 0x0 0x0 0x0 0x0 0x0 0x0
Aug 3 06:25:07 svil kernel: scsi 5:0:15:0: Command already completed
Aug 3 06:25:07 svil kernel: scsi 5:0:15:0: Device offlined - not ready after
error recovery
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* Re: [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
2009-09-11 9:23 ` [Bug 14159] " bugzilla-daemon
@ 2009-09-11 23:27 ` James Bottomley
2009-09-11 23:27 ` [Bug 14159] " bugzilla-daemon
` (15 subsequent siblings)
17 siblings, 0 replies; 26+ messages in thread
From: James Bottomley @ 2009-09-11 23:27 UTC (permalink / raw)
To: bugzilla-daemon; +Cc: linux-scsi
On Fri, 2009-09-11 at 09:18 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14159
>
> Summary: AIC79xx is not working properly with an attached scsi
> tape since 2.6.29
> Product: SCSI Drivers
> Version: 2.5
> Kernel Version: 2.6.27 (working), 2.6.30 (not working)
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: scsi_drivers-other@kernel-bugs.osdl.org
> ReportedBy: g.giorgetti@teamsystem.com
> CC: g.giorgetti@teamsystem.com
> Regression: Yes
>
>
> Both kernels 2.6.27 and 2.6.28 are working correctly.
> Since Linux 2.6.29 till 2.6.31rc8 the regression(?) is out there.
>
> Please let me know if I can provide any further details.
>
> Best regards,
> Gabriele
>
> =================
> Here is the messages part for Linux 2.6.27:
>
> aic79xx 0000:41:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
> scsi5 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0
> <Adaptec 29320ALP PCIx Ultra320 SCSI adapter>
> aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs
> target5:0:3: asynchronous
> scsi 5:0:3:0: Sequential-Access IBM HH LTO Gen 2 0376 PQ: 0 ANSI: 3
> target5:0:3: Beginning Domain Validation
> target5:0:3: wide asynchronous
> target5:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 126)
> target5:0:3: Ending Domain Validation
> scsi 5:0:3:0: Attached scsi generic sg7 type 1
> st: Version 20080504, fixed bufsize 32768, s/g segs 256
> Driver 'st' needs updating - please use bus_type methods
> st 5:0:3:0: Attached scsi tape st0
> st 5:0:3:0: st0: try direct i/o: yes (alignment 4 B)
> osst :I: Tape driver with OnStream support version 0.99.4
> osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $
> Driver 'osst' needs updating - please use bus_type methods
> st0: Block limits 256 - 524288 bytes.
> =================
>
> =================
> Here is Linux 2.6.30:
>
> Aug 3 06:25:04 svil kernel: aic79xx 0000:41:01.0: PCI INT A -> GSI 19 (level,
> low) -> IRQ 19
> Aug 3 06:25:04 svil kernel: scsi5 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev
> 3.0
> Aug 3 06:25:04 svil kernel: <Adaptec 29320ALP PCIx Ultra320 SCSI
> adapter>
> Aug 3 06:25:04 svil kernel: aic7901: Ultra320 Wide Channel A, SCSI
> Id=7, PCI-X 101-1
> Aug 3 06:25:04 svil kernel: scsi 5:0:0:0: Attempting to queue an ABORT
> message:CDB: 0x12 0x0
That's an inquiry to a non-existent target. It should have returned a
DID_NO_CONNECT timeout within 250ms. The fact that it didn't is
suggestive of interrupt routing problems. After all these messages have
completed, what does /proc/interrupts say?
James
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
2009-09-11 9:23 ` [Bug 14159] " bugzilla-daemon
2009-09-11 23:27 ` [Bug 14159] New: " James Bottomley
@ 2009-09-11 23:27 ` bugzilla-daemon
2009-09-14 7:18 ` bugzilla-daemon
` (14 subsequent siblings)
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-11 23:27 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #2 from Anonymous Emailer <anonymous@kernel-bugs.osdl.org> 2009-09-11 23:27:53 ---
Reply-To: James.Bottomley@suse.de
On Fri, 2009-09-11 at 09:18 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14159
>
> Summary: AIC79xx is not working properly with an attached scsi
> tape since 2.6.29
> Product: SCSI Drivers
> Version: 2.5
> Kernel Version: 2.6.27 (working), 2.6.30 (not working)
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: scsi_drivers-other@kernel-bugs.osdl.org
> ReportedBy: g.giorgetti@teamsystem.com
> CC: g.giorgetti@teamsystem.com
> Regression: Yes
>
>
> Both kernels 2.6.27 and 2.6.28 are working correctly.
> Since Linux 2.6.29 till 2.6.31rc8 the regression(?) is out there.
>
> Please let me know if I can provide any further details.
>
> Best regards,
> Gabriele
>
> =================
> Here is the messages part for Linux 2.6.27:
>
> aic79xx 0000:41:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
> scsi5 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0
> <Adaptec 29320ALP PCIx Ultra320 SCSI adapter>
> aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs
> target5:0:3: asynchronous
> scsi 5:0:3:0: Sequential-Access IBM HH LTO Gen 2 0376 PQ: 0 ANSI: 3
> target5:0:3: Beginning Domain Validation
> target5:0:3: wide asynchronous
> target5:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 126)
> target5:0:3: Ending Domain Validation
> scsi 5:0:3:0: Attached scsi generic sg7 type 1
> st: Version 20080504, fixed bufsize 32768, s/g segs 256
> Driver 'st' needs updating - please use bus_type methods
> st 5:0:3:0: Attached scsi tape st0
> st 5:0:3:0: st0: try direct i/o: yes (alignment 4 B)
> osst :I: Tape driver with OnStream support version 0.99.4
> osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $
> Driver 'osst' needs updating - please use bus_type methods
> st0: Block limits 256 - 524288 bytes.
> =================
>
> =================
> Here is Linux 2.6.30:
>
> Aug 3 06:25:04 svil kernel: aic79xx 0000:41:01.0: PCI INT A -> GSI 19 (level,
> low) -> IRQ 19
> Aug 3 06:25:04 svil kernel: scsi5 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev
> 3.0
> Aug 3 06:25:04 svil kernel: <Adaptec 29320ALP PCIx Ultra320 SCSI
> adapter>
> Aug 3 06:25:04 svil kernel: aic7901: Ultra320 Wide Channel A, SCSI
> Id=7, PCI-X 101-1
> Aug 3 06:25:04 svil kernel: scsi 5:0:0:0: Attempting to queue an ABORT
> message:CDB: 0x12 0x0
That's an inquiry to a non-existent target. It should have returned a
DID_NO_CONNECT timeout within 250ms. The fact that it didn't is
suggestive of interrupt routing problems. After all these messages have
completed, what does /proc/interrupts say?
James
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (2 preceding siblings ...)
2009-09-11 23:27 ` [Bug 14159] " bugzilla-daemon
@ 2009-09-14 7:18 ` bugzilla-daemon
2009-09-14 14:25 ` James Bottomley
2009-09-14 7:19 ` bugzilla-daemon
` (13 subsequent siblings)
17 siblings, 1 reply; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-14 7:18 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #3 from g.giorgetti@teamsystem.com 2009-09-14 07:18:46 ---
Hi James,
today after building and installing the latest stable kernel 2.6.31 I can tell
you that the problem is still there.
Here is the machine's /proc/interrups
CPU0 CPU1
0: 44 0 IO-APIC-edge timer
1: 0 2 IO-APIC-edge i8042
3: 0 0 IO-APIC-fasteoi ehci_hcd:usb2, ohci_hcd:usb5,
ohci_hcd:usb6
4: 0 2 IO-APIC-edge
8: 0 1 IO-APIC-edge rtc0
9: 0 0 IO-APIC-fasteoi acpi, sata_svw
12: 0 4 IO-APIC-edge i8042
14: 63 92631 IO-APIC-edge ide0
19: 0 0 IO-APIC-fasteoi aic79xx
20: 876 5417561 IO-APIC-fasteoi eth0
21: 0 29 IO-APIC-fasteoi ehci_hcd:usb1, ohci_hcd:usb3,
ohci_hcd:usb4
22: 268 827272 IO-APIC-fasteoi aacraid
NMI: 0 0 Non-maskable interrupts
LOC: 3340059 3367236 Local timer interrupts
SPU: 0 0 Spurious interrupts
CNT: 0 0 Performance counter interrupts
PND: 0 0 Performance pending work
RES: 132590 57223 Rescheduling interrupts
CAL: 80 64 Function call interrupts
TLB: 8153 6593 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
MCE: 0 0 Machine check exceptions
MCP: 40 40 Machine check polls
ERR: 0
MIS: 0
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* Re: [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-14 7:18 ` bugzilla-daemon
@ 2009-09-14 14:25 ` James Bottomley
2009-09-14 17:24 ` Bjorn Helgaas
0 siblings, 1 reply; 26+ messages in thread
From: James Bottomley @ 2009-09-14 14:25 UTC (permalink / raw)
To: bugzilla-daemon; +Cc: linux-scsi, linux-acpi
> --- Comment #3 from g.giorgetti@teamsystem.com 2009-09-14 07:18:46 ---
> today after building and installing the latest stable kernel 2.6.31 I can tell
> you that the problem is still there.
>
> Here is the machine's /proc/interrups
>
> CPU0 CPU1
> 0: 44 0 IO-APIC-edge timer
> 1: 0 2 IO-APIC-edge i8042
> 3: 0 0 IO-APIC-fasteoi ehci_hcd:usb2, ohci_hcd:usb5,
> ohci_hcd:usb6
> 4: 0 2 IO-APIC-edge
> 8: 0 1 IO-APIC-edge rtc0
> 9: 0 0 IO-APIC-fasteoi acpi, sata_svw
> 12: 0 4 IO-APIC-edge i8042
> 14: 63 92631 IO-APIC-edge ide0
> 19: 0 0 IO-APIC-fasteoi aic79xx
So this is the problem, as predicted: the card isn't getting interrupts.
This would strongly suggest an ACPI problem. Can you try booting with
pci=noacpi?
Thanks,
James
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-14 14:25 ` James Bottomley
@ 2009-09-14 17:24 ` Bjorn Helgaas
0 siblings, 0 replies; 26+ messages in thread
From: Bjorn Helgaas @ 2009-09-14 17:24 UTC (permalink / raw)
To: James Bottomley; +Cc: bugzilla-daemon, linux-scsi, linux-acpi, Stefan Assmann
On Monday 14 September 2009 08:25:12 am James Bottomley wrote:
> > --- Comment #3 from g.giorgetti@teamsystem.com 2009-09-14 07:18:46 ---
> > today after building and installing the latest stable kernel 2.6.31 I can tell
> > you that the problem is still there.
> >
> > Here is the machine's /proc/interrups
> >
> > CPU0 CPU1
> > 0: 44 0 IO-APIC-edge timer
> > 1: 0 2 IO-APIC-edge i8042
> > 3: 0 0 IO-APIC-fasteoi ehci_hcd:usb2, ohci_hcd:usb5,
> > ohci_hcd:usb6
> > 4: 0 2 IO-APIC-edge
> > 8: 0 1 IO-APIC-edge rtc0
> > 9: 0 0 IO-APIC-fasteoi acpi, sata_svw
> > 12: 0 4 IO-APIC-edge i8042
> > 14: 63 92631 IO-APIC-edge ide0
> > 19: 0 0 IO-APIC-fasteoi aic79xx
>
> So this is the problem, as predicted: the card isn't getting interrupts.
> This would strongly suggest an ACPI problem. Can you try booting with
> pci=noacpi?
You might also try "pci=noioapicquirk". Commit bbe194433bae [1]
fiddles with boot interrupts on AMD 813x devices, which you seem
to have.
Bjorn
[1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=bbe194433baeadc953f49e3795b41ffffc5486dd
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (3 preceding siblings ...)
2009-09-14 7:18 ` bugzilla-daemon
@ 2009-09-14 7:19 ` bugzilla-daemon
2009-09-14 14:25 ` bugzilla-daemon
` (12 subsequent siblings)
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-14 7:19 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #4 from g.giorgetti@teamsystem.com 2009-09-14 07:19:51 ---
Created an attachment (id=23092)
--> (http://bugzilla.kernel.org/attachment.cgi?id=23092)
2.6.31 dmesg output
This is the machine dmesg output with 2.6.31
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (4 preceding siblings ...)
2009-09-14 7:19 ` bugzilla-daemon
@ 2009-09-14 14:25 ` bugzilla-daemon
2009-09-14 17:24 ` bugzilla-daemon
` (11 subsequent siblings)
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-14 14:25 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #5 from Anonymous Emailer <anonymous@kernel-bugs.osdl.org> 2009-09-14 14:25:23 ---
Reply-To: James.Bottomley@suse.de
> --- Comment #3 from g.giorgetti@teamsystem.com 2009-09-14 07:18:46 ---
> today after building and installing the latest stable kernel 2.6.31 I can tell
> you that the problem is still there.
>
> Here is the machine's /proc/interrups
>
> CPU0 CPU1
> 0: 44 0 IO-APIC-edge timer
> 1: 0 2 IO-APIC-edge i8042
> 3: 0 0 IO-APIC-fasteoi ehci_hcd:usb2, ohci_hcd:usb5,
> ohci_hcd:usb6
> 4: 0 2 IO-APIC-edge
> 8: 0 1 IO-APIC-edge rtc0
> 9: 0 0 IO-APIC-fasteoi acpi, sata_svw
> 12: 0 4 IO-APIC-edge i8042
> 14: 63 92631 IO-APIC-edge ide0
> 19: 0 0 IO-APIC-fasteoi aic79xx
So this is the problem, as predicted: the card isn't getting interrupts.
This would strongly suggest an ACPI problem. Can you try booting with
pci=noacpi?
Thanks,
James
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (5 preceding siblings ...)
2009-09-14 14:25 ` bugzilla-daemon
@ 2009-09-14 17:24 ` bugzilla-daemon
2009-09-15 7:05 ` bugzilla-daemon
` (10 subsequent siblings)
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-14 17:24 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #6 from Bjorn Helgaas <bjorn.helgaas@hp.com> 2009-09-14 17:24:42 ---
On Monday 14 September 2009 08:25:12 am James Bottomley wrote:
> > --- Comment #3 from g.giorgetti@teamsystem.com 2009-09-14 07:18:46 ---
> > today after building and installing the latest stable kernel 2.6.31 I can tell
> > you that the problem is still there.
> >
> > Here is the machine's /proc/interrups
> >
> > CPU0 CPU1
> > 0: 44 0 IO-APIC-edge timer
> > 1: 0 2 IO-APIC-edge i8042
> > 3: 0 0 IO-APIC-fasteoi ehci_hcd:usb2, ohci_hcd:usb5,
> > ohci_hcd:usb6
> > 4: 0 2 IO-APIC-edge
> > 8: 0 1 IO-APIC-edge rtc0
> > 9: 0 0 IO-APIC-fasteoi acpi, sata_svw
> > 12: 0 4 IO-APIC-edge i8042
> > 14: 63 92631 IO-APIC-edge ide0
> > 19: 0 0 IO-APIC-fasteoi aic79xx
>
> So this is the problem, as predicted: the card isn't getting interrupts.
> This would strongly suggest an ACPI problem. Can you try booting with
> pci=noacpi?
You might also try "pci=noioapicquirk". Commit bbe194433bae [1]
fiddles with boot interrupts on AMD 813x devices, which you seem
to have.
Bjorn
[1]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=bbe194433baeadc953f49e3795b41ffffc5486dd
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (6 preceding siblings ...)
2009-09-14 17:24 ` bugzilla-daemon
@ 2009-09-15 7:05 ` bugzilla-daemon
2009-09-15 13:53 ` James Bottomley
2009-09-15 13:07 ` bugzilla-daemon
` (9 subsequent siblings)
17 siblings, 1 reply; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-15 7:05 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #7 from g.giorgetti@teamsystem.com 2009-09-15 07:05:46 ---
Hi Bjorn and James,
pci=noacpi is not working, so even before reading Bjorn's reply, we tried
"noapic" and the suddenly the tape device was working again. No more timeouts
on initialization and so on.
I haven't tried pci=noioapicquirk yet, since the server is up for production
and other people is working.
So I'm gonna do that later in the day.
Thank you very much for now.
Regards,
Gabriele
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* Re: [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-15 7:05 ` bugzilla-daemon
@ 2009-09-15 13:53 ` James Bottomley
0 siblings, 0 replies; 26+ messages in thread
From: James Bottomley @ 2009-09-15 13:53 UTC (permalink / raw)
To: bugzilla-daemon; +Cc: linux-scsi, linux-acpi
On Tue, 2009-09-15 at 07:05 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14159
cc'ing linux-acpi
James
> --- Comment #7 from g.giorgetti@teamsystem.com 2009-09-15 07:05:46 ---
> Hi Bjorn and James,
>
> pci=noacpi is not working, so even before reading Bjorn's reply, we tried
> "noapic" and the suddenly the tape device was working again. No more timeouts
> on initialization and so on.
>
> I haven't tried pci=noioapicquirk yet, since the server is up for production
> and other people is working.
> So I'm gonna do that later in the day.
>
> Thank you very much for now.
>
> Regards,
> Gabriele
>
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (7 preceding siblings ...)
2009-09-15 7:05 ` bugzilla-daemon
@ 2009-09-15 13:07 ` bugzilla-daemon
2009-09-15 13:55 ` James Bottomley
2009-09-15 13:53 ` bugzilla-daemon
` (8 subsequent siblings)
17 siblings, 1 reply; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-15 13:07 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #8 from g.giorgetti@teamsystem.com 2009-09-15 13:07:42 ---
All right, we've just rebooted the server and tried with the "noioapicquirk"
param and everything is fine.
Looking at the patch you put up in your reply I can see some code for amd_813x
(quirk_disable_amd_813x_boot_interrupt and the definition for AMD_813X_REV_B2)
So just in case you need it, I'm pasting the lspci for the AMD-8131 we have.
Please let me know if you need anything else.
Thank you,
Gabriele
40:0f.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12)
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+
Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 150
Bus: primary=40, secondary=41, subordinate=41, sec-latency=96
I/O behind bridge: 00007000-00007fff
Memory behind bridge: e1f00000-e1ffffff
Prefetchable memory behind bridge: 00000000e0200000-00000000e02fffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [a0] PCI-X bridge device
Secondary Status: 64bit+ 133MHz+ SCD- USC- SCO- SRD- Freq=133MHz
Status: Dev=40:0f.0 64bit+ 133MHz+ SCD- USC- SCO- SRD-
Upstream: Capacity=14 CommitmentLimit=65535
Downstream: Capacity=2 CommitmentLimit=65535
Capabilities: [b8] HyperTransport: Interrupt Discovery and Configuration
Capabilities: [c0] HyperTransport: Slave or Primary Interface
!!! Possibly incomplete decoding
Command: BaseUnitID=15 UnitCnt=2 MastHost- DefDir-
Link Control 0: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0
Link Config 0: MLWI=16bit MLWO=16bit LWI=16bit LWO=16bit
Link Control 1: CFlE- CST- CFE- <LkFail+ Init- EOC+ TXO+ <CRCErr=0
Link Config 1: MLWI=8bit MLWO=8bit LWI=N/C LWO=N/C
Revision ID: 1.02
40:0f.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01)
(prog-if 10 [IO-APIC])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 0
40:10.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12)
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+
Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 150
Bus: primary=40, secondary=42, subordinate=42, sec-latency=0
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
Capabilities: [a0] PCI-X bridge device
Secondary Status: 64bit+ 133MHz+ SCD- USC- SCO- SRD- Freq=conv
Status: Dev=40:10.0 64bit+ 133MHz+ SCD- USC- SCO- SRD-
Upstream: Capacity=14 CommitmentLimit=65535
Downstream: Capacity=2 CommitmentLimit=65535
Capabilities: [b8] HyperTransport: Interrupt Discovery and Configuration
40:10.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01)
(prog-if 10 [IO-APIC])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 0
41:01.0 SCSI storage controller: Adaptec ASC-29320ALP U320 (rev 10)
Subsystem: Adaptec Unknown device 0044
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+
Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 148 (10000ns min, 6250ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 19
Region 0: I/O ports at 7000 [disabled] [size=256]
Region 1: Memory at e1f80000 (64-bit, non-prefetchable) [size=8K]
Region 3: I/O ports at 7800 [disabled] [size=256]
[virtual] Expansion ROM at e0200000 [disabled] [size=512K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1
Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [94] PCI-X non-bridge device
Command: DPERE- ERO- RBC=512 OST=3
Status: Dev=41:01.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=512
DMOST=8 DMCRS=16 RSCEM- 266MHz- 533MHz-
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* Re: [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-15 13:07 ` bugzilla-daemon
@ 2009-09-15 13:55 ` James Bottomley
2009-09-15 15:08 ` Bjorn Helgaas
0 siblings, 1 reply; 26+ messages in thread
From: James Bottomley @ 2009-09-15 13:55 UTC (permalink / raw)
To: bugzilla-daemon; +Cc: linux-scsi, linux-acpi
On Tue, 2009-09-15 at 13:07 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14159
cc'ing linux-acpi
James
> --- Comment #8 from g.giorgetti@teamsystem.com 2009-09-15 13:07:42 ---
> All right, we've just rebooted the server and tried with the "noioapicquirk"
> param and everything is fine.
>
> Looking at the patch you put up in your reply I can see some code for amd_813x
> (quirk_disable_amd_813x_boot_interrupt and the definition for AMD_813X_REV_B2)
>
> So just in case you need it, I'm pasting the lspci for the AMD-8131 we have.
> Please let me know if you need anything else.
>
> Thank you,
> Gabriele
>
>
>
> 40:0f.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12)
> (prog-if 00 [Normal decode])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+
> Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort- >SERR- <PERR-
> Latency: 150
> Bus: primary=40, secondary=41, subordinate=41, sec-latency=96
> I/O behind bridge: 00007000-00007fff
> Memory behind bridge: e1f00000-e1ffffff
> Prefetchable memory behind bridge: 00000000e0200000-00000000e02fffff
> Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort- <SERR- <PERR-
> BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
> Capabilities: [a0] PCI-X bridge device
> Secondary Status: 64bit+ 133MHz+ SCD- USC- SCO- SRD- Freq=133MHz
> Status: Dev=40:0f.0 64bit+ 133MHz+ SCD- USC- SCO- SRD-
> Upstream: Capacity=14 CommitmentLimit=65535
> Downstream: Capacity=2 CommitmentLimit=65535
> Capabilities: [b8] HyperTransport: Interrupt Discovery and Configuration
> Capabilities: [c0] HyperTransport: Slave or Primary Interface
> !!! Possibly incomplete decoding
> Command: BaseUnitID=15 UnitCnt=2 MastHost- DefDir-
> Link Control 0: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0
> Link Config 0: MLWI=16bit MLWO=16bit LWI=16bit LWO=16bit
> Link Control 1: CFlE- CST- CFE- <LkFail+ Init- EOC+ TXO+ <CRCErr=0
> Link Config 1: MLWI=8bit MLWO=8bit LWI=N/C LWO=N/C
> Revision ID: 1.02
>
> 40:0f.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01)
> (prog-if 10 [IO-APIC])
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort- >SERR- <PERR-
> Latency: 0
>
> 40:10.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12)
> (prog-if 00 [Normal decode])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+
> Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort- >SERR- <PERR-
> Latency: 150
> Bus: primary=40, secondary=42, subordinate=42, sec-latency=0
> I/O behind bridge: 0000f000-00000fff
> Memory behind bridge: fff00000-000fffff
> Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
> Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort+ <SERR- <PERR-
> BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
> Capabilities: [a0] PCI-X bridge device
> Secondary Status: 64bit+ 133MHz+ SCD- USC- SCO- SRD- Freq=conv
> Status: Dev=40:10.0 64bit+ 133MHz+ SCD- USC- SCO- SRD-
> Upstream: Capacity=14 CommitmentLimit=65535
> Downstream: Capacity=2 CommitmentLimit=65535
> Capabilities: [b8] HyperTransport: Interrupt Discovery and Configuration
>
> 40:10.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01)
> (prog-if 10 [IO-APIC])
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort- >SERR- <PERR-
> Latency: 0
>
> 41:01.0 SCSI storage controller: Adaptec ASC-29320ALP U320 (rev 10)
> Subsystem: Adaptec Unknown device 0044
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+
> Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort-
> <MAbort- >SERR- <PERR-
> Latency: 148 (10000ns min, 6250ns max), Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 19
> Region 0: I/O ports at 7000 [disabled] [size=256]
> Region 1: Memory at e1f80000 (64-bit, non-prefetchable) [size=8K]
> Region 3: I/O ports at 7800 [disabled] [size=256]
> [virtual] Expansion ROM at e0200000 [disabled] [size=512K]
> Capabilities: [dc] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1
> Enable-
> Address: 0000000000000000 Data: 0000
> Capabilities: [94] PCI-X non-bridge device
> Command: DPERE- ERO- RBC=512 OST=3
> Status: Dev=41:01.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=512
> DMOST=8 DMCRS=16 RSCEM- 266MHz- 533MHz-
>
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (8 preceding siblings ...)
2009-09-15 13:07 ` bugzilla-daemon
@ 2009-09-15 13:53 ` bugzilla-daemon
2009-09-15 13:55 ` bugzilla-daemon
` (7 subsequent siblings)
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-15 13:53 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #9 from Anonymous Emailer <anonymous@kernel-bugs.osdl.org> 2009-09-15 13:53:40 ---
Reply-To: James.Bottomley@suse.de
On Tue, 2009-09-15 at 07:05 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14159
cc'ing linux-acpi
James
> --- Comment #7 from g.giorgetti@teamsystem.com 2009-09-15 07:05:46 ---
> Hi Bjorn and James,
>
> pci=noacpi is not working, so even before reading Bjorn's reply, we tried
> "noapic" and the suddenly the tape device was working again. No more timeouts
> on initialization and so on.
>
> I haven't tried pci=noioapicquirk yet, since the server is up for production
> and other people is working.
> So I'm gonna do that later in the day.
>
> Thank you very much for now.
>
> Regards,
> Gabriele
>
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (9 preceding siblings ...)
2009-09-15 13:53 ` bugzilla-daemon
@ 2009-09-15 13:55 ` bugzilla-daemon
2009-09-15 15:08 ` bugzilla-daemon
` (6 subsequent siblings)
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-15 13:55 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #10 from Anonymous Emailer <anonymous@kernel-bugs.osdl.org> 2009-09-15 13:55:57 ---
Reply-To: James.Bottomley@suse.de
On Tue, 2009-09-15 at 13:07 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14159
cc'ing linux-acpi
James
> --- Comment #8 from g.giorgetti@teamsystem.com 2009-09-15 13:07:42 ---
> All right, we've just rebooted the server and tried with the "noioapicquirk"
> param and everything is fine.
>
> Looking at the patch you put up in your reply I can see some code for amd_813x
> (quirk_disable_amd_813x_boot_interrupt and the definition for AMD_813X_REV_B2)
>
> So just in case you need it, I'm pasting the lspci for the AMD-8131 we have.
> Please let me know if you need anything else.
>
> Thank you,
> Gabriele
>
>
>
> 40:0f.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12)
> (prog-if 00 [Normal decode])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+
> Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort- >SERR- <PERR-
> Latency: 150
> Bus: primary=40, secondary=41, subordinate=41, sec-latency=96
> I/O behind bridge: 00007000-00007fff
> Memory behind bridge: e1f00000-e1ffffff
> Prefetchable memory behind bridge: 00000000e0200000-00000000e02fffff
> Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort- <SERR- <PERR-
> BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
> Capabilities: [a0] PCI-X bridge device
> Secondary Status: 64bit+ 133MHz+ SCD- USC- SCO- SRD- Freq=133MHz
> Status: Dev=40:0f.0 64bit+ 133MHz+ SCD- USC- SCO- SRD-
> Upstream: Capacity=14 CommitmentLimit=65535
> Downstream: Capacity=2 CommitmentLimit=65535
> Capabilities: [b8] HyperTransport: Interrupt Discovery and Configuration
> Capabilities: [c0] HyperTransport: Slave or Primary Interface
> !!! Possibly incomplete decoding
> Command: BaseUnitID=15 UnitCnt=2 MastHost- DefDir-
> Link Control 0: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0
> Link Config 0: MLWI=16bit MLWO=16bit LWI=16bit LWO=16bit
> Link Control 1: CFlE- CST- CFE- <LkFail+ Init- EOC+ TXO+ <CRCErr=0
> Link Config 1: MLWI=8bit MLWO=8bit LWI=N/C LWO=N/C
> Revision ID: 1.02
>
> 40:0f.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01)
> (prog-if 10 [IO-APIC])
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort- >SERR- <PERR-
> Latency: 0
>
> 40:10.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12)
> (prog-if 00 [Normal decode])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+
> Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort- >SERR- <PERR-
> Latency: 150
> Bus: primary=40, secondary=42, subordinate=42, sec-latency=0
> I/O behind bridge: 0000f000-00000fff
> Memory behind bridge: fff00000-000fffff
> Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
> Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort+ <SERR- <PERR-
> BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
> Capabilities: [a0] PCI-X bridge device
> Secondary Status: 64bit+ 133MHz+ SCD- USC- SCO- SRD- Freq=conv
> Status: Dev=40:10.0 64bit+ 133MHz+ SCD- USC- SCO- SRD-
> Upstream: Capacity=14 CommitmentLimit=65535
> Downstream: Capacity=2 CommitmentLimit=65535
> Capabilities: [b8] HyperTransport: Interrupt Discovery and Configuration
>
> 40:10.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01)
> (prog-if 10 [IO-APIC])
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
> <MAbort- >SERR- <PERR-
> Latency: 0
>
> 41:01.0 SCSI storage controller: Adaptec ASC-29320ALP U320 (rev 10)
> Subsystem: Adaptec Unknown device 0044
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+
> Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort-
> <MAbort- >SERR- <PERR-
> Latency: 148 (10000ns min, 6250ns max), Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 19
> Region 0: I/O ports at 7000 [disabled] [size=256]
> Region 1: Memory at e1f80000 (64-bit, non-prefetchable) [size=8K]
> Region 3: I/O ports at 7800 [disabled] [size=256]
> [virtual] Expansion ROM at e0200000 [disabled] [size=512K]
> Capabilities: [dc] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1
> Enable-
> Address: 0000000000000000 Data: 0000
> Capabilities: [94] PCI-X non-bridge device
> Command: DPERE- ERO- RBC=512 OST=3
> Status: Dev=41:01.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=512
> DMOST=8 DMCRS=16 RSCEM- 266MHz- 533MHz-
>
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (10 preceding siblings ...)
2009-09-15 13:55 ` bugzilla-daemon
@ 2009-09-15 15:08 ` bugzilla-daemon
2009-09-15 15:14 ` bugzilla-daemon
` (5 subsequent siblings)
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-15 15:08 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #11 from Bjorn Helgaas <bjorn.helgaas@hp.com> 2009-09-15 15:08:46 ---
> > http://bugzilla.kernel.org/show_bug.cgi?id=14159
> > --- Comment #8 from g.giorgetti@teamsystem.com 2009-09-15 13:07:42 ---
> > All right, we've just rebooted the server and tried with the "noioapicquirk"
> > param and everything is fine.
Great, thanks. Gabriele, could you attach the "lspci -nn" output,
please? I'm hoping Stefan will update the quirk, and I think he'll
need the numeric device ID.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (11 preceding siblings ...)
2009-09-15 15:08 ` bugzilla-daemon
@ 2009-09-15 15:14 ` bugzilla-daemon
2009-09-15 15:20 ` bugzilla-daemon
` (4 subsequent siblings)
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-15 15:14 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #12 from g.giorgetti@teamsystem.com 2009-09-15 15:14:58 ---
Created an attachment (id=23097)
--> (http://bugzilla.kernel.org/attachment.cgi?id=23097)
lspci -nn output as requested (2.6.31)
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (12 preceding siblings ...)
2009-09-15 15:14 ` bugzilla-daemon
@ 2009-09-15 15:20 ` bugzilla-daemon
2009-09-16 9:16 ` bugzilla-daemon
` (3 subsequent siblings)
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-15 15:20 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #13 from g.giorgetti@teamsystem.com 2009-09-15 15:20:57 ---
Of course Bjorn.
There you go. You'll find the lspci -nn output in the attachments.
Thank you again.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (13 preceding siblings ...)
2009-09-15 15:20 ` bugzilla-daemon
@ 2009-09-16 9:16 ` bugzilla-daemon
2009-09-16 13:42 ` bugzilla-daemon
` (2 subsequent siblings)
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-16 9:16 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #14 from Stefan Assmann <sassmann@redhat.com> 2009-09-16 09:16:35 ---
Created an attachment (id=23100)
--> (http://bugzilla.kernel.org/attachment.cgi?id=23100)
skip disabling NOIOAMODE on AMD 8131 rev B1
Hi Gabriele,
could you please test again with the attached patch. I've added a check to skip
rev B1 of the AMD 8131. While looking at the code I recognized that the
DECLARE_PCI_FIXUP_* calls were missing some cases as well. So I fixed that too.
Hope this works for you.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (14 preceding siblings ...)
2009-09-16 9:16 ` bugzilla-daemon
@ 2009-09-16 13:42 ` bugzilla-daemon
2009-09-17 6:45 ` bugzilla-daemon
2009-09-17 14:14 ` bugzilla-daemon
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-16 13:42 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #15 from g.giorgetti@teamsystem.com 2009-09-16 13:42:33 ---
Hi Stefan,
I'm rebuilding the patched 2.6.31 kernel just right now.
Tomorrow (unfortunately I'm not allowed to reboot today), I'll be able to
reboot the server and let you know the outcome.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (15 preceding siblings ...)
2009-09-16 13:42 ` bugzilla-daemon
@ 2009-09-17 6:45 ` bugzilla-daemon
2009-09-17 14:14 ` bugzilla-daemon
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-17 6:45 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #16 from g.giorgetti@teamsystem.com 2009-09-17 06:45:05 ---
OK great, I tried with the patched kernel. It works.
Thanks
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread* [Bug 14159] AIC79xx is not working properly with an attached scsi tape since 2.6.29
2009-09-11 9:18 [Bug 14159] New: AIC79xx is not working properly with an attached scsi tape since 2.6.29 bugzilla-daemon
` (16 preceding siblings ...)
2009-09-17 6:45 ` bugzilla-daemon
@ 2009-09-17 14:14 ` bugzilla-daemon
17 siblings, 0 replies; 26+ messages in thread
From: bugzilla-daemon @ 2009-09-17 14:14 UTC (permalink / raw)
To: linux-scsi
http://bugzilla.kernel.org/show_bug.cgi?id=14159
--- Comment #17 from Stefan Assmann <sassmann@redhat.com> 2009-09-17 14:14:46 ---
thanks for testing, I'll post the patch for upstream inclusion.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 26+ messages in thread