All of lore.kernel.org
 help / color / mirror / Atom feed
From: Werner LEMBERG <wl@gnu.org>
To: linux-acpi@vger.kernel.org
Subject: ACPI and CDROM problems
Date: Sat, 21 Oct 2006 06:58:27 +0200 (CEST)	[thread overview]
Message-ID: <20061021.065827.78720699.wl@gnu.org> (raw)


I have an inspiron 6400 (running SuSE 10.0), using kernel 2.6.18
(unmodified) together with harddisk suspend.  This laptop showed
severe problems at resuming with 2.6.17 (about 1 out of 5 resumes
failed).  Now, with 2.6.18, about 1 out of 30 doesn't work.

It takes about 20 seconds, then a normal reboot happens.

Before sending various configuration and log data I wonder what I
shall specifically do to improve debugging so that you get meaningful
data in case it is a new problem (I searched the archive but doesn't
found something relevant).  In particular, which debugging flags shall
I activate -- if I enable all of them, my `/var/log/messages' file
increases by about 100k per second...  And the default settings
doesn't show anything suspicious.


    Werner

             reply	other threads:[~2006-10-21  4:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-21  4:58 Werner LEMBERG [this message]
2006-10-21 14:04 ` ACPI and CDROM problems Rafael J. Wysocki
2006-10-21 15:11   ` Werner LEMBERG
  -- strict thread matches above, loose matches on Subject: below --
2006-06-27 17:50 Werner LEMBERG

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=20061021.065827.78720699.wl@gnu.org \
    --to=wl@gnu.org \
    --cc=linux-acpi@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.