Re: mm: OS boot failed when set command-line kmemcheck=1

2014-03-12 Thread Xishi Qiu
On 2014/2/26 18:14, Vegard Nossum wrote: > On 26 February 2014 09:43, Peter Zijlstra wrote: >> On Wed, Feb 19, 2014 at 02:24:41PM -0800, David Rientjes wrote: >>> On Wed, 19 Feb 2014, Xishi Qiu wrote: >>> Here is a warning, I don't whether it is relative to my hardware. If set "kmemchec

Re: mm: OS boot failed when set command-line kmemcheck=1

2014-02-26 Thread Peter Zijlstra
On Wed, Feb 26, 2014 at 11:14:41AM +0100, Vegard Nossum wrote: > On 26 February 2014 09:43, Peter Zijlstra wrote: > > On Wed, Feb 19, 2014 at 02:24:41PM -0800, David Rientjes wrote: > >> On Wed, 19 Feb 2014, Xishi Qiu wrote: > >> > >> > Here is a warning, I don't whether it is relative to my hardw

Re: mm: OS boot failed when set command-line kmemcheck=1

2014-02-26 Thread Vegard Nossum
On 26 February 2014 09:43, Peter Zijlstra wrote: > On Wed, Feb 19, 2014 at 02:24:41PM -0800, David Rientjes wrote: >> On Wed, 19 Feb 2014, Xishi Qiu wrote: >> >> > Here is a warning, I don't whether it is relative to my hardware. >> > If set "kmemcheck=1 nowatchdog", it can boot. >> > >> > code: >

Re: mm: OS boot failed when set command-line kmemcheck=1

2014-02-26 Thread Peter Zijlstra
On Wed, Feb 19, 2014 at 02:24:41PM -0800, David Rientjes wrote: > On Wed, 19 Feb 2014, Xishi Qiu wrote: > > > Here is a warning, I don't whether it is relative to my hardware. > > If set "kmemcheck=1 nowatchdog", it can boot. > > > > code: > > ... > > pte = kmemcheck_pte_lookup(address);

Re: mm: OS boot failed when set command-line kmemcheck=1

2014-02-26 Thread Xishi Qiu
On 2014/2/20 6:24, David Rientjes wrote: > On Wed, 19 Feb 2014, Xishi Qiu wrote: > >> Here is a warning, I don't whether it is relative to my hardware. >> If set "kmemcheck=1 nowatchdog", it can boot. >> >> code: >> ... >> pte = kmemcheck_pte_lookup(address); >> if (!pte) >>

Re: mm: OS boot failed when set command-line kmemcheck=1

2014-02-19 Thread David Rientjes
On Wed, 19 Feb 2014, Xishi Qiu wrote: > Here is a warning, I don't whether it is relative to my hardware. > If set "kmemcheck=1 nowatchdog", it can boot. > > code: > ... > pte = kmemcheck_pte_lookup(address); > if (!pte) > return false; > > WARN_ON_ONCE(in_n

Re: mm: OS boot failed when set command-line kmemcheck=1

2014-02-19 Thread Xishi Qiu
On 2014/2/19 15:49, David Rientjes wrote: > On Wed, 19 Feb 2014, Xishi Qiu wrote: > >> Hi all, >> >> CONFIG_KMEMCHECK=y and set command-line "kmemcheck=1", I find OS >> boot failed. The kernel is v3.14.0-rc3 >> >> If set "kmemcheck=1 nowatchdog", OS will boot successfully. >> > > I have automat

Re: mm: OS boot failed when set command-line kmemcheck=1

2014-02-18 Thread David Rientjes
On Wed, 19 Feb 2014, Xishi Qiu wrote: > Hi all, > > CONFIG_KMEMCHECK=y and set command-line "kmemcheck=1", I find OS > boot failed. The kernel is v3.14.0-rc3 > > If set "kmemcheck=1 nowatchdog", OS will boot successfully. > I have automated kernel boots that have both "kmemcheck=0" and "kmem

mm: OS boot failed when set command-line kmemcheck=1

2014-02-18 Thread Xishi Qiu
Hi all, CONFIG_KMEMCHECK=y and set command-line "kmemcheck=1", I find OS boot failed. The kernel is v3.14.0-rc3 If set "kmemcheck=1 nowatchdog", OS will boot successfully. Here is the boot failed log: [ 23.586826] Freeing unused kernel memory: 1160K (8800014de000 - 88000 160) [