I found the following in my syslog this morning.  At the time, nothing was happening on the server.  There were no log messages for over an hour before these series of messages.  Server is running fine.

 

Note this happened in 5.0 Beta2.

 

Any thoughts as to what might have happened?

 

Sep 26 11:24:57 Tower kernel: BUG: unable to handle kernel paging request at f971f000

Sep 26 11:24:57 Tower kernel: IP: [] md_cmd_proc_read+0x41/0x54 [md_mod]

Sep 26 11:24:57 Tower kernel: *pdpt = 0000000001447001 *pde = 000000002d452067 *pte = 0000000000000000

Sep 26 11:24:57 Tower kernel: Oops: 0000 [#1] SMP

Sep 26 11:24:57 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/port-0:5/end_device-0:5/target0:0:5/0:0:5:0/block/sds/stat

Sep 26 11:24:57 Tower kernel: Modules linked in: md_mod xor i2c_i801 i2c_core sata_promise pata_jmicron jmicron ahci sata_mv e1000e mvsas libsas scst scsi_transport_sas [last unloaded: md_mod]

Sep 26 11:24:57 Tower kernel:

Sep 26 11:24:57 Tower kernel: Pid: 1899, comm: emhttp Not tainted (2.6.32.9-unRAID #5) System Product Name

Sep 26 11:24:57 Tower kernel: EIP: 0060:[] EFLAGS: 00210203 CPU: 0

Sep 26 11:24:57 Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]

Sep 26 11:24:57 Tower kernel: EAX: c3469f38 EBX: fffffdfe ECX: 3ffff84e EDX: fffffdfe

Sep 26 11:24:57 Tower kernel: ESI: f971f000 EDI: e6c5acc4 EBP: c3469f04 ESP: c3469ef4

Sep 26 11:24:57 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Sep 26 11:24:57 Tower kernel: Process emhttp (pid: 1899, ti=c3468000 task=c44686e0 task.ti=c3468000)

Sep 26 11:24:57 Tower kernel: Stack:

Sep 26 11:24:57 Tower kernel: c3469f38 f97158a3 00000000 e6c59000 c3469f4c c109d5f5 00000400 c3469f3c

Sep 26 11:24:57 Tower kernel: <0> 00000000 00000400 00000000 00000400 b7834000 c3477c60 00000000 c3477c60

Sep 26 11:24:57 Tower kernel: <0> 00000400 e6c59000 00000001 c3477c60 c109d4ea fffffffb c3469f70 c1099f72

Sep 26 11:24:57 Tower kernel: Call Trace:

Sep 26 11:24:57 Tower kernel: [] ? md_cmd_proc_read+0x0/0x54 [md_mod]

Sep 26 11:24:57 Tower kernel: [] ? proc_file_read+0x10b/0x22d

Sep 26 11:24:57 Tower kernel: [] ? proc_file_read+0x0/0x22d

Sep 26 11:24:57 Tower kernel: [] ? proc_reg_read+0x56/0x6a

Sep 26 11:24:57 Tower kernel: [] ? proc_reg_read+0x0/0x6a

Sep 26 11:24:57 Tower kernel: [] ? vfs_read+0x8a/0x114

Sep 26 11:24:57 Tower kernel: [] ? sys_read+0x3b/0x60

Sep 26 11:24:57 Tower kernel: [] ? syscall_call+0x7/0xb

Sep 26 11:24:57 Tower kernel: Code: 55 f0 e8 6a 12 a2 c7 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 3c af 71 f9 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

Sep 26 11:24:57 Tower kernel: EIP: [] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c3469ef4

Sep 26 11:24:57 Tower kernel: CR2: 00000000f971f000

Sep 26 11:24:57 Tower kernel: ---[ end trace f256269a20d76d06 ]---

 

I found the following in my syslog this morning.  At the time, nothing was happening on the server.  There were no log messages for over an hour before these series of messages.  Server is running fine.

 

Note this happened in 5.0 Beta2.

 

Any thoughts as to what might have happened?

 

Sep 26 11:24:57 Tower kernel: BUG: unable to handle kernel paging request at f971f000

Sep 26 11:24:57 Tower kernel: IP: [] md_cmd_proc_read+0x41/0x54 [md_mod]

Sep 26 11:24:57 Tower kernel: *pdpt = 0000000001447001 *pde = 000000002d452067 *pte = 0000000000000000

Sep 26 11:24:57 Tower kernel: Oops: 0000 [#1] SMP

Sep 26 11:24:57 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/port-0:5/end_device-0:5/target0:0:5/0:0:5:0/block/sds/stat

Sep 26 11:24:57 Tower kernel: Modules linked in: md_mod xor i2c_i801 i2c_core sata_promise pata_jmicron jmicron ahci sata_mv e1000e mvsas libsas scst scsi_transport_sas [last unloaded: md_mod]

Sep 26 11:24:57 Tower kernel:

Sep 26 11:24:57 Tower kernel: Pid: 1899, comm: emhttp Not tainted (2.6.32.9-unRAID #5) System Product Name

Sep 26 11:24:57 Tower kernel: EIP: 0060:[] EFLAGS: 00210203 CPU: 0

Sep 26 11:24:57 Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]

Sep 26 11:24:57 Tower kernel: EAX: c3469f38 EBX: fffffdfe ECX: 3ffff84e EDX: fffffdfe

Sep 26 11:24:57 Tower kernel: ESI: f971f000 EDI: e6c5acc4 EBP: c3469f04 ESP: c3469ef4

Sep 26 11:24:57 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Sep 26 11:24:57 Tower kernel: Process emhttp (pid: 1899, ti=c3468000 task=c44686e0 task.ti=c3468000)

Sep 26 11:24:57 Tower kernel: Stack:

Sep 26 11:24:57 Tower kernel: c3469f38 f97158a3 00000000 e6c59000 c3469f4c c109d5f5 00000400 c3469f3c

Sep 26 11:24:57 Tower kernel: <0> 00000000 00000400 00000000 00000400 b7834000 c3477c60 00000000 c3477c60

Sep 26 11:24:57 Tower kernel: <0> 00000400 e6c59000 00000001 c3477c60 c109d4ea fffffffb c3469f70 c1099f72

Sep 26 11:24:57 Tower kernel: Call Trace:

Sep 26 11:24:57 Tower kernel: [] ? md_cmd_proc_read+0x0/0x54 [md_mod]

Sep 26 11:24:57 Tower kernel: [] ? proc_file_read+0x10b/0x22d

Sep 26 11:24:57 Tower kernel: [] ? proc_file_read+0x0/0x22d

Sep 26 11:24:57 Tower kernel: [] ? proc_reg_read+0x56/0x6a

Sep 26 11:24:57 Tower kernel: [] ? proc_reg_read+0x0/0x6a

Sep 26 11:24:57 Tower kernel: [] ? vfs_read+0x8a/0x114

Sep 26 11:24:57 Tower kernel: [] ? sys_read+0x3b/0x60

Sep 26 11:24:57 Tower kernel: [] ? syscall_call+0x7/0xb

Sep 26 11:24:57 Tower kernel: Code: 55 f0 e8 6a 12 a2 c7 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 3c af 71 f9 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

Sep 26 11:24:57 Tower kernel: EIP: [] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c3469ef4

Sep 26 11:24:57 Tower kernel: CR2: 00000000f971f000

Sep 26 11:24:57 Tower kernel: ---[ end trace f256269a20d76d06 ]---

 

 

Refer to following link for information

 

http://lime-technology.com/forum/index.php?topic=7981.0

 

Thanks.  My emhttp is fine. Seems no ill effects.  I will run a memory check just to make sure memory is okay.