mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: axel@hh59.org, linux-kernel@vger.kernel.org,
	jfs-discussion@www-124.ibm.com
Subject: Re: [Jfs-discussion] Re: 2.5.27: Software Suspend failure / JFS errors
Date: Tue, 23 Jul 2002 16:06:57 +0100	[thread overview]
Message-ID: <20020723160657.A23708@infradead.org> (raw)
In-Reply-To: <200207230954.36039.shaggy@austin.ibm.com>; from shaggy@austin.ibm.com on Tue, Jul 23, 2002 at 09:54:35AM -0500

On Tue, Jul 23, 2002 at 09:54:35AM -0500, Dave Kleikamp wrote:
> On Sunday 21 July 2002 09:42, axel@hh59.org wrote:
> > 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.


  reply	other threads:[~2002-07-23 15:05 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     ` Christoph Hellwig [this message]
2002-07-23 16:15       ` [Jfs-discussion] " Dave Kleikamp
2002-07-23 16:20         ` Christoph Hellwig
2002-07-29 18:39       ` Pavel Machek
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=20020723160657.A23708@infradead.org \
    --to=hch@infradead.org \
    --cc=axel@hh59.org \
    --cc=jfs-discussion@www-124.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®