RE: [3.9-rc1] Bug in bootup code or debug code?

2013-03-20 Thread Yu, Fenghua
> From: Shaun Ruffell [mailto:sruff...@digium.com] > On Wed, Mar 20, 2013 at 04:32:14PM +, Yu, Fenghua wrote: > > > From: Shaun Ruffell [mailto:sruff...@digium.com] > > > On Tue, Mar 19, 2013 at 10:12:39PM +, Yu, Fenghua wrote: > > > > > From: Tetsuo Handa

Re: [3.9-rc1] Bug in bootup code or debug code?

2013-03-20 Thread Shaun Ruffell
On Wed, Mar 20, 2013 at 04:32:14PM +, Yu, Fenghua wrote: > > From: Shaun Ruffell [mailto:sruff...@digium.com] > > On Tue, Mar 19, 2013 at 10:12:39PM +, Yu, Fenghua wrote: > > > > From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp] > > > > H. Peter Anvin wrote: > > > Hi

RE: [3.9-rc1] Bug in bootup code or debug code?

2013-03-20 Thread Yu, Fenghua
> From: Shaun Ruffell [mailto:sruff...@digium.com] > On Tue, Mar 19, 2013 at 10:12:39PM +, Yu, Fenghua wrote: > > > From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp] > > > H. Peter Anvin wrote: > Hi Fenghua, > > I ran into the same issue on a test system I use (not a virtual >

Re: [3.9-rc1] Bug in bootup code or debug code?

2013-03-20 Thread Shaun Ruffell
On Tue, Mar 19, 2013 at 10:12:39PM +, Yu, Fenghua wrote: > > From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp] > > H. Peter Anvin wrote: > > > This is a CONFIG_DEBUG_VIRTUAL configuration, isn't it? > > > > Yes. CONFIG_MICROCODE_INTEL_EARLY=y && CONFIG_64BIT=n && > >

Re: [3.9-rc1] Bug in bootup code or debug code?

2013-03-20 Thread Shaun Ruffell
On Tue, Mar 19, 2013 at 10:12:39PM +, Yu, Fenghua wrote: From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp] H. Peter Anvin wrote: This is a CONFIG_DEBUG_VIRTUAL configuration, isn't it? Yes. CONFIG_MICROCODE_INTEL_EARLY=y CONFIG_64BIT=n CONFIG_DEBUG_VIRTUAL=y on

RE: [3.9-rc1] Bug in bootup code or debug code?

2013-03-20 Thread Yu, Fenghua
From: Shaun Ruffell [mailto:sruff...@digium.com] On Tue, Mar 19, 2013 at 10:12:39PM +, Yu, Fenghua wrote: From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp] H. Peter Anvin wrote: Hi Fenghua, I ran into the same issue on a test system I use (not a virtual machine) and

Re: [3.9-rc1] Bug in bootup code or debug code?

2013-03-20 Thread Shaun Ruffell
On Wed, Mar 20, 2013 at 04:32:14PM +, Yu, Fenghua wrote: From: Shaun Ruffell [mailto:sruff...@digium.com] On Tue, Mar 19, 2013 at 10:12:39PM +, Yu, Fenghua wrote: From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp] H. Peter Anvin wrote: Hi Fenghua, I ran

RE: [3.9-rc1] Bug in bootup code or debug code?

2013-03-20 Thread Yu, Fenghua
From: Shaun Ruffell [mailto:sruff...@digium.com] On Wed, Mar 20, 2013 at 04:32:14PM +, Yu, Fenghua wrote: From: Shaun Ruffell [mailto:sruff...@digium.com] On Tue, Mar 19, 2013 at 10:12:39PM +, Yu, Fenghua wrote: From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp]

RE: [3.9-rc1] Bug in bootup code or debug code?

2013-03-19 Thread Yu, Fenghua
> From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp] > H. Peter Anvin wrote: > > On 03/13/2013 08:22 AM, Yu, Fenghua wrote: > > >> > > >> I found the location of "hardware reset" trigger. > > >> > > >> It is __pa_symbol(_params) call, for I don't encounter > "hardware > > >> reset" if

RE: [3.9-rc1] Bug in bootup code or debug code?

2013-03-19 Thread Yu, Fenghua
From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp] H. Peter Anvin wrote: On 03/13/2013 08:22 AM, Yu, Fenghua wrote: I found the location of hardware reset trigger. It is __pa_symbol(boot_params) call, for I don't encounter hardware reset if I remove the // from

Re: [3.9-rc1] Bug in bootup code or debug code?

2013-03-13 Thread Tetsuo Handa
H. Peter Anvin wrote: > On 03/13/2013 08:22 AM, Yu, Fenghua wrote: > >> > >> I found the location of "hardware reset" trigger. > >> > >> It is __pa_symbol(_params) call, for I don't encounter "hardware > >> reset" if > >> I remove the "//" from below debug patch. > >> > >> This bug is not yet

Re: [3.9-rc1] Bug in bootup code or debug code?

2013-03-13 Thread H. Peter Anvin
This is a CONFIG_DEBUG_VIRTUAL configuration, isn't it? -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at

Re: [3.9-rc1] Bug in bootup code or debug code?

2013-03-13 Thread H. Peter Anvin
On 03/13/2013 08:22 AM, Yu, Fenghua wrote: >> >> I found the location of "hardware reset" trigger. >> >> It is __pa_symbol(_params) call, for I don't encounter "hardware >> reset" if >> I remove the "//" from below debug patch. >> >> This bug is not yet fixed as of 3.9.0-rc2-00188-g6c23cbb . >> >>

RE: [3.9-rc1] Bug in bootup code or debug code?

2013-03-13 Thread Yu, Fenghua
> -Original Message- > From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp] > Sent: Wednesday, March 13, 2013 6:24 AM > To: Yu, Fenghua; h...@linux.intel.com > Cc: linux-kernel@vger.kernel.org > Subject: Re: [3.9-rc1] Bug in bootup code or debug code? >

Re: [3.9-rc1] Bug in bootup code or debug code?

2013-03-13 Thread Tetsuo Handa
Tetsuo Handa wrote: > Tetsuo Handa wrote: > > Hello. > > > > I can boot linux-next-20130205 using kernel config at > > http://I-love.SAKURA.ne.jp/tmp/config-3.8-rc6-next-20130205 . > > But I get VMware's virtual machine kernel stack fault (hardware reset) as > > soon > > as kernel is loaded if

Re: [3.9-rc1] Bug in bootup code or debug code?

2013-03-13 Thread Tetsuo Handa
H. Peter Anvin wrote: On 03/13/2013 08:22 AM, Yu, Fenghua wrote: I found the location of hardware reset trigger. It is __pa_symbol(boot_params) call, for I don't encounter hardware reset if I remove the // from below debug patch. This bug is not yet fixed as of

Re: [3.9-rc1] Bug in bootup code or debug code?

2013-03-13 Thread Tetsuo Handa
Tetsuo Handa wrote: Tetsuo Handa wrote: Hello. I can boot linux-next-20130205 using kernel config at http://I-love.SAKURA.ne.jp/tmp/config-3.8-rc6-next-20130205 . But I get VMware's virtual machine kernel stack fault (hardware reset) as soon as kernel is loaded if

RE: [3.9-rc1] Bug in bootup code or debug code?

2013-03-13 Thread Yu, Fenghua
-Original Message- From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp] Sent: Wednesday, March 13, 2013 6:24 AM To: Yu, Fenghua; h...@linux.intel.com Cc: linux-kernel@vger.kernel.org Subject: Re: [3.9-rc1] Bug in bootup code or debug code? Tetsuo Handa wrote: Tetsuo

Re: [3.9-rc1] Bug in bootup code or debug code?

2013-03-13 Thread H. Peter Anvin
On 03/13/2013 08:22 AM, Yu, Fenghua wrote: I found the location of hardware reset trigger. It is __pa_symbol(boot_params) call, for I don't encounter hardware reset if I remove the // from below debug patch. This bug is not yet fixed as of 3.9.0-rc2-00188-g6c23cbb . ---

Re: [3.9-rc1] Bug in bootup code or debug code?

2013-03-13 Thread H. Peter Anvin
This is a CONFIG_DEBUG_VIRTUAL configuration, isn't it? -hpa -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at

[3.9-rc1] Bug in bootup code or debug code?

2013-03-04 Thread Tetsuo Handa
Tetsuo Handa wrote: > Hello. > > I can boot linux-next-20130205 using kernel config at > http://I-love.SAKURA.ne.jp/tmp/config-3.8-rc6-next-20130205 . > But I get VMware's virtual machine kernel stack fault (hardware reset) as soon > as kernel is loaded if CONFIG_DEBUG_VIRTUAL=y is added to the

[3.9-rc1] Bug in bootup code or debug code?

2013-03-04 Thread Tetsuo Handa
Tetsuo Handa wrote: Hello. I can boot linux-next-20130205 using kernel config at http://I-love.SAKURA.ne.jp/tmp/config-3.8-rc6-next-20130205 . But I get VMware's virtual machine kernel stack fault (hardware reset) as soon as kernel is loaded if CONFIG_DEBUG_VIRTUAL=y is added to the config