All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, support@promise.com,
	linux-ide@vger.kernel.org, apiszcz@lucidpixels.com
Subject: Re: Linux Kernel 2.6.13-rc7 (WORKS) (2.6.13, DRQ/System CRASH)
Date: Mon, 5 Sep 2005 09:32:22 +0200	[thread overview]
Message-ID: <58cb370e050905003270882298@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0508311328230.1945@p34>

On 8/31/05, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> All,
> 
> I am trying to get everyone together on this to hopefully solve a serious
> bug that I have seen on multiple machines with:
> 
> a) A Promise ATA/133 controller (ATA/100 works OK)
> b) Kernel 2.6.12 or 2.6.13 (2.6.13-rc7 appears to be OK)
> 
> The drive is a Seagate 7200.8 400GB 7200RPM 8MB cache disk.
> hde: ST3400832A, ATA DISK drive
> 
> With older kernels, if I *DO NOT ENABLE DMA* it does not crash.
> If I *ENABLE DMA* then proceed to do anything with the disk, it will
> FREEZE the box, no oops, etc, *FREEZE*.
> 
> hdparm -t /dev/hde
> mkfs.xfs -f /dev/hde1
> 
> Will freeze the box.
> 
> -------
> 
> Linux Kernel 2.6.13 final experiences the same problems as 2.6.12.5.
> 
> I have e-mailed the list quite a few times with this issue, I am surprised
> very few people run into it.
> 
> Here is the error in the logs:
> 
> Aug 31 11:30:25 p34 kernel: hde: dma_timer_expiry: dma status == 0x20
> Aug 31 11:30:25 p34 kernel: hde: DMA timeout retry
> Aug 31 11:30:25 p34 kernel: PDC202XX: Primary channel reset.
> Aug 31 11:30:25 p34 kernel: hde: timeout waiting for DMA
> Aug 31 11:30:25 p34 kernel: hde: status error: status=0x58 { DriveReady
> SeekComplete DataRequest }
> Aug 31 11:30:25 p34 kernel: hde: drive not ready for command
> Aug 31 11:30:25 p34 kernel: hde: status timeout: status=0xd0 { Busy }
> Aug 31 11:30:25 p34 kernel: PDC202XX: Primary channel reset.
> Aug 31 11:30:25 p34 kernel: hde: no DRQ after issuing MULTWRITE_EXT
> Aug 31 11:30:25 p34 kernel: ide2: reset: success
> 
> After this, the machine locks up with 2.6.13.
> 
> With 2.6.13-rc7, I have not seen this once.

Absolutely no IDE changes from -rc7 to 2.6.13 final
and I don't see anything suspicious in the patch.

You may try using git to track this regression
(but it looks like a bad drive for me).

Bartlomiej

> Can anyone offer any insight to why this is happening? I have a few
> machines with the ATA/133 controller and 400GB drives; therefore, I'd
> prefer to fix the problem rather than hooking up older, ATA/100 drives,
> just so I can run newer kernels...

      parent reply	other threads:[~2005-09-05  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-31 17:37 Linux Kernel 2.6.13-rc7 (WORKS) (2.6.13, DRQ/System CRASH) Justin Piszcz
2005-08-31 18:09 ` Justin Piszcz
2005-09-05  7:26   ` Bartlomiej Zolnierkiewicz
2005-09-05 12:29     ` Alan Cox
2005-09-05 17:23       ` Justin Piszcz
2005-09-05  7:32 ` Bartlomiej Zolnierkiewicz [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=58cb370e050905003270882298@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=akpm@osdl.org \
    --cc=apiszcz@lucidpixels.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=support@promise.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 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.