MPSS 3.3 - Call trace in /var/log/messages after booting the MIC ?

[Pierre_L_]

Hi, I upgraded our MIC system from MPSS 3.2 to 3.3 and did not notice anything, all tests were OK, however  I accidentally found a calls trace in /var/log/messages. It always appears straight during the start of mpss from mic in ready state, on all the MICs regardless of the model (5110P or 7120P):

Jul 11 05:57:01 phi01-mic0 user.info kernel: [    0.010000] CPU: Physical Processor ID: 0
Jul 11 05:57:01 phi01-mic0 user.info kernel: [    0.010000] CPU: Processor Core ID: 59
Jul 11 05:57:01 phi01-mic0 user.info kernel: [    0.010000] mce: CPU supports 3 MCE banks
Jul 11 05:57:01 phi01-mic0 user.emerg kernel: [    0.010000] SFI: Entering sfi_map_memory, phys = ef180, size = 48
Jul 11 05:57:01 phi01-mic0 user.emerg kernel: [    0.010000] SFI: Entering sfi_map_table, pa = 92000
Jul 11 05:57:01 phi01-mic0 user.emerg kernel: [    0.010000] SFI: Entering sfi_map_memory, phys = 92000, size = 24
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000] ------------[ cut here ]------------
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000] WARNING: at arch/x86/mm/ioremap.c:109 __ioremap_caller+0x16b/0x
30e()
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000] Modules linked in:
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000] Pid: 0, comm: swapper Not tainted 2.6.38.8+mpss3.3 #1
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000] Call Trace:
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff8101cc83>] ? __ioremap_caller+0x16b/0x30e
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff81033e28>] ? warn_slowpath_common+0x83/0x9c
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff81033e5b>] ? warn_slowpath_null+0x1a/0x1c
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff8101cc83>] ? __ioremap_caller+0x16b/0x30e
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff81345ec0>] ? sfi_map_memory+0x43/0x53
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff8101ce51>] ? ioremap_cache+0x14/0x16
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff81345ec0>] ? sfi_map_memory+0x43/0x53
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff811dc6e0>] ? sfi_map_table+0x54/0xd3
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff81345eed>] ? sfi_check_table+0x1d/0xdf
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff811dc7f4>] ? sfi_get_table+0x3f/0x5d
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff817c770d>] ? sfi_acpi_parse_xsdt+0x0/0x7b
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff817c770d>] ? sfi_acpi_parse_xsdt+0x0/0x7b
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff811dc8fd>] ? sfi_table_parse+0x42/0x67
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff817c77b8>] ? sfi_acpi_init+0x30/0x44
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff817c7aa9>] ? sfi_init_late+0x55/0x59
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff817a6b6b>] ? start_kernel+0x375/0x38b
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff817a62a4>] ? x86_64_start_reservations+0xb4/0xb8
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000]  [<ffffffff817a639d>] ? x86_64_start_kernel+0xf5/0xfc
Jul 11 05:57:01 phi01-mic0 user.warn kernel: [    0.010000] ---[ end trace 4eaa2a86a8e2da22 ]---

Any clue ?

Pierre.

[Loc_N_Intel]

Hi Pierre,

What OS are you running the MPSS 3.3? I couldn't reproduce the error you saw on my system. Can you confirm what you observed by doing the following things:

1. Open a terminal and type: "tail -f /var/log/messages"

2. Open a second terminl and type "sudo service mpss restart" (assuming MPSS is running).

3. Capture the log in the first terminal and attach the log here.

Thank you.

[Pierre_L_1]

Hi, I am currently on business trip, I will try to get your infos asap. However I would like to confirm the log output I put in my message is from the MIC itself, not from the host, ie. it is a capture done once logged on the MIC, not when starting mpss service on the host.

Cheers,

Pierre.

[Loc_N_Intel]

Hi Pierre,

I confirm that Call Trace is generated in MIC (observed in /var/log/messages) every time we restart MPSS service or reboot the system. This issue can be seen in MPSS 3.2 and 3.3.

I will generate a ticket to track this issue. Thank you very much for reporting the issue.