Re: [Bugme-new] [Bug 36192] New: Kernel panic when boot the 2.6.39+ kernel based off of 2.6.32 kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 30 May 2011 16:01:14 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:

> On Sun, 29 May 2011 23:19:48 -0700
> Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> 
> > 
> > (switched to email.  Please respond via emailed reply-to-all, not via the
> > bugzilla web interface).
> > 
> > On Mon, 30 May 2011 02:38:33 GMT bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote:
> > 
> > > https://bugzilla.kernel.org/show_bug.cgi?id=36192
> > > 
> > >            Summary: Kernel panic when boot the 2.6.39+ kernel based off of
> > >                     2.6.32 kernel
> > >            Product: Memory Management
> > >            Version: 2.5
> > >     Kernel Version: 2.6.39+
> > >           Platform: All
> > >         OS/Version: Linux
> > >               Tree: Mainline
> > >             Status: NEW
> > >           Severity: normal
> > >           Priority: P1
> > >          Component: Page Allocator
> > >         AssignedTo: akpm@xxxxxxxxxxxxxxxxxxxx
> > >         ReportedBy: qcui@xxxxxxxxxx
> > >         Regression: Yes
> > > 
> > > 
> > > Created an attachment (id=60012)
> > >  --> (https://bugzilla.kernel.org/attachment.cgi?id=60012)
> > > kernel panic console output
> > > 
> > > When I updated the kernel from 2.6.32 to 2.6.39+ on a server with AMD
> > > Magny-Cours CPU, the server can not boot the 2.6.39+ kernel successfully. The
> > > console ouput showed 'Kernel panic - not syncing: Attempted to kill the idle
> > > task!' I have tried to set the kernel parameter idle=poll in the grub file. It
> > > still failed to reboot due to the same error. But it can reboot successfully on
> > > the server with Intel CPU. The full console output is attached.
> > > 
> > > Steps to reproduce:
> > > 1. install the 2.6.32 kernel
> > > 2. compile and install the kernel 2.6.39+
> > > 3. reboot
> > > 
> > 
> > hm, this is not good.  Might be memcg-related?
> > 
> 
> yes, and the system may be able to boot with a boot option of cgroup_disable=memory.
> but the problem happens in __alloc_pages_nodemask with NULL pointer access.
> Hmm, doesn't this imply some error in building zone/pgdat ?
> 

I want to see .config and 2.6.32's boot log (dmesg) and 2.6.39+'s boot log
if possible.

Thanks,
-Kame

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]