From: Lukas Kolbe <lkolbe@techfak.uni-bielefeld.de>
To: "Desai, Kashyap" <Kashyap.Desai@lsi.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"sfrey@techfak.uni-bielefeld.de" <sfrey@techfak.uni-bielefeld.de>
Subject: RE: Bug 14579 (was: RE: Bug 14579 - Devices disappear... and Bug 14577 - Data corruption with Adaptec)
Date: Thu, 19 Nov 2009 11:48:40 +0100 [thread overview]
Message-ID: <1258627720.8918.33.camel@muchoki.zuhause> (raw)
In-Reply-To: <0D1E8821739E724A86F4D16902CE275C1C93C74C80@inbmail01.lsi.com>
Am Donnerstag, den 19.11.2009, 16:00 +0530 schrieb Desai, Kashyap:
>
> > -----Original Message-----
> > From: Lukas Kolbe [mailto:lkolbe@techfak.uni-bielefeld.de]
> > Sent: Thursday, November 19, 2009 3:48 PM
> > To: Desai, Kashyap
> > Cc: linux-scsi@vger.kernel.org; sfrey@techfak.uni-bielefeld.de
> > Subject: Bug 14579 (was: RE: Bug 14579 - Devices disappear... and Bug
> > 14577 - Data corruption with Adaptec)
> >
> > Am Donnerstag, den 19.11.2009, 10:43 +0530 schrieb Desai, Kashyap:
> > > OK. So I get it now. You are working to solve major issue which is
> > > related to your RAID 60 + Adaptec controller. If you want to upgrade
> > > LSI driver, we can always go for latest driver. I can provide you
> > > latest driver source tar ball. Back porting to 2.6.30 is fine.
> >
> > That would be great, thank you. It seems the Adaptec-problem will still
> > take a while to debug, so if we can get further with the LSI issue it
> > would be much appreciated. It might take a few days of testing after we
> > build 2.6.30 with the new mtpfusion.
> >
> I think, without solving one issue (Adaptec related), I am not in
> position to understand what is an issue w.r.t LSI ? Pls clarify. If
> you can provide me Logs for LSI driver and provide me pointer to look
> inside, I can do something on this.
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.
If you can provide us with the current mptfusion, we can build it for
2.6.30 and test wether the bus reset and/or oops do still happen. If
they don't, you made a few people very happy :)
--
Kind regards,
Lukas
next prev parent reply other threads:[~2009-11-19 10:47 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 [this message]
2009-11-19 10:58 ` Desai, Kashyap
2009-11-19 11:11 ` Bug 14579 Lukas Kolbe
2010-02-03 13:36 ` Bug 14579 (was: RE: Bug 14579 - Devices disappear... and Bug 14577 - Data corruption with Adaptec) 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=1258627720.8918.33.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.