imm module issues
Hi,
I've compiled the 2.6.20.2 kernel today (I took the SuSE HEAD kernel instead of the vanilla one) and I'm having issues with the "imm" module. I still use a ZIP drive here for small backups and the "imm" module worked flawless on kernel 2.6.18.8 but with kernel 2.6.20.2 I get error messages that the device is offline even if the device is switched on and has a ZIP disk inside of it.
This is what I get from "dmesg" (Sorry for posting this here if it's the wrong place, but I wasn't sure if I should report this to Novell's bugzilla because I'm using the SuSE head kernel which is not officially supported)
imm: Version 2.05 (for Linux 2.4.0)
imm: Found device at ID 6, Attempting to use EPP 32 bit
imm: Communication established at 0x378 with ID 6 using EPP 32 bit scsi1 : Iomega VPI2 (imm) interface
scsi 1:0:6:0: Direct-Access IOMEGA ZIP 250 L.58 PQ: 0 ANSI: 2
sd 1:0:6:0: scsi: Device offlined - not ready after error recovery sd 1:0:6:0: rejecting I/O to offline device
sd 1:0:6:0: rejecting I/O to offline device
sd 1:0:6:0: rejecting I/O to offline device
sd 1:0:6:0: rejecting I/O to offline device
sda : READ CAPACITY failed.
sda : status=0, message=00, host=1, driver=00
sda : sense not available.
sd 1:0:6:0: rejecting I/O to offline device
sda: Write Protect is off
sda: Mode Sense: 00 00 00 00
sd 1:0:6:0: rejecting I/O to offline device
sda: asking for cache data failed
sda: assuming drive cache: write through
sd 1:0:6:0: Attached scsi removable disk sda
sd 1:0:6:0: Attached scsi generic sg0 type 0
Signature · 1 line
go openSUSE go!
[moving from lkml to linux-scsi]
Quoted 7 lines · On Sat, 10 Mar 2007 16:00:28 +0100 Grozdan Nikolov wrote:
Hi,
I've compiled the 2.6.20.2 kernel today (I took the SuSE HEAD kernel instead of the vanilla one) and I'm having issues with the "imm" module. I still use a ZIP drive here for small backups and the "imm" module worked flawless on kernel 2.6.18.8 but with kernel 2.6.20.2 I get error messages that the device is offline even if the device is switched on and has a ZIP disk inside of it.
Has there been any progress on this?
If not, can you narrow the regression down to a specific kernel version?
Quoted 17 lines
This is what I get from "dmesg" (Sorry for posting this here if it's the wrong place, but I wasn't sure if I should report this to Novell's bugzilla because I'm using the SuSE head kernel which is not officially supported)
imm: Version 2.05 (for Linux 2.4.0)
imm: Found device at ID 6, Attempting to use EPP 32 bit
imm: Communication established at0x378with ID 6 using EPP 32 bit scsi1 : Iomega VPI2 (imm) interface
scsi 1:0:6:0: Direct-Access IOMEGA ZIP 250 L.58 PQ: 0 ANSI: 2
sd 1:0:6:0: scsi: Device offlined - not ready after error recovery sd 1:0:6:0: rejecting I/O to offline device
sd 1:0:6:0: rejecting I/O to offline device
sd 1:0:6:0: rejecting I/O to offline device
sd 1:0:6:0: rejecting I/O to offline device
sda : READ CAPACITY failed.
sda : status=0, message=00, host=1, driver=00
sda : sense not available.
Quoted 11 lines
sd 1:0:6:0: rejecting I/O to offline device
sda: Write Protect is off
sda: Mode Sense: 00 00 00 00
sd 1:0:6:0: rejecting I/O to offline device
sda: asking for cache data failed
sda: assuming drive cache: write through
sd 1:0:6:0: Attached scsi removable disk sda
sd 1:0:6:0: Attached scsi generic sg0 type 0Signature · 2 lines
go openSUSE go! -
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
Quoted 12 lines · On Fri, 6 Apr 2007 22:34:33 -0700 Randy Dunlap wrote:
[moving from lkml to linux-scsi]
Quoted 7 lines · On Sat, 10 Mar 2007 16:00:28 +0100 Grozdan Nikolov wrote:
Hi,
I've compiled the 2.6.20.2 kernel today (I took the SuSE HEAD kernel instead of the vanilla one) and I'm having issues with the "imm" module. I still use a ZIP drive here for small backups and the "imm" module worked flawless on kernel 2.6.18.8 but with kernel 2.6.20.2 I get error messages that the device is offline even if the device is switched on and has a ZIP disk inside of it.
Quoted 3 lines
Has there been any progress on this?
If not, can you narrow the regression down to a specific kernel version?
Gordon replied to me: (for archives)
Yes, since I've upgraded to 2.6.21, all is working again. I'm using at the moment 2.6.21-rc5 and all seem fine. Strange that none of the 2.6.20.x kernels I've tried had this problem fixed
Quoted 29 lines
Quoted 17 lines
This is what I get from "dmesg" (Sorry for posting this here if it's the wrong place, but I wasn't sure if I should report this to Novell's bugzilla because I'm using the SuSE head kernel which is not officially supported)
imm: Version 2.05 (for Linux 2.4.0)
imm: Found device at ID 6, Attempting to use EPP 32 bit
imm: Communication established at0x378with ID 6 using EPP 32 bit scsi1 : Iomega VPI2 (imm) interface
scsi 1:0:6:0: Direct-Access IOMEGA ZIP 250 L.58 PQ: 0 ANSI: 2
sd 1:0:6:0: scsi: Device offlined - not ready after error recovery sd 1:0:6:0: rejecting I/O to offline device
sd 1:0:6:0: rejecting I/O to offline device
sd 1:0:6:0: rejecting I/O to offline device
sd 1:0:6:0: rejecting I/O to offline device
sda : READ CAPACITY failed.
sda : status=0, message=00, host=1, driver=00
sda : sense not available.Quoted 11 lines
sd 1:0:6:0: rejecting I/O to offline device
sda: Write Protect is off
sda: Mode Sense: 00 00 00 00
sd 1:0:6:0: rejecting I/O to offline device
sda: asking for cache data failed
sda: assuming drive cache: write through
sd 1:0:6:0: Attached scsi removable disk sda
sd 1:0:6:0: Attached scsi generic sg0 type 0Signature · 2 lines
go openSUSE go! -
Quoted 8 lines
---
~Randy
*** Remember to useDocumentation/SubmitChecklistwhen testing your code *** -
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***