June 4, 201214 yr I'm still seeing a Kernel Oops sometimes during system powerdown. ... Jun 3 03:58:21 Tower rc.unRAID[9093]: Stopping the Array Jun 3 03:58:21 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at (null) Jun 3 03:58:21 Tower kernel: IP: [<c1038b65>] queue_delayed_work_on+0x33/0xbf Jun 3 03:58:21 Tower kernel: *pdpt = 0000000030f4b001 *pde = 0000000000000000 Jun 3 03:58:21 Tower kernel: Oops: 0000 [#1] SMP Jun 3 03:58:21 Tower kernel: Modules linked in: md_mod xor acpi_cpufreq mperf i2c_i801 i2c_core ahci libahci e1000e mpt2sas scsi_transport_sas raid_class Jun 3 03:58:21 Tower kernel: Jun 3 03:58:21 Tower kernel: Pid: 9092, comm: sync Not tainted 3.0.31-unRAID #1 /DH55TC Jun 3 03:58:21 Tower kernel: EIP: 0060:[<c1038b65>] EFLAGS: 00010246 CPU: 3 Jun 3 03:58:21 Tower kernel: EIP is at queue_delayed_work_on+0x33/0xbf Jun 3 03:58:21 Tower kernel: EAX: f86ce138 EBX: ffffffff ECX: f86ce134 EDX: 00000000 Jun 3 03:58:21 Tower kernel: ESI: 00000000 EDI: f86ce134 EBP: f0e77ea8 ESP: f0e77e9c Jun 3 03:58:21 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Jun 3 03:58:21 Tower kernel: Process sync (pid: 9092, ti=f0e76000 task=f2815960 task.ti=f0e76000) Jun 3 03:58:21 Tower kernel: Stack: Jun 3 03:58:21 Tower kernel: f86be000 f6f3cad4 f6f3ca80 f0e77eb4 c1038fe2 0000000a f0e77f18 c10d9405 Jun 3 03:58:21 Tower kernel: c109d617 00000012 00000000 ee745f88 00004e58 03dbeb30 00000000 00000010 Jun 3 03:58:21 Tower kernel: f6f3ca98 00000012 00000004 f86be000 00000fbe 00000000 edf35000 f37c4ce0 Jun 3 03:58:21 Tower kernel: Call Trace: Jun 3 03:58:21 Tower kernel: [<c1038fe2>] queue_delayed_work+0x1b/0x1e Jun 3 03:58:21 Tower kernel: [<c10d9405>] do_journal_end+0x747/0x92a Jun 3 03:58:21 Tower kernel: [<c109d617>] ? unmap_underlying_metadata+0x2e/0x2e Jun 3 03:58:21 Tower kernel: [<c10d9643>] journal_end_sync+0x5b/0x63 Jun 3 03:58:21 Tower kernel: [<c10cd5de>] reiserfs_sync_fs+0x32/0x51 Jun 3 03:58:21 Tower kernel: [<c109b31f>] __sync_filesystem+0x53/0x65 Jun 3 03:58:21 Tower kernel: [<c109b341>] sync_one_sb+0x10/0x12 Jun 3 03:58:21 Tower kernel: [<c1081d31>] iterate_supers+0x52/0x92 Jun 3 03:58:21 Tower kernel: [<c109b331>] ? __sync_filesystem+0x65/0x65 Jun 3 03:58:21 Tower kernel: [<c109b367>] sys_sync+0x24/0x4b Jun 3 03:58:21 Tower kernel: [<c130ed05>] syscall_call+0x7/0xb Jun 3 03:58:21 Tower kernel: Code: d6 53 89 c3 f0 0f ba 29 00 19 d2 31 c0 85 d2 0f 85 9d 00 00 00 83 79 10 00 74 04 0f 0b eb fe 8d 41 04 39 41 04 74 04 0f 0b eb fe <f6> 06 02 b8 08 00 00 00 75 19 89 c8 e8 ca e4 ff ff 85 c0 74 08 Jun 3 03:58:21 Tower kernel: EIP: [<c1038b65>] queue_delayed_work_on+0x33/0xbf SS:ESP 0068:f0e77e9c Jun 3 03:58:21 Tower kernel: CR2: 0000000000000000 Jun 3 03:58:21 Tower kernel: ---[ end trace 10adb049410de448 ]--- Jun 3 03:58:21 Tower kernel: mdcmd (150): stop ... syslog-20120603-035825.txt.zip
June 4, 201214 yr I'm still seeing a Kernel Oops sometimes during system powerdown. ... Jun 3 03:58:21 Tower rc.unRAID[9093]: Stopping the Array Jun 3 03:58:21 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at (null) Jun 3 03:58:21 Tower kernel: IP: [<c1038b65>] queue_delayed_work_on+0x33/0xbf Jun 3 03:58:21 Tower kernel: *pdpt = 0000000030f4b001 *pde = 0000000000000000 Jun 3 03:58:21 Tower kernel: Oops: 0000 [#1] SMP Jun 3 03:58:21 Tower kernel: Modules linked in: md_mod xor acpi_cpufreq mperf i2c_i801 i2c_core ahci libahci e1000e mpt2sas scsi_transport_sas raid_class Jun 3 03:58:21 Tower kernel: Jun 3 03:58:21 Tower kernel: Pid: 9092, comm: sync Not tainted 3.0.31-unRAID #1 /DH55TC Jun 3 03:58:21 Tower kernel: EIP: 0060:[<c1038b65>] EFLAGS: 00010246 CPU: 3 Jun 3 03:58:21 Tower kernel: EIP is at queue_delayed_work_on+0x33/0xbf Jun 3 03:58:21 Tower kernel: EAX: f86ce138 EBX: ffffffff ECX: f86ce134 EDX: 00000000 Jun 3 03:58:21 Tower kernel: ESI: 00000000 EDI: f86ce134 EBP: f0e77ea8 ESP: f0e77e9c Jun 3 03:58:21 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Jun 3 03:58:21 Tower kernel: Process sync (pid: 9092, ti=f0e76000 task=f2815960 task.ti=f0e76000) Jun 3 03:58:21 Tower kernel: Stack: Jun 3 03:58:21 Tower kernel: f86be000 f6f3cad4 f6f3ca80 f0e77eb4 c1038fe2 0000000a f0e77f18 c10d9405 Jun 3 03:58:21 Tower kernel: c109d617 00000012 00000000 ee745f88 00004e58 03dbeb30 00000000 00000010 Jun 3 03:58:21 Tower kernel: f6f3ca98 00000012 00000004 f86be000 00000fbe 00000000 edf35000 f37c4ce0 Jun 3 03:58:21 Tower kernel: Call Trace: Jun 3 03:58:21 Tower kernel: [<c1038fe2>] queue_delayed_work+0x1b/0x1e Jun 3 03:58:21 Tower kernel: [<c10d9405>] do_journal_end+0x747/0x92a Jun 3 03:58:21 Tower kernel: [<c109d617>] ? unmap_underlying_metadata+0x2e/0x2e Jun 3 03:58:21 Tower kernel: [<c10d9643>] journal_end_sync+0x5b/0x63 Jun 3 03:58:21 Tower kernel: [<c10cd5de>] reiserfs_sync_fs+0x32/0x51 Jun 3 03:58:21 Tower kernel: [<c109b31f>] __sync_filesystem+0x53/0x65 Jun 3 03:58:21 Tower kernel: [<c109b341>] sync_one_sb+0x10/0x12 Jun 3 03:58:21 Tower kernel: [<c1081d31>] iterate_supers+0x52/0x92 Jun 3 03:58:21 Tower kernel: [<c109b331>] ? __sync_filesystem+0x65/0x65 Jun 3 03:58:21 Tower kernel: [<c109b367>] sys_sync+0x24/0x4b Jun 3 03:58:21 Tower kernel: [<c130ed05>] syscall_call+0x7/0xb Jun 3 03:58:21 Tower kernel: Code: d6 53 89 c3 f0 0f ba 29 00 19 d2 31 c0 85 d2 0f 85 9d 00 00 00 83 79 10 00 74 04 0f 0b eb fe 8d 41 04 39 41 04 74 04 0f 0b eb fe <f6> 06 02 b8 08 00 00 00 75 19 89 c8 e8 ca e4 ff ff 85 c0 74 08 Jun 3 03:58:21 Tower kernel: EIP: [<c1038b65>] queue_delayed_work_on+0x33/0xbf SS:ESP 0068:f0e77e9c Jun 3 03:58:21 Tower kernel: CR2: 0000000000000000 Jun 3 03:58:21 Tower kernel: ---[ end trace 10adb049410de448 ]--- Jun 3 03:58:21 Tower kernel: mdcmd (150): stop ... This is a known issue, hopefully fixed in -rc4.
June 4, 201214 yr Author This is a known issue, hopefully fixed in -rc4. Okay, great. I know that some 'Kernel Oops' issues had been addressed in earlier releases - I didn't know that there was still an outstanding issue.
June 5, 201214 yr Tom, is this the original one (oops) I had with the Xeon processor? I never saw it resolved. I got around it by virtualizing unRAID, which was the ultimate goal for me. But I wanted to make sure should in a dr situation I could move back to booting unRAID as physical. But never saw the oops error resolved.
Archived
This topic is now archived and is closed to further replies.