linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Howorth <dhoworth@mrc-lmb.cam.ac.uk>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_via bus errors fixed?
Date: Mon, 31 Jan 2011 10:50:03 +0000	[thread overview]
Message-ID: <4D4693DB.4070009@mrc-lmb.cam.ac.uk> (raw)
In-Reply-To: <20110126101119.GE12520@htj.dyndns.org>

Tejun Heo wrote:
> There are plenty of howtos on building kernel.  It takes some time to
> get used to but once you get a hang of it there's nothing difficult
> about it.

Hmm, I've finally managed to get the compilation to work often enough to
run my tests but I don't think I'll be taking up kernel compiling as a
hobby :(

> The best way would be finding out a workload which doesn't take too
> much time but reliably triggers the issue on a problematic kernel.

That would be booting then :) The dmesg reliably has or does not have
the error messages.

>> Tonight I plan to compile that kernel, which should confirm that I
>> understand how to do it, and then I'll disable the VIA FIFO workaround
>> as you suggest and see what happens.

OK. So the results are now in:

(1) stock SUSE HEAD/11.2 (2.6.37) - works fine with no problem
(2) SUSE 2.6.37 with the 'magic patch' commented out - shows the problem
(3) stock updated SUSE 11.2 (2.6.31.14) - shows the problem
(4) stock SUSE 11.2 with the 'magic patch' added (2.6.31.5) - works fine
with no problem

I think that's fairly indicative that the 'magic patch' is able to cure
my problem with a VT 6241A controller and a Samsung HD103SJ drive.

One thing I still need to investigate is why Ubuntu 10.04 was showing
the problem, but perhaps I never got as far as updating the kernel after
installing it. (AFAIK as installed it is 2.6.31, whilst the current
update is 2.6.32-28 which I think should have the patch)

Thanks for your help.
Dave

  reply	other threads:[~2011-01-31 10:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 16:06 sata_via bus errors fixed? Dave Howorth
2011-01-24 17:04 ` Tejun Heo
2011-01-24 17:23   ` Dave Howorth
2011-01-25 10:35   ` Dave Howorth
2011-01-25 10:50     ` Tejun Heo
2011-01-26 10:00       ` Dave Howorth
2011-01-26 10:11         ` Tejun Heo
2011-01-31 10:50           ` Dave Howorth [this message]
2011-01-31 10:53             ` Tejun Heo
2011-01-31 12:19               ` Dave Howorth
2011-01-31 13:24                 ` Tejun Heo
2011-02-04 12:09                   ` Dave Howorth
2011-02-08 11:16                     ` Dave Howorth
2011-02-09  9:43                       ` Tejun Heo
2011-02-09 10:04                         ` Dave Howorth

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=4D4693DB.4070009@mrc-lmb.cam.ac.uk \
    --to=dhoworth@mrc-lmb.cam.ac.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=tj@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).