Re: [flickertcb-devel] INPAGE error after flicker execution
Status: Alpha
Brought to you by:
jonmccune
Menu
▾
▴
Re: [flickertcb-devel] INPAGE error after flicker execution
|
From: Bryan P. <pa...@mi...> - 2015-04-13 21:44:52
|
Hi Sandeep, Great, I’m glad to hear you were able to stabilize things. Thanks for reporting back. -Bryan From: SandeepR [mailto:san...@cd...] Sent: Monday, April 13, 2015 4:43 AM To: Bryan Parno Cc: 'Jonathan McCune'; fli...@li... Subject: RE: [flickertcb-devel] INPAGE error after flicker execution Hi Bryan, Including more state to be saved worked for us and the OS is now in stable state after flicker session. Some bugs we identified in code: 1. Debug.c line:56,57 RtlStringCchPrintfA and thus snprintf is assumed returning no of output characters which is not the case. 2. Ioctl.c line:111, case FLICKERDRV_CTRL_READ_OUTPUTS should return value in returnedBytesPtr. *returnedBytesPtr = min(outBufLength, MAX_OUTPUT_SIZE - offset); Thanks for your inputs. -Sandeep. From: Bryan Parno [mailto:pa...@mi...] Sent: 07 April 2015 23:38 To: Sandeep Romana Cc: Jonathan McCune; fli...@li...<mailto:fli...@li...> Subject: RE: [flickertcb-devel] INPAGE error after flicker execution Hi Sandeep, One other step you might take would be to drastically simplify the PAL you’re running. The default PAL in Flicker 0.7 contains a lot of useful basic functionality that you’ll want for a real PAL, but if you’re investigating stability issues, you might want to cut out most or all of that. In particular, most of slb_dowork is necessary for security and performing useful work, but for your purposes, I think you can cut almost all of it. Note that if you do that, you shouldn’t expect to see anything interesting in the PAL’s outputs. This would just be a way to test whether Windows resumes successfully and remains stable. -Bryan From: Sandeep Romana [mailto:san...@cd...] Sent: Monday, April 6, 2015 8:10 PM To: Bryan Parno Cc: Jonathan McCune; fli...@li...<mailto:fli...@li...> Subject: Re: [flickertcb-devel] INPAGE error after flicker execution Hi Bryan, Yes we have tried with linux version and the results seems more stable there and certainly we are on single core. We will try with 2 options you mentioned and see if we are able to resolve it. Sandeep On 07-Apr-2015, at 4:18 am, Bryan Parno <pa...@mi...<mailto:pa...@mi...>> wrote: Hi Sandeep, I don’t know of any ongoing development efforts for Flicker on Windows at this time. You could try the Linux version of Flicker and see if you get more stable results. If you’d like to make the Windows version more stable, then two things you could look at would be: 1) Does the Windows driver need to save (and the Flicker PAL need to restore) more OS state than it currently does? 2) Is the Flicker PAL inadvertently stomping on OS memory? Option 2 seems less likely, but may be worth investigating if option 1 doesn’t work. As an additional sanity check: Are you running with a single core enabled? Using more than one core can cause problems, though I’d expect them to manifest as an inability to run Flicker at all, rather than instability afterwards. -Bryan From: SandeepR [mailto:san...@cd...] Sent: Sunday, April 5, 2015 8:53 PM To: Bryan Parno; 'Jonathan McCune' Cc: fli...@li...<mailto:fli...@li...> Subject: RE: [flickertcb-devel] INPAGE error after flicker execution Hi Bryan, Thanks for your inputs. After your inputs we were able to view PCR 17 value post flicker session by directly dumping bytes at pal->outputs in WinDbg. Though the PCR 17 appeared at offset 1056 from start of outputs. Are there any plans to improve flicker for stable OS state post flicker session or inputs on doing the same. Thanks, -Sandeep From: Bryan Parno [mailto:pa...@mi...] Sent: 31 March 2015 03:34 To: SandeepR; 'Jonathan McCune' Cc: fli...@li...<mailto:fli...@li...> Subject: Re: [flickertcb-devel] INPAGE error after flicker execution Hi Sandeep, Four years ago when we were working on the Memoir project, we were able to execute Flicker on Windows 7, 32-bit and get far enough to read out the outputs. The Windows version of Flicker was not, however, tested very extensively, so it's possible that there are still some underlying instabilities. -Bryan ________________________________ From: SandeepR <san...@cd...<mailto:san...@cd...>> Sent: Monday, March 30, 2015 2:51 AM To: 'Jonathan McCune' Cc: fli...@li...<mailto:fli...@li...> Subject: Re: [flickertcb-devel] INPAGE error after flicker execution Hello Jon and list, Has anyone successfully executed flicker on Windows 7 32 bit and read the outputs into outputs file (i.e. value of PCR 17) and remained in stable OS state after flicker session. I am able to execute flicker but unable to read the output back in resumed OS state and Windows gives in-page error exceptions after flicker session. -Sandeep From: Jonathan McCune [mailto:jon...@gm...] Sent: 23 March 2015 20:59 To: SandeepR Cc: fli...@li...<mailto:fli...@li...> Subject: Re: [flickertcb-devel] INPAGE error after flicker execution Perhaps double-check that PAE-style page tables are disabled? Newer versions of Windows may make this increasingly difficult; I'm not sure. -Jon On Sun, Mar 22, 2015 at 11:55 PM, SandeepR <san...@cd...<mailto:san...@cd...>> wrote: Hi Jon, In continuation with the mail on error c0000185 after flicker execution<http://sourceforge.net/p/flickertcb/mailman/message/33589983/> I was trying to find the root of the problem. It’s an Inpage error that occurs after flicker session with various exception codes such as c0000185, c000000e etc. c0000185 being the most common. I have verified that it’s not a disk error or disk corruption from earlier crash. In my opinion where flicker goes wrong with windows is the code inside the build_resume_page_tables() as windows page tables my not be same as page tables in linux, especially the unity mapping and hence messes up with some physical addresses which later on cause this Inpage errors. Any insights on this??? -Sandeep. ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ flickertcb-devel mailing list fli...@li...<mailto:fli...@li...> https://lists.sourceforge.net/lists/listinfo/flickertcb-devel ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------------------------- |