From: Pavel Machek <pavel@suse.cz>
To: dagit@codersbase.com
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: Wed, 15 Jun 2005 00:09:11 +0200 [thread overview]
Message-ID: <20050614220911.GD2172@elf.ucw.cz> (raw)
In-Reply-To: <87u0k061jx.fsf@www.codersbase.com>
Hi!
> >> > You got this wrong. It is three illegal instructions but
> >> > *nested*. Like error, error in fault handler, error in doublefault
> >> > handler.
> >>
> >> Ah. Yeah, this isn't an area I know much about :) Thanks for the
> >> correction.
> >>
> >> > Try replacing flags manipulation with any stack manipulation to see
> >> > what is wrong.
> >>
> >> Do you mean try something like this? Replace the push 0 with push
> >> 0x1234 ; push 0x1234 ; pop ; pop and try to figure out which line
> >> causes the reboot?
> >
> > Yep, try pushl $0, popl %eax; if that causes problems, something is
> > seriously wrong with stack, otherwise changing flags hurts.
>
> pushl $0, popl %eax gets the reboot. So it's changing the flags that
> is bad?
>
> What should we try next?
??? You wanted it to reboot? If not, something is wrong with
stack. Not sure whats next.
Pavel
--
teflon -- maybe it is a trademark, but it should not be.
next prev parent reply other threads:[~2005-06-14 22:09 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 [this message]
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
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=20050614220911.GD2172@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=acpi-devel@lists.sourceforge.net \
--cc=dagit@codersbase.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--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