From: Tejun Heo <htejun@gmail.com>
To: Fredrik Rinnestam <fredrik@obra.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: SIL3512 lockup problem using driver verion 0.9 and Linux 2.6.14
Date: Tue, 06 Feb 2007 16:34:04 +0900 [thread overview]
Message-ID: <45C82F6C.90604@gmail.com> (raw)
In-Reply-To: <20070203231757.GA2035@useful.obra.se>
Fredrik Rinnestam wrote:
>> I get very similar error-messages with my SiI 3512 controller. I just
>> noticed this while connecting a second drive and moving data from sdb to
>> sda. Copying stuff from the internal ide-controller (nvidia) to sda does
>> not produce any errors. I've also tried diffrent cables without any
>> luck. Kernel is 2.6.19.2
>>
> uhm, scratch that:
>
> this is from normal operation on the second drive (fileserver):
Sorry but can't really find anything specific in your log. Please...
1. give a host at 2.6.20. It will give us yet more info about errors.
2. turn on "Kernel hacking -> Show timing information on printks."
3. report the result of "lspci -nn"
4. try to connect harddrives to separate power supply or use other
hardware debugging tactics. There have been a lot of SATA bug reports
which turned out to be hardware problems. SATA seems to be the first to
get hit when there is generic hardware problem (e.g. insufficient / bad
power supply).
Thanks.
--
tejun
next prev parent reply other threads:[~2007-02-06 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 16:08 SIL3512 lockup problem using driver verion 0.9 and Linux 2.6.14 Steve Graham
2006-12-12 1:21 ` Tejun Heo
2006-12-30 18:53 ` Steve Graham
2007-02-03 20:14 ` Fredrik Rinnestam
2007-02-03 23:17 ` Fredrik Rinnestam
2007-02-06 7:34 ` Tejun Heo [this message]
2007-02-06 17:55 ` Fredrik Rinnestam
2007-02-12 1:03 ` 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=45C82F6C.90604@gmail.com \
--to=htejun@gmail.com \
--cc=fredrik@obra.se \
--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.