May 7, 201016 yr Running 4.5.3 on a Supermicro X7SPA-HF with AOC-SASLP-MV8 card. Last night I decided to try to add two new drives (1TB WD EADS) at the same time. I'm just using the built-in clearing, not preclearing. Shut down the array, powered down gracefully, added the two drives (disk 6 and disk 7), powered back up, stopped the auto-started array, assigned the two new drives, and started the array. Drives start clearing, I go to bed. This morning I check in, and find that none of the shares are up, and when I check the web interface, it shows all drives in a state of Mounting. Refresh does nothing. Upon reboot, the drives show up as new again. Checking the syslog, I see a kernel page error followed by a dump. Any ideas? Syslog snippet below: May 6 23:21:24 Tower kernel: md: import disk0: [8,48] (sdd) WDC WD20EARS-00S WD-WCAVY2845005 offset: 63 size: 1953514552 May 6 23:21:24 Tower kernel: md: import disk1: [8,80] (sdf) WDC WD20EARS-00S WD-WCAVY2744880 offset: 63 size: 1953514552 May 6 23:21:24 Tower kernel: md: import disk2: [8,64] (sde) WDC WD20EADS-32R WD-WCAVY3272016 offset: 63 size: 1953514552 May 6 23:21:24 Tower kernel: md: import disk3: [8,128] (sdi) WDC WD20EADS-00R WD-WCAVY1712376 offset: 63 size: 1953514552 May 6 23:21:24 Tower kernel: md: import disk4: [8,112] (sdh) WDC WD20EADS-00S WD-WCAVY1300784 offset: 63 size: 1953514552 May 6 23:21:24 Tower kernel: md: import disk5: [8,96] (sdg) WDC WD10EACS-00D WD-WCAU40691353 offset: 63 size: 976762552 May 6 23:21:24 Tower kernel: md: import disk6: [8,32] (sdc) WDC WD10EACS-22D WD-WCAU42559937 offset: 63 size: 976762552 May 6 23:21:24 Tower kernel: md: disk6 new disk May 6 23:21:24 Tower kernel: md: import disk7: [8,16] (sdb) WDC WD10EACS-22D WD-WCAU42662693 offset: 63 size: 976762552 May 6 23:21:24 Tower kernel: md: disk7 new disk May 6 23:21:24 Tower kernel: mdcmd (2): set md_num_stripes 1280 May 6 23:21:24 Tower kernel: mdcmd (3): set md_write_limit 768 May 6 23:21:24 Tower kernel: mdcmd (4): set md_sync_window 288 May 6 23:21:24 Tower kernel: mdcmd (5): set spinup_group 0 4 May 6 23:21:24 Tower kernel: mdcmd (6): set spinup_group 1 32 May 6 23:21:24 Tower kernel: mdcmd (7): set spinup_group 2 1 May 6 23:21:24 Tower kernel: mdcmd (: set spinup_group 3 0 May 6 23:21:24 Tower kernel: mdcmd (9): set spinup_group 4 0 May 6 23:21:24 Tower kernel: mdcmd (10): set spinup_group 5 2 May 6 23:21:24 Tower kernel: mdcmd (11): set spinup_group 6 128 May 6 23:21:24 Tower kernel: mdcmd (12): set spinup_group 7 64 May 6 23:21:41 Tower emhttp: shcmd (52): /usr/local/sbin/set_ncq sdd 1 >/dev/null May 6 23:21:41 Tower emhttp: shcmd (53): /usr/local/sbin/set_ncq sdf 1 >/dev/null May 6 23:21:41 Tower emhttp: shcmd (54): /usr/local/sbin/set_ncq sde 1 >/dev/null May 6 23:21:41 Tower emhttp: shcmd (55): /usr/local/sbin/set_ncq sdi 1 >/dev/null May 6 23:21:41 Tower emhttp: shcmd (56): /usr/local/sbin/set_ncq sdh 1 >/dev/null May 6 23:21:41 Tower emhttp: shcmd (57): /usr/local/sbin/set_ncq sdg 1 >/dev/null May 6 23:21:41 Tower emhttp: shcmd (58): /usr/local/sbin/set_ncq sdc 1 >/dev/null May 6 23:21:41 Tower emhttp: shcmd (59): /usr/local/sbin/set_ncq sdb 1 >/dev/null May 6 23:21:41 Tower emhttp: writing mbr on disk 6 (/dev/sdc) May 6 23:21:41 Tower emhttp: re-reading /dev/sdc partition table May 6 23:21:41 Tower kernel: sdc: sdc1 May 6 23:21:41 Tower ata_id[1948]: HDIO_GET_IDENTITY failed for '/dev/block/8:32' May 6 23:21:42 Tower ata_id[1963]: HDIO_GET_IDENTITY failed for '/dev/block/8:32' May 6 23:21:42 Tower emhttp: writing mbr on disk 7 (/dev/sdb) May 6 23:21:42 Tower emhttp: re-reading /dev/sdb partition table May 6 23:21:42 Tower kernel: sdb: sdb1 May 6 23:21:43 Tower emhttp: clearing disk6 disk7 ... May 6 23:23:45 Tower emhttp: ... clearing 1% complete May 6 23:25:48 Tower emhttp: ... clearing 2% complete May 6 23:27:46 Tower emhttp: ... clearing 3% complete May 6 23:29:47 Tower emhttp: ... clearing 4% complete May 6 23:31:46 Tower emhttp: ... clearing 5% complete May 6 23:33:47 Tower emhttp: ... clearing 6% complete May 6 23:35:55 Tower emhttp: ... clearing 7% complete May 6 23:37:56 Tower emhttp: ... clearing 8% complete May 6 23:39:56 Tower emhttp: ... clearing 9% complete May 6 23:41:57 Tower emhttp: ... clearing 10% complete May 6 23:43:57 Tower emhttp: ... clearing 11% complete May 6 23:45:57 Tower emhttp: ... clearing 12% complete May 6 23:47:58 Tower emhttp: ... clearing 13% complete May 6 23:50:07 Tower emhttp: ... clearing 14% complete May 6 23:52:09 Tower emhttp: ... clearing 15% complete May 6 23:54:11 Tower emhttp: ... clearing 16% complete May 6 23:56:12 Tower emhttp: ... clearing 17% complete May 6 23:58:14 Tower emhttp: ... clearing 18% complete May 7 00:00:17 Tower emhttp: ... clearing 19% complete May 7 00:02:19 Tower emhttp: ... clearing 20% complete May 7 00:04:27 Tower emhttp: ... clearing 21% complete May 7 00:06:30 Tower emhttp: ... clearing 22% complete May 7 00:08:32 Tower emhttp: ... clearing 23% complete May 7 00:10:32 Tower emhttp: ... clearing 24% complete May 7 00:12:33 Tower emhttp: ... clearing 25% complete May 7 00:14:37 Tower emhttp: ... clearing 26% complete May 7 00:16:42 Tower emhttp: ... clearing 27% complete May 7 00:18:42 Tower emhttp: ... clearing 28% complete May 7 00:20:46 Tower emhttp: ... clearing 29% complete May 7 00:22:47 Tower emhttp: ... clearing 30% complete May 7 00:24:49 Tower emhttp: ... clearing 31% complete May 7 00:26:51 Tower emhttp: ... clearing 32% complete May 7 00:28:53 Tower emhttp: ... clearing 33% complete May 7 00:30:57 Tower emhttp: ... clearing 34% complete May 7 00:33:01 Tower emhttp: ... clearing 35% complete May 7 00:35:14 Tower emhttp: ... clearing 36% complete May 7 00:37:17 Tower emhttp: ... clearing 37% complete May 7 00:39:21 Tower emhttp: ... clearing 38% complete May 7 00:41:25 Tower emhttp: ... clearing 39% complete May 7 00:43:30 Tower emhttp: ... clearing 40% complete May 7 00:45:33 Tower emhttp: ... clearing 41% complete May 7 00:47:46 Tower emhttp: ... clearing 42% complete May 7 00:49:51 Tower emhttp: ... clearing 43% complete May 7 00:51:59 Tower emhttp: ... clearing 44% complete May 7 00:54:06 Tower emhttp: ... clearing 45% complete May 7 00:56:14 Tower emhttp: ... clearing 46% complete May 7 00:58:21 Tower emhttp: ... clearing 47% complete May 7 01:00:29 Tower emhttp: ... clearing 48% complete May 7 01:02:41 Tower emhttp: ... clearing 49% complete May 7 01:04:50 Tower emhttp: ... clearing 50% complete May 7 01:06:59 Tower emhttp: ... clearing 51% complete May 7 01:09:08 Tower emhttp: ... clearing 52% complete May 7 01:11:17 Tower emhttp: ... clearing 53% complete May 7 01:13:27 Tower emhttp: ... clearing 54% complete May 7 01:15:42 Tower emhttp: ... clearing 55% complete May 7 01:17:54 Tower emhttp: ... clearing 56% complete May 7 01:20:07 Tower emhttp: ... clearing 57% complete May 7 01:22:20 Tower emhttp: ... clearing 58% complete May 7 01:24:34 Tower emhttp: ... clearing 59% complete May 7 01:26:47 Tower emhttp: ... clearing 60% complete May 7 01:29:04 Tower emhttp: ... clearing 61% complete May 7 01:31:21 Tower emhttp: ... clearing 62% complete May 7 01:33:38 Tower emhttp: ... clearing 63% complete May 7 01:35:56 Tower emhttp: ... clearing 64% complete May 7 01:38:18 Tower emhttp: ... clearing 65% complete May 7 01:40:39 Tower emhttp: ... clearing 66% complete May 7 01:43:01 Tower emhttp: ... clearing 67% complete May 7 01:45:33 Tower emhttp: ... clearing 68% complete May 7 01:47:56 Tower emhttp: ... clearing 69% complete May 7 01:50:19 Tower emhttp: ... clearing 70% complete May 7 01:52:59 Tower emhttp: ... clearing 71% complete May 7 01:55:27 Tower emhttp: ... clearing 72% complete May 7 01:57:58 Tower emhttp: ... clearing 73% complete May 7 02:00:28 Tower emhttp: ... clearing 74% complete May 7 02:02:59 Tower emhttp: ... clearing 75% complete May 7 02:05:34 Tower emhttp: ... clearing 76% complete May 7 02:08:09 Tower emhttp: ... clearing 77% complete May 7 02:10:50 Tower emhttp: ... clearing 78% complete May 7 02:13:27 Tower emhttp: ... clearing 79% complete May 7 02:16:09 Tower emhttp: ... clearing 80% complete May 7 02:18:56 Tower emhttp: ... clearing 81% complete May 7 02:21:52 Tower emhttp: ... clearing 82% complete May 7 02:24:49 Tower emhttp: ... clearing 83% complete May 7 02:27:47 Tower emhttp: ... clearing 84% complete May 7 02:30:42 Tower emhttp: ... clearing 85% complete May 7 02:33:41 Tower emhttp: ... clearing 86% complete May 7 02:36:48 Tower emhttp: ... clearing 87% complete May 7 02:39:49 Tower emhttp: ... clearing 88% complete May 7 02:43:00 Tower emhttp: ... clearing 89% complete May 7 02:46:01 Tower emhttp: ... clearing 90% complete May 7 02:49:08 Tower emhttp: ... clearing 91% complete May 7 02:52:18 Tower emhttp: ... clearing 92% complete May 7 02:55:30 Tower emhttp: ... clearing 93% complete May 7 02:58:50 Tower emhttp: ... clearing 94% complete May 7 03:02:10 Tower emhttp: ... clearing 95% complete May 7 03:05:40 Tower emhttp: ... clearing 96% complete May 7 03:09:13 Tower emhttp: ... clearing 97% complete May 7 03:12:59 Tower emhttp: ... clearing 98% complete May 7 03:16:50 Tower emhttp: ... clearing 99% complete May 7 03:20:43 Tower emhttp: ... clearing 100% complete May 7 03:20:43 Tower emhttp: ... syncing May 7 03:20:45 Tower kernel: mdcmd (24): start PROTECTED_EXPANSION May 7 03:20:45 Tower kernel: unraid: allocating 43820K for 1280 stripes (8 disks) May 7 03:20:45 Tower kernel: md1: running, size: 1953514552 blocks May 7 03:20:45 Tower kernel: md2: running, size: 1953514552 blocks May 7 03:20:45 Tower kernel: md3: running, size: 1953514552 blocks May 7 03:20:45 Tower kernel: md4: running, size: 1953514552 blocks May 7 03:20:45 Tower kernel: md5: running, size: 976762552 blocks May 7 03:20:45 Tower kernel: md6: running, size: 976762552 blocks May 7 03:20:45 Tower kernel: md7: running, size: 976762552 blocks May 7 03:20:45 Tower kernel: mdcmd (26): spindown 0 May 7 03:20:46 Tower kernel: mdcmd (27): spindown 1 May 7 03:20:47 Tower kernel: mdcmd (28): spindown 2 May 7 03:20:48 Tower kernel: mdcmd (30): spindown 3 May 7 03:20:48 Tower kernel: BUG: unable to handle kernel paging request at f8ac8000 May 7 03:20:48 Tower kernel: IP: [<f8abe8c4>] md_cmd_proc_read+0x41/0x54 [md_mod] May 7 03:20:48 Tower kernel: *pdpt = 0000000001443001 *pde = 00000000039fe067 *pte = 0000000000000000 May 7 03:20:48 Tower kernel: Oops: 0000 [#1] SMP May 7 03:20:48 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.5/host5/target5:0:0/5:0:0:0/block/sdi/stat May 7 03:20:48 Tower kernel: Modules linked in: md_mod xor ata_piix e1000e mvsas libsas scst scsi_transport_sas [last unloaded: md_mod] May 7 03:20:48 Tower kernel: May 7 03:20:48 Tower kernel: Pid: 1920, comm: emhttp Not tainted (2.6.32.9-unRAID #1) X7SPA-HF May 7 03:20:48 Tower kernel: EIP: 0060:[<f8abe8c4>] EFLAGS: 00210203 CPU: 1 May 7 03:20:48 Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod] May 7 03:20:48 Tower kernel: EAX: c3979f38 EBX: fffff24a ECX: 3fffef6f EDX: fffff24a May 7 03:20:48 Tower kernel: ESI: f8ac7ffe EDI: f727948c EBP: c3979f04 ESP: c3979ef4 May 7 03:20:48 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 May 7 03:20:48 Tower kernel: Process emhttp (pid: 1920, ti=c3978000 task=f6ca0000 task.ti=c3978000) May 7 03:20:48 Tower kernel: Stack: May 7 03:20:48 Tower kernel: c3979f38 f8abe883 00000000 f7276000 c3979f4c c109d56d 00000400 c3979f3c May 7 03:20:48 Tower kernel: <0> 00000000 00000400 00000000 00000400 b78c7000 f6dab9c0 00000000 f6dab9c0 May 7 03:20:48 Tower kernel: <0> 00000400 f7276000 00000001 f6dab9c0 c109d462 fffffffb c3979f70 c1099eea May 7 03:20:48 Tower kernel: Call Trace: May 7 03:20:48 Tower kernel: [<f8abe883>] ? md_cmd_proc_read+0x0/0x54 [md_mod] May 7 03:20:48 Tower kernel: [<c109d56d>] ? proc_file_read+0x10b/0x22d May 7 03:20:48 Tower kernel: [<c109d462>] ? proc_file_read+0x0/0x22d May 7 03:20:48 Tower kernel: [<c1099eea>] ? proc_reg_read+0x56/0x6a May 7 03:20:48 Tower kernel: [<c1099e94>] ? proc_reg_read+0x0/0x6a May 7 03:20:48 Tower kernel: [<c106cb60>] ? vfs_read+0x8a/0x114 May 7 03:20:48 Tower kernel: [<c106cef7>] ? sys_read+0x3b/0x60 May 7 03:20:48 Tower kernel: [<c1002935>] ? syscall_call+0x7/0xb May 7 03:20:48 Tower kernel: Code: 55 f0 e8 da 47 67 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 3d ac 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 May 7 03:20:48 Tower kernel: EIP: [<f8abe8c4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c3979ef4 May 7 03:20:48 Tower kernel: CR2: 00000000f8ac8000 May 7 03:20:48 Tower kernel: ---[ end trace 21bf876656a0f23e ]--- May 7 03:20:49 Tower kernel: mdcmd (31): spindown 4 May 7 03:20:49 Tower kernel: mdcmd (32): spindown 5 May 7 03:20:50 Tower kernel: mdcmd (33): spindown 6 May 7 03:20:51 Tower kernel: mdcmd (34): spindown 7
May 7, 201016 yr send an e-mail to lime-tech. As you said, looks like a bug with emhttp and SMP processing. Point them to this thread. Joe L.
May 7, 201016 yr did you run out of ram? or have a ram problem? you have a kernel paging error there. thre shouldnt be issue with clearing multiple hdds at a time, i recently did 4 at once with no issues (except for the drives appearing as unformatted crap wher eyou hit refresh a few times and it fixes itself)
May 7, 201016 yr Author 4GB of memory, so I doubt it's an out of mem issue, though I can run an overnight memtest again if that looks suspicious. And Joe - thanks - will send an email shortly.
September 12, 201015 yr May 7 03:20:45 Tower kernel: mdcmd (26): spindown 0 May 7 03:20:46 Tower kernel: mdcmd (27): spindown 1 May 7 03:20:47 Tower kernel: mdcmd (28): spindown 2 May 7 03:20:48 Tower kernel: mdcmd (30): spindown 3 May 7 03:20:48 Tower kernel: BUG: unable to handle kernel paging request at f8ac8000 May 7 03:20:48 Tower kernel: IP: [<f8abe8c4>] md_cmd_proc_read+0x41/0x54 [md_mod] May 7 03:20:48 Tower kernel: *pdpt = 0000000001443001 *pde = 00000000039fe067 *pte = 0000000000000000 May 7 03:20:48 Tower kernel: Oops: 0000 [#1] SMP May 7 03:20:48 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.5/host5/target5:0:0/5:0:0:0/block/sdi/stat May 7 03:20:48 Tower kernel: Modules linked in: md_mod xor ata_piix e1000e mvsas libsas scst scsi_transport_sas [last unloaded: md_mod] May 7 03:20:48 Tower kernel: May 7 03:20:48 Tower kernel: Pid: 1920, comm: emhttp Not tainted (2.6.32.9-unRAID #1) X7SPA-HF May 7 03:20:48 Tower kernel: EIP: 0060:[<f8abe8c4>] EFLAGS: 00210203 CPU: 1 May 7 03:20:48 Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod] May 7 03:20:48 Tower kernel: EAX: c3979f38 EBX: fffff24a ECX: 3fffef6f EDX: fffff24a May 7 03:20:48 Tower kernel: ESI: f8ac7ffe EDI: f727948c EBP: c3979f04 ESP: c3979ef4 May 7 03:20:48 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 May 7 03:20:48 Tower kernel: Process emhttp (pid: 1920, ti=c3978000 task=f6ca0000 task.ti=c3978000) May 7 03:20:48 Tower kernel: Stack: May 7 03:20:48 Tower kernel: c3979f38 f8abe883 00000000 f7276000 c3979f4c c109d56d 00000400 c3979f3c May 7 03:20:48 Tower kernel: <0> 00000000 00000400 00000000 00000400 b78c7000 f6dab9c0 00000000 f6dab9c0 May 7 03:20:48 Tower kernel: <0> 00000400 f7276000 00000001 f6dab9c0 c109d462 fffffffb c3979f70 c1099eea May 7 03:20:48 Tower kernel: Call Trace: May 7 03:20:48 Tower kernel: [<f8abe883>] ? md_cmd_proc_read+0x0/0x54 [md_mod] May 7 03:20:48 Tower kernel: [<c109d56d>] ? proc_file_read+0x10b/0x22d May 7 03:20:48 Tower kernel: [<c109d462>] ? proc_file_read+0x0/0x22d May 7 03:20:48 Tower kernel: [<c1099eea>] ? proc_reg_read+0x56/0x6a May 7 03:20:48 Tower kernel: [<c1099e94>] ? proc_reg_read+0x0/0x6a May 7 03:20:48 Tower kernel: [<c106cb60>] ? vfs_read+0x8a/0x114 May 7 03:20:48 Tower kernel: [<c106cef7>] ? sys_read+0x3b/0x60 May 7 03:20:48 Tower kernel: [<c1002935>] ? syscall_call+0x7/0xb May 7 03:20:48 Tower kernel: Code: 55 f0 e8 da 47 67 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 3d ac 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 May 7 03:20:48 Tower kernel: EIP: [<f8abe8c4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c3979ef4 May 7 03:20:48 Tower kernel: CR2: 00000000f8ac8000 May 7 03:20:48 Tower kernel: ---[ end trace 21bf876656a0f23e ]--- May 7 03:20:49 Tower kernel: mdcmd (31): spindown 4 May 7 03:20:49 Tower kernel: mdcmd (32): spindown 5 May 7 03:20:50 Tower kernel: mdcmd (33): spindown 6 May 7 03:20:51 Tower kernel: mdcmd (34): spindown 7 I guess this issue never go away since 4.5.3. Saw this problem twice recently, one with 4.5.4, as following log indicated. one with 4.5.6. At both cases when this bug was triggered there were always disk spin down involved then emhttp was dead. Sep 5 13:57:21 Tower kernel: mdcmd (72): spindown 4 Sep 5 13:57:31 Tower kernel: mdcmd (75): spindown 4 Sep 5 13:57:34 Tower kernel: mdcmd (77): spindown 5 Sep 5 13:57:42 Tower kernel: mdcmd (79): spindown 6 Sep 5 13:57:50 Tower kernel: mdcmd (81): spindown 7 Sep 5 13:57:56 Tower kernel: mdcmd (83): spindown 7 Sep 5 13:58:03 Tower kernel: mdcmd (85): spindown 8 Sep 5 13:58:13 Tower kernel: mdcmd (87): spindown 8 Sep 5 13:58:23 Tower kernel: mdcmd (89): spindown 9 Sep 5 13:58:23 Tower kernel: mdcmd (90): spindown 12 Sep 5 13:58:27 Tower kernel: mdcmd (91): spindown 13 Sep 5 13:58:37 Tower kernel: mdcmd (93): spindown 13 Sep 5 13:58:38 Tower kernel: mdcmd (95): spindown 14 Sep 5 13:58:38 Tower kernel: *pdpt = 0000000001447001 *pde = 00000000376d3067 *pte = 0000000000000000 Sep 5 13:58:38 Tower kernel: Oops: 0000 [#1] SMP Sep 5 13:58:38 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.5/host9/target9:0:0/9: 0:0:0/block/sdo/stat Sep 5 13:58:38 Tower kernel: Modules linked in: md_mod xor ata_piix r8169 sata_sil24 pata_jmicron jmicr on ahci mvsas libsas scst scsi_transport_sas Sep 5 13:58:38 Tower kernel: Sep 5 13:58:38 Tower kernel: Pid: 1733, comm: emhttp Tainted: G W (2.6.32.9-unRAID #2) MS-7514 Sep 5 13:58:38 Tower kernel: EIP: 0060:[<f85198c4>] EFLAGS: 00210202 CPU: 0 Sep 5 13:58:38 Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod] Sep 5 13:58:38 Tower kernel: EAX: c3d17f38 EBX: fffff81c ECX: 3fffef6f EDX: fffff81c Sep 5 13:58:38 Tower kernel: ESI: f8523000 EDI: f73d3a60 EBP: c3d17f04 ESP: c3d17ef4 Sep 5 13:58:38 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Sep 5 13:58:38 Tower kernel: Process emhttp (pid: 1733, ti=c3d16000 task=f7627700 task.ti=c3d16000) Sep 5 13:58:38 Tower kernel: Stack: Sep 5 13:58:38 Tower kernel: c3d17f38 f8519883 00000000 f73d0000 c3d17f4c c109d5f5 00000400 c3d17f3c Sep 5 13:58:38 Tower kernel: <0> 00000000 00000400 00000000 00000400 b784c000 c43a86c0 00000000 c43a86c0 Sep 5 13:58:38 Tower kernel: <0> 00000400 f73d0000 00000001 c43a86c0 c109d4ea fffffffb c3d17f70 c1099f72 Sep 5 13:58:38 Tower kernel: Call Trace: Sep 5 13:58:38 Tower kernel: [<f8519883>] ? md_cmd_proc_read+0x0/0x54 [md_mod] Sep 5 13:58:38 Tower kernel: [<c109d5f5>] ? proc_file_read+0x10b/0x22d Sep 5 13:58:38 Tower kernel: [<c109d4ea>] ? proc_file_read+0x0/0x22d Sep 5 13:58:38 Tower kernel: [<c1099f72>] ? proc_reg_read+0x56/0x6a Sep 5 13:58:38 Tower kernel: [<c1099f1c>] ? proc_reg_read+0x0/0x6a Sep 5 13:58:38 Tower kernel: [<c106cbd8>] ? vfs_read+0x8a/0x114 Sep 5 13:58:38 Tower kernel: [<c106cf6f>] ? sys_read+0x3b/0x60 Sep 5 13:58:38 Tower kernel: [<c1002935>] ? syscall_call+0x7/0xb Sep 5 13:58:38 Tower kernel: Code: 55 f0 e8 8a d2 c1 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 ed 51 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 Sep 5 13:58:38 Tower kernel: EIP: [<f85198c4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c3d17ef4 Sep 5 13:58:38 Tower kernel: CR2: 00000000f8523000 Sep 5 13:58:38 Tower kernel: ---[ end trace e84e06f9e6054ad1 ]--- Sep 5 13:58:42 Tower kernel: mdcmd (96): spindown 15 Sep 5 13:58:50 Tower ntpd[1678]: synchronized to 132.163.4.103, stratum 1 Sep 5 13:58:53 Tower kernel: mdcmd (99): spindown 15
Archived
This topic is now archived and is closed to further replies.