public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: Dan Hollis <goemon@anime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel 2.6.6 amd8111 apic bugs
Date: Thu, 01 Jul 2004 10:31:36 +0200	[thread overview]
Message-ID: <40E3CBE8.7060400@domdv.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0406301533030.28684-100000@sasami.anime.net>

Dan Hollis wrote:
>>>>There seem to be regular dma timeouts:
>>>>hdc: dma_timer_expiry: dma status == 0x24
>>>>hdc: DMA interrupt recovery
>>>>hdc: lost interrupt
>>>>hda: dma_timer_expiry: dma status == 0x24
>>>>hda: DMA interrupt recovery
>>>>hda: lost interrupt
>>>>Hardware:
>>>>Opteron 140, Tyan Tomcat K8S (S2850)
>>>
>>>Try disabling ACPI (in .config or boot acpi=off iirc)
>>
>>I had that problem, but not with ACPI, only when I forced APIC on.  It 
>>was on the VIA controller which uses the same driver.
> 
> 
> Turns out it was apic and not acpi at all. Booting with ACPI but noapic 
> and I no longer get any dma errors.
> 
> Is the bug in the linux apic code or a hardware flaw in the opteron cpu? 
> Or something else?
> 

 From the X86-64 patch release notes of Andi Kleen:

Reports that dual Tyan S2885 and S2880 can lock up when multiple IDE 
channels are stressed in parallel. "noapic" or "ideX=serialize" seems to 
work around it. Andre Hedrick thinks it's a generic bug/race in the IDE 
code.

Looks like you have a similar problem on a UP board.
-- 
Andreas Steinmetz                       SPAMmers use robotrap@domdv.de

      reply	other threads:[~2004-07-01  8:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 22:36 kernel 2.6.6 amd8111 apic bugs Dan Hollis
2004-07-01  8:31 ` Andreas Steinmetz [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=40E3CBE8.7060400@domdv.de \
    --to=ast@domdv.de \
    --cc=goemon@anime.net \
    --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