From: Lukas Kolbe <lkolbe@techfak.uni-bielefeld.de>
To: "Desai, Kashyap" <Kashyap.Desai@lsi.com>
Cc: linux-scsi@vger.kernel.org, sfrey@techfak.uni-bielefeld.de
Subject: RE: Bug 14579
Date: Thu, 19 Nov 2009 12:11:52 +0100 [thread overview]
Message-ID: <1258629112.8918.45.camel@muchoki.zuhause> (raw)
In-Reply-To: <0D1E8821739E724A86F4D16902CE275C1C93C74C97@inbmail01.lsi.com>
Am Donnerstag, den 19.11.2009, 16:28 +0530 schrieb Desai, Kashyap:
> > It's all in Bug #14579, see
> > http://bugzilla.kernel.org/show_bug.cgi?id=14579
> >
> > Basically, after a while writing to the tape drive that is attached to
> > the LSI controller, the bus either resets itself without finding the
> > tape drives again, or we get an oops and the system crashes. This is a
> > seperate problem from the one we have with the Adaptec RAID on 2.6.32,
> > that is the reason why we opened two bugs.
> >
> Looking at oops message attached to bug14579, I am still unable to map
> anything which might be related to LSI driver, in sort I am not
> getting any pointers related to fusion driver from OOPS message .
> Better way to provide Oops will be console redirect.
Okay, now I see why you don't see it being LSI related. The problem
appears only ever when writing to a tape (regardless of which one of the
two tape drives we use) or sending commands to the tape robot (all
devices are connected to the LSI controller) and is reproducible, that's
the reason we deducted it has something to do with the LSI driver or
linux scsi subsystem.
Solaris seemed to have worked fine, but that's a route we're unwilling
to go at the moment. Unfortunatly, we don't have another HBA for testing
to verify this.
Thanks for the sources, we'll build and test it. You can expect to hear
from us again early next week. We'll also try to capture the full
console output next time.
--
Kind regards,
Lukas Kolbe
next prev parent reply other threads:[~2009-11-19 11:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 16:02 Bug 14579 - Devices disappear... and Bug 14577 - Data corruption with Adaptec Lukas Kolbe
2009-11-12 22:58 ` Sascha Frey
2009-11-13 11:59 ` Desai, Kashyap
2009-11-17 14:22 ` Lukas Kolbe
2009-11-18 4:54 ` Desai, Kashyap
2009-11-18 13:39 ` Lukas Kolbe
2009-11-19 5:13 ` Desai, Kashyap
2009-11-19 10:17 ` Bug 14579 (was: RE: Bug 14579 - Devices disappear... and Bug 14577 - Data corruption with Adaptec) Lukas Kolbe
2009-11-19 10:30 ` Desai, Kashyap
2009-11-19 10:48 ` Lukas Kolbe
2009-11-19 10:58 ` Desai, Kashyap
2009-11-19 11:11 ` Lukas Kolbe [this message]
2010-02-03 13:36 ` Lukas Kolbe
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=1258629112.8918.45.camel@muchoki.zuhause \
--to=lkolbe@techfak.uni-bielefeld.de \
--cc=Kashyap.Desai@lsi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sfrey@techfak.uni-bielefeld.de \
/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.