All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Wong <kernel@implode.net>
To: linux-kernel@vger.kernel.org
Subject: Re: DMA timeouts with 2.4.22-pre6
Date: Sat, 19 Jul 2003 13:05:56 -0700	[thread overview]
Message-ID: <20030719200556.GA249@gambit.implode.net> (raw)
In-Reply-To: <20030719150728.GA265@gambit.implode.net>

Thinking it may be the "fix ida dma timeout bug", I booted up 2.4.21 and 
the DMA problems were gone.

One difference in the sytems though.  With 2.4.21, I am using ACPI and APIC.  
With 2.4.22-preX, I have to set acpi=off otherwise, system interrupts get
crazy.  I tried pci=noacpi where the system is usuable for a short 
period of time and no IRQ higher than 15 are assigned.

John

On Sat, Jul 19, 2003 at 08:07:29AM -0700, John Wong wrote:
> I am having dma timeouts with my Maxtor 6Y120P0.  It is connected as the
> slave on the primary channel of the nVidia nForce2 based Asus A7N8X DX.
> 
> I did not have this problem with 2.4.21.  On the 2.4.22-pre series, I
> have encountered this problem in pre4, pre5, and pre6.  I did not try 
> earlier pre's.  In the pre2 -> pre3 change log, there was a mention of 
> fix ide dma timeout bugs.  I am wondering if this fix is causing my newly
> experienced problems.
> 
> gambit:/root# hdparm /dev/hdb
> 
> /dev/hdb:
>  multcount    = 16 (on)
>  IO_support   =  1 (32-bit)
>  unmaskirq    =  1 (on)
>  using_dma    =  1 (on)
>  keepsettings =  0 (off)
>  readonly     =  0 (off)
>  readahead    =  8 (on)
>  geometry     = 14946/255/63, sectors = 240121728, start = 0
> 
> 
> Jul 11 18:59:26 gambit kernel: hdb: dma_intr: status=0x51 { DriveReady
> SeekComplete Error }
> Jul 11 18:59:26 gambit kernel: hdb: dma_intr: error=0x40 {
> UncorrectableError }, LBAsect=98468, sector=98405
> Jul 11 18:59:26 gambit kernel: end_request: I/O error, dev 03:41 (hdb),
> sector 98405
> Jul 11 18:59:36 gambit kernel: hdb: dma_intr: status=0x51 { DriveReady
> SeekComplete Error }
> Jul 11 18:59:36 gambit kernel: hdb: dma_intr: error=0x40 {
> UncorrectableError }, LBAsect=98470, sector=98407
> Jul 11 18:59:36 gambit kernel: end_request: I/O error, dev 03:41 (hdb),
> sector 98407
> Jul 11 18:59:42 gambit kernel: hdb: dma_intr: status=0x51 { DriveReady
> SeekComplete Error }
> Jul 11 18:59:42 gambit kernel: hdb: dma_intr: error=0x40 {
> UncorrectableError }, LBAsect=98471, sector=98408
> Jul 11 18:59:42 gambit kernel: end_request: I/O error, dev 03:41 (hdb),
> sector 98408
> 
> John

  reply	other threads:[~2003-07-19 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-19 15:07 DMA timeouts with 2.4.22-pre6 John Wong
2003-07-19 20:05 ` John Wong [this message]
2003-07-22  7:36   ` 2.4.22-pre6 DMA broken? [Was: Re: DMA timeouts with 2.4.22-pre6] John Wong

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=20030719200556.GA249@gambit.implode.net \
    --to=kernel@implode.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 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.