Since there isn't a 4.5.3 forum. I tripped across this just in the log. I'm not sure what I was doing at the time. I assume since it says its a BUG, it really is a BUG?

 

Mar 18 20:35:51 Serenity kernel: BUG: unable to handle kernel paging request at f83cf000

Mar 18 20:35:51 Serenity kernel: IP: [] md_cmd_proc_read+0x41/0x54 [md_mod]

Mar 18 20:35:51 Serenity kernel: *pdpt = 0000000001443001 *pde = 0000000037410067 *pte = 0000000000000000

Mar 18 20:35:51 Serenity kernel: Oops: 0000 [#1] SMP

Mar 18 20:35:51 Serenity kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.5/host13/target13:0:0/13:0:0:0/block/sdf/removable

Mar 18 20:35:51 Serenity kernel: Modules linked in: md_mod xor ata_piix r8169 sata_sil24 sata_mv

Mar 18 20:35:51 Serenity kernel:

Mar 18 20:35:51 Serenity kernel: Pid: 3077, comm: emhttp Not tainted (2.6.32.9-unRAID #1) C2SEA

Mar 18 20:35:51 Serenity kernel: EIP: 0060:[] EFLAGS: 00210203 CPU: 1

Mar 18 20:35:51 Serenity kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]

Mar 18 20:35:51 Serenity kernel: EAX: c2a5bf38 EBX: fffff83b ECX: 3fffef76 EDX: fffff83b

Mar 18 20:35:51 Serenity kernel: ESI: f83cf000 EDI: ca35ba60 EBP: c2a5bf04 ESP: c2a5bef4

Mar 18 20:35:51 Serenity kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Mar 18 20:35:51 Serenity kernel: Process emhttp (pid: 3077, ti=c2a5a000 task=f7779810 task.ti=c2a5a000)

Mar 18 20:35:51 Serenity kernel: Stack:

Mar 18 20:35:51 Serenity kernel: c2a5bf38 f83c5883 00000000 ca358000 c2a5bf4c c109d56d 00000400 c2a5bf3c

Mar 18 20:35:51 Serenity kernel: <0> 00000000 00000400 00000000 00000400 b77a1000 f6dadf00 00000000 f6dadf00

Mar 18 20:35:51 Serenity kernel: <0> 00000400 ca358000 00000001 f6dadf00 c109d462 fffffffb c2a5bf70 c1099eea

Mar 18 20:35:51 Serenity kernel: Call Trace:

Mar 18 20:35:51 Serenity kernel: [] ? md_cmd_proc_read+0x0/0x54 [md_mod]

Mar 18 20:35:51 Serenity kernel: [] ? proc_file_read+0x10b/0x22d

Mar 18 20:35:51 Serenity kernel: [] ? proc_file_read+0x0/0x22d

Mar 18 20:35:51 Serenity kernel: [] ? proc_reg_read+0x56/0x6a

Mar 18 20:35:51 Serenity kernel: [] ? proc_reg_read+0x0/0x6a

Mar 18 20:35:51 Serenity kernel: [] ? vfs_read+0x8a/0x114

Mar 18 20:35:51 Serenity kernel: [] ? sys_read+0x3b/0x60

Mar 18 20:35:51 Serenity kernel: [] ? syscall_call+0x7/0xb

Mar 18 20:35:51 Serenity kernel: Code: 55 f0 e8 da d7 d6 c8 8d 50 01 29 f2 39 d3 7c 0b 8b 45 0c 89 d3 c7 00 01 00 00 00 8b 45 f0 89 d9 81 c6 a0 ad 3c f8 c1 e9 02 89 38 a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89

Mar 18 20:35:51 Serenity kernel: EIP: [] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c2a5bef4

Mar 18 20:35:51 Serenity kernel: CR2: 00000000f83cf000

Mar 18 20:35:51 Serenity kernel: ---[ end trace 507e2e1b4b973720 ]---

 

I just came across some very similar reports in my log. Different address for the paging request though. I wasn't actively using the tower at the time, and it did not lock up or anything.

 

Apr  4 07:37:21 Tower kernel: BUG: unable to handle kernel paging request at f878e000

Apr  4 07:37:21 Tower kernel: IP: [<f87848c4>] md_cmd_proc_read+0x41/0x54 [md_mod]

Apr  4 07:37:21 Tower kernel: *pdpt = 0000000001443001 *pde = 00000000044d2067 *pte = 0000000000000000

Apr  4 07:37:21 Tower kernel: Oops: 0000 [#1] SMP

Apr  4 07:37:21 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/host1/target1:0:0/1:0:0:0/block/sda/stat

Apr  4 07:37:21 Tower kernel: Modules linked in: md_mod xor ata_piix piix r8169 sata_mv [last unloaded: md_mod]

Apr  4 07:37:21 Tower kernel:

Apr  4 07:37:21 Tower kernel: Pid: 1563, comm: emhttp Not tainted (2.6.32.9-unRAID #1) X7SLA

Apr  4 07:37:21 Tower kernel: EIP: 0060:[<f87848c4>] EFLAGS: 00210207 CPU: 0

Apr  4 07:37:21 Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]

Apr  4 07:37:21 Tower kernel: EAX: c2901f38 EBX: ffffff27 ECX: 3ffff031 EDX: ffffff27

Apr  4 07:37:21 Tower kernel: ESI: f878e000 EDI: e101de60 EBP: c2901f04 ESP: c2901ef4

Apr  4 07:37:21 Tower kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Apr  4 07:37:21 Tower kernel: Process emhttp (pid: 1563, ti=c2900000 task=f7681ef0 task.ti=c2900000)

Apr  4 07:37:21 Tower kernel: Stack:

Apr  4 07:37:21 Tower kernel:  c2901f38 f8784883 00000000 e101a000 c2901f4c c109d56d 00000400 c2901f3c

Apr  4 07:37:21 Tower kernel: <0> 00000000 00000400 00000000 00000400 b7765000 ed6d05a0 00000000 ed6d05a0

Apr  4 07:37:21 Tower kernel: <0> 00000400 e101a000 00000001 ed6d05a0 c109d462 fffffffb c2901f70 c1099eea

Apr  4 07:37:21 Tower kernel: Call Trace:

Apr  4 07:37:21 Tower kernel:  [<f8784883>] ? md_cmd_proc_read+0x0/0x54 [md_mod]

Apr  4 07:37:21 Tower kernel:  [<c109d56d>] ? proc_file_read+0x10b/0x22d

Apr  4 07:37:21 Tower kernel:  [<c109d462>] ? proc_file_read+0x0/0x22d

Apr  4 07:37:21 Tower kernel:  [<c1099eea>] ? proc_reg_read+0x56/0x6a

Apr  4 07:37:21 Tower kernel:  [<c1099e94>] ? proc_reg_read+0x0/0x6a

Apr  4 07:37:21 Tower kernel:  [<c106cb60>] ? vfs_read+0x8a/0x114

Apr  4 07:37:21 Tower kernel:  [<c106cef7>] ? sys_read+0x3b/0x60

Apr  4 07:37:21 Tower kernel:  [<c1002935>] ? syscall_call+0x7/0xb

Apr  4 07:37:21 Tower kernel: Code: 55 f0 e8 da e7 9a c8 8d 50 01 29 f2 39 d3 7c 0b 8b 45 0c 89 d3 c7 00 01 00 00 00 8b 45 f0 89 d9 81 c6 a0 9d 78 f8 c1 e9 02 89 38 <f3> a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89

Apr  4 07:37:21 Tower kernel: EIP: [<f87848c4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c2901ef4

Apr  4 07:37:21 Tower kernel: CR2: 00000000f878e000

Apr  4 07:37:21 Tower kernel: ---[ end trace b78ec1ff8b4b88ae ]---

Please send an email to LimeTech [ [email protected] ] detailing the issue and include a link to this thread.

I've got the same thing and mine also locked up last night.

I'd say it was 4.5.3, but I've had some odd problems with 4.5.1 as well. I'd email Tom @ Lime Tech just to let him know there's a problem but I wouldn't hold my breath waiting for help.

 

Let lime-tech know if you have a single-core CPU, or a multi-core CPU, as these might be clues needed for him to discover the cause.