All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ceriel Jacobs <linux-scsi@crashplan.pro>
To: Adam Talbot <ajtalbot1@gmail.com>, linux-scsi@vger.kernel.org
Subject: Re: mvsas panics and dies when attached to a port extender on newer kernels
Date: Thu, 23 Apr 2015 13:10:06 +0200	[thread overview]
Message-ID: <5538D30E.6090300@crashplan.pro> (raw)
In-Reply-To: <CAH_2GhdM7RgP0a2fYnY3yqb1T_LhGasmwBwsaF+yfCqRhXUikg@mail.gmail.com>

Your mvsas port expander bug might be related to bug# 81861

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

Adam Talbot schreef op 13-04-15 om 17:11:
> To make a very long debugging story short, I think there is an issues/bug
> with the mvsas driver. It works, with older kernels, and breaks on
> newer kernels.
>
> My Debian Jessie system was running great on a 3.18 kernel.  Changed
> cases to a newer supermicro case with a SAS expander backplane (SAS933EL).  That
> was the only hardware change.  Now, when ever I boot, the system kernel panics.
>
> 3.2.65-1+deb7u2 works
> 3.9.0 Gentoo CD works
> 3.16+ all fail
> Attached are 3 kernel panics on 3.16+ kernels.
>
> Motherboard is a Supermicro X8SIE, with a "Marvell Technology Group Ltd.
> 88SE6440 SAS/SATA PCIe controller"
>
> Is this a known bug?
>
> At this point I have two options:
> Stick with the old kernel (yuck)
> Buy a new card running a better supported chipset
>
> Any help would be greatly appreciated
> Thanks
> Adam
>

  reply	other threads:[~2015-04-23 11:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 15:11 mvsas panics and dies when attached to a port extender on newer kernels Adam Talbot
2015-04-23 11:10 ` Ceriel Jacobs [this message]
2015-04-23 16:27   ` Adam Talbot
  -- strict thread matches above, loose matches on Subject: below --
2015-04-14 21:03 Adam Talbot
2015-04-14 21:16 ` James Bottomley
2015-04-14 21:41   ` Adam Talbot
2015-04-16  5:16     ` James Bottomley
2015-04-16 17:26       ` Adam Talbot
2015-04-16 17:28         ` James Bottomley
2015-04-16 17:31           ` Adam Talbot
2015-04-17  2:26             ` Adam Talbot
2015-04-14 21:46   ` Laurence Oberman
2015-04-12 20:22 Adam Talbot
2015-04-13  5:41 ` Mikael Abrahamsson

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=5538D30E.6090300@crashplan.pro \
    --to=linux-scsi@crashplan.pro \
    --cc=ajtalbot1@gmail.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 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.