Open eLEcTRiCZiTy opened 4 years ago
hashworks
commented
4 years ago I'm running the mainline 5.8.9 kernel on the Surface Go 2 (since basically everything works out of the box) and I don't have this issue. Could you try that one out and report back if this "solves" your issue?
Firefnix
commented
4 years ago I have the same issue with a SP 2017. I'm on Ubuntu 20.04, so I use the Debian-like repo and the 5.8.6 kernel.
$ uname -a Linux surface 5.8.6-surface #1 SMP Fri Sep 4 17:57:45 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep surface hi libwacom 0.32-surface-1 amd64 libwacom ii libwacom-surface 1.5-2 amd64 Wacom model feature query library ii linux-headers-5.1.15-surface-linux-surface 5.1.15-surface-linux-surface-8 amd64 Linux kernel headers for 5.1.15-surface-linux-surface on amd64 ii linux-headers-5.8.10-surface 5.8.10-surface-3 amd64 Linux kernel headers for 5.8.10-surface on amd64 ii linux-headers-5.8.14-surface 5.8.14-surface-1 amd64 Linux kernel headers for 5.8.14-surface on amd64 ii linux-headers-5.8.6-surface 5.8.6-surface-1 amd64 Linux kernel headers for 5.8.6-surface on amd64 ii linux-headers-surface 5.8.14-surface-1 amd64 rc linux-image-5.7.10-surface 5.7.10-surface-1 amd64 Linux kernel, version 5.7.10-surface rc linux-image-5.7.11-surface 5.7.11-surface-1 amd64 Linux kernel, version 5.7.11-surface rc linux-image-5.7.12-surface 5.7.12-surface-1 amd64 Linux kernel, version 5.7.12-surface rc linux-image-5.7.15-surface 5.7.15-surface-1 amd64 Linux kernel, version 5.7.15-surface rc linux-image-5.7.7-surface 5.7.7-surface-2 amd64 Linux kernel, version 5.7.7-surface rc linux-image-5.7.8-surface 5.7.8-surface-2 amd64 Linux kernel, version 5.7.8-surface ii linux-image-5.8.10-surface 5.8.10-surface-3 amd64 Linux kernel, version 5.8.10-surface ii linux-image-5.8.14-surface 5.8.14-surface-1 amd64 Linux kernel, version 5.8.14-surface rc linux-image-5.8.3-surface 5.8.3-surface-1 amd64 Linux kernel, version 5.8.3-surface rc linux-image-5.8.5-surface 5.8.5-surface-1 amd64 Linux kernel, version 5.8.5-surface ii linux-image-5.8.6-surface 5.8.6-surface-1 amd64 Linux kernel, version 5.8.6-surface rc linux-image-5.8.7-surface 5.8.7-surface-1 amd64 Linux kernel, version 5.8.7-surface rc linux-image-5.8.8-surface 5.8.8-surface-1 amd64 Linux kernel, version 5.8.8-surface ii linux-image-surface 5.8.14-surface-1 amd64 ii linux-libc-dev-surface:amd64 5.7.7-1 amd64 Linux support headers for userspace development ii surface-ipts-firmware 20200929-1 amd64 Intel Precise Touch and Stylus firmware for Microsoft Surface devices
[ 542.488727] usb 1-7: new full-speed USB device number 5 using xhci_hcd [ 542.645937] usb 1-7: New USB device found, idVendor=045e, idProduct=09c0, bcdDevice= 0.07 [ 542.645946] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 542.645950] usb 1-7: Product: Surface Type Cover [ 542.645954] usb 1-7: Manufacturer: Microsoft [ 542.656072] input: Microsoft Surface Type Cover Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:045E:09C0.0003/input/input16 [ 542.713322] input: Microsoft Surface Type Cover Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:045E:09C0.0003/input/input17 [ 542.713582] input: Microsoft Surface Type Cover Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:045E:09C0.0003/input/input18 [ 542.713716] input: Microsoft Surface Type Cover UNKNOWN as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:045E:09C0.0003/input/input19 [ 542.713844] input: Microsoft Surface Type Cover Touchpad as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:045E:09C0.0003/input/input20 [ 542.714026] input: Microsoft Surface Type Cover UNKNOWN as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:045E:09C0.0003/input/input21 [ 542.714145] input: Microsoft Surface Type Cover UNKNOWN as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:045E:09C0.0003/input/input22 [ 542.714274] input: Microsoft Surface Type Cover UNKNOWN as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:045E:09C0.0003/input/input23 [ 542.714499] hid-multitouch 0003:045E:09C0.0003: input,hiddev0,hidraw0: USB HID v1.11 Keyboard [Microsoft Surface Type Cover] on usb-0000:00:14.0-7/input0
After a reboot, the touchpad worked as expected, until I locked/unlocked it. So sleeping seems to cause the same unexpected behaviour.
AquaJerry
commented
4 years ago Similar issue.
Sometimes after the type cover closes and then opens again, some actions by touchpad such as 2-finger scroll, 2-finger-tap right click, become unavailable. Tap-to-click still works but the mouse speed gets faster and makes it hard to control. Restart xorg server does not help. Reboot can fix it but is not the right way.
# /usr/share/X11/xorg.conf.d/40-libinput.confSection "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "NaturalScrolling" "on" # this line is added Option "Tapping" "on" # and this, bringing more actions metioned above Driver "libinput" EndSection
coolteddy
commented
3 years ago Similar issue.
Sometimes after the type cover closes and then opens again, some actions by touchpad such as 2-finger scroll, 2-finger-tap right click, become unavailable. Tap-to-click still works but the mouse speed gets faster and makes it hard to control. Restart xorg server does not help. Reboot can fix it but is not the right way.
* model: Surface Go 2 * uname: Linux 5.8.11-1-MANJARO x86_64 * currently using modified part of configuration file:# /usr/share/X11/xorg.conf.d/40-libinput.conf Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "NaturalScrolling" "on" # this line is added Option "Tapping" "on" # and this, bringing more actions metioned above Driver "libinput" EndSection
Same thing for me and updated the above file as well, no help I have a type cover and two finger scrolling got a problem. To resolve the issue, just pull apart the touch cover keyboard and reattached it. That solve it.
RichardODonoghue
commented
3 years ago I too have had this issue however it has only happened once or twice and not for sometime...
localjo
commented
3 years ago To resolve the issue, just pull apart the touch cover keyboard and reattached it. That solve it.
I found this issue after searching to figure out why two finger scrolling wasn't working for me. This was the solution. After disconnecting and re-connecting the touch cover keyboard, two finger scrolling works!
eLEcTRiCZiTy
commented
3 years ago Reattaching of keyboard does not solve the issue. This not-so-solution not guarantee that my system settings are loaded properly. Sometimes it is just reset to default settings. + Reattaching the keyboard every time I need to use the tablet is really bad solution.
sysrq-reisub
commented
3 years ago I can also confirm this, present on kernel 5.11.0-25-generic, ubuntu 20.04 LTS
Are you all using deep sleep?
rvbg
commented
2 years ago This issue is still present on Arch kernel 5.17.3-arch1-1, Surface Go 2 with alcantra keyboard cover. Occurs after every boot, reconnecting the keyboard every time solves the problem in the short term. This disrupts the user experience of the device immensely. Apparently occurs independently of the desktop environment as well as X11 and Wayland.
AquaJerry
commented
2 years ago For friends who just want a basic use of linux, I strongly recommend Windows Subsystem for Linux 2 (WSL2) that I'm using. It is easier to use and you can use 3 systems at the same time, even with inter-visitable filesystems: Windows, Ubuntu or other supported distros on Windows, Android if your phone can bind to Windows. However, this is a little bit out of the topic of surface, both are presented by Microsoft though😂.
qzed
commented
2 years ago I wonder if this is related to the "modes" in which (modern) touchpads can be in (see e.g. MS docs). Could be that something like folding causes the device to re-initialize, without the kernel sending the request for multi-touch. So it stays in single-touch, which probably means all sorts of differences (potentially different speed, no tapping, ...).
Someone would probably have to check with hid-recorder.
rvbg
commented
2 years ago The keyboard cover touchpad gets recognized as two input devices, namely "Microsoft Surface Type Cover Mouse" and "Microsoft Surface Type Cover Touchpad". This is nothing unusual as far as I understand, but what is unusual is the fact that the virtual mouse device is sometimes used by the system as an input device and the touchpad device is apparently locked as a result. The whole thing can also be tested quite easily with evtest, because with it, you can see which input device is producing the mouse movement. No matter what mode the cover logged in with, the output from dmesg and udevadm seems to remain the same.
A solution would have to be found so that the cover always registers with the touchpad and not with the mouse, but for now, I disabled the virtual mouse within KDE under input devices -> mouse -> select "Microsoft Surface Type Cover Mouse" -> disable. Then the mouse doesn't work at all when the cover registers like this, but at least I prefer that to this half-functioning mode.
$ sudo libinput list-devices
[...]
Device: Microsoft Surface Type Cover Mouse
Kernel: /dev/input/event19
Group: 4
Seat: seat0, default
Capabilities: pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: n/a
Calibration: n/a
Scroll methods: button
Click methods: none
Disable-w-typing: n/a
Accel profiles: flat *adaptive
Rotation: n/a
Device: Microsoft Surface Type Cover Touchpad
Kernel: /dev/input/event20
Group: 4
Seat: seat0, default
Size: 94x52mm
Capabilities: pointer gesture
Tap-to-click: disabled
Tap-and-drag: enabled
Tap drag lock: disabled
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: *two-finger edge
Click methods: *button-areas clickfinger
Disable-w-typing: enabled
Accel profiles: flat *adaptive
Rotation: n/a
PhilDevProg
commented
1 year ago I have a similar problem on the Go 3. Sometimes after it started the multitouch gestures and tap to click doesn't work. Sometimes this also happens when its flipped for a long time. Disconnecting and reconnecting fixes it.
qzed
commented
1 year ago Any chance this could be related to https://github.com/linux-surface/linux-surface/issues/1059? I.e. can you try adding usbcore.quirks=045e:09b5:g to the kernel command line (replace 045e:09b5 with your respective device IDs) and see if that helps?
qzed
commented
1 year ago The keyboard cover touchpad gets recognized as two input devices, namely "Microsoft Surface Type Cover Mouse" and "Microsoft Surface Type Cover Touchpad". This is nothing unusual as far as I understand, but what is unusual is the fact that the virtual mouse device is sometimes used by the system as an input device and the touchpad device is apparently locked as a result. The whole thing can also be tested quite easily with evtest, because with it, you can see which input device is producing the mouse movement. No matter what mode the cover logged in with, the output from dmesg and udevadm seems to remain the same.
Sorry for the very late reply. This is exactly what I meant via "modes". The "mouse" device is essentially the single-touch fallback device. A special feature request is needed to switch it to multi-touch mode. So it seems that this either isn't being sent or it gets lost. As this is related to the configuration step of the touchpad, #1059 might be related, so you should try that (see my comment above).
PhilDevProg
commented
1 year ago Any chance this could be related to https://github.com/linux-surface/linux-surface/issues/1059? I.e. can you try adding
usbcore.quirks=045e:09b5:gto the kernel command line (replace045e:09b5with your respective device IDs) and see if that helps?
Sure, I can try. What do I have to do to add it to my kernel command line?
qzed
commented
1 year ago You need to figure out the device ID of the touchpad. Since you have a Go 3 it's probably the same, but you can use sudo evtest to verify that. Run that, select the touchpad device (ideally verify it's the correct device by moving the cursor, events should show up as soon as you touch it) and look for the line Input device ID: bus <X> vendor <Y> product <Z>... at the top. Those <Y> and <Z> are the IDs you need.
Then add usbcore.quirks=<Y>:<Z>:g to the command line. How exactly you can do that depends on the bootloader you use. For grub, you can either add it permanently by editing /etc/defaults/grub and adding it to GRUB_CMDLINE_LINUX_DEFAULT (don't forget to re-generate the grub config afterwards with update-grub or something like that) or temporarily by pressing e when selecting the boot entry and appending it to the other options in the linux command field.
PhilDevProg
commented
1 year ago @qzed Unfortunately that didn't help.
WolfWings
commented
1 year ago Just to confirm @PhilDevProg what's the output from cat /proc/cmdline to confirm the quirk's in the command-line properly?
Edit: And sorry about sniping your reply @qzed just was closing this tab and saw the comment, trying to help things along wherever I can. :)
qzed
commented
1 year ago Can you check that the quirk got applied properly via cat /sys/bus/usb/devices/B-D/quirks? You can find the full path via lsusb where B is the bus number and D is the device number.
Edit: or See the comment by @WolfWings above. A full dmesg log might also help to verify that.
PhilDevProg
commented
1 year ago Just to confirm @PhilDevProg what's the output from
cat /proc/cmdlineto confirm the quirk's in the command-line properly?
cat /proc/cmdline:
BOOT_IMAGE=/vmlinuz-6.1.11-1.surface.fc37.x86_64 root=UUID=515e9922-d2db-4dd7-9176-10cb9541c00e ro rootflags=subvol=root rd.luks.uuid=luks-6126b5b3-2fe7-478b-894a-ad4600b2ccc9 rhgb quiet usbcore.quirks=045e:09b5:g
A full dmesg log might also help to verify that.
qzed
commented
1 year ago I guess that looks like it should be applied. Just to be absolutely sure though, can you post the output of cat /sys/bus/usb/devices/1-7/quirks?
qzed
commented
1 year ago Edit: And sorry about sniping your reply @qzed just was closing this tab and saw the comment, trying to help things along wherever I can. :)
Don't worry about things like that, and don't let that stop you from commenting :)
PhilDevProg
commented
1 year ago I guess that looks like it should be applied. Just to be absolutely sure though, can you post the output of
cat /sys/bus/usb/devices/1-7/quirks?
It returns 0x40
qzed
commented
1 year ago Okay. That means it really is applied, but doesn't seem to help. So I guess there might be multiple issues at play here...
WolfWings
commented
1 year ago @PhilDevProg Are you on X, or Wayland? I did see the 'synaptics' driver behave differently on X.
PhilDevProg
commented
1 year ago @PhilDevProg Are you on X, or Wayland? I did see the 'synaptics' driver behave differently on X.
Wayland
PhilDevProg
commented
1 year ago @qzed If it helps you, the touchpad also works correctly after flipping the typing cover to the back and then reflipping it to Laptop mode.
qzed
commented
1 year ago That might actually help, at least to check a theory. Can you post a dmesg excerpt of flipping the cover? I think if it's a re-initialization thing, the input devices should be removed and re-added by flipping.
PhilDevProg
commented
1 year ago @qzed Here: dmesg.txt Flipping also sometimes causes this issue. I had to flip 2/3 times until it was working again correctly.
qzed
commented
1 year ago Okay, so I can see devices being removed and added below, two or three times, I'm not entirely sure. I assume it did work at the end, after the last time that new devices are showing up. There's also one reset going on at some point.
Did the behavior differ in any kind between the failed attempts? And do you have any idea whether the reset is just being triggered randomly or if it's an attempted flip?
So I think here's what to look out for:
[...]
[ 80.781949] usb 1-7: reset full-speed USB device number 3 using xhci_hcd
[ 112.184215] usb 1-7: USB disconnect, device number 3
[ 112.518321] usb 1-7: new full-speed USB device number 4 using xhci_hcd
[ 114.912924] usb 1-7: New USB device found, idVendor=045e, idProduct=09b5, bcdDevice= 0.04
[ 114.912931] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 114.912934] usb 1-7: Product: Surface Keyboard
[ 114.912936] usb 1-7: Manufacturer: Microsoft
[... input device setup]
[ 141.962517] usb 1-7: USB disconnect, device number 4
[ 149.651389] usb 1-7: new full-speed USB device number 5 using xhci_hcd
[ 151.826993] usb 1-7: unable to read config index 0 descriptor/start: -71
[ 151.827006] usb 1-7: can't read configurations, error -71
[ 152.629347] usb 1-7: new full-speed USB device number 6 using xhci_hcd
[ 154.977640] usb 1-7: New USB device found, idVendor=045e, idProduct=09b5, bcdDevice= 0.04
[ 154.977653] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 154.977659] usb 1-7: Product: Surface Keyboard
[ 154.977663] usb 1-7: Manufacturer: Microsoft
[... input device setup]
[...]One interesting thing is that there is an error reading configurations in the second try. Based on the timestamp, I guess it's automatically resetting the device, but that could also be you trying to flip the device back again.
Can you maybe try this a couple more times and monitor the dmesg log for resets and errors like this (and ideally wait a bit between flipping back and forth)?
PhilDevProg
commented
1 year ago Did the behavior differ in any kind between the failed attempts? And do you have any idea whether the reset is just being triggered randomly or if it's an attempted flip?
I think the cursor wasn't so fast anymore. I think it's an attampted flip.
Can you maybe try this a couple more times and monitor the dmesg log for resets and errors like this (and ideally wait a bit between flipping back and forth)?
What exactly do you mean by that?
qzed
commented
1 year ago What exactly do you mean by that?
Run dmesg -w (or journalctl -kf). This should show you a running kernel log. Then try to flip the cover back and forth. After each change (so after flipping it to tablet mode and then also after flipping it to laptop mode), check what has been added in the log (should be similar to the above). Flipping it into tablet mode should disconnect the USB devices, flipping it back should re-connect it. Also check if there have been any errors (like the unable to read config index 0 descriptor/start: -71) and resets (reset full-speed USB device) and check whether you seeing any errors has any relation to the touchpad working properly or not.
My current guess is that there's some delay necessary to properly initialize the device. So if the kernel is asking it too early, it fails silently. Maybe if it's asking it way too early it fails with the error above (-71) and then the second try works.
PhilDevProg
commented
1 year ago Ok, I'll try that the next time it happens. Weirdly after I reinstalled Fedora I now can't reproduce it anymore (easily).
PhilDevProg
commented
1 year ago @qzed It now happened again after booting but I wasn't able to fix it by flipping the type cover. Only removing it and reconnecting it fixed it.
PhilDevProg
commented
1 year ago Flipping the keyboard also doesn't do anything to dmesg -w or journalctl -kf. Only on removing and reconnecting I get this:
[ 98.289302] usb 1-7: USB disconnect, device number 5
[ 103.090390] usb 1-7: new full-speed USB device number 6 using xhci_hcd
[ 105.472628] usb 1-7: New USB device found, idVendor=045e, idProduct=09b5, bcdDevice= 0.04
[ 105.472645] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 105.472652] usb 1-7: Product: Surface Keyboard
[ 105.472657] usb 1-7: Manufacturer: Microsoft
[ 105.478329] input: Microsoft Surface Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:045E:09B5.0012/input/input57
[ 105.531093] hid-generic 0003:045E:09B5.0012: input,hidraw1: USB HID v1.11 Keyboard [Microsoft Surface Keyboard] on usb-0000:00:14.0-7/input0
[ 105.533409] input: Microsoft Surface Keyboard Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1/0003:045E:09B5.0013/input/input58
[ 105.585721] input: Microsoft Surface Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1/0003:045E:09B5.0013/input/input60
[ 105.586089] hid-generic 0003:045E:09B5.0013: input,hiddev96,hidraw2: USB HID v1.11 Device [Microsoft Surface Keyboard] on usb-0000:00:14.0-7/input1
[ 105.587684] hid-generic 0003:045E:09B5.0014: hiddev97,hidraw3: USB HID v1.11 Device [Microsoft Surface Keyboard] on usb-0000:00:14.0-7/input2
[ 105.591016] input: Microsoft Surface Keyboard Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.3/0003:045E:09B5.0015/input/input61
[ 105.591459] input: Microsoft Surface Keyboard Touchpad as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.3/0003:045E:09B5.0015/input/input62
[ 105.591884] hid-multitouch 0003:045E:09B5.0015: input,hiddev98,hidraw4: USB HID v1.11 Mouse [Microsoft Surface Keyboard] on usb-0000:00:14.0-7/input3Okay, wait, so above/before it did remove the devices by flipping and now it doesn't any more? Or was the log above with disconnecting too?
PhilDevProg
commented
1 year ago The log I sent in my last comment is about disconnecting. The log I sent you 2 weeks ago was about flipping.
qzed
commented
1 year ago Yes, but you said
Flipping the keyboard also doesn't do anything to dmesg -w or journalctl -kf.
So I understand that as "flipping doesn't cause devices to be disconnected/reconnected any more" (at least in this case), correct? Whereas in the log you send 2 weeks ago, it did?
It is entirely possible that this behavior changes in some circumstances, which would explain why you had to fully disconnect it this time around. I just still can't make all that much sense of what specifically could trigger the failure.
PhilDevProg
commented
1 year ago So I understand that as "flipping doesn't cause devices to be disconnected/reconnected any more" (at least in this case), correct?
Correct.
Whereas in the log you send 2 weeks ago, it did?
You said that it did remove/reconnect the device so I suppose it did.
qzed
commented
1 year ago You said that it did remove/reconnect the device so I suppose it did.
The new full-speed USB device messages are in the log, so unless you fully disconnected the cover, that means that the devices get removed and re-added. So I'm wondering what's differently this time. Could be that the USB device went into some bad state.
I guess further debugging this would require digging into the USB or USB-HID setup code for new devices. I still think that maybe we need to give the USB device more time before trying to initialize it, so maybe that's something to try to figure out how to do.
PhilDevProg
commented
1 year ago so unless you fully disconnected the cover
I did fully disconnected the cover. Sorry, I wasn't clear enough.
qzed
commented
1 year ago Okay, so to clear up any misunderstandings: In the log from 2 weeks ago, you fully disconnected the typecover? And you did the same in the log from today.
That would mean: Flipping doesn't disconnect the USB devices, only fully disconnecting the typecover does.
I guess you can try flipping the cover a couple of times (ideally when it is in a state where it initially works) and check if dmesg -w shows any messages with new full-speed USB device. This is what I thought you did in the log from 2 weeks ago, hence me thinking that (at least in some cases) flipping the cover disconnects the USB devices.
PhilDevProg
commented
1 year ago Okay, so to clear up any misunderstandings: In the log from 2 weeks ago, you fully disconnected the typecover? And you did the same in the log from today.
No, in the log from today, I completely disconnected it. In the log from two weeks ago, I just flipped it.
I guess you can try flipping the cover a couple of times (ideally when it is in a state where it initially works) and check if dmesg -w shows any messages with new full-speed USB device. This is what I thought you did in the log from 2 weeks ago, hence me thinking that (at least in some cases) flipping the cover disconnects the USB devices.
No, there's nothing showing up when I flip the cover.
qzed
commented
1 year ago Okay, great. So that looks like the behavior two weeks ago (messages about devices being added/removed) is different than the behavior today (no messages). Note: I was talking about the log from two weeks ago in https://github.com/linux-surface/linux-surface/issues/305#issuecomment-1475319112, which I guess might have been a bit confusing, sorry.
I assume that means that you also can't spot any relation between messages appearing in the log and the typecover working vs. it not working? So it sometimes just works (without showing any messages) and sometimes just doesn't work (also without showing any messages)?
Maybe we need to try and reinitialize the HID or USB devices after tablet-mode changes?
I guess you could maybe try to reset the typecover USB device using an external keyboard if it's malfunctioning to see if that brings it back (see https://www.linux.org/threads/resetting-the-usb-subsystem.10404/ or https://askubuntu.com/questions/645/how-do-you-reset-a-usb-device-from-the-command-line for some ideas on how to do that) .
PhilDevProg
commented
1 year ago I assume that means that you also can't spot any relation between messages appearing in the log and the typecover working vs. it not working? So it sometimes just works (without showing any messages) and sometimes just doesn't work (also without showing any messages)?
I'll check that the next time it happens.
I guess you could maybe try to reset the typecover USB device using an external keyboard if it's malfunctioning to see if that brings it back (see https://www.linux.org/threads/resetting-the-usb-subsystem.10404/ or https://askubuntu.com/questions/645/how-do-you-reset-a-usb-device-from-the-command-line for some ideas on how to do that) .
I'll try that.
PhilDevProg
commented
1 year ago It happened again. This is the full dmesg (I completely disconnected and then reconnected it at the end): dmesg.txt But I don't see anything that might help...
qzed
commented
1 year ago Hmm, you're right, there isn't really anything that can help us unfortunately.
At the moment, I'm thinking that we might have to disconnect the devices when the typecover is being flipped back via the tablet mode switch, but that somewhat feels like a workaround. I have honestly no idea how to further debug/figure out the underling issue.
PhilDevProg
commented
1 year ago Was there something changed in the kernel or other surface related tools lately that has something to do with the touchpad/cover? Because for a long time, this didn't happen at all and now it suddenly happens again (maybe since updating to the newest kernel but I'm not sure).
qzed
commented
1 year ago The latest change from our side was adding the quirk from https://github.com/linux-surface/linux-surface/issues/1059.
Hi, I have Surface Go 2 with keyboard cover. I have issues with touchpad settings after power-on, after reattach. Sometimes the touchpad behave differently then it is set up in Settings.
When I power on the tablet with attached keyboard, then touchpad speed is very fast, tap-to-click do not work, and two-finger scroll do not work. When I detach and reattach keyboard, then touchpad speed is OK (as set in settings; middle setting; maybe default value), two-finger scrolling is working but sometimes in wrong direction (in settings is checked "natural scralling" but sometimes it do not work), and sometimes tap-to-click do not work too (in settings it is turned on). I think this might be because system sometimes load default settings (not the settings set in Settings app) on attach of keyboard cover.
To set my own touchpad settings again, I need to open Settings and literally switch (turn off and turn on for turned on options; in reverted order for turned off options) each non-working setting.
Environment
I have Ubuntu standard desktop environment. I use Settings to setup the touchpad settings. No special tools are installed or used to change behavior of input devices.
`dmesg` output
I cleared dmesg with `dmesg -c` before shutdown and power on of device with keyboard cover attached. On log on I reattach the keyboard cover to get pointer speed back. Then I attached dmesg log here. ``` [ 0.000000] microcode: microcode updated early to revision 0xd6, date = 2020-04-27 [ 0.000000] Linux version 5.8.12-surface (root@b20879272d4b) (gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #2 SMP Thu Oct 1 19:58:47 UTC 2020 [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.8.12-surface root=UUID=fd311530-b901-4bf9-8d73-ea70e72479f9 ro quiet splash vt.handoff=7 [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Hygon HygonGenuine [ 0.000000] Centaur CentaurHauls [ 0.000000] zhaoxin Shanghai [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 [ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 [ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable [ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable [ 0.000000] BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000040400000-0x0000000070cd3fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000070cd4000-0x0000000070cd4fff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x0000000070cd5000-0x0000000070cd5fff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000070cd6000-0x0000000073047fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000073048000-0x0000000075047fff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000075048000-0x000000008b25dfff] usable [ 0.000000] BIOS-e820: [mem 0x000000008b25e000-0x000000008c88dfff] reserved [ 0.000000] BIOS-e820: [mem 0x000000008c88e000-0x000000008cf7dfff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x000000008cf7e000-0x000000008cffdfff] ACPI data [ 0.000000] BIOS-e820: [mem 0x000000008cffe000-0x000000008cffefff] usable [ 0.000000] BIOS-e820: [mem 0x000000008cfff000-0x000000008fffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ff900000-0x00000000ffffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000026effffff] usable [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] e820: update [mem 0x70733018-0x70743057] usable ==> usable [ 0.000000] e820: update [mem 0x70733018-0x70743057] usable ==> usable [ 0.000000] extended physical RAM map: [ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x0000000000057fff] usable [ 0.000000] reserve setup_data: [mem 0x0000000000058000-0x0000000000058fff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000000059000-0x000000000009dfff] usable [ 0.000000] reserve setup_data: [mem 0x000000000009e000-0x00000000000fffff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x000000003fffffff] usable [ 0.000000] reserve setup_data: [mem 0x0000000040000000-0x00000000403fffff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000040400000-0x0000000070733017] usable [ 0.000000] reserve setup_data: [mem 0x0000000070733018-0x0000000070743057] usable [ 0.000000] reserve setup_data: [mem 0x0000000070743058-0x0000000070cd3fff] usable [ 0.000000] reserve setup_data: [mem 0x0000000070cd4000-0x0000000070cd4fff] ACPI NVS [ 0.000000] reserve setup_data: [mem 0x0000000070cd5000-0x0000000070cd5fff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000070cd6000-0x0000000073047fff] usable [ 0.000000] reserve setup_data: [mem 0x0000000073048000-0x0000000075047fff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000075048000-0x000000008b25dfff] usable [ 0.000000] reserve setup_data: [mem 0x000000008b25e000-0x000000008c88dfff] reserved [ 0.000000] reserve setup_data: [mem 0x000000008c88e000-0x000000008cf7dfff] ACPI NVS [ 0.000000] reserve setup_data: [mem 0x000000008cf7e000-0x000000008cffdfff] ACPI data [ 0.000000] reserve setup_data: [mem 0x000000008cffe000-0x000000008cffefff] usable [ 0.000000] reserve setup_data: [mem 0x000000008cfff000-0x000000008fffffff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000e0000000-0x00000000efffffff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fed00000-0x00000000fed00fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fed10000-0x00000000fed19fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fed84000-0x00000000fed84fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000ff900000-0x00000000ffffffff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000100000000-0x000000026effffff] usable [ 0.000000] efi: EFI v2.50 by INSYDE Corp. [ 0.000000] efi: ACPI 2.0=0x8cffd014 SMBIOS=0x8c02d000 SMBIOS 3.0=0x8c02b000 ESRT=0x7bf65018 RNG=0x8c029298 TPMEventLog=0x70744018 [ 0.000000] efi: seeding entropy pool [ 0.000000] random: fast init done [ 0.000000] [Firmware Bug]: TPM Final Events table missing or invalid [ 0.000000] SMBIOS 3.0.0 present. [ 0.000000] DMI: Microsoft Corporation Surface Go 2/Surface Go 2, BIOS 1.0.10 04/22/2020 [ 0.000000] tsc: Detected 1600.000 MHz processor [ 0.001007] tsc: Detected 1599.960 MHz TSC [ 0.001007] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.001008] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.001014] last_pfn = 0x26f000 max_arch_pfn = 0x400000000 [ 0.001018] MTRR default type: write-back [ 0.001019] MTRR fixed ranges enabled: [ 0.001020] 00000-9FFFF write-back [ 0.001020] A0000-BFFFF uncachable [ 0.001021] C0000-FFFFF write-protect [ 0.001021] MTRR variable ranges enabled: [ 0.001022] 0 base 00C0000000 mask 7FC0000000 uncachable [ 0.001023] 1 base 00A0000000 mask 7FE0000000 uncachable [ 0.001024] 2 base 0090000000 mask 7FF0000000 uncachable [ 0.001024] 3 base 008E000000 mask 7FFE000000 uncachable [ 0.001025] 4 base 008D800000 mask 7FFF800000 uncachable [ 0.001025] 5 disabled [ 0.001026] 6 disabled [ 0.001026] 7 disabled [ 0.001026] 8 disabled [ 0.001026] 9 disabled [ 0.001575] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [ 0.001792] last_pfn = 0x8cfff max_arch_pfn = 0x400000000 [ 0.012741] esrt: Reserving ESRT space from 0x000000007bf65018 to 0x000000007bf650f0. [ 0.012745] e820: update [mem 0x7bf65000-0x7bf65fff] usable ==> reserved [ 0.012756] check: Scanning 1 areas for low memory corruption [ 0.012760] Using GB pages for direct mapping [ 0.013521] Secure boot enabled [ 0.013521] RAMDISK: [mem 0x1c23a000-0x1f28dfff] [ 0.013530] ACPI: Early table checksum verification disabled [ 0.013533] ACPI: RSDP 0x000000008CFFD014 000024 (v02 MSFT ) [ 0.013535] ACPI: XSDT 0x000000008CFB6188 000104 (v01 MSFT MSFT 00000000 01000013) [ 0.013539] ACPI: FACP 0x000000008CFF3000 00010C (v05 MSFT MSFT 00000000 0000 00000000) [ 0.013543] ACPI: DSDT 0x000000008CFC1000 02DF80 (v02 MSFT MSFT 00000000 0000 00000000) [ 0.013544] ACPI: FACS 0x000000008CF55000 000040 [ 0.013546] ACPI: UEFI 0x000000008CFFC000 000042 (v01 MSFT MSFT 00000002 0000 00000000) [ 0.013548] ACPI: MSDM 0x000000008CFFB000 000055 (v03 MSFT MSFT 00000001 0000 00000000) [ 0.013550] ACPI: SSDT 0x000000008CFFA000 0004C3 (v02 MSFT MSFT 00001000 0000 00000000) [ 0.013552] ACPI: SSDT 0x000000008CFF9000 000046 (v02 MSFT MSFT 00003000 0000 00000000) [ 0.013554] ACPI: TPM2 0x000000008CFF8000 000034 (v03 MSFT MSFT 00000000 0000 00000000) [ 0.013556] ACPI: SSDT 0x000000008CFF4000 003138 (v02 MSFT MSFT 00003000 0000 00000000) [ 0.013557] ACPI: HPET 0x000000008CFF2000 000038 (v01 MSFT MSFT 00000001 0000 00000000) [ 0.013559] ACPI: APIC 0x000000008CFF1000 00012C (v03 MSFT MSFT 00000001 0000 00000000) [ 0.013561] ACPI: MCFG 0x000000008CFF0000 00003C (v01 MSFT MSFT 00000001 0000 00000000) [ 0.013563] ACPI: SSDT 0x000000008CFBF000 001A88 (v02 MSFT MSFT 00001000 0000 00000000) [ 0.013565] ACPI: SSDT 0x000000008CFBE000 00027F (v02 MSFT MSFT 00001000 0000 00000000) [ 0.013567] ACPI: LPIT 0x000000008CFBD000 000094 (v01 MSFT MSFT 00000000 0000 00000000) [ 0.013569] ACPI: WSMT 0x000000008CFBC000 000028 (v01 MSFT MSFT 00000000 0000 00000000) [ 0.013570] ACPI: SSDT 0x000000008CFBB000 00029F (v02 MSFT MSFT 00000000 0000 00000000) [ 0.013572] ACPI: SSDT 0x000000008CFBA000 000346 (v01 MSFT MSFT 00000000 0000 00000000) [ 0.013574] ACPI: SSDT 0x000000008CFB9000 000E6D (v02 MSFT MSFT 00001000 0000 00000000) [ 0.013576] ACPI: SSDT 0x000000008CFB8000 000306 (v02 MSFT MSFT 00000001 0000 00000000) [ 0.013578] ACPI: DBGP 0x000000008CFB7000 000034 (v01 MSFT MSFT 00000002 0000 00000000) [ 0.013580] ACPI: DBG2 0x000000008CFB5000 000054 (v00 MSFT MSFT 00000002 0000 00000000) [ 0.013581] ACPI: SSDT 0x000000008CFB4000 000EE0 (v02 MSFT MSFT 00001000 0000 00000000) [ 0.013583] ACPI: SSDT 0x000000008CFB2000 0017AE (v02 MSFT MSFT 00003000 0000 00000000) [ 0.013585] ACPI: SSDT 0x000000008CFAD000 00431D (v02 MSFT MSFT 00001000 0000 00000000) [ 0.013587] ACPI: SSDT 0x000000008CFAC000 000564 (v02 MSFT MSFT 00001000 0000 00000000) [ 0.013589] ACPI: DMAR 0x000000008CFEF000 0000A8 (v01 MSFT MSFT 00000001 0000 00000000) [ 0.013591] ACPI: NHLT 0x000000008CFAB000 00002D (v00 MSFT MSFT 00000002 0000 00000000) [ 0.013593] ACPI: FPDT 0x000000008CFAA000 000044 (v01 MSFT MSFT 00000002 0000 00000000) [ 0.013595] ACPI: BGRT 0x000000008CFA9000 000038 (v01 MSFT MSFT 00000001 0000 00000000) [ 0.013601] ACPI: Local APIC address 0xfee00000 [ 0.013786] No NUMA configuration found [ 0.013786] Faking a node at [mem 0x0000000000000000-0x000000026effffff] [ 0.013793] NODE_DATA(0) allocated [mem 0x26efd4000-0x26effdfff] [ 0.014031] Zone ranges: [ 0.014031] DMA [mem 0x0000000000001000-0x0000000000ffffff] [ 0.014032] DMA32 [mem 0x0000000001000000-0x00000000ffffffff] [ 0.014033] Normal [mem 0x0000000100000000-0x000000026effffff] [ 0.014034] Device empty [ 0.014034] Movable zone start for each node [ 0.014036] Early memory node ranges [ 0.014037] node 0: [mem 0x0000000000001000-0x0000000000057fff] [ 0.014038] node 0: [mem 0x0000000000059000-0x000000000009dfff] [ 0.014038] node 0: [mem 0x0000000000100000-0x000000003fffffff] [ 0.014039] node 0: [mem 0x0000000040400000-0x0000000070cd3fff] [ 0.014039] node 0: [mem 0x0000000070cd6000-0x0000000073047fff] [ 0.014039] node 0: [mem 0x0000000075048000-0x000000008b25dfff] [ 0.014040] node 0: [mem 0x000000008cffe000-0x000000008cffefff] [ 0.014040] node 0: [mem 0x0000000100000000-0x000000026effffff] [ 0.014331] Zeroed struct page in unavailable ranges: 33287 pages [ 0.014332] Initmem setup node 0 [mem 0x0000000000001000-0x000000026effffff] [ 0.014333] On node 0 totalpages: 2063865 [ 0.014334] DMA zone: 64 pages used for memmap [ 0.014334] DMA zone: 22 pages reserved [ 0.014335] DMA zone: 3996 pages, LIFO batch:0 [ 0.014359] DMA32 zone: 8698 pages used for memmap [ 0.014360] DMA32 zone: 556637 pages, LIFO batch:63 [ 0.019268] Normal zone: 23488 pages used for memmap [ 0.019269] Normal zone: 1503232 pages, LIFO batch:63 [ 0.032551] Reserving Intel graphics memory at [mem 0x8e000000-0x8fffffff] [ 0.033141] ACPI: PM-Timer IO Port: 0x1808 [ 0.033143] ACPI: Local APIC address 0xfee00000 [ 0.033148] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.033148] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [ 0.033149] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [ 0.033149] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [ 0.033150] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) [ 0.033150] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) [ 0.033150] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) [ 0.033151] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) [ 0.033151] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1]) [ 0.033152] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1]) [ 0.033152] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1]) [ 0.033152] ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1]) [ 0.033153] ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1]) [ 0.033153] ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1]) [ 0.033154] ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1]) [ 0.033154] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1]) [ 0.033181] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119 [ 0.033182] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.033183] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.033184] ACPI: IRQ0 used by override. [ 0.033185] ACPI: IRQ9 used by override. [ 0.033186] Using ACPI (MADT) for SMP configuration information [ 0.033187] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.033192] e820: update [mem 0x7b226000-0x7b23efff] usable ==> reserved [ 0.033199] TSC deadline timer available [ 0.033200] smpboot: Allowing 4 CPUs, 0 hotplug CPUs [ 0.033218] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff] [ 0.033219] PM: hibernation: Registered nosave memory: [mem 0x00058000-0x00058fff] [ 0.033220] PM: hibernation: Registered nosave memory: [mem 0x0009e000-0x000fffff] [ 0.033222] PM: hibernation: Registered nosave memory: [mem 0x40000000-0x403fffff] [ 0.033223] PM: hibernation: Registered nosave memory: [mem 0x70733000-0x70733fff] [ 0.033224] PM: hibernation: Registered nosave memory: [mem 0x70743000-0x70743fff] [ 0.033225] PM: hibernation: Registered nosave memory: [mem 0x70cd4000-0x70cd4fff] [ 0.033225] PM: hibernation: Registered nosave memory: [mem 0x70cd5000-0x70cd5fff] [ 0.033227] PM: hibernation: Registered nosave memory: [mem 0x73048000-0x75047fff] [ 0.033228] PM: hibernation: Registered nosave memory: [mem 0x7b226000-0x7b23efff] [ 0.033229] PM: hibernation: Registered nosave memory: [mem 0x7bf65000-0x7bf65fff] [ 0.033230] PM: hibernation: Registered nosave memory: [mem 0x8b25e000-0x8c88dfff] [ 0.033231] PM: hibernation: Registered nosave memory: [mem 0x8c88e000-0x8cf7dfff] [ 0.033231] PM: hibernation: Registered nosave memory: [mem 0x8cf7e000-0x8cffdfff] [ 0.033232] PM: hibernation: Registered nosave memory: [mem 0x8cfff000-0x8fffffff] [ 0.033233] PM: hibernation: Registered nosave memory: [mem 0x90000000-0xdfffffff] [ 0.033233] PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xefffffff] [ 0.033233] PM: hibernation: Registered nosave memory: [mem 0xf0000000-0xfcffffff] [ 0.033234] PM: hibernation: Registered nosave memory: [mem 0xfd000000-0xfe7fffff] [ 0.033234] PM: hibernation: Registered nosave memory: [mem 0xfe800000-0xfebfffff] [ 0.033234] PM: hibernation: Registered nosave memory: [mem 0xfec00000-0xfec00fff] [ 0.033235] PM: hibernation: Registered nosave memory: [mem 0xfec01000-0xfecfffff] [ 0.033235] PM: hibernation: Registered nosave memory: [mem 0xfed00000-0xfed00fff] [ 0.033236] PM: hibernation: Registered nosave memory: [mem 0xfed01000-0xfed0ffff] [ 0.033236] PM: hibernation: Registered nosave memory: [mem 0xfed10000-0xfed19fff] [ 0.033236] PM: hibernation: Registered nosave memory: [mem 0xfed1a000-0xfed83fff] [ 0.033237] PM: hibernation: Registered nosave memory: [mem 0xfed84000-0xfed84fff] [ 0.033237] PM: hibernation: Registered nosave memory: [mem 0xfed85000-0xfedfffff] [ 0.033237] PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff] [ 0.033238] PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xff8fffff] [ 0.033238] PM: hibernation: Registered nosave memory: [mem 0xff900000-0xffffffff] [ 0.033240] [mem 0x90000000-0xdfffffff] available for PCI devices [ 0.033241] Booting paravirtualized kernel on bare hardware [ 0.033243] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns [ 0.033248] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1 [ 0.033425] percpu: Embedded 56 pages/cpu s192512 r8192 d28672 u524288 [ 0.033432] pcpu-alloc: s192512 r8192 d28672 u524288 alloc=1*2097152 [ 0.033432] pcpu-alloc: [0] 0 1 2 3 [ 0.033454] Built 1 zonelists, mobility grouping on. Total pages: 2031593 [ 0.033455] Policy zone: Normal [ 0.033456] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.8.12-surface root=UUID=fd311530-b901-4bf9-8d73-ea70e72479f9 ro quiet splash vt.handoff=7 [ 0.034027] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [ 0.034311] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.034350] mem auto-init: stack:off, heap alloc:on, heap free:off [ 0.060452] Memory: 7877136K/8255460K available (14339K kernel code, 2535K rwdata, 5112K rodata, 2632K init, 4932K bss, 378324K reserved, 0K cma-reserved) [ 0.060459] random: get_random_u64 called from __kmem_cache_create+0x42/0x540 with crng_init=1 [ 0.060576] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.060589] Kernel/User page tables isolation: enabled [ 0.060601] ftrace: allocating 45661 entries in 179 pages [ 0.074363] ftrace: allocated 179 pages with 5 groups [ 0.074458] rcu: Hierarchical RCU implementation. [ 0.074459] rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=4. [ 0.074460] Trampoline variant of Tasks RCU enabled. [ 0.074460] Rude variant of Tasks RCU enabled. [ 0.074460] Tracing variant of Tasks RCU enabled. [ 0.074461] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.074461] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.076934] NR_IRQS: 524544, nr_irqs: 1024, preallocated irqs: 16 [ 0.077378] random: crng done (trusting CPU's manufacturer) [ 0.077418] Console: colour dummy device 80x25 [ 0.077423] printk: console [tty0] enabled [ 0.077441] ACPI: Core revision 20200528 [ 0.077730] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635855245 ns [ 0.077821] APIC: Switch to symmetric I/O mode setup [ 0.077823] DMAR: Host address width 39 [ 0.077825] DMAR: DRHD base: 0x000000fed90000 flags: 0x0 [ 0.077830] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e [ 0.077831] DMAR: DRHD base: 0x000000fed91000 flags: 0x1 [ 0.077835] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da [ 0.077836] DMAR: RMRR base: 0x0000008c73d000 end: 0x0000008c75cfff [ 0.077837] DMAR: RMRR base: 0x0000008d800000 end: 0x0000008fffffff [ 0.077839] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1 [ 0.077840] DMAR-IR: HPET id 0 under DRHD base 0xfed91000 [ 0.077840] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping. [ 0.079530] DMAR-IR: Enabled IRQ remapping in x2apic mode [ 0.079531] x2apic enabled [ 0.079544] Switched APIC routing to cluster x2apic. [ 0.083567] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 0.101890] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x170fff30cc4, max_idle_ns: 440795237869 ns [ 0.101894] Calibrating delay loop (skipped), value calculated using timer frequency.. 3199.92 BogoMIPS (lpj=6399840) [ 0.101896] pid_max: default: 32768 minimum: 301 [ 0.105270] LSM: Security Framework initializing [ 0.105294] Yama: becoming mindful. [ 0.105316] AppArmor: AppArmor initialized [ 0.105353] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.105364] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.105612] mce: CPU0: Thermal monitoring enabled (TM1) [ 0.105626] process: using mwait in idle threads [ 0.105628] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 [ 0.105629] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 [ 0.105632] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization [ 0.105633] Spectre V2 : Mitigation: Full generic retpoline [ 0.105633] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch [ 0.105634] Spectre V2 : Enabling Restricted Speculation for firmware calls [ 0.105635] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier [ 0.105635] Spectre V2 : User space: Mitigation: STIBP via seccomp and prctl [ 0.105636] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp [ 0.105641] SRBDS: Mitigation: Microcode [ 0.105641] MDS: Mitigation: Clear CPU buffers [ 0.105889] Freeing SMP alternatives memory: 40K [ 0.108992] smpboot: CPU0: Intel(R) Core(TM) m3-8100Y CPU @ 1.10GHz (family: 0x6, model: 0x8e, stepping: 0x9) [ 0.109120] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver. [ 0.109125] ... version: 4 [ 0.109126] ... bit width: 48 [ 0.109126] ... generic registers: 4 [ 0.109127] ... value mask: 0000ffffffffffff [ 0.109127] ... max period: 00007fffffffffff [ 0.109127] ... fixed-purpose events: 3 [ 0.109128] ... event mask: 000000070000000f [ 0.109157] rcu: Hierarchical SRCU implementation. [ 0.109869] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. [ 0.109892] smp: Bringing up secondary CPUs ... [ 0.109892] x86: Booting SMP configuration: [ 0.109892] .... node #0, CPUs: #1 #2 [ 0.110456] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. [ 0.110456] #3 [ 0.110492] smp: Brought up 1 node, 4 CPUs [ 0.110492] smpboot: Max logical packages: 1 [ 0.110492] smpboot: Total of 4 processors activated (12799.68 BogoMIPS) [ 0.111950] devtmpfs: initialized [ 0.111950] x86/mm: Memory block size: 128MB [ 0.113929] PM: Registering ACPI NVS region [mem 0x70cd4000-0x70cd4fff] (4096 bytes) [ 0.113930] PM: Registering ACPI NVS region [mem 0x8c88e000-0x8cf7dfff] (7274496 bytes) [ 0.114082] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.114082] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.114082] pinctrl core: initialized pinctrl subsystem [ 0.114082] PM: RTC time: 18:14:50, date: 2020-10-13 [ 0.114082] thermal_sys: Registered thermal governor 'fair_share' [ 0.114082] thermal_sys: Registered thermal governor 'bang_bang' [ 0.114082] thermal_sys: Registered thermal governor 'step_wise' [ 0.114082] thermal_sys: Registered thermal governor 'user_space' [ 0.114082] thermal_sys: Registered thermal governor 'power_allocator' [ 0.114082] NET: Registered protocol family 16 [ 0.114161] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations [ 0.114224] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [ 0.114297] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [ 0.114307] audit: initializing netlink subsys (disabled) [ 0.114322] audit: type=2000 audit(1602612890.036:1): state=initialized audit_enabled=0 res=1 [ 0.114322] EISA bus registered [ 0.114322] cpuidle: using governor ladder [ 0.114322] cpuidle: using governor menu [ 0.114322] ACPI: bus type PCI registered [ 0.114322] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.114322] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) [ 0.114322] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820 [ 0.114322] PCI: Using configuration type 1 for base access [ 0.114322] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 0.115210] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 0.115210] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 0.117980] ACPI: Added _OSI(Module Device) [ 0.117981] ACPI: Added _OSI(Processor Device) [ 0.117982] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.117982] ACPI: Added _OSI(Processor Aggregator Device) [ 0.117983] ACPI: Added _OSI(Linux-Dell-Video) [ 0.117984] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [ 0.117985] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) [ 0.166350] ACPI: 14 ACPI AML tables successfully acquired and loaded [ 0.169446] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [ 0.174108] ACPI: Dynamic OEM Table Load: [ 0.174122] ACPI: SSDT 0xFFFF919E256F0000 000507 (v02 PmRef Cpu0Ist 00003000 INTL 20160527) [ 0.175778] ACPI: \_PR_.PR00: _OSC native thermal LVT Acked [ 0.177340] ACPI: Dynamic OEM Table Load: [ 0.177347] ACPI: SSDT 0xFFFF919E24CA7000 0003FF (v02 PmRef Cpu0Cst 00003001 INTL 20160527) [ 0.178961] ACPI: Dynamic OEM Table Load: [ 0.178966] ACPI: SSDT 0xFFFF919E2532CA80 0000BA (v02 PmRef Cpu0Hwp 00003000 INTL 20160527) [ 0.180489] ACPI: Dynamic OEM Table Load: [ 0.180495] ACPI: SSDT 0xFFFF919E256F3800 000628 (v02 PmRef HwpLvt 00003000 INTL 20160527) [ 0.182461] ACPI: Dynamic OEM Table Load: [ 0.182469] ACPI: SSDT 0xFFFF919E2576D000 000D14 (v02 PmRef ApIst 00003000 INTL 20160527) [ 0.184894] ACPI: Dynamic OEM Table Load: [ 0.184900] ACPI: SSDT 0xFFFF919E24CA4800 000317 (v02 PmRef ApHwp 00003000 INTL 20160527) [ 0.186565] ACPI: Dynamic OEM Table Load: [ 0.186570] ACPI: SSDT 0xFFFF919E24CA7800 00030A (v02 PmRef ApCst 00003000 INTL 20160527) [ 0.190083] ACPI: EC: EC started [ 0.190084] ACPI: EC: interrupt blocked [ 0.190346] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62 [ 0.190347] ACPI: \_SB_.PCI0.LPCB.EC0_: Boot DSDT EC used to handle transactions [ 0.190348] ACPI: Interpreter enabled [ 0.190398] ACPI: (supports S0 S3 S4 S5) [ 0.190400] ACPI: Using IOAPIC for interrupt routing [ 0.190443] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.191572] ACPI: Enabled 7 GPEs in block 00 to 7F [ 0.200889] ACPI: Power Resource [WRST] (on) [ 0.213932] ACPI: Power Resource [PXTC] (on) [ 0.214409] ACPI: Power Resource [PXTC] (on) [ 0.540884] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) [ 0.540890] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] [ 0.543936] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR] [ 0.546375] PCI host bridge to bus 0000:00 [ 0.546380] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] [ 0.546381] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 0.546382] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] [ 0.546383] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff window] [ 0.546384] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff window] [ 0.546384] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff window] [ 0.546385] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff window] [ 0.546386] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window] [ 0.546387] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window] [ 0.546388] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window] [ 0.546389] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window] [ 0.546389] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window] [ 0.546390] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window] [ 0.546391] pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff window] [ 0.546392] pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff window] [ 0.546393] pci_bus 0000:00: root bus resource [mem 0x000f0000-0x000fffff window] [ 0.546394] pci_bus 0000:00: root bus resource [mem 0x90000000-0xdfffffff window] [ 0.546395] pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfe7fffff window] [ 0.546396] pci_bus 0000:00: root bus resource [bus 00-fe] [ 0.546406] pci 0000:00:00.0: [8086:590c] type 00 class 0x060000 [ 0.547619] pci 0000:00:02.0: [8086:591c] type 00 class 0x030000 [ 0.547631] pci 0000:00:02.0: reg 0x10: [mem 0xb0000000-0xb0ffffff 64bit] [ 0.547637] pci 0000:00:02.0: reg 0x18: [mem 0xa0000000-0xafffffff 64bit pref] [ 0.547641] pci 0000:00:02.0: reg 0x20: [io 0x3000-0x303f] [ 0.547658] pci 0000:00:02.0: BAR 2: assigned to efifb [ 0.548607] pci 0000:00:04.0: [8086:1903] type 00 class 0x118000 [ 0.548621] pci 0000:00:04.0: reg 0x10: [mem 0xb1730000-0xb1737fff 64bit] [ 0.549617] pci 0000:00:05.0: [8086:1919] type 00 class 0x048000 [ 0.549629] pci 0000:00:05.0: reg 0x10: [mem 0xb1000000-0xb13fffff 64bit] [ 0.550617] pci 0000:00:13.0: [8086:9d35] type 00 class 0x000000 [ 0.550644] pci 0000:00:13.0: reg 0x10: [mem 0xb1740000-0xb1740fff 64bit] [ 0.551700] pci 0000:00:14.0: [8086:9d2f] type 00 class 0x0c0330 [ 0.551724] pci 0000:00:14.0: reg 0x10: [mem 0xb1720000-0xb172ffff 64bit] [ 0.551798] pci 0000:00:14.0: PME# supported from D3hot D3cold [ 0.552822] pci 0000:00:14.2: [8086:9d31] type 00 class 0x118000 [ 0.552844] pci 0000:00:14.2: reg 0x10: [mem 0xb1741000-0xb1741fff 64bit] [ 0.553848] pci 0000:00:14.3: [8086:9d32] type 00 class 0x048000 [ 0.553970] pci 0000:00:14.3: reg 0x10: [mem 0xb1700000-0xb170ffff 64bit] [ 0.555406] pci 0000:00:15.0: [8086:9d60] type 00 class 0x118000 [ 0.555671] pci 0000:00:15.0: reg 0x10: [mem 0xb1742000-0xb1742fff 64bit] [ 0.557539] pci 0000:00:15.1: [8086:9d61] type 00 class 0x118000 [ 0.557804] pci 0000:00:15.1: reg 0x10: [mem 0xb1743000-0xb1743fff 64bit] [ 0.559665] pci 0000:00:15.2: [8086:9d62] type 00 class 0x118000 [ 0.559929] pci 0000:00:15.2: reg 0x10: [mem 0xb1744000-0xb1744fff 64bit] [ 0.561797] pci 0000:00:15.3: [8086:9d63] type 00 class 0x118000 [ 0.562059] pci 0000:00:15.3: reg 0x10: [mem 0xb1745000-0xb1745fff 64bit] [ 0.563869] pci 0000:00:16.0: [8086:9d3a] type 00 class 0x078000 [ 0.563896] pci 0000:00:16.0: reg 0x10: [mem 0xb1746000-0xb1746fff 64bit] [ 0.563974] pci 0000:00:16.0: PME# supported from D3hot [ 0.565077] pci 0000:00:19.0: [8086:9d66] type 00 class 0x118000 [ 0.565341] pci 0000:00:19.0: reg 0x10: [mem 0xb1747000-0xb1747fff 64bit] [ 0.567214] pci 0000:00:19.2: [8086:9d64] type 00 class 0x118000 [ 0.567479] pci 0000:00:19.2: reg 0x10: [mem 0xb1748000-0xb1748fff 64bit] [ 0.569283] pci 0000:00:1c.0: [8086:9d12] type 01 class 0x060400 [ 0.569372] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 0.570398] pci 0000:00:1c.3: [8086:9d13] type 01 class 0x060400 [ 0.570483] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold [ 0.571504] pci 0000:00:1c.6: [8086:9d16] type 01 class 0x060400 [ 0.571599] pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold [ 0.572709] pci 0000:00:1e.0: [8086:9d27] type 00 class 0x118000 [ 0.572974] pci 0000:00:1e.0: reg 0x10: [mem 0xb1749000-0xb1749fff 64bit] [ 0.574793] pci 0000:00:1f.0: [8086:9d4b] type 00 class 0x060100 [ 0.575857] pci 0000:00:1f.2: [8086:9d21] type 00 class 0x058000 [ 0.575874] pci 0000:00:1f.2: reg 0x10: [mem 0xb173c000-0xb173ffff] [ 0.576875] pci 0000:00:1f.3: [8086:9d71] type 00 class 0x040380 [ 0.576905] pci 0000:00:1f.3: reg 0x10: [mem 0xb1738000-0xb173bfff 64bit] [ 0.576939] pci 0000:00:1f.3: reg 0x20: [mem 0xb1710000-0xb171ffff 64bit] [ 0.576992] pci 0000:00:1f.3: PME# supported from D3hot D3cold [ 0.578267] pci 0000:01:00.0: [8086:2723] type 00 class 0x028000 [ 0.578353] pci 0000:01:00.0: reg 0x10: [mem 0xb1600000-0xb1603fff 64bit] [ 0.578650] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold [ 0.579258] pci 0000:00:1c.0: PCI bridge to [bus 01] [ 0.579263] pci 0000:00:1c.0: bridge window [mem 0xb1600000-0xb16fffff] [ 0.579322] pci 0000:02:00.0: [10ec:522a] type 00 class 0xff0000 [ 0.579353] pci 0000:02:00.0: reg 0x10: [mem 0xb1500000-0xb1500fff] [ 0.579498] pci 0000:02:00.0: supports D1 D2 [ 0.579499] pci 0000:02:00.0: PME# supported from D1 D2 D3hot D3cold [ 0.579652] pci 0000:00:1c.3: PCI bridge to [bus 02] [ 0.579656] pci 0000:00:1c.3: bridge window [mem 0xb1500000-0xb15fffff] [ 0.579734] pci 0000:03:00.0: [1c5c:1327] type 00 class 0x010802 [ 0.579769] pci 0000:03:00.0: reg 0x10: [mem 0xb1400000-0xb1403fff 64bit] [ 0.579897] pci 0000:03:00.0: supports D1 [ 0.579898] pci 0000:03:00.0: PME# supported from D0 D1 D3hot [ 0.579967] pci 0000:03:00.0: 15.752 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x2 link at 0000:00:1c.6 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link) [ 0.580049] pci 0000:00:1c.6: PCI bridge to [bus 03] [ 0.580053] pci 0000:00:1c.6: bridge window [mem 0xb1400000-0xb14fffff] [ 0.584414] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.584478] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15) [ 0.584540] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.584601] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.584662] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.584723] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.584784] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.584844] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.595432] ACPI: EC: interrupt unblocked [ 0.595433] ACPI: EC: event unblocked [ 0.595445] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62 [ 0.595446] ACPI: EC: GPE=0x50 [ 0.595447] ACPI: \_SB_.PCI0.LPCB.EC0_: Boot DSDT EC initialization complete [ 0.595448] ACPI: \_SB_.PCI0.LPCB.EC0_: EC: Used to handle transactions and events [ 0.595529] iommu: Default domain type: Translated [ 0.595529] pci 0000:00:02.0: vgaarb: setting as boot VGA device [ 0.595529] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [ 0.595529] pci 0000:00:02.0: vgaarb: bridge control possible [ 0.595529] vgaarb: loaded [ 0.595529] SCSI subsystem initialized [ 0.595529] libata version 3.00 loaded. [ 0.595529] ACPI: bus type USB registered [ 0.595529] usbcore: registered new interface driver usbfs [ 0.595529] usbcore: registered new interface driver hub [ 0.595529] usbcore: registered new device driver usb [ 0.595529] pps_core: LinuxPPS API ver. 1 registered [ 0.595529] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti