date:20170419

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/pepe__4.4.0-74.95__2017-04-20_03-45-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/1682041

Title:
  linux: 4.4.0-74.95 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- 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/1682041/+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 1682041] onza (amd64) - tests ran: 1, failed: 1

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/onza__4.4.0-74.95__2017-04-20_04-50-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/1682041

Title:
  linux: 4.4.0-74.95 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- 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/1682041/+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 1684260] Re: kernel error (hardly reproducible)

2017-04-19 Thread Brian Murray

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

** Tags added: likely-dup

** This bug has been marked a duplicate of bug 1674838
   kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

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

Title:
  kernel error (hardly reproducible)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I was doing too many things when this error occured, so I'm not able
  to report accurately. This happened just once for me on otherwise
  stable system.

  Kubuntu Zesty
  Linux peltan 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:26 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  firefox/zesty-updates,zesty-security,now 52.0.1+build2-0ubuntu1 amd64 

  I remember to run ~10 applications; in Firefox, i clicked on a link to
  PDF, opening a PDF js viewer, then i closed the tab, then reopened the
  tab again and before the PDF loaded up back, i clicked on Back button.
  At that moment, Firefox freezed up. I switched to other applications,
  they worked normally, including HDD access. An exception: in terminal,
  `htop` was not able to load. I looked into dmesg output and found what
  is pasted below. After some time (1-2 minutes), all the applications
  started freezing up, probably when requesting hard disk I/O. No other
  option that hard-reboot the computer.

  Please tell me what other gatherable information shall i append.

  [30045.147014] [ cut here ]
  [30045.147036] kernel BUG at 
/build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129!
  [30045.147059] invalid opcode:  [#1] SMP
  [30045.147071] Modules linked in: mmc_block rfcomm snd_hrtimer cmac bnep 
binfmt_misc nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc snd_hda_codec_hdmi 
snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core dell_led snd_soc_sst_match 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine btusb snd_hda_intel btrtl snd_hda_codec arc4 snd_hda_core 
dell_wmi snd_hwdep sparse_keymap snd_pcm intel_rapl x86_pkg_temp_thermal 
snd_seq_midi snd_seq_midi_event intel_powerclamp coretemp snd_rawmidi kvm_intel 
dell_laptop dell_smbios dcdbas dell_smm_hwmon kvm irqbypass crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel snd_seq pcbc iwlmvm mac80211 snd_seq_device 
snd_timer aesni_intel aes_x86_64 crypto_simd glue_helper cryptd iwlwifi 
intel_cstate intel_rapl_perf snd cfg80211 rtsx_pci_ms
  [30045.147259]  input_leds serio_raw memstick soundcore mei_me mei shpchp 
processor_thermal_device intel_pch_thermal intel_soc_dts_iosf hci_uart btbcm 
btqca btintel bluetooth dell_smo8800 intel_lpss_acpi intel_lpss int3400_thermal 
int3403_thermal acpi_thermal_rel int340x_thermal_zone acpi_pad dell_rbtn 
acpi_als kfifo_buf industrialio joydev mac_hid parport_pc ppdev lp parport 
ip_tables x_tables autofs4 hid_generic usbhid rtsx_pci_sdmmc i915 i2c_algo_bit 
drm_kms_helper e1000e psmouse syscopyarea sysfillrect sysimgblt ptp fb_sys_fops 
pps_core drm ahci rtsx_pci libahci wmi video i2c_hid pinctrl_sunrisepoint hid 
pinctrl_intel fjes
  [30045.147411] CPU: 0 PID: 1931 Comm: firefox Not tainted 4.10.0-14-generic 
#16-Ubuntu
  [30045.147431] Hardware name: Dell Inc. Latitude E5470/0P88J9, BIOS 1.7.3 
06/15/2016
  [30045.147452] task: 8adb5c64ae00 task.stack: a2b7827e4000
  [30045.147471] RIP: 0010:__migration_entry_wait+0x16a/0x180
  [30045.147489] RSP: :a2b7827e7d68 EFLAGS: 00010246
  [30045.147509] RAX: 000fc0048078 RBX: cbe1456726b0 RCX: 
cbe1456726b0
  [30045.147537] RDX: 0001 RSI: 8adad9c9aad8 RDI: 
cbe1408ad6c0
  [30045.147562] RBP: a2b7827e7d80 R08: 8adbc00f26c0 R09: 
8adbc00f26c0
  [30045.147588] R10: 7fa514f00220 R11: 7fa4b8b01640 R12: 
cbe1408ad6c0
  [30045.147617] R13: 3e022b5b R14: a2b7827e7e30 R15: 
8adbbf0f67d0
  [30045.147644] FS:  7fa5162b5740() GS:8adbcdc0() 
knlGS:
  [30045.147684] CS:  0010 DS:  ES:  CR0: 80050033
  [30045.147710] CR2: 7fa4d455be28 CR3: 00023eb3c000 CR4: 
003406f0
  [30045.147737] Call Trace:
  [30045.147758]  migration_entry_wait+0x74/0x80
  [30045.147780]  do_swap_page+0x5b3/0x770
  [30045.147792]  handle_mm_fault+0x873/0x1360
  [30045.147806]  __do_page_fault+0x23e/0x4e0
  [30045.147819]  do_page_fault+0x22/0x30
  [30045.147832]  page_fault+0x28/0x30
  [30045.147843] RIP: 0033:0x7fa50572bbaa
  [30045.147854] RSP: 002b:7ffcbbbe2450 EFLAGS: 00010202
  [30045.147869] RAX: 7fa4d455be20 RBX: 7fa4d455be20 RCX: 
0003
  [30045.147888] RDX: 7fa49e681600 RSI:  RDI: 
7fa514f00040
  [30045.147907] RBP:  R08:  R09: 
7fa514f00220
  [30045.147927] R10: 7fa514f00220 R11: 7fa4b8b01640 R12:

[Kernel-packages] [Bug 1683982] Re: net/ipv4: original ingress device index set as the loopback interface.

2017-04-19 Thread Gavin Guo

@Joseph Salisbury,

Yes, Jorge has identified the bug and will send out the SRU patches.

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

Title:
  net/ipv4: original ingress device index set as the loopback interface.

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  [Environment]

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

  # uname -a

  Linux juju-niedbalski-xenial-machine-12 4.8.0-46-generic
  #49~16.04.1-Ubuntu SMP Fri Mar 31 14:51:03 UTC 2017 x86_64 x86_64
  x86_64 GNU/Linux

  [Description]

  When we send a packet for our own local address on a non-loopback
  interface (e.g. eth0), due to the change had been introduced from
  commit 0b922b7 ("net: original ingress device index in PKTINFO"), the
  original ingress device index would be set as the loopback interface.

  [Fix]

  *
  
https://github.com/torvalds/linux/commit/f0c16ba8933ed217c2688b277410b2a37ba81591

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683982/+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 1682041] pepe (amd64) - tests ran: 34, failed: 5

tests ran:  34, failed: 5;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/pepe__4.4.0-74.95__2017-04-20_02-28-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/1682041

Title:
  linux: 4.4.0-74.95 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- 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/1682041/+subscriptions

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

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

2017-04-19 Thread Allingo.M

I tested Joseph solution on Gigabyte AB350M(bios F4) with success.

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

  1. add "acpi=off" to boot params

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

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

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

  Some observed problems:

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1682041] pepe (amd64) - tests ran: 34, failed: 4

tests ran:  34, failed: 4;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/pepe__4.4.0-74.95__2017-04-20_01-20-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/1682041

Title:
  linux: 4.4.0-74.95 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- 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/1682041/+subscriptions

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

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

2017-04-19 Thread Milosz Tanski

Roland, you sure there isn't another BIOS toggle you managed to find? On
the Gaming K7 with F3 BIOS and this still happens unless the offending
code is compiled out.

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

  1. add "acpi=off" to boot params

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

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

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

  Some observed problems:

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1684120] Re: Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 (U

2017-04-19 Thread wenxiaocong

Thank you! As these device can't connect to internet of security
limited, Dose it can capture log by offline then upload to Ubuntu
Community？ PLS advise how can do it, BTW, I have upload the all of log
files"Kernel log file-1.2MB" Thanks a lot for your help!

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

Title:
  Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0
  20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun
  Feb 5 09:39:57 UTC 2017 (Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11)
  Will intermittent crash when connect to above 2 USB device and reset
  USB device-Mobile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Clean installed with Ubuntu 16.04.02 TLS Desktop 64bit
  We used some desktop computer to test the android mobile phone. Link to PC 
through USB Type-C and Micro USB.
  We set an APK file to let mobile auto mount/dismount around 1 time/minutes.
  Kernel will intermittent crash, Even test from 16.04.01 LTS same as well.
  Seek your advise if any kernel upgrade or idea can resolve this issue.How to 
create the trace log for deep analysis if need?
  I have attach the log file for your reference, Thanks very much!!

  Kernel info:
  Apr 17 16:17:00 SH-11F3-A10-0605 kernel: [0.00] Linux version 
4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 
5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 
(Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11)
  Apr 17 16:17:00 SH-11F3-A10-0605 kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic.efi.signed 
root=UUID=4e264b55-dafb-4b87-9c25-6902e5f54272 ro quiet splash vt.handoff=7

  Log as below:
  Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.235348] scsi 1506:0:0:0: 
CD-ROMLinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
  Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.236703] sr 1506:0:0:0: [sr2] 
scsi-1 drive Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.237193] sr 
1506:0:0:0: Attached scsi CD-ROM sr2 Apr 14 21:15:51 SH-11F3-A10-0401 kernel: 
[13702.237436] sr 1506:0:0:0: Attached scsi generic sg3 type 5 Apr 14 21:15:51 
SH-11F3-A10-0401 kernel: [13702.286619] usb 1-3: new high-speed USB device 
number 120 using xhci_hcd Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.415975] usb 1-3: New USB device found, idVendor=12d1, idProduct=107e Apr 
14 21:15:52 SH-11F3-A10-0401 kernel: [13702.415982] usb 1-3: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3 Apr 14 21:15:52 SH-11F3-A10-0401 
kernel: [13702.415987] usb 1-3: Product: HUAWEI Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.415990] usb 1-3: Manufacturer: unknown Apr 14 
21:15:52 SH-11F3-A10-0401 kernel: [13702.415993] usb 1-3: SerialNumber: 
K4Q011642205 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.417894] 
usb-storage 1-3:1.3: USB Mass Storage device detected Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.418103] scsi host1507: usb-storage 1-3:1.3 Apr 
14 21:15:52 SH-11F3-A10-0401 kernel: [13702.838577] usb 1-7: new high-speed USB 
device number 121 using xhci_hcd Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.967820] usb 1-7: New USB device found, idVendor=12d1, idProduct=107e Apr 
14 21:15:52 SH-11F3-A10-0401 kernel: [13702.967829] usb 1-7: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3 Apr 14 21:15:52 SH-11F3-A10-0401 
kernel: [13702.967833] usb 1-7: Product: HUAWEI Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.967837] usb 1-7: Manufacturer: unknown Apr 14 
21:15:52 SH-11F3-A10-0401 kernel: [13702.967841] usb 1-7: SerialNumber: 
R3E011611771 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.969529] 
usb-storage 1-7:1.3: USB Mass Storage device detected Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.969724] scsi host1508: usb-storage 1-7:1.3
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.415340] scsi 1507:0:0:0: 
CD-ROMLinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.416594] sr 1507:0:0:0: [sr3] 
scsi-1 drive Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.417121] sr 
1507:0:0:0: Attached scsi CD-ROM sr3 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: 
[13703.417352] sr 1507:0:0:0: Attached scsi generic sg4 type 5
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.967196] scsi 1508:0:0:0: 
CD-ROMLinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.968605] sr 1508:0:0:0: [sr4] 
scsi-1 drive Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.969154] sr 
1508:0:0:0: Attached scsi CD-ROM sr4 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: 
[13703.969358] sr 1508:0:0:0: Attached scsi generic sg5 type 5 Apr 14 21:15:53 
SH-11F3-A10-0401 kernel: [13704.120986] usb 1-1: USB disconnect, device number 
117

[Kernel-packages] [Bug 1626158] Re: image won't boot after upgrading to yakkety's 4.8 kernel because efi

2017-04-19 Thread Mathew Hodson

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

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

Title:
  image won't boot after upgrading to yakkety's 4.8 kernel because efi

Status in cloud-images:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New

Bug description:
  If I use a relatively recent yakkety daily with uvt-kvm,

  com.ubuntu.cloud.daily:server:16.10:amd64 20160918

  and upgrade the kernel to the latest kernel (which happens to be 4.8),
  my VM won't boot any more. kern.log has:

  http://paste.ubuntu.com/23211671/

  and systemd complains that,

  [FAILED] Failed to mount /boot/efi
  See 'systemctl status boot-efi.mount' for details.

  and dumps me to a recovery console. Of course, I don't have EFI since
  I'm booting this thing on KVM. The problem here (I think) is that
  /boot/efi is in /etc/fstab, and systemd fails to boot when anything in
  /etc/fstab doesn't work.

  If I comment /boot/efi out of /etc/fstab, it boots just fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1626158/+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 1682041] pepe (i386) - tests ran: 4, failed: 0

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/pepe__4.4.0-74.95__2017-04-20_00-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/1682041

Title:
  linux: 4.4.0-74.95 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- 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/1682041/+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 1682041] pepe (i386) - tests ran: 4, failed: 0

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/pepe__4.4.0-74.95__2017-04-19_23-25-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/1682041

Title:
  linux: 4.4.0-74.95 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- 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/1682041/+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 1682041] pepe (i386) - tests ran: 10, failed: 0

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/pepe__4.4.0-74.95__2017-04-19_22-23-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/1682041

Title:
  linux: 4.4.0-74.95 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- 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/1682041/+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 1647036] Re: Client does not ACK auth/assoc responses from Cisco AP3800

2017-04-19 Thread Steve Langasek

Alberto, could you please confirm whether this has been verified for
yakkety?

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

Title:
  Client does not ACK auth/assoc responses from Cisco AP3800

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Trusty:
  Fix Committed
Status in bcmwl source package in Xenial:
  Fix Released
Status in bcmwl source package in Yakkety:
  Fix Committed
Status in bcmwl source package in Zesty:
  Fix Released

Bug description:
  This client does not ACK Assoc Responses from a Cisco 3800.  Traces
  attached.

  - Model:Dell XPS13 9343
  - OS Version:Ubuntu 14.04.5 LTS
  - WNIC:Broadcom BCM4352 rev. 03 driver version 6.30.223.248
  - SSID:user.wifi (WPA2/dot1x )
  - MAC address:c4:8e:8f:f5:4a:7f
  -Cisco AP : 3800 (wave 2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1647036/+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 1680733] onza (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/onza__3.13.0-117.164__2017-04-19_22-05-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
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: 1680735
  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/1680733/+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 1682041] pepe (amd64) - tests ran: 10, failed: 0

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/pepe__4.4.0-74.95__2017-04-19_21-19-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/1682041

Title:
  linux: 4.4.0-74.95 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- 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/1682041/+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 1680390] alinefm-avocado-tests-4.10.0-19

--- Comment (attachment only) From alin...@br.ibm.com 2017-04-19 16:59 
EDT---


** Attachment added: "alinefm-avocado-tests-4.10.0-19"
   
https://bugs.launchpad.net/bugs/1680390/+attachment/4865173/+files/alinefm-avocado-4.10.0-19.tar.xz

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

Title:
  Ubuntu17.04: Kernel Oops: Exception in kernel mode, sig: 5 [#1] during
  Avocado KVM Test runs [Regression]

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2017-03-27 
12:30:45 ==
  ---Problem Description---
  Kernel hit with oops while running avocado(kvm) tests "Oops: Exception in 
kernel mode, sig: 5 [#1]"
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  Linux ltc-test-ci1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = power 8 ppc64le 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Run Avocado(kvm) tests
  #git clone git://git.linux.ibm.com/ltc-test/avocado-fvt-wrapper.git;cd 
avocado-fvt-wrapper
  #python avocado-setup.py --bootstrap --run-suite guest_cpu --guest-os 
Ubuntu.16.04.2.ppc64le --only-filter virtio_scsi virtio_net qcow2

  2. After sometime the below mentioned traces were seen.
   
  Stack trace output:
   [20751.909458] [ cut here ]
  [20751.909461] kernel BUG at 
/build/linux-HLNhAK/linux-4.10.0/include/linux/swapops.h:129!
  [20751.909542] Oops: Exception in kernel mode, sig: 5 [#1]
  [20751.909549] SMP NR_CPUS=2048 
  [20751.909549] NUMA 
  [20751.909555] PowerNV
  [20751.909583] Modules linked in: vhost_net macvtap macvlan xt_CHECKSUM 
ipt_MASQUERADE nf_nat_masquerade_ipv4 kvm_hv kvm_pr kvm tcm_fc libfc usb_f_tcm 
tcm_usb_gadget libcomposite udc_core tcm_qla2xxx qla2xxx scsi_transport_fc 
ib_srpt iscsi_target_mod tcm_loop vhost_scsi vhost target_core_user 
target_core_file target_core_iblock target_core_pscsi target_core_mod 
ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6t_REJECT nf_reject_ipv6 xt_conntrack 
ip6t_rpfilter ip_set nfnetlink ebtable_broute bridge stp llc ebtable_nat 
ip6table_security ip6table_mangle ip6table_raw ip6table_nat iptable_security 
iptable_mangle iptable_raw iptable_nat ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter openvswitch nf_conntrack_ipv6 nf_nat_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack
  [20751.910225]  binfmt_misc powernv_rng powernv_op_panel ipmi_powernv 
ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio leds_powernv vmx_crypto 
ib_iser rdma_cm iw_cm ib_cm ib_core nfsd auth_rpcgss nfs_acl lockd grace 
configfs iscsi_tcp libiscsi_tcp sunrpc 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 ses 
enclosure scsi_transport_sas crc32c_vpmsum tg3 ipr
  [20751.910629] CPU: 24 PID: 6926 Comm: CPU 24/KVM Not tainted 
4.10.0-14-generic #16-Ubuntu
  [20751.910700] task: c007b29ac000 task.stack: c007f07b8000
  [20751.910759] NIP: c030d748 LR: c030d658 CTR: 

  [20751.910828] REGS: c007f07bb3b0 TRAP: 0700   Not tainted  
(4.10.0-14-generic)
  [20751.910897] MSR: 90029033 
  [20751.910903]   CR: 44882882  XER: 
  [20751.910984] CFAR: c030d884 SOFTE: 1 
 GPR00: c030d658 c007f07bb630 c144c900 
f1f9f1f0 
 GPR04: c007e7c7e0e0 f1f9f1f0 1f001c61 
611c001f 
 GPR08: c15bc900 0001 0001 
00e0c7e7 
 GPR12: 2200 cfb8d800  
0007fe1d 
 GPR16: 0001 3fff121c  
8800 
 GPR20: 2000 8800 2200 
c499 
 GPR24: c15be3d8 c007f05d3700 c007b972c030 
 
 GPR28: c007f07bb710 3e0d611c f3584700 
f1f9f1f0 
  [20751.911580] NIP [c030d748] __migration_entry_wait+0x128/0x2a0
  [20751.911639] LR [c030d658] __migration_entry_wait+0x38/0x2a0
  [20751.911697] Call Trace:
  [20751.911722] [c007f07bb630] [c030d658] 
__migration_entry_wait+0x38/0x2a0 (unreliable)
  [20751.911807] [c007f07bb670] [c02bbc6c] do_swap_page+0x73c/0x9a0
  [20751.911866] [c007f07bb6f0] [c02bfa98] 
handle_mm_fault+0xac8/0x1600
  [20751.911937] [c007f07bb7e0] [c02b4104] 
__get_user_pages+0x194/0x4e0
  [20751.912008] [c007f07bb890] [c02b47e4] 
get_user_pages_unlocked+0xf4/0x280
  [20751.912079]

[Kernel-packages] [Bug 1682041] pepe (amd64) - tests ran: 10, failed: 0

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/pepe__4.4.0-74.95__2017-04-19_20-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/1682041

Title:
  linux: 4.4.0-74.95 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- 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/1682041/+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 1684260] Missing required logs.

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

apport-collect 1684260

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

Title:
  kernel error (hardly reproducible)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I was doing too many things when this error occured, so I'm not able
  to report accurately. This happened just once for me on otherwise
  stable system.

  Kubuntu Zesty
  Linux peltan 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:26 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  firefox/zesty-updates,zesty-security,now 52.0.1+build2-0ubuntu1 amd64 

  I remember to run ~10 applications; in Firefox, i clicked on a link to
  PDF, opening a PDF js viewer, then i closed the tab, then reopened the
  tab again and before the PDF loaded up back, i clicked on Back button.
  At that moment, Firefox freezed up. I switched to other applications,
  they worked normally, including HDD access. An exception: in terminal,
  `htop` was not able to load. I looked into dmesg output and found what
  is pasted below. After some time (1-2 minutes), all the applications
  started freezing up, probably when requesting hard disk I/O. No other
  option that hard-reboot the computer.

  Please tell me what other gatherable information shall i append.

  [30045.147014] [ cut here ]
  [30045.147036] kernel BUG at 
/build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129!
  [30045.147059] invalid opcode:  [#1] SMP
  [30045.147071] Modules linked in: mmc_block rfcomm snd_hrtimer cmac bnep 
binfmt_misc nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc snd_hda_codec_hdmi 
snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core dell_led snd_soc_sst_match 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine btusb snd_hda_intel btrtl snd_hda_codec arc4 snd_hda_core 
dell_wmi snd_hwdep sparse_keymap snd_pcm intel_rapl x86_pkg_temp_thermal 
snd_seq_midi snd_seq_midi_event intel_powerclamp coretemp snd_rawmidi kvm_intel 
dell_laptop dell_smbios dcdbas dell_smm_hwmon kvm irqbypass crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel snd_seq pcbc iwlmvm mac80211 snd_seq_device 
snd_timer aesni_intel aes_x86_64 crypto_simd glue_helper cryptd iwlwifi 
intel_cstate intel_rapl_perf snd cfg80211 rtsx_pci_ms
  [30045.147259]  input_leds serio_raw memstick soundcore mei_me mei shpchp 
processor_thermal_device intel_pch_thermal intel_soc_dts_iosf hci_uart btbcm 
btqca btintel bluetooth dell_smo8800 intel_lpss_acpi intel_lpss int3400_thermal 
int3403_thermal acpi_thermal_rel int340x_thermal_zone acpi_pad dell_rbtn 
acpi_als kfifo_buf industrialio joydev mac_hid parport_pc ppdev lp parport 
ip_tables x_tables autofs4 hid_generic usbhid rtsx_pci_sdmmc i915 i2c_algo_bit 
drm_kms_helper e1000e psmouse syscopyarea sysfillrect sysimgblt ptp fb_sys_fops 
pps_core drm ahci rtsx_pci libahci wmi video i2c_hid pinctrl_sunrisepoint hid 
pinctrl_intel fjes
  [30045.147411] CPU: 0 PID: 1931 Comm: firefox Not tainted 4.10.0-14-generic 
#16-Ubuntu
  [30045.147431] Hardware name: Dell Inc. Latitude E5470/0P88J9, BIOS 1.7.3 
06/15/2016
  [30045.147452] task: 8adb5c64ae00 task.stack: a2b7827e4000
  [30045.147471] RIP: 0010:__migration_entry_wait+0x16a/0x180
  [30045.147489] RSP: :a2b7827e7d68 EFLAGS: 00010246
  [30045.147509] RAX: 000fc0048078 RBX: cbe1456726b0 RCX: 
cbe1456726b0
  [30045.147537] RDX: 0001 RSI: 8adad9c9aad8 RDI: 
cbe1408ad6c0
  [30045.147562] RBP: a2b7827e7d80 R08: 8adbc00f26c0 R09: 
8adbc00f26c0
  [30045.147588] R10: 7fa514f00220 R11: 7fa4b8b01640 R12: 
cbe1408ad6c0
  [30045.147617] R13: 3e022b5b R14: a2b7827e7e30 R15: 
8adbbf0f67d0
  [30045.147644] FS:  7fa5162b5740() GS:8adbcdc0() 
knlGS:
  [30045.147684] CS:  0010 DS:  ES:  CR0: 80050033
  [30045.147710] CR2: 7fa4d455be28 CR3: 00023eb3c000 CR4: 
003406f0
  [30045.147737] Call Trace:
  [30045.147758]  migration_entry_wait+0x74/0x80
  [30045.147780]  do_swap_page+0x5b3/0x770
  [30045.147792]  handle_mm_fault+0x873/0x1360
  [30045.147806]  __do_page_fault+0x23e/0x4e0
  [30045.147819]  do_page_fault+0x22/0x30
  [30045.147832]  page_fault+0x28/0x30
  [30045.147843] RIP: 0033:0x7fa50572bbaa
  [30045.147854] RSP: 002b:7ffcbbbe2450 EFLAGS: 00010202
  [30045.147869] RAX: 7fa4d455be20 RBX: 7fa4d455be20 RCX:

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

2017-04-19 Thread Jeffery Painter

I've been working pretty heavily throughout the day (Eclipse, Chrome,
Thunderbird, MySQL, etc) with the 4.10.0-8 and haven't hit the bug.  I
will run a couple more days on this version and see if it pops up.

painter@merlin:~$ uname -a 
Linux merlin 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:04:59 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

painter@merlin:~$ uptime
 16:48:33 up  6:59,  1 user,  load average: 0.36, 0.52, 0.64

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

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

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

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

  Relevant dmesg attached (dmesg_crash.txt).

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

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

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

[Kernel-packages] [Bug 1684260] Re: kernel error (hardly reproducible)

2017-04-19 Thread Brian Murray

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  kernel error (hardly reproducible)

Status in linux package in Ubuntu:
  New

Bug description:
  I was doing too many things when this error occured, so I'm not able
  to report accurately. This happened just once for me on otherwise
  stable system.

  Kubuntu Zesty
  Linux peltan 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:26 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  firefox/zesty-updates,zesty-security,now 52.0.1+build2-0ubuntu1 amd64 

  I remember to run ~10 applications; in Firefox, i clicked on a link to
  PDF, opening a PDF js viewer, then i closed the tab, then reopened the
  tab again and before the PDF loaded up back, i clicked on Back button.
  At that moment, Firefox freezed up. I switched to other applications,
  they worked normally, including HDD access. An exception: in terminal,
  `htop` was not able to load. I looked into dmesg output and found what
  is pasted below. After some time (1-2 minutes), all the applications
  started freezing up, probably when requesting hard disk I/O. No other
  option that hard-reboot the computer.

  Please tell me what other gatherable information shall i append.

  [30045.147014] [ cut here ]
  [30045.147036] kernel BUG at 
/build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129!
  [30045.147059] invalid opcode:  [#1] SMP
  [30045.147071] Modules linked in: mmc_block rfcomm snd_hrtimer cmac bnep 
binfmt_misc nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc snd_hda_codec_hdmi 
snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core dell_led snd_soc_sst_match 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine btusb snd_hda_intel btrtl snd_hda_codec arc4 snd_hda_core 
dell_wmi snd_hwdep sparse_keymap snd_pcm intel_rapl x86_pkg_temp_thermal 
snd_seq_midi snd_seq_midi_event intel_powerclamp coretemp snd_rawmidi kvm_intel 
dell_laptop dell_smbios dcdbas dell_smm_hwmon kvm irqbypass crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel snd_seq pcbc iwlmvm mac80211 snd_seq_device 
snd_timer aesni_intel aes_x86_64 crypto_simd glue_helper cryptd iwlwifi 
intel_cstate intel_rapl_perf snd cfg80211 rtsx_pci_ms
  [30045.147259]  input_leds serio_raw memstick soundcore mei_me mei shpchp 
processor_thermal_device intel_pch_thermal intel_soc_dts_iosf hci_uart btbcm 
btqca btintel bluetooth dell_smo8800 intel_lpss_acpi intel_lpss int3400_thermal 
int3403_thermal acpi_thermal_rel int340x_thermal_zone acpi_pad dell_rbtn 
acpi_als kfifo_buf industrialio joydev mac_hid parport_pc ppdev lp parport 
ip_tables x_tables autofs4 hid_generic usbhid rtsx_pci_sdmmc i915 i2c_algo_bit 
drm_kms_helper e1000e psmouse syscopyarea sysfillrect sysimgblt ptp fb_sys_fops 
pps_core drm ahci rtsx_pci libahci wmi video i2c_hid pinctrl_sunrisepoint hid 
pinctrl_intel fjes
  [30045.147411] CPU: 0 PID: 1931 Comm: firefox Not tainted 4.10.0-14-generic 
#16-Ubuntu
  [30045.147431] Hardware name: Dell Inc. Latitude E5470/0P88J9, BIOS 1.7.3 
06/15/2016
  [30045.147452] task: 8adb5c64ae00 task.stack: a2b7827e4000
  [30045.147471] RIP: 0010:__migration_entry_wait+0x16a/0x180
  [30045.147489] RSP: :a2b7827e7d68 EFLAGS: 00010246
  [30045.147509] RAX: 000fc0048078 RBX: cbe1456726b0 RCX: 
cbe1456726b0
  [30045.147537] RDX: 0001 RSI: 8adad9c9aad8 RDI: 
cbe1408ad6c0
  [30045.147562] RBP: a2b7827e7d80 R08: 8adbc00f26c0 R09: 
8adbc00f26c0
  [30045.147588] R10: 7fa514f00220 R11: 7fa4b8b01640 R12: 
cbe1408ad6c0
  [30045.147617] R13: 3e022b5b R14: a2b7827e7e30 R15: 
8adbbf0f67d0
  [30045.147644] FS:  7fa5162b5740() GS:8adbcdc0() 
knlGS:
  [30045.147684] CS:  0010 DS:  ES:  CR0: 80050033
  [30045.147710] CR2: 7fa4d455be28 CR3: 00023eb3c000 CR4: 
003406f0
  [30045.147737] Call Trace:
  [30045.147758]  migration_entry_wait+0x74/0x80
  [30045.147780]  do_swap_page+0x5b3/0x770
  [30045.147792]  handle_mm_fault+0x873/0x1360
  [30045.147806]  __do_page_fault+0x23e/0x4e0
  [30045.147819]  do_page_fault+0x22/0x30
  [30045.147832]  page_fault+0x28/0x30
  [30045.147843] RIP: 0033:0x7fa50572bbaa
  [30045.147854] RSP: 002b:7ffcbbbe2450 EFLAGS: 00010202
  [30045.147869] RAX: 7fa4d455be20 RBX: 7fa4d455be20 RCX: 
0003
  [30045.147888] RDX: 7fa49e681600 RSI:  RDI: 
7fa514f00040
  [30045.147907] RBP:  R08:  R09: 
7fa514f00220
  [30045.147927] R10: 7fa514f00220 R11: 7fa4b8b01640 R12: 
7fa4b645b480
  [30045.147948] R13: 7fa507ea069e R14: 7fa50572fe1e R15: 
7fa4916e03c0
  [30045.147975] Code: ff ff ff 4c 89 e7 e8 86 a2 f8 ff e9 3c ff ff ff 85 d2 0f 
84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1

[Kernel-packages] [Bug 1684260] [NEW] kernel error (hardly reproducible)

2017-04-19 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

I was doing too many things when this error occured, so I'm not able to
report accurately. This happened just once for me on otherwise stable
system.

Kubuntu Zesty
Linux peltan 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:26 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
firefox/zesty-updates,zesty-security,now 52.0.1+build2-0ubuntu1 amd64 

I remember to run ~10 applications; in Firefox, i clicked on a link to
PDF, opening a PDF js viewer, then i closed the tab, then reopened the
tab again and before the PDF loaded up back, i clicked on Back button.
At that moment, Firefox freezed up. I switched to other applications,
they worked normally, including HDD access. An exception: in terminal,
`htop` was not able to load. I looked into dmesg output and found what
is pasted below. After some time (1-2 minutes), all the applications
started freezing up, probably when requesting hard disk I/O. No other
option that hard-reboot the computer.

Please tell me what other gatherable information shall i append.

[30045.147014] [ cut here ]
[30045.147036] kernel BUG at 
/build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129!
[30045.147059] invalid opcode:  [#1] SMP
[30045.147071] Modules linked in: mmc_block rfcomm snd_hrtimer cmac bnep 
binfmt_misc nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc snd_hda_codec_hdmi 
snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core dell_led snd_soc_sst_match 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine btusb snd_hda_intel btrtl snd_hda_codec arc4 snd_hda_core 
dell_wmi snd_hwdep sparse_keymap snd_pcm intel_rapl x86_pkg_temp_thermal 
snd_seq_midi snd_seq_midi_event intel_powerclamp coretemp snd_rawmidi kvm_intel 
dell_laptop dell_smbios dcdbas dell_smm_hwmon kvm irqbypass crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel snd_seq pcbc iwlmvm mac80211 snd_seq_device 
snd_timer aesni_intel aes_x86_64 crypto_simd glue_helper cryptd iwlwifi 
intel_cstate intel_rapl_perf snd cfg80211 rtsx_pci_ms
[30045.147259]  input_leds serio_raw memstick soundcore mei_me mei shpchp 
processor_thermal_device intel_pch_thermal intel_soc_dts_iosf hci_uart btbcm 
btqca btintel bluetooth dell_smo8800 intel_lpss_acpi intel_lpss int3400_thermal 
int3403_thermal acpi_thermal_rel int340x_thermal_zone acpi_pad dell_rbtn 
acpi_als kfifo_buf industrialio joydev mac_hid parport_pc ppdev lp parport 
ip_tables x_tables autofs4 hid_generic usbhid rtsx_pci_sdmmc i915 i2c_algo_bit 
drm_kms_helper e1000e psmouse syscopyarea sysfillrect sysimgblt ptp fb_sys_fops 
pps_core drm ahci rtsx_pci libahci wmi video i2c_hid pinctrl_sunrisepoint hid 
pinctrl_intel fjes
[30045.147411] CPU: 0 PID: 1931 Comm: firefox Not tainted 4.10.0-14-generic 
#16-Ubuntu
[30045.147431] Hardware name: Dell Inc. Latitude E5470/0P88J9, BIOS 1.7.3 
06/15/2016
[30045.147452] task: 8adb5c64ae00 task.stack: a2b7827e4000
[30045.147471] RIP: 0010:__migration_entry_wait+0x16a/0x180
[30045.147489] RSP: :a2b7827e7d68 EFLAGS: 00010246
[30045.147509] RAX: 000fc0048078 RBX: cbe1456726b0 RCX: cbe1456726b0
[30045.147537] RDX: 0001 RSI: 8adad9c9aad8 RDI: cbe1408ad6c0
[30045.147562] RBP: a2b7827e7d80 R08: 8adbc00f26c0 R09: 8adbc00f26c0
[30045.147588] R10: 7fa514f00220 R11: 7fa4b8b01640 R12: cbe1408ad6c0
[30045.147617] R13: 3e022b5b R14: a2b7827e7e30 R15: 8adbbf0f67d0
[30045.147644] FS:  7fa5162b5740() GS:8adbcdc0() 
knlGS:
[30045.147684] CS:  0010 DS:  ES:  CR0: 80050033
[30045.147710] CR2: 7fa4d455be28 CR3: 00023eb3c000 CR4: 003406f0
[30045.147737] Call Trace:
[30045.147758]  migration_entry_wait+0x74/0x80
[30045.147780]  do_swap_page+0x5b3/0x770
[30045.147792]  handle_mm_fault+0x873/0x1360
[30045.147806]  __do_page_fault+0x23e/0x4e0
[30045.147819]  do_page_fault+0x22/0x30
[30045.147832]  page_fault+0x28/0x30
[30045.147843] RIP: 0033:0x7fa50572bbaa
[30045.147854] RSP: 002b:7ffcbbbe2450 EFLAGS: 00010202
[30045.147869] RAX: 7fa4d455be20 RBX: 7fa4d455be20 RCX: 0003
[30045.147888] RDX: 7fa49e681600 RSI:  RDI: 7fa514f00040
[30045.147907] RBP:  R08:  R09: 7fa514f00220
[30045.147927] R10: 7fa514f00220 R11: 7fa4b8b01640 R12: 7fa4b645b480
[30045.147948] R13: 7fa507ea069e R14: 7fa50572fe1e R15: 7fa4916e03c0
[30045.147975] Code: ff ff ff 4c 89 e7 e8 86 a2 f8 ff e9 3c ff ff ff 85 d2 0f 
84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 
4c 89 e7 e8 1c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 1b eb 
[30045.148057] RIP: __migration_entry_wait+0x16a/0x180 RSP: a2b7827e7d68
[30045.155713] ---[ end trace 2317e1f2c5ec0c95 ]---

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


** Tags: bot-comment
-- 
kernel error (hardly reproducible)

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

2017-04-19 Thread Fabian Grünbichler

CVE requested, will include once I get a reply.

Note that Canonical is listed as CNA for "Ubuntu/Linux issues" at
http://cve.mitre.org/cve/cna.html - maybe that list needs an update
then?

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev=149200746116365
  2: http://marc.info/?l=linux-netdev=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:38

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

2017-04-19 Thread Chris Hermansen

@Joseph Salisbury,

Running the same test on 4.10.11-041011-generic did not wedge the
system.

This was the test:

for t in 1 2 3 4 5 6 7 8 9 10; do echo iter $t; stress -c 2 -m 2 -t 60;
dmesg; done

So I'm leaving this running for awhile and will report back.

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

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

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

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

  Relevant dmesg attached (dmesg_crash.txt).

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

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

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

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

Thanks for testing, Chris.  Lets see if other folks hit this bug running
4.10.0-8.  It might be that there are multiple bugs being hit here.

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

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

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

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

  Relevant dmesg attached (dmesg_crash.txt).

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

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

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

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

2017-04-19 Thread Seth Arnold

Hi Fabian, Ubuntu is currently not assigning CVE numbers; MITRE can be
best contacted at https://cveform.mitre.org/

Thanks

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev=149200746116365
  2: http://marc.info/?l=linux-netdev=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:38 testmachine kernel: Call Trace:
  Apr 12 11:31:38 testmachine

[Kernel-packages] [Bug 1684268] 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/1684268

Title:
  Two cameras won't work together with motion

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Pinnacle analog device connected via USB to my Lenovo laptop and 
Lenovo Easy Camera installed in it.
  I'm trying to setup motion package to work with both of them. Works perfectly 
by separate, but not both at the same time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/by-path', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card2.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card2.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Wed Apr 19 22:16:19 2017
  HibernationDevice: RESUME=/dev/mapper/vmhost1--system-swap
  MachineType: LENOVO IdeaPad Y560p
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=/dev/mapper/hostname--system-root--new ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-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: 11/12/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3FCN11WW
  dmi.board.name: KL3
  dmi.board.vendor: LENOVO
  dmi.board.version: Rev 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Rev 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr3FCN11WW:bd11/12/2010:svnLENOVO:pnIdeaPadY560p:pvrRev1.0:rvnLENOVO:rnKL3:rvrRev1.0:cvnLENOVO:ct10:cvrRev1.0:
  dmi.product.name: IdeaPad Y560p
  dmi.product.version: Rev 1.0
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684268/+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 1684268] [NEW] Two cameras won't work together with motion

2017-04-19 Thread Dvbnhbq

Public bug reported:

I have a Pinnacle analog device connected via USB to my Lenovo laptop and 
Lenovo Easy Camera installed in it.
I'm trying to setup motion package to work with both of them. Works perfectly 
by separate, but not both at the same time.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-19-generic 4.10.0-19.21
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/by-path', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card2.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card2.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Date: Wed Apr 19 22:16:19 2017
HibernationDevice: RESUME=/dev/mapper/vmhost1--system-swap
MachineType: LENOVO IdeaPad Y560p
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=/dev/mapper/hostname--system-root--new ro quiet splash
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-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: 11/12/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 3FCN11WW
dmi.board.name: KL3
dmi.board.vendor: LENOVO
dmi.board.version: Rev 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Rev 1.0
dmi.modalias: 
dmi:bvnLENOVO:bvr3FCN11WW:bd11/12/2010:svnLENOVO:pnIdeaPadY560p:pvrRev1.0:rvnLENOVO:rnKL3:rvrRev1.0:cvnLENOVO:ct10:cvrRev1.0:
dmi.product.name: IdeaPad Y560p
dmi.product.version: Rev 1.0
dmi.sys.vendor: LENOVO

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


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

Title:
  Two cameras won't work together with motion

Status in linux package in Ubuntu:
  New

Bug description:
  I have a Pinnacle analog device connected via USB to my Lenovo laptop and 
Lenovo Easy Camera installed in it.
  I'm trying to setup motion package to work with both of them. Works perfectly 
by separate, but not both at the same time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/by-path', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card2.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card2.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Wed Apr 19 22:16:19 2017
  HibernationDevice:

[Kernel-packages] [Bug 1680733] onibi (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/onibi__3.13.0-117.164__2017-04-19_19-11-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/1680733

Title:
  linux: 3.13.0-117.164 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
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: 1680735
  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/1680733/+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 1682041] hainzel (amd64) - tests ran: 19, failed: 0

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/hainzel__4.4.0-74.95__2017-04-19_18-22-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- 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/1682041/+subscriptions

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

[Kernel-packages] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22

2017-04-19 Thread Seth Forshee

** Summary changed:

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

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

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

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

Bug description:
  SRU Justification

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

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

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

  ---

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22

2017-04-19 Thread Seth Forshee

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

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

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

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

Bug description:
  SRU Justification

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

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

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

  ---

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

2017-04-19 Thread Davi Dagostin

I'm on Kubuntu 17.04 and this bug persists on my Dell 7759 with bios
1.2.2. When fan is turned on never more is turned off.

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

Title:
Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
Confirmed

Bug description:
Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
be an issue with the fan control. When I first boot up the machine the
fans are off. However, after the laptop warms up under normal usage,
the fans kick on and then never shut off again. Even when the CPU
cools down to below 35c, the fans will continue to run.

If I suspend the the laptop, and then immediately wake it up again
then fans are once again off, until it warms up again. So
essentially, once the fans start they don't seem to ever shut off.

Fans seem to work normally under Windows 10. They turn on as needed,
and then turn off once the laptop cools down.

I've tried the various BIOS updates that Dell has released, without
success. I am currently running Dell's latest BIOS for this laptop
(v1.1.8)

Below is the output of lm-sensors showing the fans running when the
CPU is at a cool 35c

dell_smm-virtual-0
Adapter: Virtual device
Processor Fan: 1925 RPM
Processor Fan: 2143 RPM
CPU:+35.0°C
GPU: +1.0°C
SODIMM: +49.0°C

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/controlC0: bob1709 F pulseaudio
CurrentDesktop: Unity
Date: Wed Jul 13 19:18:45 2016
HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
InstallationDate: Installed on 2016-07-13 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Dell Inc. Inspiron 7559
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 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: No upgrade log present (probably fresh install)
dmi.bios.date: 04/17/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.8
dmi.board.name: 0H0CC0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 7559
dmi.product.version: 1.1.8
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1652815] Re: Surface Pro 4 Touch/Pen requires IPTS

2017-04-19 Thread Ben

** Description changed:

  Hardware: Microsoft Surface Pro 4, 4gb/128gb nvme drive
  
  Expected Behaviour: Pen/Touch function
  
  Actual Behaviour: Pen/Touch do not work or respond to anything
  
  Kernel/Ubuntu Versions: All
  
  Cause: Hardware requires IPTS (Intel Precision Touch & Stylus) to
  function. This is because touch processing is accelerated by the Intel
  Skylake GPU.
  
  IPTS driver can be found here: https://github.com/ipts-linux-org/ipts-
  linux-new/wiki
  
  Kernel compile under Debian with other Surface-specific patches can be
  found here: https://github.com/jimdigriz/debian-mssp4
  
  On Reddit there are some custom kernels floating around with support
  patched in:
  
https://www.reddit.com/r/SurfaceLinux/comments/4t64zt/getting_the_sp4_running_with_ubuntu_1604/
+ 
+ UPDATE: The IPTS driver needed some updates for 4.10, allegedly this is a 
working version: https://github.com/axelrtgs/linux-kernel-ipts-4.10
+ Discussion here:https://github.com/ipts-linux-org/ipts-linux-new/issues/3
+ The same person has a linux-firmware-ipts, which (again, allegedly) includes 
the firmware: https://github.com/axelrtgs/linux-firmware-ipts

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

Title:
  Surface Pro 4 Touch/Pen requires IPTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Microsoft Surface Pro 4, 4gb/128gb nvme drive

  Expected Behaviour: Pen/Touch function

  Actual Behaviour: Pen/Touch do not work or respond to anything

  Kernel/Ubuntu Versions: All

  Cause: Hardware requires IPTS (Intel Precision Touch & Stylus) to
  function. This is because touch processing is accelerated by the Intel
  Skylake GPU.

  IPTS driver can be found here: https://github.com/ipts-linux-org/ipts-
  linux-new/wiki

  Kernel compile under Debian with other Surface-specific patches can be
  found here: https://github.com/jimdigriz/debian-mssp4

  On Reddit there are some custom kernels floating around with support
  patched in:
  
https://www.reddit.com/r/SurfaceLinux/comments/4t64zt/getting_the_sp4_running_with_ubuntu_1604/

  UPDATE: The IPTS driver needed some updates for 4.10, allegedly this is a 
working version: https://github.com/axelrtgs/linux-kernel-ipts-4.10
  Discussion here:https://github.com/ipts-linux-org/ipts-linux-new/issues/3
  The same person has a linux-firmware-ipts, which (again, allegedly) includes 
the firmware: https://github.com/axelrtgs/linux-firmware-ipts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652815/+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 1671611] Re: USB wi-fi dongles not working with latest updates

2017-04-19 Thread Don Cady

So with that rtl8192 dongle, it crashes/freezes/locks up?
See bug #1666421 , this is a possible duplicate.

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

Title:
  USB wi-fi dongles not working with latest updates

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Same laptop - two different network dongles (ASUS USB-N13 + Edimax
  cheap commonly used with RaspPis). Confirmed issue with xenial-updates
  and xenial-security versions. Going to try to force a downgrade to
  original xenial to see if it still happens.

  ASUS dongle -> $ inxi -Fxxrzc0 | pastebin
  https://gist.github.com/d926d05c2bd23226a9f4b4a593b9de65

  Edimax dongle -> $ inxi -Fxxrzc0 | pastebin
  https://gist.github.com/f76284151c225ae43af82de8439efe02

  
  They work fine w/ the 18.1 Installer/Live Boot.. They worked fine after the 
install.. when I did the latest update they broke. 

  uname -a ->  Linux thinkpad 4.8.0-41-generic #44~16.04.1-Ubuntu SMP
  Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -rd
  Description:  Linux Mint 18.1 Serena
  Release:  18.1

  kern.log paste:

  
  Mar  9 12:11:17 thinkpad kernel: [  244.854264] usb 1-2: USB disconnect, 
device number 4
  Mar  9 12:11:17 thinkpad kernel: [  244.864634] wlx2c4d5406c9c1: 
deauthenticating from 58:6d:8f:8e:02:5d by local choice (Reason: 
3=DEAUTH_LEAVING)
  Mar  9 12:11:17 thinkpad kernel: [  244.864846] rtl_usb: reg 0x102, 
usbctrl_vendorreq TimeOut! status:0xffed value=0xf00069ce
  Mar  9 12:11:17 thinkpad kernel: [  244.864858] rtl_usb: reg 0x422, 
usbctrl_vendorreq TimeOut! status:0xffed value=0x69543424
  Mar  9 12:11:17 thinkpad kernel: [  244.864866] rtl_usb: reg 0x542, 
usbctrl_vendorreq TimeOut! status:0xffed value=0x69543424
  Mar  9 12:11:17 thinkpad kernel: [  244.864879] rtl_usb: reg 0x1cc, 
usbctrl_vendorreq TimeOut! status:0xffed value=0x1950812
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3310] 
sup-iface[0xa2d380,wlx2c4d5406c9c1]: connection disconnected (reason -3)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3318] 
device (wlx2c4d5406c9c1): state change: activated -> unmanaged (reason 
'removed') [100 10 36]
  Mar  9 12:11:17 thinkpad kernel: [  244.899266] cfg80211: World regulatory 
domain updated:
  Mar  9 12:11:17 thinkpad kernel: [  244.899273] cfg80211:  DFS Master region: 
unset
  Mar  9 12:11:17 thinkpad kernel: [  244.899275] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Mar  9 12:11:17 thinkpad kernel: [  244.899280] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899283] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899286] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899290] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899295] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Mar  9 12:11:17 thinkpad kernel: [  244.899298] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Mar  9 12:11:17 thinkpad kernel: [  244.899301] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899304] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3642] dhcp4 
(wlx2c4d5406c9c1): canceled DHCP transaction, DHCP client pid 2225
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3643] dhcp4 
(wlx2c4d5406c9c1): state changed bound -> done
  Mar  9 12:11:17 thinkpad NetworkManager[989]:  [1489083077.3703] 
platform-linux: do-change-link[2]: failure changing link: failure 19 (No such 
device)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:  [1489083077.3705] 
platform-linux: do-change-link[2]: failure changing link: failure 19 (No such 
device)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3708] 
dns-mgr: Writing DNS information to /sbin/resolvconf
  Mar  9 12:11:17 thinkpad NetworkManager[989]:  [1489083077.3879] 
platform-linux: do-change-link[2]: failure changing link: failure 19 (No such 
device)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3879] 
device (wlx2c4d5406c9c1): failed to disable userspace IPv6LL address handling
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3880] radio 
killswitch 
/sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/ieee80211/phy0/rfkill0 
disappeared
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3882]

[Kernel-packages] [Bug 1291969] Re: No usb on resume from suspend

2017-04-19 Thread Christophe H

Hello

Upgraded  17.04 and it is corrected for 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/1291969

Title:
  No usb on resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My XPS13 running 14.04 sometimes loses its USB ports after resume from
  suspend. When this happens the entire bus seems dead - both external
  ports do not work, and internal USB devices (webcam, touchscreen) are
  also non-functional. Furthermore lsusb shows no devices attached.
  Rebooting or performing another suspend/resume cycle will clear the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-17-generic 3.13.0-17.37
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  steve  2868 F pulseaudio
   /dev/snd/controlC0:  steve  2868 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 13 08:36:46 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=79084358-087f-4cee-a0be-e2f78361873f
  InstallationDate: Installed on 2013-12-02 (100 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic 
root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (28 days ago)
  dmi.bios.date: 11/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291969/+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 1680733] onibi (i386) - tests ran: 2, failed: 0

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/onibi__3.13.0-117.164__2017-04-19_18-17-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/1680733

Title:
  linux: 3.13.0-117.164 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
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: 1680735
  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/1680733/+subscriptions

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

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

2017-04-19 Thread Chris Hermansen

@Joseph Salisbury my computer, running 4.10.0-8, hung just now (display
frozen etc).  I was running "stress".  This is similar to what happened
previously with respect to this bug, but there seems to be nothing but a
bunch of nulls in syslog this time.  Not sure how to determine whether
the same bug was actividated or not... any thoughts?

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

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

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

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

  Relevant dmesg attached (dmesg_crash.txt).

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

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

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

[Kernel-packages] [Bug 1683865] Re: Intermittent complete system freeze

apport information

** Tags added: apport-collected zesty

** Description changed:

- This happens after the upgrade to 17.04. Every 30-40 minutes or so the
- entire system hangs up. I cannot switch to console, sysrq keys REISUB
- don't reboot the machine. I am attaching the trace written up in
- /var/log/syslog.
+ This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
+ --- 
+ ApportVersion: 2.20.4-0ubuntu4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  andrej 1789 F pulseaudio
+  /dev/snd/controlC0:  andrej 1789 F pulseaudio
+ CurrentDesktop: Unity:Unity7
+ DistroRelease: Ubuntu 17.04
+ HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
+ InstallationDate: Installed on 2016-04-26 (358 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
+ MachineType: Hewlett-Packard HP EliteBook 8570w
+ Package: linux (not installed)
+ ProcFB: 0 nouveaufb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
+ RelatedPackageVersions:
+  linux-restricted-modules-4.10.0-19-generic N/A
+  linux-backports-modules-4.10.0-19-generic  N/A
+  linux-firmware 1.164
+ Tags:  zesty
+ Uname: Linux 4.10.0-19-generic x86_64
+ UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/31/2013
+ dmi.bios.vendor: Hewlett-Packard
+ dmi.bios.version: 68IAV Ver. F.40
+ dmi.board.name: 176B
+ dmi.board.vendor: Hewlett-Packard
+ dmi.board.version: KBC Version 50.1A
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Hewlett-Packard
+ dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
+ dmi.product.name: HP EliteBook 8570w
+ dmi.product.version: A1029D1103
+ dmi.sys.vendor: Hewlett-Packard

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1683865/+attachment/4865000/+files/AlsaInfo.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1683865] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1683865/+attachment/4865013/+files/RfKill.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1683865/+attachment/4865003/+files/IwConfig.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1683865/+attachment/4865015/+files/WifiSyslog.txt

** 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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1683865/+attachment/4865001/+files/CRDA.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1683865/+attachment/4865004/+files/JournalErrors.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1683865/+attachment/4865014/+files/UdevDb.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1683865/+attachment/4865006/+files/Lsusb.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1683865/+attachment/4865008/+files/ProcCpuinfoMinimal.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1683865/+attachment/4865005/+files/Lspci.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1683865/+attachment/4865009/+files/ProcEnviron.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1683865/+attachment/4865011/+files/ProcModules.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1683865/+attachment/4865012/+files/PulseList.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1683865/+attachment/4865010/+files/ProcInterrupts.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1683865/+attachment/4865002/+files/CurrentDmesg.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1683865/+attachment/4865007/+files/ProcCpuinfo.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/1683865

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the entire 
system hangs up. I cannot switch to console, sysrq keys REISUB don't reboot the 
machine. I am attaching the trace written up in /var/log/syslog.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrej 1789 F pulseaudio
   /dev/snd/controlC0:  andrej 1789 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=9b3234e2-3997-43f2-a4f2-4a558667eaf1
  InstallationDate: Installed on 2016-04-26 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=4567f091-ead1-4fb0-ac74-e21623275641 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.40
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1103:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683865/+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 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

Hm, I don't think you will win much here. vlans made from a bond have
addr_assign_type 3.

root@xnox-iad-16:/sys/class/net# uname -r
4.8.0-46-generic

root@xnox-iad-16:/sys/class/net# grep -e 0 -e 1 -e 2 -e 3 */addr_assign_type
bond0.101/addr_assign_type:3
bond0.401/addr_assign_type:3
bond0/addr_assign_type:2
ens9f0/addr_assign_type:3
ens9f1/addr_assign_type:3
lo/addr_assign_type:0

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

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.7+ kernels.

  [Other Info]

   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into
  v4.4 kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs

  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.

  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
  to the MAC of the physical interface and thus for DAD to behave as
  expected.

  Signed-off-by: Mike Manning 
  Signed-off-by: David S. Miller 

   * Original bug report

  When attempting to verify sru for bug 1669860, I found that vlans
  are not properly filtered out by 'get_interfaces_by_mac'.  That means
  that the bug is still present with vlans.

  The reason for this is that /sys/class/net//addr_assign_type
  shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8.
  See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
  for doc on addr_assign_type.

  Related bugs:
   * bug 1669860: cloud-init attempts to rename bonds

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1682871/+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 1680390] Re: Ubuntu17.04: Kernel Oops: Exception in kernel mode, sig: 5 [#1] during Avocado KVM Test runs [Regression]

2017-04-19 Thread kiney

** This bug is no longer a duplicate of bug 1674838
   kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

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

Title:
  Ubuntu17.04: Kernel Oops: Exception in kernel mode, sig: 5 [#1] during
  Avocado KVM Test runs [Regression]

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2017-03-27 
12:30:45 ==
  ---Problem Description---
  Kernel hit with oops while running avocado(kvm) tests "Oops: Exception in 
kernel mode, sig: 5 [#1]"
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  Linux ltc-test-ci1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = power 8 ppc64le 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Run Avocado(kvm) tests
  #git clone git://git.linux.ibm.com/ltc-test/avocado-fvt-wrapper.git;cd 
avocado-fvt-wrapper
  #python avocado-setup.py --bootstrap --run-suite guest_cpu --guest-os 
Ubuntu.16.04.2.ppc64le --only-filter virtio_scsi virtio_net qcow2

  2. After sometime the below mentioned traces were seen.
   
  Stack trace output:
   [20751.909458] [ cut here ]
  [20751.909461] kernel BUG at 
/build/linux-HLNhAK/linux-4.10.0/include/linux/swapops.h:129!
  [20751.909542] Oops: Exception in kernel mode, sig: 5 [#1]
  [20751.909549] SMP NR_CPUS=2048 
  [20751.909549] NUMA 
  [20751.909555] PowerNV
  [20751.909583] Modules linked in: vhost_net macvtap macvlan xt_CHECKSUM 
ipt_MASQUERADE nf_nat_masquerade_ipv4 kvm_hv kvm_pr kvm tcm_fc libfc usb_f_tcm 
tcm_usb_gadget libcomposite udc_core tcm_qla2xxx qla2xxx scsi_transport_fc 
ib_srpt iscsi_target_mod tcm_loop vhost_scsi vhost target_core_user 
target_core_file target_core_iblock target_core_pscsi target_core_mod 
ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6t_REJECT nf_reject_ipv6 xt_conntrack 
ip6t_rpfilter ip_set nfnetlink ebtable_broute bridge stp llc ebtable_nat 
ip6table_security ip6table_mangle ip6table_raw ip6table_nat iptable_security 
iptable_mangle iptable_raw iptable_nat ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter openvswitch nf_conntrack_ipv6 nf_nat_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack
  [20751.910225]  binfmt_misc powernv_rng powernv_op_panel ipmi_powernv 
ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio leds_powernv vmx_crypto 
ib_iser rdma_cm iw_cm ib_cm ib_core nfsd auth_rpcgss nfs_acl lockd grace 
configfs iscsi_tcp libiscsi_tcp sunrpc 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 ses 
enclosure scsi_transport_sas crc32c_vpmsum tg3 ipr
  [20751.910629] CPU: 24 PID: 6926 Comm: CPU 24/KVM Not tainted 
4.10.0-14-generic #16-Ubuntu
  [20751.910700] task: c007b29ac000 task.stack: c007f07b8000
  [20751.910759] NIP: c030d748 LR: c030d658 CTR: 

  [20751.910828] REGS: c007f07bb3b0 TRAP: 0700   Not tainted  
(4.10.0-14-generic)
  [20751.910897] MSR: 90029033 
  [20751.910903]   CR: 44882882  XER: 
  [20751.910984] CFAR: c030d884 SOFTE: 1 
 GPR00: c030d658 c007f07bb630 c144c900 
f1f9f1f0 
 GPR04: c007e7c7e0e0 f1f9f1f0 1f001c61 
611c001f 
 GPR08: c15bc900 0001 0001 
00e0c7e7 
 GPR12: 2200 cfb8d800  
0007fe1d 
 GPR16: 0001 3fff121c  
8800 
 GPR20: 2000 8800 2200 
c499 
 GPR24: c15be3d8 c007f05d3700 c007b972c030 
 
 GPR28: c007f07bb710 3e0d611c f3584700 
f1f9f1f0 
  [20751.911580] NIP [c030d748] __migration_entry_wait+0x128/0x2a0
  [20751.911639] LR [c030d658] __migration_entry_wait+0x38/0x2a0
  [20751.911697] Call Trace:
  [20751.911722] [c007f07bb630] [c030d658] 
__migration_entry_wait+0x38/0x2a0 (unreliable)
  [20751.911807] [c007f07bb670] [c02bbc6c] do_swap_page+0x73c/0x9a0
  [20751.911866] [c007f07bb6f0] [c02bfa98] 
handle_mm_fault+0xac8/0x1600
  [20751.911937] [c007f07bb7e0] [c02b4104] 
__get_user_pages+0x194/0x4e0
  [20751.912008] [c007f07bb890] [c02b47e4] 
get_user_pages_unlocked+0xf4/0x280
  [20751.912079] [c007f07bb930] [c02b59ac] 
get_user_pages_fast+0xac/0x100
  [20751.912152] [c007f07bb980] [df66ca74]

[Kernel-packages] [Bug 1682047] Re: linux-aws: 4.4.0-1015.24 -proposed tracker

2017-04-19 Thread Stefan Bader

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Invalid

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

Title:
  linux-aws: 4.4.0-1015.24 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 promote-to-proposed series:
  Incomplete
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682047/+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 1683865] Missing required logs.

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

apport-collect 1683865

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

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the
  entire system hangs up. I cannot switch to console, sysrq keys REISUB
  don't reboot the machine. I am attaching the trace written up in
  /var/log/syslog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683865/+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 1545330] Re: [wily][regression] systemtap script compilation broken by new kernels

2017-04-19 Thread Rafael David Tinoco

https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1683876

Similar problem appears whenever there is a new HWE kernel (specially
for LTS versions).

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

Title:
  [wily][regression] systemtap script compilation broken by new kernels

Status in linux package in Ubuntu:
  Fix Released
Status in systemtap package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in systemtap source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Fix Released
Status in systemtap source package in Xenial:
  Fix Released
Status in systemtap package in Fedora:
  Unknown

Bug description:
  The following errors appear when compiling any systemtap script:

  In file included from include/linux/mutex.h:15:0,
   from 
/tmp/stapbdpxn3/stap_a0ec17f995e8f89d672d8c2eb7fe7c24_1693_src.c:25:
  include/linux/spinlock_types.h:55:14: error: ‘__ARCH_SPIN_LOCK_UNLOCKED’ 
undeclared here (not in a function)
    .raw_lock = __ARCH_SPIN_LOCK_UNLOCKED, \
    ^
  include/linux/spinlock_types.h:79:15: note: in expansion of macro 
‘__RAW_SPIN_LOCK_INITIALIZER’
    { { .rlock = __RAW_SPIN_LOCK_INITIALIZER(lockname) } }
     ^
  include/linux/spinlock_types.h:82:16: note: in expansion of macro 
‘__SPIN_LOCK_INITIALIZER’
    (spinlock_t ) __SPIN_LOCK_INITIALIZER(lockname)
  ^
  include/linux/mutex.h:111:18: note: in expansion of macro 
‘__SPIN_LOCK_UNLOCKED’
     , .wait_lock = __SPIN_LOCK_UNLOCKED(lockname.wait_lock) \
    ^
  include/linux/mutex.h:117:27: note: in expansion of macro 
‘__MUTEX_INITIALIZER’
    struct mutex mutexname = __MUTEX_INITIALIZER(mutexname)

  Upstream fix:
  
https://www.sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=320e1ecb16427b5769f0f5a097d80823ee1fb765

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1545330/+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 1611078] Re: Support snaps inside of lxd containers

2017-04-19 Thread Stéphane Graber

No, the solution is that snapd shouldn't assume that /lib/modules exist
and just not attempt to bind-mount it if it's missing.

Systems that don't have kernels installed (like containers) shouldn't
have /lib/modules at all.

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1611078/+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 1624540] Re: please have lxd recommend zfs

2017-04-19 Thread Stéphane Graber

Colin: This is not what this issue is about.

This issue is about getting the ZFS tools installed by default in server
images, with the problem that doing so now would result in zfs-zed
running all the time for everyone, regardless of whether they use ZFS or
not.

What we want is:
 - Don't load the module by default (as it taints the kernel)
 - Use of ZFS tools should automatically load the kernel module
 - zfs-zed should only start when one or more zpool has been imported

With those done, we'll be able to ship the zfs tools in all Ubuntu
installs without negatively affecting users.

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

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

Title:
  please have lxd recommend zfs

Status in lxd package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  Since ZFS is now in Main (Bug #1532198), LXD should recommend the ZFS
  userspace package, such that 'sudo lxd init' just works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1624540/+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 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

The cloud init patch needs work...

>>> interface_has_own_mac('bonding_masters')
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/cloudinit/net/__init__.py", line 226, in 
interface_has_own_mac
uevent = read_sys_net_safe(ifname, 'uevent').splitlines()
AttributeError: 'bool' object has no attribute 'splitlines'

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

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.7+ kernels.

  [Other Info]

   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into
  v4.4 kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs

  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.

  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
  to the MAC of the physical interface and thus for DAD to behave as
  expected.

  Signed-off-by: Mike Manning 
  Signed-off-by: David S. Miller 

   * Original bug report

  When attempting to verify sru for bug 1669860, I found that vlans
  are not properly filtered out by 'get_interfaces_by_mac'.  That means
  that the bug is still present with vlans.

  The reason for this is that /sys/class/net//addr_assign_type
  shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8.
  See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
  for doc on addr_assign_type.

  Related bugs:
   * bug 1669860: cloud-init attempts to rename bonds

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1682871/+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 1683865] Re: Intermittent complete system freeze

I have several kdump crash logs that I can share. They are $100MB each
so I don't know what the best way might be, and the traces are similar
to the trace I already uploaded.

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Intermittent complete system freeze

Status in linux package in Ubuntu:
  New

Bug description:
  This happens after the upgrade to 17.04. Every 30-40 minutes or so the
  entire system hangs up. I cannot switch to console, sysrq keys REISUB
  don't reboot the machine. I am attaching the trace written up in
  /var/log/syslog.

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

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

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

Title:
  linux: 3.13.0-117.164 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
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: 1680735
  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/1680733/+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 1682034] Re: linux: 4.8.0-48.51 -proposed tracker

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

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

Title:
  linux: 4.8.0-48.51 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

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

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

  backports: 1682037
  derivatives: 1682038
  -- 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/1682034/+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 1684120] Missing required logs.

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

apport-collect 1684120

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

Title:
  Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0
  20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun
  Feb 5 09:39:57 UTC 2017 (Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11)
  Will intermittent crash when connect to above 2 USB device and reset
  USB device-Mobile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Clean installed with Ubuntu 16.04.02 TLS Desktop 64bit
  We used some desktop computer to test the android mobile phone. Link to PC 
through USB Type-C and Micro USB.
  We set an APK file to let mobile auto mount/dismount around 1 time/minutes.
  Kernel will intermittent crash, Even test from 16.04.01 LTS same as well.
  Seek your advise if any kernel upgrade or idea can resolve this issue.How to 
create the trace log for deep analysis if need?
  I have attach the log file for your reference, Thanks very much!!

  Kernel info:
  Apr 17 16:17:00 SH-11F3-A10-0605 kernel: [0.00] Linux version 
4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 
5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 
(Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11)
  Apr 17 16:17:00 SH-11F3-A10-0605 kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic.efi.signed 
root=UUID=4e264b55-dafb-4b87-9c25-6902e5f54272 ro quiet splash vt.handoff=7

  Log as below:
  Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.235348] scsi 1506:0:0:0: 
CD-ROMLinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
  Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.236703] sr 1506:0:0:0: [sr2] 
scsi-1 drive Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.237193] sr 
1506:0:0:0: Attached scsi CD-ROM sr2 Apr 14 21:15:51 SH-11F3-A10-0401 kernel: 
[13702.237436] sr 1506:0:0:0: Attached scsi generic sg3 type 5 Apr 14 21:15:51 
SH-11F3-A10-0401 kernel: [13702.286619] usb 1-3: new high-speed USB device 
number 120 using xhci_hcd Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.415975] usb 1-3: New USB device found, idVendor=12d1, idProduct=107e Apr 
14 21:15:52 SH-11F3-A10-0401 kernel: [13702.415982] usb 1-3: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3 Apr 14 21:15:52 SH-11F3-A10-0401 
kernel: [13702.415987] usb 1-3: Product: HUAWEI Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.415990] usb 1-3: Manufacturer: unknown Apr 14 
21:15:52 SH-11F3-A10-0401 kernel: [13702.415993] usb 1-3: SerialNumber: 
K4Q011642205 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.417894] 
usb-storage 1-3:1.3: USB Mass 
 Storage device detected Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.418103] scsi host1507: usb-storage 1-3:1.3 Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.838577] usb 1-7: new high-speed USB device 
number 121 using xhci_hcd Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.967820] usb 1-7: New USB device found, idVendor=12d1, idProduct=107e Apr 
14 21:15:52 SH-11F3-A10-0401 kernel: [13702.967829] usb 1-7: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3 Apr 14 21:15:52 SH-11F3-A10-0401 
kernel: [13702.967833] usb 1-7: Product: HUAWEI Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.967837] usb 1-7: Manufacturer: unknown Apr 14 
21:15:52 SH-11F3-A10-0401 kernel: [13702.967841] usb 1-7: SerialNumber: 
R3E011611771 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.969529] 
usb-storage 1-7:1.3: USB Mass Storage device detected Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.969724] scsi host1508: usb-storage 1-7:1.3
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.415340] scsi 1507:0:0:0: 
CD-ROMLinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.416594] sr 1507:0:0:0: [sr3] 
scsi-1 drive Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.417121] sr 
1507:0:0:0: Attached scsi CD-ROM sr3 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: 
[13703.417352] sr 1507:0:0:0: Attached scsi generic sg4 type 5
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.967196] scsi 1508:0:0:0: 
CD-ROMLinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.968605] sr 1508:0:0:0: [sr4] 
scsi-1 drive Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.969154] sr 
1508:0:0:0: Attached scsi CD-ROM sr4 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: 
[13703.969358]

[Kernel-packages] [Bug 1683865] [NEW] Intermittent complete system freeze

2017-04-19 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

This happens after the upgrade to 17.04. Every 30-40 minutes or so the
entire system hangs up. I cannot switch to console, sysrq keys REISUB
don't reboot the machine. I am attaching the trace written up in
/var/log/syslog.

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


** Tags: bot-comment
-- 
Intermittent complete system freeze
https://bugs.launchpad.net/bugs/1683865
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

** Patch added: "vlans-steal-mac-addresses.patch"
   
https://bugs.launchpad.net/cloud-init/+bug/1682871/+attachment/4864966/+files/vlans-steal-mac-addresses.patch

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

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.7+ kernels.

  [Other Info]

   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into
  v4.4 kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs

  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.

  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
  to the MAC of the physical interface and thus for DAD to behave as
  expected.

  Signed-off-by: Mike Manning 
  Signed-off-by: David S. Miller 

   * Original bug report

  When attempting to verify sru for bug 1669860, I found that vlans
  are not properly filtered out by 'get_interfaces_by_mac'.  That means
  that the bug is still present with vlans.

  The reason for this is that /sys/class/net//addr_assign_type
  shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8.
  See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
  for doc on addr_assign_type.

  Related bugs:
   * bug 1669860: cloud-init attempts to rename bonds

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1682871/+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 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

2017-04-19 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.7+ kernels.

  [Other Info]

   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into
  v4.4 kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs

  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.

  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
  to the MAC of the physical interface and thus for DAD to behave as
  expected.

  Signed-off-by: Mike Manning 
  Signed-off-by: David S. Miller 

   * Original bug report

  When attempting to verify sru for bug 1669860, I found that vlans
  are not properly filtered out by 'get_interfaces_by_mac'.  That means
  that the bug is still present with vlans.

  The reason for this is that /sys/class/net//addr_assign_type
  shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8.
  See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
  for doc on addr_assign_type.

  Related bugs:
   * bug 1669860: cloud-init attempts to rename bonds

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1682871/+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 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

Adding a cloud-init workaround patch for kernels before 4.7 too.

** Description changed:

  [Impact]
  
-  * When vlan interfaces are created, their mac address is copied from
+  * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.
  
-  * When underlying interface MAC address is changed, it does not
+  * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.
  
  [Test Case]
  
-  * Create vlan interface, check the addr_assign_type sysfs attribute, it
+  * Create vlan interface, check the addr_assign_type sysfs attribute, it
  should be 2, not 0.
  
-  * Update the base interface mac address, the mac address of the vlan
+  * Update the base interface mac address, the mac address of the vlan
  interface should change too.
  
  [Regression Potential]
  
-  * Userspace may rely on non-propagating MAC addresses, and the fact
+  * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however this
- behaviour will be consistent with 4.6+ kernels.
+ behaviour will be consistent with 4.7+ kernels.
  
  [Other Info]
-  
-  * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into v4.4 
kernels
+ 
+  * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into v4.4
+ kernels
  
  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100
  
- vlan: Propagate MAC address to VLANs
- 
- The MAC address of the physical interface is only copied to the VLAN
- when it is first created, resulting in an inconsistency after MAC
- address changes of only newly created VLANs having an up-to-date MAC.
- 
- The VLANs should continue inheriting the MAC address of the physical
- interface until the VLAN MAC address is explicitly set to any value.
- This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
- to the MAC of the physical interface and thus for DAD to behave as
- expected.
- 
- Signed-off-by: Mike Manning 
- Signed-off-by: David S. Miller 
+ vlan: Propagate MAC address to VLANs
  
+ The MAC address of the physical interface is only copied to the VLAN
+ when it is first created, resulting in an inconsistency after MAC
+ address changes of only newly created VLANs having an up-to-date MAC.
  
-  * Original bug report
+ The VLANs should continue inheriting the MAC address of the physical
+ interface until the VLAN MAC address is explicitly set to any value.
+ This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
+ to the MAC of the physical interface and thus for DAD to behave as
+ expected.
+ 
+ Signed-off-by: Mike Manning 
+ Signed-off-by: David S. Miller 
+ 
+  * Original bug report
  
  When attempting to verify sru for bug 1669860, I found that vlans
  are not properly filtered out by 'get_interfaces_by_mac'.  That means
  that the bug is still present with vlans.
  
  The reason for this is that /sys/class/net//addr_assign_type
  shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8.
  See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
  for doc on addr_assign_type.
  
  Related bugs:
   * bug 1669860: cloud-init attempts to rename bonds

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

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.7+ kernels.

  [Other Info]

   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into
  v4.4 kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC

[Kernel-packages] [Bug 1684120] Re: Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 (U

2017-04-19 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0
  20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun
  Feb 5 09:39:57 UTC 2017 (Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11)
  Will intermittent crash when connect to above 2 USB device and reset
  USB device-Mobile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Clean installed with Ubuntu 16.04.02 TLS Desktop 64bit
  We used some desktop computer to test the android mobile phone. Link to PC 
through USB Type-C and Micro USB.
  We set an APK file to let mobile auto mount/dismount around 1 time/minutes.
  Kernel will intermittent crash, Even test from 16.04.01 LTS same as well.
  Seek your advise if any kernel upgrade or idea can resolve this issue.How to 
create the trace log for deep analysis if need?
  I have attach the log file for your reference, Thanks very much!!

  Kernel info:
  Apr 17 16:17:00 SH-11F3-A10-0605 kernel: [0.00] Linux version 
4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 
5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 
(Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11)
  Apr 17 16:17:00 SH-11F3-A10-0605 kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic.efi.signed 
root=UUID=4e264b55-dafb-4b87-9c25-6902e5f54272 ro quiet splash vt.handoff=7

  Log as below:
  Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.235348] scsi 1506:0:0:0: 
CD-ROMLinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
  Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.236703] sr 1506:0:0:0: [sr2] 
scsi-1 drive Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.237193] sr 
1506:0:0:0: Attached scsi CD-ROM sr2 Apr 14 21:15:51 SH-11F3-A10-0401 kernel: 
[13702.237436] sr 1506:0:0:0: Attached scsi generic sg3 type 5 Apr 14 21:15:51 
SH-11F3-A10-0401 kernel: [13702.286619] usb 1-3: new high-speed USB device 
number 120 using xhci_hcd Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.415975] usb 1-3: New USB device found, idVendor=12d1, idProduct=107e Apr 
14 21:15:52 SH-11F3-A10-0401 kernel: [13702.415982] usb 1-3: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3 Apr 14 21:15:52 SH-11F3-A10-0401 
kernel: [13702.415987] usb 1-3: Product: HUAWEI Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.415990] usb 1-3: Manufacturer: unknown Apr 14 
21:15:52 SH-11F3-A10-0401 kernel: [13702.415993] usb 1-3: SerialNumber: 
K4Q011642205 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.417894] 
usb-storage 1-3:1.3: USB Mass 
 Storage device detected Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.418103] scsi host1507: usb-storage 1-3:1.3 Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.838577] usb 1-7: new high-speed USB device 
number 121 using xhci_hcd Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.967820] usb 1-7: New USB device found, idVendor=12d1, idProduct=107e Apr 
14 21:15:52 SH-11F3-A10-0401 kernel: [13702.967829] usb 1-7: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3 Apr 14 21:15:52 SH-11F3-A10-0401 
kernel: [13702.967833] usb 1-7: Product: HUAWEI Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.967837] usb 1-7: Manufacturer: unknown Apr 14 
21:15:52 SH-11F3-A10-0401 kernel: [13702.967841] usb 1-7: SerialNumber: 
R3E011611771 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.969529] 
usb-storage 1-7:1.3: USB Mass Storage device detected Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.969724] scsi host1508: usb-storage 1-7:1.3
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.415340] scsi 1507:0:0:0: 
CD-ROMLinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.416594] sr 1507:0:0:0: [sr3] 
scsi-1 drive Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.417121] sr 
1507:0:0:0: Attached scsi CD-ROM sr3 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: 
[13703.417352] sr 1507:0:0:0: Attached scsi generic sg4 type 5
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.967196] scsi 1508:0:0:0: 
CD-ROMLinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.968605] sr 1508:0:0:0: [sr4] 
scsi-1 drive Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.969154] sr 
1508:0:0:0: Attached scsi CD-ROM sr4 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: 
[13703.969358] sr 1508:0:0:0: Attached scsi generic sg5 type 5 Apr 14 21:15:53 
SH-11F3-A10-0401 kernel: [13704.120986] usb 1-1: USB disconnect, device number 
117

[Kernel-packages] [Bug 1684120] Re: Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 (U

2017-04-19 Thread Colin Watson

** Project changed: launchpad => linux (Ubuntu)

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

Title:
  Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0
  20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun
  Feb 5 09:39:57 UTC 2017 (Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11)
  Will intermittent crash when connect to above 2 USB device and reset
  USB device-Mobile

Status in linux package in Ubuntu:
  New

Bug description:
  Clean installed with Ubuntu 16.04.02 TLS Desktop 64bit
  We used some desktop computer to test the android mobile phone. Link to PC 
through USB Type-C and Micro USB.
  We set an APK file to let mobile auto mount/dismount around 1 time/minutes.
  Kernel will intermittent crash, Even test from 16.04.01 LTS same as well.
  Seek your advise if any kernel upgrade or idea can resolve this issue.How to 
create the trace log for deep analysis if need?
  I have attach the log file for your reference, Thanks very much!!

  Kernel info:
  Apr 17 16:17:00 SH-11F3-A10-0605 kernel: [0.00] Linux version 
4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 
5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 
(Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11)
  Apr 17 16:17:00 SH-11F3-A10-0605 kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic.efi.signed 
root=UUID=4e264b55-dafb-4b87-9c25-6902e5f54272 ro quiet splash vt.handoff=7

  Log as below:
  Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.235348] scsi 1506:0:0:0: 
CD-ROMLinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
  Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.236703] sr 1506:0:0:0: [sr2] 
scsi-1 drive Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.237193] sr 
1506:0:0:0: Attached scsi CD-ROM sr2 Apr 14 21:15:51 SH-11F3-A10-0401 kernel: 
[13702.237436] sr 1506:0:0:0: Attached scsi generic sg3 type 5 Apr 14 21:15:51 
SH-11F3-A10-0401 kernel: [13702.286619] usb 1-3: new high-speed USB device 
number 120 using xhci_hcd Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.415975] usb 1-3: New USB device found, idVendor=12d1, idProduct=107e Apr 
14 21:15:52 SH-11F3-A10-0401 kernel: [13702.415982] usb 1-3: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3 Apr 14 21:15:52 SH-11F3-A10-0401 
kernel: [13702.415987] usb 1-3: Product: HUAWEI Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.415990] usb 1-3: Manufacturer: unknown Apr 14 
21:15:52 SH-11F3-A10-0401 kernel: [13702.415993] usb 1-3: SerialNumber: 
K4Q011642205 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.417894] 
usb-storage 1-3:1.3: USB Mass 
 Storage device detected Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.418103] scsi host1507: usb-storage 1-3:1.3 Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.838577] usb 1-7: new high-speed USB device 
number 121 using xhci_hcd Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.967820] usb 1-7: New USB device found, idVendor=12d1, idProduct=107e Apr 
14 21:15:52 SH-11F3-A10-0401 kernel: [13702.967829] usb 1-7: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3 Apr 14 21:15:52 SH-11F3-A10-0401 
kernel: [13702.967833] usb 1-7: Product: HUAWEI Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.967837] usb 1-7: Manufacturer: unknown Apr 14 
21:15:52 SH-11F3-A10-0401 kernel: [13702.967841] usb 1-7: SerialNumber: 
R3E011611771 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.969529] 
usb-storage 1-7:1.3: USB Mass Storage device detected Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.969724] scsi host1508: usb-storage 1-7:1.3
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.415340] scsi 1507:0:0:0: 
CD-ROMLinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.416594] sr 1507:0:0:0: [sr3] 
scsi-1 drive Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.417121] sr 
1507:0:0:0: Attached scsi CD-ROM sr3 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: 
[13703.417352] sr 1507:0:0:0: Attached scsi generic sg4 type 5
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.967196] scsi 1508:0:0:0: 
CD-ROMLinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
  Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.968605] sr 1508:0:0:0: [sr4] 
scsi-1 drive Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.969154] sr 
1508:0:0:0: Attached scsi CD-ROM sr4 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: 
[13703.969358] sr 1508:0:0:0: Attached scsi generic sg5 type 5 Apr 14 21:15:53 
SH-11F3-A10-0401 kernel: [13704.120986] usb 1-1: USB disconnect, device number 
117

[Kernel-packages] [Bug 1684120] [NEW] Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017

2017-04-19 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Clean installed with Ubuntu 16.04.02 TLS Desktop 64bit
We used some desktop computer to test the android mobile phone. Link to PC 
through USB Type-C and Micro USB.
We set an APK file to let mobile auto mount/dismount around 1 time/minutes.
Kernel will intermittent crash, Even test from 16.04.01 LTS same as well.
Seek your advise if any kernel upgrade or idea can resolve this issue.How to 
create the trace log for deep analysis if need?
I have attach the log file for your reference, Thanks very much!!

Kernel info:
Apr 17 16:17:00 SH-11F3-A10-0605 kernel: [0.00] Linux version 
4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 
5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 
(Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11)
Apr 17 16:17:00 SH-11F3-A10-0605 kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic.efi.signed 
root=UUID=4e264b55-dafb-4b87-9c25-6902e5f54272 ro quiet splash vt.handoff=7

Log as below:
Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.235348] scsi 1506:0:0:0: CD-ROM 
   LinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.236703] sr 1506:0:0:0: [sr2] 
scsi-1 drive Apr 14 21:15:51 SH-11F3-A10-0401 kernel: [13702.237193] sr 
1506:0:0:0: Attached scsi CD-ROM sr2 Apr 14 21:15:51 SH-11F3-A10-0401 kernel: 
[13702.237436] sr 1506:0:0:0: Attached scsi generic sg3 type 5 Apr 14 21:15:51 
SH-11F3-A10-0401 kernel: [13702.286619] usb 1-3: new high-speed USB device 
number 120 using xhci_hcd Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.415975] usb 1-3: New USB device found, idVendor=12d1, idProduct=107e Apr 
14 21:15:52 SH-11F3-A10-0401 kernel: [13702.415982] usb 1-3: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3 Apr 14 21:15:52 SH-11F3-A10-0401 
kernel: [13702.415987] usb 1-3: Product: HUAWEI Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.415990] usb 1-3: Manufacturer: unknown Apr 14 
21:15:52 SH-11F3-A10-0401 kernel: [13702.415993] usb 1-3: SerialNumber: 
K4Q011642205 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.417894] 
usb-storage 1-3:1.3: USB Mass St
 orage device detected Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.418103] 
scsi host1507: usb-storage 1-3:1.3 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.838577] usb 1-7: new high-speed USB device number 121 using xhci_hcd Apr 
14 21:15:52 SH-11F3-A10-0401 kernel: [13702.967820] usb 1-7: New USB device 
found, idVendor=12d1, idProduct=107e Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.967829] usb 1-7: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3 Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.967833] usb 1-7: 
Product: HUAWEI Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.967837] usb 
1-7: Manufacturer: unknown Apr 14 21:15:52 SH-11F3-A10-0401 kernel: 
[13702.967841] usb 1-7: SerialNumber: R3E011611771 Apr 14 21:15:52 
SH-11F3-A10-0401 kernel: [13702.969529] usb-storage 1-7:1.3: USB Mass Storage 
device detected Apr 14 21:15:52 SH-11F3-A10-0401 kernel: [13702.969724] scsi 
host1508: usb-storage 1-7:1.3
Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.415340] scsi 1507:0:0:0: CD-ROM 
   LinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.416594] sr 1507:0:0:0: [sr3] 
scsi-1 drive Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.417121] sr 
1507:0:0:0: Attached scsi CD-ROM sr3 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: 
[13703.417352] sr 1507:0:0:0: Attached scsi generic sg4 type 5
Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.967196] scsi 1508:0:0:0: CD-ROM 
   LinuxFile-CD Gadget   0401 PQ: 0 ANSI: 2
Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.968605] sr 1508:0:0:0: [sr4] 
scsi-1 drive Apr 14 21:15:53 SH-11F3-A10-0401 kernel: [13703.969154] sr 
1508:0:0:0: Attached scsi CD-ROM sr4 Apr 14 21:15:53 SH-11F3-A10-0401 kernel: 
[13703.969358] sr 1508:0:0:0: Attached scsi generic sg5 type 5 Apr 14 21:15:53 
SH-11F3-A10-0401 kernel: [13704.120986] usb 1-1: USB disconnect, device number 
117





Apr 15 10:27:43 
SH-11F3-A10-0401 kernel: [0.00] Initializing cgroup subsys cpuset
Apr 15 10:27:43 SH-11F3-A10-0401 kernel: [0.00] Initializing cgroup 
subsys cpu
Apr 15 10:27:43 SH-11F3-A10-0401 kernel: [0.00] Initializing cgroup 
subsys cpuacct
Apr 15 10:27:43 SH-11F3-A10-0401 kernel: [0.00] Linux version 
4.4.0-31-generic (buildd@lgw01-16) (gcc version 5.3.1 20160413 (Ubuntu 
5.3.1-14ubuntu2.1) )

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

2017-04-19 Thread Christian Sarrasin

Hi Joseph,

As previously reported:

4.10.0-15: affected
4.10.0-14: issue not experienced in over a week 

Obviously "not experienced" doesn't mean the bug isn't present.  All I
can say is that it was first experienced with 4.10.0-15.

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

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

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

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

  Relevant dmesg attached (dmesg_crash.txt).

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

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

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

[Kernel-packages] [Bug 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

** Description changed:

+ [Impact]
+ 
+  * When vlan interfaces are created, their mac address is copied from
+ the underlying interface, but it is not marked by kernel as stolen.
+ 
+  * When underlying interface MAC address is changed, it does not
+ propagate to the vlan interfaces.
+ 
+ [Test Case]
+ 
+  * Create vlan interface, check the addr_assign_type sysfs attribute, it
+ should be 2, not 0.
+ 
+  * Update the base interface mac address, the mac address of the vlan
+ interface should change too.
+ 
+ [Regression Potential]
+ 
+  * Userspace may rely on non-propagating MAC addresses, and the fact
+ that vlan mac address type is wrongly stated as non-stolen; however this
+ behaviour will be consistent with 4.6+ kernels.
+ 
+ [Other Info]
+  
+  * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into v4.4 
kernels
+ 
+ commit 308453aa9156a3b8ee382c0949befb507a32b0c1
+ Author: Mike Manning 
+ Date:   Fri May 27 17:45:07 2016 +0100
+ 
+ vlan: Propagate MAC address to VLANs
+ 
+ The MAC address of the physical interface is only copied to the VLAN
+ when it is first created, resulting in an inconsistency after MAC
+ address changes of only newly created VLANs having an up-to-date MAC.
+ 
+ The VLANs should continue inheriting the MAC address of the physical
+ interface until the VLAN MAC address is explicitly set to any value.
+ This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
+ to the MAC of the physical interface and thus for DAD to behave as
+ expected.
+ 
+ Signed-off-by: Mike Manning 
+ Signed-off-by: David S. Miller 
+ 
+ 
+  * Original bug report
+ 
  When attempting to verify sru for bug 1669860, I found that vlans
  are not properly filtered out by 'get_interfaces_by_mac'.  That means
  that the bug is still present with vlans.
  
  The reason for this is that /sys/class/net//addr_assign_type
  shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8.
  See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
  for doc on addr_assign_type.
  
  Related bugs:
   * bug 1669860: cloud-init attempts to rename bonds

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Canonical Kernel (canonical-kernel)

** Patch added: "0001-vlan-Propagate-MAC-address-to-VLANs.patch"
   
https://bugs.launchpad.net/cloud-init/+bug/1682871/+attachment/4864939/+files/0001-vlan-Propagate-MAC-address-to-VLANs.patch

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

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.6+ kernels.

  [Other Info]
   
   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into v4.4 
kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs
  
  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.
  
  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
  to the MAC of the physical interface and thus for DAD to behave as
  expected.
  
  Signed-off-by: Mike Manning 
  Signed-off-by: David S. Miller 

  
   * Original bug report

  When attempting to verify sru for bug 1669860, I found that vlans
  are not properly filtered out by

[Kernel-packages] [Bug 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

I wonder if this really should go to linux-stable too.

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

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.6+ kernels.

  [Other Info]
   
   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into v4.4 
kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs
  
  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.
  
  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
  to the MAC of the physical interface and thus for DAD to behave as
  expected.
  
  Signed-off-by: Mike Manning 
  Signed-off-by: David S. Miller 

  
   * Original bug report

  When attempting to verify sru for bug 1669860, I found that vlans
  are not properly filtered out by 'get_interfaces_by_mac'.  That means
  that the bug is still present with vlans.

  The reason for this is that /sys/class/net//addr_assign_type
  shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8.
  See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
  for doc on addr_assign_type.

  Related bugs:
   * bug 1669860: cloud-init attempts to rename bonds

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1682871/+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 1684213] 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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1684213

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+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 1683976] Re: Please backport fix to reference leak in cgroup blkio throttle

2017-04-19 Thread Chunwei Chen

Hi Joseph,

I just tested the Xenial one and it fixed the issue.

Thanks for the quick respond.

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

Title:
  Please backport fix to reference leak in cgroup blkio throttle

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

Bug description:
  This is fixed in Linux 4.5
  
https://github.com/torvalds/linux/commit/39a169b62b415390398291080dafe63aec751e0a

  Basically the module reference will leak whenever you write to
  /sys/fs/cgroup/blkio/blkio.throttle.*

  $ uname -a
  Linux david-kvm 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsmod | grep ^zfs
  zfs  2813952  1
  $ sudo sh -c 'i=100; while [ $i -gt 0 ]; do echo "230:0 1024" > 
/sys/fs/cgroup/blkio/blkio.throttle.read_bps_device; i=$(($i - 1)); done'
  $ lsmod | grep ^zfs
  zfs  2813952  101

  This patch should be applied to all kernel < 4.5

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683976/+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 1684213] [NEW] Intel Wireless 7260 often crashes

2017-04-19 Thread Ben

Public bug reported:

Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything
(kernel, firmware, etc.) is stock. Issue has persisted across multiple
installations.

Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
[  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
[  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
[  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
[  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
[  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
[  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
[  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

Solution: Rebooting doesn't fix the problem. Perhaps a different
firmware version will work better? Configuration settings? etc.?
Unknown.

Thanks ahead of time for the help. Let me know if there's anything you
need/commands I should run/solutions I can attempt.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-19-generic 4.10.0-19.21
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bmueller   1669 F pulseaudio
CurrentDesktop: MATE
Date: Wed Apr 19 10:34:11 2017
InstallationDate: Installed on 2017-04-13 (6 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:07dc Intel Corp.
 Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: GOOGLE Gnawty
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic  N/A
 linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
dmi.bios.date: 08/16/2015
dmi.bios.vendor: coreboot
dmi.chassis.type: 3
dmi.chassis.vendor: GOOGLE
dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
dmi.product.name: Gnawty
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE

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

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

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

** Attachment added: "Dmesg output when issue is occuring."
   
https://bugs.launchpad.net/bugs/1684213/+attachment/4864922/+files/dmesg-errors.txt

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

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
  
  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything
  (kernel, firmware, etc.) is stock. Issue has persisted across multiple
  installations.
  
- Bug: Wifi/Bluetooth crashes crashes and refuses to come back up, even
- after multiple reboots. Issue persists across distros (Arch, Ubuntu,
- etc.)
+ Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
+ multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)
  
  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: Invalid argument

** Tags removed: kernel-da-key

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

Title:
  Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC
    (8335-GTB)

   * This is a toleration change (no exploitation) for those HW releases
     following the SRU policy of "For Long Term Support releases we
     regularly want to enable new hardware. Such changes are appropriate
     provided that we can ensure not to affect upgrades on existing
     hardware."

   * Without the Fix that hardware won't run Xenial guests under current
     Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07
     compatibility mode (plus a few no-op changes as backport
     dependencies)

  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being
     affected.

  [Regression Potential]

   * I'd rate the potential to regress low for powerpc and next to 
 impossible for other architectures, reasons:
   * Changes are PPC only, so fallout should be contained to that
   * Patches and were created by IBM and in Upstream qemu since 2.6
   * The effective change is rather small, only allow to saner cpu model
 versions (drop some HW dev trash that was left) and add the new types.

  [Other Info]

   * Needed for certifying this Hardware for Ubuntu

  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3:

[Kernel-packages] [Bug 1682368] Re: refcount underflow / kernel NULL dereference after attempting to add basic tc filter

** Tags removed: kernel-da-key

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

Title:
  refcount underflow / kernel NULL dereference after attempting to add
  basic tc filter

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

Bug description:
  == SRU Justification ==

  Impact: adding a tc filter sometimes fails, potentially followed by
  kernel hangs and kernel NULL pointer dereference

  Fix: proposed upstream by Wolfgang Bumiller [1,2]

  Regression Potential: Since nobody else noticed this issue in 4.11 >=
  rc1 or Ubuntu 4.10 >= 15.17, and the fix only touches the broken code,
  the regression potential should be minimal ;)

  1: http://marc.info/?l=linux-netdev=149200746116365
  2: http://marc.info/?l=linux-netdev=149200742616349

  ---

  Commit 1045ba77a which was backported for #1674087 in
  fc0cef7a8ec1e63ee3405f642983dd86e04ab6cc (first released with
  Ubuntu-4.10.0-15.17) introduces the problematic code. Note that while
  the traces below were generated using a custom patched kernel, the
  same issue is reproducible using Ubuntu Zesty's 4.10.0-15.17 (and
  later) kernels.

  The full cover letter of the proposed fix by my colleague Wolfgang
  Bumiller follows:

  Commit 1045ba77a ("net sched actions: Add support for user cookies")
  added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
  nlattr array unconditionally, while it was otherwise used as well as
  initialized only when `name == NULL`:

if (name == NULL) {
err = nla_parse_nested(tb, TCA_ACT_MAX, nla, NULL);

  In the other case `nla` is instead passed over to ->init to be parsed
  there (using a different set of TCA_ enum values, iow. TCA_ACT_COOKIE
  then "clashes" with some other value). This lead to the following three
  example commands resulting in errors (sometimes followed by more traces
  and hangups some time later (although the hangups happened seconds or
  sometimes minutes later, sometimes not at all - results differed between
  different kernel versions (linux git-master vs ubuntu's mainline 4.11
  rc6 vs. pve 4.10.5 (based off ubuntu's zesty kernel where the commit is
  cherry-picked)...))):

   # ip link add ve0 type veth peer name ve0b
   # tc qdisc add dev ve0 handle : ingress
   # tc filter add dev ve0 parent : prio 50 basic police rate 1000bps burst 
1000b drop

  The 3rd command would sometimes succeed, sometimes error with:

   RTNETLINK answers: Invalid argument
   We have an error talking to the kernel

  and sometimes error with:

   RTNETLINK answers: Cannot allocate memory
   We have an error talking to the kernel

  In the latter case I assume `cklen` became negative, which passes the
  TC_COOKIE_MAX_SIZE check since it is signed but becomes unsigned later
  in kmemdup() (see the crash dump below)

  When the `tc filter add` command fails a backtrace shows up in dmesg,
  added below.

  I'm not sure why the TC_ACT_COOKIE code was added to tcf_action_init_1
  where it is now. It makes me think that it's supposed to be available
  universally, but the `name == NULL` check for how nla is used or passed
  to ->init() shows that the there are various different TC_ACT_* enums in
  use at this point, hence the 'RFC' part of the patches, I'm not that
  familiar with the code yet.

  Backtrace when running `tc filter add`:

  Apr 12 11:31:38 testmachine kernel: [ cut here ]
  Apr 12 11:31:38 testmachine kernel: WARNING: CPU: 7 PID: 16596 at 
mm/page_alloc.c:3541 __alloc_pages_slowpath+0x9fe/0xba0
  Apr 12 11:31:38 testmachine kernel: Modules linked in: act_police 
cls_basic sch_ingress veth nfsv3 nfs_acl nfs lockd grace ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
xt_mac ipt_REJECT nf_reject_ipv4 xt_physdev xt_comment nf_conntrack_ipv4 
nf_defrag_ipv4 xt_tcpudp xt_mark xt_set xt_addrtype xt_multiport xt_conntrack 
nf_conntrack ip_set_hash_net ip_set arc4 md4 nls_utf8 cifs ccm fscache ipta
  Apr 12 11:31:38 testmachine kernel:  snd_hda_codec_realtek 
snd_hda_codec_generic aesni_intel aes_x86_64 crypto_simd drm_kms_helper 
glue_helper cryptd drm snd_hda_intel intel_cstate snd_hda_codec i2c_algo_bit 
fb_sys_fops snd_hda_core joydev syscopyarea snd_hwdep sysfillrect input_leds 
sysimgblt intel_rapl_perf snd_pcm snd_timer snd pcspkr soundcore mei_me lpc_ich 
mei shpchp tpm_infineon mac_hid wmi acpi_pad video vhost_net vhost macv
  Apr 12 11:31:38 testmachine kernel: CPU: 7 PID: 16596 Comm: tc Tainted: P 
  O4.10.5-1-pve #1
  Apr 12 11:31:38 testmachine kernel: Hardware name: ASUS All Series/Z97-A, 
BIOS 2801 11/11/2015
  Apr 12 11:31:38 testmachine kernel: Call Trace:
  Apr 12 11:31:38 testmachine kernel:  dump_stack+0x63/0x81
  Apr 12 11:31:38 testmachine kernel:  __warn+0xcb/0xf0
  Apr

[Kernel-packages] [Bug 1682712] Re: Laptop lid is always reported as closed

This issue appears to be an upstream bug, since you tested the latest upstream 
kernel. Would it be possible for you to open an upstream bug report[0]? That 
will allow the upstream Developers to examine the issue, and may provide a 
quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to
email the appropriate mailing list. If no response is received, then a
bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-
reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel


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

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

Title:
  Laptop lid is always reported as closed

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

Bug description:
  On Livefan S1 laptop lid is _always_ reported as closed.

  
  #cat /proc/acpi/button/lid/LID0/state 
  state:  closed

  #lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  `acpi_listen` doesn't detect any events
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  av 2654 F pulseaudio
   /dev/snd/controlC1:  av 2654 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=32f21a3f-3826-4c6f-87f3-003691b95fd1
  InstallationDate: Installed on 2016-07-25 (262 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=d7a13f95-ab6e-4c80-947d-4c9dfd7855bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: HN01
  dmi.board.vendor: Hylink
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd04/14/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnHylink:rnHN01:rvr1.2:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  av 2654 F pulseaudio
   /dev/snd/controlC1:  av 2654 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=32f21a3f-3826-4c6f-87f3-003691b95fd1
  InstallationDate: Installed on 2016-07-25 (262 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=d7a13f95-ab6e-4c80-947d-4c9dfd7855bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: HN01
  dmi.board.vendor: Hylink
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd04/14/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnHylink:rnHN01:rvr1.2:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled

[Kernel-packages] [Bug 1680502] Re: Hang after upgrade to 16.04

2017-04-19 Thread Arlie Stephens

Hmm - 73 zombies?! And systemd is in an uninterruptible sleep. It moreover has 
not accumulated any time since I first ran top, so I'd say it's still in the 
*same* uninterruptible sleep... for at least 14 minutes. Also, the number of 
zombies has been increasing, as of right now, it's 187.
I don't have the ability to live debug this kernel, but I'm morally convinced 
that if we could trace the resource systemd is waiting on, 

---
top - 08:34:16 up 3 days, 11:44,  2 users,  load average: 10.00, 9.99, 8.69
Tasks: 472 total,   5 running, 280 sleeping,   0 stopped, 187 zombie
%Cpu(s):  1.2 us,  0.4 sy,  0.1 ni, 98.1 id,  0.2 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  8140712 total,  1037684 free,   336272 used,  6766756 buff/cache
KiB Swap:  7781712 total,  7495516 free,   286196 used.  7137692 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
 2527 arlie 20   0   0  0  0 Z 106.7  0.0  60:36.87 compiz  
1 root  20   0  120072   3980   2132 D   0.0  0.0   0:06.37 systemd 
2 root  20   0   0  0  0 S   0.0  0.0   0:00.02 kthreadd

---
And look at this, we have a defunct pager!!

arlie@ansuz$ ps -Fa -p1
UIDPID  PPID  CSZ   RSS PSR STIME TTY  TIME CMD
root 1 0  0 30018  3980   3 Apr15 ?00:00:06 /sbin/init 
splash
arlie24386 1  0 0 0   3 08:15 pts/200:00:00 [pager] 

arlie24859 24139  0  9342  3284   3 08:37 pts/200:00:00 ps -Fa -p1

--
I can't get the WCHAN for systemd out of ps. Sorry.

--
arlie@ansuz$ ps -e -o pid,wchan=WIDE-WCHAN-COLUMN -o comm | head
  PID WIDE-WCHAN-COLUMN COMMAND
1 - systemd
2 - kthreadd
3 - ksoftirqd/0

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

Title:
  Hang after upgrade to 16.04

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

Bug description:
  Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately
  to 16.04 LTS.

  12.04 was not entirely stable; something was crashing regularly, and
  the Ubuntu tools make it hard for a user to determine what. The
  upgrade went moderately well; I now get error messages during system
  startup (about an unnamed file not being found) and a couple of other
  bits of flakiness, but I counted it as a success and the system as
  functional.

  This morning I tried to wake up my screen, and nothing much happened.
  I then attempted to ssh to the ubuntu box from another system. This
  requested my password almost instantly, as normal - but then nothing
  else happened, and the connection eventually dropped.

  I conclude that IP and TCP are functional, and it's possible for some
  processes to respond, but not many. So it's not a complete kernel
  hang. (In particular, I'm seeing evidence that it's getting beyond
  things done at interrupt level.)

  I don't have any debugging aids installed, so I don't believe I can
  get a kernel crash dump, which is what I'd want if I were debugging
  this. I *can* potentially retrieve and attach logs, but you'll have to
  tell me which ones are relevant, and do so before they rollover.
  (Also, logging will have to be functioning; IIRC, there were syslog
  issues in 12.04, and while I'd implemented whatever fix was
  reccommended at the time, I haven't looked at my logs since the
  upgrade.)

  This is a desk top system originally from System 76 - i.e. built for
  linux - that's also running a bunch of server software (postfix,
  apache, ...) I was not (knowingly) running anythign unusual at the
  time - probably Unity, a few shells, firefox, maybe guncash and/or
  emacs - and all the usual demons.

  IIRC, I was not at the very latest versions of all software installed
  - some new versions ahd come out since I upgraded, and I was going to
  deal with installing them on the weekend.

  I'm going to hard reboot the system now. I can then gather identifying info. 
If I have time this AM before work, I'll check for standard things you want in 
all bugs, and add them. (Right now I'm posting from my Mac laptop ;-))
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  arlie  2507 F pulseaudio
   /dev/snd/controlC0:  arlie  2507 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09
  InstallationDate: Installed on 2012-04-26 (1811 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: System76, Inc. Wild Dog Performance
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic

[Kernel-packages] [Bug 1682712] Re: Laptop lid is always reported as closed

Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced.   If this is a
regression, we can perform a kernel bisect to identify the commit that
introduced the problem.

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

Title:
  Laptop lid is always reported as closed

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

Bug description:
  On Livefan S1 laptop lid is _always_ reported as closed.

  
  #cat /proc/acpi/button/lid/LID0/state 
  state:  closed

  #lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  `acpi_listen` doesn't detect any events
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  av 2654 F pulseaudio
   /dev/snd/controlC1:  av 2654 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=32f21a3f-3826-4c6f-87f3-003691b95fd1
  InstallationDate: Installed on 2016-07-25 (262 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=d7a13f95-ab6e-4c80-947d-4c9dfd7855bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: HN01
  dmi.board.vendor: Hylink
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd04/14/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnHylink:rnHN01:rvr1.2:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  av 2654 F pulseaudio
   /dev/snd/controlC1:  av 2654 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=32f21a3f-3826-4c6f-87f3-003691b95fd1
  InstallationDate: Installed on 2016-07-25 (262 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=d7a13f95-ab6e-4c80-947d-4c9dfd7855bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: HN01
  dmi.board.vendor: Hylink
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd04/14/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnHylink:rnHN01:rvr1.2:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to :

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

2017-04-19 Thread Chris Hermansen

Joseph, I'm running 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:04:59
UTC 2017 x86_64 x86_64 x86_64 now.  I'll keep you posted.

BTW no problems yesterday with 4.10.11.  My wife has been using the
computer for a photo project on a web-based photo book service and that
is what brought about this problem in the first place.

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

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

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

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

  Relevant dmesg attached (dmesg_crash.txt).

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

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

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

[Kernel-packages] [Bug 1680502] Re: Hang after upgrade to 16.04

2017-04-19 Thread Arlie Stephens

Note that the compiz process appears to be zombie, and "kill -9"
naturally fails to make it go away. I suppose it might be racking up all
this time attempting to dump core.

I wish I knew whether compiz has been berserk in all the cases where I
power cycled the system to regain control. If it has, the implication
seems to be that this is a Unity bug. Otherwise not.

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

Title:
Hang after upgrade to 16.04

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

Bug description:
Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately
to 16.04 LTS.

12.04 was not entirely stable; something was crashing regularly, and
the Ubuntu tools make it hard for a user to determine what. The
upgrade went moderately well; I now get error messages during system
startup (about an unnamed file not being found) and a couple of other
bits of flakiness, but I counted it as a success and the system as
functional.

This morning I tried to wake up my screen, and nothing much happened.
I then attempted to ssh to the ubuntu box from another system. This
requested my password almost instantly, as normal - but then nothing
else happened, and the connection eventually dropped.

I conclude that IP and TCP are functional, and it's possible for some
processes to respond, but not many. So it's not a complete kernel
hang. (In particular, I'm seeing evidence that it's getting beyond
things done at interrupt level.)

I don't have any debugging aids installed, so I don't believe I can
get a kernel crash dump, which is what I'd want if I were debugging
this. I *can* potentially retrieve and attach logs, but you'll have to
tell me which ones are relevant, and do so before they rollover.
(Also, logging will have to be functioning; IIRC, there were syslog
issues in 12.04, and while I'd implemented whatever fix was
reccommended at the time, I haven't looked at my logs since the
upgrade.)

This is a desk top system originally from System 76 - i.e. built for
linux - that's also running a bunch of server software (postfix,
apache, ...) I was not (knowingly) running anythign unusual at the
time - probably Unity, a few shells, firefox, maybe guncash and/or
emacs - and all the usual demons.

IIRC, I was not at the very latest versions of all software installed
- some new versions ahd come out since I upgraded, and I was going to
deal with installing them on the weekend.

I'm going to hard reboot the system now. I can then gather identifying info.
If I have time this AM before work, I'll check for standard things you want in
all bugs, and add them. (Right now I'm posting from my Mac laptop ;-))
---
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: arlie 2507 F pulseaudio
/dev/snd/controlC0: arlie 2507 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09
InstallationDate: Installed on 2012-04-26 (1811 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MachineType: System76, Inc. Wild Dog Performance
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic
root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
RelatedPackageVersions:
linux-restricted-modules-4.4.0-72-generic N/A
linux-backports-modules-4.4.0-72-generic N/A
linux-firmware1.157.8
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-72-generic x86_64
UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/24/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825
dmi.board.name: DH77KC
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39641-400
dmi.chassis.type: 3
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: WilP9
dmi.modalias:
dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9:
dmi.product.name: Wild Dog Performance
dmi.product.version: wilp9
dmi.sys.vendor: System76, Inc.

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

--
Mailing list: https://launchpad.net/~kernel-packages
Post to :

[Kernel-packages] [Bug 1682034] Re: linux: 4.8.0-48.51 -proposed tracker

2017-04-19 Thread Kleber Sacilotto de Souza

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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/1682034

Title:
  linux: 4.8.0-48.51 -proposed tracker

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

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

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

  backports: 1682037
  derivatives: 1682038
  -- 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/1682034/+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 1682041] Re: linux: 4.4.0-74.95 -proposed tracker

2017-04-19 Thread Taihsiang Ho

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-74.95
/xenial-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1682041

Title:
  linux: 4.4.0-74.95 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- 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/1682041/+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 1680502] Re: Hang after upgrade to 16.04

2017-04-19 Thread Arlie Stephens

My apologies for going dark on you. I intend to try the upstream kernel,
but I've been haviing trouble finding time. With luck, I'll get it
installed this coming weekend.

Meanwhile, I've since had 2 or 3 standard recurrences, and one this
morning involving significantly diferent behaviour. (Of course it could
be a different bug, but the primary symptom is the same ... complete
lack of response on the system console.

The difference this morning is that I was able to log in over the LAN
and attempt a controlled shutdown - which failed.

Also notable - I've installed at least one batch of fixes since the
first incident.

-- Snippets from window follow. Note the load average. Note also the hysterical 
compiz process --
arlie@ansuz$ uptime
 08:09:42 up 3 days, 11:19,  2 users,  load average: 9.95, 6.86, 3.43
arlie@ansuz$ sudo shutdown -r now
[sudo] password for arlie: 
Failed to start reboot.target: Connection timed out
See system logs and 'systemctl status reboot.target' for details.

arlie@ansuz$ systemctl status reboot.target
Failed to get properties: Connection timed out

top - 08:17:44 up 3 days, 11:27,  2 users,  load average: 10.00, 9.39, 6.11
Tasks: 312 total,   5 running, 234 sleeping,   0 stopped,  73 zombie
%Cpu(s):  0.0 us, 25.1 sy,  0.0 ni, 74.9 id,  0.1 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  8140712 total,  908 free,   288328 used,  6740476 buff/cache
KiB Swap:  7781712 total,  7495504 free,   286208 used.  7202464 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
 2527 arlie 20   0   0  0  0 Z  99.7  0.0  44:05.00 compiz  
24400 arlie 20   0   41936   3780   3048 R   0.3  0.0   0:00.02 top 
1 root  20   0  120072   3980   2132 D   0.0  0.0   0:06.37 systemd 
2 root  20   0   0  0  0 S   0.0  0.0   0:00.02 kthreadd
3 root  20   0   0  0  0 R   0.0  0.0   0:00.46 ksoftirqd/0 
5 root   0 -20   0  0  0 S   0.0  0.0   0:00.00 kworker/0:0H
7 root  20   0   0  0  0 S   0.0  0.0   0:40.51 rcu_sched   
8 root  20   0   0  0  0 S   0.0  0.0   0:00.00 rcu_bh

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

Title:
  Hang after upgrade to 16.04

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

Bug description:
  Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately
  to 16.04 LTS.

  12.04 was not entirely stable; something was crashing regularly, and
  the Ubuntu tools make it hard for a user to determine what. The
  upgrade went moderately well; I now get error messages during system
  startup (about an unnamed file not being found) and a couple of other
  bits of flakiness, but I counted it as a success and the system as
  functional.

  This morning I tried to wake up my screen, and nothing much happened.
  I then attempted to ssh to the ubuntu box from another system. This
  requested my password almost instantly, as normal - but then nothing
  else happened, and the connection eventually dropped.

  I conclude that IP and TCP are functional, and it's possible for some
  processes to respond, but not many. So it's not a complete kernel
  hang. (In particular, I'm seeing evidence that it's getting beyond
  things done at interrupt level.)

  I don't have any debugging aids installed, so I don't believe I can
  get a kernel crash dump, which is what I'd want if I were debugging
  this. I *can* potentially retrieve and attach logs, but you'll have to
  tell me which ones are relevant, and do so before they rollover.
  (Also, logging will have to be functioning; IIRC, there were syslog
  issues in 12.04, and while I'd implemented whatever fix was
  reccommended at the time, I haven't looked at my logs since the
  upgrade.)

  This is a desk top system originally from System 76 - i.e. built for
  linux - that's also running a bunch of server software (postfix,
  apache, ...) I was not (knowingly) running anythign unusual at the
  time - probably Unity, a few shells, firefox, maybe guncash and/or
  emacs - and all the usual demons.

  IIRC, I was not at the very latest versions of all software installed
  - some new versions ahd come out since I upgraded, and I was going to
  deal with installing them on the weekend.

  I'm going to hard reboot the system now. I can then gather identifying info. 
If I have time this AM before work, I'll check for standard things you want in 
all bugs, and add them. (Right now I'm posting from my Mac laptop ;-))
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  arlie  2507 F pulseaudio
   /dev/snd/controlC0:  arlie  2507 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04

[Kernel-packages] [Bug 1682034] Re: linux: 4.8.0-48.51 -proposed tracker

2017-04-19 Thread Kleber Sacilotto de Souza

** Tags added: regression-testing-passed

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

Title:
  linux: 4.8.0-48.51 -proposed tracker

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

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

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

  backports: 1682037
  derivatives: 1682038
  -- 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/1682034/+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 1654073] Comment bridged from LTC Bugzilla

--- Comment From ru...@us.ibm.com 2017-04-19 11:08 EDT---
FYI Canonical:

It appears that the issue was not resolved with the most recent patch as
this panic was recently seen with the 4.10.0-19-generic kernel.
Unfortunately, no new vmcore is available due to the issue currently
being worked in LP Bug 1680349.

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

Title:
  Ubuntu 17.04: machine crashes with Oops in dccp_v4_ctl_send_reset
  while running stress-ng.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-28 03:39:50 ==
  ---Problem Description---

  Ubuntu 17.04: machine crashes with Oops while running stress-ng.

  ---Steps followed-

  1. Install 17.04 on NV machine.
  2. apt-get install stress-ng
  3. stress-ng -a 0

  Logs
  
  dccp af_alg joydev input_leds mac_hid at24 nvmem_core ofpart cmdlinepart 
powernv_flash mtd opal_prd powernv_rng ipmi_powernv ipmi_msghandler ibmpowernv 
uio_pdrv_genirq uio vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_tran[165938083361,3] OPAL: Trying a CPU 
re-init with flags: 0x1
  [166456504189,3] OPAL: CPU 0x29 not in OPAL !
  [167510150475,3] OPAL: Trying a CPU re-init with flags: 0x2
  [168022446397,3] OPAL: CPU 0x29 not in OPAL !
  sport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear ses enclosure scsi_transport_sas hid_generic ast i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt bnx2x fb_sys_fops drm aacraid 
tg3 usbhid uas hid usb_storage mdio ahci libcrc32c libahci crc32c_vpmsum
  [  237.047216] CPU: 33 PID: 34694 Comm: stress-ng-dccp Not tainted 
4.9.0-11-generic #12-Ubuntu
  [  237.047315] task: c03312a69400 task.stack: c03779698000
  [  237.047402] NIP: d0002e7b0a7c LR: d0002e7b21cc CTR: 
c0a0dd00
  [  237.047509] REGS: c03fff68f670 TRAP: 0300   Not tainted  
(4.9.0-11-generic)
  [  237.047613] MSR: 90010280b033 
[  237.049028]   CR: 24002282  XER: 
2000
  [  237.049103] CFAR: c0008a60 DAR: 02f4 DSISR: 4000 
SOFTE: 1 
  GPR00: d0002e7b21cc c03fff68f8f0 d0002e7bb670 0001 
  GPR04: c02b5dbdc400 c03c74c0a460 0474 c03c74c0a474 
  GPR08: c03c74c0a000  c0348cd25200  
  GPR12: 2200 c7b72900 c03fff68c000  
  GPR16:  0040 0001 2713 
  GPR20: cc84 017f 017f c13b2f00 
  GPR24: 0001 0001  0004 
  GPR28: c13b2f00 c03c74c0a474  c02b5dbdc400 
  NIP [d0002e7b0a7c] dccp_v4_ctl_send_reset+0xa4/0x2f0 [dccp_ipv4]
  [  237.051403] LR [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 [dccp_ipv4]
  [  237.051486] Call Trace:
  [  237.051529] [c03fff68f8f0] [2713cc84] 0x2713cc84 (unreliable)
  [  237.051649] [c03fff68f970] [d0002e7b21cc] dccp_v4_rcv+0x5d4/0x850 
[dccp_ipv4]
  [  237.051779] [c03fff68fa50] [c0a01e40] 
ip_local_deliver_finish+0x170/0x350
  [  237.051932] [c03fff68faa0] [c0a0276c] 
ip_local_deliver+0x5c/0x130
  [  237.052038] [c03fff68fb10] [c0a02278] ip_rcv_finish+0x258/0x510
  [  237.052151] [c03fff68fba0] [c0a02b44] ip_rcv+0x304/0x420
  [  237.052263] [c03fff68fc30] [c09a28bc] 
__netif_receive_skb_core+0x97c/0xda0
  [  237.052388] [c03fff68fd10] [c09a7ab4] 
process_backlog+0xd4/0x1e0
  [  237.052489] [c03fff68fd80] [c09a6f0c] net_rx_action+0x35c/0x480
  [  237.052603] [c03fff68fe90] [c0b22a6c] __do_softirq+0x18c/0x3fc
  [  237.052726] [c03fff68ff90] [c0029fb0] call_do_softirq+0x14/0x24
  [  237.052848] [c0377969b920] [c001765c] 
do_softirq_own_stack+0x5c/0xa0
  [  237.052992] [c0377969b960] [c00cfd48] 
do_softirq.part.3+0x68/0x90
  [  237.053112] [c0377969b990] [c00cfe44] 
__local_bh_enable_ip+0xd4/0x100
  [  237.053240] [c0377969b9b0] [c0a06724] 
ip_finish_output2+0x244/0x460
  [  237.053372] [c0377969ba50] [c0a0977c] ip_output+0xcc/0x180
  [  237.053485] [c0377969bae0] [c0a08c78] ip_local_out+0x68/0x90
  [  237.053607] [c0377969bb20] [d00021966978] 
dccp_transmit_skb+0x320/0x550 [dccp]
  [  237.053739] [c0377969bb90] [d0002196732c] dccp_connect+0xf4/0x1f0 
[dccp]
  [  237.053890] [c0377969bc10] [d0002e7b0320] 
dccp_v4_connect+0x308/0x400 [dccp_ipv4]
  [  237.054213] [c0377969bc90] [c0a51678]

[Kernel-packages] [Bug 1683976] Re: Please backport fix to reference leak in cgroup blkio throttle

I built a Trusty and Xenial test kernel with commit 39a169b62b41.  These
test kernels can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1683976/

Can you test one of these kernel and post back if it resolves this bug?

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

Title:
  Please backport fix to reference leak in cgroup blkio throttle

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

Bug description:
  This is fixed in Linux 4.5
  
https://github.com/torvalds/linux/commit/39a169b62b415390398291080dafe63aec751e0a

  Basically the module reference will leak whenever you write to
  /sys/fs/cgroup/blkio/blkio.throttle.*

  $ uname -a
  Linux david-kvm 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsmod | grep ^zfs
  zfs  2813952  1
  $ sudo sh -c 'i=100; while [ $i -gt 0 ]; do echo "230:0 1024" > 
/sys/fs/cgroup/blkio/blkio.throttle.read_bps_device; i=$(($i - 1)); done'
  $ lsmod | grep ^zfs
  zfs  2813952  101

  This patch should be applied to all kernel < 4.5

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683976/+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 1681904] Re: WLan not working after Kernel update (HWE)

2017-04-19 Thread davidak

I can reproduce the issue with Linux kernel 4.8.0-45-generic
#48~lp1681904Commit3105082594OntopOfStock44.

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

Title:
  WLan not working after Kernel update (HWE)

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

Bug description:
  After the update from 4.8.0.44 to newer versions, wifi stopped
  working.

  The controller is still found with `lshw -class network`, but wifi is
  not displayed in Network Manager.

  Hardware is Broadcom BCM4331 802.11a/b/g/n.

  What additional informations do you need to resolve this?

  -

  Apple MacBookPro10,2 from ~2012
  elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681904/+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 1683976] Re: Please backport fix to reference leak in cgroup blkio throttle

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

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

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

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

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

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

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

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

** Tags added: trusty

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

Title:
  Please backport fix to reference leak in cgroup blkio throttle

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

Bug description:
  This is fixed in Linux 4.5
  
https://github.com/torvalds/linux/commit/39a169b62b415390398291080dafe63aec751e0a

  Basically the module reference will leak whenever you write to
  /sys/fs/cgroup/blkio/blkio.throttle.*

  $ uname -a
  Linux david-kvm 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsmod | grep ^zfs
  zfs  2813952  1
  $ sudo sh -c 'i=100; while [ $i -gt 0 ]; do echo "230:0 1024" > 
/sys/fs/cgroup/blkio/blkio.throttle.read_bps_device; i=$(($i - 1)); done'
  $ lsmod | grep ^zfs
  zfs  2813952  101

  This patch should be applied to all kernel < 4.5

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683976/+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 1644504] Re: [17.04 FEAT] Ensure stable PCI Identifiers using UIDs

** Tags removed: bugnameltc-149055 severity-high

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

Title:
  [17.04 FEAT] Ensure stable PCI Identifiers using UIDs

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Guarantee stable and unique identifiers for PCI functions.
  Specifically ensure that a PCI function (virtual or physical) will
  always be represented by the same value as long as the IO
  configuration for this function (IOCDS, HCD) does not change.

  Allow customers to maintain persistent configurations for PCI devices
  where needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644504/+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 1612224] Comment bridged from LTC Bugzilla

--- Comment From heinz-werner_se...@de.ibm.com 2017-04-19 10:37 EDT---
IBM Bugzilla Status -> Closed ; available with GA version

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

Title:
  [17.04 FEAT] Extend cpu topology to support drawers

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  kernel 4.8: Add support for the additional scheduling layer within the
  kernel and util-linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1612224/+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 1644504] Comment bridged from LTC Bugzilla

--- Comment From heinz-werner_se...@de.ibm.com 2017-04-19 10:35 EDT---
IBM Bugzilla Status -> Closed ; available with GA version

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

Title:
  [17.04 FEAT] Ensure stable PCI Identifiers using UIDs

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Guarantee stable and unique identifiers for PCI functions.
  Specifically ensure that a PCI function (virtual or physical) will
  always be represented by the same value as long as the IO
  configuration for this function (IOCDS, HCD) does not change.

  Allow customers to maintain persistent configurations for PCI devices
  where needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644504/+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 1655909] Comment bridged from LTC Bugzilla