From: Michael Frank <mhf@linuxmail.org>
To: Patrick Mochel <mochel@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Power Management Update
Date: Thu, 11 Sep 2003 12:45:47 +0800 [thread overview]
Message-ID: <200309111245.49449.mhf@linuxmail.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0309091726050.695-100000@cherise>
Applied test5-pm1.diff to 2.6.0-test5
patch creates drivers/cpufreq/cpufreq_powersave.c, which _is_ already in -test5
S3/mem PCI LNK's do not resume.
/proc/acpi/alarm hang on wakeup
echo multiple times > /proc/acpi/alarm
Sep 11 12:41:29 mhfl2 kernel: irq 9: nobody cared!
Sep 11 12:41:29 mhfl2 kernel: Call Trace:
Sep 11 12:41:29 mhfl2 kernel: [<c010c35b>] __report_bad_irq+0x2b/0x90
Sep 11 12:41:29 mhfl2 kernel: [<c010c363>] __report_bad_irq+0x33/0x90
Sep 11 12:41:29 mhfl2 kernel: [<c010c438>] note_interrupt+0x50/0x78
Sep 11 12:41:29 mhfl2 kernel: [<c010c5b2>] do_IRQ+0x96/0xf4
Sep 11 12:41:29 mhfl2 kernel: [<c010afe8>] common_interrupt+0x18/0x20
Sep 11 12:41:29 mhfl2 kernel: [<c011de78>] do_softirq+0x48/0xb0
Sep 11 12:41:29 mhfl2 kernel: [<c010c600>] do_IRQ+0xe4/0xf4
Sep 11 12:41:29 mhfl2 kernel: [<c010afe8>] common_interrupt+0x18/0x20
Sep 11 12:41:29 mhfl2 kernel: [<c01e305d>] acpi_os_write_port+0x35/0x50
Sep 11 12:41:29 mhfl2 kernel: [<c01f852e>] acpi_hw_low_level_write+0x7e/0x11e
Sep 11 12:41:29 mhfl2 kernel: [<c01f827d>] acpi_hw_register_write+0xb9/0x1c0
Sep 11 12:41:29 mhfl2 kernel: [<c01f7f96>] acpi_set_register+0x262/0x2d0
Sep 11 12:41:29 mhfl2 kernel: [<c020cbac>] acpi_system_write_alarm+0x4f0/0x53c
Sep 11 12:41:30 mhfl2 kernel: [<c0150000>] put_dirty_page+0x68/0xec
Sep 11 12:41:30 mhfl2 kernel: [<c0147dae>] vfs_write+0x9e/0xd0
Sep 11 12:41:30 mhfl2 kernel: [<c0147e60>] sys_write+0x30/0x50
Sep 11 12:41:30 mhfl2 kernel: [<c010adc7>] syscall_call+0x7/0xb
Sep 11 12:41:30 mhfl2 kernel:
Sep 11 12:41:30 mhfl2 kernel: handlers:
Sep 11 12:41:30 mhfl2 kernel: [<c01e2ebc>] (acpi_irq+0x0/0x1c)
Sep 11 12:41:30 mhfl2 kernel: Disabling IRQ #9
Regards
Michael
next prev parent reply other threads:[~2003-09-11 4:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 0:38 Power Management Update Patrick Mochel
2003-09-10 13:04 ` Daniele Venzano
2003-09-10 18:10 ` Pavel Machek
2003-09-11 4:45 ` Michael Frank [this message]
2003-09-11 6:06 ` CaT
[not found] <3F5F9509.8080708@btopenworld.com>
2003-09-10 22:51 ` Patrick Mochel
-- strict thread matches above, loose matches on Subject: below --
2003-09-10 19:53 Subodh Shrivastava
2003-09-10 21:09 ` Patrick Mochel
2003-09-10 20:44 ` Subodh Shrivastava
2003-09-11 0:12 ` Greg KH
[not found] <20030904224112.GA26556@lps.ens.fr>
[not found] ` <Pine.LNX.4.33.0309041637440.940-100000@localhost.localdomain>
2003-09-07 9:54 ` Éric Brunet
2003-09-08 19:54 ` Patrick Mochel
2003-09-09 10:53 ` Éric Brunet
2003-09-09 15:54 ` Patrick Mochel
2003-09-01 10:57 Éric Brunet
2003-08-30 21:25 Patrick Mochel
2003-08-31 12:31 ` Felipe Alfaro Solana
2003-08-31 13:04 ` Mathieu LESNIAK
2003-09-02 18:13 ` Patrick Mochel
2003-09-02 23:50 ` Éric Brunet
2003-09-02 23:59 ` Patrick Mochel
2003-09-03 9:41 ` Mathieu LESNIAK
2003-09-03 22:41 ` Patrick Mochel
2003-09-04 9:34 ` Éric Brunet
2003-09-04 19:34 ` Patrick Mochel
[not found] ` <20031013194127.GA16791@lps.ens.fr>
2003-10-18 9:48 ` =?unknown-8bit?Q?=C9ric?= Brunet
2003-08-31 21:28 ` Pavel Machek
2003-08-31 22:15 ` Pavel Machek
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=200309111245.49449.mhf@linuxmail.org \
--to=mhf@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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.