| Message ID | 20181003071513.13004-3-kai.heng.feng@canonical.com (mailing list archive) |
|---|---|
| State | Superseded |
| Delegated to: | Luca Coelho |
| Headers | show |
| Series | None | expand |
On Wed, 2018-10-03 at 15:15 +0800, Kai-Heng Feng wrote: > To avoid the firmware loading race between Bluetooth and WiFi on Intel > 8260, load firmware exclusively when BT_INTEL is enabled. > > Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com> > --- Where is this coming from? Can you explain what "the firmware loading race" is? > .../net/wireless/intel/iwlwifi/pcie/trans.c | 37 ++++++++++++++++++- > 1 file changed, 36 insertions(+), 1 deletion(-) > > diff --git a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c > index cc8c53dc0ab6..c30d3989e2a8 100644 > --- a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c > +++ b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c > @@ -71,6 +71,7 @@ > #include <linux/vmalloc.h> > #include <linux/pm_runtime.h> > #include <linux/module.h> > +#include <linux/intel-wifi-bt.h> I don't see this upstream. Is it something that was recently added? Looks odd... Regardless, this should also be protected on CONFIG_BT_INTEL. > #include "iwl-drv.h" > #include "iwl-trans.h" > @@ -1335,6 +1336,10 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, > bool hw_rfkill; > int ret; > > +#if IS_ENABLED(CONFIG_BT_INTEL) > + void (*firmware_lock_func)(void); > + void (*firmware_unlock_func)(void); > +#endif > /* This may fail if AMT took ownership of the device */ > if (iwl_pcie_prepare_card_hw(trans)) { > IWL_WARN(trans, "Exit HW not ready\n"); > @@ -1394,6 +1399,7 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, > * RF-Kill switch is toggled, we will find out after having loaded > * the firmware and return the proper value to the caller. > */ > + Stray empty line. > iwl_enable_fw_load_int(trans); > > /* really make sure rfkill handshake bits are cleared */ > @@ -1401,8 +1407,37 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, > iwl_write32(trans, CSR_UCODE_DRV_GP1_CLR, CSR_UCODE_SW_BIT_RFKILL); > > /* Load the given image to the HW */ > - if (trans->cfg->device_family >= IWL_DEVICE_FAMILY_8000) > + if (trans->cfg->device_family >= IWL_DEVICE_FAMILY_8000) { > +#if IS_ENABLED(CONFIG_BT_INTEL) > + firmware_lock_func = symbol_request(btintel_firmware_lock); > + firmware_unlock_func = symbol_request(btintel_firmware_unlock); > + if (!firmware_lock_func || !firmware_unlock_func) { > + if (firmware_lock_func) { > + symbol_put(btintel_firmware_lock); > + firmware_lock_func = NULL; > + } > + > + if (firmware_unlock_func) { > + symbol_put(btintel_firmware_unlock); > + firmware_unlock_func = NULL; > + } > + } > + > + if (firmware_lock_func) > + firmware_lock_func(); > +#endif > ret = iwl_pcie_load_given_ucode_8000(trans, fw); > + > +#if IS_ENABLED(CONFIG_BT_INTEL) > + if (firmware_unlock_func) { > + firmware_unlock_func(); > + symbol_put(btintel_firmware_lock); > + firmware_lock_func = NULL; > + symbol_put(btintel_firmware_unlock); > + firmware_unlock_func = NULL; > + } > +#endif > + } > else > ret = iwl_pcie_load_given_ucode(trans, fw); > I'm not sure I like adding this BT-specific stuff here, especially not without a detailed explanation. Did you also send the other patches in this series to linux-wireless? I can't see them... -- Cheers, Luca.
> On Oct 3, 2018, at 3:24 PM, Luciano Coelho <luciano.coelho@intel.com> wrote: > > On Wed, 2018-10-03 at 15:15 +0800, Kai-Heng Feng wrote: >> To avoid the firmware loading race between Bluetooth and WiFi on Intel >> 8260, load firmware exclusively when BT_INTEL is enabled. >> >> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com> >> --- > > Where is this coming from? Can you explain what "the firmware loading > race" is? Looks like the patch is not correctly threaded. I’ll resend the series. > > >> .../net/wireless/intel/iwlwifi/pcie/trans.c | 37 ++++++++++++++++++- >> 1 file changed, 36 insertions(+), 1 deletion(-) >> >> diff --git a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c >> index cc8c53dc0ab6..c30d3989e2a8 100644 >> --- a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c >> +++ b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c >> @@ -71,6 +71,7 @@ >> #include <linux/vmalloc.h> >> #include <linux/pm_runtime.h> >> #include <linux/module.h> >> +#include <linux/intel-wifi-bt.h> > > I don't see this upstream. Is it something that was recently added? > Looks odd... > > Regardless, this should also be protected on CONFIG_BT_INTEL. Thanks, I’ll update this one. > > >> #include "iwl-drv.h" >> #include "iwl-trans.h" >> @@ -1335,6 +1336,10 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, >> bool hw_rfkill; >> int ret; >> >> +#if IS_ENABLED(CONFIG_BT_INTEL) >> + void (*firmware_lock_func)(void); >> + void (*firmware_unlock_func)(void); >> +#endif >> /* This may fail if AMT took ownership of the device */ >> if (iwl_pcie_prepare_card_hw(trans)) { >> IWL_WARN(trans, "Exit HW not ready\n"); >> @@ -1394,6 +1399,7 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, >> * RF-Kill switch is toggled, we will find out after having loaded >> * the firmware and return the proper value to the caller. >> */ >> + > > Stray empty line. > >> iwl_enable_fw_load_int(trans); >> >> /* really make sure rfkill handshake bits are cleared */ >> @@ -1401,8 +1407,37 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, >> iwl_write32(trans, CSR_UCODE_DRV_GP1_CLR, CSR_UCODE_SW_BIT_RFKILL); >> >> /* Load the given image to the HW */ >> - if (trans->cfg->device_family >= IWL_DEVICE_FAMILY_8000) >> + if (trans->cfg->device_family >= IWL_DEVICE_FAMILY_8000) { >> +#if IS_ENABLED(CONFIG_BT_INTEL) >> + firmware_lock_func = symbol_request(btintel_firmware_lock); >> + firmware_unlock_func = symbol_request(btintel_firmware_unlock); >> + if (!firmware_lock_func || !firmware_unlock_func) { >> + if (firmware_lock_func) { >> + symbol_put(btintel_firmware_lock); >> + firmware_lock_func = NULL; >> + } >> + >> + if (firmware_unlock_func) { >> + symbol_put(btintel_firmware_unlock); >> + firmware_unlock_func = NULL; >> + } >> + } >> + >> + if (firmware_lock_func) >> + firmware_lock_func(); >> +#endif >> ret = iwl_pcie_load_given_ucode_8000(trans, fw); >> + >> +#if IS_ENABLED(CONFIG_BT_INTEL) >> + if (firmware_unlock_func) { >> + firmware_unlock_func(); >> + symbol_put(btintel_firmware_lock); >> + firmware_lock_func = NULL; >> + symbol_put(btintel_firmware_unlock); >> + firmware_unlock_func = NULL; >> + } >> +#endif >> + } >> else >> ret = iwl_pcie_load_given_ucode(trans, fw); >> > > I'm not sure I like adding this BT-specific stuff here, especially not > without a detailed explanation. > > Did you also send the other patches in this series to linux-wireless? I > can't see them… I’ll resend one soon. Thanks! Kai-Heng > > -- > Cheers, > Luca.
I think Canonical were facing some wifi fw load error from some 8260 earlier module during the BT still loading the fw. I believe we had later 8260 sku that fixed this issue. Hi Kai-Heng, Can you check with OEM for which SKU they are reporting the issue ? Kai Heng Feng <kai.heng.feng@canonical.com> 於 2018年10月3日 週三 下午3:28寫道： > > > > > On Oct 3, 2018, at 3:24 PM, Luciano Coelho <luciano.coelho@intel.com> wrote: > > > > On Wed, 2018-10-03 at 15:15 +0800, Kai-Heng Feng wrote: > >> To avoid the firmware loading race between Bluetooth and WiFi on Intel > >> 8260, load firmware exclusively when BT_INTEL is enabled. > >> > >> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com> > >> --- > > > > Where is this coming from? Can you explain what "the firmware loading > > race" is? > > Looks like the patch is not correctly threaded. I’ll resend the series. > > > > > > >> .../net/wireless/intel/iwlwifi/pcie/trans.c | 37 ++++++++++++++++++- > >> 1 file changed, 36 insertions(+), 1 deletion(-) > >> > >> diff --git a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c > >> index cc8c53dc0ab6..c30d3989e2a8 100644 > >> --- a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c > >> +++ b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c > >> @@ -71,6 +71,7 @@ > >> #include <linux/vmalloc.h> > >> #include <linux/pm_runtime.h> > >> #include <linux/module.h> > >> +#include <linux/intel-wifi-bt.h> > > > > I don't see this upstream. Is it something that was recently added? > > Looks odd... > > > > Regardless, this should also be protected on CONFIG_BT_INTEL. > > Thanks, I’ll update this one. > > > > > > >> #include "iwl-drv.h" > >> #include "iwl-trans.h" > >> @@ -1335,6 +1336,10 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, > >> bool hw_rfkill; > >> int ret; > >> > >> +#if IS_ENABLED(CONFIG_BT_INTEL) > >> + void (*firmware_lock_func)(void); > >> + void (*firmware_unlock_func)(void); > >> +#endif > >> /* This may fail if AMT took ownership of the device */ > >> if (iwl_pcie_prepare_card_hw(trans)) { > >> IWL_WARN(trans, "Exit HW not ready\n"); > >> @@ -1394,6 +1399,7 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, > >> * RF-Kill switch is toggled, we will find out after having loaded > >> * the firmware and return the proper value to the caller. > >> */ > >> + > > > > Stray empty line. > > > >> iwl_enable_fw_load_int(trans); > >> > >> /* really make sure rfkill handshake bits are cleared */ > >> @@ -1401,8 +1407,37 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, > >> iwl_write32(trans, CSR_UCODE_DRV_GP1_CLR, CSR_UCODE_SW_BIT_RFKILL); > >> > >> /* Load the given image to the HW */ > >> - if (trans->cfg->device_family >= IWL_DEVICE_FAMILY_8000) > >> + if (trans->cfg->device_family >= IWL_DEVICE_FAMILY_8000) { > >> +#if IS_ENABLED(CONFIG_BT_INTEL) > >> + firmware_lock_func = symbol_request(btintel_firmware_lock); > >> + firmware_unlock_func = symbol_request(btintel_firmware_unlock); > >> + if (!firmware_lock_func || !firmware_unlock_func) { > >> + if (firmware_lock_func) { > >> + symbol_put(btintel_firmware_lock); > >> + firmware_lock_func = NULL; > >> + } > >> + > >> + if (firmware_unlock_func) { > >> + symbol_put(btintel_firmware_unlock); > >> + firmware_unlock_func = NULL; > >> + } > >> + } > >> + > >> + if (firmware_lock_func) > >> + firmware_lock_func(); > >> +#endif > >> ret = iwl_pcie_load_given_ucode_8000(trans, fw); > >> + > >> +#if IS_ENABLED(CONFIG_BT_INTEL) > >> + if (firmware_unlock_func) { > >> + firmware_unlock_func(); > >> + symbol_put(btintel_firmware_lock); > >> + firmware_lock_func = NULL; > >> + symbol_put(btintel_firmware_unlock); > >> + firmware_unlock_func = NULL; > >> + } > >> +#endif > >> + } > >> else > >> ret = iwl_pcie_load_given_ucode(trans, fw); > >> > > > > I'm not sure I like adding this BT-specific stuff here, especially not > > without a detailed explanation. > > > > Did you also send the other patches in this series to linux-wireless? I > > can't see them… > > I’ll resend one soon. > > Thanks! > > Kai-Heng > > > > > -- > > Cheers, > > Luca. >
> On Oct 3, 2018, at 3:29 PM, Matt Chen <mattsled@gmail.com> wrote: > > I think Canonical were facing some wifi fw load error from some 8260 > earlier module during the BT still loading the fw. > I believe we had later 8260 sku that fixed this issue. But there are already 8260 that is affected by this bug in the wild. Search "Bluetooth: hci0: Failed to send firmware data (-38)” and there are lots of user are affected. Kai-Heng > > Hi Kai-Heng, > > Can you check with OEM for which SKU they are reporting the issue ? > Kai Heng Feng <kai.heng.feng@canonical.com> 於 2018年10月3日 週三 下午3:28寫道： >> >> >> >>> On Oct 3, 2018, at 3:24 PM, Luciano Coelho <luciano.coelho@intel.com> wrote: >>> >>> On Wed, 2018-10-03 at 15:15 +0800, Kai-Heng Feng wrote: >>>> To avoid the firmware loading race between Bluetooth and WiFi on Intel >>>> 8260, load firmware exclusively when BT_INTEL is enabled. >>>> >>>> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com> >>>> --- >>> >>> Where is this coming from? Can you explain what "the firmware loading >>> race" is? >> >> Looks like the patch is not correctly threaded. I’ll resend the series. >> >>> >>> >>>> .../net/wireless/intel/iwlwifi/pcie/trans.c | 37 ++++++++++++++++++- >>>> 1 file changed, 36 insertions(+), 1 deletion(-) >>>> >>>> diff --git a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c >>>> index cc8c53dc0ab6..c30d3989e2a8 100644 >>>> --- a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c >>>> +++ b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c >>>> @@ -71,6 +71,7 @@ >>>> #include <linux/vmalloc.h> >>>> #include <linux/pm_runtime.h> >>>> #include <linux/module.h> >>>> +#include <linux/intel-wifi-bt.h> >>> >>> I don't see this upstream. Is it something that was recently added? >>> Looks odd... >>> >>> Regardless, this should also be protected on CONFIG_BT_INTEL. >> >> Thanks, I’ll update this one. >> >>> >>> >>>> #include "iwl-drv.h" >>>> #include "iwl-trans.h" >>>> @@ -1335,6 +1336,10 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, >>>> bool hw_rfkill; >>>> int ret; >>>> >>>> +#if IS_ENABLED(CONFIG_BT_INTEL) >>>> + void (*firmware_lock_func)(void); >>>> + void (*firmware_unlock_func)(void); >>>> +#endif >>>> /* This may fail if AMT took ownership of the device */ >>>> if (iwl_pcie_prepare_card_hw(trans)) { >>>> IWL_WARN(trans, "Exit HW not ready\n"); >>>> @@ -1394,6 +1399,7 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, >>>> * RF-Kill switch is toggled, we will find out after having loaded >>>> * the firmware and return the proper value to the caller. >>>> */ >>>> + >>> >>> Stray empty line. >>> >>>> iwl_enable_fw_load_int(trans); >>>> >>>> /* really make sure rfkill handshake bits are cleared */ >>>> @@ -1401,8 +1407,37 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, >>>> iwl_write32(trans, CSR_UCODE_DRV_GP1_CLR, CSR_UCODE_SW_BIT_RFKILL); >>>> >>>> /* Load the given image to the HW */ >>>> - if (trans->cfg->device_family >= IWL_DEVICE_FAMILY_8000) >>>> + if (trans->cfg->device_family >= IWL_DEVICE_FAMILY_8000) { >>>> +#if IS_ENABLED(CONFIG_BT_INTEL) >>>> + firmware_lock_func = symbol_request(btintel_firmware_lock); >>>> + firmware_unlock_func = symbol_request(btintel_firmware_unlock); >>>> + if (!firmware_lock_func || !firmware_unlock_func) { >>>> + if (firmware_lock_func) { >>>> + symbol_put(btintel_firmware_lock); >>>> + firmware_lock_func = NULL; >>>> + } >>>> + >>>> + if (firmware_unlock_func) { >>>> + symbol_put(btintel_firmware_unlock); >>>> + firmware_unlock_func = NULL; >>>> + } >>>> + } >>>> + >>>> + if (firmware_lock_func) >>>> + firmware_lock_func(); >>>> +#endif >>>> ret = iwl_pcie_load_given_ucode_8000(trans, fw); >>>> + >>>> +#if IS_ENABLED(CONFIG_BT_INTEL) >>>> + if (firmware_unlock_func) { >>>> + firmware_unlock_func(); >>>> + symbol_put(btintel_firmware_lock); >>>> + firmware_lock_func = NULL; >>>> + symbol_put(btintel_firmware_unlock); >>>> + firmware_unlock_func = NULL; >>>> + } >>>> +#endif >>>> + } >>>> else >>>> ret = iwl_pcie_load_given_ucode(trans, fw); >>>> >>> >>> I'm not sure I like adding this BT-specific stuff here, especially not >>> without a detailed explanation. >>> >>> Did you also send the other patches in this series to linux-wireless? I >>> can't see them… >> >> I’ll resend one soon. >> >> Thanks! >> >> Kai-Heng >> >>> >>> -- >>> Cheers, >>> Luca. >>
Luciano Coelho <luciano.coelho@intel.com> writes: >> +#if IS_ENABLED(CONFIG_BT_INTEL) >> + if (firmware_unlock_func) { >> + firmware_unlock_func(); >> + symbol_put(btintel_firmware_lock); >> + firmware_lock_func = NULL; >> + symbol_put(btintel_firmware_unlock); >> + firmware_unlock_func = NULL; >> + } >> +#endif >> + } >> else >> ret = iwl_pcie_load_given_ucode(trans, fw); >> > > I'm not sure I like adding this BT-specific stuff here, especially not > without a detailed explanation. This looks like an ugly hack and the commit log tells nothing. This really needs strong justifications to even consider doing something like this.
Hi Kai-Heng, >> I think Canonical were facing some wifi fw load error from some 8260 >> earlier module during the BT still loading the fw. >> I believe we had later 8260 sku that fixed this issue. > > But there are already 8260 that is affected by this bug in the wild. > > Search "Bluetooth: hci0: Failed to send firmware data (-38)” and there are lots of user are affected. which SKUs are these actually. What are the initial details about the boot loader. For the Bluetooth side, you should be able to grab them from dmesg or by running btmon. So I am not in favor of this kind of hack and creating dependencies between drivers. If you only have a hammer, then everything looks like a nail. And this is a massive hammer trying to squash everything. This problem needs to be debugged. And this starts by providing affected SKU information and firmware information. So get the details about the SKU and its Bluetooth and WiFi boot loaders. Regards Marcel
Hi Marcel, > On Oct 4, 2018, at 2:25 AM, Marcel Holtmann <marcel@holtmann.org> wrote: > > Hi Kai-Heng, > >>> I think Canonical were facing some wifi fw load error from some 8260 >>> earlier module during the BT still loading the fw. >>> I believe we had later 8260 sku that fixed this issue. >> >> But there are already 8260 that is affected by this bug in the wild. >> >> Search "Bluetooth: hci0: Failed to send firmware data (-38)” and there are lots of user are affected. > > which SKUs are these actually. What are the initial details about the boot loader. For the Bluetooth side, you should be able to grab them from dmesg or by running btmon. Here’s the dmesg | grep Bluetooth: [ 6.086600] Bluetooth: Core ver 2.22 [ 6.086618] Bluetooth: HCI device and connection manager initialized [ 6.086621] Bluetooth: HCI socket layer initialized [ 6.086625] Bluetooth: L2CAP socket layer initialized [ 6.086632] Bluetooth: SCO socket layer initialized [ 6.107794] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 6.112803] Bluetooth: hci0: Device revision is 5 [ 6.112805] Bluetooth: hci0: Secure boot is enabled [ 6.112805] Bluetooth: hci0: OTP lock is enabled [ 6.112806] Bluetooth: hci0: API lock is enabled [ 6.112807] Bluetooth: hci0: Debug lock is disabled [ 6.112808] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 6.115231] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 6.210353] Bluetooth: hci0: Failed to send firmware data (-38) [ 8.153357] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 8.153358] Bluetooth: BNEP filters: protocol multicast [ 8.153362] Bluetooth: BNEP socket layer initialized [ 13.563790] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 13.568806] Bluetooth: hci0: Device revision is 5 [ 13.568808] Bluetooth: hci0: Secure boot is enabled [ 13.568809] Bluetooth: hci0: OTP lock is enabled [ 13.568810] Bluetooth: hci0: API lock is enabled [ 13.568811] Bluetooth: hci0: Debug lock is disabled [ 13.568813] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 13.569072] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 15.220327] Bluetooth: hci0: Waiting for firmware download to complete [ 15.220805] Bluetooth: hci0: Firmware loaded in 1618764 usecs [ 15.220877] Bluetooth: hci0: Waiting for device to boot [ 15.233031] Bluetooth: hci0: Device booted in 11881 usecs [ 15.233274] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [ 15.236794] Bluetooth: hci0: Applying Intel DDC parameters completed [ 17.232497] Bluetooth: RFCOMM TTY layer initialized [ 17.232505] Bluetooth: RFCOMM socket layer initialized [ 17.232510] Bluetooth: RFCOMM ver 1.11 I’ll file a Bugzilla if we need full dmesg as attachment. > > So I am not in favor of this kind of hack and creating dependencies between drivers. If you only have a hammer, then everything looks like a nail. And this is a massive hammer trying to squash everything. This problem needs to be debugged. And this starts by providing affected SKU information and firmware information. So get the details about the SKU and its Bluetooth and WiFi boot loaders. Apology for the hammer approach, which is the best way I can think of. Of course it’s much better if we can solve this without the ugly hack. Kai-Heng > > Regards > > Marcel >
Hello Marcel, > On Oct 4, 2018, at 2:25 AM, Marcel Holtmann <marcel@holtmann.org> wrote: > > Hi Kai-Heng, > >>> I think Canonical were facing some wifi fw load error from some 8260 >>> earlier module during the BT still loading the fw. >>> I believe we had later 8260 sku that fixed this issue. >> >> But there are already 8260 that is affected by this bug in the wild. >> >> Search "Bluetooth: hci0: Failed to send firmware data (-38)” and there are lots of user are affected. > > which SKUs are these actually. What are the initial details about the boot loader. For the Bluetooth side, you should be able to grab them from dmesg or by running btmon. > > So I am not in favor of this kind of hack and creating dependencies between drivers. If you only have a hammer, then everything looks like a nail. And this is a massive hammer trying to squash everything. This problem needs to be debugged. And this starts by providing affected SKU information and firmware information. So get the details about the SKU and its Bluetooth and WiFi boot loaders. > I have a Lenovo Yoga 900 which presents this problem and has the same bootloader / firmware information as Kai-Heng already posted: [ 5.992426] Bluetooth: Core ver 2.22 [ 5.992438] Bluetooth: HCI device and connection manager initialized [ 5.992442] Bluetooth: HCI socket layer initialized [ 5.992444] Bluetooth: L2CAP socket layer initialized [ 5.992450] Bluetooth: SCO socket layer initialized [ 6.004941] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 6.010922] Bluetooth: hci0: Device revision is 5 [ 6.010923] Bluetooth: hci0: Secure boot is enabled [ 6.010924] Bluetooth: hci0: OTP lock is enabled [ 6.010925] Bluetooth: hci0: API lock is enabled [ 6.010926] Bluetooth: hci0: Debug lock is disabled [ 6.010927] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 6.014253] bluetooth hci0: firmware: direct-loading firmware intel/ibt-11-5.sfi [ 6.014256] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 6.613961] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.613966] Bluetooth: BNEP filters: protocol multicast [ 6.613974] Bluetooth: BNEP socket layer initialized [ 6.983804] Bluetooth: hci0: Failed to send firmware data (-38) And the following product id and revision, from usb-devices: T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=0a2b Rev=00.01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I understand the drawbacks with the approach presented here and lack of clear explanation of the problem, but I can confirm these patches work around the problem on my machine. Is there any extra info or test result I can provide to help debug this? I can also dedicate time to help write a different solution if some guidance is provided. Kai-Heng, did you end up filling a Bugzilla entry for this? Please CC-me on the replies as I'm not receiving emails from linux-bluetooth or linux-wireless anymore. Thanks, -- João Paulo Rechi Vita http://about.me/jprvita
+ linux-bluetooth On Thu, Nov 8, 2018 at 4:08 PM João Paulo Rechi Vita <jprvita@gmail.com> wrote: > > Hello Marcel, > > > On Oct 4, 2018, at 2:25 AM, Marcel Holtmann <marcel@holtmann.org> wrote: > > > > Hi Kai-Heng, > > > >>> I think Canonical were facing some wifi fw load error from some 8260 > >>> earlier module during the BT still loading the fw. > >>> I believe we had later 8260 sku that fixed this issue. > >> > >> But there are already 8260 that is affected by this bug in the wild. > >> > >> Search "Bluetooth: hci0: Failed to send firmware data (-38)” and there are lots of user are affected. > > > > which SKUs are these actually. What are the initial details about the boot loader. For the Bluetooth side, you should be able to grab them from dmesg or by running btmon. > > > > So I am not in favor of this kind of hack and creating dependencies between drivers. If you only have a hammer, then everything looks like a nail. And this is a massive hammer trying to squash everything. This problem needs to be debugged. And this starts by providing affected SKU information and firmware information. So get the details about the SKU and its Bluetooth and WiFi boot loaders. > > > > I have a Lenovo Yoga 900 which presents this problem and has the same bootloader / firmware information as Kai-Heng already posted: > > [ 5.992426] Bluetooth: Core ver 2.22 > [ 5.992438] Bluetooth: HCI device and connection manager initialized > [ 5.992442] Bluetooth: HCI socket layer initialized > [ 5.992444] Bluetooth: L2CAP socket layer initialized > [ 5.992450] Bluetooth: SCO socket layer initialized > [ 6.004941] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 > [ 6.010922] Bluetooth: hci0: Device revision is 5 > [ 6.010923] Bluetooth: hci0: Secure boot is enabled > [ 6.010924] Bluetooth: hci0: OTP lock is enabled > [ 6.010925] Bluetooth: hci0: API lock is enabled > [ 6.010926] Bluetooth: hci0: Debug lock is disabled > [ 6.010927] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 > [ 6.014253] bluetooth hci0: firmware: direct-loading firmware intel/ibt-11-5.sfi > [ 6.014256] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi > [ 6.613961] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > [ 6.613966] Bluetooth: BNEP filters: protocol multicast > [ 6.613974] Bluetooth: BNEP socket layer initialized > [ 6.983804] Bluetooth: hci0: Failed to send firmware data (-38) > > And the following product id and revision, from usb-devices: > > T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 > D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 > P: Vendor=8087 ProdID=0a2b Rev=00.01 > C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > > I understand the drawbacks with the approach presented here and lack of clear explanation of the problem, but I can confirm these patches work around the problem on my machine. Is there any extra info or test result I can provide to help debug this? I can also dedicate time to help write a different solution if some guidance is provided. > > Kai-Heng, did you end up filling a Bugzilla entry for this? > > Please CC-me on the replies as I'm not receiving emails from linux-bluetooth or linux-wireless anymore. > > Thanks, > > -- > João Paulo Rechi Vita > http://about.me/jprvita
Hi Joao Paulo, >>>> I think Canonical were facing some wifi fw load error from some 8260 >>>> earlier module during the BT still loading the fw. >>>> I believe we had later 8260 sku that fixed this issue. >>> >>> But there are already 8260 that is affected by this bug in the wild. >>> >>> Search "Bluetooth: hci0: Failed to send firmware data (-38)” and there are lots of user are affected. >> >> which SKUs are these actually. What are the initial details about the boot loader. For the Bluetooth side, you should be able to grab them from dmesg or by running btmon. >> >> So I am not in favor of this kind of hack and creating dependencies between drivers. If you only have a hammer, then everything looks like a nail. And this is a massive hammer trying to squash everything. This problem needs to be debugged. And this starts by providing affected SKU information and firmware information. So get the details about the SKU and its Bluetooth and WiFi boot loaders. >> > > I have a Lenovo Yoga 900 which presents this problem and has the same bootloader / firmware information as Kai-Heng already posted: > > [ 5.992426] Bluetooth: Core ver 2.22 > [ 5.992438] Bluetooth: HCI device and connection manager initialized > [ 5.992442] Bluetooth: HCI socket layer initialized > [ 5.992444] Bluetooth: L2CAP socket layer initialized > [ 5.992450] Bluetooth: SCO socket layer initialized > [ 6.004941] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 > [ 6.010922] Bluetooth: hci0: Device revision is 5 > [ 6.010923] Bluetooth: hci0: Secure boot is enabled > [ 6.010924] Bluetooth: hci0: OTP lock is enabled > [ 6.010925] Bluetooth: hci0: API lock is enabled > [ 6.010926] Bluetooth: hci0: Debug lock is disabled > [ 6.010927] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 > [ 6.014253] bluetooth hci0: firmware: direct-loading firmware intel/ibt-11-5.sfi > [ 6.014256] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi > [ 6.613961] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > [ 6.613966] Bluetooth: BNEP filters: protocol multicast > [ 6.613974] Bluetooth: BNEP socket layer initialized > [ 6.983804] Bluetooth: hci0: Failed to send firmware data (-38) > > And the following product id and revision, from usb-devices: > > T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 > D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 > P: Vendor=8087 ProdID=0a2b Rev=00.01 > C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > > I understand the drawbacks with the approach presented here and lack of clear explanation of the problem, but I can confirm these patches work around the problem on my machine. Is there any extra info or test result I can provide to help debug this? I can also dedicate time to help write a different solution if some guidance is provided. > > Kai-Heng, did you end up filling a Bugzilla entry for this? > > Please CC-me on the replies as I'm not receiving emails from linux-bluetooth or linux-wireless anymore. our hardware teams from the Bluetooth and WiFi side really need to look at this. An inter-dependency between the firmware loading of two otherwise independent drivers is really not what I want to see upstream. However I have no idea which boot loaders are affected or if this is something that might be even possible to be fixed in operational firmware. If you can create a binary btmon trace file with the error happening and getting really every single message from the boot we might get a bit further to understand where it goes wrong. Regards Marcel
Hello Marcel, On Thu, Nov 8, 2018 at 11:49 PM Marcel Holtmann <marcel@holtmann.org> wrote: > > Hi Joao Paulo, > > >>>> I think Canonical were facing some wifi fw load error from some 8260 > >>>> earlier module during the BT still loading the fw. > >>>> I believe we had later 8260 sku that fixed this issue. > >>> > >>> But there are already 8260 that is affected by this bug in the wild. > >>> > >>> Search "Bluetooth: hci0: Failed to send firmware data (-38)” and there are lots of user are affected. > >> > >> which SKUs are these actually. What are the initial details about the boot loader. For the Bluetooth side, you should be able to grab them from dmesg or by running btmon. > >> > >> So I am not in favor of this kind of hack and creating dependencies between drivers. If you only have a hammer, then everything looks like a nail. And this is a massive hammer trying to squash everything. This problem needs to be debugged. And this starts by providing affected SKU information and firmware information. So get the details about the SKU and its Bluetooth and WiFi boot loaders. > >> > > > > I have a Lenovo Yoga 900 which presents this problem and has the same bootloader / firmware information as Kai-Heng already posted: > > > > [ 5.992426] Bluetooth: Core ver 2.22 > > [ 5.992438] Bluetooth: HCI device and connection manager initialized > > [ 5.992442] Bluetooth: HCI socket layer initialized > > [ 5.992444] Bluetooth: L2CAP socket layer initialized > > [ 5.992450] Bluetooth: SCO socket layer initialized > > [ 6.004941] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 > > [ 6.010922] Bluetooth: hci0: Device revision is 5 > > [ 6.010923] Bluetooth: hci0: Secure boot is enabled > > [ 6.010924] Bluetooth: hci0: OTP lock is enabled > > [ 6.010925] Bluetooth: hci0: API lock is enabled > > [ 6.010926] Bluetooth: hci0: Debug lock is disabled > > [ 6.010927] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 > > [ 6.014253] bluetooth hci0: firmware: direct-loading firmware intel/ibt-11-5.sfi > > [ 6.014256] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi > > [ 6.613961] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > > [ 6.613966] Bluetooth: BNEP filters: protocol multicast > > [ 6.613974] Bluetooth: BNEP socket layer initialized > > [ 6.983804] Bluetooth: hci0: Failed to send firmware data (-38) > > > > And the following product id and revision, from usb-devices: > > > > T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 > > D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 > > P: Vendor=8087 ProdID=0a2b Rev=00.01 > > C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA > > I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > > I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > > > > I understand the drawbacks with the approach presented here and lack of clear explanation of the problem, but I can confirm these patches work around the problem on my machine. Is there any extra info or test result I can provide to help debug this? I can also dedicate time to help write a different solution if some guidance is provided. > > > > Kai-Heng, did you end up filling a Bugzilla entry for this? > > > > Please CC-me on the replies as I'm not receiving emails from linux-bluetooth or linux-wireless anymore. > > our hardware teams from the Bluetooth and WiFi side really need to look at this. An inter-dependency between the firmware loading of two otherwise independent drivers is really not what I want to see upstream. However I have no idea which boot loaders are affected or if this is something that might be even possible to be fixed in operational firmware. If you can create a binary btmon trace file with the error happening and getting really every single message from the boot we might get a bit further to understand where it goes wrong. > After blacklisting iwlwifi and btusb so they don't get automatically loaded I started btmon and was able to reproduce the problem by manually loading the modules with "sudo modprobe iwlwifi & sudo modprobe btusb". I'm sending the full kernel logs and btsnoop trace from btmon attached. Let me know if I can provide anything else to help debug this. Thanks, -- João Paulo Rechi Vita http://about.me/jprvita [ 0.000000] microcode: microcode updated early to revision 0xc6, date = 2018-04-17 [ 0.000000] Linux version 4.19.0+ (jprvita@kiddo) (gcc version 8.2.0 (Debian 8.2.0-8)) #4 SMP Fri Nov 9 14:39:55 PST 2018 () [ 0.000000] Command line: BOOT_IMAGE=(hd0,gpt3)/boot/vmlinuz-4.19.0+ root=UUID=521e8cd5-f7b4-435d-a68a-40ff1af81d77 rw splash plymouth.ignore-serial-consoles quiet loglevel=2 ostree=/ostree/boot.1/eos/edef2daa2997a53735578d6a840f7a79d32c9cc4bb770e2d62ce8f23f6b58390/0 [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Centaur CentaurHauls [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 [ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 [ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x0000000000085fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000086000-0x00000000000fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000707a0fff] usable [ 0.000000] BIOS-e820: [mem 0x00000000707a1000-0x00000000707a1fff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x00000000707a2000-0x00000000707cbfff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000707cc000-0x0000000070878fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000070879000-0x0000000071178fff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000071179000-0x000000008738dfff] usable [ 0.000000] BIOS-e820: [mem 0x000000008738e000-0x0000000087d7dfff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000087d7e000-0x0000000087f7dfff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x0000000087f7e000-0x0000000087ffdfff] ACPI data [ 0.000000] BIOS-e820: [mem 0x0000000087ffe000-0x0000000087ffefff] usable [ 0.000000] BIOS-e820: [mem 0x0000000087fff000-0x00000000880fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000088800000-0x000000008b7fffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000feb00000-0x00000000feb03fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000002737fffff] usable [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] e820: update [mem 0x6e2b3018-0x6e2c3057] usable ==> usable [ 0.000000] e820: update [mem 0x6e2b3018-0x6e2c3057] usable ==> usable [ 0.000000] extended physical RAM map: [ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x0000000000057fff] usable [ 0.000000] reserve setup_data: [mem 0x0000000000058000-0x0000000000058fff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000000059000-0x0000000000085fff] usable [ 0.000000] reserve setup_data: [mem 0x0000000000086000-0x00000000000fffff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x000000006e2b3017] usable [ 0.000000] reserve setup_data: [mem 0x000000006e2b3018-0x000000006e2c3057] usable [ 0.000000] reserve setup_data: [mem 0x000000006e2c3058-0x00000000707a0fff] usable [ 0.000000] reserve setup_data: [mem 0x00000000707a1000-0x00000000707a1fff] ACPI NVS [ 0.000000] reserve setup_data: [mem 0x00000000707a2000-0x00000000707cbfff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000707cc000-0x0000000070878fff] usable [ 0.000000] reserve setup_data: [mem 0x0000000070879000-0x0000000071178fff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000071179000-0x000000008738dfff] usable [ 0.000000] reserve setup_data: [mem 0x000000008738e000-0x0000000087d7dfff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000087d7e000-0x0000000087f7dfff] ACPI NVS [ 0.000000] reserve setup_data: [mem 0x0000000087f7e000-0x0000000087ffdfff] ACPI data [ 0.000000] reserve setup_data: [mem 0x0000000087ffe000-0x0000000087ffefff] usable [ 0.000000] reserve setup_data: [mem 0x0000000087fff000-0x00000000880fffff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000088800000-0x000000008b7fffff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000e0000000-0x00000000efffffff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000feb00000-0x00000000feb03fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fed00000-0x00000000fed00fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fed10000-0x00000000fed19fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fed84000-0x00000000fed84fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000100000000-0x00000002737fffff] usable [ 0.000000] efi: EFI v2.40 by INSYDE Corp. [ 0.000000] efi: SMBIOS=0x87600000 ESRT=0x87601c18 ACPI 2.0=0x87ffd014 TPMEventLog=0x7118b018 [ 0.000000] secureboot: Secure boot disabled [ 0.000000] SMBIOS 2.8 present. [ 0.000000] DMI: LENOVO 80MK/VIUU4, BIOS C6CN35WW 12/17/2015 [ 0.000000] tsc: Detected 2600.000 MHz processor [ 0.000731] tsc: Detected 2592.000 MHz TSC [ 0.000731] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.000733] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.000740] last_pfn = 0x273800 max_arch_pfn = 0x400000000 [ 0.000743] MTRR default type: uncachable [ 0.000744] MTRR fixed ranges enabled: [ 0.000745] 00000-9FFFF write-back [ 0.000745] A0000-BFFFF uncachable [ 0.000746] C0000-FFFFF write-protect [ 0.000746] MTRR variable ranges enabled: [ 0.000747] 0 base 0000000000 mask 7C00000000 write-back [ 0.000748] 1 base 0087FFF000 mask 7FFFFFF000 uncachable [ 0.000749] 2 base 0088000000 mask 7FF8000000 uncachable [ 0.000749] 3 base 0090000000 mask 7FF0000000 uncachable [ 0.000750] 4 base 00A0000000 mask 7FE0000000 uncachable [ 0.000750] 5 base 00C0000000 mask 7FC0000000 uncachable [ 0.000751] 6 disabled [ 0.000751] 7 disabled [ 0.000752] 8 disabled [ 0.000752] 9 disabled [ 0.001641] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [ 0.001798] total RAM covered: 14463M [ 0.001894] gran_size: 64K chunk_size: 64K num_reg: 10 lose cover RAM: 12583164K [ 0.001896] gran_size: 64K chunk_size: 128K num_reg: 5 lose cover RAM: 60K [ 0.001897] gran_size: 64K chunk_size: 256K num_reg: 5 lose cover RAM: 60K [ 0.001897] gran_size: 64K chunk_size: 512K num_reg: 5 lose cover RAM: 60K [ 0.001898] gran_size: 64K chunk_size: 1M num_reg: 5 lose cover RAM: 60K [ 0.001899] gran_size: 64K chunk_size: 2M num_reg: 5 lose cover RAM: 60K [ 0.001900] gran_size: 64K chunk_size: 4M num_reg: 5 lose cover RAM: 60K [ 0.001901] gran_size: 64K chunk_size: 8M num_reg: 5 lose cover RAM: 60K [ 0.001901] gran_size: 64K chunk_size: 16M num_reg: 5 lose cover RAM: 60K [ 0.001902] gran_size: 64K chunk_size: 32M num_reg: 5 lose cover RAM: 60K [ 0.001903] gran_size: 64K chunk_size: 64M num_reg: 5 lose cover RAM: 60K [ 0.001904] gran_size: 64K chunk_size: 128M num_reg: 5 lose cover RAM: 60K [ 0.001904] gran_size: 64K chunk_size: 256M num_reg: 6 lose cover RAM: 60K [ 0.001905] gran_size: 64K chunk_size: 512M num_reg: 7 lose cover RAM: 60K [ 0.001906] gran_size: 64K chunk_size: 1G num_reg: 8 lose cover RAM: 60K [ 0.001907] gran_size: 64K chunk_size: 2G num_reg: 8 lose cover RAM: 60K [ 0.001908] gran_size: 128K chunk_size: 128K num_reg: 10 lose cover RAM: 12583164K [ 0.001908] gran_size: 128K chunk_size: 256K num_reg: 5 lose cover RAM: 124K [ 0.001909] gran_size: 128K chunk_size: 512K num_reg: 5 lose cover RAM: 124K [ 0.001910] gran_size: 128K chunk_size: 1M num_reg: 5 lose cover RAM: 124K [ 0.001911] gran_size: 128K chunk_size: 2M num_reg: 5 lose cover RAM: 124K [ 0.001912] gran_size: 128K chunk_size: 4M num_reg: 5 lose cover RAM: 124K [ 0.001912] gran_size: 128K chunk_size: 8M num_reg: 5 lose cover RAM: 124K [ 0.001913] gran_size: 128K chunk_size: 16M num_reg: 5 lose cover RAM: 124K [ 0.001914] gran_size: 128K chunk_size: 32M num_reg: 5 lose cover RAM: 124K [ 0.001915] gran_size: 128K chunk_size: 64M num_reg: 5 lose cover RAM: 124K [ 0.001915] gran_size: 128K chunk_size: 128M num_reg: 5 lose cover RAM: 124K [ 0.001916] gran_size: 128K chunk_size: 256M num_reg: 6 lose cover RAM: 124K [ 0.001917] gran_size: 128K chunk_size: 512M num_reg: 7 lose cover RAM: 124K [ 0.001918] gran_size: 128K chunk_size: 1G num_reg: 8 lose cover RAM: 124K [ 0.001918] gran_size: 128K chunk_size: 2G num_reg: 8 lose cover RAM: 124K [ 0.001919] gran_size: 256K chunk_size: 256K num_reg: 10 lose cover RAM: 12583164K [ 0.001920] gran_size: 256K chunk_size: 512K num_reg: 5 lose cover RAM: 252K [ 0.001921] gran_size: 256K chunk_size: 1M num_reg: 5 lose cover RAM: 252K [ 0.001921] gran_size: 256K chunk_size: 2M num_reg: 5 lose cover RAM: 252K [ 0.001922] gran_size: 256K chunk_size: 4M num_reg: 5 lose cover RAM: 252K [ 0.001923] gran_size: 256K chunk_size: 8M num_reg: 5 lose cover RAM: 252K [ 0.001924] gran_size: 256K chunk_size: 16M num_reg: 5 lose cover RAM: 252K [ 0.001924] gran_size: 256K chunk_size: 32M num_reg: 5 lose cover RAM: 252K [ 0.001925] gran_size: 256K chunk_size: 64M num_reg: 5 lose cover RAM: 252K [ 0.001926] gran_size: 256K chunk_size: 128M num_reg: 5 lose cover RAM: 252K [ 0.001927] gran_size: 256K chunk_size: 256M num_reg: 6 lose cover RAM: 252K [ 0.001927] gran_size: 256K chunk_size: 512M num_reg: 7 lose cover RAM: 252K [ 0.001928] gran_size: 256K chunk_size: 1G num_reg: 8 lose cover RAM: 252K [ 0.001929] gran_size: 256K chunk_size: 2G num_reg: 8 lose cover RAM: 252K [ 0.001930] gran_size: 512K chunk_size: 512K num_reg: 10 lose cover RAM: 8389116K [ 0.001930] gran_size: 512K chunk_size: 1M num_reg: 5 lose cover RAM: 508K [ 0.001931] gran_size: 512K chunk_size: 2M num_reg: 5 lose cover RAM: 508K [ 0.001932] gran_size: 512K chunk_size: 4M num_reg: 5 lose cover RAM: 508K [ 0.001933] gran_size: 512K chunk_size: 8M num_reg: 5 lose cover RAM: 508K [ 0.001933] gran_size: 512K chunk_size: 16M num_reg: 5 lose cover RAM: 508K [ 0.001934] gran_size: 512K chunk_size: 32M num_reg: 5 lose cover RAM: 508K [ 0.001935] gran_size: 512K chunk_size: 64M num_reg: 5 lose cover RAM: 508K [ 0.001936] gran_size: 512K chunk_size: 128M num_reg: 5 lose cover RAM: 508K [ 0.001936] gran_size: 512K chunk_size: 256M num_reg: 6 lose cover RAM: 508K [ 0.001937] gran_size: 512K chunk_size: 512M num_reg: 7 lose cover RAM: 508K [ 0.001938] gran_size: 512K chunk_size: 1G num_reg: 8 lose cover RAM: 508K [ 0.001939] gran_size: 512K chunk_size: 2G num_reg: 8 lose cover RAM: 508K [ 0.001940] gran_size: 1M chunk_size: 1M num_reg: 10 lose cover RAM: 1020K [ 0.001940] gran_size: 1M chunk_size: 2M num_reg: 5 lose cover RAM: 1020K [ 0.001941] gran_size: 1M chunk_size: 4M num_reg: 5 lose cover RAM: 1020K [ 0.001942] gran_size: 1M chunk_size: 8M num_reg: 5 lose cover RAM: 1020K [ 0.001943] gran_size: 1M chunk_size: 16M num_reg: 5 lose cover RAM: 1020K [ 0.001943] gran_size: 1M chunk_size: 32M num_reg: 5 lose cover RAM: 1020K [ 0.001944] gran_size: 1M chunk_size: 64M num_reg: 5 lose cover RAM: 1020K [ 0.001945] gran_size: 1M chunk_size: 128M num_reg: 5 lose cover RAM: 1020K [ 0.001946] gran_size: 1M chunk_size: 256M num_reg: 6 lose cover RAM: 1020K [ 0.001946] gran_size: 1M chunk_size: 512M num_reg: 7 lose cover RAM: 1020K [ 0.001947] gran_size: 1M chunk_size: 1G num_reg: 8 lose cover RAM: 1020K [ 0.001948] gran_size: 1M chunk_size: 2G num_reg: 8 lose cover RAM: 1020K [ 0.001949] gran_size: 2M chunk_size: 2M num_reg: 9 lose cover RAM: 2044K [ 0.001949] gran_size: 2M chunk_size: 4M num_reg: 5 lose cover RAM: 2044K [ 0.001950] gran_size: 2M chunk_size: 8M num_reg: 5 lose cover RAM: 2044K [ 0.001951] gran_size: 2M chunk_size: 16M num_reg: 5 lose cover RAM: 2044K [ 0.001952] gran_size: 2M chunk_size: 32M num_reg: 5 lose cover RAM: 2044K [ 0.001952] gran_size: 2M chunk_size: 64M num_reg: 5 lose cover RAM: 2044K [ 0.001953] gran_size: 2M chunk_size: 128M num_reg: 5 lose cover RAM: 2044K [ 0.001954] gran_size: 2M chunk_size: 256M num_reg: 6 lose cover RAM: 2044K [ 0.001954] gran_size: 2M chunk_size: 512M num_reg: 7 lose cover RAM: 2044K [ 0.001955] gran_size: 2M chunk_size: 1G num_reg: 8 lose cover RAM: 2044K [ 0.001956] gran_size: 2M chunk_size: 2G num_reg: 8 lose cover RAM: 2044K [ 0.001957] gran_size: 4M chunk_size: 4M num_reg: 8 lose cover RAM: 4092K [ 0.001957] gran_size: 4M chunk_size: 8M num_reg: 5 lose cover RAM: 4092K [ 0.001958] gran_size: 4M chunk_size: 16M num_reg: 5 lose cover RAM: 4092K [ 0.001959] gran_size: 4M chunk_size: 32M num_reg: 5 lose cover RAM: 4092K [ 0.001960] gran_size: 4M chunk_size: 64M num_reg: 5 lose cover RAM: 4092K [ 0.001960] gran_size: 4M chunk_size: 128M num_reg: 5 lose cover RAM: 4092K [ 0.001961] gran_size: 4M chunk_size: 256M num_reg: 6 lose cover RAM: 4092K [ 0.001962] gran_size: 4M chunk_size: 512M num_reg: 7 lose cover RAM: 4092K [ 0.001963] gran_size: 4M chunk_size: 1G num_reg: 8 lose cover RAM: 4092K [ 0.001963] gran_size: 4M chunk_size: 2G num_reg: 8 lose cover RAM: 4092K [ 0.001964] gran_size: 8M chunk_size: 8M num_reg: 7 lose cover RAM: 8188K [ 0.001965] gran_size: 8M chunk_size: 16M num_reg: 5 lose cover RAM: 8188K [ 0.001966] gran_size: 8M chunk_size: 32M num_reg: 5 lose cover RAM: 8188K [ 0.001966] gran_size: 8M chunk_size: 64M num_reg: 5 lose cover RAM: 8188K [ 0.001967] gran_size: 8M chunk_size: 128M num_reg: 5 lose cover RAM: 8188K [ 0.001968] gran_size: 8M chunk_size: 256M num_reg: 6 lose cover RAM: 8188K [ 0.001969] gran_size: 8M chunk_size: 512M num_reg: 7 lose cover RAM: 8188K [ 0.001969] gran_size: 8M chunk_size: 1G num_reg: 8 lose cover RAM: 8188K [ 0.001970] gran_size: 8M chunk_size: 2G num_reg: 8 lose cover RAM: 8188K [ 0.001971] gran_size: 16M chunk_size: 16M num_reg: 6 lose cover RAM: 16380K [ 0.001972] gran_size: 16M chunk_size: 32M num_reg: 5 lose cover RAM: 16380K [ 0.001972] gran_size: 16M chunk_size: 64M num_reg: 5 lose cover RAM: 16380K [ 0.001973] gran_size: 16M chunk_size: 128M num_reg: 5 lose cover RAM: 16380K [ 0.001974] gran_size: 16M chunk_size: 256M num_reg: 6 lose cover RAM: 16380K [ 0.001975] gran_size: 16M chunk_size: 512M num_reg: 7 lose cover RAM: 16380K [ 0.001975] gran_size: 16M chunk_size: 1G num_reg: 8 lose cover RAM: 16380K [ 0.001976] gran_size: 16M chunk_size: 2G num_reg: 8 lose cover RAM: 16380K [ 0.001977] gran_size: 32M chunk_size: 32M num_reg: 5 lose cover RAM: 32764K [ 0.001978] gran_size: 32M chunk_size: 64M num_reg: 5 lose cover RAM: 32764K [ 0.001978] gran_size: 32M chunk_size: 128M num_reg: 5 lose cover RAM: 32764K [ 0.001979] gran_size: 32M chunk_size: 256M num_reg: 6 lose cover RAM: 32764K [ 0.001980] gran_size: 32M chunk_size: 512M num_reg: 7 lose cover RAM: 32764K [ 0.001981] gran_size: 32M chunk_size: 1G num_reg: 8 lose cover RAM: 32764K [ 0.001981] gran_size: 32M chunk_size: 2G num_reg: 8 lose cover RAM: 32764K [ 0.001982] gran_size: 64M chunk_size: 64M num_reg: 4 lose cover RAM: 65532K [ 0.001983] gran_size: 64M chunk_size: 128M num_reg: 5 lose cover RAM: 65532K [ 0.001984] gran_size: 64M chunk_size: 256M num_reg: 6 lose cover RAM: 65532K [ 0.001984] gran_size: 64M chunk_size: 512M num_reg: 7 lose cover RAM: 65532K [ 0.001985] gran_size: 64M chunk_size: 1G num_reg: 8 lose cover RAM: 65532K [ 0.001986] gran_size: 64M chunk_size: 2G num_reg: 8 lose cover RAM: 65532K [ 0.001987] gran_size: 128M chunk_size: 128M num_reg: 3 lose cover RAM: 131068K [ 0.001987] gran_size: 128M chunk_size: 256M num_reg: 3 lose cover RAM: 131068K [ 0.001988] gran_size: 128M chunk_size: 512M num_reg: 3 lose cover RAM: 131068K [ 0.001989] gran_size: 128M chunk_size: 1G num_reg: 3 lose cover RAM: 131068K [ 0.001990] gran_size: 128M chunk_size: 2G num_reg: 3 lose cover RAM: 131068K [ 0.001990] gran_size: 256M chunk_size: 256M num_reg: 3 lose cover RAM: 131068K [ 0.001991] gran_size: 256M chunk_size: 512M num_reg: 3 lose cover RAM: 131068K [ 0.001992] gran_size: 256M chunk_size: 1G num_reg: 3 lose cover RAM: 131068K [ 0.001993] gran_size: 256M chunk_size: 2G num_reg: 3 lose cover RAM: 131068K [ 0.001994] gran_size: 512M chunk_size: 512M num_reg: 3 lose cover RAM: 131068K [ 0.001994] gran_size: 512M chunk_size: 1G num_reg: 3 lose cover RAM: 131068K [ 0.001995] gran_size: 512M chunk_size: 2G num_reg: 3 lose cover RAM: 131068K [ 0.001996] gran_size: 1G chunk_size: 1G num_reg: 3 lose cover RAM: 131068K [ 0.001997] gran_size: 1G chunk_size: 2G num_reg: 3 lose cover RAM: 131068K [ 0.001997] gran_size: 2G chunk_size: 2G num_reg: 3 lose cover RAM: 131068K [ 0.001998] mtrr_cleanup: can not find optimal value [ 0.001998] please specify mtrr_gran_size/mtrr_chunk_size [ 0.002001] e820: update [mem 0x87fff000-0xffffffff] usable ==> reserved [ 0.002005] last_pfn = 0x87fff max_arch_pfn = 0x400000000 [ 0.008972] esrt: Reserving ESRT space from 0x0000000087601c18 to 0x0000000087601c50. [ 0.008979] Scanning 1 areas for low memory corruption [ 0.008981] Base memory trampoline at [(____ptrval____)] 80000 size 24576 [ 0.008984] Using GB pages for direct mapping [ 0.008986] BRK [0x1d3401000, 0x1d3401fff] PGTABLE [ 0.008987] BRK [0x1d3402000, 0x1d3402fff] PGTABLE [ 0.008988] BRK [0x1d3403000, 0x1d3403fff] PGTABLE [ 0.009014] BRK [0x1d3404000, 0x1d3404fff] PGTABLE [ 0.009015] BRK [0x1d3405000, 0x1d3405fff] PGTABLE [ 0.009103] BRK [0x1d3406000, 0x1d3406fff] PGTABLE [ 0.009121] BRK [0x1d3407000, 0x1d3407fff] PGTABLE [ 0.009142] BRK [0x1d3408000, 0x1d3408fff] PGTABLE [ 0.009182] BRK [0x1d3409000, 0x1d3409fff] PGTABLE [ 0.009196] BRK [0x1d340a000, 0x1d340afff] PGTABLE [ 0.009234] BRK [0x1d340b000, 0x1d340bfff] PGTABLE [ 0.009284] BRK [0x1d340c000, 0x1d340cfff] PGTABLE [ 0.009335] RAMDISK: [mem 0x3b130000-0x3fffdfff] [ 0.009347] ACPI: Early table checksum verification disabled [ 0.009350] ACPI: RSDP 0x0000000087FFD014 000024 (v02 LENOVO) [ 0.009353] ACPI: XSDT 0x0000000087FE0188 00011C (v01 LENOVO CB-01 00000001 01000013) [ 0.009358] ACPI: FACP 0x0000000087FE5000 0000F4 (v05 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009362] ACPI: DSDT 0x0000000087FBC000 023015 (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009365] ACPI: FACS 0x0000000087F4E000 000040 [ 0.009367] ACPI: TCPA 0x0000000087FFC000 000032 (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009370] ACPI: UEFI 0x0000000087FFB000 000236 (v01 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009375] ACPI: UEFI 0x0000000087FFA000 000042 (v01 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009380] ACPI: SSDT 0x0000000087FF9000 0004B7 (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009382] ACPI: SSDT 0x0000000087FF8000 00004B (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009385] ACPI: TPM2 0x0000000087FF7000 000034 (v03 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009387] ACPI: MSDM 0x0000000087FF6000 000055 (v03 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009389] ACPI: SSDT 0x0000000087FF0000 0052EE (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009392] ACPI: SSDT 0x0000000087FED000 002C4A (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009394] ACPI: DBGP 0x0000000087FEC000 000034 (v01 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009396] ACPI: DBG2 0x0000000087FEB000 000054 (v00 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009399] ACPI: SSDT 0x0000000087FEA000 0004C8 (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009401] ACPI: ASF! 0x0000000087FE9000 0000A5 (v32 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009403] ACPI: ASPT 0x0000000087FE8000 000034 (v07 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009406] ACPI: BOOT 0x0000000087FE7000 000028 (v01 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009408] ACPI: DBGP 0x0000000087FE6000 000034 (v01 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009410] ACPI: HPET 0x0000000087FE4000 000038 (v01 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009412] ACPI: LPIT 0x0000000087FE3000 000094 (v01 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009415] ACPI: APIC 0x0000000087FE2000 0000BC (v03 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009417] ACPI: MCFG 0x0000000087FE1000 00003C (v01 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009419] ACPI: SSDT 0x0000000087FBB000 0002D4 (v01 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009422] ACPI: SSDT 0x0000000087FB8000 002BAE (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009424] ACPI: SSDT 0x0000000087FB7000 00019A (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009426] ACPI: SSDT 0x0000000087FB6000 0006DC (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009429] ACPI: SSDT 0x0000000087FB5000 000B49 (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009431] ACPI: SSDT 0x0000000087FB4000 0004A3 (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009433] ACPI: SSDT 0x0000000087FB3000 000E58 (v02 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009435] ACPI: DMAR 0x0000000087FB2000 000114 (v01 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009438] ACPI: FPDT 0x0000000087FB1000 000044 (v01 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009440] ACPI: BGRT 0x0000000087FB0000 000038 (v01 LENOVO CB-01 00000001 ACPI 00040000) [ 0.009447] ACPI: Local APIC address 0xfee00000 [ 0.009617] No NUMA configuration found [ 0.009618] Faking a node at [mem 0x0000000000000000-0x00000002737fffff] [ 0.009626] NODE_DATA(0) allocated [mem 0x2737d5000-0x2737fffff] [ 0.009779] Zone ranges: [ 0.009780] DMA [mem 0x0000000000001000-0x0000000000ffffff] [ 0.009781] DMA32 [mem 0x0000000001000000-0x00000000ffffffff] [ 0.009782] Normal [mem 0x0000000100000000-0x00000002737fffff] [ 0.009783] Device empty [ 0.009784] Movable zone start for each node [ 0.009786] Early memory node ranges [ 0.009787] node 0: [mem 0x0000000000001000-0x0000000000057fff] [ 0.009788] node 0: [mem 0x0000000000059000-0x0000000000085fff] [ 0.009788] node 0: [mem 0x0000000000100000-0x00000000707a0fff] [ 0.009789] node 0: [mem 0x00000000707cc000-0x0000000070878fff] [ 0.009789] node 0: [mem 0x0000000071179000-0x000000008738dfff] [ 0.009789] node 0: [mem 0x0000000087ffe000-0x0000000087ffefff] [ 0.009790] node 0: [mem 0x0000000100000000-0x00000002737fffff] [ 0.009867] Reserved but unavailable: 5656 pages [ 0.009868] Initmem setup node 0 [mem 0x0000000000001000-0x00000002737fffff] [ 0.009869] On node 0 totalpages: 2073064 [ 0.009870] DMA zone: 64 pages used for memmap [ 0.009870] DMA zone: 21 pages reserved [ 0.009871] DMA zone: 3972 pages, LIFO batch:0 [ 0.009954] DMA32 zone: 8554 pages used for memmap [ 0.009954] DMA32 zone: 547428 pages, LIFO batch:63 [ 0.021552] Normal zone: 23776 pages used for memmap [ 0.021552] Normal zone: 1521664 pages, LIFO batch:63 [ 0.050219] Reserving Intel graphics memory at [mem 0x89800000-0x8b7fffff] [ 0.050688] ACPI: PM-Timer IO Port: 0x1808 [ 0.050689] ACPI: Local APIC address 0xfee00000 [ 0.050695] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.050695] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [ 0.050696] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [ 0.050696] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [ 0.050697] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) [ 0.050697] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) [ 0.050697] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) [ 0.050698] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) [ 0.050730] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119 [ 0.050731] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.050732] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.050733] ACPI: IRQ0 used by override. [ 0.050734] ACPI: IRQ9 used by override. [ 0.050736] Using ACPI (MADT) for SMP configuration information [ 0.050737] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.050744] smpboot: Allowing 4 CPUs, 0 hotplug CPUs [ 0.050761] PM: Registered nosave memory: [mem 0x00000000-0x00000fff] [ 0.050762] PM: Registered nosave memory: [mem 0x00058000-0x00058fff] [ 0.050763] PM: Registered nosave memory: [mem 0x00086000-0x000fffff] [ 0.050765] PM: Registered nosave memory: [mem 0x6e2b3000-0x6e2b3fff] [ 0.050766] PM: Registered nosave memory: [mem 0x6e2c3000-0x6e2c3fff] [ 0.050767] PM: Registered nosave memory: [mem 0x707a1000-0x707a1fff] [ 0.050767] PM: Registered nosave memory: [mem 0x707a2000-0x707cbfff] [ 0.050768] PM: Registered nosave memory: [mem 0x70879000-0x71178fff] [ 0.050769] PM: Registered nosave memory: [mem 0x8738e000-0x87d7dfff] [ 0.050770] PM: Registered nosave memory: [mem 0x87d7e000-0x87f7dfff] [ 0.050770] PM: Registered nosave memory: [mem 0x87f7e000-0x87ffdfff] [ 0.050771] PM: Registered nosave memory: [mem 0x87fff000-0x880fffff] [ 0.050772] PM: Registered nosave memory: [mem 0x88100000-0x887fffff] [ 0.050772] PM: Registered nosave memory: [mem 0x88800000-0x8b7fffff] [ 0.050773] PM: Registered nosave memory: [mem 0x8b800000-0xdfffffff] [ 0.050773] PM: Registered nosave memory: [mem 0xe0000000-0xefffffff] [ 0.050773] PM: Registered nosave memory: [mem 0xf0000000-0xfcffffff] [ 0.050774] PM: Registered nosave memory: [mem 0xfd000000-0xfe7fffff] [ 0.050774] PM: Registered nosave memory: [mem 0xfe800000-0xfeafffff] [ 0.050775] PM: Registered nosave memory: [mem 0xfeb00000-0xfeb03fff] [ 0.050775] PM: Registered nosave memory: [mem 0xfeb04000-0xfebfffff] [ 0.050775] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff] [ 0.050776] PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff] [ 0.050776] PM: Registered nosave memory: [mem 0xfed00000-0xfed00fff] [ 0.050776] PM: Registered nosave memory: [mem 0xfed01000-0xfed0ffff] [ 0.050777] PM: Registered nosave memory: [mem 0xfed10000-0xfed19fff] [ 0.050777] PM: Registered nosave memory: [mem 0xfed1a000-0xfed83fff] [ 0.050778] PM: Registered nosave memory: [mem 0xfed84000-0xfed84fff] [ 0.050778] PM: Registered nosave memory: [mem 0xfed85000-0xfedfffff] [ 0.050778] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff] [ 0.050779] PM: Registered nosave memory: [mem 0xfee01000-0xff9fffff] [ 0.050779] PM: Registered nosave memory: [mem 0xffa00000-0xffffffff] [ 0.050781] [mem 0x8b800000-0xdfffffff] available for PCI devices [ 0.050782] Booting paravirtualized kernel on bare hardware [ 0.050784] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns [ 0.050793] random: get_random_bytes called from start_kernel+0x99/0x542 with crng_init=0 [ 0.050799] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1 [ 0.050931] percpu: Embedded 47 pages/cpu @(____ptrval____) s155648 r8192 d28672 u524288 [ 0.050936] pcpu-alloc: s155648 r8192 d28672 u524288 alloc=1*2097152 [ 0.050937] pcpu-alloc: [0] 0 1 2 3 [ 0.050958] Built 1 zonelists, mobility grouping on. Total pages: 2040649 [ 0.050958] Policy zone: Normal [ 0.050959] Kernel command line: BOOT_IMAGE=(hd0,gpt3)/boot/vmlinuz-4.19.0+ root=UUID=521e8cd5-f7b4-435d-a68a-40ff1af81d77 rw splash plymouth.ignore-serial-consoles quiet loglevel=2 ostree=/ostree/boot.1/eos/edef2daa2997a53735578d6a840f7a79d32c9cc4bb770e2d62ce8f23f6b58390/0 [ 0.054035] Calgary: detecting Calgary via BIOS EBDA area [ 0.054036] Calgary: Unable to locate Rio Grande table in EBDA - bailing! [ 0.072716] Memory: 7912248K/8292256K available (12300K kernel code, 2676K rwdata, 4316K rodata, 2440K init, 5000K bss, 380008K reserved, 0K cma-reserved) [ 0.072794] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.072798] Kernel/User page tables isolation: enabled [ 0.079834] ftrace: allocating 41001 entries in 161 pages [ 0.093119] rcu: Hierarchical RCU implementation. [ 0.093120] rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=4. [ 0.093120] Tasks RCU enabled. [ 0.093121] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.095549] NR_IRQS: 524544, nr_irqs: 1024, preallocated irqs: 16 [ 0.095842] Console: colour dummy device 80x25 [ 0.095846] console [tty0] enabled [ 0.095862] ACPI: Core revision 20180810 [ 0.096235] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635855245 ns [ 0.096265] hpet clockevent registered [ 0.096311] APIC: Switch to symmetric I/O mode setup [ 0.096313] DMAR: Host address width 39 [ 0.096314] DMAR: DRHD base: 0x000000fed90000 flags: 0x0 [ 0.096318] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e3ff0505e [ 0.096319] DMAR: DRHD base: 0x000000fed91000 flags: 0x1 [ 0.096322] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da [ 0.096322] DMAR: RMRR base: 0x00000087c79000 end: 0x00000087c98fff [ 0.096323] DMAR: RMRR base: 0x00000089000000 end: 0x0000008b7fffff [ 0.096324] DMAR: ANDD device: 1 name: \_SB.PCI0.I2C0 [ 0.096324] DMAR: ANDD device: 2 name: \_SB.PCI0.I2C1 [ 0.096325] DMAR: ANDD device: 4 name: \_SB.PCI0.I2C3 [ 0.096326] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1 [ 0.096327] DMAR-IR: HPET id 0 under DRHD base 0xfed91000 [ 0.096327] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit. [ 0.096328] DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting. [ 0.097886] DMAR-IR: Enabled IRQ remapping in xapic mode [ 0.097887] x2apic: IRQ remapping doesn't support X2APIC mode [ 0.101927] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 0.120280] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x255cb6cc5db, max_idle_ns: 440795203504 ns [ 0.120291] Calibrating delay loop (skipped), value calculated using timer frequency.. 5184.00 BogoMIPS (lpj=10368000) [ 0.120292] pid_max: default: 32768 minimum: 301 [ 0.123540] Security Framework initialized [ 0.123542] Yama: becoming mindful. [ 0.123571] AppArmor: AppArmor initialized [ 0.124471] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes) [ 0.124938] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes) [ 0.124962] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes) [ 0.124976] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes) [ 0.125167] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 0.125168] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) [ 0.125172] mce: CPU supports 8 MCE banks [ 0.125179] CPU0: Thermal monitoring enabled (TM1) [ 0.125196] process: using mwait in idle threads [ 0.125199] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 [ 0.125199] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 [ 0.125201] Spectre V2 : Spectre mitigation: kernel not compiled with retpoline; no mitigation available! [ 0.125202] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp [ 0.129366] Freeing SMP alternatives memory: 36K [ 0.133749] TSC deadline timer enabled [ 0.133753] smpboot: CPU0: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz (family: 0x6, model: 0x4e, stepping: 0x3) [ 0.133829] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver. [ 0.133854] ... version: 4 [ 0.133855] ... bit width: 48 [ 0.133855] ... generic registers: 4 [ 0.133856] ... value mask: 0000ffffffffffff [ 0.133856] ... max period: 00007fffffffffff [ 0.133857] ... fixed-purpose events: 3 [ 0.133857] ... event mask: 000000070000000f [ 0.133887] rcu: Hierarchical SRCU implementation. [ 0.134675] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. [ 0.134710] smp: Bringing up secondary CPUs ... [ 0.134766] x86: Booting SMP configuration: [ 0.134767] .... node #0, CPUs: #1 #2 #3 [ 0.136281] smp: Brought up 1 node, 4 CPUs [ 0.136286] smpboot: Max logical packages: 1 [ 0.136287] smpboot: Total of 4 processors activated (20736.00 BogoMIPS) [ 0.140285] devtmpfs: initialized [ 0.140336] x86/mm: Memory block size: 128MB [ 0.140905] PM: Registering ACPI NVS region [mem 0x707a1000-0x707a1fff] (4096 bytes) [ 0.140905] PM: Registering ACPI NVS region [mem 0x87d7e000-0x87f7dfff] (2097152 bytes) [ 0.140905] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.140905] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 0.140905] pinctrl core: initialized pinctrl subsystem [ 0.140905] RTC time: 23:43:00, date: 11/09/18 [ 0.140905] NET: Registered protocol family 16 [ 0.140905] audit: initializing netlink subsys (disabled) [ 0.140905] audit: type=2000 audit(1541806980.048:1): state=initialized audit_enabled=0 res=1 [ 0.140905] cpuidle: using governor ladder [ 0.140905] cpuidle: using governor menu [ 0.140905] Simple Boot Flag at 0x44 set to 0x1 [ 0.140905] KVM setup pv remote TLB flush [ 0.140905] ACPI: bus type PCI registered [ 0.140905] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.140905] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) [ 0.140905] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820 [ 0.140905] pmd_set_huge: Cannot satisfy [mem 0xe0000000-0xe0200000] with a huge-page mapping due to MTRR override. [ 0.140905] PCI: Using configuration type 1 for base access [ 0.141225] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 0.141225] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 0.141225] ACPI: Added _OSI(Module Device) [ 0.141225] ACPI: Added _OSI(Processor Device) [ 0.141225] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.141225] ACPI: Added _OSI(Processor Aggregator Device) [ 0.141225] ACPI: Added _OSI(Linux-Dell-Video) [ 0.141225] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [ 0.172607] ACPI: 13 ACPI AML tables successfully acquired and loaded [ 0.181362] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [ 0.184584] ACPI: Dynamic OEM Table Load: [ 0.184602] ACPI: SSDT 0xFFFF8DE72947D000 000660 (v02 PmRef Cpu0Ist 00003000 INTL 20121220) [ 0.185064] ACPI: \_PR_.CPU0: _OSC native thermal LVT Acked [ 0.188527] ACPI: Dynamic OEM Table Load: [ 0.188534] ACPI: SSDT 0xFFFF8DE729573400 00037F (v02 PmRef Cpu0Cst 00003001 INTL 20121220) [ 0.188887] ACPI: Dynamic OEM Table Load: [ 0.188892] ACPI: SSDT 0xFFFF8DE7295C3900 00008E (v02 PmRef Cpu0Hwp 00003000 INTL 20121220) [ 0.189135] ACPI: Dynamic OEM Table Load: [ 0.189141] ACPI: SSDT 0xFFFF8DE729674C00 000130 (v02 PmRef HwpLvt 00003000 INTL 20121220) [ 0.192013] ACPI: Dynamic OEM Table Load: [ 0.192020] ACPI: SSDT 0xFFFF8DE729479000 0005AA (v02 PmRef ApIst 00003000 INTL 20121220) [ 0.192654] ACPI: Dynamic OEM Table Load: [ 0.192660] ACPI: SSDT 0xFFFF8DE729675A00 000119 (v02 PmRef ApHwp 00003000 INTL 20121220) [ 0.192984] ACPI: Dynamic OEM Table Load: [ 0.192989] ACPI: SSDT 0xFFFF8DE729675800 000119 (v02 PmRef ApCst 00003000 INTL 20121220) [ 0.197826] ACPI: EC: EC started [ 0.197827] ACPI: EC: interrupt blocked [ 0.200457] ACPI: \_SB_.PCI0.LPCB.H_EC: Used as first EC [ 0.200461] ACPI: \_SB_.PCI0.LPCB.H_EC: GPE=0x50, EC_CMD/EC_SC=0x66, EC_DATA=0x62 [ 0.200464] ACPI: \_SB_.PCI0.LPCB.H_EC: Used as boot DSDT EC to handle transactions [ 0.200465] ACPI: Interpreter enabled [ 0.200503] ACPI: (supports S0 S3 S4 S5) [ 0.200503] ACPI: Using IOAPIC for interrupt routing [ 0.200536] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.201454] ACPI: Enabled 9 GPEs in block 00 to 7F [ 0.205342] ACPI: Power Resource [PG00] (on) [ 0.205342] ACPI: Power Resource [PG01] (on) [ 0.205342] ACPI: Power Resource [PG02] (on) [ 0.226117] ACPI: Power Resource [FN00] (off) [ 0.226183] ACPI: Power Resource [FN01] (off) [ 0.226246] ACPI: Power Resource [FN02] (off) [ 0.226313] ACPI: Power Resource [FN03] (off) [ 0.226376] ACPI: Power Resource [FN04] (off) [ 0.227397] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) [ 0.227411] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.230282] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR] [ 0.232243] PCI host bridge to bus 0000:00 [ 0.232245] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] [ 0.232245] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 0.232246] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] [ 0.232247] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff window] [ 0.232248] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff window] [ 0.232248] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff window] [ 0.232249] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff window] [ 0.232250] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window] [ 0.232250] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window] [ 0.232251] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window] [ 0.232252] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window] [ 0.232252] pci_bus 0000:00: root bus resource [mem 0x8b800000-0xdfffffff window] [ 0.232253] pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfe7fffff window] [ 0.232254] pci_bus 0000:00: root bus resource [bus 00-fe] [ 0.232262] pci 0000:00:00.0: [8086:1904] type 00 class 0x060000 [ 0.233192] pci 0000:00:02.0: [8086:1916] type 00 class 0x030000 [ 0.233200] pci 0000:00:02.0: reg 0x10: [mem 0xa0000000-0xa0ffffff 64bit] [ 0.233205] pci 0000:00:02.0: reg 0x18: [mem 0x90000000-0x9fffffff 64bit pref] [ 0.233208] pci 0000:00:02.0: reg 0x20: [io 0x3000-0x303f] [ 0.233220] pci 0000:00:02.0: BAR 2: assigned to efifb [ 0.233919] pci 0000:00:04.0: [8086:1903] type 00 class 0x118000 [ 0.233930] pci 0000:00:04.0: reg 0x10: [mem 0xa1220000-0xa1227fff 64bit] [ 0.234712] pci 0000:00:14.0: [8086:9d2f] type 00 class 0x0c0330 [ 0.234733] pci 0000:00:14.0: reg 0x10: [mem 0xa1200000-0xa120ffff 64bit] [ 0.234802] pci 0000:00:14.0: PME# supported from D3hot D3cold [ 0.235515] pci 0000:00:14.2: [8086:9d31] type 00 class 0x118000 [ 0.235536] pci 0000:00:14.2: reg 0x10: [mem 0xa1232000-0xa1232fff 64bit] [ 0.236365] pci 0000:00:15.0: [8086:9d60] type 00 class 0x118000 [ 0.236628] pci 0000:00:15.0: reg 0x10: [mem 0xa1233000-0xa1233fff 64bit] [ 0.238247] pci 0000:00:15.1: [8086:9d61] type 00 class 0x118000 [ 0.238510] pci 0000:00:15.1: reg 0x10: [mem 0xa1234000-0xa1234fff 64bit] [ 0.240115] pci 0000:00:15.3: [8086:9d63] type 00 class 0x118000 [ 0.244365] pci 0000:00:15.3: reg 0x10: [mem 0xa1235000-0xa1235fff 64bit] [ 0.245899] pci 0000:00:16.0: [8086:9d3a] type 00 class 0x078000 [ 0.245925] pci 0000:00:16.0: reg 0x10: [mem 0xa1236000-0xa1236fff 64bit] [ 0.246001] pci 0000:00:16.0: PME# supported from D3hot [ 0.246732] pci 0000:00:17.0: [8086:9d03] type 00 class 0x010601 [ 0.246749] pci 0000:00:17.0: reg 0x10: [mem 0xa1230000-0xa1231fff] [ 0.246756] pci 0000:00:17.0: reg 0x14: [mem 0xa1239000-0xa12390ff] [ 0.246763] pci 0000:00:17.0: reg 0x18: [io 0x3080-0x3087] [ 0.246770] pci 0000:00:17.0: reg 0x1c: [io 0x3088-0x308b] [ 0.246777] pci 0000:00:17.0: reg 0x20: [io 0x3060-0x307f] [ 0.246784] pci 0000:00:17.0: reg 0x24: [mem 0xa1237000-0xa12377ff] [ 0.246828] pci 0000:00:17.0: PME# supported from D3hot [ 0.247550] pci 0000:00:1c.0: [8086:9d14] type 01 class 0x060400 [ 0.247636] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 0.248410] pci 0000:00:1c.5: [8086:9d15] type 01 class 0x060400 [ 0.248496] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold [ 0.249260] pci 0000:00:1f.0: [8086:9d48] type 00 class 0x060100 [ 0.250073] pci 0000:00:1f.2: [8086:9d21] type 00 class 0x058000 [ 0.250088] pci 0000:00:1f.2: reg 0x10: [mem 0xa122c000-0xa122ffff] [ 0.250850] pci 0000:00:1f.3: [8086:9d70] type 00 class 0x040300 [ 0.250878] pci 0000:00:1f.3: reg 0x10: [mem 0xa1228000-0xa122bfff 64bit] [ 0.250910] pci 0000:00:1f.3: reg 0x20: [mem 0xa1210000-0xa121ffff 64bit] [ 0.250963] pci 0000:00:1f.3: PME# supported from D3hot D3cold [ 0.251714] pci 0000:00:1f.4: [8086:9d23] type 00 class 0x0c0500 [ 0.251774] pci 0000:00:1f.4: reg 0x10: [mem 0xa1238000-0xa12380ff 64bit] [ 0.251845] pci 0000:00:1f.4: reg 0x20: [io 0x3040-0x305f] [ 0.252916] pci 0000:01:00.0: [8086:24f3] type 00 class 0x028000 [ 0.253015] pci 0000:01:00.0: reg 0x10: [mem 0xa1100000-0xa1101fff 64bit] [ 0.253302] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold [ 0.253419] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x1 link at 0000:00:1c.0 (capable of 7.876 Gb/s with 8 GT/s x1 link) [ 0.253951] pci 0000:00:1c.0: PCI bridge to [bus 01] [ 0.253955] pci 0000:00:1c.0: bridge window [mem 0xa1100000-0xa11fffff] [ 0.255833] pci 0000:02:00.0: [1217:8620] type 00 class 0x080501 [ 0.255862] pci 0000:02:00.0: reg 0x10: [mem 0xa1001000-0xa1001fff] [ 0.255873] pci 0000:02:00.0: reg 0x14: [mem 0xa1000000-0xa10007ff] [ 0.256003] pci 0000:02:00.0: PME# supported from D3hot D3cold [ 0.256052] pci 0000:02:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x1 link at 0000:00:1c.5 (capable of 7.876 Gb/s with 8 GT/s x1 link) [ 0.266132] pci 0000:00:1c.5: PCI bridge to [bus 02] [ 0.266136] pci 0000:00:1c.5: bridge window [mem 0xa1000000-0xa10fffff] [ 0.269532] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.269605] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15) [ 0.269675] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.269746] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.269816] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.269886] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.269956] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.270026] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.270324] platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff] [ 0.270325] acpi MSFT0101:00: platform device creation failed: -16 [ 0.271016] ACPI Warning: GPE type mismatch (level/edge) (20180810/evxface-792) [ 0.271018] ACPI: EC: interrupt unblocked [ 0.271035] ACPI: EC: event unblocked [ 0.271070] ACPI: \_SB_.PCI0.LPCB.H_EC: GPE=0x50, EC_CMD/EC_SC=0x66, EC_DATA=0x62 [ 0.271071] ACPI: \_SB_.PCI0.LPCB.H_EC: Used as boot DSDT EC to handle transactions and events [ 0.271367] SCSI subsystem initialized [ 0.271376] libata version 3.00 loaded. [ 0.271376] pci 0000:00:02.0: vgaarb: setting as boot VGA device [ 0.271376] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [ 0.271376] pci 0000:00:02.0: vgaarb: bridge control possible [ 0.271376] vgaarb: loaded [ 0.271376] ACPI: bus type USB registered [ 0.271376] usbcore: registered new interface driver usbfs [ 0.271376] usbcore: registered new interface driver hub [ 0.271376] usbcore: registered new device driver usb [ 0.271376] pps_core: LinuxPPS API ver. 1 registered [ 0.271376] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.271376] PTP clock support registered [ 0.271376] EDAC MC: Ver: 3.0.0 [ 0.272318] Registered efivars operations [ 0.320696] PCI: Using ACPI for IRQ routing [ 0.346140] PCI: pci_cache_line_size set to 64 bytes [ 0.350316] e820: reserve RAM buffer [mem 0x00058000-0x0005ffff] [ 0.350317] e820: reserve RAM buffer [mem 0x00086000-0x0008ffff] [ 0.350318] e820: reserve RAM buffer [mem 0x6e2b3018-0x6fffffff] [ 0.350318] e820: reserve RAM buffer [mem 0x707a1000-0x73ffffff] [ 0.350319] e820: reserve RAM buffer [mem 0x70879000-0x73ffffff] [ 0.350320] e820: reserve RAM buffer [mem 0x8738e000-0x87ffffff] [ 0.350320] e820: reserve RAM buffer [mem 0x87fff000-0x87ffffff] [ 0.350321] e820: reserve RAM buffer [mem 0x273800000-0x273ffffff] [ 0.352282] NetLabel: Initializing [ 0.352282] NetLabel: domain hash size = 128 [ 0.352282] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 0.352282] NetLabel: unlabeled traffic allowed by default [ 0.352391] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0 [ 0.352395] hpet0: 8 comparators, 64-bit 24.000000 MHz counter [ 0.356286] clocksource: Switched to clocksource tsc-early [ 0.366161] VFS: Disk quotas dquot_6.6.0 [ 0.366194] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.366287] AppArmor: AppArmor Filesystem Enabled [ 0.366312] pnp: PnP ACPI init [ 0.366531] system 00:00: [mem 0xfd000000-0xfdabffff] has been reserved [ 0.366532] system 00:00: [mem 0xfdad0000-0xfdadffff] has been reserved [ 0.366533] system 00:00: [mem 0xfdb00000-0xfdffffff] has been reserved [ 0.366534] system 00:00: [mem 0xfe000000-0xfe01ffff] has been reserved [ 0.366535] system 00:00: [mem 0xfe036000-0xfe03bfff] has been reserved [ 0.366536] system 00:00: [mem 0xfe03d000-0xfe3fffff] has been reserved [ 0.366537] system 00:00: [mem 0xfe410000-0xfe7fffff] has been reserved [ 0.366540] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.366823] system 00:01: [io 0x2000-0x20fe] has been reserved [ 0.366825] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.366935] system 00:02: [io 0x06a4] has been reserved [ 0.366936] system 00:02: [io 0x06a0] has been reserved [ 0.366938] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.367123] system 00:03: [io 0x0680-0x069f] has been reserved [ 0.367124] system 00:03: [io 0xffff] has been reserved [ 0.367125] system 00:03: [io 0xffff] has been reserved [ 0.367125] system 00:03: [io 0xffff] has been reserved [ 0.367126] system 00:03: [io 0x1800-0x18fe] has been reserved [ 0.367127] system 00:03: [io 0x164e-0x164f] has been reserved [ 0.367129] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.367216] pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active) [ 0.367246] system 00:05: [io 0x1854-0x1857] has been reserved [ 0.367248] system 00:05: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active) [ 0.367269] pnp 00:06: Plug and Play ACPI device, IDs PNP0303 (active) [ 0.368378] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.368848] system 00:08: [mem 0xfed10000-0xfed17fff] has been reserved [ 0.368849] system 00:08: [mem 0xfed18000-0xfed18fff] has been reserved [ 0.368850] system 00:08: [mem 0xfed19000-0xfed19fff] has been reserved [ 0.368851] system 00:08: [mem 0xe0000000-0xefffffff] has been reserved [ 0.368852] system 00:08: [mem 0xfed20000-0xfed3ffff] has been reserved [ 0.368853] system 00:08: [mem 0xfed90000-0xfed93fff] could not be reserved [ 0.368854] system 00:08: [mem 0xfed45000-0xfed8ffff] could not be reserved [ 0.368855] system 00:08: [mem 0xff000000-0xffffffff] could not be reserved [ 0.368856] system 00:08: [mem 0xfee00000-0xfeefffff] could not be reserved [ 0.368857] system 00:08: [mem 0x8b800000-0x8b81ffff] has been reserved [ 0.368859] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active) [ 0.369536] pnp: PnP ACPI: found 9 devices [ 0.375078] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns [ 0.375100] pci 0000:00:1c.0: PCI bridge to [bus 01] [ 0.375112] pci 0000:00:1c.0: bridge window [mem 0xa1100000-0xa11fffff] [ 0.375118] pci 0000:00:1c.5: PCI bridge to [bus 02] [ 0.375121] pci 0000:00:1c.5: bridge window [mem 0xa1000000-0xa10fffff] [ 0.375128] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] [ 0.375129] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window] [ 0.375129] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window] [ 0.375130] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff window] [ 0.375131] pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff window] [ 0.375131] pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff window] [ 0.375132] pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff window] [ 0.375133] pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff window] [ 0.375134] pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff window] [ 0.375134] pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff window] [ 0.375135] pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff window] [ 0.375136] pci_bus 0000:00: resource 15 [mem 0x8b800000-0xdfffffff window] [ 0.375137] pci_bus 0000:00: resource 16 [mem 0xfd000000-0xfe7fffff window] [ 0.375138] pci_bus 0000:01: resource 1 [mem 0xa1100000-0xa11fffff] [ 0.375138] pci_bus 0000:02: resource 1 [mem 0xa1000000-0xa10fffff] [ 0.375284] NET: Registered protocol family 2 [ 0.375395] tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes) [ 0.375415] TCP established hash table entries: 65536 (order: 7, 524288 bytes) [ 0.375487] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 0.375593] TCP: Hash tables configured (established 65536 bind 65536) [ 0.375618] UDP hash table entries: 4096 (order: 5, 131072 bytes) [ 0.375635] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes) [ 0.375695] NET: Registered protocol family 1 [ 0.375699] NET: Registered protocol family 44 [ 0.375707] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff] [ 0.381296] PCI: CLS 64 bytes, default 64 [ 0.381323] Unpacking initramfs... [ 1.456491] Freeing initrd memory: 80696K [ 1.456546] DMAR: ACPI device "device:6b" under DMAR at fed91000 as 00:15.0 [ 1.456549] DMAR: ACPI device "device:6c" under DMAR at fed91000 as 00:15.1 [ 1.456551] DMAR: ACPI device "device:6d" under DMAR at fed91000 as 00:15.3 [ 1.476332] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 1.476334] software IO TLB: mapped [mem 0x82eac000-0x86eac000] (64MB) [ 1.476472] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x255cb6cc5db, max_idle_ns: 440795203504 ns [ 1.476482] clocksource: Switched to clocksource tsc [ 1.476549] Scanning for low memory corruption every 60 seconds [ 1.477126] Initialise system trusted keyrings [ 1.477132] Key type blacklist registered [ 1.477155] workingset: timestamp_bits=35 max_order=21 bucket_order=0 [ 1.478255] zbud: loaded [ 1.478552] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 1.478712] fuse init (API version 7.27) [ 1.478762] pstore: using deflate compression [ 1.479670] Key type asymmetric registered [ 1.479671] Asymmetric key parser 'x509' registered [ 1.479677] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243) [ 1.479701] io scheduler noop registered [ 1.479702] io scheduler deadline registered [ 1.479723] io scheduler cfq registered (default) [ 1.480334] pcieport 0000:00:1c.0: Signaling PME with IRQ 122 [ 1.480353] pcieport 0000:00:1c.5: Signaling PME with IRQ 123 [ 1.480380] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 1.480424] efifb: probing for efifb [ 1.480457] efifb: framebuffer at 0x90000000, using 22500k, total 22500k [ 1.480458] efifb: mode is 3200x1800x32, linelength=12800, pages=1 [ 1.480458] efifb: scrolling: redraw [ 1.480459] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 1.489536] Console: switching to colour frame buffer device 400x112 [ 1.498178] fb0: EFI VGA frame buffer device [ 1.498184] intel_idle: MWAIT substates: 0x11142120 [ 1.498185] intel_idle: v0.4.1 model 0x4E [ 1.498355] intel_idle: lapic_timer_reliable_states 0xffffffff [ 1.498460] ACPI: AC Adapter [ADP1] (on-line) [ 1.498509] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:00/PNP0C0D:00/input/input0 [ 1.498514] ACPI: Lid Switch [LID0] [ 1.498545] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 [ 1.498553] ACPI: Power Button [PWRB] [ 1.498576] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [ 1.498580] ACPI: Power Button [PWRF] [ 1.499841] thermal LNXTHERM:00: registered as thermal_zone0 [ 1.499842] ACPI: Thermal Zone [TZ00] (28 C) [ 1.499974] thermal LNXTHERM:01: registered as thermal_zone1 [ 1.499974] ACPI: Thermal Zone [TZ01] (30 C) [ 1.500114] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [ 1.506877] Linux agpgart interface v0.103 [ 1.517072] battery: ACPI: Battery Slot [BAT1] (battery present) [ 1.533298] loop: module loaded [ 1.533417] libphy: Fixed MDIO Bus: probed [ 1.533418] tun: Universal TUN/TAP device driver, 1.6 [ 1.533435] PPP generic driver version 2.4.2 [ 1.533459] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.533460] ehci-pci: EHCI PCI platform driver [ 1.533466] ehci-platform: EHCI generic platform driver [ 1.533472] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.533473] ohci-pci: OHCI PCI platform driver [ 1.533478] ohci-platform: OHCI generic platform driver [ 1.533482] uhci_hcd: USB Universal Host Controller Interface driver [ 1.533631] xhci_hcd 0000:00:14.0: xHCI Host Controller [ 1.533635] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1 [ 1.534704] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000001109810 [ 1.534709] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported [ 1.534864] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 1.534865] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.534865] usb usb1: Product: xHCI Host Controller [ 1.534866] usb usb1: Manufacturer: Linux 4.19.0+ xhci-hcd [ 1.534867] usb usb1: SerialNumber: 0000:00:14.0 [ 1.534936] hub 1-0:1.0: USB hub found [ 1.534954] hub 1-0:1.0: 12 ports detected [ 1.535898] xhci_hcd 0000:00:14.0: xHCI Host Controller [ 1.535901] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2 [ 1.535908] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed [ 1.535933] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19 [ 1.535934] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.535935] usb usb2: Product: xHCI Host Controller [ 1.535935] usb usb2: Manufacturer: Linux 4.19.0+ xhci-hcd [ 1.535936] usb usb2: SerialNumber: 0000:00:14.0 [ 1.535991] hub 2-0:1.0: USB hub found [ 1.536005] hub 2-0:1.0: 6 ports detected [ 1.536426] usb: port power management may be unreliable [ 1.536623] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1 [ 1.536623] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp [ 1.537820] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 1.537874] mousedev: PS/2 mouse device common for all mice [ 1.538223] rtc_cmos 00:04: RTC can wake from S4 [ 1.538696] rtc_cmos 00:04: registered as rtc0 [ 1.538705] rtc_cmos 00:04: alarms up to one month, y3k, 242 bytes nvram, hpet irqs [ 1.538709] i2c /dev entries driver [ 1.538711] pcie_mp2_amd: AMD(R) PCI-E MP2 Communication Driver Version: 1.0 [ 1.538755] device-mapper: uevent: version 1.0.3 [ 1.538793] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com [ 1.538795] intel_pstate: Intel P-state driver initializing [ 1.539194] intel_pstate: HWP enabled [ 1.539248] ledtrig-cpu: registered to indicate activity on CPUs [ 1.539249] EFI Variables Facility v0.08 2004-May-17 [ 1.544121] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 [ 1.592207] intel_pmc_core: initialized [ 1.592399] NET: Registered protocol family 10 [ 1.595246] Segment Routing with IPv6 [ 1.595260] NET: Registered protocol family 17 [ 1.595283] Key type dns_resolver registered [ 1.595469] RAS: Correctable Errors collector initialized. [ 1.595496] microcode: sig=0x406e3, pf=0x80, revision=0xc6 [ 1.595554] microcode: Microcode Update Driver: v2.2. [ 1.595561] sched_clock: Marking stable (1599092352, -3540415)->(1604066537, -8514600) [ 1.595738] registered taskstats version 1 [ 1.595754] Loading compiled-in X.509 certificates [ 1.596303] Loaded X.509 cert 'Build time autogenerated kernel key: 4fc05165812af47c01c7f445c9f9dc3e351572bf' [ 1.597990] Loaded UEFI:db cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53' linked to secondary sys keyring [ 1.598003] Loaded UEFI:db cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4' linked to secondary sys keyring [ 1.598015] Loaded UEFI:db cert 'C6Yoga4Pro: 8107c1c2cff21084453dd65a8bd9cec3' linked to secondary sys keyring [ 1.599102] zswap: loaded using pool lzo/zbud [ 1.601395] Key type big_key registered [ 1.601397] Key type trusted registered [ 1.602369] Key type encrypted registered [ 1.602371] AppArmor: AppArmor sha1 policy hashing enabled [ 1.602380] ima: Allocated hash algorithm: sha1 [ 1.644733] evm: Initialising EVM extended attributes: [ 1.644733] evm: security.selinux [ 1.644734] evm: security.SMACK64 [ 1.644734] evm: security.SMACK64EXEC [ 1.644734] evm: security.SMACK64TRANSMUTE [ 1.644735] evm: security.SMACK64MMAP [ 1.644735] evm: security.apparmor [ 1.644735] evm: security.ima [ 1.644736] evm: security.capability [ 1.644736] evm: HMAC attrs: 0x1 [ 1.645606] Magic number: 10:831:756 [ 1.645620] tty ttyS7: hash matches [ 1.645808] rtc_cmos 00:04: setting system clock to 2018-11-09 23:43:02 UTC (1541806982) [ 1.864490] Freeing unused decrypted memory: 2040K [ 1.868325] usb 1-6: new high-speed USB device number 2 using xhci_hcd [ 2.049373] usb 1-6: New USB device found, idVendor=0bda, idProduct=57e1, bcdDevice= 0.07 [ 2.049374] usb 1-6: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 2.049375] usb 1-6: Product: Lenovo EasyCamera [ 2.049376] usb 1-6: Manufacturer: J9ZFC96XD [ 2.049376] usb 1-6: SerialNumber: 200901010001 [ 2.125788] Freeing unused kernel image memory: 2440K [ 2.132291] Write protecting the kernel read-only data: 20480k [ 2.133315] Freeing unused kernel image memory: 2008K [ 2.133625] Freeing unused kernel image memory: 1828K [ 2.141619] x86/mm: Checked W+X mappings: passed, no W+X pages found. [ 2.141620] x86/mm: Checking user space page tables [ 2.144621] usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 2.148744] x86/mm: Checked W+X mappings: passed, no W+X pages found. [ 2.148745] Run /init as init process [ 2.173078] usb 2-2: New USB device found, idVendor=8564, idProduct=1000, bcdDevice=11.00 [ 2.173093] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.173094] usb 2-2: Product: Mass Storage Device [ 2.173095] usb 2-2: Manufacturer: JetFlash [ 2.173096] usb 2-2: SerialNumber: 03BBD3F40H4B4KS2 [ 2.236867] systemd[1]: systemd 239 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 2.256670] systemd[1]: Detected architecture x86-64. [ 2.256673] systemd[1]: Running in initial RAM disk. [ 2.259151] systemd[1]: Set hostname to <endless>. [ 2.274720] random: systemd: uninitialized urandom read (16 bytes read) [ 2.274728] systemd[1]: Reached target Slices. [ 2.274770] random: systemd: uninitialized urandom read (16 bytes read) [ 2.274775] systemd[1]: Reached target Local File Systems. [ 2.274780] random: systemd: uninitialized urandom read (16 bytes read) [ 2.274784] systemd[1]: Reached target Timers. [ 2.274850] systemd[1]: Listening on udev Control Socket. [ 2.274909] systemd[1]: Listening on Journal Socket (/dev/log). [ 2.274974] systemd[1]: Listening on Journal Audit Socket. [ 2.292298] usb 1-7: new full-speed USB device number 3 using xhci_hcd [ 2.365539] hidraw: raw HID events driver (C) Jiri Kosina [ 2.376902] sdhci: Secure Digital Host Controller Interface driver [ 2.376904] sdhci: Copyright(c) Pierre Ossman [ 2.382351] ahci 0000:00:17.0: version 3.0 [ 2.382622] ahci 0000:00:17.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x4 impl SATA mode [ 2.382624] ahci 0000:00:17.0: flags: 64bit ncq pm led clo only pio slum part deso sadm sds apst [ 2.388304] scsi host0: ahci [ 2.388444] scsi host1: ahci [ 2.388541] scsi host2: ahci [ 2.388589] ata1: DUMMY [ 2.388589] ata2: DUMMY [ 2.388596] ata3: SATA max UDMA/133 abar m2048@0xa1237000 port 0xa1237200 irq 125 [ 2.393105] sdhci-pci 0000:02:00.0: SDHCI controller found [1217:8620] (rev 1) [ 2.395129] mmc0: Unknown controller version (3). You may experience problems. [ 2.396314] usb-storage 2-2:1.0: USB Mass Storage device detected [ 2.396395] scsi host3: usb-storage 2-2:1.0 [ 2.396468] usbcore: registered new interface driver usb-storage [ 2.400031] usbcore: registered new interface driver uas [ 2.402543] mmc0: SDHCI controller on PCI [0000:02:00.0] using ADMA [ 2.453228] usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b, bcdDevice= 0.01 [ 2.453230] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.702552] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 2.703157] ata3.00: ATA-8: HFS256G39MND-3310A, 20002P00, max UDMA/133 [ 2.703158] ata3.00: 500118192 sectors, multi 0: LBA48 NCQ (depth 32), AA [ 2.704094] ata3.00: configured for UDMA/133 [ 2.704308] scsi 2:0:0:0: Direct-Access ATA HFS256G39MND-331 2P00 PQ: 0 ANSI: 5 [ 2.704475] sd 2:0:0:0: Attached scsi generic sg0 type 0 [ 2.704534] sd 2:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB) [ 2.704538] sd 2:0:0:0: [sda] Write Protect is off [ 2.704539] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 2.704544] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.707047] sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 [ 2.707344] sd 2:0:0:0: [sda] Attached SCSI disk [ 2.727628] random: fast init done [ 2.877697] checking generic (90000000 15f9000) vs hw (90000000 10000000) [ 2.877698] fb: switching to inteldrmfb from EFI VGA [ 2.877711] Console: switching to colour dummy device 80x25 [ 2.877980] [drm] Replacing VGA console driver [ 2.879206] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.879206] [drm] Driver supports precise vblank timestamp query. [ 2.879666] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 2.880031] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27) [ 3.166147] [drm] Initialized i915 1.6.0 20180719 for 0000:00:02.0 on minor 0 [ 3.167741] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 3.168043] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4 [ 3.178233] fbcon: inteldrmfb (fb0) is primary device [ 3.743371] scsi 3:0:0:0: Direct-Access JetFlash Transcend 32GB 1100 PQ: 0 ANSI: 6 [ 3.743659] sd 3:0:0:0: Attached scsi generic sg1 type 0 [ 3.744165] sd 3:0:0:0: [sdb] 61702144 512-byte logical blocks: (31.6 GB/29.4 GiB) [ 3.744652] sd 3:0:0:0: [sdb] Write Protect is off [ 3.744653] sd 3:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 3.745071] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 3.752414] sdb: sdb1 sdb2 sdb3 [ 3.754127] sd 3:0:0:0: [sdb] Attached SCSI removable disk [ 4.007915] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null) [ 4.283749] Console: switching to colour frame buffer device 400x112 [ 4.308919] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 4.526223] systemd-journald[154]: Received SIGTERM from PID 1 (systemd). [ 4.594317] systemd: 15 output lines suppressed due to ratelimiting [ 4.996433] systemd[1]: systemd 239 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 5.016461] systemd[1]: Detected architecture x86-64. [ 5.017645] systemd[1]: Set hostname to <endless>. [ 5.067841] random: crng init done [ 5.067842] random: 7 urandom warning(s) missed due to ratelimiting [ 6.916299] systemd[1]: Stopped Switch Root. [ 6.916387] systemd[1]: systemd-journald.service: Service has no hold-off time (RestartSec=0), scheduling restart. [ 6.916438] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1. [ 6.916445] systemd[1]: Stopped Journal Service. [ 6.917067] systemd[1]: Starting Journal Service... [ 6.917102] systemd[1]: Reached target Remote Encrypted Volumes. [ 6.917138] systemd[1]: Reached target endless-extra SD card mounted (if expected). [ 7.023936] EXT4-fs (sdb3): re-mounted. Opts: errors=remount-ro [ 7.159763] systemd-journald[288]: Received request to flush runtime journal from PID 1 [ 34.086446] io scheduler bfq registered [ 34.301437] media: Linux media interface: v0.10 [ 34.387463] zram: Added device: zram0 [ 34.394518] zram0: detected capacity change from 0 to 12397015040 [ 34.402195] Adding 12106456k swap on /dev/zram0. Priority:-2 extents:1 across:12106456k SSFS [ 34.476344] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002) [ 34.483681] idma64 idma64.0: Found Intel integrated DMA 64-bit [ 34.488253] i2c_hid i2c-ITE8396:00: i2c-ITE8396:00 supply vdd not found, using dummy regulator [ 34.488273] i2c_hid i2c-ITE8396:00: Linked as a consumer to regulator.0 [ 34.488274] i2c_hid i2c-ITE8396:00: i2c-ITE8396:00 supply vddl not found, using dummy regulator [ 34.502946] input: Ideapad extra buttons as /devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/input/input5 [ 34.592345] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002) [ 34.592662] idma64 idma64.1: Found Intel integrated DMA 64-bit [ 34.596422] i2c_hid i2c-SYNA2B29:00: i2c-SYNA2B29:00 supply vdd not found, using dummy regulator [ 34.596434] i2c_hid i2c-SYNA2B29:00: Linked as a consumer to regulator.0 [ 34.596435] i2c_hid i2c-SYNA2B29:00: i2c-SYNA2B29:00 supply vddl not found, using dummy regulator [ 34.624385] intel-lpss 0000:00:15.3: enabling device (0000 -> 0002) [ 34.625255] idma64 idma64.2: Found Intel integrated DMA 64-bit [ 34.631254] i2c_hid i2c-ELAN21EF:00: i2c-ELAN21EF:00 supply vdd not found, using dummy regulator [ 34.631267] i2c_hid i2c-ELAN21EF:00: Linked as a consumer to regulator.0 [ 34.631268] i2c_hid i2c-ELAN21EF:00: i2c-ELAN21EF:00 supply vddl not found, using dummy regulator [ 34.639646] videodev: Linux video capture interface: v2.00 [ 34.796288] raid6: sse2x1 gen() 9732 MB/s [ 34.844295] raid6: sse2x1 xor() 6752 MB/s [ 34.892291] raid6: sse2x2 gen() 8883 MB/s [ 34.940292] raid6: sse2x2 xor() 5277 MB/s [ 34.988295] raid6: sse2x4 gen() 10137 MB/s [ 35.013276] mei_me 0000:00:16.0: enabling device (0000 -> 0002) [ 35.036287] raid6: sse2x4 xor() 8791 MB/s [ 35.084288] raid6: avx2x1 gen() 16919 MB/s [ 35.132293] raid6: avx2x1 xor() 13328 MB/s [ 35.173879] uvcvideo: Found UVC 1.00 device Lenovo EasyCamera (0bda:57e1) [ 35.176798] uvcvideo: Failed to initialize entity for entity 6 [ 35.176799] uvcvideo: Failed to register entites (-22). [ 35.176858] input: Lenovo EasyCamera: Lenovo EasyC as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/input/input6 [ 35.176918] usbcore: registered new interface driver uvcvideo [ 35.176919] USB Video Class driver (1.1.1) [ 35.180290] raid6: avx2x2 gen() 18423 MB/s [ 35.228291] raid6: avx2x2 xor() 14402 MB/s [ 35.276292] raid6: avx2x4 gen() 17777 MB/s [ 35.324289] raid6: avx2x4 xor() 9912 MB/s [ 35.324292] raid6: using algorithm avx2x2 gen() 18423 MB/s [ 35.324292] raid6: .... xor() 14402 MB/s, rmw enabled [ 35.324293] raid6: using avx2x2 recovery algorithm [ 35.327276] xor: automatically using best checksumming function avx [ 35.346301] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer [ 35.346302] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules [ 35.346302] RAPL PMU: hw unit of domain package 2^-14 Joules [ 35.346302] RAPL PMU: hw unit of domain dram 2^-14 Joules [ 35.346303] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules [ 35.346303] RAPL PMU: hw unit of domain psys 2^-14 Joules [ 35.459915] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 35.494910] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC298: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 35.494913] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 35.494914] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 35.494915] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0 [ 35.494916] snd_hda_codec_realtek hdaudioC0D0: inputs: [ 35.494917] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 35.494918] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 35.554771] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input7 [ 35.554831] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input8 [ 35.554882] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input9 [ 35.554926] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input10 [ 35.554974] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input11 [ 35.555014] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12 [ 35.555059] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input13 [ 35.574740] cryptd: max_cpu_qlen set to 1000 [ 35.830486] hid-generic 0018:048D:8396.0001: hidraw0: I2C HID v1.00 Device [ITE8396:00 048D:8396] on i2c-ITE8396:00 [ 35.830774] input: SYNA2B29:00 06CB:77C6 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-6/i2c-SYNA2B29:00/0018:06CB:77C6.0002/input/input14 [ 35.830842] hid-generic 0018:06CB:77C6.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA2B29:00 06CB:77C6] on i2c-SYNA2B29:00 [ 35.831423] input: ELAN21EF:00 04F3:21EF Touchscreen as /devices/pci0000:00/0000:00:15.3/i2c_designware.2/i2c-7/i2c-ELAN21EF:00/0018:04F3:21EF.0003/input/input16 [ 35.831493] input: ELAN21EF:00 04F3:21EF as /devices/pci0000:00/0000:00:15.3/i2c_designware.2/i2c-7/i2c-ELAN21EF:00/0018:04F3:21EF.0003/input/input17 [ 35.831526] input: ELAN21EF:00 04F3:21EF as /devices/pci0000:00/0000:00:15.3/i2c_designware.2/i2c-7/i2c-ELAN21EF:00/0018:04F3:21EF.0003/input/input18 [ 35.831561] hid-generic 0018:04F3:21EF.0003: input,hidraw2: I2C HID v1.00 Device [ELAN21EF:00 04F3:21EF] on i2c-ELAN21EF:00 [ 35.925818] AVX2 version of gcm_enc/dec engaged. [ 35.925819] AES CTR mode by8 optimization enabled [ 35.932587] i2c_hid i2c-ELAN21EF:00: failed to change power setting. [ 35.933041] i2c_hid i2c-ELAN21EF:00: failed to retrieve report from device. [ 35.933043] hid-multitouch 0018:04F3:21EF.0003: failed to fetch feature 10 [ 35.933103] i2c_hid i2c-ELAN21EF:00: failed to retrieve report from device. [ 35.933103] hid-multitouch 0018:04F3:21EF.0003: failed to fetch feature 14 [ 35.933148] input: ELAN21EF:00 04F3:21EF as /devices/pci0000:00/0000:00:15.3/i2c_designware.2/i2c-7/i2c-ELAN21EF:00/0018:04F3:21EF.0003/input/input20 [ 35.933231] hid-multitouch 0018:04F3:21EF.0003: input,hidraw0: I2C HID v1.00 Device [ELAN21EF:00 04F3:21EF] on i2c-ELAN21EF:00 [ 35.933394] i2c_hid i2c-ELAN21EF:00: failed to change power setting. [ 36.001536] i2c_hid i2c-ELAN21EF:00: failed to change power setting. [ 36.024435] i2c_hid i2c-ELAN21EF:00: failed to change power setting. [ 36.076099] i2c_hid i2c-ELAN21EF:00: failed to change power setting. [ 36.088462] i2c_hid i2c-ELAN21EF:00: failed to change power setting. [ 36.400435] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: TM3066-002, fw id: 2024144 [ 36.487177] input: Synaptics TM3066-002 as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-6/i2c-SYNA2B29:00/0018:06CB:77C6.0002/input/input24 [ 36.487272] hid-rmi 0018:06CB:77C6.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA2B29:00 06CB:77C6] on i2c-SYNA2B29:00 [ 36.692916] Btrfs loaded, crc32c=crc32c-intel [ 36.694174] BTRFS: device label Debian devid 1 transid 2524470 /dev/sda8 [ 37.539729] intel_rapl: Found RAPL domain package [ 37.539730] intel_rapl: Found RAPL domain core [ 37.539731] intel_rapl: Found RAPL domain uncore [ 37.539732] intel_rapl: Found RAPL domain dram [ 45.487919] rfkill: input handler disabled [ 297.784823] NET: Registered protocol family 38 [ 297.997757] Bluetooth: Core ver 2.22 [ 297.997776] NET: Registered protocol family 31 [ 297.997777] Bluetooth: HCI device and connection manager initialized [ 297.997779] Bluetooth: HCI socket layer initialized [ 297.997781] Bluetooth: L2CAP socket layer initialized [ 297.997785] Bluetooth: SCO socket layer initialized [ 330.201340] usbcore: registered new interface driver btusb [ 330.210009] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 330.215016] Bluetooth: hci0: Device revision is 5 [ 330.215018] Bluetooth: hci0: Secure boot is enabled [ 330.215018] Bluetooth: hci0: OTP lock is enabled [ 330.215019] Bluetooth: hci0: API lock is enabled [ 330.215019] Bluetooth: hci0: Debug lock is disabled [ 330.215020] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 330.318833] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 330.439088] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 330.439089] Bluetooth: BNEP filters: protocol multicast [ 330.439093] Bluetooth: BNEP socket layer initialized [ 330.439517] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 330.444572] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 330.444619] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 330.444621] cfg80211: failed to load regulatory.db [ 330.661796] Intel(R) Wireless WiFi driver for Linux [ 330.661797] Copyright(c) 2003- 2015 Intel Corporation [ 330.687342] iwlwifi 0000:01:00.0: loaded firmware version 36.e91976c0.0 op_mode iwlmvm [ 331.401893] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 [ 331.419532] Bluetooth: hci0: Failed to send firmware data (-38) [ 331.493662] iwlwifi 0000:01:00.0: base HW address: a4:34:d9:81:bf:a5 [ 331.571067] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [ 331.571335] thermal thermal_zone6: failed to read out thermal zone (-61) [ 331.572960] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0 [ 331.594228] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready [ 331.862275] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready [ 331.919540] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready [ 335.403983] wlp1s0: authenticate with 16:91:82:37:a9:ea [ 335.412995] wlp1s0: send auth to 16:91:82:37:a9:ea (try 1/3) [ 335.421529] wlp1s0: authenticated [ 335.424364] wlp1s0: associate with 16:91:82:37:a9:ea (try 1/3) [ 335.446619] wlp1s0: RX AssocResp from 16:91:82:37:a9:ea (capab=0x431 status=0 aid=1) [ 335.463429] wlp1s0: associated [ 335.478937] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready [ 338.536883] usb 1-7: reset full-speed USB device number 3 using xhci_hcd
Hello Marcel, On Fri, Nov 9, 2018 at 4:36 PM João Paulo Rechi Vita <jprvita@gmail.com> wrote: > > Hello Marcel, > > On Thu, Nov 8, 2018 at 11:49 PM Marcel Holtmann <marcel@holtmann.org> wrote: > > > > our hardware teams from the Bluetooth and WiFi side really need to look at this. Were you able to get attention from the hardware teams with the logs I've provided? Are there any news or an idea of when / if we can expect this to be fixed in firmware? If not, do you have suggestions for an alternative solution? Thanks, -- João Paulo Rechi Vita http://about.me/jprvita
Hello Marcel, On Wed, Dec 5, 2018 at 11:27 AM João Paulo Rechi Vita <jprvita@gmail.com> wrote: > > Hello Marcel, > > On Fri, Nov 9, 2018 at 4:36 PM João Paulo Rechi Vita <jprvita@gmail.com> wrote: > > > > Hello Marcel, > > > > On Thu, Nov 8, 2018 at 11:49 PM Marcel Holtmann <marcel@holtmann.org> wrote: > > > > > > our hardware teams from the Bluetooth and WiFi side really need to look at this. > > Were you able to get attention from the hardware teams with the logs > I've provided? Are there any news or an idea of when / if we can > expect this to be fixed in firmware? If not, do you have suggestions > for an alternative solution? > Sorry to bother you again with this, but I'd really like to figure out some way forward here. Did you get any feedback from the hardware teams? Otherwise, I understand having an inter-dependency between the wifi and bt kernel modules is not desirable, so do you have any suggestion on how to solve this without adding this dependency? -- João Paulo Rechi Vita http://about.me/jprvita
Hello, > > > > > > > > our hardware teams from the Bluetooth and WiFi side really need to look at this. > > > > Were you able to get attention from the hardware teams with the logs > > I've provided? Are there any news or an idea of when / if we can > > expect this to be fixed in firmware? If not, do you have suggestions > > for an alternative solution? > > > > Sorry to bother you again with this, but I'd really like to figure out > some way forward here. Did you get any feedback from the hardware > teams? Otherwise, I understand having an inter-dependency between the > wifi and bt kernel modules is not desirable, so do you have any > suggestion on how to solve this without adding this dependency? > Have you tried the update the BT firmware with what is now available in mainline linux-firmware.git? I heard that this problem has now been resolved. After you update the BT firmware, you need a full power cycle.
On Wed, Jan 9, 2019 at 10:39 AM Emmanuel Grumbach <egrumbach@gmail.com> wrote: > > Hello, > > > > > > > > > > > our hardware teams from the Bluetooth and WiFi side really need to look at this. > > > > > > Were you able to get attention from the hardware teams with the logs > > > I've provided? Are there any news or an idea of when / if we can > > > expect this to be fixed in firmware? If not, do you have suggestions > > > for an alternative solution? > > > > > > > Sorry to bother you again with this, but I'd really like to figure out > > some way forward here. Did you get any feedback from the hardware > > teams? Otherwise, I understand having an inter-dependency between the > > wifi and bt kernel modules is not desirable, so do you have any > > suggestion on how to solve this without adding this dependency? > > > > Have you tried the update the BT firmware with what is now available in > mainline linux-firmware.git? > I heard that this problem has now been resolved. After you update the > BT firmware, you need a full power cycle. Thanks for the reply. The latest firmware files I see upstream are from commit c34a52ab7d, which are the same I had tested with previously. I'm still able to hit the problem, but after the firmware failed to load the Bluetooth adapter got disconnected from the USB bus and then re-connected. Since the iwlwifi firmware loading routine had already finished at this point, the Bluetooth firmware loaded successfully. I had seen this behavior a few times in my previous test, but not always (for example that behavior did not trigger on the test I had previously shared logs for). So, maybe that is the fix that has been implemented in the firmware? And perhaps some other changes in the kernel where preventing that behavior from triggering all the time? I'm pasting logs bellow where both modules where blacklisted and manually loaded with "modprobe iwlwifi & modprobe btusb": Jan 09 16:54:24 endless kernel: Bluetooth: Core ver 2.22 Jan 09 16:54:24 endless kernel: NET: Registered protocol family 31 Jan 09 16:54:24 endless kernel: Bluetooth: HCI device and connection manager initialized Jan 09 16:54:24 endless kernel: Bluetooth: HCI socket layer initialized Jan 09 16:54:24 endless kernel: Bluetooth: L2CAP socket layer initialized Jan 09 16:54:24 endless kernel: Bluetooth: SCO socket layer initialized Jan 09 16:54:24 endless kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database Jan 09 16:54:24 endless kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Jan 09 16:54:24 endless kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 Jan 09 16:54:24 endless kernel: cfg80211: failed to load regulatory.db Jan 09 16:54:24 endless kernel: usbcore: registered new interface driver btusb Jan 09 16:54:24 endless kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 Jan 09 16:54:24 endless kernel: Bluetooth: hci0: Device revision is 5 Jan 09 16:54:24 endless kernel: Bluetooth: hci0: Secure boot is enabled Jan 09 16:54:24 endless kernel: Bluetooth: hci0: OTP lock is enabled Jan 09 16:54:24 endless kernel: Bluetooth: hci0: API lock is enabled Jan 09 16:54:24 endless kernel: Bluetooth: hci0: Debug lock is disabled Jan 09 16:54:24 endless kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Jan 09 16:54:24 endless kernel: Intel(R) Wireless WiFi driver for Linux Jan 09 16:54:24 endless kernel: Copyright(c) 2003- 2015 Intel Corporation Jan 09 16:54:24 endless kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi Jan 09 16:54:25 endless kernel: iwlwifi 0000:01:00.0: loaded firmware version 36.7596afd4.0 op_mode iwlmvm Jan 09 16:54:25 endless kernel: iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 Jan 09 16:54:25 endless kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Jan 09 16:54:25 endless kernel: Bluetooth: BNEP filters: protocol multicast Jan 09 16:54:25 endless kernel: Bluetooth: BNEP socket layer initialized Jan 09 16:54:25 endless kernel: Bluetooth: hci0: Failed to send firmware data (-38) Jan 09 16:54:25 endless kernel: iwlwifi 0000:01:00.0: base HW address: a4:34:d9:81:bf:a5 Jan 09 16:54:25 endless kernel: ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' Jan 09 16:54:25 endless kernel: thermal thermal_zone6: failed to read out thermal zone (-61) Jan 09 16:54:25 endless kernel: iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0 Jan 09 16:54:25 endless kernel: IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready Jan 09 16:54:25 endless kernel: IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready Jan 09 16:54:25 endless kernel: IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready Jan 09 16:54:31 endless kernel: usb 1-7: USB disconnect, device number 3 Jan 09 16:54:32 endless kernel: usb 1-7: new full-speed USB device number 7 using xhci_hcd Jan 09 16:54:32 endless kernel: usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b, bcdDevice= 0.01 Jan 09 16:54:32 endless kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jan 09 16:54:32 endless kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 Jan 09 16:54:32 endless kernel: Bluetooth: hci0: Device revision is 5 Jan 09 16:54:32 endless kernel: Bluetooth: hci0: Secure boot is enabled Jan 09 16:54:32 endless kernel: Bluetooth: hci0: OTP lock is enabled Jan 09 16:54:32 endless kernel: Bluetooth: hci0: API lock is enabled Jan 09 16:54:32 endless kernel: Bluetooth: hci0: Debug lock is disabled Jan 09 16:54:32 endless kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Jan 09 16:54:32 endless kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi Jan 09 16:54:34 endless kernel: Bluetooth: hci0: Waiting for firmware download to complete Jan 09 16:54:34 endless kernel: Bluetooth: hci0: Firmware loaded in 1820173 usecs Jan 09 16:54:34 endless kernel: Bluetooth: hci0: Waiting for device to boot Jan 09 16:54:34 endless kernel: Bluetooth: hci0: Device booted in 11761 usecs Jan 09 16:54:34 endless kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc Jan 09 16:54:34 endless kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Jan 09 16:54:34 endless kernel: Bluetooth: RFCOMM TTY layer initialized Jan 09 16:54:34 endless kernel: Bluetooth: RFCOMM socket layer initialized Jan 09 16:54:34 endless kernel: Bluetooth: RFCOMM ver 1.11 -- João Paulo Rechi Vita http://about.me/jprvita
diff --git a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c index cc8c53dc0ab6..c30d3989e2a8 100644 --- a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c +++ b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c @@ -71,6 +71,7 @@ #include <linux/vmalloc.h> #include <linux/pm_runtime.h> #include <linux/module.h> +#include <linux/intel-wifi-bt.h> #include "iwl-drv.h" #include "iwl-trans.h" @@ -1335,6 +1336,10 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, bool hw_rfkill; int ret; +#if IS_ENABLED(CONFIG_BT_INTEL) + void (*firmware_lock_func)(void); + void (*firmware_unlock_func)(void); +#endif /* This may fail if AMT took ownership of the device */ if (iwl_pcie_prepare_card_hw(trans)) { IWL_WARN(trans, "Exit HW not ready\n"); @@ -1394,6 +1399,7 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, * RF-Kill switch is toggled, we will find out after having loaded * the firmware and return the proper value to the caller. */ + iwl_enable_fw_load_int(trans); /* really make sure rfkill handshake bits are cleared */ @@ -1401,8 +1407,37 @@ static int iwl_trans_pcie_start_fw(struct iwl_trans *trans, iwl_write32(trans, CSR_UCODE_DRV_GP1_CLR, CSR_UCODE_SW_BIT_RFKILL); /* Load the given image to the HW */ - if (trans->cfg->device_family >= IWL_DEVICE_FAMILY_8000) + if (trans->cfg->device_family >= IWL_DEVICE_FAMILY_8000) { +#if IS_ENABLED(CONFIG_BT_INTEL) + firmware_lock_func = symbol_request(btintel_firmware_lock); + firmware_unlock_func = symbol_request(btintel_firmware_unlock); + if (!firmware_lock_func || !firmware_unlock_func) { + if (firmware_lock_func) { + symbol_put(btintel_firmware_lock); + firmware_lock_func = NULL; + } + + if (firmware_unlock_func) { + symbol_put(btintel_firmware_unlock); + firmware_unlock_func = NULL; + } + } + + if (firmware_lock_func) + firmware_lock_func(); +#endif ret = iwl_pcie_load_given_ucode_8000(trans, fw); + +#if IS_ENABLED(CONFIG_BT_INTEL) + if (firmware_unlock_func) { + firmware_unlock_func(); + symbol_put(btintel_firmware_lock); + firmware_lock_func = NULL; + symbol_put(btintel_firmware_unlock); + firmware_unlock_func = NULL; + } +#endif + } else ret = iwl_pcie_load_given_ucode(trans, fw);
To avoid the firmware loading race between Bluetooth and WiFi on Intel 8260, load firmware exclusively when BT_INTEL is enabled. Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com> --- .../net/wireless/intel/iwlwifi/pcie/trans.c | 37 ++++++++++++++++++- 1 file changed, 36 insertions(+), 1 deletion(-)