[Kernel-packages] [Bug 1686048] Re: Touchpad not detected on Lenovo S21e-20

[Kai-Heng Feng]

You need to file an upstream report then. It's at
https://bugzilla.kernel.org/

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

Title:
  Touchpad not detected on Lenovo S21e-20

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  xinput list
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳  USB OPTICAL MOUSEid=9[slave  pointer  (2)]
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)]
  ↳ Power Button  id=8[slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)]
  ↳ Lenovo EasyCamera

  cat /proc/bus/input/devices 
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2
   
  B: PROP=0 
   
  B: EV=3   
   
  B: KEY=10 0   
   

   
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=15d9 Product=0a4c Version=0111
  N: Name=" USB OPTICAL MOUSE"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:15D9:0A4C.0001/input/input5
  U: Uniq=
  H: Handlers=mouse0 event5 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=103
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input6
  U: Uniq=
  H: Handlers=event6 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Front Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input7
  U: Uniq=
  H: Handlers=event7 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input8
  U: Uniq=
  H: Handlers=event8 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0003 Vendor=5986 Product=0674 Version=4207
  N: Name="Lenovo EasyCamera"
  P: Phys=usb-:00:14.0-3/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/input/input9
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1146 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Apr 25 11:15:33 2017
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 105b:e065 Foxconn International, Inc. 

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Mathieu Pellerin]

I've also been suffering from this issue. The kernel here
(http://people.canonical.com/~sforshee/lp1674838/) appears to have dealt
with the system hang, happily viewing videos on Firefox now.

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1596941] Re: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive)

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu Wily) because there has been no activity for
60 days.]

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

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

Title:
  KVM deadlock on KVM guest migration with latest QEMU (mitaka) from
  Xenial (or Mitaka Ubuntu Cloud Archive)

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Trusty:
  Expired
Status in linux source package in Vivid:
  Expired
Status in linux source package in Wily:
  Expired
Status in linux source package in Xenial:
  Expired
Status in linux source package in Yakkety:
  Expired

Bug description:
  It was brought to my knowledge that qemu-kvm live migration (with full
  storage copy) on Trusty + Mitaka Ubuntu Cloud Archive was broken. When
  investigating I stepped into the following situation:

  crash> sys
KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-86-generic
  DUMPFILE: ./201606241546/dump.201606241546  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Jun 24 15:46:39 2016
UPTIME: 00:06:00
  LOAD AVERAGE: 1.00, 0.60, 0.26
 TASKS: 146
  NODENAME: vmqemulivefail1
   RELEASE: 3.13.0-86-generic
   VERSION: #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016
   MACHINE: x86_64  (2494 Mhz)
MEMORY: 8 GB
 PANIC: "Kernel panic - not syncing: hung_task: blocked tasks"

  Full backtrace doesn't have anything useful since i've configured
  kernel.softlockup_panic.

  From scheduled-out tasks (and from kern.log) I was able to see that in
  more than one occasion I had the qemu process possibly dead-locked
  when dealing with asynchronous page faults:

  ## kernel 3.13

  # dump 1

  PID: 1604   TASK: 8800374be000  CPU: 3   COMMAND: "qemu-system-x86"
   #0 [8800ba115e28] __schedule at 8172e379
   #1 [8800ba115e90] schedule at 8172e859
   #2 [8800ba115ea0] kvm_async_pf_task_wait at 8105060f
   #3 [8800ba115f38] do_async_page_fault at 81736090
   #4 [8800ba115f50] async_page_fault at 81732cd8
  RIP: 7fb4eff0a4b3  RSP: 7fb4713facb0  RFLAGS: 00010206
  RAX: 7fb4cb9cf000  RBX: 7fb4f166d8f0  RCX: 0010
  RDX: 1fff  RSI: 7fb4cb9deff8  RDI: 4000
  RBP:    R8:    R9: 0002601b
  R10: 00fffe00  R11: 1fff  R12: 0008
  R13: 7fb4713fad84  R14: 7fb4f1665290  R15: 7fb4713fad88
  ORIG_RAX:   CS: 0033  SS: 002b

  # dump 2

  PID: 1735   TASK: 8800b9bcb000  CPU: 2   COMMAND: "qemu-system-x86"
   #0 [8802333c9e28] __schedule at 8172e379
   #1 [8802333c9e90] schedule at 8172e859
   #2 [8802333c9ea0] kvm_async_pf_task_wait at 8105060f
   #3 [8802333c9f38] do_async_page_fault at 81736090
   #4 [8802333c9f50] async_page_fault at 81732cd8
  RIP: 7f631399d3b0  RSP: 7f62912c7990  RFLAGS: 00010206
  RAX:   RBX: 7f6315f9e370  RCX: 7f62ca714000
  RDX: 32914020  RSI: 1000  RDI: 7f62ca714000
  RBP: 7f6315c66e40   R8: 7f62912c7a40   R9: 7f6315f9e3e0
  R10:   R11: 32914020  R12: 32914020
  R13: 00032914  R14:   R15: 
  ORIG_RAX:   CS: 0033  SS: 002b

  # dump 3

  PID: 1617   TASK: 880232834800  CPU: 3   COMMAND: "qemu-system-x86"
   #0 [880232a6de28] __schedule at 8172e379
   #1 [880232a6de90] schedule at 8172e859
   #2 [880232a6dea0] kvm_async_pf_task_wait at 8105060f
   #3 [880232a6df38] do_async_page_fault at 81736090
   #4 [880232a6df50] async_page_fault at 81732cd8
  RIP: 7f8c39e8b3b0  RSP: 7f8bb80c9990  RFLAGS: 00010206
  RAX:   RBX: 7f8c3aeba370  RCX: 7f8bdea18000
  RDX: 22c18020  RSI: 1000  RDI: 7f8bdea18000
  RBP: 7f8c3ab82e40   R8: 7f8bb80c9a40   R9: 7f8c3aeba498
  R10:   R11: 22c18020  R12: 22c18020
  R13: 00022c18  R14:   R15: 
  ORIG_RAX:   CS: 0033  SS: 002b

  ## kernel 4.4

  # kern.log

  544 [  360.282132] INFO: task qemu-system-x86:1592 blocked for more than 120 
seconds.
  545 [  360.282984]   Not tainted 4.4.0-27-generic #46~14.04.1-Ubuntu
  546 [  360.283581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  547 [  360.284439] qemu-system-x86 D 8800bb833e90 0  1592  1 
0x
  548 [  360.284443]  8800bb833e90 88023151c4c0 8802345eb700 
8800bb834000
  549 [  360.28]  0010 81efe6d0 55ac8fa05520 

[Kernel-packages] [Bug 1596941] Re: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive)

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu Yakkety) because there has been no activity
for 60 days.]

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

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

Title:
  KVM deadlock on KVM guest migration with latest QEMU (mitaka) from
  Xenial (or Mitaka Ubuntu Cloud Archive)

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Trusty:
  Expired
Status in linux source package in Vivid:
  Expired
Status in linux source package in Wily:
  Expired
Status in linux source package in Xenial:
  Expired
Status in linux source package in Yakkety:
  Expired

Bug description:
  It was brought to my knowledge that qemu-kvm live migration (with full
  storage copy) on Trusty + Mitaka Ubuntu Cloud Archive was broken. When
  investigating I stepped into the following situation:

  crash> sys
KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-86-generic
  DUMPFILE: ./201606241546/dump.201606241546  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Jun 24 15:46:39 2016
UPTIME: 00:06:00
  LOAD AVERAGE: 1.00, 0.60, 0.26
 TASKS: 146
  NODENAME: vmqemulivefail1
   RELEASE: 3.13.0-86-generic
   VERSION: #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016
   MACHINE: x86_64  (2494 Mhz)
MEMORY: 8 GB
 PANIC: "Kernel panic - not syncing: hung_task: blocked tasks"

  Full backtrace doesn't have anything useful since i've configured
  kernel.softlockup_panic.

  From scheduled-out tasks (and from kern.log) I was able to see that in
  more than one occasion I had the qemu process possibly dead-locked
  when dealing with asynchronous page faults:

  ## kernel 3.13

  # dump 1

  PID: 1604   TASK: 8800374be000  CPU: 3   COMMAND: "qemu-system-x86"
   #0 [8800ba115e28] __schedule at 8172e379
   #1 [8800ba115e90] schedule at 8172e859
   #2 [8800ba115ea0] kvm_async_pf_task_wait at 8105060f
   #3 [8800ba115f38] do_async_page_fault at 81736090
   #4 [8800ba115f50] async_page_fault at 81732cd8
  RIP: 7fb4eff0a4b3  RSP: 7fb4713facb0  RFLAGS: 00010206
  RAX: 7fb4cb9cf000  RBX: 7fb4f166d8f0  RCX: 0010
  RDX: 1fff  RSI: 7fb4cb9deff8  RDI: 4000
  RBP:    R8:    R9: 0002601b
  R10: 00fffe00  R11: 1fff  R12: 0008
  R13: 7fb4713fad84  R14: 7fb4f1665290  R15: 7fb4713fad88
  ORIG_RAX:   CS: 0033  SS: 002b

  # dump 2

  PID: 1735   TASK: 8800b9bcb000  CPU: 2   COMMAND: "qemu-system-x86"
   #0 [8802333c9e28] __schedule at 8172e379
   #1 [8802333c9e90] schedule at 8172e859
   #2 [8802333c9ea0] kvm_async_pf_task_wait at 8105060f
   #3 [8802333c9f38] do_async_page_fault at 81736090
   #4 [8802333c9f50] async_page_fault at 81732cd8
  RIP: 7f631399d3b0  RSP: 7f62912c7990  RFLAGS: 00010206
  RAX:   RBX: 7f6315f9e370  RCX: 7f62ca714000
  RDX: 32914020  RSI: 1000  RDI: 7f62ca714000
  RBP: 7f6315c66e40   R8: 7f62912c7a40   R9: 7f6315f9e3e0
  R10:   R11: 32914020  R12: 32914020
  R13: 00032914  R14:   R15: 
  ORIG_RAX:   CS: 0033  SS: 002b

  # dump 3

  PID: 1617   TASK: 880232834800  CPU: 3   COMMAND: "qemu-system-x86"
   #0 [880232a6de28] __schedule at 8172e379
   #1 [880232a6de90] schedule at 8172e859
   #2 [880232a6dea0] kvm_async_pf_task_wait at 8105060f
   #3 [880232a6df38] do_async_page_fault at 81736090
   #4 [880232a6df50] async_page_fault at 81732cd8
  RIP: 7f8c39e8b3b0  RSP: 7f8bb80c9990  RFLAGS: 00010206
  RAX:   RBX: 7f8c3aeba370  RCX: 7f8bdea18000
  RDX: 22c18020  RSI: 1000  RDI: 7f8bdea18000
  RBP: 7f8c3ab82e40   R8: 7f8bb80c9a40   R9: 7f8c3aeba498
  R10:   R11: 22c18020  R12: 22c18020
  R13: 00022c18  R14:   R15: 
  ORIG_RAX:   CS: 0033  SS: 002b

  ## kernel 4.4

  # kern.log

  544 [  360.282132] INFO: task qemu-system-x86:1592 blocked for more than 120 
seconds.
  545 [  360.282984]   Not tainted 4.4.0-27-generic #46~14.04.1-Ubuntu
  546 [  360.283581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  547 [  360.284439] qemu-system-x86 D 8800bb833e90 0  1592  1 
0x
  548 [  360.284443]  8800bb833e90 88023151c4c0 8802345eb700 
8800bb834000
  549 [  360.28]  0010 81efe6d0 55ac8fa05520 

[Kernel-packages] [Bug 1596941] Re: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive)

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]

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

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

Title:
  KVM deadlock on KVM guest migration with latest QEMU (mitaka) from
  Xenial (or Mitaka Ubuntu Cloud Archive)

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Trusty:
  Expired
Status in linux source package in Vivid:
  Expired
Status in linux source package in Wily:
  Expired
Status in linux source package in Xenial:
  Expired
Status in linux source package in Yakkety:
  Expired

Bug description:
  It was brought to my knowledge that qemu-kvm live migration (with full
  storage copy) on Trusty + Mitaka Ubuntu Cloud Archive was broken. When
  investigating I stepped into the following situation:

  crash> sys
KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-86-generic
  DUMPFILE: ./201606241546/dump.201606241546  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Jun 24 15:46:39 2016
UPTIME: 00:06:00
  LOAD AVERAGE: 1.00, 0.60, 0.26
 TASKS: 146
  NODENAME: vmqemulivefail1
   RELEASE: 3.13.0-86-generic
   VERSION: #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016
   MACHINE: x86_64  (2494 Mhz)
MEMORY: 8 GB
 PANIC: "Kernel panic - not syncing: hung_task: blocked tasks"

  Full backtrace doesn't have anything useful since i've configured
  kernel.softlockup_panic.

  From scheduled-out tasks (and from kern.log) I was able to see that in
  more than one occasion I had the qemu process possibly dead-locked
  when dealing with asynchronous page faults:

  ## kernel 3.13

  # dump 1

  PID: 1604   TASK: 8800374be000  CPU: 3   COMMAND: "qemu-system-x86"
   #0 [8800ba115e28] __schedule at 8172e379
   #1 [8800ba115e90] schedule at 8172e859
   #2 [8800ba115ea0] kvm_async_pf_task_wait at 8105060f
   #3 [8800ba115f38] do_async_page_fault at 81736090
   #4 [8800ba115f50] async_page_fault at 81732cd8
  RIP: 7fb4eff0a4b3  RSP: 7fb4713facb0  RFLAGS: 00010206
  RAX: 7fb4cb9cf000  RBX: 7fb4f166d8f0  RCX: 0010
  RDX: 1fff  RSI: 7fb4cb9deff8  RDI: 4000
  RBP:    R8:    R9: 0002601b
  R10: 00fffe00  R11: 1fff  R12: 0008
  R13: 7fb4713fad84  R14: 7fb4f1665290  R15: 7fb4713fad88
  ORIG_RAX:   CS: 0033  SS: 002b

  # dump 2

  PID: 1735   TASK: 8800b9bcb000  CPU: 2   COMMAND: "qemu-system-x86"
   #0 [8802333c9e28] __schedule at 8172e379
   #1 [8802333c9e90] schedule at 8172e859
   #2 [8802333c9ea0] kvm_async_pf_task_wait at 8105060f
   #3 [8802333c9f38] do_async_page_fault at 81736090
   #4 [8802333c9f50] async_page_fault at 81732cd8
  RIP: 7f631399d3b0  RSP: 7f62912c7990  RFLAGS: 00010206
  RAX:   RBX: 7f6315f9e370  RCX: 7f62ca714000
  RDX: 32914020  RSI: 1000  RDI: 7f62ca714000
  RBP: 7f6315c66e40   R8: 7f62912c7a40   R9: 7f6315f9e3e0
  R10:   R11: 32914020  R12: 32914020
  R13: 00032914  R14:   R15: 
  ORIG_RAX:   CS: 0033  SS: 002b

  # dump 3

  PID: 1617   TASK: 880232834800  CPU: 3   COMMAND: "qemu-system-x86"
   #0 [880232a6de28] __schedule at 8172e379
   #1 [880232a6de90] schedule at 8172e859
   #2 [880232a6dea0] kvm_async_pf_task_wait at 8105060f
   #3 [880232a6df38] do_async_page_fault at 81736090
   #4 [880232a6df50] async_page_fault at 81732cd8
  RIP: 7f8c39e8b3b0  RSP: 7f8bb80c9990  RFLAGS: 00010206
  RAX:   RBX: 7f8c3aeba370  RCX: 7f8bdea18000
  RDX: 22c18020  RSI: 1000  RDI: 7f8bdea18000
  RBP: 7f8c3ab82e40   R8: 7f8bb80c9a40   R9: 7f8c3aeba498
  R10:   R11: 22c18020  R12: 22c18020
  R13: 00022c18  R14:   R15: 
  ORIG_RAX:   CS: 0033  SS: 002b

  ## kernel 4.4

  # kern.log

  544 [  360.282132] INFO: task qemu-system-x86:1592 blocked for more than 120 
seconds.
  545 [  360.282984]   Not tainted 4.4.0-27-generic #46~14.04.1-Ubuntu
  546 [  360.283581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  547 [  360.284439] qemu-system-x86 D 8800bb833e90 0  1592  1 
0x
  548 [  360.284443]  8800bb833e90 88023151c4c0 8802345eb700 
8800bb834000
  549 [  360.28]  0010 81efe6d0 55ac8fa05520 

[Kernel-packages] [Bug 1596941] Re: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive)

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu Vivid) because there has been no activity for
60 days.]

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

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

Title:
  KVM deadlock on KVM guest migration with latest QEMU (mitaka) from
  Xenial (or Mitaka Ubuntu Cloud Archive)

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Trusty:
  Expired
Status in linux source package in Vivid:
  Expired
Status in linux source package in Wily:
  Expired
Status in linux source package in Xenial:
  Expired
Status in linux source package in Yakkety:
  Expired

Bug description:
  It was brought to my knowledge that qemu-kvm live migration (with full
  storage copy) on Trusty + Mitaka Ubuntu Cloud Archive was broken. When
  investigating I stepped into the following situation:

  crash> sys
KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-86-generic
  DUMPFILE: ./201606241546/dump.201606241546  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Jun 24 15:46:39 2016
UPTIME: 00:06:00
  LOAD AVERAGE: 1.00, 0.60, 0.26
 TASKS: 146
  NODENAME: vmqemulivefail1
   RELEASE: 3.13.0-86-generic
   VERSION: #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016
   MACHINE: x86_64  (2494 Mhz)
MEMORY: 8 GB
 PANIC: "Kernel panic - not syncing: hung_task: blocked tasks"

  Full backtrace doesn't have anything useful since i've configured
  kernel.softlockup_panic.

  From scheduled-out tasks (and from kern.log) I was able to see that in
  more than one occasion I had the qemu process possibly dead-locked
  when dealing with asynchronous page faults:

  ## kernel 3.13

  # dump 1

  PID: 1604   TASK: 8800374be000  CPU: 3   COMMAND: "qemu-system-x86"
   #0 [8800ba115e28] __schedule at 8172e379
   #1 [8800ba115e90] schedule at 8172e859
   #2 [8800ba115ea0] kvm_async_pf_task_wait at 8105060f
   #3 [8800ba115f38] do_async_page_fault at 81736090
   #4 [8800ba115f50] async_page_fault at 81732cd8
  RIP: 7fb4eff0a4b3  RSP: 7fb4713facb0  RFLAGS: 00010206
  RAX: 7fb4cb9cf000  RBX: 7fb4f166d8f0  RCX: 0010
  RDX: 1fff  RSI: 7fb4cb9deff8  RDI: 4000
  RBP:    R8:    R9: 0002601b
  R10: 00fffe00  R11: 1fff  R12: 0008
  R13: 7fb4713fad84  R14: 7fb4f1665290  R15: 7fb4713fad88
  ORIG_RAX:   CS: 0033  SS: 002b

  # dump 2

  PID: 1735   TASK: 8800b9bcb000  CPU: 2   COMMAND: "qemu-system-x86"
   #0 [8802333c9e28] __schedule at 8172e379
   #1 [8802333c9e90] schedule at 8172e859
   #2 [8802333c9ea0] kvm_async_pf_task_wait at 8105060f
   #3 [8802333c9f38] do_async_page_fault at 81736090
   #4 [8802333c9f50] async_page_fault at 81732cd8
  RIP: 7f631399d3b0  RSP: 7f62912c7990  RFLAGS: 00010206
  RAX:   RBX: 7f6315f9e370  RCX: 7f62ca714000
  RDX: 32914020  RSI: 1000  RDI: 7f62ca714000
  RBP: 7f6315c66e40   R8: 7f62912c7a40   R9: 7f6315f9e3e0
  R10:   R11: 32914020  R12: 32914020
  R13: 00032914  R14:   R15: 
  ORIG_RAX:   CS: 0033  SS: 002b

  # dump 3

  PID: 1617   TASK: 880232834800  CPU: 3   COMMAND: "qemu-system-x86"
   #0 [880232a6de28] __schedule at 8172e379
   #1 [880232a6de90] schedule at 8172e859
   #2 [880232a6dea0] kvm_async_pf_task_wait at 8105060f
   #3 [880232a6df38] do_async_page_fault at 81736090
   #4 [880232a6df50] async_page_fault at 81732cd8
  RIP: 7f8c39e8b3b0  RSP: 7f8bb80c9990  RFLAGS: 00010206
  RAX:   RBX: 7f8c3aeba370  RCX: 7f8bdea18000
  RDX: 22c18020  RSI: 1000  RDI: 7f8bdea18000
  RBP: 7f8c3ab82e40   R8: 7f8bb80c9a40   R9: 7f8c3aeba498
  R10:   R11: 22c18020  R12: 22c18020
  R13: 00022c18  R14:   R15: 
  ORIG_RAX:   CS: 0033  SS: 002b

  ## kernel 4.4

  # kern.log

  544 [  360.282132] INFO: task qemu-system-x86:1592 blocked for more than 120 
seconds.
  545 [  360.282984]   Not tainted 4.4.0-27-generic #46~14.04.1-Ubuntu
  546 [  360.283581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  547 [  360.284439] qemu-system-x86 D 8800bb833e90 0  1592  1 
0x
  548 [  360.284443]  8800bb833e90 88023151c4c0 8802345eb700 
8800bb834000
  549 [  360.28]  0010 81efe6d0 55ac8fa05520 

[Kernel-packages] [Bug 1596941] Re: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive)

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu Trusty) because there has been no activity
for 60 days.]

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

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

Title:
  KVM deadlock on KVM guest migration with latest QEMU (mitaka) from
  Xenial (or Mitaka Ubuntu Cloud Archive)

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Trusty:
  Expired
Status in linux source package in Vivid:
  Expired
Status in linux source package in Wily:
  Expired
Status in linux source package in Xenial:
  Expired
Status in linux source package in Yakkety:
  Expired

Bug description:
  It was brought to my knowledge that qemu-kvm live migration (with full
  storage copy) on Trusty + Mitaka Ubuntu Cloud Archive was broken. When
  investigating I stepped into the following situation:

  crash> sys
KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-86-generic
  DUMPFILE: ./201606241546/dump.201606241546  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Jun 24 15:46:39 2016
UPTIME: 00:06:00
  LOAD AVERAGE: 1.00, 0.60, 0.26
 TASKS: 146
  NODENAME: vmqemulivefail1
   RELEASE: 3.13.0-86-generic
   VERSION: #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016
   MACHINE: x86_64  (2494 Mhz)
MEMORY: 8 GB
 PANIC: "Kernel panic - not syncing: hung_task: blocked tasks"

  Full backtrace doesn't have anything useful since i've configured
  kernel.softlockup_panic.

  From scheduled-out tasks (and from kern.log) I was able to see that in
  more than one occasion I had the qemu process possibly dead-locked
  when dealing with asynchronous page faults:

  ## kernel 3.13

  # dump 1

  PID: 1604   TASK: 8800374be000  CPU: 3   COMMAND: "qemu-system-x86"
   #0 [8800ba115e28] __schedule at 8172e379
   #1 [8800ba115e90] schedule at 8172e859
   #2 [8800ba115ea0] kvm_async_pf_task_wait at 8105060f
   #3 [8800ba115f38] do_async_page_fault at 81736090
   #4 [8800ba115f50] async_page_fault at 81732cd8
  RIP: 7fb4eff0a4b3  RSP: 7fb4713facb0  RFLAGS: 00010206
  RAX: 7fb4cb9cf000  RBX: 7fb4f166d8f0  RCX: 0010
  RDX: 1fff  RSI: 7fb4cb9deff8  RDI: 4000
  RBP:    R8:    R9: 0002601b
  R10: 00fffe00  R11: 1fff  R12: 0008
  R13: 7fb4713fad84  R14: 7fb4f1665290  R15: 7fb4713fad88
  ORIG_RAX:   CS: 0033  SS: 002b

  # dump 2

  PID: 1735   TASK: 8800b9bcb000  CPU: 2   COMMAND: "qemu-system-x86"
   #0 [8802333c9e28] __schedule at 8172e379
   #1 [8802333c9e90] schedule at 8172e859
   #2 [8802333c9ea0] kvm_async_pf_task_wait at 8105060f
   #3 [8802333c9f38] do_async_page_fault at 81736090
   #4 [8802333c9f50] async_page_fault at 81732cd8
  RIP: 7f631399d3b0  RSP: 7f62912c7990  RFLAGS: 00010206
  RAX:   RBX: 7f6315f9e370  RCX: 7f62ca714000
  RDX: 32914020  RSI: 1000  RDI: 7f62ca714000
  RBP: 7f6315c66e40   R8: 7f62912c7a40   R9: 7f6315f9e3e0
  R10:   R11: 32914020  R12: 32914020
  R13: 00032914  R14:   R15: 
  ORIG_RAX:   CS: 0033  SS: 002b

  # dump 3

  PID: 1617   TASK: 880232834800  CPU: 3   COMMAND: "qemu-system-x86"
   #0 [880232a6de28] __schedule at 8172e379
   #1 [880232a6de90] schedule at 8172e859
   #2 [880232a6dea0] kvm_async_pf_task_wait at 8105060f
   #3 [880232a6df38] do_async_page_fault at 81736090
   #4 [880232a6df50] async_page_fault at 81732cd8
  RIP: 7f8c39e8b3b0  RSP: 7f8bb80c9990  RFLAGS: 00010206
  RAX:   RBX: 7f8c3aeba370  RCX: 7f8bdea18000
  RDX: 22c18020  RSI: 1000  RDI: 7f8bdea18000
  RBP: 7f8c3ab82e40   R8: 7f8bb80c9a40   R9: 7f8c3aeba498
  R10:   R11: 22c18020  R12: 22c18020
  R13: 00022c18  R14:   R15: 
  ORIG_RAX:   CS: 0033  SS: 002b

  ## kernel 4.4

  # kern.log

  544 [  360.282132] INFO: task qemu-system-x86:1592 blocked for more than 120 
seconds.
  545 [  360.282984]   Not tainted 4.4.0-27-generic #46~14.04.1-Ubuntu
  546 [  360.283581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  547 [  360.284439] qemu-system-x86 D 8800bb833e90 0  1592  1 
0x
  548 [  360.284443]  8800bb833e90 88023151c4c0 8802345eb700 
8800bb834000
  549 [  360.28]  0010 81efe6d0 55ac8fa05520 

[Kernel-packages] [Bug 1596941] Re: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive)

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  KVM deadlock on KVM guest migration with latest QEMU (mitaka) from
  Xenial (or Mitaka Ubuntu Cloud Archive)

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Trusty:
  Expired
Status in linux source package in Vivid:
  Expired
Status in linux source package in Wily:
  Expired
Status in linux source package in Xenial:
  Expired
Status in linux source package in Yakkety:
  Expired

Bug description:
  It was brought to my knowledge that qemu-kvm live migration (with full
  storage copy) on Trusty + Mitaka Ubuntu Cloud Archive was broken. When
  investigating I stepped into the following situation:

  crash> sys
KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-86-generic
  DUMPFILE: ./201606241546/dump.201606241546  [PARTIAL DUMP]
  CPUS: 4
  DATE: Fri Jun 24 15:46:39 2016
UPTIME: 00:06:00
  LOAD AVERAGE: 1.00, 0.60, 0.26
 TASKS: 146
  NODENAME: vmqemulivefail1
   RELEASE: 3.13.0-86-generic
   VERSION: #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016
   MACHINE: x86_64  (2494 Mhz)
MEMORY: 8 GB
 PANIC: "Kernel panic - not syncing: hung_task: blocked tasks"

  Full backtrace doesn't have anything useful since i've configured
  kernel.softlockup_panic.

  From scheduled-out tasks (and from kern.log) I was able to see that in
  more than one occasion I had the qemu process possibly dead-locked
  when dealing with asynchronous page faults:

  ## kernel 3.13

  # dump 1

  PID: 1604   TASK: 8800374be000  CPU: 3   COMMAND: "qemu-system-x86"
   #0 [8800ba115e28] __schedule at 8172e379
   #1 [8800ba115e90] schedule at 8172e859
   #2 [8800ba115ea0] kvm_async_pf_task_wait at 8105060f
   #3 [8800ba115f38] do_async_page_fault at 81736090
   #4 [8800ba115f50] async_page_fault at 81732cd8
  RIP: 7fb4eff0a4b3  RSP: 7fb4713facb0  RFLAGS: 00010206
  RAX: 7fb4cb9cf000  RBX: 7fb4f166d8f0  RCX: 0010
  RDX: 1fff  RSI: 7fb4cb9deff8  RDI: 4000
  RBP:    R8:    R9: 0002601b
  R10: 00fffe00  R11: 1fff  R12: 0008
  R13: 7fb4713fad84  R14: 7fb4f1665290  R15: 7fb4713fad88
  ORIG_RAX:   CS: 0033  SS: 002b

  # dump 2

  PID: 1735   TASK: 8800b9bcb000  CPU: 2   COMMAND: "qemu-system-x86"
   #0 [8802333c9e28] __schedule at 8172e379
   #1 [8802333c9e90] schedule at 8172e859
   #2 [8802333c9ea0] kvm_async_pf_task_wait at 8105060f
   #3 [8802333c9f38] do_async_page_fault at 81736090
   #4 [8802333c9f50] async_page_fault at 81732cd8
  RIP: 7f631399d3b0  RSP: 7f62912c7990  RFLAGS: 00010206
  RAX:   RBX: 7f6315f9e370  RCX: 7f62ca714000
  RDX: 32914020  RSI: 1000  RDI: 7f62ca714000
  RBP: 7f6315c66e40   R8: 7f62912c7a40   R9: 7f6315f9e3e0
  R10:   R11: 32914020  R12: 32914020
  R13: 00032914  R14:   R15: 
  ORIG_RAX:   CS: 0033  SS: 002b

  # dump 3

  PID: 1617   TASK: 880232834800  CPU: 3   COMMAND: "qemu-system-x86"
   #0 [880232a6de28] __schedule at 8172e379
   #1 [880232a6de90] schedule at 8172e859
   #2 [880232a6dea0] kvm_async_pf_task_wait at 8105060f
   #3 [880232a6df38] do_async_page_fault at 81736090
   #4 [880232a6df50] async_page_fault at 81732cd8
  RIP: 7f8c39e8b3b0  RSP: 7f8bb80c9990  RFLAGS: 00010206
  RAX:   RBX: 7f8c3aeba370  RCX: 7f8bdea18000
  RDX: 22c18020  RSI: 1000  RDI: 7f8bdea18000
  RBP: 7f8c3ab82e40   R8: 7f8bb80c9a40   R9: 7f8c3aeba498
  R10:   R11: 22c18020  R12: 22c18020
  R13: 00022c18  R14:   R15: 
  ORIG_RAX:   CS: 0033  SS: 002b

  ## kernel 4.4

  # kern.log

  544 [  360.282132] INFO: task qemu-system-x86:1592 blocked for more than 120 
seconds.
  545 [  360.282984]   Not tainted 4.4.0-27-generic #46~14.04.1-Ubuntu
  546 [  360.283581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  547 [  360.284439] qemu-system-x86 D 8800bb833e90 0  1592  1 
0x
  548 [  360.284443]  8800bb833e90 88023151c4c0 8802345eb700 
8800bb834000
  549 [  360.28]  0010 81efe6d0 55ac8fa05520 

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

[Andrey Vertexx]

Sure

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: 

[Kernel-packages] [Bug 1688424] [NEW] grub-mkrelpath returns invalid zfs dataset -> initramfs: mount /root fails

[Jens Elkner]

Public bug reported:

If zfs is used for boot, boot will fail because of bogus information returned by
/usr/bin/grub-mkrelpath.  E.g. if the zfs dataset for / is rpool/ROOT/linux:

# /usr/bin/grub-mkrelpath /
/ROOT/linux@


This leads to a bogus /boot/grub/grub.cfg because /etc/grub.d/10_linux 
generates a boot entry like this:
linux   /ROOT/linux@/boot/vmlinuz-4.4.0-77-generic root=ZFS=/ROOT/linux ro 
crashkernel=384M-2G:64M,2G-:128M bootdegraded=true debug=y console=ttyS1,115200 
 crashkernel=384M-:128M

This in turn causes that initramfs to fail on boot:
...
+ wait_for_udev
+ command -v udevadm
+ udevadm settle
+ modprobe zfs zfs_autoimport_disable=1
+ ZFS_BOOTFS=/ROOT/linux
+ echo /ROOT/linux
+ sed -e s,/.*,,
+ ZFS_RPOOL=
+ delay=0
+ [ 0 -gt 0 ]
+ unset delay
+ zpool import -N 
[   10.922149] SPL: The /etc/hostid file is not found.
[   10.927031] SPL: using hostid 0x
+ ZFS_STDERR=cannot import '': no such pool available
+ ZFS_ERROR=1
+ [ 1 -ne 0 ]
+ panic Command: zpool import -N 
Message: cannot import '': no such pool available
Error: 1

Manually import the root pool at the command prompt and then exit.
Hint: Try:  zpool import -f -R / -N 


Wrong hint BTW, but at least a hint: "zpool import; zpool import 
${poolID}|rpool" fixes it.
Anyway, when continuing after an 'exit' it fails with:

...
+ zpool status -L 
+ [ n != y ]
+ log_begin_msg Setting mountpoint=/ on ZFS filesystem /ROOT/linux
+ _log_msg Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... 
+ [ n = y ]
+ printf Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... 
Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... + zfs set 
mountpoint=/ /ROOT/linux
+ ZFS_STDERR=cannot open '/ROOT/linux': invalid dataset name
+ [ n != y ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ [ n != y ]
+ log_begin_msg Mounting ZFS filesystem /ROOT/linux
+ _log_msg Begin: Mounting ZFS filesystem /ROOT/linux ... 
+ [ n = y ]
+ printf Begin: Mounting ZFS filesystem /ROOT/linux ... 
Begin: Mounting ZFS filesystem /ROOT/linux ... + mount -t zfs -o zfsutil 
/ROOT/linux /root
+ ZFS_STDERR=filesystem 'ROOT/linux' cannot be mounted, unable to open the 
dataset
mount: mounting /ROOT/linux on /root failed: No such file or directory
+ ZFS_ERROR=1
+ [ n != y ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ [ 1 -ne 0 ]
+ panic Command: mount -t zfs -o zfsutil /ROOT/linux /root
Message: filesystem 'ROOT/linux' cannot be mounted, unable to open the dataset
mount: mounting /ROOT/linux on /root failed: No such file or directory
Error: 1

Manually mount the root filesystem on /root and then exit.


A 'mount -t zfs -o zfsutil rpool/ROOT/linux /root' fixis it and after an 'exit' 
the system finally starts.

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

** Package changed: dmidecode (Ubuntu) => grub2 (Ubuntu)

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

Title:
  grub-mkrelpath returns invalid zfs dataset -> initramfs: mount /root
  fails

Status in grub2 package in Ubuntu:
  New

Bug description:
  If zfs is used for boot, boot will fail because of bogus information returned 
by
  /usr/bin/grub-mkrelpath.  E.g. if the zfs dataset for / is rpool/ROOT/linux:

  # /usr/bin/grub-mkrelpath /
  /ROOT/linux@

  
  This leads to a bogus /boot/grub/grub.cfg because /etc/grub.d/10_linux 
generates a boot entry like this:
  linux   /ROOT/linux@/boot/vmlinuz-4.4.0-77-generic root=ZFS=/ROOT/linux ro 
crashkernel=384M-2G:64M,2G-:128M bootdegraded=true debug=y console=ttyS1,115200 
 crashkernel=384M-:128M

  This in turn causes that initramfs to fail on boot:
  ...
  + wait_for_udev
  + command -v udevadm
  + udevadm settle
  + modprobe zfs zfs_autoimport_disable=1
  + ZFS_BOOTFS=/ROOT/linux
  + echo /ROOT/linux
  + sed -e s,/.*,,
  + ZFS_RPOOL=
  + delay=0
  + [ 0 -gt 0 ]
  + unset delay
  + zpool import -N 
  [   10.922149] SPL: The /etc/hostid file is not found.
  [   10.927031] SPL: using hostid 0x
  + ZFS_STDERR=cannot import '': no such pool available
  + ZFS_ERROR=1
  + [ 1 -ne 0 ]
  + panic Command: zpool import -N 
  Message: cannot import '': no such pool available
  Error: 1

  Manually import the root pool at the command prompt and then exit.
  Hint: Try:  zpool import -f -R / -N 

  
  Wrong hint BTW, but at least a hint: "zpool import; zpool import 
${poolID}|rpool" fixes it.
  Anyway, when continuing after an 'exit' it fails with:

  ...
  + zpool status -L 
  + [ n != y ]
  + log_begin_msg Setting mountpoint=/ on ZFS filesystem /ROOT/linux
  + _log_msg Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... 
  + [ n = y ]
  + printf Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... 
  Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... + zfs set 
mountpoint=/ /ROOT/linux
  + ZFS_STDERR=cannot open '/ROOT/linux': 

[Kernel-packages] [Bug 1687534] Re: Mainline kernels no longer build due to obsolete compression type bzip2

[Rocko]

It's working again, eg http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.11/

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

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

Title:
  Mainline kernels no longer build due to obsolete compression type
  bzip2

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  From 2017-04-27 onwards, the mainline kernels are failing to build, eg
  see http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2017-05-02/

  The error logged is:

dpkg-deb: error: obsolete compression type 'bzip2'; use xz or gzip
  instead

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rocko  1490 F pulseaudio
  Date: Tue May  2 12:36:11 2017
  InstallationDate: Installed on 2017-04-13 (18 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=3f51db63-3e0b-4fe3-86b9-4d5ca0c792d5 ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687534/+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 1686414] rumford (amd64) - tests ran: 22, failed: 3

[Brad Figg]

tests ran:  22, failed: 3;
  
http://kernel.ubuntu.com/testing/4.10.0-21.23-generic/rumford__4.10.0-21.23__2017-05-04_17-35-00/results-index.html

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

Title:
  linux: 4.10.0-21.23 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1686418
  derivatives: 1686419
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686414/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Ondrej Masek]

Same issue here on Ryzen 5 1600 + Gigabyte AB350M Gaming 3 when fresh-
installing Kubuntu 17.10. Shouldn't the importance of this issue be at
least "High"? What can be worse than if you can't even install the OS on
your PC? In the meantime as a workaround, Fedora 26 seems to work 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/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x25

[TomaszChmielewski]

I just had this crash with 4.11.0-041100rc7 (from Ubuntu ppa). Updating
to 4.11 final now...

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

Title:
  System soft-freezes, BUG: unable to handle kernel NULL pointer
  dereference at 0018 in journalctl at
  gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded to 17.04. It appears that now leaving the system
  locked for long enough now makes it unable to respond to any input but
  SysRq.

  This apepars to be the only relevant bit in `journalctl --boot -1`:

  BUG: unable to handle kernel NULL pointer dereference at 0018
  IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  PGD 0 

  Oops: 0002 [#1] SMP
  Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress 
ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel 
pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci 
i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100
  CPU: 3 PID: 3826 Comm: chrome Tainted: G   OE   4.10.0-14-generic 
#16-Ubuntu
  Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015
  task: 99ddb372da00 task.stack: b0ec037dc000
  RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  RSP: 0018:b0ec037df880 EFLAGS: 00010246
  RAX: 99dd0367b880 RBX: 0003 RCX: 0003
  RDX:  RSI: 99ddb737e000 RDI: 99de4ad9
  RBP: b0ec037df8d8 R08:  R09: 
  R10:  R11: 0001 R12: 99ddc994a000
  R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000
  FS:  7fd3a0fa7b00() GS:99de5e58() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0018 CR3: 000174607000 CR4: 003406e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Call Trace:
   gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
   ? __alloc_pages_nodemask+0xff/0x260
   gen8_alloc_va_range+0x23d/0x470 [i915]
   i915_vma_bind+0x7e/0x170 [i915]
   __i915_vma_do_pin+0x2a5/0x450 [i915]
   i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
   i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
   i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915]
   ? radix_tree_lookup_slot+0x22/0x50
   ? shmem_getpage_gfp+0xf9/0xc10
   i915_gem_execbuffer2+0xa1/0x1e0 [i915]
   drm_ioctl+0x21b/0x4c0 [drm]
   ? i915_gem_execbuffer+0x310/0x310 [i915]
   ? __seccomp_filter+0x67/0x250
   do_vfs_ioctl+0xa3/0x610
   ? __secure_computing+0x3f/0xd0
   ? syscall_trace_enter+0xcd/0x2e0
   SyS_ioctl+0x79/0x90
   do_syscall_64+0x5b/0xc0
   entry_SYSCALL64_slow_path+0x25/0x25
  RIP: 0033:0x7fd39a33a907
  RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010
  RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907
  RDX: 76323860 RSI: c0406469 RDI: 000e
  RBP: 76323860 R08:  R09: 
  R10: 0038 R11: 0246 R12: c0406469
  R13: 000e R14:  R15: 
  Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 
ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 
08 0f 1f 44 00
  RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 
b0ec037df880
  CR2: 0018
  ---[ end trace 2a4103476767c23b ]---

  I walked to my computer 12 minutes later, finding it soft-locked as
  described above.

  I realize that this appears somewhat far removed from the real cause
  of the problem, so please let me know what other data I can provide to
  facilitate the debugging process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sraffa 2780 F pulseaudio
   /dev/snd/controlC0:  sraffa 2780 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 30 17:44:00 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640
  InstallationDate: Installed on 2015-11-02 (514 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  

Re: [Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Leonardo Varuzza]

I can boot 4.11, but it  freezes randomly, I don't if the problem is in the
NVIDIA driver, I'm using the 381.09 with the patch to compile on 4.11


On Wed, May 3, 2017 at 3:16 PM Tekkla <1671...@bugs.launchpad.net>
wrote:

> @Nextized Your kernel 4.11 works for me like a charm. No instabilities
> and sound is fully working.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1671360
>
> Title:
>   System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions
>

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Stefan]

For the people who aren't boss enough and just want to install Ubuntu
once this is sorted out, will the fix/work-around be rolled into the iso
as soon as it's confirmed fixed?

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1675443] Please test proposed package

[Brian Murray]

Hello Seth, or anyone else affected,

Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Update linux-firmware in xenial for 4.10 hwe-edge kernel

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

  Impact: The linux-hwe-edge kernel will soon be based on the 4.10 zesty
  kernel, which requires new/updated firmware files.

  Fix: Backport relevant commits from upstream linux-firmware.

  Regression Potential: In most cases these are new files which will not
  be used by older kernels, so no regression is possible there. In a few
  cases there are updates to existing firmware files, and while
  regressions are not expected they are possible.

  ---

  linux-hwe-edge in xenial is in the process of being updated to be
  based on the 4.10 zesty kernel. Add/update firmware files for this
  kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1675443/+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 1647826] Please test proposed package

[Brian Murray]

Hello David, or anyone else affected,

Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  intel 8260 doesn't work with linux kernel 4.8+ when using ucode
  version 22

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Yakkety:
  Fix Released
Status in linux-firmware source package in Zesty:
  Fix Committed
Status in linux-firmware source package in Artful:
  Confirmed

Bug description:
  SRU Justification

  Impact: The -22 firmware for iwlwifi introduces regressions with some
  hardware versus earlier firmware versions. As no newer firmware is
  available, the only fix is to revert back to the older firmware which
  does work.

  Test Case: Using the -22 firmware with affected hardware produces the
  behavior described below. The -21 firmware does not.

  Regression Potential: Switching back to -21 could cause some
  regressions with other hardware supported by this firmware. However as
  -22 causes some hardware to completely fail to work any regressions
  are almost certain to be less severe than the current problems.

  ---

  The -22 microcode for the intel 8260 wifi adapter has compatibility
  issues with Linux Kernel 4.8 under certain hardware configurations.

  The iwlwifi module crashes resulting in wifi failing with "device not
  ready" and kernel errors reported in dmesg.

  [   10.691115] iwlwifi :6e:00.0: Microcode SW error detected.
  Restarting 0x200.

  Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to
  fallback to the -21 ucode resolves the issue and wifi begins working
  normally again.

  This is an issue with Linux kernel 4.8 on both yakkety and xenial, so
  the bug doesn't currently affect users on xenial, but will begin to
  after the 16.04.2 HWE release.  Kernel 4.4 is unaffected because it
  doesn't attempt to use the -22 ucode

  The failure doesn't necessarily affect all machines of a given model
  with the 8260, but I can reproduce it on multiple laptops when 64GB of
  RAM are installed (4x16GB).  The RAM itself does not appear to be an
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+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 448332] Re: helpful information

[chiccomaria]

Hi!

The information that I've  just found seems to  be really helpful, just
take  a look http://tulagi.christyrilling.com

See you around, c.arcella


From: Bug 448332 [mailto:448...@bugs.launchpad.net]
Sent: Thursday, May 04, 2017 4:50 PM
To: c.arce...@bsainformatica.it
Subject: That's cute:)

I was extremely close of  getting a surgery which  would leave me with a
10

Sent from Mail for Windows 10

** Attachment added: "0BD7F2C77CD05A9E440A3C29F8F184A1.jpg"
   
https://bugs.launchpad.net/bugs/448332/+attachment/4872081/+files/0BD7F2C77CD05A9E440A3C29F8F184A1.jpg

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

Title:
  BUG: scheduling while atomic: swapper/0/0x1001

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: linux-image-2.6.31-13-generic

  After updating to kernel 2.6.31-13-generic my system became more
  unstable

  Description:Ubuntu karmic (development branch)
  Release:9.10
  Installed: 2.6.31-13.43
Candidate: 2.6.31-13.43
Version table:
   *** 2.6.31-13.43 0
  500 http://br.archive.ubuntu.com karmic/main Packages
  100 /var/lib/dpkg/status

  ProblemType: KernelOops
  Annotation: Your system might become unstable now and might need to be 
restarted.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andre 21242 F pulseaudio
andre 21244 F kmix
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 21'
 Mixer name : 'SigmaTel STAC9228'
 Components : 'HDA:14f12c06,14f1000f,0010 
HDA:10951392,10280242,0010 HDA:83847616,10280242,00100402'
 Controls  : 33
 Simple ctrls  : 20
  Date: Sat Oct 10 13:08:30 2009
  DistroRelease: Ubuntu 9.10
  Failure: oops
  HibernationDevice: RESUME=UUID=5c911086-b42e-4b82-8ae7-98f9a565b1d9
  MachineType: Dell Inc. Inspiron 1525
  NonfreeKernelModules: wl
  Package: linux-image-2.6.31-13-generic 2.6.31-13.43
  ProcCmdLine: root=UUID=0c1b8172-52a0-4bc5-91f4-98e6569c6ed3 ro splash
  ProcVersionSignature: Ubuntu 2.6.31-13.43-generic
  RelatedPackageVersions: linux-firmware 1.21
  RfKill:
   0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  Tags: kernel-oops
  Title: BUG: scheduling while atomic: swapper/0/0x1001
  Uname: Linux 2.6.31-13-generic i686
  WpaSupplicantLog:
   
  dmi.bios.date: 10/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0D109D
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0D109D:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/448332/+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 1686645] Re: linux: 4.4.0-78.99 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux: 4.4.0-78.99 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686645/+subscriptions

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

Re: [Kernel-packages] [Bug 1687256] Re: byd touchpad no longer detected

[Daveh]

I have just tried that and get "Permission denied"

On 04/05/2017 06:47, Kai-Heng Feng wrote:
> Did you try this command, as commit log suggested?
> echo -n "byd" > /sys/bus/serio/devices/serio1/drvctl
>

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

Title:
  byd touchpad no longer detected

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When running on kernel 4.8.0-34 my Lafite byd touchpad is recognised 
correctly and shows with xinput --list as BYDPS/2 BYD Touchpad.
  If I use any higher upgrade, eg 4.8.0-46 in 16.10 then touchpad is only 
identified as ImPS/2 Generic Wheel Mouse. The same applies if I try 17.04 from 
an external drive, touchpad does not work and cursor remains in top rh corner 
of screen.
  This could be related to the changelog 
https://launchpad.net/ubuntu/+source/linux/+changelog

  4.8.0-36.38 in yakkety-proposed

    * Yakkety update to v4.8.13 stable release (LP: #1650581)
  ...
  - Input: psmouse - disable automatic probing of BYD touchpads

  Any thought on what has changed and how to resolve issue so that I can 
upgrade to later version?
  Thanks
  ---
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   3590 F pulseaudio
   /dev/snd/controlC1:  dave   3590 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0b7a1f56-4391-4d9d-90ed-d0f5f5d76c90
  InstallationDate: Installed on 2015-05-17 (714 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Intel Corporation SharkBay Platform
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: WhiteTip Mountain1 Fab2
  dmi.board.vendor: Topstar
  dmi.board.version: Fab2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/27/2015:svnIntelCorporation:pnSharkBayPlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrFab2:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: SharkBay Platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687256/+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 1687383] Re: Complete computer freeze (screen, mouse, keyboard) after 17.04 upgrade

[Pascal Gicquel]

I tested kernel 4.10.14 and did not produce the crash.

I do not really understand what "see if this issue was cc'd to upstream
stable" means ? Could you explain where (or how) I could "see" 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/1687383

Title:
  Complete computer freeze (screen, mouse, keyboard) after 17.04 upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Extract of system log (Oops part)
  Apr 30 12:01:25 salon kernel: [ 8273.281441] Oops:  [#1] SMP
  Apr 30 12:01:25 salon kernel: [ 8273.281447] Modules linked in: ccm gpio_ich 
snd_hda_codec_hdmi joydev input_leds arc4 ath9k ath9k_common coretemp kvm_intel 
ath9k_hw ath kvm irqbypass mac80211 snd_hda_codec_realtek snd_hda_codec_generic 
serio_raw snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep lpc_ich cfg80211 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq tpm_infineon 
snd_seq_device snd_timer mac_hid shpchp snd soundcore parport_pc ppdev lp 
parport ip_tables x_tables autofs4 hid_logitech ff_memless psmouse uas nouveau 
firewire_ohci pata_acpi firewire_core crc_itu_t usb_storage mxm_wmi wmi video 
pata_jmicron i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
fb_sys_fops drm fjes usbhid hid
  Apr 30 12:01:25 salon kernel: [ 8273.281524] CPU: 1 PID: 1210 Comm: 
InputThread Not tainted 4.10.0-20-generic #22-Ubuntu
  Apr 30 12:01:25 salon kernel: [ 8273.281531] Hardware name: Gigabyte 
Technology Co., Ltd. EP45-DS3R/EP45-DS3R, BIOS F4 05/28/2008
  Apr 30 12:01:25 salon kernel: [ 8273.281538] task: 955c5bad6a40 
task.stack: ac66c1758000
  Apr 30 12:01:25 salon kernel: [ 8273.281545] RIP: 
0010:dma_fence_wait_timeout+0x36/0xf0
  Apr 30 12:01:25 salon kernel: [ 8273.281550] RSP: 0018:ac66c175ba38 
EFLAGS: 00010206
  Apr 30 12:01:25 salon kernel: [ 8273.281556] RAX: 0001 RBX: 
955bc39ca680 RCX: c0351fa0
  Apr 30 12:01:25 salon kernel: [ 8273.281563] RDX: 7fff RSI: 
0001 RDI: 955c5b82f300
  Apr 30 12:01:25 salon kernel: [ 8273.281569] RBP: ac66c175ba58 R08: 
 R09: 955c71c98000
  Apr 30 12:01:25 salon kernel: [ 8273.281575] R10: 955c5286bd40 R11: 
955c727aaa08 R12: 955c5b82f300
  Apr 30 12:01:25 salon kernel: [ 8273.281581] R13: 0001 R14: 
7fff R15: 0001
  Apr 30 12:01:25 salon kernel: [ 8273.281588] FS:  7fa96383f700() 
GS:955c7fc8() knlGS:
  Apr 30 12:01:25 salon kernel: [ 8273.281595] CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 30 12:01:25 salon kernel: [ 8273.281601] CR2: 0021 CR3: 
00011b64f000 CR4: 06e0
  Apr 30 12:01:25 salon kernel: [ 8273.281607] Call Trace:
  Apr 30 12:01:25 salon kernel: [ 8273.281623]  
drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper]
  Apr 30 12:01:25 salon kernel: [ 8273.281679]  
nv50_disp_atomic_commit+0x19c/0x2a0 [nouveau]
  Apr 30 12:01:25 salon kernel: [ 8273.281703]  drm_atomic_commit+0x4b/0x50 
[drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281714]  
drm_atomic_helper_update_plane+0xec/0x150 [drm_kms_helper]
  Apr 30 12:01:25 salon kernel: [ 8273.281731]  __setplane_internal+0x1b4/0x280 
[drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281738]  ? 
__ww_mutex_lock_slowpath+0x29a/0x3d0
  Apr 30 12:01:25 salon kernel: [ 8273.281757]  
drm_mode_cursor_universal+0x126/0x210 [drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281774]  
drm_mode_cursor_common+0x86/0x180 [drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281781]  ? ep_poll_callback+0xef/0x1f0
  Apr 30 12:01:25 salon kernel: [ 8273.281797]  drm_mode_cursor_ioctl+0x50/0x70 
[drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281812]  drm_ioctl+0x21b/0x4c0 [drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281828]  ? drm_mode_setplane+0x1a0/0x1a0 
[drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281835]  ? _copy_to_user+0x54/0x60
  Apr 30 12:01:25 salon kernel: [ 8273.281877]  nouveau_drm_ioctl+0x74/0xc0 
[nouveau]
  Apr 30 12:01:25 salon kernel: [ 8273.281884]  do_vfs_ioctl+0xa3/0x610
  Apr 30 12:01:25 salon kernel: [ 8273.281890]  ? 
__check_object_size+0x100/0x1d7
  Apr 30 12:01:25 salon kernel: [ 8273.281895]  SyS_ioctl+0x79/0x90
  Apr 30 12:01:25 salon kernel: [ 8273.281901]  
entry_SYSCALL_64_fastpath+0x1e/0xad
  Apr 30 12:01:25 salon kernel: [ 8273.281907] RIP: 0033:0x7fa96e376987
  Apr 30 12:01:25 salon kernel: [ 8273.281911] RSP: 002b:7fa96383d338 
EFLAGS: 3246 ORIG_RAX: 0010
  Apr 30 12:01:25 salon kernel: [ 8273.281918] RAX: ffda RBX: 
559c9117f930 RCX: 7fa96e376987
  Apr 30 12:01:25 salon kernel: [ 8273.281925] RDX: 7fa96383d370 RSI: 
c01c64a3 RDI: 000e
  Apr 30 12:01:25 salon kernel: [ 8273.281931] RBP:  R08: 
559c908510c0 R09: 0780
  Apr 30 12:01:25 salon kernel: [ 8273.282266] R10: 

[Kernel-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware

[Konrad Zapałowicz]

I'm afraid that this is how the bluetoothctl is designed. This tool is a
command-line interface to the bluetoothd and requires it up and running.
It will not quit however when it is not running for a situations where
the daemon might come back online.

Ubuntu does not do anything special here, the bluetoothctl tool is
packaged as is from the upstream.

For Ubuntu this normally should not be a problem because a user is
expected to use {unity,gnome}-system-settings anyway to interact with BT
subsystem. Is there a particular use-case that is failing on this
behavior?

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

Title:
  bluetoothctl systematically hangs when there is no bluetooth hardware

Status in bluez package in Ubuntu:
  New

Bug description:
  On a machine WITH bluetooth hardware, the 'bluetoothctl' command works 
correctly.
  For example, the command 'bluetoothctl < /dev/null' terminates correctly.

  On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command 
systematically hangs.
  Even the command 'bluetoothctl < /dev/null' systematically hangs.

  $ bluetoothctl &
  [1] 6208

  $ ps -l $!
  F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTYTIME CMD
  0 T  1001  6208  2525  0  80   0 -  9578 signal pts/1  0:00 bluetoothctl

  [1]+  Stopped bluetoothctl

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr  4 20:09:39 2016
  InstallationDate: Installed on 2015-07-20 (259 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterestingModules: bluetooth
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed 
root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago)
  dmi.bios.date: 06/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  hciconfig:
   
  rfkill:
   
  syslog:
   avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)...
   avril 03 15:10:45 urbah-sirius NetworkManager[986]:   Loaded device 
plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+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 1687791] Re: Install of kdump-tools fails

[Phillip Susi]

Could you put a "set -x" at the start of the postinst file to see where
it is failing?


** Package changed: grub2 (Ubuntu) => makedumpfile (Ubuntu)

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

Title:
  Install of kdump-tools fails

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  When installing Ubuntu xenial via netimage, installation fails because
  of an error, when configuring the kdump-tools. /var/log/syslog says:

  ...

  May  2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M
  May  2 22:15:17 in-target: Setting up lxc-common (2.0.7-0ubuntu1~16.04.2) 
...^M
  May  2 22:15:17 in-target: Running in chroot, ignoring request.^M
  May  2 22:15:17 in-target: invoke-rc.d: policy-rc.d denied execution of 
reload.^M
  May  2 22:15:17 in-target: Setting up grub-gfxpayload-lists (0.7) ...^M
  May  2 22:15:17 in-target: Processing triggers for libc-bin (2.23-0ubuntu7) 
...^M
  May  2 22:15:17 in-target: Processing triggers for systemd (229-4ubuntu17) 
...^M
  May  2 22:15:17 in-target: Processing triggers for ureadahead (0.100.0-19) 
...^M
  May  2 22:15:17 in-target: Processing triggers for dbus (1.10.6-1ubuntu3.3) 
...^M
  May  2 22:15:17 in-target: Errors were encountered while processing:^M
  May  2 22:15:17 in-target:  kdump-tools^M
  May  2 22:15:17 in-target:  linux-crashdump^M
  May  2 22:15:18 in-target: E: Sub-process /usr/bin/dpkg returned an error 
code (1)
  May  2 22:15:18 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ...
  May  2 22:15:18 in-target: dpkg: error processing package kdump-tools 
(--configure):
  May  2 22:15:18 in-target:  subprocess installed post-installation script 
returned error exit status 1
  May  2 22:15:18 in-target: dpkg: dependency problems prevent configuration of 
linux-crashdump:
  May  2 22:15:18 in-target:  linux-crashdump depends on kdump-tools; however:
  May  2 22:15:18 in-target:   Package kdump-tools is not configured yet.
  May  2 22:15:18 in-target: 
  May  2 22:15:18 in-target: dpkg: error processing package linux-crashdump 
(--configure):
  May  2 22:15:18 in-target:  dependency problems - leaving unconfigured
  May  2 22:15:18 in-target: Errors were encountered while processing:
  May  2 22:15:18 in-target:  kdump-tools
  May  2 22:15:18 in-target:  linux-crashdump
  May  2 22:15:18 main-menu[616]: WARNING **: Configuring 'pkgsel' failed with 
error code 100
  May  2 22:15:18 main-menu[616]: WARNING **: Menu item 'pkgsel' failed.

  
  After this the 'Select and install software' dialog pops up and says, that 
'Installation step failed'. If one presses '', one gets bombed back 
into the 'Ubuntu installer main menu'.
  Now you get into a loop, when choosing the 'Select and install software' item 
from the menu.

  Installer image is 'Linux foo 4.4.0-62-generic #83-Ubuntu SMP Wed Jan
  18 14:10:15 UTC 2017 x86_64 GNU/Linux'.

  The only workaround found so far is:
  cp -p /target/var/lib/dpkg/info/kdump-tools.postinst \
  /target/var/lib/dpkg/info/kdump-tools.postinst.suck
  printf '#!/bin/sh\nexit 0\n' \
  >/target/var/lib/dpkg/info/kdump-tools.postinst

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1687791/+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 1687791] [NEW] Install of kdump-tools fails

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When installing Ubuntu xenial via netimage, installation fails because
of an error, when configuring the kdump-tools. /var/log/syslog says:

...

May  2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M
May  2 22:15:17 in-target: Setting up lxc-common (2.0.7-0ubuntu1~16.04.2) ...^M
May  2 22:15:17 in-target: Running in chroot, ignoring request.^M
May  2 22:15:17 in-target: invoke-rc.d: policy-rc.d denied execution of 
reload.^M
May  2 22:15:17 in-target: Setting up grub-gfxpayload-lists (0.7) ...^M
May  2 22:15:17 in-target: Processing triggers for libc-bin (2.23-0ubuntu7) 
...^M
May  2 22:15:17 in-target: Processing triggers for systemd (229-4ubuntu17) ...^M
May  2 22:15:17 in-target: Processing triggers for ureadahead (0.100.0-19) ...^M
May  2 22:15:17 in-target: Processing triggers for dbus (1.10.6-1ubuntu3.3) 
...^M
May  2 22:15:17 in-target: Errors were encountered while processing:^M
May  2 22:15:17 in-target:  kdump-tools^M
May  2 22:15:17 in-target:  linux-crashdump^M
May  2 22:15:18 in-target: E: Sub-process /usr/bin/dpkg returned an error code 
(1)
May  2 22:15:18 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ...
May  2 22:15:18 in-target: dpkg: error processing package kdump-tools 
(--configure):
May  2 22:15:18 in-target:  subprocess installed post-installation script 
returned error exit status 1
May  2 22:15:18 in-target: dpkg: dependency problems prevent configuration of 
linux-crashdump:
May  2 22:15:18 in-target:  linux-crashdump depends on kdump-tools; however:
May  2 22:15:18 in-target:   Package kdump-tools is not configured yet.
May  2 22:15:18 in-target: 
May  2 22:15:18 in-target: dpkg: error processing package linux-crashdump 
(--configure):
May  2 22:15:18 in-target:  dependency problems - leaving unconfigured
May  2 22:15:18 in-target: Errors were encountered while processing:
May  2 22:15:18 in-target:  kdump-tools
May  2 22:15:18 in-target:  linux-crashdump
May  2 22:15:18 main-menu[616]: WARNING **: Configuring 'pkgsel' failed with 
error code 100
May  2 22:15:18 main-menu[616]: WARNING **: Menu item 'pkgsel' failed.


After this the 'Select and install software' dialog pops up and says, that 
'Installation step failed'. If one presses '', one gets bombed back 
into the 'Ubuntu installer main menu'.
Now you get into a loop, when choosing the 'Select and install software' item 
from the menu.

Installer image is 'Linux foo 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18
14:10:15 UTC 2017 x86_64 GNU/Linux'.

The only workaround found so far is:
cp -p /target/var/lib/dpkg/info/kdump-tools.postinst \
/target/var/lib/dpkg/info/kdump-tools.postinst.suck
printf '#!/bin/sh\nexit 0\n' \
>/target/var/lib/dpkg/info/kdump-tools.postinst

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

-- 
Install of kdump-tools fails
https://bugs.launchpad.net/bugs/1687791
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to makedumpfile in Ubuntu.

-- 
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 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

[Joseph Salisbury]

Hmm, I just tried to boot that kernel and it came up fine.  Can you post
a screen shot or digital picture of the error you are getting?

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

Title:
  Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel.
  This issue seems to be fixed mainstream: https://lkml.org/lkml/2017/1/9/77

  
  kdump-tools 1:1.5.9-5ubuntu0.4
  makedumpfile1:1.5.9-5ubuntu0.4
  linux-image-4.8.0-46-generic4.8.0-46.49~16.04.1

  # kdump-config show

  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x2b00
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-46-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 
cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  The kernel trace

  [   10.738064] BUG: unable to handle kernel NULL pointer dereference at 
0088
  [   10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0
  [   10.743571] PGD 0
  [   10.744482] Oops:  [#1] SMP
  [   10.745615] Modules linked in:
  [   10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic 
#49~16.04.1-Ubuntu
  [   10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017
  [   10.752574] task: 8f16b2938ec0 task.stack: 8f16b294
  [   10.754892] RIP: 0010:[]  [] 
hswep_uncore_cpu_init+0x52/0xa0
  [   10.758371] RSP: 0018:8f16b2943e40  EFLAGS: 00010206
  [   10.760337] RAX: 0050 RBX:  RCX: 
238a
  [   10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: 

  [   10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 
89231a97
  [   10.767968] R10: eac07000 R11:  R12: 
89c1a030
  [   10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 
8f16b2c19300
  [   10.772894] FS:  () GS:8f16b2c0() 
knlGS:
  [   10.775945] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.777935] CR2: 0088 CR3: 2d806000 CR4: 
001406f0
  [   10.780398] Stack:
  [   10.781154]  8f16b2943e50 df388e 8f16b2943e88 
89d8b292
  [   10.884602]   0105 89d8b196 
89c0daf8
  [   10.887394]  8f16b2c19300 8f16b2943f08 88e02190 
88ea377f
  [   10.890699] Call Trace:
  [   10.891596]  [] intel_uncore_init+0xfc/0x2d6
  [   10.893587]  [ 70 
38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00
  [   11.422367] RIP  [] hswep_uncore_cpu_init+0x52/0xa0
  [   11.425174]  RSP 
  [   11.426588] CR2: 0088
  [   11.427978] ---[ end trace d8adbfe4355f5160 ]---
  [   11.430006] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.430006]
  [   11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.433354]

  Please find the full kernel trace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+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 1673564] Re: ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on

[dann frazier]

Note that, while this symptom is seemingly only reproducible with >=
4.10 (hwe-y), there is another symptom of this problem that is
reproducible with 4.4 (hwe-x). That symptom is that VMs will hang during
teardown - easily reproducible using a parallel VM start/stop test. I'll
therefore mark this as impacting >= xenial.

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

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

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

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

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

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

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

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

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

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

** Description changed:

- This is a followup of an earlier thread/bug that we have narrowed down
- to an incompatibility/issue with vhost support in qemu-efi. Without
- vhost=on qemu seems to be working fine.
+ [Impact]
+ VMs can cause interrupts to be disabled on the host CPU, resulting in hangs.
  
- I have tested several edk2 firmwares:
- - xenial
- - zesty
- - Fedora: 
ftp://195.220.108.108/linux/fedora-secondary/development/rawhide/Everything/aarch64/os/Packages/e/edk2-aarch64-20170209git296153c5-2.fc26.noarch.rpm
+ [Test Case]
+ See Comment #1.
  
- I have also tested with different guests:
- - cirros: 
https://download.cirros-cloud.net/daily/20161201/cirros-d161201-aarch64-disk.img
- - ubuntu xenial: 
https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-arm64-uefi1.img
- 
- The test steps are simple enough. A tap device is needed, qemu-kvm,
- qemu-efi need to be installed. The UEFI iamge is run as shown in the
- launch.sh script, the tap device is used in vhost=on mode.
- 
- Also note that the QEMU_EFI.fd binary needs to be padded up to 64M:
- dd if=/dev/zero of=AAVMF_CODE.fd bs=1M count=64
- dd if=QEMU_EFI.fd of=AAVMF_CODE.fd conv=notrunc
- 
- 
- The result was always the same, the node crashing with soft-lockups when qemu 
was attempting to boot the kernel.
- 
- I will attach all the relevant information shortly.
+ [Regression Risk]
+ (TBD, once proposed patches are finalized)

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

Title:
  ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with
  vhost=on

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  [Impact]
  VMs can cause interrupts to be disabled on the host CPU, resulting in hangs.

  [Test Case]
  See Comment #1.

  [Regression Risk]
  (TBD, once proposed patches are finalized)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673564/+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 1687714] Re: Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter ID)" messages

[Joseph Salisbury]

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

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

** Also affects: linux (Ubuntu Artful)
   Importance: Medium
   Status: Triaged

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

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

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

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

Title:
  Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus
  Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter
  ID)" messages

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  The kernel log is constantly filled with the following:

236.912499] pcieport :00:1c.5: AER: Corrected error received: id=00e5
  [  236.912545] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e5(Transmitter ID)
  [  236.912553] pcieport :00:1c.5:   device [8086:a115] error 
status/mask=1000/2000
  [  236.912558] pcieport :00:1c.5:[12] Replay Timer Timeout  

  This drains battery, CPU cycles and makes the kernel log unreadable.

  Adding pcie_aspm hides that:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet button.lid_init_state=open
  pcie_aspm=off"

  Present in the upstream Linux kernel (see the attachment for 4.11
  rc8).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2345 F pulseaudio
dima   4262 F pulseaudio
  Date: Tue May  2 13:34:13 2017
  InstallationDate: Installed on 2017-02-27 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd 
   Bus 001 Device 003: ID 0bda:579f Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687714/+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 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)

[JonAbrah]

KalleValo, I added you in the hopes for some insight.

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

Title:
  Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
  1535)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Update: added some forensics in the paste (a long read):
  http://paste.ubuntu.com/24118478/

  TL;DR with a bit of intuition:
  We need a new firmware-5.bin from Qualcomm Atheros for this rev 32 card in 
order to make it work well - if anybody has contacts there it would be nice to 
ask them to upload this to the upstream linux-firmware tree.

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535

  
  Original message:
  --
  I experience a very poor 802.11ac performance of a QCA6174 Wireless card 
(Killer Wireless 1535).

  This is a dev version of Zesty with a recently released 4.10 kernel:

  uname -r
  4.10.0-9-generic

  dpkg -l linux-firmware | grep ii
  ii  linux-firmware 1.163all  Firmware for Linux kernel drivers

  lspci -vvv:

  ...
  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: ath10k_pci
  Kernel modules: ath10k_pci

  -

  Testing wireless speed with RT-87U 802.11ac router shows that the
  speed is only 27.3 megabits per second which is very low for an
  802.11ac card:

  iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [  3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001
  [ ID] Interval   Transfer Bandwidth
  [  3]  0.0-10.0 sec  32.6 MBytes  27.3 Mbits/sec

  

  For comparison, on the same network (from the same distance to the
  router) I have the following result with an Intel's card (on a 4.8
  kernel, different laptop):

  UX32LN:~$ lspci | grep 7260
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  UX32LN:~$ iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001
  [ ID] Interval Transfer Bandwidth
  [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec
  administrator@UX32LN:~$ lsp
  lspci lspcmcia lspgpot

  200 Mbps is much better.

  ---

  Back to the problematic card:

  Booted 16.04.2 with the rolling HWE kernel 4.8:

  journalctl -k | grep -i ath
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( 
-> 0002)
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch 
firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 
debugfs 1 tracing 1 dfs 0 testmode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 
bmi_id N/A crc32 6fc88fe7
  Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:00.0: htt-ver 3.26 wmi-op 4 
htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
  Mar 04 18:28:34 ubuntu kernel: ath: EEPROM regdomain: 0x6c
  Mar 04 18:28:34 ubuntu kernel: ath: EEPROM indicates we should expect a 
direct regpair map
  Mar 04 18:28:34 ubuntu kernel: ath: Country alpha2 being used: 00
  Mar 04 18:28:34 ubuntu kernel: ath: Regpair used: 0x6c
  Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:00.0 wlp59s0: renamed from 
wlan0

  

[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)

[JonAbrah]

Thank AceLan, I gave it a try, but it seems that those files are the
same or older than the ones available on github.com/kvalo/ath10k-
firmware/tree/master/QCA6174 and the poor performance remains.


I also found a bug from 2015 
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1520343 , which 
seems related to this and affects a lot of other people - that bug was 
originally due to the card not being supported [which has now been fixed], but 
has developed lately with more comments into the random poor performance of the 
card under linux.  Although, the original poster to this bug has provided more 
detailed logs for a potential solution.

I think it's apparent that there's a real problem with the linux-
firmware of QCA6174 and I've personally reached a point where I'm not
sure if it's worth riding it out or to jump OS-ship.

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

Title:
  Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
  1535)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Update: added some forensics in the paste (a long read):
  http://paste.ubuntu.com/24118478/

  TL;DR with a bit of intuition:
  We need a new firmware-5.bin from Qualcomm Atheros for this rev 32 card in 
order to make it work well - if anybody has contacts there it would be nice to 
ask them to upload this to the upstream linux-firmware tree.

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535

  
  Original message:
  --
  I experience a very poor 802.11ac performance of a QCA6174 Wireless card 
(Killer Wireless 1535).

  This is a dev version of Zesty with a recently released 4.10 kernel:

  uname -r
  4.10.0-9-generic

  dpkg -l linux-firmware | grep ii
  ii  linux-firmware 1.163all  Firmware for Linux kernel drivers

  lspci -vvv:

  ...
  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: ath10k_pci
  Kernel modules: ath10k_pci

  -

  Testing wireless speed with RT-87U 802.11ac router shows that the
  speed is only 27.3 megabits per second which is very low for an
  802.11ac card:

  iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [  3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001
  [ ID] Interval   Transfer Bandwidth
  [  3]  0.0-10.0 sec  32.6 MBytes  27.3 Mbits/sec

  

  For comparison, on the same network (from the same distance to the
  router) I have the following result with an Intel's card (on a 4.8
  kernel, different laptop):

  UX32LN:~$ lspci | grep 7260
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  UX32LN:~$ iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001
  [ ID] Interval Transfer Bandwidth
  [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec
  administrator@UX32LN:~$ lsp
  lspci lspcmcia lspgpot

  200 Mbps is much better.

  ---

  Back to the problematic card:

  Booted 16.04.2 with the rolling HWE kernel 4.8:

  journalctl -k | grep -i ath
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( 
-> 0002)
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch 
firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 

[Kernel-packages] [Bug 1687714] Re: Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter ID)" messages

[Dmitrii Shcherbakov]

Joseph,

I did (the log rotated so you don't see the version number):

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687714/+attachment/4870948/+files/dmesg_pcie_aspm_rc8.log

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

Title:
  Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus
  Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter
  ID)" messages

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Incomplete

Bug description:
  The kernel log is constantly filled with the following:

236.912499] pcieport :00:1c.5: AER: Corrected error received: id=00e5
  [  236.912545] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e5(Transmitter ID)
  [  236.912553] pcieport :00:1c.5:   device [8086:a115] error 
status/mask=1000/2000
  [  236.912558] pcieport :00:1c.5:[12] Replay Timer Timeout  

  This drains battery, CPU cycles and makes the kernel log unreadable.

  Adding pcie_aspm hides that:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet button.lid_init_state=open
  pcie_aspm=off"

  Present in the upstream Linux kernel (see the attachment for 4.11
  rc8).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2345 F pulseaudio
dima   4262 F pulseaudio
  Date: Tue May  2 13:34:13 2017
  InstallationDate: Installed on 2017-02-27 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd 
   Bus 001 Device 003: ID 0bda:579f Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687714/+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 1686636] Re: outgoing tcp connections sometimes fail to be established

[Joseph Salisbury]

The script I use to build the kernels does a "git describe" on the
commit to come up with a filename.  So for this next commit:

 git describe a80db69e47d764bbcaf2fec54b1f308925e7c490
v4.11-rc3-155-ga80db69

However, that is reporting the closet tag and not the tag that contains
it.  For that the --contains option is needed:

 git describe --contains a80db69e47d764bbcaf2fec54b1f308925e7c490
v4.11-rc6~27^2~48


I built the next test kernel, up to the following commit:
a80db69e47d764bbcaf2fec54b1f308925e7c490

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1686636/a80db69e47d764bbcaf2fec54b1f308925e7c490

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  outgoing tcp connections sometimes fail to be established

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  I spend the better part of a day debugging this.

  Symptom: Outgoing connections (ssh, tcp to port 80, to port 8080) fail
  to establish about 25% of my attempts.

  I then switched the kernel from 
  linux-image-4.10.0-20-generic (zesty)
  back to
  linux-image-4.8.0-49-generic (yakkety)

  and those problems were gone. I have no iptables rules on my system.
  I'm using an e1000e over gigabit wired network.

  Attached is a tcpdump of a connection attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.8.0-49.52-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hildeb 3286 F pulseaudio
   /dev/snd/controlC1:  hildeb 3286 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Apr 27 10:42:04 2017
  HibernationDevice: RESUME=UUID=d5037585-3853-4049-a410-b17d0c104ef3
  InstallationDate: Installed on 2014-06-19 (1042 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: FUJITSU ESPRIMO E920
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=e0d7cff3-bbdd-467d-b15b-fb96697320f0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-49-generic N/A
   linux-backports-modules-4.8.0-49-generic  N/A
   linux-firmware1.164
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-03 (23 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V4.6.5.4 R1.34.0 for D3222-A1x
  dmi.board.name: D3222-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3222-A1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: C$BK02
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.34.0forD3222-A1x:bd01/08/2015:svnFUJITSU:pnESPRIMOE920:pvr:rvnFUJITSU:rnD3222-A1:rvrS26361-D3222-A1:cvnFUJITSU:ct3:cvrC$BK02:
  dmi.product.name: ESPRIMO E920
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+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 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

[goldyfruit]

I'm even not able to boot the operating system with the kernel in
comment #6.

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

Title:
  Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel.
  This issue seems to be fixed mainstream: https://lkml.org/lkml/2017/1/9/77

  
  kdump-tools 1:1.5.9-5ubuntu0.4
  makedumpfile1:1.5.9-5ubuntu0.4
  linux-image-4.8.0-46-generic4.8.0-46.49~16.04.1

  # kdump-config show

  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x2b00
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-46-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 
cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  The kernel trace

  [   10.738064] BUG: unable to handle kernel NULL pointer dereference at 
0088
  [   10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0
  [   10.743571] PGD 0
  [   10.744482] Oops:  [#1] SMP
  [   10.745615] Modules linked in:
  [   10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic 
#49~16.04.1-Ubuntu
  [   10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017
  [   10.752574] task: 8f16b2938ec0 task.stack: 8f16b294
  [   10.754892] RIP: 0010:[]  [] 
hswep_uncore_cpu_init+0x52/0xa0
  [   10.758371] RSP: 0018:8f16b2943e40  EFLAGS: 00010206
  [   10.760337] RAX: 0050 RBX:  RCX: 
238a
  [   10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: 

  [   10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 
89231a97
  [   10.767968] R10: eac07000 R11:  R12: 
89c1a030
  [   10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 
8f16b2c19300
  [   10.772894] FS:  () GS:8f16b2c0() 
knlGS:
  [   10.775945] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.777935] CR2: 0088 CR3: 2d806000 CR4: 
001406f0
  [   10.780398] Stack:
  [   10.781154]  8f16b2943e50 df388e 8f16b2943e88 
89d8b292
  [   10.884602]   0105 89d8b196 
89c0daf8
  [   10.887394]  8f16b2c19300 8f16b2943f08 88e02190 
88ea377f
  [   10.890699] Call Trace:
  [   10.891596]  [] intel_uncore_init+0xfc/0x2d6
  [   10.893587]  [ 70 
38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00
  [   11.422367] RIP  [] hswep_uncore_cpu_init+0x52/0xa0
  [   11.425174]  RSP 
  [   11.426588] CR2: 0088
  [   11.427978] ---[ end trace d8adbfe4355f5160 ]---
  [   11.430006] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.430006]
  [   11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.433354]

  Please find the full kernel trace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+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 1688136] Re: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Vague Entertainment]

Issue was resolved by using the command line,

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happened when trying to update the system.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  benjamin   4875 F pulseaudio
   /dev/snd/controlC0:  benjamin   4875 F pulseaudio
  Date: Wed May  3 16:12:14 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-02-20 (72 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 002: ID 1b1c:1b05 Corsair 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=54b52bae-5cbf-432f-9cb8-5f570785a7e8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (64 days ago)
  dmi.bios.date: 02/02/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13RSA1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: orxp1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Oryx Pro
  dmi.product.version: orxp1
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688136/+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 1684010] Re: 17.04, i915 freeze on VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

[Joseph Salisbury]

Can you next test 4.10.0-17:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/12396981

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

Title:
  17.04, i915 freeze on VGA compatible controller: Intel Corporation
  Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just freezes all unity and/or X.
  Nothing in any logs though.

  16.10 worked just fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684010/+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 1688136] Re: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

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

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

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happened when trying to update the system.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  benjamin   4875 F pulseaudio
   /dev/snd/controlC0:  benjamin   4875 F pulseaudio
  Date: Wed May  3 16:12:14 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-02-20 (72 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 002: ID 1b1c:1b05 Corsair 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Oryx Pro
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=54b52bae-5cbf-432f-9cb8-5f570785a7e8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (64 days ago)
  dmi.bios.date: 02/02/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13RSA1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: orxp1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Oryx Pro
  dmi.product.version: orxp1
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688136/+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 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

[Joseph Salisbury]

Commit 3b7f05cbced4 is in the Ubuntu-4.4.0-77 kernel.  Can you test that
kernel to confirm it resolves this 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/1679898

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  

[Kernel-packages] [Bug 1687718] Re: linux: 3.13.0-119.166 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 3.13.0-119.166 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1687719
  derivatives:
  kernel-stable-phase-changed:Wednesday, 03. May 2017 12:31 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1687718/+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 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

[Joseph Salisbury]

So you still hit the bug with the test kernel posted in comment #6?

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

Title:
  Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel.
  This issue seems to be fixed mainstream: https://lkml.org/lkml/2017/1/9/77

  
  kdump-tools 1:1.5.9-5ubuntu0.4
  makedumpfile1:1.5.9-5ubuntu0.4
  linux-image-4.8.0-46-generic4.8.0-46.49~16.04.1

  # kdump-config show

  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x2b00
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-46-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 
cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  The kernel trace

  [   10.738064] BUG: unable to handle kernel NULL pointer dereference at 
0088
  [   10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0
  [   10.743571] PGD 0
  [   10.744482] Oops:  [#1] SMP
  [   10.745615] Modules linked in:
  [   10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic 
#49~16.04.1-Ubuntu
  [   10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017
  [   10.752574] task: 8f16b2938ec0 task.stack: 8f16b294
  [   10.754892] RIP: 0010:[]  [] 
hswep_uncore_cpu_init+0x52/0xa0
  [   10.758371] RSP: 0018:8f16b2943e40  EFLAGS: 00010206
  [   10.760337] RAX: 0050 RBX:  RCX: 
238a
  [   10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: 

  [   10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 
89231a97
  [   10.767968] R10: eac07000 R11:  R12: 
89c1a030
  [   10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 
8f16b2c19300
  [   10.772894] FS:  () GS:8f16b2c0() 
knlGS:
  [   10.775945] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.777935] CR2: 0088 CR3: 2d806000 CR4: 
001406f0
  [   10.780398] Stack:
  [   10.781154]  8f16b2943e50 df388e 8f16b2943e88 
89d8b292
  [   10.884602]   0105 89d8b196 
89c0daf8
  [   10.887394]  8f16b2c19300 8f16b2943f08 88e02190 
88ea377f
  [   10.890699] Call Trace:
  [   10.891596]  [] intel_uncore_init+0xfc/0x2d6
  [   10.893587]  [ 70 
38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00
  [   11.422367] RIP  [] hswep_uncore_cpu_init+0x52/0xa0
  [   11.425174]  RSP 
  [   11.426588] CR2: 0088
  [   11.427978] ---[ end trace d8adbfe4355f5160 ]---
  [   11.430006] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.430006]
  [   11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.433354]

  Please find the full kernel trace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+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 1686305] Re: Merlin SGMII fail on Ubuntu Xenial HWE kernel

[Joseph Salisbury]

Yes, I will request that in the SRU request.

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

Title:
  Merlin SGMII fail on Ubuntu Xenial HWE kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Using the Ubuntu Xenial HWE installation image at 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial-updates/main/installer-arm64/current/images/hwe-netboot
 to install Ubuntu into the Merlin board, the SGMII port is fail to get IP from 
DHCP.
  After installation, booting into Linux prompt, the SGMII port is fail to get 
IP from DHCP also. Checking with ethtool, the link is always report down.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 11  2016 seq
   crw-rw 1 root audio 116, 33 Feb 11  2016 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2aa90b24-e14e-4854-b52b-b853388a3466
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Merlin Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=8e10d908-38aa-4cb4-990c-4a9bcabc51a4 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-49-generic N/A
   linux-backports-modules-4.8.0-49-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-49-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: Oct 17 2016
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.06.25
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Merlin Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.06.25:bdOct172016:svnAppliedMicro:pnX-GeneMerlinBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMerlinBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Merlin Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 11  2016 seq
   crw-rw 1 root audio 116, 33 Feb 11  2016 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2aa90b24-e14e-4854-b52b-b853388a3466
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Merlin Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=8e10d908-38aa-4cb4-990c-4a9bcabc51a4 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-49-generic N/A
   linux-backports-modules-4.8.0-49-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-49-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: Oct 17 2016
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.06.25
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Merlin Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  

[Kernel-packages] [Bug 1687714] Re: Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter ID)" messages

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8

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

Title:
  Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus
  Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter
  ID)" messages

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Incomplete

Bug description:
  The kernel log is constantly filled with the following:

236.912499] pcieport :00:1c.5: AER: Corrected error received: id=00e5
  [  236.912545] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e5(Transmitter ID)
  [  236.912553] pcieport :00:1c.5:   device [8086:a115] error 
status/mask=1000/2000
  [  236.912558] pcieport :00:1c.5:[12] Replay Timer Timeout  

  This drains battery, CPU cycles and makes the kernel log unreadable.

  Adding pcie_aspm hides that:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet button.lid_init_state=open
  pcie_aspm=off"

  Present in the upstream Linux kernel (see the attachment for 4.11
  rc8).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2345 F pulseaudio
dima   4262 F pulseaudio
  Date: Tue May  2 13:34:13 2017
  InstallationDate: Installed on 2017-02-27 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd 
   Bus 001 Device 003: ID 0bda:579f Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687714/+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 1686156] Re: linux-lts-trusty: 3.13.0-118.165~precise1 -proposed tracker

[Thadeu Lima de Souza Cascardo]

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

** This bug has been marked a duplicate of bug 1687719
   linux-lts-trusty: 3.13.0-119.166~precise1 -proposed tracker

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

Title:
  linux-lts-trusty: 3.13.0-118.165~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1686154
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686156/+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 1687719] Re: linux-lts-trusty: 3.13.0-119.166~precise1 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1687718
  phase: Packaging

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1687718
  phase: Packaging
+ kernel-stable-phase-changed:Thursday, 04. May 2017 17:18 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1687718
- phase: Packaging
- kernel-stable-phase-changed:Thursday, 04. May 2017 17:18 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux-lts-trusty: 3.13.0-119.166~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1687718
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1687719/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[spike speigel]

** Tags added: zesty

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Kernel-packages] [Bug 1686048] Re: Touchpad not detected on Lenovo S21e-20

[Rob van den Berg]

I tested with the parameters one by one but it made no difference.
Touchpad isn't detected

2017-05-04 6:50 GMT+02:00 Kai-Heng Feng :

> Can you test these kernel parameter, one by one:
> i8042.nomux=1
> i8042.reset=1
> i8042.noloop=1
> i8042.kbdreset=1
> i8042.nopnp=1
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1686048
>
> Title:
>   Touchpad not detected on Lenovo S21e-20
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1686048/+subscriptions
>

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

Title:
  Touchpad not detected on Lenovo S21e-20

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  xinput list
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳  USB OPTICAL MOUSEid=9[slave  pointer  (2)]
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)]
  ↳ Power Button  id=8[slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)]
  ↳ Lenovo EasyCamera

  cat /proc/bus/input/devices 
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2
   
  B: PROP=0 
   
  B: EV=3   
   
  B: KEY=10 0   
   

   
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=15d9 Product=0a4c Version=0111
  N: Name=" USB OPTICAL MOUSE"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:15D9:0A4C.0001/input/input5
  U: Uniq=
  H: Handlers=mouse0 event5 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=103
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input6
  U: Uniq=
  H: Handlers=event6 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Front Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input7
  U: Uniq=
  H: Handlers=event7 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input8
  U: Uniq=
  H: Handlers=event8 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0003 Vendor=5986 Product=0674 Version=4207
  N: Name="Lenovo EasyCamera"
  P: Phys=usb-:00:14.0-3/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/input/input9
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

[goldyfruit]

@Thiago, yes I confirm.

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49, xenial-hwe)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+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 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[David Bierce]

4.10.0-20-generic #22+lp1674838v201705030839
fry:~$ uptime
 11:27:04 up 16:20,  2 users,  load average: 13.48, 14.59, 16.62

No crash, previous crashes would appear within an hour with lighter load
and memory pressure.  Seth's thesis on the back port seems to be
correct.

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

[Thiago Martins]

@goldyfruit, can you confirm if it also fixes the BUG:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1685742 ?

Thanks!

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49, xenial-hwe)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+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 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[kiney]

No crash after more than 23 hours uptime with 4.10.0-20-generic
#22+lp1674838v201705030839.

With the normal ubuntu 4.10 the system crashes every few hours. So I can
confirm the bug is probably fixed in the kernel from ~sforshee

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1686976] wright-kernel (arm64) - tests ran: 16, failed: 0

[Brad Figg]

tests ran:  16, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/wright-kernel__4.8.0-52.55__2017-05-04_15-22-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1686978
  derivatives: 1686979
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+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 1664602] Re: Using an NVMe drive causes huge power drain

[Dmitry Gutov]

I'm pretty sure this is not the first time a power-saving feature breaks
some subset of hardware. Why even add it in a bugfix update?

After applying the workaround from LP#1678184, I'm happy about the
somewhat improved battery life, but I'll never get back the several
hours it took to figure out what's going on, and considering whether I
should contact Dell support about my failing storage device (which
wouldn't have helped, but would probably have wasted several weeks on
top of that).

And I'm still on 16.10. Why was this even released in Yakkety, with
LP#1678184 having been reported on March 31?

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

Title:
  Using an NVMe drive causes huge power drain

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  PCIe NVMe drives are very common in new laptops. The Zesty's kernels 
(including latest 4.10 rc8 from CKT PPA) does not support APST (autonomous 
power state transitions). A patch does exist :
  http://lists.infradead.org/pipermail/linux-nvme/2017-February/008051.html
  https://github.com/damige/linux-nvme

  It seems that we cannot expect this before kernel 4.11.

  Additionally my laptop CPU does never go under PC3 power saving state, 
powertop says. I don't know if it's related.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ft 1900 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=a04b55bf-b1b6-464c-88ce-44b6adbbbc10
  InstallationDate: Installed on 2016-12-12 (63 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=0d1f213e-73a9-4097-ae64-9cd963cfba23 ro quiet
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-8-generic N/A
   linux-backports-modules-4.10.0-8-generic  N/A
   linux-firmware1.163
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.5
  dmi.board.name: 0YH43H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.5:bd12/22/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0YH43H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602/+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 1688296] Re: Azure: update configs based on Zesty 4.10.0-21.23

[Stefan Bader]

** Description changed:

+ SRU Justification:
+ 
+ Impact: As Zesty/17.04 was not released at the time of the last rebase,
+ there have been multiple changes to the kernel config in debian.master.
+ To simplify  future rebases and minimize the configuration delta between
+ the zesty and the azure kernel we need to sync the config settings.
+ 
+ Fix: Follow changes made to the configuration in debian.master and apply
+ them to debian.azure.
+ 
+ NOTE: This report is to track changes made to the azure custom kernel
+ which cannot be correctly represented in launchpad.
+ 
+ ---
+ 
  We need to update the debian.azure/ directory based on the
  debian.master/ directory from Zesty.

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

** Changed in: linux (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

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

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

Title:
  Azure: update configs based on Zesty 4.10.0-21.23

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: As Zesty/17.04 was not released at the time of the last
  rebase, there have been multiple changes to the kernel config in
  debian.master. To simplify  future rebases and minimize the
  configuration delta between the zesty and the azure kernel we need to
  sync the config settings.

  Fix: Follow changes made to the configuration in debian.master and
  apply them to debian.azure.

  NOTE: This report is to track changes made to the azure custom kernel
  which cannot be correctly represented in launchpad.

  ---

  We need to update the debian.azure/ directory based on the
  debian.master/ directory from Zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688296/+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 1686976] wright-kernel (arm64) - tests ran: 141, failed: 0

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/wright-kernel__4.8.0-52.55__2017-05-04_13-42-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1686978
  derivatives: 1686979
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

[goldyfruit]

Downgraded to 4.4 series. :(

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49, xenial-hwe)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+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 1688259] Re: kernel-wedge fails in artful due to leftover squashfs-modules d-i files

[Seth Forshee]

** Also affects: linux (Ubuntu Artful)
   Importance: High
 Assignee: Seth Forshee (sforshee)
   Status: In Progress

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

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

** Changed in: linux (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: linux (Ubuntu Artful)
   Status: In Progress => Fix Committed

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

Title:
  kernel-wedge fails in artful due to leftover squashfs-modules d-i
  files

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Committed

Bug description:
  We no longer produce a squashfs-modules udeb, but some of the d-i
  files remain in the tree, all of which include another file which has
  been removed. kernel-wedge in artful is choking on these files. Since
  we don't use them anymore they should be removed.

  We also need to tell consumers of squashfs-modules that this is
  provided by the kernel so they do not have to remove their
  dependencies on it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688259/+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 1688162] Re: dmidecode should print diagnostic messages to stderr

[ChristianEhrhardt]

Hi Jens, we usually try to keep dmidecode without Delta to Debian.
For the SRUs Delta is fine and as I said if no one helps I can try to assist 
here.
If you want to volunteer there is also the USBSD [1] where new people are 
guided to help themselfe and the community.

For the current release it would be great if Debian would pick that up
and we coudl sync into Artful. Would you mind opening a Debian bug about
moving to the current release (preferred) or at least picking this
patch? Afterwards link the bug info here - that would be great.

[1]: https://wiki.ubuntu.com/ServerTeam/BugSquashingDay

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

Title:
  dmidecode should print diagnostic messages to stderr

Status in dmidecode package in Ubuntu:
  Triaged

Bug description:
  Ubuntu version of dmidecode breaks several scripts because it prints
  diagnostics messages to stdout instead of stderr.

  E.g.: sudo /bin/ksh93
  # /usr/sbin/dmidecode -s baseboard-manufacturer 2>/dev/null
  Supermicro
  Invalid entry length (16). Fixed up to 11.

  
  The original version (https://git.savannah.nongnu.org/git/dmidecode.git) 
however, works as expected:
  # /tmp/dmidecode -s baseboard-manufacturer 2>/dev/null
  Supermicro

  
  $ /usr/bin/lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  Codename: xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1688162/+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 1688296] [NEW] Azure: update configs based on Zesty 4.10.0-21.23

[Marcelo Cerri]

Public bug reported:

We need to update the debian.azure/ directory based on the
debian.master/ directory from Zesty.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Marcelo Cerri (mhcerri)
 Status: Fix Committed


** Tags: linux-azure

** Changed in: linux (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Azure: update configs based on Zesty 4.10.0-21.23

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  We need to update the debian.azure/ directory based on the
  debian.master/ directory from Zesty.

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

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

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Bram Biesbrouck]

Ah, cool, didn't know that, thanks!

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  New

Bug description:
  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx timeout
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:09 ubuntu kernel: usb 4-1.2: reset SuperSpeed USB device number 
3 using xhci_hcd

  I can't seem to make this bug appear with any other type of USB
  traffic. I've reported it to the realtek kernel dev team and they
  don't think their RTL8153 driver (in this case the r8152 module) is to
  blame, but instead that it's an xhci_hcd 

[Kernel-packages] [Bug 1686788] Re: External displays disabled after login - regression in 4.4.0-72.93 -> 4.4.0-75.96 update

[Hannu Koivisto]

I have linux-image-extra-${ver}-generic for each normal Ubuntu linux-
image-${ver}-generic package.

There are no linux-image-extra packages for upstream kernels in
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.*/

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

Title:
  External displays disabled after login - regression in 4.4.0-72.93 ->
  4.4.0-75.96 update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With Dell E7440 with Intel graphics, attached to dock and also two
  external displays connected to the dock:

  when I boot the machine, the built-in display and the external
  displays are enabled in login screen. However, the external displays
  are disabled when I log in.

  All displays remain enabled after login with 4.4.0-72.93. I never
  installed 4.4.0-73.94 or 4.4.0-74.95 but I can see in the changelog
  that there were i915 changes in 4.4.0-73.94.

  The external displays are shown and are marked enabled in KDE's System
  Settings / Display and Monitor / Display Configuration. If I first
  mark them disabled (and apply the configuration) and then mark them
  enabled (and apply the configuration), they are actually enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-75-generic 4.4.0-75.96
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hannuko2338 F pulseaudio
   /dev/snd/controlC0:  hannuko2338 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Apr 27 19:39:12 2017
  HibernationDevice: RESUME=UUID=43dbb372-1944-40d4-b1ea-94193bf0bbb2
  InstallationDate: Installed on 2015-12-21 (493 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Latitude E7440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-75-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-12-30 (117 days ago)
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 07F3F4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686788/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

[UBUNTU user]

confirm issue on UBUNTU 16.04 with pulseaudio 8.0
Vahid Mardani's script is a valid temporary workaround by running it every time 
the bug appear

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1688259] Re: kernel-wedge fails in artful due to leftover squashfs-modules d-i files

[Seth Forshee]

** Description changed:

  We no longer produce a squashfs-modules udeb, but some of the d-i files
  remain in the tree, all of which include another file which has been
  removed. kernel-wedge in artful is choking on these files. Since we
  don't use them anymore they should be removed.
+ 
+ We also need to tell consumers of squashfs-modules that this is provided
+ by the kernel so they do not have to remove their dependencies on 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/1688259

Title:
  kernel-wedge fails in artful due to leftover squashfs-modules d-i
  files

Status in linux package in Ubuntu:
  In Progress

Bug description:
  We no longer produce a squashfs-modules udeb, but some of the d-i
  files remain in the tree, all of which include another file which has
  been removed. kernel-wedge in artful is choking on these files. Since
  we don't use them anymore they should be removed.

  We also need to tell consumers of squashfs-modules that this is
  provided by the kernel so they do not have to remove their
  dependencies on it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688259/+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 1688259] [NEW] kernel-wedge fails in artful due to leftover squashfs-modules d-i files

[Seth Forshee]

Public bug reported:

We no longer produce a squashfs-modules udeb, but some of the d-i files
remain in the tree, all of which include another file which has been
removed. kernel-wedge in artful is choking on these files. Since we
don't use them anymore they should be removed.

We also need to tell consumers of squashfs-modules that this is provided
by the kernel so they do not have to remove their dependencies on it.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

Title:
  kernel-wedge fails in artful due to leftover squashfs-modules d-i
  files

Status in linux package in Ubuntu:
  In Progress

Bug description:
  We no longer produce a squashfs-modules udeb, but some of the d-i
  files remain in the tree, all of which include another file which has
  been removed. kernel-wedge in artful is choking on these files. Since
  we don't use them anymore they should be removed.

  We also need to tell consumers of squashfs-modules that this is
  provided by the kernel so they do not have to remove their
  dependencies on it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688259/+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 1684010] Re: 17.04, i915 freeze on VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

[sles]

There is no problem in 4.10.0-14 .
What should we test now?
Thank you!

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

Title:
  17.04, i915 freeze on VGA compatible controller: Intel Corporation
  Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just freezes all unity and/or X.
  Nothing in any logs though.

  16.10 worked just fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684010/+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 1686976] wright-kernel (arm64) - tests ran: 64, failed: 2

[Brad Figg]

tests ran:  64, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/wright-kernel__4.8.0-52.55__2017-05-04_12-24-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1686978
  derivatives: 1686979
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+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 1685792] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From ranjs...@in.ibm.com 2017-05-04 09:01 EDT---
(In reply to comment #10)
> I built a test kernel with these four patches.  The test kernel can be
> downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1685792/

I have verified that the CPU-Hotplug functions correctly on this kernel
on a  machine booted with upstream skiboot.

It can be observed that the CPUs were put into stop1 on a hotplug.

root@ubuntu:/home/ego# dmesg | grep -i "deep" | grep stop
[0.702036] cpuidle-powernv: Deepest stop: psscr = 
0x00300331,mask=0x003003ff
[0.702185] cpuidle-powernv: Requested Level (RL) value of first deep stop = 
0xf


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

Title:
  Offlined CPUs of a core fail to come up online on POWER9 DD1 (Ubuntu
  17.04)

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ranjal G. Shenoy  - 2017-04-20 08:29:13 
==
  Power9 DD1 has a hardware issue due to which  in core whose all threads are 
offlined , when any of the CPUs are onlined, they come online with an incorrect 
PACA thereby resulting in a crash.

  The following fixes sent upstream need to applied to the 17.04 kernel
  to get CPU-Hotplug working correctly on a Power9 DD1 system.

  1) powerpc/linux.git next, commit a7cd88da9704 ("powernv: Move CPU-
  Offline idle state invocation from smp.c to idle.c").

  2) powerpc/linux.git next, the commit 900612315788
  ("powerpc/powernv/smp: Add busy-wait loop as fall back for CPU-
  Hotplug").

  3) powerpc/linux.git, commit f3b3f28493d932 ("powerpc/powernv/idle:
  Don't override default/deepest directly in kernel").

  4) powerpc/linux.git next, commit 17ed4c8f81da ("powerpc/powernv:
  Recover correct PACA on wakeup from a stop on P9 DD1").

  These patches have been backported onto the 17.04 Kernel tagged
  Ubuntu-4.10.0-19.21.

  == Comment: #1 - Ranjal G. Shenoy  - 2017-04-20
  08:29:54 ==

  
  == Comment: #2 - Ranjal G. Shenoy  - 2017-04-20 08:30:37 
==

  
  == Comment: #3 - Ranjal G. Shenoy  - 2017-04-20 08:31:15 
==

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1685792/+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 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

[Dave]

Fix released in what version?

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

Title:
  connection flood to port 445 on mounting cifs volume under kernel

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is identical to the bug reported on the Debian kernel list, only
  I'm running 4.4.0, not 4.[89].0

  After about 15 mintues, the cifsd daemon starts flooding echo requests
  on port 445 to the windows server causing a constant 1MB/s load
  (around 10,000 packets per second) that eventually leads to system
  instability that forces a reboot to correct.  This is repeatable and
  as far as I know started about a week ago (possibly with the
  installation of 4.4.0-75).

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856843

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1686099/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

[H.-Dirk Schmitt]

@martinx - To mitigate the problem I've dropped temporally jumbo frames
from the configuration of my servers.

Hopefully the bug will be fixed also for xenial-hwe and not only for
yakkety ;-)

I agree that this is a *blocker* for xenial.

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49, xenial-hwe)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+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 1686976] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 13, failed: 1

[Brad Figg]

tests ran:  13, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/ms10-35-mcdivittB0-kernel__4.8.0-52.55__2017-05-04_12-22-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1686978
  derivatives: 1686979
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+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 1679962] Re: psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.

[slimbook]

Sorry, "Hantick"

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

Title:
  psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost
  synchronization, throwing 3 bytes away.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  353/5000
  Hello,
  Randomly the touchpad pointer moves to one end of the screen, and we have 
found that when it does message appears in dmseg:

  psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost
  synchronization, throwing 3 bytes away.

  Sometimes it happens after 10 minutes of use, sometimes it happens after 3 or 
4 hours.
  We have tested several computers with touchpad "Hantick", that use the both, 
the evdev library and the libinput library. It always happens randomly.

  Thanks,

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-45-generic 4.8.0-45.48
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alejandrolopez   1678 F pulseaudio
   /dev/snd/controlC1:  alejandrolopez   1678 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr  5 09:39:01 2017
  HibernationDevice: RESUME=UUID=49104028-270a-4546-b219-b38918f339ba
  InstallationDate: Installed on 2016-04-30 (339 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SLIMBOOK 
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic.efi.signed 
root=UUID=d9619f09-3283-4f88-a9aa-a614f1b40470 ro elevator=noop quiet 
i8042.noloop i8042.notimeout i8042.nomux psmouse.resolution=1200 
psmouse.resetafter=1 psmouse.rate=50 mousedev.xres=1900 mousedev.yres=800 
i8042.reset plymouth:debug drm.debug=0xe
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-45-generic N/A
   linux-backports-modules-4.8.0-45-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-11-10 (145 days ago)
  dmi.bios.date: 11/21/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: h
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 
  dmi.board.vendor: SLIMBOOK
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SLIMBOOK
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrh:bd11/21/2014:svnSLIMBOOK:pn:pvr1.0:rvnSLIMBOOK:rn:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion:
  dmi.product.name: 
  dmi.product.version: 1.0
  dmi.sys.vendor: SLIMBOOK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679962/+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 1687623] Re: linux-4.4.0-77.98 was a phased update in -updates only and may become partially installed (was: 4.4.0-77-generic breaks internet on 16.04.2)

[Mark]

Thanks for the fix Stefan! If I wasn't on dual-boot it would have been a
nightmare trying to fix it without internet.

I had no issue with screen resolution so I suppose not everyone is
affected in the same way.

Maybe ubuntu admins could post an announce on the home page of the forum
to warn users?

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

Title:
  linux-4.4.0-77.98 was a phased update in -updates only and may become
  partially installed (was: 4.4.0-77-generic breaks internet on 16.04.2)

Status in linux package in Ubuntu:
  In Progress
Status in update-manager package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress
Status in update-manager source package in Xenial:
  Confirmed

Bug description:
  Hi as per title today I updated to  4.4.0-77-generic on my Lubuntu
  16.04.02 and wifi is not working anymore. When I click on the network
  manager I see "enable networking" (which is toggled) but no more the
  option about wifi.

  I reported this on ubuntuforum:
  https://ubuntuforums.org/showthread.php?t=2360216

  Where a user suggested to revert to an older kernel and see if this
  fixes the problem. I managed to revert to 4.4.0-75-generic via grub
  and everything works perfectly.

  Another user reported a similar issue caused by the same upgrade on
  the same system: https://ubuntuforums.org/showthread.php?t=2360215

  Can someone else confirm this bug?

  If you need more information I will be happy to provide it (I am a
  newbie though so please be patient).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687623/+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 1687623] Re: linux-4.4.0-77.98 was a phased update in -updates only and may become partially installed (was: 4.4.0-77-generic breaks internet on 16.04.2)

[Jos]

@Bryan Smith Sorry Bryan I should have been clearer. It is usual when
updating/upgrading via the terminal to start with

sudo apt-get update

this downloads the most recent list of packages from the repo, followed
by

sudo apt-get dist-upgrade

Apologies for any confusion I may have caused.

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

Title:
  linux-4.4.0-77.98 was a phased update in -updates only and may become
  partially installed (was: 4.4.0-77-generic breaks internet on 16.04.2)

Status in linux package in Ubuntu:
  In Progress
Status in update-manager package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress
Status in update-manager source package in Xenial:
  Confirmed

Bug description:
  Hi as per title today I updated to  4.4.0-77-generic on my Lubuntu
  16.04.02 and wifi is not working anymore. When I click on the network
  manager I see "enable networking" (which is toggled) but no more the
  option about wifi.

  I reported this on ubuntuforum:
  https://ubuntuforums.org/showthread.php?t=2360216

  Where a user suggested to revert to an older kernel and see if this
  fixes the problem. I managed to revert to 4.4.0-75-generic via grub
  and everything works perfectly.

  Another user reported a similar issue caused by the same upgrade on
  the same system: https://ubuntuforums.org/showthread.php?t=2360215

  Can someone else confirm this bug?

  If you need more information I will be happy to provide it (I am a
  newbie though so please be patient).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687623/+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 1686976] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 141, failed: 0

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/ms10-35-mcdivittB0-kernel__4.8.0-52.55__2017-05-04_11-08-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1686978
  derivatives: 1686979
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+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 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware

[Etienne URBAH]

With bluez version 5.43-0ubuntu1 from Ubuntu 17.04 (Zesty), the issue is
still there :

The command 'bluetoothctl' displays 'Waiting to connect to
bluetoothd...', then hangs.


** Tags added: zesty

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

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

Title:
  bluetoothctl systematically hangs when there is no bluetooth hardware

Status in bluez package in Ubuntu:
  New

Bug description:
  On a machine WITH bluetooth hardware, the 'bluetoothctl' command works 
correctly.
  For example, the command 'bluetoothctl < /dev/null' terminates correctly.

  On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command 
systematically hangs.
  Even the command 'bluetoothctl < /dev/null' systematically hangs.

  $ bluetoothctl &
  [1] 6208

  $ ps -l $!
  F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTYTIME CMD
  0 T  1001  6208  2525  0  80   0 -  9578 signal pts/1  0:00 bluetoothctl

  [1]+  Stopped bluetoothctl

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr  4 20:09:39 2016
  InstallationDate: Installed on 2015-07-20 (259 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterestingModules: bluetooth
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed 
root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago)
  dmi.bios.date: 06/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  hciconfig:
   
  rfkill:
   
  syslog:
   avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)...
   avril 03 15:10:45 urbah-sirius NetworkManager[986]:   Loaded device 
plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+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 1686976] wright-kernel (arm64) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/wright-kernel__4.8.0-52.55__2017-05-04_11-47-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1686978
  derivatives: 1686979
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Tekkla]

@kaihengfeng: GA-AB350-Gaming3 is affected too.

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1510570] Re: Bluetooth LE pairing fail

[Robie Basak]

Adding a task for Xenial as requested on IRC. But note that I haven't
looked into the details of the proposed fix - in particular checking for
and understanding any proposed change in behaviour for Xenial users. So
please don't take this as a +1 from ~ubuntu-sru. Before accepting this
SRU, please consider whether the proposed fix is appropriate from
scratch.

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

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

Title:
  Bluetooth LE pairing fail

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  New

Bug description:
  [Impact]

  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.

  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.

  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.

  [Original Report]

  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.

  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

  [Test Case]

  Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option.
  Remove file 50-bluetooth-hci-auto-poweron.rules located in
  /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be
  powered off now.

  [Regression Potential]

  Cannot think of any

  [Other Info]

  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+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 1656259] Re: Linux ZFS port doesn't respect RLIMIT_FSIZE

[Colin Ian King]

This was also fixed in Zesty with the kernel 4.10.0-9.11

commit d177712eb2130b8c53f9d4fd9b5b756b70fc4f35
Author: Colin Ian King 
Date:   Thu Feb 16 10:36:16 2017 +

UBUNTU: SAUCE: (noup) Update spl to 0.6.5.9-1, zfs to 0.6.5.9-2

Signed-off-by: Colin Ian King 
Signed-off-by: Tim Gardner 


** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  Linux ZFS port doesn't respect RLIMIT_FSIZE

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in zfs-linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in zfs-linux source package in Zesty:
  Fix Released

Bug description:
  == SRU Request, Yakkety, Xenial ==

  bash -c 'ulimit -f 1024; yes | head -n2097152'
  >/path/on/filesystem/under/test

  On ext4, this test case prints something along the lines of:

    bash: line 1: 11274 Broken pipe yes
     11275 File size limit exceeded(core dumped) | head -n2097152

  On ZFS, this test case incorrectly exits zero with no output,
  demonstrating that ZFS does not respect RLIMIT_FSIZE.

  I asked a friend to run this on Solaris 5.10 and FreeBSD 10.0-CURRENT,
  and on those systems this test case correctly generates SIGXFSZ; so it
  seems that this is a bug in the Linux port of ZFS.

  (This was discovered while tracking down Launchpad test suite failures
  under LXD on ZFS.  Launchpad uses RLIMIT_FSIZE in one place to guard
  against bugs that cause debdiff to generate arbitrarily large amounts
  of output and fill the disk.)

  == Fix ==

  Upstream fix
  
https://github.com/behlendorf/zfs/commit/230c03e59d3d13d9b60125f73cf3fff327b45c21

  == Test case ==

  With the fix:

  bash -c 'ulimit -f 1024; yes | head -n2097152'
  >/path/on/filesystem/under/test

  should report:

bash: line 1: 11274 Broken pipe yes
 11275 File size limit exceeded(core dumped) | head -n2097152

  == Regression Potential ==

  Could break read/writes semantics to zfs

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 13 10:01:36 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=139ad421-b014-4c34-ae8c-dd1d15205875
  InstallationDate: Installed on 2013-03-01 (1413 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1)
  MachineType: LENOVO 20BXCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed 
root=UUID=12c52021-a1ab-4984-9dd7-63cf0dcaac16 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET49WW (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1656259/+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 1325560] Re: kvm virtio netdevs lose network connectivity under "enough" load

[Daniel V . Lühr Sierra]

Hi, I'm experiencing similar issues in (x)ubuntu xenial. Is this bug
still present in 16.04?

Thanks

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

Title:
  kvm virtio netdevs lose network connectivity under "enough" load

Status in libvirt:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu-kvm package in Ubuntu:
  Incomplete

Bug description:
  Networking breaks after awhile in kvm guests using virtio networking.
  We run data intensive jobs on our virtual cluster (OpenStack Grizzly
  Installed on Ubuntu 12.04 Server).  The job runs fine on a single
  worker VM (no data transfer involved). As soon as I add more nodes
  where the workers need to exchange some data, one of the worker VM
  goes down. Ping responds with 'host unreachable'. Logging in via the
  serial console shows no problems: eth0 is up, can ping the local host,
  but no outside connectivity. Restart the network
  (/etc/init.d/networking restart) does nothing. Reboot the machine and
  it comes alive again.

  14/06/01 18:30:06 INFO YarnClientClusterScheduler: 
YarnClientClusterScheduler.postStartHook done
  14/06/01 18:30:06 INFO MemoryStore: ensureFreeSpace(190758) called with 
curMem=0, maxMem=308713881
  14/06/01 18:30:06 INFO MemoryStore: Block broadcast_0 stored as values to 
memory (estimated size 186.3 KB, free 294.2 MB)
  14/06/01 18:30:06 INFO FileInputFormat: Total input paths to process : 1
  14/06/01 18:30:06 INFO NetworkTopology: Adding a new node: 
/default-rack/10.20.20.28:50010
  14/06/01 18:30:06 INFO NetworkTopology: Adding a new node: 
/default-rack/10.20.20.23:50010
  14/06/01 18:30:06 INFO SparkContext: Starting job: count at hello_spark.py:15
  14/06/01 18:30:06 INFO DAGScheduler: Got job 0 (count at hello_spark.py:15) 
with 2 output partitions (allowLocal=false)
  14/06/01 18:30:06 INFO DAGScheduler: Final stage: Stage 0 (count at 
hello_spark.py:15)
  14/06/01 18:30:06 INFO DAGScheduler: Parents of final stage: List()
  14/06/01 18:30:06 INFO DAGScheduler: Missing parents: List()
  14/06/01 18:30:06 INFO DAGScheduler: Submitting Stage 0 (PythonRDD[2] at 
count at hello_spark.py:15), which has no missing parents
  14/06/01 18:30:07 INFO DAGScheduler: Submitting 2 missing tasks from Stage 0 
(PythonRDD[2] at count at hello_spark.py:15)
  14/06/01 18:30:07 INFO YarnClientClusterScheduler: Adding task set 0.0 with 2 
tasks
  14/06/01 18:30:08 INFO YarnClientSchedulerBackend: Registered executor: 
Actor[akka.tcp://sparkExecutor@host-10-20-20-28.novalocal:44417/user/Executor#-1352071582]
 with ID 1
  14/06/01 18:30:08 INFO TaskSetManager: Starting task 0.0:0 as TID 0 on 
executor 1: host-10-20-20-28.novalocal (PROCESS_LOCAL)
  14/06/01 18:30:08 INFO TaskSetManager: Serialized task 0.0:0 as 3123 bytes in 
14 ms
  14/06/01 18:30:09 INFO BlockManagerMasterActor$BlockManagerInfo: Registering 
block manager host-10-20-20-28.novalocal:42960 with 588.8 MB RAM
  14/06/01 18:30:16 INFO BlockManagerMasterActor$BlockManagerInfo: Added 
rdd_1_0 in memory on host-10-20-20-28.novalocal:42960 (size: 308.2 MB, free: 
280.7 MB)
  14/06/01 18:30:17 INFO YarnClientSchedulerBackend: Registered executor: 
Actor[akka.tcp://sparkExecutor@host-10-20-20-23.novalocal:58126/user/Executor#1079893974]
 with ID 2
  14/06/01 18:30:17 INFO TaskSetManager: Starting task 0.0:1 as TID 1 on 
executor 2: host-10-20-20-23.novalocal (PROCESS_LOCAL)
  14/06/01 18:30:17 INFO TaskSetManager: Serialized task 0.0:1 as 3123 bytes in 
1 ms
  14/06/01 18:30:17 INFO BlockManagerMasterActor$BlockManagerInfo: Registering 
block manager host-10-20-20-23.novalocal:56776 with 588.8 MB RAM
  fj14/06/01 18:31:20 WARN BlockManagerMasterActor: Removing BlockManager 
BlockManagerId(1, host-10-20-20-28.novalocal, 42960, 0) with no recent heart 
beats: 55828ms exceeds 45000ms
  14/06/01 18:42:23 INFO YarnClientSchedulerBackend: Executor 2 disconnected, 
so removing it
  14/06/01 18:42:23 ERROR YarnClientClusterScheduler: Lost executor 2 on 
host-10-20-20-23.novalocal: remote Akka client disassociated

  The same job finishes flawlessly on a single worker.

  System Information:
  ==

  Description: Ubuntu 12.04.4 LTS
  Release: 12.04

  Linux 3.8.0-35-generic #52~precise1-Ubuntu SMP Thu Jan 30 17:24:40 UTC
  2014 x86_64

  libvirt-bin:
  --
Installed: 1.1.1-0ubuntu8~cloud2
Candidate: 1.1.1-0ubuntu8.7~cloud1
Version table:
   1.1.1-0ubuntu8.7~cloud1 0
  500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ 
precise-updates/havana/main amd64 Packages
   *** 1.1.1-0ubuntu8~cloud2 0
  100 /var/lib/dpkg/status
   0.9.8-2ubuntu17.19 0
  500 http://se.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
   0.9.8-2ubuntu17.17 0
  500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 
Packages
   0.9.8-2ubuntu17 0
   

[Kernel-packages] [Bug 1688162] Re: dmidecode should print diagnostic messages to stderr

[Jens Elkner]

Hi Christian,

Yepp, the patch looks good. Would be nice to get this integrated (or to
sync dmidecode with the current GNU version).

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

Title:
  dmidecode should print diagnostic messages to stderr

Status in dmidecode package in Ubuntu:
  Triaged

Bug description:
  Ubuntu version of dmidecode breaks several scripts because it prints
  diagnostics messages to stdout instead of stderr.

  E.g.: sudo /bin/ksh93
  # /usr/sbin/dmidecode -s baseboard-manufacturer 2>/dev/null
  Supermicro
  Invalid entry length (16). Fixed up to 11.

  
  The original version (https://git.savannah.nongnu.org/git/dmidecode.git) 
however, works as expected:
  # /tmp/dmidecode -s baseboard-manufacturer 2>/dev/null
  Supermicro

  
  $ /usr/bin/lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  Codename: xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1688162/+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 1686645] kernel01 (s390x.zVM) - tests ran: 14, failed: 3

[Brad Figg]

tests ran:  14, failed: 3;
  
http://kernel.ubuntu.com/testing/4.4.0-78.99-generic/kernel01__4.4.0-78.99__2017-05-04_11-05-00/results-index.html

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

Title:
  linux: 4.4.0-78.99 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686645/+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 1686976] wright-kernel (arm64) - tests ran: 14, failed: 1

[Brad Figg]

tests ran:  14, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/wright-kernel__4.8.0-52.55__2017-05-04_10-48-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1686978
  derivatives: 1686979
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Alex Shchagin]

Bram,

This is because USB3 and USB-C ports in TB16 are connected to different 
controllers. See my lshw output here - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750/comments/23 - I've 
marked Ethernet cards with <<--. Working one is USB-C and it is under this one:
/0/100/1d.6/0/1/0/4/0/4 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 
2015]
/0/100/1d.6/0/1/0/4/0/4/0 bus DSL6540 USB 3.1 Controller [Alpine Ridge]

Alex

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  New

Bug description:
  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx timeout
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 

[Kernel-packages] [Bug 1687877] Re: bonding - mlx5 - speed changed to 0 after changing ring size

[Talat Batheesh]

Thank you,
Tested it and it fixes the issue.
could you please add this fix to the next SRU

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

Title:
  bonding - mlx5 - speed changed to 0 after changing ring size

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  
  The problem happens when changing the ring size of a mlx5_core interface that 
is part of a LACP bond.

  [268312.721076] mlx5_core :42:00.1 enp66s0f1: mlx5e_update_carrier:143: 
Link up
  [268312.721940] mlx5_core :42:00.1 enp66s0f1: speed changed to 0 for port 
enp66s0f1
  [268312.732089] bond0: link status up again after 0 ms for interface enp66s0f1

  
  the upstream commit "bonding: allow notifications for 
bond_set_slave_link_state " fix the issue, will cherry-pick and send to xenial 
git tree.

  
  Thanks,
  Talat

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

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

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[André Düwel]

Ohh okay, thanks for this advise I will order an adapter and try it out.

This seems to verify that the problem exists somewhere in the usb3
controller/driver (ASM1042A) in the TB16 and not in the Ethernet
controller/driver itself.

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  New

Bug description:
  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx timeout
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:09 ubuntu kernel: usb 4-1.2: reset SuperSpeed USB device number 
3 using xhci_hcd

  I can't seem to make this bug appear with any other 

[Kernel-packages] [Bug 1687847] Re: ath9k_htc doesn't work with TL-WN722N wifi USB

[Hồng Quân]

Hi, I upgraded to kernel v4.11:

$ uname -a 
Linux Zapus 4.11.0-041100rc8-generic #201704232131 SMP Mon Apr 24 01:32:55 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

The problem still exists:


May  4 17:49:46 Zapus NetworkManager[1014]:   [1493894986.1889] device 
(wlxf81a670b94db): supplicant interface state: disconnected -> scanning
May  4 17:49:47 Zapus wpa_supplicant[1672]: wlxf81a670b94db: SME: Trying to 
authenticate with 18:a6:f7:d3:8b:b2 (SSID='X\xc3\xb3m nh\xc3\xa0 l\xc3\xa1' 
freq=2462 MHz)
May  4 17:49:47 Zapus kernel: [  238.048186] wlxf81a670b94db: authenticate with 
18:a6:f7:d3:8b:b2
May  4 17:49:47 Zapus kernel: [  238.314481] wlxf81a670b94db: send auth to 
18:a6:f7:d3:8b:b2 (try 1/3)
May  4 17:49:47 Zapus NetworkManager[1014]:   [1493894987.6765] device 
(wlxf81a670b94db): supplicant interface state: scanning -> authenticating
May  4 17:49:47 Zapus kernel: [  238.317885] wlxf81a670b94db: authenticated
May  4 17:49:50 Zapus kernel: [  240.853946] wlxf81a670b94db: aborting 
authentication with 18:a6:f7:d3:8b:b2 by local choice (Reason: 3=DEAUTH_LEAVING)
May  4 17:49:50 Zapus NetworkManager[1014]:   [1493894990.2127] device 
(wlxf81a670b94db): Activation: (wifi) association took too long, failing 
activation
May  4 17:49:50 Zapus NetworkManager[1014]:   [1493894990.2128] device 
(wlxf81a670b94db): state change: config -> failed (reason 'ssid-not-found') [50 
120 53]
May  4 17:49:50 Zapus NetworkManager[1014]:   [1493894990.2132] manager: 
NetworkManager state is now DISCONNECTED
May  4 17:49:50 Zapus NetworkManager[1014]:   [1493894990.2144] device 
(wlxf81a670b94db): Activation: failed for connection 'Xóm nhà lá 1'
May  4 17:49:50 Zapus NetworkManager[1014]:   [1493894990.3047] device 
(wlxf81a670b94db): state change: failed -> disconnected (reason 'none') [120 30 
0]
May  4 17:49:50 Zapus wpa_supplicant[1672]: wlxf81a670b94db: 
CTRL-EVENT-DISCONNECTED bssid=18:a6:f7:d3:8b:b2 reason=3 locally_generated=1
May  4 17:49:50 Zapus kernel: [  240.947231] IPv6: ADDRCONF(NETDEV_UP): 
wlxf81a670b94db: link is not ready
May  4 17:49:50 Zapus NetworkManager[1014]:   [1493894990.3350] device 
(wlxf81a670b94db): set-hw-addr: set MAC address to AE:37:82:C3:B1:DF (scanning)
May  4 17:49:50 Zapus NetworkManager[1014]:   [1493894990.5493] 
sup-iface[0x55a39b9bd160,wlxf81a670b94db]: connection disconnected (reason -3)
May  4 17:49:50 Zapus kernel: [  241.187799] IPv6: ADDRCONF(NETDEV_UP): 
wlxf81a670b94db: link is not ready
May  4 17:49:50 Zapus NetworkManager[1014]:   [1493894990.5496] device 
(wlxf81a670b94db): supplicant interface state: authenticating -> disconnected

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

Title:
  ath9k_htc doesn't work with TL-WN722N wifi USB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I tried to connect to a wifi network, with my TL-WN722N wifi USB
  dongle. But it failed with this log:

  
  May  3 09:40:33 Zapus wpa_supplicant[1893]: wlxf81a670b94db: SME: Trying to 
authenticate with c4:a3:66:c1:03:54 (SSID='GUU MILK TEA' freq=2412 MHz)
  May  3 09:40:33 Zapus kernel: [ 2999.716298] wlxf81a670b94db: authenticate 
with c4:a3:66:c1:03:54
  May  3 09:40:33 Zapus NetworkManager[1140]:   [1493779233.6813] device 
(wlxf81a670b94db): supplicant interface state: scanning -> authenticating
  May  3 09:40:33 Zapus kernel: [ 2999.937634] wlxf81a670b94db: send auth to 
c4:a3:66:c1:03:54 (try 1/3)
  May  3 09:40:33 Zapus kernel: [ 2999.939494] wlxf81a670b94db: authenticated
  May  3 09:40:38 Zapus kernel: [ 3004.942553] wlxf81a670b94db: aborting 
authentication with c4:a3:66:c1:03:54 by local choice (Reason: 3=DEAUTH_LEAVING)
  May  3 09:40:38 Zapus NetworkManager[1140]:   [1493779238.7667] device 
(wlxf81a670b94db): supplicant interface state: authenticating -> disconnected
  May  3 09:40:39 Zapus NetworkManager[1140]:   [1493779239.8373] device 
(wlxf81a670b94db): supplicant interface state: disconnected -> scanning
  May  3 09:40:40 Zapus wpa_supplicant[1893]: wlxf81a670b94db: SME: Trying to 
authenticate with c4:a3:66:c1:03:54 (SSID='GUU MILK TEA' freq=2412 MHz)
  May  3 09:40:40 Zapus kernel: [ 3007.235801] wlxf81a670b94db: authenticate 
with c4:a3:66:c1:03:54
  May  3 09:40:41 Zapus kernel: [ 3007.457876] wlxf81a670b94db: send auth to 
c4:a3:66:c1:03:54 (try 1/3)
  May  3 09:40:41 Zapus NetworkManager[1140]:   [1493779241.2027] device 
(wlxf81a670b94db): supplicant interface state: scanning -> authenticating
  May  3 09:40:41 Zapus kernel: [ 3007.460138] wlxf81a670b94db: authenticated
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.3108] device 
(wlxf81a670b94db): Activation: (wifi) association took too long, failing 
activation
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.3109] device 
(wlxf81a670b94db): state change: config -> failed (reason 'ssid-not-found') [50 

[Kernel-packages] [Bug 1687847] Re: ath9k_htc doesn't work with TL-WN722N wifi USB

[Hồng Quân]

This issue starts appear when I use Ubuntu 17.04 (fresh install, not
upgrade). Last time it works is Ubuntu 16.10.

Where to change tag to 'kernel-bug-exists-upstream'?

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

** Tags added: kernel-bug-exists-upstream

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

Title:
  ath9k_htc doesn't work with TL-WN722N wifi USB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I tried to connect to a wifi network, with my TL-WN722N wifi USB
  dongle. But it failed with this log:

  
  May  3 09:40:33 Zapus wpa_supplicant[1893]: wlxf81a670b94db: SME: Trying to 
authenticate with c4:a3:66:c1:03:54 (SSID='GUU MILK TEA' freq=2412 MHz)
  May  3 09:40:33 Zapus kernel: [ 2999.716298] wlxf81a670b94db: authenticate 
with c4:a3:66:c1:03:54
  May  3 09:40:33 Zapus NetworkManager[1140]:   [1493779233.6813] device 
(wlxf81a670b94db): supplicant interface state: scanning -> authenticating
  May  3 09:40:33 Zapus kernel: [ 2999.937634] wlxf81a670b94db: send auth to 
c4:a3:66:c1:03:54 (try 1/3)
  May  3 09:40:33 Zapus kernel: [ 2999.939494] wlxf81a670b94db: authenticated
  May  3 09:40:38 Zapus kernel: [ 3004.942553] wlxf81a670b94db: aborting 
authentication with c4:a3:66:c1:03:54 by local choice (Reason: 3=DEAUTH_LEAVING)
  May  3 09:40:38 Zapus NetworkManager[1140]:   [1493779238.7667] device 
(wlxf81a670b94db): supplicant interface state: authenticating -> disconnected
  May  3 09:40:39 Zapus NetworkManager[1140]:   [1493779239.8373] device 
(wlxf81a670b94db): supplicant interface state: disconnected -> scanning
  May  3 09:40:40 Zapus wpa_supplicant[1893]: wlxf81a670b94db: SME: Trying to 
authenticate with c4:a3:66:c1:03:54 (SSID='GUU MILK TEA' freq=2412 MHz)
  May  3 09:40:40 Zapus kernel: [ 3007.235801] wlxf81a670b94db: authenticate 
with c4:a3:66:c1:03:54
  May  3 09:40:41 Zapus kernel: [ 3007.457876] wlxf81a670b94db: send auth to 
c4:a3:66:c1:03:54 (try 1/3)
  May  3 09:40:41 Zapus NetworkManager[1140]:   [1493779241.2027] device 
(wlxf81a670b94db): supplicant interface state: scanning -> authenticating
  May  3 09:40:41 Zapus kernel: [ 3007.460138] wlxf81a670b94db: authenticated
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.3108] device 
(wlxf81a670b94db): Activation: (wifi) association took too long, failing 
activation
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.3109] device 
(wlxf81a670b94db): state change: config -> failed (reason 'ssid-not-found') [50 
120 53]
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.3114] 
manager: NetworkManager state is now DISCONNECTED
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.3127] device 
(wlxf81a670b94db): Activation: failed for connection 'GUU MILK TEA 1'
  May  3 09:40:44 Zapus kernel: [ 3010.567620] wlxf81a670b94db: aborting 
authentication with c4:a3:66:c1:03:54 by local choice (Reason: 3=DEAUTH_LEAVING)
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.3141] device 
(wlxf81a670b94db): state change: failed -> disconnected (reason 'none') [120 30 
0]
  May  3 09:40:44 Zapus wpa_supplicant[1893]: wlxf81a670b94db: 
CTRL-EVENT-DISCONNECTED bssid=c4:a3:66:c1:03:54 reason=3 locally_generated=1
  May  3 09:40:44 Zapus kernel: [ 3010.646752] IPv6: ADDRCONF(NETDEV_UP): 
wlxf81a670b94db: link is not ready
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.4142] device 
(wlxf81a670b94db): set-hw-addr: set MAC address to F6:9B:02:95:1D:15 (scanning)
  May  3 09:40:44 Zapus kernel: [ 3010.851793] IPv6: ADDRCONF(NETDEV_UP): 
wlxf81a670b94db: link is not ready
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.6033] 
sup-iface[0x55d659f3ba10,wlxf81a670b94db]: connection disconnected (reason -3)
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.6038] device 
(wlxf81a670b94db): supplicant interface state: authenticating -> disconnected

  
  My Ubuntu:

  Ubuntu 17.04
  $ uname -a 
  Linux Zapus 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-extra-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  quan   2631 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Wed May  3 10:00:17 2017
  HibernationDevice: RESUME=UUID=827a1ee9-650e-42f4-943f-0fe6852a69db
  InstallationDate: Installed on 2017-04-14 (18 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1687847] Re: ath9k_htc doesn't work with TL-WN722N wifi USB

[Hồng Quân]

Found where tag is. Changed already.

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

Title:
  ath9k_htc doesn't work with TL-WN722N wifi USB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I tried to connect to a wifi network, with my TL-WN722N wifi USB
  dongle. But it failed with this log:

  
  May  3 09:40:33 Zapus wpa_supplicant[1893]: wlxf81a670b94db: SME: Trying to 
authenticate with c4:a3:66:c1:03:54 (SSID='GUU MILK TEA' freq=2412 MHz)
  May  3 09:40:33 Zapus kernel: [ 2999.716298] wlxf81a670b94db: authenticate 
with c4:a3:66:c1:03:54
  May  3 09:40:33 Zapus NetworkManager[1140]:   [1493779233.6813] device 
(wlxf81a670b94db): supplicant interface state: scanning -> authenticating
  May  3 09:40:33 Zapus kernel: [ 2999.937634] wlxf81a670b94db: send auth to 
c4:a3:66:c1:03:54 (try 1/3)
  May  3 09:40:33 Zapus kernel: [ 2999.939494] wlxf81a670b94db: authenticated
  May  3 09:40:38 Zapus kernel: [ 3004.942553] wlxf81a670b94db: aborting 
authentication with c4:a3:66:c1:03:54 by local choice (Reason: 3=DEAUTH_LEAVING)
  May  3 09:40:38 Zapus NetworkManager[1140]:   [1493779238.7667] device 
(wlxf81a670b94db): supplicant interface state: authenticating -> disconnected
  May  3 09:40:39 Zapus NetworkManager[1140]:   [1493779239.8373] device 
(wlxf81a670b94db): supplicant interface state: disconnected -> scanning
  May  3 09:40:40 Zapus wpa_supplicant[1893]: wlxf81a670b94db: SME: Trying to 
authenticate with c4:a3:66:c1:03:54 (SSID='GUU MILK TEA' freq=2412 MHz)
  May  3 09:40:40 Zapus kernel: [ 3007.235801] wlxf81a670b94db: authenticate 
with c4:a3:66:c1:03:54
  May  3 09:40:41 Zapus kernel: [ 3007.457876] wlxf81a670b94db: send auth to 
c4:a3:66:c1:03:54 (try 1/3)
  May  3 09:40:41 Zapus NetworkManager[1140]:   [1493779241.2027] device 
(wlxf81a670b94db): supplicant interface state: scanning -> authenticating
  May  3 09:40:41 Zapus kernel: [ 3007.460138] wlxf81a670b94db: authenticated
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.3108] device 
(wlxf81a670b94db): Activation: (wifi) association took too long, failing 
activation
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.3109] device 
(wlxf81a670b94db): state change: config -> failed (reason 'ssid-not-found') [50 
120 53]
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.3114] 
manager: NetworkManager state is now DISCONNECTED
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.3127] device 
(wlxf81a670b94db): Activation: failed for connection 'GUU MILK TEA 1'
  May  3 09:40:44 Zapus kernel: [ 3010.567620] wlxf81a670b94db: aborting 
authentication with c4:a3:66:c1:03:54 by local choice (Reason: 3=DEAUTH_LEAVING)
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.3141] device 
(wlxf81a670b94db): state change: failed -> disconnected (reason 'none') [120 30 
0]
  May  3 09:40:44 Zapus wpa_supplicant[1893]: wlxf81a670b94db: 
CTRL-EVENT-DISCONNECTED bssid=c4:a3:66:c1:03:54 reason=3 locally_generated=1
  May  3 09:40:44 Zapus kernel: [ 3010.646752] IPv6: ADDRCONF(NETDEV_UP): 
wlxf81a670b94db: link is not ready
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.4142] device 
(wlxf81a670b94db): set-hw-addr: set MAC address to F6:9B:02:95:1D:15 (scanning)
  May  3 09:40:44 Zapus kernel: [ 3010.851793] IPv6: ADDRCONF(NETDEV_UP): 
wlxf81a670b94db: link is not ready
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.6033] 
sup-iface[0x55d659f3ba10,wlxf81a670b94db]: connection disconnected (reason -3)
  May  3 09:40:44 Zapus NetworkManager[1140]:   [1493779244.6038] device 
(wlxf81a670b94db): supplicant interface state: authenticating -> disconnected

  
  My Ubuntu:

  Ubuntu 17.04
  $ uname -a 
  Linux Zapus 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-extra-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  quan   2631 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Wed May  3 10:00:17 2017
  HibernationDevice: RESUME=UUID=827a1ee9-650e-42f4-943f-0fe6852a69db
  InstallationDate: Installed on 2017-04-14 (18 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=2cea9e5f-d0a8-4d48-9218-6e48122a6f1e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[belgianguy]

@kaihengfeng: that seems to be very likely. (Aorus is just a Gigabyte
branding name)

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1686976] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/ms10-35-mcdivittB0-kernel__4.8.0-52.55__2017-05-04_10-41-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1686978
  derivatives: 1686979
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Bram Biesbrouck]

André,

I followed your advice and bought an inexpensive USB3 1gbit ethernet
adapter and noticed the same drops and corruptions as the built-in
ethernet port. However, when I plug it in the USB-C port of the dock
(using a little USB3 to USB-C cable), everything seems to work
correctly.

B.

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  New

Bug description:
  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx timeout
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:09 ubuntu kernel: usb 4-1.2: reset SuperSpeed USB device number 
3 using 

[Kernel-packages] [Bug 1681469] Re: Potential memory corruption with capi adapters

[bugproxy]

** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety

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

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681469/+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 1686828] Re: xhci_hcd 0000:00:14.0: WARN Event TRB for slot 4 ep 6 with no TDs queued?

[Marc F]

Just to state that also affected me, seen many different bug reports (in
different distros) and the general proposed solution is to upgrade BIOS.

I already upgrade my BIOS and still facing the same 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/1686828

Title:
  xhci_hcd :00:14.0: WARN Event TRB for slot 4 ep 6 with no TDs
  queued?

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

Bug description:
  dmesg:
  [  418.501019] xhci_hcd :00:14.0: WARN Event TRB for slot 4 ep 6 with no 
TDs queued?
  [  418.509810] xhci_hcd :00:14.0: WARN Event TRB for slot 4 ep 6 with no 
TDs queued?
  [  418.516116] xhci_hcd :00:14.0: WARN Event TRB for slot 4 ep 6 with no 
TDs queued?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2195 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Apr 27 17:21:36 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (641 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1686828/+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 1686976] wright-kernel (arm64) - tests ran: 9, failed: 4

[Brad Figg]

tests ran:   9, failed: 4;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/wright-kernel__4.8.0-52.55__2017-05-04_09-36-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1686978
  derivatives: 1686979
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+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 1598637] Re: Dell Inspiron 5555 touchpad not working

[Avanish Mishra]

I have the same laptop but after ubuntu installation, its battery backup
falls down drastically. Anyone can help me with this 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/1598637

Title:
  Dell Inspiron  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Ubuntu 16.04 64 bit (also Linux Mint and other Ubuntu 16.04
  based distros) on my Dell Inspiron  AMD A10-8700P Radeon R6.

  The touchpad sort-of works for a few seconds (pointer moves but
  cliking fails) and after a while it hangs completely. The USB mouse
  works with no issues though.

  I've found following the steps given here
  http://askubuntu.com/a/632570/55128 works:

  1. Run
  $ sudo -H gedit /etc/default/grub

  In the open window edit line

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  it should look this way

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nopnp"

  Save file and run

  $ sudo update-grub

  2. Run
  $ echo "blacklist i2c_hid" | sudo tee /etc/modprobe.d/i2c-hid.conf
  $ sudo depmod -a
  $ sudo update-initramfs -u
  $ echo "synaptics_i2c" | sudo tee -a /etc/modules

  3. Reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1598637/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

So it happens to all Gigabyte boards? A320 & B350 & X370?

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[belgianguy]

cat /sys/class/dmi/id/board_name
gives me:
AX370-Gaming K7 

(I didn't mention the command in my previous post)

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1687623] Re: linux-4.4.0-77.98 was a phased update in -updates only and may become partially installed (was: 4.4.0-77-generic breaks internet on 16.04.2)

[Stefan Bader]

Update-manager is fixed now and as Andy wrote, a change in the process
should prevent this from ever happening again. Unfortunately that does
not help anybody who is already having the problem (at least not if that
means no network connection). And without network it is hard to find any
documents about this on the net.

If network is not affected the remaining kernel packages will get
offered by update-manager (the same way as the apt-get variant). If it
is affected one needs to boot into the previous kernel and I personally
wished the grub boot menu were not hidden away by default (pressing
left-shift at the exactly right time is something I never manage to do).
As long as it is possible to login into the broken system can be enabled
by modifying /etc/default/grub (commenting out the two lines with
GRUB_HIDDEN_... and uncommenting, if needed, the GRUB_TIMEOUT line,
setting it to 5 (seconds)), then "sudo update-grub" and reboot.

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

Title:
  linux-4.4.0-77.98 was a phased update in -updates only and may become
  partially installed (was: 4.4.0-77-generic breaks internet on 16.04.2)

Status in linux package in Ubuntu:
  In Progress
Status in update-manager package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress
Status in update-manager source package in Xenial:
  Confirmed

Bug description:
  Hi as per title today I updated to  4.4.0-77-generic on my Lubuntu
  16.04.02 and wifi is not working anymore. When I click on the network
  manager I see "enable networking" (which is toggled) but no more the
  option about wifi.

  I reported this on ubuntuforum:
  https://ubuntuforums.org/showthread.php?t=2360216

  Where a user suggested to revert to an older kernel and see if this
  fixes the problem. I managed to revert to 4.4.0-75-generic via grub
  and everything works perfectly.

  Another user reported a similar issue caused by the same upgrade on
  the same system: https://ubuntuforums.org/showthread.php?t=2360215

  Can someone else confirm this bug?

  If you need more information I will be happy to provide it (I am a
  newbie though so please be patient).

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

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

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[André Düwel]

I need to correct me: Having issues during high load on the USB3
Ethernet adapter, too.

Only workaround is limiting to 100MBit.

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  New

Bug description:
  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx timeout
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:09 ubuntu kernel: usb 4-1.2: reset SuperSpeed USB device number 
3 using xhci_hcd

  I can't seem to make this bug appear with any other type of USB
  traffic. I've reported it to the realtek kernel dev team and they
  don't think their 

[Kernel-packages] [Bug 1556274] Re: MX4 bluetooth not pairing with Jaguar XKR 2007

[Dave H]

Hi Daniel, 
Thanks for looking at this. I am still using my ubuntu MX4 as my normal daily 
phone and also have the BQ M10 tablet. Very sorry to hear Canonical have 
dropped ubuntu touch, phones and tablets. I thought it was going very well, 
when you consider what you have all achieved over the past few years, its a 
real shame. I think ubuntu touch is every bit as good as Android, better in 
some cases, if you consider scopes and the swipe gestures. Going back to 
Android will be a disappointment for me. Thanks for your hard work. 

Regarding Unity desktop, I was getting to like it and its very easy for
the family to use. The HUD performance will also be difficult to replace
in Gnome and I like the sliding left icons (I think we we be limited in
Gnome). I have tried Gnome with some tweaks but its still not as nice to
use as Unity.


Regards

Dave

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

Title:
  MX4 bluetooth not pairing with Jaguar XKR 2007

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi I have an MX4 with OTA-9.1 update installed. The phone has never
  been able to pair with my Jaguar XKR 2007. The car finds the Meizu MX4
  and displays the phone type, but will not pair to it Any help to
  improve this would be appreciated.

  Just to say, really enjoying Ubuntu Touch, once miracast is added it
  will be the one to beat.

  Regards

  Dave H

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1556274/+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 1677319] Re: Support low-pin-count devices on Hisilicon SoCs

[Stefan Bader]

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  Support low-pin-count devices on Hisilicon SoCs

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  The HiSilicon Hip06/Hip07 SoCs include a low-pin-count (LPC) host controller. 
The Linux kernel needs support for this interface to use attached devices, such 
as a UART and the IPMI system interface.

  [Test Case]
  Boot up a HiSilicon D05 system, confirm that the following command returns 
w/o error:

  $ sudo ipmitool lan print

  [Regression Risk]
  The proposed patchset only enables LIBIO for arm64, so the greatest 
regression risk is to other arm64 systems. We have mitigated that by testing on 
a wide range of hardware (all certified arm64 servers + some in-devel systems). 
There remains some arch-independent changes to the generic PCI code. The patch 
"PCI: Restore codepath for !CONFIG_LIBIO" was added to mitigate the risk to 
other architectures by restoring the previous code for those architectures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677319/+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