From: "Klaus S. Madsen" <ksm@hjernemadsen.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Regression in 2.6.25-rc3: s2ram segfaults before suspending
Date: Thu, 28 Feb 2008 20:49:20 +0100 [thread overview]
Message-ID: <20080228194920.GJ17932@hjernemadsen.org> (raw)
In-Reply-To: <47C70C01.4020605@zytor.com>
On Thu, Feb 28, 2008 at 11:31:13 -0800, H. Peter Anvin wrote:
> Klaus S. Madsen wrote:
> >>
> >>Typically, when the kernel reflects an error in VM86 mode it will update
> >>the structure in memory (in your case, the vm86plus_struct) to reflect
> >>the context. Would it be possible for you to read it out?
> >Hmm. As far as I can tell, its actually using the vm86old system call?
> >That's at least what the comment in libx86 states.
> >
> >However the contents of struct vm86_struct after the segfault is:
> >
> >(gdb) print context.vm
> >$2 = {regs = {ebx = 0, ecx = 0, edx = 0, esi = 0, edi = 0, ebp = 0,
> > eax = 20227, __null_ds = 0, __null_es = 0, __null_fs = -1071579136,
> > __null_gs = 0, orig_eax = -1, eip = 6326, cs = 49152, __csh = 0,
> > eflags = 209410, esp = 4090, ss = 256, __ssh = 0, es = 0, __esh = 0,
> > ds = 64, __dsh = 0, fs = 0, __fsh = 0, gs = 0, __gsh = 0}, flags = 0,
> > screen_bitmap = 0, cpu_type = 0, int_revectored = {__map = {0, 0, 0,0,
> > 0, 0, 0, 2147483648}}, int21_revectored = {__map = {0, 0, 0, 0, 0,
> > 0, 0, 0}}}
> >
> >My version of glibc does not seem to have vm86old declared, so I haven't
> >tried to remove the assembly code.
> >
> >Should I try to change it to use vm86, instead of vm86old?
> >
>
> Yes, that would probably be a good idea. To some degree, I guess it
> really has nothing to do with the more fundamental issue, but it's
> somewhat odd.
Ok. I tried changing the code from the assembly to do:
vm86(VM86_ENTER, vm)
instead. vm the vm86plus_struct structure fill in exactly the same way
as vm86_struct.
The output from GDB after the segfault is exactly the same as
previously, and all the fields in vm86plus_info_struct is zero.
> I'll pick apart the state above looking for fishiness as soon as I get
> back from lunch.
Great, thanks.
--
Kind regards
Klaus S. Madsen
next prev parent reply other threads:[~2008-02-28 19:54 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 22:10 Klaus S. Madsen
2008-02-27 22:19 ` Rafael J. Wysocki
2008-02-27 22:40 ` Pavel Machek
2008-02-28 6:47 ` Klaus S. Madsen
2008-02-28 7:03 ` Pavel Machek
2008-02-28 7:08 ` Klaus S. Madsen
2008-02-28 9:16 ` Ingo Molnar
2008-02-28 9:28 ` Klaus S. Madsen
2008-02-28 9:40 ` Ingo Molnar
2008-02-28 15:04 ` Klaus S. Madsen
2008-02-28 17:52 ` H. Peter Anvin
2008-02-28 19:24 ` Klaus S. Madsen
2008-02-28 19:31 ` H. Peter Anvin
2008-02-28 19:49 ` Klaus S. Madsen [this message]
2008-02-28 22:45 ` H. Peter Anvin
2008-02-29 7:00 ` Klaus S. Madsen
2008-02-29 21:05 ` H. Peter Anvin
2008-02-29 21:26 ` Ingo Molnar
2008-03-01 9:45 ` Klaus S. Madsen
2008-03-01 19:53 ` H. Peter Anvin
2008-03-03 12:17 ` Pavel Machek
2008-03-03 15:11 ` Klaus S. Madsen
2008-03-03 17:48 ` Ingo Molnar
2008-03-03 17:53 ` H. Peter Anvin
2008-03-03 20:52 ` Klaus S. Madsen
2008-03-03 20:58 ` H. Peter Anvin
2008-03-03 21:05 ` Pavel Machek
2008-03-03 21:06 ` Matthew Garrett
2008-03-03 21:06 ` Pavel Machek
2008-03-03 21:21 ` Klaus S. Madsen
2008-03-04 12:36 ` Ingo Molnar
2008-03-04 21:58 ` Klaus S. Madsen
2008-03-04 22:08 ` H. Peter Anvin
2008-03-04 23:00 ` Jeremy Fitzhardinge
2008-03-04 23:11 ` H. Peter Anvin
2008-03-04 23:21 ` Jeremy Fitzhardinge
2008-03-04 23:30 ` Matthew Garrett
2008-03-04 12:42 ` Ingo Molnar
2008-03-03 15:40 ` Rafael J. Wysocki
2008-03-03 17:10 ` H. Peter Anvin
2008-03-03 17:47 ` Pavel Machek
2008-03-03 17:50 ` H. Peter Anvin
2008-03-03 17:53 ` Ingo Molnar
2008-03-03 17:58 ` H. Peter Anvin
2008-03-01 1:18 ` Rafael J. Wysocki
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=20080228194920.GJ17932@hjernemadsen.org \
--to=ksm@hjernemadsen.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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®