from:"Mika Westerberg"

[Kernel-packages] [Bug 1878602] Re: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail

2020-06-09 Thread Mika Westerberg

I don't know much about xHCI so Mathias can comment on that. I do
remember seeing messages like:

  usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

in the past but not sure if it is only with ICL. It is also weird that
the TCSS xHCI is doing anything if you plug TBT 3 device since USB is
not tunneled. Might be something related to Type-C or PD.

-- 
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/1878602

Title:
  When TBT dock is plugged into ICL TBT xHCI, port without device is in
  CAS state, causes many warm reset fail

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since we can't use bugzilla for USB bugs, let's use Launchpad so we
  can attach dmesg :)

  System: XPS 9300 ICL
  Dock: Dell WD19TB Thunderbolt dock
  Linux: 5.7-rc5

  Right after the dock is plugged,
  [  127.205823] xhci_hcd :00:0d.0: Get port status 2-1 read: 0x10202a0, 
return 0x10341
  [  127.205832] usb usb2-port1: status 0341 change 0001

  CAS is flagged so warm-reset ensues:
  [  127.313467] usb usb2-port1: do warm reset

  However, it seems nothing is connected to usb2-port1, causes many warm-reset 
fail, hence this error message:
  [  132.158968] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

  This issue doesn't happen on CML system with AR/TR TBT controller.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878602/+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 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen

2019-04-24 Thread Mika Westerberg

BTW, did you enable any Linux specific configuration in the BIOS? For
example to enable S3 (many systems I've seen default to s2idle
nowadays).

-- 
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/1825395

Title:
  thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga
  2nd gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt
  docking station.  Initial connection to the dock works great, but
  after a few plug/unplug and suspend/resume cycles, the system gets in
  a state where a reboot is needed to make the dock work.  The
  displayport connection still works so my external monitor gets the
  right display, but the thunderbolt / PCIe connection does not and so
  the USB and network ports in the dock aren't usable.  I assume it is
  connected to the kernel messages like

  [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630
  [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock

  [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400
  [37270.096820] pci :09:00.0: enabling Extended Tags
  [37270.096975] pci :09:00.0: supports D1 D2
  [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited 
by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link)
  [37270.097187] pcieport :07:01.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400
  [37270.108705] pci :0a:00.0: enabling Extended Tags
  [37270.108865] pci :0a:00.0: supports D1 D2
  [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.109066] pcieport :07:02.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330
  [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit]
  [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit]
  [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit]
  [37270.109499] pci :0b:00.0: supports D1
  [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold
  [37270.109686] pcieport :07:04.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109724] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109738] pci :09:00.0: devices behind bridge are unusable because 
[bus 0a] cannot be assigned for them
  [37270.109766] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 
0b
  [37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under 
[bus 07-0b] (conflicts with (null) [bus 07-0b])
  [37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70]
  [37270.109843] pcieport :07:04.0:   bridge window [mem 
0xd400-0xe9ff]
  [37270.109848] pcieport :07:04.0:   bridge window [mem 
0x9000-0xb9ff 64bit pref]
  [37270.109849] pcieport :07:04.0: devices behind bridge are unusable 
because [bus 3d-70] cannot be assigned for them

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roland 1690 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 09:40:22 2019
  InstallationDate: Installed on 2019-03-29 (20 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20JGS01000
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET45W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JGS01000
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENO

[Kernel-packages] [Bug 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen

2019-04-23 Thread Mika Westerberg

Thanks for the logs. It seems like the BIOS does not handle S3 exit
properly and leaves the Thunderbolt host router unconfigured. I wonder
if there is a BIOS upgrade for this system and have you tried 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/1825395

Title:
  thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga
  2nd gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt
  docking station.  Initial connection to the dock works great, but
  after a few plug/unplug and suspend/resume cycles, the system gets in
  a state where a reboot is needed to make the dock work.  The
  displayport connection still works so my external monitor gets the
  right display, but the thunderbolt / PCIe connection does not and so
  the USB and network ports in the dock aren't usable.  I assume it is
  connected to the kernel messages like

  [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630
  [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock

  [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400
  [37270.096820] pci :09:00.0: enabling Extended Tags
  [37270.096975] pci :09:00.0: supports D1 D2
  [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited 
by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link)
  [37270.097187] pcieport :07:01.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400
  [37270.108705] pci :0a:00.0: enabling Extended Tags
  [37270.108865] pci :0a:00.0: supports D1 D2
  [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.109066] pcieport :07:02.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330
  [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit]
  [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit]
  [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit]
  [37270.109499] pci :0b:00.0: supports D1
  [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold
  [37270.109686] pcieport :07:04.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109724] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109738] pci :09:00.0: devices behind bridge are unusable because 
[bus 0a] cannot be assigned for them
  [37270.109766] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 
0b
  [37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under 
[bus 07-0b] (conflicts with (null) [bus 07-0b])
  [37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70]
  [37270.109843] pcieport :07:04.0:   bridge window [mem 
0xd400-0xe9ff]
  [37270.109848] pcieport :07:04.0:   bridge window [mem 
0x9000-0xb9ff 64bit pref]
  [37270.109849] pcieport :07:04.0: devices behind bridge are unusable 
because [bus 3d-70] cannot be assigned for them

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roland 1690 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 09:40:22 2019
  InstallationDate: Installed on 2019-03-29 (20 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20JGS01000
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET45W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JGS01000
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor:

[Kernel-packages] [Bug 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen

2019-04-22 Thread Mika Westerberg

Can you also attach full dmesg of the boot so that we can see the
initial PCI configuration? Now all the dmesgs are missing that
information.

When it initially works, do you boot with the dock connected or not?

-- 
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/1825395

Title:
  thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga
  2nd gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt
  docking station.  Initial connection to the dock works great, but
  after a few plug/unplug and suspend/resume cycles, the system gets in
  a state where a reboot is needed to make the dock work.  The
  displayport connection still works so my external monitor gets the
  right display, but the thunderbolt / PCIe connection does not and so
  the USB and network ports in the dock aren't usable.  I assume it is
  connected to the kernel messages like

  [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630
  [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock

  [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400
  [37270.096820] pci :09:00.0: enabling Extended Tags
  [37270.096975] pci :09:00.0: supports D1 D2
  [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited 
by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link)
  [37270.097187] pcieport :07:01.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400
  [37270.108705] pci :0a:00.0: enabling Extended Tags
  [37270.108865] pci :0a:00.0: supports D1 D2
  [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.109066] pcieport :07:02.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330
  [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit]
  [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit]
  [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit]
  [37270.109499] pci :0b:00.0: supports D1
  [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold
  [37270.109686] pcieport :07:04.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109724] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109738] pci :09:00.0: devices behind bridge are unusable because 
[bus 0a] cannot be assigned for them
  [37270.109766] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 
0b
  [37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under 
[bus 07-0b] (conflicts with (null) [bus 07-0b])
  [37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70]
  [37270.109843] pcieport :07:04.0:   bridge window [mem 
0xd400-0xe9ff]
  [37270.109848] pcieport :07:04.0:   bridge window [mem 
0x9000-0xb9ff 64bit pref]
  [37270.109849] pcieport :07:04.0: devices behind bridge are unusable 
because [bus 3d-70] cannot be assigned for them

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roland 1690 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 09:40:22 2019
  InstallationDate: Installed on 2019-03-29 (20 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20JGS01000
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET45W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JGS01000
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.ven

[Kernel-packages] [Bug 1696325] Re: USB, display and ethernet ports in HP Thunderbolt dock don't work

2019-03-11 Thread Mika Westerberg

On "legacy enumeration" systems, such as this one the BIOS SMI handler
enumerates the PCI bridges before handing off to the OS. The bridges
here are the TBT host router bridges so no need for any authorization.

-- 
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/1696325

Title:
  USB, display and ethernet ports in HP Thunderbolt dock don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have laptop HP ZBook G3 Studio with Thunderbolt dock P5Q58AA.
  Installed OS is Ubuntu 16.04.2 LTS

  When I connect dock into laptop only power works and laptop can be
  shutdown by pressing power button in dock. USB ports, display ports,
  ethernet port and audio plug are not working.

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  $ apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
Installed: 4.8.0.54.25
Candidate: 4.8.0.54.25
Version table:
   *** 4.8.0.54.25 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  --- 
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  markus 3304 F pulseaudio
   /dev/snd/controlC0:  markus 3304 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-07 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 
1576)
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G3
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed 
root=UUID=2b78b572-05a1-4c01-b97d-9c1fea406faf ro quiet splash nomodeset 
pnpacpi=off vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-54-generic N/A
   linux-backports-modules-4.8.0-54-generic  N/A
   linux-firmware1.157.10
  Tags:  xenial
  Uname: Linux 4.8.0-54-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: 11/02/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.15
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.67
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.15:bd11/02/2016:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.67:cvnHP:ct10:cvr:
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696325/+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 1696325] Re: USB, display and ethernet ports in HP Thunderbolt dock don't work

2019-03-07 Thread Mika Westerberg

Hi, the BIOS is expected to configure the PCI bridges leading to the TBT
controller but it does not seem to do that:

[3.725792] pci :06:00.0: bridge configuration invalid ([bus 00-00]), 
reconfiguring
[3.725799] pci :06:01.0: bridge configuration invalid ([bus 00-00]), 
reconfiguring
[3.725807] pci :06:02.0: bridge configuration invalid ([bus 00-00]), 
reconfiguring
[3.725814] pci :06:04.0: bridge configuration invalid ([bus 00-00]), 
reconfiguring

to me this looks like a BIOS issue.

-- 
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/1696325

Title:
  USB, display and ethernet ports in HP Thunderbolt dock don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have laptop HP ZBook G3 Studio with Thunderbolt dock P5Q58AA.
  Installed OS is Ubuntu 16.04.2 LTS

  When I connect dock into laptop only power works and laptop can be
  shutdown by pressing power button in dock. USB ports, display ports,
  ethernet port and audio plug are not working.

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  $ apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
Installed: 4.8.0.54.25
Candidate: 4.8.0.54.25
Version table:
   *** 4.8.0.54.25 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  --- 
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  markus 3304 F pulseaudio
   /dev/snd/controlC0:  markus 3304 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-07 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 
1576)
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G3
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed 
root=UUID=2b78b572-05a1-4c01-b97d-9c1fea406faf ro quiet splash nomodeset 
pnpacpi=off vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-54-generic N/A
   linux-backports-modules-4.8.0-54-generic  N/A
   linux-firmware1.157.10
  Tags:  xenial
  Uname: Linux 4.8.0-54-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: 11/02/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.15
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.67
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.15:bd11/02/2016:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.67:cvnHP:ct10:cvr:
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696325/+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: corrupted BIOS due to Intel SPI bug in kernel

2018-01-11 Thread Mika Westerberg

#528

Keep in mind that there are two *separate* issues:

1. Bug off-by-one bug in intel-spi driver that causes CMP bit to accidentally
set to 1. This results BIOS
being read-only. The bug was fixed by 9d63f17661e2 ("spi-nor: intel-spi: Fix
broken software sequencing
codes") in september.

2. Some Lenovo Thinkpad Yoga BIOSes reset to default settings if their BCR
register is touched. This BCR
handling is in a different driver (drivers/mfd/lpc_ich.c). This issue has
been fixed by commit
d9018976cdb6 ("mfd: lpc_ich: Do not touch SPI-NOR write protection bit on
Haswell/Broadwell") in july.

So in order to have a kernel that is free from both issues, you need to
disable the intel-spi driver (for reasons being that it is not supposed
to be enabled for normal users anyway) and then cherry-pick commit
d9018976cdb6 to make sure the other issue does not happen.

--
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:
corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
Unknown
Status in linux package in Ubuntu:
Fix Released
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

Bug description:
An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
drivers results in a serial flash that is read only in Intel Broadwell
and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

1. Boot into Ubuntu
2. Download
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
3. Install the downloaded package:
$ sudo dpkg -i
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
4. Make sure the kernel is installed without any error. Once installed,
reboot.
5. At grub, choose the newly installed kernel. You can choose the "recovery"
mode.
6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
7. In case your BIOS is not recovered, reboot to the new kernel, then reboot
*once again* to the new kernel, do not enter BIOS settings before the reboot.
After the second reboot, check BIOS.
8. If your BIOS issue remains, download another kernel from
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
and use dpkg to install it, then repeat steps 4 to 6.

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

Lenovo B40-70
Lenovo B50-70
Lenovo B50-80
Lenovo Flex-3
Lenovo Flex-10
Lenovo G40-30
Lenovo G50-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 Yoga 3 11"
Lenovo Z50-70
Lenovo Z51-70
Lenovo ideapad 100-15IBY

Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
Acer TravelMate B113
Acer Swift SF314-52 (Fixed by 4.14.9)
Toshiba Satellite S55T-B5233
Toshiba Satellite L50-B-1R7
Toshiba Satellite S50-B-13G
Dell Inspiron 15-3531
Mediacom Smartbook 14 Ultra M-SB14UC
Acer Aspire E3-111-C0UM
HP 14-r012la

---

Affected serial flash devices by manufacturer part number, JEDEC ID
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
/* ESMT */
f25l32pa, 0x8c2016
f25l32qa, 0x8c4116
f25l64qa, 0x8c4117
/* GigaDevice */
gd25q16, 0xc84015
gd25q32, 0xc84016
gd25lq32, 0xc86016
gd25q64, 0xc84017
gd25lq64c, 0xc86017
gd25q128, 0xc84018
gd25q256, 0xc84019
/* Winbond */
w25q16dw, 0xef6015
w25q32dw, 0xef6016
w25q64dw, 0xef6017
w25q128fw, 0xef6018

---

Original Description:

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.

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-11 Thread Mika Westerberg

#520, #522

Actually it matters if commit d9018976cdb6 is missing with this
particular BIOS/system because every time you boot the system, the BIOS
resets to default when it finds BCR register is changed. This is
different issue than the CMP=1 issue most of the users have reported.
This one also is not permanent so everything is fine as long as you
don't touch that BCR register. In this case you either need to always
boot to a kernel where that fix (d9018976cdb6) is included or blacklist
lpc_ich.ko. Ubuntu v4.14.x kernels have that fix included so you might
want to take one of them or build your own.

--
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:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

Original Description:

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!!

To manage notifications about

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-10 Thread Mika Westerberg

#518

Hmm, you already compiled and booted the v4.15-rc7 kernel using my
instructions, right? It should have that fix so booting that kernel
should keep your BIOS working. You can remove the custom patch by
running command "git reset --hard HEAD^". Then you can rebuild and
install it.

--
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:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

Original Description:

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!!

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 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-10 Thread Mika Westerberg

Actually I think I know what is going on. I think the "unpatched" kernel
might miss commit d9018976cdb6 ("mfd: lpc_ich: Do not touch SPI-NOR
write protection bit on Haswell/Broadwell") and in that case the BIOS
resets to defaults each 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/1734147

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

Original Description:

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!!

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-10 Thread Mika Westerberg

#514

No, this is not the same issue at all. The original "buggy" off-by-one
write never took place because the flash chip does not have that
SPI_NOR_HAS_LOCK bit set in the first place (and it was not there in
v4.13 either). So this is something else.

Christian, do you have Windows there? If yes, can you boot to Windows
several times and in-between check if the BIOS can save settings or not
(don't boot to Linux at all during that time).

--
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:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

Original Description:

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!!

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-10 Thread Mika Westerberg

#512

But for the serial flash chip Christian has, the original kernel does
nothing as well (except read the JEDEC ID) so this issue cannot happen.

--
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:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

Original Description:

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!!

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-10 Thread Mika Westerberg

#510

That's really weird because in your system both patched and unpatched
kernels are doing exactly the same thing (read JEDEC ID, nothing more).

--
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:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

Original Description:

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!!

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-10 Thread Mika Westerberg

#506

Christian, I think you got the patch properly applied but based on the
output your serial flash is "s25fl064k". Looking at the table in
drivers/mtd/spi-nor/spi-nor.c:

{ "s25fl064k", INFO(0xef4017, 0, 64 * 1024, 128, SECT_4K) }

So this flash chip does not have SPI_NOR_HAS_LOCK and thus should not suffer
from
this issue at all - no status register write is ever done to that chip.

Are you sure your BIOS is 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/1734147

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

Original Description:

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!!

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.la

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-08 Thread Mika Westerberg

This is what I typically do when I compile a custom kernel on a new
machine. You need development tools like git, gcc, gmake etc. but I
guess many distros have most of that stuff already installed. I did not
try these so there might be typos and something could be missing.

These steps should help to recover a system where there is some Linux
distro (not necessarily Ubuntu).

1. Get the latest kernel tree

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux

2. Checkout the v4.15-rc7 branch

$ git checkout -b spi-nor-recover v4.15-rc7

3. Save and apply the patch from https://goo.gl/xUKJFR (this is the
same patch that is linked in the bug description)

$ git am 0001-Clear-both-SR-and-CR-explicitly-and-also-add-debug-m.patch

4. Configure the kernel so that it takes only those modules that you
have currently loaded

$ make localmodconfig

5. You may need to enable MTD subsystem, SPI-NOR and the intel-spi
driver so run

$ make nconfig

Then select following from the config

Device Drivers --->
<*> Memory Technology Device (MTD) support --->
SPI-NOR device support --->
Intel PCH/PCU SPI flash platform driver

Then press F9 and to save .config and exit nconfig.

6. Build the kernel image and modules

$ make -j8

7. Once it is properly built without any errors you can install it
along with the modules

$ sudo make modules_install
$ sudo make install

Once the custom kernel is installed, you can reboot to this new kernel
and it should clear the CMP bit from the serial flash status register.
It logs something like below to your dmesg:

[ 19.724288] intel-spi intel-spi: wrote SSFSTS_CTL=0x0045020c
[ 19.724301] intel-spi intel-spi: wrote FDATA(0)=00 00
[ 19.724304] intel-spi intel-spi: wrote SSFSTS_CTL=0x0041360c
[ 19.736538] intel-spi intel-spi: wrote SSFSTS_CTL=0x0040520c
[ 19.736542] intel-spi intel-spi: Both SR/CR cleared

Then when you reboot, the BIOS should be able to save settings again and
you can boot back to your distro kernel.

After this you can remove the custom kernel from /boot and modules from
/lib/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/1734147

Title:
corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
Unknown
Status in linux package in Ubuntu:
Fix Committed
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

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-08 Thread Mika Westerberg

#493

You can build your own kernel so that you first apply the patch in the
bug description. Then boot to that custom kernel which should clear the
CMP bit from the serial flash and your BIOS should be functional again.
Let me know if you want instructions how to patch and build a custom
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/1734147

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

Original Description:

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!!

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-05 Thread Mika Westerberg

#474

If you have status register 2 bit 6 set. e.g it reads 0x40 or something
like that, you can just clear that bit and the chip becomes read/write.

For more information about the status register you can find if you find
"w25q64dw" datasheet (or whatever the serial flash chip you have there).
Those explain all the details (typically there's a chapter "Status
Registers" or similar). I've used this link:

http://svod.od.ua/files/W25Q64DW.pdf

Page 15 shows the both status registers.

--
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:
corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
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

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

Original Description:

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!!

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] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-05 Thread Mika Westerberg

#469

I mean you can clear that one status register bit (CMP) using dediprog
(or any other tool, or software as we do in step 8. fix) and your old
serial flash works just fine.

--
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:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

Original Description:

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!!

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-05 Thread Mika Westerberg

#467

The BIOS and the chip are fine, there is only that one bit (CMP, bit 6)
set in the second status register that makes the whole chip read-only.
You can also use some external tools, like dediprog to clear the CMP bit
and the BIOS should work again. The fix in step 8. does the same in
software.

--
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:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

Original Description:

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!!

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2018-01-03 Thread Mika Westerberg

This particular bug cannot affect Dell XPS 13 9350 as it is based on
Skylake and the intel-spi driver does not even support it.

However, in order to boot Linux I think you need at least to switch the
SATA controller to AHCI mode as described in:

https://wiki.archlinux.org/index.php/Dell_XPS_13_(9350)

--
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

Bug description:
Description: An update to linux kernel on Ubuntu 17.10 that enabled
the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
Settings being not stored, USB Boot impossible and EFI entries read-
only.

Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

---

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.

---

Affected Machines:

Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
Acer TravelMate B113
Acer Swift SF314-52 (Fixed by 4.14.9)
Toshiba Satellite S55T-B5233
Toshiba Satellite L50-B-1R7
Toshiba Satellite S50-B-13G
Dell Inspiron 15-3531 (not fixed by 4.14.9)
Mediacom Smartbook 14 Ultra M-SB14UC
Acer Aspire E3-111-C0UM
HP 14-r012la

---

Original Description:

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!!

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2018-01-03 Thread Mika Westerberg

Sorry about the delay but we wanted to make sure the proposed fix can
recover the two test systems we have reliably before asking others to
try it.

I've attached a patch to this bug that should fix the still affected
systems. It applies on top of v4.15-rc6 and I'll be sending it upstream
as well. Canonical already created a kernel package including the fix
and it can be installed from the following link:

http://people.canonical.com/~ypwong/lp1734147/linux-
image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb

The reason why v4.14.9 which includes 9d63f17661e2 ("spi-nor: intel-spi:
Fix broken software sequencing codes") recovers many systems but not all
is because:

  - These systems have CMP=1 in the other status register (SR2) making
the flash read-only (this is the symptom).

  - Linux SPI-NOR core clears status register properly for flash chips
that have SPI_NOR_HAS_LOCK set.

  - Serial flashes automatically clear CMP and few other bits if 0 is
written to the first status register using WRSR command.

  - In order to WRSR take effect the serial flash need to be write
enabled (WREN must have been issued before WRSR at some point).

  - The systems that recovered the WREN was in effect (probably issued
by the BIOS before handing off to the OS) so when Linux writes 0 to
the status register CMP bit is also automatically cleared and the
problem goes away.

Those systems that were not recovered WREN was not in effect so clearing
the status register and CMP bit was ignored by the serial flash chip.

Normally WREN is send as a preopcode part of an atomic sequence when
software sequencing is used. This has been enabled since commit
8c473dd61bb5 ("spi-nor: intel-spi: Don't assume OPMENU0/1 to be
programmed by BIOS").

However, many systems have two write enable preopcodes available the
PREOP_OPTYPE register:

  0x50 - Write enable for volatile status register
  0x06 - Write enable (WREN)

The current code picks the former which does not enable write for
non-volatile bits so any writes to the status register non-volatile
bits, including BP0/1/2 protection bits do not take effect.

The attached patch changes the driver so that it prefers WREN over other
write enable preopcodes. Booting to the kernel with the patch applied on
a system where the issue still persists should reset the protection bits
and allow the BIOS to save settings again.

** Patch added: 
"0001-spi-nor-intel-spi-Prefer-WREN-over-other-write-enabl.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+attachment/5030406/+files/0001-spi-nor-intel-spi-Prefer-WREN-over-other-write-enabl.patch

-- 
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 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

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  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.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-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

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2018-01-01 Thread Mika Westerberg

Can someone who still has the problem try v4.15-rcX kernel instead? It
got few fixes for the atomic sequence handling and might explain why not
all systems recover.

-- 
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 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

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  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.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-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

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531  (not fixed by 4.14.9)
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Original Description:

  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!!

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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-27 Thread Mika Westerberg

I think the reason why 4.14.x works is because of commit 9d63f17661e2
("spi-nor: intel-spi: Fix broken software sequencing codes").

The current theory is that for certain serial flashes (those


with SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) Linux   

 
SPI-NOR core wants to clear the status register (SR) in addition to 

 
reading the chip JEDEC ID. This is done to make sure protection bits

 
(BP0, BP1 and BP2) are cleared. 

 


 
The sequence looks like this:   

 


 
  WREN (write enable)   

 
  WRSR with 0 (write status register)   

 


 
However, the intel-spi driver had an off-by-one bug that causes it to   

 
write two bytes instead of one. So the above sequence actually looks

 
like:   

 


 
  WREN (write enable)   

 
  WRSR with 0, X (write status register)

 


 
Where X is something that is in FDATA[1] FIFO. Most likely this is part 

 
of the just read chip JEDEC ID. Now, WRSR command is weird in a sense   

 
that it allows writing both the status register and the control 

 
register even though there are separate commands to read them. If the X 

 
above has bit 6 set we end up writing this to the control register which

[Kernel-packages] [Bug 1696325] Re: USB, display and ethernet ports in HP Thunderbolt dock don't work

2017-08-18 Thread Mika Westerberg

Thunderbolt support for PCs is included in v4.13-rc1 and later kernels.
Do you have a possibility to try the latest mainline kernel?

Note the userspace support is not yet ready so you need to authorize
device manually. See for example:https://www.kernel.org/doc/html/latest
/admin-guide/thunderbolt.html how it can be done.

-- 
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/1696325

Title:
  USB, display and ethernet ports in HP Thunderbolt dock don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have laptop HP ZBook G3 Studio with Thunderbolt dock P5Q58AA.
  Installed OS is Ubuntu 16.04.2 LTS

  When I connect dock into laptop only power works and laptop can be
  shutdown by pressing power button in dock. USB ports, display ports,
  ethernet port and audio plug are not working.

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  $ apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
Installed: 4.8.0.54.25
Candidate: 4.8.0.54.25
Version table:
   *** 4.8.0.54.25 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  --- 
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  markus 3304 F pulseaudio
   /dev/snd/controlC0:  markus 3304 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-07 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 
1576)
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G3
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed 
root=UUID=2b78b572-05a1-4c01-b97d-9c1fea406faf ro quiet splash nomodeset 
pnpacpi=off vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-54-generic N/A
   linux-backports-modules-4.8.0-54-generic  N/A
   linux-firmware1.157.10
  Tags:  xenial
  Uname: Linux 4.8.0-54-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: 11/02/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.15
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.67
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.15:bd11/02/2016:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.67:cvnHP:ct10:cvr:
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696325/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

2017-08-14 Thread Mika Westerberg

This definitely sounds like a platform/configuration issue rather than a
driver bug.

-- 
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/1708043

Title:
  Lenovo X1 Carbon Gen5 fails to resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last week it worked fine, this week however if I open the lid for it
  to resume the power light flashes for a bit, then comes on solid, the
  but screen stays blank and the machine is unresponsive. I have to
  power it off / on again in order to use it. It might be related to the
  APST issue with Samsung NVMe SSDs, I'm not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dean   1652 F...m pulseaudio
   /dev/snd/controlC0:  dean   1652 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug  1 17:39:20 2017
  HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-041300rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

2017-08-13 Thread Mika Westerberg

All of them are expected to work. Usually the default is "User
authorization".

-- 
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/1708043

Title:
  Lenovo X1 Carbon Gen5 fails to resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last week it worked fine, this week however if I open the lid for it
  to resume the power light flashes for a bit, then comes on solid, the
  but screen stays blank and the machine is unresponsive. I have to
  power it off / on again in order to use it. It might be related to the
  APST issue with Samsung NVMe SSDs, I'm not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dean   1652 F...m pulseaudio
   /dev/snd/controlC0:  dean   1652 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug  1 17:39:20 2017
  HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-041300rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

2017-08-12 Thread Mika Westerberg

Thanks for the information. I'll go through them.

Aaron, can you try to switch security level of your machine to the same:

Security Level - Display Port and USB

and see if the problem reproduces?

-- 
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/1708043

Title:
  Lenovo X1 Carbon Gen5 fails to resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last week it worked fine, this week however if I open the lid for it
  to resume the power light flashes for a bit, then comes on solid, the
  but screen stays blank and the machine is unresponsive. I have to
  power it off / on again in order to use it. It might be related to the
  APST issue with Samsung NVMe SSDs, I'm not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dean   1652 F...m pulseaudio
   /dev/snd/controlC0:  dean   1652 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug  1 17:39:20 2017
  HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-041300rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

2017-08-09 Thread Mika Westerberg

Thanks Aaron. So as expected the Thunderbolt controller is not there.
Only xHCI when USB-C device is connected.

Dean, is there something special you have connected to the machine?
Aaron, who has exactly the same machine and BIOS, can't reproduce the
issue you have reported.

-- 
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/1708043

Title:
  Lenovo X1 Carbon Gen5 fails to resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last week it worked fine, this week however if I open the lid for it
  to resume the power light flashes for a bit, then comes on solid, the
  but screen stays blank and the machine is unresponsive. I have to
  power it off / on again in order to use it. It might be related to the
  APST issue with Samsung NVMe SSDs, I'm not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dean   1652 F...m pulseaudio
   /dev/snd/controlC0:  dean   1652 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug  1 17:39:20 2017
  HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-041300rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

2017-08-08 Thread Mika Westerberg

Did you do any settings in BIOS related to Thunderbolt? Sometimes there
is an option called "Force power" which basically turns power on the
controller always. In normal cases that option should be disabled.

Also can you attach acpidump (along with the other things I requeted) of
the system to the bug?

-- 
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/1708043

Title:
  Lenovo X1 Carbon Gen5 fails to resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last week it worked fine, this week however if I open the lid for it
  to resume the power light flashes for a bit, then comes on solid, the
  but screen stays blank and the machine is unresponsive. I have to
  power it off / on again in order to use it. It might be related to the
  APST issue with Samsung NVMe SSDs, I'm not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dean   1652 F...m pulseaudio
   /dev/snd/controlC0:  dean   1652 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug  1 17:39:20 2017
  HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-041300rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

2017-08-07 Thread Mika Westerberg

Can you also try the attached patch? It should apply on top of
v4.13-rcX. I'm guessing ICM is not running on the Lenovo system so we
should start it but skip all the link reset things. Please post dmesg of
this test as well.

** Patch added: "Start ICM if it is not started"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+attachment/4928301/+files/lenovo-tbt-icm-test.diff

-- 
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/1708043

Title:
  Lenovo X1 Carbon Gen5 fails to resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last week it worked fine, this week however if I open the lid for it
  to resume the power light flashes for a bit, then comes on solid, the
  but screen stays blank and the machine is unresponsive. I have to
  power it off / on again in order to use it. It might be related to the
  APST issue with Samsung NVMe SSDs, I'm not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dean   1652 F...m pulseaudio
   /dev/snd/controlC0:  dean   1652 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug  1 17:39:20 2017
  HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-041300rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

2017-08-07 Thread Mika Westerberg

Also can you attach full dmesg when you boot the system using v4.13-rcX
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/1708043

Title:
  Lenovo X1 Carbon Gen5 fails to resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last week it worked fine, this week however if I open the lid for it
  to resume the power light flashes for a bit, then comes on solid, the
  but screen stays blank and the machine is unresponsive. I have to
  power it off / on again in order to use it. It might be related to the
  APST issue with Samsung NVMe SSDs, I'm not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dean   1652 F...m pulseaudio
   /dev/snd/controlC0:  dean   1652 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug  1 17:39:20 2017
  HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-041300rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

2017-08-07 Thread Mika Westerberg

Dean, just that I understand this correctly. Do you have anything
connected to the Thunderbolt port?

-- 
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/1708043

Title:
  Lenovo X1 Carbon Gen5 fails to resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last week it worked fine, this week however if I open the lid for it
  to resume the power light flashes for a bit, then comes on solid, the
  but screen stays blank and the machine is unresponsive. I have to
  power it off / on again in order to use it. It might be related to the
  APST issue with Samsung NVMe SSDs, I'm not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dean   1652 F...m pulseaudio
   /dev/snd/controlC0:  dean   1652 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug  1 17:39:20 2017
  HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-041300rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1878602] Re: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail

[Kernel-packages] [Bug 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen

[Kernel-packages] [Bug 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen

[Kernel-packages] [Bug 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen

[Kernel-packages] [Bug 1696325] Re: USB, display and ethernet ports in HP Thunderbolt dock don't work

[Kernel-packages] [Bug 1696325] Re: USB, display and ethernet ports in HP Thunderbolt dock don't work

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Kernel-packages] [Bug 1696325] Re: USB, display and ethernet ports in HP Thunderbolt dock don't work

[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

32 matches

Site Navigation

Mail list logo

Footer information