From: Tejun Heo <htejun@gmail.com>
To: Emmeran Seehuber <rototor@rototor.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18.2: sporadic SATA port resets (Broadcom BCM5785 (HT1000))
Date: Fri, 09 Feb 2007 08:54:12 -0500 [thread overview]
Message-ID: <45CC7D04.5090403@gmail.com> (raw)
In-Reply-To: <200702091237.24576.rototor@rototor.de>
Emmeran Seehuber wrote:
>>> Does somebody have a glue whats going on here? Could it be a hardware
>>> failure?
>> It might be. Quite some SATA bug reports turn out to be hardware
>> problem, most commonly PSU issues.
>
> The power supply unit (you meant this with PSU, didn`t you?) has 800 Watt, so
> it should be powerfull enough for one harddisk and no graphics board.
I see.
>>> Do you need additional information?
>> Yeah, please post the content of /var/log/boot.msg if available and the
>> result of dmesg and lspci -nn.
>
> We don`t have a /var/log/boot.msg, but it seems the boot messages were saved
> in /var/log/dmesg, so I attached it.
Yeap, that's exactly what I wanted. So, the driver is sata_svw and
errors are timeouts for both reads and writes with BMDMA engine still
running. It looks like transmission errors to me. Can you post the
result of 'smartctl -a /dev/sdX'?
--
tejun
next prev parent reply other threads:[~2007-02-09 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 17:17 2.6.18.2: sporadic SATA port resets (Broadcom BCM5785 (HT1000)) Emmeran Seehuber
2007-02-09 9:19 ` Tejun Heo
2007-02-09 11:37 ` Emmeran Seehuber
2007-02-09 13:54 ` Tejun Heo [this message]
2007-02-09 17:09 ` Emmeran Seehuber
2007-02-10 6:49 ` Tejun Heo
2007-02-10 8:42 ` Emmeran Seehuber
2007-02-11 22:19 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2007-02-09 17:56 koan
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=45CC7D04.5090403@gmail.com \
--to=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rototor@rototor.de \
/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.