All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adriaan Peeters <apeeters@lashout.net>
To: Justin Cormack <justin@street-vision.com>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: siI3112 crash on enabling dma
Date: 11 Jun 2003 21:21:56 +0200	[thread overview]
Message-ID: <1055359316.28365.317.camel@localhost> (raw)
In-Reply-To: <1055276951.2046.5.camel@lotte>

On Tue, 2003-06-10 at 22:29, Justin Cormack wrote:

> I got severe filesystem corruption on an Sii3112 system (Supermicro
> E7505 with 2 onboard SiI3112) but I later memtested the machine and
> found bad ram, so I dont think it is a valid example of corruption.
> However I am still slightly suspicious. Did you have 

The memory is stable, no problems in memtest.

> echo "max_kb_per_request:15" > /proc/ide/hdXX/settings
> set for the relevant drives? This is a known bug (I didnt have this
> either, another reason why this is not a valid datapoint...)

These were not set when the error occured. I found this option after the
crash somewhere on the net, but I can't find any references to it on
google at the moment :( Can it cause that severe filesystem corruption ?

Was DMA enabled on your system, and what drives did you use ?

I tested several firmware revisions, disabled mmio in the driver,
nothing helped. No DMA at boot, and the crash is easy to reproduce, for
example:

console1: dd if=/dev/hda of=/dev/null
console2: hdparm -X66 -d1 /dev/hda

result without max_kb_per_request:
---
/dev/hda:
 setting using_dma to 1 (on)
blk: queue c0468b00, I/O limit 4095Mb (mask 0xffffffff)
 setting xfermode to 66 (UltraDMA mode2)
hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }

hda: dma_intr: status=0xd0 { Busy }

hda: DMA disabled
--

result with max_kb_per_request:
---
/dev/hda:
 setting using_dma to 1 (on)
blk: queue c0468b00, I/O limit 4095Mb (mask 0xffffffff)
 setting xfermode to 66 (UltraDMA mode2)
hda: dma_timer_expiry: dma status = 0x21
hda: timeout waiting for DMA
hda: timeout waiting for DMA
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
--

The system hangs and nothing is written to syslog.

I don't know where to look next.

-- 
Adriaan Peeters <apeeters@lashout.net>


      reply	other threads:[~2003-06-11 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06 19:52 siI3112 crash on enabling dma Adriaan Peeters
2003-06-07  1:09 ` Alan Cox
2003-06-07  2:20   ` Adriaan Peeters
2003-06-10 16:05 ` Adriaan Peeters
2003-06-10 20:29   ` Justin Cormack
2003-06-11 19:21     ` Adriaan Peeters [this message]

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=1055359316.28365.317.camel@localhost \
    --to=apeeters@lashout.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=justin@street-vision.com \
    --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 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.