From: Olaf Hering <olh@suse.de>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [Announce] Emulex lpfcdriver v8.0.12 available
Date: Sat, 2 Oct 2004 21:36:31 +0200 [thread overview]
Message-ID: <20041002193631.GA4394@suse.de> (raw)
In-Reply-To: <0B1E13B586976742A7599D71A6AC733C08664E@xbl3.ma.emulex.com>
On Sat, Oct 02, James.Smart@Emulex.Com wrote:
>
>
> > I tried it on a legacy iseries partition, there where a few
> > warnings/errors in dmesg. the box has no storage attached. Does that
> > indicate a driver problem, or is it just the not-attached storage?
>
> Depends on the errors - please send the the dmesg log.
It was attached.
> > curry:~ # rmmod lpfc
> > Kernel panic - not syncing: PCI: Hardware I/O Error, SRC
> > B6000103, Automatic Reboot Disabled.
> >
> > this is 2.6.9-rc3-bk2, + bk-scsi-target.patch and bk-scsi.patch with
> > arch/ppc64/configs/iseriesconfig.
>
> We don't know of any issues like this. I'll look more at the logs you send and perhaps it'll give a hint...
It worked with the second try, but a few modprobe/rmmod cycles caused
the same crash. Could be something in the iseries arch code.
I cant really help with that sort of crash.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2004-10-02 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0B1E13B586976742A7599D71A6AC733C08664E@xbl3.ma.emulex.com>
2004-10-02 19:36 ` Olaf Hering [this message]
2004-10-18 21:34 [Announce] Emulex lpfcdriver v8.0.12 available James.Smart
-- strict thread matches above, loose matches on Subject: below --
2004-10-16 21:50 James.Smart
2004-10-18 20:55 ` Christoph Hellwig
2004-09-21 17:07 James.Smart
2004-09-21 1:34 James.Smart
2004-09-21 12:40 ` Christoph Hellwig
2004-09-21 12:41 ` Christoph Hellwig
2004-09-21 16:56 ` Christoph Hellwig
2004-10-02 16:38 ` Olaf Hering
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=20041002193631.GA4394@suse.de \
--to=olh@suse.de \
--cc=James.Smart@Emulex.Com \
--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;
as well as URLs for NNTP newsgroup(s).