Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Call Traces error reported by fix.common.problems since upgrading to 6.3.1

Featured Replies

As several others have reported over the past couple of days, I'm also getting a 'Call Traces found on your server' error reported by fix.common.problems. It seems unusual that several have reported identical errors since upgrading to unRAID 6.3.1. Does anyone have any ideas? (This is a server that been running unRAID for several years without issue.) I've attached diagnostics.

 

Thanks in advance!

unraid-diagnostics-20170216-1807.zip

It's a new feature of Fix Common Problems that just happened to coincide with unRAID 6.3.

 

Here's your problem:

 

Feb 16 03:24:20 unraid kernel: crond: page allocation stalls for 19588ms, order:0, mode:0x24200ca(GFP_HIGHUSER_MOVABLE)

Feb 16 03:24:20 unraid kernel: CPU: 1 PID: 21899 Comm: crond Tainted: G          I    4.9.8-unRAID #1

Feb 16 03:24:20 unraid kernel: Hardware name: Gigabyte Technology Co., Ltd. X58A-UD3R/X58A-UD3R, BIOS FF 02/18/2011

Feb 16 03:24:20 unraid kernel: ffffc900142ebbf0 ffffffff813a34fa 0000000000000001 0000000000000000

Feb 16 03:24:20 unraid kernel: ffffc900142ebc80 ffffffff810cb3f5 024200ca810c9be8 ffffffff8193d140

Feb 16 03:24:20 unraid kernel: ffffc900142ebc18 0000000000000010 ffffc900142ebc90 ffffc900142ebc30

Feb 16 03:24:20 unraid kernel: Call Trace:

Feb 16 03:24:20 unraid kernel: [<ffffffff813a34fa>] dump_stack+0x61/0x7e

Feb 16 03:24:20 unraid kernel: [<ffffffff810cb3f5>] warn_alloc+0x102/0x116

Feb 16 03:24:20 unraid kernel: [<ffffffff810cb9ab>] __alloc_pages_nodemask+0x541/0xc71

Feb 16 03:24:20 unraid kernel: [<ffffffff813a8c3e>] ? __rb_insert_augmented+0x134/0x13f

Feb 16 03:24:20 unraid kernel: [<ffffffff81117824>] ? get_mem_cgroup_from_mm+0xa1/0xa9

Feb 16 03:24:20 unraid kernel: [<ffffffff811036de>] alloc_pages_vma+0x183/0x1f5

Feb 16 03:24:20 unraid kernel: [<ffffffff810edf40>] handle_mm_fault+0x8da/0xf96

Feb 16 03:24:20 unraid kernel: [<ffffffff810f355b>] ? do_mmap+0x37a/0x3dd

Feb 16 03:24:20 unraid kernel: [<ffffffff81042218>] __do_page_fault+0x24a/0x3ed

Feb 16 03:24:20 unraid kernel: [<ffffffff810423fe>] do_page_fault+0x22/0x27

Feb 16 03:24:20 unraid kernel: [<ffffffff8167eb98>] page_fault+0x28/0x30

 

Page allocation stalls for nearly 20 seconds. Since it's memory related I'd run Memtest for 48 hours, look for a newer BIOS and try a new kernel as soon as unRAID 6.3.2 is available.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.