From: "Filippos Papadopoulos" <psybases@gmail.com>
To: "James Bottomley" <James.Bottomley@hansenpartnership.com>
Cc: linux-scsi@vger.kernel.org, "Chuck Ebbert" <cebbert@redhat.com>,
"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 18:44:23 +0200 [thread overview]
Message-ID: <9f00bd9d0801110844g176acdcdle0331783f82ed866@mail.gmail.com> (raw)
In-Reply-To: <1200066295.3286.19.camel@localhost.localdomain>
On Jan 11, 2008 5:44 PM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
> >
> > 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.
>
> > I applied the patch on 2.6.24-rc6-git9 but unfortunatelly same thing happens.
>
> First off, has this driver ever worked for you in 2.6? Just booting
> SLES9 (2.6.5) or RHEL4 (2.6.9) ... or one of their open equivalents to
> check a really old kernel would be helpful. If you can get it to work,
> then we can proceed with a patch reversion regime based on the
> assumption that the problem is a recent commit.
Yes it works under 2.6.16.13. See the beginning of this thread, i
mention there some things about newer versions.
>
> Thanks,
>
> James
>
>
>
next prev parent reply other threads:[~2008-01-11 16:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 9:39 Filippos Papadopoulos
2007-12-17 11:18 ` 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 [this message]
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=9f00bd9d0801110844g176acdcdle0331783f82ed866@mail.gmail.com \
--to=psybases@gmail.com \
--cc=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 \
/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
all inboxes | Powered by JetHome®