All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Adam Talbot <ajtalbot1@gmail.com>
Cc: Nathan Rennie-Waldock <nathan.renniewaldock@gmail.com>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [Bug 81861] Oops by mvsas v0.8.16: sas: ataX: end_device-Y:0:Z: dev error handler -> general protection fault, RIP: mvs_task_prep_ata+0x80/0x3a0
Date: Wed, 29 Apr 2015 11:10:08 -0700	[thread overview]
Message-ID: <1430331008.2189.18.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAH_2GheihL3WE75FrDigEdPzKRK6Up=rvoU10Y2rDMfp0_2q=g@mail.gmail.com>

On Wed, 2015-04-29 at 11:07 -0700, Adam Talbot wrote:
> My system was oopsing, pre patch.  I am happy to give you the full
> configuration. Would that help?

Not really ... the other guy on the thread has a system oopsing post
patch.  It's oopsing in a different place from yours.  That's the system
I need the configuration for.

James



  reply	other threads:[~2015-04-29 18:10 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 17:33 [Bug 81861] New: mvsas.ko v0.8.16 error messages and kernel crashes attaching 4 SATA drives to specific HP SAS expander ports bugzilla-daemon
2014-08-07 20:29 ` [Bug 81861] " bugzilla-daemon
2014-08-08  8:19 ` bugzilla-daemon
2014-08-08  8:24 ` [Bug 81861] Oops by mvsas v0.8.16: sas: ataX: end_device-Y:0:Z: dev error handler -> general protection fault, RIP: mvs_task_prep_ata+0x80/0x3a0 bugzilla-daemon
2014-08-08  8:34 ` bugzilla-daemon
2014-08-12 20:09 ` bugzilla-daemon
2014-08-12 22:02 ` bugzilla-daemon
2014-08-21 18:35 ` bugzilla-daemon
2014-08-22 12:13 ` bugzilla-daemon
2014-08-22 12:16 ` bugzilla-daemon
2014-08-22 12:17 ` bugzilla-daemon
2014-08-22 13:19 ` bugzilla-daemon
2014-08-22 14:05 ` bugzilla-daemon
2014-08-22 17:00 ` bugzilla-daemon
2014-08-22 17:36 ` bugzilla-daemon
2014-08-23 20:04 ` bugzilla-daemon
2014-08-23 20:06 ` bugzilla-daemon
2014-08-23 22:12 ` bugzilla-daemon
2014-09-23 21:56 ` bugzilla-daemon
2014-09-24  0:32   ` Elliott, Robert (Server Storage)
2014-09-26  7:04 ` bugzilla-daemon
2014-10-19 15:56 ` bugzilla-daemon
2014-12-17 19:49 ` bugzilla-daemon
2015-01-26 23:19 ` bugzilla-daemon
2015-01-26 23:20 ` bugzilla-daemon
2015-01-26 23:21 ` bugzilla-daemon
2015-04-23 11:31 ` bugzilla-daemon
2015-04-29 13:40 ` bugzilla-daemon
2015-04-29 14:20   ` James Bottomley
     [not found]     ` <CAC2CY-2YAy8GfjCHO+PrFWAuBnhfnMvK33KJ3YCVRZXJMEHykQ@mail.gmail.com>
2015-04-29 15:41       ` James Bottomley
2015-04-29 16:24         ` Adam Talbot
2015-04-29 18:05           ` James Bottomley
2015-04-29 18:07             ` Adam Talbot
2015-04-29 18:10               ` James Bottomley [this message]
2015-04-29 19:09             ` Nathan Rennie-Waldock
2015-10-05  0:07               ` Nathan Rennie-Waldock
2015-04-29 13:41 ` 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=1430331008.2189.18.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=ajtalbot1@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nathan.renniewaldock@gmail.com \
    /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.