mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lionel Bouton <Lionel.Bouton@inet6.fr>
To: Rob Shortt <rob@infointeractive.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: DMA errors - 2.4.22-pre8 - SiS730 - WD800JB
Date: Tue, 29 Jul 2003 15:33:09 +0200	[thread overview]
Message-ID: <20030729153309.A25792@bouton.inet6-interne.fr> (raw)
In-Reply-To: <3F266B99.1040507@infointeractive.com>; from rob@infointeractive.com on mar, jui 29, 2003 at 09:42:01 -0300

On mar, jui 29, 2003 at 09:42:01 -0300, Rob Shortt wrote:
> 
> Hello all,
> 

Hi,

> I have had some mysterious errors that aren't totally fatal in 
> themselves but have led me to reset my machine whenever it happens.  I 
> decided to investigate further by using a seperate console to examine 
> things when it happens.
> 
> My system:
> 
> ECS K7SEM w/ Athlon XP 2100+

This is a SiS based mainboard.
SiS APIC support was still buggy last time I checked.

> hda: dma_timer_expiry: dma status == 0x21
> hda: error waiting for DMA
> hda: dma timeout retry: status=0xd0 { Busy }
> 
> hda: DMA disabled
> ide0: reset timed-out, status=0xd0
> hda: status timeout: status=0xd0 { Busy }
> [...]

Can be related to my hint above.

> 
> Dmesg output after bootup and my .config are below:
> 
> Linux version 2.4.22-pre8 (root@freevo) (gcc version 2.95.4 20011002 
> (Debian prerelease)) #2 Sat Jul 26 13:13:03 ADT 2003
> BIOS-provided physical RAM map:
>   BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
>   BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
>   BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
>   BIOS-e820: 0000000000100000 - 0000000020000000 (usable)
>   BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
> 512MB LOWMEM available.
> On node 0 totalpages: 131072
> zone(0): 4096 pages.
> zone(1): 126976 pages.
> zone(2): 0 pages.
> Kernel command line: root=/dev/hda1 ro
> Local APIC disabled by BIOS -- reenabling.
> Found and enabled local APIC!

Argh ?

> [...]

Usually disabling local APIC support solves this (sometimes with nasty
side-effects like huge perf drops or lost peripheral support).

You can quickly try to pass "noapic" to the kernel and report.

There are SiS APIC patches floating around, try looking in the mailing list
archives, there was a similar problem reported not long ago (for a SiS based
laptop).

Best regards,

LB.

  reply	other threads:[~2003-07-29 13:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 12:42 Rob Shortt
2003-07-29 13:33 ` Lionel Bouton [this message]
2003-07-29 13:51   ` Rob Shortt
2003-07-29 21:22     ` Rob Shortt

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=20030729153309.A25792@bouton.inet6-interne.fr \
    --to=lionel.bouton@inet6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@infointeractive.com \
    /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

all inboxes | Powered by JetHome®