From: john stultz <johnstul@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: len.brown@intel.com, pavel@suse.cz
Subject: [BUG] sleeping function called from invalid context during resume
Date: Thu, 06 Jul 2006 20:01:36 -0700 [thread overview]
Message-ID: <1152241296.6163.4.camel@localhost> (raw)
I got the following on my laptop w/ 2.6.18-rc1.
thanks
-john
Stopping tasks:
================================================================
=======================|
pnp: Device 00:0b disabled.
ACPI: PCI interrupt for device 0000:02:01.0 disabled
ACPI: PCI interrupt for device 0000:00:1f.5 disabled
ACPI: PCI interrupt for device 0000:00:1d.7 disabled
ACPI: PCI interrupt for device 0000:00:1d.2 disabled
ACPI: PCI interrupt for device 0000:00:1d.1 disabled
ACPI: PCI interrupt for device 0000:00:1d.0 disabled
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Back to C!
BUG: sleeping function called from invalid context at mm/slab.c:2882
in_atomic():0, irqs_disabled():1
[<c0103d59>] show_trace_log_lvl+0x149/0x170
[<c01052ab>] show_trace+0x1b/0x20
[<c01052d4>] dump_stack+0x24/0x30
[<c0116e51>] __might_sleep+0xa1/0xc0
[<c0165cb5>] kmem_cache_zalloc+0xa5/0xc0
[<c0264b5a>] acpi_os_acquire_object+0x11/0x41
[<c027a898>] acpi_ut_allocate_object_desc_dbg+0xf/0x45
[<c027a926>] acpi_ut_create_internal_object_dbg+0x16/0x69
[<c0276bd3>] acpi_rs_set_srs_method_data+0x80/0xdd
[<c02762e5>] acpi_set_current_resources+0x31/0x3f
[<c02826bf>] acpi_pci_link_set+0xfc/0x1a5
[<c0282a25>] irqrouter_resume+0x52/0x73
[<c02b92aa>] __sysdev_resume+0x1a/0x90
[<c02b9367>] sysdev_resume+0x47/0x70
[<c02bf1f8>] device_power_up+0x8/0x10
[<c0142185>] suspend_enter+0x65/0x80
[<c01422a8>] enter_state+0xc8/0x1b0
[<c014242f>] state_store+0x9f/0xb0
[<c01a502e>] subsys_attr_store+0x2e/0x30
[<c01a5828>] sysfs_write_file+0xb8/0x100
[<c0169187>] vfs_write+0xa7/0x190
[<c0169bc7>] sys_write+0x47/0x70
[<c01031fd>] sysenter_past_esp+0x56/0x8d
[<b7fd3410>] 0xb7fd3410
PM: Writing back config space on device 0000:00:01.0 at offset 7 (was
2a03030, w
riting 22a03030)
PCI: Enabling device 0000:00:1d.0 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 11 (level,
low) -> IRQ
11
PCI: Setting latency timer of device 0000:00:1d.0 to 64
PM: Writing back config space on device 0000:00:1d.0 at offset f (was
100, writi
ng 10b)
next reply other threads:[~2006-07-07 3:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 3:01 john stultz [this message]
2006-07-07 3:32 ` [BUG] sleeping function called from invalid context during resume Parag Warudkar
-- strict thread matches above, loose matches on Subject: below --
2006-07-07 3:10 Brown, Len
2006-07-07 3:51 ` Andrew Morton
2006-07-07 16:32 Brown, Len
2006-07-07 19:40 ` Andrew Morton
2006-07-08 0:21 Brown, Len
2006-07-08 0:30 ` Pavel Machek
2006-07-10 5:48 Brown, Len
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=1152241296.6163.4.camel@localhost \
--to=johnstul@us.ibm.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox