From: 7091@blargh.com
To: Andi Kleen <ak@suse.de>
Cc: Tejun Heo <htejun@gmail.com>,
7091@blargh.com, linux-ide@vger.kernel.org, jgarzik@pobox.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sata_sil, writing bug with multiple cards?
Date: Wed, 04 Jul 2007 01:17:34 -0700 [thread overview]
Message-ID: <courier.468B579E.00002ECF@blargh.com> (raw)
In-Reply-To: <200707040908.21512.ak@suse.de>
Andi Kleen writes:
> If it has >2GB or so it might be worth trying booting it with mem=2G
Nope, only 1GB of RAM.
> Most likely it is some sort of hardware bug that we might
> not be able to do much about. Have you tried contacting SIL or VIA?
No, I haven't. Like I mentioned above, the OpenBSD drivers seemed to work,
or at least did with similar tests. I would need to run the more extensive
checks to be positive, but those take a lot of time, obviously. And
downtime for the box, a lot of which isn't really manageable, at the moment.
> e.g. if you have some other system with a different chipset it might
> be useful to test the SIL controllers in those.
The previous motherboard was an AMD 760 chipset, and it had the same
problem.
> I would perhaps also try a newer kernel.
I can certainly try that - I admit 2.6.20.3 is a little old now. This will
probably take me a couple days - tomorrow is the 4th of July and a holiday
for me.
next prev parent reply other threads:[~2007-07-04 8:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 6:42 sata_sil, writing bug with multiple cards? 7091
2007-07-03 8:51 ` Tejun Heo
2007-07-04 1:40 ` 7091
2007-07-04 1:48 ` Tejun Heo
2007-07-04 2:05 ` 7091
2007-07-04 3:22 ` 7091
2007-07-04 3:44 ` 7091
2007-07-04 3:53 ` Tejun Heo
2007-07-04 7:08 ` Andi Kleen
2007-07-04 8:17 ` 7091 [this message]
2007-07-04 8:38 ` Andi Kleen
2007-07-04 8:52 ` Tejun Heo
2007-07-10 10:55 ` Tejun Heo
2007-07-12 3:21 ` 7091
2007-07-04 3:41 ` Tejun Heo
2007-07-04 9:18 ` Alan Cox
2007-07-04 9:14 ` Tejun Heo
2007-07-04 9:26 ` 7091
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=courier.468B579E.00002ECF@blargh.com \
--to=7091@blargh.com \
--cc=ak@suse.de \
--cc=htejun@gmail.com \
--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).