From: Jens Axboe <axboe@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: cary_dickens2@hp.com, linux-kernel@vger.kernel.org, erik_habbinga@hp.com
Subject: Re: Problem with 2.4.14prex and qlogicfc
Date: Wed, 17 Oct 2001 09:04:08 +0200 [thread overview]
Message-ID: <20011017090408.F3035@suse.de> (raw)
In-Reply-To: <C5C45572D968D411A1B500D0B74FF4A80418D570@xfc01.fc.hp.com> <20011017081837.C3035@suse.de> <20011016.233534.48799017.davem@redhat.com>
In-Reply-To: <20011016.233534.48799017.davem@redhat.com>
On Tue, Oct 16 2001, David S. Miller wrote:
> From: Jens Axboe <axboe@suse.de>
> Date: Wed, 17 Oct 2001 08:18:37 +0200
>
> On Tue, Oct 16 2001, DICKENS,CARY (HP-Loveland,ex2) wrote:
> > I'm seeing a problem on all the kernels that are 2.4.13pre1 and up.
>
> This smells like a bug in the pci64 conversion of qlogicfc. Maybe davem
> has an idea, I'll take a look too.
>
> Not if it broke in pre1 since the pci64 stuff went into pre2 :-)
Ah yes, maybe this is my off-by-one or Cary's :-)
He also writes that it broke with 2.4.10 + block-highmem which has the
same PCI changes, so that's why I jumped to that conclusion. Cary, can
you verify that 2.4.13-pre1 _doesn't_ work and that 2.4.12 does?
--
Jens Axboe
next prev parent reply other threads:[~2001-10-17 7:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 21:23 Problem with 2.4.14prex and qlogicfc DICKENS,CARY (HP-Loveland,ex2)
2001-10-17 6:18 ` Jens Axboe
2001-10-17 6:35 ` David S. Miller
2001-10-17 7:04 ` Jens Axboe [this message]
2001-10-17 16:22 ` Arjan van de Ven
2001-10-17 16:48 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2001-10-17 16:01 DICKENS,CARY (HP-Loveland,ex2)
2001-10-17 16:52 ` David S. Miller
2001-10-17 19:16 DICKENS,CARY (HP-Loveland,ex2)
2001-10-17 19:29 ` David S. Miller
2001-10-17 20:07 DICKENS,CARY (HP-Loveland,ex2)
2001-10-18 12:25 ` David S. Miller
2001-10-18 23:50 DICKENS,CARY (HP-Loveland,ex2)
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=20011017090408.F3035@suse.de \
--to=axboe@suse.de \
--cc=cary_dickens2@hp.com \
--cc=davem@redhat.com \
--cc=erik_habbinga@hp.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.