From: Greg KH <greg@kroah.com>
To: Lukas Hejtmanek <xhejtman@mail.muni.cz>,
David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: Scheduling while atomic (2.6.10-rc3-bk13)
Date: Mon, 20 Dec 2004 10:48:14 -0800 [thread overview]
Message-ID: <20041220184814.GA21215@kroah.com> (raw)
In-Reply-To: <20041219231015.GB4166@mail.muni.cz>
On Mon, Dec 20, 2004 at 12:10:15AM +0100, Lukas Hejtmanek wrote:
> Hello,
>
> when suspending to disk I got:
> scheduling while atomic: suspenddisk.sh/0x00000001/1452
> [<c031dc81>] schedule+0x4b3/0x563
> [<c031e170>] schedule_timeout+0x5d/0xab
> [<c011e9e5>] process_timeout+0x0/0x9
> [<c011edbd>] msleep+0x2c/0x34
> [<df8303cb>] ehci_hub_resume+0xed/0x1de [ehci_hcd]
> [<c025885f>] usb_resume_device+0x80/0xc7
> [<c021dc2e>] dpm_resume+0xa2/0xa4
> [<c021dc41>] device_resume+0x11/0x1e
> [<c0130485>] finish+0x8/0x3a
> [<c013058e>] pm_suspend_disk+0x3e/0x73
> [<c012ecfa>] enter_state+0x6e/0x72
> [<c012ee18>] state_store+0xa4/0xb7
> [<c0184441>] subsys_attr_store+0x34/0x3d
> [<c01846c0>] flush_write_buffer+0x3e/0x4a
> [<c018473b>] sysfs_write_file+0x6f/0x7e
> [<c01846cc>] sysfs_write_file+0x0/0x7e
> [<c01504ec>] vfs_write+0xf4/0x12f
> [<c014fa31>] filp_close+0x52/0x96
> [<c01505f8>] sys_write+0x51/0x80
> [<c010306f>] syscall_call+0x7/0xb
David, it looks like you grab a spinlock, and then call msleep(20);
which causes this warning.
Care to fix it?
thanks,
greg k-h
next prev parent reply other threads:[~2004-12-20 18:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 23:10 Scheduling while atomic (2.6.10-rc3-bk13) Lukas Hejtmanek
2004-12-20 18:48 ` Greg KH [this message]
2004-12-20 19:52 ` David Brownell
2004-12-20 20:57 ` Lee Revell
2004-12-20 21:31 ` [linux-usb-devel] " David Brownell
2004-12-20 21:32 ` Lee Revell
2004-12-21 19:20 ` Greg KH
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=20041220184814.GA21215@kroah.com \
--to=greg@kroah.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=xhejtman@mail.muni.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