public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Walp <faceprint@faceprint.com>
To: Allen McIntosh <mcintosh@research.telcordia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18 and 19-rc1 IDE lockup on Dell Latitude
Date: Thu, 18 Jul 2002 15:10:31 -0400	[thread overview]
Message-ID: <20020718191031.GA17575@faceprint.com> (raw)
In-Reply-To: <200207181744.NAA24845@mc-pc.research.telcordia.com>

On Thu, Jul 18, 2002 at 01:44:07PM -0400, Allen McIntosh wrote:
> 2.4.18 and 2.4.19-rc1 lock up after a suspend/resume on my Dell Latitude
> CPi D300XT.
> 
> To recreate:  Suspend (using the suspend key, by closing the top, or
> using the apm command), then hit the power button for resume.  When the
> system wakes up some IDE I/O occurs (with flashing disk light and
> audible head motion), then the disk light comes on and stays on.
> Switching consoles is possible, and typed characters echo, but
> no commands run.  The system can be powered down by holding the power
> button down for 10 seconds, but that's about it.
> 
> The system seems stable otherwise.  It stayed up all last weekend, for
> example.
> 
> If you wait in the locked state long enough, the 2.4.14 and 2.4.18 kernels
> usually (but not always) output the following to the console:
> 
> hda: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> 
> Kernel versions I've tried this on:
> 
> 2.4.14, 2.4.18 (vanilla), 2.4.18-3 (RedHat), 2.4.19-rc1, 2.4.19-rc1-ac5

I've had similar problems with my Inspiron 4100.  If I leave it idle 
long enough (i think) and come back to it, it can work, but anything 
dealing with the disk just doesn't work.  Running any command results in
some sort of IO error.  I don't have it with me, so I don't have any of 
the details handy.  I was begining to suspect hardware failure on the 
part of the drive.  

However, suspending doesn't trigger the behavior.  I regularly suspend
it with no adverse effects.  

I believe I'm currently running one of the later 2.4.19-preX releases,
been meaning to upgrate it to a -rc kernel.

Hope someone can figure this out.


-- 
Nathan Walp             || faceprint@faceprint.com
GPG Fingerprint:        ||   http://faceprint.com/
5509 6EF3 928B 2363 9B2B  DA17 3E46 2CDC 492D DB7E


      reply	other threads:[~2002-07-18 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18 17:44 2.4.18 and 19-rc1 IDE lockup on Dell Latitude Allen McIntosh
2002-07-18 19:10 ` Nathan Walp [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=20020718191031.GA17575@faceprint.com \
    --to=faceprint@faceprint.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcintosh@research.telcordia.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