All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org, swsusp@lister.fornax.hu
Subject: Re: Linux 2.4.19pre5-ac3 swsusp panic
Date: 06 Apr 2002 12:37:27 -0500	[thread overview]
Message-ID: <1018114652.7477.2.camel@psuedomode> (raw)
In-Reply-To: <200204060109.g36199g10373@devserv.devel.redhat.com>

On WOLK 3.2 i use swsusp and it works just fine on my P4 system.  With
the ac kernel i get a panic whenever i try to suspend.  I tried
including the couple lines that i patched in WOLK 3.2's swsusp mentioned
in the swsusp mailing list and still it panics.  Perhaps it's due to the
Taskfile stuff i compiled with, i'll try it without that stuff next. 


wish i could take a screenshot of the panic


  parent reply	other threads:[~2002-04-06 17:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05 19:45 Linux 2.4.19pre5-ac3 Alan Cox
2002-04-05 23:40 ` Linux 2.4.19pre5-ac3: unresolved in radeonfb Eyal Lebedinsky
2002-04-06 20:30   ` Peter Horton
2002-04-06  1:04 ` Linux 2.4.19pre5-ac3 CaT
2002-04-06  1:09   ` Alan Cox
2002-04-06  1:12     ` CaT
2002-04-07 11:50       ` [swsusp fixes] " Pavel Machek
2002-04-06 17:37     ` Ed Sweetman [this message]
2002-04-06 18:04       ` Linux 2.4.19pre5-ac3 swsusp panic Ed Sweetman
2002-04-07  9:58         ` Pavel Machek
     [not found]           ` <1018546314.32748.9.camel@caffeine.pdx.osdl.net>
     [not found]             ` <20020412074948.GA26389@atrey.karlin.mff.cuni.cz>
     [not found]               ` <1018626124.2078.16.camel@caffeine.pdx.osdl.net>
2002-04-14 19:28                 ` Pavel Machek
2002-04-06  2:13 ` Linux 2.4.19pre5-ac3 w/swsusp oops brian
2002-04-08 21:46 ` Linux 2.4.19pre5-ac3 Mike Fedyk
2002-04-08  1:38   ` Pavel Machek
     [not found]     ` <20020409204019.GD523@stingr.net>
2002-04-09 20:53       ` 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=1018114652.7477.2.camel@psuedomode \
    --to=ed.sweetman@wmich.edu \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swsusp@lister.fornax.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.