Can someone take a look at this syslog and let me know if I should be concerned about any of these messages, I'm seeing the warnings below and not sure what its telling me.

 

Running v4.7

 

Mar  1 01:15:45 Tower kernel: ------------[ cut here ]------------

 

Mar  1 01:15:45 Tower kernel: WARNING: at fs/proc/generic.c:590 proc_register+0x11c/0x14b()

 

Mar  1 01:15:45 Tower kernel: Hardware name: To Be Filled By O.E.M.

 

Mar  1 01:15:45 Tower kernel: proc_dir_entry 'scsi_tgt/mvst_scst' already registered

 

Mar  1 01:15:45 Tower kernel: Modules linked in: mvsas(+) libsas scst scsi_transport_sas

 

Mar  1 01:15:45 Tower kernel: Pid: 821, comm: modprobe Not tainted 2.6.32.9-unRAID #8

 

Mar  1 01:15:45 Tower kernel: Call Trace:

 

Mar  1 01:15:45 Tower kernel:  [<c102449e>] warn_slowpath_common+0x60/0x77

 

Mar  1 01:15:45 Tower kernel:  [<c10244e9>] warn_slowpath_fmt+0x24/0x27

 

Mar  1 01:15:45 Tower kernel:  [<c109cf0e>] proc_register+0x11c/0x14b

 

Mar  1 01:15:45 Tower kernel:  [<c109d0cc>] proc_mkdir_mode+0x2f/0x43

 

Mar  1 01:15:45 Tower kernel:  [<c109d0ef>] proc_mkdir+0xf/0x11

 

Mar  1 01:15:45 Tower kernel:  [<f83e5a36>] scst_build_proc_target_dir_entries+0x55/0xdc [scst]

 

Mar  1 01:15:45 Tower kernel:  [<f83ccca9>] __scst_register_target_template+0x16c/0x3af [scst]

 

Mar  1 01:15:45 Tower kernel:  [<f844ad5d>] mvst_init+0x3b/0x5b [mvsas]

 

Mar  1 01:15:45 Tower kernel:  [<f844f895>] mvs_pci_init+0xaa5/0xaf7 [mvsas]

 

Mar  1 01:15:45 Tower kernel:  [<c10062d9>] ? dma_generic_alloc_coherent+0x0/0xdb

 

Mar  1 01:15:45 Tower kernel:  [<c1142050>] local_pci_probe+0xe/0x10

 

Mar  1 01:15:45 Tower kernel:  [<c11426ad>] pci_device_probe+0x48/0x66

 

Mar  1 01:15:45 Tower kernel:  [<c1194956>] driver_probe_device+0x79/0xed

 

Mar  1 01:15:45 Tower kernel:  [<c1194a0d>] __driver_attach+0x43/0x5f

 

Mar  1 01:15:45 Tower kernel:  [<c11940a7>] bus_for_each_dev+0x39/0x5a

 

Mar  1 01:15:45 Tower kernel:  [<f8457000>] ? mvs_init+0x0/0x45 [mvsas]

 

Mar  1 01:15:45 Tower kernel:  [<c119482f>] driver_attach+0x14/0x16

 

Mar  1 01:15:45 Tower kernel:  [<c11949ca>] ? __driver_attach+0x0/0x5f

 

Mar  1 01:15:45 Tower kernel:  [<c119451c>] bus_add_driver+0x9f/0x1c5

 

Mar  1 01:15:45 Tower kernel:  [<f8457000>] ? mvs_init+0x0/0x45 [mvsas]

 

Mar  1 01:15:45 Tower kernel:  [<c1194ccf>] driver_register+0x7b/0xd7

 

Mar  1 01:15:45 Tower kernel:  [<f8457000>] ? mvs_init+0x0/0x45 [mvsas]

 

Mar  1 01:15:45 Tower kernel:  [<c1142882>] __pci_register_driver+0x39/0x8c

 

Mar  1 01:15:45 Tower kernel:  [<f8457000>] ? mvs_init+0x0/0x45 [mvsas]

 

Mar  1 01:15:45 Tower kernel:  [<f8457030>] mvs_init+0x30/0x45 [mvsas]

 

Mar  1 01:15:45 Tower kernel:  [<c1001139>] do_one_initcall+0x4c/0x131

 

Mar  1 01:15:45 Tower kernel:  [<c1042e6e>] sys_init_module+0xa7/0x1dd

 

Mar  1 01:15:45 Tower kernel:  [<c1002935>] syscall_call+0x7/0xb

 

Mar  1 01:15:45 Tower kernel: ---[ end trace cab10f42c32e5a01 ]---

 

Mar  1 01:15:45 Tower kernel: [821]: scst: __scst_register_target_template:253:***ERROR***: Target driver mvst_scst already registered

 

Mar  1 01:15:45 Tower kernel: [821]: scst: __scst_register_target_template:293:***ERROR***: Failed to register target template mvst_scst

 

Mar  1 01:15:45 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 384:phy 0 byte dmaded.

 

Mar  1 01:15:45 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 384:phy 1 byte dmaded.

 

Mar  1 01:15:45 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 384:phy 2 byte dmaded.

 

Mar  1 01:15:45 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 384:phy 3 byte dmaded.

 

Mar  1 01:15:45 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 384:phy 4 byte dmaded.

 

Mar  1 01:15:45 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 384:phy 5 byte dmaded.

 

Mar  1 01:15:45 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 384:phy 6 byte dmaded.

syslog-2011-03-01.txt

A search would have shown you have two of the same disk controller cards and this is only a warning that the driver is already loaded.