Bug 727218 - [RHEL6.1][Kernel][debug] PERCPU: allocation failed, size=2048 align=8, failed to allocate new chunk
Summary: [RHEL6.1][Kernel][debug] PERCPU: allocation failed, size=2048 align=8, failed...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Prarit Bhargava
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-01 14:58 UTC by Jeff Burke
Modified: 2011-08-08 16:55 UTC (History)
4 users (show)

Fixed In Version: 2.6.32-178.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-08 15:51:31 UTC
Target Upstream Version:

Attachments (Terms of Use)
-178.el6 dmesg (55.49 KB, application/octet-stream)
2011-08-08 16:55 UTC, Prarit Bhargava 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jeff Burke 2011-08-01 14:58:30 UTC 
Description of problem:
 While testing the RHEL6.1-z kernel I came across a traceback while booting.

Version-Release number of selected component (if applicable):
2.6.32-131.11.1.el6.i686.debug

How reproducible:
Always

Actual results:

NET: Registered protocol family 10
PERCPU: allocation failed, size=2048 align=8, failed to allocate new chunk
Pid: 1828, comm: modprobe Not tainted 2.6.32-131.11.1.el6.i686.debug #1
Call Trace:
  [<c053475e>] ? pcpu_alloc+0x81e/0x850
  [<c05347aa>] ? __alloc_percpu+0xa/0x10
  [<c07fac40>] ? snmp_mib_init+0x30/0x60
  [<fd3ab180>] ? inet6_net_init+0xa0/0x130 [ipv6]
  [<c079f45c>] ? register_pernet_operations+0x5c/0xf0
  [<c084aefa>] ? mutex_lock_nested+0x3a/0x50
  [<c079f67e>] ? register_pernet_subsys+0x1e/0x30
  [<f7e5d0d9>] ? inet6_init+0xd9/0x296 [ipv6]
  [<c040303d>] ? do_one_initcall+0x2d/0x1d0
  [<f7e5d000>] ? inet6_init+0x0/0x296 [ipv6]
  [<c049ec13>] ? sys_init_module+0xb3/0x220
  [<c048f90c>] ? trace_hardirqs_on_caller+0x12c/0x170              
  [<c0409e9f>] ? sysenter_do_call+0x12/0x38                              

Expected results:
 Should not see traceback during normal boot operations.

Additional info:
Comment 4 Prarit Bhargava 2011-08-08 16:55:14 UTC 
Created attachment 517265 [details]
-178.el6 dmesg
Note You need to log in before you can comment on or make changes to this bug.