Distribution: Slackware 10.0.0 Hardware Environment: Adaptec SCSI Card 39160, BROWNIE-1600U3P Software Environment: kernel 2.6.12.3 Problem Description: When i'm upgrade kernel from 2.4.31 to 2.6.12.3, i can't access logical device on my brownie storage with LUN other then 0 i'm try to use another 2.6.x kernels , but this problems seem's to be present. There is no problem with 2.4.31 (and i try 2.4.29 kernel). dmesg from 2.6.12.3 after modprobe aic7xxx (module aic7xxx compiled with verbose debug info) ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 25 (level, low) -> IRQ 25 ahc_pci:3:3:0: hardware scb 64 bytes; kernel scb 52 bytes; ahc_dma 8 bytes ACPI: PCI Interrupt 0000:03:03.1[B] -> GSI 26 (level, low) -> IRQ 26 ahc_pci:3:3:1: hardware scb 64 bytes; kernel scb 52 bytes; ahc_dma 8 bytes scsi2 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 <Adaptec 3960D Ultra160 SCSI adapter> aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs (scsi2:A:0:0): Saw Selection Timeout for SCB 0x3 (scsi2:A:1:0): Handled Residual of 4 bytes Vendor: BROWNIE Model: 1600U3P Rev: 0001 Type: Direct-Access ANSI SCSI revision: 03 scsi2:A:1:0: Tagged Queuing enabled. Depth 32 target2:0:1: Beginning Domain Validation (scsi2:A:1:0): Handled Residual of 4 bytes (scsi2:A:1:0): Handled Residual of 4 bytes (scsi2:A:1:0): Handled Residual of 4 bytes (scsi2:A:1:0): Handled Residual of 4 bytes WIDTH IS 1 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0xc0 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x20 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x2 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x1 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x2 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x3 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x1 scsi2:A:1:0: INITIATOR_MSG_OUT PHASEMIS in Message-in phase scsi2:A:1:0: INITIATOR_MSG_IN byte 0x1 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x2 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x3 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x1 scsi2:A:1:0: Asserting ATN for response scsi2:A:1:0: INITIATOR_MSG_IN PHASEMIS in Message-out phase scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x1 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x3 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x1 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x45 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x0 scsi2:A:1:0: INITIATOR_MSG_OUT PHASEMIS in Message-in phase scsi2:A:1:0: INITIATOR_MSG_IN byte 0x1 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x3 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x1 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x0 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x0 (scsi2:A:1): 6.600MB/s transfers (16bit) scsi2:A:1:0: INITIATOR_MSG_IN PHASEMIS in Command phase (scsi2:A:1:0): Handled Residual of 4 bytes (scsi2:A:1:0): Handled Residual of 4 bytes (scsi2:A:1:0): Handled Residual of 4 bytes (scsi2:A:1:0): SCB 3: requests Check Status (scsi2:A:1:0): Sending Sense scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x80 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x1 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x2 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x3 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x1 scsi2:A:1:0: INITIATOR_MSG_OUT PHASEMIS in Message-in phase scsi2:A:1:0: INITIATOR_MSG_IN byte 0x1 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x2 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x3 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x1 scsi2:A:1:0: Asserting ATN for response scsi2:A:1:0: INITIATOR_MSG_IN PHASEMIS in Message-out phase scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x1 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x3 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x1 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x45 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x0 scsi2:A:1:0: INITIATOR_MSG_OUT PHASEMIS in Message-in phase scsi2:A:1:0: INITIATOR_MSG_IN byte 0x1 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x3 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x1 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x0 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x0 scsi2:A:1:0: INITIATOR_MSG_IN PHASEMIS in Command phase (scsi2:A:1:0): Handled Sense Residual of 12 bytes Copied 20 bytes of sense data: 0xf0 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x0 0x0 0x0 0x0 0x0 0x0 0x0 target2:0:1: Domain Validation skipping write tests scsi2:A:1:0: INITIATOR_MSG_OUT byte 0xc0 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x20 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x2 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x1 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x6 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x4 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x9 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x0 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x7f scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x1 scsi2:A:1:0: INITIATOR_MSG_OUT byte 0x2 scsi2:A:1:0: INITIATOR_MSG_OUT PHASEMIS in Message-in phase scsi2:A:1:0: INITIATOR_MSG_IN byte 0x1 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x6 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x4 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x9 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x0 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x1f scsi2:A:1:0: INITIATOR_MSG_IN byte 0x1 scsi2:A:1:0: INITIATOR_MSG_IN byte 0x2 (scsi2:A:1): 160.000MB/s transfers (80.000MHz DT, offset 31, 16bit) scsi2:A:1:0: INITIATOR_MSG_IN PHASEMIS in Command phase (scsi2:A:1:0): Handled Residual of 4 bytes (scsi2:A:1:0): Handled Residual of 4 bytes (scsi2:A:1:0): Handled Residual of 4 bytes (scsi2:A:1:0): Handled Residual of 4 bytes target2:0:1: Ending Domain Validation SCSI device sdc: 2788016128 512-byte hdwr sectors (1427464 MB) (scsi2:A:1:0): Handled Residual of 4 bytes SCSI device sdc: drive cache: write back SCSI device sdc: 2788016128 512-byte hdwr sectors (1427464 MB) (scsi2:A:1:0): Handled Residual of 4 bytes SCSI device sdc: drive cache: write back sdc: sdc1 sdc2 sdc3 sdc4 Attached scsi disk sdc at scsi2, channel 0, id 1, lun 0 (scsi2:A:1:0): Handled Residual of 3960 bytes scsi: host 2 channel 0 id 1 lun 0x00000200080c0400 has a LUN larger than currently supported. scsi: host 2 channel 0 id 1 lun 0xff010000ffffffff has a LUN larger than currently supported. scsi: host 2 channel 0 id 1 lun 0x0002202020202020 has a LUN larger than currently supported. scsi: host 2 channel 0 id 1 lun808529923 has a LUN larger than allowed by the host adapter (scsi2:A:1:4): Handled Residual of 4 bytes (scsi2:A:1:5): Handled Residual of 4 bytes scsi: host 2 channel 0 id 1 lun3078 has a LUN larger than allowed by the host adapter (scsi2:A:1:7): Handled Residual of 4 bytes (scsi2:A:1:8): Handled Residual of 4 bytes (scsi2:A:1:9): Handled Residual of 4 bytes (scsi2:A:1:10): Handled Residual of 4 bytes (scsi2:A:1:11): Handled Residual of 4 bytes (scsi2:A:1:12): Handled Residual of 4 bytes (scsi2:A:1:13): Handled Residual of 4 bytes (scsi2:A:1:14): Handled Residual of 4 bytes (scsi2:A:1:15): Handled Residual of 4 bytes (scsi2:A:2:0): Saw Selection Timeout for SCB 0x2 (scsi2:A:3:0): Saw Selection Timeout for SCB 0x3 (scsi2:A:4:0): Saw Selection Timeout for SCB 0x2 (scsi2:A:5:0): Saw Selection Timeout for SCB 0x3 (scsi2:A:6:0): Saw Selection Timeout for SCB 0x2 (scsi2:A:8:0): Saw Selection Timeout for SCB 0x3 (scsi2:A:9:0): Saw Selection Timeout for SCB 0x2 (scsi2:A:10:0): Saw Selection Timeout for SCB 0x3 (scsi2:A:11:0): Saw Selection Timeout for SCB 0x2 (scsi2:A:12:0): Saw Selection Timeout for SCB 0x3 (scsi2:A:13:0): Saw Selection Timeout for SCB 0x2 (scsi2:A:14:0): Saw Selection Timeout for SCB 0x3 (scsi2:A:15:0): Saw Selection Timeout for SCB 0x2 scsi3 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 <Adaptec 3960D Ultra160 SCSI adapter> aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs (scsi3:A:0:0): Handled Residual of 4 bytes Vendor: BROWNIE Model: 1600U3P Rev: 0001 Type: Direct-Access ANSI SCSI revision: 03 scsi3:A:0:0: Tagged Queuing enabled. Depth 32 target3:0:0: Beginning Domain Validation (scsi3:A:0:0): Handled Residual of 4 bytes (scsi3:A:0:0): Handled Residual of 4 bytes (scsi3:A:0:0): Handled Residual of 4 bytes (scsi3:A:0:0): Handled Residual of 4 bytes WIDTH IS 1 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0xc0 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x20 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x3 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x1 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x2 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x3 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x1 scsi3:A:0:0: INITIATOR_MSG_OUT PHASEMIS in Message-in phase scsi3:A:0:0: INITIATOR_MSG_IN byte 0x1 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x2 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x3 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x1 scsi3:A:0:0: Asserting ATN for response scsi3:A:0:0: INITIATOR_MSG_IN PHASEMIS in Message-out phase scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x1 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x3 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x1 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x45 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x0 scsi3:A:0:0: INITIATOR_MSG_OUT PHASEMIS in Message-in phase scsi3:A:0:0: INITIATOR_MSG_IN byte 0x1 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x3 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x1 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x0 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x0 (scsi3:A:0): 6.600MB/s transfers (16bit) scsi3:A:0:0: INITIATOR_MSG_IN PHASEMIS in Command phase (scsi3:A:0:0): Handled Residual of 4 bytes (scsi3:A:0:0): Handled Residual of 4 bytes (scsi3:A:0:0): Handled Residual of 4 bytes (scsi3:A:0:0): SCB 2: requests Check Status (scsi3:A:0:0): Sending Sense scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x80 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x1 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x2 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x3 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x1 scsi3:A:0:0: INITIATOR_MSG_OUT PHASEMIS in Message-in phase scsi3:A:0:0: INITIATOR_MSG_IN byte 0x1 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x2 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x3 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x1 scsi3:A:0:0: Asserting ATN for response scsi3:A:0:0: INITIATOR_MSG_IN PHASEMIS in Message-out phase scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x1 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x3 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x1 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x45 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x0 scsi3:A:0:0: INITIATOR_MSG_OUT PHASEMIS in Message-in phase scsi3:A:0:0: INITIATOR_MSG_IN byte 0x1 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x3 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x1 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x0 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x0 scsi3:A:0:0: INITIATOR_MSG_IN PHASEMIS in Command phase (scsi3:A:0:0): Handled Sense Residual of 12 bytes Copied 20 bytes of sense data: 0xf0 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x0 0x0 0x0 0x0 0x0 0x0 0x0 target3:0:0: Domain Validation skipping write tests scsi3:A:0:0: INITIATOR_MSG_OUT byte 0xc0 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x20 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x3 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x1 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x6 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x4 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x9 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x0 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x7f scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x1 scsi3:A:0:0: INITIATOR_MSG_OUT byte 0x2 scsi3:A:0:0: INITIATOR_MSG_OUT PHASEMIS in Message-in phase scsi3:A:0:0: INITIATOR_MSG_IN byte 0x1 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x6 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x4 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x9 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x0 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x1f scsi3:A:0:0: INITIATOR_MSG_IN byte 0x1 scsi3:A:0:0: INITIATOR_MSG_IN byte 0x2 (scsi3:A:0): 160.000MB/s transfers (80.000MHz DT, offset 31, 16bit) scsi3:A:0:0: INITIATOR_MSG_IN PHASEMIS in Command phase (scsi3:A:0:0): Handled Residual of 4 bytes (scsi3:A:0:0): Handled Residual of 4 bytes (scsi3:A:0:0): Handled Residual of 4 bytes (scsi3:A:0:0): Handled Residual of 4 bytes target3:0:0: Ending Domain Validation SCSI device sdd: 4294950912 512-byte hdwr sectors (2199015 MB) (scsi3:A:0:0): Handled Residual of 4 bytes SCSI device sdd: drive cache: write back SCSI device sdd: 4294950912 512-byte hdwr sectors (2199015 MB) (scsi3:A:0:0): Handled Residual of 4 bytes SCSI device sdd: drive cache: write back sdd: sdd1 Attached scsi disk sdd at scsi3, channel 0, id 0, lun 0 (scsi3:A:0:0): Handled Residual of 3960 bytes scsi: host 3 channel 0 id 0 lun 0x00000200080c0400 has a LUN larger than currently supported. scsi: host 3 channel 0 id 0 lun 0xff010000ffffffff has a LUN larger than currently supported. scsi: host 3 channel 0 id 0 lun 0x0002202020202020 has a LUN larger than currently supported. scsi: host 3 channel 0 id 0 lun808529923 has a LUN larger than allowed by the host adapter (scsi3:A:0:4): Handled Residual of 4 bytes (scsi3:A:0:5): Handled Residual of 4 bytes scsi: host 3 channel 0 id 0 lun3078 has a LUN larger than allowed by the host adapter (scsi3:A:0:7): Handled Residual of 4 bytes (scsi3:A:0:8): Handled Residual of 4 bytes (scsi3:A:0:9): Handled Residual of 4 bytes (scsi3:A:0:10): Handled Residual of 4 bytes (scsi3:A:0:11): Handled Residual of 4 bytes (scsi3:A:0:12): Handled Residual of 4 bytes (scsi3:A:0:13): Handled Residual of 4 bytes (scsi3:A:0:14): Handled Residual of 4 bytes (scsi3:A:0:15): Handled Residual of 4 bytes (scsi3:A:1:0): Saw Selection Timeout for SCB 0x3 (scsi3:A:2:0): Saw Selection Timeout for SCB 0x2 (scsi3:A:3:0): Saw Selection Timeout for SCB 0x3 (scsi3:A:4:0): Saw Selection Timeout for SCB 0x2 (scsi3:A:5:0): Saw Selection Timeout for SCB 0x3 (scsi3:A:6:0): Saw Selection Timeout for SCB 0x2 (scsi3:A:8:0): Saw Selection Timeout for SCB 0x3 (scsi3:A:9:0): Saw Selection Timeout for SCB 0x2 (scsi3:A:10:0): Saw Selection Timeout for SCB 0x3 (scsi3:A:11:0): Saw Selection Timeout for SCB 0x2 (scsi3:A:12:0): Saw Selection Timeout for SCB 0x3 (scsi3:A:13:0): Saw Selection Timeout for SCB 0x2 (scsi3:A:14:0): Saw Selection Timeout for SCB 0x3 (scsi3:A:15:0): Saw Selection Timeout for SCB 0x2 $ cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: SAMSUNG SP0812C Rev: SU10 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: SAMSUNG SP0812C Rev: SU10 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: BROWNIE Model: 1600U3P Rev: 0001 Type: Direct-Access ANSI SCSI revision: 03 Host: scsi3 Channel: 00 Id: 00 Lun: 00 Vendor: BROWNIE Model: 1600U3P Rev: 0001 Type: Direct-Access ANSI SCSI revision: 03 # /sbin/lspci -vvv 00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 0a) Subsystem: Intel Corp.: Unknown device 343f Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort->SERR- <PERR- Latency: 0 Capabilities: [40] #09 [d105] 00:00.1 Class ff00: Intel Corp. Memory Controller Hub Error Reporting Register (rev 0a) Subsystem: Intel Corp.: Unknown device 343f Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort->SERR- <PERR- 00:02.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A0 (rev 0a) (prog-if 00 [Normal decode]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort->SERR- <PERR- Latency: 0, cache line size 10 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000f000-00000fff Memory behind bridge: fff00000-000fffff Prefetchable memory behind bridge: 00000000fff00000-0000000000000000 BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B- Capabilities: [50] 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: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable- Address: fee00000 Data: 0000 Capabilities: [64] #10 [0041] 00:03.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A1 (rev 0a) (prog-if 00 [Normal decode]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort->SERR- <PERR- Latency: 0, cache line size 10 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 0000f000-00000fff Memory behind bridge: fff00000-000fffff Prefetchable memory behind bridge: 00000000fff00000-0000000000000000 BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B- Capabilities: [50] 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: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable- Address: fee00000 Data: 0000 Capabilities: [64] #10 [0041] 00:1c.0 PCI bridge: Intel Corp. Enterprise Southbridge Hublink PCI-X Bridge (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort->SERR- <PERR- Latency: 64, cache line size 10 Bus: primary=00, secondary=03, subordinate=03, sec-latency=48 I/O behind bridge: 0000d000-0000dfff Memory behind bridge: fae00000-faefffff Prefetchable memory behind bridge: 00000000fff00000-0000000000000000 BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B- Capabilities: [50] PCI-X bridge device. Secondary Status: 64bit+, 133MHz-, SCD-, USC-, SCO-, SRD- Freq=0 Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, SCO-, SRD- : Upstream: Capacity=0, Commitment Limit=0 : Downstream: Capacity=0, Commitment Limit=0 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev 0a)(prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort->SERR- <PERR- Latency: 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=32 I/O behind bridge: 0000e000-0000efff Memory behind bridge: faf00000-fbffffff Prefetchable memory behind bridge: fff00000-000fffff BridgeCtl: Parity+ SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B- 00:1f.0 ISA bridge: Intel Corp. Enterprise Southbridge ISA Bridge (rev 02) 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 00:1f.1 IDE interface: Intel Corp. Enterprise Southbridge PATA (rev 02) (prog-if 8a [Master SecP PriP]) Subsystem: Intel Corp.: Unknown device 343f 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 Interrupt: pin A routed to IRQ 18 Region 0: I/O ports at <unassigned> Region 1: I/O ports at <unassigned> Region 2: I/O ports at <unassigned> Region 3: I/O ports at <unassigned> Region 4: I/O ports at fc00 [size=16] Region 5: Memory at 80000000 (32-bit, non-prefetchable) [size=1K] 00:1f.2 IDE interface: Intel Corp. Enterprise Southbridge SATA cc=IDE (rev 02) (prog-if 8f [Master SecP SecO PriP PriO]) Subsystem: Intel Corp.: Unknown device 343f 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 Interrupt: pin A routed to IRQ 18 Region 0: I/O ports at cc00 [size=8] Region 1: I/O ports at c880 [size=4] Region 2: I/O ports at c800 [size=8] Region 3: I/O ports at c480 [size=4] Region 4: I/O ports at c400 [size=16] 00:1f.3 SMBus: Intel Corp. Enterprise Southbridge SMBUS (rev 02) Subsystem: Intel Corp.: Unknown device 343f 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- Interrupt: pin B routed to IRQ 11 Region 4: I/O ports at 0400 [size=32] 03:03.0 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m Subsystem: Adaptec AHA-3960D U160/m 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: 64 (10000ns min, 6250ns max), cache line size 10 Interrupt: pin A routed to IRQ 25 BIST result: 00 Region 0: I/O ports at d400 [disabled] [size=256] Region 1: Memory at faefe000 (64-bit, non-prefetchable) [size=4K] Expansion ROM at faea0000 [disabled] [size=128K] 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- 03:03.1 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m Subsystem: Adaptec AHA-3960D U160/m 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: 64 (10000ns min, 6250ns max), cache line size 10 Interrupt: pin B routed to IRQ 26 BIST result: 00 Region 0: I/O ports at d800 [disabled] [size=256] Region 1: Memory at faeff000 (64-bit, non-prefetchable) [size=4K] Expansion ROM at faec0000 [disabled] [size=128K] 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- 04:02.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA]) Subsystem: Intel Corp.: Unknown device 343f 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: 64 (2000ns min), cache line size 10 Interrupt: pin A routed to IRQ 11 Region 0: Memory at fb000000 (32-bit, non-prefetchable) [size=16M] Region 1: I/O ports at e800 [size=256] Region 2: Memory at fafff000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at fafc0000 [disabled] [size=128K] Capabilities: [5c] 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- 04:03.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) Subsystem: Intel Corp.: Unknown device 343f 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: 64 (63750ns min), cache line size 10 Interrupt: pin A routed to IRQ 16 Region 0: Memory at fafa0000 (32-bit, non-prefetchable) [size=128K] Region 2: I/O ports at ec00 [size=64] 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=1 PME- Capabilities: [e4] PCI-X non-bridge device. Command: DPERE- ERO+ RBC=0 OST=0 Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM- dmesg from 2.4.31: PCI: Enabling device 03:03.1 (0156 -> 0157) PCI: Enabling device 03:03.0 (0156 -> 0157) scsi2 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 <Adaptec 3960D Ultra160 SCSI adapter> aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs scsi3 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 <Adaptec 3960D Ultra160 SCSI adapter> aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs scsi3:A:0:0: DV failed to configure device. Please file a bug report against this driver. scsi2:A:1:0: DV failed to configure device. Please file a bug report against this driver. (scsi2:A:1): 160.000MB/s transfers (80.000MHz DT, offset 31, 16bit) Vendor: BROWNIE Model: 1600U3P Rev: 0001 Type: Direct-Access ANSI SCSI revision: 03 Vendor: BROWNIE Model: 1600U3P Rev: 0001 Type: Direct-Access ANSI SCSI revision: 03 scsi2:A:1:0: Tagged Queuing enabled. Depth 32 scsi2:A:1:1: Tagged Queuing enabled. Depth 32 (scsi3:A:0): 160.000MB/s transfers (80.000MHz DT, offset 31, 16bit) Vendor: BROWNIE Model: 1600U3P Rev: 0001 Type: Direct-Access ANSI SCSI revision: 03 scsi3:A:0:0: Tagged Queuing enabled. Depth 32 Attached scsi disk sdc at scsi2, channel 0, id 1, lun 0 Attached scsi disk sdd at scsi2, channel 0, id 1, lun 1 Attached scsi disk sde at scsi3, channel 0, id 0, lun 0 SCSI device sdc: 2788016128 512-byte hdwr sectors (1427464 MB) sdc: sdc1 sdc2 sdc3 sdc4 SCSI device sdd: 2389721088 512-byte hdwr sectors (1223537 MB) sdd: sdd1 sdd2 SCSI device sde: 4294950912 512-byte hdwr sectors (2199015 MB) sde: sde1 Steps to reproduce: only with Adaptec3960D card, BROWNIE-1600U3P and kernel version 2.6.x and
Well there's been a bit of activity with that driver recently. Could you please test 2.6.13-rc4 and if that also fails, test 2.6.13-rc3-mm3? Thanks.
Let's see if this email thingy works. James Bottomley <James.Bottomley@SteelEye.com> wrote: > > On Sat, 2005-07-23 at 19:51 +0100, Christoph Hellwig wrote: > > This message is totally useless. If you want to forward bugzilla reports > > please include all relevant information. > > OK, let me try. > > The format I'd like is for the text of the bug report to go over the > list with a cc to the bugzilla so that it captures any email > conversation about it. Martin has already set this up, I just can't > figure out what the bugzilla email address is for this report. > > Anyway, this is what looks to be the issue in the trace > > > target2:0:1: Ending Domain Validation > > SCSI device sdc: 2788016128 512-byte hdwr sectors (1427464 MB) > > (scsi2:A:1:0): Handled Residual of 4 bytes > > SCSI device sdc: drive cache: write back > > SCSI device sdc: 2788016128 512-byte hdwr sectors (1427464 MB) > > (scsi2:A:1:0): Handled Residual of 4 bytes > > SCSI device sdc: drive cache: write back > > sdc: sdc1 sdc2 sdc3 sdc4 > > Attached scsi disk sdc at scsi2, channel 0, id 1, lun 0 > > (scsi2:A:1:0): Handled Residual of 3960 bytes > > scsi: host 2 channel 0 id 1 lun 0x00000200080c0400 has a LUN larger than > > currently supported. > > scsi: host 2 channel 0 id 1 lun 0xff010000ffffffff has a LUN larger than > > currently supported. > > scsi: host 2 channel 0 id 1 lun 0x0002202020202020 has a LUN larger than > > currently supported. > > scsi: host 2 channel 0 id 1 lun808529923 has a LUN larger than allowed by the > > host adapter > > (scsi2:A:1:4): Handled Residual of 4 bytes > > (scsi2:A:1:5): Handled Residual of 4 bytes > > scsi: host 2 channel 0 id 1 lun3078 has a LUN larger than allowed by the host > > adapter > > So I think it's not an aic7xxx error (it seems the new DV actually works > whereas the old DV failed). It seems to be a bug in REPORT LUNS. > Either in the device or in the kernel code. > > The curious thing is why after the report luns failure, we apparently > jump to sequential LUN scanning, but choose to begin at LUN 4. > > I think as a work around, a simple > > echo scsi add-single-device 2 0 1 1 > /proc/scsi/scsi > > should bring the missing LUN back again > > James
>Could you please test 2.6.13-rc4 and >if that also fails, test 2.6.13-rc3-mm3? yes , I found that these problems persist with this patches. > I think as a work around, a simple > echo scsi add-single-device 2 0 1 1 > /proc/scsi/scsi > should bring the missing LUN back again Certainly it works. But it would be desirable to resolve the problem with incorrect scanning LUN at loading the driver. If you need additional information about driver loading process , please email me with any questions.
Reply-To: James.Bottomley@HansenPartnership.com > ------- Additional Comments From duda@matrix.odessa.ua 2005-07-29 09:50 ------- > >Could you please test 2.6.13-rc4 and > >if that also fails, test 2.6.13-rc3-mm3? > yes , I found that these problems persist with this patches. > > > > I think as a work around, a simple > > echo scsi add-single-device 2 0 1 1 > /proc/scsi/scsi > > should bring the missing LUN back again > > Certainly it works. > But it would be desirable to resolve the problem with incorrect scanning LUN at > loading the driver. > > If you need additional information about driver loading process , please email > me with any questions. Well, it can simply be fixed by blacklisting this array for the REPORT LUNS command. However, it would be nice to know what the reason for the problem is. The array claims to support REPORT LUNS but then apparently returns rubbish when the command is sent. The only people who would know definitively what's going on is the manufacturer, can someone get hold of them and ask? Thanks, James
How come 2.4.x works OK? It alse seems to use REPORT_LUNS?
Reply-To: James.Bottomley@SteelEye.com On Wed, 2005-09-14 at 23:48 -0700, bugme-daemon@kernel-bugs.osdl.org wrote: > How come 2.4.x works OK? It alse seems to use REPORT_LUNS? Actually I wasn't aware that someone had backported REPORT_LUNs to 2.4 ... it certainly didn't use to have this. James
Yup, it's there in 2.4.31 and Igor says 2.4.31 runs OK.
Reply-To: James.Bottomley@HansenPartnership.com > Yup, it's there in 2.4.31 and Igor says 2.4.31 runs > OK. Erm, which vendor kernel is this? REPORT LUN scanning definitely isn't in Marcelo's vanilla 2.4 tree. I'd be curious to know how whoever this is managed to massage the bogus report luns information to make sense. James
James Bottomley <James.Bottomley@HansenPartnership.com> wrote: > > > Yup, it's there in 2.4.31 and Igor says 2.4.31 runs > > OK. > > Erm, which vendor kernel is this? REPORT LUN scanning definitely isn't > in Marcelo's vanilla 2.4 tree. I'd be curious to know how whoever this > is managed to massage the bogus report luns information to make sense. > Maybe I'm wrong - I merely grepped the 2.4.31 tree for report_luns.
Is this problem still present in kernel 2.6.19?
Please reopen this bug if it's still present with kernel 2.6.20.