All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Leber <christian@leber.de>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>, Pavel Machek <pavel@ucw.cz>,
	linux-acpi@vger.kernel.org
Subject: Re: beeping patch for debugging acpi sleep
Date: Sun, 24 Jun 2007 22:46:29 +0200	[thread overview]
Message-ID: <20070624204629.GA28049@core> (raw)
In-Reply-To: <20070616194634.GA15953@core>

On Sat, Jun 16, 2007 at 09:46:34PM +0200, Christian Leber wrote:

> The results are a bit unclear, I took a 2.6.22-rc4 with beep.
> Logged into KDE.
> (hardware: Dell Latitude D810)
> 
> S = successfull resume
> D = had to resume 2 times, that means when pressing the power button the
> LED goes from blinking to on and after a few seconds it goes back to
> blinking, but without a beep in between; after pressing the power button
> a second time resume is successfull
> F = resume failes, NO beep
> 
> -run 1: D D F
> -run 2: D D D(some X garbadge) F
> -run 3: S S S S S S F
> -run 4: S S F
> -run 5: D F

I tracked the problem halfway down, with 2.6.20-rc1-ubuntu1 [1] it works
and with 2.6.20-rc2-ubuntu2 [2] not.

The diff is here, unfortunately the acpi changes are about 100kb.
http://debian.christian-leber.de/2.2-3.4.patch

(the problem is a bit different, it suspends, when trying to resume it
goes back to suspend and when i try again it's dead)

For some reason that i don't get vanilla 2.6.20-rc1 doesn't boot because
ata_piix doesn't work "PCI: Unable to reserve I/O region...." no remote
idea why it works with the ubuntu kernel.
So i can't bisect it.


Christian Leber


[1] https://launchpad.net/ubuntu/+source/linux-source-2.6.20/2.6.20-2.2
[2] https://launchpad.net/ubuntu/+source/linux-source-2.6.20/2.6.20-3.4

-- 
http://rettetdieti.vde-uni-mannheim.de/


  reply	other threads:[~2007-06-24 20:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 21:37 [BUG] acpi double resume and fail Christian Leber
2007-05-18 22:45 ` Andrew Morton
2007-05-19 19:42   ` Christian Leber
2007-05-20 20:01 ` Pavel Machek
     [not found]   ` <20070602182014.GB29546@core>
2007-06-09 13:08     ` beeping patch for debugging acpi sleep Pavel Machek
2007-06-09 13:16       ` Jan-Benedict Glaw
2007-06-09 22:54         ` Pavel Machek
2007-06-09 23:27           ` Nigel Cunningham
2007-06-09 23:35             ` Pavel Machek
2007-06-11  8:56       ` Stefan Seyfried
2007-06-11 16:50         ` Pavel Machek
2007-06-11 19:00       ` Andrew Morton
2007-06-11 19:49         ` Matthieu CASTET
2007-06-12 15:12           ` Pavel Machek
2007-06-13 17:58             ` Stefan Seyfried
2007-06-11 21:26         ` Pavel Machek
2007-06-11 22:42         ` Nigel Cunningham
2007-06-12 12:11           ` Rafael J. Wysocki
2007-06-13  1:17             ` Nigel Cunningham
2007-06-13  8:24               ` Pavel Machek
2007-06-13 11:32                 ` Nigel Cunningham
2007-06-13 12:28                   ` Pavel Machek
2007-06-13 12:40                     ` Rafael J. Wysocki
2007-06-16 19:46       ` Christian Leber
2007-06-24 20:46         ` Christian Leber [this message]
2007-06-28 14:08           ` Pavel Machek
2007-08-12 21:37             ` Christian Leber
2007-05-22 22:16 ` [BUG] acpi double resume and fail Mark Lord

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=20070624204629.GA28049@core \
    --to=christian@leber.de \
    --cc=akpm@osdl.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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.