Re: hdb: dma_timer_expiry: dma status == 0x64 [2.5.69]

From: Danny ter Haar (dth@ncc1701.cistron.net)
Date: Wed May 14 2003 - 09:14:13 EST

Next message: Maciej Soltysiak: "Re: hdb: dma_timer_expiry: dma status == 0x64 [2.5.69]"
Previous message: Alex Riesen: "Re: 2.5.69+bk: oops in apmd after waking up from suspend mode"
In reply to: Zephaniah E. Hull: "Re: hdb: dma_timer_expiry: dma status == 0x64 [2.5.69]"
Next in thread: Maciej Soltysiak: "Re: hdb: dma_timer_expiry: dma status == 0x64 [2.5.69]"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Zephaniah E. Hull <warp@babylon.d2dc.net> wrote:
>Happens only with heavy disk IO, running 2.5.69-mm3, happened with a few
>earlier kernels and sadly I don't remember which kernel it started on.

I had similar problems on a uni-processor machine.

Try this:

Disable IO-APIC in the kernel

EG:
Processor type and features ->
[*] Local APIC support on uniprocessors
[ ] IO-APIC support on uniprocessors

This way i don't experience these errors anymore.
I can only guess what causes these errors.

Danny

-- Miguel | "I can't tell if I have worked all my life or if de Icaza | I have never worked a single day of my life,"

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: Maciej Soltysiak: "Re: hdb: dma_timer_expiry: dma status == 0x64 [2.5.69]"
Previous message: Alex Riesen: "Re: 2.5.69+bk: oops in apmd after waking up from suspend mode"
In reply to: Zephaniah E. Hull: "Re: hdb: dma_timer_expiry: dma status == 0x64 [2.5.69]"
Next in thread: Maciej Soltysiak: "Re: hdb: dma_timer_expiry: dma status == 0x64 [2.5.69]"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu May 15 2003 - 22:00:52 EST