All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: Andre Tomt <andre@tomt.net>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org
Subject: Re: mvsas errors in 2.6.36
Date: Wed, 1 Dec 2010 23:29:54 -0700	[thread overview]
Message-ID: <201012012329.54944.thomas@fjellstrom.ca> (raw)
In-Reply-To: <4CE3912E.6060904@tomt.net>

On November 17, 2010, you wrote:
> On 11/17/2010 08:53 AM, Thomas Fjellstrom wrote:
> [snip]
> 
> > Still no fatal errors, but the problem is still happening regularly. It
> > causes a pause in disk io of a couple seconds at least. Really quite
> > annoying.
> >
> > One thing thats got me wondering, is could this be a power issue?
> > It almost seems like (from the messages) that a single drive (any drive)
> > is freaking out, and returning an error that probably shouldn't happen (no 
> > CHS 0?), which could mean the drive is underpowered and the firmware is 
> > flipping out. I'm not entirely sure. The system has a 750w decent quality
> > Antec power supply. The total power use of the system shouldn't come over 
> > half that (phenom II x4 810 cpu, gigabyte ma790fxtud5p mb, low profile 
> > nvidia 9400GS gpu, 8 sata hdds, 3 fans, etc). I'm mostly sure the 12v 
> > rails are spread out evenly, but I have yet to make absolutely sure.

Made absolute sure. I had been worrying that I was overloading one of the 
rails on the PSU, but it turns out that it isn't a multi 12v rail PSU after 
all. The box and advertising says it is, but the electronics inside all say 
its a single 12v rail device.

> [snip]
> 
> After the mvsas update in 2.6.35 this started happening to me as well;
> at least its better than the previous state - not working.. ;-) However,
> after rolling a new 2.6.35 with the following fix that is queued up for
> the upcoming 2.6.35 and 2.6.36 stable releases, they seem to have
> dissapeared - 3 days and counting.
> 
> http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git;a=blob_pl
> ain;f=queue-2.6.33/libsas-fix-ncq-mixing-with-non-ncq.patch;h=b6d7c92094d95
> ad67a3b23c2e09c25d4fbd0f46b;hb=HEAD
> 
> The fix is queued up for the next 2.6.36 and 2.6.35 stable point-releases.

Ahah. I wonder how I missed that when I first read it. I'll have to give the 
stable .36 kernel a try. Thanks!


-- 
Thomas Fjellstrom
thomas@fjellstrom.ca

  reply	other threads:[~2010-12-02  6:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 12:50 mvsas errors in 2.6.36 Thomas Fjellstrom
2010-10-31 15:11 ` Thomas Fjellstrom
2010-11-02 17:02   ` Audio Haven
2010-11-17  7:53   ` Thomas Fjellstrom
2010-11-17  8:24     ` Andre Tomt
2010-12-02  6:29       ` Thomas Fjellstrom [this message]
2010-12-02  9:48         ` Thomas Fjellstrom
2010-12-02 13:17           ` Spelic
2010-12-02 13:37             ` Thomas Fjellstrom
2010-12-03  2:16             ` Thomas Fjellstrom
2010-12-05 10:45             ` Audio Haven
2010-12-05 10:58               ` Mikael Abrahamsson
2010-12-06 11:11                 ` Audio Haven
2010-12-07 16:30                   ` Benjamin LaHaise
2010-12-03 16:39           ` Thomas Fjellstrom
2010-12-03 20:31             ` David Milburn
2010-12-04  6:57               ` Thomas Fjellstrom
     [not found]               ` <201012041550372348573@usish.com>
2010-12-04  8:37                 ` Thomas Fjellstrom
2010-12-04 11:52                 ` Thomas Fjellstrom
2010-12-04 12:33                 ` jack_wang
2010-12-04 12:54                   ` Thomas Fjellstrom
2010-12-04 15:44                     ` Thomas Fjellstrom
2010-12-04 18:22                       ` Thomas Fjellstrom
2010-12-05  2:08                       ` jack_wang
2010-12-05 20:01                         ` Thomas Fjellstrom
2010-12-07 19:45   ` tomm

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=201012012329.54944.thomas@fjellstrom.ca \
    --to=thomas@fjellstrom.ca \
    --cc=andre@tomt.net \
    --cc=linux-kernel@vger.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 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.