[Kernel-packages] [Bug 1624811] Re: package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[magisterludi]

As I said I have ran the command [code] sudo apt install -f [/code] and
the package got installed but generated the error message when I did
reboot. After the first reboot I haven't never see this error

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

Title:
  package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This error I had is probably the effect of a problem in the version
  update (14.04 LTS to 16.04 LTS) that was aborted for some problem I
  don't know, the window was frozen and I switchet to a terminal but the
  process was defunct. Then I used the command "dpkg --configure -a" but
  the new kernel was not able to install and configure then I used "apt
  -f install" and after reboot the system started with this error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maurizio   1856 F pulseaudio
  Date: Sat Sep 17 20:04:44 2016
  DuplicateSignature:
   package:linux-image-4.4.0-38-generic:4.4.0-38.57
   Preparing to unpack .../linux-image-4.4.0-38-generic_4.4.0-38.57_i386.deb ...
   frontend: Fatal IO error 0 (Successo) on X server :0.
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-38-generic_4.4.0-38.57_i386.deb 
(--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=5ad1fdd7-cf3d-49bb-971c-a80fa30d6488
  InstallationDate: Installed on 2014-04-19 (882 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Hewlett-Packard HP Mini 110-1100
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=0f9cd822-04f0-471c-88b3-9d0ad5ae4ef1 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.3
  SourcePackage: linux
  Title: package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to xenial on 2016-09-17 (0 days ago)
  dmi.bios.date: 09/16/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 308F0 Ver. F.17
  dmi.board.name: 308F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 02.10
  dmi.chassis.asset.tag: CNU938DQ8G
  dmi.chassis.type: 10
  dmi.chassis.vendor: Inventec
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr308F0Ver.F.17:bd09/16/2009:svnHewlett-Packard:pnHPMini110-1100:pvr039311201B030:rvnHewlett-Packard:rn308F:rvrKBCVersion02.10:cvnInventec:ct10:cvr:
  dmi.product.name: HP Mini 110-1100
  dmi.product.version: 039311201B030
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1628835] Re: msg='apparmor="DENIED" operation="dbus_method_call"

[dino99]

The first bug description sentence said it all: ... started with
4.8.0.17

and now using the final 4.8 kernel release (4.8.0.20) i also get the
same errors logged.

Looks like a very close message was met some times ago:
 https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1473584


** Tags added: kernel-bug-exists-upstream

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

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

Title:
  msg='apparmor="DENIED" operation="dbus_method_call"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Get some apparmor 'DENIED' messages logged when booting with 4.8.0-17
  kernel; this was not happening with some previous versions (at least
  4.8.0-12) and no other upgrades can explain such apparmor messages, so
  blaming the kernel.

  
   oem@u64:~$ journalctl | grep  DENIED

  Sep 29 08:11:52 u64 audit[840]: USER_AVC pid=840 uid=101
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:52 u64 kernel: audit: type=1107 audit(1475129512.681:27):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:53 u64 audit[840]: USER_AVC pid=840 uid=101
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:53 u64 kernel: audit: type=1107 audit(1475129513.581:28):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:54 u64 audit[840]: USER_AVC pid=840 uid=101
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:54 u64 kernel: audit: type=1107 audit(1475129514.585:29):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:55 u64 audit[840]: USER_AVC pid=840 uid=101
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  Sep 29 08:11:55 u64 kernel: audit: type=1107 audit(1475129515.124:30):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-generic 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2213 F pulseaudio
   /dev/snd/pcmC0D0p:   oem2213 F...m pulseaudio
   /dev/snd/controlC0:  oem2213 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Sep 29 10:58:44 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsu

[Kernel-packages] [Bug 1398193] Re: The bluetooth headset can not control the media playback

[Gregory Opera]

When using AfterShokz's Trekz Titanium, the result is still the same...
This issue still has not been addressed.

--

bq Aquaris E5 HD Ubuntu Edition:
* OS build number: OTA-13
* Ubuntu Image part: 20160913
* Ubuntu build description: Ubuntu 15.04 - armhf (20160913-023544)
* Device Image part: 20160606-540a47f
* Device build description: VEGETA01A-S23A_BQ_L100EN_2015_160913
* Customization Image part: 20160831-991-38-18

-- 
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 can not control the 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 1629613] Re: [Dell XPS 13] SynPS/2 Synaptics TouchPad not recognized after upgrade from 14.04 to 16.04

[Errol Pais]

FYI: Booted ubuntu 16.04 from a usb drive and the touchpad works. I am
considering doing a fresh install to solve this problem.

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

Title:
  [Dell XPS 13] SynPS/2 Synaptics TouchPad not recognized after upgrade
  from 14.04 to 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  * Touchpad doesn't work at all (No response from the Touchpad)
  * Tried using external mouse and it works fine
  * Cannot find "SynPS/2 Synaptics TouchPad" in "cat /proc/bus/input/devices"

  
  OS:   Ubuntu 16.04.1 LTS
  kernel version: 4.4.0-38-generic
  Laptop Model:   Dell XPS 13 - 9

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

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

[Kernel-packages] [Bug 1604396] Re: Kernel 4.4.0-31 cd into NFS4 directory: Operation not permitted

[Reinhard Zierke]

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

Title:
  Kernel 4.4.0-31 cd into NFS4 directory: Operation not permitted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since apt-upgrading my Ubuntu 16.04 PC to kernel 4.4.0-31 I can't cd
  into NFS4 subvolumes any more:

  zierke@rzpc100$ uname -a
  Linux rzpc100 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  zierke@rzpc100$ kinit
  Password for zie...@informatik.uni-hamburg.de:
  zierke@rzpc100$ cd /informatik2
  zierke@rzpc100$ cd rz
  -bash: cd: /informatik2/rz: Operation not permitted

  When I reboot my PC with the previous kernel 4.4.0-28 this works fine.

  This problem has also been mentioned in
  
https://www.kubuntuforums.net/showthread.php?70499-Latest-16-04-bug-NFS-problem-no-access-unless-I-use-root-first-strange
  https://ubuntuforums.org/showthread.php?t=2331137

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

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

[Kernel-packages] [Bug 1538909] Re: OPRASHB:Habanero:EEH: Opal not calling out slot number for failing adapter behind plx switch

[bugproxy]

--- Comment From cha...@us.ibm.com 2016-02-22 21:48 EDT---
Will we see this fix release in a 14.04 SRU?

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin14044

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

Title:
  OPRASHB:Habanero:EEH: Opal not calling out slot number for failing
  adapter behind plx switch

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  New
Status in linux source package in Wily:
  New
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - MAMATHA INAMDAR  - 2016-01-14 04:51:41 
==
  ---Problem Description---
  Working with Chad (IO team) we were able to inject an EEH recoverable error 
to the broadcom network adapter (PE #2) behind the PLX switch. Looks like OPAL 
calls out the Backplane PLX ( Planar ) instead of the adapter slot.

  We want to primarily focus on why the adapter slot ( behind PLX )
  didn't get called out using this defect.

  Problem:
  
  >> Working with Chad (IO team) we were able to inject an EEH recoverable error
  >> to the broadcom network adapter (PE #2) and noticed that we are not getting
  >> the adapter slot called out, instead we get the location pointing to the
  >> backplane PLX.
  >
  >If what you injected is a PCIe error message, I think those cause the
  >switch leg to freeze, but I will need Gavin to confirm.
  >
  >> Per Chad:
  >> 
??
  >> ?They're logging the right PE (#2--which corresponds to the 
Broadcom??
  >> ?adapter)--they're just not pointing to its slot 
explicitly.??
  >> 
??
  >>
  >>
  >>
  >> Here is a snippet the /var/log/messages:
  >>
  >> 
??
  >> ?Nov 11 12:17:18 habmc8p01 kernel: EEH: Frozen PHB#1-PE#2 
detected
  >> ?Nov 11 12:17:18 habmc8p01 kernel: bnx2x: [bnx2x_timer:5750(net0)]MFW 
seems???
  >> ?hanged: drv_pulse (0x1c1) != mcp_pulse 
(0x7fff)??
  >> ?Nov 11 12:17:18 habmc8p01 kernel: EEH: PE location: Backplane PLX, PHB 
location:
  >> ?Backplane 
PLX
  >> 
??
  >>
  >>
  >>
  >>
  >> injection:
  >> setpci -s 0001:0c:00.2 COMMAND
  >> ???
  >> ?setpci -s??0001:0c:00.2???
  >> ?COMMAND=0540??
  >> ???

  It seems you're disabling memory BAR and then issue MMIO load, which results
  in "unsupported request" returned from the adapter. In response to that, the
  PE#2 as shown in the kernel log is put to frozen state. Nothing wrong at this
  point. I think the only question would be: the location code isn't making 
sense.
   
  Contact Information = - 
   
  ---uname output---
  3.19.0-43-generic
   
  Machine Type =  
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   This bug is follow up of bug 133061. This  bug is opened to backport the 
kernel patch which is available to fix the issue for bug 133061 on Ubuntu.
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for -: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  Firestone server ( Ubuntu Host )
  =

  I have built the Ubuntu kernel with patch and created  *.deb files.

  Please find the same in the following path for installing and testing
  your test case

   State: Assigned by: thalerj on 13 January 2016 12:10:58 

  The patched kernel is working great for both firestone and Habanero.
  It resolves the issue and all slot numbers are called out properly.

  == Comment: #1 - MAMATHA INAMDAR  - 2016-01-28 01:02:23 
==
  Patch is now available in the following branch

  
https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=7e56f627768da4e6480986b5145dc3422bc448a5

  == Comment: #3 - MAMATHA INAMDAR  - 2016-01-28
  01:09:14 ==

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

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

[Kernel-packages] [Bug 1628835] Re: msg='apparmor="DENIED" operation="dbus_method_call"

[dino99]

** Description changed:

  Get some apparmor 'DENIED' messages logged when booting with 4.8.0-17
  kernel; this was not happening with some previous versions (at least
  4.8.0-12) and no other upgrades can explain such apparmor messages, so
  blaming the kernel.
  
- 
-  oem@u64:~$ journalctl | grep  DENIED
+  oem@u64:~$ journalctl | grep  DENIED
  
  Sep 29 08:11:52 u64 audit[840]: USER_AVC pid=840 uid=101 auid=4294967295
  ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call"
  bus="system" path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"
  
  Sep 29 08:11:52 u64 kernel: audit: type=1107 audit(1475129512.681:27):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"
  
  Sep 29 08:11:53 u64 audit[840]: USER_AVC pid=840 uid=101 auid=4294967295
  ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call"
  bus="system" path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"
  
  Sep 29 08:11:53 u64 kernel: audit: type=1107 audit(1475129513.581:28):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"
  
  Sep 29 08:11:54 u64 audit[840]: USER_AVC pid=840 uid=101 auid=4294967295
  ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call"
  bus="system" path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"
  
  Sep 29 08:11:54 u64 kernel: audit: type=1107 audit(1475129514.585:29):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"
  
  Sep 29 08:11:55 u64 audit[840]: USER_AVC pid=840 uid=101 auid=4294967295
  ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call"
  bus="system" path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"
  
  Sep 29 08:11:55 u64 kernel: audit: type=1107 audit(1475129515.124:30):
  pid=840 uid=101 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/resolve1"
  interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
  mask="send" name="org.freedesktop.resolve1" pid=1287
  label="/usr/sbin/ntpd" peer_pid=1024 peer_label="unconfined"
  
+ 
+ Note: i wonder if there is a relationship with the previous logged line 
before that error appear:
+ ntpd[1282]: Soliciting pool server .
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-generic 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  oem2213 F pulseaudio
-  /dev/snd/pcmC0D0p:   oem2213 F...m pulseaudio
-  /dev/snd/controlC0:  oem2213 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  oem2213 F pulseaudio
+  /dev/snd/pcmC0D0p:   oem2213 F...m pulseaudio
+  /dev/snd/controlC0:  oem2213 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Sep 29 10:58:44 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
-  lono wireless extensions.
-  
-  eth1  no wireless extensions.
-  
-  eth0  no wireless extensions.
+  lono wireless extensions.
+ 
+  eth1  no wireless extensions.
+ 
+  eth0  no wireless extensions.
  Lsusb:
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
- 

Re: [Kernel-packages] [Bug 1604396] Re: Kernel 4.4.0-31 cd into NFS4 directory: Operation not permitted

[Reinhard Zierke]

On Mon, Oct 03, 2016 at 07:36:35PM -, Joseph Salisbury wrote:
> Would it be possible for you to test the latest upstream stable kernel?
> Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
> latest v4.4 stable kernel[0].

Works fine, thank you very much.
 
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.

Done.
 
Cheers,
  Reinhard

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

Title:
  Kernel 4.4.0-31 cd into NFS4 directory: Operation not permitted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since apt-upgrading my Ubuntu 16.04 PC to kernel 4.4.0-31 I can't cd
  into NFS4 subvolumes any more:

  zierke@rzpc100$ uname -a
  Linux rzpc100 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  zierke@rzpc100$ kinit
  Password for zie...@informatik.uni-hamburg.de:
  zierke@rzpc100$ cd /informatik2
  zierke@rzpc100$ cd rz
  -bash: cd: /informatik2/rz: Operation not permitted

  When I reboot my PC with the previous kernel 4.4.0-28 this works fine.

  This problem has also been mentioned in
  
https://www.kubuntuforums.net/showthread.php?70499-Latest-16-04-bug-NFS-problem-no-access-unless-I-use-root-first-strange
  https://ubuntuforums.org/showthread.php?t=2331137

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

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

[Kernel-packages] [Bug 1628506] Re: Dual monitor - screen flashes and turns black on mouse movement and keyboard input

[Reiner Jung]

Yes, it started after upgrading to the current kernel. I will try to use
the upstream kernel and I will try to create a bootable USB-stick with a
fresh install. I hope, I have time to make the tests during this week.

Kind regards
Reiner

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

Title:
  Dual monitor - screen flashes and turns black on mouse movement and
  keyboard input

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553503 
  However, there are minor differences.

  The dual monitor support worked with Ubuntu 16.04

  This affects Ubuntu 16.10. 
  - Kernel Linux 4.8.0-17-generic
  - VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
  - CPU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz

  The issue manifests in multiple ways:
  a) When moving the mouse from one screen to another, on the leaving screen an 
area in the upper left corner approx. 6 by 6 cm (on an 20" screen) flashes 
(dark).
  b) In case the mouse is on the left screen
  - I move it to the right (the screen flashes) 
  - I select a text editor component (the screen flashes or the screen turns 
black for at least a second)
  - I type text (the screen flashes once or the screen turns black for at least 
a second)

  I tested this behavior with Ubuntu's Unity desktop and gnome-shell. It does 
not appear when switching between screens on the login screen. However ,ti does 
appear in case I use the switch user to get another login screen.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reiner 7701 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=400e238e-4dcd-443f-a42a-13d2056d1158
  InstallationDate: Installed on 2016-05-31 (119 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   docker0   no wireless extensions.
   
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic.efi.signed 
root=UUID=97043ee3-cff3-41af-81bc-948bebf57198 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  RfKill:
   
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/08/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd12/08/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

[bugproxy]

--- Comment From praveen.pan...@in.ibm.com 2016-10-04 04:17 EDT---
Hi

Trying to Verify this bug on Ubuntu16.10 ( 4.8.0-17)   now dump captured
but makedumpfile failed so dump was in incomplete.

LOG:

1;-1f[   92.085437] kdump-tools[10063]: Starting kdump-tools:  * running 
makedumpfile -c -d 31 /proc/vmcore /
p-incomplete
[   92.095715] kdump-tools[10063]: get_mem_map: Can't distinguish the memory 
type.
[   92.096864] kdump-tools[10063]: The kernel version is not supported.
[   92.097605] kdump-tools[10063]: The makedumpfile operation may be incomplete.
[   92.098438] kdump-tools[10063]: makedumpfile Failed.
[   92.099249] kdump-tools[10063]:  * kdump-tools: makedumpfile failed, falling 
back to 'cp'

Ubuntu Yakkety Yak (development branch) ltc-brazos1 hvc0

root@ltc-brazos1:/var/crash/201610040259# ls
vmcore-incomplete
root@ltc-brazos1:/var/crash/201610040259#

Regards
Praveen

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

Title:
  In Ubuntu16.10:Fadump fails as Kernel panic reported while
  dumping-,console got hung on 32TB Brazos System (kdump)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-07-17 
02:37:31 ==
  Hi 

   In Ubuntu16.10 I  I tried fadump in Brazos system (32TB Memory and
  192 core) , when trigger panic in kernel panic occur and console got
  hung.

  Reproducible Step:

  1- Install Ubuntu16.10
  2- boot system with 31TB and 192 Core 
  3- configure fadump in system 
  4- verify fadump in system that it is running 
  5- Trigger panic in system

  Actual Result

  Not able  to take Fadump , kernel panic and console got hung

  Expected Result

  Fadump will be captured

  Log:

  root@ltc-brazos1:~# kdump-config show
  DUMP_MODE:fadump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
 /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 fadump
  root@ltc-brazos1:~# 

  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 fadump=on 
fadump_reserve_mem=4096M crashkernel=4096M
  root@ltc-brazos1:~# 

  ltc-brazos1 login: [  442.749993] sysrq: SysRq : Trigger a crash  

  
  [  442.750031] Unable to handle kernel paging request for data at address 
0x  
  
  [  442.750037] Faulting instruction address: 0xc0670014   

  
  [  442.750043] Oops: Kernel access of bad area, sig: 11 [#1]  

  
  [  442.750047] SMP NR_CPUS=2048 NUMA pSeries  

  
  [  442.750053] Modules linked in: pseries_rng btrfs xor raid6_pq rtc_generic 
sunrpc autofs4 ses enclosure ipr
   
  [  442.750068] CPU: 157 PID: 403890 Comm: bash Not tainted 4.4.0-30-generic 
#49-Ubuntu  

  [  442.750074] task: c3f97b0af640 ti: c3f97b104000 task.ti: 
c3f97b104000

  [  442.750079] NIP: c0670014 LR: c06710c8 CTR: 
c066ffe0
 
  [  442.750083] REGS: c3f97b107990 TRAP: 0300   Not tainted  
(4.4.0-30-generic)  

  [  442.750088] MSR: 80009033   CR: 2824  
XER: 0001   
 
  [  442.750100] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1

  GPR00: c06710c8 c3f97b107c10 c15b5d00 0063

  
  GPR04: c1faba749c50 c1faba75b4e0 c0001f3efe7c 0313 
  GPR08: 0007 0001  c0001f3efe7cecb8 
  GPR12: c066ffe0 cbc9d380  2200 
  GPR16: 10170dc8 01001

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

[bugproxy]

--- Comment From praveen.pan...@in.ibm.com 2016-10-04 04:27 EDT---
Hi

verified this bug on Ubuntu16.10(4.8 ) it works fine .

LOG:

root@ltc-brazos1:~/tm-test-le# ./runtests.sh
Running ./htm_fork
PASSED!
Running ./htm_vmxcopy
PASSED!
Running ./htm_dscr
Starting, 1 loops
PASSED!
Running ./htm_dscr
Starting, 1 loops
PASSED!
Running ./htm_tar
Starting, 1 loops
PASSED!
Running ./htm_fpunavailable
Thread doing stuff!
Entering FP function
Transaction done, ret = 0, TEXASR 0x11c01,
TFIAR 0x100029e9 f = 1337.00.
FAIL, wrong number of aborts.
Done.
Test failed code:0 ./htm_fpunavailable
root@ltc-brazos1:~/tm-test-le#

Regards
Praveen

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

Title:
  in Ubuntu16.10: Hit on Call traces  and system goes down when
  transactional memory  tests are running in 32TB Brazos system

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

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-07-16 
14:21:39 ==
  ---Problem Description---
   In Ubuntu16.10 Call traces and unrecoverable exception occurs when 
Transactional memory tests are executed in 32TB system.

  Steps to reproduce:
   
  1- Download tm tests from the link - 
'http://ozlabs.au.ibm.com/~mikey/tm-test-le.tar.gz' 

  2- untar tm-test-le.tar.gz; make clean; make; ./runtests.sh

  The system gives below call traces and goes down. [Not able to do ssh
  and the console gets hung]

  LOG:

  Running ./htm_demo
  Starting 6144 worker threads, 5 loops
  --
  --
  [  438.064162] CFAR: c0008d18 SOFTE: 0

  
  PACATMSCRATCH: 80029033   

  
  GPR00: c0111028 c5f82e36f4b0 c15b5d00 

  
  GPR04: c0b28863 0001 c1755d00 00018748

  
  GPR08: 04f0 f5257d14 01fab980 0005

  
  GPR12: 0500 cbc9dd00 3ffcf5fa 0100

  
  GPR16:  c1faba7898e8 0001 c3f9865bf804

  
  GPR20: 0003 c01638b0 0001 00661a113a10

  
  GPR24:  c5f82e9f2060 01fab980 c15eaa60

  
  GPR28: c0f9e900 009e c15eaa60 c1faba79e900

  
  [  438.064303] NIP [c00a1ba4] kvmppc_interrupt_hv+0x28/0x15c  

  
  [  438.064315] LR [c0111028] trigger_load_balance+0x58/0x340  

  
  [  438.064323] Call Trace:

  
  [  438.064330] [c5f82e36f4b0] [c0111028] 
trigger_load_balance+0x58/0x340 (unreliable)
   
  [  438.064346] [c5f82e36f4f0] [c00f9ee4] 
scheduler_tick+0x104/0x180  
   
  [  438.064360] [c5f82e36f550] [c014c128] 
update_process_times+0x78/0xa0  
   
  [  438.064378] [c5f82e36f580] [c0163818] 
tick_sched_handle.isra.6+0x48/0xe0  
   
  [  438.064392] [c5f82e36f5c0] [c0163914] 
tick_sched_timer+0x64/0xd0  
  

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

[bugproxy]

--- Comment From mukeo...@in.ibm.com 2016-10-04 04:54 EDT---
Hi Tim,

Can you please remove this tag 'verification-needed-xenial' for now as the fix 
is not
yet released for Xenial.

Enable the tag once it is released for Xenial.

-Mukesh

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

Title:
  Failed to acknowledge elog:
  /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or
  directory)

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

Bug description:
  == Comment: #0 - Mukesh K. Ojha  - 2016-09-02 02:10:14 ==
  ---Problem Description---
  Kernel is failed to free the kobject while acknowledging the error log which 
has been notified two times.
   
  Contact Information = Contact Information =  mukeo...@in.ibm.com 
   
  ---uname output---
  Ubuntu 16.04.01 LTS
   
  Machine Type = All power machine 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   
  Steps to reproduce:
  1.Boot the system to petitboot.
  2. Issue FSP Soft reset of Service Processor From ASMI page.
  3. After FSP comes up, boot the system to host OS.
  4. In the host OS seen the failure to acknowledge for one of elog.

  
  root@p8wookie ~]# service opal_errd status
  Redirecting to /bin/systemctl status  opal_errd.service
  opal_errd.service - opal_errd (PowerNV platform error handling) Service
 Loaded: loaded (/usr/lib/systemd/system/opal_errd.service; enabled)
 Active: active (running) since Wed 2016-08-03 07:55:03 CDT; 2min 4s ago
Process: 3452 ExecStart=/usr/libexec/ppc64-diag/opal_errd start 
(code=exited, status=0/SUCCESS)
   Main PID: 3497 (opal_errd)
 CGroup: /system.slice/opal_errd.service
 ??3497 /usr/sbin/opal_errd

  Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)


  
  [root@p8wookie ~]# cd /sys/firmware/opal/elog/
  [root@p8wookie elog]# ls
  0x5018d709
  [root@p8wookie elog]# 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Contact Information =  mukeo...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Mukesh K. Ojha  - 2016-09-02 02:12:45 ==
  Upstream commit :

  commit a9cbf0b2195b695cbcaa4e2770948c212e9a
  Author: Mukesh Ojha 
  Date:   Mon Aug 22 12:17:44 2016 +0530

  powerpc/powernv : Drop reference added by kset_find_obj()
  
  In a situation, where Linux kernel gets notified about duplicate error log
  from OPAL, it is been observed that kernel fails to remove sysfs entries
  (/sys/firmware/opal/elog/0x) of such error logs. This is because,
  we currently search the error log/dump kobject in the kset list via
  'kset_find_obj()' routine. Which eventually increment the reference count
  by one, once it founds the kobject.

  
  Above patch is the solution of this bugzilla.

  Kindly pull this patch in for both Ubuntu 16.04 LTS and Ubuntu 16.10.

  -Mukesh

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

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

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

[bugproxy]

--- Comment From hbath...@in.ibm.com 2016-10-04 05:08 EDT---
(In reply to comment #27)
> Hi
>
>Trying to Verify this bug on Ubuntu16.10 ( 4.8.0-17)   now dump captured
> but makedumpfile failed so dump was in incomplete.
>
> LOG:
>
>  1;-1f[   92.085437] kdump-tools[10063]:
> Starting kdump-tools:  * running makedumpfile -c -d 31 /proc/vmcore /
> p-incomplete
>
> [   92.095715] kdump-tools[10063]: get_mem_map: Can't distinguish the memory
> type.
>

Bug 146571 / LP Bug 1626269 is being used to track this..

Thanks
Hari

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

Title:
  In Ubuntu16.10:Fadump fails as Kernel panic reported while
  dumping-,console got hung on 32TB Brazos System (kdump)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-07-17 
02:37:31 ==
  Hi 

   In Ubuntu16.10 I  I tried fadump in Brazos system (32TB Memory and
  192 core) , when trigger panic in kernel panic occur and console got
  hung.

  Reproducible Step:

  1- Install Ubuntu16.10
  2- boot system with 31TB and 192 Core 
  3- configure fadump in system 
  4- verify fadump in system that it is running 
  5- Trigger panic in system

  Actual Result

  Not able  to take Fadump , kernel panic and console got hung

  Expected Result

  Fadump will be captured

  Log:

  root@ltc-brazos1:~# kdump-config show
  DUMP_MODE:fadump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
 /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 fadump
  root@ltc-brazos1:~# 

  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 fadump=on 
fadump_reserve_mem=4096M crashkernel=4096M
  root@ltc-brazos1:~# 

  ltc-brazos1 login: [  442.749993] sysrq: SysRq : Trigger a crash  

  
  [  442.750031] Unable to handle kernel paging request for data at address 
0x  
  
  [  442.750037] Faulting instruction address: 0xc0670014   

  
  [  442.750043] Oops: Kernel access of bad area, sig: 11 [#1]  

  
  [  442.750047] SMP NR_CPUS=2048 NUMA pSeries  

  
  [  442.750053] Modules linked in: pseries_rng btrfs xor raid6_pq rtc_generic 
sunrpc autofs4 ses enclosure ipr
   
  [  442.750068] CPU: 157 PID: 403890 Comm: bash Not tainted 4.4.0-30-generic 
#49-Ubuntu  

  [  442.750074] task: c3f97b0af640 ti: c3f97b104000 task.ti: 
c3f97b104000

  [  442.750079] NIP: c0670014 LR: c06710c8 CTR: 
c066ffe0
 
  [  442.750083] REGS: c3f97b107990 TRAP: 0300   Not tainted  
(4.4.0-30-generic)  

  [  442.750088] MSR: 80009033   CR: 2824  
XER: 0001   
 
  [  442.750100] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1

  GPR00: c06710c8 c3f97b107c10 c15b5d00 0063

  
  GPR04: c1faba749c50 c1faba75b4e0 c0001f3efe7c 0313 
  GPR08: 0007 0001  c0001f3efe7cecb8 
  GPR12: c066ffe0 cbc9d380  2200 
  GPR16: 10170dc8 01001ef401d8 10140f58 100c7570 
  GPR20:  1017dd58 10153618 1017b608 
  GPR24: 37c9e7b4 0001 c14f8e58 0004 
  GPR28: c14f9218 0063 c14b11dc  
  [  442.750165] NIP [c0670014] sysrq_handle

[Kernel-packages] [Bug 1626970] Re: Graphics not working after upgrade

[trikrasne]

it seems that the computer hanged during the upgrade to the proposed
kernel.

https://drive.google.com/open?id=0Bz57fWPbu2BELWFGWld3a190VG8

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

Title:
  Graphics not working after upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't log-in in graphic mode after upgrading Ubuntu. I can only log-
  in via terminal.

  These are some errors reported after booting the vomputer, just before
  the login-screen.

  (45.185133) amdgpu :0a:00.0: couldn't schedule ib
  (45.185179) (drm:amdgpu_sched_run_job (amdgpu)) *ERROR* Error scheduling 
IBs (-22)
  (45.185221) (drm:amd_sched_main (amdgpu)) *ERROR* Faild to run job!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Sep 23 12:41:36 2016
  HibernationDevice: RESUME=UUID=9ae50736-ddfe-4650-9a8d-d0fa60d324cf
  InstallationDate: Installed on 2015-08-28 (391 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP ProBook 450 G2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-08 (137 days ago)
  dmi.bios.date: 11/27/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M73 Ver. 01.00
  dmi.board.name: 2248
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 59.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM73Ver.01.00:bd11/27/2014:svnHewlett-Packard:pnHPProBook450G2:pvrA3008DD10B03:rvnHewlett-Packard:rn2248:rvrKBCVersion59.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 450 G2
  dmi.product.version: A3008DD10B03
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1625932] Re: Backlight does not change when adjust it higher than 50% after S3

[Shih-Yuan Lee]

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Backlight does not change when adjust it higher than 50% after S3

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

Bug description:
  Backlight does not change when adjust it higher than 50% after S3

  Steps:
  1. Install ubuntu 16.04 and boot into OS
  2. suspend system
  3. resume system from S3
  4. Try to adjust brightness level

  Expected results: Backlight should be changed when adjust it

  Actual results: Backlight does not change when adjust it higher than
  50% after S3

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

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

[Kernel-packages] [Bug 1627709] Re: Ubuntu 16.10(Yakkety Yak) server amd64 and i386 from 21-Sep-2016 installation fails

[Ovidiu Rusu]

With the latest daily image installation works fine.

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

Title:
  Ubuntu 16.10(Yakkety Yak) server amd64 and i386 from 21-Sep-2016
  installation fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I was trying to install Ubuntu 16.10(Yakkety Yak) server amd64 from 
21-Sep-2016 Ubuntu 16.10(Yakkety Yak).
  Unfortunately the installation failed at software install.

  The following messages appear in the console:

  in-target: The following packages have unmet dependencies:
  in-target: libpython3.5 : Depends: libpython3.5-stdlib (= 3.5.2-4ubuntu2) but 
3.5.2-4ubuntu3 is to be installed
  in-target: Unable to correct problems, you have held broken packages.
  in-target: tasksel: apt-get failed (100)
  main-menu[785]: WARNING **: Configuring 'pkgsel' failed with error code 1
  main-menu[785]: WARNING **: Menu item 'pkgsel' failed.

  Note: This case also applies to Ubuntu 16.10 server i386 from 21-Sep-2016.
  With the images from 24-Sep-2016 amd64 and i386 the installation failed 
because CD-ROM couldn't be mounted.

  Thanks,
  Ovidiu.

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

-- 
Mailing list: https://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 1628694] Re: Ubuntu 16.10 bluetooth doesn't work

[Alex]

Definitely it  happened  after some upgrade, two-three months before 
now. I'm currently running Linux version 4.8.0-17. The bug was in 
previous version as well. If I load daily build 30 SEnt 2016, it also 
uses kernel 4,8,0-17 generic and it also has this bug. At the same time 
content of directory /lib/firware/bcrm is:

bcm4329-fullmac-4.bin
bcm43xx-0.fw
bcm43xx_hdr-0.fw
brcmfmac43143.bin
brcmfmac43143-sdio.bin
brcmfmac43236b.bin
brcmfmac43241b0-sdio.bin
brcmfmac43241b4-sdio.bin
brcmfmac43241b5-sdio.bin
brcmfmac43242a.bin
brcmfmac4329-sdio.bin
brcmfmac4330-sdio.bin
brcmfmac43340-sdio.bin
brcmfmac4334-sdio.bin
brcmfmac4335-sdio.bin
brcmfmac43362-sdio.bin
brcmfmac4339-sdio.bin
brcmfmac43455-sdio.bin
brcmfmac4350c2-pcie.bin
brcmfmac4350-pcie.bin
brcmfmac4354-sdio.bin
brcmfmac43569.bin
brcmfmac4356-pcie.bin
brcmfmac43570-pcie.bin
brcmfmac43602-pcie.ap.bin
brcmfmac43602-pcie.bin
brcmfmac4366b-pcie.bin
brcmfmac4371-pcie.bin


On 2016-10-03 02:52 PM, Joseph Salisbury wrote:
> 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
> tohttps://wiki.ubuntu.com/KernelMainlineBuilds  . Please test the latest
> v4.8 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.8
>
> ** 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/1628694

Title:
  Ubuntu 16.10 bluetooth doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:

  I'm trying unsuccessfully to connect headphone via bluetooth.
  Configuration: Ubuntu-gnome 16:10, Dell XPS-15. lspci shows:

  06:00.0 Network controller: Broadcom Limited BCM4352 802.11ac Wireless
  Network Adapter (rev 03)

  lsusb shows:

  Bus 003 Device 004: ID 0a5c:216f Broadcom Corp. BCM20702A0 Bluetooth

  Below is what I see in my syslog:

  Sep 27 18:19:22 alex-XPS-15-9530 /usr/lib/gdm3/gdm-x-session[4781]: (II) 
modeset(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080 1081 
1084 1118 -hsync +vsync (67.1 kHz e)
  Sep 27 18:19:22 alex-XPS-15-9530 gnome-control-c[6754]: Ignoring launcher 
gufw (missing desktop file)
  Sep 27 18:19:22 alex-XPS-15-9530 gnome-control-c[6754]: Ignoring launcher 
landscape-client-settings (missing desktop file)
  Sep 27 18:19:22 alex-XPS-15-9530 gnome-control-c[6754]: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  Sep 27 18:19:22 alex-XPS-15-9530 dbus-daemon[4819]: Activating via systemd: 
service name='org.bluez.obex' unit='dbus-org.bluez.obex.service'
  Sep 27 18:19:22 alex-XPS-15-9530 dbus-daemon[4819]: Activation via systemd 
failed for unit 'dbus-org.bluez.obex.service': Unit dbus-org.bluez.obex.service 
not found.
  Sep 27 18:20:29 alex-XPS-15-9530 systemd[1]: Starting Cleanup of Temporary 
Directories...
  Sep 27 18:20:29 alex-XPS-15-9530 systemd-tmpfiles[6783]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Sep 27 18:20:29 alex-XPS-15-9530 systemd[1]: Started Cleanup of Temporary 
Directories.
  Sep 27 18:20:41 alex-XPS-15-9530 bluetoothd[6689]: a2dp-sink profile connect 
failed for 00:18:16:07:03:FD: Protocol not available
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alex   2188 F pulseaudio
   /dev/snd/controlC0:  alex   2188 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=9c7af056-2269-4b01-9b5c-eeb6e7b3b43a
  InstallationDate: Installed on 2016-06-01 (119 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
  MachineType: Dell Inc. XPS 15 9530
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip disk lpadmin plugdev sambashare sudo 
vboxusers
  _Mark

[Kernel-packages] [Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

[Joseph Salisbury]

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

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

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.

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

Title:
  Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

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

Bug description:
  When I install Ubuntu 16.04 on my computer the screen goes blank at
  login. I can blindly login and it boots but I cannot use the display
  (external monitor through HDMI).

  I've looked online for an answer to this issue but could not find a
  solution.  However, many people report this issue in forums with the
  4.4x kernel.

  On my main computer, I upgraded from 14.04 to 16.04.1. On this
  computer I was able to switch back to the 3.13 kernel which *does
  work*.

  On the same computer, if I use a 16.04 live CD, it does the same
  thing.  The screen goes blank.

  UEFI may be part of the issue as well.  I have it disabled in bios
  (set to legacy mode) but when I first boot, it seems to go into UEFI
  mode first and then, after rebooting with  it shows
  me the list of kernels. I can select the kernel from there but if I
  use a 4.4x kernel, it blanks out at encryption passphrase screen.

  There are also people with similar issues on AskUbuntu.

  Here's some basic HW info.  If you require more, please ask.

  sudo lshw | head
  zbox
  description: Notebook
  product: ZBOX-ID18 (NA)
  vendor: ZOTAC
  version: XX
  serial: G211X
  width: 64 bits
  capabilities: smbios-2.7 dmi-2.7 vsyscall32
  configuration: boot=normal chassis=notebook family=NA sku=NA 
uuid=00020003-0004-0005-0006-000700080009
    *-core

  sudo lshw -C display
    *-display
     description: VGA compatible controller
     product: 3rd Gen Core processor Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 09
     width: 64 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:45 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user5536 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38
  InstallationDate: Installed on 2014-07-23 (743 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  MachineType: ZOTAC ZBOX-ID18
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.157.2
  RfKill:

  StagingDrivers: rts5139
  Tags:  xenial staging
  Uname: Linux 3.13.0-92-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B211P011
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID18
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 10
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA:
  dmi.product.name: ZBOX-ID18
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

[Kernel-packages] [Bug 1608236] Re: Regression: S-video output does not work

[Joseph Salisbury]

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

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

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

Title:
  Regression: S-video output does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Regression. S-video output can not be used. It works by 4.4.0-22-generic.
  xrandr tells on 4.4.0-31-generic:

  TV1 unknown connection (normal left inverted right x axis y axis)
 848x480   50.00 +
 640x480   50.00 +
 1024x768  50.00  
 800x600   50.00

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1573 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jul 31 17:15:16 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (94 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 89224MG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/06
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 63ET13WW
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 89224MG
  dmi.product.version: 3000 C200
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

[Joseph Salisbury]

Thanks for the update, Junien.  Now we know the fix is in the upstream
v4.8-rc8 kernel.  Then next step is to identify the commit that fixes
this bug, and then SRU it to Xenial.

It would be best to next step the latest upstream 4.4 kernel.  That will
tell us if the fix was already sent to upstream stable.  If it was not,
we will need to test some other upstream kernels to narrow down further
when the fix landed in mainline.

Can you test the upstream 4.4.23 kernel?  It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.23

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

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

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1630231] [NEW] /etc/hostid is not set after installing zfs

[Antti Toivonen]

Public bug reported:

When installing zfs on Ubuntu 16.04, official wiki instructs you to

 sudo apt install zfs

zfs points to zfsutils-linux. /etc/hostid remains missing after
installation. It will cause issues, when importing zfs pool after
restart.

Oct  4 07:07:13 ** kernel: [25947.708287] SPL: The /etc/hostid file is not 
found.
Oct  4 07:07:13 ** kernel: [25947.708292] SPL: using hostid 0x

/etc/hostid is generated by package spl, on which zfsutils-linux should
depend on. Alternatively /etc/hostid should be generated by zfsutils-
linux.

/var/log$ uname -a
Linux * 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

/var/log$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

/var/log$ apt show zfsutils-linux
Package: zfsutils-linux
Version: 0.6.5.6-0ubuntu12
Priority: extra
Section: admin
Source: zfs-linux
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Darik Horn 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 794 kB
Provides: zfs
Depends: init-system-helpers (>= 1.18~), zfs-doc (= 0.6.5.6-0ubuntu12), 
libblkid1 (>= 2.16), libc6 (>= 2.14), libnvpair1linux, libuuid1 (>= 2.16), 
libuutil1linux, libzfs2linux, libzpool2linux, python
Recommends: zfs-dkms, zfs-zed
Suggests: samba-common-bin (>= 3.0.23), nfs-kernel-server, zfs-initramfs
Conflicts: zfs, zfs-fuse
Replaces: zfs
Homepage: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.6
Supported: 5y
Download-Size: 276 kB
APT-Manual-Installed: yes
APT-Sources: http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
Description: Native OpenZFS management utilities for Linux
 This package provides the zpool and zfs commands that are used to
 manage OpenZFS filesystems.

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

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

Title:
  /etc/hostid is not set after installing zfs

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  When installing zfs on Ubuntu 16.04, official wiki instructs you to

   sudo apt install zfs

  zfs points to zfsutils-linux. /etc/hostid remains missing after
  installation. It will cause issues, when importing zfs pool after
  restart.

  Oct  4 07:07:13 ** kernel: [25947.708287] SPL: The /etc/hostid file is 
not found.
  Oct  4 07:07:13 ** kernel: [25947.708292] SPL: using hostid 0x

  /etc/hostid is generated by package spl, on which zfsutils-linux
  should depend on. Alternatively /etc/hostid should be generated by
  zfsutils-linux.

  /var/log$ uname -a
  Linux * 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  /var/log$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  /var/log$ apt show zfsutils-linux
  Package: zfsutils-linux
  Version: 0.6.5.6-0ubuntu12
  Priority: extra
  Section: admin
  Source: zfs-linux
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Darik Horn 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 794 kB
  Provides: zfs
  Depends: init-system-helpers (>= 1.18~), zfs-doc (= 0.6.5.6-0ubuntu12), 
libblkid1 (>= 2.16), libc6 (>= 2.14), libnvpair1linux, libuuid1 (>= 2.16), 
libuutil1linux, libzfs2linux, libzpool2linux, python
  Recommends: zfs-dkms, zfs-zed
  Suggests: samba-common-bin (>= 3.0.23), nfs-kernel-server, zfs-initramfs
  Conflicts: zfs, zfs-fuse
  Replaces: zfs
  Homepage: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.6
  Supported: 5y
  Download-Size: 276 kB
  APT-Manual-Installed: yes
  APT-Sources: http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  Description: Native OpenZFS management utilities for Linux
   This package provides the zpool and zfs commands that are used to
   manage OpenZFS filesystems.

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

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

[Kernel-packages] [Bug 1629784] Re: Ubuntu16.04 installation failed on IBM LE server

[Joseph Salisbury]

** Tags removed: kernel-key
** 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/1629784

Title:
  Ubuntu16.04 installation failed on IBM LE server

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu OS installation is getting failed on IBM LE server. Please let
  us know whether this is System/OS specific issue.,

  Also please include "christy.rajku...@broadcom.com" in bug_list for
  any further information regarding bug.

  We tried installation with the image("ubuntu-16.04-server-ppc64el") that is 
available 
  under link: http://cdimage.ubuntu.com/releases/16.04.1/release/

  
  Please find the error message below.
   
   
   
   GNU GRUB  version 2.02~beta2-36ubuntu3
   
   
++
   |*Install
|
   | Rescue mode
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   
++
   
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line.
  '
   
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) 
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon 
Apr 18 18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/install/vmlinux tasks=standard 
pkgsel/language-pack-patterns= pkgsel/install-language-support=false --- quiet
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0ad4
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0eb8... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0ad5 -> 0x0ad5197e
  Device tree struct  0x0ad6 -> 0x0adb
   -> smp_release_cpus()
  spinning_secondaries = 191
   <- smp_release_cpus()
   <- setup_system()
  [1.277480] pci 0005:50:00.0: of_irq_parse_pci() failed with rc=-22
  [1.490146] pci 0007:80:00.0: of_irq_parse_pci() failed with rc=-22
  [3.611923] genirq: Flags mismatch irq 16.  (hvc_console) vs. 
 (hvsi)
  [3.611954] hvc_open: request_irq failed with rc -16.
  [3.611981] Warning: unable to open an initial console.
  Starting system log daemon: syslogd, klogd.

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

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

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Joseph Salisbury]

Balibir, the v4.8 final kernel is now available and can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/

The latest upstream stable 4.4 kernel is also avaiable from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.23

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

Title:
  memory_stress_ng failing for Power architecture for 16.04

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

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

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

[Kernel-packages] [Bug 1538909] Re: OPRASHB:Habanero:EEH: Opal not calling out slot number for failing adapter behind plx switch

[Tim Gardner]

commit 7e56f627768da4e6480986b5145dc3422bc448a5 (powerpc/eeh: Fix PE
location code) does not appear to do anything other then add a function
that is unused.

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

Title:
  OPRASHB:Habanero:EEH: Opal not calling out slot number for failing
  adapter behind plx switch

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  New
Status in linux source package in Wily:
  New
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - MAMATHA INAMDAR  - 2016-01-14 04:51:41 
==
  ---Problem Description---
  Working with Chad (IO team) we were able to inject an EEH recoverable error 
to the broadcom network adapter (PE #2) behind the PLX switch. Looks like OPAL 
calls out the Backplane PLX ( Planar ) instead of the adapter slot.

  We want to primarily focus on why the adapter slot ( behind PLX )
  didn't get called out using this defect.

  Problem:
  
  >> Working with Chad (IO team) we were able to inject an EEH recoverable error
  >> to the broadcom network adapter (PE #2) and noticed that we are not getting
  >> the adapter slot called out, instead we get the location pointing to the
  >> backplane PLX.
  >
  >If what you injected is a PCIe error message, I think those cause the
  >switch leg to freeze, but I will need Gavin to confirm.
  >
  >> Per Chad:
  >> 
??
  >> ?They're logging the right PE (#2--which corresponds to the 
Broadcom??
  >> ?adapter)--they're just not pointing to its slot 
explicitly.??
  >> 
??
  >>
  >>
  >>
  >> Here is a snippet the /var/log/messages:
  >>
  >> 
??
  >> ?Nov 11 12:17:18 habmc8p01 kernel: EEH: Frozen PHB#1-PE#2 
detected
  >> ?Nov 11 12:17:18 habmc8p01 kernel: bnx2x: [bnx2x_timer:5750(net0)]MFW 
seems???
  >> ?hanged: drv_pulse (0x1c1) != mcp_pulse 
(0x7fff)??
  >> ?Nov 11 12:17:18 habmc8p01 kernel: EEH: PE location: Backplane PLX, PHB 
location:
  >> ?Backplane 
PLX
  >> 
??
  >>
  >>
  >>
  >>
  >> injection:
  >> setpci -s 0001:0c:00.2 COMMAND
  >> ???
  >> ?setpci -s??0001:0c:00.2???
  >> ?COMMAND=0540??
  >> ???

  It seems you're disabling memory BAR and then issue MMIO load, which results
  in "unsupported request" returned from the adapter. In response to that, the
  PE#2 as shown in the kernel log is put to frozen state. Nothing wrong at this
  point. I think the only question would be: the location code isn't making 
sense.
   
  Contact Information = - 
   
  ---uname output---
  3.19.0-43-generic
   
  Machine Type =  
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   This bug is follow up of bug 133061. This  bug is opened to backport the 
kernel patch which is available to fix the issue for bug 133061 on Ubuntu.
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for -: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  Firestone server ( Ubuntu Host )
  =

  I have built the Ubuntu kernel with patch and created  *.deb files.

  Please find the same in the following path for installing and testing
  your test case

   State: Assigned by: thalerj on 13 January 2016 12:10:58 

  The patched kernel is working great for both firestone and Habanero.
  It resolves the issue and all slot numbers are called out properly.

  == Comment: #1 - MAMATHA INAMDAR  - 2016-01-28 01:02:23 
==
  Patch is now available in the following branch

  
https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=7e56f627768da4e6480986b5145dc3422bc448a5

  == Comment: #3 - MAMATHA INAMDAR  - 2016-01-28
  01:09:14 ==

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

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

[Kernel-packages] [Bug 1630063] Re: specific USB devices disconnect and don't reconnect

[Joseph Salisbury]

Can you see if this bug happens with the v4.8-rc1 kernel?  It can be downloaded 
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/

If it does happen with -rc1, we can bisect between v4.7 and v4.8-rc1 to
identify the commit that introduced this regression.

Thanks in advance!

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

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

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

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

** Tags added: performing-bisect

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

Title:
  specific USB devices disconnect and don't reconnect

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

Bug description:
  2 USB ports randomly disconnect and don't reconnect (it's always the
  same two), and in dmesg all I get is

  "
  [ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled
  [ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up
  [ 1276.916553] usb 3-1: USB disconnect, device number 2
  [ 1277.017302] usb 3-2: USB disconnect, device number 3
  "
  This only started happening when Yakkety went to the 4.8 branch, with 4.7 
branch this doesn't occur, hence the bug report since it's unlikely that a 
hardware failure will only stick to one OS and one branch of the kernel for 
that OS. (these USB ports don't randomly die on Windows or BSD, I've tested 
that in the past couple of days)

  
  kernel version: 4.8.0.17.27
  Ubuntu version
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  c_smith2213 F pulseaudio
   /dev/snd/controlC0:  c_smith2213 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1a29baaa-55ea-4817-ba45-8c618f65ec4b
  InstallationDate: Installed on 2016-10-03 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161002)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic 
root=/dev/mapper/Linux-root ro nomodeset quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1621939] Re: Dell XPS 13 9333 (Intel Haswell) hangs several times per day

[Joseph Salisbury]

The v4.8 final kernel is now available.  It might be good to give it a
test.  It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/

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

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

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

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

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

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

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [dr

[Kernel-packages] [Bug 1619552] Re: Failed to acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or directory)

[Tim Gardner]

commit 8f1d3b68ff08466f55c55e03f9aa4d989c515095 (powerpc/powernv : Drop
reference added by kset_find_obj()) was released in UBUNTU:
Ubuntu-4.4.0-39.59 which never made it out of proposed. It has since
been superseded by Ubuntu-4.4.0-41.61 due to regressions respins. That
is the version that you should be verifying.

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

Title:
  Failed to acknowledge elog:
  /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or
  directory)

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

Bug description:
  == Comment: #0 - Mukesh K. Ojha  - 2016-09-02 02:10:14 ==
  ---Problem Description---
  Kernel is failed to free the kobject while acknowledging the error log which 
has been notified two times.
   
  Contact Information = Contact Information =  mukeo...@in.ibm.com 
   
  ---uname output---
  Ubuntu 16.04.01 LTS
   
  Machine Type = All power machine 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   
  Steps to reproduce:
  1.Boot the system to petitboot.
  2. Issue FSP Soft reset of Service Processor From ASMI page.
  3. After FSP comes up, boot the system to host OS.
  4. In the host OS seen the failure to acknowledge for one of elog.

  
  root@p8wookie ~]# service opal_errd status
  Redirecting to /bin/systemctl status  opal_errd.service
  opal_errd.service - opal_errd (PowerNV platform error handling) Service
 Loaded: loaded (/usr/lib/systemd/system/opal_errd.service; enabled)
 Active: active (running) since Wed 2016-08-03 07:55:03 CDT; 2min 4s ago
Process: 3452 ExecStart=/usr/libexec/ppc64-diag/opal_errd start 
(code=exited, status=0/SUCCESS)
   Main PID: 3497 (opal_errd)
 CGroup: /system.slice/opal_errd.service
 ??3497 /usr/sbin/opal_errd

  Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)


  
  [root@p8wookie ~]# cd /sys/firmware/opal/elog/
  [root@p8wookie elog]# ls
  0x5018d709
  [root@p8wookie elog]# 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Contact Information =  mukeo...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Mukesh K. Ojha  - 2016-09-02 02:12:45 ==
  Upstream commit :

  commit a9cbf0b2195b695cbcaa4e2770948c212e9a
  Author: Mukesh Ojha 
  Date:   Mon Aug 22 12:17:44 2016 +0530

  powerpc/powernv : Drop reference added by kset_find_obj()
  
  In a situation, where Linux kernel gets notified about duplicate error log
  from OPAL, it is been observed that kernel fails to remove sysfs entries
  (/sys/firmware/opal/elog/0x) of such error logs. This is because,
  we currently search the error log/dump kobject in the kset list via
  'kset_find_obj()' routine. Which eventually increment the reference count
  by one, once it founds the kobject.

  
  Above patch is the solution of this bugzilla.

  Kindly pull this patch in for both Ubuntu 16.04 LTS and Ubuntu 16.10.

  -Mukesh

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

-- 
Mailing list:

[Kernel-packages] [Bug 1627408] Re: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U

[Joseph Salisbury]

Can you see if this issue occurs with the Yakkety -proposed kernel?

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


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

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

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

Title:
  Severe graphics regression with mainline kernel v4.7.5 on Broadwell
  5500U

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

Bug description:
  I would like to report a severe graphics regression, involving
  frequent rainbow-glitching and flickering on a x64 computer with Intel
  Broadwell 5500U processor w/ integrated graphics. This issue was not
  present on kernel v4.7.4, which I will continue to use. Due to
  unfortunate issues with Broadwell integrated graphics support,
  virtually every kernel build in the 4.8 release chain as well as the
  newest v4.7.5 kernel have this issue. Dramatic multicolored patches
  and glitched areas appear frequently when using my computer with these
  kernels installed. The behavior is very similar to that of the
  Broadwell graphics issues present in kernel version 4.6.x. Please fix
  this issue, I don't understand why NEWER kernels are actually causing
  significant graphical problems with older hardware.

  I am running Ubuntu 16.04.1 LTS on an HP Spectre x360 4102dx with an Intel
  Broadwell 5500U core i7 processor with integrated intel Broadwell GT2 graphics

  Here is my system configuration:

  H/W path   Device Class  Description
  
system HP Spectre x360 Convertible 
(N5R94UA#ABA)
  /0bus802D
  /0/0  memory 64KiB BIOS
  /0/10 memory 32KiB L1 cache
  /0/11 memory 32KiB L1 cache
  /0/12 memory 256KiB L2 cache
  /0/13 memory 4MiB L3 cache
  /0/14 processor  Intel(R) Core(TM) i7-5500U CPU @ 
2.40GHz
  /0/16 memory 8GiB System Memory
  /0/16/0   memory 4GiB Row of chips Synchronous 1600 
MHz (0.6 ns)
  /0/16/1   memory 4GiB Row of chips Synchronous 1600 
MHz (0.6 ns)
  /0/100bridge Broadwell-U Host Bridge -OPI
  /0/100/2  displayBroadwell-U Integrated Graphics
  /0/100/3  multimedia Broadwell-U Audio Controller
  /0/100/14 busWildcat Point-LP USB xHCI Controller
  /0/100/14/0usb2   busxHCI Host Controller
  /0/100/14/1usb1   busxHCI Host Controller
  /0/100/14/1/1 input  USB Receiver
  /0/100/14/1/3 multimedia HP Truevision Full HD
  /0/100/14/1/4 input  Touchscreen
  /0/100/14/1/5 input  ITE Device(8350)
  /0/100/14/1/7 communication  Bluetooth wireless interface
  /0/100/16 communication  Wildcat Point-LP MEI Controller #1
  /0/100/1b multimedia Wildcat Point-LP High Definition 
Audio Controller
  /0/100/1c bridge Wildcat Point-LP PCI Express Root 
Port #2
  /0/100/1c/0   genericRTS5227 PCI Express Card Reader
  /0/100/1c.2   bridge Wildcat Point-LP PCI Express Root 
Port #3
  /0/100/1c.2/0  wlo1   networkWireless 7265
  /0/100/1f bridge Wildcat Point-LP LPC Controller
  /0/100/1f.2   storageWildcat Point-LP SATA Controller 
[AHCI Mode]
  /0/100/1f.3   busWildcat Point-LP SMBus Controller
  /0/1   scsi0  storage
  /0/1/0.0.0 /dev/sda   disk   512GB SAMSUNG MZNTE512
  /0/1/0.0.0/1   /dev/sda1  volume 449MiB Windows NTFS volume
  /0/1/0.0.0/2   /dev/sda2  volume 98MiB Windows FAT volume
  /0/1/0.0.0/3   /dev/sda3  volume 15MiB reserved partition
  /0/1/0.0.0/4   /dev/sda4  volume 15EiB Windows FAT volume
  /0/1/0.0.0/5   /dev/sda5  volume 807MiB Windows NTFS volume
  /0/1/0.0.0/6   /dev/sda6  volume 97GiB Windows NTFS volume
  /0/1/0.0.0/7   /dev/sda7  volume 89GiB EXT4 volume
  /0/1/0.0.0/8   /dev/sda8  volume 8098MiB Linux swap volume
  /1power  PK03056XL

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

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

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Joseph Salisbury]

Can you give the v4.8-rc1 kernel a try?  It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8

We can perform a kernel bisect, once we know the last good kernel and
first bad one.


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

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

** Tags removed: needs-bisect
** Tags added: perfomring-bisect

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1627709] Re: Ubuntu 16.10(Yakkety Yak) server amd64 and i386 from 21-Sep-2016 installation fails

[Joseph Salisbury]

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

** Also affects: linux (Ubuntu Yakkety)
   Importance: High
   Status: Triaged

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

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

Title:
  Ubuntu 16.10(Yakkety Yak) server amd64 and i386 from 21-Sep-2016
  installation fails

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

Bug description:
  I was trying to install Ubuntu 16.10(Yakkety Yak) server amd64 from 
21-Sep-2016 Ubuntu 16.10(Yakkety Yak).
  Unfortunately the installation failed at software install.

  The following messages appear in the console:

  in-target: The following packages have unmet dependencies:
  in-target: libpython3.5 : Depends: libpython3.5-stdlib (= 3.5.2-4ubuntu2) but 
3.5.2-4ubuntu3 is to be installed
  in-target: Unable to correct problems, you have held broken packages.
  in-target: tasksel: apt-get failed (100)
  main-menu[785]: WARNING **: Configuring 'pkgsel' failed with error code 1
  main-menu[785]: WARNING **: Menu item 'pkgsel' failed.

  Note: This case also applies to Ubuntu 16.10 server i386 from 21-Sep-2016.
  With the images from 24-Sep-2016 amd64 and i386 the installation failed 
because CD-ROM couldn't be mounted.

  Thanks,
  Ovidiu.

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

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

[Kernel-packages] [Bug 1604396] Re: Kernel 4.4.0-31 cd into NFS4 directory: Operation not permitted

[Joseph Salisbury]

That is good news.  The Ubuntu Xenial kernel will get the fix for this
bug, through the normal stable update process.

Xenial already has the 4.4.21 updates in the -proposed repository.  Can
you give that kernel a try to see if the fix is in a later kernel, such
as .22 or .23?

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

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

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

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

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

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

Title:
  Kernel 4.4.0-31 cd into NFS4 directory: Operation not permitted

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

Bug description:
  Since apt-upgrading my Ubuntu 16.04 PC to kernel 4.4.0-31 I can't cd
  into NFS4 subvolumes any more:

  zierke@rzpc100$ uname -a
  Linux rzpc100 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  zierke@rzpc100$ kinit
  Password for zie...@informatik.uni-hamburg.de:
  zierke@rzpc100$ cd /informatik2
  zierke@rzpc100$ cd rz
  -bash: cd: /informatik2/rz: Operation not permitted

  When I reboot my PC with the previous kernel 4.4.0-28 this works fine.

  This problem has also been mentioned in
  
https://www.kubuntuforums.net/showthread.php?70499-Latest-16-04-bug-NFS-problem-no-access-unless-I-use-root-first-strange
  https://ubuntuforums.org/showthread.php?t=2331137

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

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

[Kernel-packages] [Bug 1561474] Re: Bluetooth will be disable after resume from suspend on Xenial

[Joseph Salisbury]

** Tags removed: kernel-da-key

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

Title:
  Bluetooth will be disable after resume from suspend on Xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201208-11536 Dell Latitude 6430u

  The Bluetooth will be disabled after resume from suspend.
  You will need to use "hciconfig hci0 reset" to enable it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1202 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 24 19:14:07 2016
  HibernationDevice: RESUME=UUID=25c03762-079c-4c6d-aedb-ec768318a6bf
  InstallationDate: Installed on 2016-03-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: Dell Inc. Latitude 6430U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=18cfda3e-4f3d-40cf-8e7e-a83030819487 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.asset.tag: 1234567
  dmi.board.name: 0MN74V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.asset.tag: 1234567
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd11/15/2012:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0MN74V:rvrX01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 6430U
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled

[Ben]

It has been almost 6 month since the bug is discovered, isn't it
resolved by now?

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21 when secure boot
  enabled

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - bcmwl loads normally and wifi works.

  If secure boot disabled - bcmwl loads normally with kernel 4.4.0-21
  and wifi works.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1630238] AlsaInfo.txt

[Timo Jyrinki]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1630238/+attachment/4754271/+files/AlsaInfo.txt

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1630238] [NEW] [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11

[Timo Jyrinki]

Public bug reported:

16.10 beta 2, as installed fresh, has working keyboard and touchscreen
on my Acer Chromebook R11. However, after dist-upgrade they're lost, so
touchscreen doesn't work and I need to use external keyboard.

Looking at config diff, the likely culprit is:
+CONFIG_PINCTRL_AMD=y
 CONFIG_PINCTRL_BAYTRAIL=y
-CONFIG_PINCTRL_CHERRYVIEW=y
-CONFIG_PINCTRL_INTEL=y
-CONFIG_PINCTRL_BROXTON=y
-CONFIG_PINCTRL_SUNRISEPOINT=y
+CONFIG_PINCTRL_CHERRYVIEW=m
+CONFIG_PINCTRL_INTEL=m
+CONFIG_PINCTRL_BROXTON=m
+CONFIG_PINCTRL_SUNRISEPOINT=m

As indicated at https://github.com/GalliumOS/galliumos-
distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to m 
instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
--- 
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  timo   1922 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2016-10-04 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: GOOGLE Cyan
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-generic N/A
 linux-backports-modules-4.8.0-17-generic  N/A
 linux-firmware1.161
Tags:  yakkety
Uname: Linux 4.8.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/21/2016
dmi.bios.vendor: coreboot
dmi.chassis.type: 3
dmi.chassis.vendor: GOOGLE
dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
dmi.product.name: Cyan
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE

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


** Tags: apport-collected yakkety

** Tags added: apport-collected yakkety

** Description changed:

  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost, so
  touchscreen doesn't work and I need to use external keyboard.
  
  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m
  
  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".
  
- So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW
- one) to m instead of y causes at least the touchscreen regression, and
- probably the keyboard one too.
+ So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
+ --- 
+ ApportVersion: 2.20.3-0ubuntu7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  timo   1922 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.10
+ InstallationDate: Installed on 2016-10-04 (0 days ago)
+ InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
+  Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: GOOGLE Cyan
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
+ RelatedPackageVersions:
+  linux-restricted-modules-4.8.0-17-generic N/A
+  linux-backports-modules-4.8.0-17-generic  N/A
+  linux-firmware1.161
+ Tags:  yakkety
+ Uname: Linux 4.8.0-17-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ Us

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

[Timo Jyrinki]

apport information

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[Timo Jyrinki]

apport information

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[Timo Jyrinki]

apport information

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[Timo Jyrinki]

apport information

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[Timo Jyrinki]

apport information

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[Timo Jyrinki]

apport information

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[Timo Jyrinki]

apport information

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[Timo Jyrinki]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1630238/+attachment/4754282/+files/RfKill.txt

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1630238] ProcEnviron.txt

[Timo Jyrinki]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1630238/+attachment/4754278/+files/ProcEnviron.txt

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[Timo Jyrinki]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1630238/+attachment/4754284/+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/1630238

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1630238] IwConfig.txt

[Timo Jyrinki]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1630238/+attachment/4754274/+files/IwConfig.txt

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[Timo Jyrinki]

apport information

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1630238] PulseList.txt

[Timo Jyrinki]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1630238/+attachment/4754281/+files/PulseList.txt

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1627274] Re: kernek 4.4.0-39-generic crash my xps 13 dev.ed I had to return to the 38

[Joseph Salisbury]

You really don't need to install the -headers package.  Just the linux-image 
package:
linux-image-4.4.23-040423-generic_4.4.23-040423.201609300709_amd64.deb

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

Title:
  kernek 4.4.0-39-generic crash my xps 13 dev.ed I had to return to the
  38

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

Bug description:
  Hi there, the system does not boot and goes into initransf black screen
  I am not an experienced user and I just deleted the 4.4.0-39-generic and use 
the 4.4.0-38-generic that seem to work very good apart two small issues.
  The touch screen does not work after a sleep  and to make it to work I have 
to close the lid and open the lid again and it work!
  The sound jack does not give output
  Kind Regard
  Jacopo

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

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

[Kernel-packages] [Bug 1553503] Re: multi monitors - black flashes or black screen when the mouse cursor leaves a monitor

[Joseph Salisbury]

** Tags removed: kernel-da-key

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

Title:
  multi monitors - black flashes or black screen when the mouse cursor
  leaves a monitor

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  When the mouse cursor leaves one of the screens, there is either :
  - no problem
  - the screen becomes black just below the position of the cursor and 
instantly comes back to normal.
  - the screen becomes entirely black with some random colored pixels 
flickering on the far left of the screen. I have to move the cursor to the 
black screen, otherwise it stays black.

  It happens on Ubuntu Gnome 16.04 Beta and Ubuntu Mate 16.04 Beta.
  I have tested with other distributions (Debian Jessie and Fedora) and 
everything is fine.

  Hardware : Intel Ironlake (Thinkpad X201) with an external monitor
  plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Mar  5 13:17:15 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  MachineType: LENOVO 3680KD3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3680KD3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3680KD3:pvrThinkPadX201:rvnLENOVO:rn3680KD3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3680KD3
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Sat Mar  5 13:03:55 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id2202 
   vendor BOE
  xserver.version: 2:1.17.3-2ubuntu4

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

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

[Kernel-packages] [Bug 1627114] Re: WiFi is not detected for Intel Dual BandWireless-AC 3168

[Joseph Salisbury]

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

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

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

Title:
  WiFi is not detected for Intel Dual BandWireless-AC 3168

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have HP Pavilion 15 AU113TX laptop, which comes with Intel Core i5
  7200U Kaby Lake processor and uses Intel Dual BandWireless-AC 3168
  WiFi + Bluetooth Combo adapter, I have installed Ubuntu GNOME 16.04.1
  on it, and it is unable to detect WiFi adapter.

  Upon running "lspci -nnk | grep -A2", I'm getting following
  information about adapter.

  028005:00.0 Network controller [0280]: Intel Corporation Device [8086:24fb] 
(rev 10)
  DeviceName: Intel Dual BandWireless-AC 3168 802.11 ac 1x1 WiFi + BT 
4.0 Combo Adapter
  Subsystem: Intel Corporation Device [8086:2110]

  But running "rfkill list all", I see following output (WiFi missing
  there).

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

  And here's the output for "dmesg | grep iwl"

  [   13.570633] iwlwifi :05:00.0: Unsupported splx structure
  [   13.635662] iwlwifi :05:00.0: Direct firmware load for 
iwlwifi-3168-21.ucode failed with error -2
  [   13.650761] iwlwifi :05:00.0: Direct firmware load for 
iwlwifi-3168-20.ucode failed with error -2
  [   13.650765] iwlwifi :05:00.0: no suitable firmware found!

  Output for "ls -al /lib/firmware | grep 3168" Under both Stock Kernel
  4.4.0-36.

  -rw-r--r--  1 root root   33168 Jul 13 01:03 hfi1_pcie.fw
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Pantheon
  DistroRelease: elementary 0.4
  InstallationDate: Installed on 2016-09-21 (2 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160909)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c87 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=38aa8628-4aa2-48e4-92bd-6cd3b33b0770 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  loki
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1629482] Re: 4.4.0-38-generic reboots periodically

[Joseph Salisbury]

That is good news.  The Ubuntu Xenial kernel should receive this fix
when it gets the v4.4.23 updates via the normal stable update process.

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

Title:
  4.4.0-38-generic reboots periodically

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading a server to 4.4.0-38-generic, it started to reboot
  every ~45 minutes without any visible reasons. Logs look fine. Just
  reboots. My other computer (a desktop) works fine with the same setup.
  Another difference: the server hosts ZFS raid.

  Unfortunately (fortunately) I had this problem ~2 years ago. That time
  after much debugging it turned out to be a kernel problem. So I loaded
  a previous kernel (4.4.0-36-generic), and it is rock solid again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-36-generic.
  AplayDevices: aplay: device_list:268: no soundcards found...
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: arecord: device_list:268: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
'/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep 30 17:35:35 2016
  HibernationDevice: RESUME=/dev/mapper/croc--vg-swap_1
  InstallationDate: Installed on 2013-11-05 (1060 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic 
root=/dev/mapper/hostname--vg-root ro nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (159 days ago)
  dmi.bios.date: 05/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0216.2007.0502.1916
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP35DP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81073-206
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0216.2007.0502.1916:bd05/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-206:cvn:ct2:cvr:

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

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

[Kernel-packages] [Bug 1630238] Re: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11

[Joseph Salisbury]

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

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

Status in linux package in Ubuntu:
  New

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1622894] Re: sg devices are not being created for SCSI storage controller devices starting from v4.4.0-30

[Joseph Salisbury]

The v4.4.0-30 kernel is still available in the ppa:
https://launchpad.net/ubuntu/xenial/+source/linux

It might be good to test the v4.4.0-29 and v4.4.0-30 kernels.  We can
bisect between the two iv -29 is good and -30 is bad.

To downloaded the kernels, click on the version number from that pages.
On the next page, find the section "Builds".  Click the link for your
build.  On the final page, downloaded and install the linux-image and
linux-image-extra .deb packages.

Thanks!

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

Title:
  sg devices are not being created for SCSI storage controller devices
  starting from v4.4.0-30

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Most storage array expose a store controller device to logical unit 0.
  Following LP #1567602, when this happens and the alua driver is loaded, 
Ubuntu doesn't create the sg device for it, and linux fails to discover the 
disks that are attached to higher logical unit numbers.

  With kernel version 4.4.0-31, we tried a number of things:
  - With a disk mapped to LUN0, everything is working.
  - Without a disk mapped to LUN0, nothing works - linux doesn't see disks 
mapped to higher LUNs, calling rescan_scsi_bus throws a stack trace to syslog: 
https://gist.github.com/grzn/20c05ce3fc96062ec9572fd5b8093b55
  - When turning on SCSI logging to the maximum 
(https://access.redhat.com/articles/337903 - 0xfff), we see that after ALUA 
driver rejected the SCSI controller nothing happens (look for 18:0:0:0 which is 
a controller here 
(https://gist.github.com/grzn/f8b65dd07b2df5f3f72ca8121d8c93ad) vs 19:0:00 
which is a disk here 
(https://gist.github.com/grzn/48da86b7f7390dab2983927862cda949).
  - When removing the scsi_dh_alua driver and then reloading the lpfc driver, 
everything is working as expected when no disk is mapped to LUN0.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 18:00 seq
   crw-rw 1 root audio 116, 33 Sep 12 18:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1b089ce2-057f-44d6-9e53-5ee1b7fb5be9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6738fbd7-7243-4860-949f-717dfd084c43 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.3
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-31-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: 09/17/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

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

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Kernel-packages] [Bug 1627114] Re: WiFi is not detected for Intel Dual BandWireless-AC 3168

[Kushal]

No, this problem exists since the clean install I did for Ubuntu 16.04.1
(I'm using elementary OS Loki stable), WiFi support was missing out-of-
the-box, as I mentioned in the link I provided in my comment #1, upon
searching for Linux support for this Intel Adapter, I found this page
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi which says
that support for Intel® Wireless 3168 (the WiFi+Bluetooth adapter I have
in laptop) was added starting Kernel 4.6.

So chances are that 4.4.x may never support it until either 1) someone
back-ports the firmware to 4.4 or 2) Ubuntu 16.04.2 (with Kernel 4.8)
releases.

I filed this bug to track if someone is back-porting hardware support
from newer kernels. Also to summarize, I did test following:

1) With stock Kernel 4.4, only Bluetooth works, WiFi is undetected.
2) With Kernel 4.6.x from Mainline, Nothing works, both WiFi and Bluetooth 
remain undetected.
3) With Kernel 4.7.x from Mainline, WiFi works but Bluetooth is undetected.
4) With Kernel 4.8 from Mainline, both are working just fine!

Right now, I'm stuck with Kernel 4.8 (stable release) at the cost of
battery life.

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

Title:
  WiFi is not detected for Intel Dual BandWireless-AC 3168

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have HP Pavilion 15 AU113TX laptop, which comes with Intel Core i5
  7200U Kaby Lake processor and uses Intel Dual BandWireless-AC 3168
  WiFi + Bluetooth Combo adapter, I have installed Ubuntu GNOME 16.04.1
  on it, and it is unable to detect WiFi adapter.

  Upon running "lspci -nnk | grep -A2", I'm getting following
  information about adapter.

  028005:00.0 Network controller [0280]: Intel Corporation Device [8086:24fb] 
(rev 10)
  DeviceName: Intel Dual BandWireless-AC 3168 802.11 ac 1x1 WiFi + BT 
4.0 Combo Adapter
  Subsystem: Intel Corporation Device [8086:2110]

  But running "rfkill list all", I see following output (WiFi missing
  there).

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

  And here's the output for "dmesg | grep iwl"

  [   13.570633] iwlwifi :05:00.0: Unsupported splx structure
  [   13.635662] iwlwifi :05:00.0: Direct firmware load for 
iwlwifi-3168-21.ucode failed with error -2
  [   13.650761] iwlwifi :05:00.0: Direct firmware load for 
iwlwifi-3168-20.ucode failed with error -2
  [   13.650765] iwlwifi :05:00.0: no suitable firmware found!

  Output for "ls -al /lib/firmware | grep 3168" Under both Stock Kernel
  4.4.0-36.

  -rw-r--r--  1 root root   33168 Jul 13 01:03 hfi1_pcie.fw
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Pantheon
  DistroRelease: elementary 0.4
  InstallationDate: Installed on 2016-09-21 (2 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160909)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c87 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=38aa8628-4aa2-48e4-92bd-6cd3b33b0770 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  loki
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1613750] Re: [Ubuntu 16.10] powerpc/devtree: Add support for 2 new DRC properties

[bugproxy]

** Tags removed: targetmilestone-inin1610
** Tags added: targetmilestone-inin1704

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

Title:
  [Ubuntu 16.10] powerpc/devtree: Add support for 2 new DRC properties

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

Bug description:
  powerpc/devtree: Add support for 2 new DRC properties to the Ubuntu
  distribution for powerpc

  Several properties in the DRC device tree format are replaced by
  more compact representations to allow, for example, for the encoding
  of vast amounts of memory, and or reduced duplication of information
  in related data structures.

  "ibm,drc-info": This property, when present, replaces the following
  four properties: "ibm,drc-indexes", "ibm,drc-names", "ibm,drc-types"
  and "ibm,drc-power-domains".  This property is defined for all
  dynamically reconfigurable platform nodes.  The "ibm,drc-info" elements
  are intended to provide a more compact representation, and reduce some
  search overhead.

  "ibm,dynamic-memory-v2": This property replaces the "ibm,dynamic-memory"
  node representation within the "ibm,dynamic-reconfiguration-memory"
  property provided by the BMC.  This element format is intended to provide
  a more compact representation of memory, especially, for systems with
  massive amounts of RAM.  To simplify portability, this property is
  converted to the "ibm,dynamic-memory" property during system boot.

  "ibm,architecture.vec": Bit flags are added to this data structure
  by the front end processor to inform the kernel as to whether to expect
  the changes to one or both of the device tree structures "ibm,drc-info"
  and "ibm,dynamic-memory-v2".

  Signed-off-by: Michael Bringmann 
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-July/146536.html

  Michael Bringmann (8):
powerpc/firmware: Add definitions for new firmware features.
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-July/146537.html
powerpc/memory: Parse new memory property to register blocks.
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-July/146538.html
powerpc/memory: Parse new memory property to initialize structures.
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-July/146539.html
pseries/hotplug init: Convert new DRC memory property for hotplug runtime
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-July/146540.html
pseries/drc-info: Search new DRC properties for CPU indexes
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-July/146541.html
hotplug/drc-info: Add code to search new devtree properties
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-July/146542.html
powerpc: Check arch.vec earlier during boot for memory features
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-July/146543.html
powerpc: Enable support for new DRC devtree properties
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-July/146544.html

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

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

[Kernel-packages] [Bug 1630238] Re: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11

[Joseph Salisbury]

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

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

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

Title:
  [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on
  Acer Chromebook R11

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

Bug description:
  16.10 beta 2, as installed fresh, has working keyboard and touchscreen
  on my Acer Chromebook R11. However, after dist-upgrade they're lost,
  so touchscreen doesn't work and I need to use external keyboard.

  Looking at config diff, the likely culprit is:
  +CONFIG_PINCTRL_AMD=y
   CONFIG_PINCTRL_BAYTRAIL=y
  -CONFIG_PINCTRL_CHERRYVIEW=y
  -CONFIG_PINCTRL_INTEL=y
  -CONFIG_PINCTRL_BROXTON=y
  -CONFIG_PINCTRL_SUNRISEPOINT=y
  +CONFIG_PINCTRL_CHERRYVIEW=m
  +CONFIG_PINCTRL_INTEL=m
  +CONFIG_PINCTRL_BROXTON=m
  +CONFIG_PINCTRL_SUNRISEPOINT=m

  As indicated at https://github.com/GalliumOS/galliumos-
  distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add
  CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to
  CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.".

  So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to 
m instead of y causes at least the touchscreen regression, and probably the 
keyboard one too.
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timo   1922 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

[bugproxy]

--- Comment From bren...@br.ibm.com 2016-10-04 09:39 EDT---
Tim,

> Watch for Ubuntu-4.8.0-19.21 which should get promoted to proposed by
Monday.

I do not see kernel .21, but 4.8.0.19.28. I suppose it contains the fix
already, right?

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

Title:
  vNIC driver missing in 4.8 kernel package

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

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-09-22 01:20:10 ==
  ---Problem Description---
  There is on "ibmvnic" in 4.8.0-14-generic package:

  root@roselp2:~# uname -a
  Linux roselp2 4.8.0-14-generic #15-Ubuntu SMP Tue Sep 20 21:59:33 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@roselp2:~# modprobe ibmvnic
  modprobe: FATAL: Module ibmvnic not found in directory 
/lib/modules/4.8.0-14-generic
  root@roselp2:~# 

  so the vNIC device which  works well under 4.4 kernel doens't work
  now.

  == Comment: #6 - Kevin W. Rudd - 2016-09-27 11:49:32 ==
  From Bug 146781, this is still an issue with 4.8.0-17:

  ---
  Have installed lpar  using virtual  Ether adapter and after installation am 
not able to find vnic adapters 

  root@miglp2:~# modprobe ibmvnic
  modprobe: FATAL: Module ibmvnic not found in directory 
/lib/modules/4.8.0-17-generic
  root@miglp2:~#

  root@miglp2:~# ifconfig -a
  ibmveth2: flags=4163  mtu 1500
  inet 10.33.15.21  netmask 255.255.0.0  broadcast 10.33.255.255
  inet6 fe80::140f:bbff:fe6b:9502  prefixlen 64  scopeid 0x20
  inet6 2002:903:15f:1130:140f:bbff:fe6b:9502  prefixlen 64  scopeid 
0x0
  inet6 2002:926:3e2:1130:140f:bbff:fe6b:9502  prefixlen 64  scopeid 
0x0
  ether 16:0f:bb:6b:95:02  txqueuelen 1000  (Ethernet)
  RX packets 437923  bytes 29797431 (29.7 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 153  bytes 13014 (13.0 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 19

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1  (Local Loopback)
  RX packets 326  bytes 24184 (24.1 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 326  bytes 24184 (24.1 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  ---

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

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

[Kernel-packages] [Bug 1606178] Re: Can't suspend to ram, since linux3.11 and more

[xzu]

I'm just a musician, not computer scientist.
All that seem quite "advanced".
Can you tell me what you're waiting for with your words.
English is not my own language, maybe reading you will help me to understand 
what is needed to do.
Anyway, any help welcome.

"After the offending commit (not kernel version) has been identified" =>
I don't get the sense of that. What do "offending commit" means?

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

Title:
  Can't suspend to ram, since linux3.11 and more

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't suspend to ram since linux 3.11, with ubuntu12.04. Older version 
(3.8, 3.5 etc..) suspend perfectly.
  So, I can't suspend with ubuntu 14.04 and 16.04. :(
  Solutions from here (specially test newer kernels) don't work for me: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302
  ASRock N68C-S UCC, with phenomIIx4 processor.

  ~$ uname -a
  Linux DDX-STUDIO 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux


  ~$ sudo dmidecode -t baseboard
  # dmidecode 2.11
  SMBIOS 2.4 present.

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
Manufacturer: ASRock
Product Name: N68C-S UCC
Version:   
Serial Number:   
Asset Tag:   
Features:
Board is a hosting board
Board is replaceable
Location In Chassis:   
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Mon Jul 25 12:00:17 2016
  HibernationDevice: RESUME=UUID=3d14e312-ebd4-4129-9183-dcb17519893d
  IwConfig:
   lono wireless extensions.
   
   enp0s7no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0810:0001 Personal Communication Systems, Inc. Dual 
PSX Adaptor
   Bus 002 Device 003: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
   Bus 002 Device 002: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=7411581c-dc6e-4be3-85ba-bf5ae0c61bbc ro splash quiet vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68C-S UCC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user

[Robert Euhus]

Hi Joseph,

yes, the problem started directly after the recent upgrade to linux-
image-4.4.0-38-generic. I have never encountered this bug before, I know
for certain that 4.4.0-36 works fine (as I have said before). Versions
4.4.0-34 and 4.4.0-22 are also without a problem.

The mainline kernel shows the same problem; I have tried: 
linux-image-4.8.0-040800-generic_4.8.0-040800.201610022031_amd64.deb
v4.8 (c8d2bc9bc39ebea8437fd974fdbc21847bb897a3)

To me it looks like this bug was introduced between 4.4.0-36 and
4.4.0-38. I will try bisecting these versions following the instructions
in the Wiki.

Regards,
Robert

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

Title:
  regression: with linux-image-4.4.0-38-generic autofs tries to acess
  folders as root instead of the user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running with linux-image-4.4.0-38-generic autofs is not working
  properly anymore: when I try to access a autofs-monitored folder as
  normal user "joe" the environment variable $AUTOFS_USER inside the
  auto mounter map script is set to "root" instead of the user "joe".

  A little background information: in our setup the autofs master map
  /etc/auto.master contains a line:

  /mnt/cifs   /etc/auto.cifs-shares --timeout=300 --verbose

  The script /etc/auto.cifs-shares contains for debugging purposes the
  lines:

  DEBUG=true
  $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':"
  $DEBUG && logger -p debug -- "$(env|grep AUTOFS)"

  and

  if test "$1" = "$AUTOFS_USER" ; then
  ## First generate automount map
  [..]
  else
  logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access 
wrong directory '$1'"
  fi

  
  Which yields to the following errors in the logs:

  Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3
   AUTOFS_HOME=/root
   AUTOFS_GID=0
   AUTOFS_UID=0
   AUTOFS_GROUP=root
   AUTOFS_USER=root
  Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 
'root' tried to access wrong directory 'joe'
  Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe 
failed
  Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe

  
  So for some reason autofs with this kernel gets the environment variables 
wrong.
  Running an older Kernel like linux-image-4.4.0-36-generic does not show this 
problem and the cifs shares work as expected.

  other Info:
  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  uname -r
  4.4.0-38-generic

  If you need any further info or testing, please let me know.

  Thanks,
  Robert Euhus

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  euhus  1711 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 30 09:36:31 2016
  HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 5040
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.7
  dmi.board.name: 0R790T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 5040
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1629730] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 1

[Brad Figg]

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-19.21/s2lp6g002__4.8.0-19.21__2016-10-04_14-19-00/results-index.html

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

Title:
  linux: 4.8.0-20.22 -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:
  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 Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-20.22 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/1629730/+subscriptions

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

[Kernel-packages] [Bug 1620422] Re: Macbook Pro Retina 12, 1 SD Card Reader Doesn't Work

[graingert]

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

Hey, I'm currently using 4.8 as released in 16.10

Linux kvell 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 05:29:05 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux

This still doesn't support the SD card slot.

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

Title:
   Macbook Pro Retina 12,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SD card reader doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graingert   2672 F pulseaudio
   /dev/snd/controlC1:  graingert   2672 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep  6 00:39:03 2016
  InstallationDate: Installed on 2016-01-05 (244 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=665d68d7-0c44-48e6-9e4c-9496a5c21d21 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9136-generic N/A
   linux-backports-modules-4.4.0-9136-generic  N/A
   linux-firmware  1.160
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-09-05 (0 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1531653] Re: Macbook Pro Retina 11, 1 SD Card Reader Doesn't Work

[graingert]

@penalvch doesn't work on 4.8.0-17-generic

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

Title:
  Macbook Pro Retina 11,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown

Bug description:
  I have a Macbook Pro (MBP) Retina 11,1 with an SD card reader that
  will not work.

  The SD card reader:

  * has device code 05ac:8406
  * does work in OS X.
  * does not work in SystemRescueCD running kernel 3.14.56-std461-amd64
  - I have a friend with an identical Macbook Pro and his SD card reader 
does work in SystemRescueCD
  * Does not show up in lsusb
  * Does not display any messages in dmesg when an SD card is inserted
  * Device 05ac:8406 does not show up in dmesg
  * Does not work in kernel 4.2.0-22.27~14.04.1.  All issues reported here seem 
to be the same regardless if I use 3.13 or 4.2.
  * Uses the following drivers on my friends MBP: sd, usb-storage, usb, xhci_hcd

  The last point made me look closer at the xhci_hcd logs:

  rsyring@loftex:~$ dmesg | grep xhci_hcd
  [2.681478] xhci_hcd :00:14.0: xHCI Host Controller
  [2.681498] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 1
  [2.681589] xhci_hcd :00:14.0: cache line size of 256 is not supported
  [2.681607] xhci_hcd :00:14.0: irq 63 for MSI/MSI-X
  [2.681755] usb usb1: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [2.682098] xhci_hcd :00:14.0: xHCI Host Controller
  [2.682115] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 2
  [2.682219] usb usb2: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [3.980423] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
  [9.352422] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   14.560476] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   20.549170] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   25.757227] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   26.129482] usb 1-1: new high-speed USB device number 2 using xhci_hcd
  [   26.321707] usb 1-3: new full-speed USB device number 3 using xhci_hcd
  [   26.505802] usb 1-5: new full-speed USB device number 4 using xhci_hcd
  [   26.603224] usb 2-1.1: new SuperSpeed USB device number 6 using xhci_hcd
  [   26.754245] usb 1-1.2: new low-speed USB device number 5 using xhci_hcd
  [   26.954315] usb 1-1.4: new low-speed USB device number 6 using xhci_hcd
  [   27.050323] usb 1-3.1: new full-speed USB device number 7 using xhci_hcd
  [   27.142383] usb 1-3.2: new full-speed USB device number 8 using xhci_hcd
  [   27.234476] usb 1-3.3: new full-speed USB device number 9 using xhci_hcd
  [   81.685139] usb 1-1.4: new low-speed USB device number 10 using xhci_hcd

  The "Timeout while waiting" messages are suspicious to me.  dmesg on
  my friend's MBP  does not show those messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-57-generic 3.13.0-57.95
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rsyring5051 F pulseaudio
   /dev/snd/controlC0:  rsyring5051 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Jan  6 17:57:28 2016
  HibernationDevice: RESUME=UUID=8b8a41c8-2030-4f92-b7d6-1143a081ec85
  InstallationDate: Installed on 2014-02-15 (690 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \vmlinuz-3.13.0-57-generic.efi.signed root=ZFS=/ROOT ro 
libata.force=noncq 
cryptopts=target=cryptdev,source=/dev/disk/by-uuid/6993c5ec-7308-420d-bbe2-1ed18c15e2bc,discard
 boot=zfs initrd=\initrd.img-3.13.0-57-generic
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-57-generic N/A
   linux-backports-modules-3.13.0-57-generic  N/A
   linux-firmware 1.127.19
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-21 (534 days ago)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B16.1509081438
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B16.1509081438:bd09/08/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5F

[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user

[Robert Euhus]

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  regression: with linux-image-4.4.0-38-generic autofs tries to acess
  folders as root instead of the user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running with linux-image-4.4.0-38-generic autofs is not working
  properly anymore: when I try to access a autofs-monitored folder as
  normal user "joe" the environment variable $AUTOFS_USER inside the
  auto mounter map script is set to "root" instead of the user "joe".

  A little background information: in our setup the autofs master map
  /etc/auto.master contains a line:

  /mnt/cifs   /etc/auto.cifs-shares --timeout=300 --verbose

  The script /etc/auto.cifs-shares contains for debugging purposes the
  lines:

  DEBUG=true
  $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':"
  $DEBUG && logger -p debug -- "$(env|grep AUTOFS)"

  and

  if test "$1" = "$AUTOFS_USER" ; then
  ## First generate automount map
  [..]
  else
  logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access 
wrong directory '$1'"
  fi

  
  Which yields to the following errors in the logs:

  Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3
   AUTOFS_HOME=/root
   AUTOFS_GID=0
   AUTOFS_UID=0
   AUTOFS_GROUP=root
   AUTOFS_USER=root
  Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 
'root' tried to access wrong directory 'joe'
  Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe 
failed
  Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe

  
  So for some reason autofs with this kernel gets the environment variables 
wrong.
  Running an older Kernel like linux-image-4.4.0-36-generic does not show this 
problem and the cifs shares work as expected.

  other Info:
  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  uname -r
  4.4.0-38-generic

  If you need any further info or testing, please let me know.

  Thanks,
  Robert Euhus

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  euhus  1711 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 30 09:36:31 2016
  HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 5040
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.7
  dmi.board.name: 0R790T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 5040
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1627709] Re: Ubuntu 16.10(Yakkety Yak) server amd64 and i386 from 21-Sep-2016 installation fails

[Tim Gardner]

This was never a kernel problem.

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

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

Title:
  Ubuntu 16.10(Yakkety Yak) server amd64 and i386 from 21-Sep-2016
  installation fails

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

Bug description:
  I was trying to install Ubuntu 16.10(Yakkety Yak) server amd64 from 
21-Sep-2016 Ubuntu 16.10(Yakkety Yak).
  Unfortunately the installation failed at software install.

  The following messages appear in the console:

  in-target: The following packages have unmet dependencies:
  in-target: libpython3.5 : Depends: libpython3.5-stdlib (= 3.5.2-4ubuntu2) but 
3.5.2-4ubuntu3 is to be installed
  in-target: Unable to correct problems, you have held broken packages.
  in-target: tasksel: apt-get failed (100)
  main-menu[785]: WARNING **: Configuring 'pkgsel' failed with error code 1
  main-menu[785]: WARNING **: Menu item 'pkgsel' failed.

  Note: This case also applies to Ubuntu 16.10 server i386 from 21-Sep-2016.
  With the images from 24-Sep-2016 amd64 and i386 the installation failed 
because CD-ROM couldn't be mounted.

  Thanks,
  Ovidiu.

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

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

[Kernel-packages] [Bug 1587674] Re: [HP Pavilion dm1-3205au Entertainment Notebook PC] Wifi cannot connect to router on Ubuntu 16.04 LTS - Ralink RT5390

[Julio Palazón]

I have a HP pavilion g6-2016ss notebook with Ralink rt5390R. Same issue.
Wifi slow downs and dropping connection with default configuration based
on NetworkManager. The correct driver up and running and default kernel.
I have deleted NetworkManager stuff and installed wicd. Working fine, no
slow downs nor dropping connection. It seems to be NetworkManager
related issue.

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

Title:
  [HP Pavilion dm1-3205au Entertainment Notebook PC] Wifi cannot connect
  to router on Ubuntu 16.04 LTS - Ralink RT5390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have researched all possible solutions. The correct driver rt2800pci
  is installed correctly out of the box. No hardware faults. Wifi works
  on Ubuntu 14.04 and Windows 10. Confirmed also driver is not blocked
  and hardware is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  johnnel1436 F pulseaudio
   /dev/snd/controlC0:  johnnel1436 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue May 31 18:35:18 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f7d6820f-3da5-44be-9899-a3286c944329
  InstallationDate: Installed on 2016-05-20 (11 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1611
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.3A
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd07/07/2011:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr058911252B0310100:rvnHewlett-Packard:rn1611:rvr96.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm1 Notebook PC
  dmi.product.version: 058911252B0310100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1620422] Re: Macbook Pro Retina 12, 1 SD Card Reader Doesn't Work

[graingert]

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

** This bug has been marked a duplicate of bug 1531653
   Macbook Pro Retina 11,1 SD Card Reader Doesn't Work

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

Title:
   Macbook Pro Retina 12,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SD card reader doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graingert   2672 F pulseaudio
   /dev/snd/controlC1:  graingert   2672 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep  6 00:39:03 2016
  InstallationDate: Installed on 2016-01-05 (244 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=665d68d7-0c44-48e6-9e4c-9496a5c21d21 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9136-generic N/A
   linux-backports-modules-4.4.0-9136-generic  N/A
   linux-firmware  1.160
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-09-05 (0 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1531653] Re: Macbook Pro Retina 11, 1 SD Card Reader Doesn't Work

[graingert]

Related bug reports:

https://github.com/coldnew/macbookpro-2015-config#related-bugs-report
https://bugzilla.redhat.com/show_bug.cgi?id=1290959
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531653

https://www.reddit.com/r/linuxmint/comments/3ydoxs/unable_to_detect_builtin_sd_card_reader/


** Bug watch added: Red Hat Bugzilla #1290959
   https://bugzilla.redhat.com/show_bug.cgi?id=1290959

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

Title:
  Macbook Pro Retina 11,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown

Bug description:
  I have a Macbook Pro (MBP) Retina 11,1 with an SD card reader that
  will not work.

  The SD card reader:

  * has device code 05ac:8406
  * does work in OS X.
  * does not work in SystemRescueCD running kernel 3.14.56-std461-amd64
  - I have a friend with an identical Macbook Pro and his SD card reader 
does work in SystemRescueCD
  * Does not show up in lsusb
  * Does not display any messages in dmesg when an SD card is inserted
  * Device 05ac:8406 does not show up in dmesg
  * Does not work in kernel 4.2.0-22.27~14.04.1.  All issues reported here seem 
to be the same regardless if I use 3.13 or 4.2.
  * Uses the following drivers on my friends MBP: sd, usb-storage, usb, xhci_hcd

  The last point made me look closer at the xhci_hcd logs:

  rsyring@loftex:~$ dmesg | grep xhci_hcd
  [2.681478] xhci_hcd :00:14.0: xHCI Host Controller
  [2.681498] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 1
  [2.681589] xhci_hcd :00:14.0: cache line size of 256 is not supported
  [2.681607] xhci_hcd :00:14.0: irq 63 for MSI/MSI-X
  [2.681755] usb usb1: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [2.682098] xhci_hcd :00:14.0: xHCI Host Controller
  [2.682115] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 2
  [2.682219] usb usb2: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [3.980423] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
  [9.352422] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   14.560476] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   20.549170] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   25.757227] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   26.129482] usb 1-1: new high-speed USB device number 2 using xhci_hcd
  [   26.321707] usb 1-3: new full-speed USB device number 3 using xhci_hcd
  [   26.505802] usb 1-5: new full-speed USB device number 4 using xhci_hcd
  [   26.603224] usb 2-1.1: new SuperSpeed USB device number 6 using xhci_hcd
  [   26.754245] usb 1-1.2: new low-speed USB device number 5 using xhci_hcd
  [   26.954315] usb 1-1.4: new low-speed USB device number 6 using xhci_hcd
  [   27.050323] usb 1-3.1: new full-speed USB device number 7 using xhci_hcd
  [   27.142383] usb 1-3.2: new full-speed USB device number 8 using xhci_hcd
  [   27.234476] usb 1-3.3: new full-speed USB device number 9 using xhci_hcd
  [   81.685139] usb 1-1.4: new low-speed USB device number 10 using xhci_hcd

  The "Timeout while waiting" messages are suspicious to me.  dmesg on
  my friend's MBP  does not show those messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-57-generic 3.13.0-57.95
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rsyring5051 F pulseaudio
   /dev/snd/controlC0:  rsyring5051 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Jan  6 17:57:28 2016
  HibernationDevice: RESUME=UUID=8b8a41c8-2030-4f92-b7d6-1143a081ec85
  InstallationDate: Installed on 2014-02-15 (690 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \vmlinuz-3.13.0-57-generic.efi.signed root=ZFS=/ROOT ro 
libata.force=noncq 
cryptopts=target=cryptdev,source=/dev/disk/by-uuid/6993c5ec-7308-420d-bbe2-1ed18c15e2bc,discard
 boot=zfs initrd=\initrd.img-3.13.0-57-generic
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-57-generic N/A
   linux-backports-modules-3.13.0-57-generic  N/A
   linux-firmware 1.127.19
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-21 (534 days ago)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B16.1509081438
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.ve

[Kernel-packages] [Bug 801034] Re: SD card reader in Macbook does not work

[graingert]

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

** This bug has been marked a duplicate of bug 1531653
   Macbook Pro Retina 11,1 SD Card Reader Doesn't Work

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

Title:
  SD card reader in Macbook does not work

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The SD card reader in my Macbook Pro workes only when an ethernet
  cable is connected. When the cable is not connected, inserting an SD
  card causes the following to be printed in dmesg.

  
  [  245.886482] mmc0: Timeout waiting for hardware interrupt.
  [  245.886494] sdhci: === REGISTER DUMP (mmc0)===
  [  245.886538] sdhci: Sys addr: 0x | Version:  0x1502
  [  245.886550] sdhci: Blk size: 0x | Blk cnt:  0x
  [  245.886561] sdhci: Argument: 0x | Trn mode: 0x
  [  245.886571] sdhci: Present:  0x1eff0001 | Host ctl: 0x0001
  [  245.886583] sdhci: Power:0x000f | Blk gap:  0x
  [  245.886594] sdhci: Wake-up:  0x | Clock:0x4e47
  [  245.886604] sdhci: Timeout:  0x | Int stat: 0x
  [  245.886615] sdhci: Int enab: 0x00ff00c3 | Sig enab: 0x00ff00c3
  [  245.886635] sdhci: AC12 err: 0x | Slot int: 0x
  [  245.886641] sdhci: Caps: 0x176ec8b0 | Caps_1:   0x03002177
  [  245.886646] sdhci: Cmd:  0x0502 | Max curr: 0x
  [  245.886662] sdhci: ADMA Err: 0x | ADMA Ptr: 0x
  [  245.886665] sdhci: ===
  [  249.822867] [drm:intel_crtc_cursor_set],
  [  249.822870] [drm:intel_crtc_cursor_set], cursor off
  [  255.896340] mmc0: Timeout waiting for hardware interrupt.
  [  255.896354] sdhci: === REGISTER DUMP (mmc0)===
  [  255.896396] sdhci: Sys addr: 0x | Version:  0x1502
  [  255.896405] sdhci: Blk size: 0x | Blk cnt:  0x
  [  255.896413] sdhci: Argument: 0x | Trn mode: 0x
  [  255.896421] sdhci: Present:  0x1eff0001 | Host ctl: 0x0001
  [  255.896429] sdhci: Power:0x000f | Blk gap:  0x
  [  255.896437] sdhci: Wake-up:  0x | Clock:0x4e47
  [  255.896445] sdhci: Timeout:  0x | Int stat: 0x
  [  255.896454] sdhci: Int enab: 0x00ff00c3 | Sig enab: 0x00ff00c3
  [  255.896462] sdhci: AC12 err: 0x | Slot int: 0x
  [  255.896472] sdhci: Caps: 0x176ec8b0 | Caps_1:   0x03002177
  [  255.896480] sdhci: Cmd:  0x0502 | Max curr: 0x
  [  255.896488] sdhci: ADMA Err: 0x | ADMA Ptr: 0x
  [  255.896492] sdhci: ===
  [  260.528745] [drm:intel_crtc_cursor_set],
  [  265.906292] mmc0: Timeout waiting for hardware interrupt.
  [  265.906303] sdhci: === REGISTER DUMP (mmc0)===
  [  265.906343] sdhci: Sys addr: 0x | Version:  0x1502
  [  265.906351] sdhci: Blk size: 0x | Blk cnt:  0x
  [  265.906359] sdhci: Argument: 0x | Trn mode: 0x
  [  265.906368] sdhci: Present:  0x1fff0001 | Host ctl: 0x0001
  [  265.906375] sdhci: Power:0x000f | Blk gap:  0x
  [  265.906383] sdhci: Wake-up:  0x | Clock:0x4e47
  [  265.906391] sdhci: Timeout:  0x | Int stat: 0x
  [  265.906399] sdhci: Int enab: 0x00ff00c3 | Sig enab: 0x00ff00c3
  [  265.906407] sdhci: AC12 err: 0x | Slot int: 0x
  [  265.906415] sdhci: Caps: 0x176ec8b0 | Caps_1:   0x03002177
  [  265.906423] sdhci: Cmd:  0x0502 | Max curr: 0x
  [  265.906432] sdhci: ADMA Err: 0x | ADMA Ptr: 0x
  [  265.906435] sdhci: ===
  [  267.956769] [drm:intel_crtc_cursor_set],
  [  267.956778] [drm:intel_crtc_cursor_set], cursor off
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jpakkane   1714 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xa090 irq 47'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:10134206,106b1c00,00100302 
HDA:80862805,80860101,0010'
 Controls  : 34
 Simple ctrls  : 16
  DistroRelease: Ubuntu 11.04
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  MachineType: Apple Inc. MacBookPro8,1
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic 
root=UUID=2ee94f0e-11b3-42a2-a009-1a9b94b11fc9 ro quiet splash drm.debug=0xe 
vt.handoff=7
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2

[Kernel-packages] [Bug 1629730] Re: linux: 4.8.0-20.22 -proposed tracker

[Andy Whitcroft]

** Tags removed: block-proposed

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

Title:
  linux: 4.8.0-20.22 -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:
  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 Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-20.22 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/1629730/+subscriptions

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

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

[bugproxy]

--- Comment From gbert...@br.ibm.com 2016-10-04 10:36 EDT---
(In reply to comment #4)
> This is a bug against 16.04, right?

yes.

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

Title:
  nvme: Missing patch in Ubuntu-4.4.0-41.61

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

Bug description:
  == Comment: #0 - Gabriel Krisman Bertazi  - 2016-09-27 
22:59:44 ==
  Ubuntu-4.4.0-40.60 included my backport of :

  b00a726a9fd ("NVMe: Don't unmap controller registers on reset") #upstream 
commit
[ 30d6592fce71 on the Ubuntu -proposed branch]

  But missed the fix up that came later:

  81e9a969c441 ("nvme: Call pci_disable_device on the error path.") #
  4.4.y tree

  This means that we may hit an Oops if we need to go into the error
  path of  the nvme probe.

  
  Please cherry-pick this fix to your kernel.

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

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

[Kernel-packages] [Bug 1629057] Re: linux: 4.8.0-19.21 -proposed tracker

[Andy Whitcroft]

** Tags removed: block-proposed

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

Title:
  linux: 4.8.0-19.21 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.8.0-19.21 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/1629057/+subscriptions

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

[Kernel-packages] [Bug 1553503] Re: multi monitors - black flashes or black screen when the mouse cursor leaves a monitor

[Thomas Mayer]

The 4.4.0-38, which got released via regular updates mitigated all the
flickering for me. It's all fine now. Thanks for the patch.

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

Title:
  multi monitors - black flashes or black screen when the mouse cursor
  leaves a monitor

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  When the mouse cursor leaves one of the screens, there is either :
  - no problem
  - the screen becomes black just below the position of the cursor and 
instantly comes back to normal.
  - the screen becomes entirely black with some random colored pixels 
flickering on the far left of the screen. I have to move the cursor to the 
black screen, otherwise it stays black.

  It happens on Ubuntu Gnome 16.04 Beta and Ubuntu Mate 16.04 Beta.
  I have tested with other distributions (Debian Jessie and Fedora) and 
everything is fine.

  Hardware : Intel Ironlake (Thinkpad X201) with an external monitor
  plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Mar  5 13:17:15 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  MachineType: LENOVO 3680KD3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3680KD3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3680KD3:pvrThinkPadX201:rvnLENOVO:rn3680KD3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3680KD3
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Sat Mar  5 13:03:55 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id2202 
   vendor BOE
  xserver.version: 2:1.17.3-2ubuntu4

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

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

[Kernel-packages] [Bug 1563229] Re: Touchpad recognised as mouse FTE1000

[Onur Ozan Yüksel]

I have TP200SA and have the same problem. Additionally touch screen is
functional but can't scroll, only clicks.

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

Title:
  Touchpad recognised as mouse FTE1000

Status in linux package in Ubuntu:
  Triaged
Status in xinput package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Triaged
Status in xinput source package in Trusty:
  Confirmed
Status in linux source package in Wily:
  Triaged
Status in xinput source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Triaged
Status in xinput source package in Xenial:
  Confirmed

Bug description:
  In my Asus e200ha touchpad is recognized as mouse, only one click, no
  two finger click and scrolling

  Xinput say:
  FTE1000:00 0B05:0101   id=12[slave pointer (2)]

  i've tried:
  - ubuntu 14.04 with stock kernel
  - ubuntu 14.04 with 4.6rc1 kernel
  - Linux mint 17.3 with stock kernel
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: xinput 1.6.1-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1531653] Re: Macbook Pro Retina 11, 1 SD Card Reader Doesn't Work

[graingert]

the SD card is USB 2-3:

[   18.656434] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
[   23.529455] random: fast init done
[   24.032360] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
[   24.240351] usb 2-3: device not accepting address 3, error -62

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

Title:
  Macbook Pro Retina 11,1 SD Card Reader Doesn't Work

Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown

Bug description:
  I have a Macbook Pro (MBP) Retina 11,1 with an SD card reader that
  will not work.

  The SD card reader:

  * has device code 05ac:8406
  * does work in OS X.
  * does not work in SystemRescueCD running kernel 3.14.56-std461-amd64
  - I have a friend with an identical Macbook Pro and his SD card reader 
does work in SystemRescueCD
  * Does not show up in lsusb
  * Does not display any messages in dmesg when an SD card is inserted
  * Device 05ac:8406 does not show up in dmesg
  * Does not work in kernel 4.2.0-22.27~14.04.1.  All issues reported here seem 
to be the same regardless if I use 3.13 or 4.2.
  * Uses the following drivers on my friends MBP: sd, usb-storage, usb, xhci_hcd

  The last point made me look closer at the xhci_hcd logs:

  rsyring@loftex:~$ dmesg | grep xhci_hcd
  [2.681478] xhci_hcd :00:14.0: xHCI Host Controller
  [2.681498] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 1
  [2.681589] xhci_hcd :00:14.0: cache line size of 256 is not supported
  [2.681607] xhci_hcd :00:14.0: irq 63 for MSI/MSI-X
  [2.681755] usb usb1: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [2.682098] xhci_hcd :00:14.0: xHCI Host Controller
  [2.682115] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 2
  [2.682219] usb usb2: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
  [3.980423] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
  [9.352422] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   14.560476] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   20.549170] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   25.757227] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [   26.129482] usb 1-1: new high-speed USB device number 2 using xhci_hcd
  [   26.321707] usb 1-3: new full-speed USB device number 3 using xhci_hcd
  [   26.505802] usb 1-5: new full-speed USB device number 4 using xhci_hcd
  [   26.603224] usb 2-1.1: new SuperSpeed USB device number 6 using xhci_hcd
  [   26.754245] usb 1-1.2: new low-speed USB device number 5 using xhci_hcd
  [   26.954315] usb 1-1.4: new low-speed USB device number 6 using xhci_hcd
  [   27.050323] usb 1-3.1: new full-speed USB device number 7 using xhci_hcd
  [   27.142383] usb 1-3.2: new full-speed USB device number 8 using xhci_hcd
  [   27.234476] usb 1-3.3: new full-speed USB device number 9 using xhci_hcd
  [   81.685139] usb 1-1.4: new low-speed USB device number 10 using xhci_hcd

  The "Timeout while waiting" messages are suspicious to me.  dmesg on
  my friend's MBP  does not show those messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-57-generic 3.13.0-57.95
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rsyring5051 F pulseaudio
   /dev/snd/controlC0:  rsyring5051 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Jan  6 17:57:28 2016
  HibernationDevice: RESUME=UUID=8b8a41c8-2030-4f92-b7d6-1143a081ec85
  InstallationDate: Installed on 2014-02-15 (690 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \vmlinuz-3.13.0-57-generic.efi.signed root=ZFS=/ROOT ro 
libata.force=noncq 
cryptopts=target=cryptdev,source=/dev/disk/by-uuid/6993c5ec-7308-420d-bbe2-1ed18c15e2bc,discard
 boot=zfs initrd=\initrd.img-3.13.0-57-generic
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-57-generic N/A
   linux-backports-modules-3.13.0-57-generic  N/A
   linux-firmware 1.127.19
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-21 (534 days ago)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B16.1509081438
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.c

[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

[Eric Desrochers]

** Description changed:

  [Impact]
  
  The zfs utilities scripts shipped with debian and ubuntu such as :
  
  * arc_summary.py : Provides a summary of the statistics
  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  * dbufstat.py : Print out statistics for all cached dmu buffers
  
  should be renamed according to Policy 10.4 :
  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts
  
  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."
  
  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.
  
  [Test Case]
  
   * Install zfsutils-linux
   * List files
  
   $ dpkg -L zfsutils-linux | egrep "arc|dbufstat"
     /usr/sbin/arc_summary.py
     /usr/sbin/arcstat.py
     /usr/sbin/dbufstat.py
  
  [Regression Potential]
  
   * none expected, this is a trivial change that simply rename the
  scripts to remove the extension (.py) with a simple 'mv' before the
  dh_install invocation in order to get this expected result :
  
  $ dpkg -L zfsutils-linux | egrep -i "arc|dbuf"
    /usr/sbin/arc_summary
    /usr/sbin/arcstat
    /usr/sbin/dbufstat
  
+ Yakkety include the renaming as shown above.
+ 
+ Xenial will have a symlink to not break user experience until next release 
upgrade:
+ 
https://bugs.launchpad.net/ubuntu/xenial/+source/zfs-linux/+bug/1628279/comments/19
+ 
+ So user will be able to use both for instance : arcstat.py or arcstat
+ 
+ 
  [Other Info]
  
   * Justification/argument for Xenial
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/13
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/14
  
  * Debian bug
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839645
  
   * Upstream (ZoL) is reluctant to change it at upstream code level.
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/2
  
   * This has been flag by Adam Conrad
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1574342/comments/19
  
   * Debian policy
  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

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

Bug description:
  [Impact]

  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  * dbufstat.py : Print out statistics for all cached dmu buffers

  should be renamed according to Policy 10.4 :
  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

  [Test Case]

   * Install zfsutils-linux
   * List files

   $ dpkg -L zfsutils-linux | egrep "arc|dbufstat"
     /usr/sbin/arc_summary.py
     /usr/sbin/arcstat.py
     /usr/sbin/dbufstat.py

  [Regression Potential]

   * none expected, this is a trivial change that simply rename the
  scripts to remove the extension (.py) with a simple 'mv' before the
  dh_install invocation in order to get this expected result :

  $ dpkg -L zfsutils-linux | egrep -i "arc|dbuf"
    /usr/sbin/arc_summary
    /usr/sbin/arcstat
    /usr/sbin/dbufstat

  Yakkety include the renaming as shown above.

  Xenial will have a symlink to not break user experience until next release 
upgrade:
  
https://bugs.launchpad.net/ubuntu/xenial/+source/zfs-linux/+bug/1628279/comments/19

  So user will be able to use both for instance : arcstat.py or arcstat

  
  [Other Info]

   * Justification/argument for Xenial
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/13
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/14

  * Debian bug
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839645

   * Upstream (ZoL) is reluctant to change it at upstream code level.
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/2

   * This has been flag by Adam Conrad
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1574342/comments/19

   * Debian policy
  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

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

-- 
Mailing list: https://launchpad.

[Kernel-packages] [Bug 1625355] Re: package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 139

[Tyro]

After some days the problem disappeard 'by itself'. I did install
various other programs, and at some pint in time this generic Ubuntu bug
was solved.

Running the commands under #4 (from Joseph) showed that everything was
ok.

Thanks.

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

Title:
  package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub
  exited with return code 139

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upadte, system malfunction.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tyro   1862 F pulseaudio
   /dev/snd/controlC0:  tyro   1862 F pulseaudio
  Date: Mon Sep 19 22:21:17 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=4eef35db-0034-4ffe-926a-d9fe6efb0614
  InstallationDate: Installed on 2016-09-14 (5 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=18a4e446-5c1d-4e9f-a6ed-7c139a310871 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with 
return code 139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF13:bd05/11/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1630245] [NEW] after starting ubuntu 16.10 -- no keyboard, no mouse

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works
with an older kernel but not with the latest one, I'd assume the newer
kernel does not initialize the devices the right way.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9git1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Tue Oct  4 15:27:52 2016
InstallationDate: Installed on 2012-12-12 (1391 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.3)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-bug yakkety
-- 
after starting ubuntu 16.10 -- no keyboard, no mouse
https://bugs.launchpad.net/bugs/1630245
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic

[Brian Elliott Finley]

I am having the laggy bluetooth mouse issue with a Logitech MX Anywhere
2 and a Lenovo T450s.

The modprobe suggestion from @cribari has worked for me so far, but I've
only done 5 minutes of testing at this point, and only one suspend-
resume cycle.

Order of operations:
1) suspend/resume/suspend/resume, etc.
2) turn on bluetooth on notebook (mouse was paired weeks ago) [10:19:31 in log 
below]
3) turn on mouse and experience lag [10:19:36 in log below]
4) execute these commands "sudo modprobe -rv btusb && sleep 1s && sudo modprobe 
-v btusb" [10:22:33 in log below]
5) mouse is no longer laggy
6) suspend/resume (once)
7) mouse is still not laggy, and appears to be working fine


Oct  4 10:19:31 tbob kernel: [588896.204026] Bluetooth: hci0: read Intel 
version: 370810011003110e00
Oct  4 10:19:31 tbob kernel: [588896.205078] Bluetooth: hci0: Intel Bluetooth 
firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
Oct  4 10:19:31 tbob kernel: [588896.521054] Bluetooth: hci0: Intel Bluetooth 
firmware patch completed and activated
Oct  4 10:19:31 tbob systemd[1]: Reached target Bluetooth.
Oct  4 10:19:31 tbob bluetoothd[3094]: Failed to obtain handles for "Service 
Changed" characteristic
Oct  4 10:19:31 tbob bluetoothd[3094]: Not enough free handles to register 
service
Oct  4 10:19:31 tbob bluetoothd[3094]: Error adding Link Loss service
Oct  4 10:19:31 tbob bluetoothd[3094]: Not enough free handles to register 
service
Oct  4 10:19:31 tbob bluetoothd[3094]: message repeated 2 times: [ Not enough 
free handles to register service]
Oct  4 10:19:31 tbob bluetoothd[3094]: Current Time Service could not be 
registered
Oct  4 10:19:31 tbob bluetoothd[3094]: gatt-time-server: Input/output error (5)
Oct  4 10:19:31 tbob bluetoothd[3094]: Not enough free handles to register 
service
Oct  4 10:19:31 tbob bluetoothd[3094]: Not enough free handles to register 
service
Oct  4 10:19:31 tbob bluetoothd[3094]: Sap driver initialization failed.
Oct  4 10:19:31 tbob bluetoothd[3094]: sap-server: Operation not permitted (1)
Oct  4 10:19:31 tbob bluetoothd[3094]: Endpoint registered: sender=:1.72 
path=/MediaEndpoint/A2DPSource
Oct  4 10:19:31 tbob bluetoothd[3094]: Endpoint registered: sender=:1.72 
path=/MediaEndpoint/A2DPSink
Oct  4 10:19:36 tbob bluetoothd[3094]: Unable to register GATT service with 
handle 0x000c for device EA:4C:A8:24:2D:95
Oct  4 10:19:36 tbob bluetoothd[3094]: Unable to register GATT service with 
handle 0x001b for device EA:4C:A8:24:2D:95
Oct  4 10:19:36 tbob bluetoothd[3094]: Unable to register GATT service with 
handle 0x003f for device EA:4C:A8:24:2D:95
Oct  4 10:19:37 tbob bluetoothd[3094]: bt_uhid_send: Invalid argument (22)
Oct  4 10:19:37 tbob kernel: [588902.501689] input: MX Anywhere 2 as 
/devices/virtual/misc/uhid/0005:046D:B013.007C/input/input95
Oct  4 10:19:37 tbob kernel: [588902.502135] hid-generic 0005:046D:B013.007C: 
input,hidraw4: BLUETOOTH HID v0.07 Keyboard [MX Anywhere 2] on 10:02:B5:80:73:A1
Oct  4 10:19:37 tbob bluetoothd[3094]: message repeated 12 times: [ 
bt_uhid_send: Invalid argument (22)]
Oct  4 10:22:33 tbob kernel: [589078.328418] usbcore: deregistering interface 
driver btusb
Oct  4 10:22:33 tbob systemd[1]: bluetooth.target: Unit not needed anymore. 
Stopping.
Oct  4 10:22:33 tbob systemd[1]: Stopped target Bluetooth.
Oct  4 10:22:33 tbob bluetoothd[3094]: Endpoint unregistered: sender=:1.72 
path=/MediaEndpoint/A2DPSource
Oct  4 10:22:33 tbob bluetoothd[3094]: Endpoint unregistered: sender=:1.72 
path=/MediaEndpoint/A2DPSink
Oct  4 10:22:34 tbob kernel: [589079.485951] usbcore: registered new interface 
driver btusb
Oct  4 10:22:34 tbob kernel: [589079.500790] Bluetooth: hci0: read Intel 
version: 370810011003110e23
Oct  4 10:22:34 tbob kernel: [589079.500793] Bluetooth: hci0: Intel device is 
already patched. patch num: 23
Oct  4 10:22:34 tbob bluetoothd[3094]: Failed to obtain handles for "Service 
Changed" characteristic
Oct  4 10:22:34 tbob bluetoothd[3094]: Not enough free handles to register 
service
Oct  4 10:22:34 tbob bluetoothd[3094]: Error adding Link Loss service
Oct  4 10:22:34 tbob bluetoothd[3094]: Not enough free handles to register 
service
Oct  4 10:22:34 tbob bluetoothd[3094]: message repeated 2 times: [ Not enough 
free handles to register service]
Oct  4 10:22:34 tbob bluetoothd[3094]: Current Time Service could not be 
registered
Oct  4 10:22:34 tbob bluetoothd[3094]: gatt-time-server: Input/output error (5)
Oct  4 10:22:34 tbob bluetoothd[3094]: Not enough free handles to register 
service
Oct  4 10:22:34 tbob systemd[1]: Reached target Bluetooth.
Oct  4 10:22:34 tbob bluetoothd[3094]: Not enough free handles to register 
service
Oct  4 10:22:34 tbob bluetoothd[3094]: Sap driver initialization failed.
Oct  4 10:22:34 tbob bluetoothd[3094]: sap-server: Operation not permitted (1)
Oct  4 10:22:34 tbob bluetoothd[3094]: Endpoint registered: sender=:1.72 
path=/MediaEndpoint/A2DPSource
Oct  4 10:22:34 tbob bluetoothd[3094]: Endpoint registered: se

[Kernel-packages] [Bug 1630279] [NEW] linux: 4.8.0-21.23 -proposed tracker

[Tim Gardner]

Public bug reported:

This bug is for tracking the 4.8.0-21.23 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-changed:Tuesday, 04. October 2016 15:16 UTC
kernel-phase:Packaging

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

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-development-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Yakkety)
 Importance: Medium
 Status: Confirmed


** Tags: block-proposed kernel-release-tracking-bug yakkety

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed

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

** Tags added: yakkety

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

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-development-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

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

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Omer Akram]

I tried linux 4.8-rc1 and it does have the said regression.

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

[Martin Pitt]

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

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

Status in linux package in Ubuntu:
  New

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1630279] Re: linux: 4.8.0-21.23 -proposed tracker

[Brad Figg]

** 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.8.0-21.23 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-changed:Tuesday, 04. October 2016 15:16 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the 4.8.0-21.23 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-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging
+ 
+ -- 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/1630279

Title:
  linux: 4.8.0-21.23 -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 Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-21.23 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-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

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

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

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

[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user

[Joseph Salisbury]

Thanks for the update, Robert.  Just let me know if you need assistance
with the bisect, and I can build the kernels for you.

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

Title:
  regression: with linux-image-4.4.0-38-generic autofs tries to acess
  folders as root instead of the user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running with linux-image-4.4.0-38-generic autofs is not working
  properly anymore: when I try to access a autofs-monitored folder as
  normal user "joe" the environment variable $AUTOFS_USER inside the
  auto mounter map script is set to "root" instead of the user "joe".

  A little background information: in our setup the autofs master map
  /etc/auto.master contains a line:

  /mnt/cifs   /etc/auto.cifs-shares --timeout=300 --verbose

  The script /etc/auto.cifs-shares contains for debugging purposes the
  lines:

  DEBUG=true
  $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':"
  $DEBUG && logger -p debug -- "$(env|grep AUTOFS)"

  and

  if test "$1" = "$AUTOFS_USER" ; then
  ## First generate automount map
  [..]
  else
  logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access 
wrong directory '$1'"
  fi

  
  Which yields to the following errors in the logs:

  Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3
   AUTOFS_HOME=/root
   AUTOFS_GID=0
   AUTOFS_UID=0
   AUTOFS_GROUP=root
   AUTOFS_USER=root
  Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 
'root' tried to access wrong directory 'joe'
  Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe 
failed
  Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe

  
  So for some reason autofs with this kernel gets the environment variables 
wrong.
  Running an older Kernel like linux-image-4.4.0-36-generic does not show this 
problem and the cifs shares work as expected.

  other Info:
  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  uname -r
  4.4.0-38-generic

  If you need any further info or testing, please let me know.

  Thanks,
  Robert Euhus

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  euhus  1711 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 30 09:36:31 2016
  HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 5040
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.7
  dmi.board.name: 0R790T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 5040
  dmi.sys.vendor: Dell Inc.

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 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.8

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

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

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1630285] [NEW] mwifiex_pcie crashes after several bind/unbind

[Anthony Wong]

Public bug reported:

# echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind
# echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bin

Keep doing the bind/unbind actions, it would crash very soon.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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


** Tags: originate-from-1623583 plano

** Attachment added: "oops.txt"
   https://bugs.launchpad.net/bugs/1630285/+attachment/4754340/+files/oops.txt

** Tags added: originate-from-1623583 plano

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

Title:
  mwifiex_pcie crashes after several bind/unbind

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bin

  Keep doing the bind/unbind actions, it would crash very soon.

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

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

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

[bugproxy]

--- Comment From bren...@br.ibm.com 2016-10-04 11:37 EDT---
Hello,

> Uploaded fix into yakkety, pending approval in queue.

Was it accepted in yakkety already?

Thank you

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

Title:
  ISST-LTE:pVM:roselp2:ubuntu 16.10: crash failed to check vmcore of 4.8
  kernel

Status in crash package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han  - 2016-09-22 03:05:36 ==
  ---Problem Description---
  crash cannot check vmcore of 4.8 kernel. 

  Then when trying to check the core with crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.8.0-14-generic
  /var/crash/201609212349/vmcore.201609212349

  crash 7.1.5
  Copyright (C) 2002-2016  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering kmem slab cache data)
  crash: invalid kernel virtual address: 7aa9fe0100  type: "pmd page"

   
  ---uname output---
  Linux roselp2 4.8.0-14-generic #15-Ubuntu SMP Tue Sep 20 21:59:33 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8286-42A, lpar 
   
  ---Steps to Reproduce---
   1. install 4.8 kernel
  2. trigger kdump to get vmcore
  3. check the vmcore with crash

  
  == Comment: #8 - Hari Krishna Bathini  - 2016-09-24 14:12:23 ==
  The below commit is needed for vtop address translation to succeed

commit 182914debbb9a2671ef644027fedd339aa9c80e0
Author: Dave Anderson 
Date:   Fri Sep 23 09:09:15 2016 -0400

  With the introduction of radix MMU in Power ISA 3.0, there are
  changes in kernel page table management accommodating it.  This patch
  series makes appropriate changes here to work for such kernels.
  Also, this series fixes a few bugs along the way:
  
ppc64: fix vtop page translation for 4K pages
ppc64: Use kernel terminology for each level in 4-level page table
ppc64/book3s: address changes in kernel v4.5
ppc64/book3s: address change in page flags for PowerISA v3.0
ppc64: use physical addresses and unfold pud for 64K page size
ppc64/book3s: support big endian Linux page tables
  
  The patches are needed for Linux v4.5 and later kernels on all
  ppc64 hardware.
  (hbath...@linux.vnet.ibm.com)
  --

  Also, the below commit is needed

commit 8ceb1ac628bf6a0a7f0bbfff030ec93081bca4cd
Author: Dave Anderson 
Date:   Mon May 23 11:23:01 2016 -0400

  Fix for Linux commit 0139aa7b7fa12ceef095d99dc36606a5b10ab83a, which
  renamed the page._count member to page._refcount.  Without the patch,
  certain "kmem" commands fail with the "kmem: invalid structure member
  offset: page_count".
  (ander...@redhat.com)

  Thanks
  Hari

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

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

[Kernel-packages] [Bug 1553503] Re: multi monitors - black flashes or black screen when the mouse cursor leaves a monitor

[Andrew]

Regular updates loaded today which also cured the flickering for me . .
. ah bliss :-)

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

Title:
  multi monitors - black flashes or black screen when the mouse cursor
  leaves a monitor

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  When the mouse cursor leaves one of the screens, there is either :
  - no problem
  - the screen becomes black just below the position of the cursor and 
instantly comes back to normal.
  - the screen becomes entirely black with some random colored pixels 
flickering on the far left of the screen. I have to move the cursor to the 
black screen, otherwise it stays black.

  It happens on Ubuntu Gnome 16.04 Beta and Ubuntu Mate 16.04 Beta.
  I have tested with other distributions (Debian Jessie and Fedora) and 
everything is fine.

  Hardware : Intel Ironlake (Thinkpad X201) with an external monitor
  plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.367
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Mar  5 13:17:15 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  MachineType: LENOVO 3680KD3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3680KD3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3680KD3:pvrThinkPadX201:rvnLENOVO:rn3680KD3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3680KD3
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Sat Mar  5 13:03:55 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id2202 
   vendor BOE
  xserver.version: 2:1.17.3-2ubuntu4

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

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

[Kernel-packages] [Bug 1629730] s2lp6g002 (s390x.zKVM) - tests ran: 10, failed: 2

[Brad Figg]

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-19.21/s2lp6g002__4.8.0-19.21__2016-10-04_15-32-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/1629730

Title:
  linux: 4.8.0-20.22 -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:
  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 Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-20.22 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/1629730/+subscriptions

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

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

[Brad Figg]

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

apport-collect 1630285

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

Title:
  mwifiex_pcie crashes after several bind/unbind

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bin

  Keep doing the bind/unbind actions, it would crash very soon.

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

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

[Kernel-packages] [Bug 1630304] [NEW] Ubuntu 16.10 KVM: Issue doing hotplug detach to SRIOV VF

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

---Problem Description---
I can not get hotplug attach to work in Ubuntu but if I try to detach a CX4 VF 
from a guest I am getting some issues:
Like in this case:
[  474.393308] vfio-pci 0001:01:00.3: No device request channel registered, 
blocked until released by user
[  474.393543] pci 0001:01: 0.3: [PE# 006] Removing DMA window #0
[  474.393553] pci 0001:01: 0.3: [PE# 006] Removing DMA window #1
[  474.393906] mlx5_core 0001:01:00.3: enabling device ( -> 0002)
[  474.393939] mlx5_core 0001:01:00.3: Using 32-bit DMA via iommu
[  474.400360] pci 0001:01: 0.3: [PE# 006] Setting up window#0 0..7fff 
pg=1000
[  474.400380] mlx5_core 0001:01:00.3: firmware version: 12.17.226
[  474.401341] pci 0001:01: 0.3: [PE# 006] Enabling 64-bit DMA bypass
[  474.402284] EEH: Frozen PE#6 on PHB#1 detected
[  474.402475] EEH: PE location: Slot4, PHB location: N/A
[  474.403699] EEH: This PCI device has failed 1 times in the last hour
[  474.403700] EEH: Notify device drivers to shutdown
[  474.403707] mlx5_core 0001:01:00.3: mlx5_pci_err_detected was called
[  474.403711] mlx5_core 0001:01:00.3: 
0001:01:00.3:mlx5_enter_error_state:115:(pid 779): start
[  474.403870] mlx5_core 0001:01:00.3: 
0001:01:00.3:mlx5_enter_error_state:120:(pid 779): end


One time I saw 
SSep 13 09:41:32 ltc-fire1 kernel: [70437.943722] vfio-pci 0001:01:00.3: No 
device request channel registered, blocked until released by user
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944076] mlx5_core 0001:01:00.3: 
enabling device ( -> 0002)
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944110] mlx5_core 0001:01:00.3: Using 
32-bit DMA via iommu
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944145] pci 0001:01: 0.3: [PE# 006] 
Removing DMA window #0
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944152] pci 0001:01: 0.3: [PE# 006] 
Removing DMA window #1
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944195] mlx5_core 0001:01:00.3: 
firmware version: 12.17.226
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944260] Unable to handle kernel paging 
request for data at address 0x
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944533] Faulting instruction address: 
0xc05b37e0
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944592] Oops: Kernel access of bad 
area, sig: 11 [#1]
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944636] SMP NR_CPUS=2048 NUMA PowerNV
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944851] Modules linked in: vfio_pci 
irqbypass vfio_iommu_spapr_tce vfio_virqfd vfio vfio_spapr_eeh xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp kvm_hv kvm_pr kvm ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) 
mlx5_core(OE) mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) mlx4_en(OE) 
ib_addr(OE) ib_netlink(OE) mlx4_core(OE) mlx_compat(OE) bridge stp llc joydev 
input_leds mac_hid ofpart at24 cmdlinepart powernv_flash ipmi_powernv 
nvmem_core uio_pdrv_genirq opal_prd mtd ipmi_msghandler uio ibmpowernv 
powernv_rng binfmt_misc dm_multipath knem(OE) ip_tables x_tables autofs4 
hid_generic usbhid hid uas usb_storage ast i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect sysim
 gblt fb_sys_fops drm ahci devlink libahci [last unloaded: mlx4_core]
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946007] CPU: 40 PID: 12501 Comm: 
libvirtd Tainted: G   OE   4.7.0unofficial #5
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946074] task: c00ec319a200 ti: 
c00ec324c000 task.ti: c00ec324c000
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946140] NIP: c05b37e0 LR: 
c05ad070 CTR: 
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946208] REGS: c00ec324f100 TRAP: 
0300   Tainted: G   OE(4.7.0unofficial)
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946286] MSR: 90010280b033 
  CR: 84028844  XER: 2000
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] CFAR: c0008468 DAR: 
 DSISR: 4000 SOFTE: 0
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR00: c05d19c8 
c00ec324f380 c13bef00 
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR04:  
  
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR08:  
  f3803140
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR12: 24048840 
cfb96800 c00ec0def080 c00ec0def000
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR16: 3fff93ef 
0001  c00ec0def100
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR20: c00ec0def118 
 0001 
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR24: 0001 
f

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Joseph Salisbury]

I started a kernel bisect between v4.7 final and v4.8-rc1. The kernel
bisect will require testing of about 7-10 test kernels.

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

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

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1630304] [NEW] Ubuntu 16.10 KVM: Issue doing hotplug detach to SRIOV VF

[bugproxy]

Public bug reported:

---Problem Description---
I can not get hotplug attach to work in Ubuntu but if I try to detach a CX4 VF 
from a guest I am getting some issues:
Like in this case:
[  474.393308] vfio-pci 0001:01:00.3: No device request channel registered, 
blocked until released by user
[  474.393543] pci 0001:01: 0.3: [PE# 006] Removing DMA window #0
[  474.393553] pci 0001:01: 0.3: [PE# 006] Removing DMA window #1
[  474.393906] mlx5_core 0001:01:00.3: enabling device ( -> 0002)
[  474.393939] mlx5_core 0001:01:00.3: Using 32-bit DMA via iommu
[  474.400360] pci 0001:01: 0.3: [PE# 006] Setting up window#0 0..7fff 
pg=1000
[  474.400380] mlx5_core 0001:01:00.3: firmware version: 12.17.226
[  474.401341] pci 0001:01: 0.3: [PE# 006] Enabling 64-bit DMA bypass
[  474.402284] EEH: Frozen PE#6 on PHB#1 detected
[  474.402475] EEH: PE location: Slot4, PHB location: N/A
[  474.403699] EEH: This PCI device has failed 1 times in the last hour
[  474.403700] EEH: Notify device drivers to shutdown
[  474.403707] mlx5_core 0001:01:00.3: mlx5_pci_err_detected was called
[  474.403711] mlx5_core 0001:01:00.3: 
0001:01:00.3:mlx5_enter_error_state:115:(pid 779): start
[  474.403870] mlx5_core 0001:01:00.3: 
0001:01:00.3:mlx5_enter_error_state:120:(pid 779): end


One time I saw 
SSep 13 09:41:32 ltc-fire1 kernel: [70437.943722] vfio-pci 0001:01:00.3: No 
device request channel registered, blocked until released by user
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944076] mlx5_core 0001:01:00.3: 
enabling device ( -> 0002)
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944110] mlx5_core 0001:01:00.3: Using 
32-bit DMA via iommu
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944145] pci 0001:01: 0.3: [PE# 006] 
Removing DMA window #0
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944152] pci 0001:01: 0.3: [PE# 006] 
Removing DMA window #1
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944195] mlx5_core 0001:01:00.3: 
firmware version: 12.17.226
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944260] Unable to handle kernel paging 
request for data at address 0x
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944533] Faulting instruction address: 
0xc05b37e0
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944592] Oops: Kernel access of bad 
area, sig: 11 [#1]
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944636] SMP NR_CPUS=2048 NUMA PowerNV
Sep 13 09:41:32 ltc-fire1 kernel: [70437.944851] Modules linked in: vfio_pci 
irqbypass vfio_iommu_spapr_tce vfio_virqfd vfio vfio_spapr_eeh xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp kvm_hv kvm_pr kvm ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) 
mlx5_core(OE) mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) mlx4_en(OE) 
ib_addr(OE) ib_netlink(OE) mlx4_core(OE) mlx_compat(OE) bridge stp llc joydev 
input_leds mac_hid ofpart at24 cmdlinepart powernv_flash ipmi_powernv 
nvmem_core uio_pdrv_genirq opal_prd mtd ipmi_msghandler uio ibmpowernv 
powernv_rng binfmt_misc dm_multipath knem(OE) ip_tables x_tables autofs4 
hid_generic usbhid hid uas usb_storage ast i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect sysim
 gblt fb_sys_fops drm ahci devlink libahci [last unloaded: mlx4_core]
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946007] CPU: 40 PID: 12501 Comm: 
libvirtd Tainted: G   OE   4.7.0unofficial #5
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946074] task: c00ec319a200 ti: 
c00ec324c000 task.ti: c00ec324c000
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946140] NIP: c05b37e0 LR: 
c05ad070 CTR: 
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946208] REGS: c00ec324f100 TRAP: 
0300   Tainted: G   OE(4.7.0unofficial)
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946286] MSR: 90010280b033 
  CR: 84028844  XER: 2000
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] CFAR: c0008468 DAR: 
 DSISR: 4000 SOFTE: 0
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR00: c05d19c8 
c00ec324f380 c13bef00 
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR04:  
  
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR08:  
  f3803140
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR12: 24048840 
cfb96800 c00ec0def080 c00ec0def000
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR16: 3fff93ef 
0001  c00ec0def100
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR20: c00ec0def118 
 0001 
Sep 13 09:41:32 ltc-fire1 kernel: [70437.946533] GPR24: 0001 
 0

[Kernel-packages] [Bug 1630285] Re: mwifiex_pcie crashes after several bind/unbind

[Joseph Salisbury]

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

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

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

Title:
  mwifiex_pcie crashes after several bind/unbind

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bin

  Keep doing the bind/unbind actions, it would crash very soon.

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

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

[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

[Thomas Schweikle]

** Tags added: kernel-bug-exists-upstream

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

[Thomas Schweikle]

I've added kernel-bug-exists-upstream since this bug is in the latest
upstream kernel, linux-image-4.8.0-17-generic, present.

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

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

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1629730] dwalin (amd64) - tests ran: 10, failed: 1

[Brad Figg]

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-20.22/dwalin__4.8.0-20.22__2016-10-04_15-44-00/results-index.html

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

Title:
  linux: 4.8.0-20.22 -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:
  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 Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-20.22 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/1629730/+subscriptions

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

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

[Brad Figg]

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-20.22/onza__4.8.0-20.22__2016-10-04_15-50-00/results-index.html

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

Title:
  linux: 4.8.0-20.22 -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:
  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 Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-20.22 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/1629730/+subscriptions

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