From: Olaf Hering <olh@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: James Smart <James.Smart@Emulex.Com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 0/22] lpfc 8.1.2 driver update, crash in lpfc_worker_0
Date: Sun, 12 Feb 2006 16:26:31 +0100 [thread overview]
Message-ID: <20060212152631.GA24631@suse.de> (raw)
In-Reply-To: <1139757616.3808.4.camel@mulgrave.il.steeleye.com>
On Sun, Feb 12, James Bottomley wrote:
> Could you try to produce this on a non-ppc machine?
Yes, its an older pSeries, pre-POWER4. So far it did not reproduce on
this system after 3 reboots.
--
short story of a lazy sysadmin:
alias appserv=wotan
next prev parent reply other threads:[~2006-02-12 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 15:40 [PATCH 0/22] lpfc 8.1.2 driver update James Smart
2006-02-12 14:57 ` [PATCH 0/22] lpfc 8.1.2 driver update, crash in lpfc_worker_0 Olaf Hering
2006-02-12 15:20 ` James Bottomley
2006-02-12 15:26 ` Olaf Hering [this message]
2006-02-28 5:14 ` [PATCH 0/22] lpfc 8.1.2 driver update James Bottomley
2006-03-01 0:00 ` Jamie Wellnitz
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=20060212152631.GA24631@suse.de \
--to=olh@suse.de \
--cc=James.Bottomley@SteelEye.com \
--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).