Re: Regression in 2.6.25-rc3: s2ram segfaults before suspending

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Ingo Molnar
Date: Thursday, February 28, 2008 - 2:16 am

* Klaus S. Madsen <ksm@hjernemadsen.org> wrote:


thanks for tracking this down. It would be nice to figure out why this 
change made a difference. Perhaps VM86 mode has some restrictions in 
what type of pagetables it can operate in - and the CPU just refuses to 
properly emulate those 16-bit instructions? (this would be very weird). 
We are trying to execute 16-bit BIOS code here, right?

which instruction is the segfault coming from - the int $0x80? So in 
vm86 mode we generated a #GPF which shows up as a SIGSEGV?

	Ingo
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Regression in 2.6.25-rc3: s2ram segfaults before suspending, Klaus S. Madsen, (Wed Feb 27, 3:10 pm)
Re: Regression in 2.6.25-rc3: s2ram segfaults before suspe ..., Rafael J. Wysocki, (Wed Feb 27, 3:19 pm)
Re: Regression in 2.6.25-rc3: s2ram segfaults before suspe ..., Ingo Molnar, (Thu Feb 28, 2:16 am)
Re: Regression in 2.6.25-rc3: s2ram segfaults before suspe ..., Rafael J. Wysocki, (Fri Feb 29, 6:18 pm)
Re: Regression in 2.6.25-rc3: s2ram segfaults before suspe ..., Jeremy Fitzhardinge, (Tue Mar 4, 4:00 pm)
Re: Regression in 2.6.25-rc3: s2ram segfaults before suspe ..., Jeremy Fitzhardinge, (Tue Mar 4, 4:21 pm)