linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Klaus S. Madsen" <ksm@hjernemadsen.org>
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 09:52:57 -0800	[thread overview]
Message-ID: <47C6F4F9.90700@zytor.com> (raw)
In-Reply-To: <20080228150444.GG17932@hjernemadsen.org>

Klaus S. Madsen wrote:
> 
> Hope this helps. 
> 

What this seems to indicate is a segfault inside VM mode that causes it 
to exit to deliver the SIGSEGV, so without more information, such as 
signal context, there isn't much to know about it.

It looks like the fault happens inside the VESA BIOS, specifically VBE 
function 3:

--------V-104F03-----------------------------
INT 10 - VESA SuperVGA BIOS - GET CURRENT VIDEO MODE
         AX = 4F03h
Return: AL = 4Fh if function supported
         AH = status
             00h successful
                 BX = video mode (see #00083,#00084)
                     bit 13: VBE/AF v1.0P accelerated video mode
                     bit 14: linear frame buffer enabled (VBE v2.0+)
                     bit 15: don't clear video memory
             01h failed
SeeAlso: AH=0Fh,AX=4E04h,AX=4F02h

... which normally would be a trivial function which only reads a couple 
of status words out of internal state and returns.

****

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?

[FWIW, that code looks like it's using assembly for no good current 
reason.  Not sure if it'd help to clean it up.]

	-hpa

  reply	other threads:[~2008-02-28 17:54 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 22:10 Regression in 2.6.25-rc3: s2ram segfaults before suspending 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 [this message]
2008-02-28 19:24           ` Klaus S. Madsen
2008-02-28 19:31             ` H. Peter Anvin
2008-02-28 19:49               ` Klaus S. Madsen
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=47C6F4F9.90700@zytor.com \
    --to=hpa@zytor.com \
    --cc=ksm@hjernemadsen.org \
    --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;
as well as URLs for NNTP newsgroup(s).