From: Pavel Machek <pavel@suse.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>
Subject: Re: 2.6.11-rc4-mm1: something is wrong with swsusp powerdown
Date: Tue, 1 Mar 2005 11:48:10 +0100 [thread overview]
Message-ID: <20050301104810.GF1345@elf.ucw.cz> (raw)
In-Reply-To: <20050301020722.6faffb69.akpm@osdl.org>
Hi!
> btw, suspend is a bit messy. The disk spins down. Then up. Then down
> again. And:
Yes, that's known, pm_message_t needs to become struct to solve disk
pingpong properly.
> Debug: sleeping function called from invalid context at mm/slab.c:2082
> in_atomic():0, irqs_disabled():1
> [<c010318d>] dump_stack+0x19/0x20
> [<c0111731>] __might_sleep+0x91/0x9c
> [<c01365df>] kmem_cache_alloc+0x23/0x84
> [<c0232d50>] acpi_evaluate_integer+0x3c/0xac
> [<c024b3d9>] acpi_bus_get_status+0x39/0x94
> [<c024ca99>] acpi_pci_link_set+0x16d/0x1e8
> [<c024ce65>] acpi_pci_link_resume+0x1d/0x28
> [<c024ce8a>] irqrouter_resume+0x1a/0x38
> [<c0281e3c>] sysdev_resume+0x2c/0xae
> [<c0285ea8>] device_power_up+0x8/0x11
> [<c012a873>] swsusp_suspend+0x4b/0x58
> [<c012ac35>] pm_suspend_disk+0x35/0x74
> [<c01292ea>] enter_state+0x2e/0x70
> [<c0129336>] software_suspend+0xa/0x10
> [<c024a8a7>] acpi_system_write_sleep+0x73/0x98
> [<c0149f1b>] vfs_write+0xaf/0x118
> [<c014a028>] sys_write+0x3c/0x68
> [<c0102c05>] sysenter_past_esp+0x52/0x75
ACPI problem, patches are available (s/GFP_KERNEL/GFP_ATOMIC), but Len
claims better solution is ready... OTOH he claims that for half a year
already so we may push him a bit (added to cc).
> Powering off system
> Debug: sleeping function called from invalid context at include/linux/rwsem.h:66
> in_atomic():0, irqs_disabled():1
> [<c010318d>] dump_stack+0x19/0x20
> [<c0111731>] __might_sleep+0x91/0x9c
> [<c0285872>] device_shutdown+0x16/0x82
> [<c012aa97>] power_down+0x47/0x74
> [<c012ac5a>] pm_suspend_disk+0x5a/0x74
> [<c01292ea>] enter_state+0x2e/0x70
> [<c0129336>] software_suspend+0xa/0x10
> [<c024a8a7>] acpi_system_write_sleep+0x73/0x98
> [<c0149f1b>] vfs_write+0xaf/0x118
> [<c014a028>] sys_write+0x3c/0x68
> [<c0102c05>] sysenter_past_esp+0x52/0x75
I'll look at this one.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-03-01 10:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 23:17 Pavel Machek
2005-03-01 6:38 ` Laurent Riffard
2005-03-01 9:52 ` Andrew Morton
2005-03-01 10:54 ` Pavel Machek
2005-03-01 11:12 ` Eric W. Biederman
2005-03-01 12:02 ` Pavel Machek
2005-03-01 11:08 ` Eric W. Biederman
2005-03-01 12:08 ` Pavel Machek
2005-03-01 17:33 ` Eric W. Biederman
2005-03-01 10:07 ` Andrew Morton
2005-03-01 10:21 ` Andrew Morton
2005-03-01 10:56 ` Pavel Machek
2005-03-01 20:35 ` Andrew Morton
2005-03-01 23:39 ` Pavel Machek
2005-03-01 10:48 ` Pavel Machek [this message]
2005-03-01 13:10 ` Pavel Machek
2005-03-01 13:12 ` Pavel Machek
2005-03-01 20:38 ` Andrew Morton
2005-03-02 22:57 ` Jindrich Makovicka
2005-03-03 0:30 ` Andrew Morton
2005-03-03 12:38 ` Jindrich Makovicka
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=20050301104810.GF1345@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@osdl.org \
--cc=len.brown@intel.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
Powered by JetHome