public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob McCool <robm@robm.com>
To: linux-kernel@vger.kernel.org
Subject: disk lockup after suspend with RH 2.4.9-0.18 and 2.4.12
Date: Thu, 18 Oct 2001 11:34:02 -0700	[thread overview]
Message-ID: <3BCF209A.7010609@robm.com> (raw)

I have an Acer Travelmate 721 laptop on which I was running kernel 2.2.18, and have 
upgraded first to Red Hat's rawhide 2.4.9-0.18 kernel, and then to 2.4.12 from the 
sources. I put it back to 2.4.9 for the moment. I've been seeing the same behavior on both 
kernels, which I hadn't seen under 2.2.

After the disk goes into standby or sleep mode, the system gets into a wedged state. If I 
do something that hits the drive, I can hear it spin up again, but the kernel doesn't seem 
to notice. At that point, any process that tries to access the disk gets wedged. This is 
reproducible by either doing an APM suspend/resume, or by using hdparm -S1 ..., or by 
using hdparm -y ... and doing something to awaken it. After awakening, processes which 
only access the CPU are fine but anything which accesses the disk wedges. This means 
things like new network connections are accepted (but not acted upon), shell processes 
run, and the X server works for a while, but eventually all hang.

I've tried changing configuration options in the APM module, including the ones related to 
interrupts during APM operations, but nothing seems to help. I have a copy of 2.4.2 lying 
around which I didn't use because I needed the Orinoco driver, so I don't know yet if this 
problem happens with 2.4.2.

Does anybody know what might cause this, or have any pointers of how I can narrow this 
down further? If someone can point me to which part of the kernel this may be happening 
in, or give any suggestions about what might be happening and how specifically to diagnose 
it, it would help.

Thanks, Rob


                 reply	other threads:[~2001-10-18 18:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3BCF209A.7010609@robm.com \
    --to=robm@robm.com \
    --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