linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan <gentoopower@yahoo.de>
To: Tejun Heo <htejun@gmail.com>
Cc: Robert Hancock <hancockr@shaw.ca>, linux-ide@vger.kernel.org
Subject: Re: System freezes with kernel >2.6.19 - sata_nv [added crash info kern 2.6.21.1]
Date: Sun, 13 May 2007 21:33:19 +0200	[thread overview]
Message-ID: <464767FF.5020907@yahoo.de> (raw)
In-Reply-To: <463878E5.4020607@gmail.com>

Tejun Heo wrote:
> Robert Hancock wrote:
>   
>> Stefan wrote:
>>     
>>> Okay, I had time to set this up. I'm attaching the log messages I got
>>> via netconsole.
>>>
>>> I tested about 20h with adma disabled, the crash won't occur.
>>>
>>> If I remove
>>>
>>> sata_nv.adma=0
>>>
>>> from boot options again it doesn't take long until my machine locks up.
>>>
>>> [Attached dmesg output with 2.6.21.1 kernel + crash info I got via
>>> netconsole]
>>>
>>> I hope this is useful to you guys.
>>>       
>> It looks like you've got SError bits set from the controller, 0x200000
>> means link layer CRC error (btw, we really should be decoding that error
>> and printing it in human readable form rather than making people pore
>> through the SATA spec and count bits).
>>     
>
> Hmmm... Maybe, but most of the bits are nearly meaningless to end users
> anyway.
>
>   
>> First thing you should try is replacing the SATA cable to that drive.
>>     
>
> Yeap, please apply some hardware debugging techniques - replacing /
> reseating SATA cables and connecting it to different power connector.
> But it's disturbing to see machine lock up even if CRC error occurs.
> sata_nv non-adma interface locks the whole machine up too after certain
> error conditions but I thought adma was saner than that.  I hope we can
> work around this somehow.
>
> Thanks.
>
>   
Hi folks, got some news:

I replaced cables, which didn't change anything. My PSU is strong enough
to take a lot more, so I don't think it could be a power problem.
Therefore I replaced the SAMSUNG HD401LJ with  ST3160812AS.
With the seagate attached I don't get the crash. So this may be a
problem in combination with the HD401LJ+ NFORCE4 + ADMA.

--Stefan

  parent reply	other threads:[~2007-05-13 21:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-29 22:27 System freezes with kernel >2.6.19 - sata_nv Stefan
2007-04-30 10:04 ` Tejun Heo
2007-04-30 23:44   ` Robert Hancock
2007-05-01  2:24     ` Tejun Heo
2007-05-01 23:27       ` System freezes with kernel >2.6.19 - sata_nv [added crash info kern 2.6.21.1] Stefan
2007-05-01 23:57         ` Robert Hancock
2007-05-02 11:41           ` Tejun Heo
2007-05-02 22:04             ` Stefan
2007-05-02 23:46               ` Robert Hancock
2007-05-13 19:33             ` Stefan [this message]
2007-05-01  0:19   ` System freezes with kernel >2.6.19 - sata_nv Stefan

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=464767FF.5020907@yahoo.de \
    --to=gentoopower@yahoo.de \
    --cc=hancockr@shaw.ca \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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 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).