From: Boaz Harrosh <bharrosh@panasas.com>
To: Filippos Papadopoulos <psybases@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: INITIO scsi driver fails to work properly
Date: Mon, 17 Dec 2007 14:18:12 +0200 [thread overview]
Message-ID: <47666904.8060605@panasas.com> (raw)
In-Reply-To: <9f00bd9d0712170341u7fef1fc9pc9986dda1a0475cb@mail.gmail.com>
On Mon, Dec 17 2007 at 13:41 +0200, "Filippos Papadopoulos" <psybases@gmail.com> wrote:
> On Dec 17, 2007 1:18 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
>> On Mon, 17 Dec 2007 11:39:47 +0200 "Filippos Papadopoulos" <psybases@gmail.com> wrote:
>>
>>> Hi,
>>> I have got an INITIO 9100 UW SCSI Controller with an IBM
>>> IC35L036UWD210-0 scsi hard disk on a 32 bit x86 system.
>>> Currently i have SUSE 10.1 (Kernel 2.6.16).
>>>
>>> I tried to install OpenSUSE 10.3 (kernel 2.6.22.5) and the latest
>>> OpenSUSE 11.0 Alpha 0 (kernel 2.6.24-rc4) but although the initio
>>> driver
>>> gets loaded during the installation process, yast reports that no hard
>>> disk is found. I believe that this isnt a bug in suse's yast but a
>>> problem
>>> in the initio scsi driver because i also tried to install Fedora 8
>>> (kernel 2.6.23) with the same problem.
>>> I have seen the relevant thread "Conflict when loading initio driver"
>>> and i suppose that the initio driver isnt fixed yet.
>>> I can help testing the new patches in the initio driver if someone is
>>> interested.
>> initio doesn't seem to have a maintainer...
>>
>> Are you able to identify any earlier kernel which worked OK?
>>
>
> I have this PC configuration since 2002. The initio driver worked
> perfectly with 2.4 kernel series.
> With the release of 2.6 kernel series the driver had been marked as
> BROKEN and fixed at 2.6.9
> (see at http://www.gossamer-threads.com/lists/linux/kernel/482582?search_string=SCSI%20updates%20for%202.6.9;#482582
> Christoph Hellwig ->don't mark the initio 9100 driver broken)
>
>
>> Maybe it's a new device? If you can get the `lspci -vvxx' output
>> for that device we can take a look.
>>
>
> No its not a new device.
> -
I have found one problem. Please try patch [2] below and report.
If it still fails try to enable debugging by setting with patch [1]
these values at top of drivers/scsi/initio.c. And send dmsgs.
Boaz
--------
patch [1]
--------
diff --git a/drivers/scsi/initio.c b/drivers/scsi/initio.c
index 4c4465d..61edcd2 100644
--- a/drivers/scsi/initio.c
+++ b/drivers/scsi/initio.c
@@ -138,10 +138,10 @@ static struct pci_device_id i91u_pci_devices[] = {
};
MODULE_DEVICE_TABLE(pci, i91u_pci_devices);
-#define DEBUG_INTERRUPT 0
-#define DEBUG_QUEUE 0
-#define DEBUG_STATE 0
-#define INT_DISC 0
+#define DEBUG_INTERRUPT 1
+#define DEBUG_QUEUE 1
+#define DEBUG_STATE 1
+#define INT_DISC 1
/*--- forward references ---*/
static struct scsi_ctrl_blk *initio_find_busy_scb(struct initio_host * host, u16 tarlun);
-----------
patch [2]
-----------
git-diff --stat -p
drivers/scsi/initio.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/initio.c b/drivers/scsi/initio.c
index 4c4465d..61595f6 100644
--- a/drivers/scsi/initio.c
+++ b/drivers/scsi/initio.c
@@ -2616,6 +2616,7 @@ static void initio_build_scb(struct initio_host * host, struct scsi_ctrl_blk * c
scsi_for_each_sg(cmnd, sglist, cblk->sglen, i) {
sg->data = cpu_to_le32((u32)sg_dma_address(sglist));
total_len += sg->len = cpu_to_le32((u32)sg_dma_len(sglist));
+ sg++;
}
cblk->buflen = (scsi_bufflen(cmnd) > total_len) ?
next prev parent reply other threads:[~2007-12-17 12:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 9:39 INITIO scsi driver fails to work properly Filippos Papadopoulos
2007-12-17 11:18 ` Andrew Morton
2007-12-17 11:41 ` Filippos Papadopoulos
2007-12-17 12:18 ` Boaz Harrosh [this message]
2007-12-17 12:24 ` Boaz Harrosh
2007-12-19 8:48 ` Filippos Papadopoulos
2007-12-19 10:08 ` Boaz Harrosh
2007-12-19 13:29 ` Matthew Wilcox
2007-12-19 16:50 ` James Bottomley
2007-12-19 17:05 ` Matthew Wilcox
2007-12-20 9:32 ` Natalie Protasevich
2007-12-20 15:08 ` James Bottomley
2007-12-20 15:14 ` Theodore Tso
2007-12-21 19:30 ` Chuck Ebbert
2007-12-21 21:03 ` James Bottomley
2007-12-21 22:43 ` Chuck Ebbert
2007-12-21 22:49 ` James Bottomley
2008-01-04 0:18 ` Filippos Papadopoulos
2008-01-11 5:16 ` James Bottomley
2008-01-11 9:54 ` Filippos Papadopoulos
2008-01-11 15:44 ` James Bottomley
2008-01-11 16:44 ` Filippos Papadopoulos
2008-01-11 17:01 ` Alan Cox
2008-01-11 17:33 ` James Bottomley
2008-01-11 17:01 ` James Bottomley
2008-01-13 12:28 ` Filippos Papadopoulos
2008-01-15 15:16 ` James Bottomley
2008-01-16 5:59 ` FUJITA Tomonori
2008-01-16 14:57 ` James Bottomley
2008-01-21 22:20 ` Alan Cox
2008-01-22 17:50 ` Filippos Papadopoulos
2008-01-25 16:49 ` James Bottomley
2008-01-25 21:04 ` Filippos Papadopoulos
2008-01-11 17:52 ` Chuck Ebbert
2007-12-17 13:05 ` Alan Cox
2007-12-17 14:40 ` Boaz Harrosh
2007-12-17 14:36 ` Alan Cox
2007-12-17 15:03 ` James Bottomley
2007-12-17 16:08 ` Boaz Harrosh
2007-12-17 16:20 ` Olivier Galibert
2007-12-17 17:00 ` Boaz Harrosh
2007-12-17 16:13 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47666904.8060605@panasas.com \
--to=bharrosh@panasas.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=psybases@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).