Intel Wireless BE200: Microcode error when scanning channels

[jamez70]

Description of system

Intel Arria 10 SoC FPGA running custom built Ubuntu 18.04 with kernel 6.6.0-socfpga.
Intel BE200 WiFi-7 PCIe adapter with microcode version 83

Issue

Error occurs when executing a custom utility to scan network channels on 2.4G and 5G at around 50ms per channel. Over time, the channel switching results in a Microcode SW error in the iwlwifi driver. This error occurs on any channel after a random period of time varying from 5 minutes to 4 hours. No correlation has been found between the frequency selected during scanning and the occurrence of the error.

Observations

• Decreasing the channel scan rate slows the error occurrence down.
• Increasing the channel scan rate does not increase the error occurrence up in a linear fashion but does have some effect.
• Experimented with kernel version 6.7.0-socfpga on the same platform with microcode version 86 resulted in the same behavior.
• Experimented with an Intel i9 system running kernel 6.8.8 and microcode version 86 resulted in the same behavior when running the same channel switching application.
• Experimented with disabling hardware encryption with no change in behavior.
• Experimented with other module parameters with no effect (amsdu_size, power_save)
• Bluetooth is disabled (bt_coex_active = false)

kernel log output is shown below and attached for reference.

[13994.502353] iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.
[13994.509832] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[13994.515426] iwlwifi 0000:01:00.0: Transport status: 0x0000004B, valid: 6
[13994.522175] iwlwifi 0000:01:00.0: Loaded firmware version: 83.ec13314b.0 gl-c0-fm-c0-83.ucode
[13994.530766] iwlwifi 0000:01:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[13994.537803] iwlwifi 0000:01:00.0: 0x000002F0 | trm_hw_status0
[13994.543592] iwlwifi 0000:01:00.0: 0x00000000 | trm_hw_status1
[13994.549452] iwlwifi 0000:01:00.0: 0x002C280A | branchlink2
[13994.554969] iwlwifi 0000:01:00.0: 0x00015BEA | interruptlink1
[13994.560815] iwlwifi 0000:01:00.0: 0x00015BEA | interruptlink2
[13994.566671] iwlwifi 0000:01:00.0: 0x00015BF2 | data1
[13994.571684] iwlwifi 0000:01:00.0: 0x00000010 | data2
[13994.576670] iwlwifi 0000:01:00.0: 0x00000000 | data3
[13994.581672] iwlwifi 0000:01:00.0: 0x00000000 | beacon time
[13994.587202] iwlwifi 0000:01:00.0: 0xF77E0E95 | tsf low
[13994.592421] iwlwifi 0000:01:00.0: 0x00000000 | tsf hi
[13994.597514] iwlwifi 0000:01:00.0: 0x00000000 | time gp1
[13994.602861] iwlwifi 0000:01:00.0: 0xF78099D2 | time gp2
[13994.608160] iwlwifi 0000:01:00.0: 0x00000001 | uCode revision type
[13994.614395] iwlwifi 0000:01:00.0: 0x00000053 | uCode version major
[13994.620622] iwlwifi 0000:01:00.0: 0xEC13314B | uCode version minor
[13994.626826] iwlwifi 0000:01:00.0: 0x00000472 | hw version
[13994.632262] iwlwifi 0000:01:00.0: 0x00C80002 | board version
[13994.638061] iwlwifi 0000:01:00.0: 0x8072FD04 | hcmd
[13994.642966] iwlwifi 0000:01:00.0: 0x00020000 | isr0
[13994.647889] iwlwifi 0000:01:00.0: 0x00000000 | isr1
[13994.652786] iwlwifi 0000:01:00.0: 0x48F80002 | isr2
[13994.657701] iwlwifi 0000:01:00.0: 0x00C0000C | isr3
[13994.662600] iwlwifi 0000:01:00.0: 0x00000000 | isr4
[13994.667515] iwlwifi 0000:01:00.0: 0x00220103 | last cmd Id
[13994.673021] iwlwifi 0000:01:00.0: 0x00015BF2 | wait_event
[13994.678456] iwlwifi 0000:01:00.0: 0x00000000 | l2p_control
[13994.683962] iwlwifi 0000:01:00.0: 0x00000000 | l2p_duration
[13994.689577] iwlwifi 0000:01:00.0: 0x003C0000 | l2p_mhvalid
[13994.695085] iwlwifi 0000:01:00.0: 0x00000007 | l2p_addr_match
[13994.700867] iwlwifi 0000:01:00.0: 0x00000009 | lmpm_pmg_sel
[13994.706461] iwlwifi 0000:01:00.0: 0x00000000 | timestamp
[13994.711814] iwlwifi 0000:01:00.0: 0x0000E808 | flow_handler
[13994.717605] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[13994.723199] iwlwifi 0000:01:00.0: Transport status: 0x0000004B, valid: 6
[13994.729937] iwlwifi 0000:01:00.0: Loaded firmware version: 83.ec13314b.0 gl-c0-fm-c0-83.ucode
[13994.738587] iwlwifi 0000:01:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[13994.745576] iwlwifi 0000:01:00.0: 0x000002F0 | trm_hw_status0
[13994.751360] iwlwifi 0000:01:00.0: 0x00000000 | trm_hw_status1
[13994.757145] iwlwifi 0000:01:00.0: 0x002C280A | branchlink2
[13994.762654] iwlwifi 0000:01:00.0: 0x002B79C6 | interruptlink1
[13994.768445] iwlwifi 0000:01:00.0: 0x002B79C6 | interruptlink2
[13994.774215] iwlwifi 0000:01:00.0: 0x002A50FC | data1
[13994.779218] iwlwifi 0000:01:00.0: 0x00000010 | data2
[13994.784201] iwlwifi 0000:01:00.0: 0x00000000 | data3
[13994.789200] iwlwifi 0000:01:00.0: 0x00000000 | beacon time
[13994.794705] iwlwifi 0000:01:00.0: 0xF77E0E95 | tsf low
[13994.799878] iwlwifi 0000:01:00.0: 0x00000000 | tsf hi
[13994.804950] iwlwifi 0000:01:00.0: 0x00000000 | time gp1
[13994.810210] iwlwifi 0000:01:00.0: 0xF78099D1 | time gp2
[13994.815458] iwlwifi 0000:01:00.0: 0x00000001 | uCode revision type
[13994.821676] iwlwifi 0000:01:00.0: 0x00000053 | uCode version major
[13994.827903] iwlwifi 0000:01:00.0: 0xEC13314B | uCode version minor
[13994.834110] iwlwifi 0000:01:00.0: 0x00000472 | hw version
[13994.839538] iwlwifi 0000:01:00.0: 0x00C80002 | board version
[13994.845218] iwlwifi 0000:01:00.0: 0x8070FC08 | hcmd
[13994.850133] iwlwifi 0000:01:00.0: 0x00020000 | isr0
[13994.855031] iwlwifi 0000:01:00.0: 0x00000000 | isr1
[13994.859943] iwlwifi 0000:01:00.0: 0x58F80082 | isr2
[13994.864840] iwlwifi 0000:01:00.0: 0x00C0000C | isr3
[13994.869754] iwlwifi 0000:01:00.0: 0x00000000 | isr4
[13994.874650] iwlwifi 0000:01:00.0: 0x00000000 | last cmd Id
[13994.880171] iwlwifi 0000:01:00.0: 0x002A50FC | wait_event
[13994.885592] iwlwifi 0000:01:00.0: 0x00000000 | l2p_control
[13994.891118] iwlwifi 0000:01:00.0: 0x00000000 | l2p_duration
[13994.896713] iwlwifi 0000:01:00.0: 0x003C0000 | l2p_mhvalid
[13994.902238] iwlwifi 0000:01:00.0: 0x00000007 | l2p_addr_match
[13994.908024] iwlwifi 0000:01:00.0: 0x00000028 | lmpm_pmg_sel
[13994.913620] iwlwifi 0000:01:00.0: 0x00000000 | timestamp
[13994.918967] iwlwifi 0000:01:00.0: 0x0000E808 | flow_handler
[13994.924659] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[13994.930271] iwlwifi 0000:01:00.0: Transport status: 0x0000004B, valid: 7
[13994.937035] iwlwifi 0000:01:00.0: 0x2010300E | ADVANCED_SYSASSERT
[13994.943156] iwlwifi 0000:01:00.0: 0x00000000 | umac branchlink1
[13994.949124] iwlwifi 0000:01:00.0: 0xC00809B0 | umac branchlink2
[13994.955066] iwlwifi 0000:01:00.0: 0x8025471A | umac interruptlink1
[13994.961309] iwlwifi 0000:01:00.0: 0xC008254C | umac interruptlink2
[13994.967536] iwlwifi 0000:01:00.0: 0x00000002 | umac data1
[13994.972960] iwlwifi 0000:01:00.0: 0x000000FF | umac data2
[13994.978481] iwlwifi 0000:01:00.0: 0x00000003 | umac data3
[13994.983905] iwlwifi 0000:01:00.0: 0x00000053 | umac major
[13994.989348] iwlwifi 0000:01:00.0: 0xEC13314B | umac minor
[13994.994769] iwlwifi 0000:01:00.0: 0xF78099C4 | frame pointer
[13995.000465] iwlwifi 0000:01:00.0: 0xD00D5E54 | stack pointer
[13995.006147] iwlwifi 0000:01:00.0: 0x00910309 | last host cmd
[13995.011851] iwlwifi 0000:01:00.0: 0x00000000 | isr status reg
[13995.017755] iwlwifi 0000:01:00.0: TCM1 status:
[13995.022219] iwlwifi 0000:01:00.0: 0x00000070 | error ID
[13995.027475] iwlwifi 0000:01:00.0: 0x0000184E | tcm branchlink2
[13995.033330] iwlwifi 0000:01:00.0: 0x00001C44 | tcm interruptlink1
[13995.039463] iwlwifi 0000:01:00.0: 0x00001C44 | tcm interruptlink2
[13995.045579] iwlwifi 0000:01:00.0: 0x40000000 | tcm data1
[13995.050928] iwlwifi 0000:01:00.0: 0xDEADBEEF | tcm data2
[13995.056261] iwlwifi 0000:01:00.0: 0xDEADBEEF | tcm data3
[13995.061609] iwlwifi 0000:01:00.0: 0x000018AC | tcm log PC
[13995.067050] iwlwifi 0000:01:00.0: 0x00803FF0 | tcm frame pointer
[13995.073084] iwlwifi 0000:01:00.0: 0x00803F4C | tcm stack pointer
[13995.079129] iwlwifi 0000:01:00.0: 0x00000000 | tcm msg ID
[13995.084549] iwlwifi 0000:01:00.0: 0x4000000F | tcm ISR status
[13995.090332] iwlwifi 0000:01:00.0: 0x000002F0 | tcm HW status[0]
[13995.096277] iwlwifi 0000:01:00.0: 0x00000000 | tcm HW status[1]
[13995.102232] iwlwifi 0000:01:00.0: 0x00000000 | tcm HW status[2]
[13995.108192] iwlwifi 0000:01:00.0: 0x40008300 | tcm HW status[3]
[13995.114136] iwlwifi 0000:01:00.0: 0x00000000 | tcm HW status[4]
[13995.120106] iwlwifi 0000:01:00.0: 0x00000000 | tcm SW status[0]
[13995.126169] iwlwifi 0000:01:00.0: RCM1 status:
[13995.130656] iwlwifi 0000:01:00.0: 0x00000070 | error ID
[13995.135903] iwlwifi 0000:01:00.0: 0x00001B9E | rcm branchlink2
[13995.141778] iwlwifi 0000:01:00.0: 0x00002178 | rcm interruptlink1
[13995.147914] iwlwifi 0000:01:00.0: 0x00002178 | rcm interruptlink2
[13995.154031] iwlwifi 0000:01:00.0: 0x20000000 | rcm data1
[13995.159376] iwlwifi 0000:01:00.0: 0xDEADBEEF | rcm data2
[13995.164709] iwlwifi 0000:01:00.0: 0xDEADBEEF | rcm data3
[13995.170056] iwlwifi 0000:01:00.0: 0x00001C00 | rcm log PC
[13995.175476] iwlwifi 0000:01:00.0: 0x00803FF0 | rcm frame pointer
[13995.181525] iwlwifi 0000:01:00.0: 0x00803F4C | rcm stack pointer
[13995.187583] iwlwifi 0000:01:00.0: 0x00000000 | rcm msg ID
[13995.193005] iwlwifi 0000:01:00.0: 0x20000000 | rcm ISR status
[13995.198787] iwlwifi 0000:01:00.0: 0x00020400 | frame HW status
[13995.204642] iwlwifi 0000:01:00.0: 0x00000000 | LMAC-to-RCM request mbox
[13995.211298] iwlwifi 0000:01:00.0: 0x00000000 | RCM-to-LMAC request mbox
[13995.217964] iwlwifi 0000:01:00.0: 0x00000000 | MAC header control
[13995.224081] iwlwifi 0000:01:00.0: 0x00000000 | MAC header addr1 low
[13995.230383] iwlwifi 0000:01:00.0: 0x003C0000 | MAC header info
[13995.236238] iwlwifi 0000:01:00.0: 0x00000000 | MAC header error
[13995.242313] iwlwifi 0000:01:00.0: TCM2 status:
[13995.246775] iwlwifi 0000:01:00.0: 0x00000070 | error ID
[13995.252046] iwlwifi 0000:01:00.0: 0x0000184E | tcm branchlink2
[13995.257921] iwlwifi 0000:01:00.0: 0x00001C44 | tcm interruptlink1
[13995.264039] iwlwifi 0000:01:00.0: 0x00001C44 | tcm interruptlink2
[13995.270169] iwlwifi 0000:01:00.0: 0x40000000 | tcm data1
[13995.275502] iwlwifi 0000:01:00.0: 0xDEADBEEF | tcm data2
[13995.280850] iwlwifi 0000:01:00.0: 0xDEADBEEF | tcm data3
[13995.286183] iwlwifi 0000:01:00.0: 0x000018AC | tcm log PC
[13995.291616] iwlwifi 0000:01:00.0: 0x00803FF0 | tcm frame pointer
[13995.297666] iwlwifi 0000:01:00.0: 0x00803F4C | tcm stack pointer
[13995.303696] iwlwifi 0000:01:00.0: 0x00000000 | tcm msg ID
[13995.309132] iwlwifi 0000:01:00.0: 0x40000000 | tcm ISR status
[13995.314901] iwlwifi 0000:01:00.0: 0x000002F0 | tcm HW status[0]
[13995.320861] iwlwifi 0000:01:00.0: 0x00000000 | tcm HW status[1]
[13995.326804] iwlwifi 0000:01:00.0: 0x00000000 | tcm HW status[2]
[13995.332765] iwlwifi 0000:01:00.0: 0x00008000 | tcm HW status[3]
[13995.338727] iwlwifi 0000:01:00.0: 0x00000000 | tcm HW status[4]
[13995.344671] iwlwifi 0000:01:00.0: 0x00000000 | tcm SW status[0]
[13995.350741] iwlwifi 0000:01:00.0: RCM2 status:
[13995.355203] iwlwifi 0000:01:00.0: 0x00000070 | error ID
[13995.360464] iwlwifi 0000:01:00.0: 0x00001B9E | rcm branchlink2
[13995.366320] iwlwifi 0000:01:00.0: 0x00002178 | rcm interruptlink1
[13995.372458] iwlwifi 0000:01:00.0: 0x00002178 | rcm interruptlink2
[13995.378596] iwlwifi 0000:01:00.0: 0x20000000 | rcm data1
[13995.383929] iwlwifi 0000:01:00.0: 0xDEADBEEF | rcm data2
[13995.389272] iwlwifi 0000:01:00.0: 0xDEADBEEF | rcm data3
[13995.394604] iwlwifi 0000:01:00.0: 0x00001C00 | rcm log PC
[13995.400040] iwlwifi 0000:01:00.0: 0x00803FF0 | rcm frame pointer
[13995.406069] iwlwifi 0000:01:00.0: 0x00803F4C | rcm stack pointer
[13995.412112] iwlwifi 0000:01:00.0: 0x00000000 | rcm msg ID
[13995.417546] iwlwifi 0000:01:00.0: 0x20000000 | rcm ISR status
[13995.423316] iwlwifi 0000:01:00.0: 0x00020400 | frame HW status
[13995.429194] iwlwifi 0000:01:00.0: 0x00000000 | LMAC-to-RCM request mbox
[13995.435834] iwlwifi 0000:01:00.0: 0x00000000 | RCM-to-LMAC request mbox
[13995.442495] iwlwifi 0000:01:00.0: 0x00000000 | MAC header control
[13995.448630] iwlwifi 0000:01:00.0: 0x00000000 | MAC header addr1 low
[13995.454924] iwlwifi 0000:01:00.0: 0x003C0000 | MAC header info
[13995.460795] iwlwifi 0000:01:00.0: 0x00000000 | MAC header error
[13995.466792] iwlwifi 0000:01:00.0: IML/ROM dump:
[13995.471358] iwlwifi 0000:01:00.0: 0x00000B03 | IML/ROM error/state
[13995.477627] iwlwifi 0000:01:00.0: 0x0000E3CD | IML/ROM data1
[13995.483360] iwlwifi 0000:01:00.0: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
[13995.489973] iwlwifi 0000:01:00.0: Fseq Registers:
[13995.494734] iwlwifi 0000:01:00.0: 0x67A00000 | FSEQ_ERROR_CODE
[13995.500649] iwlwifi 0000:01:00.0: 0x80B00004 | FSEQ_TOP_INIT_VERSION
[13995.507083] iwlwifi 0000:01:00.0: 0x00550000 | FSEQ_CNVIO_INIT_VERSION
[13995.513673] iwlwifi 0000:01:00.0: 0x0000AA14 | FSEQ_OTP_VERSION
[13995.519667] iwlwifi 0000:01:00.0: 0x0000000F | FSEQ_TOP_CONTENT_VERSION
[13995.526343] iwlwifi 0000:01:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[13995.532339] iwlwifi 0000:01:00.0: 0x02001910 | FSEQ_CNVI_ID
[13995.537989] iwlwifi 0000:01:00.0: 0x02001910 | FSEQ_CNVR_ID
[13995.543639] iwlwifi 0000:01:00.0: 0x02001910 | CNVI_AUX_MISC_CHIP
[13995.549859] iwlwifi 0000:01:00.0: 0x02001910 | CNVR_AUX_MISC_CHIP
[13995.556028] iwlwifi 0000:01:00.0: 0x00001BEF | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[13995.563951] iwlwifi 0000:01:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[13995.572213] iwlwifi 0000:01:00.0: 0x00550000 | FSEQ_PREV_CNVIO_INIT_VERSION
[13995.579256] iwlwifi 0000:01:00.0: 0x00B00004 | FSEQ_WIFI_FSEQ_VERSION
[13995.585775] iwlwifi 0000:01:00.0: 0x71E95448 | FSEQ_BT_FSEQ_VERSION
[13995.592124] iwlwifi 0000:01:00.0: 0x000000C8 | FSEQ_CLASS_TP_VERSION
[13995.598773] iwlwifi 0000:01:00.0: UMAC CURRENT PC: 0x8026935a
[13995.604594] iwlwifi 0000:01:00.0: LMAC1 CURRENT PC: 0xd0
[13995.609995] iwlwifi 0000:01:00.0: LMAC2 CURRENT PC: 0xd0
[13995.615366] iwlwifi 0000:01:00.0: UMAC CURRENT PC 1: 0x80269358
[13995.621368] iwlwifi 0000:01:00.0: TCM1 CURRENT PC: 0xd0
[13995.626653] iwlwifi 0000:01:00.0: RCM1 CURRENT PC: 0xd0
[13995.631952] iwlwifi 0000:01:00.0: RCM2 CURRENT PC: 0xd0
[13995.637357] iwlwifi 0000:01:00.0: Function Scratch status:
[13995.642870] iwlwifi 0000:01:00.0: 0x01010100 | Func Scratch
[13995.789310] iwlwifi 0000:01:00.0: FW error in SYNC CMD LINK_CONFIG_CMD
[13995.798620] iwlwifi 0000:01:00.0: Failed to send LINK_CONFIG_CMD (action:2): -5
[13995.805991] iwlwifi 0000:01:00.0: PHY ctxt cmd error. ret=-5
[14079.719912] iwlwifi 0000:01:00.0: PHY ctxt cmd error. ret=-5
[14079.725674] iwlwifi 0000:01:00.0: Failed to add PHY context

[DeancR_Intel]

Hi jamez70,

Thank you for posting in the Community!

Do please wait as this concern will be investigated internally to be able to provide a resolution to your request. I will get back to your once I have the necessary information.

Best regards,

Dean R.

Intel Customer Support Technician

[jamez70]

Thank you very much for investigating this issue. I wanted to provide a few updates:

I have moved on to experimenting with the linux-next kernel as I discovered that Intel development was occurring there. I had previously attempted to merge the changes from linux-next into the 6.7.0 kernel I was experimenting with but this was very cumbersome.

After moving to this newer kernel, the same issue is still occurring with rapid channel scanning as before so the request is still valid even with the leading edge BE200 iwlwifi and firmware version 94.

In addition, I have discovered and resolved another issue you may be interested to know about. Lets suppose I had been scanning a WiFi-6e channel on a 6GHz channel, and then I bring the interface down when the last channel was a  6GHz channel. If I bring the interface back up, the driver will crash repeatedly each time I attempt to bring the interface back up. To alleviate this crash, I implemented a change of the channel back to a 2.4GHz channel then bring the interface back down. What I believe is happening is that when the interface is brought back up, it attempts to switch back to the 6GHz channel but is not allowed to do so because the 6GHz is disabled until a scan is performed.

[RandyT_Intel]

Hi jamez70,

May I confirm if the BE200 units are self-integrated or pre-installed?

Best regards, 

Randy T. 

Intel Customer Support Technician 

[jamez70]

Randy,

I am not exactly sure what you are referring to - but I believe they are self integrated units placed into custom hardware. There will be two M.2 BE200 cards in each installation. If it helps, the number of units will be in the thousands. Currently, I am attempting to get the exceptions down to a minimum before we can deploy these in the field.

[DeancR_Intel]

Hi jamez70,

Thank you for getting back to me. I will further check this internally and get back to you once I have the necessary information.

Best regards,

Dean R.

Intel Customer Support Technician

[DeancR_Intel]

Hi jamez70,

Could you please clarify whether the wireless card in your system is pre-installed (included in the system) or if you have changed or installed the wireless card yourself?

I also recommend checking out our article on Linux* Support for Intel® Wireless Adapters and trying to install the latest stable version of the mainline kernel.

Best regards,

Dean R.

Intel Customer Support Technician

[DeancR_Intel]

Hi jamez70,

I wanted to follow up on the previous message regarding your inquiry. Have you had a chance to review it? If you have any questions or need further information, please let me know.

Best regards,

Dean R.

Intel Customer Support Technician

[jamez70]

The wireless card was installed by myself and not pre-installed in a system

[DeancR_Intel]

Hi jamez70,

This is just a soft follow up for the recommendation in checking out our article on Linux* Support for Intel® Wireless Adapters. Any chance that you have tried the steps there?

Let me know if you have questions

Best regards,

Dean R.

Intel Customer Support Technician

[DeancR_Intel]

Hi jamez70,

Intel wireless firmware and drivers are designed to work with specific versions of the Linux kernel. This means that only certain versions of the firmware and drivers will function correctly with particular kernel versions. Using the correct kernel version ensures stability and proper operation of your wireless device. Intel wireless drivers are part of the upstream Linux kernel and are available through regular channels, distributions, or the Linux kernel archives. Support is provided only for the kernel version that includes the driver.

For technical issues or questions, users are encouraged to visit Bugzilla to search for solutions or submit new bug reports. Bug List

The Intel wireless drivers are included in the Linux kernel. To obtain the latest Intel wireless drivers, we recommend installing the latest (and stable) version of upstream Linux kernel. The wireless device requires firmware to operate. Firmware usually ships with your distribution, or you can download it from the repository firmware git tree. Each download provides firmware under its own license.

See the link for reference:

Linux* Support for Intel® Wireless Adapters

I will be closing this inquiry and no longer be monitored. Thank you.

Best regards,

Dean R.

Intel Customer Support Technician