From: "Fabio Comolli" <fabio.comolli@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "OGAWA Hirofumi" <hirofumi@mail.parknet.co.jp>,
"kernel list" <linux-kernel@vger.kernel.org>,
"Linus Torvalds" <torvalds@osdl.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: BUG: scheduling while atomic - Linux 2.6.20-rc2-ga3d89517
Date: Tue, 26 Dec 2006 12:25:24 -0500 [thread overview]
Message-ID: <b637ec0b0612260925x9c40e5akbb009e15d15c58d0@mail.gmail.com> (raw)
In-Reply-To: <20061226171531.GC7600@elf.ucw.cz>
Hi
On 12/26/06, Pavel Machek <pavel@ucw.cz> wrote:
> Hi!
>
> > some days and will let you know if the problem represents. Please note
> > that it happened only twice and I don't have any clue on how to
> > reproduce it.
> >
> > I added Pavel and Rafael to CC-list because for the first time in at
> > least six months my laptop failed to resume after suspend-to-disk
> > (userland tools) with this kernel. Guys, do you think that this
> > failure could be related to this BUG?
>
> everything is possible, but this one does not seem too likely. Is
> failure reproducible?
>
Not at all. I applied Hirofumi's patch and the problem seems to be
gone. But it was impossible to reproduce even without it: the BUG
happened only twice and the resume failure only once.
> Pavel
Fabio
>
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
>
next prev parent reply other threads:[~2006-12-26 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-24 13:53 Fabio Comolli
2006-12-24 16:58 ` OGAWA Hirofumi
2006-12-25 19:02 ` Fabio Comolli
2006-12-26 17:15 ` Pavel Machek
2006-12-26 17:25 ` Fabio Comolli [this message]
2006-12-26 17:27 ` Randy Dunlap
2006-12-26 13:07 ` [patch] sched: remove __resched_legal() and fix cond_resched_softirq() Ingo Molnar
2006-12-27 7:56 ` OGAWA Hirofumi
2006-12-27 11:16 ` Ingo Molnar
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=b637ec0b0612260925x9c40e5akbb009e15d15c58d0@mail.gmail.com \
--to=fabio.comolli@gmail.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®