All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeremy Smith <alceste@xmission.com>,
	Alexander Shaposhnikov <shaposh@isp.nsc.ru>,
	Carlos Pardo <Carlos.Pardo@siliconimage.com>,
	Paul Taylor <Paul.Taylor@siliconimage.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: PROBLEM: Silicon Image 3112 Lockups
Date: Wed, 07 Sep 2005 11:01:46 +0900	[thread overview]
Message-ID: <431E4A0A.3060504@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0509061835230.2270@xmission.xmission.com>


  Hello, Jeremy.

Jeremy Smith wrote:
> 
> 
> I'm working on a system (K8N-DL) with a 3114 driver running 2.6.12 and 
> experiencing lockups on heavy disk access.  This is the built-in on an 
> ASUS-K8N-DL board.  I was wondering if the following problem is 
> symptomatic of a known bug.
> 
> I will get momentary freezes, and then I'll continue.  At some point 
> though, the disk access will freeze--no panic, but a lockup of all disk 
> access.  I have configured the first drive as a single drive 
> concatenation in the "RAID" bootup and haven't done anything with the 
> second drive.  The large logical partition on each drive is configured 
> with software RAID.

  You're the second person reporting similar problem with ASUS K8N-DL 
board.  Please see the following threads.

http://marc.theaimsgroup.com/?l=linux-ide&m=112497821103098&w=2
http://marc.theaimsgroup.com/?l=linux-ide&m=112600646820285&w=2

> dd if=/dev/sda of=/dev/null can reproduct error, as can several 
> disk-intensive activities

  In the following mail, I've attached a patch which might alleviate 
errors during writes (as Alexander was reporting CRC errors with write 
commands), but it won't do any good if you're getting errors during reading.

http://marc.theaimsgroup.com/?l=linux-ide&m=112602112819183&w=2

  Carlos and Paul, do you guys know anything about this mainboard? 
Should we perform some special tweaking to get these boards work?  I'll 
dig 3112/3114 document further but I'm not very sure what I should look for.

  Thanks.

-- 
tejun

  reply	other threads:[~2005-09-07  2:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07  1:07 PROBLEM: Silicon Image 3112 Lockups Jeremy Smith
2005-09-07  2:01 ` Tejun Heo [this message]
2005-09-07  2:13   ` Jeff Garzik
2005-09-07  2:34     ` Tejun Heo
2005-09-07  2:42       ` Tejun Heo
2005-09-07  3:21         ` Jeremy Smith
2005-09-07  6:00           ` Tejun Heo
2005-09-07  6:09             ` Jeff Garzik

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=431E4A0A.3060504@gmail.com \
    --to=htejun@gmail.com \
    --cc=Carlos.Pardo@siliconimage.com \
    --cc=Paul.Taylor@siliconimage.com \
    --cc=alceste@xmission.com \
    --cc=jgarzik@pobox.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 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.