linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Fjellstrom <tfjellstrom@shaw.ca>
To: linux-kernel@vger.kernel.org
Cc: Mikael Abrahamsson <swmike@swm.pp.se>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: 2.6.31-rc9 kernel BUG and mvsas
Date: Thu, 10 Dec 2009 14:04:25 -0700	[thread overview]
Message-ID: <200912101404.26094.tfjellstrom@shaw.ca> (raw)
In-Reply-To: <alpine.DEB.1.10.0912102022460.23464@uplift.swm.pp.se>

On Thu December 10 2009, Mikael Abrahamsson wrote:
> On Sat, 5 Dec 2009, Mikael Abrahamsson wrote:
> > When removing this extra option, it compiles with vanilla 2.6.32 just
> > fine. I crashes the same way as the ubuntu kernel when hot-plugging a
> > disk as well (this time I did it without gdm/x running and it oopses,
> > but unfortunately the highest part of the oops scrolled off). It's 100%
> > reproducible anyway, so basically the controller is a no-go in 2.6.31.6
> > and 2.6.32 both vanilla and ubuntu versions, both without and including
> > the nov09 mvsas patch (at least the original version of the patch as
> > posted). Different failure scenarios though... With the stock kernel
> > the controller seems to get stuck in writing and nothing more happens
> > but at least the machine doesn't crash and burn like it does with the
> > mvsas-patch.
> 
> Would it make sense for me to log this problem in bugzilla? There seems
>  to be a similar issue with equal hw:
> 
> <http://bugzilla.kernel.org/show_bug.cgi?id=14534>
> 
> did these fixes ever go upstream? Are they scheduled to go into the
> stable rebuilds of 2.6.32 ? The patches mentioned in there, are these the
> ones I already tried that didn't solve my problem?
> 

I'm really hoping Andy Yan or someone else on the project can get some time 
to polish up the last patch set posted to linux-scsi. There were a few 
comments regarding them, but no one has responded to them yet.

-- 
Thomas Fjellstrom
tfjellstrom@shaw.ca

      reply	other threads:[~2009-12-10 21:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200909090414.41274.tfjellstrom@shaw.ca>
     [not found] ` <200909091030.13147.tfjellstrom@shaw.ca>
2009-09-09 18:52   ` 2.6.31-rc9 kernel BUG and mvsas Jeff Garzik
2009-09-09 19:10     ` Thomas Fjellstrom
2009-09-09 20:07       ` Thomas Fjellstrom
2009-09-10 23:55         ` Thomas Fjellstrom
2009-09-11 16:04           ` Thomas Fjellstrom
2009-09-13  0:43           ` Jeff Garzik
2009-09-13  4:59             ` Thomas Fjellstrom
     [not found]             ` <200909122256.50474.tfjellstrom@shaw.ca>
2009-09-15 16:20               ` Thomas Fjellstrom
2009-09-17 15:39                 ` 2.6.31-git4 mvsas DRIVER_TIMEOUT Thomas Fjellstrom
2009-11-04  0:50     ` 2.6.31-rc9 kernel BUG and mvsas Andre Tomt
2009-11-04  1:05       ` Andre Tomt
2009-12-03 21:17       ` Mikael Abrahamsson
2009-12-03 21:36         ` Kristleifur Daðason
2009-12-04 19:00           ` Mikael Abrahamsson
2009-12-04 19:08             ` Kristleifur Daðason
2009-12-05 10:54               ` Mikael Abrahamsson
2009-12-10 19:25                 ` Mikael Abrahamsson
2009-12-10 21:04                   ` Thomas Fjellstrom [this message]

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=200912101404.26094.tfjellstrom@shaw.ca \
    --to=tfjellstrom@shaw.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=swmike@swm.pp.se \
    /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).