From: David Brownell <david-b@pacbell.net>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.10-rc3
Date: Sat, 4 Dec 2004 19:03:55 -0800 [thread overview]
Message-ID: <200412041903.55583.david-b@pacbell.net> (raw)
> From: Martin Josefsson <gandalf () wlug ! westbo ! se>
> Date: 2004-12-04 21:42:11
>
> On Sat, 4 Dec 2004, Alex Romosan wrote:
>
> > thank you. the laptop wakes up now but i get the following when it
> > resumes (this is the output from dmesg):
> >
> > scheduling while atomic: sleepbtn.sh/0x00000001/3201
> ...
> That's an usb2.0 bug, the ehci driver sleeps when it can't sleep.
Who changed it so that context was no longer allowed to sleep???
That's a very recent change ... I've done a fair amount of testing
in previous kernels and _never_ got that message on that path.
Why was that changed? Are you sure it's not just a bug higher up
in the call stack? Classically(*), both suspend() and resume()
methods are called in contexts that can sleep, so that's a big
change I'd expect to impact other drivers too. In fact that'd
explain a lot of other messages I saw reported on the list...
- Dave
(*) Since APM days if not before.
next reply other threads:[~2004-12-05 3:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 3:03 David Brownell [this message]
2004-12-05 4:07 ` Linux 2.6.10-rc3 Benjamin Herrenschmidt
2004-12-05 12:14 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2004-12-04 0:19 Linus Torvalds
2004-12-04 9:06 ` Soeren Sonnenburg
2004-12-04 17:06 ` Alex Romosan
2004-12-04 17:24 ` Ari Pollak
2004-12-04 17:40 ` Alex Romosan
2004-12-04 19:21 ` Ari Pollak
2004-12-04 21:17 ` Martin Josefsson
2004-12-04 21:37 ` Alex Romosan
2004-12-04 21:42 ` Martin Josefsson
2004-12-04 23:48 ` Paul Ionescu
2004-12-04 21:47 ` Giridhar Pemmasani
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=200412041903.55583.david-b@pacbell.net \
--to=david-b@pacbell.net \
--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