[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10

[Mario Limonciello]

** Changed in: linux (Ubuntu Disco)
   Status: Incomplete => Triaged

** Changed in: linux (Ubuntu Eoan)
   Status: Incomplete => Triaged

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=110604
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1826691

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in Linux:
  Unknown
Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in fwupd source package in Disco:
  Triaged
Status in linux source package in Disco:
  Triaged
Status in fwupd source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Triaged

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
  Apr 23 19:29:14 texas kernel: [  133.673362]  ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei 
fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch 
processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt 
intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone 
dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel 
sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci 
nvme_core intel_lpss i2c_hid wmi hid video pinctrl_cannonlake pinctrl_intel
  Apr 23 19:29:14 texas kernel: [  133.673381]

[Kernel-packages] [Bug 1813537] Re: Wifi + bluetooth adapters are gone after sleep/wake

[Mario Limonciello]

Definitely support uefi capsule update.
2.10 is posted here: 
https://fwupd.org/lvfs/device/com.dell.uefi5ffdbc0d.firmware

Are you installed in uefi mode? If so, capsule update might be turned
off in bios setup.

If you are installed in legacy mode you'll have to manually download exe
and place in fat32 USB disk. Then go into F12 menu at POST and select
bios update.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813537

Title:
  Wifi + bluetooth adapters are gone after sleep/wake

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the only fix I found was to power down and power back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uri2238 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 28 11:15:43 2019
  HibernationDevice: RESUME=UUID=c88d6aec-cb91-4ff5-a406-52c6187e06a5
  InstallationDate: Installed on 2018-01-13 (380 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=dc909762-dd6b-4c9c-84da-f8e16a647a3f ro nouveau.modeset=0 quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813537/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1813537] Re: Wifi + bluetooth adapters are gone after sleep/wake

[Mario Limonciello]

You won't be able to update the BIOS from Ubuntu (this time or in the
future) in legacy mode.

Unfortunately it's not possible to convert a stock Ubuntu install to
UEFI mode. So you'll need to switch modes and reinstall.

So it probably comes down to a question of whether that's important to you in 
the future.
On Apr 14, 2019, 17:35 +0800, Uri , wrote:
> Apparently I'm on legacy boot ("Legacy boot on HDD"), but don't care
> about it as long as everything works.
>
> Should I change to UEFI?
>
> Otherwise - can you provide specific instructions, as this is all pretty
> new to me.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1813537
>
> Title:
> Wifi + bluetooth adapters are gone after sleep/wake
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813537/+subscriptions

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813537

Title:
  Wifi + bluetooth adapters are gone after sleep/wake

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the only fix I found was to power down and power back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uri2238 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 28 11:15:43 2019
  HibernationDevice: RESUME=UUID=c88d6aec-cb91-4ff5-a406-52c6187e06a5
  InstallationDate: Installed on 2018-01-13 (380 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=dc909762-dd6b-4c9c-84da-f8e16a647a3f ro nouveau.modeset=0 quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813537/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1840066] Re: DELL DA300 adaptor's Ethernet port not working after update

[Mario Limonciello]

It's not in support.dell.com either for Windows as I can tell.  Latest version 
is 40.
https://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverid=c25p2&oscode=wt64a&productcode=xps-13-9380-laptop

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1840066

Title:
  DELL DA300 adaptor's Ethernet port not working after update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  DELL DA300 adapter's Ethernet port stopped working after recent update. 
Whenever the cable is plugged in to the adapter, network manager would show the 
cable connecting icon and immediately drop the connection. I am able to get 
Ethernet connection through the DA300 with another Ethernet-USBc adapter by 
plugging the cable to the adaptor and use DA300's USBc port though.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-03-26 (142 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 131.215.195.254 dev enx00e04c680c21 proto dhcp metric 100 
   default via 10.6.41.254 dev wlp2s0 proto dhcp metric 600 
   10.6.40.0/23 dev wlp2s0 proto kernel scope link src 10.6.41.210 metric 600 
   131.215.195.0/24 dev enx00e04c680c21 proto kernel scope link src 
131.215.195.209 metric 100 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.14-0ubuntu2 [origin: unknown]
  PackageArchitecture: amd64
  Tags: third-party-packages bionic
  Uname: Linux 5.2.5-050205-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2019-08-13T09:56:21.009087
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   enx00e04c680c21  ethernet  connected
/org/freedesktop/NetworkManager/Devices/6  Wired connection 1  
483df49a-2e78-38c0-a084-58e621ab7527  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   wlp2s0   wifi  connected
/org/freedesktop/NetworkManager/Devices/3  eduroam 
f7c3132c-f44a-4f36-ba26-88e67487dddb  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   enxc8f7509d89c6  ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/5  --  --   
 -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.14  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840066/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1806323] Re: libfu_plugin_dell.so w/dell TB16 Dock blanks the display

[Mario Limonciello]

*** This bug is a duplicate of bug 1793965 ***
https://bugs.launchpad.net/bugs/1793965

** This bug has been marked a duplicate of bug 1793965
   Firmware update daemon resets displays connected to Dell TB16 dock soon 
after every first login

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806323

Title:
  libfu_plugin_dell.so w/dell TB16 Dock blanks the display

Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Absolutely reproducible in Ubuntu 18.04.1 Gnome 3 UI with a Dell XP15
  laptop and a Dell TB16 dock.

  A few seconds after logging into the Gnome 3 UI, something in the UI
  starts the fwupd.service. About 2 seconds later, the display goes
  blank and does not come back. There is no obvious recovery short of
  killing all the user's processes, and then logging back in.  A second
  login does not reproduce the problem, since the fwupd service is now
  running, and does not restart. However manually restarting the fwupd
  service causes the problem to recur.

  The problem does not occur if the "dell" module is blacklisted in
  /etc/fwupd/daemon.conf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: fwupd 1.0.6-2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 22:02:31 2018
  InstallationDate: Installed on 2018-11-19 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: fwupd
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.fwupd.daemon.conf: 2018-12-02T21:41:51.195270
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-20 (197 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-19 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.fwupd.daemon.conf: 2018-12-03T22:22:13.013702

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1806323/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1822633] Re: Pairing failure with BLE 4.0

[Mario Limonciello]

** Also affects: bluez (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1822633

Title:
  Pairing failure with BLE 4.0

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at
  https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the
  assumption that maybe this is an issue caused by LE communication
  rather than classic BR/EDR communication. Alas, my computer wasn't
  even able to start the pairing process after making the change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1822633/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1822633] Re: Pairing failure with BLE 4.0

[Mario Limonciello]

** Project changed: snappy-hwe-snaps => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1822633

Title:
  Pairing failure with BLE 4.0

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at
  https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the
  assumption that maybe this is an issue caused by LE communication
  rather than classic BR/EDR communication. Alas, my computer wasn't
  even able to start the pairing process after making the change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1822633/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3

[Mario Limonciello]

With most machines they have a security level set in BIOS.  The default
security level means you need to authorize the thunderbolt device using
bolt or thunderbolt-tools, did you do that?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thunderbolt-tools in Ubuntu.
Matching subscriptions: Kernel Packages
https://bugs.launchpad.net/bugs/1830930

Title:
  USB 3 devices are not detected on thunderbolt 3

Status in thunderbolt-tools package in Ubuntu:
  New

Bug description:
  I found a strange problem when trying to connect my Samsung T5 SSD.

  If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4,
  with Thunderbolt at boot then the SSD is detected without issues.

  If I unplug it and reconnect then it's not detected.

  If I force the thunderbolt controller on (boltctl power -t 1)  then I
  can see the new USB host created in lsusb but the attached device is
  not added.  No additional events are shown in dmesg.

  If I connect the device using another cable then it also doesn't work

  I have a USB-C cable only rated to USB 2.0 speed then the device is
  recognized without any issues.

  Ubuntu 19.04, 5.0.0-15-generic

  04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan 
Ridge 2C 2018] (rev 06)
  3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge 2C 2018] (rev 06)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  toby   1495 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-27 (31 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteDesk 800 G4 DM 65W
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  Tags:  disco
  Uname: Linux 5.0.0-15-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q21 Ver. 02.06.03
  dmi.board.name: 845A
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 07.D2.00
  dmi.chassis.asset.tag: 8CC84321CJ
  dmi.chassis.type: 6
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  dmi.product.name: HP EliteDesk 800 G4 DM 65W
  dmi.product.sku: 5BA07US#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1830930/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10

[Mario Limonciello]

This is a bug in the amdgpu kernel module.
When trying to access the DP aux channel it is causing system hangs.

At least in upstream fwupd there is a recently committed workaround:
https://github.com/hughsie/fwupd/commit/57816a7907e5f56c2136af31a4f1ae5186d87565

For now you can do the following:
1. Blacklist synapticsmst plugin in fwupd in /etc/fwupd/daemon.conf
Or
2. Try a newer kernel (like 5.x)
Or
3. Backport that patch from fwupd


** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1826691

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in fwupd package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
  Apr 23 19:29:14 texas kernel: [  133.673362]  ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei 
fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch 
processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt 
intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone 
dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel 
sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci 
nvme_core intel_lpss i2c_hid wmi hid video pinctrl_cannonlake pinctrl_intel
  Apr 23 19:29:14 texas kernel: [ 

[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10

[Mario Limonciello]

This is definitely a kernel bug, but it's exaggerated by userspace.
So whether it should be worked around in userspace or fixed in the kernel space 
is debatable.

For now, I believe you can employ that workaround to keep your system
stable, but I would ask the following.

1) Can you please follow the things that the bot said to add your logs to the 
bug.
2) Can you please try latest mainline (5.1rc7: 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc7/) and confirm it 
doesn't help?  I don't expect it to.
3) If the fwupd workaround does end up being backported to Disco, please test 
it for the purposes of the SRU, you would see notification in this bug.

** Changed in: fwupd (Ubuntu)
   Status: New => Triaged

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: fwupd (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Incomplete

** Also affects: fwupd (Ubuntu Eoan)
   Importance: Undecided
   Status: Triaged

** Changed in: fwupd (Ubuntu Disco)
   Status: New => Triaged

** Changed in: linux (Ubuntu Disco)
   Status: New => Incomplete

** Changed in: linux (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: fwupd (Ubuntu Eoan)
   Importance: Undecided => Low

** Changed in: fwupd (Ubuntu Disco)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1826691

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in fwupd source package in Disco:
  Triaged
Status in linux source package in Disco:
  Incomplete
Status in fwupd source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot

[Mario Limonciello]

FWIW a few other messages pop up to me in the above logs as suspicious
to the described symptoms, especially with keyboard working in
cryptsetup.

Mar 31 10:34:45 taplop org.gnome.Shell.desktop[5876]: libinput error: client 
bug: timer event25 debounce: offset negative (-111ms)
Mar 31 10:34:45 taplop org.gnome.Shell.desktop[5876]: libinput error: client 
bug: timer event25 debounce: offset negative (-44ms)
Mar 31 10:34:45 taplop org.gnome.Shell.desktop[5876]: libinput error: client 
bug: timer event25 debounce short: offset negative (-57ms)

When libinput initialized if it failed to configure those input devices,
that /might/ explain the behavior.  Flipping the hinge will cause them
to come on/off the bus and let libinput try again.

** Also affects: libinput (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822394

Title:
  [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working
  at gdm screen after boot

Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see 
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered 
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10

[Mario Limonciello]

So this issue needs to be reported upstream to AMD @FDO.  
https://bugs.freedesktop.org
Having the very simple replicator should be good to include it too.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1826691

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in fwupd source package in Disco:
  Triaged
Status in linux source package in Disco:
  Incomplete
Status in fwupd source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
  Apr 23 19:29:14 texas kernel: [  133.673362]  ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei 
fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch 
processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt 
intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone 
dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel 
sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci 
nvme_core intel_lpss i2c_hid wmi hid video pinctrl_cannonlake pinctrl_intel
  Apr 23 19:29:14 texas kernel: [  133.673381] CPU: 6 PID: 2467 Comm: fwupd 
Tainted: G   OE 5.0.0-13-generic #14-Ubuntu
  Apr 23 19:29:14 texas kernel: [  133.673382] Har

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot

[Mario Limonciello]

That's interesting to me. Yes the EC will emulate an PS2 mouse until the
OS brings up the I2C controller. I would think you can accomplish a
similar result by blacklisting psmouse potentially.

Is this discussion in IRC or a mailing list?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822394

Title:
  [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working
  at gdm screen after boot

Status in libinput package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see 
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered 
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1838590] Re: Update thermald to 1.9 release

[Mario Limonciello]

dptfxtract should be upgraded to 1.4.2 at the same time.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1838590

Title:
  Update thermald to 1.9 release

Status in dptfxtract package in Ubuntu:
  New
Status in thermald package in Ubuntu:
  New

Bug description:
  The thermald 1.9 release was just tagged, and has potential to help
  quite a bit with platform performance on some newer platforms when run
  with kernel 5.3. It would be nice to update eoan to this new release.

  > - The major change in this version is the active power limits adjustment.
  This will be useful to improve performance on some newer platform. But
  this will will lead to increase in CPU and other temperatures. Hence this
  is important to run dptfxtract version 1.4.1 tool to get performance
  sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1).
  If the default configuration picked up by thermald is not optimal, user
  can select other less aggressive configuration. Refer to the README here
  https://github.com/intel/dptfxtract/blob/master/README.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dptfxtract/+bug/1838590/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1838590] [NEW] Update thermald to 1.9 release

[Mario Limonciello]

Public bug reported:

The thermald 1.9 release was just tagged, and has potential to help
quite a bit with platform performance on some newer platforms when run
with kernel 5.3. It would be nice to update eoan to this new release.

> - The major change in this version is the active power limits adjustment.
This will be useful to improve performance on some newer platform. But
this will will lead to increase in CPU and other temperatures. Hence this
is important to run dptfxtract version 1.4.1 tool to get performance
sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1).
If the default configuration picked up by thermald is not optimal, user
can select other less aggressive configuration. Refer to the README here
https://github.com/intel/dptfxtract/blob/master/README.txt

** Affects: dptfxtract (Ubuntu)
 Importance: Wishlist
 Status: New

** Affects: thermald (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: thermald (Ubuntu)
   Importance: Undecided => Wishlist

** Description changed:

  The thermald 1.9 release was just tagged, and has potential to help
  quite a bit with platform performance on some newer platforms when run
- with kernel 5.3. It would be nice to update disco to this new release.
+ with kernel 5.3. It would be nice to update eoan to this new release.
  
  > - The major change in this version is the active power limits adjustment.
  This will be useful to improve performance on some newer platform. But
  this will will lead to increase in CPU and other temperatures. Hence this
  is important to run dptfxtract version 1.4.1 tool to get performance
  sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1).
  If the default configuration picked up by thermald is not optimal, user
  can select other less aggressive configuration. Refer to the README here
  https://github.com/intel/dptfxtract/blob/master/README.txt

** Also affects: dptfxtract (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: dptfxtract (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1838590

Title:
  Update thermald to 1.9 release

Status in dptfxtract package in Ubuntu:
  New
Status in thermald package in Ubuntu:
  New

Bug description:
  The thermald 1.9 release was just tagged, and has potential to help
  quite a bit with platform performance on some newer platforms when run
  with kernel 5.3. It would be nice to update eoan to this new release.

  > - The major change in this version is the active power limits adjustment.
  This will be useful to improve performance on some newer platform. But
  this will will lead to increase in CPU and other temperatures. Hence this
  is important to run dptfxtract version 1.4.1 tool to get performance
  sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1).
  If the default configuration picked up by thermald is not optimal, user
  can select other less aggressive configuration. Refer to the README here
  https://github.com/intel/dptfxtract/blob/master/README.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dptfxtract/+bug/1838590/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1838590] Re: Update thermald to 1.9 release

[Mario Limonciello]

It's carried in multiverse for that reason.

On Mon, Aug 5, 2019, 05:20 Colin Ian King <1838...@bugs.launchpad.net>
wrote:

> @Srinivas, dptfxtract is a binary, so it can't be packaged in
> debian/ubuntu.  Is there source?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1838590
>
> Title:
>   Update thermald to 1.9 release
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/dptfxtract/+bug/1838590/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1838590

Title:
  Update thermald to 1.9 release

Status in dptfxtract package in Ubuntu:
  New
Status in thermald package in Ubuntu:
  New

Bug description:
  The thermald 1.9 release was just tagged, and has potential to help
  quite a bit with platform performance on some newer platforms when run
  with kernel 5.3. It would be nice to update eoan to this new release.

  > - The major change in this version is the active power limits adjustment.
  This will be useful to improve performance on some newer platform. But
  this will will lead to increase in CPU and other temperatures. Hence this
  is important to run dptfxtract version 1.4.1 tool to get performance
  sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1).
  If the default configuration picked up by thermald is not optimal, user
  can select other less aggressive configuration. Refer to the README here
  https://github.com/intel/dptfxtract/blob/master/README.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dptfxtract/+bug/1838590/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1838590] Re: Update thermald to 1.9 release

[Mario Limonciello]

Reviewing the package in your PPA I do have a few comments that should
be addressed.

1) It looks like the standards version has been downgraded.  If being modified 
at all it should be bumped up to match standards version in Eoan.  This should 
also be mentioned in debian/changelog
2) VCS-Git and VCS-Browser URLs shouldn't be updated to upstream, packaging 
isn't maintained there.
3) in dptfxtract-helper I'm wondering why do you need to switch to 
dptfxtract-static?  Is there new dependency?
4) debian/rules changes look unnecessary to me, but should be mentioned in 
changelog if needed.
5) I think you should be updating the packaging at 
https://git.launchpad.net/~canonical-hwe-team/+git/dptfxtract, no?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1838590

Title:
  Update thermald to 1.9 release

Status in dptfxtract package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  Fix Released

Bug description:
  The thermald 1.9 release was just tagged, and has potential to help
  quite a bit with platform performance on some newer platforms when run
  with kernel 5.3. It would be nice to update eoan to this new release.

  > - The major change in this version is the active power limits adjustment.
  This will be useful to improve performance on some newer platform. But
  this will will lead to increase in CPU and other temperatures. Hence this
  is important to run dptfxtract version 1.4.1 tool to get performance
  sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1).
  If the default configuration picked up by thermald is not optimal, user
  can select other less aggressive configuration. Refer to the README here
  https://github.com/intel/dptfxtract/blob/master/README.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dptfxtract/+bug/1838590/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot

[Mario Limonciello]

Can you check if you have intel-vbtn or intel-hid driver loaded? I would
think intel-vbtn.

Whichever it is a good experiment with the above comment is to blacklist
the module, rebuild initramfs and reboot. See if this helps.

If it does then it's likely a situation of this driver starting in wrong
state.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822394

Title:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

Status in libinput package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot

[Mario Limonciello]

Looking at the dmesg from #30, it's actually intel-hid.  Here is how to
blacklist: https://askubuntu.com/questions/110341/how-to-blacklist-
kernel-modules

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822394

Title:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

Status in libinput package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake

[Mario Limonciello]

@frio:

S3?  Did you manually switch /sys/power/mem_sleep from s2idle to deep?
By default it should be going into suspend to idle (s2idle) not s3.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1855608

Title:
  Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on
  Intel Comet Lake

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just received a new Dell XPS 13 7390 laptop. With factory
  preinstalled Ubuntu Linux 18.04 LTS and the Dell OEM kernel, graphics
  was severely distorted. The display would constantly flicker with
  areas of the display staying black or showing patterns of square color
  blocks.

  Booting in recovery mode worked, though and I was able to install all
  updates for preinstalled 18.04 LTS with the OEM kernel. Problems in
  non-recovery mode persisted after installing all updates. I then
  updated to Ubuntu 19.04 and changed to "generic" linux kernel image
  without success: Problem persisted, only recovery mode was usable. I
  updated once more to 19.10 again without any success.

  From the perhaps related bug #1849947 I tried latest drm-tip kernel
  from

  https://kernel.ubuntu.com/~kernel-ppa/mainline/

  drm-tip kernel solves the issue for first boot, but after resuming
  from suspend, the same issues display issues occur.

  Kernel images I tried:
  - linux-image-4.15.0-1065-oem - on Ubuntu 18.04 LTS, corrupted graphics 
output without "nomodeset"
  - linux-image-5.0.0-37-generic - on Ubuntu 19.04, corrupted graphics output 
without "nomodeset"
  - linux-image-5.3.0-24-generic - on Ubuntu 19.10, corrupted graphics output 
without "nomodeset"
  - linux-image-unsigned-5.4.0-994-generic - on Ubuntu 19.10, corrupted 
graphics output after resuming from suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.4.0-994-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 18:51:15 2019
  DistUpgraded: 2019-12-07 22:36:44,841 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2019-11-25 (13 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-994-generic 
root=UUID=45745b59-5aff-4246-94d2-34fe9ae5012f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-12-07 (0 days ago)
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd11/08/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855608/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1813537] Re: Wifi + bluetooth adapters are gone after sleep/wake

[Mario Limonciello]

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813537

Title:
  Wifi + bluetooth adapters are gone after sleep/wake

Status in linux package in Ubuntu:
  Invalid

Bug description:
  the only fix I found was to power down and power back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uri2238 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 28 11:15:43 2019
  HibernationDevice: RESUME=UUID=c88d6aec-cb91-4ff5-a406-52c6187e06a5
  InstallationDate: Installed on 2018-01-13 (380 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=dc909762-dd6b-4c9c-84da-f8e16a647a3f ro nouveau.modeset=0 quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813537/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode

[Mario Limonciello]

I have to agree with Paul.  This is a separate issue.

Issues like this often have a firmware component (such as the BIOS ACPI
primitives or touchpad firmware).  Even if the messages are the same I
wouldn't categorize the error messages from another identically with the
problems from this specific system.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1651635

Title:
  XPS 13 9360 trackpad locks into scroll mode

Status in Dell Sputnik:
  Invalid
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I'm running Linux on a Dell XPS 13 (9360) laptop.

  I find that upwards of 10 times per day, my trackpad gets stuck in
  "scrolling" mode. Moving the trackpad won't move the X windows
  pointer, but will send scrolling events to the foreground window.

  When the trackpad is locked in this mode, the touchscreen will still
  let me move the mouse cursor, as will an external mouse.

  On Ubuntu 16.04 freshly restored from the Dell recovery image, I find
  that it's often difficult to get the trackpad to recover.

  I do find that the issue happens less frequently on Dell's build of
  Ubuntu 16.04 than on other linux distributions and versions, but it
  still happens enough to significantly impact my ability to do
  productive work.

  The issue does not occur when running Windows 10 on the same device.

  I suspect that the issue may be related to palm detection or
  misdetecting the user's palm as a gesture to enable scrolling mode,
  but have no proof for this.

  It seems that I'm often able to reproduce the issue by brushing the
  trackpad with my right palm.

  On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx
  4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64
  x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I
  am able to get the trackpad to recover, simply by clicking the
  trackpad:

  /usr/share/X11/xorg.conf.d/99-libinput.conf:

  Section "InputClass"
  Identifier "libinput touchpad catchall"
  Driver "libinput"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Option "Tapping" "True"
  Option "DisableWhileTyping" "True"
  Option "NaturalScrolling" "False"
  Option "AccelProfile" "adaptive"
  Option "AccelSpeed" "0.05"
  Option "MiddleEmulation" "True"
  Option "ScrollMethod" "twofinger"
  # Option "ClickMethod" "clickfinger"
  Option "ClickMethod" "buttonareas"
  EndSection

  
  In my experience, the problem manifests using both the Xorg synaptics driver 
and the Xorg libinput driver.

  root@szx:/etc/modprobe.d# xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech M570   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ DLL075B:01 06CB:76AF Touchpad   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=14   [slave  
keyboard (3)]
  ↳ Intel HID eventsid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]
  root@szx:/etc/modprobe.d#

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot

[Mario Limonciello]

XPS 9575 isn't (currently) available for purchase with Ubuntu.  So yes,
it's below the radar for something that is typically tested, tracked, or
fixed from a BIOS or validation team perspective.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822394

Title:
  [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working
  at gdm screen after boot

Status in libinput package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530] laptop keyboard & touchpad not working at gdm screen after boot

[Mario Limonciello]

5530 2-in-1 also isn't available for purchase with Ubuntu, so same boat.

It's (confusingly) a very different system than 5530 which /is/
available with Ubuntu.

** Summary changed:

- [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530] laptop keyboard & 
touchpad not working at gdm screen after boot
+ [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop 
keyboard & touchpad not working at gdm screen after boot

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822394

Title:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

Status in libinput package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1857883] Re: i915 DMS firmware kbl_dmc_ver1_{01, 04}.bin hang system during suspend

[Mario Limonciello]

> Is there any comment on why this issue only happened on the config
from customer, but not on our configs.

I would recommend to compare CPU stepping, perhaps a regression only
present in later CPU stepping after pre-production samples.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1857883

Title:
  i915 DMS firmware kbl_dmc_ver1_{01,04}.bin hang system during suspend

Status in HWE Next:
  New
Status in OEM Priority Project:
  Triaged
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  steps I done:
   - install stock Bionic
   - full update and reboot
   - suspend system => Failed with dark screen
   - install linux-oem-osp1 and reboot
   - suspend system => Failed with dark screen

  tests I tried:
   - pm_test failed in processors with dark screen

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-oem-osp1 5.0.0.1030.34
  ProcVersionSignature: Ubuntu 5.0.0-1030.34-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1030-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 30 16:59:36 2019
  InstallationDate: Installed on 2019-12-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: linux-meta-oem-osp1
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1401 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-12-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Latitude 5590
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1030-oem-osp1 
root=UUID=d065cd98-cc0b-4711-bcab-74f3e677de3a ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1030.34-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1030-oem-osp1 N/A
   linux-backports-modules-5.0.0-1030-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1030-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/19/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.name: 0083K0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd09/19/2019:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0083K0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5590
  dmi.product.sku: 0817
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1857883/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

[Mario Limonciello]

Alternatively this commit I suspect should help:

https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=1ffdb51f28e8ec6be0a2b812c1765b5cf5c44a8f

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823029

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9078] caught 
SIGTERM, shutting down normally.
  Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager...
  Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was 
not added
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9485] dhcp4 
(wlp2s0): canceled DHCP transaction, DHCP c
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] dhcp4 
(wlp2s0): state changed bound -> done
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] device 
(wlp2s0): DHCPv4: 480 seconds grace period
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9570] 
exiting (success)
  Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: 
[resource:///org/gnome/shell/ui/status/network.js 1187]: reference
  Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded.
  Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager.
  Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection 
(0x55d340e8f5a0), has been already deallocated — im
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for 
context 0x55d34160e1e0 ==
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0   55d345364700 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1   55d345364680 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2   7ffe97451d00 b   
self-hosted:979 (7fc3d4350a60 @ 440)
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from 
f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv6 with address fe80::1c45
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv4 with address 10.30.2.26
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
fe80::1c45:b634:dc94:8f5f on wlp2s0.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
10.30.2.26 on wlp2s0.
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit 
ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface 
p2p-dev-wlp2s0 flags: No such device
  Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system...
  Apr 02 13:39:58 taplop kernel: PM: suspe

[Kernel-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs

[Mario Limonciello]

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760106

Title:
  Enable configuring resume offset via sysfs

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760106/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1760106] [NEW] Enable configuring resume offset via sysfs

[Mario Limonciello]

Public bug reported:

In 4.17 a new attribute is introduced to configure the hibernation
resume offset. Since Ubuntu enables a swapfile by default this attribute
is important to be able to make hibernation work "out of the box".

The patch in the kernel is here:
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

Systemd support for adopting this change is available here:
https://github.com/systemd/systemd/pull/8406
As of 3/30/18 it's not yet been merged however.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760106

Title:
  Enable configuring resume offset via sysfs

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760106/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs

[Mario Limonciello]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760106

Title:
  Enable configuring resume offset via sysfs

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760106/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs

[Mario Limonciello]

** Also affects: klibc (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this attribute
  is important to be able to make hibernation work "out of the box".
  
  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9
  
  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.
+ 
+ Klibc support for adopting this change is available here:
+ https://www.zytor.com/pipermail/klibc/2018-March/003986.html

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760106

Title:
  Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Mario Limonciello]

** Summary changed:

- Enable configuring resume offset via sysfs
+ FFe: Enable configuring resume offset via sysfs

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760106

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Mario Limonciello]

@Andy,

The systemd changes are approved, just waiting for CI to pass and
they'll be merged.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760106

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Mario Limonciello]

regarding klibc upstream is MIA for a long time.  There are patches that
have been posted before mine, but no activity since:

commit 4d19974d7020488f63651244e1f9f51727c3f66c
Author: H. Peter Anvin 
Date:   Mon Feb 1 13:26:01 2016 -0800

[klibc] fwrite: fix typo in comment

Fix typo in comment, no code change.

Reported-by: Gilles Espinasse 
Signed-off-by: H. Peter Anvin 

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760106

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools

[Mario Limonciello]

> Did I get the interpretation of these rules correct?
At a glance it looks like what you thought, but dig a little deeper.
1. The rule calls tbtacl add 
(https://github.com/intel/thunderbolt-software-user-space/blob/master/tbtacl/tbtacl.rules.in#L2)
2. tbtacl add calls authorize: 
https://github.com/intel/thunderbolt-software-user-space/blob/master/tbtacl/tbtacl.in#L117
3. Authorize looks if it's in the ACL: 
https://github.com/intel/thunderbolt-software-user-space/blob/master/tbtacl/tbtacl.in#L66

If it's not in the ACL it exits.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thunderbolt-tools in Ubuntu.
Matching subscriptions: Kernel Packages
https://bugs.launchpad.net/bugs/1748157

Title:
   [MIR] thunderbolt-tools

Status in thunderbolt-tools package in Ubuntu:
  Confirmed

Bug description:
  == Overview ==

  Intel Thunderbolt userspace components provides components for using
  Intel Thunderbolt controllers with security level features.
  Thunderbolt™ technology is a transformational high-speed, dual
  protocol I/O that provides unmatched performance with up to 40Gbps bi-
  directional transfer speeds. It provides flexibility and simplicity by
  supporting both data (PCIe, USB3.1) and video (DisplayPort) on a
  single cable connection that can daisy-chain up to six devices.

  [ See https://github.com/intel/thunderbolt-software-user-space ]

  == Answers to UbuntuMainInclusionRequirements ==

  = Requirements =

  1. Availability
 Package is in universe: 
https://launchpad.net/ubuntu/+source/thunderbolt-tools

  2. Rationale
 Package a device enabler for users with Thunderbolt technology

  3. Security:
 No security issues exposed so far. However, the tools have only been in 
Ubuntu since
 2017-12-09, so this currently is less than the 90 days threshold.

  4. Quality assurance:
 * Manual is provided
 * No debconf questions higher than medium
 * No major outstanding bugs. I'm also helping Intel fix issues that I'm 
finding with
   static analysis tools such as scan-build, cppcheck and CoverityScan
   Bugs outstanding:
 #883857 please backport for stretch-backports
 #882525 thunderbolt-tools: FTBFS on kFreeBSD: 
_ZN5boost6system15system_categoryEv undefined
   - I can fix this, but it makes no sense to run on kFreeBSD
 * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an 
industry standard
   and the support for the tools are in the 4.13+ kernels
 * No Test Suite shipped with the package
 * Does not rely on obsolete or demoted packages

  5. UI standards:
 * This is a CLI tool. Tool has normal CLI style short help and man pages
 * No desktop file required as it is a CLI tool.

  6. Binary Dependencies:
libboost-dev(main)
libboost-filesystem-dev (main)
libboost-program-options-dev(main)
udev(main)

  7. Standards compliance:
 lintian clean and meets the FHS + Debian Policy standards to the best of 
my knowledge

  8. Maintenance
 * Package owning team: The Ubuntu Kernel Team
 * Debian package maintained by Colin Ian King (myself from the Kernel Team)

  9. Background Information
 The user-space components implement device approval support:

 a. Easier interaction with the kernel module for approving connected 
devices.
 b. ACL for auto-approving devices white-listed by the user.

 Tools provided by this package:

  tbtacl - triggered by udev (see the udev rules in tbtacl.rules).
  It auto-approves devices that are found in ACL.

  tbtadm - user-facing CLI tool. It provides operations for device
  approval, handling the ACL and more.

  The user-space components operate in coordination with the
  upstream Thunderbolt kernel driver (found in v4.13) to provide the
  Thunderbolt functionalities. These components are NOT compatible with
  the old out-of-tree Thunderbolt kernel module.

  = Security checks =

http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability 
Database using the package as a keyword
* No CVEs found

http://secunia.com/advisories/search/: search for the package as a keyword
* No security advisories found

Ubuntu CVE Tracker
  http://people.ubuntu.com/~ubuntu-security/cve/main.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/universe.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/partner.html
  * No

  Check for security relevant binaries. If any are present, this
  requires a more in-depth security review.

  Executables which have the suid or sgid bit set.
* Not applicable

  Executables in /sbin, /usr/sbin.
* None in these paths

  Packages which install daemons (/etc/init.d/*)
* No

  Packages which open privileged ports (ports < 1024).
* No

   Add-

[Kernel-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Mario Limonciello]

@xnox in order to coordinate the systemd upload in case you have
anything in flight, here's a debdiff:

** Patch added: "backported fix from upstream"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1760106/+attachment/5110809/+files/systemd-offsets.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760106

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50

[Mario Limonciello]

@Kai Heng,

I believe this should help:

Can you please apply
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/media/usb/uvc?h=v4.17-rc1&id=e96cdc9a0aa2fcaa276a76e8ffa86fc10a1d3d99
to a test kernel?

Or alternatively can someone affected please test 4.17-rc1 (it's
included)?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1763748

Title:
  Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
  in DELL XPS 13 9370 with firmware 1.50

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The webcam is detected by the system, but no applications detect it.

  sudo lsusb -v: (relevant part)
  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.01
    bDeviceClass  239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize064
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x58f4
    bcdDevice   72.79
    iManufacturer   3 CN0FFMHCLOG0081SB0M1A01
    iProduct1 Integrated_Webcam_HD
    iSerial 2 200901010001

  In syslog (firmware can be seen in first line - 1.50):
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new 
interface driver btusb
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non 
compliance - GET_DEF(PROBE) not supported. Enabling workaround.
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query 
(129) UVC probe control : -75 (exp. 34).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to 
initialize the device (-5).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video 
format 0032-0002-0010-8000-00aa00389b71
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wgarcia2145 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 13 16:59:02 2018
  HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc
  InstallationDate: Installed on 2018-04-09 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50

[Mario Limonciello]

@Walter Garcia-Fontes,

Sorry, I missed that comment of yours.  Thank you for confirming that
4.17-rc1 didn't adequately resolve the issue.

I believe what this is coming down to is that there are still aspects
from UVC 1.5 that are missing in the kernel then.

@Kai Heng,

There is no plugin currently available for fwupdmgr that can downgrade
this firmware currently.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1763748

Title:
  Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
  in DELL XPS 13 9370 with firmware 1.50

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The webcam is detected by the system, but no applications detect it.

  sudo lsusb -v: (relevant part)
  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.01
    bDeviceClass  239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize064
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x58f4
    bcdDevice   72.79
    iManufacturer   3 CN0FFMHCLOG0081SB0M1A01
    iProduct1 Integrated_Webcam_HD
    iSerial 2 200901010001

  In syslog (firmware can be seen in first line - 1.50):
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new 
interface driver btusb
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non 
compliance - GET_DEF(PROBE) not supported. Enabling workaround.
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query 
(129) UVC probe control : -75 (exp. 34).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to 
initialize the device (-5).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video 
format 0032-0002-0010-8000-00aa00389b71
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wgarcia2145 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 13 16:59:02 2018
  HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc
  InstallationDate: Installed on 2018-04-09 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Mario Limonciello]

@Kat,

Can you please confirm the particular Ubuntu kernel that you are still
encountering the need to run this command?  As I understood this patch
(that effectively does what that command does) is backported into all
the latest Ubuntu kernels, so if it's still happening that is important
information.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729674

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux package in Fedora:
  Confirmed

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50

[Mario Limonciello]

All,

The patch has been submitted here:

https://lkml.org/lkml/2018/5/8/1117

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1763748

Title:
  Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
  in DELL XPS 13 9370 with firmware 1.50

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The webcam is detected by the system, but no applications detect it.

  sudo lsusb -v: (relevant part)
  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.01
    bDeviceClass  239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize064
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x58f4
    bcdDevice   72.79
    iManufacturer   3 CN0FFMHCLOG0081SB0M1A01
    iProduct1 Integrated_Webcam_HD
    iSerial 2 200901010001

  In syslog (firmware can be seen in first line - 1.50):
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new 
interface driver btusb
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non 
compliance - GET_DEF(PROBE) not supported. Enabling workaround.
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query 
(129) UVC probe control : -75 (exp. 34).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to 
initialize the device (-5).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video 
format 0032-0002-0010-8000-00aa00389b71
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wgarcia2145 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 13 16:59:02 2018
  HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc
  InstallationDate: Installed on 2018-04-09 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50

[Mario Limonciello]

@Kai Heng,

Can you share a test kernel with that patch for folks in this thread
affected?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1763748

Title:
  Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
  in DELL XPS 13 9370 with firmware 1.50

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The webcam is detected by the system, but no applications detect it.

  sudo lsusb -v: (relevant part)
  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.01
    bDeviceClass  239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize064
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x58f4
    bcdDevice   72.79
    iManufacturer   3 CN0FFMHCLOG0081SB0M1A01
    iProduct1 Integrated_Webcam_HD
    iSerial 2 200901010001

  In syslog (firmware can be seen in first line - 1.50):
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new 
interface driver btusb
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non 
compliance - GET_DEF(PROBE) not supported. Enabling workaround.
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query 
(129) UVC probe control : -75 (exp. 34).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to 
initialize the device (-5).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video 
format 0032-0002-0010-8000-00aa00389b71
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wgarcia2145 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 13 16:59:02 2018
  HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc
  InstallationDate: Installed on 2018-04-09 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50

[Mario Limonciello]

@Josef,

Glad to hear that confirmation.  It may be useful to respond with a Tested-by 
to the patch upstream.
https://patchwork.kernel.org/patch/10388043/

@Stefano

No need to upgrade again.  You can stay at 1.0 and it's functionally
just fine with Ubuntu.

Thanks,

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1763748

Title:
  Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
  in DELL XPS 13 9370 with firmware 1.50

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The webcam is detected by the system, but no applications detect it.

  sudo lsusb -v: (relevant part)
  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.01
    bDeviceClass  239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize064
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x58f4
    bcdDevice   72.79
    iManufacturer   3 CN0FFMHCLOG0081SB0M1A01
    iProduct1 Integrated_Webcam_HD
    iSerial 2 200901010001

  In syslog (firmware can be seen in first line - 1.50):
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new 
interface driver btusb
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non 
compliance - GET_DEF(PROBE) not supported. Enabling workaround.
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query 
(129) UVC probe control : -75 (exp. 34).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to 
initialize the device (-5).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video 
format 0032-0002-0010-8000-00aa00389b71
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wgarcia2145 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 13 16:59:02 2018
  HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc
  InstallationDate: Installed on 2018-04-09 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50

[Mario Limonciello]

Only if you have userspace that uses other 1.5 features, which doesn't
exist today in Linux. The patch and fw 1.0 should be functionally
equivalent for Linux.

On Fri, May 11, 2018, 17:01 alkemyst <1763...@bugs.launchpad.net> wrote:

> @Mario
> Well, 1.0 already works without any patch. It'just downgraded in features
> too, right?
>
> S
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1763748
>
> Title:
>   Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
>   in DELL XPS 13 9370 with firmware 1.50
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1763748

Title:
  Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
  in DELL XPS 13 9370 with firmware 1.50

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The webcam is detected by the system, but no applications detect it.

  sudo lsusb -v: (relevant part)
  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.01
    bDeviceClass  239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize064
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x58f4
    bcdDevice   72.79
    iManufacturer   3 CN0FFMHCLOG0081SB0M1A01
    iProduct1 Integrated_Webcam_HD
    iSerial 2 200901010001

  In syslog (firmware can be seen in first line - 1.50):
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new 
interface driver btusb
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non 
compliance - GET_DEF(PROBE) not supported. Enabling workaround.
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query 
(129) UVC probe control : -75 (exp. 34).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to 
initialize the device (-5).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video 
format 0032-0002-0010-8000-00aa00389b71
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wgarcia2145 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 13 16:59:02 2018
  HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc
  InstallationDate: Installed on 2018-04-09 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1781533] Re: SATA device is not going to DEVSLP

[Mario Limonciello]

The first 2 I have no concerns, but would like to see a tested-by
submitted back to that patch to encourage it to land upstream.

The third patch, there has been a second submission (and will likely be a 3rd 
based on feedback).
https://patchwork.kernel.org/patch/10522375/

Conceptually I have no concern with the 3rd patch but just please track
to make sure the right policy does get adopted from it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1781533

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leading to other devices not getting there during long idle or s2idle. 
And it also prevents the system from entering deeper PC state other than PC3.

  [Test]
  Verified the power consumption on some new platforms, it doesn't do too much 
difference on the numbers, but it improves.

  [Fix]
  Suggested from Intel and Dell to contains the 2 commits
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/

  The third commit sets by default link power management policy to min_power
  https://patchwork.kernel.org/patch/10502291/

  [Regression Potential]
  Low, the production machines with suspend-to-idle enabled should have the 
DEVSLP function been validated.

  [Misc]
  Those commits do not show up in any public git tree yet, so let's verify
  them in oem kernel first, and then will submit to bionic kernel later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1781533/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1806323] Re: libfu_plugin_dell.so w/dell TB16 Dock blanks the display

[Mario Limonciello]

Thanks for the response.  There is quite a lot going on here.

First off - The XPS 9570 is a CFL system.

The going black in the first place is an artifact what fwupd does to
query the firmware on the MST hubs in the dock.  What it does is "wakes"
the MST hubs by putting them into a higher power mode.  When in this
mode 1-2 "fake monitors" shows up in DPCD of the DP aux channel.  This
allows applications such as fwupd to interact with the monitor.  The
flicker and going black is the i915 driver probing those "fake"
monitors.

To me this is all expected behavior thus far.

Something that (I think?) might help is if the graphics drivers can
blacklist the EDID associated with the fake monitors to prevent re-
probing them but still letting communication with them work for fwupd.
That needs to be discussed with the Intel graphics folks to see if
that's a possibility.

If it's not, then we have to have a tradeoff of no version is registered
with fwupd when no (or not enough) monitors are plugged into the dock.

Now with 4.19, the staying black sounds like a separate graphics driver bug.
It might be useful if you can test with drm-tip and still reproduce that.  if 
so, then this is worth reporting to Intel's graphics bugzilla to investigate.

The USB not working, I would wonder if it's actually an artifact of the
above bug.  Userspace is hung and so bolt isn't authorizing the
thunderbolt device meaning USB won't work.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: fwupd (Ubuntu)
   Status: New => Triaged

** Changed in: fwupd (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806323

Title:
  libfu_plugin_dell.so w/dell TB16 Dock blanks the display

Status in fwupd package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Absolutely reproducible in Ubuntu 18.04.1 Gnome 3 UI with a Dell XP15
  laptop and a Dell TB16 dock.

  A few seconds after logging into the Gnome 3 UI, something in the UI
  starts the fwupd.service. About 2 seconds later, the display goes
  blank and does not come back. There is no obvious recovery short of
  killing all the user's processes, and then logging back in.  A second
  login does not reproduce the problem, since the fwupd service is now
  running, and does not restart. However manually restarting the fwupd
  service causes the problem to recur.

  The problem does not occur if the "dell" module is blacklisted in
  /etc/fwupd/daemon.conf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: fwupd 1.0.6-2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 22:02:31 2018
  InstallationDate: Installed on 2018-11-19 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: fwupd
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.fwupd.daemon.conf: 2018-12-02T21:41:51.195270

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1806323/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1810619] Re: Sleep mode doesn't work

[Mario Limonciello]

>With :
>$ sudo sh -c 'echo mem > /sys/power/state'
>$ sudo sh -c 'echo deep > /sys/power/mem_sleep'
>the problem disappears.

This is changing how the system goes to sleep in a significant way.
With this, the BIOS turns off all devices except RAM when going to
sleep.  With the way that it works by default the kernel is controlling
all devices and putting them into their deepest sleep state.

This system "mem" will work on this system, but that can't be said for all 
systems.
You can change the default policy to this if you would like too using a 
modification to your kernel command line.  It is better in my opinion to figure 
out the root cause of your problem though.  It will lead to better runtime 
power consumption if we figure it out.

A few questions:
@Grentz:
1) Do you have anything plugged into notebook during sleep cycle with s2idle?  
Mouse, keyboard, USB key - anything like that.
2) Can you try to run powertop with --auto-tune and see if it improves things?
3) After running autotune wait a few moments and then can you please cat 
/sys/kernel/debug/pmc_core/pch_ip_power_gating_status and share results?

@Kai Heng:
4) Policy wise isn't TLP or something similar going to be needed to enact RTD3 
for the rest of the devices that kernel policy isn't properly configured?  I 
know the preload image has stuff like that.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810619

Title:
  Sleep mode doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 13 laptop (9370), the sleep mode dosn't work anymore with 
linux-image-4.18.0-13.
  The screen goes off correctly but any touch resume the laptop.

  This is the log :
  Jan  5 11:15:25 skeleton systemd[1]: Reached target Sleep.
  Jan  5 11:15:25 skeleton systemd[1]: Starting Suspend...
  Jan  5 11:15:25 skeleton systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Jan  5 11:15:25 skeleton systemd-sleep[6229]: Suspending system...
  Jan  5 11:15:25 skeleton kernel: [ 6176.006021] PM: suspend entry (s2idle)
  an  5 11:15:25 skeleton dbus-daemon[1051]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
  Jan  5 11:15:25 skeleton systemd[1]: Started Network Manager Script 
Dispatcher Service.
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: new request (1 
scripts)
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: start running 
ordered scripts...

  [...]
  Resume :

  Jan  5 12:00:02 skeleton kernel: [ 6176.006023] PM: Syncing filesystems ... 
done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.016581] Freezing user space processes 
... (elapsed 0.088 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104653] OOM killer disabled.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104654] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.106070] Suspending console(s) (use 
no_console_suspend to debug)
  Jan  5 12:00:02 skeleton kernel: [ 8852.990035] OOM killer enabled.
  Jan  5 12:00:02 skeleton kernel: [ 8852.990037] Restarting tasks ... done.
  Jan  5 12:00:02 skeleton kernel: [ 8853.015639] r8152 2-1.2:1.0 
enxe4b97acfa7e9: carrier on
  Jan  5 12:00:02 skeleton kernel: [ 8853.084055] PM: suspend exit


  
  With linux-image-4.18.0-10, it works correcly (but no with 4.18.0-11 and 
4.18.0-12).
  Thanks,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810619/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1810619] Re: Sleep mode doesn't work

[Mario Limonciello]

Can you please test without your adapter plugged in prior to the sleep
cycle? Due to the way suspend to idle works this may cause the PCH to
remain in a higher power state burning a lot more battery.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810619

Title:
  Sleep mode doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 13 laptop (9370), the sleep mode dosn't work anymore with 
linux-image-4.18.0-13.
  The screen goes off correctly but any touch resume the laptop.

  This is the log :
  Jan  5 11:15:25 skeleton systemd[1]: Reached target Sleep.
  Jan  5 11:15:25 skeleton systemd[1]: Starting Suspend...
  Jan  5 11:15:25 skeleton systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Jan  5 11:15:25 skeleton systemd-sleep[6229]: Suspending system...
  Jan  5 11:15:25 skeleton kernel: [ 6176.006021] PM: suspend entry (s2idle)
  an  5 11:15:25 skeleton dbus-daemon[1051]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
  Jan  5 11:15:25 skeleton systemd[1]: Started Network Manager Script 
Dispatcher Service.
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: new request (1 
scripts)
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: start running 
ordered scripts...

  [...]
  Resume :

  Jan  5 12:00:02 skeleton kernel: [ 6176.006023] PM: Syncing filesystems ... 
done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.016581] Freezing user space processes 
... (elapsed 0.088 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104653] OOM killer disabled.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104654] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.106070] Suspending console(s) (use 
no_console_suspend to debug)
  Jan  5 12:00:02 skeleton kernel: [ 8852.990035] OOM killer enabled.
  Jan  5 12:00:02 skeleton kernel: [ 8852.990037] Restarting tasks ... done.
  Jan  5 12:00:02 skeleton kernel: [ 8853.015639] r8152 2-1.2:1.0 
enxe4b97acfa7e9: carrier on
  Jan  5 12:00:02 skeleton kernel: [ 8853.084055] PM: suspend exit


  
  With linux-image-4.18.0-10, it works correcly (but no with 4.18.0-11 and 
4.18.0-12).
  Thanks,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810619/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1687413] Re: MST display setup show shifted, flickering picture in second half of the screen

[Mario Limonciello]

** Package changed: linux-hwe-edge (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1687413

Title:
  MST display setup show shifted, flickering picture in second half of
  the screen

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Trying to set up MST display with Intel graphics card (Dell XPS 12
  9360, Intel HD 620), but the second half of the screen is shifted
  randomly and is flickering (attached screenshot).

  uname -r
  4.10.0-14-generic


  cat ~/.xprofile
  #!/bin/sh
  xrandr --addmode DP-1 "2560x2880" && 
  xrandr --output DP-1 --above eDP-1 --mode "2560x2880" && 
  xrandr --output DP-2 --right-of DP-1 --mode "2560x2880"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  1 09:39:32 2017
  InstallationDate: Installed on 2017-04-15 (16 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1687413/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1687413] Re: MST display setup show shifted, flickering picture in second half of the screen

[Mario Limonciello]

There has been a lot of work upstream in the graphics stack around MST, but not 
all of it has been merged yet.  Would you be able to test with drm-next to see 
if the problem is resolved there?
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/current/

If it's resolved there, there will need to some effort to bisect the
particular commit that fixed it and backport it to an Ubuntu kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1687413

Title:
  MST display setup show shifted, flickering picture in second half of
  the screen

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Trying to set up MST display with Intel graphics card (Dell XPS 12
  9360, Intel HD 620), but the second half of the screen is shifted
  randomly and is flickering (attached screenshot).

  uname -r
  4.10.0-14-generic


  cat ~/.xprofile
  #!/bin/sh
  xrandr --addmode DP-1 "2560x2880" && 
  xrandr --output DP-1 --above eDP-1 --mode "2560x2880" && 
  xrandr --output DP-2 --right-of DP-1 --mode "2560x2880"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  1 09:39:32 2017
  InstallationDate: Installed on 2017-04-15 (16 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1687413/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1687413] Re: MST display setup show shifted, flickering picture in second half of the screen

[Mario Limonciello]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: linux (Ubuntu)
   Status: Opinion => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1687413

Title:
  MST display setup show shifted, flickering picture in second half of
  the screen

Status in Dell Sputnik:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to set up MST display with Intel graphics card (Dell XPS 12
  9360, Intel HD 620), but the second half of the screen is shifted
  randomly and is flickering (attached screenshot).

  uname -r
  4.10.0-14-generic


  cat ~/.xprofile
  #!/bin/sh
  xrandr --addmode DP-1 "2560x2880" && 
  xrandr --output DP-1 --above eDP-1 --mode "2560x2880" && 
  xrandr --output DP-2 --right-of DP-1 --mode "2560x2880"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  1 09:39:32 2017
  InstallationDate: Installed on 2017-04-15 (16 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  macat  2488 F pulseaudio
   /dev/snd/controlC0:  macat  2488 F pulseaudio
   /dev/snd/controlC1:  macat  2488 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-04-15 (23 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=dd205104-a1a9-4197-a36d-e96f44b97067 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-generic 4.10.3
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.157.8
  Tags:  xenial
  Uname: Linux 4.10.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1687413/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1687413] Re: MST display setup show shifted, flickering picture in second half of the screen

[Mario Limonciello]

@macat,

OK thanks for confirming.  This is likely an upstream issue then.  Can you 
please file it here:
https://01.org/linuxgraphics/documentation/how-report-bugs

and leave a link back to this bug?

Thanks,

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1687413

Title:
  MST display setup show shifted, flickering picture in second half of
  the screen

Status in Dell Sputnik:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to set up MST display with Intel graphics card (Dell XPS 12
  9360, Intel HD 620), but the second half of the screen is shifted
  randomly and is flickering (attached screenshot).

  uname -r
  4.10.0-14-generic


  cat ~/.xprofile
  #!/bin/sh
  xrandr --addmode DP-1 "2560x2880" && 
  xrandr --output DP-1 --above eDP-1 --mode "2560x2880" && 
  xrandr --output DP-2 --right-of DP-1 --mode "2560x2880"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  1 09:39:32 2017
  InstallationDate: Installed on 2017-04-15 (16 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  macat  2488 F pulseaudio
   /dev/snd/controlC0:  macat  2488 F pulseaudio
   /dev/snd/controlC1:  macat  2488 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-04-15 (23 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=dd205104-a1a9-4197-a36d-e96f44b97067 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-generic 4.10.3
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.157.8
  Tags:  xenial
  Uname: Linux 4.10.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1687413/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1687397] Re: Kernel freeze when plugging in external monitor via USB-C->DP-Adapter

[Mario Limonciello]

** Changed in: dell-sputnik
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1687397

Title:
  Kernel freeze when plugging in external monitor via USB-C->DP-Adapter

Status in Dell Sputnik:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When plugging in/out my external monitor (Acer B286HK) via an USB-C ->
  DP Adapter, there is a great chance, that the computer completely
  freezes. SysReq-Keys are also not working.

  
  I added a kernel.log where you can see the boot-up after one crash, than 
plugging In/Out the monitor several times till a new complete freeze.

  The graphics-card is the internal one of Core(TM) i7-7500Uin of the
  XPS13 MLK (9360).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-75-generic 4.4.0-75.96
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eiko   2382 F pulseaudio
   /dev/snd/controlC0:  eiko   2382 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May  1 13:25:42 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=baaa9d41-2d3b-4937-82f8-e923789084a5
  InstallationDate: Installed on 2016-12-03 (148 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed 
root=UUID=758f75ff-3e8f-4d25-8419-f30f215feee3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1687397/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot

[Mario Limonciello]

To anyone who has been affected - there is a discussion going on the
kernel mailing lists regarding this issue and it would be helpful if you
can provide an acpidump.  You can attach it to this bug (or file a
kernel bugzilla and attach it there).

Desired would be the 1.2.0 firmware (which some people have downgraded
to workaround this issue) as well as a current affected firmware.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822394

Title:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

Status in libinput package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot

[Mario Limonciello]

Thanks Joe!  By chance can you upgrade to current BIOS too and get that
dump again?  There is that workaround now (blacklist intel-vbtn) which
you should be able to use now if you have no other problems with current
firmware.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822394

Title:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

Status in libinput package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot

[Mario Limonciello]

Thanks so much!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1822394

Title:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

Status in libinput package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1880835] Re: pulse audio hangs in kernel call

[Mario Limonciello]

KH: Agree it looks like IOMMU bug, this needs to get raised up to the
Intel IOMMU guys.  They are tracking something specific to i915 in ICL
and TGL, but this is not as new.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1880835

Title:
  pulse audio hangs in kernel call

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  there is no audio device accessible any more and pulse-audio process can not 
be terminated 
  in kernel log there is such a output:

  This makes the complete audio unstable in the laptop.

  I think it is started to happen when I installed Nvidia driver and
  there is an external monitor attached with DP audio device.

  [  364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds.
  [  364.150646]   Tainted: P   OE 5.4.0-31-generic #35-Ubuntu
  [  364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  364.150647] pulseaudio  D0  2183   2175 0x4120
  [  364.150649] Call Trace:
  [  364.150653]  __schedule+0x2e3/0x740
  [  364.150655]  ? dma_pte_clear_level+0x142/0x190
  [  364.150655]  schedule+0x42/0xb0
  [  364.150656]  schedule_timeout+0x203/0x2f0
  [  364.150657]  wait_for_completion+0xb1/0x120
  [  364.150659]  ? wake_up_q+0x70/0x70
  [  364.150663]  fw_run_transaction+0xdc/0x110 [firewire_core]
  [  364.150665]  ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core]
  [  364.150666]  ? free_iova_fast+0x18/0x30
  [  364.150667]  ? close_transaction+0x110/0x110 [firewire_core]
  [  364.150668]  ? intel_unmap+0xd9/0x1c0
  [  364.150670]  ? transmit_phy_packet_callback+0x20/0x20 [firewire_core]
  [  364.150671]  snd_fw_transaction+0xbc/0x110 [snd_firewire_lib]
  [  364.150673]  ? avc_general_get_plug_info+0x100/0x100 [snd_firewire_lib]
  [  364.150674]  pcr_modify+0x65/0x100 [snd_firewire_lib]
  [  364.150675]  cmp_connection_break+0x37/0x50 [snd_firewire_lib]
  [  364.150677]  snd_oxfw_stream_start_duplex+0x1ee/0x2e0 [snd_oxfw]
  [  364.150678]  ? wait_woken+0x80/0x80
  [  364.150679]  pcm_capture_prepare+0x26/0x50 [snd_oxfw]
  [  364.150682]  snd_pcm_do_prepare+0x1e/0x30 [snd_pcm]
  [  364.150684]  snd_pcm_action_single+0x3c/0x80 [snd_pcm]
  [  364.150686]  snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm]
  [  364.150687]  snd_pcm_prepare+0x6a/0x90 [snd_pcm]
  [  364.150689]  snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm]
  [  364.150691]  snd_pcm_ioctl+0x27/0x40 [snd_pcm]
  [  364.150692]  do_vfs_ioctl+0x407/0x670
  [  364.150694]  ? __secure_computing+0x42/0xe0
  [  364.150694]  ksys_ioctl+0x67/0x90
  [  364.150695]  __x64_sys_ioctl+0x1a/0x20
  [  364.150697]  do_syscall_64+0x57/0x190
  [  364.150698]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  364.150699] RIP: 0033:0x7f0bbfa1a37b
  [  364.150701] Code: Bad RIP value.
  [  364.150701] RSP: 002b:7ffed915d308 EFLAGS: 0202 ORIG_RAX: 
0010
  [  364.150702] RAX: ffda RBX: 5607c7b63de0 RCX: 
7f0bbfa1a37b
  [  364.150703] RDX:  RSI: 4140 RDI: 
006e
  [  364.150703] RBP: 5607c7b63bb0 R08:  R09: 
1000
  [  364.150703] R10: 0004 R11: 0202 R12: 
5607c7b63de0
  [  364.150704] R13: 7ffed915d6f0 R14:  R15: 
7ffed915d480

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 27 10:07:13 2020
  InstallationDate: Installed on 2020-02-22 (94 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
  MachineType: Dell Inc. Precision 7540
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic 
root=UUID=7a5890f6-2724-480a-8fa7-778d07cd929d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 0T2FXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0T2FXT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7540
  dmi.product.sku: 0926
  dmi.sys.vendor: Dell Inc.

To manage notifications about this b

[Kernel-packages] [Bug 1908322] Re: Dell WD19 upgrade issue

[Mario Limonciello]

In the issue reported upstream it was concluded not to be a fwupd
problem, nor a WD19TB problem.  The same issue occurs trying to read the
NVM from the host.  So kernel issue TBT FW issue, or HW issue.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908322

Title:
  Dell WD19 upgrade issue

Status in fwupd package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm running 20.04 and got the alert there was a FW update pending, so
  I ran it but it's failing:

   
  ➜ sudo fwupdmgr update --force -y  
  Upgrade available for Thunderbolt controller in Dell dock from 40.00 to 43.00
  Downloading 43.00 for Thunderbolt controller in Dell dock...
  Decompressing…   [***]
  Authenticating…  [***]
  Updating Thunderbolt controller in Dell dock…]
  Writing… [***]
  could not start thunderbolt device upgrade: could not write to 
'nvm_authenticate': Input/output error

  I have also logged this against upstream fwupd, but haven't got
  anywhere as yet (good for reference though):
  https://github.com/fwupd/fwupd/issues/2689

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1908322/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1908322] Re: Dell WD19 upgrade issue

[Mario Limonciello]

** Changed in: fwupd (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908322

Title:
  Dell WD19 upgrade issue

Status in fwupd package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running 20.04 and got the alert there was a FW update pending, so
  I ran it but it's failing:

   
  ➜ sudo fwupdmgr update --force -y  
  Upgrade available for Thunderbolt controller in Dell dock from 40.00 to 43.00
  Downloading 43.00 for Thunderbolt controller in Dell dock...
  Decompressing…   [***]
  Authenticating…  [***]
  Updating Thunderbolt controller in Dell dock…]
  Writing… [***]
  could not start thunderbolt device upgrade: could not write to 
'nvm_authenticate': Input/output error

  I have also logged this against upstream fwupd, but haven't got anywhere as 
yet (good for reference though): https://github.com/fwupd/fwupd/issues/2689
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-16 (182 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17
  Tags: third-party-packages focal
  Uname: Linux 5.8.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd microk8s plugdev sambashare 
sudo
  _MarkForUpload: True
  mtime.conffile..etc.fwupd.daemon.conf: 2020-12-15T09:26:17.669606
  mtime.conffile..etc.fwupd.remotes.d.lvfs-testing.conf: 
2020-12-15T09:24:32.782612
  mtime.conffile..etc.fwupd.remotes.d.lvfs.conf: 2020-12-15T09:24:32.842613

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1908322/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1908322] Re: Dell WD19 upgrade issue

[Mario Limonciello]

** Bug watch added: Linux Kernel Bug Tracker #210761
   https://bugzilla.kernel.org/show_bug.cgi?id=210761

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=210761
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908322

Title:
  Dell WD19 upgrade issue

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running 20.04 and got the alert there was a FW update pending, so
  I ran it but it's failing:

   
  ➜ sudo fwupdmgr update --force -y  
  Upgrade available for Thunderbolt controller in Dell dock from 40.00 to 43.00
  Downloading 43.00 for Thunderbolt controller in Dell dock...
  Decompressing…   [***]
  Authenticating…  [***]
  Updating Thunderbolt controller in Dell dock…]
  Writing… [***]
  could not start thunderbolt device upgrade: could not write to 
'nvm_authenticate': Input/output error

  I have also logged this against upstream fwupd, but haven't got anywhere as 
yet (good for reference though): https://github.com/fwupd/fwupd/issues/2689
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-16 (182 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-33.36~20.04.1-generic 5.8.17
  Tags: third-party-packages focal
  Uname: Linux 5.8.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd microk8s plugdev sambashare 
sudo
  _MarkForUpload: True
  mtime.conffile..etc.fwupd.daemon.conf: 2020-12-15T09:26:17.669606
  mtime.conffile..etc.fwupd.remotes.d.lvfs-testing.conf: 
2020-12-15T09:24:32.782612
  mtime.conffile..etc.fwupd.remotes.d.lvfs.conf: 2020-12-15T09:24:32.842613

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1908322/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10

[Mario Limonciello]

I'm marking eoan as fixed, as it has 1.2.10 which contains the
workaround to avoid using synaptics mst on amdgpu devices.

The kernel tasks is still open as this is still a real kernel problem.

** Changed in: fwupd (Ubuntu Eoan)
   Status: Triaged => Fix Released

** Changed in: fwupd (Ubuntu Disco)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1826691

Title:
  fwupd hangs after 19.04 upgrade from 18.10

Status in Linux:
  Unknown
Status in fwupd package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in fwupd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Triaged
Status in fwupd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Triaged

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  Being a firmware updater, the machine is probably relevant - Dell
  7730.

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt policy fwupd
  fwupd:
Installed: (none)
Candidate: 1.2.5-1ubuntu1
Version table:
   1.2.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  I expected few/no issues after 19.04 upgrade. The fwupd process worked 
perfectly in 18.10. It's upgraded the firmware on my laptop twice since I 
installed 18.10.

  
  4) What happened instead
  After upgrading from 18.10 to 19.04 I had an issues that when I tried to 
suspend my laptop using the same button press as previous, the laptop would be 
hot and screen flickering when I returned to reopen it. I thought there were 
power management issues in the upgrade, but I've traced it to fwupd not letting 
the PM suspend process complete (see dmesg below). I tried shutting down the 
fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr 
commands timeout. 

  Thinking something might have broken in the upgrade, I tried
  uninstalling (purge) the fwupd package and reinstalling. Starting the
  process with systemctl hangs forever like stopping it. Trying to kill
  -9 the process does not work - in uninterruptible sleep (D).

  
  This crash is probably related. It happened a couple of ours before I tried 
to put it to sleep the last time before uninstalling fwupd.

  
  Apr 23 19:29:14 texas kernel: [  133.673290] [drm] REG_WAIT timeout 10us * 
160 tries - submit_channel_request line:246
  Apr 23 19:29:14 texas kernel: [  133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
  Apr 23 19:29:14 texas kernel: [  133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
  Apr 23 19:29:14 texas kernel: [  133.673362]  ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei 
fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch 
processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt 
intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone 
dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel 
sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci 
nvme_core intel_lpss i2c_hid wmi hid video 

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Mario Limonciello]

@Dave:

I was glancing at r8152 driver and notice that it has some special handling for 
ipv6.  Is this issue reproducing only in ipv6 for you?
https://github.com/torvalds/linux/commit/6128d1bb30748d0ff56a63898d14f312126e404c

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729674

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  In Progress

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Mario Limonciello]

** Bug watch added: Red Hat Bugzilla #1460789
   https://bugzilla.redhat.com/show_bug.cgi?id=1460789

** Also affects: linux (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1460789
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729674

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux package in Fedora:
  Unknown

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1734761] [NEW] enable new configure options for 4.15

[Mario Limonciello]

Public bug reported:

Hi,

When 4.15 is brought into Ubuntu bionic I wanted to make sure that a few
configure options were selected to compile as module (as they won't come
by default):

1) Intel WMI thunderbolt driver
2) Dell SMBIOS WMI driver
3) Dell SMBIOS SMM driver

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734761

Title:
  enable new configure options for 4.15

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  When 4.15 is brought into Ubuntu bionic I wanted to make sure that a
  few configure options were selected to compile as module (as they
  won't come by default):

  1) Intel WMI thunderbolt driver
  2) Dell SMBIOS WMI driver
  3) Dell SMBIOS SMM driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734761/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1734761] Re: enable new configure options for 4.15

[Mario Limonciello]

Not relevant for this bug.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734761

Title:
  enable new configure options for 4.15

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  When 4.15 is brought into Ubuntu bionic I wanted to make sure that a
  few configure options were selected to compile as module (as they
  won't come by default):

  1) Intel WMI thunderbolt driver
  2) Dell SMBIOS WMI driver
  3) Dell SMBIOS SMM driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734761/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools

[Mario Limonciello]

At the time Colin and I discussed getting thunderbolt-tools into Debian
and then eventually into Ubuntu (& of course main via this MIR) bolt's
GUI wasn't available yet and bolt was still under some pretty heavy
development.

>From a client (general purpose laptop or desktop) system perspective
it's better to offer something with a GUI, but there are other features
that thunderbolt-tools offers that aren't in bolt as well.  For example
thunderbolt-tools provides some udev rules to assist with starting up
thunderbolt networking in the proper situations and recently adopted
some features for controlling what happens with the boot time ACL.

They are both great solutions that will continue to adopt different
features at a different rate. My opinion is that both should be offered
in main, but bolt and bolt GUI should probably be the one that gets
seeded for Ubuntu desktop.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thunderbolt-tools in Ubuntu.
Matching subscriptions: Kernel Packages
https://bugs.launchpad.net/bugs/1748157

Title:
   [MIR] thunderbolt-tools

Status in thunderbolt-tools package in Ubuntu:
  Confirmed

Bug description:
  == Overview ==

  Intel Thunderbolt userspace components provides components for using
  Intel Thunderbolt controllers with security level features.
  Thunderbolt™ technology is a transformational high-speed, dual
  protocol I/O that provides unmatched performance with up to 40Gbps bi-
  directional transfer speeds. It provides flexibility and simplicity by
  supporting both data (PCIe, USB3.1) and video (DisplayPort) on a
  single cable connection that can daisy-chain up to six devices.

  [ See https://github.com/intel/thunderbolt-software-user-space ]

  == Answers to UbuntuMainInclusionRequirements ==

  = Requirements =

  1. Availability
 Package is in universe: 
https://launchpad.net/ubuntu/+source/thunderbolt-tools

  2. Rationale
 Package a device enabler for users with Thunderbolt technology

  3. Security:
 No security issues exposed so far. However, the tools have only been in 
Ubuntu since
 2017-12-09, so this currently is less than the 90 days threshold.

  4. Quality assurance:
 * Manual is provided
 * No debconf questions higher than medium
 * No major outstanding bugs. I'm also helping Intel fix issues that I'm 
finding with
   static analysis tools such as scan-build, cppcheck and CoverityScan
   Bugs outstanding:
 #883857 please backport for stretch-backports
 #882525 thunderbolt-tools: FTBFS on kFreeBSD: 
_ZN5boost6system15system_categoryEv undefined
   - I can fix this, but it makes no sense to run on kFreeBSD
 * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an 
industry standard
   and the support for the tools are in the 4.13+ kernels
 * No Test Suite shipped with the package
 * Does not rely on obsolete or demoted packages

  5. UI standards:
 * This is a CLI tool. Tool has normal CLI style short help and man pages
 * No desktop file required as it is a CLI tool.

  6. Binary Dependencies:
libboost-dev(main)
libboost-filesystem-dev (main)
libboost-program-options-dev(main)
udev(main)

  7. Standards compliance:
 lintian clean and meets the FHS + Debian Policy standards to the best of 
my knowledge

  8. Maintenance
 * Package owning team: The Ubuntu Kernel Team
 * Debian package maintained by Colin Ian King (myself from the Kernel Team)

  9. Background Information
 The user-space components implement device approval support:

 a. Easier interaction with the kernel module for approving connected 
devices.
 b. ACL for auto-approving devices white-listed by the user.

 Tools provided by this package:

  tbtacl - triggered by udev (see the udev rules in tbtacl.rules).
  It auto-approves devices that are found in ACL.

  tbtadm - user-facing CLI tool. It provides operations for device
  approval, handling the ACL and more.

  The user-space components operate in coordination with the
  upstream Thunderbolt kernel driver (found in v4.13) to provide the
  Thunderbolt functionalities. These components are NOT compatible with
  the old out-of-tree Thunderbolt kernel module.

  = Security checks =

http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability 
Database using the package as a keyword
* No CVEs found

http://secunia.com/advisories/search/: search for the package as a keyword
* No security advisories found

Ubuntu CVE Tracker
  http://people.ubuntu.com/~ubuntu-security/cve/main.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/universe.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/partner.html
  * No

  Check for security relevant binaries. If any are present, this
  re

Re: [Kernel-packages] [Bug 1745747] Re: No USB support for Dell XPS 13 9370 running Bionic 18.04

[Mario Limonciello]

A few questions:

1)It looks like you did test 4.15 final correct? This happens identically
with both 4.13 and 4.15?

2) Can you please install fwupd from proposed and start fwupd in verbose
mode and share the output?

/use/lib/fwupd/fwupd -v

3) did you try changing thunderbolt security levels after plugging in
thunderbolt device?

4) does booting with thunderbolt or usb device already plugged in affect
the results?

On Tue, Jan 30, 2018, 05:35 Joseph Borg <1745...@bugs.launchpad.net>
wrote:

> Is that something I can try to fix? (I'm a bit lost at this level of
> Kernel)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1745747
>
> Title:
>   No USB support for Dell XPS 13 9370 running Bionic 18.04
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745747

Title:
  No USB support for Dell XPS 13 9370 running Bionic 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently received an XPS 13 9370. After taking a backup for 16.04
  (in case this very thing happened), I installed the daily build of
  18.04 as it didn't really make sense for me to hold on to a distro
  that'll be replaced in a couple of months.

  I noticed there were a few Dell repositories in sources.list, but non
  of them have bionic endpoints (only xenial).

  I copied those, in case they would be useful and went to erasing the
  disk and installing 18.04. Everything seems to work fine, except the
  USB / Thunderbolt ports. Nothing I try works, whether it be USB or
  Thunderbolt 3.

  If I look in dmesg, I can see the controller is recognising something,
  but it never lands in userspace:

  [ 1807.837379] xhci_hcd :39:00.0: Host supports USB 3.1 Enhanced 
SuperSpeed
  [ 1807.837410] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
  [ 1807.837412] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [ 1807.837413] usb usb4: Product: xHCI Host Controller
  [ 1807.837414] usb usb4: Manufacturer: Linux 4.13.0-25-generic xhci-hcd
  [ 1807.837416] usb usb4: SerialNumber: :39:00.0
  [ 1807.837549] hub 4-0:1.0: USB hub found
  [ 1807.837558] hub 4-0:1.0: 2 ports detected
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-19 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180118)
  Package: linux (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-041500-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1745747] Re: No USB support for Dell XPS 13 9370 running Bionic 18.04

[Mario Limonciello]

Thanks for sharing. It looks like you're on latest BIOS and thunderbolt
controller isn't running in native mode.

Can you also share fwupdmgr get-devices output with a Thunderbolt device
plugged in?

On Tue, Jan 30, 2018, 08:05 Joseph Borg <1745...@bugs.launchpad.net>
wrote:

> Ciao Marino,
>
> Yes, it's the same with 4.13 and 4.15.
>
> I've attached the output of fwupd.
>
> I've disabled the security in BIOS.  I've looked into doing the
> /sys/bus/thunderbolt auth trick, but the device does't appear in there.
>
> I'll try the reboot with the device and let you know.
>
> Grazie!
>
> ** Attachment added: "fwupd.out"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+attachment/5045580/+files/fwupd.out
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1745747
>
> Title:
>   No USB support for Dell XPS 13 9370 running Bionic 18.04
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745747

Title:
  No USB support for Dell XPS 13 9370 running Bionic 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently received an XPS 13 9370. After taking a backup for 16.04
  (in case this very thing happened), I installed the daily build of
  18.04 as it didn't really make sense for me to hold on to a distro
  that'll be replaced in a couple of months.

  I noticed there were a few Dell repositories in sources.list, but non
  of them have bionic endpoints (only xenial).

  I copied those, in case they would be useful and went to erasing the
  disk and installing 18.04. Everything seems to work fine, except the
  USB / Thunderbolt ports. Nothing I try works, whether it be USB or
  Thunderbolt 3.

  If I look in dmesg, I can see the controller is recognising something,
  but it never lands in userspace:

  [ 1807.837379] xhci_hcd :39:00.0: Host supports USB 3.1 Enhanced 
SuperSpeed
  [ 1807.837410] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
  [ 1807.837412] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [ 1807.837413] usb usb4: Product: xHCI Host Controller
  [ 1807.837414] usb usb4: Manufacturer: Linux 4.13.0-25-generic xhci-hcd
  [ 1807.837416] usb usb4: SerialNumber: :39:00.0
  [ 1807.837549] hub 4-0:1.0: USB hub found
  [ 1807.837558] hub 4-0:1.0: 2 ports detected
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-19 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180118)
  Package: linux (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-041500-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1745747] Re: No USB support for Dell XPS 13 9370 running Bionic 18.04

[Mario Limonciello]

OK so that's an older Thunderbolt NVM.  It wouldn't hurt to upgrade to
the latest to see if it helps.

Unfortunately it's not yet on LVFS yet, but if you want to try to build it and 
flash it yourself here are the pieces you need:
http://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=3H3DP
https://github.com/hughsie/fwupd/tree/master/contrib/firmware-packager

Download the archive and those tools and follow the README.md in the
link to the tools to build yourself a CAB with the update.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745747

Title:
  No USB support for Dell XPS 13 9370 running Bionic 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently received an XPS 13 9370. After taking a backup for 16.04
  (in case this very thing happened), I installed the daily build of
  18.04 as it didn't really make sense for me to hold on to a distro
  that'll be replaced in a couple of months.

  I noticed there were a few Dell repositories in sources.list, but non
  of them have bionic endpoints (only xenial).

  I copied those, in case they would be useful and went to erasing the
  disk and installing 18.04. Everything seems to work fine, except the
  USB / Thunderbolt ports. Nothing I try works, whether it be USB or
  Thunderbolt 3.

  If I look in dmesg, I can see the controller is recognising something,
  but it never lands in userspace:

  [ 1807.837379] xhci_hcd :39:00.0: Host supports USB 3.1 Enhanced 
SuperSpeed
  [ 1807.837410] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
  [ 1807.837412] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [ 1807.837413] usb usb4: Product: xHCI Host Controller
  [ 1807.837414] usb usb4: Manufacturer: Linux 4.13.0-25-generic xhci-hcd
  [ 1807.837416] usb usb4: SerialNumber: :39:00.0
  [ 1807.837549] hub 4-0:1.0: USB hub found
  [ 1807.837558] hub 4-0:1.0: 2 ports detected
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-19 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180118)
  Package: linux (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-041500-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1745747] Re: No USB support for Dell XPS 13 9370 running Bionic 18.04

[Mario Limonciello]

Actually here you go:
https://fwupd.org/downloads/2ab30ba0769a84029af4e055270444f9391c71c8-3H3DP_NVM28.00.cab
See if that helps.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745747

Title:
  No USB support for Dell XPS 13 9370 running Bionic 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently received an XPS 13 9370. After taking a backup for 16.04
  (in case this very thing happened), I installed the daily build of
  18.04 as it didn't really make sense for me to hold on to a distro
  that'll be replaced in a couple of months.

  I noticed there were a few Dell repositories in sources.list, but non
  of them have bionic endpoints (only xenial).

  I copied those, in case they would be useful and went to erasing the
  disk and installing 18.04. Everything seems to work fine, except the
  USB / Thunderbolt ports. Nothing I try works, whether it be USB or
  Thunderbolt 3.

  If I look in dmesg, I can see the controller is recognising something,
  but it never lands in userspace:

  [ 1807.837379] xhci_hcd :39:00.0: Host supports USB 3.1 Enhanced 
SuperSpeed
  [ 1807.837410] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
  [ 1807.837412] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [ 1807.837413] usb usb4: Product: xHCI Host Controller
  [ 1807.837414] usb usb4: Manufacturer: Linux 4.13.0-25-generic xhci-hcd
  [ 1807.837416] usb usb4: SerialNumber: :39:00.0
  [ 1807.837549] hub 4-0:1.0: USB hub found
  [ 1807.837558] hub 4-0:1.0: 2 ports detected
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-19 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180118)
  Package: linux (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-041500-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1745747] Re: No USB support for Dell XPS 13 9370 running Bionic 18.04

[Mario Limonciello]

I wouldn't recommend to waste time investigating the lag mentioned in the
past few comments.

Due to the way that Thunderbolt works while enumerating in BIOS assist mode
(also known as legacy mode) I would expect a small lag like that. In native
mode the enumeration is handled by the OS ACPI hotplug subsystem.

Enumerating the Thunderbolt tree is assisted by a BIOS SMI in this
instance. The CPU goes into SMM during this time.

Native isn't supported yet by 4.15 and also the thunderbolt controller
needs special firmware for it to work in this mode that's not currently
available for the XPS 9370.

On Wed, Jan 31, 2018, 04:01 Joseph Borg <1745...@bugs.launchpad.net>
wrote:

> Hi Kai-Heng and Mario, I'll try the update when I have a moment.
>
> Yes, I get a ~1 second freeze and I plug anything or take it out.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1745747
>
> Title:
>   No USB support for Dell XPS 13 9370 running Bionic 18.04
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745747

Title:
  No USB support for Dell XPS 13 9370 running Bionic 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently received an XPS 13 9370. After taking a backup for 16.04
  (in case this very thing happened), I installed the daily build of
  18.04 as it didn't really make sense for me to hold on to a distro
  that'll be replaced in a couple of months.

  I noticed there were a few Dell repositories in sources.list, but non
  of them have bionic endpoints (only xenial).

  I copied those, in case they would be useful and went to erasing the
  disk and installing 18.04. Everything seems to work fine, except the
  USB / Thunderbolt ports. Nothing I try works, whether it be USB or
  Thunderbolt 3.

  If I look in dmesg, I can see the controller is recognising something,
  but it never lands in userspace:

  [ 1807.837379] xhci_hcd :39:00.0: Host supports USB 3.1 Enhanced 
SuperSpeed
  [ 1807.837410] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
  [ 1807.837412] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [ 1807.837413] usb usb4: Product: xHCI Host Controller
  [ 1807.837414] usb usb4: Manufacturer: Linux 4.13.0-25-generic xhci-hcd
  [ 1807.837416] usb usb4: SerialNumber: :39:00.0
  [ 1807.837549] hub 4-0:1.0: USB hub found
  [ 1807.837558] hub 4-0:1.0: 2 ports detected
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-19 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180118)
  Package: linux (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-041500-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1745747] Re: No USB support for Dell XPS 13 9370 running Bionic 18.04

[Mario Limonciello]

@Joseph,

After you upgrade NVM if you can still reproduct can you please share
more information on which USB-C (non TBT devices) and which TBT devices
you are testing with?

Also for the ones that are not TBT can you please try them in the other
USB-C ports?  As Kai Heng mentioned the XPS 9370 doesn't have every
USB-C port wired to  the TBT controller.  You should look at the
silkscreen to tell which ones are TBT.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745747

Title:
  No USB support for Dell XPS 13 9370 running Bionic 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently received an XPS 13 9370. After taking a backup for 16.04
  (in case this very thing happened), I installed the daily build of
  18.04 as it didn't really make sense for me to hold on to a distro
  that'll be replaced in a couple of months.

  I noticed there were a few Dell repositories in sources.list, but non
  of them have bionic endpoints (only xenial).

  I copied those, in case they would be useful and went to erasing the
  disk and installing 18.04. Everything seems to work fine, except the
  USB / Thunderbolt ports. Nothing I try works, whether it be USB or
  Thunderbolt 3.

  If I look in dmesg, I can see the controller is recognising something,
  but it never lands in userspace:

  [ 1807.837379] xhci_hcd :39:00.0: Host supports USB 3.1 Enhanced 
SuperSpeed
  [ 1807.837410] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
  [ 1807.837412] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [ 1807.837413] usb usb4: Product: xHCI Host Controller
  [ 1807.837414] usb usb4: Manufacturer: Linux 4.13.0-25-generic xhci-hcd
  [ 1807.837416] usb usb4: SerialNumber: :39:00.0
  [ 1807.837549] hub 4-0:1.0: USB hub found
  [ 1807.837558] hub 4-0:1.0: 2 ports detected
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-19 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180118)
  Package: linux (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-041500-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1745747] Re: No USB support for Dell XPS 13 9370 running Bionic 18.04

[Mario Limonciello]

@Joseph,

Hmm, OK.  So you may already know this but USB and Thunderbolt devices
are handled differently. I would treat these as two distinct separate
issues.

Do you have any TBT devices that are not eGPU?  It would be good to know
if the problems are specific to eGPU.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745747

Title:
  No USB support for Dell XPS 13 9370 running Bionic 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently received an XPS 13 9370. After taking a backup for 16.04
  (in case this very thing happened), I installed the daily build of
  18.04 as it didn't really make sense for me to hold on to a distro
  that'll be replaced in a couple of months.

  I noticed there were a few Dell repositories in sources.list, but non
  of them have bionic endpoints (only xenial).

  I copied those, in case they would be useful and went to erasing the
  disk and installing 18.04. Everything seems to work fine, except the
  USB / Thunderbolt ports. Nothing I try works, whether it be USB or
  Thunderbolt 3.

  If I look in dmesg, I can see the controller is recognising something,
  but it never lands in userspace:

  [ 1807.837379] xhci_hcd :39:00.0: Host supports USB 3.1 Enhanced 
SuperSpeed
  [ 1807.837410] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
  [ 1807.837412] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [ 1807.837413] usb usb4: Product: xHCI Host Controller
  [ 1807.837414] usb usb4: Manufacturer: Linux 4.13.0-25-generic xhci-hcd
  [ 1807.837416] usb usb4: SerialNumber: :39:00.0
  [ 1807.837549] hub 4-0:1.0: USB hub found
  [ 1807.837558] hub 4-0:1.0: 2 ports detected
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-19 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180118)
  Package: linux (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-041500-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1745747] Re: No USB support for Dell XPS 13 9370 running Bionic 18.04

[Mario Limonciello]

There's a lot of reports of failures when using dongles with that chip.
Some people have had success when switching to HDMI cables with better
shielding.

On Fri, Feb 2, 2018, 01:40 Kai-Heng Feng 
wrote:

> @Mario,
>
> The device I mentioned is a USB Type-C to HDMI UHD dongle, it uses a NXP
> PTN5002 inside:
>
> T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
> D:  Ver= 2.01 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
> P:  Vendor=1fc9 ProdID=5002 Rev=01.00
> S:  Manufacturer=NXP
> S:  Product=PTN5002
> S:  SerialNumber=039e5595
> C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
> I:  If#= 0 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
>
> I just tried to use this dongle under Windows 10, same result. So
> probably a hardware/firmware issue.
>
> The NXP PTN5002 works on Precision 3520's TBT port.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1745747
>
> Title:
>   No USB support for Dell XPS 13 9370 running Bionic 18.04
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745747

Title:
  No USB support for Dell XPS 13 9370 running Bionic 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently received an XPS 13 9370. After taking a backup for 16.04
  (in case this very thing happened), I installed the daily build of
  18.04 as it didn't really make sense for me to hold on to a distro
  that'll be replaced in a couple of months.

  I noticed there were a few Dell repositories in sources.list, but non
  of them have bionic endpoints (only xenial).

  I copied those, in case they would be useful and went to erasing the
  disk and installing 18.04. Everything seems to work fine, except the
  USB / Thunderbolt ports. Nothing I try works, whether it be USB or
  Thunderbolt 3.

  If I look in dmesg, I can see the controller is recognising something,
  but it never lands in userspace:

  [ 1807.837379] xhci_hcd :39:00.0: Host supports USB 3.1 Enhanced 
SuperSpeed
  [ 1807.837410] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
  [ 1807.837412] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [ 1807.837413] usb usb4: Product: xHCI Host Controller
  [ 1807.837414] usb usb4: Manufacturer: Linux 4.13.0-25-generic xhci-hcd
  [ 1807.837416] usb usb4: SerialNumber: :39:00.0
  [ 1807.837549] hub 4-0:1.0: USB hub found
  [ 1807.837558] hub 4-0:1.0: 2 ports detected
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-19 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180118)
  Package: linux (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-041500-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools

[Mario Limonciello]

Logs N/A for this type of bug.

** Changed in: linux (Ubuntu)
   Status: Incomplete => New

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1748157

Title:
   [MIR] thunderbolt-tools

Status in thunderbolt-tools package in Ubuntu:
  Confirmed

Bug description:
  == Overview ==

  Intel Thunderbolt userspace components provides components for using
  Intel Thunderbolt controllers with security level features.
  Thunderbolt™ technology is a transformational high-speed, dual
  protocol I/O that provides unmatched performance with up to 40Gbps bi-
  directional transfer speeds. It provides flexibility and simplicity by
  supporting both data (PCIe, USB3.1) and video (DisplayPort) on a
  single cable connection that can daisy-chain up to six devices.

  [ See https://github.com/intel/thunderbolt-software-user-space ]

  == Answers to UbuntuMainInclusionRequirements ==

  = Requirements =

  1. Availability
 Package is in universe: 
https://launchpad.net/ubuntu/+source/thunderbolt-tools

  2. Rationale
 Package a device enabler for users with Thunderbolt technology

  3. Security:
 No security issues exposed so far. However, the tools have only been in 
Ubuntu since
 2017-12-09, so this currently is less than the 90 days threshold.

  4. Quality assurance:
 * Manual is provided
 * No debconf questions higher than medium
 * No major outstanding bugs. I'm also helping Intel fix issues that I'm 
finding with
   static analysis tools such as scan-build, cppcheck and CoverityScan
   Bugs outstanding:
 #883857 please backport for stretch-backports
 #882525 thunderbolt-tools: FTBFS on kFreeBSD: 
_ZN5boost6system15system_categoryEv undefined
   - I can fix this, but it makes no sense to run on kFreeBSD
 * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an 
industry standard
   and the support for the tools are in the 4.13+ kernels
 * No Test Suite shipped with the package
 * Does not rely on obsolete or demoted packages

  5. UI standards:
 * This is a CLI tool. Tool has normal CLI style short help and man pages
 * No desktop file required as it is a CLI tool.

  6. Binary Dependencies:
libboost-dev(main)
libboost-filesystem-dev (main)
libboost-program-options-dev(main)
udev(main)

  7. Standards compliance:
 lintian clean and meets the FHS + Debian Policy standards to the best of 
my knowledge

  8. Maintenance
 * Package owning team: The Ubuntu Kernel Team
 * Debian package maintained by Colin Ian King (myself from the Kernel Team)

  9. Background Information
 The user-space components implement device approval support:

 a. Easier interaction with the kernel module for approving connected 
devices.
 b. ACL for auto-approving devices white-listed by the user.

 Tools provided by this package:

  tbtacl - triggered by udev (see the udev rules in tbtacl.rules).
  It auto-approves devices that are found in ACL.

  tbtadm - user-facing CLI tool. It provides operations for device
  approval, handling the ACL and more.

  The user-space components operate in coordination with the
  upstream Thunderbolt kernel driver (found in v4.13) to provide the
  Thunderbolt functionalities. These components are NOT compatible with
  the old out-of-tree Thunderbolt kernel module.

  = Security checks =

http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability 
Database using the package as a keyword
* No CVEs found

http://secunia.com/advisories/search/: search for the package as a keyword
* No security advisories found

Ubuntu CVE Tracker
  http://people.ubuntu.com/~ubuntu-security/cve/main.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/universe.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/partner.html
  * No

  Check for security relevant binaries. If any are present, this
  requires a more in-depth security review.

  Executables which have the suid or sgid bit set.
* Not applicable

  Executables in /sbin, /usr/sbin.
* None in these paths

  Packages which install daemons (/etc/init.d/*)
* No

  Packages which open privileged ports (ports < 1024).
* No

   Add-ons and plugins to security-sensitive software (filters,
   scanners, UI skins, etc)
* This does exec tbtacl from udev with new udev rules, so this
  needs security checking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad

[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools

[Mario Limonciello]

** Package changed: linux (Ubuntu) => thunderbolt-tools (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thunderbolt-tools in Ubuntu.
Matching subscriptions: Kernel Packages
https://bugs.launchpad.net/bugs/1748157

Title:
   [MIR] thunderbolt-tools

Status in thunderbolt-tools package in Ubuntu:
  Confirmed

Bug description:
  == Overview ==

  Intel Thunderbolt userspace components provides components for using
  Intel Thunderbolt controllers with security level features.
  Thunderbolt™ technology is a transformational high-speed, dual
  protocol I/O that provides unmatched performance with up to 40Gbps bi-
  directional transfer speeds. It provides flexibility and simplicity by
  supporting both data (PCIe, USB3.1) and video (DisplayPort) on a
  single cable connection that can daisy-chain up to six devices.

  [ See https://github.com/intel/thunderbolt-software-user-space ]

  == Answers to UbuntuMainInclusionRequirements ==

  = Requirements =

  1. Availability
 Package is in universe: 
https://launchpad.net/ubuntu/+source/thunderbolt-tools

  2. Rationale
 Package a device enabler for users with Thunderbolt technology

  3. Security:
 No security issues exposed so far. However, the tools have only been in 
Ubuntu since
 2017-12-09, so this currently is less than the 90 days threshold.

  4. Quality assurance:
 * Manual is provided
 * No debconf questions higher than medium
 * No major outstanding bugs. I'm also helping Intel fix issues that I'm 
finding with
   static analysis tools such as scan-build, cppcheck and CoverityScan
   Bugs outstanding:
 #883857 please backport for stretch-backports
 #882525 thunderbolt-tools: FTBFS on kFreeBSD: 
_ZN5boost6system15system_categoryEv undefined
   - I can fix this, but it makes no sense to run on kFreeBSD
 * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an 
industry standard
   and the support for the tools are in the 4.13+ kernels
 * No Test Suite shipped with the package
 * Does not rely on obsolete or demoted packages

  5. UI standards:
 * This is a CLI tool. Tool has normal CLI style short help and man pages
 * No desktop file required as it is a CLI tool.

  6. Binary Dependencies:
libboost-dev(main)
libboost-filesystem-dev (main)
libboost-program-options-dev(main)
udev(main)

  7. Standards compliance:
 lintian clean and meets the FHS + Debian Policy standards to the best of 
my knowledge

  8. Maintenance
 * Package owning team: The Ubuntu Kernel Team
 * Debian package maintained by Colin Ian King (myself from the Kernel Team)

  9. Background Information
 The user-space components implement device approval support:

 a. Easier interaction with the kernel module for approving connected 
devices.
 b. ACL for auto-approving devices white-listed by the user.

 Tools provided by this package:

  tbtacl - triggered by udev (see the udev rules in tbtacl.rules).
  It auto-approves devices that are found in ACL.

  tbtadm - user-facing CLI tool. It provides operations for device
  approval, handling the ACL and more.

  The user-space components operate in coordination with the
  upstream Thunderbolt kernel driver (found in v4.13) to provide the
  Thunderbolt functionalities. These components are NOT compatible with
  the old out-of-tree Thunderbolt kernel module.

  = Security checks =

http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability 
Database using the package as a keyword
* No CVEs found

http://secunia.com/advisories/search/: search for the package as a keyword
* No security advisories found

Ubuntu CVE Tracker
  http://people.ubuntu.com/~ubuntu-security/cve/main.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/universe.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/partner.html
  * No

  Check for security relevant binaries. If any are present, this
  requires a more in-depth security review.

  Executables which have the suid or sgid bit set.
* Not applicable

  Executables in /sbin, /usr/sbin.
* None in these paths

  Packages which install daemons (/etc/init.d/*)
* No

  Packages which open privileged ports (ports < 1024).
* No

   Add-ons and plugins to security-sensitive software (filters,
   scanners, UI skins, etc)
* This does exec tbtacl from udev with new udev rules, so this
  needs security checking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/

[Kernel-packages] [Bug 1721781] [NEW] missing firmware for i915 KBL

[Mario Limonciello]

Public bug reported:

XPS 9360 (KBL)

I was running a newer kernel on xenial userspace and noticed the
following in syslog:

i915 :00:02.0: Direct firmware load for i915/kbl_dmc_ver1_01.bin failed 
with error -2
i915 :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/downloads/firmware], disabling runtime power 
management.

Checking in /lib/firmware/i915 and comparing
https://01.org/linuxgraphics/downloads/firmware I noticed that none of
the KBL firmware is available (DMC, GuC, or HuC).

These commits are needed to backport this firmware into Xenial:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_dmc_ver1_01.bin?id=9facc31d772a3ed399760d2168d644f9de84d6db
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_huc_ver02_00_1810.bin?id=56016d2019e1335ed9739a3d31636db058d72d68
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_guc_ver9_14.bin?id=d7fe1272a38777a41ce9d1df80f58ace2d9e3d27
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_guc_ver9_14.bin?id=a22b7703f88a85180f00a1088cdbe739222f9cd5

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-firmware (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Also affects: linux-firmware (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1721781

Title:
  missing firmware for i915 KBL

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Xenial:
  New

Bug description:
  XPS 9360 (KBL)

  I was running a newer kernel on xenial userspace and noticed the
  following in syslog:

  i915 :00:02.0: Direct firmware load for i915/kbl_dmc_ver1_01.bin failed 
with error -2
  i915 :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/downloads/firmware], disabling runtime power 
management.

  Checking in /lib/firmware/i915 and comparing
  https://01.org/linuxgraphics/downloads/firmware I noticed that none of
  the KBL firmware is available (DMC, GuC, or HuC).

  These commits are needed to backport this firmware into Xenial:

  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_dmc_ver1_01.bin?id=9facc31d772a3ed399760d2168d644f9de84d6db
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_huc_ver02_00_1810.bin?id=56016d2019e1335ed9739a3d31636db058d72d68
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_guc_ver9_14.bin?id=d7fe1272a38777a41ce9d1df80f58ace2d9e3d27
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_guc_ver9_14.bin?id=a22b7703f88a85180f00a1088cdbe739222f9cd5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1721781/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1721781] Re: missing firmware for i915 KBL

[Mario Limonciello]

btw - Noticed the same error on the 4.4 kernel with i915 BPO.

[1.074319] i915_bpo :00:02.0: Direct firmware load for 
i915/kbl_dmc_ver1.bin failed with error -2
[1.074322] i915_bpo :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling 
runtime power management.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1721781

Title:
  missing firmware for i915 KBL

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Xenial:
  New

Bug description:
  XPS 9360 (KBL)

  I was running a newer kernel on xenial userspace and noticed the
  following in syslog:

  i915 :00:02.0: Direct firmware load for i915/kbl_dmc_ver1_01.bin failed 
with error -2
  i915 :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/downloads/firmware], disabling runtime power 
management.

  Checking in /lib/firmware/i915 and comparing
  https://01.org/linuxgraphics/downloads/firmware I noticed that none of
  the KBL firmware is available (DMC, GuC, or HuC).

  These commits are needed to backport this firmware into Xenial:

  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_dmc_ver1_01.bin?id=9facc31d772a3ed399760d2168d644f9de84d6db
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_huc_ver02_00_1810.bin?id=56016d2019e1335ed9739a3d31636db058d72d68
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_guc_ver9_14.bin?id=d7fe1272a38777a41ce9d1df80f58ace2d9e3d27
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_guc_ver9_14.bin?id=a22b7703f88a85180f00a1088cdbe739222f9cd5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1721781/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

[Mario Limonciello]

This is not a hardware failure.

When a proper fix is developed I'd expect it to come in the form of a
patch to XHCI driver to adjust internally how ASMedia host controller
operates.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729674

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux package in Fedora:
  Confirmed

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1744431] Re: TPM 1.2 Update Owned

[Mario Limonciello]

This particular issue is that TPM updates are being offered even if the
TPM is owned.  It's been fixed upstream already
(https://github.com/hughsie/fwupd/commit/736be7440fdee3f5339f3b1dc193f674a6191696
#diff-a60e5446a876ad45a9fd10a068b50816) and that version is available in
bionic-proposed.  It hasn't migrated due to the non-x86 architectures
being disabled
(https://twitter.com/launchpadstatus/status/954609952601116672)

For now, here are your options:
1) Go into BIOS setup and clear TPM ownership.  Then do the TPM update
2) Blacklist the TPM update in fwupd configuration file (in /etc/fwupd)
3) Install the package from -proposed.

** Package changed: linux (Ubuntu) => fwupd (Ubuntu)

** Changed in: fwupd (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1744431

Title:
  TPM 1.2 Update Owned

Status in fwupd package in Ubuntu:
  Fix Committed

Bug description:
  budgie-desktop 10.4
  ubuntu 17.10 86_64
  kernel 4.13.0-30

  My laptop is a Dell XPS 15 9550

  In software center I have 2 updates

  TPM 1.2 Update 5.81.0.0 -> 5.81.2.1
  XPS 15 9550 Precision 5510 System Update 0.1.2.19 -> 0.1.6.1

  When installing the updates it prompts me to reboot which I do.
  In the bios, it attempts to update firmware which then gives me the following 
errors in separate prompts

  TPM is owned
  Firmware is not for this machine
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dwayne 1268 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-17 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  MachineType: Dell Inc. XPS 15 9550
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-30-generic.efi.signed 
root=UUID=b88f3a78-dc71-4c8e-a182-50f19921a447 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-generic  N/A
   linux-firmware 1.170
  Tags:  bionic
  Uname: Linux 4.13.0-30-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-01-20 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1744431/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

[Mario Limonciello]

There was a problem I found a little while back with hooking up dock to
artful where gnome would crash. That was fixed recently, but I haven't seen
anything else either (both wd15 and tb16 with XPS 9350)

On Thu, Oct 19, 2017, 23:15 Kai-Heng Feng 
wrote:

> Uh, I meant "I cannot reproduce the issue".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1701499
>
> Title:
>   System often freezes or panics if I log in with Dell Dock WD15
>   connected
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701499/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1701499

Title:
  System often freezes or panics if I log in with Dell Dock WD15
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Dell Precision 5520 with Ubuntu 17.04.

  If I first start a Unity session and then connect Dell WD15 USB-C dock
  with an external diplay plugged in, the system detects it properly and
  all the things work flawlessly (ethernet, external keyboard, external
  display, external storage connected to USB on the dock). I can plug-in
  and plug-out the dock multiple times and it just works.

  However if I boot the laptop with the dock already plugged in, first I
  get to the login screen and initially all is ok. Both screens are
  activated, and I can log in using the keyboard connected to the dock.

  When I hit "Enter", both screens go blank for a while, then they turn
  back on and I can see the desktop. A second or maybe two seconds later
  things start falling apart. When I move the mouse pointer a second
  after logging, it is kinda "jumpy", the movement is not smooth. The
  move freezes for a few times. I observed this behaviour only when
  moving the wireless mouse connected to the USB of the laptop. The
  builtin touchpad works smoothly.

  If it was the only issue, this would be a very minor annoyance.
  Sometimes, after a few short mouse pointer freezes the system starts
  working smoothly and all is rock stable from that point. However quite
  often I noticed much worse things happen:

  1. The mouse pointer and everything freezes totally after a few
  seconds from displaying the desktop. It is not possible to switch to
  the console with Ctrl-Alt-F1. This happens in >50% of logins.

  2. Kernel panic.

  I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well
  as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more
  stable than 4.10.0-x) and also 4.12.rc5 which I tried once.

  Even if everything goes fine, I noticed the following errors printed
  in syslog. I'm not sure if they are related, but they look very iffy
  to me:

  Jun 30 10:46:23 p5520 kernel: [   38.391971] DMAR: DRHD: handling fault 
status reg 2
  Jun 30 10:46:23 p5520 kernel: [   38.391977] DMAR: [INTR-REMAP] Request 
device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request 
due to source-id verification failure
  Jun 30 10:46:23 p5520 kernel: [   38.472490] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.472496] usb usb4: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.472497] usb 4-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.472498] usb 4-1.2: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7510] device 
(eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
  Jun 30 10:46:23 p5520 ModemManager[1076]:   (net/eth0): released by 
modem 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7537] devices 
removed (path: 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
 iface: eth0)
  Jun 30 10:46:23 p5520 kernel: [   38.552718] xhci_hcd :0a:00.0: Host halt 
failed, -19
  Jun 30 10:46:23 p5520 kernel: [   38.552721] xhci_hcd :0a:00.0: Host not 
accessible, reset failed.
  Jun 30 10:46:23 p5520 kernel: [   38.552722] xhci_hcd :0a:00.0: USB bus 4 
deregistered
  Jun 30 10:46:23 p5520 kernel: [   38.552728] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.552731] usb usb3: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1.5: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 kernel: [   38.553322] usb 3-1.7: USB disconnect, 
device number 4
  Jun 30 10:46:23 p5520 kernel: [   38.556064] BUG: unable to handle kernel 
paging request at 002018387ad8
  Jun 30 10:46:23 p5520 kernel: [   38.556173] IP: __radix_tree_lookup+0x10/0xf0
  Jun 30 10

[Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

[Mario Limonciello]

Here's more detail, the gnome-shell fix came with this bug:
https://launchpad.net/bugs/1722811

The apparmor problem with 4.14 is described here:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278

So please do share if you're encountering issues after upgrading to that
newer version of mutter (including what version is on your system).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1701499

Title:
  System often freezes or panics if I log in with Dell Dock WD15
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Dell Precision 5520 with Ubuntu 17.04.

  If I first start a Unity session and then connect Dell WD15 USB-C dock
  with an external diplay plugged in, the system detects it properly and
  all the things work flawlessly (ethernet, external keyboard, external
  display, external storage connected to USB on the dock). I can plug-in
  and plug-out the dock multiple times and it just works.

  However if I boot the laptop with the dock already plugged in, first I
  get to the login screen and initially all is ok. Both screens are
  activated, and I can log in using the keyboard connected to the dock.

  When I hit "Enter", both screens go blank for a while, then they turn
  back on and I can see the desktop. A second or maybe two seconds later
  things start falling apart. When I move the mouse pointer a second
  after logging, it is kinda "jumpy", the movement is not smooth. The
  move freezes for a few times. I observed this behaviour only when
  moving the wireless mouse connected to the USB of the laptop. The
  builtin touchpad works smoothly.

  If it was the only issue, this would be a very minor annoyance.
  Sometimes, after a few short mouse pointer freezes the system starts
  working smoothly and all is rock stable from that point. However quite
  often I noticed much worse things happen:

  1. The mouse pointer and everything freezes totally after a few
  seconds from displaying the desktop. It is not possible to switch to
  the console with Ctrl-Alt-F1. This happens in >50% of logins.

  2. Kernel panic.

  I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well
  as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more
  stable than 4.10.0-x) and also 4.12.rc5 which I tried once.

  Even if everything goes fine, I noticed the following errors printed
  in syslog. I'm not sure if they are related, but they look very iffy
  to me:

  Jun 30 10:46:23 p5520 kernel: [   38.391971] DMAR: DRHD: handling fault 
status reg 2
  Jun 30 10:46:23 p5520 kernel: [   38.391977] DMAR: [INTR-REMAP] Request 
device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request 
due to source-id verification failure
  Jun 30 10:46:23 p5520 kernel: [   38.472490] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.472496] usb usb4: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.472497] usb 4-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.472498] usb 4-1.2: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7510] device 
(eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
  Jun 30 10:46:23 p5520 ModemManager[1076]:   (net/eth0): released by 
modem 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7537] devices 
removed (path: 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
 iface: eth0)
  Jun 30 10:46:23 p5520 kernel: [   38.552718] xhci_hcd :0a:00.0: Host halt 
failed, -19
  Jun 30 10:46:23 p5520 kernel: [   38.552721] xhci_hcd :0a:00.0: Host not 
accessible, reset failed.
  Jun 30 10:46:23 p5520 kernel: [   38.552722] xhci_hcd :0a:00.0: USB bus 4 
deregistered
  Jun 30 10:46:23 p5520 kernel: [   38.552728] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.552731] usb usb3: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1.5: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 kernel: [   38.553322] usb 3-1.7: USB disconnect, 
device number 4
  Jun 30 10:46:23 p5520 kernel: [   38.556064] BUG: unable to handle kernel 
paging request at 002018387ad8
  Jun 30 10:46:23 p5520 kernel: [   38.556173] IP: __radix_tree_lookup+0x10/0xf0
  Jun 30 10:46:23 p5520 kernel: [   38.556230] PGD 0 
  Jun 30 10:46:23 p5520 kernel: [   38.556232] 
  Jun 30 10:46:24 p5520 kernel: [   38.556280] Oops:  [#1] SMP
  Jun 30 10:46:24 p5520 kernel: [   38.556320] Modules linked in: ccm rfcomm 
cdc_ether usbnet snd_usb_audio snd_usbmidi_lib r8152 mii snd_hda_codec

[Kernel-packages] [Bug 1697395] Re: Thunderbolt devices don't work if connected during boot

[Mario Limonciello]

Those 3 patches were backported to 4.13.13.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.13.y&id=dcd2b010f17d64f19ac6a1f7cc77d85faf29196a
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.13.y&id=d055d4161c9354cd53f33c38bc9699ceeaadf1b5
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.13.y&id=61380235fe7c76ee306565c0f4dd294256e25079

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1697395

Title:
  Thunderbolt devices don't work if connected during boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I am using a Dell XP 15 9550, if my Dockingstation (Dell TB16) is
  connected during boot time, all the USB devices (like Keyboard,
  Ethernet, ...) are only working while in grub boot menu. After booting
  they stop working.

  The two 4k screens which are connected to the dock, are working
  properly in boot menu and after booting. If booting into Windows
  everything is working, only linux is affected.

  Disconnecting and reconnecting the dock solves this problem.

  I have created the bug-report directly after boot, where the USB
  devices are not working and attached "lspci-vnvn_after_reconnect.log"
  after reconnecting the dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andre_duewel   3163 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Jun 12 11:17:26 2017
  InstallationDate: Installed on 2017-04-12 (60 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=0ba04b8b-151f-4522-81a8-b6b01352ea35 ro quiet splash 
nvme_core.default_ps_max_latency_us=6000 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697395/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1697395] Re: Thunderbolt devices don't work if connected during boot

[Mario Limonciello]

*** This bug is a duplicate of bug 1717431 ***
https://bugs.launchpad.net/bugs/1717431

Looks like those made it to artful too:
https://bugs.launchpad.net/intel/+bug/1717431


** This bug has been marked a duplicate of bug 1717431
   [Bug] Thunderbolt-patches: Fixes the issue regarding the order of ACPI calls 
w.r.t. PCI enumeration

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1697395

Title:
  Thunderbolt devices don't work if connected during boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I am using a Dell XP 15 9550, if my Dockingstation (Dell TB16) is
  connected during boot time, all the USB devices (like Keyboard,
  Ethernet, ...) are only working while in grub boot menu. After booting
  they stop working.

  The two 4k screens which are connected to the dock, are working
  properly in boot menu and after booting. If booting into Windows
  everything is working, only linux is affected.

  Disconnecting and reconnecting the dock solves this problem.

  I have created the bug-report directly after boot, where the USB
  devices are not working and attached "lspci-vnvn_after_reconnect.log"
  after reconnecting the dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andre_duewel   3163 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Jun 12 11:17:26 2017
  InstallationDate: Installed on 2017-04-12 (60 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=0ba04b8b-151f-4522-81a8-b6b01352ea35 ro quiet splash 
nvme_core.default_ps_max_latency_us=6000 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697395/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1737639] Re: Touchpad stopped working in Dell XPS13

[Mario Limonciello]

That file is not shipped with standard Ubuntu. Was this an OEM shipped
machine and it came in an oem package? Or was that something you added
yourself?

You can check:
dpkg -S /etc/modprobe.d/blacklist_i2c_hid.conf

On Thu, Dec 14, 2017, 12:55 Kevin Dalley <1737...@bugs.launchpad.net>
wrote:

> And here is the  /proc/bus/input/devices
> under
> 4.13.0-16-generic
>
>
> ** Attachment added: "cat /proc/bus/input/devices under 4.13.0-16-generic"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+attachment/5022746/+files/devices-5
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1737639
>
> Title:
>   Touchpad stopped working in Dell XPS13
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1737639

Title:
  Touchpad stopped working in Dell XPS13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9343
  Recently, the touchpad stopped working. The touchpad works under the BIOS, so 
I believe that it is not a hardware issue, but a Linux kernel bug.

  The touchpad does not show up in
  cat /proc/bus/input/devices

  
  For the touchpad, the Vendor name is COMPAL and the Vendor Part Number is 
PK09000FS0L

  The problem is currently visible in 4.13.0-16-generic

  though this kernel originally worked, I believe, and 4.13.0-17 failed.

  I continued to use 16 for a while, but after the upgrade to 4.13.0-19,
  4.13.0-16 stopped working as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kevin  6040 F pulseaudio
   /dev/snd/controlC0:  kevin  6040 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 15:06:29 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=b35857db-041a-40cd-ab90-b6bd03ebad0d
  InstallationDate: Installed on 2015-05-18 (938 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (52 days ago)
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/16/2017:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1737639] Re: Touchpad stopped working in Dell XPS13

[Mario Limonciello]

So for what it's worth looking at adopting libinput would likely improve
your touchpad experience.

You should investigate if you are using that after upgrade. It's the
default with 17.10 fresh install but I don't know what would happen with
upgrade.

PS2 mode doesn't support as many features as I2C does. If you still aren't
happy with the performance in I2C mode you should be able to adjust many
options in libinput that can better improve it than switching to PS2 mode
offered.

On Thu, Dec 14, 2017, 13:35 Kevin Dalley <1737...@bugs.launchpad.net>
wrote:

> This file was a workaround, done outside of packaging. The touchpad has
> frequently been a problem over the lifetime of the laptop, through
> multiple Ubuntu releases.
>
> The problem historically was that the touchpad was flakey, and would
> often freeze, jitter, move all over the place. Many users of this laptop
> added the blacklist. I was one of those users.
>
> Here's one reference going back to Ubuntu-14.04:
>
> https://askubuntu.com/questions/593466/xps13-touchpad-issues-
> with-14-04-2
>
> Here's a more recent entrance.
>
> https://askubuntu.com/questions/134627/how-do-i-get-the-touchpad-
> settings-working-on-a-dell-xps-13-ultrabook
> 
>
> I noticed that I recreated this file on October 27, 2017, probably after
> the 17.10 upgrade.
>
> But I have been using this file for years. Hence my slowness at
> remembering the file.
>
> Perhaps something changed so that could no longer be blacklisted without
> losing the touchpad.
>
> Also, I notice that the touchscreen seems to work. I had it disabled for
> so long that I had stopped testing it.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1737639
>
> Title:
>   Touchpad stopped working in Dell XPS13
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1737639

Title:
  Touchpad stopped working in Dell XPS13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9343
  Recently, the touchpad stopped working. The touchpad works under the BIOS, so 
I believe that it is not a hardware issue, but a Linux kernel bug.

  The touchpad does not show up in
  cat /proc/bus/input/devices

  
  For the touchpad, the Vendor name is COMPAL and the Vendor Part Number is 
PK09000FS0L

  The problem is currently visible in 4.13.0-16-generic

  though this kernel originally worked, I believe, and 4.13.0-17 failed.

  I continued to use 16 for a while, but after the upgrade to 4.13.0-19,
  4.13.0-16 stopped working as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kevin  6040 F pulseaudio
   /dev/snd/controlC0:  kevin  6040 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 15:06:29 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=b35857db-041a-40cd-ab90-b6bd03ebad0d
  InstallationDate: Installed on 2015-05-18 (938 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (52 days ago)
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/16/2017:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListH

[Kernel-packages] [Bug 1737639] Re: Touchpad stopped working in Dell XPS13

[Mario Limonciello]

It looks like you don't have the associated xorg package installed with it.
https://launchpad.net/ubuntu/+source/xserver-xorg-input-libinput

You should check your Xorg log to see if libinput is active.

Given this initial issue is resolved (touchpad stopped working) I'm going to 
close this kernel task.
If there ends up still being another bug related to the performance you should 
open a separate bug relative to the libinput package.  Feel free to subscribe 
Kai Heng Feng and myself to them (although I'll be on vacation so I may not 
respond for a while).

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1737639

Title:
  Touchpad stopped working in Dell XPS13

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I have a Dell XPS 13 9343
  Recently, the touchpad stopped working. The touchpad works under the BIOS, so 
I believe that it is not a hardware issue, but a Linux kernel bug.

  The touchpad does not show up in
  cat /proc/bus/input/devices

  
  For the touchpad, the Vendor name is COMPAL and the Vendor Part Number is 
PK09000FS0L

  The problem is currently visible in 4.13.0-16-generic

  though this kernel originally worked, I believe, and 4.13.0-17 failed.

  I continued to use 16 for a while, but after the upgrade to 4.13.0-19,
  4.13.0-16 stopped working as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kevin  6040 F pulseaudio
   /dev/snd/controlC0:  kevin  6040 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 15:06:29 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=b35857db-041a-40cd-ab90-b6bd03ebad0d
  InstallationDate: Installed on 2015-05-18 (938 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (52 days ago)
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/16/2017:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1738224] Re: Suspend broken after kernel upgrade

[Mario Limonciello]

That particular commit actually breaks proper s2idle. Because of it S3
should be used instead on 9360.

It was intentionally broken because of some reported regression by one guy
with an nvme SSD of a particular vendor.

Can you please check which SSD you have? Nvme info command on it can be
helpful.

On Sat, Dec 16, 2017, 16:05 Jeffrey Bouter <1738...@bugs.launchpad.net>
wrote:

> kai-Heng, on both occasions (suspend working and broken on latest
> kernel) I had nothing connected to my USB-C port. I'll test s2idle later
> and get back to you.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1738224
>
> Title:
>   Suspend broken after kernel upgrade
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738224

Title:
  Suspend broken after kernel upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My machine (XPS 13 9360) won't go into suspend properly after
  upgrading from linux-image-4.13.0-17-generic to linux-
  image-4.13.0-19-generic.

  This affects both suspend through lid close and "systemctl suspend".
  Screen goes off, power led remains lit. Then after some time the
  screen comes back on, is stuck and lets me wait for a few before
  becoming responsive again.

  Booting back into 4.13.0-17 resolved the issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeffrey1963 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
  InstallationDate: Installed on 2017-10-18 (56 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.1
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1738224] Re: Suspend broken after kernel upgrade

[Mario Limonciello]

Did you manually set s2idle? That policy shouldn't have been picked unless
you were on 4.14.

On Sat, Dec 16, 2017, 17:55 Jeffrey Bouter <1738...@bugs.launchpad.net>
wrote:

> Kai-Heng,
>
> A cat on /sys/power/mem_sleep already shows:
>
> [s2idle] deep
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1738224
>
> Title:
>   Suspend broken after kernel upgrade
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738224

Title:
  Suspend broken after kernel upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My machine (XPS 13 9360) won't go into suspend properly after
  upgrading from linux-image-4.13.0-17-generic to linux-
  image-4.13.0-19-generic.

  This affects both suspend through lid close and "systemctl suspend".
  Screen goes off, power led remains lit. Then after some time the
  screen comes back on, is stuck and lets me wait for a few before
  becoming responsive again.

  Booting back into 4.13.0-17 resolved the issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeffrey1963 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
  InstallationDate: Installed on 2017-10-18 (56 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.1
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1738224] Re: Suspend broken after kernel upgrade

[Mario Limonciello]

Thunderbolt NVM isn't on LVFS stable but it's on testing. Either turn on
fwupd LVFS testing remote or install manually from this file:

https://fwupd.org/lvfs/device/dfd51125-338f-56ff-b721-fa3bea8e534e

On Tue, Dec 19, 2017, 02:45 Kai-Heng Feng 
wrote:

> I can't reproduce the issue on the XPS 9360 at my hand, which
> unfortunately is not the mass production one, with both BIOS 2.3.1 (the
> version you currently used) and 2.4.2.
>
> The TBT's XHCI HC failed to suspend,
> [   87.718350] xhci_hcd :39:00.0: WARN: xHC CMD_RUN timeout
> [   87.718372] suspend_common(): xhci_pci_suspend+0x0/0xd0 returns -110
> [   87.718377] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110
> [   87.718385] dpm_run_callback(): pci_pm_suspend+0x0/0x130 returns -110
> [   87.718391] PM: Device :39:00.0 failed to suspend async: error -110
>
> Also we can see that:
> 01:00.0 PCI bridge [0604]: Intel Corporation DSL6340 Thunderbolt 3 Bridge
> [Alpine Ridge 2C 2015] [8086:1576] (rev ff) (prog-if ff)
> !!! Unknown header type 7f
> Kernel driver in use: pcieport
> Kernel modules: shpchp
>
> 02:00.0 PCI bridge [0604]: Intel Corporation DSL6340 Thunderbolt 3 Bridge
> [Alpine Ridge 2C 2015] [8086:1576] (rev ff) (prog-if ff)
> !!! Unknown header type 7f
> Kernel driver in use: pcieport
> Kernel modules: shpchp
>
> 02:01.0 PCI bridge [0604]: Intel Corporation DSL6340 Thunderbolt 3 Bridge
> [Alpine Ridge 2C 2015] [8086:1576] (rev ff) (prog-if ff)
> !!! Unknown header type 7f
> Kernel driver in use: pcieport
> Kernel modules: shpchp
>
> 02:02.0 PCI bridge [0604]: Intel Corporation DSL6340 Thunderbolt 3 Bridge
> [Alpine Ridge 2C 2015] [8086:1576] (rev ff) (prog-if ff)
> !!! Unknown header type 7f
> Kernel driver in use: pcieport
> Kernel modules: shpchp
>
> 03:00.0 System peripheral [0880]: Intel Corporation DSL6340 Thunderbolt 3
> NHI [Alpine Ridge 2C 2015] [8086:1575] (rev ff) (prog-if ff)
> !!! Unknown header type 7f
> Kernel driver in use: thunderbolt
> Kernel modules: thunderbolt
>
> 39:00.0 USB controller [0c03]: Intel Corporation DSL6340 USB 3.1
> Controller [Alpine Ridge] [8086:15b5] (rev ff) (prog-if ff)
> !!! Unknown header type 7f
> Kernel driver in use: xhci_hcd
>
> All these PCI devices are not responsive.
>
> Can you attach the output `lspci` right after boot, without plugging any
> USB-C/TBT device?
>
> Also, can you upgrade your BIOS and Thunderbolt firmware? Hopefully this
> can fix the issue.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1738224
>
> Title:
>   Suspend broken after kernel upgrade
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738224

Title:
  Suspend broken after kernel upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My machine (XPS 13 9360) won't go into suspend properly after
  upgrading from linux-image-4.13.0-17-generic to linux-
  image-4.13.0-19-generic.

  This affects both suspend through lid close and "systemctl suspend".
  Screen goes off, power led remains lit. Then after some time the
  screen comes back on, is stuck and lets me wait for a few before
  becoming responsive again.

  Booting back into 4.13.0-17 resolved the issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeffrey1963 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
  InstallationDate: Installed on 2017-10-18 (56 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.1
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.1:bd

Re: [Kernel-packages] [Bug 1738224] Re: Suspend broken after kernel upgrade

[Mario Limonciello]

Information isn't available on what has changed between NVM releases from
Intel. It generally improves performance and resolves issues with the ICM
stack. Those could lead to for example the controller not going to sleep
when it should.

On Wed, Dec 20, 2017, 11:26 Jeffrey Bouter <1738...@bugs.launchpad.net>
wrote:

> Kai-Heng,
>
> As posted before, I have since upgraded to 2.4.2 - this *sometimes*
> fixes the issue, but not always. Currently, it is fixed. So I don't plan
> on rebooting my machine (just letting it suspend) until either a new
> kernel release comes out, or a firmware update comes out.
>
> Mario,
>
> What would this firmware upgrade fix? Is it advised to install testing
> firmware onto my XPS?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1738224
>
> Title:
>   Suspend broken after kernel upgrade
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738224

Title:
  Suspend broken after kernel upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My machine (XPS 13 9360) won't go into suspend properly after
  upgrading from linux-image-4.13.0-17-generic to linux-
  image-4.13.0-19-generic.

  This affects both suspend through lid close and "systemctl suspend".
  Screen goes off, power led remains lit. Then after some time the
  screen comes back on, is stuck and lets me wait for a few before
  becoming responsive again.

  Booting back into 4.13.0-17 resolved the issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeffrey1963 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
  InstallationDate: Installed on 2017-10-18 (56 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.1
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Mario Limonciello]

FWIW this bug was fixed upstream already.

https://github.com/torvalds/linux/commit/d9018976cdb6eefc62a7ba79a405f6c9661b08a7

https://bugzilla.kernel.org/show_bug.cgi?id=195951

** Bug watch added: Linux Kernel Bug Tracker #195951
   https://bugzilla.kernel.org/show_bug.cgi?id=195951

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=195951
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (20/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell XPS 13 9350 I7.

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

[Mario Limonciello]

Since you're on artful can you please use fwupdmgr to check the version
of the Thunderbolt NVM? I wonder if your thunderbolt controller is in
safe mode. If so you won't be seeing a version in fwupd. Please share
your fwupdmgr devices output.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1715146

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

[Mario Limonciello]

There is an updated NVM for the 9360. It's posted to LVFS testing remote.
You can manually download it from here.

https://fwupd.org/lvfs/device/dfd51125-338f-56ff-b721-fa3bea8e534e

Can you install that and see if if helps at all perhaps?

On Mon, Dec 25, 2017, 13:25 wdoekes <1715...@bugs.launchpad.net> wrote:

> (And indeed, no suspend, it was waking/sleeping during the entire 1.5h it
> was "suspended" just now.
> $ dmesg | grep 'PM.*Preparing system for sleep' | wc -l
> 115)
>
>
> Hi Mario, do you mean this?
>
> $ fwupdmgr get-devices
> Intel AMT (unprovisioned)
>   DeviceID: /dev/mei
>   Guid: 2800f812-b7b4-2d4b-aca8-46e0ff65814c
>   Plugin:   amt
>   Flags:internal|registered
>   Version:  11.8.50
>   VersionBootloader:11.8.50
>   Created:  2017-12-25
>
> Unifying Receiver
>   DeviceID: /sys/devices/pci:00/:00:14.0/usb1/1-1
>   Guid: 77d843f7-682c-57e8-8e29-584f5b4f52a1
>   Guid: cc4cbfa9-bf9d-540b-b92b-172ce31013c1
>   Plugin:   unifying
>   Flags:updatable|supported|registered
>   DeviceVendor: Logitech
>   DeviceVendorId:   USB:0x046D
>   Version:  RQR24.05_B0029
>   VersionBootloader:BOT03.00_B0006
>   Created:  2017-12-25
>
> XPS13 9360 Thunderbolt Controller
>   DeviceID: d203-0091-7508-22f9-f2e58a90981c
>   Guid: dfd51125-338f-56ff-b721-fa3bea8e534e
>   Plugin:   thunderbolt
>   Flags:internal|updatable|registered
>   DeviceVendor: Dell
>   DeviceVendorId:   TBT:0x00D4
>   Version:  18.5
>   Created:  2017-12-25
>
> XPS 13 9360 System Firmware
>   DeviceID: UEFI-5ffdbc0d-f340-441c-a803-8439c8c0ae10-dev0
>   Guid: 5ffdbc0d-f340-441c-a803-8439c8c0ae10
>   Plugin:   uefi
>   Flags:
> internal|updatable|require-ac|supported|registered|needs-reboot
>   Version:  0.2.4.2
>   VersionLowest:0.2.4.2
>   Created:  2017-12-25
>
> Integrated Webcam HD
>   DeviceID: usb:00:05
>   Guid: 87c78d19-a3ed-5778-9b69-8eb701529940
>   Guid: ea5dc553-c861-59a3-885c-caf80c2dea78
>   Plugin:   usb
>   Flags:registered
>   DeviceVendorId:   USB:0x0BDA
>   Version:  99.24
>   Created:  2017-12-25
>
> USB Receiver
>   DeviceID: usb:00:01
>   Guid: 77d843f7-682c-57e8-8e29-584f5b4f52a1
>   Guid: a00c69e9-62ec-56f5-bab4-177f3424793c
>   Plugin:   usb
>   Flags:registered
>   DeviceVendorId:   USB:0x046D
>   Version:  36.5
>   Created:  2017-12-25
>
> Unknown Device
>   DeviceID: ro__sys_devices_pci_00__00_02_0
>   Guid: a2721130-d6d5-51aa-a710-0323525ca469
>   Plugin:   udev
>   Flags:internal|registered
>   DeviceVendor: Intel Corporation
>   DeviceVendorId:   PCI:0x8086
>   Created:  2017-12-25
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1715146
>
> Title:
>   Not Suspending When Lid is Closed Causing Heat Issue
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1715146

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Lin

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

[Mario Limonciello]

Also don't use pm-utils. It did a few over zealous actions.
It's been removed from Ubuntu installs now but you may still have it from an 
upgrade. You should use systemctl to invoke the suspend.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1715146

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

[Mario Limonciello]

Well it's good to hear the Thunderbolt update did clear things up with
the initial issue. Just to probe a little more on the update process
though:

When you say thunderbolt enabled in setup can you be more specific which
Thunderbolt options you're referring to? That first error is confusing
to me because that means the controller enumerated but disappeared.

Regarding the need for force power, that's expected with certain fwupd
and kernel combinations if you have nothing plugged into the thunderbolt
controller. The peculiar thing however is that the device enumerated to
the extent that first error came up.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1715146

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

[Mario Limonciello]

Yeah it does go to sleep after no use with those settings activated. It's
supposed to disappear from fwupd as a result too so I expected a different
error than that. But if you went really really fast I suppose that's a
possibility.

On Tue, Dec 26, 2017, 05:55 wdoekes <1715...@bugs.launchpad.net> wrote:

> BIOS Setup: Settings -> System Configuration -> Thunderbolt(tm) Adapter
> Configuration:
>
> [x] Enable Thunderbolt(tm) Technology Support
> [ ] Enable Thunderbolt(tm) Adapter Boot Support
> [ ] Enable Thunderbolt(tm) Adapter Pre-boot Modules
>
> (x) Security level - User Authorization
>
> 
>
> I have/had no devices attached to the Thunderbolt/USB-C socket.
>
> But like I said, I ran the command quickly after reboot. Perhaps it
> enumerated right after boot but went away after a while of disuse?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1715146
>
> Title:
>   Not Suspending When Lid is Closed Causing Heat Issue
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1715146

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1698468] Re: fwupd taking 100% CPU

[Mario Limonciello]

Closing as reported fixed by user. If you can reproduce it again please
re-open.

** No longer affects: linux (Ubuntu)

** Changed in: fwupd (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1698468

Title:
  fwupd taking 100% CPU

Status in fwupd package in Ubuntu:
  Invalid

Bug description:
  After I boot into Ubuntu, top shows me a fwupd process taking 100%
  CPU. The log file /var/log/syslog has several highlighted messages
  like

  Jun 13 18:11:23 opal gnome-session[1487]: (gnome-software:1660): Gs-
  WARNING **:  failed to call gs_plugin_add_updates_historical on fwupd:
  failed to start fwupd: Error calling StartServiceByName for
  org.freedesktop.fwupd:
  GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate
  service 'org.freedesktop.fwupd': timed out

  Jun 13 18:11:26 opal gnome-session[1487]: (gnome-software:1660): Gs-
  WARNING **:  failed to call gs_plugin_refine on appstream: Error
  opening file: Permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  greg   1620 F pulseaudio
   /dev/snd/controlC1:  greg   1620 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun 16 19:00:37 2017
  HibernationDevice: RESUME=UUID=c05e0556-350a-4c17-8558-c475f250ccbf
  InstallationDate: Installed on 2016-04-28 (414 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA Satellite S50-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=9200f944-2d22-4f9b-8c44-e1498370470d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd05/05/2014:svnTOSHIBA:pnSatelliteS50-B:pvrPSPQ6C-020001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S50-B
  dmi.product.version: PSPQ6C-020001
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1698468/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode

[Mario Limonciello]

> So, does the touchpad use a firmware, and, if yes, how can the firmware 
> version be queried?
All touchpads have firmware, this one is no different.  You can read the HID 
descriptor as described in the HID over I2C protocol specification.  As 
described in the specification the firmware version is encoded in byte offset 
24.

For this particular issue, this information is not useful however
because the firmware for the XPS 9360 touchpad is unchanged since it's
been on the market.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1651635

Title:
  XPS 13 9360 trackpad locks into scroll mode

Status in Dell Sputnik:
  Confirmed
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  I'm running Linux on a Dell XPS 13 (9360) laptop.

  I find that upwards of 10 times per day, my trackpad gets stuck in
  "scrolling" mode. Moving the trackpad won't move the X windows
  pointer, but will send scrolling events to the foreground window.

  When the trackpad is locked in this mode, the touchscreen will still
  let me move the mouse cursor, as will an external mouse.

  On Ubuntu 16.04 freshly restored from the Dell recovery image, I find
  that it's often difficult to get the trackpad to recover.

  I do find that the issue happens less frequently on Dell's build of
  Ubuntu 16.04 than on other linux distributions and versions, but it
  still happens enough to significantly impact my ability to do
  productive work.

  The issue does not occur when running Windows 10 on the same device.

  I suspect that the issue may be related to palm detection or
  misdetecting the user's palm as a gesture to enable scrolling mode,
  but have no proof for this.

  It seems that I'm often able to reproduce the issue by brushing the
  trackpad with my right palm.

  On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx
  4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64
  x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I
  am able to get the trackpad to recover, simply by clicking the
  trackpad:

  /usr/share/X11/xorg.conf.d/99-libinput.conf:

  Section "InputClass"
  Identifier "libinput touchpad catchall"
  Driver "libinput"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Option "Tapping" "True"
  Option "DisableWhileTyping" "True"
  Option "NaturalScrolling" "False"
  Option "AccelProfile" "adaptive"
  Option "AccelSpeed" "0.05"
  Option "MiddleEmulation" "True"
  Option "ScrollMethod" "twofinger"
  # Option "ClickMethod" "clickfinger"
  Option "ClickMethod" "buttonareas"
  EndSection

  
  In my experience, the problem manifests using both the Xorg synaptics driver 
and the Xorg libinput driver.

  root@szx:/etc/modprobe.d# xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech M570   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ DLL075B:01 06CB:76AF Touchpad   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=14   [slave  
keyboard (3)]
  ↳ Intel HID eventsid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]
  root@szx:/etc/modprobe.d#

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode

[Mario Limonciello]

FYI for those who are not subscribed to the issue filed to the kernel bugzilla:
Benjamin T. suspects this may be a userspace issue, not a kernel issue.  

When someone reproduces this again please do the following:
1) # sudo rmmod i2c-hid
2) # sudo modprobe i2c-hid debug=1
3) Capture dmesg output at this time with the issue reproduces

Please upload that dmesg data to the kernel bugzilla
(https://bugzilla.kernel.org/show_bug.cgi?id=197683).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1651635

Title:
  XPS 13 9360 trackpad locks into scroll mode

Status in Dell Sputnik:
  Confirmed
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  I'm running Linux on a Dell XPS 13 (9360) laptop.

  I find that upwards of 10 times per day, my trackpad gets stuck in
  "scrolling" mode. Moving the trackpad won't move the X windows
  pointer, but will send scrolling events to the foreground window.

  When the trackpad is locked in this mode, the touchscreen will still
  let me move the mouse cursor, as will an external mouse.

  On Ubuntu 16.04 freshly restored from the Dell recovery image, I find
  that it's often difficult to get the trackpad to recover.

  I do find that the issue happens less frequently on Dell's build of
  Ubuntu 16.04 than on other linux distributions and versions, but it
  still happens enough to significantly impact my ability to do
  productive work.

  The issue does not occur when running Windows 10 on the same device.

  I suspect that the issue may be related to palm detection or
  misdetecting the user's palm as a gesture to enable scrolling mode,
  but have no proof for this.

  It seems that I'm often able to reproduce the issue by brushing the
  trackpad with my right palm.

  On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx
  4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64
  x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I
  am able to get the trackpad to recover, simply by clicking the
  trackpad:

  /usr/share/X11/xorg.conf.d/99-libinput.conf:

  Section "InputClass"
  Identifier "libinput touchpad catchall"
  Driver "libinput"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Option "Tapping" "True"
  Option "DisableWhileTyping" "True"
  Option "NaturalScrolling" "False"
  Option "AccelProfile" "adaptive"
  Option "AccelSpeed" "0.05"
  Option "MiddleEmulation" "True"
  Option "ScrollMethod" "twofinger"
  # Option "ClickMethod" "clickfinger"
  Option "ClickMethod" "buttonareas"
  EndSection

  
  In my experience, the problem manifests using both the Xorg synaptics driver 
and the Xorg libinput driver.

  root@szx:/etc/modprobe.d# xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech M570   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ DLL075B:01 06CB:76AF Touchpad   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=14   [slave  
keyboard (3)]
  ↳ Intel HID eventsid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]
  root@szx:/etc/modprobe.d#

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Mario Limonciello]

This is an issue with the host controller. The vendor (ASMedia) has submitted a 
patch here that fixes the issue:
http://www.spinics.net/lists/linux-usb/msg157958.html

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1667750

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  New

Bug description:
  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx timeout
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:09 ubuntu kernel: usb 4-1.2: reset SuperSpeed USB device number 
3 using xhci_hcd

  I can't seem to make this bug appear with any other type of USB
  traffic. I've reported it to the realtek kernel dev t

[Kernel-packages] [Bug 1663975] Re: XHCI errors causes dock USB and network adapter dropouts

[Mario Limonciello]

*** This bug is a duplicate of bug 1667750 ***
https://bugs.launchpad.net/bugs/1667750

This is an issue with the host controller.  The vendor (ASMedia) has submitted 
a patch here that fixes the issue:
http://www.spinics.net/lists/linux-usb/msg157958.html

** This bug has been marked a duplicate of bug 1667750
   xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 
comp_code 13

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1663975

Title:
  XHCI errors causes dock USB and network adapter dropouts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Machine: Dell XPS 15 (9560) - released 2017 January
  Install: disk completely erased
   Ubuntu 16.04.1 installed over wireless with:
 - download updates while installing ubuntu
 - install third-party hardware
 - full disk crypto+luks
   Note 1: Installation process did not realize there exists a GTX 1050
   so we are solely using Intel integrated graphics.
   Note 2: Installation done not on Dell TB16 Dock to isolate wireless
   problems alone first.
  First Boot: update/upgrade/dist-upgrade'd after first boot and rebooted

  


  After testing wireless problems and being able to reproduce them,
  machine was rebooted to the login screen, and then plugged into a Dell
  TB16 dock.

  1. Turn down wireless networking.
  2. Turn up wired networking.
  3. Browse things until this happens, after which the wired interface no 
longer works and can sometimes be successfully `down/up`ed but at other times 
locks up and requires a reboot:

  [  598.238303] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.238307] xhci_hcd :0e:00.0: Looking for event-dma 000855403010 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.238634] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.238639] xhci_hcd :0e:00.0: Looking for event-dma 000855403020 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.239248] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.239253] xhci_hcd :0e:00.0: Looking for event-dma 000855403030 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.239571] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.239576] xhci_hcd :0e:00.0: Looking for event-dma 000855403040 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.239792] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.239794] xhci_hcd :0e:00.0: Looking for event-dma 000855403050 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.240186] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.240191] xhci_hcd :0e:00.0: Looking for event-dma 000855403060 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.240326] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.240328] xhci_hcd :0e:00.0: Looking for event-dma 000855403070 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.240698] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.240703] xhci_hcd :0e:00.0: Looking for event-dma 000855403080 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  605.601884] [ cut here ]
  [  605.601890] WARNING: CPU: 1 PID: 0 at 
/build/linux-W6HB68/linux-4.4.0/net/sched/sch_generic.c:306 
dev_watchdog+0x237/0x240()
  [  605.601892] NETDEV WATCHDOG: enxd481d70e6a39 (r8152): transmit queue 0 
timed out
  [  605.601892] Modules linked in: hid_logitech_hidpp snd_usb_audio 
snd_usbmidi_lib hid_generic hid_logitech_dj cdc_ether usbnet r8152 mii ctr ccm 
arc4 rfcomm bnep nls_iso8859_1 i2c_designware_platform i2c_designware_core 
dell_wmi dcdbas ath10k_pci ath10k_core ath snd_hda_codec_hdmi mac80211 dell_led 
snd_hda_codec_realtek snd_hda_codec_generic cfg80211 rtsx_pci_ms memstick 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm x86_pkg_t