[Kernel-packages] [Bug 1492170] Re: Screen flicker and resolution problems after hot-plug

[Michael Thayer]

I can't test immediately in any case, as I am travelling and do not have
access to an external monitor.

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

Title:
  Screen flicker and resolution problems after hot-plug

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Wily, when I change the configuration of screens
  attached (specifically: dock the laptop to a docking station with a
  vertically larger external screen or open the laptop to activate the
  internal screen while correctly running with said external screen)
  this causes various display issues, including flickering while the
  mouse cursor is moved and or one screen flickering the contents of the
  other; incorrect resolution; incorrect offset of displayed screen
  contents on screen.  I saw similar (can't say whether or not
  identical) effects using the stock 4.1.0-3.3 generic kernel, and
  mainline generic kernels 4.0.0-04rc2.201503031836 (working before
  the first reboot after upgrading to Wily), 4.1.3-040103.201507220129
  and 4.1.6-040106.201508170230.  In addition (probably a separate
  issue), when booting 4.1.0-3.3 to external monitor only, the mouse
  cursor was not shown.

  After my last test I was able to bring things back to "normal" by
  killing the X server and logging in again.

  $ lsb_release -rd
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  $ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20150808-0ubuntu2
Candidate: 2:2.99.917+git20150808-0ubuntu2
Version table:
   *** 2:2.99.917+git20150808-0ubuntu2 0
  500 http://de.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2
  Uname: Linux 4.1.6-040106-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Sep  4 11:11:59 2015
  DistUpgraded: 2015-09-03 15:02:03,761 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05cb]
  InstallationDate: Installed on 2014-08-01 (399 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Latitude E7440
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.6-040106-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to wily on 2015-09-03 (0 days ago)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RYCC9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5
  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.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Sep  4 11:10:45 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4413 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu5

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

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

[Kernel-packages] [Bug 1492170] Re: Screen flicker and resolution problems after hot-plug

[Michael Thayer]

As I said, display was so badly broken with that kernel that I was
unable to test, though it might have been co-incidence - it has always
been rather temperamental with all the 4.1 and 4.2 kernels I have
tested.  In my few short tests I was unable to get the external monitor
to display anything at all while the X server was active either with or
without the panel open, though a VT worked.  gnome-display-settings (or
whatever it is called) clearly thought that the monitor was enabled
though.  I will give it another test next time I have to reboot anyway.

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

Title:
  Screen flicker and resolution problems after hot-plug

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Wily, when I change the configuration of screens
  attached (specifically: dock the laptop to a docking station with a
  vertically larger external screen or open the laptop to activate the
  internal screen while correctly running with said external screen)
  this causes various display issues, including flickering while the
  mouse cursor is moved and or one screen flickering the contents of the
  other; incorrect resolution; incorrect offset of displayed screen
  contents on screen.  I saw similar (can't say whether or not
  identical) effects using the stock 4.1.0-3.3 generic kernel, and
  mainline generic kernels 4.0.0-04rc2.201503031836 (working before
  the first reboot after upgrading to Wily), 4.1.3-040103.201507220129
  and 4.1.6-040106.201508170230.  In addition (probably a separate
  issue), when booting 4.1.0-3.3 to external monitor only, the mouse
  cursor was not shown.

  After my last test I was able to bring things back to "normal" by
  killing the X server and logging in again.

  $ lsb_release -rd
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  $ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20150808-0ubuntu2
Candidate: 2:2.99.917+git20150808-0ubuntu2
Version table:
   *** 2:2.99.917+git20150808-0ubuntu2 0
  500 http://de.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2
  Uname: Linux 4.1.6-040106-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Sep  4 11:11:59 2015
  DistUpgraded: 2015-09-03 15:02:03,761 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05cb]
  InstallationDate: Installed on 2014-08-01 (399 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Latitude E7440
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.6-040106-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to wily on 2015-09-03 (0 days ago)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RYCC9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5
  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.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Sep  4 11:10:45 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4413 
   vendor   

[Kernel-packages] [Bug 1488422] Re: Recovery from 'display cannot be detected' does not work properly

[Thaddaeus Tintenfisch]

This happened at some point in the boot sequence, and therefore before
the Xfce Desktop Environment was actually started.

** Package changed: xfce4 (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/1488422

Title:
  Recovery from 'display cannot be detected' does not work properly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This morning I got a 'display cannot be determined' popup when I
  booted. On hitting Enter I got another popup with a menu prompting for
  an action. However I had no mouse pointer and the keyboard did not
  respond to Space, Tab, arrows or Enter so I could not actually make a
  choice. Hitting Escape got me out of it and the machine continued its
  boot sequence, but with errors and without a display manager.

  After logging in on a text console I ran 'startx' with no problems.

  
  Why I got the error in the first place is another question. It is possible 
that I did not switch on the monitor early enough :-)

  Severity: not something that a newbie would be able to handle.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xfce4 4.10.1
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic i686
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: i386
  Date: Tue Aug 25 09:40:05 2015
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4
  UpgradeStatus: Upgraded to trusty on 2014-08-23 (366 days ago)

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

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

[Kernel-packages] [Bug 1478513] Re: MFG:Firestone, Linux Error message: SYSPARAM: Opal sysparam node not found

[bugproxy]

Default Comment by Bridge

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

** Attachment added: "Silence SYSPARAM warning on boot"
   
https://bugs.launchpad.net/bugs/1478513/+attachment/4478253/+files/0001-powerpc-powernv-Silence-SYSPARAM-warning-on-boot.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/1478513

Title:
  MFG:Firestone, Linux Error message: SYSPARAM: Opal sysparam node not
  found

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  When using Firestone POWER8 hardware, the following message gets printed to 
the kernel log:
  SYSPARAM: Opal sysparam node not found

  [Test Case]
  1) Boot affected hardware.
  2) dmesg | grep 'Opal sysparam node not found'

  [Fix]
  $ git describe --contains 38c0488770983b2654f075540cc1fc71f55b6df5
  v4.2-rc1~135^2~144

  --

  == Comment: #0 - Application Cdeadmin  -
  2015-07-22 11:35:05 ==

  == Comment: #1 - Application Cdeadmin  - 2015-07-22 
11:35:06 ==
   State: Open by: knodelk on 22 July 2015 10:25:15 

  The following message is being posted to the linux message log on Firestone 
systems, and we need to know what action to take.
   - is this caused by a code bug that needs to be fixed?
   - does the message indicate a real hardware problem?
     or can the message be ignore?

  Until we here otherwise, manufacturing is ignoring this message

  dmesg --level=alert,crit,err

  SYSPARAM: Opal sysparam node not found

  system is running with the following code levels:
     ver 1.5.4.3 - OS, HTX, Firmware and Machine details

     OS: GNU/Linux
     OS Version: Ubuntu 14.04.2 LTS \n \l
     Kernel Version: 3.16.0-30-generic
    HTX Version: htxubuntu-343

  == Comment: #2 - MAMATHA INAMDAR  - 2015-07-27 06:18:20 
==
  "SYSPARAM: Opal sysparam node not found" we get this warning on firestone 
system for every boot because For OpenPower BMC machines we do not place any 
sysparams in the device tree.

  This issue is addressed in the attached patch and patch is available in 
upstream.
  We need to backport following patch in ubuntu to address this issue.
  Commit ID:38c0488770983b2654f075540cc1fc71f55b6df5
  0001-powerpc-powernv-Silence-SYSPARAM-warning-on-boot.patch

  == Comment: #3 - MAMATHA INAMDAR  - 2015-07-27 06:25:34 
==
  Please find upstream commit ID link

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=38c0488770983b2654f075540cc1fc71f55b6df5

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

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

[Kernel-packages] [Bug 1499789] Re: BLUEZ5: Connecting a keyboard shows no pip popup

[Dave Morley]

** Tags added: bluez5

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

Title:
  BLUEZ5: Connecting a keyboard shows no pip popup

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  You can not connect to a pin required keyboard as the dialogue is not
  shown.

  This means that the device for all intents and purposes looks to be
  connected, but if you disconnect from it you can not reconnect and the
  device doesn't actually type anything because although it looks
  connected it actually isn't.

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

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

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

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

Title:
  Recovery from 'display cannot be detected' does not work properly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This morning I got a 'display cannot be determined' popup when I
  booted. On hitting Enter I got another popup with a menu prompting for
  an action. However I had no mouse pointer and the keyboard did not
  respond to Space, Tab, arrows or Enter so I could not actually make a
  choice. Hitting Escape got me out of it and the machine continued its
  boot sequence, but with errors and without a display manager.

  After logging in on a text console I ran 'startx' with no problems.

  
  Why I got the error in the first place is another question. It is possible 
that I did not switch on the monitor early enough :-)

  Severity: not something that a newbie would be able to handle.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xfce4 4.10.1
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic i686
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: i386
  Date: Tue Aug 25 09:40:05 2015
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4
  UpgradeStatus: Upgraded to trusty on 2014-08-23 (366 days ago)

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

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

[Kernel-packages] [Bug 1499789] Re: BLUEZ5: Connecting a keyboard shows no pip popup

[Simon Fels]

** Tags added: bluetooth

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  BLUEZ5: Connecting a keyboard shows no pip popup

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  You can not connect to a pin required keyboard as the dialogue is not
  shown.

  This means that the device for all intents and purposes looks to be
  connected, but if you disconnect from it you can not reconnect and the
  device doesn't actually type anything because although it looks
  connected it actually isn't.

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

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

[Kernel-packages] [Bug 1488422] [NEW] Recovery from 'display cannot be detected' does not work properly

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This morning I got a 'display cannot be determined' popup when I booted.
On hitting Enter I got another popup with a menu prompting for an
action. However I had no mouse pointer and the keyboard did not respond
to Space, Tab, arrows or Enter so I could not actually make a choice.
Hitting Escape got me out of it and the machine continued its boot
sequence, but with errors and without a display manager.

After logging in on a text console I ran 'startx' with no problems.


Why I got the error in the first place is another question. It is possible that 
I did not switch on the monitor early enough :-)

Severity: not something that a newbie would be able to handle.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xfce4 4.10.1
ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
Uname: Linux 3.13.0-62-generic i686
ApportVersion: 2.14.1-0ubuntu3.12
Architecture: i386
Date: Tue Aug 25 09:40:05 2015
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: xfce4
UpgradeStatus: Upgraded to trusty on 2014-08-23 (366 days ago)

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


** Tags: apport-bug i386 trusty
-- 
Recovery from 'display cannot be detected' does not work properly
https://bugs.launchpad.net/bugs/1488422
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 1478492] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From cdead...@us.ibm.com 2015-09-29 06:00 EDT---

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

Title:
  MFG:Firestone, Linux Error message: unable to open rtc device

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2015-07-22 12:35:06 ==

  
  == Comment: #1 - Application Cdeadmin  - 2015-07-22 
12:35:08 ==
   State: Open by: knodelk on 22 July 2015 11:26:27 

  he following message is being posted to the linux message log on Firestone 
systems, and we need to know what action to take.
   - is this caused by a code bug that needs to be fixed?
   - does the message indicate a real hardware problem? 
 or can the message be ignore?

  Until we here otherwise, manufacturing is ignoring this message

  dmesg --level=alert,crit,err


  /build/buildd/linux-lts-utopic-3.16.0/drivers/rtc/hctosys.c: unable to open 
rtc device (rtc0)

  system is running with the following code levels: 
 ver 1.5.4.3 - OS, HTX, Firmware and Machine details

 OS: GNU/Linux
 OS Version: Ubuntu 14.04.2 LTS \n \l
 Kernel Version: 3.16.0-30-generic
HTX Version: htxubuntu-343

  
  == Comment: #2 - MAMATHA INAMDAR  - 2015-07-23 02:10:00 
==
  Neelesh,
  Can you please comment on this issue.

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

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

[Kernel-packages] [Bug 1498065] Re: linux: 3.19.0-30.33 -proposed tracker

[Luis Henriques]

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


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

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

** Description changed:

  This bug is for tracking the 3.19.0-30.33 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 21. September 2015 15:30 UTC
  kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 06:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 06:02 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:15 UTC
  kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:01 UTC
  kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:01 
UTC
  kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:01 UTC
  kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:00 UTC
  kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:00 UTC
  kernel-stable-Verification-testing-end:Friday, 25. September 2015 16:07 UTC
  kernel-stable-Certification-testing-end:Saturday, 26. September 2015 18:00 UTC
- kernel-stable-phase:CopyToUpdates
- kernel-stable-phase-changed:Sunday, 27. September 2015 21:00 UTC
  kernel-stable-Promote-to-updates-start:Sunday, 27. September 2015 21:00 UTC
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Tuesday, 29. September 2015 14:03 UTC
+ kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 14:02 UTC

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

Title:
  linux: 3.19.0-30.33 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 21. September 2015 15:30 UTC
  kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 06:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 06:02 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:15 UTC
  kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:01 UTC
  kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:01 
UTC
  kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:01 UTC
  kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:00 UTC
  kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:00 UTC
  kernel-stable-Verification-testing-end:Friday, 25. September 2015 16:07 UTC
  kernel-stable-Certification-testing-end:Saturday, 26. September 2015 18:00 UTC
  kernel-stable-Promote-to-updates-start:Sunday, 27. September 2015 21:00 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 29. September 2015 14:03 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 14:02 UTC

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

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

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

[bugproxy]

--- Comment From mainam...@in.ibm.com 2015-09-29 05:55 EDT---
As per my discussion with developer can you please retest with the current 
latest kernel 14.04.03.
I think we don't see this issue with latest version of the kernel.

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

Title:
  MFG:Firestone, Linux Error message: unable to open rtc device

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2015-07-22 12:35:06 ==

  
  == Comment: #1 - Application Cdeadmin  - 2015-07-22 
12:35:08 ==
   State: Open by: knodelk on 22 July 2015 11:26:27 

  he following message is being posted to the linux message log on Firestone 
systems, and we need to know what action to take.
   - is this caused by a code bug that needs to be fixed?
   - does the message indicate a real hardware problem? 
 or can the message be ignore?

  Until we here otherwise, manufacturing is ignoring this message

  dmesg --level=alert,crit,err


  /build/buildd/linux-lts-utopic-3.16.0/drivers/rtc/hctosys.c: unable to open 
rtc device (rtc0)

  system is running with the following code levels: 
 ver 1.5.4.3 - OS, HTX, Firmware and Machine details

 OS: GNU/Linux
 OS Version: Ubuntu 14.04.2 LTS \n \l
 Kernel Version: 3.16.0-30-generic
HTX Version: htxubuntu-343

  
  == Comment: #2 - MAMATHA INAMDAR  - 2015-07-23 02:10:00 
==
  Neelesh,
  Can you please comment on this issue.

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

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

[Kernel-packages] [Bug 1500739] [NEW] CPU lockup on HP Proliant DL380 Gen9 servers

[Brad Marshall]

Public bug reported:

Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
servers lock up with a similar looking cpu lockup bug.  All 3 of these
servers are nova-compute nodes in an OpenStack cluster, with a
reasonable amount of load on them.  The symptoms are the load shoots up
into the hundreds, and ps stops returning.

I've attached lspci -vnvn and 3 sets of syslog message traces that we
grabbed on each of the 3 times it has crashed.

$ cat /proc/version_signature 
Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

Please let us know if you need any further information.

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


** Tags: canonical-bootstack

** Attachment added: "lspci-vnvn output"
   
https://bugs.launchpad.net/bugs/1500739/+attachment/4478311/+files/lspci-vnvn.log

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.

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

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

[Kernel-packages] [Bug 1500739] Re: CPU lockup on HP Proliant DL380 Gen9 servers

[Brad Marshall]

2nd of the lockups.

** Attachment added: "CPU Lockup 2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478313/+files/cpu-lockup-2.log

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.

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

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

[Kernel-packages] [Bug 1500739] Re: CPU lockup on HP Proliant DL380 Gen9 servers

[Brad Marshall]

The first of the lockups.  These all required us to hard reset the
servers via the ilo.


** Attachment added: "CPU Lockup 1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478312/+files/cpu-lockup-1.log

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.

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

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

[Kernel-packages] [Bug 1500739] Re: CPU lockup on HP Proliant DL380 Gen9 servers

[Brad Marshall]

3rd of the lockups

** Attachment added: "CPU Lockup 3"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478314/+files/cpu-lockup-3.log

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.

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

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

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

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.

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

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

[Kernel-packages] [Bug 1494371] Re: linux-lts-utopic: 3.16.0-50.66~14.04.1 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.16.0-50.66~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 10. September 2015 15:32 UTC
  kernel-stable-Prepare-package-end:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 11. September 2015 19:24 UTC
  kernel-stable-Verification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Certification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-start:Friday, 11. September 2015 21:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-end:Saturday, 12. September 2015 08:01 UTC
  kernel-stable-Regression-testing-end:Friday, 18. September 2015 22:01 UTC
  kernel-stable-Certification-testing-end:Thursday, 24. September 2015 03:00 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-phase-changed:Friday, 25. September 2015 16:07 UTC
  kernel-stable-Promote-to-updates-start:Friday, 25. September 2015 16:07 UTC
+ kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 13:53 UTC

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

Title:
  linux-lts-utopic: 3.16.0-50.66~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 10. September 2015 15:32 UTC
  kernel-stable-Prepare-package-end:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 11. September 2015 19:24 UTC
  kernel-stable-Verification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Certification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-start:Friday, 11. September 2015 21:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-end:Saturday, 12. September 2015 08:01 UTC
  kernel-stable-Regression-testing-end:Friday, 18. September 2015 22:01 UTC
  kernel-stable-Certification-testing-end:Thursday, 24. September 2015 03:00 UTC
  kernel-stable-Promote-to-updates-start:Friday, 25. September 2015 16:07 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 13:53 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 29. September 2015 14:00 UTC

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

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

[Kernel-packages] [Bug 1500094] Re: Asus UX303LB: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event

[Nuno]

Christopher, the latest kernel (4.3.0-040300rc3) doesn't fix the issue.


** Tags added: kernel-bug-exists-upstream 
kernel-bug-exists-upstream-4.3.0-040300rc3

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

Title:
  Asus UX303LB: Brightness keys Fn+F5 and Fn+F6 don't generate evdev
  event

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It seems brightness keys don't work with Ubuntu 15.04 for laptop Asus
  Zenbook UX303LB. Also acpi_listen does not detect fn+f5 and fn+f6

  ---
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nuno   1689 F pulseaudio
   /dev/snd/controlC0:  nuno   1689 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=b6aebadc-8f37-49d3-bd1e-e0171ac4c1ab
  InstallationDate: Installed on 2015-09-24 (5 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 064e:9700 Suyin Corp.
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed 
root=UUID=a195a7ac-d5d1-4d1e-ab13-199a8b8533bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-28-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/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  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.:bvrUX303LB.206:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  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/1500094/+subscriptions

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

[Kernel-packages] [Bug 1327774] Re: asus x200la brightness hotkeys not working (rest of them do)

[Jaime Pérez]

You have all the needed info in bugzilla. The problem was the acpi
driver detecting less than 8 inputs, and the asignee made a patch (which
I pasted here) that fixed the problem. He said they needed to find a
better solution to the issue, because the patch wasn't the best
solution.  I won't give more information.

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

Title:
  asus x200la brightness hotkeys not working (rest of them do)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  If I click on brightness hotkeys nothing (apparently) happens. I
  suppose keys are missbinded or something like that. How can I fix it?

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

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

[Kernel-packages] [Bug 1500854] [NEW] linux: 3.2.0-92.130 -proposed tracker

[Luis Henriques]

Public bug reported:

This bug is for tracking the 3.2.0-92.130 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-Prepare-package-start:Tuesday, 29. September 2015 12:55 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Tuesday, 29. September 2015 12:55 UTC

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-lbm
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Platform QA Team (canonical-platform-qa)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Precise)
 Importance: Medium
 Status: New


** Tags: block-proposed-precise kernel-release-tracking-bug precise

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-precise

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

** Tags added: precise

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-lbm
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-lbm
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-lbm
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: 

[Kernel-packages] [Bug 1496232] Re: CVE-2015-6937

[Luis Henriques]

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  CVE-2015-6937

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  New
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-fsl-imx51 source package in Wily:
  Invalid
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-backport-maverick source package in Wily:
  New
Status in 

[Kernel-packages] [Bug 1497812] Re: i40e bug: non physical MAC outbound frames appear as copied back inbound (mirrored)

[Joseph Salisbury]

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

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

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

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

Title:
  i40e bug: non physical MAC outbound frames appear as copied back
  inbound  (mirrored)

Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-vivid package in Ubuntu:
  Confirmed

Bug description:
  Using 3.19.0-28-generic #30~14.04.1-Ubuntu with stock i40e
  driver version 2.2.2-k makes every 'non physical' MAC output
  frame appear as copied back at input, as if the switch was
  doing frame 'mirroring' (and/or hair-pinning).

  FYI same setup, with i40e upgraded to 1.2.48 from
  http://downloadmirror.intel.com/25282/eng/i40e-1.2.48.tar.gz
  behaves OK, fyi also we did a port mirroring setup at
  the switch directed to a different physical port for debugging,
  and didn't observe these frames to be physically present.

  See tcpdump -P in/out and more details at
  http://paste.ubuntu.com/12511680/

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  Date: Mon Sep 21 02:05:28 2015
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1500894] [NEW] linux: 4.2.0-13.15 -proposed tracker

[Tim Gardner]

Public bug reported:

This bug is for tracking the 4.2.0-13.15 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-Prepare-package-start:Tuesday, 29. September 2015 14:01 UTC
kernel-phase-changed:Tuesday, 29. September 2015 14:01 UTC
kernel-phase:Prepare

** 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: New

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Wily)
 Importance: Undecided
 Status: Invalid


** Tags: block-proposed kernel-release-tracking-bug wily

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed

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

** Tags added: wily

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

** 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: linux (Ubuntu)
   Status: New => Invalid

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

Title:
  linux: 4.2.0-13.15 -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:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 

[Kernel-packages] [Bug 1499622] Re: multipath keep failure after the interface is recovered

[jay.xu]

Any comment on that?

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

Title:
  multipath keep failure after the interface is recovered

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We encounter a multipath issue on Ubuntu 14.04.2 LTS.

  dm state (i.e. failed) cannot be recovered automatically when the
  interface is back. But path check state (i.e. faulty) can.

  In order to describe the issue clearly, the attached slides shows the detail 
of reproduce steps. 
  Meanwhile, attachment also includes the output from multipath tool. 

  P.S. We are writing the IO to the volume through dm device during the
  interface enable/disable.

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

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

[Kernel-packages] [Bug 1494371] Re: linux-lts-utopic: 3.16.0-50.66~14.04.1 -proposed tracker

[Luis Henriques]

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


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

** Description changed:

  This bug is for tracking the 3.16.0-50.66~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 10. September 2015 15:32 UTC
  kernel-stable-Prepare-package-end:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 11. September 2015 19:24 UTC
  kernel-stable-Verification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Certification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-start:Friday, 11. September 2015 21:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-end:Saturday, 12. September 2015 08:01 UTC
  kernel-stable-Regression-testing-end:Friday, 18. September 2015 22:01 UTC
  kernel-stable-Certification-testing-end:Thursday, 24. September 2015 03:00 UTC
- kernel-stable-phase:CopyToUpdates
- kernel-stable-phase-changed:Friday, 25. September 2015 16:07 UTC
  kernel-stable-Promote-to-updates-start:Friday, 25. September 2015 16:07 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 13:53 UTC
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Tuesday, 29. September 2015 14:00 UTC

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

Title:
  linux-lts-utopic: 3.16.0-50.66~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 10. September 2015 15:32 UTC
  kernel-stable-Prepare-package-end:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 11. September 2015 19:24 UTC
  kernel-stable-Verification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Certification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-start:Friday, 11. September 2015 21:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-end:Saturday, 12. September 2015 08:01 UTC
  kernel-stable-Regression-testing-end:Friday, 18. September 2015 22:01 UTC
  kernel-stable-Certification-testing-end:Thursday, 24. September 2015 03:00 UTC
  kernel-stable-Promote-to-updates-start:Friday, 25. September 2015 16:07 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 13:53 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 29. September 2015 14:00 UTC

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

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

[Kernel-packages] [Bug 1327774] Re: asus x200la brightness hotkeys not working (rest of them do)

[Jaime Pérez]

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

Title:
  asus x200la brightness hotkeys not working (rest of them do)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  If I click on brightness hotkeys nothing (apparently) happens. I
  suppose keys are missbinded or something like that. How can I fix it?

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

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

[Kernel-packages] [Bug 1494371] Re: linux-lts-utopic: 3.16.0-50.66~14.04.1 -proposed tracker

[Luis Henriques]

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

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

Title:
  linux-lts-utopic: 3.16.0-50.66~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 10. September 2015 15:32 UTC
  kernel-stable-Prepare-package-end:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 11. September 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 11. September 2015 19:24 UTC
  kernel-stable-Verification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Certification-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-start:Friday, 11. September 2015 21:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 11. September 2015 21:03 UTC
  kernel-stable-Security-signoff-end:Saturday, 12. September 2015 08:01 UTC
  kernel-stable-Regression-testing-end:Friday, 18. September 2015 22:01 UTC
  kernel-stable-Certification-testing-end:Thursday, 24. September 2015 03:00 UTC
  kernel-stable-Promote-to-updates-start:Friday, 25. September 2015 16:07 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 13:53 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 29. September 2015 14:00 UTC

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

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

[Kernel-packages] [Bug 1250109] Re: Please use dpkg-triggers

[Mörgæs]

The report is getting somewhat old. Is any work being done in this
context?

The fix is one of the few that would benefit the entire user group.
Would be more than welcome, especially for people using old hardware.

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

Title:
  Please use dpkg-triggers

Status in grub2 package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

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

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

[Kernel-packages] [Bug 1490130] Re: Elantech touchpad stops working after suspend

[Thatoo]

@Christopher M. Penalver (penalvch), here is the answer of 
ubuntu-bug linux

It appears you are currently running a mainline kernel.  It would be
better to report this bug upstream at http://bugzilla.kernel.org/ so
that the upstream kernel developers are aware of the issue.  If you'd
still like to file a bug against the Ubuntu kernel, please boot with an
official Ubuntu kernel and re-file.

So I file a bug on http://bugzilla.kernel.org/
https://bugzilla.kernel.org/show_bug.cgi?id=105231

Before you read it, I'm sorry to say that I made a mistake, I confuse Elantech 
and Focaltech.
It seems that my touchpad is a Focaltech not an Elantech but I'm not exactly 
sure how to know, I've just find out in this file /proc/bus/input/devices .

Regards,


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

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

Title:
  Elantech touchpad stops working after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i have asus a455ld i5 5200u running kubuntu 15.04 with kernel 
4.0.8-040008-generic. 
  touchpad is recognized as elantech version 4. everything was fine until my 
notebook go to suspend and resume without touchpad working.
  I tried :
  modprobe -r psmouse
  modprobe psmouse

  it only work before suspend.
  execute those commands after resume from suspend is not working.

  the last thing i tried is this.

  when i use this command before suspend :

  insmod
  /lib/modules/4.0.8-040008-generic/kernel/drivers/input/mouse/psmouse.ko

  these appear in the dmesg:

  [  820.207105] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x381f00)
  [  820.70] psmouse serio1: elantech: Synaptics capabilities query result 
0x10, 0x14, 0x0e.
  [  820.294698] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input146

  but when i use the command after suspend, there is nothing any output
  in the dmesg.

  i tried all ubuntu varian and opensuse 13.2 live usb, the result is the same. 
  but in windows 10,  touchpad still active after suspend.
  --- 
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-06-20 (69 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: linux (not installed)
  Tags:  vivid
  Uname: Linux 4.0.8-040008-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1500810] Re: Trusty update to 3.13.11-ckt27 stable release

[Luis Henriques]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from Linus' tree or in a minimally
+    backported form of that patch. The 3.13.11-ckt27 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from Linus' tree or in a minimally
-backported form of that patch. The 3.13.11-ckt27 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://kernel.ubuntu.com/ubuntu/linux.git
  
-git://kernel.ubuntu.com/ubuntu/linux.git
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches are in the 3.13.11-ckt27 stable release:
  
-The following patches are in the 3.13.11-ckt27 stable release:
+ md/raid10: always set reshape_safe when initializing reshape_position.
+ md: flush ->event_work before stopping array.
+ ipv6: addrconf: validate new MTU before applying it
+ virtio-net: drop NETIF_F_FRAGLIST
+ RDS: verify the underlying transport exists before creating a connection
+ xen/gntdev: convert priv->lock to a mutex
+ xen/gntdevt: Fix race condition in gntdev_release()
+ PCI: Restore PCI_MSIX_FLAGS_BIRMASK definition
+ nfsd: Drop BUG_ON and ignore SECLABEL on absent filesystem
+ crypto: ixp4xx - Remove bogus BUG_ON on scattered dst buffer
+ xen-blkfront: don't add indirect pages to list when !feature_persistent
+ xen-blkback: replace work_pending with work_busy in purge_persistent_gnt()
+ USB: sierra: add 1199:68AB device ID
+ regmap: regcache-rbtree: Clean new present bits on present bitmap resize
+ target/iscsi: Fix double free of a TUR followed by a solicited NOPOUT
+ rbd: fix copyup completion race
+ md/raid1: extend spinlock to protect raid1_end_read_request against 
inconsistencies
+ target: REPORT LUNS should return LUN 0 even for dynamic ACLs
+ MIPS: Fix sched_getaffinity with MT FPAFF enabled
+ xhci: fix off by one error in TRB DMA address boundary check
+ perf: Fix fasync handling on inherited events
+ mm, vmscan: Do not wait for page writeback for GFP_NOFS allocations
+ MIPS: Make set_pte() SMP safe.
+ ipc: modify message queue accounting to not take kernel data structures into 
account
+ ocfs2: fix BUG in ocfs2_downconvert_thread_do_work()
+ fsnotify: fix oops in fsnotify_clear_marks_by_group_flags()
+ KVM: x86: Use adjustment in guest cycles when handling MSR_IA32_TSC_ADJUST
+ localmodconfig: Use Kbuild files too
+ dm thin metadata: delete btrees when releasing metadata snapshot
+ dm btree: add ref counting ops for the leaves of top level btrees
+ drm/radeon: add new OLAND pci id
+ libiscsi: Fix host busy blocking during connection teardown
+ libfc: Fix fc_exch_recv_req() error path
+ libfc: Fix fc_fcp_cleanup_each_cmd()
+ EDAC, ppc4xx: Access mci->csrows array elements properly
+ crypto: caam - fix memory corruption in ahash_final_ctx
+ mm/hwpoison: fix page refcount of unknown non LRU page
+ ipc,sem: fix use after free on IPC_RMID after a task using same semaphore set 
exits
+ ipc/sem.c: change memory barrier in sem_lock() to smp_rmb()
+ ipc/sem.c: update/correct memory barriers
+ Add factory recertified Crucial M500s to blacklist
+ arm64: KVM: Fix host crash when injecting a fault into a 32bit guest
+ batman-adv: protect tt_local_entry from concurrent delete events
+ ip6_gre: release cached dst on tunnel removal
+ net: Fix RCU splat in af_key
+ rds: fix an integer overflow test in rds_info_getsockopt()
+ udp: fix dst races with multicast early demux
+ sparc64: Fix userspace FPU register corruptions.
+ ipv6: lock socket in ip6_datagram_connect()
+ rtnetlink: verify IFLA_VF_INFO attributes before passing them to driver
+ net/tipc: initialize security state for new connection socket
+ net: pktgen: fix race between pktgen_thread_worker() and kthread_stop()
+ net: call rcu_read_lock early in process_backlog
+ net: Fix skb csum races when peeking
+ netlink: don't hold mutex in rcu callback when releasing mmapd ring
+ Linux 3.13.11-ckt27
+ 
+ The following patches from 3.13.11-ckt27 were already applied to the
+ Trusty kernel:
+ 
+ net: Fix skb_set_peeked use-after-free bug
+ net: gso: use feature flag argument in all protocol gso handlers

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

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

Title:
  Trusty update to 

[Kernel-packages] [Bug 1484799] Re: CVE-2015-5707

[Steve Beattie]

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  CVE-2015-5707

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  Fix Committed
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Invalid
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-fsl-imx51 source package in Wily:
  Invalid
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-backport-maverick source package in Wily:
  New
Status in 

[Kernel-packages] [Bug 1481039] Re: CVE-2015-5697

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  CVE-2015-5697

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 source package in Wily:
  Invalid

[Kernel-packages] [Bug 1296224] Re: Horrible noise via DisplayPort [regression]

[Andreas Schildbach]

Christopher, before I take this effort I have two questions:

1) Are you sure this is a regression in the kernel itself? It could also
be a bug in another package (e.g. xserver-xorg-video-intel), right?

2) Do kernels in the 3.11.0-3.13.0 range work in combination with a
modern 15.04 distribution? Unfortunately I cannot downgrade back to
13.10/14.04 if this would be required for testing old kernels.

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

Title:
  Horrible noise via DisplayPort [regression]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue has been present and fixed two years ago and with Trusty
  Tahr it re-appeared:

  When logging in and my display is extended to two monitors, and also
  when the screen blanks, I get 3-5 seconds of horrible noise via
  DisplayPort audio out.

  The noise is loud enough to damage ears and loudspeakers, if volume
  has been set to a normal listening level.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Mar 23 10:18:08 2014
  DistUpgraded: 2014-01-03 23:25:11,434 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21c1]
  InstallationDate: Installed on 2011-08-05 (960 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
  MachineType: LENOVO 29123AG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic 
root=UUID=b9fb2d9e-d248-4294-bd6b-9abe27dfcea4 ro quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to trusty on 2014-01-03 (78 days ago)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6UET70WW (1.50 )
  dmi.board.name: 29123AG
  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:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn29123AG:pvrThinkPadT410s:rvnLENOVO:rn29123AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 29123AG
  dmi.product.version: ThinkPad T410s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Mar 23 10:09:13 2014
  xserver.configfile: default
  xserver.errors:
   N-Trig Pen stylus: Invalid type 'cursor' for this device.
   N-Trig Pen stylus: Invalid type 'touch' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16438 
   vendor LEN
  xserver.version: 2:1.15.0-1ubuntu7

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

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

[Kernel-packages] [Bug 1500810] Re: Trusty update to 3.13.11-ckt27 stable release

[Luis Henriques]

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

Title:
  Trusty update to 3.13.11-ckt27 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  SRU Justification

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

     git://kernel.ubuntu.com/ubuntu/linux.git

  TEST CASE: TBD

     The following patches are in the 3.13.11-ckt27 stable release:

  md/raid10: always set reshape_safe when initializing reshape_position.
  md: flush ->event_work before stopping array.
  ipv6: addrconf: validate new MTU before applying it
  virtio-net: drop NETIF_F_FRAGLIST
  RDS: verify the underlying transport exists before creating a connection
  xen/gntdev: convert priv->lock to a mutex
  xen/gntdevt: Fix race condition in gntdev_release()
  PCI: Restore PCI_MSIX_FLAGS_BIRMASK definition
  nfsd: Drop BUG_ON and ignore SECLABEL on absent filesystem
  crypto: ixp4xx - Remove bogus BUG_ON on scattered dst buffer
  xen-blkfront: don't add indirect pages to list when !feature_persistent
  xen-blkback: replace work_pending with work_busy in purge_persistent_gnt()
  USB: sierra: add 1199:68AB device ID
  regmap: regcache-rbtree: Clean new present bits on present bitmap resize
  target/iscsi: Fix double free of a TUR followed by a solicited NOPOUT
  rbd: fix copyup completion race
  md/raid1: extend spinlock to protect raid1_end_read_request against 
inconsistencies
  target: REPORT LUNS should return LUN 0 even for dynamic ACLs
  MIPS: Fix sched_getaffinity with MT FPAFF enabled
  xhci: fix off by one error in TRB DMA address boundary check
  perf: Fix fasync handling on inherited events
  mm, vmscan: Do not wait for page writeback for GFP_NOFS allocations
  MIPS: Make set_pte() SMP safe.
  ipc: modify message queue accounting to not take kernel data structures into 
account
  ocfs2: fix BUG in ocfs2_downconvert_thread_do_work()
  fsnotify: fix oops in fsnotify_clear_marks_by_group_flags()
  KVM: x86: Use adjustment in guest cycles when handling MSR_IA32_TSC_ADJUST
  localmodconfig: Use Kbuild files too
  dm thin metadata: delete btrees when releasing metadata snapshot
  dm btree: add ref counting ops for the leaves of top level btrees
  drm/radeon: add new OLAND pci id
  libiscsi: Fix host busy blocking during connection teardown
  libfc: Fix fc_exch_recv_req() error path
  libfc: Fix fc_fcp_cleanup_each_cmd()
  EDAC, ppc4xx: Access mci->csrows array elements properly
  crypto: caam - fix memory corruption in ahash_final_ctx
  mm/hwpoison: fix page refcount of unknown non LRU page
  ipc,sem: fix use after free on IPC_RMID after a task using same semaphore set 
exits
  ipc/sem.c: change memory barrier in sem_lock() to smp_rmb()
  ipc/sem.c: update/correct memory barriers
  Add factory recertified Crucial M500s to blacklist
  arm64: KVM: Fix host crash when injecting a fault into a 32bit guest
  batman-adv: protect tt_local_entry from concurrent delete events
  ip6_gre: release cached dst on tunnel removal
  net: Fix RCU splat in af_key
  rds: fix an integer overflow test in rds_info_getsockopt()
  udp: fix dst races with multicast early demux
  sparc64: Fix userspace FPU register corruptions.
  ipv6: lock socket in ip6_datagram_connect()
  rtnetlink: verify IFLA_VF_INFO attributes before passing them to driver
  net/tipc: initialize security state for new connection socket
  net: pktgen: fix race between pktgen_thread_worker() and kthread_stop()
  net: call rcu_read_lock early in process_backlog
  net: Fix skb csum races when peeking
  netlink: don't hold mutex in rcu callback when releasing mmapd ring
  Linux 3.13.11-ckt27

  The following patches from 3.13.11-ckt27 were already applied to the
  Trusty kernel:

  net: Fix skb_set_peeked use-after-free bug
  net: gso: use feature flag argument in all protocol gso handlers

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

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

[Kernel-packages] [Bug 1489314] Re: CVE-2015-6252

[Steve Beattie]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

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

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  CVE-2015-6252

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  Fix Committed
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 source package in Wily:
  Invalid

[Kernel-packages] [Bug 1500810] [NEW] Trusty update to 3.13.11-ckt27 stable release

[Luis Henriques]

Public bug reported:


SRU Justification

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

   git://kernel.ubuntu.com/ubuntu/linux.git

TEST CASE: TBD

   The following patches are in the 3.13.11-ckt27 stable release:

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

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Trusty update to 3.13.11-ckt27 stable release

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

Bug description:
  
  SRU Justification

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

 git://kernel.ubuntu.com/ubuntu/linux.git

  TEST CASE: TBD

 The following patches are in the 3.13.11-ckt27 stable release:

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

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

[Kernel-packages] [Bug 1492368] Re: Calls made through car bluetooth drop out

[Marc Vanhoomissen]

Some update on this: I can normally answer incoming calls.  However, during a 
call, I can never access activate the handset to press buttons (like '3' to 
suppress a message). 
 When battery is low, however, the calls disconnects very rapidly and the phone 
is locked if I try to reboot it.  Only possibility is to fully charge the 
battery and then to reboot (eventullay reset).

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

Title:
  Calls made through car bluetooth drop out

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Calls made through car bluetooth connection always drop out after
  about 3 minutes. The phone becomes unusable and I have to hold the
  power button for 15 seconds to reboot it. Car is Skoda Octavia.

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

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

[Kernel-packages] [Bug 1436940] Re: Atheros wifi 168c:0041(QCA6174) is not supported

[robert]

Miles:
Here's a thread that might explain the situation, more device ID's requiring 
specific folders for FW.

http://lists.infradead.org/pipermail/ath10k/2015-August/005752.html

I'm using the Next Kernel, 4.3 rc3, and the chipset you have works fine,
I compiled it using the 3rd section of these instructions. On;y
exception is I did it on my desktop and did not move source to
/usr/src/, which is what Linus recommends, then just install the header
and image deb's with dpkg -i headers.deb FIRST

http://www.linuxquestions.org/questions/showthread.php?p=5414186

With a new kernel from; obtained here;
https://www.kernel.org/

Bob 
Las Vegas

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

Title:
  Atheros wifi 168c:0041(QCA6174) is not supported

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in linux source package in Wily:
  Confirmed

Bug description:
  The atheros wireless device (168c:0041) isn't supported by the
  ath10k_pci kernel driver.

  Found in several laptop models:

  Lenovo Z70
  Lenovo G50-45
  Lenovo G50-80
  Lenovo Edge 15
  Lenovo Yoga 3 11
  Lenovo Flex 3-1470
  Samsung ATIV Book 9 NP930X2K

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-9-generic 3.19.0-9.9
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicholas   1695 F pulseaudio
   /dev/snd/controlC1:  nicholas   1695 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 26 09:47:16 2015
  HibernationDevice: RESUME=UUID=5b068cd8-e60a-49b9-a88e-1581bb6b3dc1
  InstallationDate: Installed on 2015-03-25 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 003: ID 5986:0652 Acer, Inc
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80E5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=e52867c5-0b50-42fb-8288-f30765f926c5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-9-generic N/A
   linux-backports-modules-3.19.0-9-generic  N/A
   linux-firmware1.143SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-03-26 (0 days ago)
  dmi.bios.date: 06/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN69WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN69WW:bd06/20/2014:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.name: 80E5
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1500046] Re: Boot pauses for 2 minutes after upgrade to wily

[Tony Middleton]

I will update BIOS as requested but I won't be able to do that for a
couple of days.

In the meantime I must apologise as I haven't mentioned that there is
another delay of about 40s as shown here

[  122.281863] md: raid4 personality registered for level 4
[  122.287699] md: raid10 personality registered for level 10
[  122.326579] EXT4-fs (md3): mounted filesystem with ordered data mode. Opts: 
(null)
[  167.081506] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
[  167.099649] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
[  167.099847] systemd[1]: Detected architecture x86-64.
[  167.101419] systemd[1]: Set hostname to .

On the screen there are a number of messages about running scripts in /scripts 
the last one before the delay being
/scripts/init-bottom

Also, today I took out LVM temporarily and both of these problems went
away and I booted in 18s.  When I put LVM back the problems came back.

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

Title:
  Boot pauses for 2 minutes after upgrade to wily

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrade to wily the boot process pauses for two minutes before
  continuing.

  systemd-analyse shows

  Startup finished in 16.356s (firmware) + 2.898s (loader) + 2min
  46.836s (kernel) + 16.298s (userspace) = 3min 22.389s

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tony   2547 F pulseaudio
   /dev/snd/controlC0:  tony   2547 F pulseaudio
  Date: Sat Sep 26 16:17:33 2015
  HibernationDevice: RESUME=UUID=925ed755-51a9-4968-ab9d-1a8c4c0cc93c
  InstallationDate: Installed on 2015-06-12 (106 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=f32dfa71-d154-4f81-9515-bef34b96bc2a ro nomdmonddf nomdmonisw
  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.2.0-11-generic N/A
   linux-backports-modules-4.2.0-11-generic  N/A
   linux-firmware1.148
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85X-UP4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF2:bd08/31/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A85X-UP4:rvrx.x: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/1500046/+subscriptions

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

[Kernel-packages] [Bug 1497627] Re: Periodically video will freeze for no reason at all and no specific time between freezes.

[Christopher M. Penalver]

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

** Tags added: regression-potential vivid

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

Title:
  Periodically video will freeze for no reason at all and no specific
  time between freezes.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What I expect to happen is the video to not freeze every so often.
  What happened is that the video froze. This has been going on for over a 
year. It doesn't matter if I have any applications open such as Evolution or 
Firefox. It could happen any time during the day when I'm working on the 
computer or during the night when it's the most idle. Once the video freezes 
the cursor can still be moved around the desktop however clicking on anything 
does not work. During this time all background process and cronjobs continue to 
run.

  ---
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  2095 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bb329dc0-0642-4b6a-876a-12c2f02fb7f6
  InstallationDate: Installed on 2014-10-24 (332 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 780
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=4254a7e9-429b-4f53-a08c-ae7ff839b98f ro drm.debug=0xe plymouth:debug
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-63-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/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0C27VV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: LE0006476
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1500094] Re: Asus UX303LB: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event

[Christopher M. Penalver]

Nuno, to advise, you don't need to apport-collect further unless
specifically asked to do so.

Despite this, could you please test the latest upstream kernel available
from the very top line at the top of the page from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release
names are irrelevant for testing, and please do not test the daily
folder)? Install instructions are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow
additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this
report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

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

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

** Description changed:

- Hello Community,
+ It seems brightness keys don't work with Ubuntu 15.04 for laptop Asus
+ Zenbook UX303LB. Also acpi_listen does not detect fn+f5 and fn+f6
  
- It seems brightness keys don't work with Ubuntu 15.04 for laptop Asus
- Zenbook UX303LB.
- 
- sudo dmidecode -s bios-version
- UX303LB.203
- 
- also acpi_listen does not detect fn+f5 and fn+f6
- 
- Please fix this.
- --- 
+ ---
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  nuno   1550 F pulseaudio
-  /dev/snd/pcmC1D0p:   nuno   1550 F...m pulseaudio
-  /dev/snd/controlC1:  nuno   1550 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  nuno   1689 F pulseaudio
+  /dev/snd/controlC0:  nuno   1689 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=b6aebadc-8f37-49d3-bd1e-e0171ac4c1ab
- InstallationDate: Installed on 2015-09-24 (2 days ago)
+ InstallationDate: Installed on 2015-09-24 (5 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 064e:9700 Suyin Corp.
+  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed 
root=UUID=a195a7ac-d5d1-4d1e-ab13-199a8b8533bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  RelatedPackageVersions:
-  linux-restricted-modules-3.19.0-28-generic N/A
-  linux-backports-modules-3.19.0-28-generic  N/A
-  linux-firmware 1.143.3
- Tags:  vivid
- UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
- Uname: Linux 3.19.0-28-generic x86_64
- UpgradeStatus: No upgrade log present (probably fresh install)
- UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
- _MarkForUpload: True
- dmi.bios.date: 03/17/2015
- dmi.bios.vendor: American Megatrends Inc.
- dmi.bios.version: UX303LB.203
- dmi.board.asset.tag: ATN12345678901234567
- dmi.board.name: UX303LB
- 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.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
- dmi.product.name: UX303LB
- dmi.product.version: 1.0
- dmi.sys.vendor: ASUSTeK COMPUTER INC.
- --- 
- ApportVersion: 2.17.2-0ubuntu1.5
- Architecture: amd64
- AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  nuno   1689 F pulseaudio
-  /dev/snd/controlC0:  nuno   1689 F pulseaudio
- CurrentDesktop: Unity
- DistroRelease: Ubuntu 15.04
- HibernationDevice: RESUME=UUID=b6aebadc-8f37-49d3-bd1e-e0171ac4c1ab
- InstallationDate: Installed on 2015-09-24 

[Kernel-packages] [Bug 1492632] Re: [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA

[Peter Matulis]

The last kernel brought me back to my corrupted display.

I had to re-install for other reasons and I started back with the first
kernel I tried that didn't give me any grief: 4.3-rc1

However, for some reason my display started to freeze up. My mouse
pointer would move, I could manage it over SSH, and my apps would be
functioning but I could not interact with the desktop. The log I found
is pasted below.

I have since gone back to Joe's last kernel of Sept 22 ( comment #35 )
and so far so good.


[  702.086313] [ cut here ]
[  702.086355] WARNING: CPU: 2 PID: 0 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_uncore.c:620 
hsw_unclaimed_reg_debug.isra.14+0x70/0x90 [i915]()
[  702.086357] Unclaimed register detected before reading register 0x23a0
[  702.086358] Modules linked in: ctr ccm rfcomm bnep arc4 asus_nb_wmi asus_wmi 
sparse_keymap iwlmvm intel_rapl mac80211 x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm iwlwifi uvcvideo btusb videobu
f2_vmalloc snd_soc_rt5640 videobuf2_memops btrtl serio_raw videobuf2_core 
v4l2_common snd_soc_rl6231 cfg80211 btbcm btintel snd_hda_codec_hdmi 
snd_soc_core intel_pch_thermal snd_hda_codec_conexant snd_hda_codec_g
eneric joydev videodev input_leds snd_compress hid_multitouch ac97_bus media 
snd_pcm_dmaengine snd_hda_intel snd_seq_midi snd_seq_midi_event bluetooth 
snd_hda_codec snd_rawmidi mei_me lpc_ich snd_hda_core mei shp
chp snd_hwdep snd_pcm snd_seq processor_thermal_device intel_soc_dts_iosf 
snd_seq_device iosf_mbi snd_timer snd acpi_als elan_i2c soundcore dw_dmac 
dw_dmac_core i2c_designware_platform
[  702.086391]  kfifo_buf int3402_thermal i2c_designware_core 8250_dw 
spi_pxa2xx_platform industrialio snd_soc_sst_acpi int3400_thermal 
int340x_thermal_zone acpi_thermal_rel mac_hid acpi_pad parport_pc ppdev sunr
pc lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt 
hid_generic usbhid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper i2c_algo_
bit cryptd drm_kms_helper syscopyarea sysfillrect sysimgblt psmouse fb_sys_fops 
drm ahci libahci wmi sdhci_acpi video sdhci i2c_hid hid fjes
[  702.086414] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 
4.3.0-040300rc1-generic #201509160642
[  702.086415] Hardware name: ASUSTeK COMPUTER INC. UX303LAB/UX303LAB, BIOS 
UX303LAB.207 03/23/2015
[  702.086416]  c02c2a10 88021ed03cf8 813a5e7d 
88021ed03d40
[  702.086419]  88021ed03d30 8107a536 8802106a0078 
8802106a
[  702.086420]  8802106a0080 8802106a0078 23a0 
88021ed03d90
[  702.086422] Call Trace:
[  702.086423][] dump_stack+0x44/0x57
[  702.086430]  [] warn_slowpath_common+0x86/0xc0
[  702.086431]  [] warn_slowpath_fmt+0x4c/0x50
[  702.086434]  [] ? load_balance+0x19e/0x920
[  702.086447]  [] hsw_unclaimed_reg_debug.isra.14+0x70/0x90 
[i915]
[  702.086458]  [] gen6_read32+0x5f/0x1a0 [i915]
[  702.086468]  [] ? gen8_write32+0x10a/0x1b0 [i915]
[  702.086479]  [] intel_lrc_irq_handler+0x38/0x230 [i915]
[  702.086486]  [] gen8_gt_irq_handler+0x246/0x250 [i915]
[  702.086492]  [] gen8_irq_handler+0x7c/0x520 [i915]
[  702.086495]  [] handle_irq_event_percpu+0x39/0x180
[  702.086497]  [] handle_irq_event+0x45/0x70
[  702.086499]  [] handle_edge_irq+0x99/0x150
[  702.086501]  [] handle_irq+0x26/0x30
[  702.086503]  [] do_IRQ+0x4d/0xd0
[  702.086505]  [] common_interrupt+0x82/0x82
[  702.086506][] ? cpuidle_enter_state+0xb8/0x220
[  702.086509]  [] cpuidle_enter+0x17/0x20
[  702.086511]  [] call_cpuidle+0x32/0x60
[  702.086513]  [] ? cpuidle_select+0x13/0x20
[  702.086515]  [] cpu_startup_entry+0x25c/0x320
[  702.086517]  [] start_secondary+0x149/0x170
[  702.086518] ---[ end trace 2e1c0dbd105b85e8 ]---
[  901.168217] [drm:gen8_irq_handler [i915]] *ERROR* The master control 
interrupt lied (SDE)!
[  987.412485] [drm:gen8_irq_handler [i915]] *ERROR* The master control 
interrupt lied (SDE)!

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

Title:
  [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA

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

Bug description:
  My Asus Zenbook 303LA (UX303LA-DS51T) eventually gets a corrupted
  display. Everything repeatedly shifts horizontally. I found the
  following in the kernel log. The corruption does not have a 1:1
  relation with the occurrence of the error however.

  ===
  [   99.275807] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
base.adjusted_mode.crtc_clock (expected 138780, found 92519)
  [   99.275810] [ cut here ]
  [   99.275822] WARNING: CPU: 1 PID: 909 at 
/build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 
check_crtc_state+0x2c5/0x440 [i915]()
  [   99.275823] pipe state 

[Kernel-packages] [Bug 1494076] Re: [Feature] Please backport mei support for Sunrise Point

[Michael Marley]

Any chance of getting this one in too?

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

Title:
  [Feature] Please backport mei support for Sunrise Point

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Support for the Sunrise Point PCH has been added to the mei driver for
  linux 4.3, but it would be nice if this could be backported to Wily as
  well.

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

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

[Kernel-packages] [Bug 1500894] Re: linux: 4.2.0-13.15 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 4.2.0-13.15 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-Prepare-package-start:Tuesday, 29. September 2015 14:01 UTC
  kernel-phase-changed:Tuesday, 29. September 2015 14:01 UTC
  kernel-phase:Prepare
+ kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 15:00 UTC

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

Title:
  linux: 4.2.0-13.15 -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:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Invalid

Bug description:
  This bug is for tracking the 4.2.0-13.15 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-Prepare-package-start:Tuesday, 29. September 2015 14:01 UTC
  kernel-phase-changed:Tuesday, 29. September 2015 14:01 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 15:00 UTC

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

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

[Kernel-packages] [Bug 1500910] Re: linux-signed should also produce linux-signed-image-*-lowlatency

[Andy Whitcroft]

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

** Package changed: linux (Ubuntu) => linux-signed (Ubuntu)

** Changed in: linux-meta (Ubuntu)
   Status: New => Fix Committed

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

** Changed in: linux-meta (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: linux-meta (Ubuntu)
Milestone: None => ubuntu-15.10

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

Title:
  linux-signed should also produce linux-signed-image-*-lowlatency

Status in linux-meta package in Ubuntu:
  Fix Committed
Status in linux-signed package in Ubuntu:
  Fix Committed

Bug description:
  We are already uploading all flavours for signing by LP, it makes
  sense to produce actual binary packages from them.  These are tiny
  anyhow as they only contain the signature.

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

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

[Kernel-packages] [Bug 1498307] Re: linux-lts-vivid: 3.19.0-30.33~14.04.1 -proposed tracker

[Luis Henriques]

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


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

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

** Description changed:

  This bug is for tracking the 3.19.0-30.33~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 22. September 2015 06:01 UTC
  kernel-stable-master-bug:1498065
  kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 18:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 18:02 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:16 UTC
  kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:04 UTC
  kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:04 
UTC
  kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:04 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:04 UTC
  kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:01 UTC
  kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:01 UTC
  kernel-stable-Verification-testing-end:Friday, 25. September 2015 16:08 UTC
- kernel-stable-phase:CopyToUpdates
  kernel-stable-Promote-to-updates-start:Monday, 28. September 2015 18:01 UTC
- kernel-stable-phase-changed:Monday, 28. September 2015 18:01 UTC
  kernel-stable-Certification-testing-end:Monday, 28. September 2015 18:01 UTC
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Tuesday, 29. September 2015 14:13 UTC
+ kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 14:12 UTC

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

Title:
  linux-lts-vivid: 3.19.0-30.33~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 22. September 2015 06:01 UTC
  kernel-stable-master-bug:1498065
  kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 18:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 18:02 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:16 UTC
  kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:04 UTC
  kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:04 
UTC
  kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:04 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:04 UTC
  kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:01 UTC
  kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:01 UTC
  kernel-stable-Verification-testing-end:Friday, 25. September 2015 16:08 UTC
  kernel-stable-Promote-to-updates-start:Monday, 28. September 2015 18:01 UTC
  kernel-stable-Certification-testing-end:Monday, 28. September 2015 18:01 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 29. September 2015 14:13 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 14:12 UTC

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

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

[Kernel-packages] [Bug 1500910] Re: linux-signed should also produce linux-signed-image-*-lowlatency

[Andy Whitcroft]

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

Title:
  linux-signed should also produce linux-signed-image-*-lowlatency

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  We are already uploading all flavours for signing by LP, it makes
  sense to produce actual binary packages from them.  These are tiny
  anyhow as they only contain the signature.

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

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

[Kernel-packages] [Bug 1494481] Re: linux-image Suggests cripples old kernel cleanup

[Andy Whitcroft]

Seems this got fixed in Debian, and we have since sync'd:

systemtap (2.3-2) unstable; urgency=low

  * Don't Suggest linux-* since that won't guarantee right version anyway
(Closes: #724561, #735459).


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

** Changed in: linux-meta (Ubuntu)
   Status: Triaged => Invalid

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

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

Title:
  linux-image Suggests cripples old kernel cleanup

Status in linux package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in systemtap package in Ubuntu:
  Fix Released

Bug description:
  Old kernels are not being autoremoved in spite of being marked auto
  and not being in APT::NeverAutoRemove. Debugging with the
  pkgAutoRemove "true";  option of APT I can see lines like this:

  Following dep: systemtap:amd64 2.3-1ubuntu1 Suggests linux-image:amd64 , 
provided by linux-image-3.2.0-63-generic:amd64 3.2.0-63.95
  Marking: linux-image-3.2.0-63-generic:amd64 3.2.0-63.95, Curr=3.2.0-63.95, 
Inst=3.2.0-63.95

  I can confirm that removing (or marking as auto) systemtap fix the
  issue.

  root # apt-mark auto systemtap
  systemtap set to automatically installed.
  root # apt-get autoremove
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
libdw1 linux-headers-3.13.0-29 linux-headers-3.13.0-29-generic
linux-headers-3.13.0-30 linux-headers-3.13.0-30-generic
linux-headers-3.13.0-32 linux-headers-3.13.0-32-generic
linux-headers-3.13.0-33 linux-headers-3.13.0-33-generic
linux-headers-3.13.0-34 linux-headers-3.13.0-34-generic
linux-headers-3.13.0-35 linux-headers-3.13.0-35-generic
linux-headers-3.13.0-36 linux-headers-3.13.0-36-generic
linux-headers-3.13.0-37 linux-headers-3.13.0-37-generic
linux-headers-3.13.0-39 linux-headers-3.13.0-39-generic
linux-headers-3.13.0-40 linux-headers-3.13.0-40-generic
linux-headers-3.13.0-43 linux-headers-3.13.0-43-generic
linux-headers-3.13.0-44 linux-headers-3.13.0-44-generic
linux-headers-3.13.0-46 linux-headers-3.13.0-46-generic
linux-headers-3.13.0-48 linux-headers-3.13.0-48-generic
linux-headers-3.13.0-49 linux-headers-3.13.0-49-generic
linux-headers-3.13.0-51 linux-headers-3.13.0-51-generic
linux-headers-3.13.0-52 linux-headers-3.13.0-52-generic
linux-headers-3.13.0-53 linux-headers-3.13.0-53-generic
linux-headers-3.13.0-54 linux-headers-3.13.0-54-generic
linux-headers-3.13.0-55 linux-headers-3.13.0-55-generic
linux-headers-3.13.0-58 linux-headers-3.13.0-58-generic
linux-headers-3.13.0-59 linux-headers-3.13.0-59-generic
linux-headers-3.13.0-61 linux-headers-3.13.0-61-generic
linux-image-3.13.0-29-generic linux-image-3.13.0-30-generic
linux-image-3.13.0-32-generic linux-image-3.13.0-33-generic
linux-image-3.13.0-34-generic linux-image-3.13.0-35-generic
linux-image-3.13.0-36-generic linux-image-3.13.0-37-generic
linux-image-3.13.0-39-generic linux-image-3.13.0-40-generic
linux-image-3.13.0-43-generic linux-image-3.13.0-44-generic
linux-image-3.13.0-46-generic linux-image-3.13.0-48-generic
linux-image-3.13.0-49-generic linux-image-3.13.0-51-generic
linux-image-3.13.0-52-generic linux-image-3.13.0-53-generic
linux-image-3.13.0-54-generic linux-image-3.13.0-55-generic
linux-image-3.13.0-58-generic linux-image-3.13.0-59-generic
linux-image-3.13.0-61-generic systemtap systemtap-common systemtap-runtime
  0 upgraded, 0 newly installed, 73 to remove and 88 not upgraded.
  After this operation, 2,740 MB disk space will be freed.

  
  # lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

   # apt-cache policy systemtap
  systemtap:
Installed: 2.3-1ubuntu1
Candidate: 2.3-1ubuntu1
Version table:
   *** 2.3-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

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

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

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

[Luis Henriques]

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


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

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

** Description changed:

  This bug is for tracking the 3.13.0-65.105~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 22. September 2015 04:03 UTC
  kernel-stable-master-bug:1498108
  kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 20:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 20:01 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 23. September 2015 20:22 UTC
  kernel-stable-Verification-testing-start:Wednesday, 23. September 2015 22:01 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 23. September 2015 22:01 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 23. September 2015 22:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 23. September 2015 22:01 UTC
  kernel-stable-Security-signoff-end:Thursday, 24. September 2015 08:01 UTC
  kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:01 UTC
  kernel-stable-Certification-testing-end:Friday, 25. September 2015 09:01 UTC
- kernel-stable-phase:CopyToUpdates
- kernel-stable-phase-changed:Friday, 25. September 2015 16:08 UTC
  kernel-stable-Promote-to-updates-start:Friday, 25. September 2015 16:08 UTC
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Tuesday, 29. September 2015 14:08 UTC
+ kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 14:08 UTC

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

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

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 22. September 2015 04:03 UTC
  kernel-stable-master-bug:1498108
  kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 20:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 20:01 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 23. September 2015 20:22 UTC
  kernel-stable-Verification-testing-start:Wednesday, 23. September 2015 22:01 
UTC
  kernel-stable-Certification-testing-start:Wednesday, 23. September 2015 22:01 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 23. September 2015 22:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 23. September 2015 22:01 UTC
  kernel-stable-Security-signoff-end:Thursday, 24. September 2015 08:01 UTC
  kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:01 UTC
  kernel-stable-Certification-testing-end:Friday, 25. September 2015 09:01 UTC
  kernel-stable-Promote-to-updates-start:Friday, 25. September 2015 16:08 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 29. September 2015 14:08 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 29. September 2015 14:08 UTC

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

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

[Kernel-packages] [Bug 1500906] [NEW] bluetooth Lenovo G700 i3 BCM43142

[Sebastian]

Public bug reported:

Bluetooth doesnt work (BCM43142)

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: bluetooth 4.101-0ubuntu25
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep 29 16:15:44 2015
InstallationDate: Installed on 2015-09-29 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
InterestingModules: bluetooth
MachineType: LENOVO 20251
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed 
root=UUID=06643f5a-4614-47f3-a3c5-a1d0f3fea64f ro quiet splash vt.handoff=7
SourcePackage: bluez
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 7ACN89WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Ginkgo 7A
dmi.board.vendor: LENOVO
dmi.board.version: 3193WIN8 STD MLT
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G700
dmi.modalias: 
dmi:bvnLENOVO:bvr7ACN89WW:bd11/19/2013:svnLENOVO:pn20251:pvrLenovoG700:rvnLENOVO:rnGinkgo7A:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG700:
dmi.product.name: 20251
dmi.product.version: Lenovo G700
dmi.sys.vendor: LENOVO
hciconfig:

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


** Tags: amd64 apport-bug vivid

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

Title:
  bluetooth Lenovo G700 i3 BCM43142

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth doesnt work (BCM43142)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bluetooth 4.101-0ubuntu25
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 29 16:15:44 2015
  InstallationDate: Installed on 2015-09-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterestingModules: bluetooth
  MachineType: LENOVO 20251
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed 
root=UUID=06643f5a-4614-47f3-a3c5-a1d0f3fea64f ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7ACN89WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Ginkgo 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G700
  dmi.modalias: 
dmi:bvnLENOVO:bvr7ACN89WW:bd11/19/2013:svnLENOVO:pn20251:pvrLenovoG700:rvnLENOVO:rnGinkgo7A:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG700:
  dmi.product.name: 20251
  dmi.product.version: Lenovo G700
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Kernel-packages] [Bug 1500910] [NEW] linux-signed should also produce linux-signed-image-*-lowlatency

[Andy Whitcroft]

Public bug reported:

We are already uploading all flavours for signing by LP, it makes sense
to produce actual binary packages from them.  These are tiny anyhow as
they only contain the signature.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Andy Whitcroft (apw)
 Status: Triaged

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-15.10

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

Title:
  linux-signed should also produce linux-signed-image-*-lowlatency

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We are already uploading all flavours for signing by LP, it makes
  sense to produce actual binary packages from them.  These are tiny
  anyhow as they only contain the signature.

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

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

[Kernel-packages] [Bug 1500094] Re: Asus UX303LB: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event

[Nuno]

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

Title:
  Asus UX303LB: Brightness keys Fn+F5 and Fn+F6 don't generate evdev
  event

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It seems brightness keys don't work with Ubuntu 15.04 for laptop Asus
  Zenbook UX303LB. Also acpi_listen does not detect fn+f5 and fn+f6

  ---
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nuno   1689 F pulseaudio
   /dev/snd/controlC0:  nuno   1689 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=b6aebadc-8f37-49d3-bd1e-e0171ac4c1ab
  InstallationDate: Installed on 2015-09-24 (5 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 064e:9700 Suyin Corp.
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LB
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed 
root=UUID=a195a7ac-d5d1-4d1e-ab13-199a8b8533bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-28-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/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LB.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LB
  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.:bvrUX303LB.206:bd08/24/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX303LB
  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/1500094/+subscriptions

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

[Kernel-packages] [Bug 1499712] Re: linux: 4.2.0-12.14 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 4.2.0-12.14 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-Prepare-package-start:Friday, 25. September 2015 12:35 UTC
  kernel-phase-changed:Friday, 25. September 2015 12:35 UTC
  kernel-phase:Prepare
+ kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 16:31 UTC

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

Title:
  linux: 4.2.0-12.14 -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:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Invalid

Bug description:
  This bug is for tracking the 4.2.0-12.14 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-Prepare-package-start:Friday, 25. September 2015 12:35 UTC
  kernel-phase-changed:Friday, 25. September 2015 12:35 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 16:31 UTC

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

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

[Kernel-packages] [Bug 1499712] Re: linux: 4.2.0-12.14 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: Incomplete => New

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

Title:
  linux: 4.2.0-12.14 -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:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Invalid

Bug description:
  This bug is for tracking the 4.2.0-12.14 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-Prepare-package-start:Friday, 25. September 2015 12:35 UTC
  kernel-phase-changed:Friday, 25. September 2015 12:35 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 16:31 UTC

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

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

[Kernel-packages] [Bug 1499712] Re: linux: 4.2.0-12.14 -proposed tracker

[Brad Figg]

Here's the relevant information:

wily linux 4.2.0-12.14 REGRESSION blktap-dkms 2.0.93-0.3ubuntu6
REGRESSION

Please verify DKMS test results in
https://people.canonical.com/~kernel/status/dashboard-helper/proposed-
migration/regressions.txt


** Description changed:

  This bug is for tracking the 4.2.0-12.14 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-Prepare-package-start:Friday, 25. September 2015 12:35 UTC
  kernel-phase-changed:Friday, 25. September 2015 12:35 UTC
  kernel-phase:Prepare
- kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 16:31 UTC
+ kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 14:31 UTC

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: New => Fix Released

** Changed in: kernel-development-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-development-workflow/automated-testing
   Status: Confirmed => Incomplete

** Description changed:

  This bug is for tracking the 4.2.0-12.14 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-Prepare-package-start:Friday, 25. September 2015 12:35 UTC
  kernel-phase-changed:Friday, 25. September 2015 12:35 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 14:31 UTC
+ proposed-announcement-sent:True

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

Title:
  linux: 4.2.0-12.14 -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 linux package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Invalid

Bug description:
  This bug is for tracking the 4.2.0-12.14 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-Prepare-package-start:Friday, 25. September 2015 12:35 UTC
  kernel-phase-changed:Friday, 25. September 2015 12:35 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 14:31 UTC
  proposed-announcement-sent:True

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

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

[Kernel-packages] [Bug 1500936] Re: BUG: unable to handle kernel NULL pointer dereference at (null)

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at   (null)

Status in linux package in Ubuntu:
  New

Bug description:
  ???

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.19-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyle   2132 F pulseaudio
  Date: Tue Sep 29 11:34:55 2015
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at  
 (null) EIP: location drm_mode_rmfb+0x68/0xe0 [drm] SS:ESP 0068:ecc6de38
  Failure: oops
  HibernationDevice: RESUME=UUID=48abdd36-9eda-4cba-a2e9-2f13909886bd
  InstallationDate: Installed on 2015-09-19 (9 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: Dell Inc. OptiPlex 210L
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=e1b8088b-e11d-42a2-9a59-1b8573ea7252 ro plymouth:debug splash quiet 
drm.debug=0xe
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  RfKill:
   0: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at   (null)
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0HC918
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd03/29/2006:svnDellInc.:pnOptiPlex210L:pvr:rvnDellInc.:rn0HC918:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 210L
  dmi.sys.vendor: Dell Inc.

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

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

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at   (null)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ???

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.19-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyle   2132 F pulseaudio
  Date: Tue Sep 29 11:34:55 2015
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at  
 (null) EIP: location drm_mode_rmfb+0x68/0xe0 [drm] SS:ESP 0068:ecc6de38
  Failure: oops
  HibernationDevice: RESUME=UUID=48abdd36-9eda-4cba-a2e9-2f13909886bd
  InstallationDate: Installed on 2015-09-19 (9 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: Dell Inc. OptiPlex 210L
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=e1b8088b-e11d-42a2-9a59-1b8573ea7252 ro plymouth:debug splash quiet 
drm.debug=0xe
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  RfKill:
   0: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at   (null)
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0HC918
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd03/29/2006:svnDellInc.:pnOptiPlex210L:pvr:rvnDellInc.:rn0HC918:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 210L
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1492632] Re: [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA

[Joseph Salisbury]

I built the next test kernel up to the following commit:
66c826a1754c07012e29fbe9be7013e92a5acbac

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

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

Title:
  [Ubuntu 15.10] Intel Display i915 driver crashes, Asus Zenbook 303LA

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

Bug description:
  My Asus Zenbook 303LA (UX303LA-DS51T) eventually gets a corrupted
  display. Everything repeatedly shifts horizontally. I found the
  following in the kernel log. The corruption does not have a 1:1
  relation with the occurrence of the error however.

  ===
  [   99.275807] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
base.adjusted_mode.crtc_clock (expected 138780, found 92519)
  [   99.275810] [ cut here ]
  [   99.275822] WARNING: CPU: 1 PID: 909 at 
/build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 
check_crtc_state+0x2c5/0x440 [i915]()
  [   99.275823] pipe state doesn't match!
  [   99.275824] Modules linked in: bnep arc4 asus_nb_wmi asus_wmi 
sparse_keymap intel_rapl x86_pkg_temp_thermal iwlmvm intel_powerclamp coretemp 
mac80211 snd_soc_rt5640 kvm_intel snd_soc_rl6231 snd_soc_core kvm uv
  cvideo snd_compress ac97_bus snd_hda_codec_hdmi snd_pcm_dmaengine 
snd_hda_codec_conexant videobuf2_vmalloc snd_hda_codec_generic snd_seq_midi 
iwlwifi videobuf2_memops btusb snd_seq_midi_event serio_raw videobuf2_
  core snd_rawmidi btrtl btbcm snd_hda_intel v4l2_common btintel videodev 
snd_hda_codec cfg80211 lpc_ich bluetooth snd_hda_core input_leds joydev mei_me 
hid_multitouch media snd_hwdep mei shpchp snd_pcm processor_t
  hermal_device intel_soc_dts_iosf iosf_mbi snd_seq snd_seq_device snd_timer 
snd soundcore snd_soc_sst_acpi acpi_pad dw_dmac acpi_als int3402_thermal 
i2c_designware_platform dw_dmac_core
  [   99.275856]  kfifo_buf i2c_designware_core 8250_dw spi_pxa2xx_platform 
industrialio int3400_thermal int340x_thermal_zone mac_hid acpi_thermal_rel 
sunrpc parport_pc ppdev lp parport autofs4 jitterentropy_rng dr
  bg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid psmouse 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel aes_x86_64 
lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_k
  ms_helper ahci drm libahci wmi sdhci_acpi video sdhci i2c_hid hid
  [   99.275877] CPU: 1 PID: 909 Comm: Xorg Not tainted 4.2.0-7-generic 
#7-Ubuntu
  [   99.275878] Hardware name: ASUSTeK COMPUTER INC. UX303LAB/UX303LAB, BIOS 
UX303LAB.203 12/11/2014
  [   99.275879]  c02ce1e8 8800d3a977e8 817b0465 

  [   99.275881]  8800d3a97838 8800d3a97828 81076536 
8800d3a97858
  [   99.275883]  8800d3a978c0 8800d374f800 0001 
8800d374fb50
  [   99.275885] Call Trace:
  [   99.275890]  [] dump_stack+0x45/0x57
  [   99.275893]  [] warn_slowpath_common+0x86/0xc0
  [   99.275895]  [] warn_slowpath_fmt+0x46/0x50
  [   99.275906]  [] ? intel_pipe_config_compare+0xb08/0xc60 
[i915]
  [   99.275916]  [] check_crtc_state+0x2c5/0x440 [i915]
  [   99.275929]  [] intel_modeset_check_state+0x20e/0x6b0 
[i915]
  [   99.275940]  [] intel_crtc_set_config+0x4c7/0x580 [i915]
  [   99.275951]  [] ? drm_mode_create+0x25/0x60 [drm]
  [   99.275959]  [] drm_mode_set_config_internal+0x66/0x100 
[drm]
  [   99.275967]  [] drm_mode_setcrtc+0x3a8/0x4c0 [drm]
  [   99.275973]  [] drm_ioctl+0x125/0x610 [drm]
  [   99.275980]  [] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
  [   99.275983]  [] do_vfs_ioctl+0x285/0x470
  [   99.275986]  [] ? recalc_sigpending+0x1f/0x60
  [   99.275988]  [] ? __set_task_blocked+0x32/0x70
  [   99.275990]  [] SyS_ioctl+0x79/0x90
  [   99.275992]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [   99.275994] ---[ end trace 6172e2f40143dd37 ]---
  ===

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1151 F pulseaudio
   /dev/snd/controlC1:  peter  1151 F pulseaudio
  Date: Sat Sep  5 15:15:04 2015
  InstallationDate: Installed on 2015-07-05 (62 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150704)
  MachineType: ASUSTeK COMPUTER INC. UX303LAB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic 
root=UUID=9b60dccb-1ce9-4ddf-82f6-cc03b3c01b5c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1497812] Re: i40e bug: non physical MAC outbound frames appear as copied back inbound (mirrored)

[Jay Vosburgh]

Just looking at the log, it might be this:

commit fa11cb3d16a9b9b296a2b811a49faf1356240348
Author: Anjali Singhai Jain 
Date:   Wed May 27 12:06:14 2015 -0400

i40e: Make sure to be in VEB mode if SRIOV is enabled at probe

If SRIOV is enabled we need to be in VEB mode not VEPA mode at probe.
This fixes an NPAR bug when SRIOV is enabled in the BIOS.

Change-ID: Ibf006abafd9a0ca3698ec24848cd771cf345cbbc
Signed-off-by: Anjali Singhai Jain 
Tested-by: Jim Young 
Signed-off-by: Jeff Kirsher 

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

Title:
  i40e bug: non physical MAC outbound frames appear as copied back
  inbound  (mirrored)

Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-vivid package in Ubuntu:
  Confirmed

Bug description:
  Using 3.19.0-28-generic #30~14.04.1-Ubuntu with stock i40e
  driver version 2.2.2-k makes every 'non physical' MAC output
  frame appear as copied back at input, as if the switch was
  doing frame 'mirroring' (and/or hair-pinning).

  FYI same setup, with i40e upgraded to 1.2.48 from
  http://downloadmirror.intel.com/25282/eng/i40e-1.2.48.tar.gz
  behaves OK, fyi also we did a port mirroring setup at
  the switch directed to a different physical port for debugging,
  and didn't observe these frames to be physically present.

  See tcpdump -P in/out and more details at
  http://paste.ubuntu.com/12511680/

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  Date: Mon Sep 21 02:05:28 2015
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1481490] Re: Add sfc to nic-modules udeb

[Dave Chiluk]

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: debian-installer (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: debian-installer (Ubuntu Trusty)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

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

Title:
  Add sfc to nic-modules udeb

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  In Progress
Status in linux source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released

Bug description:
  == [Trusty][Vivid]SRU Justification ==

  It is being requested that we add the sfc driver to the nic-modules
  udeb to facilitate PXE booting nodes with Solarflare network adapters.

  == Fix ==
  Add the sfc driver to our nic-modules udeb.  This is being requested for
  Trusty and Vivid.  Note, this has already been applied to Wily master-next.

  == Testing ==
  I've done test builds of Wily, Vivid, and Trusty and can confirm the sfc 
driver is seeded into the nic-modules udeb:

  $ dpkg -c nic-modules-4.2.0-3-generic-di_4.2.0-3.3_amd64.udeb | grep "sfc.ko"
  -rw-r--r-- root/root495305 2015-08-04 22:17 
./lib/modules/4.2.0-3-generic/kernel/drivers/net/ethernet/sfc/sfc.ko

  $ dpkg -c nic-modules-3.19.0-26-generic-di_3.19.0-26.27_amd64.udeb | grep 
"sfc.ko"
  -rw-r--r-- root/root464452 2015-08-04 22:21 
./lib/modules/3.19.0-26-generic/kernel/drivers/net/ethernet/sfc/sfc.ko

  $ dpkg -c nic-modules-3.13.0-62-generic-di_3.13.0-62.101_amd64.udeb | grep 
"sfc.ko"
  -rw-r--r-- root/root436284 2015-08-04 22:22 
./lib/modules/3.13.0-62-generic/kernel/drivers/net/ethernet/sfc/sfc.ko

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1481490/+subscriptions

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

[Kernel-packages] [Bug 1500046] Re: Boot pauses for 2 minutes after upgrade to wily

[Tony Middleton]

Managed to try updating after all.  I tried both the F3 and F4 BIOS and
both still had both of the delays mentioned above.  Here is the output
requested on the F3

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
F3
02/05/2013

I'm currently on F3 but both F3 & F4 cause a new problem in that my USB
keyboard/mouse isn't recognised during BIOS and GRUB.  Had to borrow a
PS/2 and if I can't find a solution will need to revert to F2.

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

Title:
  Boot pauses for 2 minutes after upgrade to wily

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrade to wily the boot process pauses for two minutes before
  continuing.

  systemd-analyse shows

  Startup finished in 16.356s (firmware) + 2.898s (loader) + 2min
  46.836s (kernel) + 16.298s (userspace) = 3min 22.389s

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tony   2547 F pulseaudio
   /dev/snd/controlC0:  tony   2547 F pulseaudio
  Date: Sat Sep 26 16:17:33 2015
  HibernationDevice: RESUME=UUID=925ed755-51a9-4968-ab9d-1a8c4c0cc93c
  InstallationDate: Installed on 2015-06-12 (106 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=f32dfa71-d154-4f81-9515-bef34b96bc2a ro nomdmonddf nomdmonisw
  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.2.0-11-generic N/A
   linux-backports-modules-4.2.0-11-generic  N/A
   linux-firmware1.148
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85X-UP4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF2:bd08/31/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A85X-UP4:rvrx.x: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/1500046/+subscriptions

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

[Kernel-packages] [Bug 1500936] [NEW] BUG: unable to handle kernel NULL pointer dereference at (null)

[Kylem]

Public bug reported:

???

ProblemType: KernelOops
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-11-generic 4.2.0-11.13
ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
Uname: Linux 4.2.0-11-generic i686
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.19-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kyle   2132 F pulseaudio
Date: Tue Sep 29 11:34:55 2015
DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at   
(null) EIP: location drm_mode_rmfb+0x68/0xe0 [drm] SS:ESP 0068:ecc6de38
Failure: oops
HibernationDevice: RESUME=UUID=48abdd36-9eda-4cba-a2e9-2f13909886bd
InstallationDate: Installed on 2015-09-19 (9 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
MachineType: Dell Inc. OptiPlex 210L
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=e1b8088b-e11d-42a2-9a59-1b8573ea7252 ro plymouth:debug splash quiet 
drm.debug=0xe
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
RfKill:
 0: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: BUG: unable to handle kernel NULL pointer dereference at   (null)
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0HC918
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd03/29/2006:svnDellInc.:pnOptiPlex210L:pvr:rvnDellInc.:rn0HC918:rvr:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 210L
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-kerneloops i386 kernel-driver-drm kernel-oops wily

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at   (null)

Status in linux package in Ubuntu:
  New

Bug description:
  ???

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.19-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyle   2132 F pulseaudio
  Date: Tue Sep 29 11:34:55 2015
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at  
 (null) EIP: location drm_mode_rmfb+0x68/0xe0 [drm] SS:ESP 0068:ecc6de38
  Failure: oops
  HibernationDevice: RESUME=UUID=48abdd36-9eda-4cba-a2e9-2f13909886bd
  InstallationDate: Installed on 2015-09-19 (9 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: Dell Inc. OptiPlex 210L
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=e1b8088b-e11d-42a2-9a59-1b8573ea7252 ro plymouth:debug splash quiet 
drm.debug=0xe
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  RfKill:
   0: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at   (null)
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0HC918
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd03/29/2006:svnDellInc.:pnOptiPlex210L:pvr:rvnDellInc.:rn0HC918:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 210L
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1240940] Re: Need support for Realtek Wifi card rtl8723be [10ec:b723]

[Ekimia]

What kernel do you use ?

Yes realtek driver inclusion in the kernel is a mess

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

Title:
  Need support for Realtek Wifi  card rtl8723be [10ec:b723]

Status in HWE Next:
  Fix Released
Status in HWE Next trusty series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released

Bug description:
  This device is appearing in some OEM machines, but driver is not yet
  available upstream.

  This bug is only for the initial support of this WiFi adapter, it's
  not working 100% well yet, please report new "not working bug" or
  contact upstream but not keep posting comments, thanks.

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

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

[Kernel-packages] [Bug 1500954] [NEW] xfs DIO data corruption

[Avi Kivity]

Public bug reported:

An appending DIO write will corrupt files on XFS.

The following patch needs to be backported:

commit b9d59846f73713d77f0f3fb784c7f84249fc2b93
Author: Dave Chinner 
Date:   Thu Apr 16 22:03:07 2015 +1000
 
xfs: DIO write completion size updates race
   
xfs_end_io_direct_write() can race with other IO completions when
updating the in-core inode size. The IO completion processing is not
serialised for direct IO - they are done either under the
IOLOCK_SHARED for non-AIO DIO, and without any IOLOCK held at all
during AIO DIO completion. Hence the non-atomic test-and-set update
of the in-core inode size is racy and can result in the in-core
inode size going backwards if the race if hit just right.
   
If the inode size goes backwards, this can trigger the EOF zeroing
code to run incorrectly on the next IO, which then will zero data
that has successfully been written to disk by a previous DIO.
   
To fix this bug, we need to serialise the test/set updates of the
in-core inode size. This first patch introduces locking around the
relevant updates and checks in the DIO path. Because we now have an
ioend in xfs_end_io_direct_write(), we know exactly then we are
doing an IO that requires an in-core EOF update, and we know that
they are not running in interrupt context. As such, we do not need to
use irqsave() spinlock variants to protect against interrupts while
the lock is held.
   
Hence we can use an existing spinlock in the inode to do this
serialisation and so not need to grow the struct xfs_inode just to
work around this problem.
   
This patch does not address the test/set EOF update in
generic_file_write_direct() for various reasons - that will be done
as a followup with separate explanation.
   
Signed-off-by: Dave Chinner 
Reviewed-by: Brian Foster 
Signed-off-by: Dave Chinner 

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-25-generic 3.19.0-25.26~14.04.1 [modified: 
boot/vmlinuz-3.19.0-25-generic]
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep 29 19:29:28 2015
InstallationDate: Installed on 2015-09-29 (0 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: linux-lts-vivid
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  xfs DIO data corruption

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  An appending DIO write will corrupt files on XFS.

  The following patch needs to be backported:

  commit b9d59846f73713d77f0f3fb784c7f84249fc2b93
  Author: Dave Chinner 
  Date:   Thu Apr 16 22:03:07 2015 +1000
   
  xfs: DIO write completion size updates race
 
  xfs_end_io_direct_write() can race with other IO completions when
  updating the in-core inode size. The IO completion processing is not
  serialised for direct IO - they are done either under the
  IOLOCK_SHARED for non-AIO DIO, and without any IOLOCK held at all
  during AIO DIO completion. Hence the non-atomic test-and-set update
  of the in-core inode size is racy and can result in the in-core
  inode size going backwards if the race if hit just right.
 
  If the inode size goes backwards, this can trigger the EOF zeroing
  code to run incorrectly on the next IO, which then will zero data
  that has successfully been written to disk by a previous DIO.
 
  To fix this bug, we need to serialise the test/set updates of the
  in-core inode size. This first patch introduces locking around the
  relevant updates and checks in the DIO path. Because we now have an
  ioend in xfs_end_io_direct_write(), we know exactly then we are
  doing an IO that requires an in-core EOF update, and we know that
  they are not running in interrupt context. As such, we do not need to
  use irqsave() spinlock variants to protect against interrupts while
  the lock is held.
 
  Hence we can use an existing spinlock in the inode to do this
  serialisation and so not need to grow the struct xfs_inode just to
  work around this problem.
 
  This patch does not address the test/set EOF update in
  generic_file_write_direct() for various reasons - that will be done
  as a followup with separate explanation.
 
  Signed-off-by: Dave Chinner 
  

[Kernel-packages] [Bug 1240940] Re: Need support for Realtek Wifi card rtl8723be [10ec:b723]

[Avirup Das]

Hi all,

I am very new to Linux and facing similar issue with RTL8723BE on HP-
15AF006AX.

At first, the system couldn't recognize any Wifi network.

Tried the rtlwifi_new. Now, the wifi does connect, but only withing a
range of 1M from router's antenna. The connection drops are very
frequent.

Next i have tried to add 'options rtl8723be fwlps=0 swlps=0' to the
"/etc/modprobe.d/rtl8723be.conf". No luck. The connection keeps
dropping.

I have Ignored the IPv6 settings and checked for the Power Management to
be 'Off'.

Are we expecting this bug to be fixed in near future? Else I might have
move back to Windows.

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

Title:
  Need support for Realtek Wifi  card rtl8723be [10ec:b723]

Status in HWE Next:
  Fix Released
Status in HWE Next trusty series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released

Bug description:
  This device is appearing in some OEM machines, but driver is not yet
  available upstream.

  This bug is only for the initial support of this WiFi adapter, it's
  not working 100% well yet, please report new "not working bug" or
  contact upstream but not keep posting comments, thanks.

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

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

[Kernel-packages] [Bug 1492466] Re: linux-lts-trusty: not split but trusty linux is leading to upgrade issues

[Andy Whitcroft]

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: In Progress => Triaged

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

Title:
  linux-lts-trusty: not split but trusty linux is leading to upgrade
  issues

Status in linux-lts-trusty package in Ubuntu:
  Triaged
Status in linux-lts-trusty source package in Precise:
  Triaged

Bug description:
  This leads to upgrade failures:

Unpacking linux-image-extra-3.13.0-63-generic (3.13.0-63.103) ...
dpkg: error processing archive 
/var/cache/apt/archives/linux-image-extra-3.13.0-63-generic_3.13.0-63.103_amd64.deb
 (--unpack): trying to overwrite  
'/lib/modules/3.13.0-63-generic/kernel/mm/hwpoison-inject.ko', which is also in 
package linux-image-3.13.0-63-generic 3.13.0-63.104~precise1

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

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

[Kernel-packages] [Bug 1481490] Re: Add sfc to nic-modules udeb

[Dave Chiluk]

** Tags added: sts

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

Title:
  Add sfc to nic-modules udeb

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  == [Trusty][Vivid]SRU Justification ==

  It is being requested that we add the sfc driver to the nic-modules
  udeb to facilitate PXE booting nodes with Solarflare network adapters.

  == Fix ==
  Add the sfc driver to our nic-modules udeb.  This is being requested for
  Trusty and Vivid.  Note, this has already been applied to Wily master-next.

  == Testing ==
  I've done test builds of Wily, Vivid, and Trusty and can confirm the sfc 
driver is seeded into the nic-modules udeb:

  $ dpkg -c nic-modules-4.2.0-3-generic-di_4.2.0-3.3_amd64.udeb | grep "sfc.ko"
  -rw-r--r-- root/root495305 2015-08-04 22:17 
./lib/modules/4.2.0-3-generic/kernel/drivers/net/ethernet/sfc/sfc.ko

  $ dpkg -c nic-modules-3.19.0-26-generic-di_3.19.0-26.27_amd64.udeb | grep 
"sfc.ko"
  -rw-r--r-- root/root464452 2015-08-04 22:21 
./lib/modules/3.19.0-26-generic/kernel/drivers/net/ethernet/sfc/sfc.ko

  $ dpkg -c nic-modules-3.13.0-62-generic-di_3.13.0-62.101_amd64.udeb | grep 
"sfc.ko"
  -rw-r--r-- root/root436284 2015-08-04 22:22 
./lib/modules/3.13.0-62-generic/kernel/drivers/net/ethernet/sfc/sfc.ko

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

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

[Kernel-packages] [Bug 1397976] Re: tty hangup regression in 3.13 kernel (trusty LTS)

[Delmic BV]

As described in comment #4, the regression that the 'fix' introduced is
still present in 3.13.0-65.105~precise1.


Should I reopen this bug report, or create a new one to track the 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/1397976

Title:
  tty hangup regression in 3.13 kernel (trusty LTS)

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-trusty source package in Trusty:
  Invalid

Bug description:
  From https://lkml.org/lkml/2014/10/10/345

  #
  Commit f95499c3030f ("n_tty: Don't wait for buffer work in read() loop")
  introduces a race window where a pty master can be signalled that the 
ptyslave was closed before all the data that the slave wrote is delivered.
  Commit f8747d4a466a ("tty: Fix pty master read() after slave closes") fixed 
theproblem in case of n_tty_read, but the problem still exists for 
n_tty_poll.This can be seen by running 'for ((i=0; i<100;i++));do ./test.py 
;done'where test.py is:

  import os, select, pty
  (pid, pty_fd) = pty.fork()

  if pid == 0:
     os.write(1, 'This string should be received by parent')
  else:
     poller = select.epoll()
     poller.register( pty_fd, select.EPOLLIN )
     ready = poller.poll( 1 * 1000 )
     for fd, events in ready:
    if not events & select.EPOLLIN:
   print 'missed POLLIN event'
    else:
   print os.read(fd, 100)
     poller.close()

  The string from the slave is missed several times.
  This patch takes the same approach as the fix for read and special casesthis 
condition for poll.
  Tested on 3.16.
  #

  This is has been merged to Linus Torvalds branch:
  
https://github.com/torvalds/linux/commit/c4dc304677e8d566572c4738d95c48be150c6606

  This would be needed to be implemented in to 3.13 kernel too. As both
  12.04 and 14.04 is currently running the Trusty LTS it affectes both.

  br,

  Björn

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

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

[Kernel-packages] [Bug 1499357] Re: 830 TI on Tuleta during IPL of Linux - bad xisr passed to PHYP

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.2.0-12.14

---
linux (4.2.0-12.14) wily; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1499712

  [ Ben Pope ]

  * SAUCE: drivers/net/ethernet/atheros/alx: Add Killer E2400 device ID
- LP: #1498633

  [ Knuth Posern ]

  * SAUCE: thunderbolt: Allow loading of module on recent Apple MacBooks
with thunderbolt 2 controller
- LP: #1497321

  [ Laurent Dufour ]

  * SAUCE: powerpc/hvsi: Fix endianness issues in the HVSI driver
- LP: #1499357

  [ Upstream Kernel Changes ]

  * x86/hyperv: Mark the Hyper-V TSC as unstable
- LP: #1498206
  * intel_pstate: fix PCT_TO_HWP macro
- LP: #1499040
  * perf/x86/intel/rapl: Add support for Knights Landing (KNL)
- LP: #1461370
  * drm/i915: Add audio pin sense / ELD callback
- LP: #1398277
  * drm/i915: Call audio pin/ELD notify function
- LP: #1398277
  * ALSA: hda - allow codecs to access the i915 pin/ELD callback
- LP: #1398277
  * ALSA: hda - Wake the codec up on pin/ELD notify events
- LP: #1398277
  * drm/i915: Add locks around audio component bind/unbind
- LP: #1398277
  * drm/i915: Drop port_mst_index parameter from pin/eld callback
- LP: #1398277

 -- Tim Gardner   Thu, 24 Sep 2015 09:19:23
-0600

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

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

Title:
  830 TI on Tuleta during IPL of Linux - bad xisr passed to PHYP

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  I looked at the dump and the assert is due to a bad xisr.  From the
  VIO trace the xisr was 01000A00.

  > ~d4a3/phypmacro/vio -globals -fr
  +-+
  | HvVioGlobals (address=800807621100) |
  +-+
   BitBucket:0x07F01A2D2000
   AssertFr: 0x07F80F394C80
   AssertEnabled:  True
   VlanMap:  0x07F807621000
   ++
   | HvVioFr (address=07F01A282800) |
   ++
[  0] HvVioInterruptAssertBadXisr  [TB] 002C2067AB1A 
01000A00   

  
  Here is the trace along with some Linux output that followed:

  Token = 34, timebase = 0x24222848
  h_hypervisor_esw_call(0x504c) rc = 0xfffc (-4)
  175: b=
  0100 0A00      0001 []
  105: get_parms_ptr=
  0100 0A00      0001 []
  GET XIVE ERROR hcall rc=fffc buff_rc=1

  [0.000517] irq: (null) didn't like hwirq-0x1000a00 to VIRQ16 mapping 
(rc=-22)
  [0.000578] hvsi_console_init: couldn't create irq mapping for 0x1000a00

  -

  I then dumped the device tree for interrupts that PFW communicates to Linux
  via the device as follows:

  1) Here are all the 'interrupt-ranges' properties found:
  0 > showprops -i interrupt-ranges 
  /ibm,platform-facilities00090400 0400
  /event-sources  0009 0008
  /interrupt-controller@8002510   37f8 0004
  /interrupt-controller@8002513   3ff8 0004
  /interrupt-controller@8002514   
  /interrupt-controller@8002515   
  /interrupt-controller@8002518   17f8 0004
  /interrupt-controller@800251b   
  /interrupt-controller@800251d   1ff8 0004
  /interrupt-controller@800251e   
  /interrupt-controller@800251f   
  /interrupt-controller@8002521   0ff8 0004
  /interrupt-controller@8002528   2ff8 0004
  /interrupt-controller@8002529   27f8 0004
  /vdevice000a 00c7 
000b 007f

  2) Here are all the 'ibm,msi-ranges' properties found:
  0 > showprops -i ibm,msi-ranges 
  /pci@8002014/ethernet@0 3be0 0001
  /pci@8002014/ethernet@0,1   3be1 0001
  /pci@8002014/ethernet@0,2   3be2 0001
  /pci@8002014/ethernet@0,3   3be3 0001
  /pci@8002015/pci1014,034A@0 3820 0001
  /pci@8002018/pci@0/pci@2/fibre-channel@01000 0001
  

[Kernel-packages] [Bug 1499712] Re: linux: 4.2.0-12.14 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 4.2.0-12.14 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-Prepare-package-start:Friday, 25. September 2015 12:35 UTC
  kernel-phase-changed:Friday, 25. September 2015 12:35 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 14:31 UTC
  proposed-announcement-sent:True
+ kernel-Promote-to-release-end:Tuesday, 29. September 2015 23:00 UTC

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

Title:
  linux: 4.2.0-12.14 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.2.0-12.14 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-Prepare-package-start:Friday, 25. September 2015 12:35 UTC
  kernel-phase-changed:Friday, 25. September 2015 12:35 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 14:31 UTC
  proposed-announcement-sent:True
  kernel-Promote-to-release-end:Tuesday, 29. September 2015 23:00 UTC

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

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

[Kernel-packages] [Bug 1498108] phact (amd64) - tests ran: 2, failed: 1

[Brad Figg]

tests ran:   2, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-65.105/phact__3.13.0-65.105__2015-09-29_20-46-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/1498108

Title:
  linux: 3.13.0-65.105 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 21. September 2015 17:41 UTC
  kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 04:04 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 04:04 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:16 UTC
  kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:02 UTC
  kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:02 
UTC
  kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:02 UTC
  kernel-stable-Certification-testing-end:Wednesday, 23. September 2015 12:00 
UTC
  kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:01 UTC
  kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:00 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-phase-changed:Friday, 25. September 2015 16:07 UTC
  kernel-stable-Promote-to-updates-start:Friday, 25. September 2015 16:07 UTC
  kernel-stable-Promote-to-updates-end:Monday, 28. September 2015 16:01 UTC

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

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

[Kernel-packages] [Bug 1498108] rukbah (amd64) - tests ran: 2, failed: 1

[Brad Figg]

tests ran:   2, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-65.105/rukbah__3.13.0-65.105__2015-09-29_20-42-00/results-index.html

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

Title:
  linux: 3.13.0-65.105 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 21. September 2015 17:41 UTC
  kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 04:04 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 04:04 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:16 UTC
  kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:02 UTC
  kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:02 
UTC
  kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:02 UTC
  kernel-stable-Certification-testing-end:Wednesday, 23. September 2015 12:00 
UTC
  kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:01 UTC
  kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:00 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-phase-changed:Friday, 25. September 2015 16:07 UTC
  kernel-stable-Promote-to-updates-start:Friday, 25. September 2015 16:07 UTC
  kernel-stable-Promote-to-updates-end:Monday, 28. September 2015 16:01 UTC

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

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

[Kernel-packages] [Bug 1499712] Re: linux: 4.2.0-12.14 -proposed tracker

[Brad Figg]

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


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

** Description changed:

  This bug is for tracking the 4.2.0-12.14 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-Prepare-package-start:Friday, 25. September 2015 12:35 UTC
- kernel-phase-changed:Friday, 25. September 2015 12:35 UTC
- kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 14:31 UTC
  proposed-announcement-sent:True
  kernel-Promote-to-release-end:Tuesday, 29. September 2015 23:00 UTC
+ kernel-phase-changed:Wednesday, 30. September 2015 00:00 UTC
+ kernel-Prepare-package-end:Wednesday, 30. September 2015 00:00 UTC
+ kernel-Package-testing-start:Wednesday, 30. September 2015 00:00 UTC
+ kernel-phase:Released

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

Title:
  linux: 4.2.0-12.14 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.2.0-12.14 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-Prepare-package-start:Friday, 25. September 2015 12:35 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 14:31 UTC
  proposed-announcement-sent:True
  kernel-Promote-to-release-end:Tuesday, 29. September 2015 23:00 UTC
  kernel-phase-changed:Wednesday, 30. September 2015 00:00 UTC
  kernel-Prepare-package-end:Wednesday, 30. September 2015 00:00 UTC
  kernel-Package-testing-start:Wednesday, 30. September 2015 00:00 UTC
  kernel-phase:Released

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

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

[Kernel-packages] [Bug 1494893] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038

[Ertan Günay]

H i Christopher
I installed the last kernel 4.3.0-040300rc3-generic.
After this installation, the problem has been fixed.

But there is another problem with progress bar.
It seems as paused, then immediately it moves on to normal position.

But anyway
Actually you can close the topic.

Thanks
Ertan

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0038

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  while moving files from local hdd to NAS system, Ubuntu locked twice.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  egtaroot   1694 F pulseaudio
   /dev/snd/controlC1:  egtaroot   1694 F pulseaudio
  Date: Fri Sep 11 21:48:17 2015
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: 0010:location  location cifs_ioctl_clone.constprop.4+0x127/0x310 
[cifs]
  Failure: oops
  HibernationDevice: RESUME=UUID=1f126905-ef92-4f88-a1c9-de5d23389d16
  InstallationDate: Installed on 2015-08-16 (26 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150815.1)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=40ffe8ef-a968-42ab-9e9a-d648e8a9fb4c 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: kerneloops-daemon 0.12+git20090217-3ubuntu8
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0038
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0603
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41-M LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0603:bd06/11/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1494893] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038

[Ertan Günay]

H i Christopher
I installed the last kernel 4.3.0-040300rc3-generic.
After this installation, the problem has been fixed.

But there is another problem with progress bar.
It seems as paused, then immediately it moves on to normal position.

But anyway
Actually you can close the topic.

Thanks
Ertan

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0038

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  while moving files from local hdd to NAS system, Ubuntu locked twice.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  egtaroot   1694 F pulseaudio
   /dev/snd/controlC1:  egtaroot   1694 F pulseaudio
  Date: Fri Sep 11 21:48:17 2015
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: 0010:location  location cifs_ioctl_clone.constprop.4+0x127/0x310 
[cifs]
  Failure: oops
  HibernationDevice: RESUME=UUID=1f126905-ef92-4f88-a1c9-de5d23389d16
  InstallationDate: Installed on 2015-08-16 (26 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150815.1)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=40ffe8ef-a968-42ab-9e9a-d648e8a9fb4c 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: kerneloops-daemon 0.12+git20090217-3ubuntu8
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0038
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0603
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41-M LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0603:bd06/11/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

[Joseph Salisbury]

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

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

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

Bug description:
  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
  After upgrading the boot time is longer (what is negligible) but the more 
sever error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.

  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.

  [Test case]
  1. On an affected system boot into kernel 3.19.0-30

  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).

  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

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

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

[Kernel-packages] [Bug 1327774] Re: asus x200la brightness hotkeys not working (rest of them do)

[Christopher M. Penalver]

Jaime Pérez, this is not In Progress as defined in
https://wiki.ubuntu.com/Bugs/Status .

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

Title:
  asus x200la brightness hotkeys not working (rest of them do)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I click on brightness hotkeys nothing (apparently) happens. I
  suppose keys are missbinded or something like that. How can I fix it?

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

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

[Kernel-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

[John Rosauer]

With respect to my last comment, i meant kernel version 3.19.0-28 works.

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

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

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

Bug description:
  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
  After upgrading the boot time is longer (what is negligible) but the more 
sever error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.

  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.

  [Test case]
  1. On an affected system boot into kernel 3.19.0-30

  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).

  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

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

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

[Kernel-packages] [Bug 1424443] Re: Slow transfer rate to USB Stick (NTFS).

[Christopher M. Penalver]

Daniel Gonzalez, it will help immensely if you filed a new report via a 
terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
  Slow transfer rate to USB Stick (NTFS).

Status in linux package in Ubuntu:
  Expired

Bug description:
  Writing to a 16GB USB 2.0 stick (NTFS) goes at ~17MB/s while under
  Windows (same amount, machine, stick, everything) goes at 30+MB/s.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74~precise1
  ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-45-generic.
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  damir  4030 F pulseaudio
   /dev/snd/controlC0:  damir  4030 F pulseaudio
   /dev/snd/pcmC0D0p:   damir  4030 F...m pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xa081 irq 49'
     Mixer name : 'Intel PantherPoint HDMI'
     Components : 'HDA:10134206,106b5200,00100302 
HDA:80862806,80860101,0010'
     Controls  : 48
     Simple ctrls  : 14
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x825'/'USB Device 0x46d:0x825 at usb-:00:14.0-1.1.2, 
high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB046d:0825'
     Controls  : 3
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
     Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
     Capture channels: Mono
     Limits: Capture 0 - 16
     Mono: Capture 14 [88%] [27.00dB] [on]
  Date: Sun Feb 22 21:43:07 2015
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MachineType: Apple Inc. MacBookPro9,2
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=ff870fab-18e7-4850-bd2b-d73ad107be8c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-45-generic N/A
   linux-backports-modules-3.13.0-45-generic  N/A
   linux-firmware 1.79.18
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D3.B08.1208081132
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
  dmi.product.name: MacBookPro9,2
  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/1424443/+subscriptions

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

[Kernel-packages] [Bug 1500739] Re: CPU lockup on HP Proliant DL380 Gen9 servers

[Brad Marshall]

apport information

** Tags added: apport-collected trusty uec-images

** Description changed:

  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots up
  into the hundreds, and ps stops returning.
  
  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.
  
  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  
  Please let us know if you need any further information.
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Sep 29 06:47 seq
+  crw-rw 1 root audio 116, 33 Sep 29 06:47 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.14.1-0ubuntu3.15
+ 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:
+ CRDA: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b
+ MachineType: HP ProLiant DL380 Gen9
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 
console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet
+ ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
+ RelatedPackageVersions:
+  linux-restricted-modules-3.16.0-49-generic N/A
+  linux-backports-modules-3.16.0-49-generic  N/A
+  linux-firmware 1.127.15
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  trusty uec-images
+ Uname: Linux 3.16.0-49-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/06/2015
+ dmi.bios.vendor: HP
+ dmi.bios.version: P89
+ dmi.chassis.type: 23
+ dmi.chassis.vendor: HP
+ dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
+ dmi.product.name: ProLiant DL380 Gen9
+ dmi.sys.vendor: HP

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1500739/+attachment/4479435/+files/BootDmesg.txt

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 06:47 seq
   crw-rw 1 root audio 116, 33 Sep 29 06:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b
  MachineType: HP ProLiant DL380 Gen9
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 
console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare 

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

[Brad Marshall]

apport information

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 06:47 seq
   crw-rw 1 root audio 116, 33 Sep 29 06:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b
  MachineType: HP ProLiant DL380 Gen9
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 
console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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

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

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

[Brad Marshall]

apport information

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 06:47 seq
   crw-rw 1 root audio 116, 33 Sep 29 06:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b
  MachineType: HP ProLiant DL380 Gen9
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 
console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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

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

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

[Brad Marshall]

apport information

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

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

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 06:47 seq
   crw-rw 1 root audio 116, 33 Sep 29 06:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b
  MachineType: HP ProLiant DL380 Gen9
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 
console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1500910] Re: linux-signed should also produce linux-signed-image-*-lowlatency

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/wily-proposed/linux-meta

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

Title:
  linux-signed should also produce linux-signed-image-*-lowlatency

Status in linux-meta package in Ubuntu:
  Fix Committed
Status in linux-signed package in Ubuntu:
  Fix Committed

Bug description:
  We are already uploading all flavours for signing by LP, it makes
  sense to produce actual binary packages from them.  These are tiny
  anyhow as they only contain the signature.

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

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

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

[Brad Marshall]

apport information

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 06:47 seq
   crw-rw 1 root audio 116, 33 Sep 29 06:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b
  MachineType: HP ProLiant DL380 Gen9
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 
console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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

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

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

[Brad Marshall]

apport information

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 06:47 seq
   crw-rw 1 root audio 116, 33 Sep 29 06:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b
  MachineType: HP ProLiant DL380 Gen9
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 
console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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

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

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

[Brad Marshall]

apport information

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 06:47 seq
   crw-rw 1 root audio 116, 33 Sep 29 06:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b
  MachineType: HP ProLiant DL380 Gen9
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 
console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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

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

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

[Brad Marshall]

apport information

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

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 06:47 seq
   crw-rw 1 root audio 116, 33 Sep 29 06:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b
  MachineType: HP ProLiant DL380 Gen9
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 
console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1500739] UdevLog.txt

[Brad Marshall]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1500739/+attachment/4479444/+files/UdevLog.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/1500739

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 06:47 seq
   crw-rw 1 root audio 116, 33 Sep 29 06:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b
  MachineType: HP ProLiant DL380 Gen9
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 
console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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

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

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

[Brad Marshall]

apport information

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 06:47 seq
   crw-rw 1 root audio 116, 33 Sep 29 06:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b
  MachineType: HP ProLiant DL380 Gen9
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 
console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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

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

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

[Brad Marshall]

apport information

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 06:47 seq
   crw-rw 1 root audio 116, 33 Sep 29 06:47 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b
  MachineType: HP ProLiant DL380 Gen9
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 
console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1499869] [NEW] maas wily deployment to HP Proliant m400 fails

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This is the error seen on the console:

[   64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: 
Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin
[  124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - 
url_helper.py[WARNING]: Calling 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
[2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', 
port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id 
(Caused by 
ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect 
timeout=50.0)'))]
[  124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - 
DataSourceEc2.py[CRITICAL]: Giving up on md from 
['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds
[  124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - 
url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404]

This times out eventually and the node is left at the login prompt. I
can install wily via netboot without issue and some time back, wily was
deployable to this node from MAAS.

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Affects: curtin
 Importance: Undecided
 Status: New

** Affects: maas
 Importance: Undecided
 Status: New

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

-- 
maas wily deployment to HP Proliant m400 fails
https://bugs.launchpad.net/bugs/1499869
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 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

[rolfinator]

You are probably right, Steve. Thanks for moving (however I tried to
find the right project/audience in the first place)

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

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

Status in cryptsetup package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
  After upgrading the boot time is longer (what is negligible) but the more 
sever error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.

  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.

  [Test case]
  1. On an affected system boot into kernel 3.19.0-30

  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).

  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

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

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

[Kernel-packages] [Bug 1499869] Re: maas wily deployment to HP Proliant m400 fails

[Craig Magina]

Cloud-init is getting the wrong time because of this error:

[   14.726283] hctosys: unable to open rtc device (rtc0)

What that means is the RTC_DRV_XGENE kernel config option was changed to
'm', this needs to be built-in in order for the device to be available
for hctosys.

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

** Package changed: wily (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/1499869

Title:
  maas wily deployment to HP Proliant m400 fails

Status in cloud-init:
  New
Status in curtin:
  New
Status in MAAS:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This is the error seen on the console:

  [   64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: 
Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin
  [  124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - 
url_helper.py[WARNING]: Calling 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
[2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', 
port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id 
(Caused by 
ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect 
timeout=50.0)'))]
  [  124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - 
DataSourceEc2.py[CRITICAL]: Giving up on md from 
['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds
  [  124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - 
url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404]

  This times out eventually and the node is left at the login prompt. I
  can install wily via netboot without issue and some time back, wily
  was deployable to this node from MAAS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1499869/+subscriptions

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

[Kernel-packages] [Bug 1073887] Re: Sony memory stick pro duo is not recognized

[Adam Niedling]

** Tags added: wily

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

Title:
  Sony memory stick pro duo is not recognized

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu 12.10 on a Acer 5755G laptop. When I insert my Sony
  memory stick pro duo (with a memory stick duo adaptor) memory card
  nothing happens. It does work in Windows 7 on the same laptop. SD
  cards work in Ubuntu too with this card reader. (SD Host controller:
  Broadcom Corporation NetXtreme BCM57765 Memory Card Reader (rev 10))

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  krychek1957 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu Nov  1 11:39:37 2012
  HibernationDevice: RESUME=UUID=179d710c-8f72-46c5-a5b1-9cb7ef744366
  InstallationDate: Installed on 2012-10-31 (0 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Acer Aspire 5755G
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=0b9caecb-bfb0-41e9-8269-f7294a0df3a9 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory 
/home/krychek not ours.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JV51_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.15
  dmi.modalias: 
dmi:bvnAcer:bvrV1.15:bd10/07/2011:svnAcer:pnAspire5755G:pvrV1.15:rvnAcer:rnJV51_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.15:
  dmi.product.name: Aspire 5755G
  dmi.product.version: V1.15
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1499712] larsen (amd64) - tests ran: 194, failed: 0

[Brad Figg]

tests ran: 194, failed: 0;
  
http://kernel.ubuntu.com/testing/4.2.0-12.14/bantam__4.2.0-12.14__2015-09-29_20-20-00/results-index.html

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

Title:
  linux: 4.2.0-12.14 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.2.0-12.14 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-Prepare-package-start:Friday, 25. September 2015 12:35 UTC
  kernel-phase-changed:Friday, 25. September 2015 12:35 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 14:31 UTC
  proposed-announcement-sent:True
  kernel-Promote-to-release-end:Tuesday, 29. September 2015 23:00 UTC

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

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

[Kernel-packages] [Bug 1500156] Re: r592 IRQ: DMA errors cause log files to grow *HUGE*

[Christopher M. Penalver]

Laurent Martin-Borret, this bug report is being closed due to your last
comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500156/comments/43
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

Title:
  r592 IRQ: DMA errors cause log files to grow *HUGE*

Status in linux package in Ubuntu:
  Invalid
Status in openSUSE:
  Fix Released

Bug description:
  Hi,
  Since some recent time, my log files (syslog & kern.log) grow huge, making 
the computer unusable when it performs logrotate operations.
  Having a look to that, I see it contains many many lines :
  Sep 27 09:50:44 mmb-laptop kernel: [42839.496635] r592: IRQ: DMA error
  Sep 27 09:50:44 mmb-laptop kernel: [42839.599027] r592: IRQ: card added

  It seems related to this device : Ricoh Co Ltd R5C592 Memory Stick Bus Host 
Adapter (rev 12)
  I do not use it and I do not need it for now.

  I am using Ubuntu 15.04 with latest updates (as of 27-sep-2015),
  kernel 3.19.0-28-generic #30-Ubuntu on x86_64.

  I've read some posts/other bug reports related to the same issue :

  http://lists.opensuse.org/opensuse-bugs/2014-08/msg01076.html

  https://bugzilla.redhat.com/show_bug.cgi?id=1119361

  https://forum.ubuntu-fr.org/viewtopic.php?id=1907131=1

  https://bugzilla.novell.com/show_bug.cgi?id=892249

  I would be glad if some solution is proposed to stop filling these
  logs !

  Cheers,

  Laurent
  --- 
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lmartinb   1656 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=6512e903-d5d3-4c2e-90b4-45ed0610fcd5
  InstallationDate: Installed on 2014-07-29 (424 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: -- Logs begin at dim. 2015-09-27 14:32:35 CEST, end at 
dim. 2015-09-27 14:49:34 CEST. --
  MachineType: ASUSTeK Computer Inc. M50Vc
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic 
root=UUID=c05406a2-6b6b-4c79-aa26-51af9aa16cb1 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  Tags:  vivid
  Uname: Linux 3.19.0-28-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-08-30 (27 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/14/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M50Vc
  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.:bvr212:bd10/14/2009:svnASUSTeKComputerInc.:pnM50Vc:pvr1.0:rvnASUSTeKComputerInc.:rnM50Vc:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M50Vc
  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/1500156/+subscriptions

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

[Kernel-packages] [Bug 1500739] Re: CPU lockup on HP Proliant DL380 Gen9 servers

[Brad Marshall]

Unfortunately we're unable to test the latest upstream kernel in this
situation.  These servers are running a production system, and as they
use bcache we need a kernel that supports it.

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

Title:
  CPU lockup on HP Proliant DL380 Gen9 servers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
  servers lock up with a similar looking cpu lockup bug.  All 3 of these
  servers are nova-compute nodes in an OpenStack cluster, with a
  reasonable amount of load on them.  The symptoms are the load shoots
  up into the hundreds, and ps stops returning.

  I've attached lspci -vnvn and 3 sets of syslog message traces that we
  grabbed on each of the 3 times it has crashed.

  $ cat /proc/version_signature 
  Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15

  Please let us know if you need any further information.

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

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

[Kernel-packages] [Bug 1499712] onibi (i386) - tests ran: 167, failed: 0

[Brad Figg]

tests ran: 167, failed: 0;
  
http://kernel.ubuntu.com/testing/4.2.0-12.14/onibi__4.2.0-12.14__2015-09-29_20-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/1499712

Title:
  linux: 4.2.0-12.14 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.2.0-12.14 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-Prepare-package-start:Friday, 25. September 2015 12:35 UTC
  kernel-phase-changed:Friday, 25. September 2015 12:35 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 29. September 2015 14:31 UTC
  proposed-announcement-sent:True
  kernel-Promote-to-release-end:Tuesday, 29. September 2015 23:00 UTC

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

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

[Kernel-packages] [Bug 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails

[Tim Gardner]

** Summary changed:

- maas wily deployment to HP Proliant m400 fails
+ maas wily deployment to HP Proliant m400 arm64 server cartridge fails

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

** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
   Status: Incomplete

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

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

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

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

Title:
  maas wily deployment to HP Proliant m400 arm64 server cartridge fails

Status in cloud-init:
  Confirmed
Status in curtin:
  New
Status in MAAS:
  New
Status in cloud-init package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in cloud-init source package in Wily:
  New
Status in linux source package in Wily:
  In Progress

Bug description:
  This is the error seen on the console:

  [   64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: 
Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin
  [  124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - 
url_helper.py[WARNING]: Calling 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
[2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', 
port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id 
(Caused by 
ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect 
timeout=50.0)'))]
  [  124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - 
DataSourceEc2.py[CRITICAL]: Giving up on md from 
['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds
  [  124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - 
url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404]

  This times out eventually and the node is left at the login prompt. I
  can install wily via netboot without issue and some time back, wily
  was deployable to this node from MAAS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1499869/+subscriptions

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