On 09/02/2015 06:54 PM, Markus Trippelsdorf wrote:
On 2015.09.02 at 18:27 +0800, Xiao Guangrong wrote:
On 09/02/2015 05:38 PM, Markus Trippelsdorf wrote:
On 2015.09.02 at 17:17 +0800, Xiao Guangrong wrote:
No. PAT is of course enabled and booting is successful sometimes even
with the
On 2015.09.02 at 18:27 +0800, Xiao Guangrong wrote:
>
>
> On 09/02/2015 05:38 PM, Markus Trippelsdorf wrote:
> > On 2015.09.02 at 17:17 +0800, Xiao Guangrong wrote:
> >>>
> >>> No. PAT is of course enabled and booting is successful sometimes even
> >>> with the BUG() in allback_mtrr_type(). I
On 09/02/2015 05:38 PM, Markus Trippelsdorf wrote:
On 2015.09.02 at 17:17 +0800, Xiao Guangrong wrote:
No. PAT is of course enabled and booting is successful sometimes even
with the BUG() in allback_mtrr_type(). I suspect a setup (timing) issue.
Thanks for your confirmation.
markus@x4
On 2015.09.02 at 17:17 +0800, Xiao Guangrong wrote:
> >
> > No. PAT is of course enabled and booting is successful sometimes even
> > with the BUG() in allback_mtrr_type(). I suspect a setup (timing) issue.
>
> Thanks for your confirmation.
>
> >
> > markus@x4 linux % cat .config | grep X86_PAT
On 09/02/2015 11:50 AM, Markus Trippelsdorf wrote:
On 2015.09.02 at 06:31 +0800, Xiao Guangrong wrote:
On 09/01/2015 09:56 PM, Markus Trippelsdorf wrote:
On 2015.09.01 at 21:00 +0800, Xiao Guangrong wrote:
Did it trigger the BUG()/BUG_ON() in mtrr2protval()/fallback_mtrr_type()?
If yes,
On 09/02/2015 11:50 AM, Markus Trippelsdorf wrote:
On 2015.09.02 at 06:31 +0800, Xiao Guangrong wrote:
On 09/01/2015 09:56 PM, Markus Trippelsdorf wrote:
On 2015.09.01 at 21:00 +0800, Xiao Guangrong wrote:
Did it trigger the BUG()/BUG_ON() in mtrr2protval()/fallback_mtrr_type()?
If yes,
On 2015.09.02 at 17:17 +0800, Xiao Guangrong wrote:
> >
> > No. PAT is of course enabled and booting is successful sometimes even
> > with the BUG() in allback_mtrr_type(). I suspect a setup (timing) issue.
>
> Thanks for your confirmation.
>
> >
> > markus@x4 linux % cat .config | grep X86_PAT
On 09/02/2015 06:54 PM, Markus Trippelsdorf wrote:
On 2015.09.02 at 18:27 +0800, Xiao Guangrong wrote:
On 09/02/2015 05:38 PM, Markus Trippelsdorf wrote:
On 2015.09.02 at 17:17 +0800, Xiao Guangrong wrote:
No. PAT is of course enabled and booting is successful sometimes even
with the
On 09/02/2015 05:38 PM, Markus Trippelsdorf wrote:
On 2015.09.02 at 17:17 +0800, Xiao Guangrong wrote:
No. PAT is of course enabled and booting is successful sometimes even
with the BUG() in allback_mtrr_type(). I suspect a setup (timing) issue.
Thanks for your confirmation.
markus@x4
On 2015.09.02 at 18:27 +0800, Xiao Guangrong wrote:
>
>
> On 09/02/2015 05:38 PM, Markus Trippelsdorf wrote:
> > On 2015.09.02 at 17:17 +0800, Xiao Guangrong wrote:
> >>>
> >>> No. PAT is of course enabled and booting is successful sometimes even
> >>> with the BUG() in allback_mtrr_type(). I
On 2015.09.02 at 06:31 +0800, Xiao Guangrong wrote:
>
>
> On 09/01/2015 09:56 PM, Markus Trippelsdorf wrote:
> > On 2015.09.01 at 21:00 +0800, Xiao Guangrong wrote:
> >>
> >> Did it trigger the BUG()/BUG_ON() in mtrr2protval()/fallback_mtrr_type()?
> >> If yes, could you please print the actual
On 09/01/2015 09:56 PM, Markus Trippelsdorf wrote:
On 2015.09.01 at 21:00 +0800, Xiao Guangrong wrote:
Did it trigger the BUG()/BUG_ON() in mtrr2protval()/fallback_mtrr_type()?
If yes, could you please print the actual value out?
It is the BUG() in fallback_mtrr_type(). I changed it to a
On 2015.09.01 at 21:00 +0800, Xiao Guangrong wrote:
>
> Did it trigger the BUG()/BUG_ON() in mtrr2protval()/fallback_mtrr_type()?
> If yes, could you please print the actual value out?
It is the BUG() in fallback_mtrr_type(). I changed it to a printk and
it prints 1 for the value of mtrr.
On 09/01/2015 06:04 PM, Markus Trippelsdorf wrote:
On 2015.09.01 at 10:56 +0200, Ingo Molnar wrote:
* Markus Trippelsdorf wrote:
As I wrote in my other reply. The boot failure is nondeterministic (boot
succeeds roughly every sixth time). So the bisection and the patch is
just bogus (,but
On 2015.09.01 at 10:56 +0200, Ingo Molnar wrote:
>
> * Markus Trippelsdorf wrote:
> > As I wrote in my other reply. The boot failure is nondeterministic (boot
> > succeeds roughly every sixth time). So the bisection and the patch is
> > just bogus (,but the boot failure is real).
> >
> > Sorry.
On 09/01/2015 09:56 PM, Markus Trippelsdorf wrote:
On 2015.09.01 at 21:00 +0800, Xiao Guangrong wrote:
Did it trigger the BUG()/BUG_ON() in mtrr2protval()/fallback_mtrr_type()?
If yes, could you please print the actual value out?
It is the BUG() in fallback_mtrr_type(). I changed it to a
On 2015.09.01 at 10:56 +0200, Ingo Molnar wrote:
>
> * Markus Trippelsdorf wrote:
> > As I wrote in my other reply. The boot failure is nondeterministic (boot
> > succeeds roughly every sixth time). So the bisection and the patch is
> > just bogus (,but the boot failure
On 2015.09.02 at 06:31 +0800, Xiao Guangrong wrote:
>
>
> On 09/01/2015 09:56 PM, Markus Trippelsdorf wrote:
> > On 2015.09.01 at 21:00 +0800, Xiao Guangrong wrote:
> >>
> >> Did it trigger the BUG()/BUG_ON() in mtrr2protval()/fallback_mtrr_type()?
> >> If yes, could you please print the actual
On 09/01/2015 06:04 PM, Markus Trippelsdorf wrote:
On 2015.09.01 at 10:56 +0200, Ingo Molnar wrote:
* Markus Trippelsdorf wrote:
As I wrote in my other reply. The boot failure is nondeterministic (boot
succeeds roughly every sixth time). So the bisection and the
On 2015.09.01 at 21:00 +0800, Xiao Guangrong wrote:
>
> Did it trigger the BUG()/BUG_ON() in mtrr2protval()/fallback_mtrr_type()?
> If yes, could you please print the actual value out?
It is the BUG() in fallback_mtrr_type(). I changed it to a printk and
it prints 1 for the value of mtrr.
20 matches
Mail list logo