From: "David S. Miller" <davem@redhat.com>
To: cary_dickens2@hp.com
Cc: axboe@suse.de, linux-kernel@vger.kernel.org, erik_habbinga@hp.com
Subject: Re: Problem with 2.4.14prex and qlogicfc
Date: Wed, 17 Oct 2001 12:29:29 -0700 (PDT) [thread overview]
Message-ID: <20011017.122929.63130945.davem@redhat.com> (raw)
In-Reply-To: <C5C45572D968D411A1B500D0B74FF4A80418D573@xfc01.fc.hp.com>
In-Reply-To: <C5C45572D968D411A1B500D0B74FF4A80418D573@xfc01.fc.hp.com>
From: "DICKENS,CARY (HP-Loveland,ex2)" <cary_dickens2@hp.com>
Date: Wed, 17 Oct 2001 15:16:03 -0400
I've done that and the problem is still there. It no longer gives me the
perpetual link is up message when trying to mount storage on the fibre
channel disks. Now it just stops. I booted without any of the fibre
storage being mounted and ran an fdisk on the storage in question. The
response from the ps -eo cmd,wchan is:
fdisk /dev/sdc lock_page
Ok, and to reiterate this is on an x86 system with HIGHMEM enabled?
Also, just to confirm, you have _not_ applied Jen's block highmem
patches on top of this 2.4.13-preX tree right? It is just a vanilla
2.4.13-preX tree?
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-10-17 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 19:16 Problem with 2.4.14prex and qlogicfc DICKENS,CARY (HP-Loveland,ex2)
2001-10-17 19:29 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-18 23:50 DICKENS,CARY (HP-Loveland,ex2)
2001-10-17 20:07 DICKENS,CARY (HP-Loveland,ex2)
2001-10-18 12:25 ` David S. Miller
2001-10-17 16:01 DICKENS,CARY (HP-Loveland,ex2)
2001-10-17 16:52 ` David S. Miller
2001-10-16 21:23 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
2001-10-17 16:22 ` Arjan van de Ven
2001-10-17 16:48 ` David S. Miller
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=20011017.122929.63130945.davem@redhat.com \
--to=davem@redhat.com \
--cc=axboe@suse.de \
--cc=cary_dickens2@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox