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: Wed, 02 May 2007 17:46:30 -0600 [thread overview]
Message-ID: <463922D6.3040105@shaw.ca> (raw)
In-Reply-To: <46390AFE.8000800@yahoo.de>
Stefan wrote:
>>> 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.
>>
>>
> I have just replaced the cables with brand new ones, still no change the
> machine freezes ~10min after boot.
> Sometimes I even have to completely power down the machine to be able to
> boot again.
Power problems would be another possibility..
--
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-02 23:47 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 [this message]
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=463922D6.3040105@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 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.