From: Doug McLain <nostar@comcast.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: PALFFY Daniel <dpalffy-lists@rainstorm.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: sata_sil data corruption
Date: Mon, 21 Feb 2005 11:47:48 +0000 [thread overview]
Message-ID: <4219CA64.8020402@comcast.net> (raw)
In-Reply-To: <20050221162923.GA29621@havoc.gtf.org>
Jeff Garzik wrote:
Been there done that, all on this list actually. Bios upgrade, bios
reset, new cable, different drive, correct functionality in windows, and
now the drive and cable ahave found their home in my other PC, a kt600
board using the sata_via driver, where it works flawlessly. I'm not
even interested in using the sata interface on this machine anymore, but
I still try to make an effort whenever possible to contribute byt
reporting bugs. So many people with so many different hardware
combinations, sometimes it takes the right combination of
hardware/software to reveal a bug. That being said, if you want to
investigate further, I can provide any information you want. If you want
to ignore it, thats fine too. Evidence strongly leans towards a driver
bug though.
I also noticed that I get oops now sometimes even with no drive
attatched at all
What is a blacklist entry? A combination of drive/controller that is
determined to be incompatable together? I would assume for a drive to
make it to a blacklists it would have to be incompatable regardless of
OS right? The drive in question is a WD2000JD
Doug
>
> In this case, the bug _reports_ are hard to find.
>
> Each case with sata_sil is either solved with a BIOS update, a
> blacklist entry, or new cables. Just read through bugzilla.kernel.org.
>
> Jeff
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
http://nostar.net/
next prev parent reply other threads:[~2005-02-21 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 13:17 sata_sil data corruption PALFFY Daniel
2005-02-19 17:35 ` Jeff Garzik
2005-02-21 11:25 ` PALFFY Daniel
2005-02-21 9:02 ` Doug McLain
2005-02-21 16:17 ` Jeff Garzik
2005-02-21 11:25 ` Doug McLain
2005-02-21 16:29 ` Jeff Garzik
2005-02-21 11:47 ` Doug McLain [this message]
2005-02-21 16:35 ` Prakash Punnoor
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=4219CA64.8020402@comcast.net \
--to=nostar@comcast.net \
--cc=dpalffy-lists@rainstorm.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).