NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

pbarp's avatar
pbarp
Aspirant
Feb 17, 2013

General Protection fault (GPF) Ultra 2 hangs unresponsive

I am getting frequent general protection fault (GPF) errors on a readynas Ultra 2
which require having to press/hold reset button on front of unit to reboot. Several
people have complained about a similar problem on the forums and it seems to me
that this is a real and serious defect.

Is there a solution to the problem?
Anyone know if netgear support is actively looking into this?
Any suggestions of settings to try?
Is there a stable firmware version that does not have this problem?

The readynas is used to run the Logitech Media Server which streams music files to a
Logitech touch. About once a week it will stop responding and cannot be accessed through
the RAIDar interface. I need to press/hold reset button on front of unit to reboot.

The problem occured using RAIDiator 4.2.21 and persists after being updated to 4.2.22.

Model: ReadyNAS Ultra 2::arch=x86
Firmware: RAIDiator-x86 4.2.22
BIOS: 09/08/2010 ReadyNAS-ProUltra2 V1.4
Linux: Linux version 2.6.37.6.RNx86_64.2.4
Disk: WDC WD1003FBYX-01Y7B1 931 GB (single disk)
Addons: Logitech Media Server

[2012/07/29 15:04:34] Factory default initiated on RAIDiator 4.2.21.
[2013/02/02 19:09:44] Updated from RAIDiator 4.2.21 to 4.2.22.

Looking at the kernel log file the first message that appears when the problem occurs is:
general protection fault: 0000 [#1] SMP

The last message is:
Fixing recursive fault but reboot is needed!

You can find more details in the following text.

Using RAIDiator 4.2.21
Nov 23 07:53:23 nas-C1-15-CC kernel: general protection fault: 0000 [#1] SMP
Nov 23 07:53:26 nas-C1-15-CC kernel: general protection fault: 0000 [#2] SMP
Dec 1 16:38:09 nas-C1-15-CC kernel: general protection fault: 0000 [#1] SMP
Dec 1 16:38:12 nas-C1-15-CC kernel: general protection fault: 0000 [#2] SMP
Dec 9 03:38:08 nas-C1-15-CC kernel: general protection fault: 0000 [#1] SMP
Dec 9 03:38:11 nas-C1-15-CC kernel: general protection fault: 0000 [#2] SMP
Dec 19 05:53:23 nas-C1-15-CC kernel: general protection fault: 0000 [#1] SMP
Dec 19 05:53:26 nas-C1-15-CC kernel: general protection fault: 0000 [#2] SMP
Dec 26 19:08:08 nas-C1-15-CC kernel: general protection fault: 0000 [#1] SMP
Dec 26 19:08:11 nas-C1-15-CC kernel: general protection fault: 0000 [#2] SMP
Dec 27 04:39:32 nas-C1-15-CC kernel: general protection fault: 0000 [#3] SMP
Dec 28 04:00:08 nas-C1-15-CC kernel: general protection fault: 0000 [#4] SMP
Jan 23 06:53:23 nas-C1-15-CC kernel: general protection fault: 0000 [#1] SMP
Jan 23 06:53:25 nas-C1-15-CC kernel: general protection fault: 0000 [#2] SMP

Using RAIDiator 4.2.22
Feb 13 05:38:23 nas-C1-15-CC kernel: general protection fault: 0000 [#1] SMP
Feb 13 05:38:25 nas-C1-15-CC kernel: general protection fault: 0000 [#2] SMP



Contents of system log for a recent crash.

Feb 13 05:38:23 nas-C1-15-CC kernel: general protection fault: 0000 [#1] SMP
Feb 13 05:38:23 nas-C1-15-CC kernel: last sysfs file: /sys/devices/platform/it87.2576/fan1_input
Feb 13 05:38:23 nas-C1-15-CC kernel: CPU 1
Feb 13 05:38:23 nas-C1-15-CC kernel: Modules linked in: pvgpio nv6vpd(P)
Feb 13 05:38:23 nas-C1-15-CC kernel:
Feb 13 05:38:23 nas-C1-15-CC kernel: Pid: 20642, comm: empty_exim Tainted: P 2.6.37.6.RNx86_64.2.4 #1 NETGEAR ReadyNAS/
Feb 13 05:38:23 nas-C1-15-CC kernel: RIP: 0010:[<ffffffff880c5535>] [<ffffffff880c5535>] dup_fd+0x135/0x2a0
Feb 13 05:38:23 nas-C1-15-CC kernel: RSP: 0000:ffff880039c21d98 EFLAGS: 00010206
Feb 13 05:38:23 nas-C1-15-CC kernel: RAX: ffff880034883aa0 RBX: ffff880039c69010 RCX: 0000000000000000
Feb 13 05:38:23 nas-C1-15-CC kernel: RDX: 0000000000000000 RSI: 1400cc15c1b721a0 RDI: 00000000000000ff
Feb 13 05:38:23 nas-C1-15-CC kernel: RBP: ffff880039c21df8 R08: ffff8800348cc808 R09: 0000000000000001
Feb 13 05:38:23 nas-C1-15-CC kernel: R10: 0000000000000001 R11: ffff88003e2b8340 R12: ffff880034883240
Feb 13 05:38:23 nas-C1-15-CC kernel: R13: 0000000000000100 R14: ffff880038ef44c0 R15: 0000000000000020
Feb 13 05:38:23 nas-C1-15-CC kernel: FS: 0000000000000000(0000) GS:ffff88003fa80000(0063) knlGS:00000000f759c6b0
Feb 13 05:38:23 nas-C1-15-CC kernel: CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
Feb 13 05:38:23 nas-C1-15-CC kernel: CR2: 00000000080f9100 CR3: 0000000039b55000 CR4: 00000000000006e0
Feb 13 05:38:23 nas-C1-15-CC kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 13 05:38:23 nas-C1-15-CC kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Feb 13 05:38:23 nas-C1-15-CC kernel: Process empty_exim (pid: 20642, threadinfo ffff880039c20000, task ffff8800349316c0)
Feb 13 05:38:23 nas-C1-15-CC kernel: Stack:
Feb 13 05:38:23 nas-C1-15-CC kernel: 0000000000000000 ffff880039c21e5c ffff88003e2b82c0 ffff88003e196c00
Feb 13 05:38:23 nas-C1-15-CC kernel: ffff88003e196c00 ffff8800348cc800 ffff88003e2b8340 0000000000000000
Feb 13 05:38:23 nas-C1-15-CC kernel: ffff8800349316c0 0000000001200011 ffff8800348c0b60 ffff8800348c0b60
Feb 13 05:38:23 nas-C1-15-CC kernel: Call Trace:

Feb 13 05:38:23 nas-C1-15-CC kernel: [<ffffffff88032fea>] copy_process+0xa7a/0xed0
Feb 13 05:38:23 nas-C1-15-CC kernel: [<ffffffff88020200>] ? do_page_fault+0x200/0x420
Feb 13 05:38:23 nas-C1-15-CC kernel: [<ffffffff880336ae>] do_fork+0x9e/0x330
Feb 13 05:38:23 nas-C1-15-CC kernel: [<ffffffff880b2416>] ? vfs_stat+0x16/0x20
Feb 13 05:38:23 nas-C1-15-CC kernel: [<ffffffff88024ff7>] sys32_clone+0x27/0x30
Feb 13 05:38:23 nas-C1-15-CC kernel: [<ffffffff88024dd5>] ia32_ptregs_common+0x25/0x50
Feb 13 05:38:23 nas-C1-15-CC kernel: Code: 8b 7c 24 10 49 8b 76 10 4c 89 fa e8 46 cf 1f 00 45 85 ed 0f 84 a1 00 00 00 4c 8b 45 c8 44 89 ef 45 31 c9 41 ba 01 00 00 00 eb 13 <f0> 48 ff 46 30 49 89 30 49 ff c1 49 83 c0 08 ff cf 74 6b 48 8b
Feb 13 05:38:23 nas-C1-15-CC kernel: RIP [<ffffffff880c5535>] dup_fd+0x135/0x2a0
Feb 13 05:38:23 nas-C1-15-CC kernel: RSP <ffff880039c21d98>
Feb 13 05:38:23 nas-C1-15-CC kernel: ---[ end trace 4cd3777ecf7222ff ]---
Feb 13 05:38:25 nas-C1-15-CC kernel: general protection fault: 0000 [#2] SMP
Feb 13 05:38:25 nas-C1-15-CC kernel: last sysfs file: /sys/devices/virtual/block/md2/md/reshape_position
Feb 13 05:38:25 nas-C1-15-CC kernel: CPU 1
Feb 13 05:38:25 nas-C1-15-CC kernel: Modules linked in: pvgpio nv6vpd(P)
Feb 13 05:38:25 nas-C1-15-CC kernel:
Feb 13 05:38:25 nas-C1-15-CC kernel: Pid: 20642, comm: empty_exim Tainted: P D 2.6.37.6.RNx86_64.2.4 #1 NETGEAR ReadyNAS/
Feb 13 05:38:25 nas-C1-15-CC kernel: RIP: 0010:[<ffffffff880ac8c7>] [<ffffffff880ac8c7>] filp_close+0x17/0x90
Feb 13 05:38:25 nas-C1-15-CC kernel: RSP: 0000:ffff880039c21b48 EFLAGS: 00010286
Feb 13 05:38:25 nas-C1-15-CC kernel: RAX: ffff880039c69008 RBX: 1400cc15c1b721a0 RCX: 0000000000000000
Feb 13 05:38:25 nas-C1-15-CC kernel: RDX: 0000000000000000 RSI: ffff88003e2b82c0 RDI: 1400cc15c1b721a0
Feb 13 05:38:25 nas-C1-15-CC kernel: RBP: ffff880039c21b68 R08: ffff880039c20000 R09: 0000000000000000
Feb 13 05:38:25 nas-C1-15-CC kernel: R10: 0000000000000001 R11: 0000000000000000 R12: ffff88003e2b82c0
Feb 13 05:38:25 nas-C1-15-CC kernel: R13: 0000000000000000 R14: ffff880038ef44c0 R15: 0000000000000008
Feb 13 05:38:25 nas-C1-15-CC kernel: FS: 0000000000000000(0000) GS:ffff88003fa80000(0000) knlGS:0000000000000000
Feb 13 05:38:25 nas-C1-15-CC kernel: CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
Feb 13 05:38:25 nas-C1-15-CC kernel: CR2: 00000000080f9100 CR3: 0000000038e9f000 CR4: 00000000000006e0
Feb 13 05:38:25 nas-C1-15-CC kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 13 05:38:25 nas-C1-15-CC kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Feb 13 05:38:25 nas-C1-15-CC kernel: Process empty_exim (pid: 20642, threadinfo ffff880039c20000, task ffff8800349316c0)
Feb 13 05:38:25 nas-C1-15-CC kernel: Stack:
Feb 13 05:38:25 nas-C1-15-CC kernel: ffff88003495b480 0000000000000003 ffff88003e2b82c0 0000000000000000
Feb 13 05:38:25 nas-C1-15-CC kernel: ffff880039c21ba8 ffffffff88036843 0000000000000000 ffff8800349316c0
Feb 13 05:38:25 nas-C1-15-CC kernel: ffff88003e2b82c0 ffff8800349316c0 00000000000000e2 ffff880034920780
Feb 13 05:38:25 nas-C1-15-CC kernel: Call Trace:
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88036843>] put_files_struct+0xc3/0xd0
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88036895>] exit_files+0x45/0x50
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88037a20>] do_exit+0x190/0x770
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88002bce>] ? apic_timer_interrupt+0xe/0x20
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88035fd0>] ? kmsg_dump+0x110/0x160
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88006506>] oops_end+0xa6/0xb0
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88006606>] die+0x56/0x90
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff880040f2>] do_general_protection+0x152/0x160
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff885b48ef>] general_protection+0x1f/0x30
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff880c5535>] ? dup_fd+0x135/0x2a0
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff880c551a>] ? dup_fd+0x11a/0x2a0
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88032fea>] copy_process+0xa7a/0xed0
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88020200>] ? do_page_fault+0x200/0x420
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff880336ae>] do_fork+0x9e/0x330
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff880b2416>] ? vfs_stat+0x16/0x20
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88024ff7>] sys32_clone+0x27/0x30
Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88024dd5>] ia32_ptregs_common+0x25/0x50
Feb 13 05:38:25 nas-C1-15-CC kernel: Code: 83 80 00 00 00 48 8b 1c 24 4c 8b 64 24 08 c9 c3 66 66 66 90 55 48 89 e5 48 83 ec 20 48 89 5d e8 4c 89 65 f0 48 89 fb 4c 89 6d f8 <48> 8b 47 30 49 89 f4 48 85 c0 74 52 48 8b 47 20 48 85 c0 74 44
Feb 13 05:38:25 nas-C1-15-CC kernel: RIP [<ffffffff880ac8c7>] filp_close+0x17/0x90
Feb 13 05:38:25 nas-C1-15-CC kernel: RSP <ffff880039c21b48>
Feb 13 05:38:25 nas-C1-15-CC kernel: ---[ end trace 4cd3777ecf722300 ]---
Feb 13 05:38:25 nas-C1-15-CC kernel: Fixing recursive fault but reboot is needed!
Other Discussions
Questions

40 Replies

Replies have been turned off for this discussion
Show More
  • Andlier's avatar
    Andlier
    Tutor
    Apr 04, 2013
    I've had mine GPF issues without any addons installed. I've tried firmware 4.2.22, 4.2.21 and 4.2.20, but not 4.2.19.
  • blutarsky's avatar
    blutarsky
    Aspirant
    Apr 04, 2013
    i've had my readynas for over a year, and it has been rock solid, plugged in and working every single day without issue until a couple weeks ago when i first noticed it was unresponsive. i, too, had to resort to doing a forced reset by holding the power button and then it stayed alive for a few days before happening again. it's now happened 3-4 times. i have not upgraded the firmware or made ANY changes at all prior to this happening. the logs show the similar "general protection fault" errors related to what looks like processes "empty_exim" and "exim". again, i made no recent changes, it just started happening and sounds all too familiar with other people's sudden incidents of same.
  • Andlier's avatar
    Andlier
    Tutor
    Apr 09, 2013
    Hi again, I just got this response from tech support: "Currently this customer has one of the NIC connected to 100Mb/s port, can the customer change the 100Mb/s port to a gigabit port and see if this will resolve the problem?"

    I've now connected the readynas through a 1gbps switch to the 100mbps switch, now both ports are connected to 1gbps switches. Now I just need to wait for something that might or might not happen for several weeks... Feels a bit awkward. And what if I didn't have a 1gbps switch laying around? What would tech support do then, send me one? Someone else who has fixed it after switching to gigabit lan on one/both ports?
  • pkas's avatar
    pkas
    Tutor
    Apr 09, 2013
    I'll state again that the fix to the bug triggering the GPF is not "use a Gb switch". At best, that's a workaround; at worst, it's a waste of time. A GPF, as is any crash of an app or kernel, is a bug. And, only Netgear can _fix_ the bug; otherwise, we're left trying to work around it.
  • Andlier's avatar
    Andlier
    Tutor
    Apr 10, 2013
    pkas wrote:
    I'll state again that the fix to the bug triggering the GPF is not "use a Gb switch". At best, that's a workaround; at worst, it's a waste of time. A GPF, as is any crash of an app or kernel, is a bug. And, only Netgear can _fix_ the bug; otherwise, we're left trying to work around it.

    Totally agree, I also feel it is a waste of time, but maybe tech support want to find out if it is related to the speed of the ethernet connection somehow. I really hope they can fix this quickly. Already looking for a replacement NAS from another vendor.
  • blutarsky's avatar
    blutarsky
    Aspirant
    Apr 11, 2013
    i find it offensive that a proper company can see "use gigabit vs. 100mbit" as a fix for such a bug -- seriously? *NO* outside config, connection, variables, or any such influence should affect the device such that it triggers a GPF. and their insisting on such troubleshooting measures is insulting to us as a community. it's patently ridiculous that changing from a 100mbit to a 1000mbit router/switch could "fix" a problem like this.
  • stoney066's avatar
    stoney066
    Aspirant
    Apr 15, 2013
    I've been running on 4.2.19 for 12 days now w/o issue. Usually this breaks within a week but still not sold on it yet.
  • blutarsky's avatar
    blutarsky
    Aspirant
    Apr 29, 2013
    i'll tell ya what's even weirder for me -- i have made NO changes. no upgrades, no downgrades - still on same firmware - and as quickly as the GPF's started happening, they've now stopped. been 3+ weeks for me, as well, without a crash. very strange to have come on with seemingly no cause, and then go away with seemingly no resolution. i find this spooky odd.
  • chirpa's avatar
    chirpa
    Luminary
    Apr 29, 2013
    Does anyone have a timeframe of the crashes? Like, do they usually occur at a specific time of day?

    Since the NAS phones home in some parts of the code, I wonder if a server-side issue could have been causing it, which has been partly resolved. Automatic firmware update checks, Registration checks, language string update checks, etc.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More