linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 14831] mptsas - Use of ATA command pass-through results in unreliable operation - drive / controller resets
Date: Tue, 8 Jun 2010 06:44:53 GMT	[thread overview]
Message-ID: <201006080644.o586irFD023836@demeter.kernel.org> (raw)
In-Reply-To: <bug-14831-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=14831





--- Comment #29 from Tim Small <tim@seoss.co.uk>  2010-06-08 06:44:45 ---
(In reply to comment #28)

> linux 2.6.32 and the LSI official driver 4.22.00.00:

The official Linux driver seems to be 3.04.15 -

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/message/fusion/mptbase.h;hb=HEAD#l69

so my understanding is that you should probably be testing with this driver,
rather than the 4.x LSI driver which hasn't made it into the Linux tree (yet). 
The 4.x driver might be useful for providing additional data points.

Some official word from LSI on this would be useful.

Thanks,

Tim.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2010-06-08  6:44 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-14831-11613@https.bugzilla.kernel.org/>
2010-03-21 11:34 ` [Bug 14831] mptsas - Use of ATA command pass-through results in unreliable operation - drive / controller resets bugzilla-daemon
2010-03-30 14:53 ` bugzilla-daemon
2010-04-29  7:25 ` bugzilla-daemon
2010-04-29  9:27 ` bugzilla-daemon
2010-05-03 22:22 ` bugzilla-daemon
2010-05-04  5:16 ` bugzilla-daemon
2010-05-04  9:16 ` bugzilla-daemon
2010-05-05 10:35 ` bugzilla-daemon
2010-05-07  4:56 ` bugzilla-daemon
2010-05-07  8:01 ` bugzilla-daemon
2010-05-12  8:50 ` bugzilla-daemon
2010-05-12  9:04 ` bugzilla-daemon
2010-05-12  9:33 ` bugzilla-daemon
2010-05-12 10:22 ` bugzilla-daemon
2010-05-24  9:05 ` bugzilla-daemon
2010-05-26  8:08 ` bugzilla-daemon
2010-06-07 20:00 ` bugzilla-daemon
2010-06-08  0:29 ` bugzilla-daemon
2010-06-08  6:44 ` bugzilla-daemon [this message]
2010-06-08  8:43 ` bugzilla-daemon
2010-06-29 20:26 ` bugzilla-daemon
2010-08-28 15:44 ` bugzilla-daemon
2010-08-28 15:45 ` bugzilla-daemon
2010-08-28 15:46 ` bugzilla-daemon
2010-08-28 15:47 ` bugzilla-daemon
2010-08-28 15:51 ` bugzilla-daemon
2010-08-28 15:53 ` bugzilla-daemon
2010-08-30 15:18 ` bugzilla-daemon
2010-08-30 16:42 ` bugzilla-daemon
2010-08-31  8:17 ` bugzilla-daemon
2010-09-28 19:07 ` bugzilla-daemon
2012-06-18 13:20 ` bugzilla-daemon
2012-06-18 13:20 ` bugzilla-daemon
2009-12-18 11:25 [Bug 14831] New: " bugzilla-daemon
2009-12-18 12:44 ` [Bug 14831] " bugzilla-daemon
2009-12-18 15:18 ` bugzilla-daemon
2009-12-18 15:31 ` bugzilla-daemon
2009-12-18 15:32 ` bugzilla-daemon
2009-12-21  4:51 ` bugzilla-daemon
2009-12-21  4:52 ` bugzilla-daemon
2009-12-21 12:08 ` bugzilla-daemon
2009-12-21 12:11 ` bugzilla-daemon
2010-01-11 11:59 ` bugzilla-daemon
2010-01-12 23:15 ` bugzilla-daemon
2010-01-13 12:30 ` bugzilla-daemon

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=201006080644.o586irFD023836@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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).