All of lore.kernel.org
 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 12:19:31 +0000	[thread overview]
Message-ID: <4D46A8D3.3000807@mrc-lmb.cam.ac.uk> (raw)
In-Reply-To: <20110131105322.GE7459@htj.dyndns.org>

Tejun Heo wrote:
>> 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)
> 
> Most likely.

I've just been googling and peeking and it seems there may be another
possibility but I'm much less familiar with Ubuntu so I could easily be
misinterpreting something.

I have an Ubuntu box at work and I just installed the
linux-source-2.6.32-28.55 package on it. When I look at sata_via.c I see
that there's a different (earlier?) version of the patch there than what
is in 2.6.37 (the test is pdev->device == 0x3249 versus one based on
board_id)

So it's conceivable that I did update my lucid installation at home but
that this version of the patch doesn't fix the problem. I'll check
exactly what's what tonight.

> So, that leaves the problem sil was seeing.  Are you
> interested in digging that down too?

Well I don't mind testing that card with the kernels I've now got,
assuming I can borrow the card again. I'm a lot less enthusiastic about
compiling more new versions though.

Firstly, I've got to finish sorting out my machine - my backup system
has stopped working for example and I've still got a bunch of data to
migrate/integrate from the old disk. And I need to upgrade SUSE to 11.3
to see if that fixes this problem without introducing any new ones.

Secondly, kernel compilation in my limited experience has been a big
hassle. Every time I change anything in sata_via.c it seems to want to
recompile absolutely everything and that takes over two hours. I thought
make was supposed to do minimal recompilation? That plus a bug in the
script, the unexpectedly large amount of space required and some finger
trouble made it a less than smooth process.

Since we don't yet know whether a recent kernel fixes my sil problem and
if it does we don't have any idea of a particular patch, that suggests
the strategy would be bisection, which probably involves more compiles
than I'm up for.

But first steps first. I'll see if I can test it with my existing kernels.

Cheers, Dave

  reply	other threads:[~2011-01-31 12:19 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
2011-01-31 10:53             ` Tejun Heo
2011-01-31 12:19               ` Dave Howorth [this message]
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=4D46A8D3.3000807@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 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.