public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: dagit@codersbase.com
To: Pavel Machek <pavel@suse.cz>
Cc: Shaohua Li <shaohua.li@intel.com>,
	stefandoesinger@gmx.at,
	acpi-dev <acpi-devel@lists.sourceforge.net>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: S3 test tool (was : Re: Bizarre oops after suspend to RAM (was: Re: [ACPI] Resume from Suspend to RAM))
Date: Tue, 14 Jun 2005 17:50:41 -0700	[thread overview]
Message-ID: <87acls5tpa.fsf@www.codersbase.com> (raw)
In-Reply-To: <87ekb45u5a.fsf@www.codersbase.com> (dagit@codersbase.com's message of "Tue, 14 Jun 2005 17:41:05 -0700")

> As for check about the push alone causing the reboot, I removed the
> pop, and it still reboots, but to me that doesn't say that it's the
> push that does it.  It could be the next line.  I'll try to put in an
> infinite loop.

I added a loop "jmp ." right after the pushl and the machine still
reboots.  So the pushl does cause the reboot.

Hopefully, you can show me how to move the stack and I will try that
as well.

Thanks,
Jason


  reply	other threads:[~2005-06-15  0:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200506051456.44810.hugelmopf@web.de>
     [not found] ` <1117978635.6648.136.camel@tyrosine>
     [not found]   ` <200506051732.08854.stefandoesinger@gmx.at>
     [not found]     ` <1118053578.6648.142.camel@tyrosine>
2005-06-06 11:06       ` Bizarre oops after suspend to RAM (was: Re: [ACPI] Resume from Suspend to RAM) Matthew Garrett
2005-06-06 14:45         ` Pavel Machek
2005-06-06 14:54           ` Matthew Garrett
2005-06-06 15:09             ` Pavel Machek
2005-06-07 14:14               ` Martin Michlmayr
2005-06-06 15:31         ` Stefan Dösinger
2005-06-07  6:23           ` S3 test tool (was : Re: Bizarre oops after suspend to RAM (was: Re: [ACPI] Resume from Suspend to RAM)) Shaohua Li
2005-06-07 12:07             ` Martin Michlmayr
2005-06-14  7:25             ` dagit
2005-06-14  8:47               ` Matthew Garrett
2005-06-14 16:24                 ` dagit
2005-06-17 13:16                   ` Matthew Garrett
2005-06-14  9:06               ` Pavel Machek
2005-06-14 15:51                 ` dagit
2005-06-14 21:37                   ` Pavel Machek
2005-06-14 22:01                     ` dagit
2005-06-14 22:09                       ` Pavel Machek
2005-06-14 22:18                         ` dagit
2005-06-14 23:11                           ` Pavel Machek
2005-06-15  0:41                             ` dagit
2005-06-15  0:50                               ` dagit [this message]
2005-06-15 18:41                               ` 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=87acls5tpa.fsf@www.codersbase.com \
    --to=dagit@codersbase.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=pavel@suse.cz \
    --cc=shaohua.li@intel.com \
    --cc=stefandoesinger@gmx.at \
    /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