From: Robert Hancock <hancockr@shaw.ca>
To: Stefan <gentoopower@yahoo.de>
Cc: Tejun Heo <htejun@gmail.com>, 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: Tue, 01 May 2007 17:57:46 -0600 [thread overview]
Message-ID: <4637D3FA.2070403@shaw.ca> (raw)
In-Reply-To: <4637CCEA.8020202@yahoo.de>
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). First thing you should try is
replacing the SATA cable to that drive.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next prev parent reply other threads:[~2007-05-01 23:57 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 [this message]
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
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=4637D3FA.2070403@shaw.ca \
--to=hancockr@shaw.ca \
--cc=gentoopower@yahoo.de \
--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).