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:49:29 +0100 [thread overview]
Message-ID: <20050304114929.GR1345@elf.ucw.cz> (raw)
In-Reply-To: <1109935857.5918.99.camel@tyrosine>
Hi!
> > 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
>
> Yeah, the resume script crashes, which is a bit of a problem. I'll get
> the user to try with a vanilla kernel, but I'm not having these problems
> with an identical kernel - it seems to be something specific to his
> setup.
Make him try it with minimal list of modules, then.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
prev parent reply other threads:[~2005-03-04 12:20 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
2005-03-04 11:30 ` Matthew Garrett
2005-03-04 11:49 ` Pavel Machek [this message]
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=20050304114929.GR1345@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