← Back to team overview

kernel-packages team mailing list archive

[Bug 1318342] Re: Error Messages during boot...


DooMMasteR, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1318342
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Error Messages during boot...

Status in “linux” package in Ubuntu:

Bug description:
  I have some not very helpful errors during boot (which finishes fine)

  Description:	Ubuntu 14.04 LTS
  Release:	14.04

  ------------[ cut here ]------------
  WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/mm/page_alloc.c:2498 __alloc_pages_nodemask+0x2da/0xa20()
  Modules linked in:
  CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-24-generic #47-Ubuntu
  Hardware name: Notebook                         W740SU                          /W740SU                          , BIOS 4.6.5 11/27/2013
   0000000000000009 ffffffff81c01ca8 ffffffff81715ac4 0000000000000000
   ffffffff81c01ce0 ffffffff810676bd 0000000000104000 0000000000000000
   0000000000000000 0000000000000000 0000000000000000 ffffffff81c01cf0
  Call Trace:
   [<ffffffff81715ac4>] dump_stack+0x45/0x56
   [<ffffffff810676bd>] warn_slowpath_common+0x7d/0xa0
   [<ffffffff8106779a>] warn_slowpath_null+0x1a/0x20
   [<ffffffff81157b7a>] __alloc_pages_nodemask+0x2da/0xa20
   [<ffffffff81185eef>] ? alloc_vmap_area+0x6f/0x320
   [<ffffffff8118510c>] ? __insert_vmap_area+0x7c/0xd0
   [<ffffffff8171d945>] ? _raw_spin_unlock+0x5/0x30
   [<ffffffff8118614f>] ? alloc_vmap_area+0x2cf/0x320
   [<ffffffff81194f16>] alloc_page_interleave+0x46/0xa0
   [<ffffffff81195465>] alloc_pages_current+0xf5/0x160
   [<ffffffff81152b7e>] __get_free_pages+0xe/0x50
   [<ffffffff8116f40e>] kmalloc_order_trace+0x2e/0xa0
   [<ffffffff811a0041>] __kmalloc+0x181/0x190
   [<ffffffff81d520ea>] efi_bgrt_init+0xbf/0x12b
   [<ffffffff81d51862>] efi_late_init+0x9/0xb
   [<ffffffff81d34f61>] start_kernel+0x429/0x443
   [<ffffffff81d34941>] ? repair_env_string+0x5c/0x5c
   [<ffffffff81d34120>] ? early_idt_handlers+0x120/0x120
   [<ffffffff81d345ee>] x86_64_start_reservations+0x2a/0x2c
   [<ffffffff81d34733>] x86_64_start_kernel+0x143/0x152
  ---[ end trace 34eea23368c1abdb ]---

To manage notifications about this bug go to: