All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Ivar Rykkelid <jonry@pvv.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Jeff Garzik <jeff@garzik.org>, Tejun Heo <htejun@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: sata_nv issues with MCP51 SATA controller
Date: Fri, 14 Sep 2007 14:10:21 +0200	[thread overview]
Message-ID: <46EA7A2D.90700@pvv.org> (raw)
In-Reply-To: <46E9D7DD.30801@shaw.ca>

Hi,

To eliminate the possibility of this being a hardware issue, I have now 
acquired another "Gigabyte GA-N650SLI-DS4" motherboard (with the "MCP51" 
chipset) for testing. I'll swap parts this evening. Hopefully I'll be 
able to tell you in a few hours whether this appears to be working as it 
should. The motherboard that I'm going to swap to has actually been 
tested (with MS Windows OS+driver) for more than a day with a disk 
connected, so if this MB also fails, I think it will be safe to say that 
the issue is with the sata_nv driver... So hang on.

(You can't think of something else that could conflict with the sata_nv 
driver after a bit of time, like two of my raid-disks being encrypted, 
me running a SW raid-5 array / some special HW (quad-core CPU) / me 
running vmware on this server ... ? - To me, all these suggestions seems 
rather far fetched, especially as all is working with another 
controller, so I'm arguing that unless there's a HW issue, the issue is 
with the driver, but you're the expert(s), so let me know if you differ.)

I'll keep you posted as to the result of swapping HW.. Give me a few 
hours.  :-)

BR
Jon Ivar

Robert Hancock wrote:
> Jeff Garzik wrote:
>> Jon Ivar Rykkelid wrote:
>>> Hi,
>>>
>>> I now tested with the adma=0 option, but if anything I got a crash 
>>> quicker than before. Same error message started coming in, but this 
>>> time the system hung before I was able to capture the log as well 
>>> (but I saw the error, and it was the same as before, except that 
>>> this time it was the ata3-channel that first started acting up..) - 
>>> To remind you all what this is about, I have reattached the log that 
>>> I originally captured...
>>
>> Sounds like a hardware problem, since disabling ADMA is generally the 
>> cure-all we use -- it appears to stress the hardware less.
>
> If this is an MCP51 chipset, adma=0 will make no difference since that 
> chipset does not support ADMA in the first place.
>

  reply	other threads:[~2007-09-14 12:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13  7:46 sata_nv issues with MCP51 SATA controller Jon Ivar Rykkelid
2007-09-13 14:20 ` Jeff Garzik
2007-09-13 15:05   ` Jon Ivar Rykkelid
2007-09-13 15:14     ` Tejun Heo
2007-09-13 18:01       ` Jon Ivar Rykkelid
2007-09-13 19:26         ` Jon Ivar Rykkelid
2007-09-13 19:54           ` Jeff Garzik
2007-09-13 21:15             ` Jon Ivar Rykkelid
2007-09-14  0:37             ` Robert Hancock
2007-09-14 12:10               ` Jon Ivar Rykkelid [this message]
2007-09-14 13:29         ` Prakash Punnoor
2007-09-14 14:17           ` Jon Ivar Rykkelid
2007-09-14 14:25             ` Jeff Garzik
2007-09-14 14:39               ` Tejun Heo
     [not found]                 ` <46EAAA9A.1020903@pvv.org>
2007-09-14 15:58                   ` Jeff Garzik
2007-09-14 18:38                     ` Jon Ivar Rykkelid
2007-09-14 20:24                       ` auxsvr
2007-09-14 20:35             ` Jon Ivar Rykkelid
2007-09-15  7:12               ` Prakash Punnoor
2007-09-15 10:14                 ` Jon Ivar Rykkelid
2007-09-15 14:47                   ` John Stoffel
2007-09-15 19:29                     ` Jon Ivar Rykkelid
     [not found]                 ` <46EBA82C.6050000@pvv.org>
2007-09-15 11:30                   ` Prakash Punnoor
  -- strict thread matches above, loose matches on Subject: below --
2007-09-13  7:18 Jon Ivar Rykkelid
2007-09-13  9:16 ` 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=46EA7A2D.90700@pvv.org \
    --to=jonry@pvv.org \
    --cc=hancockr@shaw.ca \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@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.