public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Filippos Papadopoulos <psybases@gmail.com>,
	Boaz Harrosh <bharrosh@panasas.com>,
	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: Fri, 21 Dec 2007 16:49:51 -0600	[thread overview]
Message-ID: <1198277391.3130.73.camel@localhost.localdomain> (raw)
In-Reply-To: <476C4177.3030902@redhat.com>


On Fri, 2007-12-21 at 17:43 -0500, Chuck Ebbert wrote:
> On 12/21/2007 04:03 PM, James Bottomley wrote:
> > On Fri, 2007-12-21 at 14:30 -0500, Chuck Ebbert wrote:
> >> On 12/19/2007 03:48 AM, Filippos Papadopoulos wrote:
> >>> On Dec 17, 2007 2:18 PM, Boaz Harrosh <bharrosh@panasas.com> wrote:
> >>>> 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
> >>>>
> >>>
> >>> I tried patch[2] (addition of   sg++)  at 2.6.24-rc5-mm1 but the
> >>> system hangs after some seconds when the initio driver loads.
> >>> I will try patch[1] next week to see what happens.
> >>>
> >>> Would it be better to open a bug report at bugzilla?
> >>>
> >> There is also a Fedora bug report against 2.6.23. The user has
> >> applied commit e9e42faf47255274a1ed0b9bf1c46118023ec5fa from
> >> 2.6.24-rc plus the two additional fixes under discussion and it
> >> hangs for him too.
> >>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=390531
> > 
> > It really sounds like there's some problem applying the patches.  The
> > consistent report throughout is this one:
> > 
> > initio: I/O port range 0x0 is busy.
> > 
> > Which should be fixed by 99f1f534922a2f2251ba05b14657a1c62882a80e.  I
> > didn't actually find that in the bug thread anywhere, but maybe I missed
> > it?
> > 
> 
> The "I/O port 0" bug just prints the message and the system continues
> to run. It's only after that is fixed that the system just hangs on
> boot shortly after loading the driver.

That should happen unless the PCI BAR is genuinely misconfigured; it's
saying we got zero when we requested the starting address of BAR0.  What
does lspci -vv show for this device?

James



  reply	other threads:[~2007-12-21 22:50 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9f00bd9d0712170139q1397af5fp3c855a2b94726227@mail.gmail.com>
2007-12-17 11:18 ` INITIO scsi driver fails to work properly Andrew Morton
2007-12-17 11:41   ` Filippos Papadopoulos
2007-12-17 12:18     ` Boaz Harrosh
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 [this message]
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
2008-01-11 18:21                           ` Alan Cox
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=1198277391.3130.73.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=bharrosh@panasas.com \
    --cc=cebbert@redhat.com \
    --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