I am getting frequent general protection fault (GPF) errors on a readynas Ultra 2which require having to press/hold reset button on front of unit to reboot. Severalpeople have complained about a similar problem on the forums and it seems to methat 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 aLogitech 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=x86Firmware: RAIDiator-x86 4.2.22BIOS: 09/08/2010 ReadyNAS-ProUltra2 V1.4Linux: Linux version 2.6.37.6.RNx86_64.2.4Disk: 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] SMPThe last message is: Fixing recursive fault but reboot is needed!You can find more details in the following text.Using RAIDiator 4.2.21Nov 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.22Feb 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] SMPFeb 13 05:38:23 nas-C1-15-CC kernel: last sysfs file: /sys/devices/platform/it87.2576/fan1_inputFeb 13 05:38:23 nas-C1-15-CC kernel: CPU 1Feb 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/0x2a0Feb 13 05:38:23 nas-C1-15-CC kernel: RSP: 0000:ffff880039c21d98 EFLAGS: 00010206Feb 13 05:38:23 nas-C1-15-CC kernel: RAX: ffff880034883aa0 RBX: ffff880039c69010 RCX: 0000000000000000Feb 13 05:38:23 nas-C1-15-CC kernel: RDX: 0000000000000000 RSI: 1400cc15c1b721a0 RDI: 00000000000000ffFeb 13 05:38:23 nas-C1-15-CC kernel: RBP: ffff880039c21df8 R08: ffff8800348cc808 R09: 0000000000000001Feb 13 05:38:23 nas-C1-15-CC kernel: R10: 0000000000000001 R11: ffff88003e2b8340 R12: ffff880034883240Feb 13 05:38:23 nas-C1-15-CC kernel: R13: 0000000000000100 R14: ffff880038ef44c0 R15: 0000000000000020Feb 13 05:38:23 nas-C1-15-CC kernel: FS: 0000000000000000(0000) GS:ffff88003fa80000(0063) knlGS:00000000f759c6b0Feb 13 05:38:23 nas-C1-15-CC kernel: CS: 0010 DS: 002b ES: 002b CR0: 000000008005003bFeb 13 05:38:23 nas-C1-15-CC kernel: CR2: 00000000080f9100 CR3: 0000000039b55000 CR4: 00000000000006e0Feb 13 05:38:23 nas-C1-15-CC kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000Feb 13 05:38:23 nas-C1-15-CC kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400Feb 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 ffff88003e196c00Feb 13 05:38:23 nas-C1-15-CC kernel: ffff88003e196c00 ffff8800348cc800 ffff88003e2b8340 0000000000000000Feb 13 05:38:23 nas-C1-15-CC kernel: ffff8800349316c0 0000000001200011 ffff8800348c0b60 ffff8800348c0b60Feb 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/0xed0Feb 13 05:38:23 nas-C1-15-CC kernel: [<ffffffff88020200>] ? do_page_fault+0x200/0x420Feb 13 05:38:23 nas-C1-15-CC kernel: [<ffffffff880336ae>] do_fork+0x9e/0x330Feb 13 05:38:23 nas-C1-15-CC kernel: [<ffffffff880b2416>] ? vfs_stat+0x16/0x20Feb 13 05:38:23 nas-C1-15-CC kernel: [<ffffffff88024ff7>] sys32_clone+0x27/0x30Feb 13 05:38:23 nas-C1-15-CC kernel: [<ffffffff88024dd5>] ia32_ptregs_common+0x25/0x50Feb 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 8bFeb 13 05:38:23 nas-C1-15-CC kernel: RIP [<ffffffff880c5535>] dup_fd+0x135/0x2a0Feb 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] SMPFeb 13 05:38:25 nas-C1-15-CC kernel: last sysfs file: /sys/devices/virtual/block/md2/md/reshape_positionFeb 13 05:38:25 nas-C1-15-CC kernel: CPU 1Feb 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/0x90Feb 13 05:38:25 nas-C1-15-CC kernel: RSP: 0000:ffff880039c21b48 EFLAGS: 00010286Feb 13 05:38:25 nas-C1-15-CC kernel: RAX: ffff880039c69008 RBX: 1400cc15c1b721a0 RCX: 0000000000000000Feb 13 05:38:25 nas-C1-15-CC kernel: RDX: 0000000000000000 RSI: ffff88003e2b82c0 RDI: 1400cc15c1b721a0Feb 13 05:38:25 nas-C1-15-CC kernel: RBP: ffff880039c21b68 R08: ffff880039c20000 R09: 0000000000000000Feb 13 05:38:25 nas-C1-15-CC kernel: R10: 0000000000000001 R11: 0000000000000000 R12: ffff88003e2b82c0Feb 13 05:38:25 nas-C1-15-CC kernel: R13: 0000000000000000 R14: ffff880038ef44c0 R15: 0000000000000008Feb 13 05:38:25 nas-C1-15-CC kernel: FS: 0000000000000000(0000) GS:ffff88003fa80000(0000) knlGS:0000000000000000Feb 13 05:38:25 nas-C1-15-CC kernel: CS: 0010 DS: 002b ES: 002b CR0: 000000008005003bFeb 13 05:38:25 nas-C1-15-CC kernel: CR2: 00000000080f9100 CR3: 0000000038e9f000 CR4: 00000000000006e0Feb 13 05:38:25 nas-C1-15-CC kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000Feb 13 05:38:25 nas-C1-15-CC kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400Feb 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 0000000000000000Feb 13 05:38:25 nas-C1-15-CC kernel: ffff880039c21ba8 ffffffff88036843 0000000000000000 ffff8800349316c0Feb 13 05:38:25 nas-C1-15-CC kernel: ffff88003e2b82c0 ffff8800349316c0 00000000000000e2 ffff880034920780Feb 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/0xd0Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88036895>] exit_files+0x45/0x50Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88037a20>] do_exit+0x190/0x770Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88002bce>] ? apic_timer_interrupt+0xe/0x20Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88035fd0>] ? kmsg_dump+0x110/0x160Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88006506>] oops_end+0xa6/0xb0Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88006606>] die+0x56/0x90Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff880040f2>] do_general_protection+0x152/0x160Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff885b48ef>] general_protection+0x1f/0x30Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff880c5535>] ? dup_fd+0x135/0x2a0Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff880c551a>] ? dup_fd+0x11a/0x2a0Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88032fea>] copy_process+0xa7a/0xed0Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88020200>] ? do_page_fault+0x200/0x420Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff880336ae>] do_fork+0x9e/0x330Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff880b2416>] ? vfs_stat+0x16/0x20Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88024ff7>] sys32_clone+0x27/0x30Feb 13 05:38:25 nas-C1-15-CC kernel: [<ffffffff88024dd5>] ia32_ptregs_common+0x25/0x50Feb 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 44Feb 13 05:38:25 nas-C1-15-CC kernel: RIP [<ffffffff880ac8c7>] filp_close+0x17/0x90Feb 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!

Are you using 100M router or switch?to fix this issue I would advise you to change network hardware to 1000M device.

HiThanks for your reply.The Ultra 2 is connected to a Linksys WRT54G v4 which has 100M ports.Is the Ultra 2 known to be unstable with this wireless router?I may have a gige switch I can use between the readynas and router...Any suggestions on a router that is known to work well with the ultra2?

Some 100M devices might be incompatible with Ultra unit,so changing it to 1000M device would be the only way to solve this issue.

I'm sorry - but the Ultra should not take a GPF because of an external device. If the ReadyNAS is susceptible to GPF because of bad or malformed packets, protocol violations or the such, the ReadyNAS has a serious bug.It might be true that using a Gb switch works around the problem, but the defect in the ReadyNAS should be resolved.I am seeing this problem also, and it is very frustrating. Not being able to rely on the stability of the ReadyNAS is a real problem. And, the fact that the ReadyNAS doesn't automatically reboot, is even worse. So, there are TWO defects:1) the defect that triggers the GPF2) the deficiency in design that prevents the ReadyNAS from rebootingpkas

Hi,I have the same problem and I was glad when I read the beginning of this thread because I too have a 100Mbit router.Unfortunately, It's actually a Netgear WNDR3700 router that is connected to my Readynas (which in turn is connected to the ISP-provided 100mbit router).So.. Should I really be getting this problem when two Netgear devices are connected to each other?I have a Netgear gigabit switch too which I could place in between the NAS and the WNDR3700, but that starts to get quite ridiculous.Thoughts?

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

de_niro
Guide
Feb 17, 2013
Are you using 100M router or switch?
to fix this issue I　would advise you to change network hardware to 1000M device.
pbarp
Aspirant
Feb 17, 2013
Hi

Thanks for your reply.

The Ultra 2 is connected to a Linksys WRT54G v4 which has 100M ports.
Is the Ultra 2 known to be unstable with this wireless router?

I may have a gige switch I can use between the readynas and router...

Any suggestions on a router that is known to work well with the ultra2?
de_niro
Guide
Feb 18, 2013
Some 100M devices might be incompatible with Ultra unit,so changing it to 1000M device would be the only way to solve this issue.
pkas
Tutor
Mar 16, 2013
I'm sorry - but the Ultra should not take a GPF because of an external device. If the ReadyNAS is susceptible to GPF because of bad or malformed packets, protocol violations or the such, the ReadyNAS has a serious bug.

It might be true that using a Gb switch works around the problem, but the defect in the ReadyNAS should be resolved.

I am seeing this problem also, and it is very frustrating. Not being able to rely on the stability of the ReadyNAS is a real problem. And, the fact that the ReadyNAS doesn't automatically reboot, is even worse. So, there are TWO defects:
1) the defect that triggers the GPF
2) the deficiency in design that prevents the ReadyNAS from rebooting

pkas
JanneK
Aspirant
Mar 17, 2013
Hi,

I have the same problem and I was glad when I read the beginning of this thread because I too have a 100Mbit router.
Unfortunately, It's actually a Netgear WNDR3700 router that is connected to my Readynas (which in turn is connected to the ISP-provided 100mbit router).

So.. Should I really be getting this problem when two Netgear devices are connected to each other?
I have a Netgear gigabit switch too which I could place in between the NAS and the WNDR3700, but that starts to get quite ridiculous.

Thoughts?
StephenB
Guru - Experienced User
Mar 17, 2013
The WNDR3700 is gigabit (http://www.netgear.com/home/products/wi ... 3700.aspx#).

I'm not sure why DeNiro is suggesting that the 100 mbit switch might be causing this problem - I haven't seen other posts on this forum that confirm that, or where GPF problems were solved by upgrading to gigabit.
de_niro
Guide
Mar 18, 2013
This issue just happens on some particular 100M devices,to make sure this ,you can connect NAS box to a 1000M device directly(such as your PC machine with 1000M NIC on- board) to check if any difference can be made
JanneK
Aspirant
Mar 18, 2013
StephenB wrote:
The WNDR3700 is gigabit (http://www.netgear.com/home/products/wirelessrouters/high-performance/wndr3700.aspx#).

That's what I said, albeit not too clearly. :)
The NAS is the only device in my home, any category, that needs to be rebooted to function properly (or in this case, at all), which is ironic in a very sad way considering the core function of the thing.
I really would like to know what the root cause to this is.
StephenB
Guru - Experienced User
Mar 18, 2013
You could try an OS reinstall from the boot menu (NOT a factory reset). Do you have a backup?

The OS reinstall shouldn't wipe your data, though it will reset the admin password and the IP configuration.

Also, you should probably start up a new thread. If you have any logged information on the details of your specific GPF, you should include it.
stoney066
Aspirant
Mar 19, 2013
I have same problem as well with Ultra 2 Plus. I've had this issue with 4.2.20, 21 and 22. I did an OS reinstall, and also had the unit RMA'd. The GPF still happens every few days. I am also using a 100Mb firewall/switch. I set the interfaces to 100Mb/Full instead of auto-neg to see if this will help (i use both NIC's for different networks). I will get a 1000Mb switch soon hopefully that takes care of the problem. If not synology/qnap here I come. When the GPF happens, NIC1 isn't usable (no ping, no gui etc), but NIC2 is so I can still reboot it from the GUI. However the unit is really really slow but at least I can still login and douche it.

Did anyone here try a 1000Mb switch yet? If so did it fix the problem?