All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: mark.paulus@verizonbusiness.com
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_sil issue on 2.6.22
Date: Wed, 05 Dec 2007 23:33:55 +0900	[thread overview]
Message-ID: <4756B6D3.9020307@gmail.com> (raw)
In-Reply-To: <4756B5B2.1010302@verizonbusiness.com>

Mark Paulus wrote:
> Well, I feel foolish. 
> One problem is that the prebuilt kernel is using an initrd
> image, so I made your patch changes, and put them into
> /lib/modules/`uname -r`/kernel/drivers/ata/sata_sil.ko,
> and guess what, they never got loaded.  Foolishness on my
> part.
> 
> Anyway, this time I got to the single boot prompt, where I did
> a 'rmmod sata_sil', and a 'modprobe sata_sil', and I know
> it loaded the new version, because you can see the 'sata_sil
> 0000:02:0b.0: version 2.2b', which I put in
> to verify what the heck is going on.
> This machine is pretty slow to compile the kernel, which is
> why I was trying to short cut the build/install some, but I might try to
> build the kernel on a faster machine and see if
> I can get the initrd image rebuilt also.

This one is good enough, thanks.  It seems the controller is raising
spurious SATA_IRQ.  I wonder why.  You're using a SATA-PATA bridge,
right?  What chip are you using?

-- 
tejun

  reply	other threads:[~2007-12-05 14:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 20:35 sata_sil issue on 2.6.22 Mark Paulus
2007-11-28  1:21 ` Tejun Heo
2007-11-30 15:56   ` Mark Paulus
2007-12-04  2:54     ` Tejun Heo
2007-12-05 14:29       ` Mark Paulus
2007-12-05 14:33         ` Tejun Heo [this message]
2007-12-05 14:49           ` Mark Paulus
2007-12-06  0:25             ` Tejun Heo
2007-12-06  2:10               ` Tejun Heo

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=4756B6D3.9020307@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mark.paulus@verizonbusiness.com \
    /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.