public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Ed Sweetman <ed.sweetman@wmich.edu>
Cc: Alan Cox <alan@redhat.com>,
	linux-kernel@vger.kernel.org, swsusp@lister.fornax.hu
Subject: Re: Linux 2.4.19pre5-ac3 swsusp panic
Date: 06 Apr 2002 13:04:52 -0500	[thread overview]
Message-ID: <1018116297.7477.21.camel@psuedomode> (raw)
In-Reply-To: <1018114652.7477.2.camel@psuedomode>

On Sat, 2002-04-06 at 12:37, Ed Sweetman wrote:
> 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


No, taskfile did nothing.

here's all i can see on my screen when executing a suspend I had to type
it up by hand so, hopefully no mistakes. 

I have the preempt patch and lock break patch included too. Since it had
no problem in WOLK and since it really does bring latency down to the
AA's low latency patches (since AC uses rmap I cant use those patches). 

NULL pointer dereference at virtual address 000000c3
printing eip:
c0140b3b
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c0140b3b>] Not tainted
EFLAGS: 00010293
eax: ffffffff	ebx: cf3c1c00	ecx: 00000000	edx: c1313c90
esi: 00000000	edi: 00001000	ebp: 00000001	esp: cff5de04
ds: 0018	es: 0018	ss: 0018
Process bdflush	(pid: 6, stackpage=cff5d000)
stack:	cf3c1c00 c0140bc6 cf3c1c00 c1313c90 00000000 37363534 62614938 66656463
	6a696867 c1313c90 cf265000 cff5dea4 00001000 c0140dd8 c1313c90 00001000
	00000001 c1313c90 cf265000 c014259c c1313c90 00000303 00001000 0000850f
Call Trace: [<c0140bc6>] [<c0140dd8>] [<c014259c>] [<c0137b73>] [<c011aad6>] [<c0137cd3>] [<c0128a44>] [<c012892c>] [<c0129448>] [<c011ae10>] [<c012969e>] [<c0129bd7>] [<c011f72c>] [<c0142e9a>] [<c0142dc0>] [<c0105000>] [<c0105000>] [<c01071d6>] [<c0142dc0>]
Code: 2b 90 c4 00 00 00 c1 fa 02 69 d2 c5 4e ec c4 c1 e2 0c 03 90
<3> bdflush[6] exited with preempt_count 295




  reply	other threads:[~2002-04-06 18:05 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     ` Linux 2.4.19pre5-ac3 swsusp panic Ed Sweetman
2002-04-06 18:04       ` Ed Sweetman [this message]
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=1018116297.7477.21.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox