From: Pavel Machek <pavel@suse.cz>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scheduling while atomic errors on swsusp resume
Date: Fri, 4 Mar 2005 12:26:49 +0100 [thread overview]
Message-ID: <20050304112649.GQ1345@elf.ucw.cz> (raw)
In-Reply-To: <1109811404.5918.80.camel@tyrosine>
Hi!
> Using the current Ubuntu development kernel (2.6.10 with acpi and swsusp
> stuff backported from 2.6.11), a user is getting the following trace on
> resume. Passing noapic nolapic removes the APIC error, but the rest of
> the trace is identical. This is reproducible, but only seems to happen
> on this machine. Anyone have any idea what's going on before I head off
> to try getting it reproduced with a stock kernel?
Well, those are warnings, so it still works, right? Aha, "exited with
preempt count 1" seems very wrong. Yes, please try this with
vanilla. I'm running 2.6.11 with
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
and I certainly do not get these ugly warnings.
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-04 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 0:56 Scheduling while atomic errors on swsusp resume Matthew Garrett
2005-03-04 11:26 ` Pavel Machek [this message]
2005-03-04 11:30 ` Matthew Garrett
2005-03-04 11:49 ` 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=20050304112649.GQ1345@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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