> 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
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
> 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
>
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 &&
> >
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
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
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
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]
> 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
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
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
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
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 .
>>
>>
> -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 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
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
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
-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
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 .
---
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
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
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
22 matches
Mail list logo