public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Filippos Papadopoulos <psybases@gmail.com>,
	linux-scsi@vger.kernel.org, Boaz Harrosh <bharrosh@panasas.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: INITIO scsi driver fails to work properly
Date: Fri, 11 Jan 2008 12:52:49 -0500	[thread overview]
Message-ID: <4787ACF1.7040501@redhat.com> (raw)
In-Reply-To: <1200066295.3286.19.camel@localhost.localdomain>

On 01/11/2008 10:44 AM, James Bottomley wrote:
>>> This proves the BAR0 to be non zero, but I also take it from your report
>>> that the
>>>
>>> initio: I/O port range 0x0 is busy.
>>>
>>> message is also gone?
>>>
>>
>> I havent reported "initio: I/O port range 0x0 is busy."
> 
> Sorry ... we appear to have several reporters of different bugs in this
> thread.  That message was copied by Chuck Ebbert from a Red Hat
> bugzilla ... I was assuming it was the same problem.
> 

Our reporter has applied patches since then and now reports the exact
same symptoms that Filippos does. (It just hangs after loading the driver.)

  parent reply	other threads:[~2008-01-11 17:53 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
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 [this message]
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=4787ACF1.7040501@redhat.com \
    --to=cebbert@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=bharrosh@panasas.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