[Kernel-packages] [Bug 1654782] Re: Can not pair with bluetooth headphones

[Konrad Zapałowicz]

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz)

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

Title:
  Can not pair with bluetooth headphones

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 
wireless aebt).
  (If it matters, I *CAN* pair and use it on another laptop with Linux and with 
my android smartphone. So headset itself is working well.)

  Here is how I try to pair:
  $ bluetoothctl
  [NEW] Controller 54:27:1E:33:4B:85 impedance [default]
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 54:27:1E:33:4B:85 Discovering: yes
  [bluetooth]# scan on

  I tried to put my headset in pairing mode just before and after
  issuing "scan on" command. It ends up with nothing - I waited for 3-5
  minutes. For example, my smartphone pairs with the headset within 5-15
  seconds, my laptop pairs with the headset within about 30 seconds.

  =

  Here is info

  $ hciconfig -a
  hci0:   Type: Primary  Bus: USB
  BD Address: 54:27:1E:33:4B:85  ACL MTU: 1021:8  SCO MTU: 64:1
  UP RUNNING PSCAN ISCAN
  RX bytes:4475 acl:0 sco:0 events:565 errors:0
  TX bytes:7214 acl:0 sco:0 commands:487 errors:0
  Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'impedance'
  Class: 0x1c0104
  Service Classes: Rendering, Capturing, Object Transfer
  Device Class: Computer, Desktop workstation
  HCI Version: 4.0 (0x6)  Revision: 0x1000
  LMP Version: 4.0 (0x6)  Subversion: 0x220e
  Manufacturer: Broadcom Corporation (15)

  =

  rfkill list
  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  =

  Bluez packages installed:
  $ dpkg -l | grep bluez
  ii  bluez
  ii  bluez-btsco
  ii  bluez-cups
  ii  bluez-hcidump
  ii  bluez-obexd
  ii  bluez-tools
  ii  libkf5bluezqt-data
  ii  libkf5bluezqt6:amd64
  ii  qml-module-org-kde-bluezqt:amd64

  =

  $ dmesg | grep -i blue
  [4.632406] Bluetooth: Core ver 2.21
  [4.632414] Bluetooth: HCI device and connection manager initialized
  [4.632416] Bluetooth: HCI socket layer initialized
  [4.632417] Bluetooth: L2CAP socket layer initialized
  [4.632420] Bluetooth: SCO socket layer initialized
  [4.644619] Bluetooth: hci0: BCM: chip id 63
  [4.660554] Bluetooth: hci0: impedance
  [4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [4.661798] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0b05-17cf.hcd failed with error -2
  [4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not 
found
  [   15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.061604] Bluetooth: BNEP filters: protocol multicast
  [   15.061606] Bluetooth: BNEP socket layer initialized
  [   48.001553] Bluetooth: RFCOMM TTY layer initialized
  [   48.001558] Bluetooth: RFCOMM socket layer initialized
  [   48.001562] Bluetooth: RFCOMM ver 1.11
  [  615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp 
bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc 
nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor 
snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq 
btusb btrtl btbcm btintel bluetooth kvm_intel kvm irqbypass crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper 
ablk_helper cryptd intel_cstate input_leds intel_rapl_perf 8021q garp mrp stp 
serio_raw llc b43 mac80211 snd_hda_codec_realtek snd_hda_codec_generic

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Jan  7 22:36:22 2017
  InstallationDate: Installed on 2014-07-05 (917 days ago)
  InstallationMedia: Kubuntu 14.04 

[Kernel-packages] [Bug 1654782] Re: Can not pair with bluetooth headphones

[Konrad Zapałowicz]

Hey,

Thanks for the report. I will mark it as "needs information" because I
need a follow up from your side. Once I get the log files I ask about
below I will change the status to further.

- what kind of Ubuntu version is installed on the Linux computer that
works just wine with your headset?

Also, could you capture a somewhat more verbose logs. I would love to
see at least a HCI trace. You can capture it with sudo btmon --write
~/hcitrace.snoop. Just start it and then try to pair with your headset.
Also please do not make the test case really long so that it is easier
to understand the output :) Finally please read also
https://wiki.ubuntu.com/DebuggingBluetooth to understand how different
logs for BT debugging can be captured.

Thanks.

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

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

Title:
  Can not pair with bluetooth headphones

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 
wireless aebt).
  (If it matters, I *CAN* pair and use it on another laptop with Linux and with 
my android smartphone. So headset itself is working well.)

  Here is how I try to pair:
  $ bluetoothctl
  [NEW] Controller 54:27:1E:33:4B:85 impedance [default]
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 54:27:1E:33:4B:85 Discovering: yes
  [bluetooth]# scan on

  I tried to put my headset in pairing mode just before and after
  issuing "scan on" command. It ends up with nothing - I waited for 3-5
  minutes. For example, my smartphone pairs with the headset within 5-15
  seconds, my laptop pairs with the headset within about 30 seconds.

  =

  Here is info

  $ hciconfig -a
  hci0:   Type: Primary  Bus: USB
  BD Address: 54:27:1E:33:4B:85  ACL MTU: 1021:8  SCO MTU: 64:1
  UP RUNNING PSCAN ISCAN
  RX bytes:4475 acl:0 sco:0 events:565 errors:0
  TX bytes:7214 acl:0 sco:0 commands:487 errors:0
  Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'impedance'
  Class: 0x1c0104
  Service Classes: Rendering, Capturing, Object Transfer
  Device Class: Computer, Desktop workstation
  HCI Version: 4.0 (0x6)  Revision: 0x1000
  LMP Version: 4.0 (0x6)  Subversion: 0x220e
  Manufacturer: Broadcom Corporation (15)

  =

  rfkill list
  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  =

  Bluez packages installed:
  $ dpkg -l | grep bluez
  ii  bluez
  ii  bluez-btsco
  ii  bluez-cups
  ii  bluez-hcidump
  ii  bluez-obexd
  ii  bluez-tools
  ii  libkf5bluezqt-data
  ii  libkf5bluezqt6:amd64
  ii  qml-module-org-kde-bluezqt:amd64

  =

  $ dmesg | grep -i blue
  [4.632406] Bluetooth: Core ver 2.21
  [4.632414] Bluetooth: HCI device and connection manager initialized
  [4.632416] Bluetooth: HCI socket layer initialized
  [4.632417] Bluetooth: L2CAP socket layer initialized
  [4.632420] Bluetooth: SCO socket layer initialized
  [4.644619] Bluetooth: hci0: BCM: chip id 63
  [4.660554] Bluetooth: hci0: impedance
  [4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [4.661798] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0b05-17cf.hcd failed with error -2
  [4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not 
found
  [   15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.061604] Bluetooth: BNEP filters: protocol multicast
  [   15.061606] Bluetooth: BNEP socket layer initialized
  [   48.001553] Bluetooth: RFCOMM TTY layer initialized
  [   48.001558] Bluetooth: RFCOMM socket layer initialized
  [   48.001562] Bluetooth: RFCOMM ver 1.11
  [  615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp 
bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc 
nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor 
snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq 
btusb btrtl btbcm btintel 

[Kernel-packages] [Bug 1653314] Re: package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Konrad Zapałowicz]

Hey,

Could you share some more information about the nature of the failure.
Right now I cannot tell what has happened.

Thanks

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

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

Title:
  package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: подпроцесс
  установлен сценарий post-installation возвратил код ошибки 1

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  i can'conekt bluetooth

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez:i386 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Fri Dec 30 19:39:34 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2016-11-29 (31 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: bnep bluetooth
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=fb1fce69-ec71-4461-85dd-690d60245405 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: bluez
  Title: package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CROSSHAIR V FORMULA-Z
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1302:bd01/11/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVFORMULA-Z:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  hciconfig:
   
  rfkill:

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

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

[Kernel-packages] [Bug 1626870] Re: USB-devices connected to dockin not recognized when connected at boot

[Andreas Noteng]

The problem seems to have gone away. I don't know when it was fixed for me, has 
there been a recent kernel update?
After reporting this bug I reinstalled using kubuntu installer, but later 
switched to mate desktop. I do know the problem was still present after 
installing kubuntu, but it has gone away some time after that.

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

Title:
  USB-devices connected to dockin not recognized when connected at boot

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  My laptop is mostly connected to a docking station in my office. If
  the computer is docked when booting, the USB devices (keyboard, mouse)
  are not detected. If I remove the computer from docking and then
  reinsert everything works as expected. Monitors and network connected
  to the dock does not have this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-generic 4.4.0.9136.37
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas5094 F pulseaudio
   /dev/snd/controlC0:  andreas5094 F pulseaudio
   /dev/snd/controlC1:  andreas5094 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 09:22:41 2016
  HibernationDevice: RESUME=UUID=a573b0e2-8ed1-4d22-9313-8e552c603b2f
  InstallationDate: Installed on 2016-07-13 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=cdbcc31e-7f7d-4ad9-b46d-5299d8f494ec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9136-generic N/A
   linux-backports-modules-4.4.0-9136-generic  N/A
   linux-firmware  1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-09-20 (2 days ago)
  dmi.bios.date: 05/19/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0JNYGR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/19/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0JNYGR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1657112] Re: linux: 4.8.0-36.38 -proposed tracker

[Steve Langasek]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

[Konrad Zapałowicz]

@Wesley

You mean with Sony or Bose?

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions

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

[Kernel-packages] [Bug 1655476] Re: linux: 3.13.0-108.155 -proposed tracker

[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/trusty/3.13.0-108.155
/trusty-proposed-frozen.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/1655476

Title:
  linux: 3.13.0-108.155 -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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  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 3.13.0-108.155 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
  derivative-trackers-created: 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/1655476/+subscriptions

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

[Kernel-packages] [Bug 1635447] Re: Upgraded or Live USB 16.10 hangs at boot up blank purple screen

[renm]

@Joseph, both versions can boot up properly.

And more, I just found out the latest v4.8.0-34 already can boot up
successfully without acpi=off while previous v4.8.0-30 does not.

So looks like that my issue has been fixed in 4.8.0-34.

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

Title:
  Upgraded or Live USB 16.10 hangs at boot up blank purple screen

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

Bug description:
  My HP dm3z-2000 laptop works out of box for everything with Ubuntu
  16.04, but fails to boot up after upgraded to 16.10. The upgrading
  went smooth itself.

  Laptop still can boot up with the latest 4.4 kernel of 16.04 which I
  did a regular update/upgrade before 16.10 release upgrade.

  Then I tried to boot with 16.10 Live USB and got same result.

  It also can boot up with kernel 4.8 if "acpi=off" parameter in place,
  but it takes long time to boot up. Everything seems fine after logged
  in and Unity 8 session works too.

  I couldn't get any log files since the system won't boot up,
  Ctrl+Alt+F1 does nothing. I can only see some messages in text boot
  mode, so I took a screen shot with my phone and attached here.

  Let me know how to get more details.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  renm   2918 F pulseaudio
   /dev/snd/controlC1:  renm   2918 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7e8ca036-f81d-43e2-820a-1deadcffc2dc
  InstallationDate: Installed on 2016-10-08 (13 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Pavilion dm3t Notebook PC
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=19005996-db50-4249-9c73-17cf874dc678 ro acpi=off
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1482
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd10/13/2010:svnHewlett-Packard:pnHPPaviliondm3tNotebookPC:pvr048620241F0011032:rvnHewlett-Packard:rn1482:rvr76.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm3t Notebook PC
  dmi.product.version: 048620241F0011032
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1657430] onza (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/onza__4.4.0-62.83__2017-01-19_03-10-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1657453] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1595765, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1595765
   Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here]

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  cheesecame issue - webcam

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: hid_generic usbhid uas usb_storage psmouse ahci r8169 
libahci mii wmi i915 fjes i2c_hid hid video i2c_algo_bit drm_kms_helper 
sdhci_acpi sdhci syscopyarea sysfillrect sysimgblt fb_sys_fops drm
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DKMSKernelVersion: 4.8.0-34-generic
  Date: Wed Jan 18 18:38:31 2017
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:237:12:
 error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu0.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module 
failed to build
  UpgradeStatus: Upgraded to xenial on 2017-01-18 (0 days ago)

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

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

[Kernel-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

[Wesley C wamer]

I am also seeing the identical issues as described above

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions

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

[Kernel-packages] [Bug 1657430] Re: linux: 4.4.0-62.83 -proposed tracker

[Steve Langasek]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1657430] Re: linux: 4.4.0-62.83 -proposed tracker

[Steve Langasek]

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

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-lowlatency/onza__4.4.0-62.83__2017-01-19_00-29-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/1657430

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

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

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

[Brad Figg]

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel updates for this 16.04 system keep reporting this error but an
  apt -f install will fix it. Didn't suffer this problem when on 14.04
  previously (upgraded to 16.04 from it)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Thu Jan 19 00:02:25 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=e40cfdf2-c116-4a18-95b6-b0b0c6f6d674
  InstallationDate: Installed on 2014-02-16 (1067 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA69G-S3H
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=46657d9d-c39e-427e-8924-6ea788a4cb78 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.6
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-59-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to xenial on 2016-10-10 (100 days ago)
  dmi.bios.date: 11/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8e
  dmi.board.name: GA-MA69G-S3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8e:bd11/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA69G-S3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA69G-S3H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA69G-S3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1657606] Re: package linux-image-4.4.0-59-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel updates for this 16.04 system keep reporting this error but an
  apt -f install will fix it. Didn't suffer this problem when on 14.04
  previously (upgraded to 16.04 from it)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Thu Jan 19 00:02:25 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=e40cfdf2-c116-4a18-95b6-b0b0c6f6d674
  InstallationDate: Installed on 2014-02-16 (1067 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA69G-S3H
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=46657d9d-c39e-427e-8924-6ea788a4cb78 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.6
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-59-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to xenial on 2016-10-10 (100 days ago)
  dmi.bios.date: 11/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8e
  dmi.board.name: GA-MA69G-S3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8e:bd11/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA69G-S3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA69G-S3H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA69G-S3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1657606] [NEW] package linux-image-4.4.0-59-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[breezer]

Public bug reported:

Kernel updates for this 16.04 system keep reporting this error but an
apt -f install will fix it. Didn't suffer this problem when on 14.04
previously (upgraded to 16.04 from it)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-59-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Thu Jan 19 00:02:25 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=e40cfdf2-c116-4a18-95b6-b0b0c6f6d674
InstallationDate: Installed on 2014-02-16 (1067 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA69G-S3H
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=46657d9d-c39e-427e-8924-6ea788a4cb78 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.6
RfKill:
 
SourcePackage: linux
Title: package linux-image-4.4.0-59-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: Upgraded to xenial on 2016-10-10 (100 days ago)
dmi.bios.date: 11/18/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8e
dmi.board.name: GA-MA69G-S3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8e:bd11/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA69G-S3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA69G-S3H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA69G-S3H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package xenial

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  Kernel updates for this 16.04 system keep reporting this error but an
  apt -f install will fix it. Didn't suffer this problem when on 14.04
  previously (upgraded to 16.04 from it)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Thu Jan 19 00:02:25 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=e40cfdf2-c116-4a18-95b6-b0b0c6f6d674
  InstallationDate: Installed on 2014-02-16 (1067 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA69G-S3H
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=46657d9d-c39e-427e-8924-6ea788a4cb78 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.6
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-59-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to xenial on 2016-10-10 (100 days ago)
  dmi.bios.date: 11/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8e
  dmi.board.name: GA-MA69G-S3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8e:bd11/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA69G-S3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA69G-S3H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA69G-S3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1657430] modoc (ppc64el) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/modoc__4.4.0-62.83__2017-01-18_23-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/1657430

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/onza__4.4.0-62.83__2017-01-18_23-42-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1657430] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/ms10-35-mcdivittB0-kernel__4.4.0-62.83__2017-01-18_23-40-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/1657430

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1634881] Re: Installation/Live-System freezes on Splash screen

[DasJott]

All Kernel 4.x do not boot on my laptop. I tried some...

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

Title:
  Installation/Live-System freezes on Splash screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A USB Stick prepared with 16.04.1 no matter whether "Try Ubuntu" or
  "Install" is chosen, it freezes on splash-Screen.

  With "quiet splash" removed, I get the output on the picture attached.

  In the last line it says: "BUG  Can't handle kernel"

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

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

[Kernel-packages] [Bug 1657430] Re: linux: 4.4.0-62.83 -proposed tracker

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/s2lp6g001__4.4.0-60.81__2017-01-18_23-18-00/results-index.html

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

** Description changed:

  This bug is for tracking the 4.4.0-62.83 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
  
  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC
  
  -- swm properties --
+ boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1657430] kernel01 (s390x.zVM) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/kernel01__4.4.0-60.81__2017-01-18_23-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/1657430

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1657430] s2lp3 (s390x.LPAR) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/s2lp3__4.4.0-60.81__2017-01-18_23-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/1657430

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1657430] Re: linux: 4.4.0-62.83 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-meta
   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/1657430

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1400319] Re: [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10, 15.04, and 15.10

[Chris Valean]

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

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

Title:
  [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10, 15.04,
  and 15.10

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

Bug description:
  While testing the final build of 14.10 32bit we found that kernel
  panic cannot be activated for an installation on a Hyper-V VM.

  Repro rate: 100%
  Repro details:
  Hyper-V: Server 2012 R2
  VM: Ubuntu 14.10 32bit

  Kdump is enabled in the config file at /etc/default/kdump-tools

  Different crashkernel values used in grub.cfg – 128M-:64M | 256M-:128m
  | 384M-:256M

  VM settings: 2 cores, various RAM sizes attempted: 1, 2 or 4 GB – this
  in combination with the values for crashkernel.

  Trying to start the kdump service:
  root@ubuntu1410i386:~# /etc/init.d/kdump-tools start
  Starting kdump-tools: Could not find a free area of memory of 0x9f000 bytes...
  locate_hole failed
  * failed to load kdump kernel
  ---

  root@ubuntu1410i386:~# cat /sys/kernel/kexec_crash_loaded
  0

  
  If the conversion from hex to dec is right, the mentioned memory mapping of 
0x9f000 bytes is equal to 651264 (bytes), so under 1MB. This is not then 
related to the RAM allocation nor the crashkernel value used.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=5a5d0aa4-b8ee-4bf7-b1b9-761b7d1550b6
  InstallationDate: Installed on 2014-10-31 (37 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release i386 
(20141022.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=83fb481a-8898-4adc-bf31-4e160f5f0ce8 ro crashkernel=128M-:64M
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.138
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic
  Uname: Linux 3.16.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   Dec  8 08:16:46 ubuntu1410i386 dhclient: DHCPREQUEST of 10.226.59.102 on 
eth0 to 10.184.232.100 port 67 (xid=0x4b67ffa3)
   Dec  8 08:16:46 ubuntu1410i386 dhclient: DHCPACK of 10.226.59.102 from 
10.184.232.100
   Dec  8 08:16:47 ubuntu1410i386 dhclient: bound to 10.226.59.102 -- renewal 
in 13914 seconds.
   Dec  8 10:10:47 ubuntu1410i386 kernel: [1840786.031060] init: tty1 main 
process ended, respawning
  _MarkForUpload: True
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7176-0455-3377-8479-3268-6677-66
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

[Сергей]

Confirmed. 
It looks like 17.04 uses less ram than 16.04.

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

Title:
  Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

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

Bug description:
  Ubuntu 16.04 64bit ISO number 20160420.1
  unity version 7.4.0+16.04.20160415-0ubuntu1
  Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10
  Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB
  Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 21 01:44:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1920x1080+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 
'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 
'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 
'unityshell']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 21 01:37:17 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Kernel-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Michael Doube]

This bug definitely depends on kernel version. Both the fix mentioned
above in #8
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/comments/8
and mainline kernel after this commit (found with reverse bisect), are
required. Marking as linux bug. Would be very nice if fix could make it
into Ubuntu 16.04 LTS.

:~/linux/linux$ git bisect bad
e075b3c898e4055ec62a1f0ed7f3b8e62814bfb6 is the first bad commit
commit e075b3c898e4055ec62a1f0ed7f3b8e62814bfb6
Author: Pali Rohár 
Date:   Wed Jun 15 21:49:13 2016 +0200

dell-wmi: Generate one sparse keymap for all machines

This patch reworks code for generating sparse keymap and processing WMI
events. It unifies procedure for generating sparse keymap and also unifies
big switch code for processing WMI events of different types. After this
patch dell-wmi driver does not differ between "old" and "new" hotkey type.

It constructs sparse keymap table with all WMI codes. It is because on some
laptops (e.g. Dell Latitude E6440) ACPI/firmware send both event types (old
and new).

Each WMI code in sparse keymap table is prefixed by 16bit event type, so it
does not change functionality on laptops with "old" hotkey support (those
without scancodes in DMI).

This allow us to distinguish between same WMI codes with different types in
sparse keymap. Thanks to this WMI events of type 0x0011 were moved from big
switch into sparse keymap table too.

This patch also fixes possible bug in parsing WMI event buffer introduced
in commit 5ea2559726b7 ("dell-wmi: Add support for new Dell systems"). That
commit changed buffer type from int* to u16* without fixing code. More at:
http://lkml.iu.edu/hypermail/linux/kernel/1507.0/01950.html

Signed-off-by: Pali Rohár 
Tested-by: Michał Kępień 
Reviewed-by: Michał Kępień 
Tested-by: Gabriele Mazzotta 
Signed-off-by: Darren Hart 

:04 04 babec68576f8756c9b0ee28a7ca7496de1c3c41a
b2e0e8cffb710d6ef2bdb9d4634cbd8b65867a34 M  drivers


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

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

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

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Brad Figg]

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

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

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1655101] Re: [Feature] UbuntuKVM: Add and enable seccomp mode 2 in kernel

[Tim Gardner]

All of the requisite SECCOMP configs are already enabled (and have been
since at least 16.04)

CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP=y
CONFIG_SECCOMP_FILTER=y

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

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

Title:
  [Feature] UbuntuKVM: Add and enable seccomp mode 2 in kernel

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  [Feature] add and enable seccomp in kernel

  == Comment: #6 - Leonardo Augusto Guimaraes Garcia  - 
2016-08-30 13:37:40 ==
  My understanding is that all patches required for seccomp enablement in 
kernel are available in kernel 4.8 which will be used in Ubuntu 16.10. However, 
iiuc, we need some build config options to be enabled.

  == Comment: #7 - Michael T. Strosaker  - 2016-09-19 
17:04:51 ==
  Support has been available upstream since 4.3, if memory serves.  The 16.10 
kernel config should include CONFIG_SECCOMP_FILTER=y if it does not already 
(HAVE_ARCH_SECCOMP_FILTER is required for CONFIG_SECCOMP_FILTER to be 
available).

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

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

[Kernel-packages] [Bug 1656618] Re: Any key pressed opens shutdown dialog (Asus X205TA)

[harry]

and with dyndbg==pmf enabled while loading the module:
<7>[  857.237099] i2c_hid:i2c_hid_init_irq: i2c_hid i2c-PDEC3393:00: Requesting 
IRQ: 195
<3>[  868.461393] i2c_hid i2c-PDEC3393:00: failed to reset device.
<3>[  880.840464] i2c_hid i2c-PDEC3393:00: failed to reset device.
<4>[  881.884430] i2c_hid: probe of i2c-PDEC3393:00 failed with error -61

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

Title:
  Any key pressed opens shutdown dialog (Asus X205TA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of 16.10 on my Asus X205TA, any key pressed on
  the built-in keyboard brings up the shutdown dialog. The system works
  fine with a USB keyboard.

  The installed kernel was 4.8.0-34-generic. Booting with
  4.8.0-22-generic, the keyboard works fine.

  Other users have confirmed the bug in Fedora and Tails 
(https://ubuntuforums.org/showthread.php?t=2254322=13594241#post13594241) and 
in 16.10 MATE 
(https://ubuntuforums.org/showthread.php?t=2254322=13594617#post13594617).
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 8087:07e6 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X205TA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=05a20fbf-3084-4535-bae3-bed719df662c ro quiet splash 
intel_max.idle_cstate=1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X205TA.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X205TA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X205TA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=94efdbb7-8cb5-442c-8a16-5fbe6fbf4959
  InstallationDate: Installed on 2017-01-16 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 001 Device 005: ID 413c:2101 Dell Computer Corp. SmartCard Reader 
Keyboard
   Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 8087:07e6 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X205TA
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=/dev/mmcblk1p2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X205TA.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X205TA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  

[Kernel-packages] [Bug 1634881] Re: Installation/Live-System freezes on Splash screen

[DasJott]

Tried the 14.04.2 which works correctly. The 14.04.5 does the same bug.

So I guess the Kernel 4.x is broke for Lenovo. And Canonical does not
care at all.

What does Priority "high" even mean? No progress since October 2016 and
all Lenovo Yoga 3 Notebooks keep Linux free...

A shame.

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

Title:
  Installation/Live-System freezes on Splash screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A USB Stick prepared with 16.04.1 no matter whether "Try Ubuntu" or
  "Install" is chosen, it freezes on splash-Screen.

  With "quiet splash" removed, I get the output on the picture attached.

  In the last line it says: "BUG  Can't handle kernel"

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

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

[Kernel-packages] [Bug 1655101] Re: [Feature] UbuntuKVM: Add and enable seccomp mode 2 in kernel

[Leann Ogasawara]

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

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

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  [Feature] UbuntuKVM: Add and enable seccomp mode 2 in kernel

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Feature] add and enable seccomp in kernel

  == Comment: #6 - Leonardo Augusto Guimaraes Garcia  - 
2016-08-30 13:37:40 ==
  My understanding is that all patches required for seccomp enablement in 
kernel are available in kernel 4.8 which will be used in Ubuntu 16.10. However, 
iiuc, we need some build config options to be enabled.

  == Comment: #7 - Michael T. Strosaker  - 2016-09-19 
17:04:51 ==
  Support has been available upstream since 4.3, if memory serves.  The 16.10 
kernel config should include CONFIG_SECCOMP_FILTER=y if it does not already 
(HAVE_ARCH_SECCOMP_FILTER is required for CONFIG_SECCOMP_FILTER to be 
available).

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

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

[Kernel-packages] [Bug 1656618] Re: Any key pressed opens shutdown dialog (Asus X205TA)

[harry]

the OOB write fix was submitted in march 2016, so I doubt that has
anything to do with it.

I tried debugging the module i2c_hid (which I'm not accustomed to) and
dug op the following while loading the module and reading /proc/kmsg
simultaneously (on kernel 4.10-rc1):

<3>[  299.249790] i2c_hid i2c-PDEC3393:00: failed to reset device.
<3>[  305.439747] i2c_hid i2c-PDEC3393:00: failed to reset device.
<3>[  318.832237] i2c_hid i2c-PDEC3393:00: can't add hid device: -61

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

Title:
  Any key pressed opens shutdown dialog (Asus X205TA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of 16.10 on my Asus X205TA, any key pressed on
  the built-in keyboard brings up the shutdown dialog. The system works
  fine with a USB keyboard.

  The installed kernel was 4.8.0-34-generic. Booting with
  4.8.0-22-generic, the keyboard works fine.

  Other users have confirmed the bug in Fedora and Tails 
(https://ubuntuforums.org/showthread.php?t=2254322=13594241#post13594241) and 
in 16.10 MATE 
(https://ubuntuforums.org/showthread.php?t=2254322=13594617#post13594617).
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 8087:07e6 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X205TA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=05a20fbf-3084-4535-bae3-bed719df662c ro quiet splash 
intel_max.idle_cstate=1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X205TA.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X205TA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X205TA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=94efdbb7-8cb5-442c-8a16-5fbe6fbf4959
  InstallationDate: Installed on 2017-01-16 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 001 Device 005: ID 413c:2101 Dell Computer Corp. SmartCard Reader 
Keyboard
   Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 8087:07e6 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X205TA
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=/dev/mmcblk1p2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X205TA.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X205TA
  dmi.board.vendor: 

[Kernel-packages] [Bug 1657540] Re: [Hyper-V] netvsc: add rcu_read locked to netvsc callback

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2017-January/081900.html

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  [Hyper-V] netvsc: add rcu_read locked to netvsc callback

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

Bug description:
  Please add the following upstream commit (and its prerequisites) for
  SR-IOV on Azure:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0719e72ccb801829a3d735d187ca8417f0930459

  author
  stephen hemminger 
  2017-01-11 17:16:32 (GMT)
  committer
  David S. Miller 
  2017-01-11 21:13:53 (GMT)
  commit
  0719e72ccb801829a3d735d187ca8417f0930459 (patch)
  tree
  a4f718fefcb15433fa59f6d4add44ae220edb806
  parent
  4ecb1d83f6abe8d49163427f4d431ebe98f8bd5f (diff)
  netvsc: add rcu_read locking to netvsc callback
  The receive callback (in tasklet context) is using RCU to get reference
  to associated VF network device but this is not safe. RCU read lock
  needs to be held. Found by running with full lockdep debugging
  enabled.

  Fixes: f207c10d9823 ("hv_netvsc: use RCU to protect vf_netdev")
  Signed-off-by: Stephen Hemminger 
  Signed-off-by: David S. Miller 

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

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

[Kernel-packages] [Bug 1657540] Re: [Hyper-V] netvsc: add rcu_read locked to netvsc callback

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2017-January/081901.html

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  [Hyper-V] netvsc: add rcu_read locked to netvsc callback

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

Bug description:
  Please add the following upstream commit (and its prerequisites) for
  SR-IOV on Azure:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0719e72ccb801829a3d735d187ca8417f0930459

  author
  stephen hemminger 
  2017-01-11 17:16:32 (GMT)
  committer
  David S. Miller 
  2017-01-11 21:13:53 (GMT)
  commit
  0719e72ccb801829a3d735d187ca8417f0930459 (patch)
  tree
  a4f718fefcb15433fa59f6d4add44ae220edb806
  parent
  4ecb1d83f6abe8d49163427f4d431ebe98f8bd5f (diff)
  netvsc: add rcu_read locking to netvsc callback
  The receive callback (in tasklet context) is using RCU to get reference
  to associated VF network device but this is not safe. RCU read lock
  needs to be held. Found by running with full lockdep debugging
  enabled.

  Fixes: f207c10d9823 ("hv_netvsc: use RCU to protect vf_netdev")
  Signed-off-by: Stephen Hemminger 
  Signed-off-by: David S. Miller 

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

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

[Kernel-packages] [Bug 1605974] Re: usbduxsigma_firmware.bin: old version causes driver crash

[Bernd Porr]

Tested:
linux-firmware_1.157.8_all.deb
from xenial proposed and it works!
Bug fixed!


** Tags added: verification-done

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

Title:
  usbduxsigma_firmware.bin: old version causes driver crash

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

Bug description:
  SRU Justification

  Impact: The usbduxsigma firmware is out of date and causes the driver
  to fail. This is fixed by updating the firmware from upstream linux-
  firmware.

  Test Case: Using the driver with the old firmware fails. Using it with
  the new firmware does not.

  Regression potential: The firmware is only used by the one driver so
  there is no potential for regression anywhere else, and the driver
  already isn't working with the old firmware.

  ---

  The firmware of the usbduxsigma (alongside with the usbduxsigma.c) was
  updated in 2015 during a major rewrite but its binary was still the
  old one which causes the kernel driver to fail.

  I've submitted a patch to the kernel people (see below).

  However, as a quick fix could you also apply the patch to the package
  directly to have this fixed now and then we can wait until it trickles
  down from the kernel.

  I'm the maintainer of both the firmware and the drivers.

  This affects both 32 and 64 bit distros.

  Best,
  /Bernd Porr (www.linux-usb-daq.co.uk)

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  linux-firmware:
    Installed: 1.157.2
    Candidate: 1.157.2
    Version table:
   *** 1.157.2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  Expect to happen: plug in a duxduxsigma device, start comedirecord and see 
the signals plotted
  Happens instead: plug in a duxduxsigma device, start comedirecord and GARBLED 
DATA shows up / crash
  Fix: install this patch (new version of the firmware binary)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.2 [modified: 
lib/firmware/usbduxsigma_firmware.bin]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 24 10:04:19 2016
  Dependencies:

  InstallationDate: Installed on 2013-12-09 (957 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131209)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to xenial on 2016-07-23 (0 days ago)

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

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

[Kernel-packages] [Bug 1657488] Re: Please merge crash version 7.1.7-1 (main) from debian sid

[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 crash in Ubuntu.
https://bugs.launchpad.net/bugs/1657488

Title:
  Please merge crash version 7.1.7-1 (main) from debian sid

Status in crash package in Ubuntu:
  Confirmed

Bug description:
  merge bug

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

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

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

[Mike Rushton]

4.10 RC3 gives a kernel panic:

[3.863436] ahci 0009:04:00.0: AHCI 0001. 32 slots 4 ports 6 Gbps 0xf 
impl SATA mode
[3.863631] ahci 0009:04:00.0: flags: 64bit ncq sntf led only pmp fbs pio 
slum part sxs 
[3.864221] scsi host0: ahci
[3.864404] scsi host1: ahci
[3.864562] scsi host2: ahci
[3.864715] scsi host3: ahci
[3.864781] ata1: SATA max UDMA/133 abar m2048@0x3fe28081 port 
0x3fe280810100 irq 447
[3.864826] ata2: SATA max UDMA/133 abar m2048@0x3fe28081 port 
0x3fe280810180 irq 447
[3.864871] ata3: SATA max UDMA/133 abar m2048@0x3fe28081 port 
0x3fe280810200 irq 447
[3.864917] ata4: SATA max UDMA/133 abar m2048@0x3fe28081 port 
0x3fe280810280 irq 447
[3.869801] [drm] platform has no IO space, trying MMIO
[3.869832] [drm] AST 2400 detected
[3.869863] [drm] Analog VGA only
[3.869896] [drm] dram 163200 7 16 00c0
[3.869970] [TTM] Zone  kernel: Available graphics memory: 267838144 kiB
[3.870007] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[3.870044] [TTM] Initializing pool allocator
[3.870076] [TTM] Initializing DMA pool allocator
[3.874823] fb: switching to astdrmfb from OFfb vga
[3.874938] Console: switching to colour dummy device 80x25
[3.899718] nouveau 0002:01:00.0: enabling device (0140 -> 0142)
[3.928774] Kernel panic - not syncing: stack-protector: Kernel stack is 
corrupted in: c02ad0d4
[3.928774] 
[3.928776] CPU: 11 PID: 1118 Comm: systemd-udevd Not tainted 4.10.0-041000r

-- 
You 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) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

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

Bug description:
  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: 

[Kernel-packages] [Bug 1657539] Re: [Hyper-V] mkfs regression in 4.10 fixed by patch in "for-4.11"

[Tim Gardner]

Applied to unstable (which will eventually become Zesty)

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  [Hyper-V] mkfs regression in 4.10 fixed by patch in "for-4.11"

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

Bug description:
  Linux-next testing with upstream identified a regression with mkfs
  operations based on an uptream patch accepted into Linus's tree.
  Please consider this commit that corrects the regression:

  https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-4.11/block=729204ef49ec00b788ce23deb9eb922a5769f55d

  author
  Ming Lei 
  2016-12-17 10:49:09 (GMT)
  committer
  Jens Axboe 
  2017-01-12 03:47:08 (GMT)
  commit
  729204ef49ec00b788ce23deb9eb922a5769f55d (patch)
  tree
  ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3
  parent
  1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff)
  block: relax check on sg gap
  If the last bvec of the 1st bio and the 1st bvec of the next
  bio are physically contigious, and the latter can be merged
  to last segment of the 1st bio, we should think they don't
  violate sg gap(or virt boundary) limit.

  Both Vitaly and Dexuan reported lots of unmergeable small bios
  are observed when running mkfs on Hyper-V virtual storage, and
  performance becomes quite low. This patch fixes that performance
  issue.

  The same issue should exist on NVMe, since it sets virt boundary too.

  Reported-by: Vitaly Kuznetsov 
  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Cc: Keith Busch 
  Signed-off-by: Ming Lei 
  Signed-off-by: Jens Axboe 

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

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

[Kernel-packages] [Bug 1657430] Re: linux: 4.4.0-62.83 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-signed
   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/1657430

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1657430] Re: linux: 4.4.0-62.83 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   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/1657430

Title:
  linux: 4.4.0-62.83 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-62.83 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 18. January 2017 11:48 UTC

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1657540] Re: [Hyper-V] netvsc: add rcu_read locked to netvsc callback

[Joseph Salisbury]

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

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

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

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

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

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

** Tags added: kernel-da-key kernel-hyper-v xenial yakkety 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/1657540

Title:
  [Hyper-V] netvsc: add rcu_read locked to netvsc callback

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

Bug description:
  Please add the following upstream commit (and its prerequisites) for
  SR-IOV on Azure:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0719e72ccb801829a3d735d187ca8417f0930459

  author
  stephen hemminger 
  2017-01-11 17:16:32 (GMT)
  committer
  David S. Miller 
  2017-01-11 21:13:53 (GMT)
  commit
  0719e72ccb801829a3d735d187ca8417f0930459 (patch)
  tree
  a4f718fefcb15433fa59f6d4add44ae220edb806
  parent
  4ecb1d83f6abe8d49163427f4d431ebe98f8bd5f (diff)
  netvsc: add rcu_read locking to netvsc callback
  The receive callback (in tasklet context) is using RCU to get reference
  to associated VF network device but this is not safe. RCU read lock
  needs to be held. Found by running with full lockdep debugging
  enabled.

  Fixes: f207c10d9823 ("hv_netvsc: use RCU to protect vf_netdev")
  Signed-off-by: Stephen Hemminger 
  Signed-off-by: David S. Miller 

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

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

[Kernel-packages] [Bug 1560482] Re: perf: 24x7: Eliminate domain name suffix in event names

[John Donnelly]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  perf: 24x7: Eliminate domain name suffix in event names

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

Bug description:
  Events in the 24x7 counters can belong to different domains like
  core, chip, virtual CPU home core, etc. To monitor an event, the
  user must specify the required parameters for the event, which
  include its name, the chip/core on which to monitor the event
  as well as the domain.

  Currently the event is specified to the perf tool as:

  'hv_24x7/HPM_0THRD_NON_IDLE_CCYC__PHYS_CORE,core=1/' \

  where the event name is 'HPM_0THRD_NON_IDLE_CCYC', the suffix
  '__PHYS_CORE' specifies the domain, and 'core=1' specifies the 
  core. This is inconsistent in that one parameter is specified
  as a suffix and the other in a parameter=value format.

  To simplify the usage, we can eliminate the suffix and let the 
  user specify the domain also in the param=value format. While
  the domain indices are "well known" or nearly fixed in value,
  we could display the domain indices in sysfs as a reference for 
  the users:

  $ cat /sys/bus/event_source/devices/hv_24x7/interface/domains
  1: Physical Chip
  2: Physical Core
  3: VCPU Home Core
  4: VCPU Home Chip
  5: VCPU Home Node
  6: VCPU Remote Node

  Using these the perf event can now be identified as

  hv_24x7/HPM_0THRD_NON_IDLE_CCYC,domain=2,core=1

  . This feature is implemented by the following commits which have now
  been merged into mainline:

  d34171e: powerpc/perf/hv-24x7: Display domain indices in sysfs
  8f69dc7: powerpc/perf/24x7: Eliminate domain suffix in event names

  == Comment: #1 - Sukadev Bhattiprolu  - 2016-03-21 15:26:33 
==
  Following two upstream commits are also related 24x7 and could
  be included in this feature:

  e5a5886: powerpc/perf/hv-24x7: Fix usage with chip events.
  2b206ee: powerpc/perf/hv-24x7: Display change in counter values

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

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

[Kernel-packages] [Bug 1635177] Re: mfd: intel-lpss: Add default I2C device properties for Apollo Lake

[John Donnelly]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  mfd: intel-lpss: Add default I2C device properties for Apollo Lake

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  We need this patch for all Apollo Lake platforms for enabling the touchpad.
  This patch was cherry-picked from c50cdd62dda3f885c1e6ca8b3d5a0851c911ec54. 
And later backported to 4.4 kernel.
  It is because for Apollo Lake, the default freq/falling-time is incorrect. So 
it makes the i2c acts weird.

  Please consider SRU this commit.

  Impact:
All touchpad on Apollo Lake work unstable on i2c mode. Sometimes it will
  
fallback to PS/2 mode and lost some functionality.  
  
  Fix:
    touchpad works good on i2c mode.

  Tested:
    The patch is tested on many Dell ApolloLake laptops and works good.

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

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

[Kernel-packages] [Bug 1634129] Re: Couldn't emulate instruction 0x7813427c

[John Donnelly]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  Couldn't emulate instruction 0x7813427c

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

Bug description:
  Couldn't emulate instruction 0x7813427c
  ---

  Cannot boot nested VMs in Xenial or Yakkety w/ kvm accel.
  It worked until Vivid (in spite of not being possible in x86)
  TCG mode works fine, but very slow.

  TCG full emulation is the mode in the x86 world for nested virt.
  However, in Power, we've been using in OpenStack CI w/ kvm accel
  (native virtualization) to speed up 2nd level VMs. It worked until
  Vivid.

  Is the case that kvm accel isn't possible anymore for nested virt
  (aligned with x86 KVM) ? So full emulation TCG mode is the only
  possible mode in newer kernels ?

  qemu-system-ppc64le -machine pseries,accel=kvm,usb=off -m 1G -enable-
  kvm -cpu POWER8E -display none -nographic cirros-d161007-ppc64le-
  disk.img

  lsmod |grep kvm
  kvm_pr 96452  1
  kvm   152984  4 kvm_pr

  
  Nested VM console:

  OF stdout device is: /vdevice/vty@7100
  Preparing to boot Linux version 4.4.0-28-generic (buildd@bos01-ppc64el-018) 
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #47-Ubuntu SMP Fri 
Jun 24 10:09:20 UTC 2016 (Ubuntu 4.4.0-28.47-generic 4.4.13)
  Detected machine type: 0101
  Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-4.4.0-28-generic LABEL=cirros-rootfs ro
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0421
alloc_top: 1000
alloc_top_hi : 4000
rmo_top  : 1000
ram_top  : 4000
  found display   : /pci@8002000/vga@0, opening... done
  instantiating rtas at 0x0daf... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0422 -> 0x04220aa9
  Device tree struct  0x0423 -> 0x0424
  Quiescing Open Firmware ...
  Booting Linux via __start() ?

  


  /var/log/syslog & /var/log/kern.log

  Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.186975] 
kvmppc_handle_exit_pr: emulation at 700 failed (7813427c)
  Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187023] Couldn't emulate 
instruction 0x7813427c (op 30 xop 318)
  Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187066] 
kvmppc_handle_exit_pr: emulation at 700 failed (7813427c)
  Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187113] Couldn't emulate 
instruction 0x7813427c (op 30 xop 318)
  Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187156] 
kvmppc_handle_exit_pr: emulation at 700 failed (7813427c)

  

  Host:
  cpu   : POWER8E (raw), altivec supported
  clock : 3690.00MHz
  revision  : 2.1 (pvr 004b 0201)

  timebase  : 51200
  platform  : PowerNV
  model : 8247-22L
  machine   : PowerNV 8247-22L
  firmware  : OPAL v3

  
  Guest: Xenial or Yakkety
  Description: Ubuntu 16.10
  Release: 16.10
  Codename: yakkety

  Nested VM:
  CirrOS
  
http://download.cirros-cloud.net/daily/20161007/cirros-d161007-ppc64le-disk.img

  
  This seems to be related
  https://patchwork.kernel.org/patch/9121881/

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

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

[Kernel-packages] [Bug 1654497] Re: ACPI probe support for AD5592/3 configurable multi-channel converter

[John Donnelly]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  ACPI probe support for AD5592/3 configurable multi-channel converter

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

Bug description:
  ACPI probe support for AD5592/3 configurable multi-channel converter
  in Ubuntu kernel.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1652018] Re: PowerNV: PCI Slot is invalid after fencedPHB Error injection

[John Donnelly]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  PowerNV: PCI Slot is invalid after fencedPHB Error injection

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

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2016-12-21 
01:16:41 ==
  ---Problem Description---
  PCI Slot is in invalid state after fencedPHB Error injection Test.
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux brigstrat1p1 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:46:13 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV CSE-829U 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot the system to runtime.
  2. Inject fencedPHB Error.
  echo 0x8000 > /sys/kernel/debug/powerpc/PCI0002/err_injct_outbound

  
  dmesg:
  [42725.641368] EEH: PHB#2 failure detected, location: N/A
  [42725.641450] CPU: 8 PID: 898 Comm: kworker/u320:1 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [42725.641461] Workqueue: i40e i40e_service_task [i40e]
  [42725.641464] Call Trace:
  [42725.641469] [c407f9e0] [c0b13b4c] dump_stack+0xb0/0xf0 
(unreliable)
  [42725.641474] [c407fa20] [c00376e0] 
eeh_dev_check_failure+0x200/0x580
  [42725.641477] [c407fac0] [c0037ae4] 
eeh_check_failure+0x84/0xd0
  [42725.641485] [c407fb00] [d00035845710] 
i40e_service_task+0x17b0/0x1a30 [i40e]
  [42725.641489] [c407fc50] [c00dde10] 
process_one_work+0x1e0/0x5a0
  [42725.641492] [c407fce0] [c00de364] worker_thread+0x194/0x680
  [42725.641496] [c407fd80] [c00e6e60] kthread+0x110/0x130
  [42725.641499] [c407fe30] [c0009538] 
ret_from_kernel_thread+0x5c/0xa4
  [42725.641509] EEH: Detected error on PHB#2
  [42725.641514] EEH: This PCI device has failed 1 times in the last hour
  [42725.641516] EEH: Notify device drivers to shutdown
  [42725.641523] i40e 0002:01:00.0: i40e_pci_error_detected: error 2
  [42725.641907] i40e 0002:01:00.0: VSI seid 396 Tx ring 0 disable timeout
  [42725.642144] i40e 0002:01:00.0: VSI seid 396 Rx ring 0 disable timeout
  [42725.666205] i40e 0002:01:00.1: i40e_pci_error_detected: error 2
  [42725.666499] i40e 0002:01:00.2: i40e_pci_error_detected: error 2
  [42725.666533] i40e 0002:01:00.0: ARQ event error -32
  [42725.01] i40e 0002:01:00.3: i40e_pci_error_detected: error 2
  [42725.666700] EEH: Collect temporary log
  [42725.666702] PHB3 PHB#2 Diag-data (Version: 1)
  [42725.666703] brdgCtl: 
  [42725.666704] UtlSts:  0010  
  [42725.666706] RootSts:     
  [42725.666707] RootErrSts:    
  [42725.666708] RootErrLog:     
  [42725.666709] RootErrLog1:   
  [42725.666711] nFir:8080 0030006e 8000
  [42725.666712] PhbSts:  0018 0018
  [42725.666713] Lem: 8280 42498e367f502eae 8000
  [42725.666715] OutErr:  8020 8000 
12080063fffe 402002a8
  [42725.666716] InBErr:  4000 4000 
0800 000c10c01001
  [42725.666718] EEH: Reset without hotplug activity
  [42730.052455] EEH: Notify device drivers the completion of reset
  [42730.053334] EEH: Notify device driver to resume
  [42730.184457] i40e 0002:01:00.0 enP2p1s0f0: NIC Link is Down
  [42731.568230] i40e 0002:01:00.0 enP2p1s0f0: NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: None

  
  OPAL LOG:
  [42990.475630456,7] PHB#0002: CRESET: Starts
  [42990.482717333,7] PHB#0002: CRESET: No pending transactions
  [42991.023963215,7] PHB#0002: CRESET: Reinitialization
  [42991.023964143,7] PHB#0002: Initializing PHB...
  [42991.075167078,7] PHB#0002: Core revision 0xa30005
  [42991.075171529,7] PHB#0002: Default system config: 0x421100fc3000
  [42991.075172655,7] PHB#0002: New system config: 0x421000fc3000
  

[Kernel-packages] [Bug 1651322] Re: VMX module autoloading if available

[John Donnelly]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  VMX module autoloading if available

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

Bug description:
  Problem Description
  
  This two commits provide the support for VMX autoload if supported by the 
machine. Nowadays the module needs to be loaded manually.

  4a12027 powerpc: Add module autoloading based on CPU features
  ccf5c44 crypto: vmx - Convert to CPU feature based module autoloading

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

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

[Kernel-packages] [Bug 1639810] Re: igb i210 probe of pci device failed with error -2

[John Donnelly]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  igb i210 probe of pci device failed with error -2

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

Bug description:
  [Impact]

  Intel I210 NIC may show:
  'igb: probe of :07:00.0 failed with error -2'
  Upon boot after power has been completely disconnected.

  I was able to bisect it down to commit 
2a3cdead8b408351fa1e3079b220fa331480ffbc
  Upon further investigation it was determined that firmware may not properly 
initialize I347AT4_PAGE_SELECT causing the probe of an igb i210 NIC to fail. 

  This also happens with the linux 4.9-rc4.

  [Fix]

  https://patchwork.ozlabs.org/patch/690464/
  This patch adds an addition zeroing of this register during igb_get_phy_id to 
workaround this issue.

  [Test Case]

  Completely power down machine with intel igb 210 NIC. Power on and
  ensure igb device is properly probed and initialized.

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

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

[Kernel-packages] [Bug 1655040] Re: i386 ftrace tests hang on ADT testing

[John Donnelly]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  i386 ftrace tests hang on ADT testing

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

Bug description:
  == SRU REQUEST, XENIAL, YAKKETY + ZESTY ==

  Running the autotest client ubuntu_kernel_selftests tests hang on i386
  because of a bug in the ftracing, resolved with upstream fix:

  commit 847fa1a6d3d00f3bdf68ef5fa4a786f644a0dd67
  ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short jumps 
to it

  Although these have fixes ready to come down into -stable, lets SRU
  these in sooner than later.

  == Test ==

  Without the fix, the i386 kernel self tests always hang on the
  ftracing tests.  With the fix, it works perfectly.

  == Regression potential ==

  Minimal, this is a tried and tested patch, plus it matches the  fixes
  in the amd64 paths that were not ported over to the i386 paths which
  this fix now addresses.

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

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

[Kernel-packages] [Bug 1650336] Re: NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

[Thomas Fili]

When you ask if the kernel 4.10-rc4 do not crash any long on boot time,
then i can answer : Yes, the kernel do not crash any longer.

But when you ask if the kernel 4.10-rc4 work as expected with nfs

Then i can answer No, he do not work as expected with nfs shares.

IMHO the mainline kernel 4.9.4 work as expeced ;)

But maybe you think there are different parts in the kernel responsibly
for this hehaviour ?

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

Title:
  NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

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

Bug description:
  On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel
  crash on boot when in /etc/fstab a nfsv4 entry is active

  When comment the line or set to noauto the kernel boot with no error
  and mounting the nfs shares (after uncomment ) is also possible
  without error

  4.4.0-54 boots without this problem.

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

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

[Kernel-packages] [Bug 1433906] Re: Acer, Inc ID 5986:055a is useless after 14.04.2 installed.

[Sebastiano]

It is working perfectly on my Lenovo Thinkpad E450. Thank you very much.

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

Title:
  Acer, Inc ID 5986:055a is useless after 14.04.2 installed.

Status in HWE Next:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-vivid package in Ubuntu:
  Triaged
Status in linux-lts-xenial package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux-lts-vivid source package in Yakkety:
  Confirmed
Status in linux-lts-xenial source package in Yakkety:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in Fedora:
  Unknown

Bug description:
  CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic)
  CID : 201408-15472 Lenovo E555 (A+A) with 14.04.2 (utopic)

  Steps:
  1. Install 14.04.2 on E450 or E555.
  2. Log in system and open a terminal.
  3. $ gst-launch-0.10 v4l2src ! xvimagesink

  Expected result:
  Camara is activated

  Actual result:
  $  gst-launch-0.10 v4l2src ! xvimagesink
  Setting pipeline to PAUSED ...
  ERROR: Pipeline doesn't want to pause.
  ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Cannot 
identify device '/dev/video0'.
  Additional debug info:
  v4l2_calls.c(497): gst_v4l2_open (): 
/GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
  system error: No such file or directory
  Setting pipeline to NULL ...
  Freeing pipeline ...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: 
boot/vmlinuz-3.16.0-30-generic]
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 19 02:21:31 2015
  InstallationDate: Installed on 2015-03-16 (2 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1657539] Re: [Hyper-V] mkfs regression in 4.10 fixed by patch in "for-4.11"

[Joseph Salisbury]

The Zesty kernel is still at 4.9.  We can request this commit in Zesty
when it is rebased to 4.10.

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

** Also affects: linux (Ubuntu Zesty)
   Importance: Medium
   Status: Confirmed

** Tags added: kernel-da-key kernel-hyper-v zesty

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

Title:
  [Hyper-V] mkfs regression in 4.10 fixed by patch in "for-4.11"

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

Bug description:
  Linux-next testing with upstream identified a regression with mkfs
  operations based on an uptream patch accepted into Linus's tree.
  Please consider this commit that corrects the regression:

  https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-4.11/block=729204ef49ec00b788ce23deb9eb922a5769f55d

  author
  Ming Lei 
  2016-12-17 10:49:09 (GMT)
  committer
  Jens Axboe 
  2017-01-12 03:47:08 (GMT)
  commit
  729204ef49ec00b788ce23deb9eb922a5769f55d (patch)
  tree
  ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3
  parent
  1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff)
  block: relax check on sg gap
  If the last bvec of the 1st bio and the 1st bvec of the next
  bio are physically contigious, and the latter can be merged
  to last segment of the 1st bio, we should think they don't
  violate sg gap(or virt boundary) limit.

  Both Vitaly and Dexuan reported lots of unmergeable small bios
  are observed when running mkfs on Hyper-V virtual storage, and
  performance becomes quite low. This patch fixes that performance
  issue.

  The same issue should exist on NVMe, since it sets virt boundary too.

  Reported-by: Vitaly Kuznetsov 
  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Cc: Keith Busch 
  Signed-off-by: Ming Lei 
  Signed-off-by: Jens Axboe 

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

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

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

[Brad Figg]

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

Title:
  Laptop stick and touchpad problems after linux 4.4 update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have 
behaved erratically on my Dell Precision 7510:
  * The trackpoint moves WAY too fast and there don't seem to be any parameters 
I can change in xinput to fix this. It is essentially unusable.
  * The touchpad starts with parameters set incorrectly.
  * Touchpad tap to click is now turned on again and is very sensitive. This I 
can change through xinput but the change is still odd.
  * The two finger scrolling is set incorrectly to be highly sensitive. This I 
can also change through xinput.
  * Two finger scrolling still activates often during normal use of the 
trackpad. To the extent that I had to turn off two finger scrolling to stop 
inadvertent scrolling.

  All of the above behavior is new going from 4.4.0-47 to -53.
  Previously this all worked perfectly on this machine.

  Seems to be symptoms noted by these other users on askubuntu here as
  well: http://askubuntu.com/questions/862527/laptop-stick-mouse-
  problems-after-linux-4-4-update-on-14-04

  The touchpad symptoms I seem to be able to work around my changing
  xinput parameters, but the trackpoint I have not been able to fix at
  all (which is sad since that is my primary mouse device normally).
  Would appreciate any suggestions as to how to revert the old behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpeverill   2813 F pulseaudio
   /dev/snd/controlC0:  jpeverill   2813 F pulseaudio
  Date: Wed Jan 18 10:21:55 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-17 (916 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
  dmi.bios.date: 01/24/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1598312] Re: Cannot scale AMD Turion CPU frequency. It runs on lowest 800MHz

[Joseph Salisbury]

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

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

Title:
  Cannot scale AMD Turion CPU frequency. It runs on lowest 800MHz

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed

Bug description:
  http://askubuntu.com/questions/789096/cant-scale-frequencies-of-amd-
  turion-cpu-it-always-jumps-to-lowest

  The CPU does not scale frequency on kernel "4.2.0-41-generic
  #48~14.04.1-Ubuntu SMP Fri Jun 24 17:09:15". The notebook behaves very
  slow despite on Windows Vista it works great.

  Cpufreq-info program shows that there is a limit on the frequency setting 
between 800MHz and 800MHz. I tried to impose the frequency by setting the 
"performance policy" or by setting the limit in /etc/default/cpufrequency, but 
it does not work. 
  Next I tried to check the BIOS limits, because there are some suggestions 
that some battery/power supply problems could cause the BIOS to set the limits 
on CPU freq but it is not there.

  The CPU freq scaling works good on 'linux-image-4.1.26-040126-generic'
  kernel. It does not work on this kernel "4.2.0-41-generic" and "linux-
  headers-4.2.0-38-generic". The current workaround is to switch off the
  ACPI by "acpi=off" boot parameter. Using this setting the CPU
  frequency scaling works but it makes the system single CPU core only.

  Hardware: HP Compaq 6715B notebook with AMD Turion CPU TL-58 and
  powernow-k8 cpufreq driver. I've heard some posts that on others HP
  notebooks there are similar problems with the freq scaling.

  
  $ cpufreq-info 
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0 1
maximum transition latency: 109 us.
hardware limits: 800 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 1.80 GHz, 1.60 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, 
performance
current policy: frequency should be within 800 MHz and 800 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.90 GHz:0,07%, 1.80 GHz:0,00%, 1.60 GHz:0,00%, 800 
MHz:99,93%  (1)
  analyzing CPU 1:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0 1
maximum transition latency: 109 us.
hardware limits: 800 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 1.80 GHz, 1.60 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, 
performance
current policy: frequency should be within 800 MHz and 800 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.90 GHz:0,07%, 1.80 GHz:0,00%, 1.60 GHz:0,00%, 800 
MHz:99,93%  (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-41-generic 4.2.0-41.48~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  Uname: Linux 4.2.0-41-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jul  1 23:49:34 2016
  InstallationDate: Installed on 2016-04-08 (83 days ago)
  InstallationMedia: Kubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1657540] Re: [Hyper-V] netvsc: add rcu_read locked to netvsc callback

[Brad Figg]

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

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

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

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

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

Title:
  [Hyper-V] netvsc: add rcu_read locked to netvsc callback

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

Bug description:
  Please add the following upstream commit (and its prerequisites) for
  SR-IOV on Azure:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0719e72ccb801829a3d735d187ca8417f0930459

  author
  stephen hemminger 
  2017-01-11 17:16:32 (GMT)
  committer
  David S. Miller 
  2017-01-11 21:13:53 (GMT)
  commit
  0719e72ccb801829a3d735d187ca8417f0930459 (patch)
  tree
  a4f718fefcb15433fa59f6d4add44ae220edb806
  parent
  4ecb1d83f6abe8d49163427f4d431ebe98f8bd5f (diff)
  netvsc: add rcu_read locking to netvsc callback
  The receive callback (in tasklet context) is using RCU to get reference
  to associated VF network device but this is not safe. RCU read lock
  needs to be held. Found by running with full lockdep debugging
  enabled.

  Fixes: f207c10d9823 ("hv_netvsc: use RCU to protect vf_netdev")
  Signed-off-by: Stephen Hemminger 
  Signed-off-by: David S. Miller 

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

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

[Kernel-packages] [Bug 1655260] Re: Kernel freezes

[Joseph Salisbury]

That is good news.  The Xenial kernel does not yet have the 4.4.42
updates, but it now has up to the 4.4.40 updates.

Would it be possible for you to test this latest kernel and post back if it 
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
enable and use -proposed. 

Thank you in advance!

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

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

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

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

Title:
  Kernel freezes

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

Bug description:
  Background info:
  - I'm using Ubuntu 16.04.1 LTS with kernel 4.4.0-57-generic, with i3wm and 
couple of terminals plus a web browser running on it.

  What happens:
  - On random time intervals the OS freezes and I don't have mouse, nor 
keyboard responding. The only thing I can do is cold restart. Searching through 
the syslog, I've got the following:

  Please see the attached file for more information.

  Best Regards,
  Viktor Penkov

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   viktor 2809 F...m pulseaudio
   /dev/snd/controlC1:  viktor 2809 F pulseaudio
   /dev/snd/controlC0:  viktor 2809 F pulseaudio
  Date: Tue Jan 10 09:56:27 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d88c0a8e-3bfa-400e-a3fe-cb7d6cd262c9
  InstallationDate: Installed on 2016-01-06 (369 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: LENOVO 20BV003SBM
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV003SBM
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BV003SBM:pvrThinkPadT450:rvnLENOVO:rn20BV003SBM:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV003SBM
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1657553] [NEW] Laptop stick and touchpad problems after linux 4.4 update

[arsenix]

Public bug reported:

Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have behaved 
erratically on my Dell Precision 7510:
* The trackpoint moves WAY too fast and there don't seem to be any parameters I 
can change in xinput to fix this. It is essentially unusable.
* The touchpad starts with parameters set incorrectly.
* Touchpad tap to click is now turned on again and is very sensitive. This I 
can change through xinput but the change is still odd.
* The two finger scrolling is set incorrectly to be highly sensitive. This I 
can also change through xinput.
* Two finger scrolling still activates often during normal use of the trackpad. 
To the extent that I had to turn off two finger scrolling to stop inadvertent 
scrolling.

All of the above behavior is new going from 4.4.0-47 to -53. Previously
this all worked perfectly on this machine.

Seems to be symptoms noted by these other users on askubuntu here as
well: http://askubuntu.com/questions/862527/laptop-stick-mouse-problems-
after-linux-4-4-update-on-14-04

The touchpad symptoms I seem to be able to work around my changing
xinput parameters, but the trackpoint I have not been able to fix at all
(which is sad since that is my primary mouse device normally). Would
appreciate any suggestions as to how to revert the old behavior.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-53-generic 4.4.0-53.74
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jpeverill   2813 F pulseaudio
 /dev/snd/controlC0:  jpeverill   2813 F pulseaudio
Date: Wed Jan 18 10:21:55 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-07-17 (916 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. 
 Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 7510
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-59-generic N/A
 linux-backports-modules-4.4.0-59-generic  N/A
 linux-firmware1.157.6
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
dmi.bios.date: 01/24/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.10
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision 7510
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Laptop stick and touchpad problems after linux 4.4 update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have 
behaved erratically on my Dell Precision 7510:
  * The trackpoint moves WAY too fast and there don't seem to be any parameters 
I can change in xinput to fix this. It is essentially unusable.
  * The touchpad starts with parameters set incorrectly.
  * Touchpad tap to click is now turned on again and is very sensitive. This I 
can change through xinput but the change is still odd.
  * The two finger scrolling is set incorrectly to be highly sensitive. This I 
can also change through xinput.
  * Two finger scrolling still activates often during normal use of the 
trackpad. To the extent that I had to turn off two finger scrolling to stop 
inadvertent scrolling.

  All of the above behavior is new going from 4.4.0-47 to -53.
  Previously this all worked perfectly on this machine.

  Seems to be symptoms noted by these other users on askubuntu here as
  well: http://askubuntu.com/questions/862527/laptop-stick-mouse-
  problems-after-linux-4-4-update-on-14-04

  The touchpad symptoms I seem to be able to work around my changing
  xinput parameters, but the trackpoint I have not been able to fix at
  all (which is sad since that is my primary mouse device normally).
  Would appreciate any suggestions as to how to revert the old behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 

[Kernel-packages] [Bug 1635447] Re: Upgraded or Live USB 16.10 hangs at boot up blank purple screen

[Joseph Salisbury]

@kjellahl, you may want to open a new bug report.

@renm, thanks for testing.  We can perform a "Reverse" bisect to
identify the commit that fixes this bug.  We first need to identify the
last kernel that had the bug and the first kernel version that did not.

Can you test the following kernels:

4.9 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/
4.10-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/

** Tags added: performing-bisect

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

Title:
  Upgraded or Live USB 16.10 hangs at boot up blank purple screen

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

Bug description:
  My HP dm3z-2000 laptop works out of box for everything with Ubuntu
  16.04, but fails to boot up after upgraded to 16.10. The upgrading
  went smooth itself.

  Laptop still can boot up with the latest 4.4 kernel of 16.04 which I
  did a regular update/upgrade before 16.10 release upgrade.

  Then I tried to boot with 16.10 Live USB and got same result.

  It also can boot up with kernel 4.8 if "acpi=off" parameter in place,
  but it takes long time to boot up. Everything seems fine after logged
  in and Unity 8 session works too.

  I couldn't get any log files since the system won't boot up,
  Ctrl+Alt+F1 does nothing. I can only see some messages in text boot
  mode, so I took a screen shot with my phone and attached here.

  Let me know how to get more details.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  renm   2918 F pulseaudio
   /dev/snd/controlC1:  renm   2918 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7e8ca036-f81d-43e2-820a-1deadcffc2dc
  InstallationDate: Installed on 2016-10-08 (13 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Pavilion dm3t Notebook PC
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=19005996-db50-4249-9c73-17cf874dc678 ro acpi=off
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1482
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd10/13/2010:svnHewlett-Packard:pnHPPaviliondm3tNotebookPC:pvr048620241F0011032:rvnHewlett-Packard:rn1482:rvr76.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm3t Notebook PC
  dmi.product.version: 048620241F0011032
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Rod Smith]

Joseph, the 3.19.0-79.87 kernel boots fine.

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1657540] Missing required logs.

[Brad Figg]

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

apport-collect 1657540

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

Title:
  [Hyper-V] netvsc: add rcu_read locked to netvsc callback

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please add the following upstream commit (and its prerequisites) for
  SR-IOV on Azure:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0719e72ccb801829a3d735d187ca8417f0930459

  author
  stephen hemminger 
  2017-01-11 17:16:32 (GMT)
  committer
  David S. Miller 
  2017-01-11 21:13:53 (GMT)
  commit
  0719e72ccb801829a3d735d187ca8417f0930459 (patch)
  tree
  a4f718fefcb15433fa59f6d4add44ae220edb806
  parent
  4ecb1d83f6abe8d49163427f4d431ebe98f8bd5f (diff)
  netvsc: add rcu_read locking to netvsc callback
  The receive callback (in tasklet context) is using RCU to get reference
  to associated VF network device but this is not safe. RCU read lock
  needs to be held. Found by running with full lockdep debugging
  enabled.

  Fixes: f207c10d9823 ("hv_netvsc: use RCU to protect vf_netdev")
  Signed-off-by: Stephen Hemminger 
  Signed-off-by: David S. Miller 

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

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

[Kernel-packages] [Bug 1657539] Re: [Hyper-V] mkfs regression in 4.10 fixed by patch in "for-4.11"

[Joshua R. Poulson]

No log files, request to include upstream commit.

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

Title:
  [Hyper-V] mkfs regression in 4.10 fixed by patch in "for-4.11"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux-next testing with upstream identified a regression with mkfs
  operations based on an uptream patch accepted into Linus's tree.
  Please consider this commit that corrects the regression:

  https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-4.11/block=729204ef49ec00b788ce23deb9eb922a5769f55d

  author
  Ming Lei 
  2016-12-17 10:49:09 (GMT)
  committer
  Jens Axboe 
  2017-01-12 03:47:08 (GMT)
  commit
  729204ef49ec00b788ce23deb9eb922a5769f55d (patch)
  tree
  ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3
  parent
  1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff)
  block: relax check on sg gap
  If the last bvec of the 1st bio and the 1st bvec of the next
  bio are physically contigious, and the latter can be merged
  to last segment of the 1st bio, we should think they don't
  violate sg gap(or virt boundary) limit.

  Both Vitaly and Dexuan reported lots of unmergeable small bios
  are observed when running mkfs on Hyper-V virtual storage, and
  performance becomes quite low. This patch fixes that performance
  issue.

  The same issue should exist on NVMe, since it sets virt boundary too.

  Reported-by: Vitaly Kuznetsov 
  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Cc: Keith Busch 
  Signed-off-by: Ming Lei 
  Signed-off-by: Jens Axboe 

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

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

[Kernel-packages] [Bug 1657540] Re: [Hyper-V] netvsc: add rcu_read locked to netvsc callback

[Joshua R. Poulson]

No log files, request to include upstream commit.

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

Title:
  [Hyper-V] netvsc: add rcu_read locked to netvsc callback

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please add the following upstream commit (and its prerequisites) for
  SR-IOV on Azure:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0719e72ccb801829a3d735d187ca8417f0930459

  author
  stephen hemminger 
  2017-01-11 17:16:32 (GMT)
  committer
  David S. Miller 
  2017-01-11 21:13:53 (GMT)
  commit
  0719e72ccb801829a3d735d187ca8417f0930459 (patch)
  tree
  a4f718fefcb15433fa59f6d4add44ae220edb806
  parent
  4ecb1d83f6abe8d49163427f4d431ebe98f8bd5f (diff)
  netvsc: add rcu_read locking to netvsc callback
  The receive callback (in tasklet context) is using RCU to get reference
  to associated VF network device but this is not safe. RCU read lock
  needs to be held. Found by running with full lockdep debugging
  enabled.

  Fixes: f207c10d9823 ("hv_netvsc: use RCU to protect vf_netdev")
  Signed-off-by: Stephen Hemminger 
  Signed-off-by: David S. Miller 

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

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

[Kernel-packages] [Bug 1657539] Missing required logs.

[Brad Figg]

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

apport-collect 1657539

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

Title:
  [Hyper-V] mkfs regression in 4.10 fixed by patch in "for-4.11"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux-next testing with upstream identified a regression with mkfs
  operations based on an uptream patch accepted into Linus's tree.
  Please consider this commit that corrects the regression:

  https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-4.11/block=729204ef49ec00b788ce23deb9eb922a5769f55d

  author
  Ming Lei 
  2016-12-17 10:49:09 (GMT)
  committer
  Jens Axboe 
  2017-01-12 03:47:08 (GMT)
  commit
  729204ef49ec00b788ce23deb9eb922a5769f55d (patch)
  tree
  ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3
  parent
  1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff)
  block: relax check on sg gap
  If the last bvec of the 1st bio and the 1st bvec of the next
  bio are physically contigious, and the latter can be merged
  to last segment of the 1st bio, we should think they don't
  violate sg gap(or virt boundary) limit.

  Both Vitaly and Dexuan reported lots of unmergeable small bios
  are observed when running mkfs on Hyper-V virtual storage, and
  performance becomes quite low. This patch fixes that performance
  issue.

  The same issue should exist on NVMe, since it sets virt boundary too.

  Reported-by: Vitaly Kuznetsov 
  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Cc: Keith Busch 
  Signed-off-by: Ming Lei 
  Signed-off-by: Jens Axboe 

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

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

[Kernel-packages] [Bug 1657540] [NEW] [Hyper-V] netvsc: add rcu_read locked to netvsc callback

[Joshua R. Poulson]

Public bug reported:

Please add the following upstream commit (and its prerequisites) for SR-
IOV on Azure:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0719e72ccb801829a3d735d187ca8417f0930459

author
stephen hemminger 
2017-01-11 17:16:32 (GMT)
committer
David S. Miller 
2017-01-11 21:13:53 (GMT)
commit
0719e72ccb801829a3d735d187ca8417f0930459 (patch)
tree
a4f718fefcb15433fa59f6d4add44ae220edb806
parent
4ecb1d83f6abe8d49163427f4d431ebe98f8bd5f (diff)
netvsc: add rcu_read locking to netvsc callback
The receive callback (in tasklet context) is using RCU to get reference
to associated VF network device but this is not safe. RCU read lock
needs to be held. Found by running with full lockdep debugging
enabled.

Fixes: f207c10d9823 ("hv_netvsc: use RCU to protect vf_netdev")
Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller 

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1657540

Title:
  [Hyper-V] netvsc: add rcu_read locked to netvsc callback

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Please add the following upstream commit (and its prerequisites) for
  SR-IOV on Azure:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0719e72ccb801829a3d735d187ca8417f0930459

  author
  stephen hemminger 
  2017-01-11 17:16:32 (GMT)
  committer
  David S. Miller 
  2017-01-11 21:13:53 (GMT)
  commit
  0719e72ccb801829a3d735d187ca8417f0930459 (patch)
  tree
  a4f718fefcb15433fa59f6d4add44ae220edb806
  parent
  4ecb1d83f6abe8d49163427f4d431ebe98f8bd5f (diff)
  netvsc: add rcu_read locking to netvsc callback
  The receive callback (in tasklet context) is using RCU to get reference
  to associated VF network device but this is not safe. RCU read lock
  needs to be held. Found by running with full lockdep debugging
  enabled.

  Fixes: f207c10d9823 ("hv_netvsc: use RCU to protect vf_netdev")
  Signed-off-by: Stephen Hemminger 
  Signed-off-by: David S. Miller 

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

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

[Kernel-packages] [Bug 1657539] [NEW] [Hyper-V] mkfs regression in 4.10 fixed by patch in "for-4.11"

[Joshua R. Poulson]

Public bug reported:

Linux-next testing with upstream identified a regression with mkfs
operations based on an uptream patch accepted into Linus's tree. Please
consider this commit that corrects the regression:

https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
block.git/commit/?h=for-4.11/block=729204ef49ec00b788ce23deb9eb922a5769f55d

author
Ming Lei 
2016-12-17 10:49:09 (GMT)
committer
Jens Axboe 
2017-01-12 03:47:08 (GMT)
commit
729204ef49ec00b788ce23deb9eb922a5769f55d (patch)
tree
ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3
parent
1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff)
block: relax check on sg gap
If the last bvec of the 1st bio and the 1st bvec of the next
bio are physically contigious, and the latter can be merged
to last segment of the 1st bio, we should think they don't
violate sg gap(or virt boundary) limit.

Both Vitaly and Dexuan reported lots of unmergeable small bios
are observed when running mkfs on Hyper-V virtual storage, and
performance becomes quite low. This patch fixes that performance
issue.

The same issue should exist on NVMe, since it sets virt boundary too.

Reported-by: Vitaly Kuznetsov 
Reported-by: Dexuan Cui 
Tested-by: Dexuan Cui 
Cc: Keith Busch 
Signed-off-by: Ming Lei 
Signed-off-by: Jens Axboe 

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1657539

Title:
  [Hyper-V] mkfs regression in 4.10 fixed by patch in "for-4.11"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux-next testing with upstream identified a regression with mkfs
  operations based on an uptream patch accepted into Linus's tree.
  Please consider this commit that corrects the regression:

  https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-4.11/block=729204ef49ec00b788ce23deb9eb922a5769f55d

  author
  Ming Lei 
  2016-12-17 10:49:09 (GMT)
  committer
  Jens Axboe 
  2017-01-12 03:47:08 (GMT)
  commit
  729204ef49ec00b788ce23deb9eb922a5769f55d (patch)
  tree
  ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3
  parent
  1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff)
  block: relax check on sg gap
  If the last bvec of the 1st bio and the 1st bvec of the next
  bio are physically contigious, and the latter can be merged
  to last segment of the 1st bio, we should think they don't
  violate sg gap(or virt boundary) limit.

  Both Vitaly and Dexuan reported lots of unmergeable small bios
  are observed when running mkfs on Hyper-V virtual storage, and
  performance becomes quite low. This patch fixes that performance
  issue.

  The same issue should exist on NVMe, since it sets virt boundary too.

  Reported-by: Vitaly Kuznetsov 
  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Cc: Keith Busch 
  Signed-off-by: Ming Lei 
  Signed-off-by: Jens Axboe 

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

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

[Kernel-packages] [Bug 1650058] Re: [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and image

[Joshua R. Poulson]

Mellanox has pointed me to a repository that has the minimal set of
drivers and utilities needed for SR-IOV (and, eventually, DPDK).
Consider the "mlnx_rdma_minimal" repository, here:
http://linux.mellanox.com/public/repo/mlnx_rdma_minimal/

I am requesting the latest 64-bit drivers and userspace for Azure
images, here:
http://linux.mellanox.com/public/repo/mlnx_rdma_minimal/3.4-2.0.0.0/ubuntu16.04/x86_64/

and here if we want to apply to the yakkety kernel:
http://linux.mellanox.com/public/repo/mlnx_rdma_minimal/3.4-2.0.0.0/ubuntu16.10/x86_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/1650058

Title:
  [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel
  and image

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

Bug description:
  In order to have the correct VF driver to support SR-IOV in Azure, the
  Mellanox OFED distribution needs to be included in the kernel and the
  image. Mellanox's drivers are not upstream, but they are available
  from here:

  
https://www.mellanox.com/page/products_dyn?product_family=26=linux_sw_drivers=3nnhohirh5htv6dnp1uk7tf487

  While this configuration is not explicitly listed as supported in the
  release notes, Microsoft and Mellanox engineers are working on the
  corresponding Windows Server 2016 PF driver to support this VF driver
  in operation in Ubuntu guests.

  I file file a corresponding rebase request to pick up the PCI
  passthrough and other SR-IOV work done for the Hyper-V capabilities in
  the upstream 4.9 kernel.

  Only 64-bit support for Ubuntu 16.04's HWE kernel is needed.

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

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

[Kernel-packages] [Bug 1641078] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From ma...@de.ibm.com 2017-01-18 12:02 EDT---
(In reply to comment #23)
> > (In reply to comment #21)
> >> Installed lpar onto 154d dasd drive, using LVM automatic partitioning 
> >> recipe.
> >> After installation and reipl, I did the following:
> >
> >> $ sudo update-initramfs -u
> >
> > I understand that things work with this explicit call.
>
> How does it work with e.g. dracut? One must regenerate the initramfs
> to activate the additional drive on boot, no?

yes.

> Does one required to call zipl (which calls into dracut to regenerate
> initramfs?!) or does one call dracut?

user sequence (in that order): dracut && zipl.

"update-initramfs -u" includes the final zipl step which is nice.

> > However, users can easily miss this since it's not entirely obvious.
> Regular ubuntu/debian users do know to call update-initramfs -u when
> fiddling/changing rootfs devices (not the most trivial task to be
> honest).
> Same as fedora users know to call dracut. IMHO.

I guess, I've seen too many cases where the user missed this (or a
related) step and therefore I was hoping for an automatic solution.

> Ubuntu uses chzdev, which generates udev rules, and our initramfs
> hooks copy all of the udev rules into the initramfs as udev is running
> in Ubuntu initramfs.

OK, I learned that Ubuntu does not do root-fs dependency tracking of
z-specific device activation udev rules it includes into initramfs.

IIRC, zdev might have such tracking if it was used with dracut instead
of update-initramfs. Maybe that's why I was on a misleading track.

> The boot continues as soon as rootfs is detected to be available. If
> other devices are activated in parallel, it should be mostly harmless.
> And the boot will not wait to activate all the things that udev rules
> specify in the initramfs.
> Thus it's kind of a zero sum game, eventually all chzdev->udev rules
> specified devices will be activated, and it does not matter much if
> some of them are activated from initramfs or post-initramfs.

I've seen it matter, where large installations choked within initramfs
because of processing udev rules (and in turn things such as multipath
events) for all the other (unnecessary) devices.

But that would be a different bug anyway.

> I added the hook in place such that chzdev can call it when it needs to.
>
> But I'm arguing that the hooks that chzdev calls will never be
> sufficient when one decides to move their rootfs, on any Linux.
> Because at initial "chzdev -e" call time the device that is being
> activated is not yet part of the rootfs stack, but will become after
> one e.g. expands lvm / mdadm / btrfs / etc on to it. Does that make
> sense?

It does indeed make sense to me.

> > If the bug is now declared invalid as in "user error", then I'm puzzled 
> > about the reasons for a code change.
>
> a code change was mostly a red-herring

OK, got it. Thanks for making this clear.

So the bug is invalid unless someone finds a solution for the problem
that root-fs dependencies (can) change after any current chzdev hook.

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

Title:
  System cannot be booted up when root filesystem is on an LVM on two
  disks

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  LVMed root file system acrossing multiple disks cannot be booted up 

  ---uname output---
  Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC 2016 
s390x s390x s390x GNU/Linux
   
  ---Patches Installed---
  n/a
   
  Machine Type = z13 
   
  ---System Hang---
   cannot boot up the system after shutdown or reboot
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Created root file system on an LVM and the LVM crosses two disks. After shut 
down or reboot the system, the system cannot be up. 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Device driver error code:
   Begin: Mounting root file system ... Begin: Running /scripts/local-top ...   
lvmetad is not active yet, using direct activation during sysinit 
Couldn't find device with uuid 7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V. 
   
  -Attach sysctl -a output output to the bug.

  More detailed installation description:

  The installation was on a FCP SCSI SAN volumes each with two active
  paths.  Multipath was involved.  The system IPLed fine up to the point
  that we expanded the /root filesystem to span volumes.  At boot time,
  the system was unable to locate the second segment of the /root
  filesystem.   The error message indicated this was due to lvmetad not
  being not active.

  Error message:   
 Begin: Running /scripts/local-block ...   lvmetad is not active yet, 
using direct 

[Kernel-packages] [Bug 1655480] Re: linux-lts-trusty: 3.13.0-108.155~precise1 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the 3.13.0-108.155~precise1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655476
  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/1655480/+subscriptions

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

[Kernel-packages] [Bug 1655476] Re: linux: 3.13.0-108.155 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 3.13.0-108.155 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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 3.13.0-108.155 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
  derivative-trackers-created: 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/1655476/+subscriptions

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

[Kernel-packages] [Bug 1657488] Re: Please merge crash version 7.1.7-1 (main) from debian sid

[Louis Bouchard]

** Patch removed: "debian_7.1.7-1_to_ubuntu_7.1.7-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1657488/+attachment/4805918/+files/debian_7.1.7-1_to_ubuntu_7.1.7-1ubuntu1.debdiff

** Patch added: "ubuntu_7.1.5_to_7.1.7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1657488/+attachment/4805920/+files/ubuntu_7.1.5_to_7.1.7.debdiff

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

Title:
  Please merge crash version 7.1.7-1 (main) from debian sid

Status in crash package in Ubuntu:
  Confirmed

Bug description:
  merge bug

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

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

[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Joseph Salisbury]

This would indicate that the bug was introduced by a SAUCE patch in
Trusty.  We also know that this bug is fixed in Xenial, so there is
another patch that fixes this regression that has not made it into
Trusty.

I think the next step should be to identify the patch in Xenial and
backport it to Trusty.

Can you test the 3.19 based Vivid kernel?  It can be downloaded from:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/11760211

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1657488] Re: Please merge crash version 7.1.7-1 (main) from debian sid

[Louis Bouchard]

** Patch added: "debian_7.1.7-1_to_ubuntu_7.1.7-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1657488/+attachment/4805918/+files/debian_7.1.7-1_to_ubuntu_7.1.7-1ubuntu1.debdiff

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

Title:
  Please merge crash version 7.1.7-1 (main) from debian sid

Status in crash package in Ubuntu:
  Confirmed

Bug description:
  merge bug

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

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

[Kernel-packages] [Bug 1657488] Re: Please merge crash version 7.1.7-1 (main) from debian sid

[Louis Bouchard]

** Patch added: "debian_7.1.7-1_to_ubuntu_7.1.7-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1657488/+attachment/4805917/+files/debian_7.1.7-1_to_ubuntu_7.1.7-1ubuntu1.debdiff

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

Title:
  Please merge crash version 7.1.7-1 (main) from debian sid

Status in crash package in Ubuntu:
  Confirmed

Bug description:
  merge bug

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

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

[Kernel-packages] [Bug 1657367] Re: Intel-based ethernet interfaces can't detect link state

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc4


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

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

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

Title:
  Intel-based ethernet interfaces can't detect link state

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have number of SUN x86-based  servers with Intel Ethenet
  controllers.  Both igb and e1000 drivers are used. All servers have
  strange issue: after fresh Ubuntu 16.04 installation all ethernet
  links are in down state even if cables are plugged in.

  At the network switch side links are in up state!

  If i try to manually up the link via ip link tool, all works fine.
  When i try to manually assign an IP address to "dead" interface it
  brings up... After reboot all links are down again.

  Any suggestion?

  Environment:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"
  NAME="Ubuntu"
  VERSION="16.04.1 LTS (Xenial Xerus)"

  Description of affected adapters:

  10:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet 
Controller (rev 06)
  Subsystem: QLogic Corp. 82571EB Gigabit Ethernet Controller
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ 
Stepping- SERR+ FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: e1000e
  Kernel modules: e1000e

  1f:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network 
Connection (rev 01)
  Subsystem: Oracle/SUN 82576 Gigabit Network Connection
  Physical Slot: 0
  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: igb
  Kernel modules: igb

  Modules:
  modinfo igb
  filename:   
/lib/modules/4.4.0-59-generic/kernel/drivers/net/ethernet/intel/igb/igb.ko
  version:5.3.0-k

  modinfo e1000e
  filename:   
/lib/modules/4.4.0-59-generic/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
  version:3.2.6-k

  --- 
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Jan 17 10:38 seq
   crw-rw+ 1 root audio 116, 33 Jan 17 10:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a4e3c371-9e25-45f8-ae21-6e876f19c276
  InstallationDate: Installed on 2016-12-29 (19 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Oracle Corporation SUN BLADE X6270 M2 SERVER MODULE
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=UUID=396b00e0-4d6d-4143-a0a0-d954eafc3c12 ro
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 08070400
  dmi.board.asset.tag: 511-1418-03
  dmi.board.name: ASSY,BLADE,X6270,M2
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 511-1418-03
  dmi.chassis.type: 28
  dmi.chassis.vendor: ORACLE CORPORATION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr08070400:bd02/17/2014:svnOracleCorporation:pnSUNBLADEX6270M2SERVERMODULE:pvr:rvnOracleCorporation:rnASSY,BLADE,X6270,M2:rvr511-1418-03:cvnORACLECORPORATION:ct28:cvr:
  

[Kernel-packages] [Bug 1650336] Re: NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

[Joseph Salisbury]

So this bug does not happen with the 4.10-rc4 kernel from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc4

If that is the case, we can perform a "Reverse" bisect to identify the
commit that resolves that bug upstream.

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

Title:
  NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

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

Bug description:
  On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel
  crash on boot when in /etc/fstab a nfsv4 entry is active

  When comment the line or set to noauto the kernel boot with no error
  and mounting the nfs shares (after uncomment ) is also possible
  without error

  4.4.0-54 boots without this problem.

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

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

Re: [Kernel-packages] [Bug 1641078] Comment bridged from LTC Bugzilla

[Dimitri John Ledkov]

On 18 January 2017 at 15:39, bugproxy  wrote:
> --- Comment From ma...@de.ibm.com 2017-01-18 10:36 EDT---
> (In reply to comment #21)
>> Installed lpar onto 154d dasd drive, using LVM automatic partitioning recipe.
>> After installation and reipl, I did the following:
>
>> $ sudo update-initramfs -u
>
> I understand that things work with this explicit call.

How does it work with e.g. dracut? One must regenerate the initramfs
to activate the additional drive on boot, no?
Does one required to call zipl (which calls into dracut to regenerate
initramfs?!) or does one call dracut?
E.g. how does thing work without any explicit calls to regenerate the initramfs?

> However, users can easily miss this since it's not entirely obvious.
>

Regular ubuntu/debian users do know to call update-initramfs -u when
fiddling/changing rootfs devices (not the most trivial task to be
honest).
Same as fedora users know to call dracut. IMHO.

>> At the end of all of this I have triggered a reboot; whilst watching
>> Operating system messages. Reboot was completed successfully. Thus imho this
>> bug is invalid.
>
>> However, I do think that on Ubuntu systems "chzdev -e" should always trigger
>> "initramfs-update -u" irrespective of what has been activated. Such that
>> initramfs has as up-to-date udev rules as possible. Simply because it is
>> impossible to predict at chzdev activation time whether or not something
>> will be formated and added to become part of the rootfs backing devices or
>> not.
>
> Hm, good point. But then again, it would be suboptimal to have hundreds
> of disks (paths) (or vNICs or other device types) activated early in
> initramfs just because a few of the disks are actually required to mount
> the root-fs (and that's all an initramfs should do). Alas, I don't know
> how to solve it optimally.
>

Ubuntu uses chzdev, which generates udev rules, and our initramfs
hooks copy all of the udev rules into the initramfs as udev is running
in Ubuntu initramfs.
The boot continues as soon as rootfs is detected to be available. If
other devices are activated in parallel, it should be mostly harmless.
And the boot will not wait to activate all the things that udev rules
specify in the initramfs.
Thus it's kind of a zero sum game, eventually all chzdev->udev rules
specified devices will be activated, and it does not matter much if
some of them are activated from initramfs or post-initramfs.

> (In reply to comment #18)
>> I have now added zdev root update hook in zesty, such that chzdev will
>> call update-initramfs -u.
>> I will test the behaviour and will cherry-pick that as an SRU into
>> xenial & yakkety.
>
> I cannot quite follow why this bug is invalid.
> I thought your above quoted code changes actually fixed this bug by not 
> requiring the user to explicitly run  "update-initramfs -u" any more.

I added the hook in place such that chzdev can call it when it needs to.

But I'm arguing that the hooks that chzdev calls will never be
sufficient when one decides to move their rootfs, on any Linux.
Because at initial "chzdev -e" call time the device that is being
activated is not yet part of the rootfs stack, but will become after
one e.g. expands lvm / mdadm / btrfs / etc on to it. Does that make
sense?

> If the bug is now declared invalid as in "user error", then I'm puzzled about 
> the reasons for a code change.
>

a code change was mostly a red-herring (oh there is a hook integration
that is not currently used, let's use it if we can).
The root cause of the bug is a user error - not regenerating initramfs
after changing rootfs devices.

>From the bug log, it seems there have been no attempts made to make
sure initramfs is updated, after the devices for the rootfs are
changed.

As far as I understand the pattern should be: (1) chzdev -e
new-device; (2) mangle new-device into roofs; (3) call something to
regenerated initramfs

Where (3) should be "update-initramfs -u" or "chzdev" (again) since at
this point it should have enough information to realise that rootfs
stack has changed and would therefore call "update-initramfs -u" via
the newly integrated hook (the red-herring code change, on the newer
ubuntu, as I don't think I have SRUed this).

But in practice step (3) imho should be just "update-initramfs -u"
(debian/ubuntu) or "dracut" (fedora/suse/rhel/etc) which is in my
opinion trivial and discoverable enough.
-- 
Regards,

Dimitri.

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

Title:
  System cannot be booted up when root filesystem is on an LVM on two
  disks

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  LVMed root file system acrossing multiple disks cannot be booted up 

  ---uname output---
  Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 

[Kernel-packages] [Bug 1656489] Re: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity

[Mikemecanic]

There is no relation between custom kernel and Ubiquity or the installer.  The 
bug is in today's build:  Same message on startup and Kylin opens in try Ubuntu 
in Chinese(20170117).  
 Plus , fans and HDD are too noisy to run Zesty under 4.10, even 4.9.  I tried 
4.10-rc4 when it came out and there was too many noises in Zesty or Xenial.  
The Ubiquity team introduced this bug a month ago.  I don't have any of these 
issues under Windows 10. 

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

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 

[Kernel-packages] [Bug 1646622] Re: TouchPad doesn't work ASUS x556uj

[david]

Thank you for clearing that to me Christopher M. Penalver

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

Title:
  TouchPad doesn't work ASUS x556uj

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My TouchPad doesn't work on ASUS x556uj-xx186D 
  It is a new laptop, with dual bot with windows 10, and the touchpad work fine 
in windows 10.
  in my ubuntu 16.10 the touchpad isn't working.

  (i don't know what is the manufacturer of the touchpad is...)

  thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-28-generic 4.8.0-28.30
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  avi2228 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec  1 23:10:43 2016
  HibernationDevice: RESUME=UUID=e64b1929-f4cf-4bcb-bbfc-e77d031f6728
  InstallationDate: Installed on 2016-11-28 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: ASUSTeK COMPUTER INC. X556UJ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-28-generic 
root=UUID=ae71182c-429d-4b16-acf4-990d1bdf256f ro quiet splash pci=nomsi 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-28-generic N/A
   linux-backports-modules-4.8.0-28-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UJ.406
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UJ.406:bd06/28/2016:svnASUSTeKCOMPUTERINC.:pnX556UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X556UJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1654774] Re: battery informatin displayed incorrectly

[david]

** Description changed:

  I did a fresh install of ubuntu 16.04.1 on an asus x556uak laptop and
  noticed that when connected to AC and the battery is not charging the
  system shows the battery icon as discharging , but when the battery has
  discharged a little and when connected again it charges, then system
  shows the battery icon as connected to AC and charging.
- 
- Also I've noticed that all though I have 2 38 Whr cells ubuntu is only
- detecting one 38 Whr cell, as if the second one doesn't exist? But maybe
- this is not a bug and it switches to secondary battery when the 1st one
- is empty?
  
  This is the output of `upower -d`
  
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  IST 19:06:36 2017 ינו 07 ש' (1564 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  no
  icon-name:  'ac-adapter-symbolic'
  
  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  IST 19:32:37 2017 ינו 07 ש' (3 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   discharging
  warning-level:   none
  energy:  27.154 Wh
  energy-empty:0 Wh
  energy-full: 37.886 Wh
  energy-full-design:  38 Wh
  energy-rate: 8.648 W
  voltage: 7.6 V
  time to empty:   3.1 hours
  percentage:  72%
  capacity:99.7%
  technology:  lithium-ion
  icon-name:  'battery-full-symbolic'
    History (rate):
  14838103578.648   discharging
  
  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  IST 19:32:37 2017 ינו 07 ש' (3 seconds ago)
    has history:  no
    has statistics:   no
    battery
  present: yes
  state:   discharging
  warning-level:   none
  energy:  27.154 Wh
  energy-full: 37.886 Wh
  energy-rate: 8.648 W
  time to empty:   3.1 hours
  percentage:  72%
  icon-name:  'battery-full-symbolic'
  
  Daemon:
    daemon-version:  0.99.4
    on-battery:  yes
    lid-is-closed:   no
    lid-is-present:  yes
    critical-action: HybridSleep
  
  This is the output of `upower -d` when the battery is allready charged
  and the laptop is plugged to AC:
  
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  IST 20:44:01 2017 ינו 07 ש' (21 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'
  
  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  IST 20:44:01 2017 ינו 07 ש' (21 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   discharging
  warning-level:   none
  energy:  37.825 Wh
  energy-empty:0 Wh
  energy-full: 37.886 Wh
  energy-full-design:  38 Wh
  energy-rate: 3.564 W
  voltage: 7.6 V
  time to empty:   10.6 hours
  percentage:  100%
  capacity:99.7%
  technology:  lithium-ion
  icon-name:  'battery-full-symbolic'
    History (charge):
  1483814641100.000 discharging
    History (rate):
  14838146413.564   discharging
  14838146412.348   discharging
  
  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  IST 20:44:01 2017 ינו 07 ש' (21 seconds ago)
    has history:  no
    has statistics:   no
    battery
  present: yes
  state:   discharging
  warning-level:   none
  energy:  37.825 Wh
  energy-full: 

[Kernel-packages] [Bug 1655476] onza (i386) - tests ran: 19, failed: 1

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-108.155-generic/onza__3.13.0-108.155__2017-01-18_14-59-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/1655476

Title:
  linux: 3.13.0-108.155 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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 3.13.0-108.155 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
  derivative-trackers-created: 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/1655476/+subscriptions

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

Re: [Kernel-packages] [Bug 1656489] AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity

[Mikemecanic]

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

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  

[Kernel-packages] [Bug 1641078] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From ma...@de.ibm.com 2017-01-18 10:36 EDT---
(In reply to comment #21)
> Installed lpar onto 154d dasd drive, using LVM automatic partitioning recipe.
> After installation and reipl, I did the following:

> $ sudo update-initramfs -u

I understand that things work with this explicit call.
However, users can easily miss this since it's not entirely obvious.

> At the end of all of this I have triggered a reboot; whilst watching
> Operating system messages. Reboot was completed successfully. Thus imho this
> bug is invalid.

> However, I do think that on Ubuntu systems "chzdev -e" should always trigger
> "initramfs-update -u" irrespective of what has been activated. Such that
> initramfs has as up-to-date udev rules as possible. Simply because it is
> impossible to predict at chzdev activation time whether or not something
> will be formated and added to become part of the rootfs backing devices or
> not.

Hm, good point. But then again, it would be suboptimal to have hundreds
of disks (paths) (or vNICs or other device types) activated early in
initramfs just because a few of the disks are actually required to mount
the root-fs (and that's all an initramfs should do). Alas, I don't know
how to solve it optimally.

(In reply to comment #18)
> I have now added zdev root update hook in zesty, such that chzdev will
> call update-initramfs -u.
> I will test the behaviour and will cherry-pick that as an SRU into
> xenial & yakkety.

I cannot quite follow why this bug is invalid.
I thought your above quoted code changes actually fixed this bug by not 
requiring the user to explicitly run  "update-initramfs -u" any more.
If the bug is now declared invalid as in "user error", then I'm puzzled about 
the reasons for a code change.

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

Title:
  System cannot be booted up when root filesystem is on an LVM on two
  disks

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  LVMed root file system acrossing multiple disks cannot be booted up 

  ---uname output---
  Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC 2016 
s390x s390x s390x GNU/Linux
   
  ---Patches Installed---
  n/a
   
  Machine Type = z13 
   
  ---System Hang---
   cannot boot up the system after shutdown or reboot
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Created root file system on an LVM and the LVM crosses two disks. After shut 
down or reboot the system, the system cannot be up. 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Device driver error code:
   Begin: Mounting root file system ... Begin: Running /scripts/local-top ...   
lvmetad is not active yet, using direct activation during sysinit 
Couldn't find device with uuid 7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V. 
   
  -Attach sysctl -a output output to the bug.

  More detailed installation description:

  The installation was on a FCP SCSI SAN volumes each with two active
  paths.  Multipath was involved.  The system IPLed fine up to the point
  that we expanded the /root filesystem to span volumes.  At boot time,
  the system was unable to locate the second segment of the /root
  filesystem.   The error message indicated this was due to lvmetad not
  being not active.

  Error message:   
 Begin: Running /scripts/local-block ...   lvmetad is not active yet, 
using direct activation during sysinit 
 Couldn't find device with uuid 7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V 
  Failed to find logical volume "ub01-vg/root" 
  
  PV Volume information: 
  physical_volumes { 

 pv0 { 
 id = "L2qixM-SKkF-rQsp-ddao-gagl-LwKV-7Bw1Dz" 
 device = "/dev/sdb5"# Hint only 

 status = ["ALLOCATABLE"] 
 flags = [] 
 dev_size = 208713728# 99.5225 Gigabytes 
 pe_start = 2048 
 pe_count = 25477# 99.5195 Gigabytes 
 } 

 pv1 { 
 id = "7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V" 
 device = "/dev/sda"# Hint only 

 status = ["ALLOCATABLE"] 
 flags = [] 
 dev_size = 209715200# 100 Gigabytes 
 pe_start = 2048 
 pe_count = 25599# 99.9961 Gigabytes 

  
  LV Volume Information: 
  logical_volumes { 

 root { 
 id = "qWuZeJ-Libv-DrEs-9b1a-p0QF-2Fj0-qgGsL8" 
 status = ["READ", 

[Kernel-packages] [Bug 1656381] Re: Xen MSI setup code incorrectly re-uses cached pirq

[Dan Streetman]

** Description changed:

  [Impact]
  
  This bug fixes the root problem reported in bug 1648449, so its
  description can be mostly reused here:
  
  On an Amazon AWS instance that has NVMe drives, the NVMe drives fail to
  initialize, and so aren't usable by the system. If one of the NVMe
  drives contains the root filesystem, the instance won't boot.
  
  [Test Case]
  
  Boot an AWS instance with multiple NVMe drives. All except the first
  will fail to initialize, and errors will appear in the system log (if
  the system boots at all). With a patched kernel, all NVMe drives are
  initialized and enumerated and work properly.
  
  [Regression Potential]
  
  Patching the Xen MSI setup function may cause problems with other PCI
  devices using MSI/MSIX interrupts on a Xen guest.
  
+ Note this patch restores correct behavior for guests running under Xen
+ 4.5 or later hypervisors - specifically Xen hypervisors with qemu 2.1.0
+ or later.  For Xen hypervisors with qemu 2.0.0 or earlier, this patch
+ causes a regression.  With an Ubuntu hypervisor, Vivid or later qemu is
+ patched, as well as UCA Kilo or later qemu.  Trusty qemu or UCA Icehouse
+ qemu are not patched - see bug 1657489.
+ 
  [Other Info]
  
  The patch from bug 1648449 was only a workaround, that changed the NVMe
  driver to not trigger this Xen bug.  However, there have been reports of
  that patch causing non-Xen systems with NVMe drives to stop working, in
  bug 1626894.  So, the best thing to do is revert the workaround patch
  (and its regression fix patch from bug 1651602) back to the original
  NVMe drive code, and apply the real Xen patch to fix the problem.  That
  should restore functionality for non-Xen systems, and should allow Xen
  systems with multiple NVMe controllers to work.
+ 
+ Upstream discussion:
+ https://lists.xen.org/archives/html/xen-devel/2017-01/msg00447.html
+ 
+ Related: bug 1657489 ("qemu-xen: free all the pirqs for msi/msix when
+ driver unload")

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

Title:
  Xen MSI setup code incorrectly re-uses cached pirq

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

Bug description:
  [Impact]

  This bug fixes the root problem reported in bug 1648449, so its
  description can be mostly reused here:

  On an Amazon AWS instance that has NVMe drives, the NVMe drives fail
  to initialize, and so aren't usable by the system. If one of the NVMe
  drives contains the root filesystem, the instance won't boot.

  [Test Case]

  Boot an AWS instance with multiple NVMe drives. All except the first
  will fail to initialize, and errors will appear in the system log (if
  the system boots at all). With a patched kernel, all NVMe drives are
  initialized and enumerated and work properly.

  [Regression Potential]

  Patching the Xen MSI setup function may cause problems with other PCI
  devices using MSI/MSIX interrupts on a Xen guest.

  Note this patch restores correct behavior for guests running under Xen
  4.5 or later hypervisors - specifically Xen hypervisors with qemu
  2.1.0 or later.  For Xen hypervisors with qemu 2.0.0 or earlier, this
  patch causes a regression.  With an Ubuntu hypervisor, Vivid or later
  qemu is patched, as well as UCA Kilo or later qemu.  Trusty qemu or
  UCA Icehouse qemu are not patched - see bug 1657489.

  [Other Info]

  The patch from bug 1648449 was only a workaround, that changed the
  NVMe driver to not trigger this Xen bug.  However, there have been
  reports of that patch causing non-Xen systems with NVMe drives to stop
  working, in bug 1626894.  So, the best thing to do is revert the
  workaround patch (and its regression fix patch from bug 1651602) back
  to the original NVMe drive code, and apply the real Xen patch to fix
  the problem.  That should restore functionality for non-Xen systems,
  and should allow Xen systems with multiple NVMe controllers to work.

  Upstream discussion:
  https://lists.xen.org/archives/html/xen-devel/2017-01/msg00447.html

  Related: bug 1657489 ("qemu-xen: free all the pirqs for msi/msix when
  driver unload")

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

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

[Kernel-packages] [Bug 1657488] [NEW] Please merge crash version 7.1.7-1 (main) from debian sid

[Louis Bouchard]

Public bug reported:

merge bug

** Affects: crash (Ubuntu)
 Importance: Wishlist
 Assignee: Louis Bouchard (louis-bouchard)
 Status: Confirmed

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

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

** Changed in: crash (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

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

Title:
  Please merge crash version 7.1.7-1 (main) from debian sid

Status in crash package in Ubuntu:
  Confirmed

Bug description:
  merge bug

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

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

[Kernel-packages] [Bug 1655476] onibi (i386) - tests ran: 19, failed: 1

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-108.155-generic/onibi__3.13.0-108.155__2017-01-18_14-01-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/1655476

Title:
  linux: 3.13.0-108.155 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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 3.13.0-108.155 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
  derivative-trackers-created: 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/1655476/+subscriptions

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

[Kernel-packages] [Bug 1655476] modoc (ppc64el) - tests ran: 141, failed: 0

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-108.155-generic/modoc__3.13.0-108.155__2017-01-18_14-12-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/1655476

Title:
  linux: 3.13.0-108.155 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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 3.13.0-108.155 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
  derivative-trackers-created: 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/1655476/+subscriptions

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

[Kernel-packages] [Bug 1641078] Re: System cannot be booted up when root filesystem is on an LVM on two disks

[Dimitri John Ledkov]

Installed lpar onto 154d dasd drive, using LVM automatic partitioning recipe.
After installation and reipl, I did the following:

$ sudo chzdev -e 254d
ECKD DASD 0.0.254d configured

$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.4.0-60-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Using config file '/etc/zipl.conf'
Ignore section 'old': Image file '/boot/vmlinuz.old'
Building bootmap in '/boot'
Building menu 'menu'
Adding #1: IPL section 'ubuntu' (default)
Ignore #2: IPL section 'old'
Preparing boot device: dasda (154d).
Done.

$ sudo pvcreate /dev/dasdb1
WARNING: ext4 signature detected on /dev/dasdb1 at offset 1080. Wipe it? [y/n]: 
y
  Wiping ext4 signature on /dev/dasdb1.
  Physical volume "/dev/dasdb1" successfully created

$ sudo vgextend s1lp7-vg /dev/dasdb1
  Volume group "s1lp7-vg" successfully extended

$ sudo lvextend s1lp7-vg/root /dev/dasdb1
  Size of logical volume s1lp7-vg/root changed from 38.89 GiB (9957 extents) to 
80.16 GiB (20521 extents).
  Logical volume root successfully resized.

$ sudo resize2fs /dev/mapper/s1lp7--vg-root 
resize2fs 1.42.13 (17-May-2015)
Filesystem at /dev/mapper/s1lp7--vg-root is mounted on /; on-line resizing 
required
old_desc_blocks = 3, new_desc_blocks = 6
The filesystem on /dev/mapper/s1lp7--vg-root is now 21013504 (4k) blocks long.

Which is activate another dasd drive; update initramfs; format physical
volume on the new drive's partition; extend volume group to include that
physical volume; extend root logical volume to use new the new physical
volume; and resize the root filesystem. Confirmed with df that root
filesystem is now twice as big.

At the end of all of this I have triggered a reboot; whilst watching
Operating system messages. Reboot was completed successfully. Thus imho
this bug is invalid.

However, I do think that on Ubuntu systems "chzdev -e" should always
trigger "initramfs-update -u" irrespective of what has been activated.
Such that initramfs has as up-to-date udev rules as possible. Simply
because it is impossible to predict at chzdev activation time whether or
not something will be formated and added to become part of the rootfs
backing devices or not.

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

** Changed in: ubuntu-z-systems
   Status: Triaged => Invalid

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

Title:
  System cannot be booted up when root filesystem is on an LVM on two
  disks

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  LVMed root file system acrossing multiple disks cannot be booted up 

  ---uname output---
  Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC 2016 
s390x s390x s390x GNU/Linux
   
  ---Patches Installed---
  n/a
   
  Machine Type = z13 
   
  ---System Hang---
   cannot boot up the system after shutdown or reboot
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Created root file system on an LVM and the LVM crosses two disks. After shut 
down or reboot the system, the system cannot be up. 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Device driver error code:
   Begin: Mounting root file system ... Begin: Running /scripts/local-top ...   
lvmetad is not active yet, using direct activation during sysinit 
Couldn't find device with uuid 7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V. 
   
  -Attach sysctl -a output output to the bug.

  More detailed installation description:

  The installation was on a FCP SCSI SAN volumes each with two active
  paths.  Multipath was involved.  The system IPLed fine up to the point
  that we expanded the /root filesystem to span volumes.  At boot time,
  the system was unable to locate the second segment of the /root
  filesystem.   The error message indicated this was due to lvmetad not
  being not active.

  Error message:   
 Begin: Running /scripts/local-block ...   lvmetad is not active yet, 
using direct activation during sysinit 
 Couldn't find device with uuid 7PC3sg-i5Dc-iSqq-AvU1-XYv2-M90B-M0kO8V 
  Failed to find logical volume "ub01-vg/root" 
  
  PV Volume information: 
  physical_volumes { 

 pv0 { 
 id = "L2qixM-SKkF-rQsp-ddao-gagl-LwKV-7Bw1Dz" 
 device = "/dev/sdb5"# Hint only 

 status = ["ALLOCATABLE"] 
 flags = [] 
 dev_size = 208713728# 99.5225 Gigabytes 
 pe_start = 2048 
 pe_count = 25477# 99.5195 Gigabytes 
 } 

 pv1 { 
 id = 

[Kernel-packages] [Bug 1655476] onza (amd64) - tests ran: 19, failed: 1

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-108.155-generic/onza__3.13.0-108.155__2017-01-18_13-44-00/results-index.html

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

Title:
  linux: 3.13.0-108.155 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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 3.13.0-108.155 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
  derivative-trackers-created: 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/1655476/+subscriptions

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

[Kernel-packages] [Bug 1578944] Re: regular system freeze - 16.04

[mickEDK]

Suffered from this bug for 3 months. Tried more than 12 solutions
suggested by WWW. Given up and downgraded to Ubuntu 14.04 last week. No
recurrence 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/1578944

Title:
  regular system freeze - 16.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  Seems this is common enough to have a few requests on Ask Ubuntu:
  http://askubuntu.com/search?q=16.04+freeze

  I would update my kernel, as suggested, however there are not clear
  instructions and I have had issues doing kernel upgrades in the past.
  The freezes are not Chrome only, as they also occur when Chrome is not
  running, though, from memory, Steam uses some of the same things as
  Chrome.  Once the freeze happens a hard reset (holding down the power
  button) and restarting is the only solution (I can't even open a CLI
  instance).

  Thanks for your time, hope there is a fix soon.  Best regards,

  Taz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tamsyn 1886 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  6 16:45:25 2016
  HibernationDevice: RESUME=UUID=318736d3-a7a7-4b0e-8e64-6cce65e801ad
  InstallationDate: Installed on 2016-04-22 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Aspire E5-511
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=35b282c1-4348-4d7a-90db-fef77f539874 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2014
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.03
  dmi.board.name: Aspire E5-511
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV1.03:bd05/16/2014:svnAcer:pnAspireE5-511:pvrV1.03:rvnAcer:rnAspireE5-511:rvrV1.03:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-511
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1655476] modoc (ppc64el) - tests ran: 16, failed: 3

[Brad Figg]

tests ran:  16, failed: 3;
  
http://kernel.ubuntu.com/testing/3.13.0-108.155-generic/modoc__3.13.0-108.155__2017-01-18_13-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/1655476

Title:
  linux: 3.13.0-108.155 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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 3.13.0-108.155 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
  derivative-trackers-created: 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/1655476/+subscriptions

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

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

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-108.155-generic/onibi__3.13.0-108.155__2017-01-18_12-47-00/results-index.html

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

Title:
  linux: 3.13.0-108.155 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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 3.13.0-108.155 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
  derivative-trackers-created: 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/1655476/+subscriptions

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

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

[Michał Skrzypczak]

Thank you, it seems that your configuration helped with the trackpoint.
Do you have any suggestions regarding 1, 2 and 4?

Is it possible to add those settings to the GUI setting tab?

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

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

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

  Actual result: Touchpad settings missing entirely

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

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

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

  xinput list does not display a touchpad at all:

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

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

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

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

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

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

[Kernel-packages] [Bug 1657281] Re: Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue

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

Bug description:
  
  [Impact]

   * When running block device I/O on an Amazon i3 system there
 is a performance degradation. A patch with git change id
 87c279e613f848c69b29 that is in Ubuntu-lts-4.8.0 kernel
 series increases I/O performance.

   * Fix should be backported to xenial 4.4 series to avoid more
 support issues being filed.

   * This change gets rid of uneccessary work being performed.

  [Test Case]

   * Steps to reproduce below
 1) partition ephemeral disks 
/sbin/parted -s --align optimal /dev/nvme0n1 mklabel gpt mkpart primary 
0% 100% 
/sbin/parted -s --align optimal /dev/nvme1n1 mklabel gpt mkpart primary 
0% 100% 
/sbin/parted -s --align optimal /dev/nvme2n1 mklabel gpt mkpart primary 
0% 100% 
/sbin/parted -s --align optimal /dev/nvme3n1 mklabel gpt mkpart primary 
0% 100% 

 2) create raid array 
/sbin/mdadm --create /dev/md0 --assume-clean --chunk=2048 --level=10 
--raid-devices=4 /dev/nvme0n1p1 /dev/nvme1n1p1 /dev/nvme2n1p1 /dev/nvme3n1p1 

 3) create pv 
/sbin/pvcreate --force --metadatasize 4092k /dev/md0 

 4) create volume group 
/sbin/vgcreate RDSVG /dev/md0 

 5) create lv 
/sbin/lvcreate -L 2.5T -n RDSRAIDLV RDSVG 

 5) test I/O
sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync

  [Regression Potential]

   * No known regression potential.

  [Original Description]

  When we were doing testing on i3, we noticed that it is taking
  significantly longer to perform operations when using software RAID
  than without, we believe this is resolved in an upstream commit:
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  xenial.git/commit/?id=87c279e613f848c69b29d49de8df3f4f56da

  So stock 4.4.0-59-generic performs ok:
  $ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync 
  sudo: unable to resolve host ip-10-0-85-167
  100+0 records in
  100+0 records out
  819200 bytes (8.2 GB, 7.6 GiB) copied, 54.3711 s, 151 MB/s

  and the patch you originally providing works a little bit better (as 
expected):
  $ uname -a
  Linux ip-10-0-85-167 4.4.0-57-generic 
#78hf00v20170110b0h3199a6e718db-Ubuntu SMP Tue Jan 10 02:53: x86_64 x86_64 
x86_64 GNU/Linux
  ubuntu@ip-10-0-85-167:~$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k 
count=100 && sync 
  sudo: unable to resolve host ip-10-0-85-167
  100+0 records in
  100+0 records out
  819200 bytes (8.2 GB, 7.6 GiB) copied, 31.4108 s, 261 MB/s

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

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

[Kernel-packages] [Bug 1657353] Re: Backport DP MST fixes to i915

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Backport DP MST fixes to i915

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  New

Bug description:
  A machine being certified needs two commits from drm-intel-next:

  commit 22a2c8e0457f5d66db0819a49beb8c119d8f7a97
  Author: Dhinakaran Pandiyan 
  Date:   Tue Nov 15 12:59:06 2016 -0800

  drm/i915: Validate mode against max. link data rate for DP MST

  commit fd81c44eba9ca1e78d0601f37b5d7819df522aa7
  Author: Dhinakaran Pandiyan 
  Date:   Mon Nov 14 13:50:20 2016 -0800

  drm/i915: Fix DP link rate math

  
  these fix issues getting extended display mode working with a 4k monitor on a 
built-in MST hub.

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

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

[Kernel-packages] [Bug 1655476] onza (i386) - tests ran: 5, failed: 0

[Brad Figg]

tests ran:   5, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-108.155-generic/onza__3.13.0-108.155__2017-01-18_13-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/1655476

Title:
  linux: 3.13.0-108.155 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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 3.13.0-108.155 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
  derivative-trackers-created: 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/1655476/+subscriptions

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

[Kernel-packages] [Bug 1657281] Re: Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2017-January/081890.html

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue

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

Bug description:
  
  [Impact]

   * When running block device I/O on an Amazon i3 system there
 is a performance degradation. A patch with git change id
 87c279e613f848c69b29 that is in Ubuntu-lts-4.8.0 kernel
 series increases I/O performance.

   * Fix should be backported to xenial 4.4 series to avoid more
 support issues being filed.

   * This change gets rid of uneccessary work being performed.

  [Test Case]

   * Steps to reproduce below
 1) partition ephemeral disks 
/sbin/parted -s --align optimal /dev/nvme0n1 mklabel gpt mkpart primary 
0% 100% 
/sbin/parted -s --align optimal /dev/nvme1n1 mklabel gpt mkpart primary 
0% 100% 
/sbin/parted -s --align optimal /dev/nvme2n1 mklabel gpt mkpart primary 
0% 100% 
/sbin/parted -s --align optimal /dev/nvme3n1 mklabel gpt mkpart primary 
0% 100% 

 2) create raid array 
/sbin/mdadm --create /dev/md0 --assume-clean --chunk=2048 --level=10 
--raid-devices=4 /dev/nvme0n1p1 /dev/nvme1n1p1 /dev/nvme2n1p1 /dev/nvme3n1p1 

 3) create pv 
/sbin/pvcreate --force --metadatasize 4092k /dev/md0 

 4) create volume group 
/sbin/vgcreate RDSVG /dev/md0 

 5) create lv 
/sbin/lvcreate -L 2.5T -n RDSRAIDLV RDSVG 

 5) test I/O
sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync

  [Regression Potential]

   * No known regression potential.

  [Original Description]

  When we were doing testing on i3, we noticed that it is taking
  significantly longer to perform operations when using software RAID
  than without, we believe this is resolved in an upstream commit:
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  xenial.git/commit/?id=87c279e613f848c69b29d49de8df3f4f56da

  So stock 4.4.0-59-generic performs ok:
  $ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync 
  sudo: unable to resolve host ip-10-0-85-167
  100+0 records in
  100+0 records out
  819200 bytes (8.2 GB, 7.6 GiB) copied, 54.3711 s, 151 MB/s

  and the patch you originally providing works a little bit better (as 
expected):
  $ uname -a
  Linux ip-10-0-85-167 4.4.0-57-generic 
#78hf00v20170110b0h3199a6e718db-Ubuntu SMP Tue Jan 10 02:53: x86_64 x86_64 
x86_64 GNU/Linux
  ubuntu@ip-10-0-85-167:~$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k 
count=100 && sync 
  sudo: unable to resolve host ip-10-0-85-167
  100+0 records in
  100+0 records out
  819200 bytes (8.2 GB, 7.6 GiB) copied, 31.4108 s, 261 MB/s

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

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

[Kernel-packages] [Bug 1657453] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  cheesecame issue - webcam

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: hid_generic usbhid uas usb_storage psmouse ahci r8169 
libahci mii wmi i915 fjes i2c_hid hid video i2c_algo_bit drm_kms_helper 
sdhci_acpi sdhci syscopyarea sysfillrect sysimgblt fb_sys_fops drm
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DKMSKernelVersion: 4.8.0-34-generic
  Date: Wed Jan 18 18:38:31 2017
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:237:12:
 error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu0.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module 
failed to build
  UpgradeStatus: Upgraded to xenial on 2017-01-18 (0 days ago)

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

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

[Kernel-packages] [Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

Yes, working perfectly! Trying to remember how I set tags. Here is the
output of applying the test kernel:


mdlueck@ldslnx01:/srv/shares/data/Download/OpenSource/Ubuntu/Xenial/Bugs/1656605_ServerNoConsoleDisplay/v4.10-rc4$
 sudo dpkg -i 
linux-image-4.10.0-041000rc4-generic_4.10.0-041000rc4.201701152031_i386.deb 
[sudo] password for mdlueck: 
Selecting previously unselected package linux-image-4.10.0-041000rc4-generic.
(Reading database ... 57910 files and directories currently installed.)
Preparing to unpack 
linux-image-4.10.0-041000rc4-generic_4.10.0-041000rc4.201701152031_i386.deb ...
Done.
Unpacking linux-image-4.10.0-041000rc4-generic (4.10.0-041000rc4.201701152031) 
...
Setting up linux-image-4.10.0-041000rc4-generic (4.10.0-041000rc4.201701152031) 
...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.10.0-041000rc4-generic /boot/vmlinuz-4.10.0-041000rc4-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
4.10.0-041000rc4-generic /boot/vmlinuz-4.10.0-041000rc4-generic
update-initramfs: Generating /boot/initrd.img-4.10.0-041000rc4-generic
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
run-parts: executing /etc/kernel/postinst.d/update-notifier 
4.10.0-041000rc4-generic /boot/vmlinuz-4.10.0-041000rc4-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 
4.10.0-041000rc4-generic /boot/vmlinuz-4.10.0-041000rc4-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.10.0-041000rc4-generic
Found initrd image: /boot/initrd.img-4.10.0-041000rc4-generic
Found linux image: /boot/vmlinuz-4.4.0-59-generic
Found initrd image: /boot/initrd.img-4.4.0-59-generic
Found linux image: /boot/vmlinuz-3.13.0-107-generic
Found initrd image: /boot/initrd.img-3.13.0-107-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done

** Tags added: kernel-fixed-upstream

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

Title:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Today I did our first production 14.04 to 16.04 LTS server upgrade. I
  had done so a couple of times successfully on test server machines.
  Upon booting up on the 16.04 system/kernel, after the Grub screen the
  server console screen is completely blank.

  Someone suggested using Ctrl-Alt-F1/8, and indeed pressing those
  hotkeys does toggle through the tty screens.

  There is no boot process logged to the server console screen.

  I did have the last 14.04 kernel yet installed, so selected that one
  from the Grub menu. Booting that 14.04 kernel, then server console
  display behaves normally.

  So I suspected perhaps a bum install of the 16.04 kernel. I used the
  following commands while booted to the 14.04 kernel to reinstall the
  16.04 kernel:

  $ sudo dpkg -P linux-image-4.4.0-59-generic 
linux-image-extra-4.4.0-59-generic linux-image-generic
  $ sudo apt-get install linux-image-generic

  Same results booting the 16.04 kernel after those steps.

  Hardware spec is an Intel Atom D945GCLF2D boxed motherboard with Intel
  Atom 330 Dual-Core processor and 2GB RAM. RAID is 3Ware SATA RAID.

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

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