From: Pavel Machek <pavel@suse.cz>
To: Christoph Hellwig <hch@infradead.org>,
Dave Kleikamp <shaggy@austin.ibm.com>,
axel@hh59.org, linux-kernel@vger.kernel.org,
jfs-discussion@oss.software.ibm.com
Subject: Re: [Jfs-discussion] Re: 2.5.27: Software Suspend failure / JFS errors
Date: Mon, 29 Jul 2002 18:39:38 +0000 [thread overview]
Message-ID: <20020729183937.D38@toy.ucw.cz> (raw)
In-Reply-To: <20020723160657.A23708@infradead.org>; from hch@infradead.org on Tue, Jul 23, 2002 at 04:06:57PM +0100
Hi!
> > > This oops occurred during build of gcc..
> > > Kernel 2.4.19-rc2-ac2.
> > > About the same happens with 2.5.27. I will post an oops of jfsCommit
> > > of 2.5.27 as soon as I get one.
> >
> > I just built gcc on 2.4.19-rc3 + latest JFS and didn't have a problem.
> > I'll repeat it on 2.4.19-rc2-ac2, but there shouldn't be more than a
> > comsmetic difference in the JFS code. I haven't tried 2.5.27 yet.
>
> As I read 'Software Suspend' in the subject I guess it's swsusp fault.
> Swsusp needs magic flags for kernel threads which no one has added to
> JFS yet.
Hehe. Really someone should add if (current->flags & PF_FREEZE) refrigerator();
at the right place of JFS threads. I don't have JFS installed so it is hard
for me to do that, sorry.
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2002-07-29 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 12:29 axel
2002-07-21 14:42 ` axel
2002-07-23 14:54 ` Dave Kleikamp
2002-07-23 15:06 ` [Jfs-discussion] " Christoph Hellwig
2002-07-23 16:15 ` Dave Kleikamp
2002-07-23 16:20 ` Christoph Hellwig
2002-07-29 18:39 ` Pavel Machek [this message]
2002-07-25 22:27 ` axel
2002-07-26 14:04 ` Dave Kleikamp
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=20020729183937.D38@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=axel@hh59.org \
--cc=hch@infradead.org \
--cc=jfs-discussion@oss.software.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@austin.ibm.com \
/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®