date:20170323

tests ran:  22, failed: 3;
  
http://kernel.ubuntu.com/testing/4.10.0-14.16-generic/s2lp6g003__4.10.0-14.16__2017-03-24_05-30-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/1673805

Title:
  linux: 4.10.0-14.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-14.16 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-development-workflow/+bug/1673805/+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 1673805] s2lp6g003 (s390x.zKVM) - tests ran: 15, failed: 3

tests ran:  15, failed: 3;
  
http://kernel.ubuntu.com/testing/4.10.0-14.16-generic/s2lp6g003__4.10.0-14.16__2017-03-24_05-16-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/1673805

Title:
  linux: 4.10.0-14.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-14.16 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-development-workflow/+bug/1673805/+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 1673805] amaura (amd64) - tests ran: 64, failed: 0

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-14.16-generic/amaura__4.10.0-14.16__2017-03-24_05-10-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/1673805

Title:
  linux: 4.10.0-14.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-14.16 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-development-workflow/+bug/1673805/+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 1674938] onibi (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-70.91-generic/onibi__4.4.0-70.91__2017-03-24_05-18-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/1674938

Title:
  linux: 4.4.0-70.91 -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 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

  backports: 1674939
  derivatives: 1674940,1674941,1674944,1674945
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+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 1673805] s2lp6g003 (s390x.zKVM) - tests ran: 141, failed: 28

tests ran: 141, failed: 28;
  
http://kernel.ubuntu.com/testing/4.10.0-14.16-generic/s2lp6g003__4.10.0-14.16__2017-03-24_04-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/1673805

Title:
  linux: 4.10.0-14.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-14.16 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-development-workflow/+bug/1673805/+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 1673805] s2lp6g003 (s390x.zKVM) - tests ran: 2, failed: 0

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-14.16-generic/s2lp6g003__4.10.0-14.16__2017-03-24_04-38-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/1673805

Title:
  linux: 4.10.0-14.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-14.16 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-development-workflow/+bug/1673805/+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 1673805] s2lp6g003 (s390x.zKVM) - tests ran: 64, failed: 0

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-14.16-generic/s2lp6g003__4.10.0-14.16__2017-03-24_04-13-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/1673805

Title:
  linux: 4.10.0-14.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-14.16 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-development-workflow/+bug/1673805/+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 1673805] naumann (amd64) - tests ran: 64, failed: 0

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-14.16-generic/naumann__4.10.0-14.16__2017-03-24_03-30-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/1673805

Title:
  linux: 4.10.0-14.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-14.16 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-development-workflow/+bug/1673805/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2017-03-23 Thread Kai-Heng Feng

Download [1] and put it to /etc/udev/hwdb.d/.

Then execute the following commands:
$ sudo systemd-hwdb update
$ sudo udevadm trigger

[1]
https://raw.githubusercontent.com/systemd/systemd/master/hwdb/70-pointingstick.hwdb

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1637550] Re: [Feature] R3 mwait support for Knights Mill

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

** Changed in: intel
   Status: New => Fix Committed

** Changed in: intel
 Assignee: (unassigned) => Robert Hooker (sarvatt)

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

Title:
  [Feature] R3 mwait support for Knights Mill

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Enable r3 mwait for  Knights Mill.

  Schedule:
  upstream: 4.11 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1637550/+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 1675509] Re: ARM arch_timer erratum

** Description changed:

- There are a few platforms requiring errata workarounds for their
- arch_timer implementations. Specifically, the HiSilicon D05 in ACPI
- mode, and Cortex-A73-based systems.
+ The HiSilicon D05 board and systems based on Cortex-A73 each have errata
+ for their architected timers which can cause reads to return bogus data.

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

Title:
  ARM arch_timer erratum

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The HiSilicon D05 board and systems based on Cortex-A73 each have
  errata for their architected timers which can cause reads to return
  bogus data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675509/+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 1654319] Re: kernel BUG at /build/linux-_qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413

2017-03-23 Thread cryptz

also i saw your other thread where there is mention of the # of cpus
being a factor. In my case i have 1 socket with 2 cpus assigned to each
vm. I have 2 identical vms running haproxy. for whatever reason the
primary typically locks up 2-3 times a day, the secondary is only once
or twice a week.

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

Title:
  kernel BUG at /build/linux-
  _qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413

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

Bug description:
  Hello everyone,

  I have jenkins installed with an apache frontend. Sometimes, after
  making few GET requests whole system crashes and restarts.

  ESXi host version 6.5, virtual hardware version 13.

  I've found similar bug report here
  https://bugzilla.kernel.org/show_bug.cgi?id=191201

  
  [ 6544.559660] [ cut here ]
  [ 6544.559694] kernel BUG at 
/build/linux-_qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413!
  [ 6544.559728] invalid opcode:  [#1] SMP
  [ 6544.559745] Modules linked in: xt_multiport vmw_vsock_vmci_transport vsock 
ppdev vmw_balloon joydev coretemp input_leds serio_raw nfit shpchp i2c_piix4 
vmw_vmci parport_pc parport mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables 
nf_conntrack_netbios_ns ib_iser rdma_cm nf_conntrack_broadcast iw_cm nf_nat_ftp 
ib_cm nf_nat ib_core nf_conntrack_ftp nf_conntrack iptable_filter configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic
  [ 6544.560172]  usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
vmwgfx ttm aesni_intel aes_x86_64 lrw glue_helper ablk_helper cryptd 
drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops vmxnet3 
ahci libahci mptspi drm mptscsih mptbase scsi_transport_spi pata_acpi fjes
  [ 6544.560332] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.8.0-32-generic 
#34-Ubuntu
  [ 6544.560360] Hardware name: VMware, Inc. VMware Virtual Platform/440BX 
Desktop Reference Platform, BIOS 6.00 04/05/2016
  [ 6544.560399] task: a172f62a0d00 task.stack: a172f62ac000
  [ 6544.560422] RIP: 0010:[]  [] 
vmxnet3_rq_rx_complete+0x8d1/0xeb0 [vmxnet3]
  [ 6544.560465] RSP: 0018:a172ffc83dc8  EFLAGS: 00010297
  [ 6544.560487] RAX:  RBX:  RCX: 
a172efb8a000
  [ 6544.560513] RDX: 0040 RSI: 0001 RDI: 
0040
  [ 6544.560540] RBP: a172ffc83e40 R08: 0002 R09: 
0030
  [ 6544.560566] R10:  R11: a172ec950880 R12: 
a172f35cc280
  [ 6544.560593] R13: a172ec951400 R14: a172f1c83000 R15: 
a172f2b1c000
  [ 6544.560621] FS:  () GS:a172ffc8() 
knlGS:
  [ 6544.560650] CS:  0010 DS:  ES:  CR0: 80050033
  [ 6544.560671] CR2: 7f742a78da30 CR3: 00022f962000 CR4: 
06e0
  [ 6544.560752] Stack:
  [ 6544.560766]  a172ec950880 a172ec950880  
a172ec950880
  [ 6544.560803]  002d a172ec951420 0002 
00010040
  [ 6544.560837]  a172ec9514e8  a172ec950880 
a172ec951420
  [ 6544.560872] Call Trace:
  [ 6544.561677]  
  [ 6544.561689]  [] vmxnet3_poll_rx_only+0x3a/0xb0 [vmxnet3]
  [ 6544.563233]  [] net_rx_action+0x238/0x380
  [ 6544.564004]  [] __do_softirq+0x10d/0x298
  [ 6544.564757]  [] irq_exit+0xa3/0xb0
  [ 6544.565499]  [] do_IRQ+0x54/0xd0
  [ 6544.566224]  [] common_interrupt+0x82/0x82
  [ 6544.566928]  
  [ 6544.566940]  [] ? native_safe_halt+0x6/0x10
  [ 6544.568313]  [] default_idle+0x20/0xd0
  [ 6544.568978]  [] arch_cpu_idle+0xf/0x20
  [ 6544.569625]  [] default_idle_call+0x2a/0x40
  [ 6544.570255]  [] cpu_startup_entry+0x2ec/0x350
  [ 6544.570871]  [] start_secondary+0x151/0x190
  [ 6544.571475] Code: 90 88 45 98 4c 89 55 a0 e8 4d 70 e9 d8 0f b6 45 98 4c 8b 
5d 90 4c 8b 55 a0 49 c7 85 60 01 00 00 00 00 00 00 89 c6 e9 91 f8 ff ff <0f> 0b 
0f 0b 49 83 85 b8 01 00 00 01 49 c7 85 60 01 00 00 00 00
  [ 6544.573327] RIP  [] vmxnet3_rq_rx_complete+0x8d1/0xeb0 
[vmxnet3]
  [ 6544.573926]  RSP 

  
  BR, 
  Mikolaj Kowalski

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 sty  3 17:47 seq
   crw-rw 1 root audio 116, 33 sty  3 17:47 timer
  AplayDevices: Error:

[Kernel-packages] [Bug 1654319] Re: kernel BUG at /build/linux-_qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413

2017-03-23 Thread cryptz

Just to confirm your test, are you running a hw version 13 vm with
kernel ~4.8? I am also using the driver provided in vmware tools 10.1.5

it is my understanding that hw version 11 is fine.

of note the system can run for a day but generally speaking it only runs
for an hour or 2 before the lockup.

i will get you the requested info when it happens again tomorrow.

my vms are light use/haproxy so while i do have vrrp in the mix i see
too many other people with the issue and no mention of keepalived. I
just wanted to point out that you do not need to run larges amount of
traffic to the system. Its actually possible that idle may be better for
reproducing the 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/1654319

Title:
  kernel BUG at /build/linux-
  _qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413

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

Bug description:
  Hello everyone,

  I have jenkins installed with an apache frontend. Sometimes, after
  making few GET requests whole system crashes and restarts.

  ESXi host version 6.5, virtual hardware version 13.

  I've found similar bug report here
  https://bugzilla.kernel.org/show_bug.cgi?id=191201

  
  [ 6544.559660] [ cut here ]
  [ 6544.559694] kernel BUG at 
/build/linux-_qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413!
  [ 6544.559728] invalid opcode:  [#1] SMP
  [ 6544.559745] Modules linked in: xt_multiport vmw_vsock_vmci_transport vsock 
ppdev vmw_balloon joydev coretemp input_leds serio_raw nfit shpchp i2c_piix4 
vmw_vmci parport_pc parport mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables 
nf_conntrack_netbios_ns ib_iser rdma_cm nf_conntrack_broadcast iw_cm nf_nat_ftp 
ib_cm nf_nat ib_core nf_conntrack_ftp nf_conntrack iptable_filter configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic
  [ 6544.560172]  usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
vmwgfx ttm aesni_intel aes_x86_64 lrw glue_helper ablk_helper cryptd 
drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops vmxnet3 
ahci libahci mptspi drm mptscsih mptbase scsi_transport_spi pata_acpi fjes
  [ 6544.560332] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.8.0-32-generic 
#34-Ubuntu
  [ 6544.560360] Hardware name: VMware, Inc. VMware Virtual Platform/440BX 
Desktop Reference Platform, BIOS 6.00 04/05/2016
  [ 6544.560399] task: a172f62a0d00 task.stack: a172f62ac000
  [ 6544.560422] RIP: 0010:[]  [] 
vmxnet3_rq_rx_complete+0x8d1/0xeb0 [vmxnet3]
  [ 6544.560465] RSP: 0018:a172ffc83dc8  EFLAGS: 00010297
  [ 6544.560487] RAX:  RBX:  RCX: 
a172efb8a000
  [ 6544.560513] RDX: 0040 RSI: 0001 RDI: 
0040
  [ 6544.560540] RBP: a172ffc83e40 R08: 0002 R09: 
0030
  [ 6544.560566] R10:  R11: a172ec950880 R12: 
a172f35cc280
  [ 6544.560593] R13: a172ec951400 R14: a172f1c83000 R15: 
a172f2b1c000
  [ 6544.560621] FS:  () GS:a172ffc8() 
knlGS:
  [ 6544.560650] CS:  0010 DS:  ES:  CR0: 80050033
  [ 6544.560671] CR2: 7f742a78da30 CR3: 00022f962000 CR4: 
06e0
  [ 6544.560752] Stack:
  [ 6544.560766]  a172ec950880 a172ec950880  
a172ec950880
  [ 6544.560803]  002d a172ec951420 0002 
00010040
  [ 6544.560837]  a172ec9514e8  a172ec950880 
a172ec951420
  [ 6544.560872] Call Trace:
  [ 6544.561677]  
  [ 6544.561689]  [] vmxnet3_poll_rx_only+0x3a/0xb0 [vmxnet3]
  [ 6544.563233]  [] net_rx_action+0x238/0x380
  [ 6544.564004]  [] __do_softirq+0x10d/0x298
  [ 6544.564757]  [] irq_exit+0xa3/0xb0
  [ 6544.565499]  [] do_IRQ+0x54/0xd0
  [ 6544.566224]  [] common_interrupt+0x82/0x82
  [ 6544.566928]  
  [ 6544.566940]  [] ? native_safe_halt+0x6/0x10
  [ 6544.568313]  [] default_idle+0x20/0xd0
  [ 6544.568978]  [] arch_cpu_idle+0xf/0x20
  [ 6544.569625]  [] default_idle_call+0x2a/0x40
  [ 6544.570255]  [] cpu_startup_entry+0x2ec/0x350
  [ 6544.570871]  [] start_secondary+0x151/0x190
  [ 6544.571475] Code: 90 88 45 98 4c 89 55 a0 e8 4d 70 e9 d8 0f b6 45 98 4c 8b 
5d 90 4c 8b 55 a0 49 c7 85 60 01 00 00 00 00 00 00 89 c6 e9 91 f8 ff ff <0f> 0b 
0f 0b 49 83 85 b8 01 00 00 01 49 c7 85 60 01 00 00 00 00
  [ 6544.573327] RIP  [] vmxnet3_rq_rx_complete+0x8d1/0xeb0 
[vmxnet3]
  [ 6544.573926]  RSP

[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2017-03-23 Thread Oliver Yates

Hello,
I have the same bug on my E7470 (Xubuntu 16 LTS). Kai-Heng Feng, how can I 
import the latest configuration you talk about?

Btw, even though the pointingstick is clearly the main issue, it seems
like the touchpad has a really abnormal behavior, I hope an update will
be released soon...

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1600624] Re: MacBook wifi doesn't work (brcmfmac)

2017-03-23 Thread archenroot

Ok, well in my case I was:
- 1. missing the firmware at all as I thought it is not required for this 
device, but this was quickly resolved, my kernel config is as follows:
ares ~ # grep -Hrn "FIRMWARE" /usr/src/linux/.config 
/usr/src/linux/.config:1541:CONFIG_PREVENT_FIRMWARE_BUILD=y 
/usr/src/linux/.config:1543:CONFIG_FIRMWARE_IN_KERNEL=y 
/usr/src/linux/.config:1544:CONFIG_EXTRA_FIRMWARE="brcm/brcmfmac43602-pcie.bin 
brcm/BCM-0a5c-6410.hcd" 
/usr/src/linux/.config:1545:CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" 
/usr/src/linux/.config:3222:# CONFIG_CYPRESS_FIRMWARE is not set 
/usr/src/linux/.config:3372:# CONFIG_DRM_LOAD_EDID_FIRMWARE is not set 
/usr/src/linux/.config:3428:CONFIG_FIRMWARE_EDID=y 
/usr/src/linux/.config:5000:CONFIG_FIRMWARE_MEMMAP=y 
/usr/src/linux/.config:5009:# CONFIG_GOOGLE_FIRMWARE is not set 
/usr/src/linux/.config:5408:CONFIG_TEST_FIRMWARE=y

2. The message "Direct firmware load for brcm/brcmfmac43602-pcie.txt
failed with error -2" is not an issue in general, such file is related
to calibration as per my understanding and is not provided for this
device.

3. The message "brcmf_cfg80211_reg_notifier: not a ISO3166 code" might
cause or not some issue, but this is probably related to manufacturer
based on discussions on Gentoo forum

4. I got confirmation from one Gentoo guy from link referenced in previous post 
by me that he has the device and it works, but mine still didn't work. The last 
step I check was network stack app boot and found that both packages are in 
default runlevel:
net-misc/networkmanager-1.6.2_pre 
net-misc/dhcpcd-6.11.3 

Once I disabled dhcpcd (which is anyway auto-started on demand by
NetworkManager and that was somehow causing issue and continuous
switching of MAC addresses as well) I was able to connect to wifi.

Stability - I am on 4.10.3-gentoo kernel and:
A. At work/airports - I am on Open or WPA2-PSK secured network and all is fine, 
I didn't experienced disconnect or Kernel Panic for about 2 weeks
B. At home - Well, this is still strange. When I work alone all is stable, but 
when my wife sit at me and connect from here Android based Lenovo phone, in 
about less then ~5-30 minutes I get kernel panic. I will try to capture some 
more details about this strange and probably unique situation as I don't 
experience it anywhere else. (probably it is because of my wife :-) )

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

Title:
  MacBook wifi doesn't work (brcmfmac)

Status in linux package in Ubuntu:
  Expired

Bug description:
  wifi doesn't work at all. Output from dmesg:
  [...]
  brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt 
failed with error -2
  ...
  brcmf_cfg80211_reg_notifier: not a ISO3166 code

  There is no file brcmfmac43602-pcie.txt anywhere on the system.
  However, /lib/firmware/brcm/brcmfmac43602-pcie.bin does exist.

  Iw reg get outputs:
  sudo iw reg get
  country DK: DFS-ETSI
   (2402 - 2482 @ 40), (N/A, 20), (N/A)
   (5170 - 5250 @ 80), (N/A, 20), (N/A)
   (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
   (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lars   2010 F pulseaudio
   /dev/snd/controlC0:  lars   2010 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jul 10 19:41:18 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a45b9984-4de8-49e3-ba57-a98ae560ad61
  InstallationDate: Installed on 2016-01-30 (162 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=d3ba9d27-321b-45cb-99f2-776b10c1dc7a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (78 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:

[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load

2017-03-23 Thread Daniel

I am having the issue as well on kernel 4.4.0-66 (x64). Disabling
HighDMA did not fix anything on my end and I cannot figure out what will
trigger the issue. It seems to occur randomly and even if there is no
active network traffic.

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

Title:
  14e4:1687 broadcom tg3 network driver disconnects under high load

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

Bug description:
  The tg3 broadcom network driver that binds with chipset 5762 goes
  offline and unable to recover (even with tg3 watchdog timeout) when
  network transmit is under high load.  Then this happens, only a reboot
  would be able to fix it.  Sometimes, however, bringing the interface
  offline and online (via ifconfig) would recover networking.  I've also
  tested with the latest tg3 driver (dec 2014 version) and networking is
  still problematic.I have also disabled TSO, GSO etc... with
  ethtool and the bug still surfaces.  This bug may be related to the
  integrated Firmware.

  Here is the procedure to replicate the issue because it is hard to
  replicate it under moderate network load.

  1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a 
Ubuntu/Kubunu Live CD 14.04-15.04.
  2. from another machine: start 5 sessions, repetitively copy (scp with public 
key authentication) a 70 meg file back and forth to the tg3 machine in each 
session. (not sure if this is necessary)
  3. create a 1GB file on the tg3 machine, with something like dd 
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
  4. from another machine: repetitively scp copy that 1GB file from the tg3 
machine. This can be done with something like:

  while [ 0 ]; do
     scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
  done;

  Networking will mostly goes offline in about 10-30 minutes.

  WORKAROUND: Add udev rule to make the changes permanent in 
/etc/udev/rules.d/80-tg3-fix.rules :
  ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4", 
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kubuntu3748 F pulseaudio
   /dev/snd/controlC0:  kubuntu3748 F pulseaudio
  CasperVersion: 1.360
  Date: Thu Apr 23 11:16:24 2015
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity 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-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:

  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L06 v02.15
  dmi.board.asset.tag: 2UA5041TG4
  dmi.board.name: 2215
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA5041TG4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP EliteDesk 705 G1 MT
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447664/+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 1639016] Re: e100e NETDEV WATCHDOG: transmit queue 0 timed out

2017-03-23 Thread Daniel

I'm having a similar issue on kernel 4.8.0-42 while running on an HP 705
G1 MT PC. This problem did not occur on the last kernel running on the
machine, which was 4.4.0-66.

What information do you need from me?

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

Title:
  e100e NETDEV WATCHDOG: transmit queue 0 timed out

Status in linux package in Ubuntu:
  Expired

Bug description:
  After some time the Ethernet adapter resets itself and a reboot is required 
to use it.
  It started to happen with 4.8.0 kernel.

  [22677.216049] [ cut here ]
  [22677.216067] WARNING: CPU: 1 PID: 0 at 
/build/linux-yFroJZ/linux-4.8.0/net/sched/sch_generic.c:316 
dev_watchdog+0x1ee/0x1f0
  [22677.216074] NETDEV WATCHDOG: enp2s0 (e1000e): transmit queue 0 timed out
  [22677.216076] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge 
stp llc aufs bnep ccm snd_hrtimer zram nvidia(POE) btusb btrtl btbcm btintel 
bluetooth coretemp kvm irqbypass arc4 iwl3945 snd_hda_codec_conexant 
snd_hda_codec_generic iwlegacy input_leds snd_hda_intel joydev mac80211 
snd_hda_codec serio_raw snd_hda_core snd_hwdep snd_pcm pcmcia snd_seq_midi 
cfg80211 lpc_ich snd_seq_midi_event drm tifm_7xx1 snd_rawmidi yenta_socket 
snd_seq pcmcia_rsrc tifm_core snd_seq_device pcmcia_core snd_timer toshiba_acpi 
snd soundcore industrialio sparse_keymap toshiba_bluetooth shpchp wmi mac_hid 
binfmt_misc parport_pc ppdev lp parport ip_tables x_tables
  [22677.216181]  autofs4 btrfs xor raid6_pq uas usb_storage hid_generic usbhid 
hid psmouse firewire_ohci firewire_core sdhci_pci e1000e pata_acpi sdhci 
crc_itu_t ptp pps_core fjes video
  [22677.216215] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P   OE   
4.8.0-26-generic #28-Ubuntu
  [22677.216218] Hardware name: TOSHIBA Satellite P100/Satellite P100, BIOS 
V4.80   11/12/20092
  [22677.216221]  d5b54967 866cf8be 00200286 f63a9e9c d53da625 f63a9ee0 
d5af19b8 f63a9ecc
  [22677.216232]  d5071b9a d5af197c f63a9f00  d5af19b8 013c 
d57268fe 013c
  [22677.216242]   f5658000 fb74 f63a9eec d5071c06 0009 
 f63a9ee0
  [22677.216252] Call Trace:
  [22677.216261]  [] dump_stack+0x58/0x73
  [22677.216267]  [] __warn+0xea/0x110
  [22677.216272]  [] ? dev_watchdog+0x1ee/0x1f0
  [22677.216276]  [] warn_slowpath_fmt+0x46/0x60
  [22677.216281]  [] dev_watchdog+0x1ee/0x1f0
  [22677.216287]  [] ? qdisc_rcu_free+0x40/0x40
  [22677.216293]  [] call_timer_fn+0x30/0x110
  [22677.216297]  [] ? qdisc_rcu_free+0x40/0x40
  [22677.216301]  [] ? qdisc_rcu_free+0x40/0x40
  [22677.216306]  [] run_timer_softirq+0x1dd/0x490
  [22677.216310]  [] ? rcu_report_qs_rnp+0x92/0x160
  [22677.216317]  [] __do_softirq+0xd7/0x245
  [22677.216331]  [] ? nmi+0x53/0x6d
  [22677.216333]  [] ? __irqentry_text_end+0x3/0x3
  [22677.216335]  [] ? __irqentry_text_end+0x3/0x3
  [22677.216337]  [] do_softirq_own_stack+0x28/0x30
  [22677.216338][] irq_exit+0xa5/0xb0
  [22677.216343]  [] smp_apic_timer_interrupt+0x38/0x50
  [22677.216344]  [] apic_timer_interrupt+0x34/0x3c
  [22677.216348]  [] ? cpuidle_enter_state+0x136/0x330
  [22677.216350]  [] cpuidle_enter+0x14/0x20
  [22677.216353]  [] call_cpuidle+0x2c/0x50
  [22677.216355]  [] cpu_startup_entry+0x281/0x320
  [22677.216358]  [] start_secondary+0x144/0x1a0
  [22677.216359] ---[ end trace 63b8fe6a0c6fd16b ]---
  [22677.216382] e1000e :02:00.0 enp2s0: Reset adapter unexpectedly
  [22686.433572] e1000e: enp2s0 NIC Link is Down
  [22687.952535] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
  [22688.304061] e1000e :02:00.0 enp2s0: MSI interrupt test failed, using 
legacy interrupt.
  [22688.304635] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  konrad 3522 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  MachineType: TOSHIBA Satellite P100
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=4c307497-59d5-4242-b842-3afe0801f5b6 ro quiet splash
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-generic N/A
   linux-backports-modules-4.8.0-26-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-26-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare

[Kernel-packages] [Bug 1670490] Re: FC Adapter (LPe32000-based) prints "iotag out of range", goes offline, and delays boot a lot (Ubuntu17.04/Emulex/lpfc))

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

** Changed in: linux (Ubuntu Xenial)
   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/1670490

Title:
  FC Adapter (LPe32000-based) prints "iotag out of range", goes offline,
  and delays boot a lot (Ubuntu17.04/Emulex/lpfc))

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

Bug description:
  ---Problem Description---
  FC Adapter goes offline and produces the call traces while booting into OS, 
on assigning the LUNs to it.
   
  ---uname output---
  Linux ltciofvtr-firestone1 4.9.0-12-generic #13-Ubuntu SMP Tue Jan 10 
12:52:39 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  FC Redfish Adapter(32 GB) is going offline on assigning the Luns to it. 
Adapter shows online till pettitboot and even Luns are also vissible in 
pettitboot.
  once selecting the OS from pettitboot and booting into it, it produces call 
traces and also few lpfc errors. attached the comple console logs FYR.
  The FC switch to which the Redfish adapter is connected is a 16 GB switch and 
the adapter is of 32 GB. According to me this parameter should not have any 
concern as the adapter has to support backward compatibility. 

  ---Steps to Reproduce---
  1. install the adapter in a server. and connect it to FC switch (16 GB)
  2. create zone and assign the LUNS to it from V7000.
  3. reboot the OS

  
  root@ltciofvtr-firestone1:~# ll /sys/class/fc_host/
  total 0
  drwxr-xr-x  2 root root 0 Jan 25 04:22 ./
  drwxr-xr-x 72 root root 0 Jan 25 03:50 ../
  lrwxrwxrwx  1 root root 0 Jan 25 04:13 host10 -> 
../../devices/pci0001:00/0001:00:00.0/0001:01:00.1/host10/fc_host/host10/
  lrwxrwxrwx  1 root root 0 Jan 25 04:13 host6 -> 
../../devices/pci:00/:00:00.0/:01:00.0/host6/fc_host/host6/
  lrwxrwxrwx  1 root root 0 Jan 25 04:13 host8 -> 
../../devices/pci:00/:00:00.0/:01:00.1/host8/fc_host/host8/
  lrwxrwxrwx  1 root root 0 Jan 25 04:13 host9 -> 
../../devices/pci0001:00/0001:00:00.0/0001:01:00.0/host9/fc_host/host9/
  root@ltciofvtr-firestone1:~# 
  root@ltciofvtr-firestone1:~# cat /sys/class/fc_host/host6/port_state 
  Offline
  root@ltciofvtr-firestone1:~# cat /sys/class/fc_host/host8/port_state 
  Offline
  root@ltciofvtr-firestone1:~# cat /sys/class/fc_host/host9/port_state 
  Online
  root@ltciofvtr-firestone1:~# cat /sys/class/fc_host/host10/port_state 
  Online
  root@ltciofvtr-firestone1:~# 
  root@ltciofvtr-firestone1:~# lspci -nn | grep -i fibre
  :01:00.0 Fibre Channel [0c04]: Emulex Corporation Lancer Gen6: LPe32000 
Fibre Channel Host Adapter [10df:e300] (rev 01)
  :01:00.1 Fibre Channel [0c04]: Emulex Corporation Lancer Gen6: LPe32000 
Fibre Channel Host Adapter [10df:e300] (rev 01)
  0001:01:00.0 Fibre Channel [0c04]: Emulex Corporation Lancer-X: LightPulse 
Fibre Channel Host Adapter [10df:e200] (rev 10)
  0001:01:00.1 Fibre Channel [0c04]: Emulex Corporation Lancer-X: LightPulse 
Fibre Channel Host Adapter [10df:e200] (rev 10)
  root@ltciofvtr-firestone1:~# 

  
  Device driver error code:
   [  537.317563] lpfc :01:00.1: 1:0338 IOCB wait timeout error - no wake 
response Data x3c
  [  537.317755] lpfc :01:00.1: 1:(0):0727 TMF FCP_LUN_RESET to TGT 1 LUN 0 
failed (0, 0) iocb_flag x206
  [  537.317934] lpfc :01:00.1: 1:(0):0713 SCSI layer issued Device Reset 
(1, 0) return x2007
  [  537.318005] lpfc :01:00.1: 1:0372 iotag x0 is out off range: max iotag 
(x880)
  [  551.653563] lpfc :01:00.0: 0:(0):0748 abort handler timed out waiting 
for abortng I/O (xri:x149) to complete: ret 0x2003, ID 1, LUN 1
  [  551.653795] lpfc :01:00.0: 0:0372 iotag x0 is out off range: max iotag 
(x880)
  [  598.757557] lpfc :01:00.1: 1:0338 IOCB wait timeout error - no wake 
response Data x3c
  [  598.757766] lpfc :01:00.1: 1:(0):0727 TMF FCP_LUN_RESET to TGT 1 LUN 1 
failed (0, 0) iocb_flag x206
  [  598.757946] lpfc :01:00.1: 1:(0):0713 SCSI layer issued Device Reset 
(1, 1) return x2007
  [  598.758017] lpfc :01:00.1: 1:0372 iotag x0 is out off range: max iotag 
(x880)
  [  613.093562] lpfc :01:00.0: 0:(0):0748 abort handler timed out waiting 
for abortng I/O (xri:x14f) to complete: ret 0x2003, ID 1, LUN 0
  [  613.093630] INFO: task systemd-udevd:1148 blocked for more than 120 
seconds.
  [  613.093631]   Not tainted 4.9.0-12-generic #13-Ubuntu
  [  613.093631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  613.093632] systemd-udevd   D0  1148   1141 0x0004

   
  Stack trace output:
   [  613.093633] Call Trace:
  [  613.093634] [c01fd6b5b360] [] 0x 
(unreliable)
  [  613.093636]

[Kernel-packages] [Bug 1629512] Re: HDD failed command: SET FEATURES error

2017-03-23 Thread Jean-Pierre van Riel

I too see this error for Seagate 'ST3500418AS' SATA drives via 88SE9123
PCIe SATA 6.0 Gb/s controller (Ubuntu 16.04.2, latest 4.8 Kernel)


```
exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
irq_stat 0x4001
failed command: SET FEATURES
cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 4
status: { DRDY ERR }
error: { ABRT }
```

Note:

- `Emask 0x1` = "device reported error"
- `status: { DRDY ERR }` = device ready, but with error

If it relates to other posts on the internet, it might be benign and
simply failed power management setting attempts, or the like via the
Marvel controller.

To note, I have other SSD drives in the system that are connected via a
different controller (SB850) and also don't support APM, but they don't
exhibit this error!


`cmd ef/05:fe:00:00:00/00:00:00:00:00/40` requires understanding ATA commands 
to know what the above command is attempting. As per the "Enable/disable 
advanced power management" section of the ATA.8 standard:

- "Subcommand code `05h` allows the host to enable Advanced Power Management."
- `FEh` = Maximum performance

So this confirms:

- ATA command = ef = SET FEATURE
- ATA Feature = 05 = Advanced Power Management4
- ATA NSect = fe = 254 = Maximum performance
- remainder of string ":00:00:00/00:00:00:00:00/40" is addressing 

SOMETHING during boot is trying to set APM on drives that don't support
it!!!

I checked udev rules - this doesn't seem to be udev...

```
$ grep -r hdparm /lib/udev/*
/lib/udev/hdparm:. /lib/hdparm/hdparm-functions
/lib/udev/hdparm:   if grep -wq nohdparm /proc/cmdline ; then
/lib/udev/hdparm:OPTIONS=$(hdparm_options $DEVNAME)
/lib/udev/hdparm:   /sbin/hdparm $OPTIONS $DEVNAME 2>/dev/null
/lib/udev/rules.d/85-hdparm.rules:ACTION=="add", SUBSYSTEM=="block", 
KERNEL=="[sh]d[a-z]", RUN+="/lib/udev/hdparm"
```

Tracing the udev -> hdparm scritping, I found that in 
`/lib/hdparm/hdparm-functions`, there is `hdparm_options()` and 
`hdparm_try_apm()`, which might default to `hdparm_set_option -B254`
```

and

```
hdparm_try_apm()
{
# set our default global apm policy here.
if [ -z "$ID_PATH" ]; then
local ID_PATH="$(udevadm info -n "$1" -q property 2>/dev/null | sed -n 
's/^ID_PATH=//p')" || true
fi
case $ID_PATH in
pci-*-ieee1394-*|pci-*-usb-*)
return 1
;;
esac
return 0
}
```

But in my case, when I query udev properties for the device, I see this

```
$ udevadm info -n /dev/sdg
...
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
...
```

But I do not see `ID_ATA_FEATURE_SET_APM=1` so udev is, or it shouldn't
be setting APM on my drive that doesn't support it...

So if it's not the normal system udev rules, I wondered if it might be
something about the init on initramfs trying to enable this, given that
does try to load block device drivers and probably runs udev rules in
preparation for mounting root. I uncompressed initramfs, but failed to
identify anything that sets the APM on drives that don't support it.

So it's still a mystery why APM is attempted when, clearly, it's obvious
the drives don't support it, and also, why only the HDD drives on the
marvel controller vs other SSDs (not on Marvel) that don't have APM?

Also, if I force `sudo hdparm -B 254 /dev/sdg` and tail
/var/log/kern.log, I can't trigger that same error seen during boot.

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

Title:
  HDD failed command: SET FEATURES error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When my computer boots, i get a screen with following errors

  [9.470860] ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
  [9.470880] ata6.00: irq_stat 0x4001
  [9.470893] ata6.00: failed command: SET FEATURES
  [9.470908] ata6.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 29
  [9.470908]  res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1 
(device error)
  [9.470942] ata6.00: status: { DRDY ERR }
  [9.470954] ata6.00: error: { ABRT }
  [9.506904] ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
  [9.506944] ata5.00: irq_stat 0x4001
  [9.506974] ata5.00: failed command: SET FEATURES
  [9.507008] ata5.00: cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 26
  [9.507008]  res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1 
(device error)
  [9.507083] ata5.00: status: { DRDY ERR }
  [9.507110] ata5.00: error: { ABRT }

  I stays there for like a minute before continue booting.

  It started after i upgrade to Ubuntu 16.04, i had no such errors with
  both HDD on Ubuntu 14.04

  The HDDs are western digital WDC WD20EZRX-00D. Both purchased same time.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  boby   2509 F pulseaudio
   /dev/snd/pcmC0D0p:   boby

[Kernel-packages] [Bug 1669941] Re: CIFS: Call echo service immediately after socket reconnect

** Changed in: linux (Ubuntu Yakkety)
   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/1669941

Title:
  CIFS: Call echo service immediately after socket reconnect

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  When using Azure Files, a "Host is down" error can occur with the
  Linux CIFS client when the client has been idle for an extended period
  of time.  Commit 4fcd1813e640 mostly resolved this issue and is
  already integrated into the Xenial kernel.

  The following additional patch is needed to fully resolve a related
  corner case. Please take this commit to the Xenial kernel and later:

  Call echo service immediately after socket reconnect
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b8c600120fc87d53642476f48c8055b38d6e14c7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669941/+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 1669023] Re: Kernel: Fix Transactional memory config typo

** Changed in: linux (Ubuntu Yakkety)
   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/1669023

Title:
  Kernel: Fix Transactional memory config typo

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Canonical,

  Please include the following fix on 16.10.  This typo is causing some issue 
on TM.
  The patches that causes this problem is 
ec2a04841b785373a6379af66032201a2b90922b on yakkety-ubuntu repo.

  commit 39715bf972ed4fee18fe5409609a971fb16b1771
  Author: Valentin Rothberg 
  Date:   Wed Oct 5 07:57:26 2016 +0200

  powerpc/process: Fix CONFIG_ALIVEC typo in restore_tm_state()
  
  It should be ALTIVEC, not ALIVEC.
  
  Cyril explains: If a thread performs a transaction with altivec and then
  gets preempted for whatever reason, this bug may cause the kernel to not
  re-enable altivec when that thread runs again. This will result in an
  altivec unavailable fault, when that fault happens inside a user
  transaction the kernel has no choice but to enable altivec and doom the
  transaction.
  
  The result is that transactions using altivec may get aborted more often
  than they should.
  
  The difficulty in catching this with a selftest is my deliberate use of
  the word may above. Optimisations to avoid FPU/altivec/VSX faults mean
  that the kernel will always leave them on for 255 switches. This code
  prevents the kernel turning it off if it got to the 256th switch (and
  userspace was transactional).
  
  Fixes: dc16b553c949 ("powerpc: Always restore FPU/VEC/VSX if hardware 
transactional memory in use")
  Reviewed-by: Cyril Bur 
  Signed-off-by: Valentin Rothberg 
  Signed-off-by: Michael Ellerman 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669023/+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 1670726] Re: h-prod does not function across cores

** Changed in: linux (Ubuntu Yakkety)
   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/1670726

Title:
  h-prod does not function across cores

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  There is a  performance problem issue with h-prod. I can see that
  h-prod calls are only waking hardware threads from a h-cede call when
  the caller is on the same core as the thread being awoken (sibling
  theads).  For cross core prods the target thread remains in h-cede
  until its next decrementer interrupt.  That is causing guest OS some
  significant dispatching delays.

   The fix is now upstream as commit 8464c8842de2 ("KVM: PPC: Book3S HV:
  Fix H_PROD to actually wake the target vcpu", 2016-12-06) in
  v4.11-rc1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670726/+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 1667081] Re: Nvlink2: Additional patches

** Changed in: linux (Ubuntu Yakkety)
   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/1667081

Title:
  Nvlink2: Additional patches

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Hello Canonical,

  Could you please integrate the patches to enable NVLink2 in Ubuntu?

  They are, so far:

  
   commit 616badd2fb499320d3ac3b54462f55dededd0e0f
Author: Alistair Popple 
Date:   Tue Jan 10 15:41:44 2017 +1100

powerpc/powernv: Use OPAL call for TCE kill on NVLink2

Add detection of NPU2 PHBs. NPU2/NVLink2 has a different register
layout for the TCE kill register therefore TCE invalidation should be
done via the OPAL call rather than using the register directly as it
is for PHB3 and NVLink1. This changes TCE invalidation to use the OPAL
call in the case of a NPU2 PHB model.

  
  commit 1d0761d2557d1540727723e4f05395d53321d555
  Author: Alistair Popple 
  Date:   Wed Dec 14 13:36:51 2016 +1100

  powerpc/powernv: Initialise nest mmu
  
  POWER9 contains an off core mmu called the nest mmu (NMMU). This is
  used by other hardware units on the chip to translate virtual
  addresses into real addresses. The unit attempting an address
  translation provides the majority of the context required for the
  translation request except for the base address of the partition table
  (ie. the PTCR) which needs to be programmed into the NMMU.
  
  This patch adds a call to OPAL to set the PTCR for the nest mmu in
  opal_init().
  

  These patches are, still, in the powerpc-next tree.

  == Comment: #2 - Breno Henrique Leitao  - 2017-02-22 
13:33:59 ==
  In order to support NVLink2, the memory hotplugs should be applied also, they 
are:

  0d0a4bc powerpc/mm: unstub radix__vmemmap_remove_mapping()
  4b5d62c powerpc/mm: add radix__remove_section_mapping()
  6cc2734 powerpc/mm: add radix__create_section_mapping()
  b5200ec powerpc/mm: refactor radix physical page mapping
  32b53c0 powerpc/mm: Fix memory hotplug BUG() on radix
  c3352cb dt: add documentation of "hotpluggable" memory property
  41a9ada of/fdt: mark hotpluggable memory
  114cf3c mm: enable CONFIG_MOVABLE_NODE on non-x86 arches
  39fa104 mm: remove x86-only restriction of movable_node
  4a3bac4 powerpc/mm: allow memory hotplug into a memoryless node

  Note that you need to set CONFIG_MOVABLE_NODE=y.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667081/+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 1674680] Re: Deprecated rfcomm.conf still mentioned

2017-03-23 Thread Mathew Hodson

** Changed in: bluez (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: bluez (Ubuntu Yakkety)
   Importance: Undecided => Low

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

Title:
  Deprecated rfcomm.conf still mentioned

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  New

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+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 1578141] Re: Predictable interface names partially broken with igb driver

2017-03-23 Thread Spike

quick update, fwiw I just got an updated bios from a SM tech and it
worked:

$ sudo biosdevname -d | grep "BIOS dev" 
 
BIOS device: em1
BIOS device: em2
BIOS device: em3
BIOS device: em4

The bios's reported version from the BIOS screen is 3.2, which @pdxvoyd
said he had problems with, but I guess for me it's the complete opposite
since I had probs on 3.0 which he said worked for him and 3.2 fixes it
for me which didn't work for him.

In any case something should probably happen with systemd to handle
clashing names because these are servers, not desktop boxes, and
automation is pretty much impossible if network interfaces fail to come
back.

best,

Spike

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

Title:
  Predictable interface names partially broken with igb driver

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

Bug description:
  Note: I'm not sure whether this is really a kernel bug or something
  within systemd/udev, please advise how to further debug.

  On a system with two GE ports, instead of getting named eno1 and eno2,
  I am getting eno1 and renameN. Where N starts at 3 and increases by 2
  on every iteration of doing "rmmod igb;modprobe igb". The
  corresponding lines in dmesg look like this:

  [2.748429] igb :07:00.0: added PHC on eth0
  [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection
  [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8e
  [2.748505] igb :07:00.0: eth0: PBA No: 106100-000
  [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.802555] igb :07:00.1: added PHC on eth1
  [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection
  [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8f
  [2.802631] igb :07:00.1: eth1: PBA No: 106100-000
  [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.803618] igb :07:00.0 eno1: renamed from eth0
  [2.833208] igb :07:00.1 rename3: renamed from eth1

  What is even worse: Sometimes the naming changes and the second
  interface ends up as eno1 while the first interface is named renameN
  with an even N. The bad thing about this version is that when it
  happens while the installer is running, the installer will setup
  "rename2" as the primary network interface, which works fine for the
  installation itself, but after installation is finished and the first
  boot of the installed system happens, that interface will be gone,
  leaving the system without network connectivity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  4 09:48 seq
   crw-rw 1 root audio 116, 33 May  4 09:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed May  4 10:00:39 2016
  HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   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 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   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
  MachineType: Supermicro X9DRT-HF+
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRT-HF+
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro

[Kernel-packages] [Bug 1671760] Re: Xen HVM guests running linux 4.10 fail to boot on Intel hosts

This bug was fixed in the package xen - 4.7.2-0ubuntu1

---
xen (4.7.2-0ubuntu1) yakkety; urgency=medium

  * Rebasing to upstream stable release 4.7.2 (LP: #1672767)
https://www.xenproject.org/downloads/xen-archives/xen-47-series.html
- Includes fix for booting 4.10 Linux kernels in HVM guests on Intel
  hosts which support the TSC_ADJUST MSR (LP: #1671760)
- Dropping: d/p/preup-tools-fix-linear-p2m-save.patch which is part
  of the stable update.
- Additional security relevant changes:
  * XSA-207
- memory leak when destroying guest without PT devices
- Replacing the following security fixes with the versions from the
  stable update:
  * CVE-2016-6258 / XSA-182
- x86: Privilege escalation in PV guests
  * CVE-2016-6259 / XSA-183
- x86: Missing SMAP whitelisting in 32-bit exception / event delivery
  * CVE-2016-7092 / XSA-185
- x86: Disallow L3 recursive pagetable for 32-bit PV guests
  * CVE-2016-7093 / XSA-186
- x86: Mishandling of instruction pointer truncation during emulation
  * CVE-2016-7094 / XSA-187
- x86 HVM: Overflow of sh_ctxt->seg_reg[]
  * CVE-2016- / XSA-190
- CR0.TS and CR0.EM not always honored for x86 HVM guests
  * CVE-2016-9386 / XSA-191
- x86 null segments not always treated as unusable
  * CVE-2016-9382 / XSA-192
- x86 task switch to VM86 mode mis-handled
  * CVE-2016-9385 / XSA-193
- x86 segment base write emulation lacking canonical address checks
  * CVE-2016-9384 / XSA-194
- guest 32-bit ELF symbol table load leaking host data
  * CVE-2016-9383 / XSA-195
- x86 64-bit bit test instruction emulation broken
  * CVE-2016-9377, CVE-2016-9378 / XSA-196
- x86 software interrupt injection mis-handled
  * CVE-2016-9379, CVE-2016-9380 / XSA-198
- delimiter injection vulnerabilities in pygrub
  * CVE-2016-9932 / XSA-200
- x86 CMPXCHG8B emulation fails to ignore operand size override
  * CVE-2016-9815, CVE-2016-9816, CVE-2016-9817, CVE-2016-9818 / XSA-201
- ARM guests may induce host asynchronous abort
  * CVE-2016-10024 / XSA-202
- x86 PV guests may be able to mask interrupts
  * CVE-2016-10025 / XSA-203
- x86: missing NULL pointer check in VMFUNC emulation
  * CVE-2016-10013 / XSA-204
- x86: Mishandling of SYSCALL singlestep during emulation
  * Copy contents of debian/build/install-utils_$(ARCH)/usr/sbin into
debian/build/install-utils_$ARCH/usr/lib/xen-$(VERSION) (LP: #1396670).

 -- Stefan Bader   Tue, 14 Mar 2017 15:45:59
+0100

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

Title:
  Xen HVM guests running linux 4.10 fail to boot on Intel hosts

Status in linux package in Ubuntu:
  Won't Fix
Status in xen package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in xen source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in xen source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Invalid
Status in xen source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Won't Fix
Status in xen source package in Zesty:
  Fix Released

Bug description:
  Starting with Linux kernel 4.10, the kernel does some sanity checking
  on the TSC_ADJUST MSR. Xen has implemented some support for that MSR
  in the hypervisor (Xen 4.3 and later) for HVM guests. But boot and
  secondary vCPUs are set up inconsistently. This causes the boot of a
  4.10 HVM guest to hang early on boot.

  This was fixed in the hypervisor by:

    commit 98297f09bd07bb63407909aae1d309d8adeb572e
    x86/hvm: do not set msr_tsc_adjust on hvm_set_guest_tsc_fixed

  That fix would be contained in 4.6.5 and 4.7.2 and would be in 4.8.1
  (not released, yet) which mean that Ubuntu 14.04/16.04/16.10 and 17.04
  currently are affected.

  ---

  SRU Justification:

  Impact: Without the TSC_ADJUST MSR fix, 4.10 and later kernels will
  get stuck at boot when running as (PV)HVM guests on Xen 4.3 and later.

  Fix: Above fix either individually applied or as part of Xen stable
  stream (for Xen 4.7.x and 4.6.x) resolves the issue.

  Testcase:
  - Requires Intel based host which supports the TSC_ADJUST MSR
  - Configured as Xen host
  - HVM guest running Zesty/17.04
  - Stuck at boot before, normal booting OS after

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671760/+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 1671760] Re: Xen HVM guests running linux 4.10 fail to boot on Intel hosts

This bug was fixed in the package xen - 4.6.5-0ubuntu1

---
xen (4.6.5-0ubuntu1) xenial; urgency=medium

  * Rebasing to upstream stable release 4.6.5 (LP: #1671864)
https://www.xenproject.org/downloads/xen-archives/xen-46-series.html
- Includes fix for booting 4.10 Linux kernels in HVM guests on Intel
  hosts which support the TSC_ADJUST MSR (LP: #1671760)
- Additional security relevant changes:
  * CVE-2013-2076 / XSA-052 (update)
- Information leak on XSAVE/XRSTOR capable AMD CPUs
  * CVE-2016-7093 / XSA-186 (4.6.3 became vulnerable)
- x86: Mishandling of instruction pointer truncation during emulation
  * XSA-207
- memory leak when destroying guest without PT devices
- Replacing the following security fixes with the versions from the
  stable update:
  * CVE-2015-7812 / XSA-145
- arm: Host crash when preempting a multicall
  * CVE-2015-7813 / XSA-146
- arm: various unimplemented hypercalls log without rate limiting
  * CVE-2015-7814 / XSA-147
- arm: Race between domain destruction and memory allocation decrease
  * CVE-2015-7835 / XSA-148
- x86: Uncontrolled creation of large page mappings by PV guests
  * CVE-2015-7969 / XSA-149, XSA-151
- leak of main per-domain vcpu pointer array
- x86: leak of per-domain profiling-related vcpu pointer array
  * CVE-2015-7970 / XSA-150
- x86: Long latency populate-on-demand operation is not preemptible
  * CVE-2015-7971 / XSA-152
- x86: some pmu and profiling hypercalls log without rate limiting
  * CVE-2015-7972 / XSA-153
- x86: populate-on-demand balloon size inaccuracy can crash guests
  * CVE-2016-2270 / XSA-154
- x86: inconsistent cachability flags on guest mappings
  * CVE-2015-8550 / XSA-155
- paravirtualized drivers incautious about shared memory contents
  * CVE-2015-5307, CVE-2015-8104 / XSA-156
- x86: CPU lockup during exception delivery
  * CVE-2015-8338 / XSA-158
- long running memory operations on ARM
  * CVE-2015-8339, CVE-2015-8340 / XSA-159
XENMEM_exchange error handling issues
  * CVE-2015-8341 / XSA-160
- libxl leak of pv kernel and initrd on error
  * CVE-2015-8555 / XSA-165
- information leak in legacy x86 FPU/XMM initialization
  * XSA-166
- ioreq handling possibly susceptible to multiple read issue
  * CVE-2016-1570 / XSA-167
- PV superpage functionality missing sanity checks
  * CVE-2016-1571 / XSA-168
- VMX: intercept issue with INVLPG on non-canonical address
  * CVE-2015-8615 / XSA-169
- x86: unintentional logging upon guest changing callback method
  * CVE-2016-2271 / XSA-170
- VMX: guest user mode may crash guest with non-canonical RIP
  * CVE-2016-3158, CVE-2016-3159 / XSA-172
- broken AMD FPU FIP/FDP/FOP leak workaround
  * CVE-2016-3960 / XSA-173
- x86 shadow pagetables: address width overflow
  * CVE-2016-4962 / XSA-175
- Unsanitised guest input in libxl device handling code
  * CVE-2016-4480 / XSA-176
- x86 software guest page walk PS bit handling flaw
  * CVE-2016-4963 / XSA-178
- Unsanitised driver domain input in libxl device handling
  * CVE-2016-5242 / XSA-181
- arm: Host crash caused by VMID exhaustion
  * CVE-2016-6258 / XSA-182
- x86: Privilege escalation in PV guests
  * CVE-2016-6259 / XSA-183
- x86: Missing SMAP whitelisting in 32-bit exception / event delivery
  * CVE-2016-7092 / XSA-185
- x86: Disallow L3 recursive pagetable for 32-bit PV guests
  * CVE-2016-7094 / XSA-187
- x86 HVM: Overflow of sh_ctxt->seg_reg[]
  * CVE-2016- / XSA-190
- CR0.TS and CR0.EM not always honored for x86 HVM guests
  * CVE-2016-9386 / XSA-191
- x86 null segments not always treated as unusable
  * CVE-2016-9382 / XSA-192
- x86 task switch to VM86 mode mis-handled
  * CVE-2016-9385 / XSA-193
- x86 segment base write emulation lacking canonical address checks
  * CVE-2016-9383 / XSA-195
- x86 64-bit bit test instruction emulation broken
  * CVE-2016-9377, CVE-2016-9378 / XSA-196
- x86 software interrupt injection mis-handled
  * CVE-2016-9379, CVE-2016-9380 / XSA-198
- delimiter injection vulnerabilities in pygrub
  * CVE-2016-9932 / XSA-200
- x86 CMPXCHG8B emulation fails to ignore operand size override
  * CVE-2016-9815, CVE-2016-9816, CVE-2016-9817, CVE-2016-9818 / XSA-201
- ARM guests may induce host asynchronous abort
  * CVE-2016-10024 / XSA-202
- x86 PV guests may be able to mask interrupts
  * CVE-2016-10025 / XSA-203
- x86: missing NULL pointer check in VMFUNC emulation
  * CVE-2016-10013 / XSA-204
- x86: Mishandling of SYSCALL singlestep during emulation

[Kernel-packages] [Bug 1671760] Re: Xen HVM guests running linux 4.10 fail to boot on Intel hosts

This bug was fixed in the package xen - 4.4.2-0ubuntu0.14.04.10

---
xen (4.4.2-0ubuntu0.14.04.10) trusty; urgency=medium

  * Backport upstream change to fix TSC_ADJUST MSR handling in HVM
guests running on Intel based hosts (LP: #1671760)

 -- Stefan Bader   Tue, 14 Mar 2017 11:17:48
+0100

** Changed in: xen (Ubuntu Trusty)
   Status: Fix Committed => 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/1671760

Title:
  Xen HVM guests running linux 4.10 fail to boot on Intel hosts

Status in linux package in Ubuntu:
  Won't Fix
Status in xen package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in xen source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in xen source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Invalid
Status in xen source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Won't Fix
Status in xen source package in Zesty:
  Fix Released

Bug description:
  Starting with Linux kernel 4.10, the kernel does some sanity checking
  on the TSC_ADJUST MSR. Xen has implemented some support for that MSR
  in the hypervisor (Xen 4.3 and later) for HVM guests. But boot and
  secondary vCPUs are set up inconsistently. This causes the boot of a
  4.10 HVM guest to hang early on boot.

  This was fixed in the hypervisor by:

    commit 98297f09bd07bb63407909aae1d309d8adeb572e
    x86/hvm: do not set msr_tsc_adjust on hvm_set_guest_tsc_fixed

  That fix would be contained in 4.6.5 and 4.7.2 and would be in 4.8.1
  (not released, yet) which mean that Ubuntu 14.04/16.04/16.10 and 17.04
  currently are affected.

  ---

  SRU Justification:

  Impact: Without the TSC_ADJUST MSR fix, 4.10 and later kernels will
  get stuck at boot when running as (PV)HVM guests on Xen 4.3 and later.

  Fix: Above fix either individually applied or as part of Xen stable
  stream (for Xen 4.7.x and 4.6.x) resolves the issue.

  Testcase:
  - Requires Intel based host which supports the TSC_ADJUST MSR
  - Configured as Xen host
  - HVM guest running Zesty/17.04
  - Stuck at boot before, normal booting OS after

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671760/+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 1671760] Update Released

2017-03-23 Thread Brian Murray

The verification of the Stable Release Update for xen has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Xen HVM guests running linux 4.10 fail to boot on Intel hosts

Status in linux package in Ubuntu:
  Won't Fix
Status in xen package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in xen source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in xen source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Invalid
Status in xen source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Won't Fix
Status in xen source package in Zesty:
  Fix Released

Bug description:
  Starting with Linux kernel 4.10, the kernel does some sanity checking
  on the TSC_ADJUST MSR. Xen has implemented some support for that MSR
  in the hypervisor (Xen 4.3 and later) for HVM guests. But boot and
  secondary vCPUs are set up inconsistently. This causes the boot of a
  4.10 HVM guest to hang early on boot.

  This was fixed in the hypervisor by:

    commit 98297f09bd07bb63407909aae1d309d8adeb572e
    x86/hvm: do not set msr_tsc_adjust on hvm_set_guest_tsc_fixed

  That fix would be contained in 4.6.5 and 4.7.2 and would be in 4.8.1
  (not released, yet) which mean that Ubuntu 14.04/16.04/16.10 and 17.04
  currently are affected.

  ---

  SRU Justification:

  Impact: Without the TSC_ADJUST MSR fix, 4.10 and later kernels will
  get stuck at boot when running as (PV)HVM guests on Xen 4.3 and later.

  Fix: Above fix either individually applied or as part of Xen stable
  stream (for Xen 4.7.x and 4.6.x) resolves the issue.

  Testcase:
  - Requires Intel based host which supports the TSC_ADJUST MSR
  - Configured as Xen host
  - HVM guest running Zesty/17.04
  - Stuck at boot before, normal booting OS after

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671760/+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 1637550] Re: [Feature] R3 mwait support for Knights Mill

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

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

Title:
  [Feature] R3 mwait support for Knights Mill

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

Bug description:
  Enable r3 mwait for  Knights Mill.

  Schedule:
  upstream: 4.11 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1637550/+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 1674748] Re: Intel 8265 does not work with 16.04 linux-firmware 1.157.8

So I'm clear, which file exactly do you need? Because we already have
the exact same iwlwifi-8265-{21,22}.ucode files in both 1.157.8 and
1.161.1.

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

Title:
  Intel 8265 does not work with 16.04 linux-firmware 1.157.8

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  In Progress
Status in linux-firmware source package in Yakkety:
  In Progress

Bug description:
  SRU Justification

  Impact: The current iwlwifi firmware lacks support for Intel 8265
  wireless.

  Fix: An updated version of the -22 ucode includes support for this
  hardware.

  Regression Potential: There were some regressions with earlier
  versions of the -22 ucode, but testing the most recent update found
  that these have been fixed. No additional regressions were found in
  testing.

  ---

  Using the Intel wireless firmware from 1.161.1 should fix this issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1674748/+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 1675564] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  After hibernation screen becomes completely pixellated.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This started happening just this morning. After resuming from
  hibernation, the screen becomes pixellated, and the screen around GUI
  apps, such as File Explorer or Terminal, also becomes pixellated when
  opened in a minimized window. Any help is appreciated. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-41-generic 4.8.0-41.44
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexander   2553 F pulseaudio
   /dev/snd/controlC0:  alexander   2553 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 23 17:17:57 2017
  HibernationDevice: RESUME=UUID=331f3735-3e6d-4a8e-b06c-64f51b2c9d36
  InstallationDate: Installed on 2017-01-22 (60 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP ENVY m7 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic.efi.signed 
root=UUID=6d932bfc-8d72-4c9c-b619-902eb6e1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-41-generic N/A
   linux-backports-modules-4.8.0-41-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVYm7NotebookPC:pvr096F120022405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY m7 Notebook PC
  dmi.product.version: 096F120022405F1620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675564/+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 1637550] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1637550

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => 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/1637550

Title:
  [Feature] R3 mwait support for Knights Mill

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

Bug description:
  Enable r3 mwait for  Knights Mill.

  Schedule:
  upstream: 4.11 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1637550/+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 1667160] Re: Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2

2017-03-23 Thread Michael Dye

Looks like the same issue as reported in
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1669802

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

Title:
  Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use
  wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And
  there's a RTL2838 DVB-T USB stick attached to monitor airplane
  positions for Flightradar24.

  After updateing the kernel from 4.8.0-1024, which runs flawlessly, to
  -1025, there's a kernel panic happening 10-20 seconds after booting up
  to the login prompt. I thought the -1026 fixed that, but it's still no
  worky. The trace is scrolling so fast I can't read anything but the
  last page:

  [<808c76c8>] (sock_sendmsg) from...
  [<808c7778>] (sock_write_iter) from...
  [<802c39c8>] (new_sync_write) from...
  [<802c3a4c>] (__vfs_write) from...
  [<802c48d8>] (vfs_write) from...
  [<802c5ab4>] (SyS_write) from...
  Code: e5922004 e0033002 e353 0a0a (e5902034)
  ---[ end trace 0f53d17efe0c6ba ]---
  Kernel panic - not syncing: Fatal exception in interrupt
  CPU2: stopping
  CPU: 2 PID: 21 Comm: migration/2 Tainted: G  D  4.8.0-1026-raspi2 
#29-Ubuntu
  Hardware name: BCM2709
  [<801120ac>] (unwind_backtrace) from ...
  [<8010d2dc>] (show_stack) from ...
  [<8059c38c>] (handle_IPI) from ...
  [<80101564>] (bcm2836_arm_irqchip_handle_irq) from [<80a49f3c>] 
(__irq_svc+0x5c/0x7c)
  Exception stack(0xbb99de68 to 0xbb99deb0)
  de60:    0004  0001 bac05de0 0001
  de80: bac05dcc  a00e0013  bac05d6c bb99dedc bb99dee0 bb99deb8
  dea0: 801d367c 801d35f4 600e0013 
  [<80a49f3c>] (__irq_svc) from ...
  [<801d35f4>] (multi_cpu_stop) from ...
  [<801d38ec>] (cpu_stopper_thread) from ...
  [<8014b71c>] (smpboot_thread_fn) from ...
  [<80147770>] (kthread) from [<80108e28>] (ret_from_fork+0x14/0x2c)

  
  And then this block repeats with CPU3 and CPU0.

  
  Going back to 4.8.0-1024 makes everything work again.

  
  Affected packages:

  linux-image-4.8.0-1025-raspi2:armhf (4.8.0-1025.28)
  linux-image-4.8.0-1026-raspi2:armhf (4.8.0-1026.29)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 25  2016 seq
   crw-rw 1 root audio 116, 33 Jul 25  2016 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.8.0-1024-raspi2.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: armhf
  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: N/A
  DistroRelease: Ubuntu 16.10
  Lsusb:
   Bus 001 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
   Bus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 
802.11n Wireless Adapter [Realtek RTL8188CUS]
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0xecd3f749 
smsc95xx.macaddr=B8:27:EB:D3:F7:49 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3ea0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: Ubuntu 4.8.0-1024.27-raspi2 4.8.16
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-1024-raspi2 N/A
   linux-backports-modules-4.8.0-1024-raspi2  N/A
   linux-firmware 1.161.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-1024-raspi2 armv7l
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to yakkety on 2016-10-24 (122 days ago)
  UserGroups: adm audio cdrom dialout floppy fuse netdev plugdev sudo users 
video www-data
  _MarkForUpload: False

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+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] Re: Update linux-firmware in xenial for 4.10 hwe-edge kernel

** Description changed:

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

-- 
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:
  In Progress

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 1675564] [NEW] After hibernation screen becomes completely pixellated.

2017-03-23 Thread Alexander Whatley

Public bug reported:

This started happening just this morning. After resuming from
hibernation, the screen becomes pixellated, and the screen around GUI
apps, such as File Explorer or Terminal, also becomes pixellated when
opened in a minimized window. Any help is appreciated. Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-41-generic 4.8.0-41.44
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  alexander   2553 F pulseaudio
 /dev/snd/controlC0:  alexander   2553 F pulseaudio
CurrentDesktop: Unity
Date: Thu Mar 23 17:17:57 2017
HibernationDevice: RESUME=UUID=331f3735-3e6d-4a8e-b06c-64f51b2c9d36
InstallationDate: Installed on 2017-01-22 (60 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Hewlett-Packard HP ENVY m7 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic.efi.signed 
root=UUID=6d932bfc-8d72-4c9c-b619-902eb6e1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-41-generic N/A
 linux-backports-modules-4.8.0-41-generic  N/A
 linux-firmware1.161.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.33
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 229D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 78.15
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVYm7NotebookPC:pvr096F120022405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY m7 Notebook PC
dmi.product.version: 096F120022405F1620180
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug 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/1675564

Title:
  After hibernation screen becomes completely pixellated.

Status in linux package in Ubuntu:
  New

Bug description:
  This started happening just this morning. After resuming from
  hibernation, the screen becomes pixellated, and the screen around GUI
  apps, such as File Explorer or Terminal, also becomes pixellated when
  opened in a minimized window. Any help is appreciated. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-41-generic 4.8.0-41.44
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexander   2553 F pulseaudio
   /dev/snd/controlC0:  alexander   2553 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 23 17:17:57 2017
  HibernationDevice: RESUME=UUID=331f3735-3e6d-4a8e-b06c-64f51b2c9d36
  InstallationDate: Installed on 2017-01-22 (60 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP ENVY m7 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic.efi.signed 
root=UUID=6d932bfc-8d72-4c9c-b619-902eb6e1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-41-generic N/A
   linux-backports-modules-4.8.0-41-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVYm7NotebookPC:pvr096F120022405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY m7 Notebook PC
  dmi.product.version: 096F120022405F1620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675564/+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 1674748] Re: Intel 8265 does not work with 16.04 linux-firmware 1.157.8

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

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

** Changed in: linux-firmware (Ubuntu)
   Status: Confirmed => Fix Released

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

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Xenial)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: linux-firmware (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Yakkety)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

** Description changed:

+ SRU Justification
+ 
+ Impact: The current iwlwifi firmware lacks support for Intel 8265
+ wireless.
+ 
+ Fix: An updated version of the -22 ucode includes support for this
+ hardware.
+ 
+ Regression Potential: There were some regressions with earlier versions
+ of the -22 ucode, but testing the most recent update found that these
+ have been fixed. No additional regressions were found in testing.
+ 
+ ---
+ 
  Using the Intel wireless firmware from 1.161.1 should fix this issue

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

Title:
  Intel 8265 does not work with 16.04 linux-firmware 1.157.8

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  In Progress
Status in linux-firmware source package in Yakkety:
  In Progress

Bug description:
  SRU Justification

  Impact: The current iwlwifi firmware lacks support for Intel 8265
  wireless.

  Fix: An updated version of the -22 ucode includes support for this
  hardware.

  Regression Potential: There were some regressions with earlier
  versions of the -22 ucode, but testing the most recent update found
  that these have been fixed. No additional regressions were found in
  testing.

  ---

  Using the Intel wireless firmware from 1.161.1 should fix this issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1674748/+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 1670518] Re: [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

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

** Changed in: linux (Ubuntu Xenial)
   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/1670518

Title:
  [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

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

Bug description:
  Looks like the rebase work missed some prerequisite patches in
  drivers/pci/host/pci-hyperv.c

  (Needed for SR-IOV in Azure on lts-xenial, HWE, and custom)

  commit 0de8ce3ee8e38cc66683438f715c79a2cc69539e
  Author: Long Li 
  Date:   Tue Nov 8 14:04:38 2016 -0800

  PCI: hv: Allocate physically contiguous hypercall params buffer

  hv_do_hypercall() assumes that we pass a segment from a physically
  contiguous buffer.  A buffer allocated on the stack may not work if
  CONFIG_VMAP_STACK=y is set.

  Use kmalloc() to allocate this buffer.

  
  commit 542ccf4551fa019a8ae9dfb7c8cd7e73a3d7e614
  Author: Tobias Klauser 
  Date:   Mon Oct 31 12:04:09 2016 +0100

  PCI: hv: Make unnecessarily global IRQ masking functions static

  Make hv_irq_mask() and hv_irq_unmask() static as they are only used in
  pci-hyperv.c

  This fixes a sparse warning.

  commit e74d2ebdda33b3bdd1826b5b92e9aa45bdf92bb3
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:19:52 2016 +

  PCI: hv: Delete the device earlier from hbus->children for hot-
  remove

  After we send a PCI_EJECTION_COMPLETE message to the host, the host will
  immediately send us a PCI_BUS_RELATIONS message with
  relations->device_count == 0, so pci_devices_present_work(), running on
  another thread, can find the being-ejected device, mark the
  hpdev->reported_missing to true, and run list_move_tail()/list_del() for
  the device -- this races hv_eject_device_work() -> list_del().

  Move the list_del() in hv_eject_device_work() to an earlier place, i.e.,
  before we send PCI_EJECTION_COMPLETE, so later the
  pci_devices_present_work() can't see the device.

  
  commit 17978524a636d007e6b929304ae3eb5ea0371019
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:18:47 2016 +

  PCI: hv: Fix hv_pci_remove() for hot-remove

  1. We don't really need such a big on-stack buffer when sending the
  teardown_packet: vmbus_sendpacket() here only uses sizeof(struct
  pci_message).

  2. In the hot-remove case (PCI_EJECT), after we send PCI_EJECTION_COMPLETE
  to the host, the host will send a RESCIND_CHANNEL message to us and the
  host won't access the per-channel ringbuffer any longer, so we needn't 
send
  PCI_RESOURCES_RELEASED/PCI_BUS_D0EXIT to the host, and we shouldn't expect
  the host's completion message of PCI_BUS_D0EXIT, which will never come.

  3. We should send PCI_BUS_D0EXIT after
  hv_send_resources_released().

  Signed-off-by: Dexuan Cui 
  Signed-off-by: Bjorn Helgaas 
  Reviewed-by: Jake Oshins 
  Acked-by: K. Y. Srinivasan 
  CC: Haiyang Zhang 
  CC: Vitaly Kuznetsov 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670518/+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 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520

** Changed in: linux (Ubuntu Xenial)
   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/1672439

Title:
  No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
  5520

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

Bug description:
  My processor does not appear to be utilizing and idling states deeper
  than C3.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   2446 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 13 08:57:06 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88
  InstallationDate: Installed on 2017-03-09 (3 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IwConfig:
   lono wireless extensions.
   
   wlp2s0no wireless extensions.
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 
root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+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 1637550] Re: [Feature] R3 mwait support for Knights Mill

** Information type changed from Proprietary to Public

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Robert Hooker (sarvatt)

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

Title:
  [Feature] R3 mwait support for Knights Mill

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Enable r3 mwait for  Knights Mill.

  Schedule:
  upstream: 4.11 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1637550/+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 1670544] Re: [Hyper-V] Rebase Hyper-V to the upstream 4.10 kernel

2017-03-23 Thread Tim Gardner

Test kernel at http://kernel.ubuntu.com/~rtg/hv-lp1670544/

git://kernel.ubuntu.com/rtg/ubuntu-yakkety.git hv

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

Title:
  [Hyper-V] Rebase Hyper-V to the upstream 4.10 kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Catching up with upstream 4.10 Hyper-V, files:
  arch/x86/kernel/cpu/mshyperv.c
  arch/x86/include/asm/mshyperv.h
  arch/x86/include/uapi/asm/hyperv.h
  include/linux/hyperv.h
  drivers/hv/channel.c
  drivers/hv/channel_mgmt.c
  drivers/hv/connection.c
  drivers/hv/hv_balloon.c
  drivers/hv/hv.c
  drivers/hv/hv_fcopy.c
  drivers/hv/hv_kvp.c
  drivers/hv/hv_snapshot.c
  drivers/hv/hv_util.c
  drivers/hv/hv_utils_transport.c
  drivers/hv/hv_utils_transport.h
  drivers/hv/hyperv_vmbus.h
  drivers/hv/ring_buffer.c
  drivers/hv/vmbus_drv.c
  tools/hv/hv_fcopy_daemon.c
  tools/hv/hv_get_dhcp_info.sh
  tools/hv/hv_get_dns_info.sh
  tools/hv/hv_kvp_daemon.c
  tools/hv/hv_set_ifconfig.sh
  tools/hv/hv_vss_daemon.c
  tools/hv/lsvmbus
  drivers/input/serio/hyperv-keyboard.c
  drivers/net/hyperv/hyperv_net.h
  drivers/net/hyperv/netvsc.c
  drivers/net/hyperv/netvsc_drv.c
  drivers/net/hyperv/rndis_filter.c
  drivers/scsi/storvsc_drv.c
  drivers/hid/hid-hyperv.c
  drivers/pci/host/pci-hyperv.c
  drivers/video/fbdev/hyperv_fb.c
  drivers/uio/uio_hv_generic.c

  Here is the delta from 4.9 to 4.10:
  mshyperv.c : commit a5a1d1c2914b5316924c7893eb683a5420ebd3be : 
clocksource: Use a plain u64 instead of cycle_t
  hyperv.h : commit 433e19cf33d34bb6751c874a9c00980552fe508c : Drivers: hv: 
vmbus: finally fix hv_need_to_signal_on_read()
  hyperv.h : commit f45be72c8ec0b85263d1fe1e6c681d8c87e198e6 : hyperv: Fix 
spelling of HV_UNKOWN
  hyperv.h : commit fc76936d3ea5720a6e0948a08381b803a68deb28 : vmbus: add 
support for dynamic device id's
  hyperv.h : commit 1f6ee4e7d83586c8b10bd4f2f4346353d04ce884 : Drivers: hv: 
vmbus: On write cleanup the logic to interrupt the host
  hyperv.h : commit fa32ff6576623616c1751562edaed8c164ca5199 : Drivers: hv: 
ring_buffer: count on wrap around mappings in get_next_pkt_raw() (v2)
  channel.c : commit 1f6ee4e7d83586c8b10bd4f2f4346353d04ce884 : Drivers: 
hv: vmbus: On write cleanup the logic to interrupt the host
  channel.c : commit 3372592a140db69fd63837e81f048ab4abf8111e : Drivers: 
hv: vmbus: On the read path cleanup the logic to interrupt the host
  channel_mgmt.c : commit f45be72c8ec0b85263d1fe1e6c681d8c87e198e6 : 
hyperv: Fix spelling of HV_UNKOWN
  channel_mgmt.c : commit abd1026da4a7700a8db370947f75cd17b6ae6f76 : hv: 
acquire vmbus_connection.channel_mutex in vmbus_free_channels()
  channel_mgmt.c : commit 74198eb4a42c4a3c4fbef08fa01a291a282f7c2e : 
Drivers: hv: vmbus: Base host signaling strictly on the ring state
  connection.c : commit 95096f2fbd10186d3e78a328b327afc71428f65f : 
uio-hv-generic: new userspace i/o driver for VMBus
  hv_balloon.c : commit b3bb97b8a49f3c489134793705bc636c7883e777 : Drivers: 
hv: balloon: Add logging for dynamic memory operations
  hv_balloon.c : commit 8500096017e3a1baadbdefe8b84a99117472af46 : Drivers: 
hv: balloon: Fix info request to show max page count
  hv_balloon.c : commit 8ba8c0a111083bfe53f7a8a0e2f14fd12eb2e030 : Drivers: 
hv: balloon: Disable hot add when CONFIG_MEMORY_HOTPLUG is not set
  hv.c : commit a5a1d1c2914b5316924c7893eb683a5420ebd3be : clocksource: Use 
a plain u64 instead of cycle_t
  hv.c : commit 6ffc4b85358f6b7d252420cfa5862312cf5f83d8 : hv: change 
clockevents unbind tactics
  hv_snapshot.c : commit b357fd3908c1191f2f56e38aa77f2aecdae18bc8 : 
Drivers: hv: vss: Operation timeouts should match host expectation
  hv_snapshot.c : commit 23d2cc0c29eb0e7c6fe4cac88098306c31c40208 : 
Drivers: hv: vss: Improve log messages.
  hv_util.c : commit 3da0401b4d0e17aea7526db0235d98fa535d903e : Drivers: 
hv: utils: Fix the mapping between host version and protocol to use
  hyperv_vmbus.h : commit d7edd31ba9a661f1a3f357b43e84e84e5fad9538 : 
Drivers: hv: utils: reduce HV_UTIL_NEGO_TIMEOUT timeout
  ring_buffer.c : commit 433e19cf33d34bb6751c874a9c00980552fe508c : 
Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read()
  vmbus_drv.c : commit fc76936d3ea5720a6e0948a08381b803a68deb28 : vmbus: 
add support for dynamic device id's
  vmbus_drv.c : commit f6b2db084b65b9dc0f910bc48d5f77c0e5166dc6 : vmbus: 
make sysfs names consistent with PCI
  hv_fcopy_daemon.c : commit 0c38cda64aecb4a821210bb2d3d04092c181c0ae : 
tools: hv: remove unnecessary header files and netlink related code
  hv_kvp_daemon.c : commit 0c38cda64aecb4a821210bb2d3d04092c181c0ae : 
tools: hv: remove unnecessary header

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

2017-03-23 Thread Karlyn Fielding

I can confirm that I have the same issue being reported here.   I have a
Dell XPS13 Developer Edition (9360) with Ubuntu 16.04, TB16 Dock and an
upgraded Ubuntu Mainline build kernel of 4.10.4.

Additionally, I tried downloading the source code from Realtek for their
v2.08.0 r8152 driver.   I compiled that driver and manually removed and
re-inserted the new kernel module into my running system.  With that
driver running, I see the exact same behavior described here.

I'd be happy to volunteer for any testing on my hardware that might help
debug the issue.

I can also confirm that changing the connection speed to 100Mb with
ethtool provides a work around to the problem.

Also, I have some kernel output I have saved while experiencing the
issue if there is interest in 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/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 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

[Kernel-packages] [Bug 1675522] Re: arm64: Synchronous Exception at 0x00000000BBC129BC

Upgrading the host from xenial's QEMU to zesty's QEMU seems to fix it. I
can do several reboots of zesty w/o a hang.

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

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

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

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

Title:
  arm64: Synchronous Exception at 0xBBC129BC

Status in edk2 package in Ubuntu:
  Invalid
Status in grub2 package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  New

Bug description:
  I installed a KVM VM with the zesty beta server ISO. The install went
  well but, upon reboot, GRUB entered a Synchronous Exception loop after
  selecting the Ubuntu boot option.

  After killing qemu-system-aarch64 and restarting the VM, the system
  booted to a prompt w/o issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1675522/+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 1667416] Re: PowerNV: No rate limit for kernel error "KVM can't copy data from"

No, it didn't. There was a regression in a recent update, and the kernel
that was in -proposed got replaced with one that only has the reverts
necessary to fix the regression. That's the kernel you tested.

Sorry for the confusion. I'll remove the verification tags, and once a
new kernel with the fix is in -proposed there will be another comment
asking for testing.

** Tags removed: verification-failed-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/1667416

Title:
  PowerNV: No rate limit for kernel error "KVM can't copy data from"

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  == Comment: #0 - MIKHAIL S. MEDVEDEV  - 2017-02-03 
14:40:58 ==
  ---Problem Description---
  I am experiencing a problem with KVM on Power with a symptom of "KVM can't 
copy data" message being spammed to kern.log at about 10 messages a second. 
Apart from original problem that triggers the error, the printk is a problem on 
its own. System might run out of space for logs, and would have high CPU load 
caused by journald.

  This bug is to address an absence of rate limiter on printk at
  
https://github.com/torvalds/linux/blob/f64e8084c94bb0449177364856d8117e2f14c4c0/arch/powerpc/kvm/book3s_64_mmu.c#L268

  Maybe wrapping the printk in printk_ratelimit() is all that is
  required?

  if(printk_ratelimit()){
 printk("KVM can't copy");
  }
   
  Contact Information = Mikhail Medvedev / mmedv...@us.ibm.com, Rafael Folco / 
rfo...@br.ibm.com 
   
  ---uname output---
  4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le 
ppc64le ppc64le GNU/Linux
   
  Machine Type = KVM guest on P8 8247 21L  
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Deploy OpenStack with devstack
  2. Run simultaneously between 4 and 6 instances of a script that
  - boots a VM (openstack server create)
  - immediately creates the backup of the VM (openstack server backup 
create)

  This is not a very good way to reproduce it. I am still unable to
  reproduce the problem just by using libvirt and qemu.

  
  == Comment: #5 - VIPIN K. PARASHAR  - 2017-02-07 
09:42:31 ==

  From kernel logs
  ===

  [852719.001593] KVM can't copy data from 0x3fff86683c80!
  [852719.001614] KVM can't copy data from 0x3fff86683c80!
  [852719.001617] KVM can't copy data from 0x3fff66a83c80!
  [852719.001624] KVM can't copy data from 0x3fff86683c80!
  [852719.001634] KVM can't copy data from 0x3fff86683c80!
  [852719.001637] KVM can't copy data from 0x3fff66a83c80!
  [852719.001645] KVM can't copy data from 0x3fff86683c80!
  [852719.001655] KVM can't copy data from 0x3fff86683c80!
  [852719.001658] KVM can't copy data from 0x3fff66a83c80!
  [852719.001665] KVM can't copy data from 0x3fff86683c80!
  [852719.001668] KVM can't copy data from 0x3fff66a83c80!
  [852719.001678] KVM can't copy data from 0x3fff66a83c80!
  [852719.001686] KVM can't copy data from 0x3fff86683c80!

  
  "KVM can't copy data from" error is being logged at very high rate
  by kernel. rate limiting this error should fix this issue.

  
  == Comment: #20 - VIPIN K. PARASHAR  - 2017-02-23 
12:01:26 ==
  Fix for this is submitted to PowerPC mailing list 
  and is available at below location:

  https://patchwork.ozlabs.org/patch/728831/

  It reads:

  "KVM: PPC: Book3S: Ratelimit copy data failure error messages"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667416/+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 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev

2017-03-23 Thread Rod Smith

** Merge proposal linked:
   
https://code.launchpad.net/~rodsmith/checkbox-support/+git/checkbox-support/+merge/320862

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

Title:
  Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
  udev

Status in checkbox package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in checkbox source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  During certification testing on Power8NVL, the network tests for the
  Mellanox 40/56G network cards are failing. According to the failure
  pasted below, udev/dbus isn't detecting the network card properly, but
  NetworkManager is. My feeling is this might be an issue with
  UdevadmParser.

  
  ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager 
saw 8 devices in ('Ethernet', 'Modem')
  ---[ Devices found by udev 
]
  Category: NETWORK
  Interface: enP1p1s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f2
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f3
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP8p1s0d1
  Product: MT27500 Family [ConnectX-3]
  Vendor: Mellanox Technologies
  Driver: mlx4_core (ver: 2.2-1)
  Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0

  Category: NETWORK
  Interface: enP9p7s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1981]

  Category: NETWORK
  Interface: enP9p7s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1657]

  --[ Devices found by Network Manager 
]--
  Category: Ethernet
  Interface: enP1p1s0f3
  IP: 10.20.30.54
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f0
  IP: 10.20.30.52
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f1
  IP: 10.20.30.53
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0
  IP: 10.20.30.5
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f0
  IP: 10.20.30.56
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0d1
  IP: 10.20.30.6
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f1
  IP: 10.20.30.57
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f2
  IP: 10.20.30.55
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 17:00 seq
   crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 22 15:59:40 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro
  ProcLoadAvg: 5.79 2.74 1.02 1/1261 881
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 4149 00:14:817 0 EOF
   2: POSIX

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-23 Thread Cristiano Casella

4ddd2ccae5e00fc62ca72410d2fc8ea668747134 does not boot

p.s. on our side we are still investigating and we are focusing on the boot 
configuration, do you have some details about the right device should be 
selected in the hypervisor?
just the hard drive?
the efi file in efi partition? (which name and path is expected)

thanks for your support

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  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:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-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: 4898-1213-1192-4801-7611-1594-99
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+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 1675540] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1675540

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => 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/1675540

Title:
  i2c i2c-1: sendbytes: NAK bailout.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug still exists and looks like it was identified as part of the
  Nouveau video driver, experienced now with Ubuntu 16.10.

  Timed out (original?) bug thread:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1015165

  Trackback on forums with no clear resolution:
  https://ubuntuforums.org/showthread.php?t=2074280

  
  Details:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.10
  Release:16.10
  Codename:   yakkety

  $ lsmod | grep 'i2c'
  i2c_piix4  24576  0
  i2c_algo_bit   16384  1 nouveau
  support@apollo:~$ lsmod | grep 'nouveau'
  nouveau  1572864  1
  mxm_wmi16384  1 nouveau
  video  40960  1 nouveau
  i2c_algo_bit   16384  1 nouveau
  ttm   102400  1 nouveau
  drm_kms_helper167936  1 nouveau
  drm   368640  4 nouveau,ttm,drm_kms_helper
  wmi16384  2 mxm_wmi,nouveau

  $ uname -a
  Linux apollo 4.8.0-40-generic #43-Ubuntu SMP Thu Feb 23 16:01:19 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  
  $ lspci | grep -i 'nvidia'
  01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] 
(rev a2)

  dmesg spam :

  [74243.701317] Raw EDID:
  [74243.702234]  78 ee c1 25 a3 56 4b 99 27 11 50 54 bf ef 80 95
  [74243.703153]  00 71 4f 81 80 95 0f 01 01 01 01 01 01 01 01 9a
  [74243.704050]  29 a0 d0 51 84 22 30 50 98 36 00 98 ff 10 00 00
  [74243.704925]  1c 00 00 00 fd 00 38 4b 1e 53 0e 00 0a 20 20 20
  [74243.705816]  20 20 20 00 00 00 ff 00 37 33 37 33 31 38 33 49
  [74243.706732]  32 38 57 53 01 00 00 00 fc 00 44 45 4c 4c 20 45
  [74243.707617]  31 39 38 57 46 50 0a 00 3a ff ff ff ff ff ff ff
  [74243.708508]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [74243.65] i2c i2c-1: sendbytes: NAK bailout.
  [74246.557345] i2c i2c-1: sendbytes: NAK bailout.
  [74246.843767] i2c i2c-1: sendbytes: NAK bailout.
  [74247.128195] i2c i2c-1: sendbytes: NAK bailout.
  [74249.366638] i2c i2c-1: sendbytes: NAK bailout.
  [74250.883810] i2c i2c-1: sendbytes: NAK bailout.
  [74251.295261] i2c i2c-1: sendbytes: NAK bailout.
  [74252.939101] i2c i2c-1: sendbytes: NAK bailout.
  [74254.200165] i2c i2c-1: sendbytes: NAK bailout.
  [74254.885717] i2c i2c-1: readbytes: ack/nak timeout
  [74255.169703] i2c i2c-1: readbytes: ack/nak timeout
  [74255.737676] i2c i2c-1: readbytes: ack/nak timeout
  [74257.450821] i2c i2c-1: sendbytes: NAK bailout.

  No packages :
  $ dpkg --list | grep  -i 'nvidia'
  $ dpkg --list | grep  -i 'nouveau'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675540/+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 1675540] [NEW] i2c i2c-1: sendbytes: NAK bailout.

2017-03-23 Thread beadon

Public bug reported:

This bug still exists and looks like it was identified as part of the
Nouveau video driver, experienced now with Ubuntu 16.10.

Timed out (original?) bug thread:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1015165

Trackback on forums with no clear resolution:
https://ubuntuforums.org/showthread.php?t=2074280


Details:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename:   yakkety

$ lsmod | grep 'i2c'
i2c_piix4  24576  0
i2c_algo_bit   16384  1 nouveau
support@apollo:~$ lsmod | grep 'nouveau'
nouveau  1572864  1
mxm_wmi16384  1 nouveau
video  40960  1 nouveau
i2c_algo_bit   16384  1 nouveau
ttm   102400  1 nouveau
drm_kms_helper167936  1 nouveau
drm   368640  4 nouveau,ttm,drm_kms_helper
wmi16384  2 mxm_wmi,nouveau

$ uname -a
Linux apollo 4.8.0-40-generic #43-Ubuntu SMP Thu Feb 23 16:01:19 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux


$ lspci | grep -i 'nvidia'
01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] 
(rev a2)

dmesg spam :

[74243.701317] Raw EDID:
[74243.702234]  78 ee c1 25 a3 56 4b 99 27 11 50 54 bf ef 80 95
[74243.703153]  00 71 4f 81 80 95 0f 01 01 01 01 01 01 01 01 9a
[74243.704050]  29 a0 d0 51 84 22 30 50 98 36 00 98 ff 10 00 00
[74243.704925]  1c 00 00 00 fd 00 38 4b 1e 53 0e 00 0a 20 20 20
[74243.705816]  20 20 20 00 00 00 ff 00 37 33 37 33 31 38 33 49
[74243.706732]  32 38 57 53 01 00 00 00 fc 00 44 45 4c 4c 20 45
[74243.707617]  31 39 38 57 46 50 0a 00 3a ff ff ff ff ff ff ff
[74243.708508]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[74243.65] i2c i2c-1: sendbytes: NAK bailout.
[74246.557345] i2c i2c-1: sendbytes: NAK bailout.
[74246.843767] i2c i2c-1: sendbytes: NAK bailout.
[74247.128195] i2c i2c-1: sendbytes: NAK bailout.
[74249.366638] i2c i2c-1: sendbytes: NAK bailout.
[74250.883810] i2c i2c-1: sendbytes: NAK bailout.
[74251.295261] i2c i2c-1: sendbytes: NAK bailout.
[74252.939101] i2c i2c-1: sendbytes: NAK bailout.
[74254.200165] i2c i2c-1: sendbytes: NAK bailout.
[74254.885717] i2c i2c-1: readbytes: ack/nak timeout
[74255.169703] i2c i2c-1: readbytes: ack/nak timeout
[74255.737676] i2c i2c-1: readbytes: ack/nak timeout
[74257.450821] i2c i2c-1: sendbytes: NAK bailout.

No packages :
$ dpkg --list | grep  -i 'nvidia'
$ dpkg --list | grep  -i 'nouveau'

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

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

Title:
  i2c i2c-1: sendbytes: NAK bailout.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug still exists and looks like it was identified as part of the
  Nouveau video driver, experienced now with Ubuntu 16.10.

  Timed out (original?) bug thread:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1015165

  Trackback on forums with no clear resolution:
  https://ubuntuforums.org/showthread.php?t=2074280

  
  Details:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.10
  Release:16.10
  Codename:   yakkety

  $ lsmod | grep 'i2c'
  i2c_piix4  24576  0
  i2c_algo_bit   16384  1 nouveau
  support@apollo:~$ lsmod | grep 'nouveau'
  nouveau  1572864  1
  mxm_wmi16384  1 nouveau
  video  40960  1 nouveau
  i2c_algo_bit   16384  1 nouveau
  ttm   102400  1 nouveau
  drm_kms_helper167936  1 nouveau
  drm   368640  4 nouveau,ttm,drm_kms_helper
  wmi16384  2 mxm_wmi,nouveau

  $ uname -a
  Linux apollo 4.8.0-40-generic #43-Ubuntu SMP Thu Feb 23 16:01:19 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  
  $ lspci | grep -i 'nvidia'
  01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] 
(rev a2)

  dmesg spam :

  [74243.701317] Raw EDID:
  [74243.702234]  78 ee c1 25 a3 56 4b 99 27 11 50 54 bf ef 80 95
  [74243.703153]  00 71 4f 81 80 95 0f 01 01 01 01 01 01 01 01 9a
  [74243.704050]  29 a0 d0 51 84 22 30 50 98 36 00 98 ff 10 00 00
  [74243.704925]  1c 00 00 00 fd 00 38 4b 1e 53 0e 00 0a 20 20 20
  [74243.705816]  20 20 20 00 00 00 ff 00 37 33 37 33 31 38 33 49
  [74243.706732]  32 38 57 53 01 00 00 00 fc 00 44 45 4c 4c 20 45
  [74243.707617]  31 39 38 57 46 50 0a 00 3a ff ff ff ff ff ff ff
  [74243.708508]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [74243.65] i2c i2c-1: sendbytes: NAK bailout.
  [74246.557345] i2c i2c-1: sendbytes: NAK bailout.
  [74246.843767] i2c i2c-1: sendbytes: NAK bailout.
  [74247.128195] i2c i2c-1:

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

2017-03-23 Thread Mathieu Marquer

So I *thnk* it's fixed in 4.11 RC3, although I'm not fully sure because
I was encountering bug
https://bugs.freedesktop.org/show_bug.cgi?id=100181 which made display
crash about every 30 minutes, but after a few hours testing I didn't
encounter this kernel bug, while it appeared after ~45 minutes when back
on 4.10.

** Bug watch added: freedesktop.org Bugzilla #100181
   https://bugs.freedesktop.org/show_bug.cgi?id=100181

** Tags added: kernel-fixed-upstream

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

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

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

Status in linux package in Ubuntu:
  Confirmed

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 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev

2017-03-23 Thread Rod Smith

** Changed in: checkbox (Ubuntu)
 Assignee: (unassigned) => Rod Smith (rodsmith)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Rod Smith (rodsmith)

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

Title:
  Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
  udev

Status in checkbox package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in checkbox source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  During certification testing on Power8NVL, the network tests for the
  Mellanox 40/56G network cards are failing. According to the failure
  pasted below, udev/dbus isn't detecting the network card properly, but
  NetworkManager is. My feeling is this might be an issue with
  UdevadmParser.

  
  ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager 
saw 8 devices in ('Ethernet', 'Modem')
  ---[ Devices found by udev 
]
  Category: NETWORK
  Interface: enP1p1s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f2
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f3
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP8p1s0d1
  Product: MT27500 Family [ConnectX-3]
  Vendor: Mellanox Technologies
  Driver: mlx4_core (ver: 2.2-1)
  Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0

  Category: NETWORK
  Interface: enP9p7s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1981]

  Category: NETWORK
  Interface: enP9p7s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1657]

  --[ Devices found by Network Manager 
]--
  Category: Ethernet
  Interface: enP1p1s0f3
  IP: 10.20.30.54
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f0
  IP: 10.20.30.52
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f1
  IP: 10.20.30.53
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0
  IP: 10.20.30.5
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f0
  IP: 10.20.30.56
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0d1
  IP: 10.20.30.6
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f1
  IP: 10.20.30.57
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f2
  IP: 10.20.30.55
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 17:00 seq
   crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 22 15:59:40 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro
  ProcLoadAvg: 5.79 2.74 1.02 1/1261 881
  ProcLocks:
   1: POSIX

[Kernel-packages] [Bug 1675533] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  Black screen on Kernel 4.4.0-64 and 4.4.0-66

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
   It was suggested on askubuntu that I try here. I can load up on Kernel 
4.4.0-62 but not 4.4.0-64 or 4.4.0-66. I currently have to press escape on 
load-up and select 4.4.0-62 on the GRUB screen. I assume new Kernels come out 
every few weeks and therefore 4.4.0-62 will eventually be redundant? 
Coincidentally kernel 4.4.0-64 & 4.4.0-66 stopped working after I installed the 
GIMP image program.

  I also have an additional problem of the wifi stopping/dropping every
  few minutes but hope I can fix that later on askubuntu. I haven't
  worked out if it stops regularly or when I briefly stop typing and
  read a webpage. I thought I would mention it in case it is related.

  My knowledge of ubuntu/computers is limited. What are the best
  commands to try and diagnose the problem?

  CPU: AMD phenom 11x4 970 Processor x4 (32-bit)
  RAM: 15.8 GiB
  Graphics: Gallium 0.4 on AMD CAICOS (DRM 2.43.0/4.4.0-62-generic, LLVM 
3.8.0)
  Disk: 475.2GB

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-generic 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lalalala   1648 F pulseaudio
   /dev/snd/controlC1:  lalalala   1648 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 23 19:14:39 2017
  HibernationDevice: RESUME=UUID=d99064f6-aa39-4d52-95df-27762169c27e
  InstallationDate: Installed on 2017-01-02 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=5b90d169-62a7-498f-92d2-673ed94400aa ro rootflags=sync quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78LT-M
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd08/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675533/+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 1675522] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1675522

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => 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/1675522

Title:
  arm64: Synchronous Exception at 0xBBC129BC

Status in edk2 package in Ubuntu:
  New
Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  New

Bug description:
  I installed a KVM VM with the zesty beta server ISO. The install went
  well but, upon reboot, GRUB entered a Synchronous Exception loop after
  selecting the Ubuntu boot option.

  After killing qemu-system-aarch64 and restarting the VM, the system
  booted to a prompt w/o issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1675522/+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 1675522] Re: arm64: Synchronous Exception at 0x00000000BBC129BC

Behavior is the same after reverting to yakkety grub. This issue follows
the guest kernel that we are rebooting *from*:

kernel running  |  kernel we  |  Reboot
  at reboot | reboot into |  Success?  

 4.10   |   4.10  |  Failure
 4.8|   4.8   |  Success
 4.10   |   4.8   |  Failure
 4.8|   4.10  |  Success

This suggests a bug in QEMU/qemu-efi. I suppose it could also be a bug
in the kernel if it were a long-standing issue with boottime init that
existed in 4.8 but was never tickled until now.

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

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

Title:
  arm64: Synchronous Exception at 0xBBC129BC

Status in edk2 package in Ubuntu:
  New
Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New

Bug description:
  I installed a KVM VM with the zesty beta server ISO. The install went
  well but, upon reboot, GRUB entered a Synchronous Exception loop after
  selecting the Ubuntu boot option.

  After killing qemu-system-aarch64 and restarting the VM, the system
  booted to a prompt w/o issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1675522/+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 1675533] [NEW] Black screen on Kernel 4.4.0-64 and 4.4.0-66

2017-03-23 Thread David Smith

Public bug reported:

Hi,
 It was suggested on askubuntu that I try here. I can load up on Kernel 
4.4.0-62 but not 4.4.0-64 or 4.4.0-66. I currently have to press escape on 
load-up and select 4.4.0-62 on the GRUB screen. I assume new Kernels come out 
every few weeks and therefore 4.4.0-62 will eventually be redundant? 
Coincidentally kernel 4.4.0-64 & 4.4.0-66 stopped working after I installed the 
GIMP image program.

I also have an additional problem of the wifi stopping/dropping every
few minutes but hope I can fix that later on askubuntu. I haven't worked
out if it stops regularly or when I briefly stop typing and read a
webpage. I thought I would mention it in case it is related.

My knowledge of ubuntu/computers is limited. What are the best commands
to try and diagnose the problem?

CPU: AMD phenom 11x4 970 Processor x4 (32-bit)
RAM: 15.8 GiB
Graphics: Gallium 0.4 on AMD CAICOS (DRM 2.43.0/4.4.0-62-generic, LLVM 
3.8.0)
Disk: 475.2GB

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-62-generic 4.4.0-62.83
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lalalala   1648 F pulseaudio
 /dev/snd/controlC1:  lalalala   1648 F pulseaudio
CurrentDesktop: Unity
Date: Thu Mar 23 19:14:39 2017
HibernationDevice: RESUME=UUID=d99064f6-aa39-4d52-95df-27762169c27e
InstallationDate: Installed on 2017-01-02 (80 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=5b90d169-62a7-498f-92d2-673ed94400aa ro rootflags=sync quiet splash 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-62-generic N/A
 linux-backports-modules-4.4.0-62-generic  N/A
 linux-firmware1.157.8
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A78LT-M
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd08/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: apport-bug i386 xenial

** Description changed:

- Hi, 
-  It was suggested on askubuntu that I try here. I can load up on Kernel 
4.4.0-62 but not 4.4.0-64 or 4.4.0-66. I currently have to press escape on 
load-up and select 4.4.0-62 on the GRUB screen. I assume new Kernels come out 
every few weeks and therefore 4.4.0-62 will eventually be redundant? 
Coincidentally kernel 4.4.0-64 & 4.4.0-66 stopped working after I installed the 
GIMP image program.
+ Hi,
+  It was suggested on askubuntu that I try here. I can load up on Kernel 
4.4.0-62 but not 4.4.0-64 or 4.4.0-66. I currently have to press escape on 
load-up and select 4.4.0-62 on the GRUB screen. I assume new Kernels come out 
every few weeks and therefore 4.4.0-62 will eventually be redundant? 
Coincidentally kernel 4.4.0-64 & 4.4.0-66 stopped working after I installed the 
GIMP image program.
  
- I have also have an additional problem of the wifi stopping/dropping
- every few minutes but hope I can fix that later on askubuntu. I haven't
- worked out if it stops regularly or only I briefly stop typing and read
- a webpage. I thought I would mention it in case it is related.
+ I also have an additional problem of the wifi stopping/dropping every
+ few minutes but hope I can fix that later on askubuntu. I haven't worked
+ out if it stops regularly or when I briefly stop typing and read a
+ webpage. I thought I would mention it in case it is related.
  
+ My knowledge of ubuntu/computers is limited. What are the best commands
+ to try and diagnose the problem?
  
- My knowledge of ubuntu/computers is limited. What are the best commands to 
try and diagnose the problem?
- 
- CPU: AMD phenom 11x4 970 Processor x4 (32-bit)
- RAM: 15.8 GiB
- Graphics: Gallium 0.4 on AMD CAICOS (DRM 2.43.0/4.4.0-62-generic, LLVM 
3.8.0)
- Disk: 475.2GB
+ CPU: AMD phenom 11x4 970 Processor x4 (32-bit)
+ RAM: 15.8 GiB
+ Graphics: Gallium 0.4 on AMD CAICOS (DRM 2.43.0/4.4.0-62-generic, LLVM 
3.8.0)
+ Disk: 475.2GB
  
  ProblemType: Bug

[Kernel-packages] [Bug 1667416] Re: PowerNV: No rate limit for kernel error "KVM can't copy data from"

2017-03-23 Thread Mikhail S Medvedev

The latest kernel from yakkety-proposed does not appear to fix the
problem. Note that I did test it on Xenial, not Yakkety, because I do
not have an easy way to reproduce the bug that excercises rate-limited
printk on Yakkety.

I made sure that the proposed kernel was used by comparing what is
getting installed on Yakkety vs Xenial:

On Yakkety
==

$ sudo apt-get install -y linux-image-generic/yakkety-proposed

Selected version '4.8.0.44.56' (Ubuntu:16.10/yakkety-proposed [ppc64el]) for 
'linux-image-generic'
The following additional packages will be installed:
  crda iw libnl-3-200 libnl-genl-3-200 linux-firmware 
linux-image-4.8.0-44-generic
  linux-image-extra-4.8.0-44-generic wireless-regdb
Suggested packages:
  fdutils linux-doc-4.8.0 | linux-source-4.8.0 linux-tools 
linux-headers-4.8.0-44-generic
The following NEW packages will be installed:
  crda iw libnl-3-200 libnl-genl-3-200 linux-firmware 
linux-image-4.8.0-44-generic
  linux-image-extra-4.8.0-44-generic linux-image-generic wireless-regdb

# uname -a
Linux mmedvede2-test-ratelimit-pkvmci836 4.8.0-44-generic #47-Ubuntu SMP Wed 
Mar 22 14:27:02 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

On Xenial
=

$ sudo apt-get install -y linux-image-generic/yakkety-proposed
Selected version '4.8.0.44.56' (Ubuntu:16.10/yakkety-proposed [ppc64el]) for 
'linux-image-generic'
The following additional packages will be installed:
  linux-image-4.8.0-44-generic linux-image-extra-4.8.0-44-generic
Suggested packages:
  fdutils linux-doc-4.8.0 | linux-source-4.8.0 linux-tools 
linux-headers-4.8.0-44-generic
The following NEW packages will be installed:
  linux-image-4.8.0-44-generic linux-image-extra-4.8.0-44-generic
The following packages will be upgraded:
  linux-image-generic

$ uname -a
Linux mmedvede-test-ratelimit-pkvmci8361 4.8.0-44-generic #47-Ubuntu SMP Wed 
Mar 22 14:27:02 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux


And I was able to reproduce the printk spam on Xenial with the proposed kernel. 
Did the fix actually get into 4.8.0.44.56?

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

Title:
  PowerNV: No rate limit for kernel error "KVM can't copy data from"

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  == Comment: #0 - MIKHAIL S. MEDVEDEV  - 2017-02-03 
14:40:58 ==
  ---Problem Description---
  I am experiencing a problem with KVM on Power with a symptom of "KVM can't 
copy data" message being spammed to kern.log at about 10 messages a second. 
Apart from original problem that triggers the error, the printk is a problem on 
its own. System might run out of space for logs, and would have high CPU load 
caused by journald.

  This bug is to address an absence of rate limiter on printk at
  
https://github.com/torvalds/linux/blob/f64e8084c94bb0449177364856d8117e2f14c4c0/arch/powerpc/kvm/book3s_64_mmu.c#L268

  Maybe wrapping the printk in printk_ratelimit() is all that is
  required?

  if(printk_ratelimit()){
 printk("KVM can't copy");
  }
   
  Contact Information = Mikhail Medvedev / mmedv...@us.ibm.com, Rafael Folco / 
rfo...@br.ibm.com 
   
  ---uname output---
  4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le 
ppc64le ppc64le GNU/Linux
   
  Machine Type = KVM guest on P8 8247 21L  
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Deploy OpenStack with devstack
  2. Run simultaneously between 4 and 6 instances of a script that
  - boots a VM (openstack server create)
  - immediately creates the backup of the VM (openstack server backup 
create)

  This is not a very good way to reproduce it. I am still unable to
  reproduce the problem just by using libvirt and qemu.

  
  == Comment: #5 - VIPIN K. PARASHAR  - 2017-02-07 
09:42:31 ==

  From kernel logs
  ===

  [852719.001593] KVM can't copy data from 0x3fff86683c80!
  [852719.001614] KVM can't copy data from 0x3fff86683c80!
  [852719.001617] KVM can't copy data from 0x3fff66a83c80!
  [852719.001624] KVM can't copy data from 0x3fff86683c80!
  [852719.001634] KVM can't copy data from 0x3fff86683c80!
  [852719.001637] KVM can't copy data from 0x3fff66a83c80!
  [852719.001645] KVM can't copy data from 0x3fff86683c80!
  [852719.001655] KVM can't copy data from 0x3fff86683c80!
  [852719.001658] KVM can't copy data from 0x3fff66a83c80!
  [852719.001665] KVM can't copy data from 0x3fff86683c80!
  [852719.001668] KVM can't copy data from 0x3fff66a83c80!
  [852719.001678] KVM can't copy data from 0x3fff66a83c80!
  [852719.001686] KVM can't copy data from 0x3fff86683c80!

  
  "KVM can't copy data from" error is being logged at very high rate
  by kernel. rate limiting this error should fix this issue.

  
  == Comment: #20 - VIPIN K. PARASHAR

[Kernel-packages] [Bug 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-23 Thread Marcin Banaszek

4ddd2ccae5e00fc62ca72410d2fc8ea668747134 does not boot.

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  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:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-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: 4898-1213-1192-4801-7611-1594-99
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+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 1667416] Re: PowerNV: No rate limit for kernel error "KVM can't copy data from"

2017-03-23 Thread Mikhail S Medvedev

** Tags removed: verification-needed-yakkety
** Tags added: verification-failed-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/1667416

Title:
  PowerNV: No rate limit for kernel error "KVM can't copy data from"

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  == Comment: #0 - MIKHAIL S. MEDVEDEV  - 2017-02-03 
14:40:58 ==
  ---Problem Description---
  I am experiencing a problem with KVM on Power with a symptom of "KVM can't 
copy data" message being spammed to kern.log at about 10 messages a second. 
Apart from original problem that triggers the error, the printk is a problem on 
its own. System might run out of space for logs, and would have high CPU load 
caused by journald.

  This bug is to address an absence of rate limiter on printk at
  
https://github.com/torvalds/linux/blob/f64e8084c94bb0449177364856d8117e2f14c4c0/arch/powerpc/kvm/book3s_64_mmu.c#L268

  Maybe wrapping the printk in printk_ratelimit() is all that is
  required?

  if(printk_ratelimit()){
 printk("KVM can't copy");
  }
   
  Contact Information = Mikhail Medvedev / mmedv...@us.ibm.com, Rafael Folco / 
rfo...@br.ibm.com 
   
  ---uname output---
  4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le 
ppc64le ppc64le GNU/Linux
   
  Machine Type = KVM guest on P8 8247 21L  
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Deploy OpenStack with devstack
  2. Run simultaneously between 4 and 6 instances of a script that
  - boots a VM (openstack server create)
  - immediately creates the backup of the VM (openstack server backup 
create)

  This is not a very good way to reproduce it. I am still unable to
  reproduce the problem just by using libvirt and qemu.

  
  == Comment: #5 - VIPIN K. PARASHAR  - 2017-02-07 
09:42:31 ==

  From kernel logs
  ===

  [852719.001593] KVM can't copy data from 0x3fff86683c80!
  [852719.001614] KVM can't copy data from 0x3fff86683c80!
  [852719.001617] KVM can't copy data from 0x3fff66a83c80!
  [852719.001624] KVM can't copy data from 0x3fff86683c80!
  [852719.001634] KVM can't copy data from 0x3fff86683c80!
  [852719.001637] KVM can't copy data from 0x3fff66a83c80!
  [852719.001645] KVM can't copy data from 0x3fff86683c80!
  [852719.001655] KVM can't copy data from 0x3fff86683c80!
  [852719.001658] KVM can't copy data from 0x3fff66a83c80!
  [852719.001665] KVM can't copy data from 0x3fff86683c80!
  [852719.001668] KVM can't copy data from 0x3fff66a83c80!
  [852719.001678] KVM can't copy data from 0x3fff66a83c80!
  [852719.001686] KVM can't copy data from 0x3fff86683c80!

  
  "KVM can't copy data from" error is being logged at very high rate
  by kernel. rate limiting this error should fix this issue.

  
  == Comment: #20 - VIPIN K. PARASHAR  - 2017-02-23 
12:01:26 ==
  Fix for this is submitted to PowerPC mailing list 
  and is available at below location:

  https://patchwork.ozlabs.org/patch/728831/

  It reads:

  "KVM: PPC: Book3S: Ratelimit copy data failure error messages"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667416/+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 1627828] Re: iwl3945 crashes randomly

2017-03-23 Thread drwt

I have the issue with wifi power save off so it cant be 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/1627828

Title:
  iwl3945 crashes randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Out of nothing a once properly working 
  0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] 
Network Connection (rev 02)
  started to crash with:
  Sep 22 14:38:16 seba-Latitude-D630 kernel: [26707.320032] iwl3945 
:0c:00.0: Error sending C_POWER_TBL: time out after 500ms.
  Sep 22 14:38:16 seba-Latitude-D630 kernel: [26707.320039] iwl3945 
:0c:00.0: set power fail, ret = -110
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.012031] iwl3945 
:0c:00.0: Queue 2 stuck for 2500 ms.
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.012039] iwl3945 
:0c:00.0: On demand firmware reload
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.050333] ieee80211 phy0: 
Hardware restart was requested
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.084769] retire_capture_urb: 
33 callbacks suppressed
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.098359] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.098364] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.145087] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.145089] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.191802] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.191805] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.238526] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.238528] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.285272] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.285275] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.322030] iwl3945 
:0c:00.0: Unable to initialize device after 5 attempts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seba   1421 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Sep 26 16:38:18 2016
  HibernationDevice: RESUME=UUID=64d7608d-53a8-46a6-884c-0ccf1814fb03
  InstallationDate: Installed on 2016-08-28 (29 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude D630
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=dce979b5-6a44-48cf-a87a-d314263a895c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627828/+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 1559643] Re: kswapd0 high cpu

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  kswapd0 high cpu

Status in linux package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed

Bug description:
  kswapd0 high cpu load.
  System doesn't have swap partition / swap file.

  Using AWS t2.nano

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-34-generic 4.2.0-34.39
  ProcVersionSignature: User Name 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 07:35 seq
   crw-rw 1 root audio 116, 33 Mar 20 07:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sun Mar 20 07:57:52 2016
  Ec2AMI: ami-b7443fc0
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 cirrusdrmfb
   1 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=b079c5f1-8fc8-4bb0-aa26-31610f9c5615 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-34-generic N/A
   linux-backports-modules-4.2.0-34-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-13 (127 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/07/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559643/+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 1670508] Re: CIFS: Enable encryption for SMB3

2017-03-23 Thread Joseph Salisbury

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => 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/1670508

Title:
  CIFS: Enable encryption for SMB3

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

Bug description:
  There has been work upstream to enable encryption support for SMB3
  connections. This is a particularly valuable (and commonly requested)
  feature with the Azure Files service as encryption is required to
  connect to an Azure Files storage share from on-prem or from a
  different Azure region.

  The relevant commits are as follows:

  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

  CIFS: Allow to switch on encryption with seal mount option
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e

  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb

  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e

  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

  cifs: Only select the required crypto modules
  Commit 3692304bba6164be3810afd41b84ecb0e1e41db1

  cifs: Simplify SMB2 and SMB311 dependencies
  Commit c1ecea87471bbb614f8121e00e5787f363140365

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670508/+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 1674635] Re: Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft Hyper-v 2012r2 Gen2 VM

2017-03-23 Thread Joseph Salisbury

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

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1674635/4ddd2ccae5e00fc62ca72410d2fc8ea668747134

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

Title:
  Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
  Hyper-v 2012r2 Gen2 VM

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

Bug description:
  After updating the kernel inside the virtual machine to the version 
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every 
try. An hard reset is required.
  The only workaround is to set the default in grub to the previous version.
  The virtual machine hardware is a Gen2.
  We are experiencing this issue on all our vps with the same kernel (around 
300-400 vms).
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 10:30 seq
   crw-rw 1 root audio 116, 33 Mar 20 10:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  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:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg01--vg-swap_1
  InstallationDate: Installed on 2017-03-13 (7 days ago)
  InstallationMedia:
   
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic.efi.signed 
root=/dev/mapper/vg01--vg-root ro nomodeset
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-66-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: 4898-1213-1192-4801-7611-1594-99
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+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 1673207] Re: linux: 3.13.0-114.161 -proposed tracker

2017-03-23 Thread Taihsiang Ho

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  linux: 3.13.0-114.161 -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:
  In Progress
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Invalid
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 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: 1673211
  derivatives:
  -- 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/1673207/+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 1675509] [NEW] ARM arch_timer erratum

Public bug reported:

There are a few platforms requiring errata workarounds for their
arch_timer implementations. Specifically, the HiSilicon D05 in ACPI
mode, and Cortex-A73-based systems.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: dann frazier (dannf)
 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/1675509

Title:
  ARM arch_timer erratum

Status in linux package in Ubuntu:
  In Progress

Bug description:
  There are a few platforms requiring errata workarounds for their
  arch_timer implementations. Specifically, the HiSilicon D05 in ACPI
  mode, and Cortex-A73-based systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675509/+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 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev

2017-03-23 Thread Rod Smith

I've been looking at this (on and off), and it seems to reach close to
the end of UdevadmParser.run() (in udevadm.py) with the data intact, but
it gets lost in the last line or in transferring control out, in the
main() function of the udev_resource script.

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

Title:
  Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
  udev

Status in checkbox package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in checkbox source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  During certification testing on Power8NVL, the network tests for the
  Mellanox 40/56G network cards are failing. According to the failure
  pasted below, udev/dbus isn't detecting the network card properly, but
  NetworkManager is. My feeling is this might be an issue with
  UdevadmParser.

  
  ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager 
saw 8 devices in ('Ethernet', 'Modem')
  ---[ Devices found by udev 
]
  Category: NETWORK
  Interface: enP1p1s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f2
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f3
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP8p1s0d1
  Product: MT27500 Family [ConnectX-3]
  Vendor: Mellanox Technologies
  Driver: mlx4_core (ver: 2.2-1)
  Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0

  Category: NETWORK
  Interface: enP9p7s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1981]

  Category: NETWORK
  Interface: enP9p7s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1657]

  --[ Devices found by Network Manager 
]--
  Category: Ethernet
  Interface: enP1p1s0f3
  IP: 10.20.30.54
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f0
  IP: 10.20.30.52
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f1
  IP: 10.20.30.53
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0
  IP: 10.20.30.5
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f0
  IP: 10.20.30.56
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0d1
  IP: 10.20.30.6
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f1
  IP: 10.20.30.57
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f2
  IP: 10.20.30.55
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 17:00 seq
   crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 22 15:59:40 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine:

[Kernel-packages] [Bug 1656259] Re: Linux ZFS port doesn't respect RLIMIT_FSIZE

This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu16

---
zfs-linux (0.6.5.6-0ubuntu16) xenial; urgency=medium

  * Enable zfs to respect RSIZE_LIMIT limits (LP: #1656259)
- backport of zfs upstream commit 4b908d32200b6e5c7b5115322b6c8d25e770daa0
  ("Linux 4.8 compat: posix_acl_valid()") to facilitate changes in 
posix_acl_valid.
  1015-Linux-4.8-compat-posix_acl_valid.patch
- backport of upstream commit 933ec999511f3d29de005bfa8966ae007b161c0f
  ("Retire .write/.read file operations")
  1016-Retire-.write-.read-file-operations.patch

 -- Colin Ian King   Fri, 17 Feb 2017 11:00:12
+

** Changed in: zfs-linux (Ubuntu Xenial)
   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 Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed
Status in zfs-linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
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 1656259] Update Released

2017-03-23 Thread Brian Murray

The verification of the Stable Release Update for zfs-linux has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed
Status in zfs-linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
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 1656259] Re: Linux ZFS port doesn't respect RLIMIT_FSIZE

This bug was fixed in the package zfs-linux - 0.6.5.8-0ubuntu4.2

---
zfs-linux (0.6.5.8-0ubuntu4.2) yakkety; urgency=low

  * Enable zfs to respect RSIZE_LIMIT limits (LP: #1656259)
backport of upstream commit 933ec999511f3d29de005bfa8966ae007b161c0f
("Retire .write/.read file operations")

 -- Colin Ian King   Fri, 17 Feb 2017 11:00:12
+

** Changed in: zfs-linux (Ubuntu Yakkety)
   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 Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed
Status in zfs-linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
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 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev

2017-03-23 Thread Jeff Lane

The important bits of udev seem to be these:

P: /devices/pci0008:00/0008:00:00.0/0008:01:00.0
E: DEVPATH=/devices/pci0008:00/0008:00:00.0/0008:01:00.0
E: DRIVER=mlx4_core
E: ID_MODEL_FROM_DATABASE=MT27500 Family [ConnectX-3]
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Mellanox Technologies
E: MODALIAS=pci:v15B3d1003sv1014sd04B5bc02sc00i00
E: OF_COMPATIBLE_N=0
E: OF_FULLNAME=/pciex@3fffe4040/pci@0/ethernet@0
E: OF_NAME=ethernet
E: PCI_CLASS=2
E: PCI_ID=15B3:1003
E: PCI_SLOT_NAME=0008:01:00.0
E: PCI_SUBSYS_ID=1014:04B5
E: SUBSYSTEM=pci
E: USEC_INITIALIZED=11882462

P: /devices/pci0008:00/0008:00:00.0/0008:01:00.0/net/enP8p1s0
E: DEVPATH=/devices/pci0008:00/0008:00:00.0/0008:01:00.0/net/enP8p1s0
E: ID_BUS=pci
E: ID_MM_CANDIDATE=1
E: ID_MODEL_FROM_DATABASE=MT27500 Family [ConnectX-3]
E: ID_MODEL_ID=0x1003
E: ID_NET_DRIVER=mlx4_en
E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
E: ID_NET_NAME_MAC=enxe41d2d2590c0
E: ID_NET_NAME_PATH=enP8p1s0
E: ID_OUI_FROM_DATABASE=Mellanox Technologies, Inc.
E: ID_PATH=pci-0008:01:00.0
E: ID_PATH_TAG=pci-0008_01_00_0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Mellanox Technologies
E: ID_VENDOR_ID=0x15b3
E: IFINDEX=8
E: INTERFACE=enP8p1s0
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enP8p1s0
E: TAGS=:systemd:
E: USEC_INITIALIZED=8004370

P: /devices/pci0008:00/0008:00:00.0/0008:01:00.0/net/enP8p1s0d1
E: DEVPATH=/devices/pci0008:00/0008:00:00.0/0008:01:00.0/net/enP8p1s0d1
E: ID_BUS=pci
E: ID_MM_CANDIDATE=1
E: ID_MODEL_FROM_DATABASE=MT27500 Family [ConnectX-3]
E: ID_MODEL_ID=0x1003
E: ID_NET_DRIVER=mlx4_en
E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
E: ID_NET_NAME_MAC=enxe41d2d2590c1
E: ID_NET_NAME_PATH=enP8p1s0d1
E: ID_OUI_FROM_DATABASE=Mellanox Technologies, Inc.
E: ID_PATH=pci-0008:01:00.0
E: ID_PATH_TAG=pci-0008_01_00_0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Mellanox Technologies
E: ID_VENDOR_ID=0x15b3
E: IFINDEX=9
E: INTERFACE=enP8p1s0d1
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enP8p1s0d1
E: TAGS=:systemd:
E: USEC_INITIALIZED=7956109

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

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

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

** Changed in: checkbox (Ubuntu)
   Status: New => 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/1675091

Title:
  Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
  udev

Status in checkbox package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in checkbox source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  During certification testing on Power8NVL, the network tests for the
  Mellanox 40/56G network cards are failing. According to the failure
  pasted below, udev/dbus isn't detecting the network card properly, but
  NetworkManager is. My feeling is this might be an issue with
  UdevadmParser.

  
  ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager 
saw 8 devices in ('Ethernet', 'Modem')
  ---[ Devices found by udev 
]
  Category: NETWORK
  Interface: enP1p1s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f2
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f3
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP8p1s0d1
  Product: MT27500 Family [ConnectX-3]
  Vendor: Mellanox Technologies
  Driver: mlx4_core (ver: 2.2-1)
  Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0

  Category: NETWORK
  Interface: enP9p7s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver:

[Kernel-packages] [Bug 1673805] Re: linux: 4.10.0-14.16 -proposed tracker

** Changed in: kernel-development-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/1673805

Title:
  linux: 4.10.0-14.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-14.16 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-development-workflow/+bug/1673805/+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 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev

2017-03-23 Thread Mike Rushton

kernel 4.11.0-041100rc3-generic failed with the same symptoms.

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

Title:
  Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
  udev

Status in checkbox package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in checkbox source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  During certification testing on Power8NVL, the network tests for the
  Mellanox 40/56G network cards are failing. According to the failure
  pasted below, udev/dbus isn't detecting the network card properly, but
  NetworkManager is. My feeling is this might be an issue with
  UdevadmParser.

  
  ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager 
saw 8 devices in ('Ethernet', 'Modem')
  ---[ Devices found by udev 
]
  Category: NETWORK
  Interface: enP1p1s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f2
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f3
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP8p1s0d1
  Product: MT27500 Family [ConnectX-3]
  Vendor: Mellanox Technologies
  Driver: mlx4_core (ver: 2.2-1)
  Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0

  Category: NETWORK
  Interface: enP9p7s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1981]

  Category: NETWORK
  Interface: enP9p7s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1657]

  --[ Devices found by Network Manager 
]--
  Category: Ethernet
  Interface: enP1p1s0f3
  IP: 10.20.30.54
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f0
  IP: 10.20.30.52
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f1
  IP: 10.20.30.53
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0
  IP: 10.20.30.5
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f0
  IP: 10.20.30.56
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0d1
  IP: 10.20.30.6
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f1
  IP: 10.20.30.57
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f2
  IP: 10.20.30.55
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 17:00 seq
   crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 22 15:59:40 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro
  ProcLoadAvg: 5.79 2.74 1.02 1/1261 881
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 4149 00:14:817 0 EOF
   2: POSIX  ADVISORY  WRITE 1701 00:14:477 0 EOF
   3: POSIX  ADVISORY

[Kernel-packages] [Bug 1675204] Re: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP)

2017-03-23 Thread Qianqian Fang

sorry, I posted the logs twice.

I just want to mention that my above logs were collected when only 2
displays are attached (in which case, the graphics functions ok),
despite that you can see plenty of pipe A FIFO underrun errors.

do you want me to connect the 3rd cable (to the TV) to trigger the
crash, and recollect the logs?

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675204/+attachment/4842918/+files/AlsaInfo.txt

** Attachment removed: "BootDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675204/+attachment/4842919/+files/BootDmesg.txt

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

Title:
  Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a very strange issue related to Intel graphics drivers (i915)
  with 3 connected on-board displays.

  I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop
  computer running on a i7-6700K processor and on-board graphics (Mobo:
  AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG
  display (via onboard DP port), a 1920x1200 Dell display (via on-board
  HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter).

  If I just connect my desktop to the first two displays (not the TV),
  everything works fine (except some minor issues). However, if I
  connect the 4k TV, even the TV is not on, my graphics starts to
  flicker every 5 min-ish (window theme turns off and then turns quickly
  back on); after a few flickering, the window theme will disappear, and
  the screen becomes weird - my chrome window will not fresh, or show
  blank boxes etc.

  If I disconnect the DVI connector to the TV (just use the LG+Dell
  dual-display), flickering and crash will not appear.

  I want to mention that, when I connect the computer to all 3 displays,
  I was actually able to get video output to all displays (I used arandr
  to configure them). I can even get 4k output to the 4k TV at 30Hz.

  I can't find a useful log entry when the flicking or graphics crash
  happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F
  (log attached at the end), but I can see many similar errors in my log
  and the appearance is not correlated to the flickering/crash. The
  "pipe A FIFO underrun" issue was previously reported in Bug#1550779.

  I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my
  Xorg.0.log file constantly, I also do not see an consistent mapping
  between the log entry and the flickering.

  Can anyone tell me how to properly debug this? what can I do to get a
  log for what was wrong?

  ---

  [  145.033055] WARNING: CPU: 2 PID: 1804 at 
/build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675
 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]()
  [  145.033058] WARN_ON(!wm_changed)
  [  145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev 
input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main 
v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) 
uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi 
coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) 
nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw 
gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi 
cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo 
auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc 
intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel 
btintel intel_lpss_ac
 pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops 
syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi 
kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp 
pps_core ahci nvme libahci fjes
  [  145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW  OE   
4.4.0-66-generic #87~14.04.1-Ubuntu
  [  145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016
  [  145.033290]   88086e5879a0 813dc80c 
88086e5879e8
  [  145.033295]  c0556700 88086e5879d8 8107e9d6 
88086d898000
  [  145.033300]  88086d89b000 0004 880871924b78 
88086e587a64
  [  145.033305] Call Trace:
  [  145.033311]  [] dump_stack+0x63/0x87
  [  145.033317]  [] warn_slowpath_common+0x86/0xc0
  [  145.033323]  [] warn_slowpath_fmt+0x4c/0x50
  [

[Kernel-packages] [Bug 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev

2017-03-23 Thread Mike Rushton

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

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

Title:
  Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
  udev

Status in checkbox package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in checkbox source package in Xenial:
  New
Status in linux source package in Xenial:
  Confirmed

Bug description:
  During certification testing on Power8NVL, the network tests for the
  Mellanox 40/56G network cards are failing. According to the failure
  pasted below, udev/dbus isn't detecting the network card properly, but
  NetworkManager is. My feeling is this might be an issue with
  UdevadmParser.

  
  ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager 
saw 8 devices in ('Ethernet', 'Modem')
  ---[ Devices found by udev 
]
  Category: NETWORK
  Interface: enP1p1s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f2
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP1p1s0f3
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
  ID:   [14e4:1657]
  Subsystem ID: [1014:0420]

  Category: NETWORK
  Interface: enP8p1s0d1
  Product: MT27500 Family [ConnectX-3]
  Vendor: Mellanox Technologies
  Driver: mlx4_core (ver: 2.2-1)
  Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0

  Category: NETWORK
  Interface: enP9p7s0f0
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1981]

  Category: NETWORK
  Interface: enP9p7s0f1
  Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
  Vendor: Broadcom Corporation
  Driver: tg3 (ver: Unknown)
  Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
  ID:   [14e4:1657]
  Subsystem ID: [14e4:1657]

  --[ Devices found by Network Manager 
]--
  Category: Ethernet
  Interface: enP1p1s0f3
  IP: 10.20.30.54
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f0
  IP: 10.20.30.52
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP9p7s0f1
  IP: 10.20.30.53
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0
  IP: 10.20.30.5
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f0
  IP: 10.20.30.56
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP8p1s0d1
  IP: 10.20.30.6
  Driver: mlx4_core (ver: 2.2-1)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f1
  IP: 10.20.30.57
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  Category: Ethernet
  Interface: enP1p1s0f2
  IP: 10.20.30.55
  Driver: tg3 (ver: Unknown)
  State: Unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 17:00 seq
   crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 22 15:59:40 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro
  ProcLoadAvg: 5.79 2.74 1.02 1/1261 881
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 4149 00:14:817 0 EOF
   2: POSIX  ADVISORY  WRITE 1701 00:14:477 0 EOF
   3: POSIX

[Kernel-packages] [Bug 1662589] Re: Touchpad not working correctly after kernel upgrade

2017-03-23 Thread Joseph Salisbury

That could be possible.  I'll review all the patches and build a test
kernel once the one for this bug lands.

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

Title:
  Touchpad not working correctly after kernel upgrade

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

Bug description:
  Since the kernel upgraded from 4.4.0-31-generic the touchpad on my
  Toshiba Tecra laptop has not been functioning correctly.

  Whenever I try and do two finger srcolling it also thinks I'm doing a
  two finger tap to to rightclick, making two finger scrolling almost
  impossible.

  It is the same for both kernel updates since 4.4.0-31.  If I boot from
  4.4.0-31 then the touchpad works fine.

  If I do an xinput in the later kernels it shows :-
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Wired Keyboard 600id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Comfort Mouse 6000id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Microsoft Wired Keyboard 600id=9[slave  
keyboard (3)]
  ↳ TOSHIBA Web Camera - FHDid=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Toshiba input device  

  
  The AlpsPS/2 devices aren't aren't present when booting with 4.4.0.31:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Wired Keyboard 600id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Comfort Mouse 6000id=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=14   [slave  pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Microsoft Wired Keyboard 600id=9[slave  
keyboard (3)]
  ↳ TOSHIBA Web Camera - FHDid=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Toshiba input deviceid=15 [slave  keyboard 
(3)]

  Any ideas?

  Thanks.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nick   1867 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5f888cc2-be17-45fe-9b4c-c8cf49eb1db8
  InstallationDate: Installed on 2017-02-03 (4 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: TOSHIBA TECRA A40-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=7c18c2ca-0cc6-4c2c-80ba-194bbbc22646 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.6
  Tags:  xenial xenial
  Uname: Linux 4.4.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/12/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 7.40
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A40-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA

[Kernel-packages] [Bug 1675443] [NEW] Update linux-firmware in xenial for 4.10 hwe-edge kernel

Public bug reported:

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.

** Affects: linux-firmware (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: Invalid

** Affects: linux-firmware (Ubuntu Xenial)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

** Changed in: linux-firmware (Ubuntu)
   Status: In Progress => Invalid

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

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Xenial)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Summary changed:

- Update linux-firmware in xenial for zesty hwe-edge kernel
+ Update linux-firmware in xenial for 4.10 hwe-edge kernel

-- 
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:
  In Progress

Bug description:
  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 1674936] Re: ubuntu_sysdig_smoke_test failed with "no events in file"

** Changed in: linux (Ubuntu)
   Status: Fix Committed => 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/1674936

Title:
  ubuntu_sysdig_smoke_test failed with "no events in file"

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  For the ubuntu_sysdig_smoke_test on 4.10.0-14.16, almost every node
  failed with this test (6 out of 7), except node "gonzo"

  root@naumann:/home/ubuntu/autotest-client-tests/ubuntu_sysdig_smoke_test# 
./ubuntu_sysdig_smoke_test.sh 
  == sysdig smoke test to trace dd, cat, read and writes ==
  Converting raw events to human readable format..
  no events in file
  Found:
 0 sysdig events
 0 dd context switches
 0 cat context switches
 0 reads from /dev/zero by dd
 0 writes to /dev/null by dd
  FAILED (trace at least 50 context switches involving dd)
  FAILED (trace at least 50 context switches involving cat)
  FAILED (trace at least 50 reads of /dev/zero by dd)
  FAILED (trace at least 50 writes to /dev/null by dd)
   
  Summary: 0 passed, 4 failed

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-13-generic 4.10.0-13.15
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 22 09:35 seq
   crw-rw 1 root audio 116, 33 Mar 22 09:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 22 09:55:41 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. 
   Bus 001 Device 002: ID :0001  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation S2600WFS
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=ae837c54-b162-4377-930a-4a2d82425066 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2016
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C620.86B.01.00.0294.101220161543
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600WFS
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H94548-410
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 23
  dmi.chassis.vendor: ...
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C620.86B.01.00.0294.101220161543:bd10/12/2016:svnIntelCorporation:pnS2600WFS:pvr:rvnIntelCorporation:rnS2600WFS:rvrH94548-410:cvn...:ct23:cvr..:
  dmi.product.name: S2600WFS
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674936/+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 1675329] Re: ubuntu_blktrace_smoke_test failed with "invalid path" on ARM64 Zesty

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1675329

Title:
  ubuntu_blktrace_smoke_test failed with "invalid path" on ARM64 Zesty

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  It looks like the sed in the get_dev() function is the cause.

  mount=$(stat -c '%m' $1 | tail -1)
  DEV=$(df $mount | grep dev | head -1 | cut -d' ' -f1 | sed 's/[0-9]//g')

  Note that this issue does not affect other amd64 systems, the sed
  command is for SATA devices there, to change /dev/sda1 to /dev/sda

  On ARM64 nodes, the actual DEV should be:
  /dev/disk/by-uuid/ec71a3bf-d777-4edb-a0ea-5b6d3504748d

  But after the sed command, it will become:
  /dev/disk/by-uuid/ecabf-d-edb-aea-bdd

  This is what I can see from /dev/disk/by-uuid:
  root@ms10-34-mcdivittB0-kernel:/dev/disk/by-uuid# ls
  9c648a56-06ad-4ca7-b23a-caaf7f5810a5  ec71a3bf-d777-4edb-a0ea-5b6d3504748d

  
  Error log:
  PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-4.10.0-14-generic)
  Using block device /dev/disk/by-uuid/ecabf-d-edb-aea-bdd for path 
/home/ubuntu/autotest/client/results/default/ubuntu_blktrace_smoke_test.blktrace-smoke-test
  FAILED expecting at least 1024 block traces events from the dd process, got 0
  FAILED expecting at least 1024 block read traces events, got 0
  FAILED expecting at least 1024 block write traces events, got 0
  Summary: 1 passed, 3 failed
  stderr:
  Invalid path /dev/disk/by-uuid/ecabf-d-edb-aea-bdd specified: 2/No such file 
or directory
  
/home/ubuntu/autotest/client/tests/ubuntu_blktrace_smoke_test/ubuntu_blktrace_smoke_test.sh:
 line 105: kill: (15290) - No such process

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-13-generic 4.10.0-13.15
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 23 04:39 seq
   crw-rw 1 root audio 116, 33 Mar 23 04:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Mar 23 08:59:50 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675329/+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 1645962] Re: [Feature] GLK Intel PT write

** Changed in: intel
   Status: New => 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/1645962

Title:
  [Feature] GLK Intel PT write

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Gemini Lake has support for Intel PT write.

  HW: Gemini Lake

  Upstream schedule:
  kernel: 4.11

  Commit Ids:
  5443624bed
  8ee83b2ab3

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1645962/+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 1675178] Re: package linux-firmware (not installed) failed to install/upgrade: próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który istnieje także w pakiecie firmware

This isn't really a bug. You have a package which duplicates a file in
the linux-firmware package, which causes an error. You simply can't have
both installed. Only the linux-firmware package is supported in Ubuntu,
and not the firmware-iwlwifi package.

** Changed in: linux-firmware (Ubuntu)
   Status: New => Invalid

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

Title:
  package linux-firmware (not installed) failed to install/upgrade:
  próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który
  istnieje także w pakiecie firmware-iwlwifi 0.43

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  first installing firmware-iwlwifi
  than: linux-firmware
  error occured

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   linux-firmware: Install
   linux-firmware: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Mar 22 22:17:46 2017
  DpkgTerminalLog:
   Przygotowywanie do rozpakowania pakietu .../linux-firmware_1.157.8_all.deb 
...
   Rozpakowywanie pakietu linux-firmware (1.157.8) ...
   dpkg: błąd przetwarzania archiwum 
/var/cache/apt/archives/linux-firmware_1.157.8_all.deb (--unpack):
próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który istnieje 
także w pakiecie firmware-iwlwifi 0.43
  ErrorMessage: próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który 
istnieje także w pakiecie firmware-iwlwifi 0.43
  InstallationDate: Installed on 2016-07-25 (240 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: linux-firmware
  Title: package linux-firmware (not installed) failed to install/upgrade: 
próba nadpisania "/lib/firmware/iwlwifi-6000g2b-6.ucode", który istnieje także 
w pakiecie firmware-iwlwifi 0.43
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1675178/+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 1675395] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  ubuntu_bpf test fail to build on aarch64 system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  # make
  for TARGET in bpf; do \
make -C $TARGET; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest-client-tests/ubuntu_bpf/linux/tools/testing/selftests/bpf'
  gcc -Wall -O2 -I../../../../usr/includetest_verifier.c   -o test_verifier
  In file included from test_verifier.c:23:0:
  /usr/include/linux/bpf_perf_event.h:13:17: error: field ‘regs’ has incomplete 
type
struct pt_regs regs;
   ^~~~
  : recipe for target 'test_verifier' failed
  make[1]: *** [test_verifier] Error 1
  make[1]: Leaving directory 
'/home/ubuntu/autotest-client-tests/ubuntu_bpf/linux/tools/testing/selftests/bpf'
  Makefile:18: recipe for target 'all' failed
  make: *** [all] Error 2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-13-generic 4.10.0-13.15
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 23 04:39 seq
   crw-rw 1 root audio 116, 33 Mar 23 04:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Mar 23 12:23:15 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675395/+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 1675395] [NEW] ubuntu_bpf test fail to build on aarch64 system

2017-03-23 Thread Po-Hsu Lin

Public bug reported:

# make
for TARGET in bpf; do \
make -C $TARGET; \
done;
make[1]: Entering directory 
'/home/ubuntu/autotest-client-tests/ubuntu_bpf/linux/tools/testing/selftests/bpf'
gcc -Wall -O2 -I../../../../usr/includetest_verifier.c   -o test_verifier
In file included from test_verifier.c:23:0:
/usr/include/linux/bpf_perf_event.h:13:17: error: field ‘regs’ has incomplete 
type
  struct pt_regs regs;
 ^~~~
: recipe for target 'test_verifier' failed
make[1]: *** [test_verifier] Error 1
make[1]: Leaving directory 
'/home/ubuntu/autotest-client-tests/ubuntu_bpf/linux/tools/testing/selftests/bpf'
Makefile:18: recipe for target 'all' failed
make: *** [all] Error 2

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-13-generic 4.10.0-13.15
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar 23 04:39 seq
 crw-rw 1 root audio 116, 33 Mar 23 04:39 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.4-0ubuntu2
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Mar 23 12:23:15 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-13-generic N/A
 linux-backports-modules-4.10.0-13-generic  N/A
 linux-firmware 1.164
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 uec-images zesty

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

Title:
  ubuntu_bpf test fail to build on aarch64 system

Status in linux package in Ubuntu:
  New

Bug description:
  # make
  for TARGET in bpf; do \
make -C $TARGET; \
  done;
  make[1]: Entering directory 
'/home/ubuntu/autotest-client-tests/ubuntu_bpf/linux/tools/testing/selftests/bpf'
  gcc -Wall -O2 -I../../../../usr/includetest_verifier.c   -o test_verifier
  In file included from test_verifier.c:23:0:
  /usr/include/linux/bpf_perf_event.h:13:17: error: field ‘regs’ has incomplete 
type
struct pt_regs regs;
   ^~~~
  : recipe for target 'test_verifier' failed
  make[1]: *** [test_verifier] Error 1
  make[1]: Leaving directory 
'/home/ubuntu/autotest-client-tests/ubuntu_bpf/linux/tools/testing/selftests/bpf'
  Makefile:18: recipe for target 'all' failed
  make: *** [all] Error 2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-13-generic 4.10.0-13.15
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 23 04:39 seq
   crw-rw 1 root audio 116, 33 Mar 23 04:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Mar 23 12:23:15 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675395/+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 1651454] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  [Lenovo Thinkpad T460p] Ultra Dock external displays not detected
  after suspend/resume cycle

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The bug is identical to the expired
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573 where a
  new report was requested.

  This time around with a fresh install of 16.10 amd64 on a Thinkpad
  T460p and a Lenovo Ultra Dock with two external monitors.

  The setup does work when freshly booting with the laptop on the dock. 
Suspending undocked, docking, resuming doesn't light up the external monitors. 
Neither does just docking awake.
  The relevant error messages seem to be these:

  Dec 20 13:21:50 talas kernel: [265391.482117] 
[drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage 
retries, give up
  Dec 20 13:21:50 talas kernel: [265391.498583] [drm:intel_wait_ddi_buf_idle 
[i915]] *ERROR* Timeout waiting for DDI BUF D idle bit

  Other relevant bug reports might be:
  https://bugzilla.redhat.com/show_bug.cgi?id=1316877
  https://bbs.archlinux.org/viewtopic.php?id=209791

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-30-generic 4.8.0-30.32
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  donjan 2341 F pulseaudio
   /dev/snd/pcmC1D0p:   donjan 2341 F...m pulseaudio
   /dev/snd/controlC1:  donjan 2341 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Dec 20 15:36:08 2016
  InstallationDate: Installed on 2016-10-25 (56 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20FXS0Y200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=104820cc-7d87-46d1-a1aa-e650ff221603 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET71W (2.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS0Y200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET71W(2.11):bd09/26/2016:svnLENOVO:pn20FXS0Y200:pvrThinkPadT460p:rvnLENOVO:rn20FXS0Y200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FXS0Y200
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651454/+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 1651454] Re: [Lenovo Thinkpad T460p] Ultra Dock external displays not detected after suspend/resume cycle

2017-03-23 Thread Donjan Rodic

This has stopped working in either 4.8.0-40 or 4.8.0-41.
It still works when booting with 4.8.0-39.
I can open a new one as regression, if necessary.

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

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

Title:
  [Lenovo Thinkpad T460p] Ultra Dock external displays not detected
  after suspend/resume cycle

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The bug is identical to the expired
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573 where a
  new report was requested.

  This time around with a fresh install of 16.10 amd64 on a Thinkpad
  T460p and a Lenovo Ultra Dock with two external monitors.

  The setup does work when freshly booting with the laptop on the dock. 
Suspending undocked, docking, resuming doesn't light up the external monitors. 
Neither does just docking awake.
  The relevant error messages seem to be these:

  Dec 20 13:21:50 talas kernel: [265391.482117] 
[drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage 
retries, give up
  Dec 20 13:21:50 talas kernel: [265391.498583] [drm:intel_wait_ddi_buf_idle 
[i915]] *ERROR* Timeout waiting for DDI BUF D idle bit

  Other relevant bug reports might be:
  https://bugzilla.redhat.com/show_bug.cgi?id=1316877
  https://bbs.archlinux.org/viewtopic.php?id=209791

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-30-generic 4.8.0-30.32
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  donjan 2341 F pulseaudio
   /dev/snd/pcmC1D0p:   donjan 2341 F...m pulseaudio
   /dev/snd/controlC1:  donjan 2341 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Dec 20 15:36:08 2016
  InstallationDate: Installed on 2016-10-25 (56 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20FXS0Y200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=104820cc-7d87-46d1-a1aa-e650ff221603 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET71W (2.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS0Y200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET71W(2.11):bd09/26/2016:svnLENOVO:pn20FXS0Y200:pvrThinkPadT460p:rvnLENOVO:rn20FXS0Y200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FXS0Y200
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651454/+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 1674986] Re: linux: 4.8.0-44.47 -proposed tracker

2017-03-23 Thread Ł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/1674986

Title:
  linux: 4.8.0-44.47 -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 Yakkety:
  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: 1674988
  derivatives: 1674989
  kernel-stable-phase-changed:Wednesday, 22. March 2017 21: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/1674986/+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 1670358] Re: Bcmwl-kernel-source not supporting wifi card

2017-03-23 Thread HB

I have managed to get through the process.
Thanks for patience

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

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

Title:
  Bcmwl-kernel-source not supporting wifi card

Status in bcmwl package in Ubuntu:
  Invalid

Bug description:
  No version of the driver would work with a Broadcom Limited BCM43142 
802.11b/g/n [14e4:4365] (rev 01) netcard on Ubuntu 16.10 LTS.
  Other information: actually the installation process won't disable Secure 
Boot so is the wrong working.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1
  ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  6 14:32:10 2017
  InstallationDate: Installed on 2017-03-05 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1670358/+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 1667323] Re: Backlight control does not work and there are no entries in /sys/class/backlight

2017-03-23 Thread André Desgualdo Pereira

Unfortunately you are right. 4.4 final is good.

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

Title:
  Backlight control does not work and there are no entries in
  /sys/class/backlight

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

Bug description:
  It was working fine until today. 
  The folder /sys/class/backlight/ use to have "acpi_video0/brightness", but 
now is empty. 
  I am using Nvidia Proprietary driver 340.101 (proprietary, tested). The 
problem persists even with the 304 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  desgua 2028 F pulseaudio
   /dev/snd/controlC0:  desgua 2028 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 23 11:31:18 2017
  HibernationDevice: RESUME=UUID=f23a6347-9483-460e-aa29-cbc47850f890
  InstallationDate: Installed on 2014-05-01 (1028 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 003: ID 064e:a127 Suyin Corp. 
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-17 (189 days ago)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

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

2017-03-23 Thread Ł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/1674938

Title:
  linux: 4.4.0-70.91 -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 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

  backports: 1674939
  derivatives: 1674940,1674941,1674944,1674945
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+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 1675329] Re: ubuntu_blktrace_smoke_test failed with "invalid path" on ARM64 Zesty

Fix emailed, waiting to be included in autotest-client-tests repo for
testing.

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

Title:
  ubuntu_blktrace_smoke_test failed with "invalid path" on ARM64 Zesty

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It looks like the sed in the get_dev() function is the cause.

  mount=$(stat -c '%m' $1 | tail -1)
  DEV=$(df $mount | grep dev | head -1 | cut -d' ' -f1 | sed 's/[0-9]//g')

  Note that this issue does not affect other amd64 systems, the sed
  command is for SATA devices there, to change /dev/sda1 to /dev/sda

  On ARM64 nodes, the actual DEV should be:
  /dev/disk/by-uuid/ec71a3bf-d777-4edb-a0ea-5b6d3504748d

  But after the sed command, it will become:
  /dev/disk/by-uuid/ecabf-d-edb-aea-bdd

  This is what I can see from /dev/disk/by-uuid:
  root@ms10-34-mcdivittB0-kernel:/dev/disk/by-uuid# ls
  9c648a56-06ad-4ca7-b23a-caaf7f5810a5  ec71a3bf-d777-4edb-a0ea-5b6d3504748d

  
  Error log:
  PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-4.10.0-14-generic)
  Using block device /dev/disk/by-uuid/ecabf-d-edb-aea-bdd for path 
/home/ubuntu/autotest/client/results/default/ubuntu_blktrace_smoke_test.blktrace-smoke-test
  FAILED expecting at least 1024 block traces events from the dd process, got 0
  FAILED expecting at least 1024 block read traces events, got 0
  FAILED expecting at least 1024 block write traces events, got 0
  Summary: 1 passed, 3 failed
  stderr:
  Invalid path /dev/disk/by-uuid/ecabf-d-edb-aea-bdd specified: 2/No such file 
or directory
  
/home/ubuntu/autotest/client/tests/ubuntu_blktrace_smoke_test/ubuntu_blktrace_smoke_test.sh:
 line 105: kill: (15290) - No such process

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-13-generic 4.10.0-13.15
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 23 04:39 seq
   crw-rw 1 root audio 116, 33 Mar 23 04:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Mar 23 08:59:50 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675329/+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 1675329] Re: ubuntu_blktrace_smoke_test failed with "invalid path" on ARM64 Zesty

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  ubuntu_blktrace_smoke_test failed with "invalid path" on ARM64 Zesty

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It looks like the sed in the get_dev() function is the cause.

  mount=$(stat -c '%m' $1 | tail -1)
  DEV=$(df $mount | grep dev | head -1 | cut -d' ' -f1 | sed 's/[0-9]//g')

  Note that this issue does not affect other amd64 systems, the sed
  command is for SATA devices there, to change /dev/sda1 to /dev/sda

  On ARM64 nodes, the actual DEV should be:
  /dev/disk/by-uuid/ec71a3bf-d777-4edb-a0ea-5b6d3504748d

  But after the sed command, it will become:
  /dev/disk/by-uuid/ecabf-d-edb-aea-bdd

  This is what I can see from /dev/disk/by-uuid:
  root@ms10-34-mcdivittB0-kernel:/dev/disk/by-uuid# ls
  9c648a56-06ad-4ca7-b23a-caaf7f5810a5  ec71a3bf-d777-4edb-a0ea-5b6d3504748d

  
  Error log:
  PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-4.10.0-14-generic)
  Using block device /dev/disk/by-uuid/ecabf-d-edb-aea-bdd for path 
/home/ubuntu/autotest/client/results/default/ubuntu_blktrace_smoke_test.blktrace-smoke-test
  FAILED expecting at least 1024 block traces events from the dd process, got 0
  FAILED expecting at least 1024 block read traces events, got 0
  FAILED expecting at least 1024 block write traces events, got 0
  Summary: 1 passed, 3 failed
  stderr:
  Invalid path /dev/disk/by-uuid/ecabf-d-edb-aea-bdd specified: 2/No such file 
or directory
  
/home/ubuntu/autotest/client/tests/ubuntu_blktrace_smoke_test/ubuntu_blktrace_smoke_test.sh:
 line 105: kill: (15290) - No such process

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-13-generic 4.10.0-13.15
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 23 04:39 seq
   crw-rw 1 root audio 116, 33 Mar 23 04:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Mar 23 08:59:50 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675329/+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 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update

2017-03-23 Thread N/A

Hi again,

after fiddeling around somehow, I found following combination most
useful:

evdev:name:*DualPoint Stick:dmi:bvn*:bvr*:bd*:svnDellInc.:pnPrecision7510*:pvr*
POINTINGSTICK_CONST_ACCEL=0.025

*AND* in ~/.xsession:

xinput set-prop 'AlpsPS/2 ALPS DualPoint Stick' 'libinput Accel Speed' 1

So set, it's a little bit slow when moving across the whole screen, but
accurate enough to position on very small items as single characters and small
buttons for example in BB forums. ;-)

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

Title:
Laptop stick and touchpad problems after linux 4.4 update

Status in linux package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Incomplete
Status in systemd source package in Xenial:
Confirmed

Bug description:
Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have
behaved erratically on my Dell Precision 7510:
* The trackpoint moves WAY too fast and there don't seem to be any parameters
I can change in xinput to fix this. It is essentially unusable.
* The touchpad starts with parameters set incorrectly.
* Touchpad tap to click is now turned on again and is very sensitive. This I
can change through xinput but the change is still odd.
* The two finger scrolling is set incorrectly to be highly sensitive. This I
can also change through xinput.
* Two finger scrolling still activates often during normal use of the
trackpad. To the extent that I had to turn off two finger scrolling to stop
inadvertent scrolling.

All of the above behavior is new going from 4.4.0-47 to -53.
Previously this all worked perfectly on this machine.

Seems to be symptoms noted by these other users on askubuntu here as
well: http://askubuntu.com/questions/862527/laptop-stick-mouse-
problems-after-linux-4-4-update-on-14-04

The touchpad symptoms I seem to be able to work around my changing
xinput parameters, but the trackpoint I have not been able to fix at
all (which is sad since that is my primary mouse device normally).
Would appreciate any suggestions as to how to revert the old behavior.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-53-generic 4.4.0-53.74
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jpeverill 2813 F pulseaudio
/dev/snd/controlC0: jpeverill 2813 F pulseaudio
Date: Wed Jan 18 10:21:55 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-07-17 (916 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc.
Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 7510
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed
root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-59-generic N/A
linux-backports-modules-4.4.0-59-generic N/A
linux-firmware1.157.6
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
dmi.bios.date: 01/24/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.10
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr: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/1657553/+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 1675327] [NEW] Fix line-out port noise on Baytrail-I with RT5660 based sound card

2017-03-23 Thread Shrirang Bagul

Public bug reported:

On Dell IoT gateways, Baytrail-I ASoC with RT5660(ALC3277) codec
supports line-out port. However, the audio output has background noise.

This bug is used for tracking purposes, please do not triage.

** Affects: hwe-next
 Importance: Critical
 Assignee: Shrirang Bagul (shrirang-bagul)
 Status: In Progress

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Shrirang Bagul (shrirang-bagul)
 Status: In Progress


** Tags: originate-from-1672679 plano

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)

** Tags added: originate-from-1672679 plano

** Summary changed:

- Fix noise on line-out port on Baytrail-I+RT5660 based sound card
+ Fix line-out port noise on Baytrail-I+RT5660 based sound card

** Changed in: hwe-next
   Status: New => In Progress

** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
 Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)

** Summary changed:

- Fix line-out port noise on Baytrail-I+RT5660 based sound card
+ Fix line-out port noise on Baytrail-I with RT5660 based sound card

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

Title:
  Fix line-out port noise on Baytrail-I with RT5660 based sound card

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  On Dell IoT gateways, Baytrail-I ASoC with RT5660(ALC3277) codec
  supports line-out port. However, the audio output has background
  noise.

  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1675327/+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 1675329] [NEW] ubuntu_blktrace_smoke_test failed with "invalid path" on ARM64 Zesty

2017-03-23 Thread Po-Hsu Lin

Public bug reported:

It looks like the sed in the get_dev() function is the cause.

mount=$(stat -c '%m' $1 | tail -1)
DEV=$(df $mount | grep dev | head -1 | cut -d' ' -f1 | sed 's/[0-9]//g')

Note that this issue does not affect other amd64 systems, the sed
command is for SATA devices there, to change /dev/sda1 to /dev/sda

On ARM64 nodes, the actual DEV should be:
/dev/disk/by-uuid/ec71a3bf-d777-4edb-a0ea-5b6d3504748d

But after the sed command, it will become:
/dev/disk/by-uuid/ecabf-d-edb-aea-bdd

This is what I can see from /dev/disk/by-uuid:
root@ms10-34-mcdivittB0-kernel:/dev/disk/by-uuid# ls
9c648a56-06ad-4ca7-b23a-caaf7f5810a5  ec71a3bf-d777-4edb-a0ea-5b6d3504748d


Error log:
PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-4.10.0-14-generic)
Using block device /dev/disk/by-uuid/ecabf-d-edb-aea-bdd for path 
/home/ubuntu/autotest/client/results/default/ubuntu_blktrace_smoke_test.blktrace-smoke-test
FAILED expecting at least 1024 block traces events from the dd process, got 0
FAILED expecting at least 1024 block read traces events, got 0
FAILED expecting at least 1024 block write traces events, got 0
Summary: 1 passed, 3 failed
stderr:
Invalid path /dev/disk/by-uuid/ecabf-d-edb-aea-bdd specified: 2/No such file or 
directory
/home/ubuntu/autotest/client/tests/ubuntu_blktrace_smoke_test/ubuntu_blktrace_smoke_test.sh:
 line 105: kill: (15290) - No such process

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-13-generic 4.10.0-13.15
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar 23 04:39 seq
 crw-rw 1 root audio 116, 33 Mar 23 04:39 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.4-0ubuntu2
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Mar 23 08:59:50 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-13-generic N/A
 linux-backports-modules-4.10.0-13-generic  N/A
 linux-firmware 1.164
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Colin Ian King (colin-king)
 Status: In Progress


** Tags: apport-bug arm64 uec-images zesty

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

Title:
  ubuntu_blktrace_smoke_test failed with "invalid path" on ARM64 Zesty

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It looks like the sed in the get_dev() function is the cause.

  mount=$(stat -c '%m' $1 | tail -1)
  DEV=$(df $mount | grep dev | head -1 | cut -d' ' -f1 | sed 's/[0-9]//g')

  Note that this issue does not affect other amd64 systems, the sed
  command is for SATA devices there, to change /dev/sda1 to /dev/sda

  On ARM64 nodes, the actual DEV should be:
  /dev/disk/by-uuid/ec71a3bf-d777-4edb-a0ea-5b6d3504748d

  But after the sed command, it will become:
  /dev/disk/by-uuid/ecabf-d-edb-aea-bdd

  This is what I can see from /dev/disk/by-uuid:
  root@ms10-34-mcdivittB0-kernel:/dev/disk/by-uuid# ls
  9c648a56-06ad-4ca7-b23a-caaf7f5810a5  ec71a3bf-d777-4edb-a0ea-5b6d3504748d

  
  Error log:
  PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-4.10.0-14-generic)
  Using block device /dev/disk/by-uuid/ecabf-d-edb-aea-bdd for path 
/home/ubuntu/autotest/client/results/default/ubuntu_blktrace_smoke_test.blktrace-smoke-test
  FAILED expecting at least 1024 block traces events from the dd process, got 0
  FAILED expecting at least 1024 block read traces events, got 0
  FAILED expecting at least 1024 block write traces events, got 0
  Summary: 1 passed, 3 failed
  stderr:
  Invalid path /dev/disk/by-uuid/ecabf-d-edb-aea-bdd specified: 2/No such file 
or directory
  
/home/ubuntu/autotest/client/tests/ubuntu_blktrace_smoke_test/ubuntu_blktrace_smoke_test.sh:
 line 105: kill: (15290) - No such process

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-13-generic 4.10.0-13.15
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 23 04:39 seq
   crw-rw 1 root audio 116, 33 Mar 23 04:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:

[Kernel-packages] [Bug 1673805] hainzel (amd64) - tests ran: 21, failed: 0

tests ran:  21, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-14.16-generic/hainzel__4.10.0-14.16__2017-03-23_06-44-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/1673805

Title:
  linux: 4.10.0-14.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-14.16 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-development-workflow/+bug/1673805/+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 1673211] Re: linux-lts-trusty: 3.13.0-114.161~precise1 -proposed tracker

2017-03-23 Thread Taihsiang Ho

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  linux-lts-trusty: 3.13.0-114.161~precise1 -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:
  In Progress
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1673207
  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/1673211/+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 1674986] onibi (i386) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-44.47-generic/onibi__4.8.0-44.47__2017-03-23_06-51-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/1674986

Title:
  linux: 4.8.0-44.47 -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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1674988
  derivatives: 1674989
  kernel-stable-phase-changed:Wednesday, 22. March 2017 21: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/1674986/+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 1673805] gonzo (amd64) - tests ran: 2, failed: 0

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-14.16-generic/gonzo__4.10.0-14.16__2017-03-23_06-44-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/1673805

Title:
  linux: 4.10.0-14.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-14.16 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-development-workflow/+bug/1673805/+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 1673805] modoc (ppc64el) - tests ran: 1, failed: 0