date:20170202

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 405294] Re: a2dp skips terribly

2017-02-02 Thread Shadowpool

On Xubuntu 16.04.1 64bit. Switching to the brcmsmac wireless driver
seems to have fixed/significantly improved this issue for me. Using the
original bcmwl-kernel-source driver, bluetooth audio would cut out
completely during a network speedtest on wifi. With wifi off, bluetooth
sound would be flawless.

I just installed b43-fwcutter, firmware-b43-installer, and completely
removed / purged bcmwl-kernel-source all at once and restarted.

Now playback seems *greatly* improved during wireless network use.

Wireless card is BCM4313.

4.4.0-62-generic
pulseaudio 1:8.0-0ubuntu3.2
bluez 5.37-0ubuntu5

Also using pylover a2dp.py script 0.2.5.

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

Title:
  a2dp skips terribly

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

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

This change was made by a bot.

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

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

Title:
  i915 driver fails to resume display from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Symptom is that the LCD on the laptop (Dell Latitude E7450) stays off
  after boot.  The laptop is running fine and can be reached via SSH,
  and rebooted.  I can also kill the Xorg server at which point my
  display manager starts a new session and restores the driver.

  I believe the display driver is failing to resume as indicated by this kernel 
log line:
  Feb  2 19:08:33 LON-IX-L-763 kernel: [32839.947460] [drm:intel_display_resume 
[i915]] *ERROR* Restoring old state failed with -22

  This looks like a regression in a recent kernel; this worked fine for
  ~1 year on Ubuntu 15.10 but I didn't test it on 16.04 so I can't
  confirm if it exists there.

  I suspend the machine by running pm-suspend, and it is resumed by the
  lid open event.

  I've attached the relevant time from /var/log/syslog which shows the
  kernel messages; this suspend was entered at 18:16:30 and woken up at
  19:08:33.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-extra-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   pv 4009 F...m pulseaudio
   /dev/snd/controlC1:  pv 4009 F pulseaudio
   /dev/snd/controlC0:  pv 4009 F pulseaudio
   /dev/snd/seq:pv 4126 F chrome
  Date: Fri Feb  3 03:23:55 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=adb71bac-b2c6-4c48-9f39-8b07f2b1d7b7
  InstallationDate: Installed on 2015-07-24 (559 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=3cd0b0b6-f38d-45bf-85aa-e6578b5e37c4 ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-12-19 (45 days ago)
  dmi.bios.date: 11/18/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0R1VJD
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/18/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0R1VJD:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1661475] Re: i915 driver fails to resume display from suspend

2017-02-02 Thread Patrick van Staveren

I've just done some additional testing which might give a hint to what's
happening.

I had suspended my machine while connected to a docking station with two
external displays in addition to the onboard one.

Over SSH I ran this script which I normally use to tell Xorg that I've undocked 
and to turn off the other outputs:
xrandr --output DP-3 --off --output eDP-1 --mode 1920x1080 --pos 0x0 --rotate 
normal --output DP-1-2 --off --output HDMI-2 --off --output HDMI-1 --off 
--output DP-1 --off --output DP-1-3 --off --output DP-2 --off --output DP-1-1 
--off

This caused the on-board display to start functioning again.

I'll test & reproduce further.  Perhaps the i915 driver not detecting
that the outputs list has changed is part of the issue, however still
doesn't explain why it fails to enable the on-board output.

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

Title:
  i915 driver fails to resume display from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Symptom is that the LCD on the laptop (Dell Latitude E7450) stays off
  after boot.  The laptop is running fine and can be reached via SSH,
  and rebooted.  I can also kill the Xorg server at which point my
  display manager starts a new session and restores the driver.

  I believe the display driver is failing to resume as indicated by this kernel 
log line:
  Feb  2 19:08:33 LON-IX-L-763 kernel: [32839.947460] [drm:intel_display_resume 
[i915]] *ERROR* Restoring old state failed with -22

  This looks like a regression in a recent kernel; this worked fine for
  ~1 year on Ubuntu 15.10 but I didn't test it on 16.04 so I can't
  confirm if it exists there.

  I suspend the machine by running pm-suspend, and it is resumed by the
  lid open event.

  I've attached the relevant time from /var/log/syslog which shows the
  kernel messages; this suspend was entered at 18:16:30 and woken up at
  19:08:33.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-extra-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   pv 4009 F...m pulseaudio
   /dev/snd/controlC1:  pv 4009 F pulseaudio
   /dev/snd/controlC0:  pv 4009 F pulseaudio
   /dev/snd/seq:pv 4126 F chrome
  Date: Fri Feb  3 03:23:55 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=adb71bac-b2c6-4c48-9f39-8b07f2b1d7b7
  InstallationDate: Installed on 2015-07-24 (559 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=3cd0b0b6-f38d-45bf-85aa-e6578b5e37c4 ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-12-19 (45 days ago)
  dmi.bios.date: 11/18/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0R1VJD
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/18/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0R1VJD:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1661475] [NEW] i915 driver fails to resume display from suspend

2017-02-02 Thread Patrick van Staveren

Public bug reported:

Symptom is that the LCD on the laptop (Dell Latitude E7450) stays off
after boot.  The laptop is running fine and can be reached via SSH, and
rebooted.  I can also kill the Xorg server at which point my display
manager starts a new session and restores the driver.

I believe the display driver is failing to resume as indicated by this kernel 
log line:
Feb  2 19:08:33 LON-IX-L-763 kernel: [32839.947460] [drm:intel_display_resume 
[i915]] *ERROR* Restoring old state failed with -22

This looks like a regression in a recent kernel; this worked fine for ~1
year on Ubuntu 15.10 but I didn't test it on 16.04 so I can't confirm if
it exists there.

I suspend the machine by running pm-suspend, and it is resumed by the
lid open event.

I've attached the relevant time from /var/log/syslog which shows the
kernel messages; this suspend was entered at 18:16:30 and woken up at
19:08:33.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-extra-4.8.0-34-generic 4.8.0-34.36
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   pv 4009 F...m pulseaudio
 /dev/snd/controlC1:  pv 4009 F pulseaudio
 /dev/snd/controlC0:  pv 4009 F pulseaudio
 /dev/snd/seq:pv 4126 F chrome
Date: Fri Feb  3 03:23:55 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=adb71bac-b2c6-4c48-9f39-8b07f2b1d7b7
InstallationDate: Installed on 2015-07-24 (559 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Dell Inc. Latitude E7450
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=3cd0b0b6-f38d-45bf-85aa-e6578b5e37c4 ro quiet splash vt.handoff=7
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
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2016-12-19 (45 days ago)
dmi.bios.date: 11/18/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0R1VJD
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/18/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0R1VJD:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7450
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug yakkety

** Attachment added: "resume-fail-syslog"
   
https://bugs.launchpad.net/bugs/1661475/+attachment/4812340/+files/resume-fail-syslog

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

Title:
  i915 driver fails to resume display from suspend

Status in linux package in Ubuntu:
  New

Bug description:
  Symptom is that the LCD on the laptop (Dell Latitude E7450) stays off
  after boot.  The laptop is running fine and can be reached via SSH,
  and rebooted.  I can also kill the Xorg server at which point my
  display manager starts a new session and restores the driver.

  I believe the display driver is failing to resume as indicated by this kernel 
log line:
  Feb  2 19:08:33 LON-IX-L-763 kernel: [32839.947460] [drm:intel_display_resume 
[i915]] *ERROR* Restoring old state failed with -22

  This looks like a regression in a recent kernel; this worked fine for
  ~1 year on Ubuntu 15.10 but I didn't test it on 16.04 so I can't
  confirm if it exists there.

  I suspend the machine by running pm-suspend, and it is resumed by the
  lid open event.

  I've attached the relevant time from /var/log/syslog which shows the
  kernel messages; this suspend was entered at 18:16:30 and woken up at
  19:08:33.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-extra-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   pv 4009 F...m pulseaudio
   /dev/snd/controlC1:  pv 4009 F pulseaudio
   /dev/snd/controlC0:  pv 4009 F pulseaudio
   /dev/snd/seq:pv 4126 F chrome
  Date: Fri Feb  3 03:23:55 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=adb71bac-b2c6-4c48-9f39-8b07f2b1d7b7
  InstallationDate: Installed on 2015-07-24 (559 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=3cd0b0b6-f38d-45bf-85aa-e6578b5e37c4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:

[Kernel-packages] [Bug 1661476] [NEW] package linux-signed-image-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: package linux-signed-image-4.4.0-53-generic is not ready for configuration cann

2017-02-02 Thread Tyler Simpson

Public bug reported:

I'm new to Ubuntu and was tying to update through the "software store". I went 
to the terminal and ran sudo apt dist-upgrade. 
I got this back:
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  gstreamer1.0-tools libgssapi-krb5-2 libgstreamer1.0-0 libkrb5-3
  libkrb5support0
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 1,046 kB/1,235 kB of archives.
After this operation, 7,168 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
linux-signed-image-4.4.0-53-generic amd64 4.4.0-53.74 [4,002 B]
Err:2 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libkrb5-3 
amd64 1.13.2+dfsg-5ubuntu2
  500  No space left on device
Err:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libgstreamer1.0-0 amd64 1.8.3-1~ubuntu0.1
  500  No space left on device
Fetched 4,002 B in 1min 7s (59 B/s)
E: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/pool/main/k/krb5/libkrb5-3_1.13.2+dfsg-5ubuntu2_amd64.deb
  500  No space left on device

E: Failed to fetch
http://us.archive.ubuntu.com/ubuntu/pool/main/g/gstreamer1.0/libgstreamer1.0-0_1.8.3-1~ubuntu0.1_amd64.deb
500  No space left on device

E: Unable to fetch some archives, maybe run apt-get update or try with
--fix-missing?

Next I ran: sudo apt dist-upgrade --fix-missing 
and got back:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  gstreamer1.0-tools libgssapi-krb5-2 libgstreamer1.0-0 libkrb5-3
  libkrb5support0
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 1,042 kB/1,235 kB of archives.
After this operation, 7,168 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Err:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libkrb5-3 
amd64 1.13.2+dfsg-5ubuntu2
  500  No space left on device
Err:2 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libgstreamer1.0-0 amd64 1.8.3-1~ubuntu0.1
  500  No space left on device
dpkg: error processing package linux-signed-image-4.4.0-53-generic 
(--configure):
 package linux-signed-image-4.4.0-53-generic is not ready for configuration
 cannot configure (current status 'half-installed')
E: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/pool/main/k/krb5/libkrb5-3_1.13.2+dfsg-5ubuntu2_amd64.deb
  500  No space left on device

E: Failed to fetch
http://us.archive.ubuntu.com/ubuntu/pool/main/g/gstreamer1.0/libgstreamer1.0-0_1.8.3-1~ubuntu0.1_amd64.deb
500  No space left on device

E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-signed-image-4.4.0-53-generic 4.4.0-53.74
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
 linux-signed-image-4.4.0-53-generic: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Feb  2 20:33:00 2017
DpkgTerminalLog:
 dpkg: error processing package linux-signed-image-4.4.0-53-generic 
(--configure):
  package linux-signed-image-4.4.0-53-generic is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package linux-signed-image-4.4.0-53-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
InstallationDate: Installed on 2016-11-30 (65 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: linux-signed
Title: package linux-signed-image-4.4.0-53-generic 4.4.0-53.74 failed to 
install/upgrade: package linux-signed-image-4.4.0-53-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed (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-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1661476

Title:
  package linux-signed-image-4.4.0-53-generic 4.4.0-53.74 failed to
  install/upgrade: package linux-signed-image-4.4.0-53-generic is not
  ready for configuration  cannot configure (current status 'half-
  installed')

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I'm new to Ubuntu and was tying to update through the "software store". I 
went to the terminal and ran sudo apt dist-upgrade. 
  I got this back:
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating

[Kernel-packages] [Bug 1661170] PciMultimedia.txt

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1661170/+attachment/4812334/+files/PciMultimedia.txt

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1661170/+attachment/4812330/+files/CurrentDmesg.txt

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] Card0.Codecs.codec.0.txt

apport information

** Attachment added: "Card0.Codecs.codec.0.txt"

https://bugs.launchpad.net/bugs/1661170/+attachment/4812328/+files/Card0.Codecs.codec.0.txt

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

Title:
HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
Incomplete

Bug description:
On HP Z640 Workstations running ubuntu 16.04 with any official ubuntu
kernel newer than 4.4.0-21-generic USB devices do not work.

They appear to be listed correctly via lsusb and connects and
disconnects are logged but keyboards, mice, storage devices, ethernet
adapters do not work at all when they are connected directly via any
USB ports on the machines or through USB hubs.

All ubuntu packages are up to date. The BIOS version is the latest
(2.29).

The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
4.4.30 and 4.4.38 work correctly.

Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] AlsaDevices.txt

apport information

** Attachment added: "AlsaDevices.txt"
   
https://bugs.launchpad.net/bugs/1661170/+attachment/4812326/+files/AlsaDevices.txt

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1661170/+attachment/4812335/+files/ProcCpuinfo.txt

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1661170/+attachment/4812331/+files/JournalErrors.txt

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] Card1.Codecs.codec.0.txt

apport information

** Attachment added: "Card1.Codecs.codec.0.txt"

https://bugs.launchpad.net/bugs/1661170/+attachment/4812329/+files/Card1.Codecs.codec.0.txt

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

Title:
HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
Incomplete

Bug description:
On HP Z640 Workstations running ubuntu 16.04 with any official ubuntu
kernel newer than 4.4.0-21-generic USB devices do not work.

All ubuntu packages are up to date. The BIOS version is the latest
(2.29).

The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
4.4.30 and 4.4.38 work correctly.

Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

[Kernel-packages] [Bug 1661170] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1661170/+attachment/4812327/+files/CRDA.txt

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1661170/+attachment/4812332/+files/Lspci.txt

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1661170/+attachment/4812336/+files/ProcInterrupts.txt

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1661170/+attachment/4812338/+files/UdevDb.txt

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] WifiSyslog.txt

apport information

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

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1661170/+attachment/4812333/+files/Lsusb.txt

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1661170/+attachment/4812337/+files/ProcModules.txt

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1661170] Re: HP Z640 USB port stopped working since 4.4.0-22.38

AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-59-generic.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Card1.Amixer.info: Error: [Errno 2] No such file or directory
Card1.Amixer.values: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Hewlett-Packard HP Z640 Workstation
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=abd14d06-7dd1-4652-ab73-598ed50ac0ee ro quiet splash vt.handoff=7
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 xenial
Uname: Linux 4.4.0-59-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
_MarkForUpload: False
dmi.bios.date: 11/08/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M60 v02.29
dmi.board.name: 212A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 1.01
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM60v02.29:bd11/08/2016:svnHewlett-Packard:pnHPZ640Workstation:pvr:rvnHewlett-Packard:rn212A:rvr1.01:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Z640 Workstation
dmi.sys.vendor: Hewlett-Packard


** Tags added: apport-collected

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

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

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

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

[Kernel-packages] [Bug 1555786] Re: [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

2017-02-02 Thread Dexuan Cui

@jrp, it looks the patch in comment #26 is unrelated to this bug?
The patch is for cxlflash (Support for IBM CAPI Flash), which doesn't exist in 
a VM running on Hyper-V.

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

Title:
  [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

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

Bug description:
  We identified that at least ubuntu (let's take 15.10) does not boot if
  installed in the 32bit architecture, and using the linux-next upstream
  kernel 4.5 on it. This has been seen on other distributions as well.

  We took both the official linux-next branch from kernel.org and the one from 
kernel.ubuntu.com v4.5-rc7.
  For the compilation process we went either with the 4.2 kernel config file 
from the installed running kernel, and also built the config separately. 
  No errors have been encountered during the build or install process of the 
4.5 kernel, however at boot, the VM will just hang.
  There are no call traces or messages at boot to show any pottential issue.

  Have you seen this on your end when testing the 32bit build?
  Attaching the full serial log for reference, however I don't see any errors 
in the kernel boot process.

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

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

[Kernel-packages] [Bug 1595765] Re: Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here]

2017-02-02 Thread JaSauders

I installed 4.8 hwe edge from the repositories on my 16.04 system
(Macbook Pro with Broadcom 4331 card). I lost wireless.

I rebooted, made sure I was up to date, etc etc. Nothing in 4.8 would
work. Anything 4.4.x would work fine though.

I received an error when installing via terminal much like the error in
the original post. This gave me a lead which ultimately lead me here.
Installing via GUI (system settings >> software and updates >>
additional drivers) did not yield any sort of error.

In the end, nothing worked with getting wifi working again on 16.04.1 +
BCM4331 + HWE Edge Kernel 4.8 -- until I downloaded the .deb Vincent
linked in post 14 above. I was skeptical to try it as the version
numbers of the .deb seemed to match what was in the repos when I
searched Synaptic, but alas, I tried it. Immediately I reconnected to
wifi on my 5ghz network. I installed it via dpkg -i in terminal, and the
output looked cleaner.

Given I tried installing the 4.8 hwe edge kernel here on February 2nd
and ran into this problem... yet 16.04.2 is due out within days... I
raise the difficult question and can't help but to wonder if things are
"ready". Otherwise I would anticipate an additional flurry of reported
issues coming in relating to this topic.

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

Title:
  Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’
  undeclared here]

Status in bcmwl package in Ubuntu:
  Confirmed
Status in broadcom-sta package in Ubuntu:
  Confirmed
Status in rtl8812au package in Ubuntu:
  Confirmed

Bug description:
  error update for kernel 4.7 RC 3

  ProblemType: Package
  DistroRelease: elementary 0.4
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 [origin: Ubuntu]
  Uname: Linux 4.6.2-040602-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSKernelVersion: 4.7.0-040700rc3-generic
  Date: Thu Jun 23 22:03:59 2016
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8:/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)
  InstallationDate: Installed on 2016-06-14 (9 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Daily amd64 (20160613)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu8
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

This change was made by a bot.

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

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

Title:
  package linux-image-extra-4.8.0-37-generic 4.8.0-37.39 failed to
  install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-
  image-extra-4.8.0-37-generic.list-new': Operation not permitted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  not a tech guy but trying to do my part hope it helps.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-extra-4.8.0-37-generic 4.8.0-37.39
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apollo30   3426 F pulseaudio
  Date: Thu Feb  2 19:34:49 2017
  DuplicateSignature:
   package:linux-image-extra-4.8.0-37-generic:4.8.0-37.39
   Unpacking linux-image-4.8.0-37-generic (4.8.0-37.39) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PWl0Ok/03-linux-image-4.8.0-37-generic_4.8.0-37.39_amd64.deb
 (--unpack):
unable to create new file 
'/var/lib/dpkg/info/linux-image-4.8.0-37-generic.list-new': Operation not 
permitted
  ErrorMessage: unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic.list-new': Operation not 
permitted
  HibernationDevice: RESUME=UUID=a0124356-9144-4037-adc9-975b85afab53
  InstallationDate: Installed on 2016-08-31 (155 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  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-36ubuntu11
  SourcePackage: linux
  Title: package linux-image-extra-4.8.0-37-generic 4.8.0-37.39 failed to 
install/upgrade: unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic.list-new': Operation not 
permitted
  UpgradeStatus: Upgraded to yakkety on 2017-01-05 (28 days ago)
  dmi.bios.date: 05/02/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.0A
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.18
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.0A:bd05/02/2012:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr07901020571620100:rvnHewlett-Packard:rn181D:rvr52.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 07901020571620100
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~kernel-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)

2017-02-02 Thread Rod Smith

Joseph, I don't see the usual linux-image-* files at that URL. Could you
please double-check that and fix as necessary?

-- 
You 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 1661462] Re: package linux-image-extra-4.8.0-37-generic 4.8.0-37.39 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic.l

2017-02-02 Thread 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/1661462

Title:
  package linux-image-extra-4.8.0-37-generic 4.8.0-37.39 failed to
  install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-
  image-extra-4.8.0-37-generic.list-new': Operation not permitted

Status in linux package in Ubuntu:
  New

Bug description:
  not a tech guy but trying to do my part hope it helps.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-extra-4.8.0-37-generic 4.8.0-37.39
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apollo30   3426 F pulseaudio
  Date: Thu Feb  2 19:34:49 2017
  DuplicateSignature:
   package:linux-image-extra-4.8.0-37-generic:4.8.0-37.39
   Unpacking linux-image-4.8.0-37-generic (4.8.0-37.39) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PWl0Ok/03-linux-image-4.8.0-37-generic_4.8.0-37.39_amd64.deb
 (--unpack):
unable to create new file 
'/var/lib/dpkg/info/linux-image-4.8.0-37-generic.list-new': Operation not 
permitted
  ErrorMessage: unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic.list-new': Operation not 
permitted
  HibernationDevice: RESUME=UUID=a0124356-9144-4037-adc9-975b85afab53
  InstallationDate: Installed on 2016-08-31 (155 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  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-36ubuntu11
  SourcePackage: linux
  Title: package linux-image-extra-4.8.0-37-generic 4.8.0-37.39 failed to 
install/upgrade: unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic.list-new': Operation not 
permitted
  UpgradeStatus: Upgraded to yakkety on 2017-01-05 (28 days ago)
  dmi.bios.date: 05/02/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.0A
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 181D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.18
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.0A:bd05/02/2012:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr07901020571620100:rvnHewlett-Packard:rn181D:rvr52.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 07901020571620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1661462] [NEW] package linux-image-extra-4.8.0-37-generic 4.8.0-37.39 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic

2017-02-02 Thread David

Public bug reported:

not a tech guy but trying to do my part hope it helps.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: linux-image-extra-4.8.0-37-generic 4.8.0-37.39
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  apollo30   3426 F pulseaudio
Date: Thu Feb  2 19:34:49 2017
DuplicateSignature:
 package:linux-image-extra-4.8.0-37-generic:4.8.0-37.39
 Unpacking linux-image-4.8.0-37-generic (4.8.0-37.39) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-PWl0Ok/03-linux-image-4.8.0-37-generic_4.8.0-37.39_amd64.deb
 (--unpack):
  unable to create new file 
'/var/lib/dpkg/info/linux-image-4.8.0-37-generic.list-new': Operation not 
permitted
ErrorMessage: unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic.list-new': Operation not 
permitted
HibernationDevice: RESUME=UUID=a0124356-9144-4037-adc9-975b85afab53
InstallationDate: Installed on 2016-08-31 (155 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
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-36ubuntu11
SourcePackage: linux
Title: package linux-image-extra-4.8.0-37-generic 4.8.0-37.39 failed to 
install/upgrade: unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic.list-new': Operation not 
permitted
UpgradeStatus: Upgraded to yakkety on 2017-01-05 (28 days ago)
dmi.bios.date: 05/02/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.0A
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 181D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 52.18
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.0A:bd05/02/2012:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr07901020571620100:rvnHewlett-Packard:rn181D:rvr52.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.version: 07901020571620100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package yakkety

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

Title:
  package linux-image-extra-4.8.0-37-generic 4.8.0-37.39 failed to
  install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-
  image-extra-4.8.0-37-generic.list-new': Operation not permitted

Status in linux package in Ubuntu:
  New

Bug description:
  not a tech guy but trying to do my part hope it helps.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-extra-4.8.0-37-generic 4.8.0-37.39
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apollo30   3426 F pulseaudio
  Date: Thu Feb  2 19:34:49 2017
  DuplicateSignature:
   package:linux-image-extra-4.8.0-37-generic:4.8.0-37.39
   Unpacking linux-image-4.8.0-37-generic (4.8.0-37.39) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PWl0Ok/03-linux-image-4.8.0-37-generic_4.8.0-37.39_amd64.deb
 (--unpack):
unable to create new file 
'/var/lib/dpkg/info/linux-image-4.8.0-37-generic.list-new': Operation not 
permitted
  ErrorMessage: unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic.list-new': Operation not 
permitted
  HibernationDevice: RESUME=UUID=a0124356-9144-4037-adc9-975b85afab53
  InstallationDate: Installed on 2016-08-31 (155 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  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-36ubuntu11
  SourcePackage: linux
  Title: package linux-image-extra-4.8.0-37-generic 4.8.0-37.39 failed to 
install/upgrade: unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic.list-new': Operation not

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

2017-02-02 Thread Dimitrij Mijoski

I booted to 4.8 again and saw the dmesg.

This is the error:
[3.375735] ...
[   12.768084] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] 
*ERROR* [CRTC:26:pipe A] flip_done timed out

Apparently it is a known problem
https://bbs.archlinux.org/viewtopic.php?id=218581 related to the Intel
video driver in 4.8.

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

Title:
  [4.8 regression] boot has become very slow

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

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

2017-02-02 Thread WinEunuchs2Unix

To make these annoying warnings go away I used:

$ sudo cp assembly/hello  /lib/firmware/i915/kbl_dmc_ver1_01.bin
$ sudo cp assembly/hello /lib/firmware/i915/kbl_guc_ver9_14.bin
$ sudo cp assembly/hello /lib/firmware/i915/bxt_guc_ver8_7.bin
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.9.5-040905-generic

Voila! Error (warning) messages went away. It's been working fine for
1/2 hour.

"hello" is a 504 byte assembly program that simply says "Hello World!"
when run. I presume you can copy any executable program you want. When
Intel eventually gets around releasing the "kaby lake" processor and
appropriate drivers they will overwrite my fake drivers.

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

Title:
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915

Status in xen:
  Unknown
Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency

  [...]

  update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency
  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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-firmware 1.159
  Uname: Linux 4.8.0-040800rc1-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  Date: Mon Aug  8 17:50:38 2016
  Dependencies:
   
  InstallationDate: Installed on 2015-07-26 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1533009] Re: arm64: "unsupported RELA relocation"

2017-02-02 Thread Kj

I came across the same issue today (2/2/2017), i.e. "unsupported RELA
relocation: 275", while using "Ubuntu 16.04.1 LTS (GNU/Linux
4.4.0-59-generic aarch64)".  I read above messages and have verified
that arch/arm64/Makefile does have -mpc-relative-literal-loads as shown
below.  The kernel config file also has CONFIG_ARM64_ERRATUM_843419=y.

However, module.c shows "#ifndef CONFIG_ARM64_ERRATUM_843419".
Shouldn't this be #ifdef instead? Could it be that I'm seeing the error
message since #ifndef compiled out "case R_AARCH64_ADR_PREL_PG_HI21"
(275)?

ifeq ($(CONFIG_ARM64_ERRATUM_843419), y)
 KBUILD_CFLAGS_MODULE += -mcmodel=large
 KBUILD_CFLAGS_MODULE += $(call cc-option, -mpc-relative-literal-loads)
endif


File: arch/arm64/kernel/module.c
Linux Kernel Version: 4.9

 195int apply_relocate_add(Elf64_Shdr *sechdrs,
 196   const char *strtab,
 197   unsigned int symindex,
 198   unsigned int relsec,
 199   struct module *me)
 200{
 ...
 334#ifndef CONFIG_ARM64_ERRATUM_843419
 335case R_AARCH64_ADR_PREL_PG_HI21_NC:
 336overflow_check = false;
 337case R_AARCH64_ADR_PREL_PG_HI21:
 338ovf = reloc_insn_imm(RELOC_OP_PAGE, loc, val, 12, 
21,
 339 AARCH64_INSN_IMM_ADR);
 340break;
 341#endif

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

Title:
  arm64: "unsupported RELA relocation"

Status in Linaro GCC:
  Unknown
Status in Linux:
  Unknown
Status in gcc-5 package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in gcc-5 source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Released
Status in gcc-5 source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in gcc-5 source package in Wily:
  New
Status in linux source package in Wily:
  Fix Released
Status in gcc-5 source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  linux-image-4.3.0-5-generic 4.3.0-5.16 arm64 fails to load modules
  (and therefore boot). It emits messages like the following for each
  attempted module load:

  [2.156817] module libahci: unsupported RELA relocation: 275

  This is reminiscent of LP: #1502946 - except that fix appears to still
  be in-tact. What has changed, however, is the build environment. If I
  rebuild the same kernel source in a wily chroot, it boots fine.

  Marking "Confirmed" because Paulo Pisatti reported this to me, and I
  reproduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-linaro/+bug/1533009/+subscriptions

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

[Kernel-packages] [Bug 1661430] Re: [Hyper-V] Fix ring buffer handling to avoid host throttling

2017-02-02 Thread Joshua R. Poulson

No logs, request to include upstream commits.

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

Title:
  [Hyper-V] Fix ring buffer handling to avoid host throttling

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  An unfortunate side effect of some of the recent work done to improve
  ring buffer performance made a situation where the host would
  interpret guest requests as a denial of service attack, pausing guest
  communications for five seconds. This series of fixes corrects this
  problem.

  Needed for each kernel that has included a389fcfd2cb5 ("Drivers: hv:
  vmbus: Fix signaling logic in hv_need_to_signal_on_read()")

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=74198eb4a42c4a3c4fbef08fa01a291a282f7c2e

  Drivers: hv: vmbus: Base host signaling strictly on the ring state
  One of the factors that can result in the host concluding that a given
  guest in mounting a DOS attack is if the guest generates interrupts
  to the host when the host is not expecting it. If these "spurious"
  interrupts reach a certain rate, the host can throttle the guest to
  minimize the impact. The host computation of the "expected number
  of interrupts" is strictly based on the ring transitions. Until
  the host logic is fixed, base the guest logic to interrupt solely
  on the ring state.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f6ee4e7d83586c8b10bd4f2f4346353d04ce884

  Drivers: hv: vmbus: On write cleanup the logic to interrupt the host
  Signal the host when we determine the host is to be signaled.
  The currrent code determines the need to signal in the ringbuffer
  code and actually issues the signal elsewhere. This can result
  in the host viewing this interrupt as spurious since the host may also
  poll the channel. Make the necessary adjustments.

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/?id=3372592a140db69fd63837e81f048ab4abf8111e

  Drivers: hv: vmbus: On the read path cleanup the logic to interrupt the host
  Signal the host when we determine the host is to be signaled -
  on th read path. The currrent code determines the need to signal in the
  ringbuffer code and actually issues the signal elsewhere. This can result
  in the host viewing this interrupt as spurious since the host may also
  poll the channel. Make the necessary adjustments.

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/?id=433e19cf33d34bb6751c874a9c00980552fe508c

  Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read()
  Commit a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in
  hv_need_to_signal_on_read()")
  added the proper mb(), but removed the test "prev_write_sz < pending_sz"
  when making the signal decision.

  As a result, the guest can signal the host unnecessarily,
  and then the host can throttle the guest because the host
  thinks the guest is buggy or malicious; finally the user
  running stress test can perceive intermittent freeze of
  the guest.

  This patch brings back the test, and properly handles the
  in-place consumption APIs used by NetVSC (see get_next_pkt_raw(),
  put_pkt_raw() and commit_rd_index()).

  Fixes: a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in
  hv_need_to_signal_on_read()")

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

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

2017-02-02 Thread Daemon

I'm unsure that I have same issue but seems that yes.
I'm unable to boot latest kernel after upgrade to 16.10, It's just hangs with 
no disk activity, all latest updates where installed using 4.4.0-59 (it boots 
properly) but no luck.
I also tried latest nouveau, latest available nvidia driver from driver manager 
and latest available nvidia driver from nvidia site (375.26) but still unable 
to boot 4.8 kernel :(
Can anyone help or maybe additional info needed ?

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-5.7-generic/ms10-35-mcdivittB0-kernel__4.10.0-5.7__2017-02-02_23-36-00/results-index.html

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

Title:
  linux: 4.9.0-11.12 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.9.0-6.7 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-development-workflow/+bug/1642044/+subscriptions

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

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-5.7-generic/ms10-34-mcdivittB0-kernel__4.10.0-5.7__2017-02-02_23-35-00/results-index.html

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

Title:
  linux: 4.9.0-11.12 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.9.0-6.7 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-development-workflow/+bug/1642044/+subscriptions

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

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

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

apport-collect 1661430

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

Title:
[Hyper-V] Fix ring buffer handling to avoid host throttling

Status in linux package in Ubuntu:
Incomplete

Bug description:
An unfortunate side effect of some of the recent work done to improve
ring buffer performance made a situation where the host would
interpret guest requests as a denial of service attack, pausing guest
communications for five seconds. This series of fixes corrects this
problem.

Needed for each kernel that has included a389fcfd2cb5 ("Drivers: hv:
vmbus: Fix signaling logic in hv_need_to_signal_on_read()")

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=74198eb4a42c4a3c4fbef08fa01a291a282f7c2e

Drivers: hv: vmbus: Base host signaling strictly on the ring state
One of the factors that can result in the host concluding that a given
guest in mounting a DOS attack is if the guest generates interrupts
to the host when the host is not expecting it. If these "spurious"
interrupts reach a certain rate, the host can throttle the guest to
minimize the impact. The host computation of the "expected number
of interrupts" is strictly based on the ring transitions. Until
the host logic is fixed, base the guest logic to interrupt solely
on the ring state.

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f6ee4e7d83586c8b10bd4f2f4346353d04ce884

Drivers: hv: vmbus: On write cleanup the logic to interrupt the host
Signal the host when we determine the host is to be signaled.
The currrent code determines the need to signal in the ringbuffer
code and actually issues the signal elsewhere. This can result
in the host viewing this interrupt as spurious since the host may also
poll the channel. Make the necessary adjustments.

https://git.kernel.org/cgit/linux/kernel/git/next/linux-
next.git/commit/?id=3372592a140db69fd63837e81f048ab4abf8111e

Drivers: hv: vmbus: On the read path cleanup the logic to interrupt the host
Signal the host when we determine the host is to be signaled -
on th read path. The currrent code determines the need to signal in the
ringbuffer code and actually issues the signal elsewhere. This can result
in the host viewing this interrupt as spurious since the host may also
poll the channel. Make the necessary adjustments.

https://git.kernel.org/cgit/linux/kernel/git/next/linux-
next.git/commit/?id=433e19cf33d34bb6751c874a9c00980552fe508c

Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read()
Commit a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in
hv_need_to_signal_on_read()")
added the proper mb(), but removed the test "prev_write_sz < pending_sz"
when making the signal decision.

As a result, the guest can signal the host unnecessarily,
and then the host can throttle the guest because the host
thinks the guest is buggy or malicious; finally the user
running stress test can perceive intermittent freeze of
the guest.

This patch brings back the test, and properly handles the
in-place consumption APIs used by NetVSC (see get_next_pkt_raw(),
put_pkt_raw() and commit_rd_index()).

Fixes: a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in
hv_need_to_signal_on_read()")

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

[Kernel-packages] [Bug 1661430] [NEW] [Hyper-V] Fix ring buffer handling to avoid host throttling

2017-02-02 Thread Joshua R. Poulson

Public bug reported:

An unfortunate side effect of some of the recent work done to improve
ring buffer performance made a situation where the host would interpret
guest requests as a denial of service attack, pausing guest
communications for five seconds. This series of fixes corrects this
problem.

Needed for each kernel that has included a389fcfd2cb5 ("Drivers: hv:
vmbus: Fix signaling logic in hv_need_to_signal_on_read()")

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=74198eb4a42c4a3c4fbef08fa01a291a282f7c2e

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f6ee4e7d83586c8b10bd4f2f4346353d04ce884

https://git.kernel.org/cgit/linux/kernel/git/next/linux-
next.git/commit/?id=3372592a140db69fd63837e81f048ab4abf8111e

https://git.kernel.org/cgit/linux/kernel/git/next/linux-
next.git/commit/?id=433e19cf33d34bb6751c874a9c00980552fe508c

This patch brings back the test, and properly handles the
in-place consumption APIs used by NetVSC (see get_next_pkt_raw(),
put_pkt_raw() and commit_rd_index()).

Fixes: a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in
hv_need_to_signal_on_read()")

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

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

Title:
[Hyper-V] Fix ring buffer handling to avoid host throttling

Status in linux package in Ubuntu:
Incomplete

Needed for each kernel that has included a389fcfd2cb5 ("Drivers: hv:
vmbus: Fix signaling logic in hv_need_to_signal_on_read()")

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=74198eb4a42c4a3c4fbef08fa01a291a282f7c2e

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f6ee4e7d83586c8b10bd4f2f4346353d04ce884

[Kernel-packages] [Bug 1661363] Re: Fails to load compressed kernels on arm64

2017-02-02 Thread dann frazier

As mentioned on IRC, we shouldn't include amd64 in this unless we know
that it actually improves amd64 support. My guess is that this doesn't
help x86 - IIRC, those images decompress themselves at runtime.

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

Title:
  Fails to load compressed kernels on arm64

Status in kexec-tools package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  kexec-tools will not load a compressed kernel on arm64. Ubuntu ships 
compressed kernel images on arm64 starting with 16.10 (and hwe kernels for 
16.04). A workaround is to manually decompress the kernel before loading it, 
but this is not supported by the use-kexec-for-reboot-by-default feature of the 
kexec-tools package.

  [Test Case]
  ubuntu@ubuntu:~$ sudo file /boot/vmlinuz-4.9.0-15-generic
  /boot/vmlinuz-4.9.0-15-generic: gzip compressed data, max compression, from 
Unix
  ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.9.0-15-generic -t Image
  arch_process_options:141: command_line: (null)
  arch_process_options:143: initrd: (null)
  arch_process_options:144: dtb: (null)
  kernel: 0x8ff61010 kernel_size: 0x6ee18b
  get_memory_ranges_iomem_cb: 4000 - bfff : System RAM
  get_memory_ranges_iomem_cb: 0001 - 00013858 : System RAM
  get_memory_ranges_iomem_cb: 00013875 - 00013bc1 : System RAM
  get_memory_ranges_iomem_cb: 00013c00 - 00013fff : System RAM
  image_arm64_probe: Bad arm64 image header.
  elf_arm64_probe: Not an ELF executable.
  image_arm64_probe: Bad arm64 image header.
  Cannot determine the file type of /boot/vmlinuz-4.9.0-15-generic

  [Regression Risk]
  kexec-tools did not support arm64 until zesty so, assuming the fix is 
localized to arm64 code, regression risk is negligible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1661363/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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

2017-02-02 Thread Michael Lueck

The 3.19.0-80 kernel build still has the defect. I purged it back off
our server. Booted back to 4.4.0-59.

-- 
You 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:
  In Progress
Status in linux source package in Xenial:
  In Progress

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

[Kernel-packages] [Bug 1661363] Re: Fails to load compressed kernels on arm64

2017-02-02 Thread Manoj Iyer

The debian/control file lists gnu-efi and libz-dev only for ia64, since
amd64, and arm64 (may be other archs) also need these dependencies for
it to support compressed kernel we need something like the following
change for it to work on those archs.

-Build-Depends: debhelper (>= 7.0.0), dh-autoreconf, gnu-efi (>=3.0a-4)[ia64], 
libz-dev[ia64], po-debconf
+Build-Depends: debhelper (>= 7.0.0), dh-autoreconf, gnu-efi (>=3.0a-4)[amd64 
arm64 ia64], libz-dev[amd64 arm64 ia64], po-debconf

I will upload a patch to zesty shortly.

** Changed in: kexec-tools (Ubuntu)
 Assignee: (unassigned) => Manoj Iyer (manjo)

** Changed in: kexec-tools (Ubuntu)
   Status: New => In Progress

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

Title:
  Fails to load compressed kernels on arm64

Status in kexec-tools package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  kexec-tools will not load a compressed kernel on arm64. Ubuntu ships 
compressed kernel images on arm64 starting with 16.10 (and hwe kernels for 
16.04). A workaround is to manually decompress the kernel before loading it, 
but this is not supported by the use-kexec-for-reboot-by-default feature of the 
kexec-tools package.

  [Test Case]
  ubuntu@ubuntu:~$ sudo file /boot/vmlinuz-4.9.0-15-generic
  /boot/vmlinuz-4.9.0-15-generic: gzip compressed data, max compression, from 
Unix
  ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.9.0-15-generic -t Image
  arch_process_options:141: command_line: (null)
  arch_process_options:143: initrd: (null)
  arch_process_options:144: dtb: (null)
  kernel: 0x8ff61010 kernel_size: 0x6ee18b
  get_memory_ranges_iomem_cb: 4000 - bfff : System RAM
  get_memory_ranges_iomem_cb: 0001 - 00013858 : System RAM
  get_memory_ranges_iomem_cb: 00013875 - 00013bc1 : System RAM
  get_memory_ranges_iomem_cb: 00013c00 - 00013fff : System RAM
  image_arm64_probe: Bad arm64 image header.
  elf_arm64_probe: Not an ELF executable.
  image_arm64_probe: Bad arm64 image header.
  Cannot determine the file type of /boot/vmlinuz-4.9.0-15-generic

  [Regression Risk]
  kexec-tools did not support arm64 until zesty so, assuming the fix is 
localized to arm64 code, regression risk is negligible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1661363/+subscriptions

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

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

2017-02-02 Thread Tomas Janousek

So I did a little bisecting today on mainline x86_64 kernels with
CONFIG_SLUB:

v4.4 Startup finished in 2.718s (kernel) + 11.831s 
(userspace) = 14.549s
v4.5 Startup finished in 2.707s (kernel) + 12.777s 
(userspace) = 15.484s
v4.6-rc4-1018-g5a5f0792e98b  Startup finished in 2.970s (kernel) + 13.641s 
(userspace) = 16.611s
v4.6-3615-g1eccc6e1529e  Startup finished in 3.005s (kernel) + 14.063s 
(userspace) = 17.069s
v4.6-5396-g07b75260ebc2  Startup finished in 3.044s (kernel) + 14.932s 
(userspace) = 17.977s
v4.6-5931-gf4c80d5a16eb  Startup finished in 3.057s (kernel) + 13.429s 
(userspace) = 16.487s
v4.6-6084-g78975f23cba0  Startup finished in 3.050s (kernel) + 13.903s 
(userspace) = 16.954s
v4.6-5050-g18726ca8b34b  Startup finished in 3.015s (kernel) + 13.510s 
(userspace) = 16.525s
v4.6-5055-g6052b7880a95  Startup finished in 3.029s (kernel) + 13.519s 
(userspace) = 16.549s
v4.6-5058-g76b342bdc71b  Startup finished in 2.998s (kernel) + 14.179s 
(userspace) = 17.177s
v4.6-5060-g801faf0db894  Startup finished in 3.064s (kernel) + 14.667s 
(userspace) = 17.732s
v4.6-5061-g81ae6d03952c  Startup finished in 3.057s (kernel) + 18.357s 
(userspace) = 21.414s
v4.6-5073-g9cc3387fa29f  Startup finished in 3.073s (kernel) + 17.976s 
(userspace) = 21.049s
v4.6-5119-g682a3385e773  Startup finished in 3.089s (kernel) + 17.987s 
(userspace) = 21.077s
v4.6-6266-ga05a70db34ba  Startup finished in 3.037s (kernel) + 18.550s 
(userspace) = 21.588s
v4.6-7135-g0eff4589c36e  Startup finished in 3.008s (kernel) + 18.074s 
(userspace) = 21.082s
v4.7-rc5-1395-g877fa9a42ddc  Startup finished in 3.179s (kernel) + 19.147s 
(userspace) = 22.327s
v4.8 Startup finished in 3.197s (kernel) + 20.836s 
(userspace) = 24.034s
v4.9.7   Startup finished in 3.674s (kernel) + 20.034s 
(userspace) = 23.708s
v4.9.7 + the two patches Startup finished in 3.518s (kernel) + 13.027s 
(userspace) = 16.546s

What we can observe from this:

The big bump came in
https://github.com/torvalds/linux/commit/81ae6d03952c1bfb96e1a716809bd65e7cd14360
(or alternatively in
https://github.com/torvalds/linux/commit/801faf0db8947e01877920e848a4d338dd7a99e7
for CONFIG_SLAB, if bz.k.o is trustworthy). This is likely fixed by
https://github.com/torvalds/linux/commit/86d9f48534e800e4d62cdc1b5aaf539f4c1d47d6,
https://github.com/torvalds/linux/commit/13583c3d3224508582ec03d881d0b68dd3ee8e10
and
https://github.com/torvalds/linux/commit/89e364db71fb5e7fc8d93228152abfa67daf35fa.
The last two are not in stable, though.

Speaking of
https://github.com/torvalds/linux/commit/86d9f48534e800e4d62cdc1b5aaf539f4c1d47d6,
this went into v4.8.7 as
https://github.com/torvalds/linux/commit/68adb469dd3b28513c5b548df3437f2bc1a83e43,
so that may be the fix you were looking for in comment #65.

There are also lots of small performance regressions here and there that
may be difficult to bisect. A second in userspace between v4.4 and v4.5
and another second between v4.5 and v4.6. Some 300 ms in kernel between
v4.5 and v4.6, 200 ms between v4.6 and v4.7 and another 300 ms between
v4.8 and v4.9. That's here, on my .config and my hardware. Dimitrij has
10 seconds in kernel between v4.7 and v4.8-rc1, but I can't see anything
like that here. (In this case you might want to look into dmesg if it's
a general slowdown or there's one thing that blocks for 10 secs. I
suspect there might be.)

I think that these other slowdowns that I and Dimitrij and possibly
others are experiencing are likely unrelated to the main issue here
(https://bugzilla.kernel.org/show_bug.cgi?id=172981,
https://bugzilla.kernel.org/show_bug.cgi?id=172991) and we'll need to
bisect further ourselves. :-)

** Bug watch added: Linux Kernel Bug Tracker #172981
   http://bugzilla.kernel.org/show_bug.cgi?id=172981

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

Title:
  [4.8 regression] boot has become very slow

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

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:

[Kernel-packages] [Bug 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)

We are bisecting between those two kernel versions to identify the
commit that introduced this regression.  Some of the test kernels I post
will be bad and some will be good.  At the end of the testing the bisect
will point to one particular commit.

I built the first test kernel, up to the following commit:
aee3bfa3307cd0da2126bdc0ea359dabea5ee8f7

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

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

Thanks in advance

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

Title:
  Regression:  HDMI audio produces no sound (Skylake NUC)

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

Bug description:
  After upgrade from Xenial 16.04 to Yakkety 16.10, playing audio over HDMI no 
longer produces sound.
  * When booting with old kernel from Xenial (4.4.0-59), HDMI audio works fine
  * Audio from headphone jack works fine
  * Userspace seems to be happily playing to HDMI audio device, but no sound 
produced at HDMI sink (Samsung TV)

  Any of a wide range of pre-built mainline kernels fail to produce HDMI
  audio, but with a different failure mode (HDMI audio does not seem to
  be enumerated in the same way as in the Ubuntu kernels.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  israel 1973 F pulseaudio
   /dev/snd/controlC1:  israel 1973 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jan 20 08:58:35 2017
  HibernationDevice: RESUME=UUID=ca27f739-071f-4c25-974e-0d0f0614b21c
  InstallationDate: Installed on 2016-10-03 (108 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=90c3e094-e890-4c35-a0d2-0a358f5d2430 ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-01-13 (6 days ago)
  dmi.bios.date: 06/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-405
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up

2017-02-02 Thread lotek

4.8.0-34-generic #36~lp1659340Patched   passed

uname -a 
Linux mex-notebook 4.8.0-34-generic #36~lp1659340Patched SMP Thu Feb 2 21:04:45 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Linux kernel 4.8 hangs at boot up

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

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1661394] Re: Asus X206H Bluetooth / WLAN Malfunktion

2017-02-02 Thread Benny

** Attachment added: "lspic-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661394/+attachment/4812228/+files/lspic-vnvn.log

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

Title:
  Asus X206H Bluetooth / WLAN Malfunktion

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi There,

  got a unpleasant bug in (K)ubuntu 16.10 which wont establish a
  connection simultaneously with bluetooth and WLAN. If Bluetooth is
  established, WLAN connection gets down to 0 Bytes, but seems to stay
  connected. The same goes via Bluetooth. The Both work just a few
  seconds at the same time, then one of them gets "offline", but stay
  connected. I tested that with Bluetooth Earplugs, and the connection
  seems to go bad in form of noisy sound, in that time WLAN is
  continuously working until it goes down to 0 Bytes.

  Kernel Version is:
  Ubuntu 4.8.0-34.36-generic 4.8.11

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

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

[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up

Upstream has a patch that may fix this bug:
https://git.kernel.org/cgit/linux/kernel/git/efi/efi.git/commit/?h=urgent=090abfc9dc7faf3f84799f956158c8c3af149a81

I built a test kernel with this patch applied.  The test kernel can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1659340/patched/

Can you try this kernel and see if it resolves this bug?

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

Title:
  Linux kernel 4.8 hangs at boot up

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

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

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

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

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

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

apport-collect 1661394

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

Title:
  Asus X206H Bluetooth / WLAN Malfunktion

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi There,

  got a unpleasant bug in (K)ubuntu 16.10 which wont establish a
  connection simultaneously with bluetooth and WLAN. If Bluetooth is
  established, WLAN connection gets down to 0 Bytes, but seems to stay
  connected. The same goes via Bluetooth. The Both work just a few
  seconds at the same time, then one of them gets "offline", but stay
  connected. I tested that with Bluetooth Earplugs, and the connection
  seems to go bad in form of noisy sound, in that time WLAN is
  continuously working until it goes down to 0 Bytes.

  Kernel Version is:
  Ubuntu 4.8.0-34.36-generic 4.8.11

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

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

[Kernel-packages] [Bug 1661394] [NEW] Asus X206H Bluetooth / WLAN Malfunktion

2017-02-02 Thread Benny

Public bug reported:

Hi There,

got a unpleasant bug in (K)ubuntu 16.10 which wont establish a
connection simultaneously with bluetooth and WLAN. If Bluetooth is
established, WLAN connection gets down to 0 Bytes, but seems to stay
connected. The same goes via Bluetooth. The Both work just a few seconds
at the same time, then one of them gets "offline", but stay connected. I
tested that with Bluetooth Earplugs, and the connection seems to go bad
in form of noisy sound, in that time WLAN is continuously working until
it goes down to 0 Bytes.

Kernel Version is:
Ubuntu 4.8.0-34.36-generic 4.8.11

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

** Attachment added: "DMESG.txt"
   https://bugs.launchpad.net/bugs/1661394/+attachment/4812227/+files/DMESG.txt

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

Title:
  Asus X206H Bluetooth / WLAN Malfunktion

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi There,

  got a unpleasant bug in (K)ubuntu 16.10 which wont establish a
  connection simultaneously with bluetooth and WLAN. If Bluetooth is
  established, WLAN connection gets down to 0 Bytes, but seems to stay
  connected. The same goes via Bluetooth. The Both work just a few
  seconds at the same time, then one of them gets "offline", but stay
  connected. I tested that with Bluetooth Earplugs, and the connection
  seems to go bad in form of noisy sound, in that time WLAN is
  continuously working until it goes down to 0 Bytes.

  Kernel Version is:
  Ubuntu 4.8.0-34.36-generic 4.8.11

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

-- 
Mailing list: https://launchpad.net/~kernel-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)

I built the next test kernel with commit 59ed4b6 reverted.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1649326/commit-59ed4b67da-reverted

Can you give this kernel a try?

-- 
You 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 1619918] Re: [REVERT][v4.10][V2] btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in btrfs_ioctl

On 02/02/2017 03:57 PM, Greg KH wrote:
> On Thu, Feb 02, 2017 at 02:58:16PM -0500, Joseph Salisbury wrote:
>> On 02/02/2017 01:23 PM, Greg KH wrote:
>>> On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
 Hello,

 Please consider reverting commit
 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release.
>>> What release can I remove it from?
>>>
>>> It isn't in 4.4.y, and 4.9.y doesn't make much sense, unless it's
>>> reverted in Linus's tree already?
>>>
>>> totally confused.
>>>
>>> greg k-h
>> Sorry, commit 4c63c2454eff996c5e27991221106eb511f7db38 was introduced in
>> mainline in v4.7-rc1.  The request should be only for kernels newer than
>> 4.7-rc1, so 4.9 and 4.10.
>>
>> I assume it will come down to 4.9 once reverted in mainline. 
> Let me know when it is reverted, and what that revert commit is please.
>
> thanks,
>
> greg k-h

Will do.


Thanks again,


Joe

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

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

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Kernel-packages] [Bug 1619918] Re: [REVERT][v4.10][V2] btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in btrfs_ioctl

2017-02-02 Thread Greg KH

On Thu, Feb 02, 2017 at 02:58:16PM -0500, Joseph Salisbury wrote:
> On 02/02/2017 01:23 PM, Greg KH wrote:
> > On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
> >> Hello,
> >>
> >> Please consider reverting commit
> >> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release.
> > What release can I remove it from?
> >
> > It isn't in 4.4.y, and 4.9.y doesn't make much sense, unless it's
> > reverted in Linus's tree already?
> >
> > totally confused.
> >
> > greg k-h
> 
> Sorry, commit 4c63c2454eff996c5e27991221106eb511f7db38 was introduced in
> mainline in v4.7-rc1.  The request should be only for kernels newer than
> 4.7-rc1, so 4.9 and 4.10.
> 
> I assume it will come down to 4.9 once reverted in mainline. 

Let me know when it is reverted, and what that revert commit is please.

thanks,

greg k-h

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

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

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Kernel-packages] [Bug 1642044] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 10, failed: 2

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/4.10.0-5.7-generic/ms10-35-mcdivittB0-kernel__4.10.0-5.7__2017-02-02_19-48-00/results-index.html

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

Title:
  linux: 4.9.0-11.12 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.9.0-6.7 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-development-workflow/+bug/1642044/+subscriptions

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

[Kernel-packages] [Bug 1658839] Re: package linux-firmware 1.127.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-02-02 Thread Mike Housley

For about the last month I have encountered this error. While /boot does
appear to be full it is only after the update starts generating images
that it can't find. Running "sudo apt-get autoremove" will do the same
thing:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up initramfs-tools (0.103ubuntu4.6) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-firmware (1.127.23) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-107-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-106-generic
grep: /boot/config-3.13.0-106-generic: No such file or directory
update-initramfs: Generating /boot/initrd.img-3.13.0-105-generic
grep: /boot/config-3.13.0-105-generic: No such file or directory
update-initramfs: Generating /boot/initrd.img-3.13.0-103-generic
grep: /boot/config-3.13.0-103-generic: No such file or directory
update-initramfs: Generating /boot/initrd.img-3.13.0-101-generic
grep: /boot/config-3.13.0-101-generic: No such file or directory
update-initramfs: Generating /boot/initrd.img-3.13.0-100-generic
grep: /boot/config-3.13.0-100-generic: No such file or directory
update-initramfs: Generating /boot/initrd.img-3.13.0-98-generic
grep: /boot/config-3.13.0-98-generic: No such file or directory
update-initramfs: Generating /boot/initrd.img-3.13.0-96-generic
grep: /boot/config-3.13.0-96-generic: No such file or directory
update-initramfs: Generating /boot/initrd.img-3.13.0-95-generic
grep: /boot/config-3.13.0-95-generic: No such file or directory
update-initramfs: Generating /boot/initrd.img-3.13.0-93-generic
grep: /boot/config-3.13.0-93-generic: No such file or directory
update-initramfs: Generating /boot/initrd.img-3.13.0-92-generic
grep: /boot/config-3.13.0-92-generic: No such file or directory

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.13.0-92-generic with 1.
dpkg: error processing package linux-firmware (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-firmware; however:
  Package linux-firmware is not configured yet.

dpkg: error processing package linux-image-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-image-generic (= 3.13.0.107.115); however:
  Package linux-image-generic is not configured yet.

How can I stop the creation of old kernel images?

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

Title:
  package linux-firmware 1.127.23 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  The error occurred during the automated software update.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-firmware 1.127.23
  ProcVersionSignature: Ubuntu 4.4.0-42.62~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Mon Jan 23 18:05:15 2017
  Dependencies:
   
  DuplicateSignature: package:linux-firmware:1.127.23:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-02-27 (696 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.127.23 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1659623] Re: Shutdown/reboot hang on Dell XPS 15 9550 BIOS 1.2.18+

2017-02-02 Thread Shinjo Park

I tested both 4.8.17 and 4.9.6 mainline kernel, shutdown/reboot both
works fine there. However 4.8.0-34-generic Ubuntu kernel still has the
problem.

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

Title:
  Shutdown/reboot hang on Dell XPS 15 9550 BIOS 1.2.18+

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Dell XPS 15 9550 BIOS 1.2.18+, shutdown/reboot job is delayed for
  several seconds in Ubuntu kernel. After shutdown screen appears and
  all shutdown sequence had been done, the power LED turns off; however
  the front LED is flashing in orange for several seconds and the system
  finally turns off. Rebooting is also not working: front LED flashes in
  orange and the system just turns off.

  Switching to mainline kernel 4.9.6, or downgrading to BIOS 1.2.16
  solved the problem. Other Linux distro users didn't observed the
  problem, see also:

  * 
https://www.reddit.com/r/Dell/comments/5przxq/new_dell_xps_15_9550_bios_1219/
  * 
https://www.reddit.com/r/Dell/comments/5l9n3b/xps_15_9550_bios_1218_ubuntu_1610_shutdown_problem/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psj5638 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Jan 26 19:17:24 2017
  HibernationDevice: RESUME=UUID=2cfb78ae-e2b8-4d3a-9ab2-a61ae1a79fd1
  InstallationDate: Installed on 2016-01-21 (371 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=db90ced3-4cfe-4001-b877-d4aa35e7260f ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (103 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.asset.tag: ainazi
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: ainazi
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up

** No longer affects: linux (Ubuntu Trusty)

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

Title:
  Linux kernel 4.8 hangs at boot up

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

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1642044] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 18, failed: 0

tests ran:  18, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-5.7-generic/ms10-34-mcdivittB0-kernel__4.10.0-5.7__2017-02-02_19-25-00/results-index.html

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

Title:
  linux: 4.9.0-11.12 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.9.0-6.7 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-development-workflow/+bug/1642044/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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

Can you test the following 3.19 based kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/11849331

-- 
You 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:
  In Progress
Status in linux source package in Xenial:
  In Progress

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

[Kernel-packages] [Bug 1619918] [REVERT][v4.10][V2] btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in btrfs_ioctl

On 02/02/2017 01:23 PM, Greg KH wrote:
> On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
>> Hello,
>>
>> Please consider reverting commit
>> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release.
> What release can I remove it from?
>
> It isn't in 4.4.y, and 4.9.y doesn't make much sense, unless it's
> reverted in Linus's tree already?
>
> totally confused.
>
> greg k-h

Sorry, commit 4c63c2454eff996c5e27991221106eb511f7db38 was introduced in
mainline in v4.7-rc1.  The request should be only for kernels newer than
4.7-rc1, so 4.9 and 4.10.

I assume it will come down to 4.9 once reverted in mainline.

I updated the subject.

Thanks,

Joe

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

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

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Kernel-packages] [Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot

2017-02-02 Thread jeffrey leung

I've asked the engineer to try the latest v4.10-rc6 kernel. This is
their first test with 16.04.1, so unknown if it works with previous
kernel version. I've asked them to check older versions to see if it
exists.

I'll update the tag and comment when I hear back from them. Thanks for
the recommendation.

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

Title:
  kernel crash when NVMe drive inserted in one slot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Opening this on behalf of one of my colleagues at Cisco, we're seeing
  an issue on our new S-series S3260 server that's causing the kernel to
  crash.

  If we have an NVMe device inserted into one of two drive slots, we
  will see kernel crash only with Ubuntu. With an NVMe drive in the bad
  slot, other OS's will work fine. If we move the NVMe drive out of the
  bad slot and into the other slot, everything is working fine as
  expected. We only see the kernel crash with an NVMe drive in that bad
  slot when using Ubuntu. We tested with HGST and Intel NVMe drives and
  were able to reproduce the issue with both. HGST reviewed some logs
  and they don't believe at this time the issue is with the NVMe drives.

  We're hoping someone from Canonical can take a look to understand what
  is the difference between the working and failing slot. The data
  collection was done with the NVMe drive inserted in the working slot
  so we could access the OS.

  I had a connection time out when trying to use ubuntu-bug, so I saved
  the apport file and will attach to the bug. I have collected the
  kernel and syslog as well, but they are ~9GB. I found a call trace in
  the kernel log start on Jan 25 06:02:54 and floods the logs
  afterwards. I will include the call trace in a separate text file on
  the attachment.

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

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

[Kernel-packages] [Bug 1656876] Re: Xenial update to v4.4.43 stable release

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

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

Title:
  Xenial update to v4.4.43 stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The v4.4.43 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the v4.4.43 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1658091] Re: Xenial update to v4.4.44 stable release

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

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

Title:
  Xenial update to v4.4.44 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.4.44 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.44 stable release shall be
  applied:

  Input: xpad - use correct product id for x360w controllers
  Input: i8042 - add Pegatron touchpad to noloop table
  selftests: do not require bash to run netsocktests testcase
  selftests: do not require bash for the generated test
  mm: fix devm_memremap_pages crash, use mem_hotplug_{begin, done}
  ocfs2: fix crash caused by stale lvb with fsdlm plugin
  mm/hugetlb.c: fix reservation race when freeing surplus pages
  KVM: x86: fix emulation of "MOV SS, null selector"
  KVM: eventfd: fix NULL deref irqbypass consumer
  jump_labels: API for flushing deferred jump label updates
  KVM: x86: flush pending lapic jump label updates on module unload
  KVM: x86: add Align16 instruction flag
  KVM: x86: add asm_safe wrapper
  KVM: x86: emulate FXSAVE and FXRSTOR
  KVM: x86: Introduce segmented_write_std
  nl80211: fix sched scan netlink socket owner destruction
  USB: serial: kl5kusb105: fix line-state error handling
  USB: serial: ch341: fix initial modem-control state
  USB: serial: ch341: fix open error handling
  USB: serial: ch341: fix control-message error handling
  USB: serial: ch341: fix open and resume after B0
  Input: elants_i2c - avoid divide by 0 errors on bad touchscreen data
  i2c: print correct device invalid address
  i2c: fix kernel memory disclosure in dev interface
  xhci: fix deadlock at host remove by running watchdog correctly
  vme: Fix wrong pointer utilization in ca91cx42_slave_get
  mnt: Protect the mountpoint hashtable with mount_lock
  tty/serial: atmel_serial: BUG: stop DMA from transmitting in stop_tx
  sysrq: attach sysrq handler correctly for 32-bit kernel
  sysctl: Drop reference added by grab_header in proc_sys_readdir
  drm/radeon: drop verde dpm quirks
  USB: serial: ch341: fix resume after reset
  USB: serial: ch341: fix modem-control and B0 handling
  x86/cpu: Fix bootup crashes by sanitizing the argument of the 'clearcpuid=' 
command-line option
  btrfs: fix locking when we put back a delayed ref that's too new
  btrfs: fix error handling when run_delayed_extent_op fails
  pinctrl: meson: fix gpio request disabling other modes
  pNFS: Fix race in pnfs_wait_on_layoutreturn
  NFS: Fix a performance regression in readdir
  NFSv4.1: nfs4_fl_prepare_ds must be careful about reporting success.
  cpufreq: powernv: Disable preemption while checking CPU throttling state
  block: cfq_cpd_alloc() should use @gfp
  ACPI / APEI: Fix NMI notification handling
  blk-mq: Always schedule hctx->next_cpu
  bus: vexpress-config: fix device reference leak
  powerpc/ibmebus: Fix further device reference leaks
  powerpc/ibmebus: Fix device reference leaks in sysfs interface
  pinctrl: sh-pfc: Do not unconditionally support PIN_CONFIG_BIAS_DISABLE
  Linux 4.4.44

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

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

[Kernel-packages] [Bug 1660993] Re: Xenial update to v4.4.45 stable release

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

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

Title:
  Xenial update to v4.4.45 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.4.45 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.45 stable release shall be
  applied:

  ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to 
it
  IB/mlx5: Wait for all async command completions to complete
  IB/mlx4: Set traffic class in AH
  IB/mlx4: Fix out-of-range array index in destroy qp flow
  IB/mlx4: Fix port query for 56Gb Ethernet links
  IB/mlx4: When no DMFS for IPoIB, don't allow NET_IF QPs
  IB/IPoIB: Remove can't use GFP_NOIO warning
  perf scripting: Avoid leaking the scripting_context variable
  ARM: dts: imx31: fix clock control module interrupts description
  ARM: dts: imx31: move CCM device node to AIPS2 bus devices
  ARM: dts: imx31: fix AVIC base address
  tmpfs: clear S_ISGID when setting posix ACLs
  x86/PCI: Ignore _CRS on Supermicro X8DTH-i/6/iF/6F
  svcrpc: don't leak contexts on PROC_DESTROY
  fuse: clear FR_PENDING flag when moving requests out of pending queue
  PCI: Enumerate switches below PCI-to-PCIe bridges
  HID: corsair: fix DMA buffers on stack
  HID: corsair: fix control-transfer error handling
  mmc: mxs-mmc: Fix additional cycles after transmission stop
  ieee802154: atusb: do not use the stack for buffers to make them DMA able
  mtd: nand: xway: disable module support
  x86/ioapic: Restore IO-APIC irq_chip retrigger callback
  qla2xxx: Fix crash due to null pointer access
  ubifs: Fix journal replay wrt. xattr nodes
  clocksource/exynos_mct: Clear interrupt when cpu is shut down
  svcrdma: avoid duplicate dma unmapping during error recovery
  ARM: 8634/1: hw_breakpoint: blacklist Scorpion CPUs
  ceph: fix bad endianness handling in parse_reply_info_extra
  ARM: dts: da850-evm: fix read access to SPI flash
  arm64/ptrace: Preserve previous registers for short regset write
  arm64/ptrace: Preserve previous registers for short regset write - 2
  arm64/ptrace: Preserve previous registers for short regset write - 3
  arm64/ptrace: Avoid uninitialised struct padding in fpr_set()
  arm64/ptrace: Reject attempts to set incomplete hardware breakpoint fields
  ARM: dts: imx6qdl-nitrogen6_max: fix sgtl5000 pinctrl init
  ARM: ux500: fix prcmu_is_cpu_in_wfi() calculation
  ARM: 8613/1: Fix the uaccess crash on PB11MPCore
  blackfin: check devm_pinctrl_get() for errors
  ite-cir: initialize use_demodulator before using it
  dmaengine: pl330: Fix runtime PM support for terminated transfers
  selftest/powerpc: Wrong PMC initialized in pmc56_overflow test
  arm64: avoid returning from bad_mode
  Linux 4.4.45

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

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

[Kernel-packages] [Bug 1660993] Re: Xenial update to v4.4.45 stable release

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

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

Title:
  Xenial update to v4.4.45 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.4.45 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.45 stable release shall be
  applied:

  ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to 
it
  IB/mlx5: Wait for all async command completions to complete
  IB/mlx4: Set traffic class in AH
  IB/mlx4: Fix out-of-range array index in destroy qp flow
  IB/mlx4: Fix port query for 56Gb Ethernet links
  IB/mlx4: When no DMFS for IPoIB, don't allow NET_IF QPs
  IB/IPoIB: Remove can't use GFP_NOIO warning
  perf scripting: Avoid leaking the scripting_context variable
  ARM: dts: imx31: fix clock control module interrupts description
  ARM: dts: imx31: move CCM device node to AIPS2 bus devices
  ARM: dts: imx31: fix AVIC base address
  tmpfs: clear S_ISGID when setting posix ACLs
  x86/PCI: Ignore _CRS on Supermicro X8DTH-i/6/iF/6F
  svcrpc: don't leak contexts on PROC_DESTROY
  fuse: clear FR_PENDING flag when moving requests out of pending queue
  PCI: Enumerate switches below PCI-to-PCIe bridges
  HID: corsair: fix DMA buffers on stack
  HID: corsair: fix control-transfer error handling
  mmc: mxs-mmc: Fix additional cycles after transmission stop
  ieee802154: atusb: do not use the stack for buffers to make them DMA able
  mtd: nand: xway: disable module support
  x86/ioapic: Restore IO-APIC irq_chip retrigger callback
  qla2xxx: Fix crash due to null pointer access
  ubifs: Fix journal replay wrt. xattr nodes
  clocksource/exynos_mct: Clear interrupt when cpu is shut down
  svcrdma: avoid duplicate dma unmapping during error recovery
  ARM: 8634/1: hw_breakpoint: blacklist Scorpion CPUs
  ceph: fix bad endianness handling in parse_reply_info_extra
  ARM: dts: da850-evm: fix read access to SPI flash
  arm64/ptrace: Preserve previous registers for short regset write
  arm64/ptrace: Preserve previous registers for short regset write - 2
  arm64/ptrace: Preserve previous registers for short regset write - 3
  arm64/ptrace: Avoid uninitialised struct padding in fpr_set()
  arm64/ptrace: Reject attempts to set incomplete hardware breakpoint fields
  ARM: dts: imx6qdl-nitrogen6_max: fix sgtl5000 pinctrl init
  ARM: ux500: fix prcmu_is_cpu_in_wfi() calculation
  ARM: 8613/1: Fix the uaccess crash on PB11MPCore
  blackfin: check devm_pinctrl_get() for errors
  ite-cir: initialize use_demodulator before using it
  dmaengine: pl330: Fix runtime PM support for terminated transfers
  selftest/powerpc: Wrong PMC initialized in pmc56_overflow test
  arm64: avoid returning from bad_mode
  Linux 4.4.45

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

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

[Kernel-packages] [Bug 1660994] Re: Xenial update to v4.4.46 stable release

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

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

Title:
  Xenial update to v4.4.46 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.4.46 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.46 stable release shall be
  applied:

  fbdev: color map copying bounds checking
  tile/ptrace: Preserve previous registers for short regset write
  drm: Fix broken VT switch with video=1366x768 option
  mm/mempolicy.c: do not put mempolicy before using its nodemask
  sysctl: fix proc_doulongvec_ms_jiffies_minmax()
  ISDN: eicon: silence misleading array-bounds warning
  RDMA/cma: Fix unknown symbol when CONFIG_IPV6 is not enabled
  s390/ptrace: Preserve previous registers for short regset write
  can: c_can_pci: fix null-pointer-deref in c_can_start() - set device pointer
  can: ti_hecc: add missing prepare and unprepare of the clock
  ARC: udelay: fix inline assembler by adding LP_COUNT to clobber list
  ARC: [arcompact] handle unaligned access delay slot corner case
  parisc: Don't use BITS_PER_LONG in userspace-exported swab.h header
  nfs: Don't increment lock sequence ID after NFS4ERR_MOVED
  NFSv4.0: always send mode in SETATTR after EXCLUSIVE4
  SUNRPC: cleanup ida information when removing sunrpc module
  drm/i915: Don't leak edid in intel_crt_detect_ddc()
  IB/ipoib: move back IB LL address into the hard header
  IB/umem: Release pid in error and ODP flow
  s5k4ecgx: select CRC32 helper
  pinctrl: broxton: Use correct PADCFGLOCK offset
  platform/x86: intel_mid_powerbtn: Set IRQ_ONESHOT
  mm, memcg: do not retry precharge charges
  Linux 4.4.46

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

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

[Kernel-packages] [Bug 1660994] Re: Xenial update to v4.4.46 stable release

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

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

Title:
  Xenial update to v4.4.46 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.4.46 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.46 stable release shall be
  applied:

  fbdev: color map copying bounds checking
  tile/ptrace: Preserve previous registers for short regset write
  drm: Fix broken VT switch with video=1366x768 option
  mm/mempolicy.c: do not put mempolicy before using its nodemask
  sysctl: fix proc_doulongvec_ms_jiffies_minmax()
  ISDN: eicon: silence misleading array-bounds warning
  RDMA/cma: Fix unknown symbol when CONFIG_IPV6 is not enabled
  s390/ptrace: Preserve previous registers for short regset write
  can: c_can_pci: fix null-pointer-deref in c_can_start() - set device pointer
  can: ti_hecc: add missing prepare and unprepare of the clock
  ARC: udelay: fix inline assembler by adding LP_COUNT to clobber list
  ARC: [arcompact] handle unaligned access delay slot corner case
  parisc: Don't use BITS_PER_LONG in userspace-exported swab.h header
  nfs: Don't increment lock sequence ID after NFS4ERR_MOVED
  NFSv4.0: always send mode in SETATTR after EXCLUSIVE4
  SUNRPC: cleanup ida information when removing sunrpc module
  drm/i915: Don't leak edid in intel_crt_detect_ddc()
  IB/ipoib: move back IB LL address into the hard header
  IB/umem: Release pid in error and ODP flow
  s5k4ecgx: select CRC32 helper
  pinctrl: broxton: Use correct PADCFGLOCK offset
  platform/x86: intel_mid_powerbtn: Set IRQ_ONESHOT
  mm, memcg: do not retry precharge charges
  Linux 4.4.46

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

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

[Kernel-packages] [Bug 1661363] [NEW] Fails to load compressed kernels on arm64

2017-02-02 Thread dann frazier

Public bug reported:

[Impact]
kexec-tools will not load a compressed kernel on arm64. Ubuntu ships compressed 
kernel images on arm64 starting with 16.10 (and hwe kernels for 16.04). A 
workaround is to manually decompress the kernel before loading it, but this is 
not supported by the use-kexec-for-reboot-by-default feature of the kexec-tools 
package.

[Test Case]
ubuntu@ubuntu:~$ sudo file /boot/vmlinuz-4.9.0-15-generic
/boot/vmlinuz-4.9.0-15-generic: gzip compressed data, max compression, from Unix
ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.9.0-15-generic -t Image
arch_process_options:141: command_line: (null)
arch_process_options:143: initrd: (null)
arch_process_options:144: dtb: (null)
kernel: 0x8ff61010 kernel_size: 0x6ee18b
get_memory_ranges_iomem_cb: 4000 - bfff : System RAM
get_memory_ranges_iomem_cb: 0001 - 00013858 : System RAM
get_memory_ranges_iomem_cb: 00013875 - 00013bc1 : System RAM
get_memory_ranges_iomem_cb: 00013c00 - 00013fff : System RAM
image_arm64_probe: Bad arm64 image header.
elf_arm64_probe: Not an ELF executable.
image_arm64_probe: Bad arm64 image header.
Cannot determine the file type of /boot/vmlinuz-4.9.0-15-generic

[Regression Risk]
kexec-tools did not support arm64 until zesty so, assuming the fix is localized 
to arm64 code, regression risk is negligible.

** Affects: kexec-tools (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  [Impact]
  kexec-tools will not load a compressed kernel on arm64. Ubuntu ships 
compressed kernel images on arm64 starting with 16.10 (and hwe kernels for 
16.04). A workaround is to manually decompress the kernel before loading it, 
but this is not supported by the use-kexec-for-reboot-by-default feature of the 
kexec-tools package.
  
  [Test Case]
- ubuntu@ubuntu:~$ sudo file /boot/vmlinuz-4.9.0-15-generic 
+ ubuntu@ubuntu:~$ sudo file /boot/vmlinuz-4.9.0-15-generic
  /boot/vmlinuz-4.9.0-15-generic: gzip compressed data, max compression, from 
Unix
  ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.9.0-15-generic -t Image
  arch_process_options:141: command_line: (null)
  arch_process_options:143: initrd: (null)
  arch_process_options:144: dtb: (null)
  kernel: 0x8ff61010 kernel_size: 0x6ee18b
  get_memory_ranges_iomem_cb: 4000 - bfff : System RAM
  get_memory_ranges_iomem_cb: 0001 - 00013858 : System RAM
  get_memory_ranges_iomem_cb: 00013875 - 00013bc1 : System RAM
  get_memory_ranges_iomem_cb: 00013c00 - 00013fff : System RAM
  image_arm64_probe: Bad arm64 image header.
  elf_arm64_probe: Not an ELF executable.
  image_arm64_probe: Bad arm64 image header.
  Cannot determine the file type of /boot/vmlinuz-4.9.0-15-generic
+ 
+ [Regression Risk]
+ kexec-tools did not support arm64 until zesty so, assuming the fix is 
localized to arm64 code, regression risk is negligible.

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

Title:
  Fails to load compressed kernels on arm64

Status in kexec-tools package in Ubuntu:
  New

Bug description:
  [Impact]
  kexec-tools will not load a compressed kernel on arm64. Ubuntu ships 
compressed kernel images on arm64 starting with 16.10 (and hwe kernels for 
16.04). A workaround is to manually decompress the kernel before loading it, 
but this is not supported by the use-kexec-for-reboot-by-default feature of the 
kexec-tools package.

  [Test Case]
  ubuntu@ubuntu:~$ sudo file /boot/vmlinuz-4.9.0-15-generic
  /boot/vmlinuz-4.9.0-15-generic: gzip compressed data, max compression, from 
Unix
  ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.9.0-15-generic -t Image
  arch_process_options:141: command_line: (null)
  arch_process_options:143: initrd: (null)
  arch_process_options:144: dtb: (null)
  kernel: 0x8ff61010 kernel_size: 0x6ee18b
  get_memory_ranges_iomem_cb: 4000 - bfff : System RAM
  get_memory_ranges_iomem_cb: 0001 - 00013858 : System RAM
  get_memory_ranges_iomem_cb: 00013875 - 00013bc1 : System RAM
  get_memory_ranges_iomem_cb: 00013c00 - 00013fff : System RAM
  image_arm64_probe: Bad arm64 image header.
  elf_arm64_probe: Not an ELF executable.
  image_arm64_probe: Bad arm64 image header.
  Cannot determine the file type of /boot/vmlinuz-4.9.0-15-generic

  [Regression Risk]
  kexec-tools did not support arm64 until zesty so, assuming the fix is 
localized to arm64 code, regression risk is negligible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1661363/+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 1642044] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-5.7-generic/ms10-34-mcdivittB0-kernel__4.10.0-5.7__2017-02-02_18-57-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.9.0-6.7 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-development-workflow/+bug/1642044/+subscriptions

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

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

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-5.7-generic/ms10-35-mcdivittB0-kernel__4.10.0-5.7__2017-02-02_18-57-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/1642044

Title:
  linux: 4.9.0-11.12 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.9.0-6.7 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-development-workflow/+bug/1642044/+subscriptions

-- 
Mailing list: https://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 1661168] [NEW] In Ubuntu16.10: Kdump stuck in boot for longer time need to force reboot via HMC in 32TB Brazos System

2017-02-02 Thread Michael Hohnbaum

Louis,

While we can't test this without access to a machine with large amounts
of memory, is it possible to apply this patch and provide an image to
IBM for testing?

  Michael


On 02/01/2017 11:09 PM, bugproxy wrote:
> Public bug reported:
>
> Problem Description
> ===
>   In Ubuntu16.10 tried  kdump in Brazos system (32TB Memory and 192 core). 
> when trigger panic  kdump process  stuck in boot process  need to do force 
> reboot .After reboot system captured vmcore-incomplete.
>
> Reproducible Step:
> ==
> 1- Install Ubuntu16.10
> 2- boot system with 31TB and 192 Core 
> 3- configure kdump in system 
> 4- verify kdump in system that it is running 
> 5- Trigger panic in system
>
> Actual Result
> --
> kdump process  stuck in boot process  need to do force reboot
>
> Expected Result 
> -
> Kdump will proceed and vmcore captured  successfully.
>
> LOG:
>
> root@ltc-brazos1:~# cat /proc/cmdline 
> BOOT_IMAGE=/boot/vmlinux-4.4.0-30-generic 
> root=UUID=516c4b1b-6700-4b55-bd37-d61c4c5af6af ro quiet splash 
> crashkernel=4096M
> root@ltc-brazos1:~# kdump-config show
> DUMP_MODE:kdump
> USE_KDUMP:1
> KDUMP_SYSCTL: kernel.panic_on_oops=1
> KDUMP_COREDIR:/var/crash
> crashkernel addr: 
>/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-30-generic
> kdump initrd: 
>/var/lib/kdump/initrd.img: symbolic link to 
> /var/lib/kdump/initrd.img-4.4.0-30-generic
> current state:ready to kdump
>
> kexec command:
>   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-30-generic 
> root=UUID=516c4b1b-6700-4b55-bd37-d61c4c5af6af ro quiet splash irqpoll 
> nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
> --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
> root@ltc-brazos1:~# 
> root@ltc-brazos1:~# dpkg -l | grep kdump 
> ii  kdump-tools1:1.6.0-2 all  
> scripts and tools for automating kdump (Linux crash dumps)
> root@ltc-brazos1:~# 
> root@ltc-brazos1:~# echo c > /proc/sysrq-trigger 
>
>
> ltc-brazos1 login: [  416.229464] sysrq: SysRq : Trigger a crash  
>   
> 
> [  416.229496] Unable to handle kernel paging request for data at address 
> 0x
> 
> [  416.229502] Faulting instruction address: 0xc0670014   
>   
> 
> [  416.229508] Oops: Kernel access of bad area, sig: 11 [#1]  
>   
> 
> [  416.229511] SMP NR_CPUS=2048 NUMA pSeries  
>   
> 
> [  416.229517] Modules linked in: pseries_rng btrfs xor raid6_pq rtc_generic 
> sunrpc autofs4 ses enclosure ipr  
>  
> [  416.229532] CPU: 65 PID: 404785 Comm: bash Not tainted 4.4.0-30-generic 
> #49-Ubuntu
>
> [  416.229537] task: c1f9d583c8e0 ti: c1fa13cd8000 task.ti: 
> c1fa13cd8000  
>   
> [  416.229543] NIP: c0670014 LR: c06710c8 CTR: 
> c066ffe0  
>
> [  416.229548] REGS: c1fa13cdb990 TRAP: 0300   Not tainted  
> (4.4.0-30-generic)
>   
> [  416.229552] MSR: 80009033   CR: 2824  
> XER: 0001 
>
> [  416.229565] CFAR: c0008468 DAR:  DSISR: 4200 
> SOFTE: 1  
>   
> GPR00: c06710c8 c1fa13cdbc10 c15b5d00 0063
>   
> 
> GPR04: c1fab9049c50 c1fab905b4e0 c0001f3fff3d 0313
>   
> 
> GPR08: 0007 0001  c0001f3fff3dec68
>   
> 
> GPR12: c066ffe0 c7546980  2200 
> GPR16: 10170dc8 0100174901d8

[Kernel-packages] [Bug 1619918] Re: Subject: [REVERT][v4.x.y] btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in btrfs_ioctl

2017-02-02 Thread Greg KH

On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
> Hello,
> 
> Please consider reverting commit
> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release.

What release can I remove it from?

It isn't in 4.4.y, and 4.9.y doesn't make much sense, unless it's
reverted in Linus's tree already?

totally confused.

greg k-h

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

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

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Kernel-packages] [Bug 1593293] Re: brd module compiled as built-in

2017-02-02 Thread Tim Gardner

https://lists.ubuntu.com/archives/kernel-team/2017-February/082295.html

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

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

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

Title:
  brd module compiled as built-in

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:
  Block RAM disk module (brd, CONFIG_BLK_DEV_RAM) compiled as 'y', that
  means it is 'built-in' and can not be unloaded or loaded with
  different parameters. This render module completely useless because
  user can not anymore change it size.

  Please change it back to 'm' (module) to allow users use this module.

  Affected kernels (so far): Xenial, Yakkety (4.4).

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

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

[Kernel-packages] [Bug 1593293] Re: brd module compiled as built-in

2017-02-02 Thread Tim Gardner

https://lists.ubuntu.com/archives/kernel-team/2017-February/082294.html

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

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

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

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

Title:
  brd module compiled as built-in

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:
  Block RAM disk module (brd, CONFIG_BLK_DEV_RAM) compiled as 'y', that
  means it is 'built-in' and can not be unloaded or loaded with
  different parameters. This render module completely useless because
  user can not anymore change it size.

  Please change it back to 'm' (module) to allow users use this module.

  Affected kernels (so far): Xenial, Yakkety (4.4).

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

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

[Kernel-packages] [Bug 1660738] Re: linux: 4.9.0-16.17 -proposed tracker

** Changed in: kernel-development-workflow
   Status: In Progress => 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/1660738

Title:
  linux: 4.9.0-16.17 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.9.0-16.17 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-development-workflow/+bug/1660738/+subscriptions

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

[Kernel-packages] [Bug 1661300] Re: linux: 4.10.0-6.8 -proposed tracker

It was not possible to create or handle the tracking bugs for the following 
packages (their tracking bugs based on this update must be handled manually):
linux-lts-zesty (16.04.1)

** Changed in: kernel-development-workflow/prepare-package
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.10.0-6.8 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-phase:Packaging
+ kernel-phase-changed:Thursday, 02. February 2017 17:47 UTC

** Description changed:

  This bug is for tracking the 4.10.0-6.8 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-phase:Packaging
  kernel-phase-changed:Thursday, 02. February 2017 17:47 UTC
+ 
+ -- swm properties --
+ 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/1661300

Title:
  linux: 4.10.0-6.8 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.10.0-6.8 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-phase:Packaging
  kernel-phase-changed:Thursday, 02. February 2017 17:47 UTC

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

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

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

[Kernel-packages] [Bug 1619918] Subject: [REVERT][v4.x.y] btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in btrfs_ioctl

Hello,

Please consider reverting commit
4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release.  It
was included upstream as of v4.7-rc1  This commit introduced a
regression, described in the following bug:
http://bugs.launchpad.net/bugs/1619918

This new regression was discussed in the following thread:

https://lkml.org/lkml/2017/1/6/467


Sincerely,

Joseph Salisbury

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

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

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Kernel-packages] [Bug 1636656] Re: [Hyper-V] netvsc: fix incorrect receive checksum offloading

Thanks for the update, Chris.

** No longer affects: linux (Ubuntu Trusty)

** No longer affects: linux (Ubuntu Vivid)

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

Title:
  [Hyper-V] netvsc: fix incorrect receive checksum offloading

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

Bug description:
  The Hyper-V netvsc driver was looking at the incorrect status bits
  in the checksum info. It was setting the receive checksum unnecessary
  flag based on the IP header checksum being correct. The checksum
  flag is skb is about TCP and UDP checksum status. Because of this
  bug, any packet received with bad TCP checksum would be passed
  up the stack and to the application causing data corruption.
  The problem is reproducible via netcat and netem.

  This had a side effect of not doing receive checksum offload
  on IPv6. The driver was also also always doing checksum offload
  independent of the checksum setting done via ethtool.

  Signed-off-by: Stephen Hemminger 

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

  When this patch is committed I will include the commit ID in this bug.

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

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

[Kernel-packages] [Bug 1659381] Re: linux: 4.8.0-37.39 -proposed tracker

The package has been published and the bug is being set to Fix Released


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

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

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

** Description changed:

  This bug is for tracking the 4.8.0-37.39 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
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 02. February 2017 17:31 UTC

** Description changed:

  This bug is for tracking the 4.8.0-37.39 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
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 02. February 2017 17:31 UTC

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

Title:
  linux: 4.8.0-37.39 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  This bug is for tracking the 4.8.0-37.39 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: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

-- 
Mailing list: https://launchpad.net/~kernel-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

The package has been published and the bug is being set to Fix Released


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

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

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

** 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
  
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 02. February 2017 17:33 UTC

** 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
  
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 02. February 2017 17:33 UTC

-- 
You 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:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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 1655480] Re: linux-lts-trusty: 3.13.0-108.155~precise1 -proposed tracker

The package has been published and the bug is being set to Fix Released


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

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

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

** Description changed:

  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
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 02. February 2017 17:28 UTC

** Description changed:

  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
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 02. February 2017 17:28 UTC

-- 
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:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released

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

The package has been published and the bug is being set to Fix Released


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

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

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

** Description changed:

  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
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 02. February 2017 17:30 UTC

** Description changed:

  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
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 02. February 2017 17:30 UTC

-- 
You 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:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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: Released
  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 1661046] Re: ACPI cannot be activated on my MSI GE62 laptop. acpi-ht already causes failure, so the hyperthreading is responsible.

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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


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

Title:
  ACPI cannot be activated on my MSI GE62 laptop.  acpi-ht already
  causes failure, so the hyperthreading is responsible.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am including what you suggest on
  https://wiki.ubuntu.com/DebuggingACPI

  WIth acpi off, the fan doesn't work at top capacity, and the trackpad
  doesn't work at all.

  I'm including the uname, lspci, and dmidecode.

  I am not including the /proc/acpi directory, as it doesn't exist at
  all.

  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 x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benjones   1849 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Feb  1 10:09:36 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ad294c16-796f-449c-943b-a5f0f6dbb961
  InstallationDate: Installed on 2017-01-31 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Micro-Star International Co., Ltd. GE62 6QD
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=cf5aded0-f481-4da8-9b31-78b854cd2a66 ro acpi=off
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.114
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.114:bd04/29/2016:svnMicro-StarInternationalCo.,Ltd.:pnGE626QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GE62 6QD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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


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

** Tags added: kernel-da-key

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

Title:
  kernel crash when NVMe drive inserted in one slot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Opening this on behalf of one of my colleagues at Cisco, we're seeing
  an issue on our new S-series S3260 server that's causing the kernel to
  crash.

  If we have an NVMe device inserted into one of two drive slots, we
  will see kernel crash only with Ubuntu. With an NVMe drive in the bad
  slot, other OS's will work fine. If we move the NVMe drive out of the
  bad slot and into the other slot, everything is working fine as
  expected. We only see the kernel crash with an NVMe drive in that bad
  slot when using Ubuntu. We tested with HGST and Intel NVMe drives and
  were able to reproduce the issue with both. HGST reviewed some logs
  and they don't believe at this time the issue is with the NVMe drives.

  We're hoping someone from Canonical can take a look to understand what
  is the difference between the working and failing slot. The data
  collection was done with the NVMe drive inserted in the working slot
  so we could access the OS.

  I had a connection time out when trying to use ubuntu-bug, so I saved
  the apport file and will attach to the bug. I have collected the
  kernel and syslog as well, but they are ~9GB. I found a call trace in
  the kernel log start on Jan 25 06:02:54 and floods the logs
  afterwards. I will include the call trace in a separate text file on
  the attachment.

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

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

[Kernel-packages] [Bug 1655745] Re: linux: 3.19.0-80.88 -proposed tracker

The package has been published and the bug is being set to Fix Released


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

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

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

** Description changed:

  This bug is for tracking the 3.19.0-80.88 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
+ kernel-stable-phase-changed:Thursday, 02. February 2017 17:06 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 3.19.0-80.88 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
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Thursday, 02. February 2017 17:06 UTC
- kernel-stable-phase: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/1655745

Title:
  linux: 3.19.0-80.88 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-80.88 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: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1655748] Re: linux-lts-vivid: 3.19.0-80.88~14.04.1 -proposed tracker

The package has been published and the bug is being set to Fix Released


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

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

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

** Description changed:

  This bug is for tracking the 3.19.0-80.88~14.04.1 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: 1655745
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Thursday, 02. February 2017 17:07 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 3.19.0-80.88~14.04.1 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: 1655745
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Thursday, 02. February 2017 17:07 UTC
- kernel-stable-phase:Released

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

Title:
  linux-lts-vivid: 3.19.0-80.88~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-80.88~14.04.1 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: 1655745
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1660704] Re: linux: 4.4.0-63.84 -proposed tracker

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

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

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

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

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

** Description changed:

  This bug is for tracking the 4.4.0-63.84 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 --
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-stable-phase-changed:Thursday, 02. February 2017 17:12 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.4.0-63.84 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
- kernel-stable-phase-changed:Thursday, 02. February 2017 17:12 UTC
- kernel-stable-phase:Uploaded

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

Title:
  linux: 4.4.0-63.84 -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:
  In Progress
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-63.84 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/1660704/+subscriptions

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

[Kernel-packages] [Bug 1655076] Re: linux-armadaxp: 3.2.0-1682.109 -proposed tracker

The package has been published and the bug is being set to Fix Released


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

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

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

** Description changed:

  This bug is for tracking the 3.2.0-1682.109 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: 1655071
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Thursday, 02. February 2017 17:13 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 3.2.0-1682.109 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: 1655071
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Thursday, 02. February 2017 17:13 UTC
- kernel-stable-phase:Released

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

Title:
  linux-armadaxp: 3.2.0-1682.109 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.2.0-1682.109 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: 1655071
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1655071] Re: linux: 3.2.0-121.164 -proposed tracker

The package has been published and the bug is being set to Fix Released


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

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

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

** Description changed:

  This bug is for tracking the 3.2.0-121.164 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
+ kernel-stable-phase-changed:Thursday, 02. February 2017 17:11 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 3.2.0-121.164 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
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Thursday, 02. February 2017 17:11 UTC
- kernel-stable-phase: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/1655071

Title:
  linux: 3.2.0-121.164 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
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-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released

Bug description:
  This bug is for tracking the 3.2.0-121.164 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: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1661232] Re: linux: 4.8.0-38.40 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

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

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

** Description changed:

  This bug is for tracking the 4.8.0-38.40 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 --
  derivative-trackers-created: true
+ kernel-stable-phase-changed:Thursday, 02. February 2017 17:14 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the 4.8.0-38.40 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 --
  derivative-trackers-created: true
- kernel-stable-phase-changed:Thursday, 02. February 2017 17:14 UTC
- kernel-stable-phase:Packaging
+ 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/1661232

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

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

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

-- 
Mailing list: https://launchpad.net/~kernel-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

This bug was fixed in the package linux - 4.4.0-62.83

---
linux (4.4.0-62.83) xenial; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1657430

  * Backport DP MST fixes to i915 (LP: #1657353)
- SAUCE: i915_bpo: Fix DP link rate math
- SAUCE: i915_bpo: Validate mode against max. link data rate for DP MST

  * Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue (LP: #1657281)
- blk-mq: really fix plug list flushing for nomerge queues

linux (4.4.0-61.82) xenial; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1656810

  * Xen MSI setup code incorrectly re-uses cached pirq (LP: #1656381)
- SAUCE: xen: do not re-use pirq number cached in pci device msi msg data

  * nvme drive probe failure (LP: #1626894)
- nvme: revert NVMe: only setup MSIX once

linux (4.4.0-60.81) xenial; urgency=low

  [ John Donnelly ]

  * Release Tracking Bug
- LP: #1656084

  * Couldn't emulate instruction 0x7813427c (LP: #1634129)
- KVM: PPC: Book3S PR: Fix illegal opcode emulation

  * perf: 24x7: Eliminate domain name suffix in event names (LP: #1560482)
- powerpc/perf/hv-24x7: Fix usage with chip events.
- powerpc/perf/hv-24x7: Display change in counter values
- powerpc/perf/hv-24x7: Display domain indices in sysfs
- powerpc/perf/24x7: Eliminate domain suffix in event names

  * i386 ftrace tests hang on ADT testing (LP: #1655040)
- ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short 
jumps
  to it

  * VMX module autoloading if available (LP: #1651322)
- powerpc: Add module autoloading based on CPU features
- crypto: vmx - Convert to CPU feature based module autoloading

  * ACPI probe support for AD5592/3 configurable multi-channel converter
(LP: #1654497)
- SAUCE: iio: dac: ad5592r: Add ACPI support
- SAUCE: iio: dac: ad5593r: Add ACPI support

  * Xenial update to v4.4.40 stable release (LP: #1654602)
- btrfs: limit async_work allocation and worker func duration
- Btrfs: fix tree search logic when replaying directory entry deletes
- btrfs: store and load values of stripes_min/stripes_max in balance status
  item
- Btrfs: fix qgroup rescan worker initialization
- USB: serial: option: add support for Telit LE922A PIDs 0x1040, 0x1041
- USB: serial: option: add dlink dwm-158
- USB: serial: kl5kusb105: fix open error path
- USB: cdc-acm: add device id for GW Instek AFG-125
- usb: hub: Fix auto-remount of safely removed or ejected USB-3 devices
- usb: gadget: f_uac2: fix error handling at afunc_bind
- usb: gadget: composite: correctly initialize ep->maxpacket
- USB: UHCI: report non-PME wakeup signalling for Intel hardware
- ALSA: usb-audio: Add QuickCam Communicate Deluxe/S7500 to
  volume_control_quirks
- ALSA: hiface: Fix M2Tech hiFace driver sampling rate change
- ALSA: hda/ca0132 - Add quirk for Alienware 15 R2 2016
- ALSA: hda - ignore the assoc and seq when comparing pin configurations
- ALSA: hda - fix headset-mic problem on a Dell laptop
- ALSA: hda - Gate the mic jack on HP Z1 Gen3 AiO
- ALSA: hda: when comparing pin configurations, ignore assoc in addition to
  seq
- clk: ti: omap36xx: Work around sprz319 advisory 2.1
- Btrfs: fix memory leak in reading btree blocks
- Btrfs: bail out if block group has different mixed flag
- Btrfs: return gracefully from balance if fs tree is corrupted
- Btrfs: don't leak reloc root nodes on error
- Btrfs: fix memory leak in do_walk_down
- Btrfs: don't BUG() during drop snapshot
- btrfs: make file clone aware of fatal signals
- block_dev: don't test bdev->bd_contains when it is not stable
- ptrace: Capture the ptracer's creds not PT_PTRACE_CAP
- crypto: caam - fix AEAD givenc descriptors
- ext4: fix mballoc breakage with 64k block size
- ext4: fix stack memory corruption with 64k block size
- ext4: use more strict checks for inodes_per_block on mount
- ext4: fix in-superblock mount options processing
- ext4: add sanity checking to count_overhead()
- ext4: reject inodes with negative size
- ext4: return -ENOMEM instead of success
- ext4: do not perform data journaling when data is encrypted
- f2fs: set ->owner for debugfs status file's file_operations
- loop: return proper error from loop_queue_rq()
- mm/vmscan.c: set correct defer count for shrinker
- fs: exec: apply CLOEXEC before changing dumpable task flags
- exec: Ensure mm->user_ns contains the execed files
- usb: gadget: composite: always set ep->mult to a sensible value
- blk-mq: Do not invoke .queue_rq() for a stopped queue
- dm flakey: return -EINVAL on interval bounds error in flakey_ctr()
- dm crypt: mark key as invalid until properly loaded
- dm space map metadata: fix 'struct sm_metadata' leak on failed create
- ASoC: intel: Fix crash at

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

This bug was fixed in the package linux - 4.4.0-62.83

---
linux (4.4.0-62.83) xenial; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1657430

  * Backport DP MST fixes to i915 (LP: #1657353)
- SAUCE: i915_bpo: Fix DP link rate math
- SAUCE: i915_bpo: Validate mode against max. link data rate for DP MST

  * Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue (LP: #1657281)
- blk-mq: really fix plug list flushing for nomerge queues

linux (4.4.0-61.82) xenial; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1656810

  * Xen MSI setup code incorrectly re-uses cached pirq (LP: #1656381)
- SAUCE: xen: do not re-use pirq number cached in pci device msi msg data

  * nvme drive probe failure (LP: #1626894)
- nvme: revert NVMe: only setup MSIX once

linux (4.4.0-60.81) xenial; urgency=low

  [ John Donnelly ]

  * Release Tracking Bug
- LP: #1656084

  * Couldn't emulate instruction 0x7813427c (LP: #1634129)
- KVM: PPC: Book3S PR: Fix illegal opcode emulation

  * perf: 24x7: Eliminate domain name suffix in event names (LP: #1560482)
- powerpc/perf/hv-24x7: Fix usage with chip events.
- powerpc/perf/hv-24x7: Display change in counter values
- powerpc/perf/hv-24x7: Display domain indices in sysfs
- powerpc/perf/24x7: Eliminate domain suffix in event names

  * i386 ftrace tests hang on ADT testing (LP: #1655040)
- ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short 
jumps
  to it

  * VMX module autoloading if available (LP: #1651322)
- powerpc: Add module autoloading based on CPU features
- crypto: vmx - Convert to CPU feature based module autoloading

  * ACPI probe support for AD5592/3 configurable multi-channel converter
(LP: #1654497)
- SAUCE: iio: dac: ad5592r: Add ACPI support
- SAUCE: iio: dac: ad5593r: Add ACPI support

  * Xenial update to v4.4.40 stable release (LP: #1654602)
- btrfs: limit async_work allocation and worker func duration
- Btrfs: fix tree search logic when replaying directory entry deletes
- btrfs: store and load values of stripes_min/stripes_max in balance status
  item
- Btrfs: fix qgroup rescan worker initialization
- USB: serial: option: add support for Telit LE922A PIDs 0x1040, 0x1041
- USB: serial: option: add dlink dwm-158
- USB: serial: kl5kusb105: fix open error path
- USB: cdc-acm: add device id for GW Instek AFG-125
- usb: hub: Fix auto-remount of safely removed or ejected USB-3 devices
- usb: gadget: f_uac2: fix error handling at afunc_bind
- usb: gadget: composite: correctly initialize ep->maxpacket
- USB: UHCI: report non-PME wakeup signalling for Intel hardware
- ALSA: usb-audio: Add QuickCam Communicate Deluxe/S7500 to
  volume_control_quirks
- ALSA: hiface: Fix M2Tech hiFace driver sampling rate change
- ALSA: hda/ca0132 - Add quirk for Alienware 15 R2 2016
- ALSA: hda - ignore the assoc and seq when comparing pin configurations
- ALSA: hda - fix headset-mic problem on a Dell laptop
- ALSA: hda - Gate the mic jack on HP Z1 Gen3 AiO
- ALSA: hda: when comparing pin configurations, ignore assoc in addition to
  seq
- clk: ti: omap36xx: Work around sprz319 advisory 2.1
- Btrfs: fix memory leak in reading btree blocks
- Btrfs: bail out if block group has different mixed flag
- Btrfs: return gracefully from balance if fs tree is corrupted
- Btrfs: don't leak reloc root nodes on error
- Btrfs: fix memory leak in do_walk_down
- Btrfs: don't BUG() during drop snapshot
- btrfs: make file clone aware of fatal signals
- block_dev: don't test bdev->bd_contains when it is not stable
- ptrace: Capture the ptracer's creds not PT_PTRACE_CAP
- crypto: caam - fix AEAD givenc descriptors
- ext4: fix mballoc breakage with 64k block size
- ext4: fix stack memory corruption with 64k block size
- ext4: use more strict checks for inodes_per_block on mount
- ext4: fix in-superblock mount options processing
- ext4: add sanity checking to count_overhead()
- ext4: reject inodes with negative size
- ext4: return -ENOMEM instead of success
- ext4: do not perform data journaling when data is encrypted
- f2fs: set ->owner for debugfs status file's file_operations
- loop: return proper error from loop_queue_rq()
- mm/vmscan.c: set correct defer count for shrinker
- fs: exec: apply CLOEXEC before changing dumpable task flags
- exec: Ensure mm->user_ns contains the execed files
- usb: gadget: composite: always set ep->mult to a sensible value
- blk-mq: Do not invoke .queue_rq() for a stopped queue
- dm flakey: return -EINVAL on interval bounds error in flakey_ctr()
- dm crypt: mark key as invalid until properly loaded
- dm space map metadata: fix 'struct sm_metadata' leak on failed create
- ASoC: intel: Fix crash at

[Kernel-packages] [Bug 1398193] Re: The bluetooth headset cannot control media playback

2017-02-02 Thread Jim Hodapp

** Summary changed:

- The bluetooth headset can not control the media playback
+ The bluetooth headset cannot control media playback

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

Title:
  The bluetooth headset cannot control media playback

Status in Canonical System Image:
  Triaged
Status in bluez package in Ubuntu:
  Triaged
Status in media-hub package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu RTM:
  Invalid

Bug description:
  [Preconditions]
  1.The DUT pair with bluetooth headset

  [Procedures]
  1.Play a video using the mediaplayer-app
  2.Play/pause video by bluetooth headset

  [Expect results]
  The bluetooth headset can play/pause video
  [Actual results]
  The bluetooth headset can not control the video playback.

  [Reproduce]
  Always

  Same for audio playback

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

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

[Kernel-packages] [Bug 1654343] Re: SRIOV VNIC Server/Backing Device Failover support

This bug was fixed in the package linux - 4.8.0-37.39

---
linux (4.8.0-37.39) yakkety; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1659381

  * Mouse cursor invisible or does not move (LP: #1646574)
- drm/nouveau/disp/nv50-: split chid into chid.ctrl and chid.user
- drm/nouveau/disp/nv50-: specify ctrl/user separately when constructing
  classes
- drm/nouveau/disp/gp102: fix cursor/overlay immediate channel indices

 -- Benjamin M Romer   Wed, 25 Jan 2017
16:12:02 -0200

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

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

Title:
  SRIOV VNIC Server/Backing Device Failover support

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

Bug description:
  Now that failover has been accepted into net-next, we're going to try
  to provide a backport for Ubuntu 16.04.2.

  This is the commit:
  https://patchwork.ozlabs.org/patch/660487/

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

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

[Kernel-packages] [Bug 1626740] Re: i915 module requests unreleased GUC firmware files

This bug was fixed in the package linux - 4.8.0-37.39

---
linux (4.8.0-37.39) yakkety; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1659381

  * Mouse cursor invisible or does not move (LP: #1646574)
- drm/nouveau/disp/nv50-: split chid into chid.ctrl and chid.user
- drm/nouveau/disp/nv50-: specify ctrl/user separately when constructing
  classes
- drm/nouveau/disp/gp102: fix cursor/overlay immediate channel indices

 -- Benjamin M Romer   Wed, 25 Jan 2017
16:12:02 -0200

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

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

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

Title:
  i915 module requests unreleased GUC firmware files

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

Bug description:
  This causes the following warnings when generating the initrd:

  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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-14-generic 4.8.0-14.15
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2032 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2032 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Sep 22 18:02:29 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (424 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-14-generic N/A
   linux-backports-modules-4.8.0-14-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1647465] Re: Yakkety update to v4.8.12 stable release

This bug was fixed in the package linux - 4.8.0-37.39

---
linux (4.8.0-37.39) yakkety; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1659381

  * Mouse cursor invisible or does not move (LP: #1646574)
- drm/nouveau/disp/nv50-: split chid into chid.ctrl and chid.user
- drm/nouveau/disp/nv50-: specify ctrl/user separately when constructing
  classes
- drm/nouveau/disp/gp102: fix cursor/overlay immediate channel indices

 -- Benjamin M Romer   Wed, 25 Jan 2017
16:12:02 -0200

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

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

Title:
  Yakkety update to v4.8.12 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.8.12 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.8.12 stable release shall be
  applied:

  iommu/vt-d: Fix PASID table allocation
  iommu/vt-d: Fix IOMMU lookup for SR-IOV Virtual Functions
  KVM: x86: fix out-of-bounds access in lapic
  KVM: x86: drop error recovery in em_jmp_far and em_ret_far
  KVM: x86: fix out-of-bounds accesses of rtc_eoi map
  KVM: x86: check for pic and ioapic presence before use
  usb: chipidea: move the lock initialization to core file
  USB: serial: cp210x: add ID for the Zone DPMX
  USB: serial: ftdi_sio: add support for TI CC3200 LaunchPad
  Fix USB CB/CBI storage devices with CONFIG_VMAP_STACK=y
  scsi: mpt3sas: Fix secure erase premature termination
  tile: avoid using clocksource_cyc2ns with absolute cycle count
  cfg80211: limit scan results cache size
  NFSv4.x: hide array-bounds warning
  x86/fpu: Fix invalid FPU ptrace state after execve()
  x86/traps: Ignore high word of regs->cs in early_fixup_exception()
  perf/core: Fix address filter parser
  perf/x86/intel: Cure bogus unwind from PEBS entries
  thermal/powerclamp: add back module device table
  parisc: Fix races in parisc_setup_cache_timing()
  parisc: Switch to generic sched_clock implementation
  parisc: Fix race in pci-dma.c
  parisc: Also flush data TLB in flush_icache_page_asm
  mmc: sdhci-of-esdhc: fixup PRESENT_STATE read
  mpi: Fix NULL ptr dereference in mpi_powm() [ver #3]
  X.509: Fix double free in x509_cert_parse() [ver #3]
  xc2028: Fix use-after-free bug properly
  device-dax: check devm_nsio_enable() return value
  device-dax: fail all private mapping attempts
  powerpc: Set missing wakeup bit in LPCR on POWER9
  powerpc/mm: Fixup kernel read only mapping
  powerpc/boot: Fix the early OPAL console wrappers
  can: bcm: fix support for CAN FD frames
  mm, oom: stop pre-mature high-order OOM killer invocations
  scsi: mpt3sas: Unblock device after controller reset
  Linux 4.8.12

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

This bug was fixed in the package linux - 4.8.0-37.39

---
linux (4.8.0-37.39) yakkety; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1659381

  * Mouse cursor invisible or does not move (LP: #1646574)
- drm/nouveau/disp/nv50-: split chid into chid.ctrl and chid.user
- drm/nouveau/disp/nv50-: specify ctrl/user separately when constructing
  classes
- drm/nouveau/disp/gp102: fix cursor/overlay immediate channel indices

 -- Benjamin M Romer   Wed, 25 Jan 2017
16:12:02 -0200

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

Title:
  nvme drive probe failure

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

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

This bug was fixed in the package linux - 4.4.0-62.83

---
linux (4.4.0-62.83) xenial; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1657430

  * Backport DP MST fixes to i915 (LP: #1657353)
- SAUCE: i915_bpo: Fix DP link rate math
- SAUCE: i915_bpo: Validate mode against max. link data rate for DP MST

  * Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue (LP: #1657281)
- blk-mq: really fix plug list flushing for nomerge queues

linux (4.4.0-61.82) xenial; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
- LP: #1656810

  * Xen MSI setup code incorrectly re-uses cached pirq (LP: #1656381)
- SAUCE: xen: do not re-use pirq number cached in pci device msi msg data

  * nvme drive probe failure (LP: #1626894)
- nvme: revert NVMe: only setup MSIX once

linux (4.4.0-60.81) xenial; urgency=low

  [ John Donnelly ]

  * Release Tracking Bug
- LP: #1656084

  * Couldn't emulate instruction 0x7813427c (LP: #1634129)
- KVM: PPC: Book3S PR: Fix illegal opcode emulation

  * perf: 24x7: Eliminate domain name suffix in event names (LP: #1560482)
- powerpc/perf/hv-24x7: Fix usage with chip events.
- powerpc/perf/hv-24x7: Display change in counter values
- powerpc/perf/hv-24x7: Display domain indices in sysfs
- powerpc/perf/24x7: Eliminate domain suffix in event names

  * i386 ftrace tests hang on ADT testing (LP: #1655040)
- ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short 
jumps
  to it

  * VMX module autoloading if available (LP: #1651322)
- powerpc: Add module autoloading based on CPU features
- crypto: vmx - Convert to CPU feature based module autoloading

  * ACPI probe support for AD5592/3 configurable multi-channel converter
(LP: #1654497)
- SAUCE: iio: dac: ad5592r: Add ACPI support
- SAUCE: iio: dac: ad5593r: Add ACPI support

  * Xenial update to v4.4.40 stable release (LP: #1654602)
- btrfs: limit async_work allocation and worker func duration
- Btrfs: fix tree search logic when replaying directory entry deletes
- btrfs: store and load values of stripes_min/stripes_max in balance status
  item
- Btrfs: fix qgroup rescan worker initialization
- USB: serial: option: add support for Telit LE922A PIDs 0x1040, 0x1041
- USB: serial: option: add dlink dwm-158
- USB: serial: kl5kusb105: fix open error path
- USB: cdc-acm: add device id for GW Instek AFG-125
- usb: hub: Fix auto-remount of safely removed or ejected USB-3 devices
- usb: gadget: f_uac2: fix error handling at afunc_bind
- usb: gadget: composite: correctly initialize ep->maxpacket
- USB: UHCI: report non-PME wakeup signalling for Intel hardware
- ALSA: usb-audio: Add QuickCam Communicate Deluxe/S7500 to
  volume_control_quirks
- ALSA: hiface: Fix M2Tech hiFace driver sampling rate change
- ALSA: hda/ca0132 - Add quirk for Alienware 15 R2 2016
- ALSA: hda - ignore the assoc and seq when comparing pin configurations
- ALSA: hda - fix headset-mic problem on a Dell laptop
- ALSA: hda - Gate the mic jack on HP Z1 Gen3 AiO
- ALSA: hda: when comparing pin configurations, ignore assoc in addition to
  seq
- clk: ti: omap36xx: Work around sprz319 advisory 2.1
- Btrfs: fix memory leak in reading btree blocks
- Btrfs: bail out if block group has different mixed flag
- Btrfs: return gracefully from balance if fs tree is corrupted
- Btrfs: don't leak reloc root nodes on error
- Btrfs: fix memory leak in do_walk_down
- Btrfs: don't BUG() during drop snapshot
- btrfs: make file clone aware of fatal signals
- block_dev: don't test bdev->bd_contains when it is not stable
- ptrace: Capture the ptracer's creds not PT_PTRACE_CAP
- crypto: caam - fix AEAD givenc descriptors
- ext4: fix mballoc breakage with 64k block size
- ext4: fix stack memory corruption with 64k block size
- ext4: use more strict checks for inodes_per_block on mount
- ext4: fix in-superblock mount options processing
- ext4: add sanity checking to count_overhead()
- ext4: reject inodes with negative size
- ext4: return -ENOMEM instead of success
- ext4: do not perform data journaling when data is encrypted
- f2fs: set ->owner for debugfs status file's file_operations
- loop: return proper error from loop_queue_rq()
- mm/vmscan.c: set correct defer count for shrinker
- fs: exec: apply CLOEXEC before changing dumpable task flags
- exec: Ensure mm->user_ns contains the execed files
- usb: gadget: composite: always set ep->mult to a sensible value
- blk-mq: Do not invoke .queue_rq() for a stopped queue
- dm flakey: return -EINVAL on interval bounds error in flakey_ctr()
- dm crypt: mark key as invalid until properly loaded
- dm space map metadata: fix 'struct sm_metadata' leak on failed create
- ASoC: intel: Fix crash at

[Kernel-packages] [Bug 1646574] Re: Mouse cursor invisible or does not move