Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices

regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
       [not found]                           ` <CABBYNZJNTOT-mEQe2cfZiEX6A2pR7+sacBqtBRPRZY69YmgtvA@mail.gmail.com>
@ 2022-02-24 10:08                             ` Chris Clayton
  2022-02-24 15:16                               ` Luiz Augusto von Dentz
  0 siblings, 1 reply; 19+ messages in thread
From: Chris Clayton @ 2022-02-24 10:08 UTC (permalink / raw)
  To: Luiz Augusto von Dentz; +Cc: Chris Murphy, Bluetooth, regressions

Hi Luiz,

On 24/02/2022 08:16, Luiz Augusto von Dentz wrote:
> Hi Chris,
> 
> On Wed, Feb 23, 2022 at 9:59 PM Chris Clayton <chris2553@googlemail.com> wrote:
>>
>>
>>
>> On 23/02/2022 22:42, Chris Clayton wrote:
>>> Hi.
>>>
>>> <snip>
>>>
>>>>
>>>> We are starting to suspect this is not a new issue, it just become
>>>> easier to reproduce with newer kernels since the mgmt commands are now
>>>> handled by a different work/thread which probably takes longer to
>>>> respond hitting problems such as:
>>>>
>>>> https://github.com/bluez/bluez/issues/275#issuecomment-1020608282
>>>>
>>>> This has been fixed by:
>>>>
>>>> https://github.com/bluez/bluez/commit/faad125c5505b941f06c54525616e192a6369208
>>>> https://github.com/bluez/bluez/commit/5f378404bff6bbfea3f20e36535c494efa5066a5
>>>>
>>>
>>> I cloned bluez, but that FTBFS, so I applied the two patches by hand.
>>>
>>> After the first boot, my bluetooth devices connected fine. But after a poweroff and boot, they didn't. Nor did they on
>>> the third and fourth boots, so the patches don't seem to be the answer. (They couldn't really be anyway because changes
>>> to the kernel have broken user-space which I understand is a big no no unless there is a really compelling reason.)
>>>
>>> I've gathered some diagnostics today and they are attached. They consist of 6 files containing the output from btmon and
>>> dmesg and the log file for the system daemons, which, of course, includes bluetoothd. There are 2 sets of these files -
>>> one from a boot that resulted in a system where my devices would not connect and another from a boot where they could
>>
>> s/would not connect and another/would connect and another/
>>
>>> not connect. You'll note that the btmon log is empty for a failed connection.
>>>
>>> I also tried a bisection with v5.16 as good and v5.17-rc1 as bad. Unfortunately, I found several steps resulted in a
>>> kernel where bluetooth seemed to be substantially borked - to the extent that blueman was non-functional and clicking on
>>> the tray icon did not start up the blueman-manager application.
> 
> Running with 5.17.0-0.rc5.102.fc37.x86_64 there doesn't seem to be any
> problems, well apart from LE device with Privacy/RPA:
> 
> https://gist.github.com/Vudentz/5792f4989198c7f2994af2e31eb973af
>
> Ive tried suspend/resume a couple of times just to see if there is
> something odd going own, anyway I'm running with the latest userspace
> so perhaps I really need some old userspace to reproduce this. There

I don't have an old userspace. I built my system from source about four years ago using the methods from Linux From
Scratch and Beyond Linux From Scratch. I have been updating the packages since then as and when they are released. In a
way, you could equate my system to one of the rolling releases. It is very up-to-date but at the same time very stable.

This morning I updated to the latest releases of the 5.15 and 5.16 stable series. I've also built and installed the
latest in the 5.4 and 5.10 stable series. (All four had new releases yesterday.) Bluetooth works as expected on all 4 of
those kernels. It has also worked on every kernel released by Linus and every stables series kernel in the last four
years. I usually start trying out a development kernel when rc3, 4 or 5 is released, depending on time available. If I
find any problems I report them and provide any diagnostics required and test patches.

Bluetooth is unreliable on my system when I boot 5.17-rc kernels. There is little doubt in my mind that something that
has changed in 5.17 is at the root of this. Whether it is actually a bug in userspace doesn't change the fact that there
is a regression because of one or more changes in the kernel. As I said yesterday, my understanding is that such
regressions are frowned upon.

I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.

In the meantime I've copied this email to regressions@lists.linux.dev, so they can track this.

Chris

> might be something with name resolving though, it appears gnome don't
> show devices if they don't have a proper name (that is not their
> address) so perhaps that gives the impression there is nothing going
> on when in fact that all normal, well apart from the fact that names
> takes way too long to be resolved.
> 
>>> I also booted into a 5.16.10 kernel and connecting bluetooth devices worked flawlessly. (This was with the unpatched
>>> bluez daemon)
>>>
>>> Chris
>>>> So the timer doesn't start until the request is sent. but obvoiusly
>>>> older versions of userspace don't have that fix so they end up
>>>> cancelling the loading of LTKs, this would explain why reloading the
>>>> daemon would make it work again.
> 
> 
> 

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-02-24 10:08                             ` bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices Chris Clayton
@ 2022-02-24 15:16                               ` Luiz Augusto von Dentz
  2022-02-24 16:18                                 ` Thorsten Leemhuis
  2022-02-26  8:04                                 ` Chris Clayton
  0 siblings, 2 replies; 19+ messages in thread
From: Luiz Augusto von Dentz @ 2022-02-24 15:16 UTC (permalink / raw)
  To: Chris Clayton; +Cc: Chris Murphy, Bluetooth, regressions

Hi Chris,

On Thu, Feb 24, 2022 at 2:08 AM Chris Clayton <chris2553@googlemail.com> wrote:
>
> Hi Luiz,
>
> On 24/02/2022 08:16, Luiz Augusto von Dentz wrote:
> > Hi Chris,
> >
> > On Wed, Feb 23, 2022 at 9:59 PM Chris Clayton <chris2553@googlemail.com> wrote:
> >>
> >>
> >>
> >> On 23/02/2022 22:42, Chris Clayton wrote:
> >>> Hi.
> >>>
> >>> <snip>
> >>>
> >>>>
> >>>> We are starting to suspect this is not a new issue, it just become
> >>>> easier to reproduce with newer kernels since the mgmt commands are now
> >>>> handled by a different work/thread which probably takes longer to
> >>>> respond hitting problems such as:
> >>>>
> >>>> https://github.com/bluez/bluez/issues/275#issuecomment-1020608282
> >>>>
> >>>> This has been fixed by:
> >>>>
> >>>> https://github.com/bluez/bluez/commit/faad125c5505b941f06c54525616e192a6369208
> >>>> https://github.com/bluez/bluez/commit/5f378404bff6bbfea3f20e36535c494efa5066a5
> >>>>
> >>>
> >>> I cloned bluez, but that FTBFS, so I applied the two patches by hand.
> >>>
> >>> After the first boot, my bluetooth devices connected fine. But after a poweroff and boot, they didn't. Nor did they on
> >>> the third and fourth boots, so the patches don't seem to be the answer. (They couldn't really be anyway because changes
> >>> to the kernel have broken user-space which I understand is a big no no unless there is a really compelling reason.)
> >>>
> >>> I've gathered some diagnostics today and they are attached. They consist of 6 files containing the output from btmon and
> >>> dmesg and the log file for the system daemons, which, of course, includes bluetoothd. There are 2 sets of these files -
> >>> one from a boot that resulted in a system where my devices would not connect and another from a boot where they could
> >>
> >> s/would not connect and another/would connect and another/
> >>
> >>> not connect. You'll note that the btmon log is empty for a failed connection.
> >>>
> >>> I also tried a bisection with v5.16 as good and v5.17-rc1 as bad. Unfortunately, I found several steps resulted in a
> >>> kernel where bluetooth seemed to be substantially borked - to the extent that blueman was non-functional and clicking on
> >>> the tray icon did not start up the blueman-manager application.
> >
> > Running with 5.17.0-0.rc5.102.fc37.x86_64 there doesn't seem to be any
> > problems, well apart from LE device with Privacy/RPA:
> >
> > https://gist.github.com/Vudentz/5792f4989198c7f2994af2e31eb973af
> >
> > Ive tried suspend/resume a couple of times just to see if there is
> > something odd going own, anyway I'm running with the latest userspace
> > so perhaps I really need some old userspace to reproduce this. There
>
> I don't have an old userspace. I built my system from source about four years ago using the methods from Linux From
> Scratch and Beyond Linux From Scratch. I have been updating the packages since then as and when they are released. In a
> way, you could equate my system to one of the rolling releases. It is very up-to-date but at the same time very stable.
>
> This morning I updated to the latest releases of the 5.15 and 5.16 stable series. I've also built and installed the
> latest in the 5.4 and 5.10 stable series. (All four had new releases yesterday.) Bluetooth works as expected on all 4 of
> those kernels. It has also worked on every kernel released by Linus and every stables series kernel in the last four
> years. I usually start trying out a development kernel when rc3, 4 or 5 is released, depending on time available. If I
> find any problems I report them and provide any diagnostics required and test patches.
>
> Bluetooth is unreliable on my system when I boot 5.17-rc kernels. There is little doubt in my mind that something that
> has changed in 5.17 is at the root of this. Whether it is actually a bug in userspace doesn't change the fact that there
> is a regression because of one or more changes in the kernel. As I said yesterday, my understanding is that such
> regressions are frowned upon.
>
> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.

Please record the HCI with btmon, it must be producing something since
it records even the mgmt commands.

> In the meantime I've copied this email to regressions@lists.linux.dev, so they can track this.

Hmm, is that really necessary? 5.17 has not been release tagged yet
and you are already considering it a regression?

> Chris
>
> > might be something with name resolving though, it appears gnome don't
> > show devices if they don't have a proper name (that is not their
> > address) so perhaps that gives the impression there is nothing going
> > on when in fact that all normal, well apart from the fact that names
> > takes way too long to be resolved.
> >
> >>> I also booted into a 5.16.10 kernel and connecting bluetooth devices worked flawlessly. (This was with the unpatched
> >>> bluez daemon)
> >>>
> >>> Chris
> >>>> So the timer doesn't start until the request is sent. but obvoiusly
> >>>> older versions of userspace don't have that fix so they end up
> >>>> cancelling the loading of LTKs, this would explain why reloading the
> >>>> daemon would make it work again.
> >
> >
> >



-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-02-24 15:16                               ` Luiz Augusto von Dentz
@ 2022-02-24 16:18                                 ` Thorsten Leemhuis
  2022-02-26  8:04                                 ` Chris Clayton
  1 sibling, 0 replies; 19+ messages in thread
From: Thorsten Leemhuis @ 2022-02-24 16:18 UTC (permalink / raw)
  To: Luiz Augusto von Dentz, Chris Clayton
  Cc: Chris Murphy, Bluetooth, regressions

On 24.02.22 16:16, Luiz Augusto von Dentz wrote:
> On Thu, Feb 24, 2022 at 2:08 AM Chris Clayton <chris2553@googlemail.com> wrote:
>> On 24/02/2022 08:16, Luiz Augusto von Dentz wrote:
>>> On Wed, Feb 23, 2022 at 9:59 PM Chris Clayton <chris2553@googlemail.com> wrote:
>>>> On 23/02/2022 22:42, Chris Clayton wrote:
> [...]
>> In the meantime I've copied this email to regressions@lists.linux.dev, so they can track this.

Many thx for this, much appreciated.

> Hmm, is that really necessary? 5.17 has not been release tagged yet
> and you are already considering it a regression?

Sure it's a regression, just one that didn't make it into a release yet.
But tracking regressions in mainline is just as important as tracking
them in stable trees, as it allows Linus to take a look at the known
regressions when he needs to decide between "release another rc" and
"call this finished and release the final". That's why mainline in the
past often was the main focus of regression tracking or the only tree
for which is was performed!

> [...]

Ciao, Thorsten

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-02-24 15:16                               ` Luiz Augusto von Dentz
  2022-02-24 16:18                                 ` Thorsten Leemhuis
@ 2022-02-26  8:04                                 ` Chris Clayton
  2022-02-28 19:34                                   ` Luiz Augusto von Dentz
  1 sibling, 1 reply; 19+ messages in thread
From: Chris Clayton @ 2022-02-26  8:04 UTC (permalink / raw)
  To: Luiz Augusto von Dentz; +Cc: Chris Murphy, Bluetooth, regressions

[-- Attachment #1: Type: text/plain, Size: 3264 bytes --]

Hi,

On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.

That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:

blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting

Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.

> Please record the HCI with btmon, it must be producing something since
> it records even the mgmt commands.
> 

Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
to get the hci trace that Luiz has asked for.

Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".

I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.

Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
however, I can provide any other diagnostics, please let me know.

Chris

[-- Attachment #3: btmon.log.good --]
[-- Type: text/plain, Size: 196608 bytes --]

Bluetooth monitor ver 5.63
= Note: Linux version 5.16.0-rc5+ (x86_64)                      14:00:03.050405
= Note: Bluetooth subsystem version 2.22                        14:00:03.050405
= New Index: 34:7D:F6:DF:83:1E (Primary,USB,hci0)               14:00:03.050406
= Open Index: 34:7D:F6:DF:83:1E                                 14:00:03.050406
= Index Info: 34:7D:F6:DF:83:1E (Intel Corp.)                   14:00:03.050406
@ MGMT Open: bluetoothd (privileged) version 1.21      {0x0002} 14:00:03.050406
> HCI Event: Connect Request (0x04) plen 10                  #1 14:00:13.067096
        Address: 00:08:4C:FA:B0:47 (OUI 00-08-4C)
        Class: 0x240404
          Major class: Audio/Video (headset, speaker, stereo, video, vcr)
          Minor class: Wearable Headset Device
          Rendering (Printing, Speaker)
          Audio (Speaker, Microphone, Headset)
        Link type: ACL (0x01)
< HCI Command: Accept Connection Req.. (0x01|0x0009) plen 7  #2 14:00:13.067154
        Address: 00:08:4C:FA:B0:47 (OUI 00-08-4C)
        Role: Central (0x00)
> HCI Event: Command Status (0x0f) plen 4                    #3 14:00:13.068994
      Accept Connection Request (0x01|0x0009) ncmd 1
        Status: Success (0x00)
> HCI Event: Role Change (0x12) plen 8                       #4 14:00:13.187097
        Status: Success (0x00)
        Address: 00:08:4C:FA:B0:47 (OUI 00-08-4C)
        Role: Central (0x00)
> HCI Event: Vendor (0xff) plen 4                            #5 14:00:13.367092
        26 00 01 01                                      &...            
> HCI Event: Connect Complete (0x03) plen 11                 #6 14:00:13.370021
        Status: Success (0x00)
        Handle: 256
        Address: 00:08:4C:FA:B0:47 (OUI 00-08-4C)
        Link type: ACL (0x01)
        Encryption: Disabled (0x00)
< HCI Command: Read Remote Supported.. (0x01|0x001b) plen 2  #7 14:00:13.370111
        Handle: 256
> HCI Event: Command Status (0x0f) plen 4                    #8 14:00:13.370565
      Read Remote Supported Features (0x01|0x001b) ncmd 1
        Status: Success (0x00)
> HCI Event: Max Slots Change (0x1b) plen 3                  #9 14:00:13.376857
        Handle: 256
        Max slots: 5
> HCI Event: Read Remote Supported Features (0x0b) plen 11  #10 14:00:13.377891
        Status: Success (0x00)
        Handle: 256
        Features: 0xff 0xff 0x8f 0xfa 0x9b 0xbf 0x59 0x87
          3 slot packets
          5 slot packets
          Encryption
          Slot offset
          Timing accuracy
          Role switch
          Hold mode
          Sniff mode
          Park state
          Power control requests
          Channel quality driven data rate (CQDDR)
          SCO link
          HV2 packets
          HV3 packets
          u-law log synchronous data
          A-law log synchronous data
          CVSD synchronous data
          Paging parameter negotiation
          Power control
          Transparent synchronous data
          Broadcast Encryption
          Enhanced Data Rate ACL 2 Mbps mode
          Enhanced inquiry scan
          Interlaced inquiry scan
          Interlaced page scan
          RSSI with inquiry results
          Extended SCO link (EV3 packets)
          EV4 packets
          EV5 packets
          AFH capable peripheral
          AFH classification peripheral
          3-slot Enhanced Data Rate ACL packets
          5-slot Enhanced Data Rate ACL packets
          Sniff subrating
          Pause encryption
          AFH capable central
          AFH classification central
          Enhanced Data Rate eSCO 2 Mbps mode
          3-slot Enhanced Data Rate eSCO packets
          Extended Inquiry Response
          Secure Simple Pairing
          Encapsulated PDU
          Non-flushable Packet Boundary Flag
          Link Supervision Timeout Changed Event
          Inquiry TX Power Level
          Enhanced Power Control
          Extended features
< HCI Command: Read Remote Extended.. (0x01|0x001c) plen 3  #11 14:00:13.377944
        Handle: 256
        Page: 1
> HCI Event: Command Status (0x0f) plen 4                   #12 14:00:13.378861
      Read Remote Extended Features (0x01|0x001c) ncmd 1
        Status: Success (0x00)
> ACL Data RX: Handle 256 flags 0x02 dlen 12                #13 14:00:13.380087
      L2CAP: Connection Request (0x02) ident 1 len 4
        PSM: 1 (0x0001)
        Source CID: 128
> HCI Event: Read Remote Extended Features (0x23) plen 13   #14 14:00:13.383863
        Status: Success (0x00)
        Handle: 256
        Page: 1/1
        Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
          Secure Simple Pairing (Host Support)
< HCI Command: Remote Name Request (0x01|0x0019) plen 10    #15 14:00:13.383921
        Address: 00:08:4C:FA:B0:47 (OUI 00-08-4C)
        Page scan repetition mode: R2 (0x02)
        Page scan mode: Mandatory (0x00)
        Clock offset: 0x0000
< ACL Data TX: Handle 256 flags 0x00 dlen 10                #16 14:00:13.383926
      L2CAP: Information Request (0x0a) ident 1 len 2
        Type: Extended features supported (0x0002)
@ MGMT Event: Device Connected (0x000b) plen 18        {0x0002} 14:00:13.383928
        BR/EDR Address: 00:08:4C:FA:B0:47 (OUI 00-08-4C)
        Flags: 0x00000000
        Data length: 5
        Class: 0x240404
          Major class: Audio/Video (headset, speaker, stereo, video, vcr)
          Minor class: Wearable Headset Device
          Rendering (Printing, Speaker)
          Audio (Speaker, Microphone, Headset)
< ACL Data TX: Handle 256 flags 0x00 dlen 16                #17 14:00:13.383947
      L2CAP: Connection Response (0x03) ident 1 len 8
        Destination CID: 64
        Source CID: 128
        Result: Connection pending (0x0001)
        Status: No further information available (0x0000)
< ACL Data TX: Handle 256 flags 0x00 dlen 10                #18 14:00:13.383949
      L2CAP: Information Request (0x0a) ident 2 len 2
        Type: Extended features supported (0x0002)
> HCI Event: Command Status (0x0f) plen 4                   #19 14:00:13.384589
      Remote Name Request (0x01|0x0019) ncmd 1
        Status: Success (0x00)
> HCI Event: Number of Completed Packets (0x13) plen 5      #20 14:00:13.389587
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5      #21 14:00:13.391586
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5      #22 14:00:13.393588
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 16                #23 14:00:13.396402
      L2CAP: Information Response (0x0b) ident 1 len 8
        Type: Extended features supported (0x0002)
        Result: Success (0x0000)
        Features: 0x000000b8
          Enhanced Retransmission Mode
          Streaming Mode
          FCS Option
          Fixed Channels
> ACL Data RX: Handle 256 flags 0x02 dlen 16                #24 14:00:13.397629
      L2CAP: Information Response (0x0b) ident 2 len 8
        Type: Extended features supported (0x0002)
        Result: Success (0x0000)
        Features: 0x000000b8
          Enhanced Retransmission Mode
          Streaming Mode
          FCS Option
          Fixed Channels
< ACL Data TX: Handle 256 flags 0x00 dlen 10                #25 14:00:13.397663
      L2CAP: Information Request (0x0a) ident 3 len 2
        Type: Fixed channels supported (0x0003)
> HCI Event: Remote Name Req Complete (0x07) plen 255       #26 14:00:13.399563
        Status: Success (0x00)
        Address: 00:08:4C:FA:B0:47 (OUI 00-08-4C)
        Name: Anker MP140
> HCI Event: Number of Completed Packets (0x13) plen 5      #27 14:00:13.401561
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 20                #28 14:00:13.403779
      L2CAP: Information Response (0x0b) ident 3 len 12
        Type: Fixed channels supported (0x0003)
        Result: Success (0x0000)
        Channels: 0x0000000000000036
          L2CAP Signaling (BR/EDR)
          Connectionless reception
          Attribute Protocol
          L2CAP Signaling (LE)
< ACL Data TX: Handle 256 flags 0x00 dlen 16                #29 14:00:13.403789
      L2CAP: Connection Response (0x03) ident 1 len 8
        Destination CID: 64
        Source CID: 128
        Result: Connection successful (0x0000)
        Status: No further information available (0x0000)
< ACL Data TX: Handle 256 flags 0x00 dlen 23                #30 14:00:13.403804
      L2CAP: Configure Request (0x04) ident 4 len 15
        Destination CID: 128
        Flags: 0x0000
        Option: Retransmission and Flow Control (0x04) [mandatory]
          Mode: Basic (0x00)
          TX window size: 0
          Max transmit: 0
          Retransmission timeout: 0
          Monitor timeout: 0
          Maximum PDU size: 0
> HCI Event: Number of Completed Packets (0x13) plen 5      #31 14:00:13.406599
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5      #32 14:00:13.408589
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 16                #33 14:00:13.410281
      L2CAP: Configure Request (0x04) ident 2 len 8
        Destination CID: 64
        Flags: 0x0000
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 48
< ACL Data TX: Handle 256 flags 0x00 dlen 18                #34 14:00:13.410324
      L2CAP: Configure Response (0x05) ident 2 len 10
        Source CID: 128
        Flags: 0x0000
        Result: Success (0x0000)
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 48
> ACL Data RX: Handle 256 flags 0x02 dlen 14                #35 14:00:13.411613
      L2CAP: Configure Response (0x05) ident 4 len 6
        Source CID: 64
        Flags: 0x0000
        Result: Success (0x0000)
> HCI Event: Number of Completed Packets (0x13) plen 5      #36 14:00:13.414836
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 24                #37 14:00:13.416297
      Channel: 64 len 20 [PSM 1 mode Basic (0x00)] {chan 0}
      SDP: Service Search Attribute Request (0x06) tid 1 len 15
        Search pattern: [len 7]
          Sequence (6) with 5 bytes [8 extra bits] len 7
            UUID (3) with 4 bytes [0 extra bits] len 5
              Handsfree Audio Gateway (0x0000111f)
        Max record count: 38
        Attribute list: [len 5]
          Sequence (6) with 3 bytes [8 extra bits] len 5
            Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
              0x0004
        Continuation state: 0
< ACL Data TX: Handle 256 flags 0x00 dlen 33                #38 14:00:13.416518
      Channel: 128 len 29 [PSM 1 mode Basic (0x00)] {chan 0}
      SDP: Service Search Attribute Response (0x07) tid 1 len 24
        Attribute bytes: 21
          Attribute list: [len 17] {position 0}
            Attribute: Protocol Descriptor List (0x0004) [len 2]
              Sequence (6) with 3 bytes [8 extra bits] len 5
                UUID (3) with 2 bytes [0 extra bits] len 3
                  L2CAP (0x0100)
              Sequence (6) with 5 bytes [8 extra bits] len 7
                UUID (3) with 2 bytes [0 extra bits] len 3
                  RFCOMM (0x0003)
                Unsigned Integer (1) with 1 byte [0 extra bits] len 2
                  0x0d
        Continuation state: 0
> HCI Event: Number of Completed Packets (0x13) plen 5      #39 14:00:13.420597
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 12                #40 14:00:13.422834
      L2CAP: Disconnection Request (0x06) ident 3 len 4
        Destination CID: 64
        Source CID: 128
< ACL Data TX: Handle 256 flags 0x00 dlen 12                #41 14:00:13.422875
      L2CAP: Disconnection Response (0x07) ident 3 len 4
        Destination CID: 64
        Source CID: 128
> HCI Event: Number of Completed Packets (0x13) plen 5      #42 14:00:13.426850
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Link Key Request (0x17) plen 6                 #43 14:00:13.432807
        Address: 00:08:4C:FA:B0:47 (OUI 00-08-4C)
< HCI Command: Link Key Request Re.. (0x01|0x000b) plen 22  #44 14:00:13.432874
        Address: 00:08:4C:FA:B0:47 (OUI 00-08-4C)
        Link key: 0ac295bde3bb857b7fec9bad22bc9e88
> HCI Event: Command Complete (0x0e) plen 10                #45 14:00:13.433603
      Link Key Request Reply (0x01|0x000b) ncmd 1
        Status: Success (0x00)
        Address: 00:08:4C:FA:B0:47 (OUI 00-08-4C)
> HCI Event: Encryption Change (0x08) plen 4                #46 14:00:13.467043
        Status: Success (0x00)
        Handle: 256
        Encryption: Enabled with E0 (0x01)
< HCI Command: Read Encryption Key... (0x05|0x0008) plen 2  #47 14:00:13.467060
        Handle: 256
> HCI Event: Command Complete (0x0e) plen 7                 #48 14:00:13.467855
      Read Encryption Key Size (0x05|0x0008) ncmd 1
        Status: Success (0x00)
        Handle: 256
        Key size: 16
> ACL Data RX: Handle 256 flags 0x02 dlen 12                #49 14:00:13.467862
      L2CAP: Connection Request (0x02) ident 4 len 4
        PSM: 3 (0x0003)
        Source CID: 192
< ACL Data TX: Handle 256 flags 0x00 dlen 16                #50 14:00:13.467931
      L2CAP: Connection Response (0x03) ident 4 len 8
        Destination CID: 64
        Source CID: 192
        Result: Connection successful (0x0000)
        Status: No further information available (0x0000)
< ACL Data TX: Handle 256 flags 0x00 dlen 27                #51 14:00:13.467954
      L2CAP: Configure Request (0x04) ident 5 len 19
        Destination CID: 192
        Flags: 0x0000
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 1021
        Option: Retransmission and Flow Control (0x04) [mandatory]
          Mode: Basic (0x00)
          TX window size: 0
          Max transmit: 0
          Retransmission timeout: 0
          Monitor timeout: 0
          Maximum PDU size: 0
> HCI Event: Number of Completed Packets (0x13) plen 5      #52 14:00:13.472096
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5      #53 14:00:13.472941
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 16                #54 14:00:13.472947
      L2CAP: Configure Request (0x04) ident 5 len 8
        Destination CID: 64
        Flags: 0x0000
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 4022
< ACL Data TX: Handle 256 flags 0x00 dlen 18                #55 14:00:13.473017
      L2CAP: Configure Response (0x05) ident 5 len 10
        Source CID: 192
        Flags: 0x0000
        Result: Success (0x0000)
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 4022
> ACL Data RX: Handle 256 flags 0x02 dlen 18                #56 14:00:13.475390
      L2CAP: Configure Response (0x05) ident 5 len 10
        Source CID: 64
        Flags: 0x0000
        Result: Success (0x0000)
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 1021
> HCI Event: Number of Completed Packets (0x13) plen 5      #57 14:00:13.476951
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 8                 #58 14:00:13.477909
      Channel: 64 len 4 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Set Async Balance Mode (SABM) (0x2f)
         Address: 0x03 cr 1 dlci 0x00
         Control: 0x3f poll/final 1
         Length: 0
         FCS: 0x1c
< ACL Data TX: Handle 256 flags 0x00 dlen 8                 #59 14:00:13.478064
      Channel: 192 len 4 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Ack (UA) (0x63)
         Address: 0x03 cr 1 dlci 0x00
         Control: 0x73 poll/final 1
         Length: 0
         FCS: 0xd7
> HCI Event: Number of Completed Packets (0x13) plen 5      #60 14:00:13.482098
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 18                #61 14:00:13.484205
      Channel: 64 len 14 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x03 cr 1 dlci 0x00
         Control: 0xef poll/final 0
         Length: 10
         FCS: 0x70
         MCC Message type: DLC Parameter Negotiation CMD (0x20)
           Length: 8
           dlci 26 frame_type 0 credit_flow 15 pri 0
           ack_timer 0 frame_size 884 max_retrans 0 credits 1
< ACL Data TX: Handle 256 flags 0x00 dlen 18                #62 14:00:13.484362
      Channel: 192 len 14 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x01 cr 0 dlci 0x00
         Control: 0xef poll/final 0
         Length: 10
         FCS: 0xaa
         MCC Message type: DLC Parameter Negotiation RSP (0x20)
           Length: 8
           dlci 26 frame_type 0 credit_flow 14 pri 0
           ack_timer 0 frame_size 884 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5      #63 14:00:13.489092
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 8                 #64 14:00:13.490066
      Channel: 64 len 4 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Set Async Balance Mode (SABM) (0x2f)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0x3f poll/final 1
         Length: 0
         FCS: 0xe7
< ACL Data TX: Handle 256 flags 0x00 dlen 8                 #65 14:00:13.490374
      Channel: 192 len 4 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Ack (UA) (0x63)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0x73 poll/final 1
         Length: 0
         FCS: 0x2c
< ACL Data TX: Handle 256 flags 0x00 dlen 12                #66 14:00:13.490379
      Channel: 192 len 8 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x01 cr 0 dlci 0x00
         Control: 0xef poll/final 0
         Length: 4
         FCS: 0xaa
         MCC Message type: Modem Status Command CMD (0x38)
           Length: 2
           dlci 26 
           fc 0 rtc 1 rtr 1 ic 0 dv 1
> HCI Event: Number of Completed Packets (0x13) plen 5      #67 14:00:13.494852
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5      #68 14:00:13.495854
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 12                #69 14:00:13.497618
      Channel: 64 len 8 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x03 cr 1 dlci 0x00
         Control: 0xef poll/final 0
         Length: 4
         FCS: 0x70
         MCC Message type: Modem Status Command CMD (0x38)
           Length: 2
           dlci 26 
           fc 0 rtc 1 rtr 1 ic 0 dv 1
< ACL Data TX: Handle 256 flags 0x00 dlen 12                #70 14:00:13.497727
      Channel: 192 len 8 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x01 cr 0 dlci 0x00
         Control: 0xef poll/final 0
         Length: 4
         FCS: 0xaa
         MCC Message type: Modem Status Command RSP (0x38)
           Length: 2
           dlci 26 
           fc 0 rtc 1 rtr 1 ic 0 dv 1
> ACL Data RX: Handle 256 flags 0x02 dlen 12                #71 14:00:13.498862
      Channel: 64 len 8 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x03 cr 1 dlci 0x00
         Control: 0xef poll/final 0
         Length: 4
         FCS: 0x70
         MCC Message type: Modem Status Command RSP (0x38)
           Length: 2
           dlci 26 
           fc 0 rtc 1 rtr 1 ic 0 dv 1
< ACL Data TX: Handle 256 flags 0x00 dlen 9                 #72 14:00:13.498999
      Channel: 192 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0x22
         Credits: 33
        22                                               "               
> HCI Event: Number of Completed Packets (0x13) plen 5      #73 14:00:13.501842
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5      #74 14:00:13.503610
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 20                #75 14:00:13.505293
      Channel: 64 len 16 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 11
         FCS: 0xf8
         Credits: 2
        41 54 2b 42 52 53 46 3d 35 39 0d f8              AT+BRSF=59..    
< ACL Data TX: Handle 256 flags 0x00 dlen 22                #76 14:00:13.505530
      Channel: 192 len 18 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 14
         FCS: 0x3e
        0d 0a 2b 42 52 53 46 3a 20 35 37 36 0d 0a 3e     ..+BRSF: 576..> 
< ACL Data TX: Handle 256 flags 0x00 dlen 14                #77 14:00:13.505549
      Channel: 192 len 10 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 6
         FCS: 0x3e
        0d 0a 4f 4b 0d 0a 3e                             ..OK..>         
> HCI Event: Number of Completed Packets (0x13) plen 5      #78 14:00:13.510102
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5      #79 14:00:13.510603
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 9                 #80 14:00:13.512774
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
> ACL Data RX: Handle 256 flags 0x02 dlen 9                 #81 14:00:13.513907
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
> ACL Data RX: Handle 256 flags 0x02 dlen 18                #82 14:00:13.515044
      Channel: 64 len 14 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 10
         FCS: 0xe4
        41 54 2b 43 49 4e 44 3d 3f 0d e4                 AT+CIND=?..     
< ACL Data TX: Handle 256 flags 0x00 dlen 90                #83 14:00:13.515238
      Channel: 192 len 86 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 82
         FCS: 0x3e
        0d 0a 2b 43 49 4e 44 3a 20 28 22 73 65 72 76 69  ..+CIND: ("servi
        63 65 22 2c 28 30 2d 31 29 29 2c 28 22 63 61 6c  ce",(0-1)),("cal
        6c 22 2c 28 30 2d 31 29 29 2c 28 22 63 61 6c 6c  l",(0-1)),("call
        73 65 74 75 70 22 2c 28 30 2d 33 29 29 2c 28 22  setup",(0-3)),("
        63 61 6c 6c 68 65 6c 64 22 2c 28 30 2d 32 29 29  callheld",(0-2))
        0d 0a 3e                                         ..>             
< ACL Data TX: Handle 256 flags 0x00 dlen 14                #84 14:00:13.515245
      Channel: 192 len 10 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 6
         FCS: 0x3e
        0d 0a 4f 4b 0d 0a 3e                             ..OK..>         
> HCI Event: Number of Completed Packets (0x13) plen 5      #85 14:00:13.520823
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5      #86 14:00:13.521604
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 9                 #87 14:00:13.524051
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
> ACL Data RX: Handle 256 flags 0x02 dlen 9                 #88 14:00:13.525316
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
> ACL Data RX: Handle 256 flags 0x02 dlen 17                #89 14:00:13.526431
      Channel: 64 len 13 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 9
         FCS: 0xe4
        41 54 2b 43 49 4e 44 3f 0d e4                    AT+CIND?..      
< ACL Data TX: Handle 256 flags 0x00 dlen 26                #90 14:00:13.526630
      Channel: 192 len 22 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 18
         FCS: 0x3e
        0d 0a 2b 43 49 4e 44 3a 20 30 2c 30 2c 30 2c 30  ..+CIND: 0,0,0,0
        0d 0a 3e                                         ..>             
< ACL Data TX: Handle 256 flags 0x00 dlen 14                #91 14:00:13.526635
      Channel: 192 len 10 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 6
         FCS: 0x3e
        0d 0a 4f 4b 0d 0a 3e                             ..OK..>         
> HCI Event: Number of Completed Packets (0x13) plen 5      #92 14:00:13.530888
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5      #93 14:00:13.531845
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 9                 #94 14:00:13.533791
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
> ACL Data RX: Handle 256 flags 0x02 dlen 9                 #95 14:00:13.535059
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
> ACL Data RX: Handle 256 flags 0x02 dlen 27                #96 14:00:13.536320
      Channel: 64 len 23 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 19
         FCS: 0xe4
        41 54 2b 43 4d 45 52 3d 33 2c 20 30 2c 20 30 2c  AT+CMER=3, 0, 0,
        20 31 0d e4                                       1..            
< ACL Data TX: Handle 256 flags 0x00 dlen 14                #97 14:00:13.536473
      Channel: 192 len 10 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 6
         FCS: 0x3e
        0d 0a 4f 4b 0d 0a 3e                             ..OK..>         
> HCI Event: Number of Completed Packets (0x13) plen 5      #98 14:00:13.540847
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 9                 #99 14:00:13.542923
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
> ACL Data RX: Handle 256 flags 0x02 dlen 18               #100 14:00:13.566681
      Channel: 64 len 14 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 10
         FCS: 0xe4
        41 54 2b 56 47 53 3d 31 35 0d e4                 AT+VGS=15..     
< ACL Data TX: Handle 256 flags 0x00 dlen 14               #101 14:00:13.566941
      Channel: 192 len 10 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 6
         FCS: 0x3e
        0d 0a 4f 4b 0d 0a 3e                             ..OK..>         
> HCI Event: Number of Completed Packets (0x13) plen 5     #102 14:00:13.570957
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 9                #103 14:00:13.572984
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
> ACL Data RX: Handle 256 flags 0x02 dlen 17               #104 14:00:13.586898
      Channel: 64 len 13 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 9
         FCS: 0xe4
        41 54 2b 42 54 52 48 3f 0d e4                    AT+BTRH?..      
< ACL Data TX: Handle 256 flags 0x00 dlen 14               #105 14:00:13.587122
      Channel: 192 len 10 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 6
         FCS: 0x3e
        0d 0a 4f 4b 0d 0a 3e                             ..OK..>         
> ACL Data RX: Handle 256 flags 0x02 dlen 12               #106 14:00:13.587937
      L2CAP: Connection Request (0x02) ident 6 len 4
        PSM: 25 (0x0019)
        Source CID: 257
< ACL Data TX: Handle 256 flags 0x00 dlen 16               #107 14:00:13.587961
      L2CAP: Connection Response (0x03) ident 6 len 8
        Destination CID: 65
        Source CID: 257
        Result: Connection pending (0x0001)
        Status: Authorization pending (0x0002)
< ACL Data TX: Handle 256 flags 0x00 dlen 16               #108 14:00:13.588134
      L2CAP: Connection Response (0x03) ident 6 len 8
        Destination CID: 65
        Source CID: 257
        Result: Connection successful (0x0000)
        Status: No further information available (0x0000)
< ACL Data TX: Handle 256 flags 0x00 dlen 23               #109 14:00:13.588140
      L2CAP: Configure Request (0x04) ident 6 len 15
        Destination CID: 257
        Flags: 0x0000
        Option: Retransmission and Flow Control (0x04) [mandatory]
          Mode: Basic (0x00)
          TX window size: 0
          Max transmit: 0
          Retransmission timeout: 0
          Monitor timeout: 0
          Maximum PDU size: 0
> HCI Event: Number of Completed Packets (0x13) plen 5     #110 14:00:13.590889
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #111 14:00:13.591891
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #112 14:00:13.592607
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #113 14:00:13.594905
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 9                #114 14:00:13.616719
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
> ACL Data RX: Handle 256 flags 0x02 dlen 33               #115 14:00:13.617941
      Channel: 64 len 29 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 25
         FCS: 0xe4
        41 54 2b 58 41 50 4c 3d 30 30 31 32 2d 30 30 30  AT+XAPL=0012-000
        31 2d 30 31 30 30 2c 33 0d e4                    1-0100,3..      
< ACL Data TX: Handle 256 flags 0x00 dlen 14               #116 14:00:13.618227
      Channel: 192 len 10 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 6
         FCS: 0x3e
        0d 0a 4f 4b 0d 0a 3e                             ..OK..>         
> HCI Event: Number of Completed Packets (0x13) plen 5     #117 14:00:13.621844
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 20               #118 14:00:13.626662
      L2CAP: Configure Request (0x04) ident 7 len 12
        Destination CID: 65
        Flags: 0x0000
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 895
        Option: Flush Timeout (0x02) [mandatory]
          Flush timeout: 65535
< ACL Data TX: Handle 256 flags 0x00 dlen 18               #119 14:00:13.626680
      L2CAP: Configure Response (0x05) ident 7 len 10
        Source CID: 257
        Flags: 0x0000
        Result: Success (0x0000)
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 895
> HCI Event: Number of Completed Packets (0x13) plen 5     #120 14:00:13.631082
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 22               #121 14:00:13.635380
      L2CAP: Configure Response (0x05) ident 6 len 14
        Source CID: 65
        Flags: 0x0000
        Result: Success (0x0000)
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 672
        Option: Flush Timeout (0x02) [mandatory]
          Flush timeout: 65535
> ACL Data RX: Handle 256 flags 0x02 dlen 9                #122 14:00:13.659055
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
> ACL Data RX: Handle 256 flags 0x02 dlen 33               #123 14:00:13.661578
      Channel: 64 len 29 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 25
         FCS: 0xe4
        41 54 2b 49 50 48 4f 4e 45 41 43 43 45 56 3d 32  AT+IPHONEACCEV=2
        2c 31 2c 39 2c 32 2c 30 0d e4                    ,1,9,2,0..      
< ACL Data TX: Handle 256 flags 0x00 dlen 14               #124 14:00:13.661796
      Channel: 192 len 10 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 6
         FCS: 0x3e
        0d 0a 4f 4b 0d 0a 3e                             ..OK..>         
> HCI Event: Number of Completed Packets (0x13) plen 5     #125 14:00:13.666003
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 9                #126 14:00:13.708101
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
> ACL Data RX: Handle 256 flags 0x02 dlen 16               #127 14:00:13.713156
      Channel: 64 len 12 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 8
         FCS: 0xe4
        41 54 2b 43 4c 43 43 0d e4                       AT+CLCC..       
< ACL Data TX: Handle 256 flags 0x00 dlen 14               #128 14:00:13.713423
      Channel: 192 len 10 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 6
         FCS: 0x3e
        0d 0a 4f 4b 0d 0a 3e                             ..OK..>         
> HCI Event: Number of Completed Packets (0x13) plen 5     #129 14:00:13.719010
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 9                #130 14:00:13.740557
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
> ACL Data RX: Handle 256 flags 0x02 dlen 31               #131 14:00:13.741630
      Channel: 64 len 27 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 23
         FCS: 0xe4
        41 54 2b 43 53 52 53 46 3d 30 2c 30 2c 30 2c 31  AT+CSRSF=0,0,0,1
        2c 30 2c 30 2c 30 0d e4                          ,0,0,0..        
< ACL Data TX: Handle 256 flags 0x00 dlen 14               #132 14:00:13.741841
      Channel: 192 len 10 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x69 cr 0 dlci 0x1a
         Control: 0xef poll/final 0
         Length: 6
         FCS: 0x3e
        0d 0a 4f 4b 0d 0a 3e                             ..OK..>         
> HCI Event: Number of Completed Packets (0x13) plen 5     #133 14:00:13.746094
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 9                #134 14:00:13.753101
      Channel: 64 len 5 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Info with Header Check (UIH) (0xef)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0xff poll/final 1
         Length: 0
         FCS: 0xf8
         Credits: 1
        f8                                               .               
< ACL Data TX: Handle 256 flags 0x00 dlen 6                #135 14:00:15.354926
      Channel: 257 len 2 [PSM 25 mode Basic (0x00)] {chan 1}
      AVDTP: Discover (0x01) Command (0x00) type 0x00 label 0 nosp 0
> HCI Event: Number of Completed Packets (0x13) plen 5     #136 14:00:15.359092
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 8                #137 14:00:15.361727
      Channel: 65 len 4 [PSM 25 mode Basic (0x00)] {chan 1}
      AVDTP: Discover (0x01) Response Accept (0x02) type 0x00 label 0 nosp 0
        ACP SEID: 1
          Media Type: Audio (0x00)
          SEP Type: SNK (0x01)
          In use: No
< ACL Data TX: Handle 256 flags 0x00 dlen 18               #138 14:00:15.363980
      Channel: 257 len 14 [PSM 25 mode Basic (0x00)] {chan 1}
      AVDTP: Set Configuration (0x03) Command (0x00) type 0x00 label 1 nosp 0
        ACP SEID: 1
        INT SEID: 4
        Service Category: Media Transport (0x01)
        Service Category: Media Codec (0x07)
          Media Type: Audio (0x00)
          Media Codec: SBC (0x00)
            Frequency: 44100 (0x20)
            Channel Mode: Dual Channel (0x04)
            Block Length: 16 (0x10)
            Subbands: 8 (0x04)
            Allocation Method: Loudness (0x01)
            Minimum Bitpool: 2
            Maximum Bitpool: 38
> HCI Event: Number of Completed Packets (0x13) plen 5     #139 14:00:15.368857
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 6                #140 14:00:15.372870
      Channel: 65 len 2 [PSM 25 mode Basic (0x00)] {chan 1}
      AVDTP: Set Configuration (0x03) Response Accept (0x02) type 0x00 label 1 nosp 0
< ACL Data TX: Handle 256 flags 0x00 dlen 7                #141 14:00:15.373388
      Channel: 257 len 3 [PSM 25 mode Basic (0x00)] {chan 1}
      AVDTP: Open (0x06) Command (0x00) type 0x00 label 2 nosp 0
        ACP SEID: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #142 14:00:15.376606
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 6                #143 14:00:15.380034
      Channel: 65 len 2 [PSM 25 mode Basic (0x00)] {chan 1}
      AVDTP: Open (0x06) Response Accept (0x02) type 0x00 label 2 nosp 0
< ACL Data TX: Handle 256 flags 0x00 dlen 12               #144 14:00:15.380182
      L2CAP: Connection Request (0x02) ident 7 len 4
        PSM: 25 (0x0019)
        Source CID: 66
> HCI Event: Number of Completed Packets (0x13) plen 5     #145 14:00:15.385034
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 16               #146 14:00:15.386713
      L2CAP: Connection Response (0x03) ident 7 len 8
        Destination CID: 322
        Source CID: 66
        Result: Connection pending (0x0001)
        Status: Authorization pending (0x0002)
> ACL Data RX: Handle 256 flags 0x02 dlen 16               #147 14:00:15.387900
      L2CAP: Connection Response (0x03) ident 7 len 8
        Destination CID: 322
        Source CID: 66
        Result: Connection successful (0x0000)
        Status: No further information available (0x0000)
< ACL Data TX: Handle 256 flags 0x00 dlen 23               #148 14:00:15.387955
      L2CAP: Configure Request (0x04) ident 8 len 15
        Destination CID: 322
        Flags: 0x0000
        Option: Retransmission and Flow Control (0x04) [mandatory]
          Mode: Basic (0x00)
          TX window size: 0
          Max transmit: 0
          Retransmission timeout: 0
          Monitor timeout: 0
          Maximum PDU size: 0
> ACL Data RX: Handle 256 flags 0x02 dlen 20               #149 14:00:15.389052
      L2CAP: Configure Request (0x04) ident 8 len 12
        Destination CID: 66
        Flags: 0x0000
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 895
        Option: Flush Timeout (0x02) [mandatory]
          Flush timeout: 65535
< ACL Data TX: Handle 256 flags 0x00 dlen 18               #150 14:00:15.389071
      L2CAP: Configure Response (0x05) ident 8 len 10
        Source CID: 322
        Flags: 0x0000
        Result: Success (0x0000)
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 895
> HCI Event: Number of Completed Packets (0x13) plen 5     #151 14:00:15.391839
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #152 14:00:15.393973
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 22               #153 14:00:15.395391
      L2CAP: Configure Response (0x05) ident 8 len 14
        Source CID: 66
        Flags: 0x0000
        Result: Success (0x0000)
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 672
        Option: Flush Timeout (0x02) [mandatory]
          Flush timeout: 65535
< ACL Data TX: Handle 256 flags 0x00 dlen 7                #154 14:00:15.395622
      Channel: 257 len 3 [PSM 25 mode Basic (0x00)] {chan 1}
      AVDTP: Start (0x07) Command (0x00) type 0x00 label 3 nosp 0
        ACP SEID: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #155 14:00:15.400025
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 6                #156 14:00:15.406777
      Channel: 65 len 2 [PSM 25 mode Basic (0x00)] {chan 1}
      AVDTP: Start (0x07) Response Accept (0x02) type 0x00 label 3 nosp 0
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #157 14:00:15.409673
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #158 14:00:15.419609
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #159 14:00:15.424330
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #160 14:00:15.434607
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #161 14:00:15.439157
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #162 14:00:15.448092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #163 14:00:15.453824
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #164 14:00:15.463094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #165 14:00:15.468323
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #166 14:00:15.478093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #167 14:00:15.482837
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #168 14:00:15.492092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #169 14:00:15.497334
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #170 14:00:15.507080
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #171 14:00:15.511841
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #172 14:00:15.522088
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #173 14:00:15.526365
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #174 14:00:15.536085
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #175 14:00:15.540876
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #176 14:00:15.551080
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #177 14:00:15.555382
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #178 14:00:15.565083
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #179 14:00:15.569898
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #180 14:00:15.580080
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #181 14:00:15.584409
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #182 14:00:15.598398
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #183 14:00:15.606925
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #184 14:00:15.612703
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #185 14:00:15.612979
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #186 14:00:15.623092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #187 14:00:15.627957
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #188 14:00:15.637092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #189 14:00:15.642469
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #190 14:00:15.652092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #191 14:00:15.656990
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #192 14:00:15.667094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #193 14:00:15.671497
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #194 14:00:15.681093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #195 14:00:15.686006
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #196 14:00:15.696095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #197 14:00:15.700521
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> ACL Data RX: Handle 256 flags 0x02 dlen 12               #198 14:00:15.708105
      L2CAP: Connection Request (0x02) ident 9 len 4
        PSM: 23 (0x0017)
        Source CID: 387
< ACL Data TX: Handle 256 flags 0x00 dlen 16               #199 14:00:15.708166
      L2CAP: Connection Response (0x03) ident 9 len 8
        Destination CID: 67
        Source CID: 387
        Result: Connection pending (0x0001)
        Status: Authorization pending (0x0002)
< ACL Data TX: Handle 256 flags 0x00 dlen 16               #200 14:00:15.708328
      L2CAP: Connection Response (0x03) ident 9 len 8
        Destination CID: 67
        Source CID: 387
        Result: Connection successful (0x0000)
        Status: No further information available (0x0000)
< ACL Data TX: Handle 256 flags 0x00 dlen 23               #201 14:00:15.708334
      L2CAP: Configure Request (0x04) ident 9 len 15
        Destination CID: 387
        Flags: 0x0000
        Option: Retransmission and Flow Control (0x04) [mandatory]
          Mode: Basic (0x00)
          TX window size: 0
          Max transmit: 0
          Retransmission timeout: 0
          Monitor timeout: 0
          Maximum PDU size: 0
> ACL Data RX: Handle 256 flags 0x02 dlen 12               #202 14:00:15.710473
      L2CAP: Connection Request (0x02) ident 10 len 4
        PSM: 1 (0x0001)
        Source CID: 452
> HCI Event: Number of Completed Packets (0x13) plen 5     #203 14:00:15.710612
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x00 dlen 16               #204 14:00:15.710658
      L2CAP: Connection Response (0x03) ident 10 len 8
        Destination CID: 68
        Source CID: 452
        Result: Connection successful (0x0000)
        Status: No further information available (0x0000)
> HCI Event: Number of Completed Packets (0x13) plen 5     #205 14:00:15.712860
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x00 dlen 23               #206 14:00:15.712913
      L2CAP: Configure Request (0x04) ident 10 len 15
        Destination CID: 452
        Flags: 0x0000
        Option: Retransmission and Flow Control (0x04) [mandatory]
          Mode: Basic (0x00)
          TX window size: 0
          Max transmit: 0
          Retransmission timeout: 0
          Monitor timeout: 0
          Maximum PDU size: 0
> HCI Event: Number of Completed Packets (0x13) plen 5     #207 14:00:15.714597
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #208 14:00:15.714630
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #209 14:00:15.715802
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #210 14:00:15.716677
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 10               #211 14:00:15.716684
      L2CAP: Information Request (0x0a) ident 11 len 2
        Type: Extended features supported (0x0002)
< ACL Data TX: Handle 256 flags 0x00 dlen 16               #212 14:00:15.716735
      L2CAP: Information Response (0x0b) ident 11 len 8
        Type: Extended features supported (0x0002)
        Result: Success (0x0000)
        Features: 0x000002b8
          Enhanced Retransmission Mode
          Streaming Mode
          FCS Option
          Fixed Channels
          Unicast Connectionless Data Reception
> HCI Event: Number of Completed Packets (0x13) plen 5     #213 14:00:15.717880
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 18               #214 14:00:15.717890
      L2CAP: Configure Response (0x05) ident 9 len 10
        Source CID: 67
        Flags: 0x0000
        Result: Success (0x0000)
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 672
> ACL Data RX: Handle 256 flags 0x02 dlen 16               #215 14:00:15.721882
      L2CAP: Configure Request (0x04) ident 12 len 8
        Destination CID: 68
        Flags: 0x0000
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 48
< ACL Data TX: Handle 256 flags 0x00 dlen 18               #216 14:00:15.721942
      L2CAP: Configure Response (0x05) ident 12 len 10
        Source CID: 452
        Flags: 0x0000
        Result: Success (0x0000)
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 48
> ACL Data RX: Handle 256 flags 0x02 dlen 14               #217 14:00:15.724266
      L2CAP: Configure Response (0x05) ident 10 len 6
        Source CID: 68
        Flags: 0x0000
        Result: Success (0x0000)
> HCI Event: Number of Completed Packets (0x13) plen 5     #218 14:00:15.725025
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #219 14:00:15.725602
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #220 14:00:15.726604
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #221 14:00:15.729047
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> ACL Data RX: Handle 256 flags 0x02 dlen 34               #222 14:00:15.735418
      L2CAP: Configure Request (0x04) ident 13 len 26
        Destination CID: 67
        Flags: 0x0000
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 672
        Option: Flush Timeout (0x02) [mandatory]
          Flush timeout: 65535
        Option: Retransmission and Flow Control (0x04) [mandatory]
          Mode: Enhanced Retransmission (0x03)
          TX window size: 5
          Max transmit: 10
          Retransmission timeout: 0
          Monitor timeout: 0
          Maximum PDU size: 4022
        Option: Frame Check Sequence (0x05) [mandatory]
          FCS: 16-bit FCS (0x01)
< ACL Data TX: Handle 256 flags 0x00 dlen 25               #223 14:00:15.735472
      L2CAP: Configure Response (0x05) ident 13 len 17
        Source CID: 387
        Flags: 0x0000
        Result: Failure - unacceptable parameters (0x0001)
        Option: Retransmission and Flow Control (0x04) [mandatory]
          Mode: Basic (0x00)
          TX window size: 5
          Max transmit: 10
          Retransmission timeout: 0
          Monitor timeout: 0
          Maximum PDU size: 4022
> HCI Event: Number of Completed Packets (0x13) plen 5     #224 14:00:15.737933
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 25               #225 14:00:15.737939
      Channel: 68 len 21 [PSM 1 mode Basic (0x00)] {chan 4}
      SDP: Service Search Attribute Request (0x06) tid 1 len 16
        Search pattern: [len 5]
          Sequence (6) with 3 bytes [8 extra bits] len 5
            UUID (3) with 2 bytes [0 extra bits] len 3
              A/V Remote Control Target (0x110c)
        Max record count: 38
        Attribute list: [len 8]
          Sequence (6) with 6 bytes [8 extra bits] len 8
            Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
              0x0009
            Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
              0x0311
        Continuation state: 0
< ACL Data TX: Handle 256 flags 0x00 dlen 35               #226 14:00:15.738070
      Channel: 452 len 31 [PSM 1 mode Basic (0x00)] {chan 4}
      SDP: Service Search Attribute Response (0x07) tid 1 len 26
        Attribute bytes: 23
          Attribute list: [len 19] {position 0}
            Attribute: Bluetooth Profile Descriptor List (0x0009) [len 2]
              Sequence (6) with 6 bytes [8 extra bits] len 8
                UUID (3) with 2 bytes [0 extra bits] len 3
                  A/V Remote Control (0x110e)
                Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
                  0x0105
            Attribute: Unknown (0x0311) [len 2]
              0x005f
        Continuation state: 0
> HCI Event: Number of Completed Packets (0x13) plen 5     #227 14:00:15.740832
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #228 14:00:15.741865
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #229 14:00:15.743822
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> ACL Data RX: Handle 256 flags 0x02 dlen 20               #230 14:00:15.750053
      L2CAP: Configure Request (0x04) ident 14 len 12
        Destination CID: 67
        Flags: 0x0000
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 672
        Option: Flush Timeout (0x02) [mandatory]
          Flush timeout: 65535
< ACL Data TX: Handle 256 flags 0x00 dlen 18               #231 14:00:15.750095
      L2CAP: Configure Response (0x05) ident 14 len 10
        Source CID: 387
        Flags: 0x0000
        Result: Success (0x0000)
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 672
< ACL Data TX: Handle 256 flags 0x00 dlen 18               #232 14:00:15.750299
      Channel: 387 len 14 [PSM 23 mode Basic (0x00)] {chan 3}
      AVCTP Control: Command: type 0x00 label 0 PID 0x110e
        AV/C: Status: address 0x48 opcode 0x00
          Subunit: Panel
          Opcode: Vendor Dependent
          Company ID: 0x001958
          AVRCP: GetCapabilities pt Single len 0x0001
            CapabilityID: 0x03 (EventsID)
> HCI Event: Number of Completed Packets (0x13) plen 5     #233 14:00:15.752597
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 12               #234 14:00:15.752600
      L2CAP: Disconnection Request (0x06) ident 15 len 4
        Destination CID: 68
        Source CID: 452
< ACL Data TX: Handle 256 flags 0x00 dlen 12               #235 14:00:15.752609
      L2CAP: Disconnection Response (0x07) ident 15 len 4
        Destination CID: 68
        Source CID: 452
> HCI Event: Number of Completed Packets (0x13) plen 5     #236 14:00:15.755846
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #237 14:00:15.756864
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #238 14:00:15.757884
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #239 14:00:15.758047
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> ACL Data RX: Handle 256 flags 0x02 dlen 17               #240 14:00:15.765169
      Channel: 67 len 13 [PSM 23 mode Basic (0x00)] {chan 3}
      AVCTP Control: Response: type 0x00 label 1 PID 0x110e
        AV/C: Not Implemented: address 0x48 opcode 0x00
          Subunit: Panel
          Opcode: Vendor Dependent
        00 19 58 10 00 00 00                             ..X....         
> HCI Event: Number of Completed Packets (0x13) plen 5     #241 14:00:15.767595
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 12               #242 14:00:15.767598
      L2CAP: Connection Request (0x02) ident 16 len 4
        PSM: 1 (0x0001)
        Source CID: 516
< ACL Data TX: Handle 256 flags 0x00 dlen 16               #243 14:00:15.767629
      L2CAP: Connection Response (0x03) ident 16 len 8
        Destination CID: 68
        Source CID: 516
        Result: Connection successful (0x0000)
        Status: No further information available (0x0000)
< ACL Data TX: Handle 256 flags 0x00 dlen 23               #244 14:00:15.767632
      L2CAP: Configure Request (0x04) ident 11 len 15
        Destination CID: 516
        Flags: 0x0000
        Option: Retransmission and Flow Control (0x04) [mandatory]
          Mode: Basic (0x00)
          TX window size: 0
          Max transmit: 0
          Retransmission timeout: 0
          Monitor timeout: 0
          Maximum PDU size: 0
> HCI Event: Number of Completed Packets (0x13) plen 5     #245 14:00:15.771819
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #246 14:00:15.772792
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #247 14:00:15.772834
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> ACL Data RX: Handle 256 flags 0x02 dlen 16               #248 14:00:15.778962
      L2CAP: Configure Request (0x04) ident 17 len 8
        Destination CID: 68
        Flags: 0x0000
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 48
< ACL Data TX: Handle 256 flags 0x00 dlen 18               #249 14:00:15.778999
      L2CAP: Configure Response (0x05) ident 17 len 10
        Source CID: 516
        Flags: 0x0000
        Result: Success (0x0000)
        Option: Maximum Transmission Unit (0x01) [mandatory]
          MTU: 48
> HCI Event: Number of Completed Packets (0x13) plen 5     #250 14:00:15.781619
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 14               #251 14:00:15.781625
      L2CAP: Configure Response (0x05) ident 11 len 6
        Source CID: 68
        Flags: 0x0000
        Result: Success (0x0000)
> HCI Event: Number of Completed Packets (0x13) plen 5     #252 14:00:15.785091
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #253 14:00:15.787361
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> ACL Data RX: Handle 256 flags 0x02 dlen 25               #254 14:00:15.794289
      Channel: 68 len 21 [PSM 1 mode Basic (0x00)] {chan 4}
      SDP: Service Search Attribute Request (0x06) tid 1 len 16
        Search pattern: [len 5]
          Sequence (6) with 3 bytes [8 extra bits] len 5
            UUID (3) with 2 bytes [0 extra bits] len 3
              A/V Remote Control Target (0x110c)
        Max record count: 38
        Attribute list: [len 8]
          Sequence (6) with 6 bytes [8 extra bits] len 8
            Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
              0x0009
            Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
              0x0311
        Continuation state: 0
< ACL Data TX: Handle 256 flags 0x00 dlen 35               #255 14:00:15.794481
      Channel: 516 len 31 [PSM 1 mode Basic (0x00)] {chan 4}
      SDP: Service Search Attribute Response (0x07) tid 1 len 26
        Attribute bytes: 23
          Attribute list: [len 19] {position 0}
            Attribute: Bluetooth Profile Descriptor List (0x0009) [len 2]
              Sequence (6) with 6 bytes [8 extra bits] len 8
                UUID (3) with 2 bytes [0 extra bits] len 3
                  A/V Remote Control (0x110e)
                Unsigned Integer (1) with 2 bytes [0 extra bits] len 3
                  0x0105
            Attribute: Unknown (0x0311) [len 2]
              0x005f
        Continuation state: 0
> HCI Event: Number of Completed Packets (0x13) plen 5     #256 14:00:15.796896
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #257 14:00:15.800017
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #258 14:00:15.801989
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> ACL Data RX: Handle 256 flags 0x02 dlen 12               #259 14:00:15.812834
      L2CAP: Disconnection Request (0x06) ident 18 len 4
        Destination CID: 68
        Source CID: 516
< ACL Data TX: Handle 256 flags 0x00 dlen 12               #260 14:00:15.812886
      L2CAP: Disconnection Response (0x07) ident 18 len 4
        Destination CID: 68
        Source CID: 516
> HCI Event: Number of Completed Packets (0x13) plen 5     #261 14:00:15.815845
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #262 14:00:15.816526
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #263 14:00:15.818624
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #264 14:00:15.826086
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #265 14:00:15.831122
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #266 14:00:15.840843
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #267 14:00:15.845397
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #268 14:00:15.855084
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #269 14:00:15.860150
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #270 14:00:15.870086
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #271 14:00:15.874667
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #272 14:00:15.885084
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #273 14:00:15.889173
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #274 14:00:15.898097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #275 14:00:15.903696
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #276 14:00:15.913094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #277 14:00:15.918207
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #278 14:00:15.928092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #279 14:00:15.932223
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #280 14:00:15.941877
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #281 14:00:15.947166
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #282 14:00:15.957100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #283 14:00:15.961744
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #284 14:00:15.972101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #285 14:00:15.976263
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #286 14:00:15.986095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #287 14:00:15.990771
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #288 14:00:16.001094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #289 14:00:16.005217
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #290 14:00:16.018095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #291 14:00:16.019643
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #292 14:00:16.030095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #293 14:00:16.034310
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #294 14:00:16.045092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #295 14:00:16.048736
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #296 14:00:16.058092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #297 14:00:16.063333
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #298 14:00:16.073091
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #299 14:00:16.077850
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #300 14:00:16.087095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #301 14:00:16.092356
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #302 14:00:16.102092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #303 14:00:16.106870
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #304 14:00:16.117100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #305 14:00:16.121383
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #306 14:00:16.131094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #307 14:00:16.135396
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #308 14:00:16.144857
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #309 14:00:16.150302
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #310 14:00:16.160096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #311 14:00:16.164923
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #312 14:00:16.175093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #313 14:00:16.179430
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #314 14:00:16.190096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #315 14:00:16.193945
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #316 14:00:16.202967
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #317 14:00:16.208460
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #318 14:00:16.221094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #319 14:00:16.222835
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #320 14:00:16.232092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #321 14:00:16.237482
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #322 14:00:16.247106
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #323 14:00:16.251849
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #324 14:00:16.262096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #325 14:00:16.266507
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #326 14:00:16.276093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #327 14:00:16.281019
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #328 14:00:16.291095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #329 14:00:16.295531
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #330 14:00:16.306095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #331 14:00:16.310047
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #332 14:00:16.320097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #333 14:00:16.324556
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #334 14:00:16.335092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #335 14:00:16.338969
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #336 14:00:16.348611
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #337 14:00:16.353120
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #338 14:00:16.362675
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #339 14:00:16.367860
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #340 14:00:16.376859
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #341 14:00:16.382159
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #342 14:00:16.391982
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #343 14:00:16.396879
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #344 14:00:16.406962
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #345 14:00:16.411467
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #346 14:00:16.420970
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #347 14:00:16.426146
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #348 14:00:16.436096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #349 14:00:16.440657
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #350 14:00:16.451095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #351 14:00:16.455167
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #352 14:00:16.465095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #353 14:00:16.469686
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #354 14:00:16.480096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #355 14:00:16.484192
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #356 14:00:16.493093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #357 14:00:16.498706
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #358 14:00:16.508098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #359 14:00:16.513218
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #360 14:00:16.523098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #361 14:00:16.527740
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #362 14:00:16.537099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #363 14:00:16.542240
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #364 14:00:16.552094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #365 14:00:16.556240
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #366 14:00:16.565884
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #367 14:00:16.571196
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #368 14:00:16.581100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #369 14:00:16.585782
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #370 14:00:16.596093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #371 14:00:16.600294
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #372 14:00:16.610096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #373 14:00:16.614806
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #374 14:00:16.625094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #375 14:00:16.629321
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #376 14:00:16.640097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #377 14:00:16.643831
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #378 14:00:16.653093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #379 14:00:16.658348
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #380 14:00:16.668098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #381 14:00:16.672765
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #382 14:00:16.682098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #383 14:00:16.687371
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #384 14:00:16.697095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #385 14:00:16.701878
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #386 14:00:16.712093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #387 14:00:16.716392
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #388 14:00:16.726093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #389 14:00:16.730905
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #390 14:00:16.741092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #391 14:00:16.745418
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #392 14:00:16.755095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #393 14:00:16.759871
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #394 14:00:16.769607
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #395 14:00:16.773953
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #396 14:00:16.782593
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #397 14:00:16.788762
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #398 14:00:16.798096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #399 14:00:16.803314
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #400 14:00:16.813092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #401 14:00:16.818006
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #402 14:00:16.828098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #403 14:00:16.832524
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #404 14:00:16.842097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #405 14:00:16.847030
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #406 14:00:16.857091
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #407 14:00:16.861545
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #408 14:00:16.876058
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #409 14:00:16.882096
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #410 14:00:16.887862
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #411 14:00:16.890141
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #412 14:00:16.905080
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #413 14:00:16.909018
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #414 14:00:16.916093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #415 14:00:16.919593
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #416 14:00:16.930096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #417 14:00:16.934106
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #418 14:00:16.943094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #419 14:00:16.948615
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #420 14:00:16.958095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #421 14:00:16.963015
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #422 14:00:16.973093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #423 14:00:16.977121
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #424 14:00:16.986643
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #425 14:00:16.992054
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #426 14:00:17.002098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #427 14:00:17.006668
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #428 14:00:17.016097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #429 14:00:17.021183
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #430 14:00:17.031095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #431 14:00:17.035565
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #432 14:00:17.046094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #433 14:00:17.050210
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #434 14:00:17.060093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #435 14:00:17.064717
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #436 14:00:17.075095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #437 14:00:17.079232
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #438 14:00:17.090103
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #439 14:00:17.093508
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #440 14:00:17.103092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #441 14:00:17.108269
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #442 14:00:17.118095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #443 14:00:17.122768
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #444 14:00:17.132098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #445 14:00:17.137279
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #446 14:00:17.147093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #447 14:00:17.151790
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #448 14:00:17.162093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #449 14:00:17.166305
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #450 14:00:17.176093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #451 14:00:17.180583
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #452 14:00:17.190607
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #453 14:00:17.194967
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #454 14:00:17.204649
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #455 14:00:17.209423
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #456 14:00:17.220093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #457 14:00:17.224356
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #458 14:00:17.235095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #459 14:00:17.238867
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #460 14:00:17.248097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #461 14:00:17.253380
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #462 14:00:17.263093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #463 14:00:17.267895
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #464 14:00:17.277094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #465 14:00:17.282410
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #466 14:00:17.292098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #467 14:00:17.296919
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #468 14:00:17.306980
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #469 14:00:17.311432
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #470 14:00:17.321093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #471 14:00:17.325945
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #472 14:00:17.335940
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #473 14:00:17.340452
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #474 14:00:17.350093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #475 14:00:17.354823
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #476 14:00:17.365093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #477 14:00:17.369478
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #478 14:00:17.383094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #479 14:00:17.383909
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #480 14:00:17.393096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #481 14:00:17.397960
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #482 14:00:17.407980
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #483 14:00:17.412575
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #484 14:00:17.422096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #485 14:00:17.427528
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #486 14:00:17.437094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #487 14:00:17.442041
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #488 14:00:17.452095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #489 14:00:17.456554
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #490 14:00:17.466098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #491 14:00:17.471066
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #492 14:00:17.481093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #493 14:00:17.485580
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #494 14:00:17.496092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #495 14:00:17.500091
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #496 14:00:17.510092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #497 14:00:17.514447
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #498 14:00:17.525093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #499 14:00:17.529117
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #500 14:00:17.538096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #501 14:00:17.543627
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #502 14:00:17.557092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #503 14:00:17.558033
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #504 14:00:17.568099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #505 14:00:17.572657
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #506 14:00:17.582096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #507 14:00:17.587165
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #508 14:00:17.597095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #509 14:00:17.601602
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #510 14:00:17.614764
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #511 14:00:17.615751
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #512 14:00:17.625947
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #513 14:00:17.630488
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #514 14:00:17.641093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #515 14:00:17.645221
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #516 14:00:17.659727
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #517 14:00:17.660913
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #518 14:00:17.673095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #519 14:00:17.674080
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #520 14:00:17.683096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #521 14:00:17.688752
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #522 14:00:17.698097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #523 14:00:17.703270
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #524 14:00:17.717094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #525 14:00:17.717284
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #526 14:00:17.726992
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #527 14:00:17.732291
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #528 14:00:17.742094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #529 14:00:17.746805
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #530 14:00:17.757093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #531 14:00:17.761248
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #532 14:00:17.775093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #533 14:00:17.775394
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #534 14:00:17.785094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #535 14:00:17.790340
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #536 14:00:17.800092
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #537 14:00:17.804856
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #538 14:00:17.817035
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #539 14:00:17.818843
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #540 14:00:17.827996
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #541 14:00:17.833712
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #542 14:00:17.843097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #543 14:00:17.848394
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #544 14:00:17.862094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #545 14:00:17.862854
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #546 14:00:17.872106
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #547 14:00:17.877416
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #548 14:00:17.887094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #549 14:00:17.891927
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #550 14:00:17.902097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #551 14:00:17.906440
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #552 14:00:17.916099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #553 14:00:17.920951
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #554 14:00:17.931094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #555 14:00:17.935273
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #556 14:00:17.945093
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #557 14:00:17.949983
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #558 14:00:17.960094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #559 14:00:17.964490
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #560 14:00:17.975096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #561 14:00:17.978861
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #562 14:00:17.988094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #563 14:00:17.993512
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #564 14:00:18.003089
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #565 14:00:18.008027
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #566 14:00:18.018096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #567 14:00:18.022467
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #568 14:00:18.031612
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #569 14:00:18.036793
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #570 14:00:18.047016
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #571 14:00:18.051113
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #572 14:00:18.063096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #573 14:00:18.066005
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #574 14:00:18.076099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #575 14:00:18.080500
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #576 14:00:18.091099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #577 14:00:18.095105
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #578 14:00:18.105095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #579 14:00:18.109616
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #580 14:00:18.120096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #581 14:00:18.124125
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #582 14:00:18.133098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #583 14:00:18.138645
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #584 14:00:18.153152
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #585 14:00:18.167670
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #586 14:00:18.169923
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #587 14:00:18.176098
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #588 14:00:18.182099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #589 14:00:18.182166
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #590 14:00:18.192099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #591 14:00:18.196606
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #592 14:00:18.206097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #593 14:00:18.210968
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #594 14:00:18.221096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #595 14:00:18.225719
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #596 14:00:18.236099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #597 14:00:18.239706
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #598 14:00:18.250107
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #599 14:00:18.254648
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #600 14:00:18.265096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #601 14:00:18.269253
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #602 14:00:18.280096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #603 14:00:18.283767
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #604 14:00:18.293094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #605 14:00:18.298282
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #606 14:00:18.308094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #607 14:00:18.312790
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #608 14:00:18.322097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #609 14:00:18.327301
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #610 14:00:18.337096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #611 14:00:18.341816
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #612 14:00:18.352099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #613 14:00:18.356216
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #614 14:00:18.366096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #615 14:00:18.370844
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #616 14:00:18.381094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #617 14:00:18.385357
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #618 14:00:18.395094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #619 14:00:18.399873
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #620 14:00:18.410099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #621 14:00:18.414378
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #622 14:00:18.425094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #623 14:00:18.428891
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #624 14:00:18.438094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #625 14:00:18.443405
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #626 14:00:18.452608
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #627 14:00:18.457686
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #628 14:00:18.467016
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #629 14:00:18.472267
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #630 14:00:18.482097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #631 14:00:18.486942
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #632 14:00:18.497105
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #633 14:00:18.501452
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #634 14:00:18.511094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #635 14:00:18.515967
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #636 14:00:18.526104
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #637 14:00:18.530475
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #638 14:00:18.541094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #639 14:00:18.544987
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #640 14:00:18.555094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #641 14:00:18.559502
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #642 14:00:18.569869
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #643 14:00:18.574018
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #644 14:00:18.583094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #645 14:00:18.588528
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #646 14:00:18.598094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #647 14:00:18.603041
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #648 14:00:18.613102
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #649 14:00:18.617465
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #650 14:00:18.627095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #651 14:00:18.631830
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #652 14:00:18.642097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #653 14:00:18.646579
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #654 14:00:18.656097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #655 14:00:18.660546
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #656 14:00:18.670641
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #657 14:00:18.675514
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #658 14:00:18.686098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #659 14:00:18.690116
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #660 14:00:18.700099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #661 14:00:18.704627
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #662 14:00:18.715100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #663 14:00:18.719136
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #664 14:00:18.728097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #665 14:00:18.733657
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #666 14:00:18.743095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #667 14:00:18.748162
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #668 14:00:18.758095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #669 14:00:18.762680
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #670 14:00:18.772097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #671 14:00:18.777113
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #672 14:00:18.787097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #673 14:00:18.791556
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #674 14:00:18.801096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #675 14:00:18.806212
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #676 14:00:18.816099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #677 14:00:18.820725
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #678 14:00:18.831096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #679 14:00:18.835242
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #680 14:00:18.845094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #681 14:00:18.849750
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #682 14:00:18.860094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #683 14:00:18.864179
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #684 14:00:18.872615
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #685 14:00:18.878620
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #686 14:00:18.887842
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #687 14:00:18.892976
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #688 14:00:18.903097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #689 14:00:18.907803
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #690 14:00:18.917102
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #691 14:00:18.922314
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #692 14:00:18.932094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #693 14:00:18.936827
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #694 14:00:18.947096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #695 14:00:18.951339
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #696 14:00:18.961096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #697 14:00:18.965850
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #698 14:00:18.976098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #699 14:00:18.980367
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #700 14:00:18.990107
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #701 14:00:18.994774
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #702 14:00:19.005029
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #703 14:00:19.009397
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #704 14:00:19.020100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #705 14:00:19.023902
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #706 14:00:19.033096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #707 14:00:19.038420
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #708 14:00:19.048097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #709 14:00:19.052929
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #710 14:00:19.062096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #711 14:00:19.067252
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #712 14:00:19.077094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #713 14:00:19.081432
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #714 14:00:19.094909
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #715 14:00:19.096290
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #716 14:00:19.106098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #717 14:00:19.110569
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #718 14:00:19.121096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #719 14:00:19.125488
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #720 14:00:19.136098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #721 14:00:19.140000
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #722 14:00:19.150096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #723 14:00:19.154511
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #724 14:00:19.165096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #725 14:00:19.169026
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #726 14:00:19.178094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #727 14:00:19.183352
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #728 14:00:19.193094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #729 14:00:19.198051
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #730 14:00:19.207968
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #731 14:00:19.212340
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #732 14:00:19.222094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #733 14:00:19.227082
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #734 14:00:19.237095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #735 14:00:19.241587
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #736 14:00:19.255098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #737 14:00:19.255972
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #738 14:00:19.266097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #739 14:00:19.270613
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #740 14:00:19.281096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #741 14:00:19.285033
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #742 14:00:19.294616
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #743 14:00:19.299330
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #744 14:00:19.309945
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #745 14:00:19.314218
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #746 14:00:19.325095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #747 14:00:19.328664
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #748 14:00:19.338099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #749 14:00:19.343180
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #750 14:00:19.353095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #751 14:00:19.357686
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #752 14:00:19.367097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #753 14:00:19.372200
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #754 14:00:19.382096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #755 14:00:19.386712
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #756 14:00:19.396094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #757 14:00:19.401154
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #758 14:00:19.410998
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #759 14:00:19.415737
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #760 14:00:19.426097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #761 14:00:19.430251
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #762 14:00:19.444761
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #763 14:00:19.458098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #764 14:00:19.459095
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #765 14:00:19.465095
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #766 14:00:19.471094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #767 14:00:19.473697
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #768 14:00:19.488300
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #769 14:00:19.490952
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #770 14:00:19.502832
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #771 14:00:19.504607
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #772 14:00:19.511866
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #773 14:00:19.517081
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #774 14:00:19.527098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #775 14:00:19.531849
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #776 14:00:19.542096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #777 14:00:19.546351
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #778 14:00:19.556094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #779 14:00:19.560863
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #780 14:00:19.571097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #781 14:00:19.575377
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #782 14:00:19.585097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #783 14:00:19.589888
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #784 14:00:19.600098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #785 14:00:19.604302
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #786 14:00:19.615094
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #787 14:00:19.618375
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #788 14:00:19.628100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #789 14:00:19.633423
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #790 14:00:19.643095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #791 14:00:19.647938
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #792 14:00:19.657096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #793 14:00:19.662140
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #794 14:00:19.672095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #795 14:00:19.676463
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #796 14:00:19.686097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #797 14:00:19.691279
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #798 14:00:19.705986
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #799 14:00:19.706609
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #800 14:00:19.719609
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #801 14:00:19.719979
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #802 14:00:19.730108
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #803 14:00:19.734932
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #804 14:00:19.745097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #805 14:00:19.749526
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #806 14:00:19.760099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #807 14:00:19.764035
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #808 14:00:19.773095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #809 14:00:19.778548
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #810 14:00:19.788100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #811 14:00:19.793061
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #812 14:00:19.803101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #813 14:00:19.807573
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #814 14:00:19.817102
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #815 14:00:19.822086
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #816 14:00:19.832097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #817 14:00:19.836501
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #818 14:00:19.846096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #819 14:00:19.851111
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #820 14:00:19.861098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #821 14:00:19.865627
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #822 14:00:19.875961
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #823 14:00:19.880142
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #824 14:00:19.890097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #825 14:00:19.894373
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #826 14:00:19.907097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #827 14:00:19.909044
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #828 14:00:19.918097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #829 14:00:19.923153
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #830 14:00:19.933030
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #831 14:00:19.938050
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #832 14:00:19.948099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #833 14:00:19.952698
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #834 14:00:19.962100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #835 14:00:19.967213
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #836 14:00:19.977097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #837 14:00:19.981721
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #838 14:00:19.991097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #839 14:00:19.996130
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #840 14:00:20.006006
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #841 14:00:20.010747
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #842 14:00:20.021102
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #843 14:00:20.025260
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #844 14:00:20.035098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #845 14:00:20.039613
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #846 14:00:20.049865
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #847 14:00:20.054291
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #848 14:00:20.065022
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #849 14:00:20.068802
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #850 14:00:20.078097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #851 14:00:20.083313
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #852 14:00:20.093096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #853 14:00:20.097828
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #854 14:00:20.106909
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #855 14:00:20.112342
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #856 14:00:20.122106
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #857 14:00:20.126328
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #858 14:00:20.135995
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #859 14:00:20.141068
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #860 14:00:20.151095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #861 14:00:20.155875
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #862 14:00:20.166095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #863 14:00:20.170386
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #864 14:00:20.180097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #865 14:00:20.184827
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #866 14:00:20.195097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #867 14:00:20.199240
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #868 14:00:20.210099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #869 14:00:20.213426
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #870 14:00:20.223095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #871 14:00:20.228192
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #872 14:00:20.238099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #873 14:00:20.242445
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #874 14:00:20.252100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #875 14:00:20.257466
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #876 14:00:20.267101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #877 14:00:20.271971
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #878 14:00:20.282095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #879 14:00:20.286489
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #880 14:00:20.296097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #881 14:00:20.300915
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #882 14:00:20.311097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #883 14:00:20.315518
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #884 14:00:20.326095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #885 14:00:20.329925
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #886 14:00:20.339610
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #887 14:00:20.343981
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #888 14:00:20.352733
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #889 14:00:20.359065
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #890 14:00:20.368099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #891 14:00:20.373561
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #892 14:00:20.383097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #893 14:00:20.387958
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #894 14:00:20.397096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #895 14:00:20.402586
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #896 14:00:20.412101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #897 14:00:20.416856
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #898 14:00:20.426867
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #899 14:00:20.431454
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #900 14:00:20.441097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #901 14:00:20.446124
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #902 14:00:20.455965
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #903 14:00:20.460635
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #904 14:00:20.471100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #905 14:00:20.475145
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #906 14:00:20.485104
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #907 14:00:20.489662
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #908 14:00:20.500095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #909 14:00:20.504173
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #910 14:00:20.513098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #911 14:00:20.518686
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #912 14:00:20.528099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #913 14:00:20.533197
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #914 14:00:20.543095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #915 14:00:20.547168
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #916 14:00:20.557096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #917 14:00:20.562095
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #918 14:00:20.572100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #919 14:00:20.576736
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #920 14:00:20.586100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #921 14:00:20.591092
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #922 14:00:20.601096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #923 14:00:20.605763
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #924 14:00:20.616096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #925 14:00:20.620151
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #926 14:00:20.630096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #927 14:00:20.634784
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #928 14:00:20.645095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #929 14:00:20.649297
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #930 14:00:20.662989
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #931 14:00:20.663754
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #932 14:00:20.678325
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #933 14:00:20.680950
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #934 14:00:20.688099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #935 14:00:20.692839
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #936 14:00:20.702096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #937 14:00:20.707346
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #938 14:00:20.721866
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #939 14:00:20.735096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #940 14:00:20.736173
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #941 14:00:20.741103
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5     #942 14:00:20.747105
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #943 14:00:20.750780
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #944 14:00:20.760612
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #945 14:00:20.764860
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #946 14:00:20.774925
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #947 14:00:20.779975
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #948 14:00:20.790097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #949 14:00:20.794425
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #950 14:00:20.805096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #951 14:00:20.808937
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #952 14:00:20.818098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #953 14:00:20.823252
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #954 14:00:20.833097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #955 14:00:20.837964
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #956 14:00:20.848101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #957 14:00:20.852470
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #958 14:00:20.862096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #959 14:00:20.866987
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #960 14:00:20.877020
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #961 14:00:20.881495
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #962 14:00:20.891096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #963 14:00:20.896010
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #964 14:00:20.906101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #965 14:00:20.910522
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #966 14:00:20.921095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #967 14:00:20.925038
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #968 14:00:20.935097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #969 14:00:20.939547
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #970 14:00:20.950095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #971 14:00:20.954066
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #972 14:00:20.963098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #973 14:00:20.968053
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #974 14:00:20.977884
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #975 14:00:20.983006
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #976 14:00:20.992100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #977 14:00:20.997593
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #978 14:00:21.007097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #979 14:00:21.012111
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #980 14:00:21.022098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #981 14:00:21.026631
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #982 14:00:21.036101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #983 14:00:21.041141
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #984 14:00:21.051096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #985 14:00:21.055648
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #986 14:00:21.070070
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #987 14:00:21.070140
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #988 14:00:21.080096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #989 14:00:21.084575
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #990 14:00:21.095098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #991 14:00:21.099184
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #992 14:00:21.108095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #993 14:00:21.113696
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #994 14:00:21.123098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #995 14:00:21.128207
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #996 14:00:21.142096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #997 14:00:21.142284
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5     #998 14:00:21.152100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837              #999 14:00:21.157231
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1000 14:00:21.167100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1001 14:00:21.171676
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1002 14:00:21.180613
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1003 14:00:21.185962
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1004 14:00:21.195840
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1005 14:00:21.200609
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1006 14:00:21.211096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1007 14:00:21.215134
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1008 14:00:21.225099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1009 14:00:21.229655
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1010 14:00:21.240097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1011 14:00:21.244311
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1012 14:00:21.255098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1013 14:00:21.258822
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1014 14:00:21.268097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1015 14:00:21.273334
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1016 14:00:21.283098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1017 14:00:21.287847
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1018 14:00:21.297097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1019 14:00:21.302362
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1020 14:00:21.312096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1021 14:00:21.316869
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1022 14:00:21.327096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1023 14:00:21.331386
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1024 14:00:21.345097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1025 14:00:21.345844
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1026 14:00:21.356100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1027 14:00:21.360313
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1028 14:00:21.370101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1029 14:00:21.374922
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1030 14:00:21.385103
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1031 14:00:21.388913
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1032 14:00:21.397890
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1033 14:00:21.403852
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1034 14:00:21.413018
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1035 14:00:21.418457
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1036 14:00:21.428095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1037 14:00:21.432975
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1038 14:00:21.443099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1039 14:00:21.447490
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1040 14:00:21.457098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1041 14:00:21.462000
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1042 14:00:21.472100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1043 14:00:21.476512
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1044 14:00:21.486099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1045 14:00:21.491020
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1046 14:00:21.501095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1047 14:00:21.505532
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1048 14:00:21.516101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1049 14:00:21.520049
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1050 14:00:21.530101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1051 14:00:21.534375
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1052 14:00:21.548101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1053 14:00:21.548937
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1054 14:00:21.558097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1055 14:00:21.563591
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1056 14:00:21.573104
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1057 14:00:21.578096
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1058 14:00:21.588097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1059 14:00:21.592535
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1060 14:00:21.601610
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1061 14:00:21.606759
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1062 14:00:21.616646
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1063 14:00:21.621572
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1064 14:00:21.631097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1065 14:00:21.636145
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1066 14:00:21.646098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1067 14:00:21.650660
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1068 14:00:21.661007
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1069 14:00:21.665176
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1070 14:00:21.675101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1071 14:00:21.679685
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1072 14:00:21.690102
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1073 14:00:21.694198
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1074 14:00:21.703096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1075 14:00:21.708625
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1076 14:00:21.718105
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1077 14:00:21.723223
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1078 14:00:21.733097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1079 14:00:21.737732
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1080 14:00:21.750095
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1081 14:00:21.752133
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1082 14:00:21.762099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1083 14:00:21.766757
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1084 14:00:21.777098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1085 14:00:21.781275
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1086 14:00:21.791096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1087 14:00:21.795646
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1088 14:00:21.806098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1089 14:00:21.809779
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1090 14:00:21.819856
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1091 14:00:21.824439
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1092 14:00:21.835097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1093 14:00:21.839319
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1094 14:00:21.850101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1095 14:00:21.853831
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1096 14:00:21.863097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1097 14:00:21.868346
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1098 14:00:21.878097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1099 14:00:21.882856
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1100 14:00:21.892097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1101 14:00:21.897373
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1102 14:00:21.907096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1103 14:00:21.911883
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1104 14:00:21.922099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1105 14:00:21.926392
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1106 14:00:21.936097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1107 14:00:21.940907
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1108 14:00:21.951097
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1109 14:00:21.955427
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1110 14:00:21.965098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1111 14:00:21.969935
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1112 14:00:21.980102
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1113 14:00:21.984445
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1114 14:00:21.998959
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1115 14:00:22.012102
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1116 14:00:22.013279
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1117 14:00:22.018100
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5    #1118 14:00:22.025096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1119 14:00:22.027461
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1120 14:00:22.042370
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1121 14:00:22.044946
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5    #1122 14:00:22.052096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1123 14:00:22.057007
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1124 14:00:22.067098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1125 14:00:22.071517
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1126 14:00:22.081099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1127 14:00:22.086032
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1128 14:00:22.096100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1129 14:00:22.100457
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1130 14:00:22.110100
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1131 14:00:22.115058
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1132 14:00:22.125098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1133 14:00:22.129569
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1134 14:00:22.140101
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1135 14:00:22.143958
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1136 14:00:22.153096
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1137 14:00:22.158597
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1138 14:00:22.168098
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1139 14:00:22.173111
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1140 14:00:22.183099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1141 14:00:22.187466
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> ACL Data RX: Handle 256 flags 0x02 dlen 7               #1142 14:00:22.194261
      Channel: 65 len 3 [PSM 25 mode Basic (0x00)] {chan 1}
      AVDTP: Abort (0x0a) Command (0x00) type 0x00 label 1 nosp 0
        ACP SEID: 4
< ACL Data TX: Handle 256 flags 0x00 dlen 6               #1143 14:00:22.194427
      Channel: 257 len 2 [PSM 25 mode Basic (0x00)] {chan 1}
      AVDTP: Abort (0x0a) Response Accept (0x02) type 0x00 label 1 nosp 0
> HCI Event: Number of Completed Packets (0x13) plen 5    #1144 14:00:22.197018
        Num handles: 1
        Handle: 256
        Count: 1
> HCI Event: Number of Completed Packets (0x13) plen 5    #1145 14:00:22.199947
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1146 14:00:22.201959
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1147 14:00:22.212613
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1148 14:00:22.216389
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1149 14:00:22.227019
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1150 14:00:22.231028
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1151 14:00:22.245672
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1152 14:00:22.260183
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1153 14:00:22.274695
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1154 14:00:22.311099
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1155 14:00:22.311154
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1156 14:00:22.316836
        Num handles: 1
        Handle: 256
        Count: 1
> ACL Data RX: Handle 256 flags 0x02 dlen 12              #1157 14:00:22.316842
      L2CAP: Disconnection Request (0x06) ident 19 len 4
        Destination CID: 67
        Source CID: 387
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1158 14:00:22.316859
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> ACL Data RX: Handle 256 flags 0x02 dlen 12              #1159 14:00:22.320488
      L2CAP: Disconnection Request (0x06) ident 20 len 4
        Destination CID: 66
        Source CID: 322
> HCI Event: Number of Completed Packets (0x13) plen 5    #1160 14:00:22.322570
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x00 dlen 12              #1161 14:00:22.322603
      L2CAP: Disconnection Response (0x07) ident 19 len 4
        Destination CID: 67
        Source CID: 387
> ACL Data RX: Handle 256 flags 0x02 dlen 8               #1162 14:00:22.322630
      Channel: 64 len 4 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Disconnect (DISC) (0x43)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0x53 poll/final 1
         Length: 0
         FCS: 0x06
> HCI Event: Number of Completed Packets (0x13) plen 5    #1163 14:00:22.329886
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x02 dlen 837             #1164 14:00:22.329940
      Channel: 322 len 833 [PSM 25 mode Basic (0x00)] {chan 2}
> HCI Event: Number of Completed Packets (0x13) plen 5    #1165 14:00:22.335862
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x00 dlen 12              #1166 14:00:22.335916
      L2CAP: Disconnection Response (0x07) ident 20 len 4
        Destination CID: 66
        Source CID: 322
> HCI Event: Number of Completed Packets (0x13) plen 5    #1167 14:00:22.341858
        Num handles: 1
        Handle: 256
        Count: 1
< ACL Data TX: Handle 256 flags 0x00 dlen 8               #1168 14:00:22.341901
      Channel: 192 len 4 [PSM 3 mode Basic (0x00)] {chan 0}
      RFCOMM: Unnumbered Ack (UA) (0x63)
         Address: 0x6b cr 1 dlci 0x1a
         Control: 0x73 poll/final 1
         Length: 0
         FCS: 0x2c
> HCI Event: Number of Completed Packets (0x13) plen 5    #1169 14:00:22.342900
        Num handles: 1
        H

[-- Attachment #4: daemon.log.bad --]
[-- Type: text/plain, Size: 8236 bytes --]

Feb 25 14:16:48 laptop acpid: starting up with netlink and the input layer
Feb 25 14:16:48 laptop acpid: 3 rules loaded
Feb 25 14:16:48 laptop acpid: waiting for events: event logging is off
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/bftpd [file=/etc/xinetd.conf] [line=15]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.d/chargen] [line=11]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/cups-lpd [file=/etc/xinetd.d/cups-lpd] [line=25]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=12]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/ssh [file=/etc/xinetd.d/ssh] [line=25]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/sysstat [file=/etc/xinetd.d/sysstat] [line=14]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=15]
Feb 25 14:16:50 laptop xinetd[1041]: removing chargen
Feb 25 14:16:50 laptop xinetd[1041]: removing chargen
Feb 25 14:16:50 laptop xinetd[1041]: removing printer
Feb 25 14:16:50 laptop xinetd[1041]: removing daytime
Feb 25 14:16:50 laptop xinetd[1041]: removing daytime
Feb 25 14:16:50 laptop xinetd[1041]: removing echo
Feb 25 14:16:50 laptop xinetd[1041]: removing echo
Feb 25 14:16:50 laptop xinetd[1041]: removing systat
Feb 25 14:16:50 laptop xinetd[1041]: removing time
Feb 25 14:16:50 laptop xinetd[1041]: removing time
Feb 25 14:16:50 laptop xinetd[1041]: xinetd Version 2.3.15 started with loadavg options compiled in.
Feb 25 14:16:50 laptop xinetd[1041]: Started working: 2 available services
Feb 25 14:16:50 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.ColorManager' requested by ':1.1' (uid=0 pid=1063 comm="/usr/sbin/cupsd -C /etc/cups/cupsd.conf -s /etc/cu") (using servicehelper)
Feb 25 14:16:50 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Feb 25 14:16:50 laptop bluetoothd[1094]: Bluetooth daemon 5.63
Feb 25 14:16:50 laptop bluetoothd[1094]: Starting SDP server
Feb 25 14:16:50 laptop bluetoothd[1094]: Bluetooth management interface 1.21 initialized
Feb 25 14:16:50 laptop nmbd[1128]: [2022/02/25 14:16:50.693604,  0] ../../source3/nmbd/nmbd.c:901(main) 
Feb 25 14:16:50 laptop nmbd[1128]:   nmbd version 4.15.5 started. 
Feb 25 14:16:50 laptop nmbd[1128]:   Copyright Andrew Tridgell and the Samba Team 1992-2021 
Feb 25 14:16:50 laptop smbd[1148]: [2022/02/25 14:16:50.731684,  0] ../../source3/smbd/server.c:1734(main) 
Feb 25 14:16:50 laptop smbd[1148]:   smbd version 4.15.5 started. 
Feb 25 14:16:50 laptop smbd[1148]:   Copyright Andrew Tridgell and the Samba Team 1992-2021 
Feb 25 14:16:50 laptop smbd[1149]: [2022/02/25 14:16:50.763818,  0] ../../source3/smbd/server.c:1082(smbd_open_one_socket) 
Feb 25 14:16:50 laptop smbd[1149]:   smbd_open_one_socket: open_socket_in failed: Address family not supported by protocol 
Feb 25 14:16:50 laptop smbd[1149]: [2022/02/25 14:16:50.764232,  0] ../../source3/smbd/server.c:1082(smbd_open_one_socket) 
Feb 25 14:16:50 laptop smbd[1149]:   smbd_open_one_socket: open_socket_in failed: Address family not supported by protocol 
Feb 25 14:16:52 laptop bluetoothd[1094]: Loading LTKs timed out for hci0
Feb 25 14:16:54 laptop vnstatd[1356]: vnStat daemon 2.9 started. (pid:1356 uid:0 gid:0 64-bit)
Feb 25 14:16:54 laptop vnstatd[1356]: Monitoring (1): wlan0 (1000 Mbit) 
Feb 25 14:16:54 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.6' (uid=0 pid=1334 comm="/usr/bin/sddm ") (using servicehelper)
Feb 25 14:16:54 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 25 14:16:54 laptop acpid: client connected from 1365[0:0]
Feb 25 14:16:54 laptop acpid: 1 client rule loaded
Feb 25 14:16:54 laptop acpid: client connected from 1365[0:0]
Feb 25 14:16:54 laptop acpid: 1 client rule loaded
Feb 25 14:16:59 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.ConsoleKit' requested by ':1.8' (uid=1000 pid=1423 comm="ck-launch-session lxqt-session ") (using servicehelper)
Feb 25 14:16:59 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.9' (uid=0 pid=1454 comm="/usr/sbin/console-kit-daemon --no-daemon ") (using servicehelper)
Feb 25 14:16:59 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Feb 25 14:16:59 laptop polkitd[1460]: Started polkitd version 0.120
Feb 25 14:16:59 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 25 14:16:59 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Activating service name='org.kde.KScreen' requested by ':1.1' (uid=1000 pid=1512 comm="/usr/bin/lxqt-config-monitor -l ")
Feb 25 14:16:59 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Successfully activated service 'org.kde.KScreen'
Feb 25 14:16:59 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Activating service name='org.gtk.vfs.Daemon' requested by ':1.4' (uid=1000 pid=1516 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 14:16:59 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Successfully activated service 'org.gtk.vfs.Daemon'
Feb 25 14:16:59 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.4' (uid=1000 pid=1516 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 14:16:59 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.UDisks2' requested by ':1.26' (uid=1000 pid=1618 comm="/usr/libexec/gvfs-udisks2-volume-monitor ") (using servicehelper)
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Feb 25 14:17:00 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Activating service name='org.a11y.Bus' requested by ':1.21' (uid=1000 pid=1663 comm="/usr/bin/python3 /usr/bin/blueman-applet ")
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Successfully activated service 'org.a11y.Bus'
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Activating service name='org.gtk.vfs.GPhoto2VolumeMonitor' requested by ':1.4' (uid=1000 pid=1516 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Activating service name='org.gtk.vfs.MTPVolumeMonitor' requested by ':1.4' (uid=1000 pid=1516 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'

[-- Attachment #5: daemon.log.good --]
[-- Type: text/plain, Size: 9341 bytes --]

Feb 25 13:58:19 laptop acpid: starting up with netlink and the input layer
Feb 25 13:58:19 laptop acpid: 3 rules loaded
Feb 25 13:58:19 laptop acpid: waiting for events: event logging is off
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/bftpd [file=/etc/xinetd.conf] [line=15]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.d/chargen] [line=11]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/cups-lpd [file=/etc/xinetd.d/cups-lpd] [line=25]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=12]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/ssh [file=/etc/xinetd.d/ssh] [line=25]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/sysstat [file=/etc/xinetd.d/sysstat] [line=14]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=15]
Feb 25 13:58:21 laptop xinetd[1042]: removing chargen
Feb 25 13:58:21 laptop xinetd[1042]: removing chargen
Feb 25 13:58:21 laptop xinetd[1042]: removing printer
Feb 25 13:58:21 laptop xinetd[1042]: removing daytime
Feb 25 13:58:21 laptop xinetd[1042]: removing daytime
Feb 25 13:58:21 laptop xinetd[1042]: removing echo
Feb 25 13:58:21 laptop xinetd[1042]: removing echo
Feb 25 13:58:21 laptop xinetd[1042]: removing systat
Feb 25 13:58:21 laptop xinetd[1042]: removing time
Feb 25 13:58:21 laptop xinetd[1042]: removing time
Feb 25 13:58:21 laptop xinetd[1042]: xinetd Version 2.3.15 started with loadavg options compiled in.
Feb 25 13:58:21 laptop xinetd[1042]: Started working: 2 available services
Feb 25 13:58:21 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.ColorManager' requested by ':1.1' (uid=0 pid=1064 comm="/usr/sbin/cupsd -C /etc/cups/cupsd.conf -s /etc/cu") (using servicehelper)
Feb 25 13:58:21 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Feb 25 13:58:21 laptop bluetoothd[1095]: Bluetooth daemon 5.63
Feb 25 13:58:21 laptop bluetoothd[1095]: Starting SDP server
Feb 25 13:58:21 laptop bluetoothd[1095]: Bluetooth management interface 1.21 initialized
Feb 25 13:58:21 laptop bluetoothd[1095]: Failed to set privacy: Rejected (0x0b)
Feb 25 13:58:21 laptop nmbd[1130]: [2022/02/25 13:58:21.693041,  0] ../../source3/nmbd/nmbd.c:901(main) 
Feb 25 13:58:21 laptop nmbd[1130]:   nmbd version 4.15.5 started. 
Feb 25 13:58:21 laptop nmbd[1130]:   Copyright Andrew Tridgell and the Samba Team 1992-2021 
Feb 25 13:58:21 laptop nmbd[1131]: [2022/02/25 13:58:21.712491,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response) 
Feb 25 13:58:21 laptop nmbd[1131]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.10 for name HOMENET<1d>. 
Feb 25 13:58:21 laptop nmbd[1131]:   This response was from IP 192.168.1.50, reporting an IP address of 192.168.1.50. 
Feb 25 13:58:21 laptop smbd[1150]: [2022/02/25 13:58:21.731786,  0] ../../source3/smbd/server.c:1734(main) 
Feb 25 13:58:21 laptop smbd[1150]:   smbd version 4.15.5 started. 
Feb 25 13:58:21 laptop smbd[1150]:   Copyright Andrew Tridgell and the Samba Team 1992-2021 
Feb 25 13:58:21 laptop smbd[1151]: [2022/02/25 13:58:21.764778,  0] ../../source3/smbd/server.c:1082(smbd_open_one_socket) 
Feb 25 13:58:21 laptop smbd[1151]:   smbd_open_one_socket: open_socket_in failed: Address family not supported by protocol 
Feb 25 13:58:21 laptop smbd[1151]: [2022/02/25 13:58:21.765160,  0] ../../source3/smbd/server.c:1082(smbd_open_one_socket) 
Feb 25 13:58:21 laptop smbd[1151]:   smbd_open_one_socket: open_socket_in failed: Address family not supported by protocol 
Feb 25 13:58:25 laptop vnstatd[1358]: vnStat daemon 2.9 started. (pid:1358 uid:0 gid:0 64-bit)
Feb 25 13:58:25 laptop vnstatd[1358]: Monitoring (1): wlan0 (1000 Mbit) 
Feb 25 13:58:25 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.6' (uid=0 pid=1336 comm="/usr/bin/sddm ") (using servicehelper)
Feb 25 13:58:25 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 25 13:58:25 laptop acpid: client connected from 1367[0:0]
Feb 25 13:58:25 laptop acpid: 1 client rule loaded
Feb 25 13:58:25 laptop acpid: client connected from 1367[0:0]
Feb 25 13:58:25 laptop acpid: 1 client rule loaded
Feb 25 13:58:32 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.ConsoleKit' requested by ':1.8' (uid=1000 pid=1424 comm="ck-launch-session lxqt-session ") (using servicehelper)
Feb 25 13:58:32 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.9' (uid=0 pid=1455 comm="/usr/sbin/console-kit-daemon --no-daemon ") (using servicehelper)
Feb 25 13:58:32 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Feb 25 13:58:32 laptop polkitd[1461]: Started polkitd version 0.120
Feb 25 13:58:32 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 25 13:58:32 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Activating service name='org.kde.KScreen' requested by ':1.1' (uid=1000 pid=1513 comm="/usr/bin/lxqt-config-monitor -l ")
Feb 25 13:58:32 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Successfully activated service 'org.kde.KScreen'
Feb 25 13:58:32 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Activating service name='org.gtk.vfs.Daemon' requested by ':1.3' (uid=1000 pid=1517 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 13:58:32 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Successfully activated service 'org.gtk.vfs.Daemon'
Feb 25 13:58:32 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.3' (uid=1000 pid=1517 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 13:58:32 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.UDisks2' requested by ':1.33' (uid=1000 pid=1619 comm="/usr/libexec/gvfs-udisks2-volume-monitor ") (using servicehelper)
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Feb 25 13:58:33 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Activating service name='org.a11y.Bus' requested by ':1.20' (uid=1000 pid=1655 comm="/usr/bin/python3 /usr/bin/blueman-applet ")
Feb 25 13:58:33 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Successfully activated service 'org.a11y.Bus'
Feb 25 13:58:34 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 25 13:58:34 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Feb 25 13:58:34 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Activating service name='org.gtk.vfs.GPhoto2VolumeMonitor' requested by ':1.3' (uid=1000 pid=1517 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 13:58:34 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Feb 25 13:58:34 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Activating service name='org.gtk.vfs.MTPVolumeMonitor' requested by ':1.3' (uid=1000 pid=1517 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 13:58:34 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Feb 25 14:00:15 laptop bluetoothd[1095]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:08:4C:FA:B0:47: Device or resource busy
Feb 25 14:00:15 laptop bluetoothd[1095]: /org/bluez/hci0/dev_00_08_4C_FA_B0_47/sep1/fd0: fd(28) ready
Feb 25 14:00:15 laptop bluetoothd[1095]: profiles/audio/avctp.c:uinput_create() Can't open input device: No such file or directory (2)
Feb 25 14:00:15 laptop bluetoothd[1095]: profiles/audio/avctp.c:init_uinput() AVRCP: failed to init uinput for Anker MP140
Feb 25 14:00:22 laptop bluetoothd[1095]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)

[-- Attachment #6: kern.log.bad --]
[-- Type: text/plain, Size: 67366 bytes --]

Feb 25 14:16:48 laptop kernel: klogd 1.5.1, log source = /proc/kmsg started.
Feb 25 14:16:48 laptop kernel: Inspecting /boot/System.map-5.16.0-rc5+
Feb 25 14:16:48 laptop kernel: Cannot find map file.
Feb 25 14:16:48 laptop kernel: Loaded 48003 symbols from 47 modules.
Feb 25 14:16:48 laptop kernel: microcode: microcode updated early to revision 0xea, date = 2021-02-07
Feb 25 14:16:48 laptop kernel: Linux version 5.16.0-rc5+ (chris@laptop) (gcc (GCC) 11.2.1 20220219, GNU ld (GNU Binutils) 2.38) #907 SMP PREEMPT Fri Feb 25 11:29:24 GMT 2022
Feb 25 14:16:48 laptop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+ ro root=PARTUUID=f927883a-e95c-4cdd-b64e-a0a778216b9f resume=PARTUUID=70ccedc5-d788-42bc-9f13-81e2beb61338 apm=power_off rootfstype=ext4 net.ifnames=0
Feb 25 14:16:48 laptop kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Feb 25 14:16:48 laptop kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Feb 25 14:16:48 laptop kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Feb 25 14:16:48 laptop kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Feb 25 14:16:48 laptop kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Feb 25 14:16:48 laptop kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Feb 25 14:16:48 laptop kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Feb 25 14:16:48 laptop kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Feb 25 14:16:48 laptop kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Feb 25 14:16:48 laptop kernel: x86/fpu: xstate_offset[9]:  960, xstate_sizes[9]:    8
Feb 25 14:16:48 laptop kernel: x86/fpu: Enabled xstate features 0x21f, context size is 968 bytes, using 'compacted' format.
Feb 25 14:16:48 laptop kernel: signal: max sigframe size: 3632
Feb 25 14:16:48 laptop kernel: BIOS-provided physical RAM map:
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007e1d8fff] usable
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000007e1d9000-0x000000007ead8fff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000007ead9000-0x000000008cceefff] usable
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000008ccef000-0x000000008d0befff] type 20
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000008d0bf000-0x000000008eedefff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000008eedf000-0x000000008fbcefff] ACPI NVS
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000008fbcf000-0x000000008fc4efff] ACPI data
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000008fc4f000-0x000000008fc4ffff] usable
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000008fc50000-0x000000009d7fffff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x00000000ff400000-0x00000000ffffffff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008607fffff] usable
Feb 25 14:16:48 laptop kernel: NX (Execute Disable) protection: active
Feb 25 14:16:48 laptop kernel: efi: EFI v2.70 by INSYDE Corp.
Feb 25 14:16:48 laptop kernel: efi: ACPI=0x8fc4e000 ACPI 2.0=0x8fc4e014 TPMFinalLog=0x8fbc5000 SMBIOS=0x8d1e4000 SMBIOS 3.0=0x8d1e2000 ESRT=0x8d1e5998 MEMATTR=0x79ea3018 
Feb 25 14:16:48 laptop kernel: SMBIOS 3.2.0 present.
Feb 25 14:16:48 laptop kernel: DMI: Notebook                         NP50DE_DB                       /NP50DE_DB                       , BIOS 1.07.04 02/17/2020
Feb 25 14:16:48 laptop kernel: tsc: Detected 2600.000 MHz processor
Feb 25 14:16:48 laptop kernel: tsc: Detected 2599.992 MHz TSC
Feb 25 14:16:48 laptop kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 25 14:16:48 laptop kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 25 14:16:48 laptop kernel: last_pfn = 0x860800 max_arch_pfn = 0x400000000
Feb 25 14:16:48 laptop kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Feb 25 14:16:48 laptop kernel: last_pfn = 0x8fc50 max_arch_pfn = 0x400000000
Feb 25 14:16:48 laptop kernel: esrt: Reserving ESRT space from 0x000000008d1e5998 to 0x000000008d1e5a48.
Feb 25 14:16:48 laptop kernel: Using GB pages for direct mapping
Feb 25 14:16:48 laptop kernel: Secure boot disabled
Feb 25 14:16:48 laptop kernel: RAMDISK: [mem 0x37fc1000-0x37fd7fff]
Feb 25 14:16:48 laptop kernel: ACPI: Early table checksum verification disabled
Feb 25 14:16:48 laptop kernel: ACPI: RSDP 0x000000008FC4E014 000024 (v02 INSYDE)
Feb 25 14:16:48 laptop kernel: ACPI: XSDT 0x000000008FBF9188 0000DC (v01 INSYDE CML      00000002      01000013)
Feb 25 14:16:48 laptop kernel: ACPI: FACP 0x000000008FC37000 00010C (v05 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: DSDT 0x000000008FC00000 03337F (v02 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: FACS 0x000000008FB47000 000040
Feb 25 14:16:48 laptop kernel: ACPI: UEFI 0x000000008FBCE000 000236 (v01 INSYDE CML      00000001 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC4A000 002087 (v02 CpuRef CpuSsdt  00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC46000 003158 (v02 SaSsdt SaSsdt   00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC44000 001848 (v02 PegSsd PegSsdt  00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC43000 000790 (v02 INSYDE Tpm2Tabl 00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: TPM2 0x000000008FC42000 000034 (v04 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: LPIT 0x000000008FC40000 000094 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: WSMT 0x000000008FC3F000 000028 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC3D000 001616 (v02 INSYDE PtidDevc 00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: DBGP 0x000000008FC3C000 000034 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: DBG2 0x000000008FC3B000 00005C (v00 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC3A000 000502 (v02 Intel  PerfTune 00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: NHLT 0x000000008FC38000 001821 (v00 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: HPET 0x000000008FC36000 000038 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: APIC 0x000000008FC35000 000164 (v03 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: MCFG 0x000000008FC34000 00003C (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FBFF000 000E58 (v02 INSYDE ClevoRTD 00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FBFA000 0039F7 (v01 Insyde NvdTable 00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC4D000 000164 (v01 INSYDE PcdTabl  00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: DMAR 0x000000008FBFE000 0000A8 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: FPDT 0x000000008FBF8000 000044 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: BGRT 0x000000008FBF7000 000038 (v01 INSYDE CML      00000001 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: Reserving FACP table memory at [mem 0x8fc37000-0x8fc3710b]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving DSDT table memory at [mem 0x8fc00000-0x8fc3337e]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving FACS table memory at [mem 0x8fb47000-0x8fb4703f]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving UEFI table memory at [mem 0x8fbce000-0x8fbce235]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc4a000-0x8fc4c086]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc46000-0x8fc49157]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc44000-0x8fc45847]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc43000-0x8fc4378f]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving TPM2 table memory at [mem 0x8fc42000-0x8fc42033]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving LPIT table memory at [mem 0x8fc40000-0x8fc40093]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving WSMT table memory at [mem 0x8fc3f000-0x8fc3f027]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc3d000-0x8fc3e615]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving DBGP table memory at [mem 0x8fc3c000-0x8fc3c033]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving DBG2 table memory at [mem 0x8fc3b000-0x8fc3b05b]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc3a000-0x8fc3a501]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving NHLT table memory at [mem 0x8fc38000-0x8fc39820]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving HPET table memory at [mem 0x8fc36000-0x8fc36037]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving APIC table memory at [mem 0x8fc35000-0x8fc35163]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving MCFG table memory at [mem 0x8fc34000-0x8fc3403b]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fbff000-0x8fbffe57]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fbfa000-0x8fbfd9f6]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc4d000-0x8fc4d163]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving DMAR table memory at [mem 0x8fbfe000-0x8fbfe0a7]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving FPDT table memory at [mem 0x8fbf8000-0x8fbf8043]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving BGRT table memory at [mem 0x8fbf7000-0x8fbf7037]
Feb 25 14:16:48 laptop kernel: Zone ranges:
Feb 25 14:16:48 laptop kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 25 14:16:48 laptop kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 25 14:16:48 laptop kernel:   Normal   [mem 0x0000000100000000-0x00000008607fffff]
Feb 25 14:16:48 laptop kernel: Movable zone start for each node
Feb 25 14:16:48 laptop kernel: Early memory node ranges
Feb 25 14:16:48 laptop kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 25 14:16:48 laptop kernel:   node   0: [mem 0x0000000000100000-0x000000007e1d8fff]
Feb 25 14:16:48 laptop kernel:   node   0: [mem 0x000000007ead9000-0x000000008cceefff]
Feb 25 14:16:48 laptop kernel:   node   0: [mem 0x000000008fc4f000-0x000000008fc4ffff]
Feb 25 14:16:48 laptop kernel:   node   0: [mem 0x0000000100000000-0x00000008607fffff]
Feb 25 14:16:48 laptop kernel: Initmem setup node 0 [mem 0x0000000000001000-0x00000008607fffff]
Feb 25 14:16:48 laptop kernel: On node 0, zone DMA: 1 pages in unavailable ranges
Feb 25 14:16:48 laptop kernel: On node 0, zone DMA: 97 pages in unavailable ranges
Feb 25 14:16:48 laptop kernel: On node 0, zone DMA32: 2304 pages in unavailable ranges
Feb 25 14:16:48 laptop kernel: On node 0, zone DMA32: 12128 pages in unavailable ranges
Feb 25 14:16:48 laptop kernel: On node 0, zone Normal: 944 pages in unavailable ranges
Feb 25 14:16:48 laptop kernel: On node 0, zone Normal: 30720 pages in unavailable ranges
Feb 25 14:16:48 laptop kernel: Reserving Intel graphics memory at [mem 0x99800000-0x9d7fffff]
Feb 25 14:16:48 laptop kernel: ACPI: PM-Timer IO Port: 0x1808
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x14] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
Feb 25 14:16:48 laptop kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 25 14:16:48 laptop kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 25 14:16:48 laptop kernel: ACPI: Using ACPI (MADT) for SMP configuration information
Feb 25 14:16:48 laptop kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
Feb 25 14:16:48 laptop kernel: TSC deadline timer available
Feb 25 14:16:48 laptop kernel: smpboot: Allowing 12 CPUs, 0 hotplug CPUs
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x000fffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x7e1d9000-0x7ead8fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8ccef000-0x8d0befff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8d0bf000-0x8eedefff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8eedf000-0x8fbcefff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8fbcf000-0x8fc4efff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8fc50000-0x9d7fffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x9d800000-0xdfffffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xefffffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xf0000000-0xfdffffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfe000000-0xfe010fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfe011000-0xfed0ffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed10000-0xfed19fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed1a000-0xfed83fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed84000-0xfed84fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed85000-0xfedfffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xff3fffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xff400000-0xffffffff]
Feb 25 14:16:48 laptop kernel: [mem 0x9d800000-0xdfffffff] available for PCI devices
Feb 25 14:16:48 laptop kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 25 14:16:48 laptop kernel: setup_percpu: NR_CPUS:12 nr_cpumask_bits:12 nr_cpu_ids:12 nr_node_ids:1
Feb 25 14:16:48 laptop kernel: percpu: Embedded 44 pages/cpu s140440 r8192 d31592 u262144
Feb 25 14:16:48 laptop kernel: pcpu-alloc: s140440 r8192 d31592 u262144 alloc=1*2097152
Feb 25 14:16:48 laptop kernel: pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 -- -- -- -- 
Feb 25 14:16:48 laptop kernel: Built 1 zonelists, mobility grouping on.  Total pages: 8179648
Feb 25 14:16:48 laptop kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+ ro root=PARTUUID=f927883a-e95c-4cdd-b64e-a0a778216b9f resume=PARTUUID=70ccedc5-d788-42bc-9f13-81e2beb61338 apm=power_off rootfstype=ext4 net.ifnames=0
Feb 25 14:16:48 laptop kernel: Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+ apm=power_off", will be passed to user space.
Feb 25 14:16:48 laptop kernel: Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
Feb 25 14:16:48 laptop kernel: Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
Feb 25 14:16:48 laptop kernel: mem auto-init: stack:off, heap alloc:off, heap free:off
Feb 25 14:16:48 laptop kernel: Memory: 32517468K/33238584K available (10242K kernel code, 1120K rwdata, 2548K rodata, 1008K init, 892K bss, 720856K reserved, 0K cma-reserved)
Feb 25 14:16:48 laptop kernel: random: get_random_u64 called from __kmem_cache_create+0x1f/0x470 with crng_init=0
Feb 25 14:16:48 laptop kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=12, Nodes=1
Feb 25 14:16:48 laptop kernel: Dynamic Preempt: full
Feb 25 14:16:48 laptop kernel: rcu: Preemptible hierarchical RCU implementation.
Feb 25 14:16:48 laptop kernel: rcu: ^IRCU event tracing is enabled.
Feb 25 14:16:48 laptop kernel: ^ITrampoline variant of Tasks RCU enabled.
Feb 25 14:16:48 laptop kernel: rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
Feb 25 14:16:48 laptop kernel: NR_IRQS: 4352, nr_irqs: 2152, preallocated irqs: 16
Feb 25 14:16:48 laptop kernel: Console: colour dummy device 80x25
Feb 25 14:16:48 laptop kernel: printk: console [tty0] enabled
Feb 25 14:16:48 laptop kernel: ACPI: Core revision 20210930
Feb 25 14:16:48 laptop kernel: hpet: HPET dysfunctional in PC10. Force disabled.
Feb 25 14:16:48 laptop kernel: APIC: Switch to symmetric I/O mode setup
Feb 25 14:16:48 laptop kernel: Switched APIC routing to physical flat.
Feb 25 14:16:48 laptop kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x257a34a6eea, max_idle_ns: 440795264358 ns
Feb 25 14:16:48 laptop kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5199.98 BogoMIPS (lpj=10399968)
Feb 25 14:16:48 laptop kernel: pid_max: default: 32768 minimum: 301
Feb 25 14:16:48 laptop kernel: Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Feb 25 14:16:48 laptop kernel: Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Feb 25 14:16:48 laptop kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 25 14:16:48 laptop kernel: process: using mwait in idle threads
Feb 25 14:16:48 laptop kernel: Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
Feb 25 14:16:48 laptop kernel: Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
Feb 25 14:16:48 laptop kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
Feb 25 14:16:48 laptop kernel: Spectre V2 : Mitigation: Enhanced IBRS
Feb 25 14:16:48 laptop kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
Feb 25 14:16:48 laptop kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
Feb 25 14:16:48 laptop kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
Feb 25 14:16:48 laptop kernel: Freeing SMP alternatives memory: 28K
Feb 25 14:16:48 laptop kernel: smpboot: Estimated ratio of average max frequency by base frequency (times 1024): 1811
Feb 25 14:16:48 laptop kernel: smpboot: CPU0: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (family: 0x6, model: 0xa5, stepping: 0x2)
Feb 25 14:16:48 laptop kernel: Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
Feb 25 14:16:48 laptop kernel: ... version:                4
Feb 25 14:16:48 laptop kernel: ... bit width:              48
Feb 25 14:16:48 laptop kernel: ... generic registers:      4
Feb 25 14:16:48 laptop kernel: ... value mask:             0000ffffffffffff
Feb 25 14:16:48 laptop kernel: ... max period:             00007fffffffffff
Feb 25 14:16:48 laptop kernel: ... fixed-purpose events:   3
Feb 25 14:16:48 laptop kernel: ... event mask:             000000070000000f
Feb 25 14:16:48 laptop kernel: rcu: Hierarchical SRCU implementation.
Feb 25 14:16:48 laptop kernel: smp: Bringing up secondary CPUs ...
Feb 25 14:16:48 laptop kernel: x86: Booting SMP configuration:
Feb 25 14:16:48 laptop kernel: .... node  #0, CPUs:        #1  #2  #3  #4  #5  #6  #7  #8  #9 #10 #11
Feb 25 14:16:48 laptop kernel: smp: Brought up 1 node, 12 CPUs
Feb 25 14:16:48 laptop kernel: smpboot: Max logical packages: 1
Feb 25 14:16:48 laptop kernel: smpboot: Total of 12 processors activated (62399.80 BogoMIPS)
Feb 25 14:16:48 laptop kernel: devtmpfs: initialized
Feb 25 14:16:48 laptop kernel: ACPI: PM: Registering ACPI NVS region [mem 0x8eedf000-0x8fbcefff] (13565952 bytes)
Feb 25 14:16:48 laptop kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 25 14:16:48 laptop kernel: futex hash table entries: 4096 (order: 6, 262144 bytes, linear)
Feb 25 14:16:48 laptop kernel: NET: Registered PF_NETLINK/PF_ROUTE protocol family
Feb 25 14:16:48 laptop kernel: thermal_sys: Registered thermal governor 'step_wise'
Feb 25 14:16:48 laptop kernel: thermal_sys: Registered thermal governor 'user_space'
Feb 25 14:16:48 laptop kernel: cpuidle: using governor ladder
Feb 25 14:16:48 laptop kernel: cpuidle: using governor menu
Feb 25 14:16:48 laptop kernel: PCI: Using configuration type 1 for base access
Feb 25 14:16:48 laptop kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 25 14:16:48 laptop kernel: cryptd: max_cpu_qlen set to 1000
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(Module Device)
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(Processor Device)
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(Linux-Dell-Video)
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
Feb 25 14:16:48 laptop kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.XDCI], AE_NOT_FOUND (20210930/dswload2-162)
Feb 25 14:16:48 laptop kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210930/psobject-220)
Feb 25 14:16:48 laptop kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0010)
Feb 25 14:16:48 laptop kernel: ACPI: 10 ACPI AML tables successfully acquired and loaded
Feb 25 14:16:48 laptop kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF8939000F3300 0000FC (v02 PmRef  Cpu0Psd  00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: \_SB_.PR00: _OSC native thermal LVT Acked
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF893900CC0800 000400 (v02 PmRef  Cpu0Cst  00003001 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF893900CBA800 000581 (v02 PmRef  Cpu0Ist  00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF89390014B400 000137 (v02 PmRef  Cpu0Hwp  00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF89390006C000 000BEA (v02 PmRef  HwpLvt   00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF893900CBC000 000778 (v02 PmRef  ApIst    00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF893900CC0C00 0003D7 (v02 PmRef  ApHwp    00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF89390006D000 000D22 (v02 PmRef  ApPsd    00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF893900CC1000 0003CA (v02 PmRef  ApCst    00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: EC: EC started
Feb 25 14:16:48 laptop kernel: ACPI: EC: interrupt blocked
Feb 25 14:16:48 laptop kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
Feb 25 14:16:48 laptop kernel: ACPI: \_SB_.PCI0.LPCB.EC__: Boot DSDT EC used to handle transactions
Feb 25 14:16:48 laptop kernel: ACPI: Interpreter enabled
Feb 25 14:16:48 laptop kernel: ACPI: PM: (supports S0 S3 S4 S5)
Feb 25 14:16:48 laptop kernel: ACPI: Using IOAPIC for interrupt routing
Feb 25 14:16:48 laptop kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 25 14:16:48 laptop kernel: ACPI: Enabled 7 GPEs in block 00 to 7F
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [PG00]
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [BTPR]
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [V0PR]
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [V1PR]
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [V2PR]
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [WRST]
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [PIN]
Feb 25 14:16:48 laptop kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
Feb 25 14:16:48 laptop kernel: acpi PNP0A08:00: _OSC: OS supports [ASPM ClockPM Segments MSI HPX-Type3]
Feb 25 14:16:48 laptop kernel: acpi PNP0A08:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI]
Feb 25 14:16:48 laptop kernel: PCI host bridge to bus 0000:00
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: root bus resource [mem 0x9d800000-0xdfffffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: root bus resource [mem 0xfc800000-0xfe7fffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: root bus resource [bus 00-fe]
Feb 25 14:16:48 laptop kernel: pci 0000:00:00.0: [8086:9b54] type 00 class 0x060000
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0: [8086:1901] type 01 class 0x060400
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: [8086:9bc4] type 00 class 0x030000
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: reg 0x10: [mem 0xc2000000-0xc2ffffff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: reg 0x18: [mem 0xa0000000-0xafffffff 64bit pref]
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: reg 0x20: [io  0x5000-0x503f]
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: BAR 2: assigned to efifb
Feb 25 14:16:48 laptop kernel: pci 0000:00:12.0: [8086:06f9] type 00 class 0x118000
Feb 25 14:16:48 laptop kernel: pci 0000:00:12.0: reg 0x10: [mem 0xc539c000-0xc539cfff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.0: [8086:06ed] type 00 class 0x0c0330
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.0: reg 0x10: [mem 0xc5380000-0xc538ffff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.2: [8086:06ef] type 00 class 0x050000
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.2: reg 0x10: [mem 0xc5398000-0xc5399fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.2: reg 0x18: [mem 0xc539d000-0xc539dfff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.3: [8086:06f0] type 00 class 0x028000
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.3: reg 0x10: [mem 0xc5390000-0xc5393fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.3: PME# supported from D0 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:15.0: [8086:06e8] type 00 class 0x0c8000
Feb 25 14:16:48 laptop kernel: pci 0000:00:15.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:15.1: [8086:06e9] type 00 class 0x0c8000
Feb 25 14:16:48 laptop kernel: pci 0000:00:15.1: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:16.0: [8086:06e0] type 00 class 0x078000
Feb 25 14:16:48 laptop kernel: pci 0000:00:16.0: reg 0x10: [mem 0xc53a0000-0xc53a0fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:16.0: PME# supported from D3hot
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: [8086:06d3] type 00 class 0x010601
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: reg 0x10: [mem 0xc539a000-0xc539bfff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: reg 0x14: [mem 0xc53a4000-0xc53a40ff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: reg 0x18: [io  0x5080-0x5087]
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: reg 0x1c: [io  0x5088-0x508b]
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: reg 0x20: [io  0x5060-0x507f]
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: reg 0x24: [mem 0xc53a3000-0xc53a37ff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: PME# supported from D3hot
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.0: [8086:06b0] type 01 class 0x060400
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.5: [8086:06b5] type 01 class 0x060400
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.5: PME# supported from D0 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6: [8086:06b6] type 01 class 0x060400
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6: PME# supported from D0 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.0: [8086:068d] type 00 class 0x060100
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.3: [8086:06c8] type 00 class 0x040300
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xc5394000-0xc5397fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.3: reg 0x20: [mem 0xc5000000-0xc50fffff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.3: PME# supported from D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.4: [8086:06a3] type 00 class 0x0c0500
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.4: reg 0x10: [mem 0xc53a1000-0xc53a10ff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.4: reg 0x20: [io  0xefa0-0xefbf]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.5: [8086:06a4] type 00 class 0x0c8000
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.5: reg 0x10: [mem 0xfe010000-0xfe010fff]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: [10de:1f95] type 00 class 0x030000
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: reg 0x10: [mem 0xc4000000-0xc4ffffff]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: reg 0x14: [mem 0xb0000000-0xbfffffff 64bit pref]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xc0000000-0xc1ffffff 64bit pref]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: reg 0x24: [io  0x4000-0x407f]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfff80000-0xffffffff pref]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: Enabling HDA controller
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: 63.008 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x8 link at 0000:00:01.0 (capable of 126.016 Gb/s with 8.0 GT/s PCIe x16 link)
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0: PCI bridge to [bus 01-05]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0:   bridge window [io  0x4000-0x4fff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xc3000000-0xc4ffffff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xb0000000-0xc1ffffff 64bit pref]
Feb 25 14:16:48 laptop kernel: pci 0000:06:00.0: [15b7:5009] type 00 class 0x010802
Feb 25 14:16:48 laptop kernel: pci 0000:06:00.0: reg 0x10: [mem 0xc5200000-0xc5203fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:06:00.0: reg 0x20: [mem 0xc5204000-0xc52040ff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.0: PCI bridge to [bus 06]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.0:   bridge window [mem 0xc5200000-0xc52fffff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.5: PCI bridge to [bus 07]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.0: [10ec:5287] type 00 class 0xff0000
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.0: reg 0x10: [mem 0xc5105000-0xc5105fff]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.0: supports D1 D2
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.0: PME# supported from D1 D2 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.1: [10ec:8168] type 00 class 0x020000
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.1: reg 0x10: [io  0x3000-0x30ff]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.1: reg 0x18: [mem 0xc5104000-0xc5104fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.1: reg 0x20: [mem 0xc5100000-0xc5103fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.1: supports D1 D2
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.1: PME# supported from D0 D1 D2 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6: PCI bridge to [bus 08]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6:   bridge window [io  0x3000-0x3fff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6:   bridge window [mem 0xc5100000-0xc51fffff]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: on NUMA node 0
Feb 25 14:16:48 laptop kernel: ACPI: EC: interrupt unblocked
Feb 25 14:16:48 laptop kernel: ACPI: EC: event unblocked
Feb 25 14:16:48 laptop kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
Feb 25 14:16:48 laptop kernel: ACPI: EC: GPE=0x3
Feb 25 14:16:48 laptop kernel: ACPI: \_SB_.PCI0.LPCB.EC__: Boot DSDT EC initialization complete
Feb 25 14:16:48 laptop kernel: ACPI: \_SB_.PCI0.LPCB.EC__: EC: Used to handle transactions and events
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: vgaarb: no bridge control possible
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: vgaarb: bridge control possible
Feb 25 14:16:48 laptop kernel: vgaarb: loaded
Feb 25 14:16:48 laptop kernel: SCSI subsystem initialized
Feb 25 14:16:48 laptop kernel: libata version 3.00 loaded.
Feb 25 14:16:48 laptop kernel: ACPI: bus type USB registered
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver usbfs
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver hub
Feb 25 14:16:48 laptop kernel: usbcore: registered new device driver usb
Feb 25 14:16:48 laptop kernel: mc: Linux media interface: v0.10
Feb 25 14:16:48 laptop kernel: videodev: Linux video capture interface: v2.00
Feb 25 14:16:48 laptop kernel: Registered efivars operations
Feb 25 14:16:48 laptop kernel: Advanced Linux Sound Architecture Driver Initialized.
Feb 25 14:16:48 laptop kernel: Bluetooth: Core ver 2.22
Feb 25 14:16:48 laptop kernel: NET: Registered PF_BLUETOOTH protocol family
Feb 25 14:16:48 laptop kernel: Bluetooth: HCI device and connection manager initialized
Feb 25 14:16:48 laptop kernel: Bluetooth: HCI socket layer initialized
Feb 25 14:16:48 laptop kernel: Bluetooth: L2CAP socket layer initialized
Feb 25 14:16:48 laptop kernel: Bluetooth: SCO socket layer initialized
Feb 25 14:16:48 laptop kernel: PCI: Using ACPI for IRQ routing
Feb 25 14:16:48 laptop kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 25 14:16:48 laptop kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 25 14:16:48 laptop kernel: e820: reserve RAM buffer [mem 0x7e1d9000-0x7fffffff]
Feb 25 14:16:48 laptop kernel: e820: reserve RAM buffer [mem 0x8ccef000-0x8fffffff]
Feb 25 14:16:48 laptop kernel: e820: reserve RAM buffer [mem 0x8fc50000-0x8fffffff]
Feb 25 14:16:48 laptop kernel: e820: reserve RAM buffer [mem 0x860800000-0x863ffffff]
Feb 25 14:16:48 laptop kernel: clocksource: Switched to clocksource tsc-early
Feb 25 14:16:48 laptop kernel: pnp: PnP ACPI init
Feb 25 14:16:48 laptop kernel: system 00:00: [mem 0x40000000-0x403fffff] could not be reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [io  0x1800-0x18fe] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [mem 0xfd000000-0xfd69ffff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [mem 0xfd6c0000-0xfd6cffff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [mem 0xfd6f0000-0xfdffffff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [mem 0xfe000000-0xfe01ffff] could not be reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [mem 0xfe200000-0xfe7fffff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [mem 0xff000000-0xffffffff] could not be reserved
Feb 25 14:16:48 laptop kernel: system 00:02: [io  0x2000-0x20fe] has been reserved
Feb 25 14:16:48 laptop kernel: pnp 00:03: disabling [io  0x3322-0x3323] because it overlaps 0000:00:1d.6 BAR 7 [io  0x3000-0x3fff]
Feb 25 14:16:48 laptop kernel: system 00:03: [io  0x0680-0x069f] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:03: [io  0x164e-0x164f] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:05: [io  0x1854-0x1857] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xe0000000-0xefffffff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfed45000-0xfed8ffff] could not be reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 25 14:16:48 laptop kernel: system 00:09: [mem 0xfe038000-0xfe038fff] has been reserved
Feb 25 14:16:48 laptop kernel: pnp: PnP ACPI: found 10 devices
Feb 25 14:16:48 laptop kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 25 14:16:48 laptop kernel: NET: Registered PF_INET protocol family
Feb 25 14:16:48 laptop kernel: IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Feb 25 14:16:48 laptop kernel: tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)
Feb 25 14:16:48 laptop kernel: TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Feb 25 14:16:48 laptop kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
Feb 25 14:16:48 laptop kernel: TCP: Hash tables configured (established 262144 bind 65536)
Feb 25 14:16:48 laptop kernel: UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)
Feb 25 14:16:48 laptop kernel: UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)
Feb 25 14:16:48 laptop kernel: NET: Registered PF_UNIX/PF_LOCAL protocol family
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: can't claim BAR 6 [mem 0xfff80000-0xffffffff pref]: no compatible bridge window
Feb 25 14:16:48 laptop kernel: pci 0000:00:15.0: BAR 0: assigned [mem 0x9d800000-0x9d800fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:15.1: BAR 0: assigned [mem 0x9d801000-0x9d801fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xc3000000-0xc307ffff pref]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0: PCI bridge to [bus 01-05]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0:   bridge window [io  0x4000-0x4fff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xc3000000-0xc4ffffff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xb0000000-0xc1ffffff 64bit pref]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.0: PCI bridge to [bus 06]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.0:   bridge window [mem 0xc5200000-0xc52fffff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.5: PCI bridge to [bus 07]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.0: BAR 6: assigned [mem 0xc5110000-0xc511ffff pref]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6: PCI bridge to [bus 08]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6:   bridge window [io  0x3000-0x3fff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6:   bridge window [mem 0xc5100000-0xc51fffff]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: resource 7 [mem 0x9d800000-0xdfffffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: resource 8 [mem 0xfc800000-0xfe7fffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:01: resource 0 [io  0x4000-0x4fff]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:01: resource 1 [mem 0xc3000000-0xc4ffffff]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:01: resource 2 [mem 0xb0000000-0xc1ffffff 64bit pref]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:06: resource 1 [mem 0xc5200000-0xc52fffff]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:08: resource 0 [io  0x3000-0x3fff]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:08: resource 1 [mem 0xc5100000-0xc51fffff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Feb 25 14:16:48 laptop kernel: PCI: CLS 64 bytes, default 64
Feb 25 14:16:48 laptop kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 25 14:16:48 laptop kernel: software IO TLB: mapped [mem 0x0000000087d15000-0x000000008bd15000] (64MB)
Feb 25 14:16:48 laptop kernel: Unpacking initramfs...
Feb 25 14:16:48 laptop kernel: Freeing initrd memory: 92K
Feb 25 14:16:48 laptop kernel: RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
Feb 25 14:16:48 laptop kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
Feb 25 14:16:48 laptop kernel: RAPL PMU: hw unit of domain package 2^-14 Joules
Feb 25 14:16:48 laptop kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules
Feb 25 14:16:48 laptop kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
Feb 25 14:16:48 laptop kernel: RAPL PMU: hw unit of domain psys 2^-14 Joules
Feb 25 14:16:48 laptop kernel: Initialise system trusted keyrings
Feb 25 14:16:48 laptop kernel: workingset: timestamp_bits=62 max_order=23 bucket_order=0
Feb 25 14:16:48 laptop kernel: Key type cifs.spnego registered
Feb 25 14:16:48 laptop kernel: Key type cifs.idmap registered
Feb 25 14:16:48 laptop kernel: fuse: init (API version 7.35)
Feb 25 14:16:48 laptop kernel: NET: Registered PF_ALG protocol family
Feb 25 14:16:48 laptop kernel: Key type asymmetric registered
Feb 25 14:16:48 laptop kernel: Asymmetric key parser 'x509' registered
Feb 25 14:16:48 laptop kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 25 14:16:48 laptop kernel: io scheduler mq-deadline registered
Feb 25 14:16:48 laptop kernel: Monitor-Mwait will be used to enter C-1 state
Feb 25 14:16:48 laptop kernel: Monitor-Mwait will be used to enter C-2 state
Feb 25 14:16:48 laptop kernel: Monitor-Mwait will be used to enter C-3 state
Feb 25 14:16:48 laptop kernel: ACPI: \_SB_.PR00: Found 3 idle states
Feb 25 14:16:48 laptop kernel: ACPI: AC: AC Adapter [AC] (on-line)
Feb 25 14:16:48 laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
Feb 25 14:16:48 laptop kernel: ACPI: button: Power Button [PWRB]
Feb 25 14:16:48 laptop kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
Feb 25 14:16:48 laptop kernel: ACPI: button: Sleep Button [SLPB]
Feb 25 14:16:48 laptop kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
Feb 25 14:16:48 laptop kernel: ACPI: button: Lid Switch [LID0]
Feb 25 14:16:48 laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
Feb 25 14:16:48 laptop kernel: ACPI: button: Power Button [PWRF]
Feb 25 14:16:48 laptop kernel: ACPI: \_TZ_.TZ0_: Invalid active0 threshold
Feb 25 14:16:48 laptop kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 25 14:16:48 laptop kernel: ACPI: thermal: Thermal Zone [TZ0] (25 C)
Feb 25 14:16:48 laptop kernel: ACPI: battery: Slot [BAT0] (battery present)
Feb 25 14:16:48 laptop kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Feb 25 14:16:48 laptop kernel: Linux agpgart interface v0.103
Feb 25 14:16:48 laptop kernel: ACPI: bus type drm_connector registered
Feb 25 14:16:48 laptop kernel: rtsx_pci 0000:08:00.0: enabling device (0000 -> 0002)
Feb 25 14:16:48 laptop kernel: nvme 0000:06:00.0: platform quirk: setting simple suspend
Feb 25 14:16:48 laptop kernel: nvme nvme0: pci function 0000:06:00.0
Feb 25 14:16:48 laptop kernel: ahci 0000:00:17.0: version 3.0
Feb 25 14:16:48 laptop kernel: nvme nvme0: allocated 32 MiB host memory buffer.
Feb 25 14:16:48 laptop kernel: nvme nvme0: 12/0/0 default/read/poll queues
Feb 25 14:16:48 laptop kernel: ahci 0000:00:17.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x10 impl SATA mode
Feb 25 14:16:48 laptop kernel: ahci 0000:00:17.0: flags: 64bit ncq sntf pm clo only pio slum part ems deso sadm sds apst 
Feb 25 14:16:48 laptop kernel: scsi host0: ahci
Feb 25 14:16:48 laptop kernel: scsi host1: ahci
Feb 25 14:16:48 laptop kernel: scsi host2: ahci
Feb 25 14:16:48 laptop kernel: scsi host3: ahci
Feb 25 14:16:48 laptop kernel: scsi host4: ahci
Feb 25 14:16:48 laptop kernel: ata1: DUMMY
Feb 25 14:16:48 laptop kernel: ata2: DUMMY
Feb 25 14:16:48 laptop kernel: ata3: DUMMY
Feb 25 14:16:48 laptop kernel: ata4: DUMMY
Feb 25 14:16:48 laptop kernel: ata5: SATA max UDMA/133 abar m2048@0xc53a3000 port 0xc53a3300 irq 122
Feb 25 14:16:48 laptop kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 25 14:16:48 laptop kernel: ehci-pci: EHCI PCI platform driver
Feb 25 14:16:48 laptop kernel: uhci_hcd: USB Universal Host Controller Interface driver
Feb 25 14:16:48 laptop kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Feb 25 14:16:48 laptop kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
Feb 25 14:16:48 laptop kernel:  nvme0n1: p1 p2 p3 p4 p5 p6 p7 p8
Feb 25 14:16:48 laptop kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000000009810
Feb 25 14:16:48 laptop kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.16
Feb 25 14:16:48 laptop kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 25 14:16:48 laptop kernel: usb usb1: Product: xHCI Host Controller
Feb 25 14:16:48 laptop kernel: usb usb1: Manufacturer: Linux 5.16.0-rc5+ xhci-hcd
Feb 25 14:16:48 laptop kernel: usb usb1: SerialNumber: 0000:00:14.0
Feb 25 14:16:48 laptop kernel: hub 1-0:1.0: USB hub found
Feb 25 14:16:48 laptop kernel: hub 1-0:1.0: 16 ports detected
Feb 25 14:16:48 laptop kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Feb 25 14:16:48 laptop kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
Feb 25 14:16:48 laptop kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed
Feb 25 14:16:48 laptop kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.16
Feb 25 14:16:48 laptop kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 25 14:16:48 laptop kernel: usb usb2: Product: xHCI Host Controller
Feb 25 14:16:48 laptop kernel: usb usb2: Manufacturer: Linux 5.16.0-rc5+ xhci-hcd
Feb 25 14:16:48 laptop kernel: usb usb2: SerialNumber: 0000:00:14.0
Feb 25 14:16:48 laptop kernel: hub 2-0:1.0: USB hub found
Feb 25 14:16:48 laptop kernel: hub 2-0:1.0: 8 ports detected
Feb 25 14:16:48 laptop kernel: usb: port power management may be unreliable
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver usb-storage
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver ums-realtek
Feb 25 14:16:48 laptop kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
Feb 25 14:16:48 laptop kernel: i8042: Detected active multiplexing controller, rev 1.1
Feb 25 14:16:48 laptop kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 25 14:16:48 laptop kernel: serio: i8042 AUX0 port at 0x60,0x64 irq 12
Feb 25 14:16:48 laptop kernel: serio: i8042 AUX1 port at 0x60,0x64 irq 12
Feb 25 14:16:48 laptop kernel: serio: i8042 AUX2 port at 0x60,0x64 irq 12
Feb 25 14:16:48 laptop kernel: serio: i8042 AUX3 port at 0x60,0x64 irq 12
Feb 25 14:16:48 laptop kernel: mousedev: PS/2 mouse device common for all mice
Feb 25 14:16:48 laptop kernel: rtc_cmos 00:04: RTC can wake from S4
Feb 25 14:16:48 laptop kernel: rtc_cmos 00:04: registered as rtc0
Feb 25 14:16:48 laptop kernel: rtc_cmos 00:04: setting system clock to 2022-02-25T14:16:43 UTC (1645798603)
Feb 25 14:16:48 laptop kernel: rtc_cmos 00:04: alarms up to one month, y3k, 242 bytes nvram
Feb 25 14:16:48 laptop kernel: i2c_dev: i2c /dev entries driver
Feb 25 14:16:48 laptop kernel: intel_pstate: Intel P-state driver initializing
Feb 25 14:16:48 laptop kernel: intel_pstate: HWP enabled
Feb 25 14:16:48 laptop kernel: efifb: probing for efifb
Feb 25 14:16:48 laptop kernel: efifb: framebuffer at 0xa0000000, using 8128k, total 8128k
Feb 25 14:16:48 laptop kernel: efifb: mode is 1920x1080x32, linelength=7680, pages=1
Feb 25 14:16:48 laptop kernel: efifb: scrolling: redraw
Feb 25 14:16:48 laptop kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 25 14:16:48 laptop kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
Feb 25 14:16:48 laptop kernel: Console: switching to colour frame buffer device 240x67
Feb 25 14:16:48 laptop kernel: fb0: EFI VGA frame buffer device
Feb 25 14:16:48 laptop kernel: NET: Registered PF_PACKET protocol family
Feb 25 14:16:48 laptop kernel: NET: Registered PF_KEY protocol family
Feb 25 14:16:48 laptop kernel: Key type dns_resolver registered
Feb 25 14:16:48 laptop kernel: microcode: sig=0xa0652, pf=0x20, revision=0xea
Feb 25 14:16:48 laptop kernel: microcode: Microcode Update Driver: v2.2.
Feb 25 14:16:48 laptop kernel: IPI shorthand broadcast: enabled
Feb 25 14:16:48 laptop kernel: AVX2 version of gcm_enc/dec engaged.
Feb 25 14:16:48 laptop kernel: AES CTR mode by8 optimization enabled
Feb 25 14:16:48 laptop kernel: sched_clock: Marking stable (1031587700, 5545988)->(1053381787, -16248099)
Feb 25 14:16:48 laptop kernel: registered taskstats version 1
Feb 25 14:16:48 laptop kernel: Loading compiled-in X.509 certificates
Feb 25 14:16:48 laptop kernel: usb 1-1: new full-speed USB device number 2 using xhci_hcd
Feb 25 14:16:48 laptop kernel: tsc: Refined TSC clocksource calibration: 2591.998 MHz
Feb 25 14:16:48 laptop kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x255cb518234, max_idle_ns: 440795279333 ns
Feb 25 14:16:48 laptop kernel: clocksource: Switched to clocksource tsc
Feb 25 14:16:48 laptop kernel: usb 1-1: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.01
Feb 25 14:16:48 laptop kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 25 14:16:48 laptop kernel: usb 1-1: Product: USB Receiver
Feb 25 14:16:48 laptop kernel: usb 1-1: Manufacturer: Logitech
Feb 25 14:16:48 laptop kernel: mmc0: cannot verify signal voltage switch
Feb 25 14:16:48 laptop kernel: usb 1-8: new high-speed USB device number 3 using xhci_hcd
Feb 25 14:16:48 laptop kernel: mmc0: new ultra high speed SDR104 SDHC card at address 59b4
Feb 25 14:16:48 laptop kernel: mmcblk0: mmc0:59b4 SDU1  14.7 GiB 
Feb 25 14:16:48 laptop kernel:  mmcblk0: p1
Feb 25 14:16:48 laptop kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 14:16:48 laptop kernel: ata5.00: ATA-10: ST2000LM015-2E8174, 0001, max UDMA/133
Feb 25 14:16:48 laptop kernel: usb 1-8: New USB device found, idVendor=04f2, idProduct=b685, bcdDevice=54.04
Feb 25 14:16:48 laptop kernel: usb 1-8: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Feb 25 14:16:48 laptop kernel: usb 1-8: Product: Chicony USB2.0 Camera
Feb 25 14:16:48 laptop kernel: usb 1-8: Manufacturer: Sonix Technology Co., Ltd.
Feb 25 14:16:48 laptop kernel: ata5.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Feb 25 14:16:48 laptop kernel: ata5.00: configured for UDMA/133
Feb 25 14:16:48 laptop kernel: scsi 4:0:0:0: Direct-Access     ATA      ST2000LM015-2E81 0001 PQ: 0 ANSI: 5
Feb 25 14:16:48 laptop kernel: scsi 4:0:0:0: Attached scsi generic sg0 type 0
Feb 25 14:16:48 laptop kernel: sd 4:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Feb 25 14:16:48 laptop kernel: sd 4:0:0:0: [sda] 4096-byte physical blocks
Feb 25 14:16:48 laptop kernel: sd 4:0:0:0: [sda] Write Protect is off
Feb 25 14:16:48 laptop kernel: sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 25 14:16:48 laptop kernel: sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 25 14:16:48 laptop kernel:  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
Feb 25 14:16:48 laptop kernel: sd 4:0:0:0: [sda] Attached SCSI disk
Feb 25 14:16:48 laptop kernel: usb 1-14: new full-speed USB device number 4 using xhci_hcd
Feb 25 14:16:48 laptop kernel: ALSA device list:
Feb 25 14:16:48 laptop kernel:   No soundcards found.
Feb 25 14:16:48 laptop kernel: EXT4-fs (nvme0n1p4): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop kernel: VFS: Mounted root (ext4 filesystem) readonly on device 259:4.
Feb 25 14:16:48 laptop kernel: devtmpfs: mounted
Feb 25 14:16:48 laptop kernel: Freeing unused kernel image (initmem) memory: 1008K
Feb 25 14:16:48 laptop kernel: Write protecting the kernel read-only data: 16384k
Feb 25 14:16:48 laptop kernel: Freeing unused kernel image (text/rodata gap) memory: 2044K
Feb 25 14:16:48 laptop kernel: Freeing unused kernel image (rodata/data gap) memory: 1548K
Feb 25 14:16:48 laptop kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
Feb 25 14:16:48 laptop kernel: Run /sbin/init as init process
Feb 25 14:16:48 laptop kernel:   with arguments:
Feb 25 14:16:48 laptop kernel:     /sbin/init
Feb 25 14:16:48 laptop kernel:   with environment:
Feb 25 14:16:48 laptop kernel:     HOME=/
Feb 25 14:16:48 laptop kernel:     TERM=linux
Feb 25 14:16:48 laptop kernel:     BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+
Feb 25 14:16:48 laptop kernel:     apm=power_off
Feb 25 14:16:48 laptop kernel: random: fast init done
Feb 25 14:16:48 laptop kernel: tun: Universal TUN/TAP device driver, 1.6
Feb 25 14:16:48 laptop kernel: usb 1-14: New USB device found, idVendor=8087, idProduct=0026, bcdDevice= 0.02
Feb 25 14:16:48 laptop kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 25 14:16:48 laptop kernel: <30>udevd[308]: starting version 3.2.11
Feb 25 14:16:48 laptop kernel: random: udevd: uninitialized urandom read (16 bytes read)
Feb 25 14:16:48 laptop last message repeated 2 times
Feb 25 14:16:48 laptop kernel: <30>udevd[309]: starting eudev-3.2.11
Feb 25 14:16:48 laptop kernel: wmi_bus wmi_bus-PNP0C14:01: WQ data block query control method not found
Feb 25 14:16:48 laptop last message repeated 3 times
Feb 25 14:16:48 laptop kernel: acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:03)
Feb 25 14:16:48 laptop kernel: mei_me 0000:00:16.0: enabling device (0000 -> 0002)
Feb 25 14:16:48 laptop kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Feb 25 14:16:48 laptop kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Feb 25 14:16:48 laptop kernel: Intel(R) Wireless WiFi driver for Linux
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver btusb
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Device revision is 2
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-69.ucode failed with error -2
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Secure boot is enabled
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-68.ucode failed with error -2
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: OTP lock is enabled
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: API lock is enabled
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Debug lock is disabled
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: loaded firmware version 67.8f59b80b.0 QuZ-a0-hr-b0-67.ucode op_mode iwlmvm
Feb 25 14:16:48 laptop kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C534.0001/input/input9
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
Feb 25 14:16:48 laptop kernel: intel-lpss 0000:00:15.0: enabling device (0004 -> 0006)
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Boot Address: 0x24800
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Firmware Version: 125-46.21
Feb 25 14:16:48 laptop kernel: intel-lpss 0000:00:15.1: enabling device (0004 -> 0006)
Feb 25 14:16:48 laptop kernel: checking generic (a0000000 7f0000) vs hw (c2000000 1000000)
Feb 25 14:16:48 laptop kernel: checking generic (a0000000 7f0000) vs hw (a0000000 10000000)
Feb 25 14:16:48 laptop kernel: fb0: switching to i915 from EFI VGA
Feb 25 14:16:48 laptop kernel: Console: switching to colour dummy device 80x25
Feb 25 14:16:48 laptop kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Feb 25 14:16:48 laptop kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
Feb 25 14:16:48 laptop kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
Feb 25 14:16:48 laptop kernel: i801_smbus 0000:00:1f.4: SPD Write Disable is set
Feb 25 14:16:48 laptop kernel: i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
Feb 25 14:16:48 laptop kernel: i2c i2c-4: 2/2 memory slots populated (from DMI)
Feb 25 14:16:48 laptop kernel: i2c i2c-4: Successfully instantiated SPD at 0x50
Feb 25 14:16:48 laptop kernel: usb 1-8: Found UVC 1.00 device Chicony USB2.0 Camera (04f2:b685)
Feb 25 14:16:48 laptop kernel: snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351
Feb 25 14:16:48 laptop kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver uvcvideo
Feb 25 14:16:48 laptop kernel: hid-generic 0003:046D:C534.0001: input: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-1/input0
Feb 25 14:16:48 laptop kernel: input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/input/input10
Feb 25 14:16:48 laptop kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/input/input11
Feb 25 14:16:48 laptop kernel: i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
Feb 25 14:16:48 laptop kernel: i915 0000:00:02.0: [drm] [ENCODER:117:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it
Feb 25 14:16:48 laptop kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
Feb 25 14:16:48 laptop kernel: ACPI: video: Video Device [PEGP] (multi-head: no  rom: yes  post: no)
Feb 25 14:16:48 laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input15
Feb 25 14:16:48 laptop kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/input/input12
Feb 25 14:16:48 laptop kernel: hid-generic 0003:046D:C534.0002: input,hiddev96: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-1/input1
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver usbhid
Feb 25 14:16:48 laptop kernel: usbhid: USB HID core driver
Feb 25 14:16:48 laptop kernel: ACPI: video: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Feb 25 14:16:48 laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input16
Feb 25 14:16:48 laptop kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Feb 25 14:16:48 laptop kernel: fbcon: i915 (fb0) is primary device
Feb 25 14:16:48 laptop kernel: Console: switching to colour frame buffer device 240x67
Feb 25 14:16:48 laptop kernel: i915 0000:00:02.0: [drm] fb0: i915 frame buffer device
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC293: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x18
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:      Headset Mic=0x1a
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: base HW address: 34:7d:f6:df:83:1a
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input21
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input22
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input23
Feb 25 14:16:48 laptop kernel: urandom_read: 6 callbacks suppressed
Feb 25 14:16:48 laptop kernel: random: udevd: uninitialized urandom read (16 bytes read)
Feb 25 14:16:48 laptop kernel: random: crng init done
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Waiting for firmware download to complete
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Firmware loaded in 1546001 usecs
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Waiting for device to boot
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Device booted in 13899 usecs
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Firmware revision 0.4 build 125 week 46 2021
Feb 25 14:16:48 laptop kernel: Adding 65535996k swap on /dev/sda5.  Priority:1 extents:1 across:65535996k 
Feb 25 14:16:48 laptop kernel: EXT4-fs (nvme0n1p4): re-mounted. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop kernel: EXT4-fs (nvme0n1p4): re-mounted. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop kernel: ntfs3: Max link count 4000
Feb 25 14:16:48 laptop kernel: EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop kernel: EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 14:16:50 laptop kernel: wlan0: authenticate with DE:AD:BE:EF:7c:25
Feb 25 14:16:50 laptop kernel: wlan0: send auth to DE:AD:BE:EF:7c:25 (try 1/3)
Feb 25 14:16:50 laptop kernel: wlan0: authenticated
Feb 25 14:16:50 laptop kernel: wlan0: associate with DE:AD:BE:EF:7c:25 (try 1/3)
Feb 25 14:16:50 laptop kernel: wlan0: RX AssocResp from DE:AD:BE:EF:7c:25 (capab=0x1011 status=0 aid=1)
Feb 25 14:16:50 laptop kernel: wlan0: associated
Feb 25 14:16:50 laptop kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by DE:AD:BE:EF:7c:25
Feb 25 14:16:50 laptop kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 25 14:16:50 laptop kernel: Bluetooth: BNEP filters: protocol multicast
Feb 25 14:16:50 laptop kernel: Bluetooth: BNEP socket layer initialized
Feb 25 14:16:50 laptop kernel: CIFS: Attempting to mount \\nas\Share
Feb 25 14:16:52 laptop kernel: CIFS: Attempting to mount \\nas\Media
Feb 25 14:17:00 laptop kernel: Bluetooth: RFCOMM TTY layer initialized
Feb 25 14:17:00 laptop kernel: Bluetooth: RFCOMM socket layer initialized
Feb 25 14:17:00 laptop kernel: Bluetooth: RFCOMM ver 1.11
Feb 25 14:17:03 laptop kernel: EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: disabled.

[-- Attachment #7: kern.log.good --]
[-- Type: text/plain, Size: 67332 bytes --]

Feb 25 13:58:19 laptop kernel: klogd 1.5.1, log source = /proc/kmsg started.
Feb 25 13:58:19 laptop kernel: Inspecting /boot/System.map-5.16.0-rc5+
Feb 25 13:58:19 laptop kernel: Cannot find map file.
Feb 25 13:58:19 laptop kernel: Loaded 48003 symbols from 47 modules.
Feb 25 13:58:19 laptop kernel: microcode: microcode updated early to revision 0xea, date = 2021-02-07
Feb 25 13:58:19 laptop kernel: Linux version 5.16.0-rc5+ (chris@laptop) (gcc (GCC) 11.2.1 20220219, GNU ld (GNU Binutils) 2.38) #907 SMP PREEMPT Fri Feb 25 11:29:24 GMT 2022
Feb 25 13:58:19 laptop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+ ro root=PARTUUID=f927883a-e95c-4cdd-b64e-a0a778216b9f resume=PARTUUID=70ccedc5-d788-42bc-9f13-81e2beb61338 apm=power_off rootfstype=ext4 net.ifnames=0
Feb 25 13:58:19 laptop kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Feb 25 13:58:19 laptop kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Feb 25 13:58:19 laptop kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Feb 25 13:58:19 laptop kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Feb 25 13:58:19 laptop kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Feb 25 13:58:19 laptop kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Feb 25 13:58:19 laptop kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Feb 25 13:58:19 laptop kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Feb 25 13:58:19 laptop kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Feb 25 13:58:19 laptop kernel: x86/fpu: xstate_offset[9]:  960, xstate_sizes[9]:    8
Feb 25 13:58:19 laptop kernel: x86/fpu: Enabled xstate features 0x21f, context size is 968 bytes, using 'compacted' format.
Feb 25 13:58:19 laptop kernel: signal: max sigframe size: 3632
Feb 25 13:58:19 laptop kernel: BIOS-provided physical RAM map:
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007e1d8fff] usable
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000007e1d9000-0x000000007ead8fff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000007ead9000-0x000000008cceefff] usable
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000008ccef000-0x000000008d0befff] type 20
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000008d0bf000-0x000000008eedefff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000008eedf000-0x000000008fbcefff] ACPI NVS
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000008fbcf000-0x000000008fc4efff] ACPI data
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000008fc4f000-0x000000008fc4ffff] usable
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000008fc50000-0x000000009d7fffff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x00000000ff400000-0x00000000ffffffff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008607fffff] usable
Feb 25 13:58:19 laptop kernel: NX (Execute Disable) protection: active
Feb 25 13:58:19 laptop kernel: efi: EFI v2.70 by INSYDE Corp.
Feb 25 13:58:19 laptop kernel: efi: ACPI=0x8fc4e000 ACPI 2.0=0x8fc4e014 TPMFinalLog=0x8fbc5000 SMBIOS=0x8d1e4000 SMBIOS 3.0=0x8d1e2000 ESRT=0x8d1e5998 MEMATTR=0x79ea3018 
Feb 25 13:58:19 laptop kernel: SMBIOS 3.2.0 present.
Feb 25 13:58:19 laptop kernel: DMI: Notebook                         NP50DE_DB                       /NP50DE_DB                       , BIOS 1.07.04 02/17/2020
Feb 25 13:58:19 laptop kernel: tsc: Detected 2600.000 MHz processor
Feb 25 13:58:19 laptop kernel: tsc: Detected 2599.992 MHz TSC
Feb 25 13:58:19 laptop kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 25 13:58:19 laptop kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 25 13:58:19 laptop kernel: last_pfn = 0x860800 max_arch_pfn = 0x400000000
Feb 25 13:58:19 laptop kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Feb 25 13:58:19 laptop kernel: last_pfn = 0x8fc50 max_arch_pfn = 0x400000000
Feb 25 13:58:19 laptop kernel: esrt: Reserving ESRT space from 0x000000008d1e5998 to 0x000000008d1e5a48.
Feb 25 13:58:19 laptop kernel: Using GB pages for direct mapping
Feb 25 13:58:19 laptop kernel: Secure boot disabled
Feb 25 13:58:19 laptop kernel: RAMDISK: [mem 0x37fc1000-0x37fd7fff]
Feb 25 13:58:19 laptop kernel: ACPI: Early table checksum verification disabled
Feb 25 13:58:19 laptop kernel: ACPI: RSDP 0x000000008FC4E014 000024 (v02 INSYDE)
Feb 25 13:58:19 laptop kernel: ACPI: XSDT 0x000000008FBF9188 0000DC (v01 INSYDE CML      00000002      01000013)
Feb 25 13:58:19 laptop kernel: ACPI: FACP 0x000000008FC37000 00010C (v05 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: DSDT 0x000000008FC00000 03337F (v02 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: FACS 0x000000008FB47000 000040
Feb 25 13:58:19 laptop kernel: ACPI: UEFI 0x000000008FBCE000 000236 (v01 INSYDE CML      00000001 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC4A000 002087 (v02 CpuRef CpuSsdt  00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC46000 003158 (v02 SaSsdt SaSsdt   00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC44000 001848 (v02 PegSsd PegSsdt  00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC43000 000790 (v02 INSYDE Tpm2Tabl 00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: TPM2 0x000000008FC42000 000034 (v04 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: LPIT 0x000000008FC40000 000094 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: WSMT 0x000000008FC3F000 000028 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC3D000 001616 (v02 INSYDE PtidDevc 00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: DBGP 0x000000008FC3C000 000034 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: DBG2 0x000000008FC3B000 00005C (v00 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC3A000 000502 (v02 Intel  PerfTune 00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: NHLT 0x000000008FC38000 001821 (v00 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: HPET 0x000000008FC36000 000038 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: APIC 0x000000008FC35000 000164 (v03 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: MCFG 0x000000008FC34000 00003C (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FBFF000 000E58 (v02 INSYDE ClevoRTD 00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FBFA000 0039F7 (v01 Insyde NvdTable 00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC4D000 000164 (v01 INSYDE PcdTabl  00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: DMAR 0x000000008FBFE000 0000A8 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: FPDT 0x000000008FBF8000 000044 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: BGRT 0x000000008FBF7000 000038 (v01 INSYDE CML      00000001 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: Reserving FACP table memory at [mem 0x8fc37000-0x8fc3710b]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving DSDT table memory at [mem 0x8fc00000-0x8fc3337e]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving FACS table memory at [mem 0x8fb47000-0x8fb4703f]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving UEFI table memory at [mem 0x8fbce000-0x8fbce235]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc4a000-0x8fc4c086]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc46000-0x8fc49157]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc44000-0x8fc45847]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc43000-0x8fc4378f]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving TPM2 table memory at [mem 0x8fc42000-0x8fc42033]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving LPIT table memory at [mem 0x8fc40000-0x8fc40093]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving WSMT table memory at [mem 0x8fc3f000-0x8fc3f027]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc3d000-0x8fc3e615]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving DBGP table memory at [mem 0x8fc3c000-0x8fc3c033]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving DBG2 table memory at [mem 0x8fc3b000-0x8fc3b05b]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc3a000-0x8fc3a501]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving NHLT table memory at [mem 0x8fc38000-0x8fc39820]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving HPET table memory at [mem 0x8fc36000-0x8fc36037]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving APIC table memory at [mem 0x8fc35000-0x8fc35163]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving MCFG table memory at [mem 0x8fc34000-0x8fc3403b]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fbff000-0x8fbffe57]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fbfa000-0x8fbfd9f6]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc4d000-0x8fc4d163]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving DMAR table memory at [mem 0x8fbfe000-0x8fbfe0a7]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving FPDT table memory at [mem 0x8fbf8000-0x8fbf8043]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving BGRT table memory at [mem 0x8fbf7000-0x8fbf7037]
Feb 25 13:58:19 laptop kernel: Zone ranges:
Feb 25 13:58:19 laptop kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 25 13:58:19 laptop kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 25 13:58:19 laptop kernel:   Normal   [mem 0x0000000100000000-0x00000008607fffff]
Feb 25 13:58:19 laptop kernel: Movable zone start for each node
Feb 25 13:58:19 laptop kernel: Early memory node ranges
Feb 25 13:58:19 laptop kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 25 13:58:19 laptop kernel:   node   0: [mem 0x0000000000100000-0x000000007e1d8fff]
Feb 25 13:58:19 laptop kernel:   node   0: [mem 0x000000007ead9000-0x000000008cceefff]
Feb 25 13:58:19 laptop kernel:   node   0: [mem 0x000000008fc4f000-0x000000008fc4ffff]
Feb 25 13:58:19 laptop kernel:   node   0: [mem 0x0000000100000000-0x00000008607fffff]
Feb 25 13:58:19 laptop kernel: Initmem setup node 0 [mem 0x0000000000001000-0x00000008607fffff]
Feb 25 13:58:19 laptop kernel: On node 0, zone DMA: 1 pages in unavailable ranges
Feb 25 13:58:19 laptop kernel: On node 0, zone DMA: 97 pages in unavailable ranges
Feb 25 13:58:19 laptop kernel: On node 0, zone DMA32: 2304 pages in unavailable ranges
Feb 25 13:58:19 laptop kernel: On node 0, zone DMA32: 12128 pages in unavailable ranges
Feb 25 13:58:19 laptop kernel: On node 0, zone Normal: 944 pages in unavailable ranges
Feb 25 13:58:19 laptop kernel: On node 0, zone Normal: 30720 pages in unavailable ranges
Feb 25 13:58:19 laptop kernel: Reserving Intel graphics memory at [mem 0x99800000-0x9d7fffff]
Feb 25 13:58:19 laptop kernel: ACPI: PM-Timer IO Port: 0x1808
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x14] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
Feb 25 13:58:19 laptop kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 25 13:58:19 laptop kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 25 13:58:19 laptop kernel: ACPI: Using ACPI (MADT) for SMP configuration information
Feb 25 13:58:19 laptop kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
Feb 25 13:58:19 laptop kernel: TSC deadline timer available
Feb 25 13:58:19 laptop kernel: smpboot: Allowing 12 CPUs, 0 hotplug CPUs
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x000fffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x7e1d9000-0x7ead8fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8ccef000-0x8d0befff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8d0bf000-0x8eedefff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8eedf000-0x8fbcefff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8fbcf000-0x8fc4efff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8fc50000-0x9d7fffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x9d800000-0xdfffffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xefffffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xf0000000-0xfdffffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfe000000-0xfe010fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfe011000-0xfed0ffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed10000-0xfed19fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed1a000-0xfed83fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed84000-0xfed84fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed85000-0xfedfffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xff3fffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xff400000-0xffffffff]
Feb 25 13:58:19 laptop kernel: [mem 0x9d800000-0xdfffffff] available for PCI devices
Feb 25 13:58:19 laptop kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 25 13:58:19 laptop kernel: setup_percpu: NR_CPUS:12 nr_cpumask_bits:12 nr_cpu_ids:12 nr_node_ids:1
Feb 25 13:58:19 laptop kernel: percpu: Embedded 44 pages/cpu s140440 r8192 d31592 u262144
Feb 25 13:58:19 laptop kernel: pcpu-alloc: s140440 r8192 d31592 u262144 alloc=1*2097152
Feb 25 13:58:19 laptop kernel: pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 -- -- -- -- 
Feb 25 13:58:19 laptop kernel: Built 1 zonelists, mobility grouping on.  Total pages: 8179648
Feb 25 13:58:19 laptop kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+ ro root=PARTUUID=f927883a-e95c-4cdd-b64e-a0a778216b9f resume=PARTUUID=70ccedc5-d788-42bc-9f13-81e2beb61338 apm=power_off rootfstype=ext4 net.ifnames=0
Feb 25 13:58:19 laptop kernel: Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+ apm=power_off", will be passed to user space.
Feb 25 13:58:19 laptop kernel: Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
Feb 25 13:58:19 laptop kernel: Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
Feb 25 13:58:19 laptop kernel: mem auto-init: stack:off, heap alloc:off, heap free:off
Feb 25 13:58:19 laptop kernel: Memory: 32517468K/33238584K available (10242K kernel code, 1120K rwdata, 2548K rodata, 1008K init, 892K bss, 720856K reserved, 0K cma-reserved)
Feb 25 13:58:19 laptop kernel: random: get_random_u64 called from __kmem_cache_create+0x1f/0x470 with crng_init=0
Feb 25 13:58:19 laptop kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=12, Nodes=1
Feb 25 13:58:19 laptop kernel: Dynamic Preempt: full
Feb 25 13:58:19 laptop kernel: rcu: Preemptible hierarchical RCU implementation.
Feb 25 13:58:19 laptop kernel: rcu: ^IRCU event tracing is enabled.
Feb 25 13:58:19 laptop kernel: ^ITrampoline variant of Tasks RCU enabled.
Feb 25 13:58:19 laptop kernel: rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
Feb 25 13:58:19 laptop kernel: NR_IRQS: 4352, nr_irqs: 2152, preallocated irqs: 16
Feb 25 13:58:19 laptop kernel: Console: colour dummy device 80x25
Feb 25 13:58:19 laptop kernel: printk: console [tty0] enabled
Feb 25 13:58:19 laptop kernel: ACPI: Core revision 20210930
Feb 25 13:58:19 laptop kernel: hpet: HPET dysfunctional in PC10. Force disabled.
Feb 25 13:58:19 laptop kernel: APIC: Switch to symmetric I/O mode setup
Feb 25 13:58:19 laptop kernel: Switched APIC routing to physical flat.
Feb 25 13:58:19 laptop kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x257a34a6eea, max_idle_ns: 440795264358 ns
Feb 25 13:58:19 laptop kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5199.98 BogoMIPS (lpj=10399968)
Feb 25 13:58:19 laptop kernel: pid_max: default: 32768 minimum: 301
Feb 25 13:58:19 laptop kernel: Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Feb 25 13:58:19 laptop kernel: Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Feb 25 13:58:19 laptop kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 25 13:58:19 laptop kernel: process: using mwait in idle threads
Feb 25 13:58:19 laptop kernel: Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
Feb 25 13:58:19 laptop kernel: Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
Feb 25 13:58:19 laptop kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
Feb 25 13:58:19 laptop kernel: Spectre V2 : Mitigation: Enhanced IBRS
Feb 25 13:58:19 laptop kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
Feb 25 13:58:19 laptop kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
Feb 25 13:58:19 laptop kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
Feb 25 13:58:19 laptop kernel: Freeing SMP alternatives memory: 28K
Feb 25 13:58:19 laptop kernel: smpboot: Estimated ratio of average max frequency by base frequency (times 1024): 1811
Feb 25 13:58:19 laptop kernel: smpboot: CPU0: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (family: 0x6, model: 0xa5, stepping: 0x2)
Feb 25 13:58:19 laptop kernel: Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
Feb 25 13:58:19 laptop kernel: ... version:                4
Feb 25 13:58:19 laptop kernel: ... bit width:              48
Feb 25 13:58:19 laptop kernel: ... generic registers:      4
Feb 25 13:58:19 laptop kernel: ... value mask:             0000ffffffffffff
Feb 25 13:58:19 laptop kernel: ... max period:             00007fffffffffff
Feb 25 13:58:19 laptop kernel: ... fixed-purpose events:   3
Feb 25 13:58:19 laptop kernel: ... event mask:             000000070000000f
Feb 25 13:58:19 laptop kernel: rcu: Hierarchical SRCU implementation.
Feb 25 13:58:19 laptop kernel: smp: Bringing up secondary CPUs ...
Feb 25 13:58:19 laptop kernel: x86: Booting SMP configuration:
Feb 25 13:58:19 laptop kernel: .... node  #0, CPUs:        #1  #2  #3  #4  #5  #6  #7  #8  #9 #10 #11
Feb 25 13:58:19 laptop kernel: smp: Brought up 1 node, 12 CPUs
Feb 25 13:58:19 laptop kernel: smpboot: Max logical packages: 1
Feb 25 13:58:19 laptop kernel: smpboot: Total of 12 processors activated (62399.80 BogoMIPS)
Feb 25 13:58:19 laptop kernel: devtmpfs: initialized
Feb 25 13:58:19 laptop kernel: ACPI: PM: Registering ACPI NVS region [mem 0x8eedf000-0x8fbcefff] (13565952 bytes)
Feb 25 13:58:19 laptop kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 25 13:58:19 laptop kernel: futex hash table entries: 4096 (order: 6, 262144 bytes, linear)
Feb 25 13:58:19 laptop kernel: NET: Registered PF_NETLINK/PF_ROUTE protocol family
Feb 25 13:58:19 laptop kernel: thermal_sys: Registered thermal governor 'step_wise'
Feb 25 13:58:19 laptop kernel: thermal_sys: Registered thermal governor 'user_space'
Feb 25 13:58:19 laptop kernel: cpuidle: using governor ladder
Feb 25 13:58:19 laptop kernel: cpuidle: using governor menu
Feb 25 13:58:19 laptop kernel: PCI: Using configuration type 1 for base access
Feb 25 13:58:19 laptop kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 25 13:58:19 laptop kernel: cryptd: max_cpu_qlen set to 1000
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(Module Device)
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(Processor Device)
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(Linux-Dell-Video)
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
Feb 25 13:58:19 laptop kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.XDCI], AE_NOT_FOUND (20210930/dswload2-162)
Feb 25 13:58:19 laptop kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210930/psobject-220)
Feb 25 13:58:19 laptop kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0010)
Feb 25 13:58:19 laptop kernel: ACPI: 10 ACPI AML tables successfully acquired and loaded
Feb 25 13:58:19 laptop kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA184000F3300 0000FC (v02 PmRef  Cpu0Psd  00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: \_SB_.PR00: _OSC native thermal LVT Acked
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA18400CC0800 000400 (v02 PmRef  Cpu0Cst  00003001 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA18400CBA800 000581 (v02 PmRef  Cpu0Ist  00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA1840014B400 000137 (v02 PmRef  Cpu0Hwp  00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA1840006C000 000BEA (v02 PmRef  HwpLvt   00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA18400CBC000 000778 (v02 PmRef  ApIst    00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA18400CC0C00 0003D7 (v02 PmRef  ApHwp    00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA1840006D000 000D22 (v02 PmRef  ApPsd    00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA18400CC1000 0003CA (v02 PmRef  ApCst    00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: EC: EC started
Feb 25 13:58:19 laptop kernel: ACPI: EC: interrupt blocked
Feb 25 13:58:19 laptop kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
Feb 25 13:58:19 laptop kernel: ACPI: \_SB_.PCI0.LPCB.EC__: Boot DSDT EC used to handle transactions
Feb 25 13:58:19 laptop kernel: ACPI: Interpreter enabled
Feb 25 13:58:19 laptop kernel: ACPI: PM: (supports S0 S3 S4 S5)
Feb 25 13:58:19 laptop kernel: ACPI: Using IOAPIC for interrupt routing
Feb 25 13:58:19 laptop kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 25 13:58:19 laptop kernel: ACPI: Enabled 7 GPEs in block 00 to 7F
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [PG00]
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [BTPR]
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [V0PR]
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [V1PR]
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [V2PR]
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [WRST]
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [PIN]
Feb 25 13:58:19 laptop kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
Feb 25 13:58:19 laptop kernel: acpi PNP0A08:00: _OSC: OS supports [ASPM ClockPM Segments MSI HPX-Type3]
Feb 25 13:58:19 laptop kernel: acpi PNP0A08:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI]
Feb 25 13:58:19 laptop kernel: PCI host bridge to bus 0000:00
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: root bus resource [mem 0x9d800000-0xdfffffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: root bus resource [mem 0xfc800000-0xfe7fffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: root bus resource [bus 00-fe]
Feb 25 13:58:19 laptop kernel: pci 0000:00:00.0: [8086:9b54] type 00 class 0x060000
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0: [8086:1901] type 01 class 0x060400
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: [8086:9bc4] type 00 class 0x030000
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: reg 0x10: [mem 0xc2000000-0xc2ffffff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: reg 0x18: [mem 0xa0000000-0xafffffff 64bit pref]
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: reg 0x20: [io  0x5000-0x503f]
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: BAR 2: assigned to efifb
Feb 25 13:58:19 laptop kernel: pci 0000:00:12.0: [8086:06f9] type 00 class 0x118000
Feb 25 13:58:19 laptop kernel: pci 0000:00:12.0: reg 0x10: [mem 0xc539c000-0xc539cfff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.0: [8086:06ed] type 00 class 0x0c0330
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.0: reg 0x10: [mem 0xc5380000-0xc538ffff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.2: [8086:06ef] type 00 class 0x050000
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.2: reg 0x10: [mem 0xc5398000-0xc5399fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.2: reg 0x18: [mem 0xc539d000-0xc539dfff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.3: [8086:06f0] type 00 class 0x028000
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.3: reg 0x10: [mem 0xc5390000-0xc5393fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.3: PME# supported from D0 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:15.0: [8086:06e8] type 00 class 0x0c8000
Feb 25 13:58:19 laptop kernel: pci 0000:00:15.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:15.1: [8086:06e9] type 00 class 0x0c8000
Feb 25 13:58:19 laptop kernel: pci 0000:00:15.1: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:16.0: [8086:06e0] type 00 class 0x078000
Feb 25 13:58:19 laptop kernel: pci 0000:00:16.0: reg 0x10: [mem 0xc53a0000-0xc53a0fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:16.0: PME# supported from D3hot
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: [8086:06d3] type 00 class 0x010601
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: reg 0x10: [mem 0xc539a000-0xc539bfff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: reg 0x14: [mem 0xc53a4000-0xc53a40ff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: reg 0x18: [io  0x5080-0x5087]
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: reg 0x1c: [io  0x5088-0x508b]
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: reg 0x20: [io  0x5060-0x507f]
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: reg 0x24: [mem 0xc53a3000-0xc53a37ff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: PME# supported from D3hot
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.0: [8086:06b0] type 01 class 0x060400
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.5: [8086:06b5] type 01 class 0x060400
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.5: PME# supported from D0 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6: [8086:06b6] type 01 class 0x060400
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6: PME# supported from D0 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.0: [8086:068d] type 00 class 0x060100
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.3: [8086:06c8] type 00 class 0x040300
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xc5394000-0xc5397fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.3: reg 0x20: [mem 0xc5000000-0xc50fffff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.3: PME# supported from D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.4: [8086:06a3] type 00 class 0x0c0500
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.4: reg 0x10: [mem 0xc53a1000-0xc53a10ff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.4: reg 0x20: [io  0xefa0-0xefbf]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.5: [8086:06a4] type 00 class 0x0c8000
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.5: reg 0x10: [mem 0xfe010000-0xfe010fff]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: [10de:1f95] type 00 class 0x030000
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: reg 0x10: [mem 0xc4000000-0xc4ffffff]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: reg 0x14: [mem 0xb0000000-0xbfffffff 64bit pref]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xc0000000-0xc1ffffff 64bit pref]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: reg 0x24: [io  0x4000-0x407f]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfff80000-0xffffffff pref]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: Enabling HDA controller
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: 63.008 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x8 link at 0000:00:01.0 (capable of 126.016 Gb/s with 8.0 GT/s PCIe x16 link)
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0: PCI bridge to [bus 01-05]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0:   bridge window [io  0x4000-0x4fff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xc3000000-0xc4ffffff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xb0000000-0xc1ffffff 64bit pref]
Feb 25 13:58:19 laptop kernel: pci 0000:06:00.0: [15b7:5009] type 00 class 0x010802
Feb 25 13:58:19 laptop kernel: pci 0000:06:00.0: reg 0x10: [mem 0xc5200000-0xc5203fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:06:00.0: reg 0x20: [mem 0xc5204000-0xc52040ff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.0: PCI bridge to [bus 06]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.0:   bridge window [mem 0xc5200000-0xc52fffff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.5: PCI bridge to [bus 07]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.0: [10ec:5287] type 00 class 0xff0000
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.0: reg 0x10: [mem 0xc5105000-0xc5105fff]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.0: supports D1 D2
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.0: PME# supported from D1 D2 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.1: [10ec:8168] type 00 class 0x020000
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.1: reg 0x10: [io  0x3000-0x30ff]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.1: reg 0x18: [mem 0xc5104000-0xc5104fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.1: reg 0x20: [mem 0xc5100000-0xc5103fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.1: supports D1 D2
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.1: PME# supported from D0 D1 D2 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6: PCI bridge to [bus 08]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6:   bridge window [io  0x3000-0x3fff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6:   bridge window [mem 0xc5100000-0xc51fffff]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: on NUMA node 0
Feb 25 13:58:19 laptop kernel: ACPI: EC: interrupt unblocked
Feb 25 13:58:19 laptop kernel: ACPI: EC: event unblocked
Feb 25 13:58:19 laptop kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
Feb 25 13:58:19 laptop kernel: ACPI: EC: GPE=0x3
Feb 25 13:58:19 laptop kernel: ACPI: \_SB_.PCI0.LPCB.EC__: Boot DSDT EC initialization complete
Feb 25 13:58:19 laptop kernel: ACPI: \_SB_.PCI0.LPCB.EC__: EC: Used to handle transactions and events
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: vgaarb: no bridge control possible
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: vgaarb: bridge control possible
Feb 25 13:58:19 laptop kernel: vgaarb: loaded
Feb 25 13:58:19 laptop kernel: SCSI subsystem initialized
Feb 25 13:58:19 laptop kernel: libata version 3.00 loaded.
Feb 25 13:58:19 laptop kernel: ACPI: bus type USB registered
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver usbfs
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver hub
Feb 25 13:58:19 laptop kernel: usbcore: registered new device driver usb
Feb 25 13:58:19 laptop kernel: mc: Linux media interface: v0.10
Feb 25 13:58:19 laptop kernel: videodev: Linux video capture interface: v2.00
Feb 25 13:58:19 laptop kernel: Registered efivars operations
Feb 25 13:58:19 laptop kernel: Advanced Linux Sound Architecture Driver Initialized.
Feb 25 13:58:19 laptop kernel: Bluetooth: Core ver 2.22
Feb 25 13:58:19 laptop kernel: NET: Registered PF_BLUETOOTH protocol family
Feb 25 13:58:19 laptop kernel: Bluetooth: HCI device and connection manager initialized
Feb 25 13:58:19 laptop kernel: Bluetooth: HCI socket layer initialized
Feb 25 13:58:19 laptop kernel: Bluetooth: L2CAP socket layer initialized
Feb 25 13:58:19 laptop kernel: Bluetooth: SCO socket layer initialized
Feb 25 13:58:19 laptop kernel: PCI: Using ACPI for IRQ routing
Feb 25 13:58:19 laptop kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 25 13:58:19 laptop kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 25 13:58:19 laptop kernel: e820: reserve RAM buffer [mem 0x7e1d9000-0x7fffffff]
Feb 25 13:58:19 laptop kernel: e820: reserve RAM buffer [mem 0x8ccef000-0x8fffffff]
Feb 25 13:58:19 laptop kernel: e820: reserve RAM buffer [mem 0x8fc50000-0x8fffffff]
Feb 25 13:58:19 laptop kernel: e820: reserve RAM buffer [mem 0x860800000-0x863ffffff]
Feb 25 13:58:19 laptop kernel: clocksource: Switched to clocksource tsc-early
Feb 25 13:58:19 laptop kernel: pnp: PnP ACPI init
Feb 25 13:58:19 laptop kernel: system 00:00: [mem 0x40000000-0x403fffff] could not be reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [io  0x1800-0x18fe] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [mem 0xfd000000-0xfd69ffff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [mem 0xfd6c0000-0xfd6cffff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [mem 0xfd6f0000-0xfdffffff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [mem 0xfe000000-0xfe01ffff] could not be reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [mem 0xfe200000-0xfe7fffff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [mem 0xff000000-0xffffffff] could not be reserved
Feb 25 13:58:19 laptop kernel: system 00:02: [io  0x2000-0x20fe] has been reserved
Feb 25 13:58:19 laptop kernel: pnp 00:03: disabling [io  0x3322-0x3323] because it overlaps 0000:00:1d.6 BAR 7 [io  0x3000-0x3fff]
Feb 25 13:58:19 laptop kernel: system 00:03: [io  0x0680-0x069f] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:03: [io  0x164e-0x164f] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:05: [io  0x1854-0x1857] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xe0000000-0xefffffff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfed45000-0xfed8ffff] could not be reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 25 13:58:19 laptop kernel: system 00:09: [mem 0xfe038000-0xfe038fff] has been reserved
Feb 25 13:58:19 laptop kernel: pnp: PnP ACPI: found 10 devices
Feb 25 13:58:19 laptop kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 25 13:58:19 laptop kernel: NET: Registered PF_INET protocol family
Feb 25 13:58:19 laptop kernel: IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Feb 25 13:58:19 laptop kernel: tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)
Feb 25 13:58:19 laptop kernel: TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Feb 25 13:58:19 laptop kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
Feb 25 13:58:19 laptop kernel: TCP: Hash tables configured (established 262144 bind 65536)
Feb 25 13:58:19 laptop kernel: UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)
Feb 25 13:58:19 laptop kernel: UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)
Feb 25 13:58:19 laptop kernel: NET: Registered PF_UNIX/PF_LOCAL protocol family
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: can't claim BAR 6 [mem 0xfff80000-0xffffffff pref]: no compatible bridge window
Feb 25 13:58:19 laptop kernel: pci 0000:00:15.0: BAR 0: assigned [mem 0x9d800000-0x9d800fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:15.1: BAR 0: assigned [mem 0x9d801000-0x9d801fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xc3000000-0xc307ffff pref]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0: PCI bridge to [bus 01-05]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0:   bridge window [io  0x4000-0x4fff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xc3000000-0xc4ffffff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xb0000000-0xc1ffffff 64bit pref]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.0: PCI bridge to [bus 06]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.0:   bridge window [mem 0xc5200000-0xc52fffff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.5: PCI bridge to [bus 07]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.0: BAR 6: assigned [mem 0xc5110000-0xc511ffff pref]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6: PCI bridge to [bus 08]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6:   bridge window [io  0x3000-0x3fff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6:   bridge window [mem 0xc5100000-0xc51fffff]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: resource 7 [mem 0x9d800000-0xdfffffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: resource 8 [mem 0xfc800000-0xfe7fffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:01: resource 0 [io  0x4000-0x4fff]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:01: resource 1 [mem 0xc3000000-0xc4ffffff]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:01: resource 2 [mem 0xb0000000-0xc1ffffff 64bit pref]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:06: resource 1 [mem 0xc5200000-0xc52fffff]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:08: resource 0 [io  0x3000-0x3fff]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:08: resource 1 [mem 0xc5100000-0xc51fffff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Feb 25 13:58:19 laptop kernel: PCI: CLS 64 bytes, default 64
Feb 25 13:58:19 laptop kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 25 13:58:19 laptop kernel: software IO TLB: mapped [mem 0x0000000087d15000-0x000000008bd15000] (64MB)
Feb 25 13:58:19 laptop kernel: Unpacking initramfs...
Feb 25 13:58:19 laptop kernel: Freeing initrd memory: 92K
Feb 25 13:58:19 laptop kernel: RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
Feb 25 13:58:19 laptop kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
Feb 25 13:58:19 laptop kernel: RAPL PMU: hw unit of domain package 2^-14 Joules
Feb 25 13:58:19 laptop kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules
Feb 25 13:58:19 laptop kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
Feb 25 13:58:19 laptop kernel: RAPL PMU: hw unit of domain psys 2^-14 Joules
Feb 25 13:58:19 laptop kernel: Initialise system trusted keyrings
Feb 25 13:58:19 laptop kernel: workingset: timestamp_bits=62 max_order=23 bucket_order=0
Feb 25 13:58:19 laptop kernel: Key type cifs.spnego registered
Feb 25 13:58:19 laptop kernel: Key type cifs.idmap registered
Feb 25 13:58:19 laptop kernel: fuse: init (API version 7.35)
Feb 25 13:58:19 laptop kernel: NET: Registered PF_ALG protocol family
Feb 25 13:58:19 laptop kernel: Key type asymmetric registered
Feb 25 13:58:19 laptop kernel: Asymmetric key parser 'x509' registered
Feb 25 13:58:19 laptop kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 25 13:58:19 laptop kernel: io scheduler mq-deadline registered
Feb 25 13:58:19 laptop kernel: Monitor-Mwait will be used to enter C-1 state
Feb 25 13:58:19 laptop kernel: Monitor-Mwait will be used to enter C-2 state
Feb 25 13:58:19 laptop kernel: Monitor-Mwait will be used to enter C-3 state
Feb 25 13:58:19 laptop kernel: ACPI: \_SB_.PR00: Found 3 idle states
Feb 25 13:58:19 laptop kernel: ACPI: AC: AC Adapter [AC] (on-line)
Feb 25 13:58:19 laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
Feb 25 13:58:19 laptop kernel: ACPI: button: Power Button [PWRB]
Feb 25 13:58:19 laptop kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
Feb 25 13:58:19 laptop kernel: ACPI: button: Sleep Button [SLPB]
Feb 25 13:58:19 laptop kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
Feb 25 13:58:19 laptop kernel: ACPI: button: Lid Switch [LID0]
Feb 25 13:58:19 laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
Feb 25 13:58:19 laptop kernel: ACPI: button: Power Button [PWRF]
Feb 25 13:58:19 laptop kernel: ACPI: \_TZ_.TZ0_: Invalid active0 threshold
Feb 25 13:58:19 laptop kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 25 13:58:19 laptop kernel: ACPI: thermal: Thermal Zone [TZ0] (25 C)
Feb 25 13:58:19 laptop kernel: ACPI: battery: Slot [BAT0] (battery present)
Feb 25 13:58:19 laptop kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Feb 25 13:58:19 laptop kernel: Linux agpgart interface v0.103
Feb 25 13:58:19 laptop kernel: ACPI: bus type drm_connector registered
Feb 25 13:58:19 laptop kernel: rtsx_pci 0000:08:00.0: enabling device (0000 -> 0002)
Feb 25 13:58:19 laptop kernel: nvme 0000:06:00.0: platform quirk: setting simple suspend
Feb 25 13:58:19 laptop kernel: nvme nvme0: pci function 0000:06:00.0
Feb 25 13:58:19 laptop kernel: ahci 0000:00:17.0: version 3.0
Feb 25 13:58:19 laptop kernel: ahci 0000:00:17.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x10 impl SATA mode
Feb 25 13:58:19 laptop kernel: ahci 0000:00:17.0: flags: 64bit ncq sntf pm clo only pio slum part ems deso sadm sds apst 
Feb 25 13:58:19 laptop kernel: scsi host0: ahci
Feb 25 13:58:19 laptop kernel: scsi host1: ahci
Feb 25 13:58:19 laptop kernel: scsi host2: ahci
Feb 25 13:58:19 laptop kernel: scsi host3: ahci
Feb 25 13:58:19 laptop kernel: scsi host4: ahci
Feb 25 13:58:19 laptop kernel: ata1: DUMMY
Feb 25 13:58:19 laptop kernel: ata2: DUMMY
Feb 25 13:58:19 laptop kernel: ata3: DUMMY
Feb 25 13:58:19 laptop kernel: ata4: DUMMY
Feb 25 13:58:19 laptop kernel: ata5: SATA max UDMA/133 abar m2048@0xc53a3000 port 0xc53a3300 irq 122
Feb 25 13:58:19 laptop kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 25 13:58:19 laptop kernel: ehci-pci: EHCI PCI platform driver
Feb 25 13:58:19 laptop kernel: uhci_hcd: USB Universal Host Controller Interface driver
Feb 25 13:58:19 laptop kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Feb 25 13:58:19 laptop kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
Feb 25 13:58:19 laptop kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000000009810
Feb 25 13:58:19 laptop kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.16
Feb 25 13:58:19 laptop kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 25 13:58:19 laptop kernel: usb usb1: Product: xHCI Host Controller
Feb 25 13:58:19 laptop kernel: usb usb1: Manufacturer: Linux 5.16.0-rc5+ xhci-hcd
Feb 25 13:58:19 laptop kernel: usb usb1: SerialNumber: 0000:00:14.0
Feb 25 13:58:19 laptop kernel: hub 1-0:1.0: USB hub found
Feb 25 13:58:19 laptop kernel: hub 1-0:1.0: 16 ports detected
Feb 25 13:58:19 laptop kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Feb 25 13:58:19 laptop kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
Feb 25 13:58:19 laptop kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed
Feb 25 13:58:19 laptop kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.16
Feb 25 13:58:19 laptop kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 25 13:58:19 laptop kernel: usb usb2: Product: xHCI Host Controller
Feb 25 13:58:19 laptop kernel: usb usb2: Manufacturer: Linux 5.16.0-rc5+ xhci-hcd
Feb 25 13:58:19 laptop kernel: usb usb2: SerialNumber: 0000:00:14.0
Feb 25 13:58:19 laptop kernel: hub 2-0:1.0: USB hub found
Feb 25 13:58:19 laptop kernel: hub 2-0:1.0: 8 ports detected
Feb 25 13:58:19 laptop kernel: usb: port power management may be unreliable
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver usb-storage
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver ums-realtek
Feb 25 13:58:19 laptop kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
Feb 25 13:58:19 laptop kernel: nvme nvme0: allocated 32 MiB host memory buffer.
Feb 25 13:58:19 laptop kernel: nvme nvme0: 12/0/0 default/read/poll queues
Feb 25 13:58:19 laptop kernel:  nvme0n1: p1 p2 p3 p4 p5 p6 p7 p8
Feb 25 13:58:19 laptop kernel: i8042: Detected active multiplexing controller, rev 1.1
Feb 25 13:58:19 laptop kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 25 13:58:19 laptop kernel: serio: i8042 AUX0 port at 0x60,0x64 irq 12
Feb 25 13:58:19 laptop kernel: serio: i8042 AUX1 port at 0x60,0x64 irq 12
Feb 25 13:58:19 laptop kernel: serio: i8042 AUX2 port at 0x60,0x64 irq 12
Feb 25 13:58:19 laptop kernel: serio: i8042 AUX3 port at 0x60,0x64 irq 12
Feb 25 13:58:19 laptop kernel: mousedev: PS/2 mouse device common for all mice
Feb 25 13:58:19 laptop kernel: rtc_cmos 00:04: RTC can wake from S4
Feb 25 13:58:19 laptop kernel: rtc_cmos 00:04: registered as rtc0
Feb 25 13:58:19 laptop kernel: rtc_cmos 00:04: setting system clock to 2022-02-25T13:58:14 UTC (1645797494)
Feb 25 13:58:19 laptop kernel: rtc_cmos 00:04: alarms up to one month, y3k, 242 bytes nvram
Feb 25 13:58:19 laptop kernel: i2c_dev: i2c /dev entries driver
Feb 25 13:58:19 laptop kernel: intel_pstate: Intel P-state driver initializing
Feb 25 13:58:19 laptop kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
Feb 25 13:58:19 laptop kernel: intel_pstate: HWP enabled
Feb 25 13:58:19 laptop kernel: efifb: probing for efifb
Feb 25 13:58:19 laptop kernel: efifb: framebuffer at 0xa0000000, using 8128k, total 8128k
Feb 25 13:58:19 laptop kernel: efifb: mode is 1920x1080x32, linelength=7680, pages=1
Feb 25 13:58:19 laptop kernel: efifb: scrolling: redraw
Feb 25 13:58:19 laptop kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 25 13:58:19 laptop kernel: Console: switching to colour frame buffer device 240x67
Feb 25 13:58:19 laptop kernel: fb0: EFI VGA frame buffer device
Feb 25 13:58:19 laptop kernel: NET: Registered PF_PACKET protocol family
Feb 25 13:58:19 laptop kernel: NET: Registered PF_KEY protocol family
Feb 25 13:58:19 laptop kernel: Key type dns_resolver registered
Feb 25 13:58:19 laptop kernel: microcode: sig=0xa0652, pf=0x20, revision=0xea
Feb 25 13:58:19 laptop kernel: microcode: Microcode Update Driver: v2.2.
Feb 25 13:58:19 laptop kernel: IPI shorthand broadcast: enabled
Feb 25 13:58:19 laptop kernel: AVX2 version of gcm_enc/dec engaged.
Feb 25 13:58:19 laptop kernel: AES CTR mode by8 optimization enabled
Feb 25 13:58:19 laptop kernel: sched_clock: Marking stable (1022591746, 5459506)->(1044397101, -16345849)
Feb 25 13:58:19 laptop kernel: registered taskstats version 1
Feb 25 13:58:19 laptop kernel: Loading compiled-in X.509 certificates
Feb 25 13:58:19 laptop kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 13:58:19 laptop kernel: usb 1-1: new full-speed USB device number 2 using xhci_hcd
Feb 25 13:58:19 laptop kernel: tsc: Refined TSC clocksource calibration: 2591.998 MHz
Feb 25 13:58:19 laptop kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x255cb518234, max_idle_ns: 440795279333 ns
Feb 25 13:58:19 laptop kernel: clocksource: Switched to clocksource tsc
Feb 25 13:58:19 laptop kernel: usb 1-1: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.01
Feb 25 13:58:19 laptop kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 25 13:58:19 laptop kernel: usb 1-1: Product: USB Receiver
Feb 25 13:58:19 laptop kernel: usb 1-1: Manufacturer: Logitech
Feb 25 13:58:19 laptop kernel: mmc0: cannot verify signal voltage switch
Feb 25 13:58:19 laptop kernel: usb 1-8: new high-speed USB device number 3 using xhci_hcd
Feb 25 13:58:19 laptop kernel: mmc0: new ultra high speed SDR104 SDHC card at address 59b4
Feb 25 13:58:19 laptop kernel: mmcblk0: mmc0:59b4 SDU1  14.7 GiB 
Feb 25 13:58:19 laptop kernel:  mmcblk0: p1
Feb 25 13:58:19 laptop kernel: usb 1-8: New USB device found, idVendor=04f2, idProduct=b685, bcdDevice=54.04
Feb 25 13:58:19 laptop kernel: usb 1-8: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Feb 25 13:58:19 laptop kernel: usb 1-8: Product: Chicony USB2.0 Camera
Feb 25 13:58:19 laptop kernel: usb 1-8: Manufacturer: Sonix Technology Co., Ltd.
Feb 25 13:58:19 laptop kernel: usb 1-14: new full-speed USB device number 4 using xhci_hcd
Feb 25 13:58:19 laptop kernel: ata5.00: ATA-10: ST2000LM015-2E8174, 0001, max UDMA/133
Feb 25 13:58:19 laptop kernel: usb 1-14: New USB device found, idVendor=8087, idProduct=0026, bcdDevice= 0.02
Feb 25 13:58:19 laptop kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 25 13:58:19 laptop kernel: ata5.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Feb 25 13:58:19 laptop kernel: ata5.00: configured for UDMA/133
Feb 25 13:58:19 laptop kernel: scsi 4:0:0:0: Direct-Access     ATA      ST2000LM015-2E81 0001 PQ: 0 ANSI: 5
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: Attached scsi generic sg0 type 0
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: [sda] 4096-byte physical blocks
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: [sda] Write Protect is off
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 25 13:58:19 laptop kernel:  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: [sda] Attached SCSI disk
Feb 25 13:58:19 laptop kernel: ALSA device list:
Feb 25 13:58:19 laptop kernel:   No soundcards found.
Feb 25 13:58:19 laptop kernel: EXT4-fs (nvme0n1p4): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop kernel: VFS: Mounted root (ext4 filesystem) readonly on device 259:4.
Feb 25 13:58:19 laptop kernel: devtmpfs: mounted
Feb 25 13:58:19 laptop kernel: Freeing unused kernel image (initmem) memory: 1008K
Feb 25 13:58:19 laptop kernel: Write protecting the kernel read-only data: 16384k
Feb 25 13:58:19 laptop kernel: Freeing unused kernel image (text/rodata gap) memory: 2044K
Feb 25 13:58:19 laptop kernel: Freeing unused kernel image (rodata/data gap) memory: 1548K
Feb 25 13:58:19 laptop kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
Feb 25 13:58:19 laptop kernel: Run /sbin/init as init process
Feb 25 13:58:19 laptop kernel:   with arguments:
Feb 25 13:58:19 laptop kernel:     /sbin/init
Feb 25 13:58:19 laptop kernel:   with environment:
Feb 25 13:58:19 laptop kernel:     HOME=/
Feb 25 13:58:19 laptop kernel:     TERM=linux
Feb 25 13:58:19 laptop kernel:     BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+
Feb 25 13:58:19 laptop kernel:     apm=power_off
Feb 25 13:58:19 laptop kernel: random: fast init done
Feb 25 13:58:19 laptop kernel: tun: Universal TUN/TAP device driver, 1.6
Feb 25 13:58:19 laptop kernel: <30>udevd[307]: starting version 3.2.11
Feb 25 13:58:19 laptop kernel: random: udevd: uninitialized urandom read (16 bytes read)
Feb 25 13:58:19 laptop last message repeated 2 times
Feb 25 13:58:19 laptop kernel: <30>udevd[308]: starting eudev-3.2.11
Feb 25 13:58:19 laptop kernel: wmi_bus wmi_bus-PNP0C14:01: WQ data block query control method not found
Feb 25 13:58:19 laptop last message repeated 3 times
Feb 25 13:58:19 laptop kernel: acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:03)
Feb 25 13:58:19 laptop kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Feb 25 13:58:19 laptop kernel: mei_me 0000:00:16.0: enabling device (0000 -> 0002)
Feb 25 13:58:19 laptop kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Feb 25 13:58:19 laptop kernel: Intel(R) Wireless WiFi driver for Linux
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver btusb
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-69.ucode failed with error -2
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Device revision is 2
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-68.ucode failed with error -2
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Secure boot is enabled
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: OTP lock is enabled
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: API lock is enabled
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: loaded firmware version 67.8f59b80b.0 QuZ-a0-hr-b0-67.ucode op_mode iwlmvm
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Debug lock is disabled
Feb 25 13:58:19 laptop kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C534.0001/input/input9
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Boot Address: 0x24800
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Firmware Version: 125-46.21
Feb 25 13:58:19 laptop kernel: intel-lpss 0000:00:15.0: enabling device (0004 -> 0006)
Feb 25 13:58:19 laptop kernel: intel-lpss 0000:00:15.1: enabling device (0004 -> 0006)
Feb 25 13:58:19 laptop kernel: checking generic (a0000000 7f0000) vs hw (c2000000 1000000)
Feb 25 13:58:19 laptop kernel: checking generic (a0000000 7f0000) vs hw (a0000000 10000000)
Feb 25 13:58:19 laptop kernel: fb0: switching to i915 from EFI VGA
Feb 25 13:58:19 laptop kernel: Console: switching to colour dummy device 80x25
Feb 25 13:58:19 laptop kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Feb 25 13:58:19 laptop kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
Feb 25 13:58:19 laptop kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
Feb 25 13:58:19 laptop kernel: usb 1-8: Found UVC 1.00 device Chicony USB2.0 Camera (04f2:b685)
Feb 25 13:58:19 laptop kernel: i801_smbus 0000:00:1f.4: SPD Write Disable is set
Feb 25 13:58:19 laptop kernel: i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351
Feb 25 13:58:19 laptop kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Feb 25 13:58:19 laptop kernel: i2c i2c-4: 2/2 memory slots populated (from DMI)
Feb 25 13:58:19 laptop kernel: i2c i2c-4: Successfully instantiated SPD at 0x50
Feb 25 13:58:19 laptop kernel: snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver uvcvideo
Feb 25 13:58:19 laptop kernel: hid-generic 0003:046D:C534.0001: input: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-1/input0
Feb 25 13:58:19 laptop kernel: input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/input/input10
Feb 25 13:58:19 laptop kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/input/input11
Feb 25 13:58:19 laptop kernel: i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
Feb 25 13:58:19 laptop kernel: i915 0000:00:02.0: [drm] [ENCODER:117:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it
Feb 25 13:58:19 laptop kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
Feb 25 13:58:19 laptop kernel: ACPI: video: Video Device [PEGP] (multi-head: no  rom: yes  post: no)
Feb 25 13:58:19 laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input15
Feb 25 13:58:19 laptop kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/input/input12
Feb 25 13:58:19 laptop kernel: hid-generic 0003:046D:C534.0002: input,hiddev96: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-1/input1
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver usbhid
Feb 25 13:58:19 laptop kernel: usbhid: USB HID core driver
Feb 25 13:58:19 laptop kernel: ACPI: video: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Feb 25 13:58:19 laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input16
Feb 25 13:58:19 laptop kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Feb 25 13:58:19 laptop kernel: fbcon: i915 (fb0) is primary device
Feb 25 13:58:19 laptop kernel: Console: switching to colour frame buffer device 240x67
Feb 25 13:58:19 laptop kernel: i915 0000:00:02.0: [drm] fb0: i915 frame buffer device
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC293: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x18
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:      Headset Mic=0x1a
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: base HW address: 34:7d:f6:df:83:1a
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input21
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input22
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input23
Feb 25 13:58:19 laptop kernel: random: crng init done
Feb 25 13:58:19 laptop kernel: random: 7 urandom warning(s) missed due to ratelimiting
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Waiting for firmware download to complete
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Firmware loaded in 1554718 usecs
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Waiting for device to boot
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Device booted in 14566 usecs
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Firmware revision 0.4 build 125 week 46 2021
Feb 25 13:58:19 laptop kernel: Adding 65535996k swap on /dev/sda5.  Priority:1 extents:1 across:65535996k 
Feb 25 13:58:19 laptop kernel: EXT4-fs (nvme0n1p4): re-mounted. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop kernel: EXT4-fs (nvme0n1p4): re-mounted. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop kernel: ntfs3: Max link count 4000
Feb 25 13:58:19 laptop kernel: EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop kernel: EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 13:58:21 laptop kernel: wlan0: authenticate with DE:AD:BE:EF:7c:22
Feb 25 13:58:21 laptop kernel: wlan0: bad VHT capabilities, disabling VHT
Feb 25 13:58:21 laptop kernel: wlan0: 80 MHz not supported, disabling VHT
Feb 25 13:58:21 laptop kernel: wlan0: send auth to DE:AD:BE:EF:7c:22 (try 1/3)
Feb 25 13:58:21 laptop kernel: wlan0: authenticated
Feb 25 13:58:21 laptop kernel: wlan0: associate with DE:AD:BE:EF:7c:22 (try 1/3)
Feb 25 13:58:21 laptop kernel: wlan0: RX AssocResp from DE:AD:BE:EF:7c:22 (capab=0x1411 status=0 aid=2)
Feb 25 13:58:21 laptop kernel: wlan0: associated
Feb 25 13:58:21 laptop kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 25 13:58:21 laptop kernel: Bluetooth: BNEP filters: protocol multicast
Feb 25 13:58:21 laptop kernel: Bluetooth: BNEP socket layer initialized
Feb 25 13:58:21 laptop kernel: CIFS: Attempting to mount \\nas\Share
Feb 25 13:58:22 laptop kernel: CIFS: Attempting to mount \\nas\Media
Feb 25 13:58:32 laptop kernel: Bluetooth: RFCOMM TTY layer initialized
Feb 25 13:58:32 laptop kernel: Bluetooth: RFCOMM socket layer initialized
Feb 25 13:58:32 laptop kernel: Bluetooth: RFCOMM ver 1.11
Feb 25 13:58:37 laptop kernel: EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: disabled.

[-- Attachment #8: sys.log.bad --]
[-- Type: text/plain, Size: 75896 bytes --]

Feb 25 14:16:48 laptop syslogd 1.5.1: restart.
Feb 25 14:16:48 laptop kernel: klogd 1.5.1, log source = /proc/kmsg started.
Feb 25 14:16:48 laptop kernel: Inspecting /boot/System.map-5.16.0-rc5+
Feb 25 14:16:48 laptop kernel: Cannot find map file.
Feb 25 14:16:48 laptop kernel: Loaded 48003 symbols from 47 modules.
Feb 25 14:16:48 laptop kernel: microcode: microcode updated early to revision 0xea, date = 2021-02-07
Feb 25 14:16:48 laptop kernel: Linux version 5.16.0-rc5+ (chris@laptop) (gcc (GCC) 11.2.1 20220219, GNU ld (GNU Binutils) 2.38) #907 SMP PREEMPT Fri Feb 25 11:29:24 GMT 2022
Feb 25 14:16:48 laptop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+ ro root=PARTUUID=f927883a-e95c-4cdd-b64e-a0a778216b9f resume=PARTUUID=70ccedc5-d788-42bc-9f13-81e2beb61338 apm=power_off rootfstype=ext4 net.ifnames=0
Feb 25 14:16:48 laptop kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Feb 25 14:16:48 laptop kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Feb 25 14:16:48 laptop kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Feb 25 14:16:48 laptop kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Feb 25 14:16:48 laptop kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Feb 25 14:16:48 laptop kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Feb 25 14:16:48 laptop kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Feb 25 14:16:48 laptop kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Feb 25 14:16:48 laptop kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Feb 25 14:16:48 laptop kernel: x86/fpu: xstate_offset[9]:  960, xstate_sizes[9]:    8
Feb 25 14:16:48 laptop kernel: x86/fpu: Enabled xstate features 0x21f, context size is 968 bytes, using 'compacted' format.
Feb 25 14:16:48 laptop kernel: signal: max sigframe size: 3632
Feb 25 14:16:48 laptop kernel: BIOS-provided physical RAM map:
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007e1d8fff] usable
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000007e1d9000-0x000000007ead8fff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000007ead9000-0x000000008cceefff] usable
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000008ccef000-0x000000008d0befff] type 20
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000008d0bf000-0x000000008eedefff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000008eedf000-0x000000008fbcefff] ACPI NVS
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000008fbcf000-0x000000008fc4efff] ACPI data
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000008fc4f000-0x000000008fc4ffff] usable
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x000000008fc50000-0x000000009d7fffff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x00000000ff400000-0x00000000ffffffff] reserved
Feb 25 14:16:48 laptop kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008607fffff] usable
Feb 25 14:16:48 laptop kernel: NX (Execute Disable) protection: active
Feb 25 14:16:48 laptop kernel: efi: EFI v2.70 by INSYDE Corp.
Feb 25 14:16:48 laptop kernel: efi: ACPI=0x8fc4e000 ACPI 2.0=0x8fc4e014 TPMFinalLog=0x8fbc5000 SMBIOS=0x8d1e4000 SMBIOS 3.0=0x8d1e2000 ESRT=0x8d1e5998 MEMATTR=0x79ea3018 
Feb 25 14:16:48 laptop kernel: SMBIOS 3.2.0 present.
Feb 25 14:16:48 laptop kernel: DMI: Notebook                         NP50DE_DB                       /NP50DE_DB                       , BIOS 1.07.04 02/17/2020
Feb 25 14:16:48 laptop kernel: tsc: Detected 2600.000 MHz processor
Feb 25 14:16:48 laptop kernel: tsc: Detected 2599.992 MHz TSC
Feb 25 14:16:48 laptop kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 25 14:16:48 laptop kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 25 14:16:48 laptop kernel: last_pfn = 0x860800 max_arch_pfn = 0x400000000
Feb 25 14:16:48 laptop kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Feb 25 14:16:48 laptop kernel: last_pfn = 0x8fc50 max_arch_pfn = 0x400000000
Feb 25 14:16:48 laptop kernel: esrt: Reserving ESRT space from 0x000000008d1e5998 to 0x000000008d1e5a48.
Feb 25 14:16:48 laptop kernel: Using GB pages for direct mapping
Feb 25 14:16:48 laptop kernel: Secure boot disabled
Feb 25 14:16:48 laptop kernel: RAMDISK: [mem 0x37fc1000-0x37fd7fff]
Feb 25 14:16:48 laptop kernel: ACPI: Early table checksum verification disabled
Feb 25 14:16:48 laptop kernel: ACPI: RSDP 0x000000008FC4E014 000024 (v02 INSYDE)
Feb 25 14:16:48 laptop kernel: ACPI: XSDT 0x000000008FBF9188 0000DC (v01 INSYDE CML      00000002      01000013)
Feb 25 14:16:48 laptop kernel: ACPI: FACP 0x000000008FC37000 00010C (v05 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: DSDT 0x000000008FC00000 03337F (v02 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: FACS 0x000000008FB47000 000040
Feb 25 14:16:48 laptop kernel: ACPI: UEFI 0x000000008FBCE000 000236 (v01 INSYDE CML      00000001 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC4A000 002087 (v02 CpuRef CpuSsdt  00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC46000 003158 (v02 SaSsdt SaSsdt   00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC44000 001848 (v02 PegSsd PegSsdt  00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC43000 000790 (v02 INSYDE Tpm2Tabl 00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: TPM2 0x000000008FC42000 000034 (v04 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: LPIT 0x000000008FC40000 000094 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: WSMT 0x000000008FC3F000 000028 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC3D000 001616 (v02 INSYDE PtidDevc 00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: DBGP 0x000000008FC3C000 000034 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: DBG2 0x000000008FC3B000 00005C (v00 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC3A000 000502 (v02 Intel  PerfTune 00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: NHLT 0x000000008FC38000 001821 (v00 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: HPET 0x000000008FC36000 000038 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: APIC 0x000000008FC35000 000164 (v03 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: MCFG 0x000000008FC34000 00003C (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FBFF000 000E58 (v02 INSYDE ClevoRTD 00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FBFA000 0039F7 (v01 Insyde NvdTable 00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0x000000008FC4D000 000164 (v01 INSYDE PcdTabl  00001000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: DMAR 0x000000008FBFE000 0000A8 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: FPDT 0x000000008FBF8000 000044 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: BGRT 0x000000008FBF7000 000038 (v01 INSYDE CML      00000001 ACPI 00040000)
Feb 25 14:16:48 laptop kernel: ACPI: Reserving FACP table memory at [mem 0x8fc37000-0x8fc3710b]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving DSDT table memory at [mem 0x8fc00000-0x8fc3337e]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving FACS table memory at [mem 0x8fb47000-0x8fb4703f]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving UEFI table memory at [mem 0x8fbce000-0x8fbce235]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc4a000-0x8fc4c086]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc46000-0x8fc49157]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc44000-0x8fc45847]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc43000-0x8fc4378f]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving TPM2 table memory at [mem 0x8fc42000-0x8fc42033]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving LPIT table memory at [mem 0x8fc40000-0x8fc40093]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving WSMT table memory at [mem 0x8fc3f000-0x8fc3f027]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc3d000-0x8fc3e615]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving DBGP table memory at [mem 0x8fc3c000-0x8fc3c033]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving DBG2 table memory at [mem 0x8fc3b000-0x8fc3b05b]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc3a000-0x8fc3a501]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving NHLT table memory at [mem 0x8fc38000-0x8fc39820]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving HPET table memory at [mem 0x8fc36000-0x8fc36037]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving APIC table memory at [mem 0x8fc35000-0x8fc35163]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving MCFG table memory at [mem 0x8fc34000-0x8fc3403b]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fbff000-0x8fbffe57]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fbfa000-0x8fbfd9f6]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc4d000-0x8fc4d163]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving DMAR table memory at [mem 0x8fbfe000-0x8fbfe0a7]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving FPDT table memory at [mem 0x8fbf8000-0x8fbf8043]
Feb 25 14:16:48 laptop kernel: ACPI: Reserving BGRT table memory at [mem 0x8fbf7000-0x8fbf7037]
Feb 25 14:16:48 laptop kernel: Zone ranges:
Feb 25 14:16:48 laptop kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 25 14:16:48 laptop kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 25 14:16:48 laptop kernel:   Normal   [mem 0x0000000100000000-0x00000008607fffff]
Feb 25 14:16:48 laptop kernel: Movable zone start for each node
Feb 25 14:16:48 laptop kernel: Early memory node ranges
Feb 25 14:16:48 laptop kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 25 14:16:48 laptop kernel:   node   0: [mem 0x0000000000100000-0x000000007e1d8fff]
Feb 25 14:16:48 laptop kernel:   node   0: [mem 0x000000007ead9000-0x000000008cceefff]
Feb 25 14:16:48 laptop kernel:   node   0: [mem 0x000000008fc4f000-0x000000008fc4ffff]
Feb 25 14:16:48 laptop kernel:   node   0: [mem 0x0000000100000000-0x00000008607fffff]
Feb 25 14:16:48 laptop kernel: Initmem setup node 0 [mem 0x0000000000001000-0x00000008607fffff]
Feb 25 14:16:48 laptop kernel: On node 0, zone DMA: 1 pages in unavailable ranges
Feb 25 14:16:48 laptop kernel: On node 0, zone DMA: 97 pages in unavailable ranges
Feb 25 14:16:48 laptop kernel: On node 0, zone DMA32: 2304 pages in unavailable ranges
Feb 25 14:16:48 laptop kernel: On node 0, zone DMA32: 12128 pages in unavailable ranges
Feb 25 14:16:48 laptop kernel: On node 0, zone Normal: 944 pages in unavailable ranges
Feb 25 14:16:48 laptop kernel: On node 0, zone Normal: 30720 pages in unavailable ranges
Feb 25 14:16:48 laptop kernel: Reserving Intel graphics memory at [mem 0x99800000-0x9d7fffff]
Feb 25 14:16:48 laptop kernel: ACPI: PM-Timer IO Port: 0x1808
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x14] high edge lint[0x1])
Feb 25 14:16:48 laptop kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
Feb 25 14:16:48 laptop kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 25 14:16:48 laptop kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 25 14:16:48 laptop kernel: ACPI: Using ACPI (MADT) for SMP configuration information
Feb 25 14:16:48 laptop kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
Feb 25 14:16:48 laptop kernel: TSC deadline timer available
Feb 25 14:16:48 laptop kernel: smpboot: Allowing 12 CPUs, 0 hotplug CPUs
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x000fffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x7e1d9000-0x7ead8fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8ccef000-0x8d0befff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8d0bf000-0x8eedefff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8eedf000-0x8fbcefff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8fbcf000-0x8fc4efff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8fc50000-0x9d7fffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x9d800000-0xdfffffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xefffffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xf0000000-0xfdffffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfe000000-0xfe010fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfe011000-0xfed0ffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed10000-0xfed19fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed1a000-0xfed83fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed84000-0xfed84fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed85000-0xfedfffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xff3fffff]
Feb 25 14:16:48 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xff400000-0xffffffff]
Feb 25 14:16:48 laptop kernel: [mem 0x9d800000-0xdfffffff] available for PCI devices
Feb 25 14:16:48 laptop kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 25 14:16:48 laptop kernel: setup_percpu: NR_CPUS:12 nr_cpumask_bits:12 nr_cpu_ids:12 nr_node_ids:1
Feb 25 14:16:48 laptop kernel: percpu: Embedded 44 pages/cpu s140440 r8192 d31592 u262144
Feb 25 14:16:48 laptop kernel: pcpu-alloc: s140440 r8192 d31592 u262144 alloc=1*2097152
Feb 25 14:16:48 laptop kernel: pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 -- -- -- -- 
Feb 25 14:16:48 laptop kernel: Built 1 zonelists, mobility grouping on.  Total pages: 8179648
Feb 25 14:16:48 laptop kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+ ro root=PARTUUID=f927883a-e95c-4cdd-b64e-a0a778216b9f resume=PARTUUID=70ccedc5-d788-42bc-9f13-81e2beb61338 apm=power_off rootfstype=ext4 net.ifnames=0
Feb 25 14:16:48 laptop kernel: Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+ apm=power_off", will be passed to user space.
Feb 25 14:16:48 laptop kernel: Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
Feb 25 14:16:48 laptop kernel: Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
Feb 25 14:16:48 laptop kernel: mem auto-init: stack:off, heap alloc:off, heap free:off
Feb 25 14:16:48 laptop kernel: Memory: 32517468K/33238584K available (10242K kernel code, 1120K rwdata, 2548K rodata, 1008K init, 892K bss, 720856K reserved, 0K cma-reserved)
Feb 25 14:16:48 laptop kernel: random: get_random_u64 called from __kmem_cache_create+0x1f/0x470 with crng_init=0
Feb 25 14:16:48 laptop kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=12, Nodes=1
Feb 25 14:16:48 laptop kernel: Dynamic Preempt: full
Feb 25 14:16:48 laptop kernel: rcu: Preemptible hierarchical RCU implementation.
Feb 25 14:16:48 laptop kernel: rcu: ^IRCU event tracing is enabled.
Feb 25 14:16:48 laptop kernel: ^ITrampoline variant of Tasks RCU enabled.
Feb 25 14:16:48 laptop kernel: rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
Feb 25 14:16:48 laptop kernel: NR_IRQS: 4352, nr_irqs: 2152, preallocated irqs: 16
Feb 25 14:16:48 laptop kernel: Console: colour dummy device 80x25
Feb 25 14:16:48 laptop kernel: printk: console [tty0] enabled
Feb 25 14:16:48 laptop kernel: ACPI: Core revision 20210930
Feb 25 14:16:48 laptop kernel: hpet: HPET dysfunctional in PC10. Force disabled.
Feb 25 14:16:48 laptop kernel: APIC: Switch to symmetric I/O mode setup
Feb 25 14:16:48 laptop kernel: Switched APIC routing to physical flat.
Feb 25 14:16:48 laptop kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x257a34a6eea, max_idle_ns: 440795264358 ns
Feb 25 14:16:48 laptop kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5199.98 BogoMIPS (lpj=10399968)
Feb 25 14:16:48 laptop kernel: pid_max: default: 32768 minimum: 301
Feb 25 14:16:48 laptop kernel: Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Feb 25 14:16:48 laptop kernel: Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Feb 25 14:16:48 laptop kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 25 14:16:48 laptop kernel: process: using mwait in idle threads
Feb 25 14:16:48 laptop kernel: Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
Feb 25 14:16:48 laptop kernel: Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
Feb 25 14:16:48 laptop kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
Feb 25 14:16:48 laptop kernel: Spectre V2 : Mitigation: Enhanced IBRS
Feb 25 14:16:48 laptop kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
Feb 25 14:16:48 laptop kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
Feb 25 14:16:48 laptop kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
Feb 25 14:16:48 laptop kernel: Freeing SMP alternatives memory: 28K
Feb 25 14:16:48 laptop kernel: smpboot: Estimated ratio of average max frequency by base frequency (times 1024): 1811
Feb 25 14:16:48 laptop kernel: smpboot: CPU0: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (family: 0x6, model: 0xa5, stepping: 0x2)
Feb 25 14:16:48 laptop kernel: Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
Feb 25 14:16:48 laptop kernel: ... version:                4
Feb 25 14:16:48 laptop kernel: ... bit width:              48
Feb 25 14:16:48 laptop kernel: ... generic registers:      4
Feb 25 14:16:48 laptop kernel: ... value mask:             0000ffffffffffff
Feb 25 14:16:48 laptop kernel: ... max period:             00007fffffffffff
Feb 25 14:16:48 laptop kernel: ... fixed-purpose events:   3
Feb 25 14:16:48 laptop kernel: ... event mask:             000000070000000f
Feb 25 14:16:48 laptop kernel: rcu: Hierarchical SRCU implementation.
Feb 25 14:16:48 laptop kernel: smp: Bringing up secondary CPUs ...
Feb 25 14:16:48 laptop kernel: x86: Booting SMP configuration:
Feb 25 14:16:48 laptop kernel: .... node  #0, CPUs:        #1  #2  #3  #4  #5  #6  #7  #8  #9 #10 #11
Feb 25 14:16:48 laptop kernel: smp: Brought up 1 node, 12 CPUs
Feb 25 14:16:48 laptop kernel: smpboot: Max logical packages: 1
Feb 25 14:16:48 laptop kernel: smpboot: Total of 12 processors activated (62399.80 BogoMIPS)
Feb 25 14:16:48 laptop kernel: devtmpfs: initialized
Feb 25 14:16:48 laptop kernel: ACPI: PM: Registering ACPI NVS region [mem 0x8eedf000-0x8fbcefff] (13565952 bytes)
Feb 25 14:16:48 laptop kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 25 14:16:48 laptop kernel: futex hash table entries: 4096 (order: 6, 262144 bytes, linear)
Feb 25 14:16:48 laptop kernel: NET: Registered PF_NETLINK/PF_ROUTE protocol family
Feb 25 14:16:48 laptop kernel: thermal_sys: Registered thermal governor 'step_wise'
Feb 25 14:16:48 laptop kernel: thermal_sys: Registered thermal governor 'user_space'
Feb 25 14:16:48 laptop kernel: cpuidle: using governor ladder
Feb 25 14:16:48 laptop kernel: cpuidle: using governor menu
Feb 25 14:16:48 laptop kernel: PCI: Using configuration type 1 for base access
Feb 25 14:16:48 laptop kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 25 14:16:48 laptop kernel: cryptd: max_cpu_qlen set to 1000
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(Module Device)
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(Processor Device)
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(Linux-Dell-Video)
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
Feb 25 14:16:48 laptop kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
Feb 25 14:16:48 laptop kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.XDCI], AE_NOT_FOUND (20210930/dswload2-162)
Feb 25 14:16:48 laptop kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210930/psobject-220)
Feb 25 14:16:48 laptop kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0010)
Feb 25 14:16:48 laptop kernel: ACPI: 10 ACPI AML tables successfully acquired and loaded
Feb 25 14:16:48 laptop kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF8939000F3300 0000FC (v02 PmRef  Cpu0Psd  00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: \_SB_.PR00: _OSC native thermal LVT Acked
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF893900CC0800 000400 (v02 PmRef  Cpu0Cst  00003001 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF893900CBA800 000581 (v02 PmRef  Cpu0Ist  00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF89390014B400 000137 (v02 PmRef  Cpu0Hwp  00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF89390006C000 000BEA (v02 PmRef  HwpLvt   00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF893900CBC000 000778 (v02 PmRef  ApIst    00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF893900CC0C00 0003D7 (v02 PmRef  ApHwp    00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF89390006D000 000D22 (v02 PmRef  ApPsd    00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 14:16:48 laptop kernel: ACPI: SSDT 0xFFFF893900CC1000 0003CA (v02 PmRef  ApCst    00003000 INTL 20160422)
Feb 25 14:16:48 laptop kernel: ACPI: EC: EC started
Feb 25 14:16:48 laptop kernel: ACPI: EC: interrupt blocked
Feb 25 14:16:48 laptop kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
Feb 25 14:16:48 laptop kernel: ACPI: \_SB_.PCI0.LPCB.EC__: Boot DSDT EC used to handle transactions
Feb 25 14:16:48 laptop kernel: ACPI: Interpreter enabled
Feb 25 14:16:48 laptop kernel: ACPI: PM: (supports S0 S3 S4 S5)
Feb 25 14:16:48 laptop kernel: ACPI: Using IOAPIC for interrupt routing
Feb 25 14:16:48 laptop kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 25 14:16:48 laptop kernel: ACPI: Enabled 7 GPEs in block 00 to 7F
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [PG00]
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [BTPR]
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [V0PR]
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [V1PR]
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [V2PR]
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [WRST]
Feb 25 14:16:48 laptop kernel: ACPI: PM: Power Resource [PIN]
Feb 25 14:16:48 laptop kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
Feb 25 14:16:48 laptop kernel: acpi PNP0A08:00: _OSC: OS supports [ASPM ClockPM Segments MSI HPX-Type3]
Feb 25 14:16:48 laptop kernel: acpi PNP0A08:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI]
Feb 25 14:16:48 laptop kernel: PCI host bridge to bus 0000:00
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: root bus resource [mem 0x9d800000-0xdfffffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: root bus resource [mem 0xfc800000-0xfe7fffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: root bus resource [bus 00-fe]
Feb 25 14:16:48 laptop kernel: pci 0000:00:00.0: [8086:9b54] type 00 class 0x060000
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0: [8086:1901] type 01 class 0x060400
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: [8086:9bc4] type 00 class 0x030000
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: reg 0x10: [mem 0xc2000000-0xc2ffffff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: reg 0x18: [mem 0xa0000000-0xafffffff 64bit pref]
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: reg 0x20: [io  0x5000-0x503f]
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: BAR 2: assigned to efifb
Feb 25 14:16:48 laptop kernel: pci 0000:00:12.0: [8086:06f9] type 00 class 0x118000
Feb 25 14:16:48 laptop kernel: pci 0000:00:12.0: reg 0x10: [mem 0xc539c000-0xc539cfff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.0: [8086:06ed] type 00 class 0x0c0330
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.0: reg 0x10: [mem 0xc5380000-0xc538ffff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.2: [8086:06ef] type 00 class 0x050000
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.2: reg 0x10: [mem 0xc5398000-0xc5399fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.2: reg 0x18: [mem 0xc539d000-0xc539dfff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.3: [8086:06f0] type 00 class 0x028000
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.3: reg 0x10: [mem 0xc5390000-0xc5393fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:14.3: PME# supported from D0 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:15.0: [8086:06e8] type 00 class 0x0c8000
Feb 25 14:16:48 laptop kernel: pci 0000:00:15.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:15.1: [8086:06e9] type 00 class 0x0c8000
Feb 25 14:16:48 laptop kernel: pci 0000:00:15.1: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:16.0: [8086:06e0] type 00 class 0x078000
Feb 25 14:16:48 laptop kernel: pci 0000:00:16.0: reg 0x10: [mem 0xc53a0000-0xc53a0fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:16.0: PME# supported from D3hot
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: [8086:06d3] type 00 class 0x010601
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: reg 0x10: [mem 0xc539a000-0xc539bfff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: reg 0x14: [mem 0xc53a4000-0xc53a40ff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: reg 0x18: [io  0x5080-0x5087]
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: reg 0x1c: [io  0x5088-0x508b]
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: reg 0x20: [io  0x5060-0x507f]
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: reg 0x24: [mem 0xc53a3000-0xc53a37ff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:17.0: PME# supported from D3hot
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.0: [8086:06b0] type 01 class 0x060400
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.5: [8086:06b5] type 01 class 0x060400
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.5: PME# supported from D0 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6: [8086:06b6] type 01 class 0x060400
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6: PME# supported from D0 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.0: [8086:068d] type 00 class 0x060100
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.3: [8086:06c8] type 00 class 0x040300
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xc5394000-0xc5397fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.3: reg 0x20: [mem 0xc5000000-0xc50fffff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.3: PME# supported from D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.4: [8086:06a3] type 00 class 0x0c0500
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.4: reg 0x10: [mem 0xc53a1000-0xc53a10ff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.4: reg 0x20: [io  0xefa0-0xefbf]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.5: [8086:06a4] type 00 class 0x0c8000
Feb 25 14:16:48 laptop kernel: pci 0000:00:1f.5: reg 0x10: [mem 0xfe010000-0xfe010fff]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: [10de:1f95] type 00 class 0x030000
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: reg 0x10: [mem 0xc4000000-0xc4ffffff]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: reg 0x14: [mem 0xb0000000-0xbfffffff 64bit pref]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xc0000000-0xc1ffffff 64bit pref]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: reg 0x24: [io  0x4000-0x407f]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfff80000-0xffffffff pref]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: Enabling HDA controller
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: 63.008 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x8 link at 0000:00:01.0 (capable of 126.016 Gb/s with 8.0 GT/s PCIe x16 link)
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0: PCI bridge to [bus 01-05]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0:   bridge window [io  0x4000-0x4fff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xc3000000-0xc4ffffff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xb0000000-0xc1ffffff 64bit pref]
Feb 25 14:16:48 laptop kernel: pci 0000:06:00.0: [15b7:5009] type 00 class 0x010802
Feb 25 14:16:48 laptop kernel: pci 0000:06:00.0: reg 0x10: [mem 0xc5200000-0xc5203fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:06:00.0: reg 0x20: [mem 0xc5204000-0xc52040ff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.0: PCI bridge to [bus 06]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.0:   bridge window [mem 0xc5200000-0xc52fffff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.5: PCI bridge to [bus 07]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.0: [10ec:5287] type 00 class 0xff0000
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.0: reg 0x10: [mem 0xc5105000-0xc5105fff]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.0: supports D1 D2
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.0: PME# supported from D1 D2 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.1: [10ec:8168] type 00 class 0x020000
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.1: reg 0x10: [io  0x3000-0x30ff]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.1: reg 0x18: [mem 0xc5104000-0xc5104fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.1: reg 0x20: [mem 0xc5100000-0xc5103fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.1: supports D1 D2
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.1: PME# supported from D0 D1 D2 D3hot D3cold
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6: PCI bridge to [bus 08]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6:   bridge window [io  0x3000-0x3fff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6:   bridge window [mem 0xc5100000-0xc51fffff]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: on NUMA node 0
Feb 25 14:16:48 laptop kernel: ACPI: EC: interrupt unblocked
Feb 25 14:16:48 laptop kernel: ACPI: EC: event unblocked
Feb 25 14:16:48 laptop kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
Feb 25 14:16:48 laptop kernel: ACPI: EC: GPE=0x3
Feb 25 14:16:48 laptop kernel: ACPI: \_SB_.PCI0.LPCB.EC__: Boot DSDT EC initialization complete
Feb 25 14:16:48 laptop kernel: ACPI: \_SB_.PCI0.LPCB.EC__: EC: Used to handle transactions and events
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: vgaarb: no bridge control possible
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: vgaarb: bridge control possible
Feb 25 14:16:48 laptop kernel: vgaarb: loaded
Feb 25 14:16:48 laptop kernel: SCSI subsystem initialized
Feb 25 14:16:48 laptop kernel: libata version 3.00 loaded.
Feb 25 14:16:48 laptop kernel: ACPI: bus type USB registered
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver usbfs
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver hub
Feb 25 14:16:48 laptop kernel: usbcore: registered new device driver usb
Feb 25 14:16:48 laptop kernel: mc: Linux media interface: v0.10
Feb 25 14:16:48 laptop kernel: videodev: Linux video capture interface: v2.00
Feb 25 14:16:48 laptop kernel: Registered efivars operations
Feb 25 14:16:48 laptop kernel: Advanced Linux Sound Architecture Driver Initialized.
Feb 25 14:16:48 laptop kernel: Bluetooth: Core ver 2.22
Feb 25 14:16:48 laptop kernel: NET: Registered PF_BLUETOOTH protocol family
Feb 25 14:16:48 laptop kernel: Bluetooth: HCI device and connection manager initialized
Feb 25 14:16:48 laptop kernel: Bluetooth: HCI socket layer initialized
Feb 25 14:16:48 laptop kernel: Bluetooth: L2CAP socket layer initialized
Feb 25 14:16:48 laptop kernel: Bluetooth: SCO socket layer initialized
Feb 25 14:16:48 laptop kernel: PCI: Using ACPI for IRQ routing
Feb 25 14:16:48 laptop kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 25 14:16:48 laptop kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 25 14:16:48 laptop kernel: e820: reserve RAM buffer [mem 0x7e1d9000-0x7fffffff]
Feb 25 14:16:48 laptop kernel: e820: reserve RAM buffer [mem 0x8ccef000-0x8fffffff]
Feb 25 14:16:48 laptop kernel: e820: reserve RAM buffer [mem 0x8fc50000-0x8fffffff]
Feb 25 14:16:48 laptop kernel: e820: reserve RAM buffer [mem 0x860800000-0x863ffffff]
Feb 25 14:16:48 laptop kernel: clocksource: Switched to clocksource tsc-early
Feb 25 14:16:48 laptop kernel: pnp: PnP ACPI init
Feb 25 14:16:48 laptop kernel: system 00:00: [mem 0x40000000-0x403fffff] could not be reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [io  0x1800-0x18fe] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [mem 0xfd000000-0xfd69ffff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [mem 0xfd6c0000-0xfd6cffff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [mem 0xfd6f0000-0xfdffffff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [mem 0xfe000000-0xfe01ffff] could not be reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [mem 0xfe200000-0xfe7fffff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:01: [mem 0xff000000-0xffffffff] could not be reserved
Feb 25 14:16:48 laptop kernel: system 00:02: [io  0x2000-0x20fe] has been reserved
Feb 25 14:16:48 laptop kernel: pnp 00:03: disabling [io  0x3322-0x3323] because it overlaps 0000:00:1d.6 BAR 7 [io  0x3000-0x3fff]
Feb 25 14:16:48 laptop kernel: system 00:03: [io  0x0680-0x069f] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:03: [io  0x164e-0x164f] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:05: [io  0x1854-0x1857] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xe0000000-0xefffffff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfed45000-0xfed8ffff] could not be reserved
Feb 25 14:16:48 laptop kernel: system 00:08: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 25 14:16:48 laptop kernel: system 00:09: [mem 0xfe038000-0xfe038fff] has been reserved
Feb 25 14:16:48 laptop kernel: pnp: PnP ACPI: found 10 devices
Feb 25 14:16:48 laptop kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 25 14:16:48 laptop kernel: NET: Registered PF_INET protocol family
Feb 25 14:16:48 laptop kernel: IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Feb 25 14:16:48 laptop kernel: tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)
Feb 25 14:16:48 laptop kernel: TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Feb 25 14:16:48 laptop kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
Feb 25 14:16:48 laptop kernel: TCP: Hash tables configured (established 262144 bind 65536)
Feb 25 14:16:48 laptop kernel: UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)
Feb 25 14:16:48 laptop kernel: UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)
Feb 25 14:16:48 laptop kernel: NET: Registered PF_UNIX/PF_LOCAL protocol family
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: can't claim BAR 6 [mem 0xfff80000-0xffffffff pref]: no compatible bridge window
Feb 25 14:16:48 laptop kernel: pci 0000:00:15.0: BAR 0: assigned [mem 0x9d800000-0x9d800fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:00:15.1: BAR 0: assigned [mem 0x9d801000-0x9d801fff 64bit]
Feb 25 14:16:48 laptop kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xc3000000-0xc307ffff pref]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0: PCI bridge to [bus 01-05]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0:   bridge window [io  0x4000-0x4fff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xc3000000-0xc4ffffff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xb0000000-0xc1ffffff 64bit pref]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.0: PCI bridge to [bus 06]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.0:   bridge window [mem 0xc5200000-0xc52fffff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.5: PCI bridge to [bus 07]
Feb 25 14:16:48 laptop kernel: pci 0000:08:00.0: BAR 6: assigned [mem 0xc5110000-0xc511ffff pref]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6: PCI bridge to [bus 08]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6:   bridge window [io  0x3000-0x3fff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:1d.6:   bridge window [mem 0xc5100000-0xc51fffff]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: resource 7 [mem 0x9d800000-0xdfffffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:00: resource 8 [mem 0xfc800000-0xfe7fffff window]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:01: resource 0 [io  0x4000-0x4fff]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:01: resource 1 [mem 0xc3000000-0xc4ffffff]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:01: resource 2 [mem 0xb0000000-0xc1ffffff 64bit pref]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:06: resource 1 [mem 0xc5200000-0xc52fffff]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:08: resource 0 [io  0x3000-0x3fff]
Feb 25 14:16:48 laptop kernel: pci_bus 0000:08: resource 1 [mem 0xc5100000-0xc51fffff]
Feb 25 14:16:48 laptop kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Feb 25 14:16:48 laptop kernel: PCI: CLS 64 bytes, default 64
Feb 25 14:16:48 laptop kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 25 14:16:48 laptop kernel: software IO TLB: mapped [mem 0x0000000087d15000-0x000000008bd15000] (64MB)
Feb 25 14:16:48 laptop kernel: Unpacking initramfs...
Feb 25 14:16:48 laptop kernel: Freeing initrd memory: 92K
Feb 25 14:16:48 laptop kernel: RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
Feb 25 14:16:48 laptop kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
Feb 25 14:16:48 laptop kernel: RAPL PMU: hw unit of domain package 2^-14 Joules
Feb 25 14:16:48 laptop kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules
Feb 25 14:16:48 laptop kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
Feb 25 14:16:48 laptop kernel: RAPL PMU: hw unit of domain psys 2^-14 Joules
Feb 25 14:16:48 laptop kernel: Initialise system trusted keyrings
Feb 25 14:16:48 laptop kernel: workingset: timestamp_bits=62 max_order=23 bucket_order=0
Feb 25 14:16:48 laptop kernel: Key type cifs.spnego registered
Feb 25 14:16:48 laptop kernel: Key type cifs.idmap registered
Feb 25 14:16:48 laptop kernel: fuse: init (API version 7.35)
Feb 25 14:16:48 laptop kernel: NET: Registered PF_ALG protocol family
Feb 25 14:16:48 laptop kernel: Key type asymmetric registered
Feb 25 14:16:48 laptop kernel: Asymmetric key parser 'x509' registered
Feb 25 14:16:48 laptop kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 25 14:16:48 laptop kernel: io scheduler mq-deadline registered
Feb 25 14:16:48 laptop kernel: Monitor-Mwait will be used to enter C-1 state
Feb 25 14:16:48 laptop kernel: Monitor-Mwait will be used to enter C-2 state
Feb 25 14:16:48 laptop kernel: Monitor-Mwait will be used to enter C-3 state
Feb 25 14:16:48 laptop kernel: ACPI: \_SB_.PR00: Found 3 idle states
Feb 25 14:16:48 laptop kernel: ACPI: AC: AC Adapter [AC] (on-line)
Feb 25 14:16:48 laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
Feb 25 14:16:48 laptop kernel: ACPI: button: Power Button [PWRB]
Feb 25 14:16:48 laptop kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
Feb 25 14:16:48 laptop kernel: ACPI: button: Sleep Button [SLPB]
Feb 25 14:16:48 laptop kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
Feb 25 14:16:48 laptop kernel: ACPI: button: Lid Switch [LID0]
Feb 25 14:16:48 laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
Feb 25 14:16:48 laptop kernel: ACPI: button: Power Button [PWRF]
Feb 25 14:16:48 laptop kernel: ACPI: \_TZ_.TZ0_: Invalid active0 threshold
Feb 25 14:16:48 laptop kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 25 14:16:48 laptop kernel: ACPI: thermal: Thermal Zone [TZ0] (25 C)
Feb 25 14:16:48 laptop kernel: ACPI: battery: Slot [BAT0] (battery present)
Feb 25 14:16:48 laptop kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Feb 25 14:16:48 laptop kernel: Linux agpgart interface v0.103
Feb 25 14:16:48 laptop kernel: ACPI: bus type drm_connector registered
Feb 25 14:16:48 laptop kernel: rtsx_pci 0000:08:00.0: enabling device (0000 -> 0002)
Feb 25 14:16:48 laptop kernel: nvme 0000:06:00.0: platform quirk: setting simple suspend
Feb 25 14:16:48 laptop kernel: nvme nvme0: pci function 0000:06:00.0
Feb 25 14:16:48 laptop kernel: ahci 0000:00:17.0: version 3.0
Feb 25 14:16:48 laptop kernel: nvme nvme0: allocated 32 MiB host memory buffer.
Feb 25 14:16:48 laptop kernel: nvme nvme0: 12/0/0 default/read/poll queues
Feb 25 14:16:48 laptop kernel: ahci 0000:00:17.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x10 impl SATA mode
Feb 25 14:16:48 laptop kernel: ahci 0000:00:17.0: flags: 64bit ncq sntf pm clo only pio slum part ems deso sadm sds apst 
Feb 25 14:16:48 laptop kernel: scsi host0: ahci
Feb 25 14:16:48 laptop kernel: scsi host1: ahci
Feb 25 14:16:48 laptop kernel: scsi host2: ahci
Feb 25 14:16:48 laptop kernel: scsi host3: ahci
Feb 25 14:16:48 laptop kernel: scsi host4: ahci
Feb 25 14:16:48 laptop kernel: ata1: DUMMY
Feb 25 14:16:48 laptop kernel: ata2: DUMMY
Feb 25 14:16:48 laptop kernel: ata3: DUMMY
Feb 25 14:16:48 laptop kernel: ata4: DUMMY
Feb 25 14:16:48 laptop kernel: ata5: SATA max UDMA/133 abar m2048@0xc53a3000 port 0xc53a3300 irq 122
Feb 25 14:16:48 laptop kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 25 14:16:48 laptop kernel: ehci-pci: EHCI PCI platform driver
Feb 25 14:16:48 laptop kernel: uhci_hcd: USB Universal Host Controller Interface driver
Feb 25 14:16:48 laptop kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Feb 25 14:16:48 laptop kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
Feb 25 14:16:48 laptop kernel:  nvme0n1: p1 p2 p3 p4 p5 p6 p7 p8
Feb 25 14:16:48 laptop kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000000009810
Feb 25 14:16:48 laptop kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.16
Feb 25 14:16:48 laptop kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 25 14:16:48 laptop kernel: usb usb1: Product: xHCI Host Controller
Feb 25 14:16:48 laptop kernel: usb usb1: Manufacturer: Linux 5.16.0-rc5+ xhci-hcd
Feb 25 14:16:48 laptop kernel: usb usb1: SerialNumber: 0000:00:14.0
Feb 25 14:16:48 laptop kernel: hub 1-0:1.0: USB hub found
Feb 25 14:16:48 laptop kernel: hub 1-0:1.0: 16 ports detected
Feb 25 14:16:48 laptop kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Feb 25 14:16:48 laptop kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
Feb 25 14:16:48 laptop kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed
Feb 25 14:16:48 laptop kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.16
Feb 25 14:16:48 laptop kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 25 14:16:48 laptop kernel: usb usb2: Product: xHCI Host Controller
Feb 25 14:16:48 laptop kernel: usb usb2: Manufacturer: Linux 5.16.0-rc5+ xhci-hcd
Feb 25 14:16:48 laptop kernel: usb usb2: SerialNumber: 0000:00:14.0
Feb 25 14:16:48 laptop kernel: hub 2-0:1.0: USB hub found
Feb 25 14:16:48 laptop kernel: hub 2-0:1.0: 8 ports detected
Feb 25 14:16:48 laptop kernel: usb: port power management may be unreliable
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver usb-storage
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver ums-realtek
Feb 25 14:16:48 laptop kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
Feb 25 14:16:48 laptop kernel: i8042: Detected active multiplexing controller, rev 1.1
Feb 25 14:16:48 laptop kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 25 14:16:48 laptop kernel: serio: i8042 AUX0 port at 0x60,0x64 irq 12
Feb 25 14:16:48 laptop kernel: serio: i8042 AUX1 port at 0x60,0x64 irq 12
Feb 25 14:16:48 laptop kernel: serio: i8042 AUX2 port at 0x60,0x64 irq 12
Feb 25 14:16:48 laptop kernel: serio: i8042 AUX3 port at 0x60,0x64 irq 12
Feb 25 14:16:48 laptop kernel: mousedev: PS/2 mouse device common for all mice
Feb 25 14:16:48 laptop kernel: rtc_cmos 00:04: RTC can wake from S4
Feb 25 14:16:48 laptop kernel: rtc_cmos 00:04: registered as rtc0
Feb 25 14:16:48 laptop kernel: rtc_cmos 00:04: setting system clock to 2022-02-25T14:16:43 UTC (1645798603)
Feb 25 14:16:48 laptop kernel: rtc_cmos 00:04: alarms up to one month, y3k, 242 bytes nvram
Feb 25 14:16:48 laptop kernel: i2c_dev: i2c /dev entries driver
Feb 25 14:16:48 laptop kernel: intel_pstate: Intel P-state driver initializing
Feb 25 14:16:48 laptop kernel: intel_pstate: HWP enabled
Feb 25 14:16:48 laptop kernel: efifb: probing for efifb
Feb 25 14:16:48 laptop kernel: efifb: framebuffer at 0xa0000000, using 8128k, total 8128k
Feb 25 14:16:48 laptop kernel: efifb: mode is 1920x1080x32, linelength=7680, pages=1
Feb 25 14:16:48 laptop kernel: efifb: scrolling: redraw
Feb 25 14:16:48 laptop kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 25 14:16:48 laptop kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
Feb 25 14:16:48 laptop kernel: Console: switching to colour frame buffer device 240x67
Feb 25 14:16:48 laptop kernel: fb0: EFI VGA frame buffer device
Feb 25 14:16:48 laptop kernel: NET: Registered PF_PACKET protocol family
Feb 25 14:16:48 laptop kernel: NET: Registered PF_KEY protocol family
Feb 25 14:16:48 laptop kernel: Key type dns_resolver registered
Feb 25 14:16:48 laptop kernel: microcode: sig=0xa0652, pf=0x20, revision=0xea
Feb 25 14:16:48 laptop kernel: microcode: Microcode Update Driver: v2.2.
Feb 25 14:16:48 laptop kernel: IPI shorthand broadcast: enabled
Feb 25 14:16:48 laptop kernel: AVX2 version of gcm_enc/dec engaged.
Feb 25 14:16:48 laptop kernel: AES CTR mode by8 optimization enabled
Feb 25 14:16:48 laptop kernel: sched_clock: Marking stable (1031587700, 5545988)->(1053381787, -16248099)
Feb 25 14:16:48 laptop kernel: registered taskstats version 1
Feb 25 14:16:48 laptop kernel: Loading compiled-in X.509 certificates
Feb 25 14:16:48 laptop kernel: usb 1-1: new full-speed USB device number 2 using xhci_hcd
Feb 25 14:16:48 laptop kernel: tsc: Refined TSC clocksource calibration: 2591.998 MHz
Feb 25 14:16:48 laptop kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x255cb518234, max_idle_ns: 440795279333 ns
Feb 25 14:16:48 laptop kernel: clocksource: Switched to clocksource tsc
Feb 25 14:16:48 laptop kernel: usb 1-1: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.01
Feb 25 14:16:48 laptop kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 25 14:16:48 laptop kernel: usb 1-1: Product: USB Receiver
Feb 25 14:16:48 laptop kernel: usb 1-1: Manufacturer: Logitech
Feb 25 14:16:48 laptop kernel: mmc0: cannot verify signal voltage switch
Feb 25 14:16:48 laptop kernel: usb 1-8: new high-speed USB device number 3 using xhci_hcd
Feb 25 14:16:48 laptop kernel: mmc0: new ultra high speed SDR104 SDHC card at address 59b4
Feb 25 14:16:48 laptop kernel: mmcblk0: mmc0:59b4 SDU1  14.7 GiB 
Feb 25 14:16:48 laptop kernel:  mmcblk0: p1
Feb 25 14:16:48 laptop kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 14:16:48 laptop kernel: ata5.00: ATA-10: ST2000LM015-2E8174, 0001, max UDMA/133
Feb 25 14:16:48 laptop kernel: usb 1-8: New USB device found, idVendor=04f2, idProduct=b685, bcdDevice=54.04
Feb 25 14:16:48 laptop kernel: usb 1-8: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Feb 25 14:16:48 laptop kernel: usb 1-8: Product: Chicony USB2.0 Camera
Feb 25 14:16:48 laptop kernel: usb 1-8: Manufacturer: Sonix Technology Co., Ltd.
Feb 25 14:16:48 laptop kernel: ata5.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Feb 25 14:16:48 laptop kernel: ata5.00: configured for UDMA/133
Feb 25 14:16:48 laptop kernel: scsi 4:0:0:0: Direct-Access     ATA      ST2000LM015-2E81 0001 PQ: 0 ANSI: 5
Feb 25 14:16:48 laptop kernel: scsi 4:0:0:0: Attached scsi generic sg0 type 0
Feb 25 14:16:48 laptop kernel: sd 4:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Feb 25 14:16:48 laptop kernel: sd 4:0:0:0: [sda] 4096-byte physical blocks
Feb 25 14:16:48 laptop kernel: sd 4:0:0:0: [sda] Write Protect is off
Feb 25 14:16:48 laptop kernel: sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 25 14:16:48 laptop kernel: sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 25 14:16:48 laptop kernel:  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
Feb 25 14:16:48 laptop kernel: sd 4:0:0:0: [sda] Attached SCSI disk
Feb 25 14:16:48 laptop kernel: usb 1-14: new full-speed USB device number 4 using xhci_hcd
Feb 25 14:16:48 laptop kernel: ALSA device list:
Feb 25 14:16:48 laptop kernel:   No soundcards found.
Feb 25 14:16:48 laptop kernel: EXT4-fs (nvme0n1p4): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop kernel: VFS: Mounted root (ext4 filesystem) readonly on device 259:4.
Feb 25 14:16:48 laptop kernel: devtmpfs: mounted
Feb 25 14:16:48 laptop kernel: Freeing unused kernel image (initmem) memory: 1008K
Feb 25 14:16:48 laptop kernel: Write protecting the kernel read-only data: 16384k
Feb 25 14:16:48 laptop kernel: Freeing unused kernel image (text/rodata gap) memory: 2044K
Feb 25 14:16:48 laptop kernel: Freeing unused kernel image (rodata/data gap) memory: 1548K
Feb 25 14:16:48 laptop kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
Feb 25 14:16:48 laptop kernel: Run /sbin/init as init process
Feb 25 14:16:48 laptop kernel:   with arguments:
Feb 25 14:16:48 laptop kernel:     /sbin/init
Feb 25 14:16:48 laptop kernel:   with environment:
Feb 25 14:16:48 laptop kernel:     HOME=/
Feb 25 14:16:48 laptop kernel:     TERM=linux
Feb 25 14:16:48 laptop kernel:     BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+
Feb 25 14:16:48 laptop kernel:     apm=power_off
Feb 25 14:16:48 laptop kernel: random: fast init done
Feb 25 14:16:48 laptop kernel: tun: Universal TUN/TAP device driver, 1.6
Feb 25 14:16:48 laptop kernel: usb 1-14: New USB device found, idVendor=8087, idProduct=0026, bcdDevice= 0.02
Feb 25 14:16:48 laptop kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 25 14:16:48 laptop kernel: <30>udevd[308]: starting version 3.2.11
Feb 25 14:16:48 laptop kernel: random: udevd: uninitialized urandom read (16 bytes read)
Feb 25 14:16:48 laptop last message repeated 2 times
Feb 25 14:16:48 laptop kernel: <30>udevd[309]: starting eudev-3.2.11
Feb 25 14:16:48 laptop kernel: wmi_bus wmi_bus-PNP0C14:01: WQ data block query control method not found
Feb 25 14:16:48 laptop last message repeated 3 times
Feb 25 14:16:48 laptop kernel: acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:03)
Feb 25 14:16:48 laptop kernel: mei_me 0000:00:16.0: enabling device (0000 -> 0002)
Feb 25 14:16:48 laptop kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Feb 25 14:16:48 laptop kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Feb 25 14:16:48 laptop kernel: Intel(R) Wireless WiFi driver for Linux
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver btusb
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Device revision is 2
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-69.ucode failed with error -2
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Secure boot is enabled
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-68.ucode failed with error -2
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: OTP lock is enabled
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: API lock is enabled
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Debug lock is disabled
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: loaded firmware version 67.8f59b80b.0 QuZ-a0-hr-b0-67.ucode op_mode iwlmvm
Feb 25 14:16:48 laptop kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C534.0001/input/input9
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
Feb 25 14:16:48 laptop kernel: intel-lpss 0000:00:15.0: enabling device (0004 -> 0006)
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Boot Address: 0x24800
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Firmware Version: 125-46.21
Feb 25 14:16:48 laptop kernel: intel-lpss 0000:00:15.1: enabling device (0004 -> 0006)
Feb 25 14:16:48 laptop kernel: checking generic (a0000000 7f0000) vs hw (c2000000 1000000)
Feb 25 14:16:48 laptop kernel: checking generic (a0000000 7f0000) vs hw (a0000000 10000000)
Feb 25 14:16:48 laptop kernel: fb0: switching to i915 from EFI VGA
Feb 25 14:16:48 laptop kernel: Console: switching to colour dummy device 80x25
Feb 25 14:16:48 laptop kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Feb 25 14:16:48 laptop kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
Feb 25 14:16:48 laptop kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
Feb 25 14:16:48 laptop kernel: i801_smbus 0000:00:1f.4: SPD Write Disable is set
Feb 25 14:16:48 laptop kernel: i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
Feb 25 14:16:48 laptop kernel: i2c i2c-4: 2/2 memory slots populated (from DMI)
Feb 25 14:16:48 laptop kernel: i2c i2c-4: Successfully instantiated SPD at 0x50
Feb 25 14:16:48 laptop kernel: usb 1-8: Found UVC 1.00 device Chicony USB2.0 Camera (04f2:b685)
Feb 25 14:16:48 laptop kernel: snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351
Feb 25 14:16:48 laptop kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver uvcvideo
Feb 25 14:16:48 laptop kernel: hid-generic 0003:046D:C534.0001: input: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-1/input0
Feb 25 14:16:48 laptop kernel: input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/input/input10
Feb 25 14:16:48 laptop kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/input/input11
Feb 25 14:16:48 laptop kernel: i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
Feb 25 14:16:48 laptop kernel: i915 0000:00:02.0: [drm] [ENCODER:117:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it
Feb 25 14:16:48 laptop kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
Feb 25 14:16:48 laptop kernel: ACPI: video: Video Device [PEGP] (multi-head: no  rom: yes  post: no)
Feb 25 14:16:48 laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input15
Feb 25 14:16:48 laptop kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/input/input12
Feb 25 14:16:48 laptop kernel: hid-generic 0003:046D:C534.0002: input,hiddev96: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-1/input1
Feb 25 14:16:48 laptop kernel: usbcore: registered new interface driver usbhid
Feb 25 14:16:48 laptop kernel: usbhid: USB HID core driver
Feb 25 14:16:48 laptop kernel: ACPI: video: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Feb 25 14:16:48 laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input16
Feb 25 14:16:48 laptop kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Feb 25 14:16:48 laptop kernel: fbcon: i915 (fb0) is primary device
Feb 25 14:16:48 laptop kernel: Console: switching to colour frame buffer device 240x67
Feb 25 14:16:48 laptop kernel: i915 0000:00:02.0: [drm] fb0: i915 frame buffer device
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC293: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x18
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:      Headset Mic=0x1a
Feb 25 14:16:48 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12
Feb 25 14:16:48 laptop kernel: iwlwifi 0000:00:14.3: base HW address: 34:7d:f6:df:83:1a
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input21
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input22
Feb 25 14:16:48 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input23
Feb 25 14:16:48 laptop kernel: urandom_read: 6 callbacks suppressed
Feb 25 14:16:48 laptop kernel: random: udevd: uninitialized urandom read (16 bytes read)
Feb 25 14:16:48 laptop kernel: random: crng init done
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Waiting for firmware download to complete
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Firmware loaded in 1546001 usecs
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Waiting for device to boot
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Device booted in 13899 usecs
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Feb 25 14:16:48 laptop kernel: Bluetooth: hci0: Firmware revision 0.4 build 125 week 46 2021
Feb 25 14:16:48 laptop kernel: Adding 65535996k swap on /dev/sda5.  Priority:1 extents:1 across:65535996k 
Feb 25 14:16:48 laptop kernel: EXT4-fs (nvme0n1p4): re-mounted. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop kernel: EXT4-fs (nvme0n1p4): re-mounted. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop kernel: ntfs3: Max link count 4000
Feb 25 14:16:48 laptop kernel: EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop kernel: EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 14:16:48 laptop acpid: starting up with netlink and the input layer
Feb 25 14:16:48 laptop acpid: 3 rules loaded
Feb 25 14:16:48 laptop acpid: waiting for events: event logging is off
Feb 25 14:16:50 laptop kernel: wlan0: authenticate with DE:AD:BE:EF:7c:25
Feb 25 14:16:50 laptop kernel: wlan0: send auth to DE:AD:BE:EF:7c:25 (try 1/3)
Feb 25 14:16:50 laptop kernel: wlan0: authenticated
Feb 25 14:16:50 laptop kernel: wlan0: associate with DE:AD:BE:EF:7c:25 (try 1/3)
Feb 25 14:16:50 laptop kernel: wlan0: RX AssocResp from DE:AD:BE:EF:7c:25 (capab=0x1011 status=0 aid=1)
Feb 25 14:16:50 laptop kernel: wlan0: associated
Feb 25 14:16:50 laptop kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by DE:AD:BE:EF:7c:25
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/bftpd [file=/etc/xinetd.conf] [line=15]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.d/chargen] [line=11]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/cups-lpd [file=/etc/xinetd.d/cups-lpd] [line=25]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=12]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/ssh [file=/etc/xinetd.d/ssh] [line=25]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/sysstat [file=/etc/xinetd.d/sysstat] [line=14]
Feb 25 14:16:50 laptop xinetd[1041]: Reading included configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=15]
Feb 25 14:16:50 laptop xinetd[1041]: removing chargen
Feb 25 14:16:50 laptop xinetd[1041]: removing chargen
Feb 25 14:16:50 laptop xinetd[1041]: removing printer
Feb 25 14:16:50 laptop xinetd[1041]: removing daytime
Feb 25 14:16:50 laptop xinetd[1041]: removing daytime
Feb 25 14:16:50 laptop xinetd[1041]: removing echo
Feb 25 14:16:50 laptop xinetd[1041]: removing echo
Feb 25 14:16:50 laptop xinetd[1041]: removing systat
Feb 25 14:16:50 laptop xinetd[1041]: removing time
Feb 25 14:16:50 laptop xinetd[1041]: removing time
Feb 25 14:16:50 laptop xinetd[1041]: xinetd Version 2.3.15 started with loadavg options compiled in.
Feb 25 14:16:50 laptop xinetd[1041]: Started working: 2 available services
Feb 25 14:16:50 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.ColorManager' requested by ':1.1' (uid=0 pid=1063 comm="/usr/sbin/cupsd -C /etc/cups/cupsd.conf -s /etc/cu") (using servicehelper)
Feb 25 14:16:50 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Feb 25 14:16:50 laptop bluetoothd[1094]: Bluetooth daemon 5.63
Feb 25 14:16:50 laptop bluetoothd[1094]: Starting SDP server
Feb 25 14:16:50 laptop kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 25 14:16:50 laptop kernel: Bluetooth: BNEP filters: protocol multicast
Feb 25 14:16:50 laptop kernel: Bluetooth: BNEP socket layer initialized
Feb 25 14:16:50 laptop bluetoothd[1094]: Bluetooth management interface 1.21 initialized
Feb 25 14:16:50 laptop nmbd[1128]: [2022/02/25 14:16:50.693604,  0] ../../source3/nmbd/nmbd.c:901(main) 
Feb 25 14:16:50 laptop nmbd[1128]:   nmbd version 4.15.5 started. 
Feb 25 14:16:50 laptop nmbd[1128]:   Copyright Andrew Tridgell and the Samba Team 1992-2021 
Feb 25 14:16:50 laptop smbd[1148]: [2022/02/25 14:16:50.731684,  0] ../../source3/smbd/server.c:1734(main) 
Feb 25 14:16:50 laptop smbd[1148]:   smbd version 4.15.5 started. 
Feb 25 14:16:50 laptop smbd[1148]:   Copyright Andrew Tridgell and the Samba Team 1992-2021 
Feb 25 14:16:50 laptop smbd[1149]: [2022/02/25 14:16:50.763818,  0] ../../source3/smbd/server.c:1082(smbd_open_one_socket) 
Feb 25 14:16:50 laptop smbd[1149]:   smbd_open_one_socket: open_socket_in failed: Address family not supported by protocol 
Feb 25 14:16:50 laptop smbd[1149]: [2022/02/25 14:16:50.764232,  0] ../../source3/smbd/server.c:1082(smbd_open_one_socket) 
Feb 25 14:16:50 laptop smbd[1149]:   smbd_open_one_socket: open_socket_in failed: Address family not supported by protocol 
Feb 25 14:16:50 laptop kernel: CIFS: Attempting to mount \\nas\Share
Feb 25 14:16:51 laptop nmbd[1129]: [2022/02/25 14:16:51.005187,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response) 
Feb 25 14:16:52 laptop bluetoothd[1094]: Loading LTKs timed out for hci0
Feb 25 14:16:54 laptop vnstatd[1356]: vnStat daemon 2.9 started. (pid:1356 uid:0 gid:0 64-bit)
Feb 25 14:16:54 laptop vnstatd[1356]: Monitoring (1): wlan0 (1000 Mbit) 
Feb 25 14:16:54 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.6' (uid=0 pid=1334 comm="/usr/bin/sddm ") (using servicehelper)
Feb 25 14:16:54 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 25 14:16:54 laptop acpid: client connected from 1365[0:0]
Feb 25 14:16:54 laptop acpid: 1 client rule loaded
Feb 25 14:16:54 laptop acpid: client connected from 1365[0:0]
Feb 25 14:16:54 laptop acpid: 1 client rule loaded
Feb 25 14:16:59 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.ConsoleKit' requested by ':1.8' (uid=1000 pid=1423 comm="ck-launch-session lxqt-session ") (using servicehelper)
Feb 25 14:16:59 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.9' (uid=0 pid=1454 comm="/usr/sbin/console-kit-daemon --no-daemon ") (using servicehelper)
Feb 25 14:16:59 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Feb 25 14:16:59 laptop polkitd[1460]: Started polkitd version 0.120
Feb 25 14:16:59 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 25 14:16:59 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Activating service name='org.kde.KScreen' requested by ':1.1' (uid=1000 pid=1512 comm="/usr/bin/lxqt-config-monitor -l ")
Feb 25 14:16:59 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Successfully activated service 'org.kde.KScreen'
Feb 25 14:16:59 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Activating service name='org.gtk.vfs.Daemon' requested by ':1.4' (uid=1000 pid=1516 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 14:16:59 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Successfully activated service 'org.gtk.vfs.Daemon'
Feb 25 14:16:59 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.4' (uid=1000 pid=1516 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 14:16:59 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.UDisks2' requested by ':1.26' (uid=1000 pid=1618 comm="/usr/libexec/gvfs-udisks2-volume-monitor ") (using servicehelper)
Feb 25 14:17:00 laptop pulseaudio[1615]: [pulseaudio] module-rescue-streams.c: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.
Feb 25 14:17:00 laptop kernel: Bluetooth: RFCOMM TTY layer initialized
Feb 25 14:17:00 laptop kernel: Bluetooth: RFCOMM socket layer initialized
Feb 25 14:17:00 laptop kernel: Bluetooth: RFCOMM ver 1.11
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Feb 25 14:17:00 laptop bluetoothd[1094]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Feb 25 14:17:00 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Activating service name='org.a11y.Bus' requested by ':1.21' (uid=1000 pid=1663 comm="/usr/bin/python3 /usr/bin/blueman-applet ")
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Successfully activated service 'org.a11y.Bus'
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Activating service name='org.gtk.vfs.GPhoto2VolumeMonitor' requested by ':1.4' (uid=1000 pid=1516 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Activating service name='org.gtk.vfs.MTPVolumeMonitor' requested by ':1.4' (uid=1000 pid=1516 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 14:17:00 laptop dbus-daemon[1445]: [session uid=1000 pid=1443] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Feb 25 14:17:03 laptop kernel: EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: disabled.

[-- Attachment #9: sys.log.good --]
[-- Type: text/plain, Size: 77536 bytes --]

Feb 25 13:58:19 laptop syslogd 1.5.1: restart.
Feb 25 13:58:19 laptop kernel: klogd 1.5.1, log source = /proc/kmsg started.
Feb 25 13:58:19 laptop kernel: Inspecting /boot/System.map-5.16.0-rc5+
Feb 25 13:58:19 laptop kernel: Cannot find map file.
Feb 25 13:58:19 laptop kernel: Loaded 48003 symbols from 47 modules.
Feb 25 13:58:19 laptop kernel: microcode: microcode updated early to revision 0xea, date = 2021-02-07
Feb 25 13:58:19 laptop kernel: Linux version 5.16.0-rc5+ (chris@laptop) (gcc (GCC) 11.2.1 20220219, GNU ld (GNU Binutils) 2.38) #907 SMP PREEMPT Fri Feb 25 11:29:24 GMT 2022
Feb 25 13:58:19 laptop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+ ro root=PARTUUID=f927883a-e95c-4cdd-b64e-a0a778216b9f resume=PARTUUID=70ccedc5-d788-42bc-9f13-81e2beb61338 apm=power_off rootfstype=ext4 net.ifnames=0
Feb 25 13:58:19 laptop kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Feb 25 13:58:19 laptop kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Feb 25 13:58:19 laptop kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Feb 25 13:58:19 laptop kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Feb 25 13:58:19 laptop kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Feb 25 13:58:19 laptop kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Feb 25 13:58:19 laptop kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Feb 25 13:58:19 laptop kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Feb 25 13:58:19 laptop kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Feb 25 13:58:19 laptop kernel: x86/fpu: xstate_offset[9]:  960, xstate_sizes[9]:    8
Feb 25 13:58:19 laptop kernel: x86/fpu: Enabled xstate features 0x21f, context size is 968 bytes, using 'compacted' format.
Feb 25 13:58:19 laptop kernel: signal: max sigframe size: 3632
Feb 25 13:58:19 laptop kernel: BIOS-provided physical RAM map:
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007e1d8fff] usable
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000007e1d9000-0x000000007ead8fff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000007ead9000-0x000000008cceefff] usable
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000008ccef000-0x000000008d0befff] type 20
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000008d0bf000-0x000000008eedefff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000008eedf000-0x000000008fbcefff] ACPI NVS
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000008fbcf000-0x000000008fc4efff] ACPI data
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000008fc4f000-0x000000008fc4ffff] usable
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x000000008fc50000-0x000000009d7fffff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x00000000ff400000-0x00000000ffffffff] reserved
Feb 25 13:58:19 laptop kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008607fffff] usable
Feb 25 13:58:19 laptop kernel: NX (Execute Disable) protection: active
Feb 25 13:58:19 laptop kernel: efi: EFI v2.70 by INSYDE Corp.
Feb 25 13:58:19 laptop kernel: efi: ACPI=0x8fc4e000 ACPI 2.0=0x8fc4e014 TPMFinalLog=0x8fbc5000 SMBIOS=0x8d1e4000 SMBIOS 3.0=0x8d1e2000 ESRT=0x8d1e5998 MEMATTR=0x79ea3018 
Feb 25 13:58:19 laptop kernel: SMBIOS 3.2.0 present.
Feb 25 13:58:19 laptop kernel: DMI: Notebook                         NP50DE_DB                       /NP50DE_DB                       , BIOS 1.07.04 02/17/2020
Feb 25 13:58:19 laptop kernel: tsc: Detected 2600.000 MHz processor
Feb 25 13:58:19 laptop kernel: tsc: Detected 2599.992 MHz TSC
Feb 25 13:58:19 laptop kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 25 13:58:19 laptop kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 25 13:58:19 laptop kernel: last_pfn = 0x860800 max_arch_pfn = 0x400000000
Feb 25 13:58:19 laptop kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Feb 25 13:58:19 laptop kernel: last_pfn = 0x8fc50 max_arch_pfn = 0x400000000
Feb 25 13:58:19 laptop kernel: esrt: Reserving ESRT space from 0x000000008d1e5998 to 0x000000008d1e5a48.
Feb 25 13:58:19 laptop kernel: Using GB pages for direct mapping
Feb 25 13:58:19 laptop kernel: Secure boot disabled
Feb 25 13:58:19 laptop kernel: RAMDISK: [mem 0x37fc1000-0x37fd7fff]
Feb 25 13:58:19 laptop kernel: ACPI: Early table checksum verification disabled
Feb 25 13:58:19 laptop kernel: ACPI: RSDP 0x000000008FC4E014 000024 (v02 INSYDE)
Feb 25 13:58:19 laptop kernel: ACPI: XSDT 0x000000008FBF9188 0000DC (v01 INSYDE CML      00000002      01000013)
Feb 25 13:58:19 laptop kernel: ACPI: FACP 0x000000008FC37000 00010C (v05 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: DSDT 0x000000008FC00000 03337F (v02 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: FACS 0x000000008FB47000 000040
Feb 25 13:58:19 laptop kernel: ACPI: UEFI 0x000000008FBCE000 000236 (v01 INSYDE CML      00000001 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC4A000 002087 (v02 CpuRef CpuSsdt  00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC46000 003158 (v02 SaSsdt SaSsdt   00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC44000 001848 (v02 PegSsd PegSsdt  00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC43000 000790 (v02 INSYDE Tpm2Tabl 00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: TPM2 0x000000008FC42000 000034 (v04 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: LPIT 0x000000008FC40000 000094 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: WSMT 0x000000008FC3F000 000028 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC3D000 001616 (v02 INSYDE PtidDevc 00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: DBGP 0x000000008FC3C000 000034 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: DBG2 0x000000008FC3B000 00005C (v00 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC3A000 000502 (v02 Intel  PerfTune 00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: NHLT 0x000000008FC38000 001821 (v00 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: HPET 0x000000008FC36000 000038 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: APIC 0x000000008FC35000 000164 (v03 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: MCFG 0x000000008FC34000 00003C (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FBFF000 000E58 (v02 INSYDE ClevoRTD 00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FBFA000 0039F7 (v01 Insyde NvdTable 00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0x000000008FC4D000 000164 (v01 INSYDE PcdTabl  00001000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: DMAR 0x000000008FBFE000 0000A8 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: FPDT 0x000000008FBF8000 000044 (v01 INSYDE CML      00000002 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: BGRT 0x000000008FBF7000 000038 (v01 INSYDE CML      00000001 ACPI 00040000)
Feb 25 13:58:19 laptop kernel: ACPI: Reserving FACP table memory at [mem 0x8fc37000-0x8fc3710b]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving DSDT table memory at [mem 0x8fc00000-0x8fc3337e]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving FACS table memory at [mem 0x8fb47000-0x8fb4703f]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving UEFI table memory at [mem 0x8fbce000-0x8fbce235]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc4a000-0x8fc4c086]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc46000-0x8fc49157]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc44000-0x8fc45847]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc43000-0x8fc4378f]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving TPM2 table memory at [mem 0x8fc42000-0x8fc42033]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving LPIT table memory at [mem 0x8fc40000-0x8fc40093]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving WSMT table memory at [mem 0x8fc3f000-0x8fc3f027]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc3d000-0x8fc3e615]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving DBGP table memory at [mem 0x8fc3c000-0x8fc3c033]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving DBG2 table memory at [mem 0x8fc3b000-0x8fc3b05b]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc3a000-0x8fc3a501]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving NHLT table memory at [mem 0x8fc38000-0x8fc39820]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving HPET table memory at [mem 0x8fc36000-0x8fc36037]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving APIC table memory at [mem 0x8fc35000-0x8fc35163]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving MCFG table memory at [mem 0x8fc34000-0x8fc3403b]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fbff000-0x8fbffe57]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fbfa000-0x8fbfd9f6]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving SSDT table memory at [mem 0x8fc4d000-0x8fc4d163]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving DMAR table memory at [mem 0x8fbfe000-0x8fbfe0a7]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving FPDT table memory at [mem 0x8fbf8000-0x8fbf8043]
Feb 25 13:58:19 laptop kernel: ACPI: Reserving BGRT table memory at [mem 0x8fbf7000-0x8fbf7037]
Feb 25 13:58:19 laptop kernel: Zone ranges:
Feb 25 13:58:19 laptop kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Feb 25 13:58:19 laptop kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Feb 25 13:58:19 laptop kernel:   Normal   [mem 0x0000000100000000-0x00000008607fffff]
Feb 25 13:58:19 laptop kernel: Movable zone start for each node
Feb 25 13:58:19 laptop kernel: Early memory node ranges
Feb 25 13:58:19 laptop kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Feb 25 13:58:19 laptop kernel:   node   0: [mem 0x0000000000100000-0x000000007e1d8fff]
Feb 25 13:58:19 laptop kernel:   node   0: [mem 0x000000007ead9000-0x000000008cceefff]
Feb 25 13:58:19 laptop kernel:   node   0: [mem 0x000000008fc4f000-0x000000008fc4ffff]
Feb 25 13:58:19 laptop kernel:   node   0: [mem 0x0000000100000000-0x00000008607fffff]
Feb 25 13:58:19 laptop kernel: Initmem setup node 0 [mem 0x0000000000001000-0x00000008607fffff]
Feb 25 13:58:19 laptop kernel: On node 0, zone DMA: 1 pages in unavailable ranges
Feb 25 13:58:19 laptop kernel: On node 0, zone DMA: 97 pages in unavailable ranges
Feb 25 13:58:19 laptop kernel: On node 0, zone DMA32: 2304 pages in unavailable ranges
Feb 25 13:58:19 laptop kernel: On node 0, zone DMA32: 12128 pages in unavailable ranges
Feb 25 13:58:19 laptop kernel: On node 0, zone Normal: 944 pages in unavailable ranges
Feb 25 13:58:19 laptop kernel: On node 0, zone Normal: 30720 pages in unavailable ranges
Feb 25 13:58:19 laptop kernel: Reserving Intel graphics memory at [mem 0x99800000-0x9d7fffff]
Feb 25 13:58:19 laptop kernel: ACPI: PM-Timer IO Port: 0x1808
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: ACPI: LAPIC_NMI (acpi_id[0x14] high edge lint[0x1])
Feb 25 13:58:19 laptop kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
Feb 25 13:58:19 laptop kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 25 13:58:19 laptop kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 25 13:58:19 laptop kernel: ACPI: Using ACPI (MADT) for SMP configuration information
Feb 25 13:58:19 laptop kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
Feb 25 13:58:19 laptop kernel: TSC deadline timer available
Feb 25 13:58:19 laptop kernel: smpboot: Allowing 12 CPUs, 0 hotplug CPUs
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x000fffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x7e1d9000-0x7ead8fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8ccef000-0x8d0befff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8d0bf000-0x8eedefff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8eedf000-0x8fbcefff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8fbcf000-0x8fc4efff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x8fc50000-0x9d7fffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0x9d800000-0xdfffffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xefffffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xf0000000-0xfdffffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfe000000-0xfe010fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfe011000-0xfed0ffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed10000-0xfed19fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed1a000-0xfed83fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed84000-0xfed84fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfed85000-0xfedfffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xff3fffff]
Feb 25 13:58:19 laptop kernel: PM: hibernation: Registered nosave memory: [mem 0xff400000-0xffffffff]
Feb 25 13:58:19 laptop kernel: [mem 0x9d800000-0xdfffffff] available for PCI devices
Feb 25 13:58:19 laptop kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Feb 25 13:58:19 laptop kernel: setup_percpu: NR_CPUS:12 nr_cpumask_bits:12 nr_cpu_ids:12 nr_node_ids:1
Feb 25 13:58:19 laptop kernel: percpu: Embedded 44 pages/cpu s140440 r8192 d31592 u262144
Feb 25 13:58:19 laptop kernel: pcpu-alloc: s140440 r8192 d31592 u262144 alloc=1*2097152
Feb 25 13:58:19 laptop kernel: pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 -- -- -- -- 
Feb 25 13:58:19 laptop kernel: Built 1 zonelists, mobility grouping on.  Total pages: 8179648
Feb 25 13:58:19 laptop kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+ ro root=PARTUUID=f927883a-e95c-4cdd-b64e-a0a778216b9f resume=PARTUUID=70ccedc5-d788-42bc-9f13-81e2beb61338 apm=power_off rootfstype=ext4 net.ifnames=0
Feb 25 13:58:19 laptop kernel: Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+ apm=power_off", will be passed to user space.
Feb 25 13:58:19 laptop kernel: Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
Feb 25 13:58:19 laptop kernel: Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
Feb 25 13:58:19 laptop kernel: mem auto-init: stack:off, heap alloc:off, heap free:off
Feb 25 13:58:19 laptop kernel: Memory: 32517468K/33238584K available (10242K kernel code, 1120K rwdata, 2548K rodata, 1008K init, 892K bss, 720856K reserved, 0K cma-reserved)
Feb 25 13:58:19 laptop kernel: random: get_random_u64 called from __kmem_cache_create+0x1f/0x470 with crng_init=0
Feb 25 13:58:19 laptop kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=12, Nodes=1
Feb 25 13:58:19 laptop kernel: Dynamic Preempt: full
Feb 25 13:58:19 laptop kernel: rcu: Preemptible hierarchical RCU implementation.
Feb 25 13:58:19 laptop kernel: rcu: ^IRCU event tracing is enabled.
Feb 25 13:58:19 laptop kernel: ^ITrampoline variant of Tasks RCU enabled.
Feb 25 13:58:19 laptop kernel: rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
Feb 25 13:58:19 laptop kernel: NR_IRQS: 4352, nr_irqs: 2152, preallocated irqs: 16
Feb 25 13:58:19 laptop kernel: Console: colour dummy device 80x25
Feb 25 13:58:19 laptop kernel: printk: console [tty0] enabled
Feb 25 13:58:19 laptop kernel: ACPI: Core revision 20210930
Feb 25 13:58:19 laptop kernel: hpet: HPET dysfunctional in PC10. Force disabled.
Feb 25 13:58:19 laptop kernel: APIC: Switch to symmetric I/O mode setup
Feb 25 13:58:19 laptop kernel: Switched APIC routing to physical flat.
Feb 25 13:58:19 laptop kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x257a34a6eea, max_idle_ns: 440795264358 ns
Feb 25 13:58:19 laptop kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5199.98 BogoMIPS (lpj=10399968)
Feb 25 13:58:19 laptop kernel: pid_max: default: 32768 minimum: 301
Feb 25 13:58:19 laptop kernel: Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Feb 25 13:58:19 laptop kernel: Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Feb 25 13:58:19 laptop kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 25 13:58:19 laptop kernel: process: using mwait in idle threads
Feb 25 13:58:19 laptop kernel: Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
Feb 25 13:58:19 laptop kernel: Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
Feb 25 13:58:19 laptop kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
Feb 25 13:58:19 laptop kernel: Spectre V2 : Mitigation: Enhanced IBRS
Feb 25 13:58:19 laptop kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
Feb 25 13:58:19 laptop kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
Feb 25 13:58:19 laptop kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
Feb 25 13:58:19 laptop kernel: Freeing SMP alternatives memory: 28K
Feb 25 13:58:19 laptop kernel: smpboot: Estimated ratio of average max frequency by base frequency (times 1024): 1811
Feb 25 13:58:19 laptop kernel: smpboot: CPU0: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (family: 0x6, model: 0xa5, stepping: 0x2)
Feb 25 13:58:19 laptop kernel: Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
Feb 25 13:58:19 laptop kernel: ... version:                4
Feb 25 13:58:19 laptop kernel: ... bit width:              48
Feb 25 13:58:19 laptop kernel: ... generic registers:      4
Feb 25 13:58:19 laptop kernel: ... value mask:             0000ffffffffffff
Feb 25 13:58:19 laptop kernel: ... max period:             00007fffffffffff
Feb 25 13:58:19 laptop kernel: ... fixed-purpose events:   3
Feb 25 13:58:19 laptop kernel: ... event mask:             000000070000000f
Feb 25 13:58:19 laptop kernel: rcu: Hierarchical SRCU implementation.
Feb 25 13:58:19 laptop kernel: smp: Bringing up secondary CPUs ...
Feb 25 13:58:19 laptop kernel: x86: Booting SMP configuration:
Feb 25 13:58:19 laptop kernel: .... node  #0, CPUs:        #1  #2  #3  #4  #5  #6  #7  #8  #9 #10 #11
Feb 25 13:58:19 laptop kernel: smp: Brought up 1 node, 12 CPUs
Feb 25 13:58:19 laptop kernel: smpboot: Max logical packages: 1
Feb 25 13:58:19 laptop kernel: smpboot: Total of 12 processors activated (62399.80 BogoMIPS)
Feb 25 13:58:19 laptop kernel: devtmpfs: initialized
Feb 25 13:58:19 laptop kernel: ACPI: PM: Registering ACPI NVS region [mem 0x8eedf000-0x8fbcefff] (13565952 bytes)
Feb 25 13:58:19 laptop kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Feb 25 13:58:19 laptop kernel: futex hash table entries: 4096 (order: 6, 262144 bytes, linear)
Feb 25 13:58:19 laptop kernel: NET: Registered PF_NETLINK/PF_ROUTE protocol family
Feb 25 13:58:19 laptop kernel: thermal_sys: Registered thermal governor 'step_wise'
Feb 25 13:58:19 laptop kernel: thermal_sys: Registered thermal governor 'user_space'
Feb 25 13:58:19 laptop kernel: cpuidle: using governor ladder
Feb 25 13:58:19 laptop kernel: cpuidle: using governor menu
Feb 25 13:58:19 laptop kernel: PCI: Using configuration type 1 for base access
Feb 25 13:58:19 laptop kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 25 13:58:19 laptop kernel: cryptd: max_cpu_qlen set to 1000
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(Module Device)
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(Processor Device)
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(Linux-Dell-Video)
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
Feb 25 13:58:19 laptop kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
Feb 25 13:58:19 laptop kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.XDCI], AE_NOT_FOUND (20210930/dswload2-162)
Feb 25 13:58:19 laptop kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210930/psobject-220)
Feb 25 13:58:19 laptop kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0010)
Feb 25 13:58:19 laptop kernel: ACPI: 10 ACPI AML tables successfully acquired and loaded
Feb 25 13:58:19 laptop kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA184000F3300 0000FC (v02 PmRef  Cpu0Psd  00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: \_SB_.PR00: _OSC native thermal LVT Acked
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA18400CC0800 000400 (v02 PmRef  Cpu0Cst  00003001 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA18400CBA800 000581 (v02 PmRef  Cpu0Ist  00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA1840014B400 000137 (v02 PmRef  Cpu0Hwp  00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA1840006C000 000BEA (v02 PmRef  HwpLvt   00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA18400CBC000 000778 (v02 PmRef  ApIst    00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA18400CC0C00 0003D7 (v02 PmRef  ApHwp    00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA1840006D000 000D22 (v02 PmRef  ApPsd    00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: Dynamic OEM Table Load:
Feb 25 13:58:19 laptop kernel: ACPI: SSDT 0xFFFFA18400CC1000 0003CA (v02 PmRef  ApCst    00003000 INTL 20160422)
Feb 25 13:58:19 laptop kernel: ACPI: EC: EC started
Feb 25 13:58:19 laptop kernel: ACPI: EC: interrupt blocked
Feb 25 13:58:19 laptop kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
Feb 25 13:58:19 laptop kernel: ACPI: \_SB_.PCI0.LPCB.EC__: Boot DSDT EC used to handle transactions
Feb 25 13:58:19 laptop kernel: ACPI: Interpreter enabled
Feb 25 13:58:19 laptop kernel: ACPI: PM: (supports S0 S3 S4 S5)
Feb 25 13:58:19 laptop kernel: ACPI: Using IOAPIC for interrupt routing
Feb 25 13:58:19 laptop kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 25 13:58:19 laptop kernel: ACPI: Enabled 7 GPEs in block 00 to 7F
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [PG00]
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [BTPR]
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [V0PR]
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [V1PR]
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [V2PR]
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [WRST]
Feb 25 13:58:19 laptop kernel: ACPI: PM: Power Resource [PIN]
Feb 25 13:58:19 laptop kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
Feb 25 13:58:19 laptop kernel: acpi PNP0A08:00: _OSC: OS supports [ASPM ClockPM Segments MSI HPX-Type3]
Feb 25 13:58:19 laptop kernel: acpi PNP0A08:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI]
Feb 25 13:58:19 laptop kernel: PCI host bridge to bus 0000:00
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: root bus resource [mem 0x9d800000-0xdfffffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: root bus resource [mem 0xfc800000-0xfe7fffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: root bus resource [bus 00-fe]
Feb 25 13:58:19 laptop kernel: pci 0000:00:00.0: [8086:9b54] type 00 class 0x060000
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0: [8086:1901] type 01 class 0x060400
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: [8086:9bc4] type 00 class 0x030000
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: reg 0x10: [mem 0xc2000000-0xc2ffffff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: reg 0x18: [mem 0xa0000000-0xafffffff 64bit pref]
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: reg 0x20: [io  0x5000-0x503f]
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: BAR 2: assigned to efifb
Feb 25 13:58:19 laptop kernel: pci 0000:00:12.0: [8086:06f9] type 00 class 0x118000
Feb 25 13:58:19 laptop kernel: pci 0000:00:12.0: reg 0x10: [mem 0xc539c000-0xc539cfff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.0: [8086:06ed] type 00 class 0x0c0330
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.0: reg 0x10: [mem 0xc5380000-0xc538ffff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.2: [8086:06ef] type 00 class 0x050000
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.2: reg 0x10: [mem 0xc5398000-0xc5399fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.2: reg 0x18: [mem 0xc539d000-0xc539dfff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.3: [8086:06f0] type 00 class 0x028000
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.3: reg 0x10: [mem 0xc5390000-0xc5393fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:14.3: PME# supported from D0 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:15.0: [8086:06e8] type 00 class 0x0c8000
Feb 25 13:58:19 laptop kernel: pci 0000:00:15.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:15.1: [8086:06e9] type 00 class 0x0c8000
Feb 25 13:58:19 laptop kernel: pci 0000:00:15.1: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:16.0: [8086:06e0] type 00 class 0x078000
Feb 25 13:58:19 laptop kernel: pci 0000:00:16.0: reg 0x10: [mem 0xc53a0000-0xc53a0fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:16.0: PME# supported from D3hot
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: [8086:06d3] type 00 class 0x010601
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: reg 0x10: [mem 0xc539a000-0xc539bfff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: reg 0x14: [mem 0xc53a4000-0xc53a40ff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: reg 0x18: [io  0x5080-0x5087]
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: reg 0x1c: [io  0x5088-0x508b]
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: reg 0x20: [io  0x5060-0x507f]
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: reg 0x24: [mem 0xc53a3000-0xc53a37ff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:17.0: PME# supported from D3hot
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.0: [8086:06b0] type 01 class 0x060400
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.5: [8086:06b5] type 01 class 0x060400
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.5: PME# supported from D0 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6: [8086:06b6] type 01 class 0x060400
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6: PME# supported from D0 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.0: [8086:068d] type 00 class 0x060100
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.3: [8086:06c8] type 00 class 0x040300
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xc5394000-0xc5397fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.3: reg 0x20: [mem 0xc5000000-0xc50fffff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.3: PME# supported from D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.4: [8086:06a3] type 00 class 0x0c0500
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.4: reg 0x10: [mem 0xc53a1000-0xc53a10ff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.4: reg 0x20: [io  0xefa0-0xefbf]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.5: [8086:06a4] type 00 class 0x0c8000
Feb 25 13:58:19 laptop kernel: pci 0000:00:1f.5: reg 0x10: [mem 0xfe010000-0xfe010fff]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: [10de:1f95] type 00 class 0x030000
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: reg 0x10: [mem 0xc4000000-0xc4ffffff]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: reg 0x14: [mem 0xb0000000-0xbfffffff 64bit pref]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xc0000000-0xc1ffffff 64bit pref]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: reg 0x24: [io  0x4000-0x407f]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfff80000-0xffffffff pref]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: Enabling HDA controller
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: 63.008 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x8 link at 0000:00:01.0 (capable of 126.016 Gb/s with 8.0 GT/s PCIe x16 link)
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0: PCI bridge to [bus 01-05]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0:   bridge window [io  0x4000-0x4fff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xc3000000-0xc4ffffff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xb0000000-0xc1ffffff 64bit pref]
Feb 25 13:58:19 laptop kernel: pci 0000:06:00.0: [15b7:5009] type 00 class 0x010802
Feb 25 13:58:19 laptop kernel: pci 0000:06:00.0: reg 0x10: [mem 0xc5200000-0xc5203fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:06:00.0: reg 0x20: [mem 0xc5204000-0xc52040ff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.0: PCI bridge to [bus 06]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.0:   bridge window [mem 0xc5200000-0xc52fffff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.5: PCI bridge to [bus 07]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.0: [10ec:5287] type 00 class 0xff0000
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.0: reg 0x10: [mem 0xc5105000-0xc5105fff]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.0: supports D1 D2
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.0: PME# supported from D1 D2 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.1: [10ec:8168] type 00 class 0x020000
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.1: reg 0x10: [io  0x3000-0x30ff]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.1: reg 0x18: [mem 0xc5104000-0xc5104fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.1: reg 0x20: [mem 0xc5100000-0xc5103fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.1: supports D1 D2
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.1: PME# supported from D0 D1 D2 D3hot D3cold
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6: PCI bridge to [bus 08]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6:   bridge window [io  0x3000-0x3fff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6:   bridge window [mem 0xc5100000-0xc51fffff]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: on NUMA node 0
Feb 25 13:58:19 laptop kernel: ACPI: EC: interrupt unblocked
Feb 25 13:58:19 laptop kernel: ACPI: EC: event unblocked
Feb 25 13:58:19 laptop kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
Feb 25 13:58:19 laptop kernel: ACPI: EC: GPE=0x3
Feb 25 13:58:19 laptop kernel: ACPI: \_SB_.PCI0.LPCB.EC__: Boot DSDT EC initialization complete
Feb 25 13:58:19 laptop kernel: ACPI: \_SB_.PCI0.LPCB.EC__: EC: Used to handle transactions and events
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: vgaarb: no bridge control possible
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: vgaarb: bridge control possible
Feb 25 13:58:19 laptop kernel: vgaarb: loaded
Feb 25 13:58:19 laptop kernel: SCSI subsystem initialized
Feb 25 13:58:19 laptop kernel: libata version 3.00 loaded.
Feb 25 13:58:19 laptop kernel: ACPI: bus type USB registered
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver usbfs
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver hub
Feb 25 13:58:19 laptop kernel: usbcore: registered new device driver usb
Feb 25 13:58:19 laptop kernel: mc: Linux media interface: v0.10
Feb 25 13:58:19 laptop kernel: videodev: Linux video capture interface: v2.00
Feb 25 13:58:19 laptop kernel: Registered efivars operations
Feb 25 13:58:19 laptop kernel: Advanced Linux Sound Architecture Driver Initialized.
Feb 25 13:58:19 laptop kernel: Bluetooth: Core ver 2.22
Feb 25 13:58:19 laptop kernel: NET: Registered PF_BLUETOOTH protocol family
Feb 25 13:58:19 laptop kernel: Bluetooth: HCI device and connection manager initialized
Feb 25 13:58:19 laptop kernel: Bluetooth: HCI socket layer initialized
Feb 25 13:58:19 laptop kernel: Bluetooth: L2CAP socket layer initialized
Feb 25 13:58:19 laptop kernel: Bluetooth: SCO socket layer initialized
Feb 25 13:58:19 laptop kernel: PCI: Using ACPI for IRQ routing
Feb 25 13:58:19 laptop kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 25 13:58:19 laptop kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Feb 25 13:58:19 laptop kernel: e820: reserve RAM buffer [mem 0x7e1d9000-0x7fffffff]
Feb 25 13:58:19 laptop kernel: e820: reserve RAM buffer [mem 0x8ccef000-0x8fffffff]
Feb 25 13:58:19 laptop kernel: e820: reserve RAM buffer [mem 0x8fc50000-0x8fffffff]
Feb 25 13:58:19 laptop kernel: e820: reserve RAM buffer [mem 0x860800000-0x863ffffff]
Feb 25 13:58:19 laptop kernel: clocksource: Switched to clocksource tsc-early
Feb 25 13:58:19 laptop kernel: pnp: PnP ACPI init
Feb 25 13:58:19 laptop kernel: system 00:00: [mem 0x40000000-0x403fffff] could not be reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [io  0x1800-0x18fe] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [mem 0xfd000000-0xfd69ffff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [mem 0xfd6c0000-0xfd6cffff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [mem 0xfd6f0000-0xfdffffff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [mem 0xfe000000-0xfe01ffff] could not be reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [mem 0xfe200000-0xfe7fffff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:01: [mem 0xff000000-0xffffffff] could not be reserved
Feb 25 13:58:19 laptop kernel: system 00:02: [io  0x2000-0x20fe] has been reserved
Feb 25 13:58:19 laptop kernel: pnp 00:03: disabling [io  0x3322-0x3323] because it overlaps 0000:00:1d.6 BAR 7 [io  0x3000-0x3fff]
Feb 25 13:58:19 laptop kernel: system 00:03: [io  0x0680-0x069f] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:03: [io  0x164e-0x164f] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:05: [io  0x1854-0x1857] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xe0000000-0xefffffff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfed45000-0xfed8ffff] could not be reserved
Feb 25 13:58:19 laptop kernel: system 00:08: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 25 13:58:19 laptop kernel: system 00:09: [mem 0xfe038000-0xfe038fff] has been reserved
Feb 25 13:58:19 laptop kernel: pnp: PnP ACPI: found 10 devices
Feb 25 13:58:19 laptop kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Feb 25 13:58:19 laptop kernel: NET: Registered PF_INET protocol family
Feb 25 13:58:19 laptop kernel: IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Feb 25 13:58:19 laptop kernel: tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)
Feb 25 13:58:19 laptop kernel: TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Feb 25 13:58:19 laptop kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
Feb 25 13:58:19 laptop kernel: TCP: Hash tables configured (established 262144 bind 65536)
Feb 25 13:58:19 laptop kernel: UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)
Feb 25 13:58:19 laptop kernel: UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)
Feb 25 13:58:19 laptop kernel: NET: Registered PF_UNIX/PF_LOCAL protocol family
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: can't claim BAR 6 [mem 0xfff80000-0xffffffff pref]: no compatible bridge window
Feb 25 13:58:19 laptop kernel: pci 0000:00:15.0: BAR 0: assigned [mem 0x9d800000-0x9d800fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:00:15.1: BAR 0: assigned [mem 0x9d801000-0x9d801fff 64bit]
Feb 25 13:58:19 laptop kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xc3000000-0xc307ffff pref]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0: PCI bridge to [bus 01-05]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0:   bridge window [io  0x4000-0x4fff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xc3000000-0xc4ffffff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:01.0:   bridge window [mem 0xb0000000-0xc1ffffff 64bit pref]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.0: PCI bridge to [bus 06]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.0:   bridge window [mem 0xc5200000-0xc52fffff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.5: PCI bridge to [bus 07]
Feb 25 13:58:19 laptop kernel: pci 0000:08:00.0: BAR 6: assigned [mem 0xc5110000-0xc511ffff pref]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6: PCI bridge to [bus 08]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6:   bridge window [io  0x3000-0x3fff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:1d.6:   bridge window [mem 0xc5100000-0xc51fffff]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: resource 7 [mem 0x9d800000-0xdfffffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:00: resource 8 [mem 0xfc800000-0xfe7fffff window]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:01: resource 0 [io  0x4000-0x4fff]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:01: resource 1 [mem 0xc3000000-0xc4ffffff]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:01: resource 2 [mem 0xb0000000-0xc1ffffff 64bit pref]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:06: resource 1 [mem 0xc5200000-0xc52fffff]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:08: resource 0 [io  0x3000-0x3fff]
Feb 25 13:58:19 laptop kernel: pci_bus 0000:08: resource 1 [mem 0xc5100000-0xc51fffff]
Feb 25 13:58:19 laptop kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Feb 25 13:58:19 laptop kernel: PCI: CLS 64 bytes, default 64
Feb 25 13:58:19 laptop kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 25 13:58:19 laptop kernel: software IO TLB: mapped [mem 0x0000000087d15000-0x000000008bd15000] (64MB)
Feb 25 13:58:19 laptop kernel: Unpacking initramfs...
Feb 25 13:58:19 laptop kernel: Freeing initrd memory: 92K
Feb 25 13:58:19 laptop kernel: RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
Feb 25 13:58:19 laptop kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
Feb 25 13:58:19 laptop kernel: RAPL PMU: hw unit of domain package 2^-14 Joules
Feb 25 13:58:19 laptop kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules
Feb 25 13:58:19 laptop kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
Feb 25 13:58:19 laptop kernel: RAPL PMU: hw unit of domain psys 2^-14 Joules
Feb 25 13:58:19 laptop kernel: Initialise system trusted keyrings
Feb 25 13:58:19 laptop kernel: workingset: timestamp_bits=62 max_order=23 bucket_order=0
Feb 25 13:58:19 laptop kernel: Key type cifs.spnego registered
Feb 25 13:58:19 laptop kernel: Key type cifs.idmap registered
Feb 25 13:58:19 laptop kernel: fuse: init (API version 7.35)
Feb 25 13:58:19 laptop kernel: NET: Registered PF_ALG protocol family
Feb 25 13:58:19 laptop kernel: Key type asymmetric registered
Feb 25 13:58:19 laptop kernel: Asymmetric key parser 'x509' registered
Feb 25 13:58:19 laptop kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 25 13:58:19 laptop kernel: io scheduler mq-deadline registered
Feb 25 13:58:19 laptop kernel: Monitor-Mwait will be used to enter C-1 state
Feb 25 13:58:19 laptop kernel: Monitor-Mwait will be used to enter C-2 state
Feb 25 13:58:19 laptop kernel: Monitor-Mwait will be used to enter C-3 state
Feb 25 13:58:19 laptop kernel: ACPI: \_SB_.PR00: Found 3 idle states
Feb 25 13:58:19 laptop kernel: ACPI: AC: AC Adapter [AC] (on-line)
Feb 25 13:58:19 laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
Feb 25 13:58:19 laptop kernel: ACPI: button: Power Button [PWRB]
Feb 25 13:58:19 laptop kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
Feb 25 13:58:19 laptop kernel: ACPI: button: Sleep Button [SLPB]
Feb 25 13:58:19 laptop kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
Feb 25 13:58:19 laptop kernel: ACPI: button: Lid Switch [LID0]
Feb 25 13:58:19 laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
Feb 25 13:58:19 laptop kernel: ACPI: button: Power Button [PWRF]
Feb 25 13:58:19 laptop kernel: ACPI: \_TZ_.TZ0_: Invalid active0 threshold
Feb 25 13:58:19 laptop kernel: thermal LNXTHERM:00: registered as thermal_zone0
Feb 25 13:58:19 laptop kernel: ACPI: thermal: Thermal Zone [TZ0] (25 C)
Feb 25 13:58:19 laptop kernel: ACPI: battery: Slot [BAT0] (battery present)
Feb 25 13:58:19 laptop kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Feb 25 13:58:19 laptop kernel: Linux agpgart interface v0.103
Feb 25 13:58:19 laptop kernel: ACPI: bus type drm_connector registered
Feb 25 13:58:19 laptop kernel: rtsx_pci 0000:08:00.0: enabling device (0000 -> 0002)
Feb 25 13:58:19 laptop kernel: nvme 0000:06:00.0: platform quirk: setting simple suspend
Feb 25 13:58:19 laptop kernel: nvme nvme0: pci function 0000:06:00.0
Feb 25 13:58:19 laptop kernel: ahci 0000:00:17.0: version 3.0
Feb 25 13:58:19 laptop kernel: ahci 0000:00:17.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x10 impl SATA mode
Feb 25 13:58:19 laptop kernel: ahci 0000:00:17.0: flags: 64bit ncq sntf pm clo only pio slum part ems deso sadm sds apst 
Feb 25 13:58:19 laptop kernel: scsi host0: ahci
Feb 25 13:58:19 laptop kernel: scsi host1: ahci
Feb 25 13:58:19 laptop kernel: scsi host2: ahci
Feb 25 13:58:19 laptop kernel: scsi host3: ahci
Feb 25 13:58:19 laptop kernel: scsi host4: ahci
Feb 25 13:58:19 laptop kernel: ata1: DUMMY
Feb 25 13:58:19 laptop kernel: ata2: DUMMY
Feb 25 13:58:19 laptop kernel: ata3: DUMMY
Feb 25 13:58:19 laptop kernel: ata4: DUMMY
Feb 25 13:58:19 laptop kernel: ata5: SATA max UDMA/133 abar m2048@0xc53a3000 port 0xc53a3300 irq 122
Feb 25 13:58:19 laptop kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 25 13:58:19 laptop kernel: ehci-pci: EHCI PCI platform driver
Feb 25 13:58:19 laptop kernel: uhci_hcd: USB Universal Host Controller Interface driver
Feb 25 13:58:19 laptop kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Feb 25 13:58:19 laptop kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
Feb 25 13:58:19 laptop kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000000009810
Feb 25 13:58:19 laptop kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.16
Feb 25 13:58:19 laptop kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 25 13:58:19 laptop kernel: usb usb1: Product: xHCI Host Controller
Feb 25 13:58:19 laptop kernel: usb usb1: Manufacturer: Linux 5.16.0-rc5+ xhci-hcd
Feb 25 13:58:19 laptop kernel: usb usb1: SerialNumber: 0000:00:14.0
Feb 25 13:58:19 laptop kernel: hub 1-0:1.0: USB hub found
Feb 25 13:58:19 laptop kernel: hub 1-0:1.0: 16 ports detected
Feb 25 13:58:19 laptop kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Feb 25 13:58:19 laptop kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
Feb 25 13:58:19 laptop kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed
Feb 25 13:58:19 laptop kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.16
Feb 25 13:58:19 laptop kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 25 13:58:19 laptop kernel: usb usb2: Product: xHCI Host Controller
Feb 25 13:58:19 laptop kernel: usb usb2: Manufacturer: Linux 5.16.0-rc5+ xhci-hcd
Feb 25 13:58:19 laptop kernel: usb usb2: SerialNumber: 0000:00:14.0
Feb 25 13:58:19 laptop kernel: hub 2-0:1.0: USB hub found
Feb 25 13:58:19 laptop kernel: hub 2-0:1.0: 8 ports detected
Feb 25 13:58:19 laptop kernel: usb: port power management may be unreliable
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver usb-storage
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver ums-realtek
Feb 25 13:58:19 laptop kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
Feb 25 13:58:19 laptop kernel: nvme nvme0: allocated 32 MiB host memory buffer.
Feb 25 13:58:19 laptop kernel: nvme nvme0: 12/0/0 default/read/poll queues
Feb 25 13:58:19 laptop kernel:  nvme0n1: p1 p2 p3 p4 p5 p6 p7 p8
Feb 25 13:58:19 laptop kernel: i8042: Detected active multiplexing controller, rev 1.1
Feb 25 13:58:19 laptop kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 25 13:58:19 laptop kernel: serio: i8042 AUX0 port at 0x60,0x64 irq 12
Feb 25 13:58:19 laptop kernel: serio: i8042 AUX1 port at 0x60,0x64 irq 12
Feb 25 13:58:19 laptop kernel: serio: i8042 AUX2 port at 0x60,0x64 irq 12
Feb 25 13:58:19 laptop kernel: serio: i8042 AUX3 port at 0x60,0x64 irq 12
Feb 25 13:58:19 laptop kernel: mousedev: PS/2 mouse device common for all mice
Feb 25 13:58:19 laptop kernel: rtc_cmos 00:04: RTC can wake from S4
Feb 25 13:58:19 laptop kernel: rtc_cmos 00:04: registered as rtc0
Feb 25 13:58:19 laptop kernel: rtc_cmos 00:04: setting system clock to 2022-02-25T13:58:14 UTC (1645797494)
Feb 25 13:58:19 laptop kernel: rtc_cmos 00:04: alarms up to one month, y3k, 242 bytes nvram
Feb 25 13:58:19 laptop kernel: i2c_dev: i2c /dev entries driver
Feb 25 13:58:19 laptop kernel: intel_pstate: Intel P-state driver initializing
Feb 25 13:58:19 laptop kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
Feb 25 13:58:19 laptop kernel: intel_pstate: HWP enabled
Feb 25 13:58:19 laptop kernel: efifb: probing for efifb
Feb 25 13:58:19 laptop kernel: efifb: framebuffer at 0xa0000000, using 8128k, total 8128k
Feb 25 13:58:19 laptop kernel: efifb: mode is 1920x1080x32, linelength=7680, pages=1
Feb 25 13:58:19 laptop kernel: efifb: scrolling: redraw
Feb 25 13:58:19 laptop kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 25 13:58:19 laptop kernel: Console: switching to colour frame buffer device 240x67
Feb 25 13:58:19 laptop kernel: fb0: EFI VGA frame buffer device
Feb 25 13:58:19 laptop kernel: NET: Registered PF_PACKET protocol family
Feb 25 13:58:19 laptop kernel: NET: Registered PF_KEY protocol family
Feb 25 13:58:19 laptop kernel: Key type dns_resolver registered
Feb 25 13:58:19 laptop kernel: microcode: sig=0xa0652, pf=0x20, revision=0xea
Feb 25 13:58:19 laptop kernel: microcode: Microcode Update Driver: v2.2.
Feb 25 13:58:19 laptop kernel: IPI shorthand broadcast: enabled
Feb 25 13:58:19 laptop kernel: AVX2 version of gcm_enc/dec engaged.
Feb 25 13:58:19 laptop kernel: AES CTR mode by8 optimization enabled
Feb 25 13:58:19 laptop kernel: sched_clock: Marking stable (1022591746, 5459506)->(1044397101, -16345849)
Feb 25 13:58:19 laptop kernel: registered taskstats version 1
Feb 25 13:58:19 laptop kernel: Loading compiled-in X.509 certificates
Feb 25 13:58:19 laptop kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 13:58:19 laptop kernel: usb 1-1: new full-speed USB device number 2 using xhci_hcd
Feb 25 13:58:19 laptop kernel: tsc: Refined TSC clocksource calibration: 2591.998 MHz
Feb 25 13:58:19 laptop kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x255cb518234, max_idle_ns: 440795279333 ns
Feb 25 13:58:19 laptop kernel: clocksource: Switched to clocksource tsc
Feb 25 13:58:19 laptop kernel: usb 1-1: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.01
Feb 25 13:58:19 laptop kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 25 13:58:19 laptop kernel: usb 1-1: Product: USB Receiver
Feb 25 13:58:19 laptop kernel: usb 1-1: Manufacturer: Logitech
Feb 25 13:58:19 laptop kernel: mmc0: cannot verify signal voltage switch
Feb 25 13:58:19 laptop kernel: usb 1-8: new high-speed USB device number 3 using xhci_hcd
Feb 25 13:58:19 laptop kernel: mmc0: new ultra high speed SDR104 SDHC card at address 59b4
Feb 25 13:58:19 laptop kernel: mmcblk0: mmc0:59b4 SDU1  14.7 GiB 
Feb 25 13:58:19 laptop kernel:  mmcblk0: p1
Feb 25 13:58:19 laptop kernel: usb 1-8: New USB device found, idVendor=04f2, idProduct=b685, bcdDevice=54.04
Feb 25 13:58:19 laptop kernel: usb 1-8: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Feb 25 13:58:19 laptop kernel: usb 1-8: Product: Chicony USB2.0 Camera
Feb 25 13:58:19 laptop kernel: usb 1-8: Manufacturer: Sonix Technology Co., Ltd.
Feb 25 13:58:19 laptop kernel: usb 1-14: new full-speed USB device number 4 using xhci_hcd
Feb 25 13:58:19 laptop kernel: ata5.00: ATA-10: ST2000LM015-2E8174, 0001, max UDMA/133
Feb 25 13:58:19 laptop kernel: usb 1-14: New USB device found, idVendor=8087, idProduct=0026, bcdDevice= 0.02
Feb 25 13:58:19 laptop kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 25 13:58:19 laptop kernel: ata5.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Feb 25 13:58:19 laptop kernel: ata5.00: configured for UDMA/133
Feb 25 13:58:19 laptop kernel: scsi 4:0:0:0: Direct-Access     ATA      ST2000LM015-2E81 0001 PQ: 0 ANSI: 5
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: Attached scsi generic sg0 type 0
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: [sda] 4096-byte physical blocks
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: [sda] Write Protect is off
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 25 13:58:19 laptop kernel:  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
Feb 25 13:58:19 laptop kernel: sd 4:0:0:0: [sda] Attached SCSI disk
Feb 25 13:58:19 laptop kernel: ALSA device list:
Feb 25 13:58:19 laptop kernel:   No soundcards found.
Feb 25 13:58:19 laptop kernel: EXT4-fs (nvme0n1p4): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop kernel: VFS: Mounted root (ext4 filesystem) readonly on device 259:4.
Feb 25 13:58:19 laptop kernel: devtmpfs: mounted
Feb 25 13:58:19 laptop kernel: Freeing unused kernel image (initmem) memory: 1008K
Feb 25 13:58:19 laptop kernel: Write protecting the kernel read-only data: 16384k
Feb 25 13:58:19 laptop kernel: Freeing unused kernel image (text/rodata gap) memory: 2044K
Feb 25 13:58:19 laptop kernel: Freeing unused kernel image (rodata/data gap) memory: 1548K
Feb 25 13:58:19 laptop kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
Feb 25 13:58:19 laptop kernel: Run /sbin/init as init process
Feb 25 13:58:19 laptop kernel:   with arguments:
Feb 25 13:58:19 laptop kernel:     /sbin/init
Feb 25 13:58:19 laptop kernel:   with environment:
Feb 25 13:58:19 laptop kernel:     HOME=/
Feb 25 13:58:19 laptop kernel:     TERM=linux
Feb 25 13:58:19 laptop kernel:     BOOT_IMAGE=/boot/vmlinuz-5.16.0-rc5+
Feb 25 13:58:19 laptop kernel:     apm=power_off
Feb 25 13:58:19 laptop kernel: random: fast init done
Feb 25 13:58:19 laptop kernel: tun: Universal TUN/TAP device driver, 1.6
Feb 25 13:58:19 laptop kernel: <30>udevd[307]: starting version 3.2.11
Feb 25 13:58:19 laptop kernel: random: udevd: uninitialized urandom read (16 bytes read)
Feb 25 13:58:19 laptop last message repeated 2 times
Feb 25 13:58:19 laptop kernel: <30>udevd[308]: starting eudev-3.2.11
Feb 25 13:58:19 laptop kernel: wmi_bus wmi_bus-PNP0C14:01: WQ data block query control method not found
Feb 25 13:58:19 laptop last message repeated 3 times
Feb 25 13:58:19 laptop kernel: acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:03)
Feb 25 13:58:19 laptop kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Feb 25 13:58:19 laptop kernel: mei_me 0000:00:16.0: enabling device (0000 -> 0002)
Feb 25 13:58:19 laptop kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Feb 25 13:58:19 laptop kernel: Intel(R) Wireless WiFi driver for Linux
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver btusb
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-69.ucode failed with error -2
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Device revision is 2
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-68.ucode failed with error -2
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Secure boot is enabled
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: OTP lock is enabled
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: API lock is enabled
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: loaded firmware version 67.8f59b80b.0 QuZ-a0-hr-b0-67.ucode op_mode iwlmvm
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Debug lock is disabled
Feb 25 13:58:19 laptop kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C534.0001/input/input9
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Boot Address: 0x24800
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Firmware Version: 125-46.21
Feb 25 13:58:19 laptop kernel: intel-lpss 0000:00:15.0: enabling device (0004 -> 0006)
Feb 25 13:58:19 laptop kernel: intel-lpss 0000:00:15.1: enabling device (0004 -> 0006)
Feb 25 13:58:19 laptop kernel: checking generic (a0000000 7f0000) vs hw (c2000000 1000000)
Feb 25 13:58:19 laptop kernel: checking generic (a0000000 7f0000) vs hw (a0000000 10000000)
Feb 25 13:58:19 laptop kernel: fb0: switching to i915 from EFI VGA
Feb 25 13:58:19 laptop kernel: Console: switching to colour dummy device 80x25
Feb 25 13:58:19 laptop kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Feb 25 13:58:19 laptop kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
Feb 25 13:58:19 laptop kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
Feb 25 13:58:19 laptop kernel: usb 1-8: Found UVC 1.00 device Chicony USB2.0 Camera (04f2:b685)
Feb 25 13:58:19 laptop kernel: i801_smbus 0000:00:1f.4: SPD Write Disable is set
Feb 25 13:58:19 laptop kernel: i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351
Feb 25 13:58:19 laptop kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Feb 25 13:58:19 laptop kernel: i2c i2c-4: 2/2 memory slots populated (from DMI)
Feb 25 13:58:19 laptop kernel: i2c i2c-4: Successfully instantiated SPD at 0x50
Feb 25 13:58:19 laptop kernel: snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver uvcvideo
Feb 25 13:58:19 laptop kernel: hid-generic 0003:046D:C534.0001: input: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-1/input0
Feb 25 13:58:19 laptop kernel: input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/input/input10
Feb 25 13:58:19 laptop kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/input/input11
Feb 25 13:58:19 laptop kernel: i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
Feb 25 13:58:19 laptop kernel: i915 0000:00:02.0: [drm] [ENCODER:117:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it
Feb 25 13:58:19 laptop kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
Feb 25 13:58:19 laptop kernel: ACPI: video: Video Device [PEGP] (multi-head: no  rom: yes  post: no)
Feb 25 13:58:19 laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input15
Feb 25 13:58:19 laptop kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C534.0002/input/input12
Feb 25 13:58:19 laptop kernel: hid-generic 0003:046D:C534.0002: input,hiddev96: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-1/input1
Feb 25 13:58:19 laptop kernel: usbcore: registered new interface driver usbhid
Feb 25 13:58:19 laptop kernel: usbhid: USB HID core driver
Feb 25 13:58:19 laptop kernel: ACPI: video: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Feb 25 13:58:19 laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input16
Feb 25 13:58:19 laptop kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Feb 25 13:58:19 laptop kernel: fbcon: i915 (fb0) is primary device
Feb 25 13:58:19 laptop kernel: Console: switching to colour frame buffer device 240x67
Feb 25 13:58:19 laptop kernel: i915 0000:00:02.0: [drm] fb0: i915 frame buffer device
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC293: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x18
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:      Headset Mic=0x1a
Feb 25 13:58:19 laptop kernel: snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12
Feb 25 13:58:19 laptop kernel: iwlwifi 0000:00:14.3: base HW address: 34:7d:f6:df:83:1a
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input21
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input22
Feb 25 13:58:19 laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input23
Feb 25 13:58:19 laptop kernel: random: crng init done
Feb 25 13:58:19 laptop kernel: random: 7 urandom warning(s) missed due to ratelimiting
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Waiting for firmware download to complete
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Firmware loaded in 1554718 usecs
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Waiting for device to boot
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Device booted in 14566 usecs
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Feb 25 13:58:19 laptop kernel: Bluetooth: hci0: Firmware revision 0.4 build 125 week 46 2021
Feb 25 13:58:19 laptop kernel: Adding 65535996k swap on /dev/sda5.  Priority:1 extents:1 across:65535996k 
Feb 25 13:58:19 laptop kernel: EXT4-fs (nvme0n1p4): re-mounted. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop kernel: EXT4-fs (nvme0n1p4): re-mounted. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop kernel: ntfs3: Max link count 4000
Feb 25 13:58:19 laptop kernel: EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop kernel: EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: disabled.
Feb 25 13:58:19 laptop acpid: starting up with netlink and the input layer
Feb 25 13:58:19 laptop acpid: 3 rules loaded
Feb 25 13:58:19 laptop acpid: waiting for events: event logging is off
Feb 25 13:58:21 laptop kernel: wlan0: authenticate with DE:AD:BE:EF:7c:22
Feb 25 13:58:21 laptop kernel: wlan0: bad VHT capabilities, disabling VHT
Feb 25 13:58:21 laptop kernel: wlan0: 80 MHz not supported, disabling VHT
Feb 25 13:58:21 laptop kernel: wlan0: send auth to DE:AD:BE:EF:7c:22 (try 1/3)
Feb 25 13:58:21 laptop kernel: wlan0: authenticated
Feb 25 13:58:21 laptop kernel: wlan0: associate with DE:AD:BE:EF:7c:22 (try 1/3)
Feb 25 13:58:21 laptop kernel: wlan0: RX AssocResp from DE:AD:BE:EF:7c:22 (capab=0x1411 status=0 aid=2)
Feb 25 13:58:21 laptop kernel: wlan0: associated
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/bftpd [file=/etc/xinetd.conf] [line=15]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.d/chargen] [line=11]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/cups-lpd [file=/etc/xinetd.d/cups-lpd] [line=25]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=12]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/ssh [file=/etc/xinetd.d/ssh] [line=25]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/sysstat [file=/etc/xinetd.d/sysstat] [line=14]
Feb 25 13:58:21 laptop xinetd[1042]: Reading included configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=15]
Feb 25 13:58:21 laptop xinetd[1042]: removing chargen
Feb 25 13:58:21 laptop xinetd[1042]: removing chargen
Feb 25 13:58:21 laptop xinetd[1042]: removing printer
Feb 25 13:58:21 laptop xinetd[1042]: removing daytime
Feb 25 13:58:21 laptop xinetd[1042]: removing daytime
Feb 25 13:58:21 laptop xinetd[1042]: removing echo
Feb 25 13:58:21 laptop xinetd[1042]: removing echo
Feb 25 13:58:21 laptop xinetd[1042]: removing systat
Feb 25 13:58:21 laptop xinetd[1042]: removing time
Feb 25 13:58:21 laptop xinetd[1042]: removing time
Feb 25 13:58:21 laptop xinetd[1042]: xinetd Version 2.3.15 started with loadavg options compiled in.
Feb 25 13:58:21 laptop xinetd[1042]: Started working: 2 available services
Feb 25 13:58:21 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.ColorManager' requested by ':1.1' (uid=0 pid=1064 comm="/usr/sbin/cupsd -C /etc/cups/cupsd.conf -s /etc/cu") (using servicehelper)
Feb 25 13:58:21 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Feb 25 13:58:21 laptop bluetoothd[1095]: Bluetooth daemon 5.63
Feb 25 13:58:21 laptop bluetoothd[1095]: Starting SDP server
Feb 25 13:58:21 laptop kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 25 13:58:21 laptop kernel: Bluetooth: BNEP filters: protocol multicast
Feb 25 13:58:21 laptop kernel: Bluetooth: BNEP socket layer initialized
Feb 25 13:58:21 laptop bluetoothd[1095]: Bluetooth management interface 1.21 initialized
Feb 25 13:58:21 laptop bluetoothd[1095]: Failed to set privacy: Rejected (0x0b)
Feb 25 13:58:21 laptop nmbd[1130]: [2022/02/25 13:58:21.693041,  0] ../../source3/nmbd/nmbd.c:901(main) 
Feb 25 13:58:21 laptop nmbd[1130]:   nmbd version 4.15.5 started. 
Feb 25 13:58:21 laptop nmbd[1130]:   Copyright Andrew Tridgell and the Samba Team 1992-2021 
Feb 25 13:58:21 laptop nmbd[1131]: [2022/02/25 13:58:21.712491,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response) 
Feb 25 13:58:21 laptop nmbd[1131]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.10 for name HOMENET<1d>. 
Feb 25 13:58:21 laptop nmbd[1131]:   This response was from IP 192.168.1.50, reporting an IP address of 192.168.1.50. 
Feb 25 13:58:21 laptop smbd[1150]: [2022/02/25 13:58:21.731786,  0] ../../source3/smbd/server.c:1734(main) 
Feb 25 13:58:21 laptop smbd[1150]:   smbd version 4.15.5 started. 
Feb 25 13:58:21 laptop smbd[1150]:   Copyright Andrew Tridgell and the Samba Team 1992-2021 
Feb 25 13:58:21 laptop smbd[1151]: [2022/02/25 13:58:21.764778,  0] ../../source3/smbd/server.c:1082(smbd_open_one_socket) 
Feb 25 13:58:21 laptop smbd[1151]:   smbd_open_one_socket: open_socket_in failed: Address family not supported by protocol 
Feb 25 13:58:21 laptop smbd[1151]: [2022/02/25 13:58:21.765160,  0] ../../source3/smbd/server.c:1082(smbd_open_one_socket) 
Feb 25 13:58:21 laptop smbd[1151]:   smbd_open_one_socket: open_socket_in failed: Address family not supported by protocol 
Feb 25 13:58:21 laptop kernel: CIFS: Attempting to mount \\nas\Share
Feb 25 13:58:22 laptop kernel: CIFS: Attempting to mount \\nas\Media
Feb 25 13:58:25 laptop vnstatd[1358]: vnStat daemon 2.9 started. (pid:1358 uid:0 gid:0 64-bit)
Feb 25 13:58:25 laptop vnstatd[1358]: Monitoring (1): wlan0 (1000 Mbit) 
Feb 25 13:58:25 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.UPower' requested by ':1.6' (uid=0 pid=1336 comm="/usr/bin/sddm ") (using servicehelper)
Feb 25 13:58:25 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 25 13:58:25 laptop acpid: client connected from 1367[0:0]
Feb 25 13:58:25 laptop acpid: 1 client rule loaded
Feb 25 13:58:25 laptop acpid: client connected from 1367[0:0]
Feb 25 13:58:25 laptop acpid: 1 client rule loaded
Feb 25 13:58:32 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.ConsoleKit' requested by ':1.8' (uid=1000 pid=1424 comm="ck-launch-session lxqt-session ") (using servicehelper)
Feb 25 13:58:32 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.9' (uid=0 pid=1455 comm="/usr/sbin/console-kit-daemon --no-daemon ") (using servicehelper)
Feb 25 13:58:32 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Feb 25 13:58:32 laptop polkitd[1461]: Started polkitd version 0.120
Feb 25 13:58:32 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 25 13:58:32 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Activating service name='org.kde.KScreen' requested by ':1.1' (uid=1000 pid=1513 comm="/usr/bin/lxqt-config-monitor -l ")
Feb 25 13:58:32 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Successfully activated service 'org.kde.KScreen'
Feb 25 13:58:32 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Activating service name='org.gtk.vfs.Daemon' requested by ':1.3' (uid=1000 pid=1517 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 13:58:32 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Successfully activated service 'org.gtk.vfs.Daemon'
Feb 25 13:58:32 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.3' (uid=1000 pid=1517 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 13:58:32 laptop dbus-daemon[746]: [system] Activating service name='org.freedesktop.UDisks2' requested by ':1.33' (uid=1000 pid=1619 comm="/usr/libexec/gvfs-udisks2-volume-monitor ") (using servicehelper)
Feb 25 13:58:32 laptop pulseaudio[1616]: [pulseaudio] module-rescue-streams.c: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Feb 25 13:58:32 laptop bluetoothd[1095]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Feb 25 13:58:32 laptop kernel: Bluetooth: RFCOMM TTY layer initialized
Feb 25 13:58:32 laptop kernel: Bluetooth: RFCOMM socket layer initialized
Feb 25 13:58:32 laptop kernel: Bluetooth: RFCOMM ver 1.11
Feb 25 13:58:33 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Activating service name='org.a11y.Bus' requested by ':1.20' (uid=1000 pid=1655 comm="/usr/bin/python3 /usr/bin/blueman-applet ")
Feb 25 13:58:33 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Successfully activated service 'org.a11y.Bus'
Feb 25 13:58:34 laptop dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 25 13:58:34 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Feb 25 13:58:34 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Activating service name='org.gtk.vfs.GPhoto2VolumeMonitor' requested by ':1.3' (uid=1000 pid=1517 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 13:58:34 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Feb 25 13:58:34 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Activating service name='org.gtk.vfs.MTPVolumeMonitor' requested by ':1.3' (uid=1000 pid=1517 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
Feb 25 13:58:34 laptop dbus-daemon[1446]: [session uid=1000 pid=1444] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Feb 25 13:58:37 laptop kernel: EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: disabled.
Feb 25 14:00:15 laptop bluetoothd[1095]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:08:4C:FA:B0:47: Device or resource busy
Feb 25 14:00:15 laptop bluetoothd[1095]: /org/bluez/hci0/dev_00_08_4C_FA_B0_47/sep1/fd0: fd(28) ready
Feb 25 14:00:15 laptop pulseaudio[1616]: [pulseaudio] bluez5-util.c: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_00_08_4C_FA_B0_47/sep1/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume'
Feb 25 14:00:15 laptop bluetoothd[1095]: profiles/audio/avctp.c:uinput_create() Can't open input device: No such file or directory (2)
Feb 25 14:00:15 laptop bluetoothd[1095]: profiles/audio/avctp.c:init_uinput() AVRCP: failed to init uinput for Anker MP140
Feb 25 14:00:22 laptop bluetoothd[1095]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Feb 25 14:03:36 laptop nmbd[1131]: [2022/02/25 14:03:36.049478,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response) 
Feb 25 14:03:36 laptop nmbd[1131]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.10 for name HOMENET<1d>. 
Feb 25 14:03:36 laptop nmbd[1131]:   This response was from IP 192.168.1.50, reporting an IP address of 192.168.1.50. 

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-02-26  8:04                                 ` Chris Clayton
@ 2022-02-28 19:34                                   ` Luiz Augusto von Dentz
  2022-02-28 21:02                                     ` Chris Clayton
  0 siblings, 1 reply; 19+ messages in thread
From: Luiz Augusto von Dentz @ 2022-02-28 19:34 UTC (permalink / raw)
  To: Chris Clayton; +Cc: Chris Murphy, Bluetooth, regressions

Hi Chris,

On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
>
> Hi,
>
> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
> >> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
>
> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
>
> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
>
> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
>
> > Please record the HCI with btmon, it must be producing something since
> > it records even the mgmt commands.
> >
>
> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
> to get the hci trace that Luiz has asked for.
>
> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
>
> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
>
> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
> however, I can provide any other diagnostics, please let me know.
>
> Chris

Can you try with the following patch:

https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/


-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-02-28 19:34                                   ` Luiz Augusto von Dentz
@ 2022-02-28 21:02                                     ` Chris Clayton
  2022-02-28 21:20                                       ` Luiz Augusto von Dentz
  0 siblings, 1 reply; 19+ messages in thread
From: Chris Clayton @ 2022-02-28 21:02 UTC (permalink / raw)
  To: Luiz Augusto von Dentz; +Cc: Chris Murphy, Bluetooth, regressions

Hi Luiz,

On 28/02/2022 19:34, Luiz Augusto von Dentz wrote:
> Hi Chris,
> 
> On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
>>
>> Hi,
>>
>> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
>>>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
>>
>> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
>> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
>>
>> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
>> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
>>
>> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
>> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
>> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
>> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
>>
>>> Please record the HCI with btmon, it must be producing something since
>>> it records even the mgmt commands.
>>>
>>
>> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
>> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
>> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
>> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
>> to get the hci trace that Luiz has asked for.
>>
>> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
>> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
>> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
>> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
>> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
>>
>> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
>> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
>> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
>> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
>> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
>> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
>>
>> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
>> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
>> however, I can provide any other diagnostics, please let me know.
>>
>> Chris
> 
> Can you try with the following patch:
> 
> https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
> 
> 
Sorry, that patch has made no difference. After the first boot my headphones connected okay, but after a power-down and
reboot they would not connect without an unload and reload of the btusb module.

Chris

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-02-28 21:02                                     ` Chris Clayton
@ 2022-02-28 21:20                                       ` Luiz Augusto von Dentz
  2022-03-01  9:26                                         ` Chris Clayton
  0 siblings, 1 reply; 19+ messages in thread
From: Luiz Augusto von Dentz @ 2022-02-28 21:20 UTC (permalink / raw)
  To: Chris Clayton; +Cc: Chris Murphy, Bluetooth, regressions

Hi Chris,

On Mon, Feb 28, 2022 at 1:02 PM Chris Clayton <chris2553@googlemail.com> wrote:
>
> Hi Luiz,
>
> On 28/02/2022 19:34, Luiz Augusto von Dentz wrote:
> > Hi Chris,
> >
> > On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
> >>
> >> Hi,
> >>
> >> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
> >>>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
> >>
> >> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
> >> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
> >>
> >> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
> >> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
> >>
> >> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
> >> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
> >> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
> >> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
> >>
> >>> Please record the HCI with btmon, it must be producing something since
> >>> it records even the mgmt commands.
> >>>
> >>
> >> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
> >> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
> >> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
> >> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
> >> to get the hci trace that Luiz has asked for.
> >>
> >> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
> >> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
> >> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
> >> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
> >> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
> >>
> >> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
> >> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
> >> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
> >> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
> >> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
> >> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
> >>
> >> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
> >> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
> >> however, I can provide any other diagnostics, please let me know.
> >>
> >> Chris
> >
> > Can you try with the following patch:
> >
> > https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
> >
> >
> Sorry, that patch has made no difference. After the first boot my headphones connected okay, but after a power-down and
> reboot they would not connect without an unload and reload of the btusb module.

Can you tell us exactly what steps you are using? Are you applying on
top of what, rc6?


-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-02-28 21:20                                       ` Luiz Augusto von Dentz
@ 2022-03-01  9:26                                         ` Chris Clayton
  2022-03-01 18:34                                           ` Luiz Augusto von Dentz
  0 siblings, 1 reply; 19+ messages in thread
From: Chris Clayton @ 2022-03-01  9:26 UTC (permalink / raw)
  To: Luiz Augusto von Dentz; +Cc: Chris Murphy, Bluetooth, regressions

Hi Luiz,

I guess you are hoping for PEBKAC :-)

On 28/02/2022 21:20, Luiz Augusto von Dentz wrote:
> Hi Chris,
> 
> On Mon, Feb 28, 2022 at 1:02 PM Chris Clayton <chris2553@googlemail.com> wrote:
>>
>> Hi Luiz,
>>
>> On 28/02/2022 19:34, Luiz Augusto von Dentz wrote:
>>> Hi Chris,
>>>
>>> On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
>>>>>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
>>>>
>>>> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
>>>> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
>>>>
>>>> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
>>>> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
>>>>
>>>> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
>>>> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
>>>> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
>>>> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
>>>>
>>>>> Please record the HCI with btmon, it must be producing something since
>>>>> it records even the mgmt commands.
>>>>>
>>>>
>>>> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
>>>> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
>>>> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
>>>> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
>>>> to get the hci trace that Luiz has asked for.
>>>>
>>>> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
>>>> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
>>>> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
>>>> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
>>>> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
>>>>
>>>> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
>>>> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
>>>> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
>>>> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
>>>> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
>>>> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
>>>>
>>>> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
>>>> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
>>>> however, I can provide any other diagnostics, please let me know.
>>>>
>>>> Chris
>>>
>>> Can you try with the following patch:
>>>
>>> https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
>>>
>>>
>> Sorry, that patch has made no difference. After the first boot my headphones connected okay, but after a power-down and
>> reboot they would not connect without an unload and reload of the btusb module.
> 
> Can you tell us exactly what steps you are using? Are you applying on
> top of what, rc6?
> 

Until I got your patch yesterday, I was using a clone of
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git which I update frequently and have been doing so for as
long as I can remember. Just in case there was a hidden flaw in that tree, I took a new clone yesterday, (so yes, the
patch was tested on top of rc6) copied over the .config file and applied the patch. Then I built and installed the
kernel, updated grub, powered off the laptop and booted into the new kernel. Once the laptop had booted and logged in to
my LXQt desktop, I powered on my headphones and a connection was establisehed almost straight away. I powered the
headphones off and the disconnection worked fine.

Knowing that the problem crops up intermittently, I then rebooted the laptop. When the boot was complete, I then powered
on my bluetooth headphones an waited for them to connect to the laptop. After about 20 seconds, a connection had not
been established. I powered off the headphones, used modprobe to unload and then reload the btusb module. When I powered
on the headphones, a connectiin was established within 2 or 3 seconds.

I've booted this laptop countless times over the last few days. Doing the bisect, I didn't mark a commit as good until I
had done five boots and been able to connect my headphones on each boot. What I can say from that work is that two
consecutive boots into a working kernel are very rare. I can't remeber an occasion when it took more than two boots to
establish that a kernel was bad.

Chris

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-03-01  9:26                                         ` Chris Clayton
@ 2022-03-01 18:34                                           ` Luiz Augusto von Dentz
  2022-03-01 18:56                                             ` Chris Clayton
  2022-03-01 18:57                                             ` Luiz Augusto von Dentz
  0 siblings, 2 replies; 19+ messages in thread
From: Luiz Augusto von Dentz @ 2022-03-01 18:34 UTC (permalink / raw)
  To: Chris Clayton; +Cc: Chris Murphy, Bluetooth, regressions

Hi Chris,

On Tue, Mar 1, 2022 at 1:26 AM Chris Clayton <chris2553@googlemail.com> wrote:
>
> Hi Luiz,
>
> I guess you are hoping for PEBKAC :-)
>
> On 28/02/2022 21:20, Luiz Augusto von Dentz wrote:
> > Hi Chris,
> >
> > On Mon, Feb 28, 2022 at 1:02 PM Chris Clayton <chris2553@googlemail.com> wrote:
> >>
> >> Hi Luiz,
> >>
> >> On 28/02/2022 19:34, Luiz Augusto von Dentz wrote:
> >>> Hi Chris,
> >>>
> >>> On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
> >>>>>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
> >>>>
> >>>> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
> >>>> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
> >>>>
> >>>> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
> >>>> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
> >>>>
> >>>> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
> >>>> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
> >>>> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
> >>>> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
> >>>>
> >>>>> Please record the HCI with btmon, it must be producing something since
> >>>>> it records even the mgmt commands.
> >>>>>
> >>>>
> >>>> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
> >>>> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
> >>>> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
> >>>> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
> >>>> to get the hci trace that Luiz has asked for.
> >>>>
> >>>> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
> >>>> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
> >>>> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
> >>>> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
> >>>> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
> >>>>
> >>>> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
> >>>> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
> >>>> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
> >>>> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
> >>>> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
> >>>> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
> >>>>
> >>>> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
> >>>> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
> >>>> however, I can provide any other diagnostics, please let me know.
> >>>>
> >>>> Chris
> >>>
> >>> Can you try with the following patch:
> >>>
> >>> https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
> >>>
> >>>
> >> Sorry, that patch has made no difference. After the first boot my headphones connected okay, but after a power-down and
> >> reboot they would not connect without an unload and reload of the btusb module.
> >
> > Can you tell us exactly what steps you are using? Are you applying on
> > top of what, rc6?
> >
>
> Until I got your patch yesterday, I was using a clone of
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git which I update frequently and have been doing so for as
> long as I can remember. Just in case there was a hidden flaw in that tree, I took a new clone yesterday, (so yes, the
> patch was tested on top of rc6) copied over the .config file and applied the patch. Then I built and installed the
> kernel, updated grub, powered off the laptop and booted into the new kernel. Once the laptop had booted and logged in to
> my LXQt desktop, I powered on my headphones and a connection was establisehed almost straight away. I powered the
> headphones off and the disconnection worked fine.
>
> Knowing that the problem crops up intermittently, I then rebooted the laptop. When the boot was complete, I then powered
> on my bluetooth headphones an waited for them to connect to the laptop. After about 20 seconds, a connection had not
> been established. I powered off the headphones, used modprobe to unload and then reload the btusb module. When I powered
> on the headphones, a connectiin was established within 2 or 3 seconds.
>
> I've booted this laptop countless times over the last few days. Doing the bisect, I didn't mark a commit as good until I
> had done five boots and been able to connect my headphones on each boot. What I can say from that work is that two
> consecutive boots into a working kernel are very rare. I can't remeber an occasion when it took more than two boots to
> establish that a kernel was bad.

Do commands such as bluetoothctl power on or scan on works? Try
running bluetoothd -dn from a shell (disable bluetooth.service), also
are there any settings changed in main.conf?


-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-03-01 18:34                                           ` Luiz Augusto von Dentz
@ 2022-03-01 18:56                                             ` Chris Clayton
  2022-03-01 18:57                                             ` Luiz Augusto von Dentz
  1 sibling, 0 replies; 19+ messages in thread
From: Chris Clayton @ 2022-03-01 18:56 UTC (permalink / raw)
  To: Luiz Augusto von Dentz; +Cc: Chris Murphy, Bluetooth, regressions

Hi

On 01/03/2022 18:34, Luiz Augusto von Dentz wrote:
> Hi Chris,
> 
> On Tue, Mar 1, 2022 at 1:26 AM Chris Clayton <chris2553@googlemail.com> wrote:
>>
>> Hi Luiz,
>>
>> I guess you are hoping for PEBKAC :-)
>>
>> On 28/02/2022 21:20, Luiz Augusto von Dentz wrote:
>>> Hi Chris,
>>>
>>> On Mon, Feb 28, 2022 at 1:02 PM Chris Clayton <chris2553@googlemail.com> wrote:
>>>>
>>>> Hi Luiz,
>>>>
>>>> On 28/02/2022 19:34, Luiz Augusto von Dentz wrote:
>>>>> Hi Chris,
>>>>>
>>>>> On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
>>>>>>>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
>>>>>>
>>>>>> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
>>>>>> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
>>>>>>
>>>>>> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
>>>>>> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
>>>>>>
>>>>>> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
>>>>>> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
>>>>>> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
>>>>>> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
>>>>>>
>>>>>>> Please record the HCI with btmon, it must be producing something since
>>>>>>> it records even the mgmt commands.
>>>>>>>
>>>>>>
>>>>>> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
>>>>>> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
>>>>>> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
>>>>>> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
>>>>>> to get the hci trace that Luiz has asked for.
>>>>>>
>>>>>> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
>>>>>> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
>>>>>> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
>>>>>> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
>>>>>> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
>>>>>>
>>>>>> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
>>>>>> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
>>>>>> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
>>>>>> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
>>>>>> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
>>>>>> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
>>>>>>
>>>>>> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
>>>>>> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
>>>>>> however, I can provide any other diagnostics, please let me know.
>>>>>>
>>>>>> Chris
>>>>>
>>>>> Can you try with the following patch:
>>>>>
>>>>> https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
>>>>>
>>>>>
>>>> Sorry, that patch has made no difference. After the first boot my headphones connected okay, but after a power-down and
>>>> reboot they would not connect without an unload and reload of the btusb module.
>>>
>>> Can you tell us exactly what steps you are using? Are you applying on
>>> top of what, rc6?
>>>
>>
>> Until I got your patch yesterday, I was using a clone of
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git which I update frequently and have been doing so for as
>> long as I can remember. Just in case there was a hidden flaw in that tree, I took a new clone yesterday, (so yes, the
>> patch was tested on top of rc6) copied over the .config file and applied the patch. Then I built and installed the
>> kernel, updated grub, powered off the laptop and booted into the new kernel. Once the laptop had booted and logged in to
>> my LXQt desktop, I powered on my headphones and a connection was establisehed almost straight away. I powered the
>> headphones off and the disconnection worked fine.
>>
>> Knowing that the problem crops up intermittently, I then rebooted the laptop. When the boot was complete, I then powered
>> on my bluetooth headphones an waited for them to connect to the laptop. After about 20 seconds, a connection had not
>> been established. I powered off the headphones, used modprobe to unload and then reload the btusb module. When I powered
>> on the headphones, a connectiin was established within 2 or 3 seconds.
>>
>> I've booted this laptop countless times over the last few days. Doing the bisect, I didn't mark a commit as good until I
>> had done five boots and been able to connect my headphones on each boot. What I can say from that work is that two
>> consecutive boots into a working kernel are very rare. I can't remeber an occasion when it took more than two boots to
>> establish that a kernel was bad.
> 
> Do commands such as bluetoothctl power on or scan on works?

You're taking about systemd things here but as I said last week, I don't use systemd. I use sysvinit and an associated
set of boot scripts.

 Try
> running bluetoothd -dn from a shell (disable bluetooth.service), also
> are there any settings changed in main.conf?
> 
OK, I'll try that later, It might be tomorrow because I'm busy with other stuff at the moment.

Chris

> 

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-03-01 18:34                                           ` Luiz Augusto von Dentz
  2022-03-01 18:56                                             ` Chris Clayton
@ 2022-03-01 18:57                                             ` Luiz Augusto von Dentz
  2022-03-01 19:40                                               ` Chris Clayton
  1 sibling, 1 reply; 19+ messages in thread
From: Luiz Augusto von Dentz @ 2022-03-01 18:57 UTC (permalink / raw)
  To: Chris Clayton; +Cc: Chris Murphy, Bluetooth, regressions

Hi Chris,

On Tue, Mar 1, 2022 at 10:34 AM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> Hi Chris,
>
> On Tue, Mar 1, 2022 at 1:26 AM Chris Clayton <chris2553@googlemail.com> wrote:
> >
> > Hi Luiz,
> >
> > I guess you are hoping for PEBKAC :-)
> >
> > On 28/02/2022 21:20, Luiz Augusto von Dentz wrote:
> > > Hi Chris,
> > >
> > > On Mon, Feb 28, 2022 at 1:02 PM Chris Clayton <chris2553@googlemail.com> wrote:
> > >>
> > >> Hi Luiz,
> > >>
> > >> On 28/02/2022 19:34, Luiz Augusto von Dentz wrote:
> > >>> Hi Chris,
> > >>>
> > >>> On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
> > >>>>
> > >>>> Hi,
> > >>>>
> > >>>> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
> > >>>>>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
> > >>>>
> > >>>> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
> > >>>> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
> > >>>>
> > >>>> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
> > >>>> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
> > >>>>
> > >>>> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
> > >>>> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
> > >>>> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
> > >>>> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
> > >>>>
> > >>>>> Please record the HCI with btmon, it must be producing something since
> > >>>>> it records even the mgmt commands.
> > >>>>>
> > >>>>
> > >>>> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
> > >>>> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
> > >>>> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
> > >>>> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
> > >>>> to get the hci trace that Luiz has asked for.
> > >>>>
> > >>>> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
> > >>>> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
> > >>>> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
> > >>>> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
> > >>>> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
> > >>>>
> > >>>> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
> > >>>> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
> > >>>> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
> > >>>> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
> > >>>> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
> > >>>> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
> > >>>>
> > >>>> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
> > >>>> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
> > >>>> however, I can provide any other diagnostics, please let me know.
> > >>>>
> > >>>> Chris
> > >>>
> > >>> Can you try with the following patch:
> > >>>
> > >>> https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
> > >>>
> > >>>
> > >> Sorry, that patch has made no difference. After the first boot my headphones connected okay, but after a power-down and
> > >> reboot they would not connect without an unload and reload of the btusb module.
> > >
> > > Can you tell us exactly what steps you are using? Are you applying on
> > > top of what, rc6?
> > >
> >
> > Until I got your patch yesterday, I was using a clone of
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git which I update frequently and have been doing so for as
> > long as I can remember. Just in case there was a hidden flaw in that tree, I took a new clone yesterday, (so yes, the
> > patch was tested on top of rc6) copied over the .config file and applied the patch. Then I built and installed the
> > kernel, updated grub, powered off the laptop and booted into the new kernel. Once the laptop had booted and logged in to
> > my LXQt desktop, I powered on my headphones and a connection was establisehed almost straight away. I powered the
> > headphones off and the disconnection worked fine.
> >
> > Knowing that the problem crops up intermittently, I then rebooted the laptop. When the boot was complete, I then powered
> > on my bluetooth headphones an waited for them to connect to the laptop. After about 20 seconds, a connection had not
> > been established. I powered off the headphones, used modprobe to unload and then reload the btusb module. When I powered
> > on the headphones, a connectiin was established within 2 or 3 seconds.

Ive attempted 5 restart with 5.17.0-0.rc6.109.fc37.x86_64, my headset
was able to reconnect every single time without any problem. The only
think that was a little bit strange was that it reconnects two
normally, once from gdm and then another time when gnome is loading,
but I assume it is normal nowadays since it appears when switching
session pipewire unregisters its audio endpoints.

Perhaps it is some race that depends on how bluetoothd is being
started or something.

> > I've booted this laptop countless times over the last few days. Doing the bisect, I didn't mark a commit as good until I
> > had done five boots and been able to connect my headphones on each boot. What I can say from that work is that two
> > consecutive boots into a working kernel are very rare. I can't remeber an occasion when it took more than two boots to
> > establish that a kernel was bad.
>
> Do commands such as bluetoothctl power on or scan on works? Try
> running bluetoothd -dn from a shell (disable bluetooth.service), also
> are there any settings changed in main.conf?
>
>
> --
> Luiz Augusto von Dentz



-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-03-01 18:57                                             ` Luiz Augusto von Dentz
@ 2022-03-01 19:40                                               ` Chris Clayton
  2022-03-01 22:40                                                 ` Luiz Augusto von Dentz
  0 siblings, 1 reply; 19+ messages in thread
From: Chris Clayton @ 2022-03-01 19:40 UTC (permalink / raw)
  To: Luiz Augusto von Dentz; +Cc: Chris Murphy, Bluetooth, regressions

Hi

On 01/03/2022 18:57, Luiz Augusto von Dentz wrote:
> Hi Chris,
> 
> On Tue, Mar 1, 2022 at 10:34 AM Luiz Augusto von Dentz
> <luiz.dentz@gmail.com> wrote:
>>
>> Hi Chris,
>>
>> On Tue, Mar 1, 2022 at 1:26 AM Chris Clayton <chris2553@googlemail.com> wrote:
>>>
>>> Hi Luiz,
>>>
>>> I guess you are hoping for PEBKAC :-)
>>>
>>> On 28/02/2022 21:20, Luiz Augusto von Dentz wrote:
>>>> Hi Chris,
>>>>
>>>> On Mon, Feb 28, 2022 at 1:02 PM Chris Clayton <chris2553@googlemail.com> wrote:
>>>>>
>>>>> Hi Luiz,
>>>>>
>>>>> On 28/02/2022 19:34, Luiz Augusto von Dentz wrote:
>>>>>> Hi Chris,
>>>>>>
>>>>>> On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
>>>>>>>>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
>>>>>>>
>>>>>>> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
>>>>>>> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
>>>>>>>
>>>>>>> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
>>>>>>> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
>>>>>>>
>>>>>>> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
>>>>>>> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
>>>>>>> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
>>>>>>> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
>>>>>>>
>>>>>>>> Please record the HCI with btmon, it must be producing something since
>>>>>>>> it records even the mgmt commands.
>>>>>>>>
>>>>>>>
>>>>>>> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
>>>>>>> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
>>>>>>> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
>>>>>>> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
>>>>>>> to get the hci trace that Luiz has asked for.
>>>>>>>
>>>>>>> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
>>>>>>> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
>>>>>>> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
>>>>>>> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
>>>>>>> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
>>>>>>>
>>>>>>> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
>>>>>>> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
>>>>>>> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
>>>>>>> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
>>>>>>> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
>>>>>>> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
>>>>>>>
>>>>>>> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
>>>>>>> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
>>>>>>> however, I can provide any other diagnostics, please let me know.
>>>>>>>
>>>>>>> Chris
>>>>>>
>>>>>> Can you try with the following patch:
>>>>>>
>>>>>> https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
>>>>>>
>>>>>>
>>>>> Sorry, that patch has made no difference. After the first boot my headphones connected okay, but after a power-down and
>>>>> reboot they would not connect without an unload and reload of the btusb module.
>>>>
>>>> Can you tell us exactly what steps you are using? Are you applying on
>>>> top of what, rc6?
>>>>
>>>
>>> Until I got your patch yesterday, I was using a clone of
>>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git which I update frequently and have been doing so for as
>>> long as I can remember. Just in case there was a hidden flaw in that tree, I took a new clone yesterday, (so yes, the
>>> patch was tested on top of rc6) copied over the .config file and applied the patch. Then I built and installed the
>>> kernel, updated grub, powered off the laptop and booted into the new kernel. Once the laptop had booted and logged in to
>>> my LXQt desktop, I powered on my headphones and a connection was establisehed almost straight away. I powered the
>>> headphones off and the disconnection worked fine.
>>>
>>> Knowing that the problem crops up intermittently, I then rebooted the laptop. When the boot was complete, I then powered
>>> on my bluetooth headphones an waited for them to connect to the laptop. After about 20 seconds, a connection had not
>>> been established. I powered off the headphones, used modprobe to unload and then reload the btusb module. When I powered
>>> on the headphones, a connectiin was established within 2 or 3 seconds.
> 
> Ive attempted 5 restart with 5.17.0-0.rc6.109.fc37.x86_64, my headset
> was able to reconnect every single time without any problem. The only

For your five tests, did it connect on the first boot? As I've said, sometimes it fails to connect on the first boot,
but if it succeeds, it has always failed after a power-off and restart. Looking back at the notes I took during the
bisect, I've didn't have a single bisection step where I had to boot more more than twice to ascertain that it was a bad
kernel. As I said, I didn't mark a kernel as good until I'd had five successful boots.
> normally, once from gdm and then another time when gnome is loading,
> but I assume it is normal nowadays since it appears when switching
> session pipewire unregisters its audio endpoints.
> 

I don't use pipewire. Prior to 5.17, bluetooth has worked more or less trouble free for at least 4 years. I've read
about pipewire in Linux Magazine but don't see what it would bring to my party except complication.

ends on how bluetoothd is being
> started or something.
> 

Did you see the warnings that read "Bluetooth: hci0: unexpected event 0xff length: 5 > 0"? That seems to indicate that
something is sending events that are unexpected. What effect will that have?  As I said, according to lshw, my system's
bluetooth hardware is Intel AX201. Is that what you are testing on?

>>> I've booted this laptop countless times over the last few days. Doing the bisect, I didn't mark a commit as good until I
>>> had done five boots and been able to connect my headphones on each boot. What I can say from that work is that two
>>> consecutive boots into a working kernel are very rare. I can't remeber an occasion when it took more than two boots to
>>> establish that a kernel was bad.
>>
>> Do commands such as bluetoothctl power on or scan on works? Try
>> running bluetoothd -dn from a shell (disable bluetooth.service), also
>> are there any settings changed in main.conf?
>>

Sorry, I forgot to answer this question earlier. I haven't changed main.conf. Besides, my bluetooth devices connect
successfully every time with 5.16.11 and 5.15.25 kernels. As I've said before, that strongly suggests that there is a
code regression in 5.17.

>>
>> --
>> Luiz Augusto von Dentz
> 
> 
> 

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-03-01 19:40                                               ` Chris Clayton
@ 2022-03-01 22:40                                                 ` Luiz Augusto von Dentz
  2022-03-01 22:47                                                   ` Luiz Augusto von Dentz
  0 siblings, 1 reply; 19+ messages in thread
From: Luiz Augusto von Dentz @ 2022-03-01 22:40 UTC (permalink / raw)
  To: Chris Clayton; +Cc: Chris Murphy, Bluetooth, regressions

Hi Chris,

On Tue, Mar 1, 2022 at 11:40 AM Chris Clayton <chris2553@googlemail.com> wrote:
>
> Hi
>
> On 01/03/2022 18:57, Luiz Augusto von Dentz wrote:
> > Hi Chris,
> >
> > On Tue, Mar 1, 2022 at 10:34 AM Luiz Augusto von Dentz
> > <luiz.dentz@gmail.com> wrote:
> >>
> >> Hi Chris,
> >>
> >> On Tue, Mar 1, 2022 at 1:26 AM Chris Clayton <chris2553@googlemail.com> wrote:
> >>>
> >>> Hi Luiz,
> >>>
> >>> I guess you are hoping for PEBKAC :-)
> >>>
> >>> On 28/02/2022 21:20, Luiz Augusto von Dentz wrote:
> >>>> Hi Chris,
> >>>>
> >>>> On Mon, Feb 28, 2022 at 1:02 PM Chris Clayton <chris2553@googlemail.com> wrote:
> >>>>>
> >>>>> Hi Luiz,
> >>>>>
> >>>>> On 28/02/2022 19:34, Luiz Augusto von Dentz wrote:
> >>>>>> Hi Chris,
> >>>>>>
> >>>>>> On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
> >>>>>>>>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
> >>>>>>>
> >>>>>>> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
> >>>>>>> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
> >>>>>>>
> >>>>>>> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
> >>>>>>> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
> >>>>>>>
> >>>>>>> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
> >>>>>>> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
> >>>>>>> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
> >>>>>>> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
> >>>>>>>
> >>>>>>>> Please record the HCI with btmon, it must be producing something since
> >>>>>>>> it records even the mgmt commands.
> >>>>>>>>
> >>>>>>>
> >>>>>>> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
> >>>>>>> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
> >>>>>>> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
> >>>>>>> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
> >>>>>>> to get the hci trace that Luiz has asked for.
> >>>>>>>
> >>>>>>> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
> >>>>>>> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
> >>>>>>> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
> >>>>>>> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
> >>>>>>> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
> >>>>>>>
> >>>>>>> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
> >>>>>>> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
> >>>>>>> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
> >>>>>>> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
> >>>>>>> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
> >>>>>>> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
> >>>>>>>
> >>>>>>> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
> >>>>>>> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
> >>>>>>> however, I can provide any other diagnostics, please let me know.
> >>>>>>>
> >>>>>>> Chris
> >>>>>>
> >>>>>> Can you try with the following patch:
> >>>>>>
> >>>>>> https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
> >>>>>>
> >>>>>>
> >>>>> Sorry, that patch has made no difference. After the first boot my headphones connected okay, but after a power-down and
> >>>>> reboot they would not connect without an unload and reload of the btusb module.
> >>>>
> >>>> Can you tell us exactly what steps you are using? Are you applying on
> >>>> top of what, rc6?
> >>>>
> >>>
> >>> Until I got your patch yesterday, I was using a clone of
> >>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git which I update frequently and have been doing so for as
> >>> long as I can remember. Just in case there was a hidden flaw in that tree, I took a new clone yesterday, (so yes, the
> >>> patch was tested on top of rc6) copied over the .config file and applied the patch. Then I built and installed the
> >>> kernel, updated grub, powered off the laptop and booted into the new kernel. Once the laptop had booted and logged in to
> >>> my LXQt desktop, I powered on my headphones and a connection was establisehed almost straight away. I powered the
> >>> headphones off and the disconnection worked fine.
> >>>
> >>> Knowing that the problem crops up intermittently, I then rebooted the laptop. When the boot was complete, I then powered
> >>> on my bluetooth headphones an waited for them to connect to the laptop. After about 20 seconds, a connection had not
> >>> been established. I powered off the headphones, used modprobe to unload and then reload the btusb module. When I powered
> >>> on the headphones, a connectiin was established within 2 or 3 seconds.
> >
> > Ive attempted 5 restart with 5.17.0-0.rc6.109.fc37.x86_64, my headset
> > was able to reconnect every single time without any problem. The only
>
> For your five tests, did it connect on the first boot? As I've said, sometimes it fails to connect on the first boot,
> but if it succeeds, it has always failed after a power-off and restart. Looking back at the notes I took during the
> bisect, I've didn't have a single bisection step where I had to boot more more than twice to ascertain that it was a bad
> kernel. As I said, I didn't mark a kernel as good until I'd had five successful boots.

It did connect every single time.

> > normally, once from gdm and then another time when gnome is loading,
> > but I assume it is normal nowadays since it appears when switching
> > session pipewire unregisters its audio endpoints.
> >
>
> I don't use pipewire. Prior to 5.17, bluetooth has worked more or less trouble free for at least 4 years. I've read
> about pipewire in Linux Magazine but don't see what it would bring to my party except complication.
>
> ends on how bluetoothd is being
> > started or something.
> >
>
> Did you see the warnings that read "Bluetooth: hci0: unexpected event 0xff length: 5 > 0"? That seems to indicate that
> something is sending events that are unexpected. What effect will that have?  As I said, according to lshw, my system's
> bluetooth hardware is Intel AX201. Is that what you are testing on?

I have an AX200 on my system, AX201 is very similar so Id be surprised
if that is the problem, btw Ive also got some unexpected events but
that didn't stop the headset to reconnect.

> >>> I've booted this laptop countless times over the last few days. Doing the bisect, I didn't mark a commit as good until I
> >>> had done five boots and been able to connect my headphones on each boot. What I can say from that work is that two
> >>> consecutive boots into a working kernel are very rare. I can't remeber an occasion when it took more than two boots to
> >>> establish that a kernel was bad.
> >>
> >> Do commands such as bluetoothctl power on or scan on works? Try
> >> running bluetoothd -dn from a shell (disable bluetooth.service), also
> >> are there any settings changed in main.conf?
> >>
>
> Sorry, I forgot to answer this question earlier. I haven't changed main.conf. Besides, my bluetooth devices connect
> successfully every time with 5.16.11 and 5.15.25 kernels. As I've said before, that strongly suggests that there is a
> code regression in 5.17.

Not saying there isn't something wrong, we have sent a couple of fixes
that doesn't seem to be merged yet, and we are working on another one
for fixing the scan:

https://lore.kernel.org/linux-bluetooth/f648f2e11bb3c2974c32e605a85ac3a9fac944f1.camel@redhat.com/T/

> >>
> >> --
> >> Luiz Augusto von Dentz
> >
> >
> >



-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-03-01 22:40                                                 ` Luiz Augusto von Dentz
@ 2022-03-01 22:47                                                   ` Luiz Augusto von Dentz
  2022-03-02  2:31                                                     ` Luiz Augusto von Dentz
  2022-03-02  8:54                                                     ` Chris Clayton
  0 siblings, 2 replies; 19+ messages in thread
From: Luiz Augusto von Dentz @ 2022-03-01 22:47 UTC (permalink / raw)
  To: Chris Clayton; +Cc: Chris Murphy, Bluetooth, regressions

Hi Chris,

On Tue, Mar 1, 2022 at 2:40 PM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> Hi Chris,
>
> On Tue, Mar 1, 2022 at 11:40 AM Chris Clayton <chris2553@googlemail.com> wrote:
> >
> > Hi
> >
> > On 01/03/2022 18:57, Luiz Augusto von Dentz wrote:
> > > Hi Chris,
> > >
> > > On Tue, Mar 1, 2022 at 10:34 AM Luiz Augusto von Dentz
> > > <luiz.dentz@gmail.com> wrote:
> > >>
> > >> Hi Chris,
> > >>
> > >> On Tue, Mar 1, 2022 at 1:26 AM Chris Clayton <chris2553@googlemail.com> wrote:
> > >>>
> > >>> Hi Luiz,
> > >>>
> > >>> I guess you are hoping for PEBKAC :-)
> > >>>
> > >>> On 28/02/2022 21:20, Luiz Augusto von Dentz wrote:
> > >>>> Hi Chris,
> > >>>>
> > >>>> On Mon, Feb 28, 2022 at 1:02 PM Chris Clayton <chris2553@googlemail.com> wrote:
> > >>>>>
> > >>>>> Hi Luiz,
> > >>>>>
> > >>>>> On 28/02/2022 19:34, Luiz Augusto von Dentz wrote:
> > >>>>>> Hi Chris,
> > >>>>>>
> > >>>>>> On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
> > >>>>>>>
> > >>>>>>> Hi,
> > >>>>>>>
> > >>>>>>> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
> > >>>>>>>>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
> > >>>>>>>
> > >>>>>>> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
> > >>>>>>> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
> > >>>>>>>
> > >>>>>>> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
> > >>>>>>> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
> > >>>>>>>
> > >>>>>>> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
> > >>>>>>> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
> > >>>>>>> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
> > >>>>>>> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
> > >>>>>>>
> > >>>>>>>> Please record the HCI with btmon, it must be producing something since
> > >>>>>>>> it records even the mgmt commands.
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
> > >>>>>>> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
> > >>>>>>> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
> > >>>>>>> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
> > >>>>>>> to get the hci trace that Luiz has asked for.
> > >>>>>>>
> > >>>>>>> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
> > >>>>>>> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
> > >>>>>>> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
> > >>>>>>> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
> > >>>>>>> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
> > >>>>>>>
> > >>>>>>> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
> > >>>>>>> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
> > >>>>>>> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
> > >>>>>>> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
> > >>>>>>> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
> > >>>>>>> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
> > >>>>>>>
> > >>>>>>> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
> > >>>>>>> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
> > >>>>>>> however, I can provide any other diagnostics, please let me know.
> > >>>>>>>
> > >>>>>>> Chris
> > >>>>>>
> > >>>>>> Can you try with the following patch:
> > >>>>>>
> > >>>>>> https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
> > >>>>>>
> > >>>>>>
> > >>>>> Sorry, that patch has made no difference. After the first boot my headphones connected okay, but after a power-down and
> > >>>>> reboot they would not connect without an unload and reload of the btusb module.
> > >>>>
> > >>>> Can you tell us exactly what steps you are using? Are you applying on
> > >>>> top of what, rc6?
> > >>>>
> > >>>
> > >>> Until I got your patch yesterday, I was using a clone of
> > >>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git which I update frequently and have been doing so for as
> > >>> long as I can remember. Just in case there was a hidden flaw in that tree, I took a new clone yesterday, (so yes, the
> > >>> patch was tested on top of rc6) copied over the .config file and applied the patch. Then I built and installed the
> > >>> kernel, updated grub, powered off the laptop and booted into the new kernel. Once the laptop had booted and logged in to
> > >>> my LXQt desktop, I powered on my headphones and a connection was establisehed almost straight away. I powered the
> > >>> headphones off and the disconnection worked fine.
> > >>>
> > >>> Knowing that the problem crops up intermittently, I then rebooted the laptop. When the boot was complete, I then powered
> > >>> on my bluetooth headphones an waited for them to connect to the laptop. After about 20 seconds, a connection had not
> > >>> been established. I powered off the headphones, used modprobe to unload and then reload the btusb module. When I powered
> > >>> on the headphones, a connectiin was established within 2 or 3 seconds.
> > >
> > > Ive attempted 5 restart with 5.17.0-0.rc6.109.fc37.x86_64, my headset
> > > was able to reconnect every single time without any problem. The only
> >
> > For your five tests, did it connect on the first boot? As I've said, sometimes it fails to connect on the first boot,
> > but if it succeeds, it has always failed after a power-off and restart. Looking back at the notes I took during the
> > bisect, I've didn't have a single bisection step where I had to boot more more than twice to ascertain that it was a bad
> > kernel. As I said, I didn't mark a kernel as good until I'd had five successful boots.
>
> It did connect every single time.
>
> > > normally, once from gdm and then another time when gnome is loading,
> > > but I assume it is normal nowadays since it appears when switching
> > > session pipewire unregisters its audio endpoints.
> > >
> >
> > I don't use pipewire. Prior to 5.17, bluetooth has worked more or less trouble free for at least 4 years. I've read
> > about pipewire in Linux Magazine but don't see what it would bring to my party except complication.
> >
> > ends on how bluetoothd is being
> > > started or something.
> > >
> >
> > Did you see the warnings that read "Bluetooth: hci0: unexpected event 0xff length: 5 > 0"? That seems to indicate that
> > something is sending events that are unexpected. What effect will that have?  As I said, according to lshw, my system's
> > bluetooth hardware is Intel AX201. Is that what you are testing on?
>
> I have an AX200 on my system, AX201 is very similar so Id be surprised
> if that is the problem, btw Ive also got some unexpected events but
> that didn't stop the headset to reconnect.
>
> > >>> I've booted this laptop countless times over the last few days. Doing the bisect, I didn't mark a commit as good until I
> > >>> had done five boots and been able to connect my headphones on each boot. What I can say from that work is that two
> > >>> consecutive boots into a working kernel are very rare. I can't remeber an occasion when it took more than two boots to
> > >>> establish that a kernel was bad.
> > >>
> > >> Do commands such as bluetoothctl power on or scan on works? Try
> > >> running bluetoothd -dn from a shell (disable bluetooth.service), also
> > >> are there any settings changed in main.conf?
> > >>
> >
> > Sorry, I forgot to answer this question earlier. I haven't changed main.conf. Besides, my bluetooth devices connect
> > successfully every time with 5.16.11 and 5.15.25 kernels. As I've said before, that strongly suggests that there is a
> > code regression in 5.17.
>
> Not saying there isn't something wrong, we have sent a couple of fixes
> that doesn't seem to be merged yet, and we are working on another one
> for fixing the scan:
>
> https://lore.kernel.org/linux-bluetooth/f648f2e11bb3c2974c32e605a85ac3a9fac944f1.camel@redhat.com/T/

Btw, are you by any chance doing something like hciconfig hci0 up on
your init scripts?

> > >>
> > >> --
> > >> Luiz Augusto von Dentz
> > >
> > >
> > >
>
>
>
> --
> Luiz Augusto von Dentz



-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-03-01 22:47                                                   ` Luiz Augusto von Dentz
@ 2022-03-02  2:31                                                     ` Luiz Augusto von Dentz
  2022-03-02  6:55                                                       ` Luiz Augusto von Dentz
  2022-03-02  8:54                                                     ` Chris Clayton
  1 sibling, 1 reply; 19+ messages in thread
From: Luiz Augusto von Dentz @ 2022-03-02  2:31 UTC (permalink / raw)
  To: Chris Clayton; +Cc: Chris Murphy, Bluetooth, regressions

Hi Chris,

On Tue, Mar 1, 2022 at 2:47 PM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> Hi Chris,
>
> On Tue, Mar 1, 2022 at 2:40 PM Luiz Augusto von Dentz
> <luiz.dentz@gmail.com> wrote:
> >
> > Hi Chris,
> >
> > On Tue, Mar 1, 2022 at 11:40 AM Chris Clayton <chris2553@googlemail.com> wrote:
> > >
> > > Hi
> > >
> > > On 01/03/2022 18:57, Luiz Augusto von Dentz wrote:
> > > > Hi Chris,
> > > >
> > > > On Tue, Mar 1, 2022 at 10:34 AM Luiz Augusto von Dentz
> > > > <luiz.dentz@gmail.com> wrote:
> > > >>
> > > >> Hi Chris,
> > > >>
> > > >> On Tue, Mar 1, 2022 at 1:26 AM Chris Clayton <chris2553@googlemail.com> wrote:
> > > >>>
> > > >>> Hi Luiz,
> > > >>>
> > > >>> I guess you are hoping for PEBKAC :-)
> > > >>>
> > > >>> On 28/02/2022 21:20, Luiz Augusto von Dentz wrote:
> > > >>>> Hi Chris,
> > > >>>>
> > > >>>> On Mon, Feb 28, 2022 at 1:02 PM Chris Clayton <chris2553@googlemail.com> wrote:
> > > >>>>>
> > > >>>>> Hi Luiz,
> > > >>>>>
> > > >>>>> On 28/02/2022 19:34, Luiz Augusto von Dentz wrote:
> > > >>>>>> Hi Chris,
> > > >>>>>>
> > > >>>>>> On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
> > > >>>>>>>
> > > >>>>>>> Hi,
> > > >>>>>>>
> > > >>>>>>> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
> > > >>>>>>>>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
> > > >>>>>>>
> > > >>>>>>> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
> > > >>>>>>> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
> > > >>>>>>>
> > > >>>>>>> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
> > > >>>>>>> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
> > > >>>>>>>
> > > >>>>>>> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
> > > >>>>>>> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
> > > >>>>>>> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
> > > >>>>>>> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
> > > >>>>>>>
> > > >>>>>>>> Please record the HCI with btmon, it must be producing something since
> > > >>>>>>>> it records even the mgmt commands.
> > > >>>>>>>>
> > > >>>>>>>
> > > >>>>>>> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
> > > >>>>>>> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
> > > >>>>>>> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
> > > >>>>>>> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
> > > >>>>>>> to get the hci trace that Luiz has asked for.
> > > >>>>>>>
> > > >>>>>>> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
> > > >>>>>>> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
> > > >>>>>>> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
> > > >>>>>>> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
> > > >>>>>>> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
> > > >>>>>>>
> > > >>>>>>> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
> > > >>>>>>> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
> > > >>>>>>> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
> > > >>>>>>> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
> > > >>>>>>> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
> > > >>>>>>> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
> > > >>>>>>>
> > > >>>>>>> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
> > > >>>>>>> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
> > > >>>>>>> however, I can provide any other diagnostics, please let me know.
> > > >>>>>>>
> > > >>>>>>> Chris
> > > >>>>>>
> > > >>>>>> Can you try with the following patch:
> > > >>>>>>
> > > >>>>>> https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
> > > >>>>>>
> > > >>>>>>
> > > >>>>> Sorry, that patch has made no difference. After the first boot my headphones connected okay, but after a power-down and
> > > >>>>> reboot they would not connect without an unload and reload of the btusb module.
> > > >>>>
> > > >>>> Can you tell us exactly what steps you are using? Are you applying on
> > > >>>> top of what, rc6?
> > > >>>>
> > > >>>
> > > >>> Until I got your patch yesterday, I was using a clone of
> > > >>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git which I update frequently and have been doing so for as
> > > >>> long as I can remember. Just in case there was a hidden flaw in that tree, I took a new clone yesterday, (so yes, the
> > > >>> patch was tested on top of rc6) copied over the .config file and applied the patch. Then I built and installed the
> > > >>> kernel, updated grub, powered off the laptop and booted into the new kernel. Once the laptop had booted and logged in to
> > > >>> my LXQt desktop, I powered on my headphones and a connection was establisehed almost straight away. I powered the
> > > >>> headphones off and the disconnection worked fine.
> > > >>>
> > > >>> Knowing that the problem crops up intermittently, I then rebooted the laptop. When the boot was complete, I then powered
> > > >>> on my bluetooth headphones an waited for them to connect to the laptop. After about 20 seconds, a connection had not
> > > >>> been established. I powered off the headphones, used modprobe to unload and then reload the btusb module. When I powered
> > > >>> on the headphones, a connectiin was established within 2 or 3 seconds.
> > > >
> > > > Ive attempted 5 restart with 5.17.0-0.rc6.109.fc37.x86_64, my headset
> > > > was able to reconnect every single time without any problem. The only
> > >
> > > For your five tests, did it connect on the first boot? As I've said, sometimes it fails to connect on the first boot,
> > > but if it succeeds, it has always failed after a power-off and restart. Looking back at the notes I took during the
> > > bisect, I've didn't have a single bisection step where I had to boot more more than twice to ascertain that it was a bad
> > > kernel. As I said, I didn't mark a kernel as good until I'd had five successful boots.
> >
> > It did connect every single time.
> >
> > > > normally, once from gdm and then another time when gnome is loading,
> > > > but I assume it is normal nowadays since it appears when switching
> > > > session pipewire unregisters its audio endpoints.
> > > >
> > >
> > > I don't use pipewire. Prior to 5.17, bluetooth has worked more or less trouble free for at least 4 years. I've read
> > > about pipewire in Linux Magazine but don't see what it would bring to my party except complication.
> > >
> > > ends on how bluetoothd is being
> > > > started or something.
> > > >
> > >
> > > Did you see the warnings that read "Bluetooth: hci0: unexpected event 0xff length: 5 > 0"? That seems to indicate that
> > > something is sending events that are unexpected. What effect will that have?  As I said, according to lshw, my system's
> > > bluetooth hardware is Intel AX201. Is that what you are testing on?
> >
> > I have an AX200 on my system, AX201 is very similar so Id be surprised
> > if that is the problem, btw Ive also got some unexpected events but
> > that didn't stop the headset to reconnect.
> >
> > > >>> I've booted this laptop countless times over the last few days. Doing the bisect, I didn't mark a commit as good until I
> > > >>> had done five boots and been able to connect my headphones on each boot. What I can say from that work is that two
> > > >>> consecutive boots into a working kernel are very rare. I can't remeber an occasion when it took more than two boots to
> > > >>> establish that a kernel was bad.
> > > >>
> > > >> Do commands such as bluetoothctl power on or scan on works? Try
> > > >> running bluetoothd -dn from a shell (disable bluetooth.service), also
> > > >> are there any settings changed in main.conf?
> > > >>
> > >
> > > Sorry, I forgot to answer this question earlier. I haven't changed main.conf. Besides, my bluetooth devices connect
> > > successfully every time with 5.16.11 and 5.15.25 kernels. As I've said before, that strongly suggests that there is a
> > > code regression in 5.17.
> >
> > Not saying there isn't something wrong, we have sent a couple of fixes
> > that doesn't seem to be merged yet, and we are working on another one
> > for fixing the scan:
> >
> > https://lore.kernel.org/linux-bluetooth/f648f2e11bb3c2974c32e605a85ac3a9fac944f1.camel@redhat.com/T/
>
> Btw, are you by any chance doing something like hciconfig hci0 up on
> your init scripts?

Looks like I was able to reproduce but I still don't know the cause,
anyway the symptom is the following:

[23412.856410] remove_uuid:2273: hci0: sock 0000000049dcd70a
[23412.856467] mgmt_class_complete:2174: hci0: err 0
[23412.856470] mgmt_cmd_complete:176: sock 00000000d63e046a

It looks like the cmd->sk is wrong/corrupted, what is even more
strange is that the socket pointer does seem to match previously
connected MGMT clients and after a few attempts with btmgmt> power on
it does come back to life, very bizarre...

Can you try to enable some kernel debugs before you start bluetoothd:

echo "file net/bluetooth/mgmt.c +pfl" > /sys/kernel/debug/dynamic_debug/control
echo "file net/bluetooth/mgmt_util.c +pfl" >
/sys/kernel/debug/dynamic_debug/control

Maybe that should give us a clue what triggers it.

> > > >>
> > > >> --
> > > >> Luiz Augusto von Dentz
> > > >
> > > >
> > > >
> >
> >
> >
> > --
> > Luiz Augusto von Dentz
>
>
>
> --
> Luiz Augusto von Dentz



-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-03-02  2:31                                                     ` Luiz Augusto von Dentz
@ 2022-03-02  6:55                                                       ` Luiz Augusto von Dentz
  2022-03-02  9:59                                                         ` Chris Clayton
  0 siblings, 1 reply; 19+ messages in thread
From: Luiz Augusto von Dentz @ 2022-03-02  6:55 UTC (permalink / raw)
  To: Chris Clayton; +Cc: Chris Murphy, Bluetooth, regressions

Hi Chris,

On Tue, Mar 1, 2022 at 6:31 PM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> Hi Chris,
>
> On Tue, Mar 1, 2022 at 2:47 PM Luiz Augusto von Dentz
> <luiz.dentz@gmail.com> wrote:
> >
> > Hi Chris,
> >
> > On Tue, Mar 1, 2022 at 2:40 PM Luiz Augusto von Dentz
> > <luiz.dentz@gmail.com> wrote:
> > >
> > > Hi Chris,
> > >
> > > On Tue, Mar 1, 2022 at 11:40 AM Chris Clayton <chris2553@googlemail.com> wrote:
> > > >
> > > > Hi
> > > >
> > > > On 01/03/2022 18:57, Luiz Augusto von Dentz wrote:
> > > > > Hi Chris,
> > > > >
> > > > > On Tue, Mar 1, 2022 at 10:34 AM Luiz Augusto von Dentz
> > > > > <luiz.dentz@gmail.com> wrote:
> > > > >>
> > > > >> Hi Chris,
> > > > >>
> > > > >> On Tue, Mar 1, 2022 at 1:26 AM Chris Clayton <chris2553@googlemail.com> wrote:
> > > > >>>
> > > > >>> Hi Luiz,
> > > > >>>
> > > > >>> I guess you are hoping for PEBKAC :-)
> > > > >>>
> > > > >>> On 28/02/2022 21:20, Luiz Augusto von Dentz wrote:
> > > > >>>> Hi Chris,
> > > > >>>>
> > > > >>>> On Mon, Feb 28, 2022 at 1:02 PM Chris Clayton <chris2553@googlemail.com> wrote:
> > > > >>>>>
> > > > >>>>> Hi Luiz,
> > > > >>>>>
> > > > >>>>> On 28/02/2022 19:34, Luiz Augusto von Dentz wrote:
> > > > >>>>>> Hi Chris,
> > > > >>>>>>
> > > > >>>>>> On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
> > > > >>>>>>>
> > > > >>>>>>> Hi,
> > > > >>>>>>>
> > > > >>>>>>> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
> > > > >>>>>>>>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
> > > > >>>>>>>
> > > > >>>>>>> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
> > > > >>>>>>> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
> > > > >>>>>>>
> > > > >>>>>>> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
> > > > >>>>>>> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
> > > > >>>>>>>
> > > > >>>>>>> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
> > > > >>>>>>> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
> > > > >>>>>>> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
> > > > >>>>>>> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
> > > > >>>>>>>
> > > > >>>>>>>> Please record the HCI with btmon, it must be producing something since
> > > > >>>>>>>> it records even the mgmt commands.
> > > > >>>>>>>>
> > > > >>>>>>>
> > > > >>>>>>> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
> > > > >>>>>>> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
> > > > >>>>>>> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
> > > > >>>>>>> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
> > > > >>>>>>> to get the hci trace that Luiz has asked for.
> > > > >>>>>>>
> > > > >>>>>>> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
> > > > >>>>>>> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
> > > > >>>>>>> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
> > > > >>>>>>> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
> > > > >>>>>>> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
> > > > >>>>>>>
> > > > >>>>>>> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
> > > > >>>>>>> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
> > > > >>>>>>> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
> > > > >>>>>>> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
> > > > >>>>>>> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
> > > > >>>>>>> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
> > > > >>>>>>>
> > > > >>>>>>> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
> > > > >>>>>>> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
> > > > >>>>>>> however, I can provide any other diagnostics, please let me know.
> > > > >>>>>>>
> > > > >>>>>>> Chris
> > > > >>>>>>
> > > > >>>>>> Can you try with the following patch:
> > > > >>>>>>
> > > > >>>>>> https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>> Sorry, that patch has made no difference. After the first boot my headphones connected okay, but after a power-down and
> > > > >>>>> reboot they would not connect without an unload and reload of the btusb module.
> > > > >>>>
> > > > >>>> Can you tell us exactly what steps you are using? Are you applying on
> > > > >>>> top of what, rc6?
> > > > >>>>
> > > > >>>
> > > > >>> Until I got your patch yesterday, I was using a clone of
> > > > >>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git which I update frequently and have been doing so for as
> > > > >>> long as I can remember. Just in case there was a hidden flaw in that tree, I took a new clone yesterday, (so yes, the
> > > > >>> patch was tested on top of rc6) copied over the .config file and applied the patch. Then I built and installed the
> > > > >>> kernel, updated grub, powered off the laptop and booted into the new kernel. Once the laptop had booted and logged in to
> > > > >>> my LXQt desktop, I powered on my headphones and a connection was establisehed almost straight away. I powered the
> > > > >>> headphones off and the disconnection worked fine.
> > > > >>>
> > > > >>> Knowing that the problem crops up intermittently, I then rebooted the laptop. When the boot was complete, I then powered
> > > > >>> on my bluetooth headphones an waited for them to connect to the laptop. After about 20 seconds, a connection had not
> > > > >>> been established. I powered off the headphones, used modprobe to unload and then reload the btusb module. When I powered
> > > > >>> on the headphones, a connectiin was established within 2 or 3 seconds.
> > > > >
> > > > > Ive attempted 5 restart with 5.17.0-0.rc6.109.fc37.x86_64, my headset
> > > > > was able to reconnect every single time without any problem. The only
> > > >
> > > > For your five tests, did it connect on the first boot? As I've said, sometimes it fails to connect on the first boot,
> > > > but if it succeeds, it has always failed after a power-off and restart. Looking back at the notes I took during the
> > > > bisect, I've didn't have a single bisection step where I had to boot more more than twice to ascertain that it was a bad
> > > > kernel. As I said, I didn't mark a kernel as good until I'd had five successful boots.
> > >
> > > It did connect every single time.
> > >
> > > > > normally, once from gdm and then another time when gnome is loading,
> > > > > but I assume it is normal nowadays since it appears when switching
> > > > > session pipewire unregisters its audio endpoints.
> > > > >
> > > >
> > > > I don't use pipewire. Prior to 5.17, bluetooth has worked more or less trouble free for at least 4 years. I've read
> > > > about pipewire in Linux Magazine but don't see what it would bring to my party except complication.
> > > >
> > > > ends on how bluetoothd is being
> > > > > started or something.
> > > > >
> > > >
> > > > Did you see the warnings that read "Bluetooth: hci0: unexpected event 0xff length: 5 > 0"? That seems to indicate that
> > > > something is sending events that are unexpected. What effect will that have?  As I said, according to lshw, my system's
> > > > bluetooth hardware is Intel AX201. Is that what you are testing on?
> > >
> > > I have an AX200 on my system, AX201 is very similar so Id be surprised
> > > if that is the problem, btw Ive also got some unexpected events but
> > > that didn't stop the headset to reconnect.
> > >
> > > > >>> I've booted this laptop countless times over the last few days. Doing the bisect, I didn't mark a commit as good until I
> > > > >>> had done five boots and been able to connect my headphones on each boot. What I can say from that work is that two
> > > > >>> consecutive boots into a working kernel are very rare. I can't remeber an occasion when it took more than two boots to
> > > > >>> establish that a kernel was bad.
> > > > >>
> > > > >> Do commands such as bluetoothctl power on or scan on works? Try
> > > > >> running bluetoothd -dn from a shell (disable bluetooth.service), also
> > > > >> are there any settings changed in main.conf?
> > > > >>
> > > >
> > > > Sorry, I forgot to answer this question earlier. I haven't changed main.conf. Besides, my bluetooth devices connect
> > > > successfully every time with 5.16.11 and 5.15.25 kernels. As I've said before, that strongly suggests that there is a
> > > > code regression in 5.17.
> > >
> > > Not saying there isn't something wrong, we have sent a couple of fixes
> > > that doesn't seem to be merged yet, and we are working on another one
> > > for fixing the scan:
> > >
> > > https://lore.kernel.org/linux-bluetooth/f648f2e11bb3c2974c32e605a85ac3a9fac944f1.camel@redhat.com/T/
> >
> > Btw, are you by any chance doing something like hciconfig hci0 up on
> > your init scripts?
>
> Looks like I was able to reproduce but I still don't know the cause,
> anyway the symptom is the following:
>
> [23412.856410] remove_uuid:2273: hci0: sock 0000000049dcd70a
> [23412.856467] mgmt_class_complete:2174: hci0: err 0
> [23412.856470] mgmt_cmd_complete:176: sock 00000000d63e046a
>
> It looks like the cmd->sk is wrong/corrupted, what is even more
> strange is that the socket pointer does seem to match previously
> connected MGMT clients and after a few attempts with btmgmt> power on
> it does come back to life, very bizarre...
>
> Can you try to enable some kernel debugs before you start bluetoothd:
>
> echo "file net/bluetooth/mgmt.c +pfl" > /sys/kernel/debug/dynamic_debug/control
> echo "file net/bluetooth/mgmt_util.c +pfl" >
> /sys/kernel/debug/dynamic_debug/control
>
> Maybe that should give us a clue what triggers it.

Here is an attempt to fix the problem:

https://patchwork.kernel.org/project/bluetooth/patch/20220302064351.225212-1-luiz.dentz@gmail.com/

Also it probably make more sense to test with the following tree since
we are using it to push regression fixes:

https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/

> > > > >>
> > > > >> --
> > > > >> Luiz Augusto von Dentz
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
> > > --
> > > Luiz Augusto von Dentz
> >
> >
> >
> > --
> > Luiz Augusto von Dentz
>
>
>
> --
> Luiz Augusto von Dentz



-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-03-02  6:55                                                       ` Luiz Augusto von Dentz
@ 2022-03-02  9:59                                                         ` Chris Clayton
  0 siblings, 0 replies; 19+ messages in thread
From: Chris Clayton @ 2022-03-02  9:59 UTC (permalink / raw)
  To: Luiz Augusto von Dentz; +Cc: Chris Murphy, Bluetooth, regressions

Hi Luiz,

Good news...

On 02/03/2022 06:55, Luiz Augusto von Dentz wrote:

<snip>
>>
>> Looks like I was able to reproduce but I still don't know the cause,
>> anyway the symptom is the following:
>>
>> [23412.856410] remove_uuid:2273: hci0: sock 0000000049dcd70a
>> [23412.856467] mgmt_class_complete:2174: hci0: err 0
>> [23412.856470] mgmt_cmd_complete:176: sock 00000000d63e046a
>>
>> It looks like the cmd->sk is wrong/corrupted, what is even more
>> strange is that the socket pointer does seem to match previously
>> connected MGMT clients and after a few attempts with btmgmt> power on
>> it does come back to life, very bizarre...
>>
>> Can you try to enable some kernel debugs before you start bluetoothd:
>>
>> echo "file net/bluetooth/mgmt.c +pfl" > /sys/kernel/debug/dynamic_debug/control
>> echo "file net/bluetooth/mgmt_util.c +pfl" >
>> /sys/kernel/debug/dynamic_debug/control
>>
>> Maybe that should give us a clue what triggers it.
> 
> Here is an attempt to fix the problem:
> 
> https://patchwork.kernel.org/project/bluetooth/patch/20220302064351.225212-1-luiz.dentz@gmail.com/
> 
> Also it probably make more sense to test with the following tree since
> we are using it to push regression fixes:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/
> 

I've cloned bluetooth.git, applied the patch and installed the resultant kernel. I've booted into the kernel eight times
and on each occasion , my bluetooth devices connected successfully. Additionally, I've the latest updates from Linus'
tree into my local clone and applied your patch to that. That too has resulted in a working bluetooth service.

Thanks and well done to you and your colleagues.

For the patch above:

Tested-by: Chris Clayton <chris2553@googlemail.com>

>>>>>>>
>>>>>>> --
>>>>>>> Luiz Augusto von Dentz
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Luiz Augusto von Dentz
>>>
>>>
>>>
>>> --
>>> Luiz Augusto von Dentz
>>
>>
>>
>> --
>> Luiz Augusto von Dentz
> 
> 
> 

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
  2022-03-01 22:47                                                   ` Luiz Augusto von Dentz
  2022-03-02  2:31                                                     ` Luiz Augusto von Dentz
@ 2022-03-02  8:54                                                     ` Chris Clayton
  1 sibling, 0 replies; 19+ messages in thread
From: Chris Clayton @ 2022-03-02  8:54 UTC (permalink / raw)
  To: Luiz Augusto von Dentz; +Cc: Chris Murphy, Bluetooth, regressions



On 01/03/2022 22:47, Luiz Augusto von Dentz wrote:
> Hi Chris,
> 
> On Tue, Mar 1, 2022 at 2:40 PM Luiz Augusto von Dentz
> <luiz.dentz@gmail.com> wrote:
>>
>> Hi Chris,
>>
>> On Tue, Mar 1, 2022 at 11:40 AM Chris Clayton <chris2553@googlemail.com> wrote:
>>>
>>> Hi
>>>
>>> On 01/03/2022 18:57, Luiz Augusto von Dentz wrote:
>>>> Hi Chris,
>>>>
>>>> On Tue, Mar 1, 2022 at 10:34 AM Luiz Augusto von Dentz
>>>> <luiz.dentz@gmail.com> wrote:
>>>>>
>>>>> Hi Chris,
>>>>>
>>>>> On Tue, Mar 1, 2022 at 1:26 AM Chris Clayton <chris2553@googlemail.com> wrote:
>>>>>>
>>>>>> Hi Luiz,
>>>>>>
>>>>>> I guess you are hoping for PEBKAC :-)
>>>>>>
>>>>>> On 28/02/2022 21:20, Luiz Augusto von Dentz wrote:
>>>>>>> Hi Chris,
>>>>>>>
>>>>>>> On Mon, Feb 28, 2022 at 1:02 PM Chris Clayton <chris2553@googlemail.com> wrote:
>>>>>>>>
>>>>>>>> Hi Luiz,
>>>>>>>>
>>>>>>>> On 28/02/2022 19:34, Luiz Augusto von Dentz wrote:
>>>>>>>>> Hi Chris,
>>>>>>>>>
>>>>>>>>> On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
>>>>>>>>>>>> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
>>>>>>>>>>
>>>>>>>>>> That  bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
>>>>>>>>>> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
>>>>>>>>>>
>>>>>>>>>> blueman-manager 12.00.37 ERROR    Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
>>>>>>>>>> blueman-manager 12.00.37 ERROR    Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
>>>>>>>>>>
>>>>>>>>>> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
>>>>>>>>>> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
>>>>>>>>>> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
>>>>>>>>>> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
>>>>>>>>>>
>>>>>>>>>>> Please record the HCI with btmon, it must be producing something since
>>>>>>>>>>> it records even the mgmt commands.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
>>>>>>>>>> time did not limit it to net/bluetooth.  That was going okay until I ran into what I assume is the same batch of borked
>>>>>>>>>> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
>>>>>>>>>> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
>>>>>>>>>> to get the hci trace that Luiz has asked for.
>>>>>>>>>>
>>>>>>>>>> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
>>>>>>>>>> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
>>>>>>>>>> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
>>>>>>>>>> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
>>>>>>>>>> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
>>>>>>>>>>
>>>>>>>>>> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
>>>>>>>>>> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
>>>>>>>>>> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
>>>>>>>>>> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
>>>>>>>>>> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
>>>>>>>>>> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
>>>>>>>>>>
>>>>>>>>>> Since I now have a workround, I'm going stop the current bisection that I was doing.  I've done another couple of steps
>>>>>>>>>> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
>>>>>>>>>> however, I can provide any other diagnostics, please let me know.
>>>>>>>>>>
>>>>>>>>>> Chris
>>>>>>>>>
>>>>>>>>> Can you try with the following patch:
>>>>>>>>>
>>>>>>>>> https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Sorry, that patch has made no difference. After the first boot my headphones connected okay, but after a power-down and
>>>>>>>> reboot they would not connect without an unload and reload of the btusb module.
>>>>>>>
>>>>>>> Can you tell us exactly what steps you are using? Are you applying on
>>>>>>> top of what, rc6?
>>>>>>>
>>>>>>
>>>>>> Until I got your patch yesterday, I was using a clone of
>>>>>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git which I update frequently and have been doing so for as
>>>>>> long as I can remember. Just in case there was a hidden flaw in that tree, I took a new clone yesterday, (so yes, the
>>>>>> patch was tested on top of rc6) copied over the .config file and applied the patch. Then I built and installed the
>>>>>> kernel, updated grub, powered off the laptop and booted into the new kernel. Once the laptop had booted and logged in to
>>>>>> my LXQt desktop, I powered on my headphones and a connection was establisehed almost straight away. I powered the
>>>>>> headphones off and the disconnection worked fine.
>>>>>>
>>>>>> Knowing that the problem crops up intermittently, I then rebooted the laptop. When the boot was complete, I then powered
>>>>>> on my bluetooth headphones an waited for them to connect to the laptop. After about 20 seconds, a connection had not
>>>>>> been established. I powered off the headphones, used modprobe to unload and then reload the btusb module. When I powered
>>>>>> on the headphones, a connectiin was established within 2 or 3 seconds.
>>>>
>>>> Ive attempted 5 restart with 5.17.0-0.rc6.109.fc37.x86_64, my headset
>>>> was able to reconnect every single time without any problem. The only
>>>
>>> For your five tests, did it connect on the first boot? As I've said, sometimes it fails to connect on the first boot,
>>> but if it succeeds, it has always failed after a power-off and restart. Looking back at the notes I took during the
>>> bisect, I've didn't have a single bisection step where I had to boot more more than twice to ascertain that it was a bad
>>> kernel. As I said, I didn't mark a kernel as good until I'd had five successful boots.
>>
>> It did connect every single time.
>>
>>>> normally, once from gdm and then another time when gnome is loading,
>>>> but I assume it is normal nowadays since it appears when switching
>>>> session pipewire unregisters its audio endpoints.
>>>>
>>>
>>> I don't use pipewire. Prior to 5.17, bluetooth has worked more or less trouble free for at least 4 years. I've read
>>> about pipewire in Linux Magazine but don't see what it would bring to my party except complication.
>>>
>>> ends on how bluetoothd is being
>>>> started or something.
>>>>
>>>
>>> Did you see the warnings that read "Bluetooth: hci0: unexpected event 0xff length: 5 > 0"? That seems to indicate that
>>> something is sending events that are unexpected. What effect will that have?  As I said, according to lshw, my system's
>>> bluetooth hardware is Intel AX201. Is that what you are testing on?
>>
>> I have an AX200 on my system, AX201 is very similar so Id be surprised
>> if that is the problem, btw Ive also got some unexpected events but
>> that didn't stop the headset to reconnect.
>>
>>>>>> I've booted this laptop countless times over the last few days. Doing the bisect, I didn't mark a commit as good until I
>>>>>> had done five boots and been able to connect my headphones on each boot. What I can say from that work is that two
>>>>>> consecutive boots into a working kernel are very rare. I can't remeber an occasion when it took more than two boots to
>>>>>> establish that a kernel was bad.
>>>>>
>>>>> Do commands such as bluetoothctl power on or scan on works? Try
>>>>> running bluetoothd -dn from a shell (disable bluetooth.service), also
>>>>> are there any settings changed in main.conf?
>>>>>
>>>
>>> Sorry, I forgot to answer this question earlier. I haven't changed main.conf. Besides, my bluetooth devices connect
>>> successfully every time with 5.16.11 and 5.15.25 kernels. As I've said before, that strongly suggests that there is a
>>> code regression in 5.17.
>>
>> Not saying there isn't something wrong, we have sent a couple of fixes
>> that doesn't seem to be merged yet, and we are working on another one
>> for fixing the scan:
>>
>> https://lore.kernel.org/linux-bluetooth/f648f2e11bb3c2974c32e605a85ac3a9fac944f1.camel@redhat.com/T/
> 
> Btw, are you by any chance doing something like hciconfig hci0 up on
> your init scripts?
> 
Yes , that is included in /etc/init.d/bluetooth.
>>>>>
>>>>> --
>>>>> Luiz Augusto von Dentz
>>>>
>>>>
>>>>
>>
>>
>>
>> --
>> Luiz Augusto von Dentz
> 
> 
> 

^ permalink raw reply	[flat|nested] 19+ messages in thread

[parent not found: <0ab4466e-1fa8-1904-3f71-770fbd28c83a@leemhuis.info>]

* Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices #forregzbot
       [not found] ` <0ab4466e-1fa8-1904-3f71-770fbd28c83a@leemhuis.info>
@ 2022-03-04  6:21   ` Thorsten Leemhuis
  0 siblings, 0 replies; 19+ messages in thread
From: Thorsten Leemhuis @ 2022-03-04  6:21 UTC (permalink / raw)
  To: regressions

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

#regzbot fixed-by: 008ee9eb8a11bcabf12c91771dd4f470b082bd44

https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=008ee9eb8a11bcabf12c91771dd4f470b082bd44

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.



On 24.02.22 11:26, Thorsten Leemhuis wrote:
> [TLDR: I'm adding the regression report below to regzbot, the Linux
> kernel regression tracking bot; all text you find below is compiled from
> a few templates paragraphs you might have encountered already already
> from similar mails.]
> 
> Hi, this is your Linux kernel regression tracker speaking.
> 
> Thanks for the report and CCing the regression list in a downstream reply.
> 
> To be sure this issue doesn't fall through the cracks unnoticed, I'm
> adding it to regzbot, my Linux kernel regression tracking bot:
> 
> #regzbot ^introduced v5.16..
> #regzbot title net: bluetooth: qualcom and intel adapters, unable to
> reliably connect to bluetooth devices
> #regzbot ignore-activity
> 
> Reminder for developers: when fixing the issue, please add a 'Link:'
> tags pointing to the report (the mail quoted above) using
> lore.kernel.org/r/, as explained in
> 'Documentation/process/submitting-patches.rst' and
> 'Documentation/process/5.Posting.rst'. This allows the bot to connect
> the report with any patches posted or committed to fix the issue; this
> again allows the bot to show the current status of regressions and
> automatically resolve the issue when the fix hits the right tree.
> 
> I'm sending this to everyone that got the initial report, to make them
> aware of the tracking. I also hope that messages like this motivate
> people to directly get at least the regression mailing list and ideally
> even regzbot involved when dealing with regressions, as messages like
> this wouldn't be needed then.
> 
> Don't worry, I'll send further messages wrt to this regression just to
> the lists (with a tag in the subject so people can filter them away), if
> they are relevant just for regzbot. With a bit of luck no such messages
> will be needed anyway.
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> 
> P.S.: As the Linux kernel's regression tracker I'm getting a lot of
> reports on my table. I can only look briefly into most of them and lack
> knowledge about most of the areas they concern. I thus unfortunately
> will sometimes get things wrong or miss something important. I hope
> that's not the case here; if you think it is, don't hesitate to tell me
> in a public reply, it's in everyone's interest to set the public record
> straight.
> 
> 
> 
> 
> 
> On 11.02.22 02:44, Chris Murphy wrote:
>> Since kernel 5.17, some users are seeing problems connecting to
>> bluetooth devices, the problem doesn't happen with 5.16 series
>> kernels.
>>
>> So far two different devices are affected, although it's possible it's
>> not even device related, but could be the interface between kernel and
>> user space.
>>
>> Case 1:
>>
>> Bus 001 Device 003: ID 0cf3:e301 Qualcomm Atheros Communications
>>
>> Not seeing anything that stands out in dmesg, bluetoothd -d shows
>> various curious messages like
>>
>> bluetoothd[5889]: src/service.c:change_state() 0x7f33becdebc0: device
>> 94:65:2D:DC:F4:A7 profile avrcp-controller state changed: disconnected
>> -> unavailable (0)
>> and
>> bluetoothd[5889]: src/service.c:change_state() 0x7f33becd91e0: device
>> 94:65:2D:DC:F4:A7 profile Hands-Free Voice gateway state changed:
>> unavailable -> disconnected (0)
>>
>>
>> Case 2:
>>
>> Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560
>> Jefferson Peak (JfP)
>> [    5.923865] kernel: Bluetooth: hci0: Found device firmware:
>> intel/ibt-17-16-1.sfi
>> [    5.930536] kernel: Bluetooth: hci0: Boot Address: 0x40800
>> [    5.930539] kernel: Bluetooth: hci0: Firmware Version: 60-44.21
>> ...
>> [16102.640651] Bluetooth: hci0: unexpected event 0xff length: 5 > 0
>> [16102.640802] Bluetooth: hci0: Waiting for device to boot
>> [16102.654712] Bluetooth: hci0: Device booted in 13698 usecs
>> [16102.654753] Bluetooth: hci0: unexpected event 0xff length: 7 > 0
>> [16102.655907] Bluetooth: hci0: Found Intel DDC parameters:
>> intel/ibt-17-16-1.ddc
>> [16102.657821] Bluetooth: hci0: Applying Intel DDC parameters completed
>> [16102.658829] Bluetooth: hci0: Firmware revision 0.1 build 60 week 44 2021
>> [17422.210558] Bluetooth: hci0: command 0x0c03 tx timeout
>> [17430.338412] Bluetooth: hci0: HCI reset during shutdown failed
>>
>> [15975.194153] bluetoothd[42895]:
>> src/adapter.c:device_found_callback() hci0 addr 75:0B:19:0C:47:F6,
>> rssi -82 flags 0x0000 eir_len 17
>> [15975.194412] bluetoothd[42895]:
>> src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL,
>> get offload support failed
>> [15975.194510] bluetoothd[42895]: src/device.c:device_set_legacy() legacy 0
>> [15975.194599] bluetoothd[42895]:
>> src/device.c:device_set_rssi_with_delta() rssi -82 delta 1
>> [15975.194661] bluetoothd[42895]: src/device.c:device_set_flags() flags 26
>>
>> There are many many of the "Manager is NULL, get offload support
>> failed" messages in this case. I'm not entirely sure the root causes
>> are the same for the two cases.
>>
>> Downstream bug has attachments (dmesg, btmon, lsbsb, journalctl
>> snippet with bluetoothd in debug, for both)
>> https://bugzilla.redhat.com/show_bug.cgi?id=2053283
>>
>> Thanks,
>>
> 

^ permalink raw reply	[flat|nested] 19+ messages in thread

end of thread, other threads:[~2022-03-04  6:21 UTC | newest]

Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAJCQCtSeUtHCgsHXLGrSTWKmyjaQDbDNpP4rb0i+RE+L2FTXSA@mail.gmail.com>
     [not found] ` <CAJCQCtRiTQ1BTEHugxhS-zmXFG4qi4WLxsRyZsG9-_Q0isM+7Q@mail.gmail.com>
     [not found]   ` <CAJCQCtS35JeABLDBaNpfgxjq+ZJ9rZgwtRnSYLNm8tMwtdYGMw@mail.gmail.com>
     [not found]     ` <CABBYNZKTSe83iP4tm36we4cpAbeGUbEw9frZD1wCM9yo1zry5w@mail.gmail.com>
     [not found]       ` <CAJCQCtTpHQe2co3fLNs5csKQchmwH=3YwQOvFnuc2nhjRseVnw@mail.gmail.com>
     [not found]         ` <9ad505e1-7b59-7ebf-378b-23a6c0e25802@googlemail.com>
     [not found]           ` <CABBYNZ+9tUKgLyUWM5vkMW8vHxYsXv6DEaDWdHt8xTTs6puGQA@mail.gmail.com>
     [not found]             ` <aaeb4131-d177-d41e-617b-b0060cd83c92@googlemail.com>
     [not found]               ` <CABBYNZLB+8UzhzttMrKbHW_+-A1EsY9iT5Y55VuOOEPuD4kAHQ@mail.gmail.com>
     [not found]                 ` <b1a4a920-dbba-58be-72b4-2c95b9b79283@googlemail.com>
     [not found]                   ` <82216882-463a-8976-e6bc-4a8919107a31@googlemail.com>
     [not found]                     ` <CABBYNZ+mO1gQgfwhemY9cqbi8vNLm_60A9c1vPYT2tH4rhgFww@mail.gmail.com>
     [not found]                       ` <a35b4b75-bb64-89c8-bacd-d58ed8576272@googlemail.com>
     [not found]                         ` <2ce6175c-74ec-8469-80a5-374bd1429542@googlemail.com>
     [not found]                           ` <CABBYNZJNTOT-mEQe2cfZiEX6A2pR7+sacBqtBRPRZY69YmgtvA@mail.gmail.com>
2022-02-24 10:08                             ` bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices Chris Clayton
2022-02-24 15:16                               ` Luiz Augusto von Dentz
2022-02-24 16:18                                 ` Thorsten Leemhuis
2022-02-26  8:04                                 ` Chris Clayton
2022-02-28 19:34                                   ` Luiz Augusto von Dentz
2022-02-28 21:02                                     ` Chris Clayton
2022-02-28 21:20                                       ` Luiz Augusto von Dentz
2022-03-01  9:26                                         ` Chris Clayton
2022-03-01 18:34                                           ` Luiz Augusto von Dentz
2022-03-01 18:56                                             ` Chris Clayton
2022-03-01 18:57                                             ` Luiz Augusto von Dentz
2022-03-01 19:40                                               ` Chris Clayton
2022-03-01 22:40                                                 ` Luiz Augusto von Dentz
2022-03-01 22:47                                                   ` Luiz Augusto von Dentz
2022-03-02  2:31                                                     ` Luiz Augusto von Dentz
2022-03-02  6:55                                                       ` Luiz Augusto von Dentz
2022-03-02  9:59                                                         ` Chris Clayton
2022-03-02  8:54                                                     ` Chris Clayton
     [not found] ` <0ab4466e-1fa8-1904-3f71-770fbd28c83a@leemhuis.info>
2022-03-04  6:21   ` bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices #forregzbot Thorsten Leemhuis

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).