On Mon, Dec 19, 2016 at 12:40 AM, Aaron Durbin wrote:
> On Sun, Dec 18, 2016 at 9:37 AM, Chauhan, Himanshu
> wrote:
>> Hi Aaron,
>>
>> I figured out the crash. It wan't because wrong load of the ROM image
>> (thanks to the nifty post_code which I
Hi Paul,
sorry for the late reply.
On 11.12.2016 22:48, Paul Menzel via coreboot wrote:
> Dear coreboot folks,
>
>
> Several devices using the Intel 945 chipset copied code for PCI reset,
> costing 200 ms of boot time.
>
> ```
> /* Force PCIRST# */
>
Dear Timothy,
Thank you for your reply.
Am Sonntag, den 11.12.2016, 15:54 -0600 schrieb Timothy Pearson:
> > Several devices using the Intel 945 chipset copied code for PCI reset,
> > costing 200 ms of boot time.
> >
> > ```
> > /* Force PCIRST# */
> >
On Sun, Dec 18, 2016 at 9:37 AM, Chauhan, Himanshu
wrote:
> Hi Aaron,
>
> I figured out the crash. It wan't because wrong load of the ROM image
> (thanks to the nifty post_code which I could trap on IO). I see that
> the page fault I am getting is in following code:
>
Hi Aaron,
I figured out the crash. It wan't because wrong load of the ROM image
(thanks to the nifty post_code which I could trap on IO). I see that
the page fault I am getting is in following code:
(gdb) list *(((0xfff81e41 - 0xfff8)-200)+0x200)
0x2001d79 is in imd_recover
Haleigh Novak wrote:
> how exactly to I use the "$ cbmem -c" command, specifically where
> exactly in boot/start up process should I call it-
Not at all. Run cbmem once you have booted Linux.
> I cant call it from the OS,
Why not?
> I haven't been able to find anything on google relating to
Thanks you for your answers, finally i use decode-dimms for check value
because i have an spb binary with others reference component very close, i
had compare with documentation.
Be careful: Only problems, the input file of decode-dimms take output
hexdump -C exactly ( with numbers line ) else
7 matches
Mail list logo