From: Tejun Heo <htejun@gmail.com>
Cc: 'Jeff Garzik' <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, Carlos.Pardo@siliconimage.com,
Paul.Taylor@siliconimage.com, lbattraw@insightbb.com,
'Yuri Kirsanov' <flash@rccb.ru>,
'Jeremy Smith' <alceste@xmission.com>,
shaposh@isp.nsc.ru
Subject: Re: RE :sata_sil + UDMA CRC errors
Date: Wed, 07 Sep 2005 18:56:44 +0900 [thread overview]
Message-ID: <431EB95C.3070801@gmail.com> (raw)
In-Reply-To: <200509070730.j877UxgA022401@ns.isp.nsc.ru>
Hello, Alexander & Jeremy.
Alexander Shaposhnikov wrote:
> Hellow Tejun
>
> I tried your patch (by the way, it cannot be applied by patch utility -it
> complains about malformed expression on line 19 and so on)
> Default reads in 500mv. With 600mv, I am starting to get CRC errors for
> Seagate drive (no errors with 2.6.13-git4). Samsung drive produces so many
> errors, that it is unusable both with and without patch.
Ugh... that's ugly. :-/
Jeremy, apparantly my little patch doesn't do any good. Please ignore it.
> Concerning K8N-DL motherboard -current BIOS 1004 is very buggy. It has
> screwed up ACPI APIC table. To use onboard lan and usb, I have to boot with
> pci=noacpi boot option. And I cannot use 1003, as I have DualCore Opterons,
> and 1004 the only one which supports them!
>
> There is long problem with Nvidia CK804 southbridge sata under Linux.
> Despite that the board was released some 8 month ago, it still cannot be
> used! And nobody seems to care about this. ASUS in the least.
> I was able to boot from NVidia SATA with latest kernel and irqpoll option.
> At first I thought that all my problems are gone at last, but the god
> decided differently. It works at light disk load, but havy load lead to
> system freeze. No errors, just dead freeze. I returned to silicon3114 sata.
> At least, I have one working drive now:)
>
I fear that there's nothing much else I can do about this K8N-DL sil
CRC error. I've read the hw doc but couldn't find anything which seems
helpful. Let's hope something (BIOS update?) comes up soon.
Sorry.
--
tejun
next prev parent reply other threads:[~2005-09-07 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 11:33 RE :sata_sil + UDMA CRC errors Alexander Shaposhnikov
2005-09-06 11:56 ` Tejun Heo
[not found] ` <1126016000.3760.15.camel@m00>
2005-09-06 15:38 ` Tejun Heo
2005-09-07 7:30 ` Alexander Shaposhnikov
2005-09-07 9:56 ` Tejun Heo [this message]
2005-09-07 13:52 ` Jeremy Smith
2005-09-09 20:10 ` Jeremy Smith
-- strict thread matches above, loose matches on Subject: below --
2005-08-26 4:41 Alexander Shaposhnikov
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=431EB95C.3070801@gmail.com \
--to=htejun@gmail.com \
--cc=Carlos.Pardo@siliconimage.com \
--cc=Paul.Taylor@siliconimage.com \
--cc=alceste@xmission.com \
--cc=flash@rccb.ru \
--cc=jgarzik@pobox.com \
--cc=lbattraw@insightbb.com \
--cc=linux-ide@vger.kernel.org \
--cc=shaposh@isp.nsc.ru \
/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).