[Kernel-packages] [Bug 1435731] Re: [Dell Inspiron 7437] Wireless key does not work on 14.04.1

2015-03-24 Thread Po-Hsu Lin
BTW, it does not work with 3.16.0-33-generic kernel as well.


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

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

Title:
  [Dell Inspiron 7437] Wireless key does not work on 14.04.1

Status in HWE Next Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201307-13932 Dell Inspiron 7437

  The wireless key does not work on this system.
  Nothing could be detected with sudo showkey -s

  ubuntu@201307-13932:~$ sudo showkey -k
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 240 press
  keycode 240 release
  ^Ccaught signal 2, cleaning up...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-48-generic 3.13.0-48.80
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1574 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1574 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Tue Mar 24 04:45:23 2015
  HibernationDevice: RESUME=UUID=bd120b66-ea6e-4f9b-b52a-021340e042d3
  InstallationDate: Installed on 2015-03-24 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 7437
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic 
root=UUID=b603f1fd-caaa-4688-aff0-288141b61d50 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd10/31/2013:svnDellInc.:pnInspiron7437:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 7437
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1434367] Re: Unable to scroll with DLL0662:00 06CB:2985 touchpad on 14.04

2015-03-24 Thread Po-Hsu Lin
It works on 14.04.1 stock image (3.13.0-32), verified on 201404-14997
(with the same touchpad)

** Summary changed:

- Unable to scroll with DLL0662:00 06CB:2985 touchpad on 14.04.1
+ Unable to scroll with DLL0662:00 06CB:2985 touchpad on 14.04

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

Title:
  Unable to scroll with DLL0662:00 06CB:2985 touchpad on 14.04

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  CID: 201404-14998 Dell Vostro 3546

  The touchpad on this system was detected as DLL0662:00 06CB:2985
  And user can't scroll with it (option not available in the Mouse  Touchpad 
tool)

  $ xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ DLL0662:00 06CB:2985id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]

  ubuntu@201404-14998:~$ xinput --list-props 11
  Device 'DLL0662:00 06CB:2985':
Device Enabled (135):   1
Coordinate Transformation Matrix (137): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (256): 0
Device Accel Constant Deceleration (257):   1.00
Device Accel Adaptive Deceleration (258):   1.00
Device Accel Velocity Scaling (259):10.00
Device Product ID (252):1739, 10629
Device Node (253):  /dev/input/event7
Evdev Axis Inversion (260): 0, 0
Evdev Axes Swap (262):  0
Axis Labels (263):  Rel X (145), Rel Y (146)
Button Labels (264):Button Left (138), Button Unknown (255), 
Button Right (140), Button Wheel Up (141), Button Wheel Down (142)
Evdev Middle Button Emulation (265):0
Evdev Middle Button Timeout (266):  50
Evdev Third Button Emulation (267): 0
Evdev Third Button Emulation Timeout (268): 1000
Evdev Third Button Emulation Button (269):  3
Evdev Third Button Emulation Threshold (270):   20
Evdev Wheel Emulation (271):0
Evdev Wheel Emulation Axes (272):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (273):10
Evdev Wheel Emulation Timeout (274):200
Evdev Wheel Emulation Button (275): 4
Evdev Drag Lock Buttons (276):  0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1725 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1725 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Thu Mar 19 23:32:39 2015
  HibernationDevice: RESUME=UUID=d84f8bd0-6fab-4415-a264-eb416a69854c
  InstallationDate: Installed on 2015-03-19 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Vostro 3546
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=9aa14e5d-d94f-4f90-9622-e087e92ae5e4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 02R010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnVostro3546:pvrNotSpecified:rvnDellInc.:rn02R010:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:

[Kernel-packages] [Bug 1423391] Re: CVE-2014-9683

2015-03-24 Thread John Johansen
** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   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/1423391

Title:
  CVE-2014-9683

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-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 Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic 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:
  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 Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New

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

2015-03-24 Thread bugproxy
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 08:31 EDT---
comment test, please ignore~~

--- Comment From cdead...@us.ibm.com 2015-03-24 08:35 EDT---
another comment test, please ignore~~
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 10:51 EDT---
new comment, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:52 EDT---
comment test from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:53 EDT---
another comment from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:59 EDT---
3rd comment from rtc

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

Title:
  [Ubuntu 15.04] Enable perf to exploit 24x7 hardware counters

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Breno Henrique Leitao bren...@br.ibm.com - 2014-11-06 
12:52:04 ==
  Enable perf tool to exploit POWER 24x7 hardware counters

  Parts of the project:
  a) Some patches upstream and done
  b) Reset targets on remaining features still to be done (jit support, symbol 
names)

  == Comment: #16 - Breno Henrique Leitao bren...@br.ibm.com - 2015-02-24 
08:06:45 ==
  Initial patches already accepted by Canonical on 117275. Patchset posted to 
community, waiting on
  review. (I had posted a version of the patchset in Dec after fixing minor 
comments. Waiting to hear back from community )

  == Comment: #18 - Sukadev Bhattiprolu s...@us.ibm.com - 2015-02-25 16:18:34 
==
  There are two separate patch sets, one for the perf tool and other
  for the kernel. They are both available in mainline 3.19-rc4.

  === Perf tool patches (4)

  Patch 1/4:
  http://marc.info/?l=linuxppc-embeddedm=142067974403807w=2
  commit 688d4df
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:50 2015 -0800

  perf tools: Support parsing parameterized events

  Patch 2/4:
  http://marc.info/?l=linux-kernelm=142067973603799w=2
  commit aaea361
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:51 2015 -0800

  perf tools: Extend format_alias() to include event parameters

  Patch 3/4:
  http://marc.info/?l=linux-kernelm=142067971103796w=2
  commit 98a43e0
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:52 2015 -0800

  perf Documentation: Add event parameters

  Patch 4/4:
  http://marc.info/?l=linux-kernelm=142067968803787w=2
  commit f9ab9c1
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:53 2015 -0800

  perf tools: Document parameterized and symbolic events

  === Kernel patches(7)
  Patch 1/7:
  

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

2015-03-24 Thread bugproxy
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 08:31 EDT---
comment test, please ignore~~

--- Comment From cdead...@us.ibm.com 2015-03-24 08:35 EDT---
another comment test, please ignore~~
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 10:51 EDT---
new comment, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:52 EDT---
comment test from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:53 EDT---
another comment from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:59 EDT---
3rd comment from rtc
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 11:53 EDT---
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 06:31:11
comment again
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 06:23:46
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:59:19
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:58:07
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:53:15
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:51:59
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:41:52
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:40:17
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:35:35
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:33:54
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:51:29
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:33:10
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:22:03
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:01:20
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 00:41:25
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 00:21:24
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 00:01:22
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 23:41:20
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 23:21:22
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 23:01:23
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 22:41:27
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 22:21:20
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 22:01:24
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 21:42:09
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 21:41:14
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 21:21:08
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 21:01:08
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 20:41:08
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 20:21:56
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 20:01:15
Note 

[Kernel-packages] [Bug 1435509] Re: cciss: hangs in modprobe, prevents server from booting

2015-03-24 Thread Marius Gedminas
** Description changed:

  I've upgraded an Ubuntu 10.04 LTS server to 12.04 LTS.  It now fails to
  boot.  More specifically, kernel 3.2.0-77 hangs in the cciss driver
  during initialization.
  
  The hardware is an HP ProLiant DL385 G2.  The RAID controller is HP
  Smart Array P400:
  
  lspci -knn -s 06:01
  06:01.0 RAID bus controller [0104]: Hewlett-Packard Company Smart Array 
P600 [103c:3220]
   Subsystem: Hewlett-Packard Company 3 Gb/s SAS RAID [103c:3225]
   Kernel driver in use: cciss
   Kernel modules: cciss
  
  I can observe the boot process over serial console (attached: 
serial-console.log).  You can see the kernel messages about cciss being 
detected, udev messages about modprobe timing out followed by boot process 
timeouts and a failure to mount the root filesystem.
  You can also see hung task messages from the kernel (kworker/0:2 and modprobe 
are both hung inside cciss), and you can see some of my futile attempts to look 
around in the initramfs.
  
  I can boot an older kernel (2.6.32-73-server, left over from Ubuntu
  10.04 LTS) just fine.  I'm afraid dmesg and other bits of information
  collected by apport for this bug report will be misleadingly from that
  older kernel.
+ 
+ = WORKAROUND =
+ 
+ Add 'pci=noioapicreroute' to the kernel command line.
+ 
+ = WORKAROUND =
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-77-generic 3.2.0-77.114
  ProcVersionSignature: Ubuntu 2.6.32-73.141-server 2.6.32.63+drm33.26
  Uname: Linux 2.6.32-73-server x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: aplay: device_list:252: no soundcards found...
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  ArecordDevices: arecord: device_list:252: no soundcards found...
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [8.816593] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   19.233266] eth0: no IPv6 routers present
   [   79.512524] Clocksource tsc unstable (delta = -264288670 ns)
  Date: Mon Mar 23 19:07:30 2015
  HibernationDevice: RESUME=UUID=06183660-d359-4e05-9f0f-941b61ae65cf
  IwConfig:
   lono wireless extensions.
  
   eth0  no wireless extensions.
  
   eth1  no wireless extensions.
  MachineType: HP ProLiant DL385 G2
  MarkForUpload: True
  PciMultimedia:
  
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VGA16 VGA
  ProcKernelCmdLine: root=UUID=3241700a-e0ca-4d26-8a7f-4fa088b98e75 ro 
console=tty0 console=ttyS1,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-2.6.32-73-server N/A
   linux-backports-modules-2.6.32-73-server  N/A
   linux-firmware1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2015-03-20 (2 days ago)
  dmi.bios.date: 04/07/2007
  dmi.bios.vendor: HP
  dmi.bios.version: A09
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA09:bd04/07/2007:svnHP:pnProLiantDL385G2:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL385 G2
  dmi.sys.vendor: HP

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

Title:
  cciss: hangs in modprobe, prevents server from booting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've upgraded an Ubuntu 10.04 LTS server to 12.04 LTS.  It now fails
  to boot.  More specifically, kernel 3.2.0-77 hangs in the cciss driver
  during initialization.

  The hardware is an HP ProLiant DL385 G2.  The RAID controller is HP
  Smart Array P400:

  lspci -knn -s 06:01
  06:01.0 RAID bus controller [0104]: Hewlett-Packard Company Smart Array 
P600 [103c:3220]
   Subsystem: Hewlett-Packard Company 3 Gb/s SAS RAID [103c:3225]
   Kernel driver in use: cciss
   Kernel modules: cciss

  I can observe the boot process over serial console (attached: 
serial-console.log).  You can see the kernel messages about cciss being 
detected, udev messages about modprobe timing out followed by boot process 
timeouts and a failure to mount the root filesystem.
  You can also see hung task messages from the kernel (kworker/0:2 and modprobe 
are both hung inside cciss), and you can see some of my futile attempts to look 
around in the initramfs.

  I can boot an older kernel (2.6.32-73-server, left over from Ubuntu
  10.04 LTS) just fine.  I'm afraid dmesg and other bits of information
  collected by apport for this bug report will be misleadingly from that
  older kernel.

  = WORKAROUND =

  Add 'pci=noioapicreroute' to the 

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

2015-03-24 Thread bugproxy
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 08:31 EDT---
comment test, please ignore~~

--- Comment From cdead...@us.ibm.com 2015-03-24 08:35 EDT---
another comment test, please ignore~~
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 10:51 EDT---
new comment, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:52 EDT---
comment test from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:53 EDT---
another comment from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:59 EDT---
3rd comment from rtc
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 11:53 EDT---
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 06:31:11
comment again
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 06:23:46
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:59:19
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:58:07
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:53:15
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:51:59
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:41:52
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:40:17
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:35:35
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:33:54
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:51:29
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:33:10
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:22:03
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:01:20
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 00:41:25
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 00:21:24
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 00:01:22
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 23:41:20
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 23:21:22
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 23:01:23
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 22:41:27
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 22:21:20
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 22:01:24
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 21:42:09
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 21:41:14
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 21:21:08
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 21:01:08
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 20:41:08
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 20:21:56
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 20:01:15
Note 

[Kernel-packages] [Bug 1434581] Re: Console extremely slow with 3.13 and newer kernels for certified servers with Matrox G200er2 or similar

2015-03-24 Thread Mike Jester
** Attachment added: dmesg12rc1.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434581/+attachment/4354502/+files/dmesg12rc1.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/1434581

Title:
  Console extremely slow with 3.13 and newer kernels for certified
  servers with Matrox G200er2 or similar

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I first came across this issue I thought it was the same as bug
  #1316035 (https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1316035), but this bug seems to be about X and it is
  reporting xorg-server as the package with the issue. I've seen a
  report on the certification program already on this, but it was
  lacking follow-up and suggested a bug report, question 255332
  (https://answers.launchpad.net/ubuntu-certification/+question/255332).
  I've already asked about this on the forums, and received no replies.

  I originally encountered this issue due to having a bunch of Dell
  servers that I was testing with kernel 3.13 on 12.04. The text console
  is so slow that it is unusable when using vi or doing an operation
  similar to dpkg -l |grep xorg. Comparing the exact same system with
  kernel 3.2 or 3.11 loaded and running lsmod, vesafb is listed and
  performance is excellent. It is not listed on the 3.13 system. The
  same issue exists on 14.04 with the 3.13 or 3.16 kernel.

  Attempting to do modprobe vesa or modprobe vesafb returns modprobe:
  FATAL: Module vesa not found and modprobe: FATAL: Module vesafb not
  found respectively.

  Attempting to use uvesafb on this hardware results in a black screen.
  Attempting to use vga16fb results in good performance, but I am locked
  to 640x480. I tried to use fbset to force higher resolutions, but it
  either results in a distorted display or tells me there is not enough
  memory.

  I need a 1280x1024 console with performance equal to 12.04 with
  kernels 3.2-3.11. The server I'm using for testing is a Dell R320.

  This appears to be regression as I can duplicate it by simply doing a fresh 
install of 12.04.1 and not having the issue, while doing a fresh install of 
12.04.5, 14.04.1, or 14.04.2 results in a very slow console.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 13:17 seq
   crw-rw 1 root audio 116, 33 Mar 20 13:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.7
  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=3255aa87-ba68-4b74-bdb0-1112aba7d46e
  InstallationDate: Installed on 2015-03-20 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=fda4445f-efe2-4e93-9adb-ecaf6386f8cd ro consoleblank=0
  ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   linux-backports-modules-3.13.0-46-generic  N/A
   linux-firmware 1.127.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: root
  _MarkForUpload: True
  dmi.bios.date: 09/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.21
  dmi.board.name: 0R5KP9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.21:bd09/23/2013:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0R5KP9:rvrA09:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1434581] Re: Console extremely slow with 3.13 and newer kernels for certified servers with Matrox G200er2 or similar

2015-03-24 Thread Mike Jester
I tried more kernels this morning, and unfortunately my results weren't
so good.

All of the v3.12-rc# kernels, v3.11.0 and v3.11.10.15 give me a black
screen. The system does boot and function, but I am blind. I'm attaching
the dmesg from v3.12.0, v3.12-rc1 and v3.11.0.

The last versions of 3.8 (lts-raring) and 3.11 (lts-saucy) in the
official repositories perform well, with no issues.

I'm going to try v3.10-saucy, v3.9-saucy and v3.8-raring as well.

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

Title:
  Console extremely slow with 3.13 and newer kernels for certified
  servers with Matrox G200er2 or similar

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I first came across this issue I thought it was the same as bug
  #1316035 (https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1316035), but this bug seems to be about X and it is
  reporting xorg-server as the package with the issue. I've seen a
  report on the certification program already on this, but it was
  lacking follow-up and suggested a bug report, question 255332
  (https://answers.launchpad.net/ubuntu-certification/+question/255332).
  I've already asked about this on the forums, and received no replies.

  I originally encountered this issue due to having a bunch of Dell
  servers that I was testing with kernel 3.13 on 12.04. The text console
  is so slow that it is unusable when using vi or doing an operation
  similar to dpkg -l |grep xorg. Comparing the exact same system with
  kernel 3.2 or 3.11 loaded and running lsmod, vesafb is listed and
  performance is excellent. It is not listed on the 3.13 system. The
  same issue exists on 14.04 with the 3.13 or 3.16 kernel.

  Attempting to do modprobe vesa or modprobe vesafb returns modprobe:
  FATAL: Module vesa not found and modprobe: FATAL: Module vesafb not
  found respectively.

  Attempting to use uvesafb on this hardware results in a black screen.
  Attempting to use vga16fb results in good performance, but I am locked
  to 640x480. I tried to use fbset to force higher resolutions, but it
  either results in a distorted display or tells me there is not enough
  memory.

  I need a 1280x1024 console with performance equal to 12.04 with
  kernels 3.2-3.11. The server I'm using for testing is a Dell R320.

  This appears to be regression as I can duplicate it by simply doing a fresh 
install of 12.04.1 and not having the issue, while doing a fresh install of 
12.04.5, 14.04.1, or 14.04.2 results in a very slow console.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 13:17 seq
   crw-rw 1 root audio 116, 33 Mar 20 13:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.7
  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=3255aa87-ba68-4b74-bdb0-1112aba7d46e
  InstallationDate: Installed on 2015-03-20 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=fda4445f-efe2-4e93-9adb-ecaf6386f8cd ro consoleblank=0
  ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   linux-backports-modules-3.13.0-46-generic  N/A
   linux-firmware 1.127.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: root
  _MarkForUpload: True
  dmi.bios.date: 09/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.21
  dmi.board.name: 0R5KP9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.21:bd09/23/2013:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0R5KP9:rvrA09:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1434581] Re: Console extremely slow with 3.13 and newer kernels for certified servers with Matrox G200er2 or similar

2015-03-24 Thread Mike Jester
** Attachment added: dmesg110.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434581/+attachment/4354500/+files/dmesg110.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/1434581

Title:
  Console extremely slow with 3.13 and newer kernels for certified
  servers with Matrox G200er2 or similar

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I first came across this issue I thought it was the same as bug
  #1316035 (https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1316035), but this bug seems to be about X and it is
  reporting xorg-server as the package with the issue. I've seen a
  report on the certification program already on this, but it was
  lacking follow-up and suggested a bug report, question 255332
  (https://answers.launchpad.net/ubuntu-certification/+question/255332).
  I've already asked about this on the forums, and received no replies.

  I originally encountered this issue due to having a bunch of Dell
  servers that I was testing with kernel 3.13 on 12.04. The text console
  is so slow that it is unusable when using vi or doing an operation
  similar to dpkg -l |grep xorg. Comparing the exact same system with
  kernel 3.2 or 3.11 loaded and running lsmod, vesafb is listed and
  performance is excellent. It is not listed on the 3.13 system. The
  same issue exists on 14.04 with the 3.13 or 3.16 kernel.

  Attempting to do modprobe vesa or modprobe vesafb returns modprobe:
  FATAL: Module vesa not found and modprobe: FATAL: Module vesafb not
  found respectively.

  Attempting to use uvesafb on this hardware results in a black screen.
  Attempting to use vga16fb results in good performance, but I am locked
  to 640x480. I tried to use fbset to force higher resolutions, but it
  either results in a distorted display or tells me there is not enough
  memory.

  I need a 1280x1024 console with performance equal to 12.04 with
  kernels 3.2-3.11. The server I'm using for testing is a Dell R320.

  This appears to be regression as I can duplicate it by simply doing a fresh 
install of 12.04.1 and not having the issue, while doing a fresh install of 
12.04.5, 14.04.1, or 14.04.2 results in a very slow console.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 13:17 seq
   crw-rw 1 root audio 116, 33 Mar 20 13:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.7
  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=3255aa87-ba68-4b74-bdb0-1112aba7d46e
  InstallationDate: Installed on 2015-03-20 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=fda4445f-efe2-4e93-9adb-ecaf6386f8cd ro consoleblank=0
  ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   linux-backports-modules-3.13.0-46-generic  N/A
   linux-firmware 1.127.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: root
  _MarkForUpload: True
  dmi.bios.date: 09/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.21
  dmi.board.name: 0R5KP9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.21:bd09/23/2013:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0R5KP9:rvrA09:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1434581] Re: Console extremely slow with 3.13 and newer kernels for certified servers with Matrox G200er2 or similar

2015-03-24 Thread Mike Jester
** Attachment added: dmesg120.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434581/+attachment/4354501/+files/dmesg120.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/1434581

Title:
  Console extremely slow with 3.13 and newer kernels for certified
  servers with Matrox G200er2 or similar

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I first came across this issue I thought it was the same as bug
  #1316035 (https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1316035), but this bug seems to be about X and it is
  reporting xorg-server as the package with the issue. I've seen a
  report on the certification program already on this, but it was
  lacking follow-up and suggested a bug report, question 255332
  (https://answers.launchpad.net/ubuntu-certification/+question/255332).
  I've already asked about this on the forums, and received no replies.

  I originally encountered this issue due to having a bunch of Dell
  servers that I was testing with kernel 3.13 on 12.04. The text console
  is so slow that it is unusable when using vi or doing an operation
  similar to dpkg -l |grep xorg. Comparing the exact same system with
  kernel 3.2 or 3.11 loaded and running lsmod, vesafb is listed and
  performance is excellent. It is not listed on the 3.13 system. The
  same issue exists on 14.04 with the 3.13 or 3.16 kernel.

  Attempting to do modprobe vesa or modprobe vesafb returns modprobe:
  FATAL: Module vesa not found and modprobe: FATAL: Module vesafb not
  found respectively.

  Attempting to use uvesafb on this hardware results in a black screen.
  Attempting to use vga16fb results in good performance, but I am locked
  to 640x480. I tried to use fbset to force higher resolutions, but it
  either results in a distorted display or tells me there is not enough
  memory.

  I need a 1280x1024 console with performance equal to 12.04 with
  kernels 3.2-3.11. The server I'm using for testing is a Dell R320.

  This appears to be regression as I can duplicate it by simply doing a fresh 
install of 12.04.1 and not having the issue, while doing a fresh install of 
12.04.5, 14.04.1, or 14.04.2 results in a very slow console.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 13:17 seq
   crw-rw 1 root audio 116, 33 Mar 20 13:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.7
  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=3255aa87-ba68-4b74-bdb0-1112aba7d46e
  InstallationDate: Installed on 2015-03-20 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=fda4445f-efe2-4e93-9adb-ecaf6386f8cd ro consoleblank=0
  ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   linux-backports-modules-3.13.0-46-generic  N/A
   linux-firmware 1.127.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: root
  _MarkForUpload: True
  dmi.bios.date: 09/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.21
  dmi.board.name: 0R5KP9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.21:bd09/23/2013:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0R5KP9:rvrA09:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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


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

2015-03-24 Thread bugproxy
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 08:31 EDT---
comment test, please ignore~~

--- Comment From cdead...@us.ibm.com 2015-03-24 08:35 EDT---
another comment test, please ignore~~
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 10:51 EDT---
new comment, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:52 EDT---
comment test from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:53 EDT---
another comment from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:59 EDT---
3rd comment from rtc
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 11:53 EDT---
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 06:31:11
comment again
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 06:23:46
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:59:19
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:58:07
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:53:15
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:51:59
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:41:52
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:40:17
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:35:35
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:33:54
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:51:29
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:33:10
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:22:03
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:01:20
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 00:41:25
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 00:21:24
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 00:01:22
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 23:41:20
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 23:21:22
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 23:01:23
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 22:41:27
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 22:21:20
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 22:01:24
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 21:42:09
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 21:41:14
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 21:21:08
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 21:01:08
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 20:41:08
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 20:21:56
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 20:01:15
Note 

[Kernel-packages] [Bug 1434581] Re: Console extremely slow with 3.13 and newer kernels for certified servers with Matrox G200er2 or similar

2015-03-24 Thread Mike Jester
Chris, the output is:

2.3.3
07/10/2014

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

Title:
  Console extremely slow with 3.13 and newer kernels for certified
  servers with Matrox G200er2 or similar

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I first came across this issue I thought it was the same as bug
  #1316035 (https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1316035), but this bug seems to be about X and it is
  reporting xorg-server as the package with the issue. I've seen a
  report on the certification program already on this, but it was
  lacking follow-up and suggested a bug report, question 255332
  (https://answers.launchpad.net/ubuntu-certification/+question/255332).
  I've already asked about this on the forums, and received no replies.

  I originally encountered this issue due to having a bunch of Dell
  servers that I was testing with kernel 3.13 on 12.04. The text console
  is so slow that it is unusable when using vi or doing an operation
  similar to dpkg -l |grep xorg. Comparing the exact same system with
  kernel 3.2 or 3.11 loaded and running lsmod, vesafb is listed and
  performance is excellent. It is not listed on the 3.13 system. The
  same issue exists on 14.04 with the 3.13 or 3.16 kernel.

  Attempting to do modprobe vesa or modprobe vesafb returns modprobe:
  FATAL: Module vesa not found and modprobe: FATAL: Module vesafb not
  found respectively.

  Attempting to use uvesafb on this hardware results in a black screen.
  Attempting to use vga16fb results in good performance, but I am locked
  to 640x480. I tried to use fbset to force higher resolutions, but it
  either results in a distorted display or tells me there is not enough
  memory.

  I need a 1280x1024 console with performance equal to 12.04 with
  kernels 3.2-3.11. The server I'm using for testing is a Dell R320.

  This appears to be regression as I can duplicate it by simply doing a fresh 
install of 12.04.1 and not having the issue, while doing a fresh install of 
12.04.5, 14.04.1, or 14.04.2 results in a very slow console.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 13:17 seq
   crw-rw 1 root audio 116, 33 Mar 20 13:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.7
  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=3255aa87-ba68-4b74-bdb0-1112aba7d46e
  InstallationDate: Installed on 2015-03-20 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=fda4445f-efe2-4e93-9adb-ecaf6386f8cd ro consoleblank=0
  ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   linux-backports-modules-3.13.0-46-generic  N/A
   linux-firmware 1.127.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: root
  _MarkForUpload: True
  dmi.bios.date: 09/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.21
  dmi.board.name: 0R5KP9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.21:bd09/23/2013:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0R5KP9:rvrA09:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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


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

2015-03-24 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New = Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques 
(henrix)

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

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

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

Bug description:
  This bug is for tracking the 3.16.0-34.45~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, 24. March 2015 02:00 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 24. March 2015 02:00 UTC
  kernel-stable-master-bug:1435400

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

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


[Kernel-packages] [Bug 1433568] Re: PCM mixer controls just line out, and Line out mixer missing

2015-03-24 Thread Jarno Suni
Correction, PCM mixer is stuck at 100% volume in the upstream kernel.
Otherwise it seems to work.

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

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

Title:
  PCM mixer controls just line out, and Line out mixer missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't know this PCM really well, but I am used to that it controls
  volume of several outputs together with other mixers like Master mixer
  does. However, here PCM controls volume of Line out (i.e. analog out),
  but does not work with Headphone or Speaker. I would expect there was
  a specific mixer called Line out for controlling line out volume.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-46-lowlatency 3.13.0-46.79
  ProcVersionSignature: Ubuntu 3.13.0-46.79-lowlatency 3.13.11-ckt15
  Uname: Linux 3.13.0-46-lowlatency x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Mar 18 14:25:59 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (178 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.1)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 745
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-lowlatency 
root=UUID=d012c1bd-7e56-4035-b321-38d20cb14421 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:
   linux-restricted-modules-3.13.0-46-lowlatency N/A
   linux-backports-modules-3.13.0-46-lowlatency  N/A
   linux-firmware1.127.11
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1414930] Re: [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't work

2015-03-24 Thread Timo Aaltonen
no changes needed to the X driver

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: xserver-xorg-input-synaptics (Ubuntu Trusty)
   Status: Confirmed = Invalid

** Changed in: xserver-xorg-input-synaptics (Ubuntu Utopic)
   Status: Confirmed = Invalid

** Changed in: linux (Ubuntu)
 Assignee: Liming Wang (wangliming) = Timo Aaltonen (tjaalton)

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

Title:
  [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't
  work

Status in HWE Next Project:
  In Progress
Status in The Linux Kernel:
  In Progress
Status in libinput package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed
Status in systemd source package in Trusty:
  Confirmed
Status in xserver-xorg-input-synaptics source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Confirmed
Status in systemd source package in Utopic:
  Confirmed
Status in xserver-xorg-input-synaptics source package in Utopic:
  Invalid

Bug description:
  Lenovo X1 3rd Carbon (201411-16196)

  Steps to reproduce the bug:
  1, Log in to system
  2, Click left/right/middle buttons of the touchpad

  Actual result:
  No response after clicking the buttons

  Expected results:
  Buttons work as expected behavirour

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: 
boot/vmlinuz-3.13.0-45-generic]
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1598 F pulseaudio
   /dev/snd/controlC0:  u  1598 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 27 02:48:23 2015
  HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f
  InstallationDate: Installed on 2015-01-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126)
  MachineType: LENOVO 20BTZ09ZUS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=1d34e685-c98b-41f3-b649-87770517b194 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.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET24W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTZ09ZUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTZ09ZUS
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1435509] Re: cciss: hangs in modprobe, prevents server from booting

2015-03-24 Thread Marius Gedminas
I'm hesitating to link to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=650119 because it seems like a subtly different
bug (also one that was fixed in upstream 3.2.0), but it probably has
emails of people who understand CCISS kernel code.

** Bug watch added: Debian Bug tracker #650119
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650119

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

Title:
  cciss: hangs in modprobe, prevents server from booting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've upgraded an Ubuntu 10.04 LTS server to 12.04 LTS.  It now fails
  to boot.  More specifically, kernel 3.2.0-77 hangs in the cciss driver
  during initialization.

  The hardware is an HP ProLiant DL385 G2.  The RAID controller is HP
  Smart Array P400:

  lspci -knn -s 06:01
  06:01.0 RAID bus controller [0104]: Hewlett-Packard Company Smart Array 
P600 [103c:3220]
   Subsystem: Hewlett-Packard Company 3 Gb/s SAS RAID [103c:3225]
   Kernel driver in use: cciss
   Kernel modules: cciss

  I can observe the boot process over serial console (attached: 
serial-console.log).  You can see the kernel messages about cciss being 
detected, udev messages about modprobe timing out followed by boot process 
timeouts and a failure to mount the root filesystem.
  You can also see hung task messages from the kernel (kworker/0:2 and modprobe 
are both hung inside cciss), and you can see some of my futile attempts to look 
around in the initramfs.

  I can boot an older kernel (2.6.32-73-server, left over from Ubuntu
  10.04 LTS) just fine.  I'm afraid dmesg and other bits of information
  collected by apport for this bug report will be misleadingly from that
  older kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-77-generic 3.2.0-77.114
  ProcVersionSignature: Ubuntu 2.6.32-73.141-server 2.6.32.63+drm33.26
  Uname: Linux 2.6.32-73-server x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: aplay: device_list:252: no soundcards found...
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  ArecordDevices: arecord: device_list:252: no soundcards found...
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [8.816593] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   19.233266] eth0: no IPv6 routers present
   [   79.512524] Clocksource tsc unstable (delta = -264288670 ns)
  Date: Mon Mar 23 19:07:30 2015
  HibernationDevice: RESUME=UUID=06183660-d359-4e05-9f0f-941b61ae65cf
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.

   eth1  no wireless extensions.
  MachineType: HP ProLiant DL385 G2
  MarkForUpload: True
  PciMultimedia:

  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VGA16 VGA
  ProcKernelCmdLine: root=UUID=3241700a-e0ca-4d26-8a7f-4fa088b98e75 ro 
console=tty0 console=ttyS1,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-2.6.32-73-server N/A
   linux-backports-modules-2.6.32-73-server  N/A
   linux-firmware1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2015-03-20 (2 days ago)
  dmi.bios.date: 04/07/2007
  dmi.bios.vendor: HP
  dmi.bios.version: A09
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrA09:bd04/07/2007:svnHP:pnProLiantDL385G2:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL385 G2
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1408833] Re: broken postinst test for uvtool-libvirt on utopic

2015-03-24 Thread Luis Henriques
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  broken postinst test for uvtool-libvirt on utopic

Status in AppArmor Linux application security framework:
  Confirmed
Status in ubuntu virtualization tools:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  Installing uvtool-libvirt *inside an lxc container* on utopic fails
  due to a test in the postinst script.

  It uses socat on the libvirt socket, which fails, despite libvirt
  being installed correctly.

  ubuntu@uoi-bootstrap:~$ sudo apt-get install -f
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libfreetype6 os-prober
  Use 'apt-get autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up uvtool-libvirt (0~bzr92-0ubuntu2) ...
  2015/01/08 13:01:34 socat[10184] E read(3, 0x13b2a30, 8192): Permission denied
  libvirtd does not appear to be listening on /var/run/libvirt/libvirt-sock.
  On Ubuntu, libvirtd is managed with the libvirt-bin upstart job.
  Repair libvirtd, then reconfigure uvtool-libvirt with:
  sudo apt-get -f install
  dpkg: error processing package uvtool-libvirt (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   uvtool-libvirt
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  ubuntu@uoi-bootstrap:~$ ps -ef | grep libvirt
  libvirt+  9556 1  0 09:52 ?00:00:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  root  9557  9556  0 09:52 ?00:00:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  root  9854 1  0 10:24 ?00:00:00 /usr/sbin/libvirtd -d
  ubuntu   10155 10120  0 12:56 pts/000:00:00 grep libvirt

  ubuntu@uoi-bootstrap:~$ groups
  ubuntu adm dialout cdrom floppy sudo audio dip video plugdev netdev libvirtd

  
  ubuntu@uoi-bootstrap:~$ virsh list
   IdName   State
  

  for a little more context, there are notes here:
  https://gist.github.com/mikemccracken/53c665e6094db21efc03

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

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


[Kernel-packages] [Bug 1433568] Re: PCM mixer controls just line out, and Line out mixer missing

2015-03-24 Thread Jarno Suni
Now I can change PCM volume again with the upstream kernel. I don't know
what kept it from changing some time ago. I didn't reboot.

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

Title:
  PCM mixer controls just line out, and Line out mixer missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't know this PCM really well, but I am used to that it controls
  volume of several outputs together with other mixers like Master mixer
  does. However, here PCM controls volume of Line out (i.e. analog out),
  but does not work with Headphone or Speaker. I would expect there was
  a specific mixer called Line out for controlling line out volume.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-46-lowlatency 3.13.0-46.79
  ProcVersionSignature: Ubuntu 3.13.0-46.79-lowlatency 3.13.11-ckt15
  Uname: Linux 3.13.0-46-lowlatency x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Mar 18 14:25:59 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (178 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.1)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 745
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-lowlatency 
root=UUID=d012c1bd-7e56-4035-b321-38d20cb14421 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:
   linux-restricted-modules-3.13.0-46-lowlatency N/A
   linux-backports-modules-3.13.0-46-lowlatency  N/A
   linux-firmware1.127.11
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

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

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


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

2015-03-24 Thread bugproxy
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 08:31 EDT---
comment test, please ignore~~

--- Comment From cdead...@us.ibm.com 2015-03-24 08:35 EDT---
another comment test, please ignore~~
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 10:51 EDT---
new comment, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:52 EDT---
comment test from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:53 EDT---
another comment from rtc, please ignore

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

Title:
  [Ubuntu 15.04] Enable perf to exploit 24x7 hardware counters

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Breno Henrique Leitao bren...@br.ibm.com - 2014-11-06 
12:52:04 ==
  Enable perf tool to exploit POWER 24x7 hardware counters

  Parts of the project:
  a) Some patches upstream and done
  b) Reset targets on remaining features still to be done (jit support, symbol 
names)

  == Comment: #16 - Breno Henrique Leitao bren...@br.ibm.com - 2015-02-24 
08:06:45 ==
  Initial patches already accepted by Canonical on 117275. Patchset posted to 
community, waiting on
  review. (I had posted a version of the patchset in Dec after fixing minor 
comments. Waiting to hear back from community )

  == Comment: #18 - Sukadev Bhattiprolu s...@us.ibm.com - 2015-02-25 16:18:34 
==
  There are two separate patch sets, one for the perf tool and other
  for the kernel. They are both available in mainline 3.19-rc4.

  === Perf tool patches (4)

  Patch 1/4:
  http://marc.info/?l=linuxppc-embeddedm=142067974403807w=2
  commit 688d4df
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:50 2015 -0800

  perf tools: Support parsing parameterized events

  Patch 2/4:
  http://marc.info/?l=linux-kernelm=142067973603799w=2
  commit aaea361
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:51 2015 -0800

  perf tools: Extend format_alias() to include event parameters

  Patch 3/4:
  http://marc.info/?l=linux-kernelm=142067971103796w=2
  commit 98a43e0
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:52 2015 -0800

  perf Documentation: Add event parameters

  Patch 4/4:
  http://marc.info/?l=linux-kernelm=142067968803787w=2
  commit f9ab9c1
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:53 2015 -0800

  perf tools: Document parameterized and symbolic events

  === Kernel patches(7)
  Patch 1/7:
  http://marc.info/?l=linux-kernelm=142265456708471w=2
  commit fd979c0
  Author: Cody P Schafer c...@linux.vnet.ibm.com
 

[Kernel-packages] [Bug 1433920] Re: [Lenovo E450] ([Radeon R7 M260] [1002:6900]) [Lenovo E550] ([Radeon R7 M265] [1002:6604]) Display abnormally on both screen under extend mode.

2015-03-24 Thread Gabriel Zhi Chen
** Attachment added: picture-201411-16167.jpg
   
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1433920/+attachment/4354332/+files/picture-201411-16167.jpg

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

Title:
  [Lenovo E450] ([Radeon R7 M260] [1002:6900]) [Lenovo E550] ([Radeon R7
  M265] [1002:6604]) Display abnormally on both screen under extend
  mode.

Status in HWE Next Project:
  New
Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic)
  CID : 201411-16167 Lenovo E550 (I+A) with 14.04.2 (utopic)

  Steps:
  1. Install 14.04.2 on E450.
  2. Log in system and install fglrx.
  3. Reboot system.
  4. Connect HDMI cable.
  5. Switch internal, external, mirror and extend modes by display key.

  Expected result:
  The 4 modes show normally.

  Actual result:
  Display abnormally on both screen under extendl mode. Please refer to 
picture.jpg

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

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

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


[Kernel-packages] [Bug 1415507] Re: CVE-2013-7421

2015-03-24 Thread John Johansen
** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

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

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

Title:
  CVE-2013-7421

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-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 Lucid:
  Invalid
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Invalid
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic 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:
  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 Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source 

[Kernel-packages] [Bug 1290867] Re: [7392:a822] rtl8812au - Edimax AC-1200 not supported

2015-03-24 Thread 0xnate
It looks like this is still not supported in 15.04. Any update?

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

Title:
  [7392:a822] rtl8812au - Edimax AC-1200 not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I would like to use my Edimax AC-1200 dongle (802.11ac dongle)
  natively, without compiling my own driver. The driver to use does not
  appear to be included in the mainline kernel yet.

  I am currently using the hacked up driver from
  https://github.com/gnab/rtl8812au when I really need to use that
  device.

  Bus 003 Device 026: ID 7392:a822 Edimax Technology Co., Ltd 
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   2.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
idVendor   0x7392 Edimax Technology Co., Ltd
idProduct  0xa822 
bcdDevice0.00
iManufacturer   1 Realtek
iProduct2 802.11n NIC
iSerial 3 123456
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   53
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0x80
(Bus Powered)
  MaxPower  500mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   5
bInterfaceClass   255 Vendor Specific Class
bInterfaceSubClass255 Vendor Specific Subclass
bInterfaceProtocol255 Vendor Specific Protocol
iInterface  0 
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x03  EP 3 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x04  EP 4 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x85  EP 5 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0040  1x 64 bytes
  bInterval   1
  Device Qualifier (for other device speed):
bLength10
bDescriptorType 6
bcdUSB   2.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
bNumConfigurations  1
  Device Status: 0x0002
(Bus Powered)
Remote Wakeup Enabled
  --- 
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mtrudel3110 F pulseaudio
   /dev/snd/pcmC1D0p:   mtrudel3110 F...m pulseaudio
   /dev/snd/controlC0:  mtrudel3110 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=99bbaa3c-8461-48a3-87c9-e6c026dd22ce
  InstallationDate: Installed on 2014-01-31 (39 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140130)
  MachineType: LENOVO 2306CTO
  NonfreeKernelModules: 8812au
  Package: linux (not installed)
  ProcFB: 0 

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

2015-03-24 Thread bugproxy
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 08:31 EDT---
comment test, please ignore~~

--- Comment From cdead...@us.ibm.com 2015-03-24 08:35 EDT---
another comment test, please ignore~~
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 10:51 EDT---
new comment, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:52 EDT---
comment test from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:53 EDT---
another comment from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:59 EDT---
3rd comment from rtc
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 11:53 EDT---
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 06:31:11
comment again
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 06:23:46
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:59:19
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:58:07
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:53:15
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 05:51:59
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:41:52
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:40:17
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:35:35
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 03:33:54
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:51:29
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:33:10
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:22:03
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 01:01:20
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 00:41:25
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 00:21:24
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-24 00:01:22
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 23:41:20
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 23:21:22
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 23:01:23
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 22:41:27
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 22:21:20
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 22:01:24
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-23 21:42:09
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 21:41:14
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 21:21:08
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 21:01:08
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 20:41:08
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 20:21:56
Note by Application Cdeadmin (cdead...@us.ibm.com), 2015-03-20 20:01:15
Note 

[Kernel-packages] [Bug 1354975] Re: iwlwifi Intel 7260 Wifi disconnects

2015-03-24 Thread Claudio
@brianwc
I have unstable WiFi connection on my Thinkpad T440p with 7260-10 with kernel 
3.19.0-6/ubuntu 14.10

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

Title:
  iwlwifi Intel 7260 Wifi disconnects

Status in Unity Linux:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  I experience frequent disconnects and auth issues, never more than 30
  minutes without a disconnect. Sometimes dozens of disconnects in a few
  minutes.

  This happens with the default 7260-8 firmware.
  Tried replacing the -8 with -9 ucode. Failed to load due to API version. This 
loaded the -7 driver which seems to be more stable.

  Tested against 2.4ghz APs (Apple, Netgear, Linksys).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  2577 F pulseaudio
   /dev/snd/controlC1:  steve  2577 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Aug 10 17:49:06 2014
  HibernationDevice: RESUME=UUID=374a0c1c-4ac2-456b-a67e-9ea54fe11fe6
  InstallationDate: Installed on 2013-12-28 (225 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS 12-9Q33
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=58deb355-7a09-440b-ade2-69a84fd74460 ro ipv6.disable=1 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-06 (35 days ago)
  dmi.bios.date: 05/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd05/06/2013:svnDellInc.:pnXPS12-9Q33:pvrA00:rvnDellInc.:rnXPS12-9Q33:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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


Re: [Kernel-packages] [Bug 1411193] Re: [Asus F200MA] bluetooth not working

2015-03-24 Thread Jeremy
Download the attached file and extract it to your home folder, open terminal 
window and enter the following
sudo apt-get install build-essential linux-headers-generic
cd bluetooth-3.16
cp /boot/config-$(uname -r) .config
cp /usr/src/linux-headers-$(uname -r)/Module.symvers Module.symvers
make -C /lib/modules/$(uname -r)/build M=$PWD modules
sudo modprobe -r btusb
sudo cp btusb.ko /lib/modules/$(uname -r)/kernel/drivers/bluetooth/
sudo modprobe btusbsudo cp ath3k.ko /lib/modules/$(uname 
-r)/kernel/drivers/bluetooth/sudo modprobe ath3kecho ath3k | sudo tee -a 
/etc/modulesYou should have working bluetooth after a reboot 


 On Monday, March 23, 2015 11:25 AM, Luis Henriques 
luis.henriq...@canonical.com wrote:
   

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

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

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1411193

Title:
  [Asus F200MA] bluetooth not working

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  In my opinion, this is a very similar bug to

  https://bugs.launchpad.net/bugs/1395465

  in the sense that the bluetooth indicator works but no external devices are 
detected.
  I don't know which information I should provide here so I just insert uname 
-a and lsusb.

  lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 13d3:3423 IMC Networks 
  Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
  Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  uname -a
  Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

  Any help will be greatly appreciated. Alessandro

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


** Attachment added: bluetooth-3.16.tar.gz
   
https://bugs.launchpad.net/bugs/1411193/+attachment/4354354/+files/bluetooth-3.16.tar.gz

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

Title:
  [Asus F200MA] bluetooth not working

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  In my opinion, this is a very similar bug to

  https://bugs.launchpad.net/bugs/1395465

  in the sense that the bluetooth indicator works but no external devices are 
detected.
  I don't know which information I should provide here so I just insert uname 
-a and lsusb.

  lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 13d3:3423 IMC Networks 
  Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
  Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  uname -a
  Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

  Any help will be greatly appreciated. Alessandro

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

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


[Kernel-packages] [Bug 1331077] Re: [Lenovo ThinkPad Edge E540] suspend/resume failure

2015-03-24 Thread Ivan Frederiks
@xc-racer2
Thank you for good news! BIOS update solved the issue for me.

BTW, after BIOS update my system became unbootable, looks like Ubuntu UEFI boot 
entry was removed.
See http://superuser.com/questions/376470/how-to-reinstall-grub2-efi for 
recovery procedure.

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

Title:
  [Lenovo ThinkPad Edge E540] suspend/resume failure

Status in The Linux Kernel:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  suspend to RAM failed before it was completed:
  * fan was still on and
  * Fn-F1-  Fn-F4-status LEDs were still on (signifying muted speakers and 
microphone respectively)
  * nevertheless the general ThinkPad LED (the i's dot) (/proc/acpi/ibm/led 0) 
behaved like normal: slowly blinking, which normally means I'm suspended to 
RAM.
  * however resume was impossible: wakeup failed through mouse clicks, various 
keyboard keys and combinations and also the power key, only a hard reset (5s or 
so holding down the power key) could bring it back to life

  Adding the kernel cmdline option acpi_sleep=nonvs was of no avail,
  too.

  I recently upgraded to a new BIOS v2.07 [1], I think the problem
  exists since then.

  Update
  ==
  I confirmed that this is definitely a BIOS issue. The last working BIOS is 
v1.61 [2], so the change was introduced by v2.07 [1]. Installing the latest 
v2.08 [3] does not fix this problem.

  So this is the changelog for v2.07 [1]:
  - (Fix) Fixed an issue that system will auto wakeup after shutdown when 
battery capacity is under 15% on DC only.
  - (Fix) Fixed an issue related to APS.
  - (New) Added support for new GPU config.

  By the way, I could not find a new GPU config option in the BIOS, same
  old choice Integrated vs. Optimus, nothing new.

  [1] http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j9uj10wd.iso
  http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j9uj10wd.txt
  [2] http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j9uj09wd.iso
  http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j9uj09wd.txt
  [3] http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j9uj11wd.iso
  http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/j9uj11wd.txt

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.54
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xx 2499 F pulseaudio
   /dev/snd/controlC0:  xx 2499 F pulseaudio
  Date: Tue Jun 17 17:16:54 2014
  DuplicateSignature: suspend/resume:LENOVO 20C6S00200:J9ET87WW (2.07 )
  ExecutablePath: /usr/share/apport/apportcheckresume
  ExecutableTimestamp: 1400281919
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=2ecc68b9-65e3-4cee-9b2a-d41ff651e4e8
  InstallationDate: Installed on 2014-01-06 (161 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: LENOVO 20C6S00200
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcCwd: /
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic.efi.signed 
root=/dev/mapper/ubuntuvg-root ro quiet splash acpi_osi=!Windows 2012 
pcie_aspm=force intel_pstate=enable vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.3
  SourcePackage: linux
  Title: [LENOVO 20C6S00200] suspend/resume failure
  UpgradeStatus: Upgraded to trusty on 2014-06-12 (5 days ago)
  UserGroups:

  dmi.bios.date: 05/13/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET87WW (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C6S00200
  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:bvrJ9ET87WW(2.07):bd05/13/2014:svnLENOVO:pn20C6S00200:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6S00200:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C6S00200
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1407945] Re: CVE-2014-9419

2015-03-24 Thread John Johansen
** Changed in: linux (Ubuntu Precise)
   Status: Fix Committed = Fix Released

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

Title:
  CVE-2014-9419

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-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 Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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:
  Fix Committed
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-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:
  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 Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New

[Kernel-packages] [Bug 1415632] Re: CVE-2014-9644

2015-03-24 Thread John Johansen
** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

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

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

Title:
  CVE-2014-9644

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-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 Lucid:
  Invalid
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Invalid
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic 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:
  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 Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source 

[Kernel-packages] [Bug 1425274] Re: CVE-2015-2042

2015-03-24 Thread John Johansen
** Changed in: linux (Ubuntu Utopic)
   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/1425274

Title:
  CVE-2015-2042

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-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 Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic 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:
  Fix Committed
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-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 Utopic:
  Fix Committed
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-lts-trusty source package 

[Kernel-packages] [Bug 1423757] Re: CVE-2015-1593

2015-03-24 Thread John Johansen
** Changed in: linux (Ubuntu Utopic)
   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/1423757

Title:
  CVE-2015-1593

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-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 Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic 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:
  Fix Committed
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-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 Utopic:
  Fix Committed
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-lts-trusty source package 

[Kernel-packages] [Bug 1425271] Re: CVE-2015-2041

2015-03-24 Thread John Johansen
** Changed in: linux (Ubuntu Utopic)
   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/1425271

Title:
  CVE-2015-2041

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-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 Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic 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:
  Fix Committed
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-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 Utopic:
  Fix Committed
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-lts-trusty source package 

[Kernel-packages] [Bug 1420027] Re: CVE-2015-1465

2015-03-24 Thread John Johansen
** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

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

Title:
  CVE-2015-1465

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:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
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-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Invalid
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Invalid
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
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:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Fix Committed
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic 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:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
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-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 Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in 

[Kernel-packages] [Bug 1430855] Re: [i915_bdw] fix GPU hangs on startup with BDW GT3

2015-03-24 Thread Timo Aaltonen
The commit is included in 3.16 and up, so not a concern for utopic or
vivid.

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

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

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

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

Title:
  [i915_bdw] fix GPU hangs on startup with BDW GT3

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

Bug description:
  Broadwell cpu's with Iris graphics fail to boot up properly, the GPU
  hangs on X startup. This is fixed since 3.16, and it needs a single
  commit to i915_bdw driver:

  commit 1d2866baf71e222308345ec745c20cbdb279f325
  Author: Ben Widawsky benjamin.widaw...@intel.com
  Date:   Fri Apr 18 18:04:28 2014 -0300

  drm/i915/bdw: enable eDRAM.

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

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


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

2015-03-24 Thread bugproxy
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 08:31 EDT---
comment test, please ignore~~

--- Comment From cdead...@us.ibm.com 2015-03-24 08:35 EDT---
another comment test, please ignore~~
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 10:51 EDT---
new comment, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:52 EDT---
comment test from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:53 EDT---
another comment from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:59 EDT---
3rd comment from rtc

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

Title:
  [Ubuntu 15.04] Enable perf to exploit 24x7 hardware counters

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Breno Henrique Leitao bren...@br.ibm.com - 2014-11-06 
12:52:04 ==
  Enable perf tool to exploit POWER 24x7 hardware counters

  Parts of the project:
  a) Some patches upstream and done
  b) Reset targets on remaining features still to be done (jit support, symbol 
names)

  == Comment: #16 - Breno Henrique Leitao bren...@br.ibm.com - 2015-02-24 
08:06:45 ==
  Initial patches already accepted by Canonical on 117275. Patchset posted to 
community, waiting on
  review. (I had posted a version of the patchset in Dec after fixing minor 
comments. Waiting to hear back from community )

  == Comment: #18 - Sukadev Bhattiprolu s...@us.ibm.com - 2015-02-25 16:18:34 
==
  There are two separate patch sets, one for the perf tool and other
  for the kernel. They are both available in mainline 3.19-rc4.

  === Perf tool patches (4)

  Patch 1/4:
  http://marc.info/?l=linuxppc-embeddedm=142067974403807w=2
  commit 688d4df
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:50 2015 -0800

  perf tools: Support parsing parameterized events

  Patch 2/4:
  http://marc.info/?l=linux-kernelm=142067973603799w=2
  commit aaea361
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:51 2015 -0800

  perf tools: Extend format_alias() to include event parameters

  Patch 3/4:
  http://marc.info/?l=linux-kernelm=142067971103796w=2
  commit 98a43e0
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:52 2015 -0800

  perf Documentation: Add event parameters

  Patch 4/4:
  http://marc.info/?l=linux-kernelm=142067968803787w=2
  commit f9ab9c1
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:53 2015 -0800

  perf tools: Document parameterized and symbolic events

  === Kernel patches(7)
  Patch 1/7:
  

[Kernel-packages] [Bug 1416506] Re: CVE-2015-1421

2015-03-24 Thread John Johansen
** Changed in: linux (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: Fix Committed = Fix Released

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

Title:
  CVE-2015-1421

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-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 Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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:
  Fix Committed
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-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 Committed
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-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 Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source 

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

2015-03-24 Thread bugproxy
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 08:31 EDT---
comment test, please ignore~~

--- Comment From cdead...@us.ibm.com 2015-03-24 08:35 EDT---
another comment test, please ignore~~
Hi ? Leann,

--- Comment From cdead...@us.ibm.com 2015-03-24 10:51 EDT---
new comment, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:52 EDT---
comment test from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:53 EDT---
another comment from rtc, please ignore

--- Comment From cdead...@us.ibm.com 2015-03-24 10:59 EDT---
3rd comment from rtc

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

Title:
  [Ubuntu 15.04] Enable perf to exploit 24x7 hardware counters

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Breno Henrique Leitao bren...@br.ibm.com - 2014-11-06 
12:52:04 ==
  Enable perf tool to exploit POWER 24x7 hardware counters

  Parts of the project:
  a) Some patches upstream and done
  b) Reset targets on remaining features still to be done (jit support, symbol 
names)

  == Comment: #16 - Breno Henrique Leitao bren...@br.ibm.com - 2015-02-24 
08:06:45 ==
  Initial patches already accepted by Canonical on 117275. Patchset posted to 
community, waiting on
  review. (I had posted a version of the patchset in Dec after fixing minor 
comments. Waiting to hear back from community )

  == Comment: #18 - Sukadev Bhattiprolu s...@us.ibm.com - 2015-02-25 16:18:34 
==
  There are two separate patch sets, one for the perf tool and other
  for the kernel. They are both available in mainline 3.19-rc4.

  === Perf tool patches (4)

  Patch 1/4:
  http://marc.info/?l=linuxppc-embeddedm=142067974403807w=2
  commit 688d4df
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:50 2015 -0800

  perf tools: Support parsing parameterized events

  Patch 2/4:
  http://marc.info/?l=linux-kernelm=142067973603799w=2
  commit aaea361
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:51 2015 -0800

  perf tools: Extend format_alias() to include event parameters

  Patch 3/4:
  http://marc.info/?l=linux-kernelm=142067971103796w=2
  commit 98a43e0
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:52 2015 -0800

  perf Documentation: Add event parameters

  Patch 4/4:
  http://marc.info/?l=linux-kernelm=142067968803787w=2
  commit f9ab9c1
  Author: Cody P Schafer c...@linux.vnet.ibm.com
  Date:   Wed Jan 7 17:13:53 2015 -0800

  perf tools: Document parameterized and symbolic events

  === Kernel patches(7)
  Patch 1/7:
  

[Kernel-packages] [Bug 1430952] Re: CVE-2015-2150

2015-03-24 Thread John Johansen
** Changed in: linux-lts-raring (Ubuntu Precise)
   Status: New = Invalid

** Description changed:

  Xen 3.3.x through 4.5.x and the Linux kernel through 3.19.1 do not
  properly restrict access to PCI command registers, which might allow
  local guest users to cause a denial of service (non-maskable interrupt
  and host crash) by disabling the (1) memory or (2) I/O decoding for a
  PCI Express device and then accessing the device, which triggers an
  Unsupported Request (UR) response.
  
- Break-Fix: - -
+ Break-Fix: - af6fc858a35b90e89ea7a7ee58e66628c55c776b

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

Title:
  CVE-2015-2150

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-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 Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  New
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:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic 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:
  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 Utopic:
  New
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package 

[Kernel-packages] [Bug 1416498] Re: CVE-2014-7822

2015-03-24 Thread John Johansen
** Changed in: linux (Ubuntu Precise)
   Status: Fix Committed = Fix Released

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

Title:
  CVE-2014-7822

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-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 Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic 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:
  Invalid
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 Utopic:
  Invalid
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package 

[Kernel-packages] [Bug 1413741] Re: CVE-2014-8159

2015-03-24 Thread John Johansen
** Changed in: linux-lts-raring (Ubuntu Precise)
   Status: New = Invalid

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New = Fix Released

** Description changed:

  The InfiniBand (IB) implementation in the Linux kernel package before
  2.6.32-504.12.2 on Red Hat Enterprise Linux (RHEL) 6 does not properly
  restrict use of User Verbs for registration of memory regions, which
  allows local users to access arbitrary physical memory locations, and
  consequently cause a denial of service (system crash) or gain
  privileges, by leveraging permissions on a uverbs device under
  /dev/infiniband/.
  
- Break-Fix: - -
+ Break-Fix: - local-2014-8159

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

Title:
  CVE-2014-8159

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-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 Lucid:
  Fix Released
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic 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:
  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-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 Utopic:
  Fix Released
Status in linux-armadaxp source package in 

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

2015-03-24 Thread 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/1436090

Title:
  kernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Periodically (every few days) I'm hitting this kernel bug, which
  causes the session to close and drops me back to the login screen. If
  I attempt to login it does some stuff (usual screen flashes) then
  drops me back to the login.

  It seems to be when I'm doing something related to an item on the top
  Unity panel. I thought for a while it was when I was trying to
  activate Skype from the icon it places in the panel (so I assumed
  Skype was at fault). But I've just had it happen too when attempting
  to pick Sound Settings from the audio panel icon.

  I'll be happy to provide other information if I can.

  The most recent example:
  --
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327041] [ cut 
here ]
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327045] kernel BUG at 
/build/buildd/linux-3.13.0/mm/slub.c:3365!
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327046] invalid opcode: 
 [#2] SMP 
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327048] Modules linked in: 
dm_crypt pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) cuse 
arc4 bnep rfcomm bluetooth binfmt_misc gpio_ich ath9k_htc a
  th9k_common ath9k_hw ath intel_rapl snd_hda_codec_hdmi x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_realtek mac80211 
snd_hda_intel crct10dif_pclmul snd_usb_audio snd_hda_codec crc32_pclmul 
snd_usbmidi_lib ghash_clmulni_intel snd_hwdep cfg80211 snd_pcm aesni_intel 
fglrx(POX) aes_x86_64 lrw gf128mul glue_helper snd_page_alloc ablk_helper 
cryptd snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq 
snd_seq_device snd_timer amd_iommu_v2 snd lpc_ich mei_me shpchp mei soundcore 
mac_hid parport_pc ppdev lp parport hid_generic usbhid hid usb_storage mxm_wmi 
ahci e1000e libahci wmi ptp pps_core
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327078] CPU: 4 PID: 20166 
Comm: Xorg Tainted: P  D W  OX 3.13.0-46-generic #79-Ubuntu
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327080] Hardware name: 
LENOVO IdeaCentre K330/To be filled by O.E.M., BIOS DKKT20AUS 03/16/2011
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327081] task: 
8800333c4800 ti: 8802a6e98000 task.ti: 8802a6e98000
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327082] RIP: 
0010:[811a2363]  [811a2363] kfree+0x133/0x140
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327088] RSP: 
0018:8802a6e99c78  EFLAGS: 00010246
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327089] RAX: 
0100 RBX: 88000228 RCX: 0001
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327090] RDX: 
0100 RSI: a01f2f55 RDI: 88000228
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327090] RBP: 
8802a6e99c90 R08:  R09: a042a1c6
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327091] R10: 
ea08a000 R11: 880424d24000 R12: 0002
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327092] R13: 
a01ba25e R14: 00011414 R15: 880172da1050
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327093] FS:  
7f6f6d4c29c0() GS:88043f50() knlGS:
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327094] CS:  0010 DS:  
ES:  CR0: 80050033
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327095] CR2: 
7f6f62e7 CR3: a9f98000 CR4: 000407e0
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327096] Stack:
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327097]  88000228 
0002 0070 8802a6e99ca0
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327099]  a01ba25e 
00011414 a01c151c 88000228
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327101]  00011414 
a042a085 88000228 880424a26280
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327103] Call Trace:
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327146]  
[a01ba25e] KCL_MEM_SmallBufferFree+0xe/0x10 [fglrx]
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327172]  
[a01c151c] drm_free+0xcc/0x1a0 [fglrx]
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327204]  
[a01f44a7] ? firegl_apl_loadDatabase+0xb7/0x280 [fglrx]
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327231]  
[a01d1e0c] ? firegl_cwddeci+0x17c/0x190 [fglrx]
  Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327257]  
[a01d1c50] ? 

[Kernel-packages] [Bug 1429821] Re: CVE-2015-0274

2015-03-24 Thread Mathew Hodson
** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: Confirmed = Invalid

** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
   Status: Confirmed = Invalid

** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
   Status: Confirmed = Invalid

** Changed in: linux-lts-backport-maverick (Ubuntu Trusty)
   Status: Confirmed = Invalid

** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
   Status: Confirmed = Invalid

** Changed in: linux-lts-backport-maverick (Ubuntu Vivid)
   Status: Confirmed = Invalid

** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
   Status: Confirmed = Invalid

** Changed in: linux-lts-backport-natty (Ubuntu Precise)
   Status: Confirmed = Invalid

** Changed in: linux-lts-backport-natty (Ubuntu Trusty)
   Status: Confirmed = Invalid

** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
   Status: Confirmed = Invalid

** Changed in: linux-lts-backport-natty (Ubuntu Vivid)
   Status: Confirmed = Invalid

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

Title:
  CVE-2015-0274

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:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
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-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Invalid
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Invalid
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Invalid
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
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:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
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-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:
  Invalid
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:
  Invalid
Status in linux-lts-backport-natty source package in Trusty:
  Invalid
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 

[Kernel-packages] [Bug 1416506] Re: CVE-2015-1421

2015-03-24 Thread Mathew Hodson
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Invalid

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

Title:
  CVE-2015-1421

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-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 Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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:
  New
Status in linux-lts-utopic 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 Committed
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-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 Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in 

[Kernel-packages] [Bug 1423391] Re: CVE-2014-9683

2015-03-24 Thread Mathew Hodson
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Invalid

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: Fix Committed = Invalid

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

Title:
  CVE-2014-9683

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-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 Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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-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:
  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 Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package 

[Kernel-packages] [Bug 1420027] Re: CVE-2015-1465

2015-03-24 Thread Mathew Hodson
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Invalid

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: Fix Committed = Invalid

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

Title:
  CVE-2015-1465

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:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
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-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Invalid
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Invalid
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
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 Committed
Status in linux-lts-utopic 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:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
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-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 Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in 

[Kernel-packages] [Bug 912230] Re: CVE-2011-4916

2015-03-24 Thread Mathew Hodson
** Description changed:

  /dev/pts/, /dev/tty* info disclosure
+ 
+ Break-Fix: - 0499680a42141d86417a8fbaa8c8db806bea1201
+ Break-Fix: -  a2ef990ab5a6705a356d146dd773a3b359787497

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

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New = Invalid

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: New = Invalid

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

Title:
  CVE-2011-4916

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-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
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-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux-lts-backport-oneiric source package in Lucid:
  Won't Fix
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Won't Fix
Status in linux-lts-saucy 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 Quantal:
  Won't Fix
Status in linux-armadaxp source package in Quantal:
  Won't Fix
Status in linux-ec2 source package in Quantal:
  Invalid
Status in linux-fsl-imx51 source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux-lts-raring source package in Quantal:
  Invalid
Status in linux-lts-saucy source package in Quantal:
  Invalid
Status in linux-mvl-dove source package in Quantal:
  Invalid
Status in linux-ti-omap4 source package in Quantal:
  Won't Fix
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux source package in Saucy:
  Won't Fix
Status in linux-armadaxp source package in Saucy:
  Invalid
Status in linux-ec2 source package in Saucy:
  Invalid
Status in linux-fsl-imx51 source package in Saucy:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in linux-lts-backport-oneiric source package in Saucy:
  Invalid
Status in linux-lts-quantal source package in Saucy:
  Invalid
Status in linux-lts-raring source package in Saucy:
  Invalid
Status in linux-lts-saucy source package in Saucy:
  Invalid
Status in linux-mvl-dove source package in Saucy:
  Invalid
Status in linux-ti-omap4 source package in Saucy:
  Won't Fix
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-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Invalid
Status in linux-lts-backport-natty source package in Trusty:
  Invalid
Status in linux-lts-backport-oneiric source package in Trusty:
  Invalid
Status in linux-lts-quantal 

[Kernel-packages] [Bug 1436090] [NEW] kernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365!

2015-03-24 Thread Phil Ayres
Public bug reported:

Periodically (every few days) I'm hitting this kernel bug, which causes
the session to close and drops me back to the login screen. If I attempt
to login it does some stuff (usual screen flashes) then drops me back to
the login.

It seems to be when I'm doing something related to an item on the top
Unity panel. I thought for a while it was when I was trying to activate
Skype from the icon it places in the panel (so I assumed Skype was at
fault). But I've just had it happen too when attempting to pick Sound
Settings from the audio panel icon.

I'll be happy to provide other information if I can.

The most recent example:
--
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327041] [ cut 
here ]
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327045] kernel BUG at 
/build/buildd/linux-3.13.0/mm/slub.c:3365!
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327046] invalid opcode:  
[#2] SMP 
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327048] Modules linked in: 
dm_crypt pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) cuse 
arc4 bnep rfcomm bluetooth binfmt_misc gpio_ich ath9k_htc a
th9k_common ath9k_hw ath intel_rapl snd_hda_codec_hdmi x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_realtek mac80211 
snd_hda_intel crct10dif_pclmul snd_usb_audio snd_hda_codec crc32_pclmul 
snd_usbmidi_lib ghash_clmulni_intel snd_hwdep cfg80211 snd_pcm aesni_intel 
fglrx(POX) aes_x86_64 lrw gf128mul glue_helper snd_page_alloc ablk_helper 
cryptd snd_seq_midi snd_seq_midi_event snd_rawmidi serio_raw snd_seq 
snd_seq_device snd_timer amd_iommu_v2 snd lpc_ich mei_me shpchp mei soundcore 
mac_hid parport_pc ppdev lp parport hid_generic usbhid hid usb_storage mxm_wmi 
ahci e1000e libahci wmi ptp pps_core
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327078] CPU: 4 PID: 20166 
Comm: Xorg Tainted: P  D W  OX 3.13.0-46-generic #79-Ubuntu
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327080] Hardware name: LENOVO 
IdeaCentre K330/To be filled by O.E.M., BIOS DKKT20AUS 03/16/2011
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327081] task: 
8800333c4800 ti: 8802a6e98000 task.ti: 8802a6e98000
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327082] RIP: 
0010:[811a2363]  [811a2363] kfree+0x133/0x140
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327088] RSP: 
0018:8802a6e99c78  EFLAGS: 00010246
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327089] RAX: 0100 
RBX: 88000228 RCX: 0001
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327090] RDX: 0100 
RSI: a01f2f55 RDI: 88000228
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327090] RBP: 8802a6e99c90 
R08:  R09: a042a1c6
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327091] R10: ea08a000 
R11: 880424d24000 R12: 0002
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327092] R13: a01ba25e 
R14: 00011414 R15: 880172da1050
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327093] FS:  
7f6f6d4c29c0() GS:88043f50() knlGS:
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327094] CS:  0010 DS:  
ES:  CR0: 80050033
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327095] CR2: 7f6f62e7 
CR3: a9f98000 CR4: 000407e0
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327096] Stack:
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327097]  88000228 
0002 0070 8802a6e99ca0
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327099]  a01ba25e 
00011414 a01c151c 88000228
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327101]  00011414 
a042a085 88000228 880424a26280
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327103] Call Trace:
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327146]  [a01ba25e] 
KCL_MEM_SmallBufferFree+0xe/0x10 [fglrx]
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327172]  [a01c151c] 
drm_free+0xcc/0x1a0 [fglrx]
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327204]  [a01f44a7] 
? firegl_apl_loadDatabase+0xb7/0x280 [fglrx]
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327231]  [a01d1e0c] 
? firegl_cwddeci+0x17c/0x190 [fglrx]
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327257]  [a01d1c50] 
? firegl_cwddeci_adl_handler+0x70/0xb0 [fglrx]
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327260]  [811a2b91] 
? __kmalloc+0x211/0x230
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327286]  [a01d1766] 
? Dispatch+0x1d6/0x240 [fglrx]
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327311]  [a01c10c3] 
? drm_alloc+0x133/0x1a0 [fglrx]
Mar 24 17:26:21 consected-sv1-001 kernel: [626030.327338]  [a01d129e] 
? 

[Kernel-packages] [Bug 1416498] Re: CVE-2014-7822

2015-03-24 Thread Mathew Hodson
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New = Invalid

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: New = Invalid

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

Title:
  CVE-2014-7822

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-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 Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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-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:
  Invalid
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 Utopic:
  Invalid
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status 

[Kernel-packages] [Bug 1068888] Re: CVE-2012-4530

2015-03-24 Thread Mathew Hodson
** Changed in: linux-lts-backport-maverick (Ubuntu Trusty)
   Status: New = Invalid

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

Title:
  CVE-2012-4530

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:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
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:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Released
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Fix Released
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  New
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Fix Released
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic 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-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in linux-lts-backport-oneiric source package in Saucy:
  Invalid
Status in linux source package in Trusty:
  Invalid
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:
  Invalid
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-backport-oneiric 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:
  New
Status in linux-lts-trusty source package in Trusty:
  Invalid

[Kernel-packages] [Bug 1380076] Re: Can't suspend on Surface Pro 3

2015-03-24 Thread Christopher M. Penalver
Keith McClelland, it would help immensely if you filed a new report via a 
terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Tags removed: latest-bios-3.11.0350
** Tags added: bios-outdated-3.11.0450

** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing

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

Title:
  Can't suspend on Surface Pro 3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my Surface Pro 3 when I suspend from the GUI nothing happens. Doing it 
manually also fails, and nothing appears in dmesg:
  #echo mem  /sys/power/state

  Error while writing to stdout
  write_loop: Invalid argument

  And, more interestingly:
  cat /sys/power/state

  freeze disk

  Using the not-so-good-and-apparently-unsupported:
  echo freeze  /sys/power/state

  does seem to successfully suspend, however I cannot resume from this
  (assumed to be a separate issue).

  I am using a modified utopic unicorn kernel compiled from git at 
kernel.ubuntu.com, with the following patch to enable mykeyboard to work:
  http://www.spinics.net/lists/linux-input/msg34918.html

  The official kernel behaves identically, as does vanilla 3.17 from the
  mainline folder of kernel-ppa.

  WORKAROUND: Use hibernate.

  ---
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jarrad 2491 F pulseaudio
   /dev/snd/controlC0:  jarrad 2491 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=178ac532-25db-4ef3-a587-f1fdd2649bf0
  InstallationDate: Installed on 2014-10-10 (57 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923)
  MachineType: Microsoft Corporation Surface Pro 3
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.4-surface3 
root=UUID=f6c17817-9127-4792-be23-a39a07e7f240 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.4-surface3 N/A
   linux-backports-modules-3.16.4-surface3  N/A
   linux-firmware   1.135
  Tags:  utopic
  Uname: Linux 3.16.4-surface3 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.11.0350
  dmi.board.asset.tag: 0
  dmi.board.name: Surface Pro 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.11.0350:bd10/16/2014:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.name: Surface Pro 3
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation

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

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


[Kernel-packages] [Bug 1435728] Re: HP Pavilion 13-b208tu wireless fails to resume (Broadcom BCM43142HM )

2015-03-24 Thread Christopher M. Penalver
Stuart Bishop, unfortunately testing the latest mainline kernel won't
help in this report as the proprietary module typically doesn't work
with an unmodified mainline kernel, and your chipset doesn't have an
open source variant AFAIK.

Despite this, could you please provide the missing information following
https://wiki.ubuntu.com/DebuggingKernelSuspend (please ignore for now
the request for the mainline kernel in the support article, just do it
in the Vivid repository kernel)?

** Summary changed:

- HP Pavilion 13-b208tu wireless fails to resume (Broadcom BCM43142HM )
+ [HP Pavilion Notebook - 13-b208tu] Broadcom BCM43142 wireless fails to resume 
from suspend

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

Title:
  [HP Pavilion Notebook - 13-b208tu] Broadcom BCM43142 wireless fails to
  resume from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The wifi connection on the HP 13-b208tu laptop (Broadcom BCM4365)
  fails during suspend or resume.

  This may be related to Bug 1432659. Also, per Bug 1434136 this laptop
  is running the latest version of the bios that boots Linux (F.24).

  Mar 23 22:55:48 aargh kernel: [ 3216.807039] PM: Syncing filesystems ... done.
  Mar 23 22:55:48 aargh kernel: [ 3216.822610] PM: Preparing system for mem 
sleep
  Mar 23 22:55:48 aargh kernel: [ 3216.822812] Freezing user space processes 
... (elapsed 0.001 seconds) done.
  Mar 23 22:55:48 aargh kernel: [ 3216.824475] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Mar 23 22:55:48 aargh kernel: [ 3216.825619] PM: Entering mem sleep
  Mar 23 22:55:48 aargh kernel: [ 3216.825633] Suspending console(s) (use 
no_console_suspend to debug)
  Mar 23 22:55:48 aargh kernel: [ 3216.826983] sd 0:0:0:0: [sda] Synchronizing 
SCSI cache
  Mar 23 22:55:48 aargh kernel: [ 3216.828497] cfg80211: Calling CRDA to update 
world regulatory domain
  Mar 23 22:55:48 aargh kernel: [ 3216.835195] sd 0:0:0:0: [sda] Stopping disk
  Mar 23 22:55:48 aargh kernel: [ 3216.886782] i8042 aux 00:03: System wakeup 
disabled by ACPI
  Mar 23 22:55:48 aargh kernel: [ 3216.886805] i8042 kbd 00:02: System wakeup 
enabled by ACPI
  Mar 23 22:55:48 aargh kernel: [ 3217.893531] [drm:stop_ring [i915]] *ERROR* 
render ring : timed out trying to stop ring
  Mar 23 22:55:48 aargh kernel: [ 3217.901564] PM: suspend of devices complete 
after 1074.780 msecs
  Mar 23 22:55:48 aargh kernel: [ 3217.941598] PM: late suspend of devices 
complete after 39.977 msecs
  Mar 23 22:55:48 aargh kernel: [ 3217.942146] r8169 :04:00.0: System 
wakeup enabled by ACPI
  Mar 23 22:55:48 aargh kernel: [ 3217.942187] xhci_hcd :00:14.0: System 
wakeup enabled by ACPI
  Mar 23 22:55:48 aargh kernel: [ 3217.957869] PM: noirq suspend of devices 
complete after 16.253 msecs
  Mar 23 22:55:48 aargh kernel: [ 3217.958141] ACPI: Preparing to enter system 
sleep state S3
  Mar 23 22:55:48 aargh kernel: [ 3218.025580] PM: Saving platform NVS memory
  Mar 23 22:55:48 aargh kernel: [ 3218.025586] Disabling non-boot CPUs ...
  Mar 23 22:55:48 aargh kernel: [ 3218.025609] intel_pstate CPU 1 exiting
  Mar 23 22:55:48 aargh kernel: [ 3218.025800] Broke affinity for irq 18
  Mar 23 22:55:48 aargh kernel: [ 3218.026820] kvm: disabling virtualization on 
CPU1
  Mar 23 22:55:48 aargh kernel: [ 3218.026825] smpboot: CPU 1 is now offline
  Mar 23 22:55:48 aargh kernel: [ 3218.027186] intel_pstate CPU 2 exiting
  Mar 23 22:55:48 aargh kernel: [ 3218.028368] kvm: disabling virtualization on 
CPU2
  Mar 23 22:55:48 aargh kernel: [ 3218.028376] smpboot: CPU 2 is now offline
  Mar 23 22:55:48 aargh kernel: [ 3218.028681] intel_pstate CPU 3 exiting
  Mar 23 22:55:48 aargh kernel: [ 3218.028782] Broke affinity for irq 42
  Mar 23 22:55:48 aargh kernel: [ 3218.029796] kvm: disabling virtualization on 
CPU3
  Mar 23 22:55:48 aargh kernel: [ 3218.029808] smpboot: CPU 3 is now offline
  Mar 23 22:55:48 aargh kernel: [ 3218.032593] ACPI: Low-level resume complete
  Mar 23 22:55:48 aargh kernel: [ 3218.032659] PM: Restoring platform NVS memory
  Mar 23 22:55:48 aargh kernel: [ 3218.033062] Enabling non-boot CPUs ...
  Mar 23 22:55:48 aargh kernel: [ 3218.033105] x86: Booting SMP configuration:
  Mar 23 22:55:48 aargh kernel: [ 3218.033106] smpboot: Booting Node 0 
Processor 1 APIC 0x2
  Mar 23 22:55:48 aargh kernel: [ 3218.045557] kvm: enabling virtualization on 
CPU1
  Mar 23 22:55:48 aargh kernel: [ 3218.047928] CPU1 is up
  Mar 23 22:55:48 aargh kernel: [ 3218.047959] smpboot: Booting Node 0 
Processor 2 APIC 0x1
  Mar 23 22:55:48 aargh kernel: [ 3218.060017] kvm: enabling virtualization on 
CPU2
  Mar 23 22:55:48 aargh kernel: [ 3218.062313] CPU2 is up
  Mar 23 22:55:48 aargh kernel: [ 3218.062330] smpboot: Booting Node 0 
Processor 3 APIC 0x3
  Mar 23 22:55:48 aargh kernel: [ 3218.074403] kvm: enabling virtualization on 
CPU3
  Mar 23 

[Kernel-packages] [Bug 912231] Re: CVE-2011-4917

2015-03-24 Thread Mathew Hodson
** Description changed:

  /proc/stat info disclosure
+ 
+ Break-Fix: - 0499680a42141d86417a8fbaa8c8db806bea1201
+ Break-Fix: - a2ef990ab5a6705a356d146dd773a3b359787497

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

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New = Invalid

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: New = Invalid

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

Title:
  CVE-2011-4917

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-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
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-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux-lts-backport-oneiric source package in Lucid:
  Won't Fix
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Won't Fix
Status in linux-lts-saucy 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 Quantal:
  Won't Fix
Status in linux-armadaxp source package in Quantal:
  Won't Fix
Status in linux-ec2 source package in Quantal:
  Invalid
Status in linux-fsl-imx51 source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux-lts-raring source package in Quantal:
  Invalid
Status in linux-lts-saucy source package in Quantal:
  Invalid
Status in linux-mvl-dove source package in Quantal:
  Invalid
Status in linux-ti-omap4 source package in Quantal:
  Won't Fix
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux source package in Saucy:
  Won't Fix
Status in linux-armadaxp source package in Saucy:
  Invalid
Status in linux-ec2 source package in Saucy:
  Invalid
Status in linux-fsl-imx51 source package in Saucy:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in linux-lts-backport-oneiric source package in Saucy:
  Invalid
Status in linux-lts-quantal source package in Saucy:
  Invalid
Status in linux-lts-raring source package in Saucy:
  Invalid
Status in linux-lts-saucy source package in Saucy:
  Invalid
Status in linux-mvl-dove source package in Saucy:
  Invalid
Status in linux-ti-omap4 source package in Saucy:
  Won't Fix
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-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Invalid
Status in linux-lts-backport-natty source package in Trusty:
  Invalid
Status in linux-lts-backport-oneiric source package in Trusty:
  Invalid
Status in linux-lts-quantal source 

[Kernel-packages] [Bug 1436084] [NEW] bluetooth pairing impossible BQ phone

2015-03-24 Thread mna
Public bug reported:

the bluetooth activation seem to be OK but no device were listed on the
BQ aquaris ubuntu phone :(

the test have been done with different bluetooth headset with the same
result : no device detected by the phone.

ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: bluez 4.101-0ubuntu24
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
CurrentDesktop: Unity
CurrentDmesg: dmesg: read kernel buffer failed: Operation not permitted
Date: Tue Mar 24 22:40:19 2015
InstallationDate: Installed on 2015-03-12 (12 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150312-002053)
Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 fixrtc 
lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=456 bootprof.lk_t=1690 
printk.disable_uart=1 boot_reason=0 datapart=/dev/mmcblk0p7 
systempart=/dev/mmcblk0p6 androidboot.serialno=JU001083 � 
lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=456 bootprof.lk_t=1690 
printk.disable_uart=1 boot_reason=0 datapart=/dev/mmcblk0p7 
systempart=/dev/mmcblk0p6 androidboot.serialno=JU001083 �
ProcModules:
 
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
hciconfig:
 hci0:  Type: BR/EDR  Bus: UART
BD Address: 4C:74:03:5F:13:48  ACL MTU: 1021:4  SCO MTU: 184:1
DOWN 
RX bytes:5489 acl:0 sco:0 events:338 errors:0
TX bytes:6152 acl:0 sco:0 commands:302 errors:0

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


** Tags: apport-bug armhf utopic

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

Title:
  bluetooth pairing impossible BQ phone

Status in bluez package in Ubuntu:
  New

Bug description:
  the bluetooth activation seem to be OK but no device were listed on
  the BQ aquaris ubuntu phone :(

  the test have been done with different bluetooth headset with the same
  result : no device detected by the phone.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: bluez 4.101-0ubuntu24
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  CurrentDesktop: Unity
  CurrentDmesg: dmesg: read kernel buffer failed: Operation not permitted
  Date: Tue Mar 24 22:40:19 2015
  InstallationDate: Installed on 2015-03-12 (12 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150312-002053)
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 
fixrtc lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=456 
bootprof.lk_t=1690 printk.disable_uart=1 boot_reason=0 datapart=/dev/mmcblk0p7 
systempart=/dev/mmcblk0p6 androidboot.serialno=JU001083 � 
lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=456 bootprof.lk_t=1690 
printk.disable_uart=1 boot_reason=0 datapart=/dev/mmcblk0p7 
systempart=/dev/mmcblk0p6 androidboot.serialno=JU001083 �
  ProcModules:
   
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  hciconfig:
   hci0:Type: BR/EDR  Bus: UART
BD Address: 4C:74:03:5F:13:48  ACL MTU: 1021:4  SCO MTU: 184:1
DOWN 
RX bytes:5489 acl:0 sco:0 events:338 errors:0
TX bytes:6152 acl:0 sco:0 commands:302 errors:0

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

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


[Kernel-packages] [Bug 1415632] Re: CVE-2014-9644

2015-03-24 Thread Mathew Hodson
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Invalid

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: Fix Committed = Invalid

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

Title:
  CVE-2014-9644

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-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 Lucid:
  Invalid
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Invalid
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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-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:
  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 Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source 

[Kernel-packages] [Bug 1434764] Re: External HDD stop working

2015-03-24 Thread Christopher M. Penalver
** Tags added: bios-outdated-a11

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

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

Title:
  External HDD  stop working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [ 1026.241834] blk_update_request: I/O error, dev sdc, sector 205592175
  [ 1026.241853] EXT4-fs warning (device dm-0): __ext4_read_dirblock:884: error 
-5 reading directory block (ino 6426347, block 0)
  [ 1441.263728] sd 6:0:0:0: rejecting I/O to offline device
  [ 1441.263737] blk_update_request: I/O error, dev sdc, sector 0
  [ 1441.265369] sd 6:0:0:0: rejecting I/O to offline device
  [ 1441.265375] blk_update_request: I/O error, dev sdc, sector 0
  [ 1441.265410] sd 6:0:0:0: rejecting I/O to offline device
  [ 1441.265415] Buffer I/O error on dev dm-0, logical block 13139968, lost 
sync page write
  [ 1441.265418] JBD2: Error -5 detected when updating journal superblock for 
dm-0-8.
  [ 1441.265423] sd 6:0:0:0: rejecting I/O to offline device
  [ 1441.265424] blk_update_request: I/O error, dev sdc, sector 0
  [ 1441.265447] sd 6:0:0:0: rejecting I/O to offline device
  [ 1441.265449] Buffer I/O error on dev dm-0, logical block 13139968, lost 
sync page write
  [ 1441.265451] JBD2: Error -5 detected when updating journal superblock for 
dm-0-8.
  [ 1441.265453] sd 6:0:0:0: rejecting I/O to offline device
  [ 1441.265454] blk_update_request: I/O error, dev sdc, sector 0
  [ 1441.265477] sd 6:0:0:0: rejecting I/O to offline device
  [ 1441.265479] Buffer I/O error on dev dm-0, logical block 13139968, lost 
sync page write
  [ 1441.265480] JBD2: Error -5 detected when updating journal superblock for 
dm-0-8.
  [ 1441.265502] sd 6:0:0:0: rejecting I/O to offline device
  [ 1441.265504] Buffer I/O error on dev dm-0, logical block 13139968, lost 
sync page write
  [ 1441.265506] JBD2: Error -5 detected when updating journal superblock for 
dm-0-8.
  [ 1441.265593] sd 6:0:0:0: rejecting I/O to offline device
  [ 1441.265595] Buffer I/O error on dev dm-0, logical block 0, lost sync page 
write
  [ 1441.267936] [ cut here ]
  [ 1441.267944] WARNING: CPU: 0 PID: 5697 at 
/build/buildd/linux-3.19.0/fs/block_dev.c:67 bdev_inode_switch_bdi+0x64/0x90()
  [ 1441.267945] Modules linked in: xts gf128mul dm_crypt uas usb_storage 
zfs(POE) zunicode(POE) zcommon(POE) znvpair(POE) spl(OE) zavl(POE) pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc hid_generic 
usbhid hid dcdbas i8k intel_rapl dm_multipath scsi_dh arc4 ath9k iosf_mbi 
ath9k_common ath9k_hw x86_pkg_temp_thermal intel_powerclamp coretemp ath 
snd_hda_codec_hdmi snd_hda_codec_realtek mac80211 snd_hda_codec_generic 
snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm kvm_intel 
cfg80211 kvm snd_seq_midi crct10dif_pclmul snd_seq_midi_event snd_rawmidi 
crc32_pclmul snd_seq ghash_clmulni_intel snd_seq_device cryptd serio_raw 
snd_timer snd soundcore ie31200_edac mei_me edac_core mei shpchp lpc_ich 
mac_hid parport_pc ppdev lp parport autofs4 i915 i2c_algo_bit drm_kms_helper
  [ 1441.267975]  psmouse ahci drm r8169 libahci mii video
  [ 1441.267980] CPU: 0 PID: 5697 Comm: umount Tainted: P U OE  
3.19.0-9-generic #9-Ubuntu
  [ 1441.267982] Hardware name: Dell Inc. Vostro 270s  /0XFWHV   , BIOS A09 
11/22/2012
  [ 1441.267983]  81ab8450 88013de0fd68 817c09b5 
0007
  [ 1441.267984]   88013de0fda8 8107595a 

  [ 1441.267986]  8800d4e3eb30 8800d4e3ebb8 81c6a800 
0083
  [ 1441.267988] Call Trace:
  [ 1441.267992]  [817c09b5] dump_stack+0x45/0x57
  [ 1441.267995]  [8107595a] warn_slowpath_common+0x8a/0xc0
  [ 1441.267996]  [81075a4a] warn_slowpath_null+0x1a/0x20
  [ 1441.267998]  [8122c034] bdev_inode_switch_bdi+0x64/0x90
  [ 1441.268000]  [8122cc98] __blkdev_put+0x78/0x1c0
  [ 1441.268001]  [8122d740] blkdev_put+0x50/0x160
  [ 1441.268005]  [811f56e1] kill_block_super+0x41/0x80
  [ 1441.268006]  [811f5a09] deactivate_locked_super+0x49/0x60
  [ 1441.268008]  [811f5e5c] deactivate_super+0x6c/0x80
  [ 1441.268010]  [81213c53] cleanup_mnt+0x43/0xa0
  [ 1441.268012]  [81213d02] __cleanup_mnt+0x12/0x20
  [ 1441.268014]  [81092c44] task_work_run+0xd4/0xf0
  [ 1441.268017]  [81015007] do_notify_resume+0x97/0xb0
  [ 1441.268020]  [817c7d8f] int_signal+0x12/0x17
  [ 1441.268021] ---[ end trace 88507186f399609d ]---

  ProblemType: Bug
  DistroRelease: 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
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  

[Kernel-packages] [Bug 1407945] Re: CVE-2014-9419

2015-03-24 Thread Mathew Hodson
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Invalid

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

Title:
  CVE-2014-9419

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-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 Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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-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:
  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 Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  

[Kernel-packages] [Bug 912227] Re: CVE-2011-4915

2015-03-24 Thread Mathew Hodson
** Changed in: linux (Ubuntu)
   Status: New = Invalid

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New = Invalid

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: New = Invalid

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

Title:
  CVE-2011-4915

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-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
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-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux-lts-backport-oneiric source package in Lucid:
  Won't Fix
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Won't Fix
Status in linux-lts-saucy 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 Quantal:
  Won't Fix
Status in linux-armadaxp source package in Quantal:
  Won't Fix
Status in linux-ec2 source package in Quantal:
  Invalid
Status in linux-fsl-imx51 source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux-lts-raring source package in Quantal:
  Invalid
Status in linux-lts-saucy source package in Quantal:
  Invalid
Status in linux-mvl-dove source package in Quantal:
  Invalid
Status in linux-ti-omap4 source package in Quantal:
  Won't Fix
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux source package in Saucy:
  Won't Fix
Status in linux-armadaxp source package in Saucy:
  Invalid
Status in linux-ec2 source package in Saucy:
  Invalid
Status in linux-fsl-imx51 source package in Saucy:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in linux-lts-backport-oneiric source package in Saucy:
  Invalid
Status in linux-lts-quantal source package in Saucy:
  Invalid
Status in linux-lts-raring source package in Saucy:
  Invalid
Status in linux-lts-saucy source package in Saucy:
  Invalid
Status in linux-mvl-dove source package in Saucy:
  Invalid
Status in linux-ti-omap4 source package in Saucy:
  Won't Fix
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-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Invalid
Status in linux-lts-backport-natty source package in Trusty:
  Invalid
Status in linux-lts-backport-oneiric source package in Trusty:
  Invalid
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 

[Kernel-packages] [Bug 1434581] Re: Console extremely slow with 3.13 and newer kernels for certified servers with Matrox G200er2 or similar

2015-03-24 Thread Christopher M. Penalver
** Tags added: latest-bios-2.3.3

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

Title:
  Console extremely slow with 3.13 and newer kernels for certified
  servers with Matrox G200er2 or similar

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

Bug description:
  When I first came across this issue I thought it was the same as bug
  #1316035 (https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1316035), but this bug seems to be about X and it is
  reporting xorg-server as the package with the issue. I've seen a
  report on the certification program already on this, but it was
  lacking follow-up and suggested a bug report, question 255332
  (https://answers.launchpad.net/ubuntu-certification/+question/255332).
  I've already asked about this on the forums, and received no replies.

  I originally encountered this issue due to having a bunch of Dell
  servers that I was testing with kernel 3.13 on 12.04. The text console
  is so slow that it is unusable when using vi or doing an operation
  similar to dpkg -l |grep xorg. Comparing the exact same system with
  kernel 3.2 or 3.11 loaded and running lsmod, vesafb is listed and
  performance is excellent. It is not listed on the 3.13 system. The
  same issue exists on 14.04 with the 3.13 or 3.16 kernel.

  Attempting to do modprobe vesa or modprobe vesafb returns modprobe:
  FATAL: Module vesa not found and modprobe: FATAL: Module vesafb not
  found respectively.

  Attempting to use uvesafb on this hardware results in a black screen.
  Attempting to use vga16fb results in good performance, but I am locked
  to 640x480. I tried to use fbset to force higher resolutions, but it
  either results in a distorted display or tells me there is not enough
  memory.

  I need a 1280x1024 console with performance equal to 12.04 with
  kernels 3.2-3.11. The server I'm using for testing is a Dell R320.

  This appears to be regression as I can duplicate it by simply doing a fresh 
install of 12.04.1 and not having the issue, while doing a fresh install of 
12.04.5, 14.04.1, or 14.04.2 results in a very slow console.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 13:17 seq
   crw-rw 1 root audio 116, 33 Mar 20 13:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.7
  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=3255aa87-ba68-4b74-bdb0-1112aba7d46e
  InstallationDate: Installed on 2015-03-20 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=fda4445f-efe2-4e93-9adb-ecaf6386f8cd ro consoleblank=0
  ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   linux-backports-modules-3.13.0-46-generic  N/A
   linux-firmware 1.127.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: root
  _MarkForUpload: True
  dmi.bios.date: 09/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.21
  dmi.board.name: 0R5KP9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.21:bd09/23/2013:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0R5KP9:rvrA09:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1435400] Re: linux: 3.16.0-34.45 -proposed tracker

2015-03-24 Thread Brad Figg
** Description changed:

  This bug is for tracking the 3.16.0-34.45 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, 23. March 2015 15:55 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 02:02 UTC
  kernel-stable-phase-changed:Tuesday, 24. March 2015 02:02 UTC
+ kernel-stable-Promote-to-proposed-end:Tuesday, 24. March 2015 22:32 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/1435400

Title:
  linux: 3.16.0-34.45 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.16.0-34.45 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, 23. March 2015 15:55 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 02:02 UTC
  kernel-stable-phase-changed:Tuesday, 24. March 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 24. March 2015 22:32 UTC

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

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


[Kernel-packages] [Bug 1415507] Re: CVE-2013-7421

2015-03-24 Thread Mathew Hodson
** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: Fix Committed = Invalid

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: Fix Committed = Invalid

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

Title:
  CVE-2013-7421

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-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 Lucid:
  Invalid
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Invalid
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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-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:
  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 Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source 

[Kernel-packages] [Bug 1435400] Re: linux: 3.16.0-34.45 -proposed tracker

2015-03-24 Thread Chris J Arges
Promoted to proposed:
 linux| 3.16.0-34.45  | utopic-proposed  | source
 linux-meta   | 3.16.0.34.35  | utopic-proposed  | source
 linux-signed | 3.16.0-34.45  | utopic-proposed  | source

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

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

Title:
  linux: 3.16.0-34.45 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.16.0-34.45 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, 23. March 2015 15:55 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 24. March 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 24. March 2015 02:02 UTC
  kernel-stable-phase-changed:Tuesday, 24. March 2015 02:02 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 24. March 2015 22:32 UTC

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

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


[Kernel-packages] [Bug 1436016] Re: linux: 3.13.0-49.81 -proposed tracker

2015-03-24 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New = Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) = Kamal Mostafa 
(kamalmostafa)

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

Title:
  linux: 3.13.0-49.81 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-49.81 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, 24. March 2015 18:55 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 24. March 2015 18:55 UTC

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

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


[Kernel-packages] [Bug 1413355] Re: package linux-image-3.13.0-44-generic 3.13.0-44.73 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-03-24 Thread Ronald Nelson
What can be done to fix this bug problem? I have a very limited knoledge
of ubuntu.

** Changed in: linux (Ubuntu)
   Status: Confirmed = Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/linux/+question/264141

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

Title:
  package linux-image-3.13.0-44-generic 3.13.0-44.73 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  The are others bugs in my system which i will like them to be debug.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-44-generic 3.13.0-44.73
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  billmax1918 F pulseaudio
  Date: Wed Jan 21 18:08:14 2015
  DuplicateSignature: 
package:linux-image-3.13.0-44-generic:3.13.0-44.73:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=0dcf1890-ecb0-43c4-a41e-1c0f0b1f7fc1
  InstallationDate: Installed on 2014-11-12 (70 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 
(20140204)
  MachineType: Hewlett-Packard HP ProBook 4530s
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=d43f07be-7d35-4ad3-897f-3b49bee28f2e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1
  SourcePackage: linux
  Title: package linux-image-3.13.0-44-generic 3.13.0-44.73 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-11-26 (56 days ago)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SRR Ver. F.28
  dmi.board.name: 167C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 22.23
  dmi.chassis.asset.tag: CNU1343T8S
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.28:bd06/26/2012:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.23:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4530s
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 927885] Re: CVE-2011-2393

2015-03-24 Thread Mathew Hodson
** Changed in: linux (Ubuntu)
   Status: New = Invalid

** Changed in: linux-lts-quantal (Ubuntu Precise)
   Status: New = Invalid

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: New = Invalid

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

Title:
  CVE-2011-2393

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-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
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-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux-lts-backport-oneiric source package in Lucid:
  Won't Fix
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Won't Fix
Status in linux-lts-saucy 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-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in linux-lts-backport-oneiric source package in Saucy:
  Invalid
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-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Invalid
Status in linux-lts-backport-natty source package in Trusty:
  Invalid
Status in linux-lts-backport-oneiric source package in Trusty:
  Invalid
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-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  New
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Invalid
Status in linux-lts-backport-natty source package in Utopic:
  Invalid
Status in linux-lts-backport-oneiric source package in Utopic:
  Invalid
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid

Bug description:
  The Neighbor Discovery (ND) protocol implementation in the IPv6 stack
  in FreeBSD, NetBSD, and possibly other BSD-based operating systems
  allows remote attackers to cause a denial of service (CPU consumption
  

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

2015-03-24 Thread Benedikt
apport information

** Attachment added: RfKill.txt
   https://bugs.launchpad.net/bugs/1435898/+attachment/4354579/+files/RfKill.txt

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


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

2015-03-24 Thread Benedikt
apport information

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


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

2015-03-24 Thread 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/1435898

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


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

2015-03-24 Thread Benedikt
apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1435898/+attachment/4354573/+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/1435898

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1435898] UdevLog.txt

2015-03-24 Thread Benedikt
apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1435898/+attachment/4354581/+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/1435898

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


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

2015-03-24 Thread Benedikt
apport information

** Attachment added: PulseList.txt
   
https://bugs.launchpad.net/bugs/1435898/+attachment/4354578/+files/PulseList.txt

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


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

2015-03-24 Thread Benedikt
apport information

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


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

2015-03-24 Thread Benedikt
apport information

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

2015-03-24 Thread Jordan Curzon
To add to my comment just above, we have found a workload that is not
under own our control (which limits what we can do with it, including
sharing it) but which exacerbates the issue on our systems. This
workload causes the issue less than 5% of the time and that gives us the
chance to look at what callers are using dst_release on the dst in
question (the one that meets conditions A, B, and C; ABC dst). To
clarify, failure at this point for us is when the dst-ref_cnt=1 during
free_fib_info_rcu, success is when dst-ref_cnt=0 and free_fib_info_rcu
calls dst_destroy on it's nh_rth_input member.

In both failure and non-failure scenarios the only two callers we see on
are a single call to ipv4_pktinfo_prepare, and many calls to
inet_sock_destruct, and tcp_data_queue. That likely eliminates a unique
function call to dst_release that can be identified as missing in
failure scenarios. My interpretation is that a single call to
inet_sock_destruct or tcp_data_queue is failing to occur when in the
failure scenario.

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

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in The Linux Kernel:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Utopic:
  Confirmed

Bug description:
  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

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

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


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

2015-03-24 Thread Benedikt
apport information

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


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

2015-03-24 Thread Benedikt
apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1435898/+attachment/4354582/+files/WifiSyslog.txt

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1435898] AudioDevicesInUse.txt

2015-03-24 Thread Benedikt
apport information

** Attachment added: AudioDevicesInUse.txt
   
https://bugs.launchpad.net/bugs/1435898/+attachment/4354568/+files/AudioDevicesInUse.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/1435898

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1435898] Re: Can not start (kde5) Desktop: Intel driver Failure

2015-03-24 Thread Benedikt
apport information

** Tags added: apport-collected vivid

** Description changed:

  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.
  
  Dmesg shows several oopses in the intel driver:
  
  invalid max DP link bw val 0, using 1.62Gps
  
  and
  
  compute-config() on unknown output!
  
  Will collect logs shortly.
  
  I think this problem occurs since the update to 3.19.0-9.
  
  Kernel 4.0-rc5 tested with the same problem.
+ --- 
+ ApportVersion: 2.16.2-0ubuntu4
+ Architecture: amd64
+ DistroRelease: Ubuntu 15.04
+ HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
+ InstallationDate: Installed on 2014-12-21 (93 days ago)
+ InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
+ MachineType: LENOVO 20354
+ NonfreeKernelModules: nvidia
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
+ RelatedPackageVersions:
+  linux-restricted-modules-3.19.0-10-generic N/A
+  linux-backports-modules-3.19.0-10-generic  N/A
+  linux-firmware 1.143
+ Tags:  vivid vivid
+ Uname: Linux 3.19.0-10-generic x86_64
+ UnreportableReason: The report belongs to a package that is not installed.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/20/2014
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: 9BCN29WW
+ dmi.board.asset.tag: No Asset Tag
+ dmi.board.name: Lancer 5A5
+ dmi.board.vendor: LENOVO
+ dmi.board.version: 31900058WIN
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Lenovo Z50-70
+ dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
+ dmi.product.name: 20354
+ dmi.product.version: Lenovo Z50-70
+ dmi.sys.vendor: LENOVO

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1435898/+attachment/4354567/+files/AlsaInfo.txt

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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

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

2015-03-24 Thread Benedikt
apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1435898/+attachment/4354575/+files/ProcEnviron.txt

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


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

2015-03-24 Thread Benedikt
apport information

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/1435898/+attachment/4354569/+files/CRDA.txt

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


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

2015-03-24 Thread Benedikt
apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/1435898/+attachment/4354571/+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/1435898

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1434581] Re: Console extremely slow with 3.13 and newer kernels for certified servers with Matrox G200er2 or similar

2015-03-24 Thread Mike Jester
I tested more mainline kernels: 3.2.0 through 3.10.0. The corresponding
Ubuntu kernels (ex: lts-quantal 3.5.0-54 vs mainline 3.5.0) work
properly. The ones from mainline all black screen.

If I go to / and do find . -name vesafb.ko only the Ubuntu kernels from
3.11 and earlier have the file.

Was this driver added by the Ubuntu kernel team but left out of 3.13 and
3.16?

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

Title:
  Console extremely slow with 3.13 and newer kernels for certified
  servers with Matrox G200er2 or similar

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I first came across this issue I thought it was the same as bug
  #1316035 (https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1316035), but this bug seems to be about X and it is
  reporting xorg-server as the package with the issue. I've seen a
  report on the certification program already on this, but it was
  lacking follow-up and suggested a bug report, question 255332
  (https://answers.launchpad.net/ubuntu-certification/+question/255332).
  I've already asked about this on the forums, and received no replies.

  I originally encountered this issue due to having a bunch of Dell
  servers that I was testing with kernel 3.13 on 12.04. The text console
  is so slow that it is unusable when using vi or doing an operation
  similar to dpkg -l |grep xorg. Comparing the exact same system with
  kernel 3.2 or 3.11 loaded and running lsmod, vesafb is listed and
  performance is excellent. It is not listed on the 3.13 system. The
  same issue exists on 14.04 with the 3.13 or 3.16 kernel.

  Attempting to do modprobe vesa or modprobe vesafb returns modprobe:
  FATAL: Module vesa not found and modprobe: FATAL: Module vesafb not
  found respectively.

  Attempting to use uvesafb on this hardware results in a black screen.
  Attempting to use vga16fb results in good performance, but I am locked
  to 640x480. I tried to use fbset to force higher resolutions, but it
  either results in a distorted display or tells me there is not enough
  memory.

  I need a 1280x1024 console with performance equal to 12.04 with
  kernels 3.2-3.11. The server I'm using for testing is a Dell R320.

  This appears to be regression as I can duplicate it by simply doing a fresh 
install of 12.04.1 and not having the issue, while doing a fresh install of 
12.04.5, 14.04.1, or 14.04.2 results in a very slow console.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 13:17 seq
   crw-rw 1 root audio 116, 33 Mar 20 13:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.7
  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=3255aa87-ba68-4b74-bdb0-1112aba7d46e
  InstallationDate: Installed on 2015-03-20 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=fda4445f-efe2-4e93-9adb-ecaf6386f8cd ro consoleblank=0
  ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   linux-backports-modules-3.13.0-46-generic  N/A
   linux-firmware 1.127.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: root
  _MarkForUpload: True
  dmi.bios.date: 09/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.21
  dmi.board.name: 0R5KP9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.21:bd09/23/2013:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0R5KP9:rvrA09:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1435898] [NEW] Can not start (kde5) Desktop: Intel driver Failure

2015-03-24 Thread Benedikt
Public bug reported:

Kubuntu 15.04 start without problems to the display manager sddm. If I
enter my password the display is blank for a second and then does
kubuntu load forever the desktop environment.

Dmesg shows several oopses in the intel driver:

invalid max DP link bw val 0, using 1.62Gps

and

compute-config() on unknown output!

Will collect logs shortly.

I think this problem occurs since the update to 3.19.0-9.

Kernel 4.0-rc5 tested with the same problem.

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

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  New

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  Will collect logs shortly.

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.

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

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


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

2015-03-24 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:

apport-collect 1435946

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

Title:
  IBM Power8 PPC MAAS images booting with no network

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The latest daily hwe-u image for MAAS seems to lack network
  connectivity. Along with the below error, I cannot ssh or ping the
  installation. I will follow up with further information once the
  machine becomes available in the coming weeks.

  Ubuntu 14.04.2 LTS ubuntu hvc0

  ubuntu login: Can not apply stage final, no datasource found! Likely bad
  things to come!
  
  Traceback (most recent call last):
File /usr/bin/cloud-init, line 318, in main_modules
  init.fetch()
File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 308,
  in fetch
  return self._get_data_source()
File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 236,
  in _get_data_source
  pkg_list)
File /usr/lib/python2.7/dist-packages/cloudinit/sources/__init__.py,
  line 260, in find_source
  raise DataSourceNotFoundException(msg)
  DataSourceNotFoundException: Did not find any data source, searched
  classes: ()
  

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

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


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

2015-03-24 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New = Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques 
(henrix)

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

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

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

Bug description:
  This bug is for tracking the 3.16.0-34.45~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, 24. March 2015 02:00 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 24. March 2015 02:00 UTC
  kernel-stable-master-bug:1435400

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

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


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

2015-03-24 Thread Benedikt
apport information

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1435898] Re: Can not start (kde5) Desktop: Intel driver Failure

2015-03-24 Thread Benedikt
** Description changed:

  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.
  
  Dmesg shows several oopses in the intel driver:
  
  invalid max DP link bw val 0, using 1.62Gps
  
  and
  
  compute-config() on unknown output!
  
- Will collect logs shortly.
- 
  I think this problem occurs since the update to 3.19.0-9.
  
  Kernel 4.0-rc5 tested with the same problem.
- --- 
+ ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
-  linux-restricted-modules-3.19.0-10-generic N/A
-  linux-backports-modules-3.19.0-10-generic  N/A
-  linux-firmware 1.143
+  linux-restricted-modules-3.19.0-10-generic N/A
+  linux-backports-modules-3.19.0-10-generic  N/A
+  linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1435946] [NEW] IBM Power8 PPC MAAS images booting with no network

2015-03-24 Thread Mike Rushton
Public bug reported:

The latest daily hwe-u image for MAAS seems to lack network
connectivity. Along with the below error, I cannot ssh or ping the
installation. I will follow up with further information once the machine
becomes available in the coming weeks.

Ubuntu 14.04.2 LTS ubuntu hvc0

ubuntu login: Can not apply stage final, no datasource found! Likely bad
things to come!

Traceback (most recent call last):
  File /usr/bin/cloud-init, line 318, in main_modules
init.fetch()
  File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 308,
in fetch
return self._get_data_source()
  File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 236,
in _get_data_source
pkg_list)
  File /usr/lib/python2.7/dist-packages/cloudinit/sources/__init__.py,
line 260, in find_source
raise DataSourceNotFoundException(msg)
DataSourceNotFoundException: Did not find any data source, searched
classes: ()


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

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

Title:
  IBM Power8 PPC MAAS images booting with no network

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The latest daily hwe-u image for MAAS seems to lack network
  connectivity. Along with the below error, I cannot ssh or ping the
  installation. I will follow up with further information once the
  machine becomes available in the coming weeks.

  Ubuntu 14.04.2 LTS ubuntu hvc0

  ubuntu login: Can not apply stage final, no datasource found! Likely bad
  things to come!
  
  Traceback (most recent call last):
File /usr/bin/cloud-init, line 318, in main_modules
  init.fetch()
File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 308,
  in fetch
  return self._get_data_source()
File /usr/lib/python2.7/dist-packages/cloudinit/stages.py, line 236,
  in _get_data_source
  pkg_list)
File /usr/lib/python2.7/dist-packages/cloudinit/sources/__init__.py,
  line 260, in find_source
  raise DataSourceNotFoundException(msg)
  DataSourceNotFoundException: Did not find any data source, searched
  classes: ()
  

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

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


[Kernel-packages] [Bug 1403653] Re: Kworker takes 100% CPU after installing OSX Yosemite upgrade

2015-03-24 Thread Zaf
Confirming the bug.
kernel = 3.16.0-33-generic
Ubuntu 14.04.2 LTS

for me it was gpe06. Fixed using following
http://sudoremember.blogspot.com/2013/05/high-cpu-usage-due-to-
kworker.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/1403653

Title:
  Kworker takes 100% CPU after installing OSX Yosemite upgrade

Status in The Linux Kernel:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  When running on a Macbook Pro Retina that has had its OSX install
  upgraded to Yosemite, a kworker process constantly takes 100% CPU.

  When grepping for large values in  /sys/firmware/acpi/interrupts, this
  one stands out:

  /sys/firmware/acpi/interrupts/gpe66: 2510732   enabled

  Trying to disable it with

  echo disable  /sys/firmware/acpi/interrupts/gpe66

  makes the CPU load go away.

  This will also prevent installation of Ubuntu, because if you try to
  install when kworker is running causes ubiquity to hang while trying
  to format the disk.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.38
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpakkane   2346 F pulseaudio
   /dev/snd/controlC0:  jpakkane   2346 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec 17 23:36:32 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-17 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=7196f220-ff77-4982-bfc1-03506a8013f7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B11.1408291433
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B11.1408291433:bd08/29/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1303552] Re: kernel BUG at include/net/cfg80211.h:3150!

2015-03-24 Thread Christopher M. Penalver
** No longer affects: bcmwl (Ubuntu)

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

Title:
  kernel BUG at include/net/cfg80211.h:3150!

Status in linux package in Ubuntu:
  Expired

Bug description:
  error happened after installing broadcom divers for an Dell Latitude
  X300

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-23-generic 3.13.0-23.45
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  NonfreeKernelModules: wl
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  recovering   1994 F pulseaudio
recovering   2764 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Sun Apr  6 20:06:57 2014
  Failure: oops
  HibernationDevice: RESUME=UUID=47dbaa7f-e734-42a9-ba56-8fab02aa7559
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 002: ID 413c:8000 Dell Computer Corp. BC02 Bluetooth Adapter
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Computer Corporation Latitude X300
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: kernel BUG at include/net/cfg80211.h:3150!
  UpgradeStatus: Upgraded to trusty on 2014-04-07 (0 days ago)
  dmi.bios.date: 08/31/2004
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: A08
  dmi.board.name: PP
  dmi.board.vendor: Dell Computer Corporation
  dmi.board.version: X04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.chassis.version: 00h
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrA08:bd08/31/2004:svnDellComputerCorporation:pnLatitudeX300:pvrA08:rvnDellComputerCorporation:rnPP:rvrX04:cvnDellComputerCorporation:ct8:cvr00h:
  dmi.product.name: Latitude X300
  dmi.product.version: A08
  dmi.sys.vendor: Dell Computer Corporation

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

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


[Kernel-packages] [Bug 1436016] Re: linux: 3.13.0-49.81 -proposed tracker

2015-03-24 Thread Brad Figg
All builds are complete, packages in this bug can be copied to
-proposed.

Derivative packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-keystone - bug 1436131

Backport packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-lts-trusty (precise1) - bug 1436132

** Changed in: kernel-sru-workflow/prepare-package
   Status: New = Fix Released

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

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

** Changed in: kernel-sru-workflow/package-testing
   Status: New = Confirmed

** Description changed:

  This bug is for tracking the 3.13.0-49.81 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, 24. March 2015 18:55 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 24. March 2015 18:55 UTC
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Wednesday, 25. March 2015 02:03 UTC
+ kernel-stable-Promote-to-proposed-start:Wednesday, 25. March 2015 02:03 UTC
+ kernel-stable-phase-changed:Wednesday, 25. March 2015 02:03 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/1436016

Title:
  linux: 3.13.0-49.81 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-49.81 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, 24. March 2015 18:55 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Wednesday, 25. March 2015 02:03 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 25. March 2015 02:03 UTC
  kernel-stable-phase-changed:Wednesday, 25. March 2015 02:03 UTC

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

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


[Kernel-packages] [Bug 1433937] Re: [Lenovo E?50] System got hang after resumed back from S3 , hibernate or hybird_sleep.

2015-03-24 Thread Gabriel Zhi Chen
** Summary changed:

- [Lenovo E450] System got hang after resumed back from S3 , hibernate or 
hybird_sleep.
+ [Lenovo E?50] System got hang after resumed back from S3 , hibernate or 
hybird_sleep.

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

Title:
  [Lenovo E?50] System got hang after resumed back from S3 , hibernate
  or hybird_sleep.

Status in HWE Next Project:
  New
Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic)
  CID : 201409-15790 Lenovo E450 (I+A) with 14.04.2 (utopic)
  CID : 201411-16167 Lenovo E550 (I+A) with 14.04.2 (utopic)

  Steps:
  1. Install 14.04.2 on E450.
  2. Log in system and install fglrx.
  3. Reboot system.
  4. Log in system again
  5. Click 'Suspend' from gear list on the top right corner of screen.
  6. Make sure system enter S3, then press 'Fn' to wake it up.

  Expected result:
  System resumed back smoothly.

  Actual result:
  System got hang after resumed back.

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

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

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


[Kernel-packages] [Bug 1433891] Re: [Lenovo E?50 I+A] There is no 'HDMI / DisplayPort' selection in output tab of Sound Setting when plug in HDMI cable on the port.

2015-03-24 Thread Gabriel Zhi Chen
** Summary changed:

- [Lenovo E450 I+A] There is no 'HDMI / DisplayPort' selection in output tab of 
Sound Setting when plug in HDMI cable on the port.
+ [Lenovo E?50 I+A] There is no 'HDMI / DisplayPort' selection in output tab of 
Sound Setting when plug in HDMI cable on the port.

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

Title:
  [Lenovo E?50 I+A] There is no 'HDMI / DisplayPort' selection in output
  tab of Sound Setting when plug in HDMI cable on the port.

Status in HWE Next Project:
  New
Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic)
  CID : 201411-16167 Lenovo E550 (I+A) with 14.04.2 (utopic)
  CID : 201409-15790 Lenovo E450 (I+A) with 14.04.2 (utopic)

  Steps:
  1. Install 14.04.2 on E450.
  2. Connect HDMI cable.
  3. Navigate to System setting - Sound - output, observe the result.
  4. Un-plug HDMI cable, then install fglrx.
  5. Reboot system.
  6. Connect HDMI cable.
  7. Navigate to System setting - Sound - output, observe the result.

  Expected result:
  Step 3 and 7, there should be a 'HDMI / DisplayPort' selection in output tab

  Actual result:
  There is no 'HDMI / DisplayPort' selection in output tab

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

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

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


[Kernel-packages] [Bug 1436132] [NEW] linux-lts-trusty: 3.13.0-49.81~precise1 -proposed tracker

2015-03-24 Thread Brad Figg
Public bug reported:

This bug is for tracking the 3.13.0-49.81~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:Wednesday, 25. March 2015 02:02 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Wednesday, 25. March 2015 02:02 UTC
kernel-stable-master-bug:1436016

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

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

** Affects: kernel-sru-workflow/package-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 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-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 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-lts-trusty (Ubuntu)
 Importance: Medium
 Status: New

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


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

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

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

** Tags added: precise

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

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

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

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

** Also affects: kernel-sru-workflow/prepare-package-signed
   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/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/package-testing
   Importance: Undecided = Medium

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

** 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-meta
   Importance: Undecided = Medium

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

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

** Changed in: 

[Kernel-packages] [Bug 1436147] [NEW] Ubuntu 14.04 LTS support release does not return to signon screen after suspend mode is woken up

2015-03-24 Thread Michael E. Slowinski
Public bug reported:

I am running Ubnutu 14.04 LTS. I can put my computer into suspend mode
successfully. But, when I try to waken the computer from suspend mode, I
never get the signon screen. I just get a blank screen and linux seems
to be in some type of loop. I have to power down my computer to get out
of this situation. Quite annoying to say the least. Christopher M.
Penalver said to assign/subscribe him to this bug.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-46-generic 3.13.0-46.79
ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  michael1881 F pulseaudio
 /dev/snd/controlC1:  michael1881 F pulseaudio
CurrentDesktop: Unity
Date: Tue Mar 24 22:52:53 2015
HibernationDevice: RESUME=UUID=b002383e-573d-44a8-b7c8-0e2bb5f9e517
InstallationDate: Installed on 2014-07-14 (253 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
IwConfig:
 eth0  no wireless extensions.
 
 eth1  no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=fe2c6d32-094c-40c4-8713-eee378320a08 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-46-generic N/A
 linux-backports-modules-3.13.0-46-generic  N/A
 linux-firmware 1.127.11
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080009
dmi.board.name: P4P800SE
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 2.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080009:bd12/13/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerInc.:rnP4P800SE:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

Title:
  Ubuntu 14.04 LTS support release does not return to signon screen
  after suspend mode is woken up

Status in linux package in Ubuntu:
  New

Bug description:
  I am running Ubnutu 14.04 LTS. I can put my computer into suspend mode
  successfully. But, when I try to waken the computer from suspend mode,
  I never get the signon screen. I just get a blank screen and linux
  seems to be in some type of loop. I have to power down my computer to
  get out of this situation. Quite annoying to say the least.
  Christopher M. Penalver said to assign/subscribe him to this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-46-generic 3.13.0-46.79
  ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1881 F pulseaudio
   /dev/snd/controlC1:  michael1881 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar 24 22:52:53 2015
  HibernationDevice: RESUME=UUID=b002383e-573d-44a8-b7c8-0e2bb5f9e517
  InstallationDate: Installed on 2014-07-14 (253 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=fe2c6d32-094c-40c4-8713-eee378320a08 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   

[Kernel-packages] [Bug 1091187] Re: CVE-2012-5374

2015-03-24 Thread Mathew Hodson
This doesn't affect trusty and utopic according to
http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-5374.html

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

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

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

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

Title:
  CVE-2012-5374

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-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
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-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux-lts-backport-oneiric source package in Lucid:
  Invalid
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  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-fsl-imx51 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Fix Released
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy 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-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in linux-lts-backport-oneiric source package in Saucy:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Invalid
Status in linux-lts-backport-natty source package in Trusty:
  Invalid
Status in linux-lts-backport-oneiric source package in Trusty:
  Invalid
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-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Invalid
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Invalid
Status in linux-lts-backport-natty source package in Utopic:
  Invalid
Status in linux-lts-backport-oneiric source package in Utopic:
  Invalid
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-mvl-dove source package in Utopic:
  Invalid
Status in linux-ti-omap4 source package in Utopic:
  Invalid

Bug description:
  The CRC32C feature in the Btrfs implementation 

[Kernel-packages] [Bug 1102374] Re: CVE-2013-0190

2015-03-24 Thread Mathew Hodson
This doesn't affect vivid according to http://people.canonical.com
/~ubuntu-security/cve/2013/CVE-2013-0190.html

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

** Changed in: linux-lts-backport-maverick (Ubuntu Trusty)
   Status: New = Invalid

** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
   Status: New = Invalid

** Changed in: linux-lts-backport-natty (Ubuntu Trusty)
   Status: New = Invalid

** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
   Status: New = Invalid

** Changed in: linux-lts-backport-oneiric (Ubuntu Trusty)
   Status: New = Invalid

** Changed in: linux-lts-backport-oneiric (Ubuntu Utopic)
   Status: New = Invalid

** Changed in: linux-lts-saucy (Ubuntu Lucid)
   Status: New = Invalid

** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: New = Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New = Invalid

** Changed in: linux-lts-saucy (Ubuntu Utopic)
   Status: New = Invalid

** Changed in: linux-lts-saucy (Ubuntu Vivid)
   Status: New = Invalid

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

Title:
  CVE-2013-0190

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:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
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-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Released
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Fix Released
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Oneiric:
  Invalid
Status in linux-lts-backport-natty source package in Oneiric:
  Invalid
Status in linux-lts-backport-oneiric source package in Oneiric:
  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:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Fix Released
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:
  Invalid
Status in linux-lts-utopic 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-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid

[Kernel-packages] [Bug 1435898] Re: Can not start (kde5) Desktop: Intel driver Failure

2015-03-24 Thread Christopher M. Penalver
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.0-rc5 latest-bios-9bcn29ww regression-potential

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

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

Title:
  Can not start (kde5) Desktop: Intel driver Failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kubuntu 15.04 start without problems to the display manager sddm. If I
  enter my password the display is blank for a second and then does
  kubuntu load forever the desktop environment.

  Dmesg shows several oopses in the intel driver:

  invalid max DP link bw val 0, using 1.62Gps

  and

  compute-config() on unknown output!

  I think this problem occurs since the update to 3.19.0-9.

  Kernel 4.0-rc5 tested with the same problem.
  ---
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (93 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro xforcevesa quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  Tags:  vivid vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1436137] [NEW] Touchpad DLL0662:00 06CB:2985 detected as a SynPS/2 Synaptics TouchPad an, making 3 / 4-finger gesture does not work after upgrade on 14.04.1

2015-03-24 Thread Po-Hsu Lin
Public bug reported:

CID: 201404-14997 Dell Vostro 3546

The touchpad was detected as DLL0662:00 06CB:2985 on 14.04.1 stock image 
(3.13.0-32)
And it works with three / four finger tapping gesture.

But after upgraded to 3.13.0-48, it's detected as SynPS/2 Synaptics TouchPad, 
therefore it can't do three / four finger tapping.
(bug 1384042)

ubuntu@201404-14997:~$ xinput list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPadid=12   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ Sleep Button  id=9[slave  keyboard (3)]
↳ Integrated_Webcam_HD  id=10   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)]
↳ Dell WMI hotkeys  id=13   [slave  keyboard (3)]

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-48-generic 3.13.0-48.80
ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
Uname: Linux 3.13.0-48-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ubuntu 1415 F pulseaudio
 /dev/snd/controlC0:  ubuntu 1415 F pulseaudio
CurrentDesktop: Unity
Date: Tue Mar 24 22:11:26 2015
HibernationDevice: RESUME=UUID=cb4a77a9-ee15-4ee5-b063-5c0b28a5d789
InstallationDate: Installed on 2015-03-24 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: Dell Inc. Vostro 3546
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic 
root=UUID=7d45912a-8768-4c39-8ec0-43eec97c733d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-48-generic N/A
 linux-backports-modules-3.13.0-48-generic  N/A
 linux-firmware 1.127.11
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 02R010
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnVostro3546:pvrNotSpecified:rvnDellInc.:rn02R010:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Vostro 3546
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


** Tags: 201404-14997 amd64 apport-bug certification-grey staging taipei-lab 
trusty

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

Title:
  Touchpad DLL0662:00 06CB:2985 detected as a SynPS/2 Synaptics
  TouchPad an, making 3 / 4-finger gesture does not work after upgrade
  on 14.04.1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201404-14997 Dell Vostro 3546

  The touchpad was detected as DLL0662:00 06CB:2985 on 14.04.1 stock image 
(3.13.0-32)
  And it works with three / four finger tapping gesture.

  But after upgraded to 3.13.0-48, it's detected as SynPS/2 Synaptics 
TouchPad, therefore it can't do three / four finger tapping.
  (bug 1384042)

  ubuntu@201404-14997:~$ xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=12   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]

  ProblemType: Bug
  

[Kernel-packages] [Bug 1435478] rainier (amd64) - tests ran: 274, failed: 3

2015-03-24 Thread Brad Figg
tests ran: 274, failed: 3;
  
http://kernel.ubuntu.com/testing/rainier__3.19.0-10.10__2015-03-24_21-32-00/results-index.html

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

Title:
  linux: 3.19.0-10.10 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow package-testing series:
  Won't Fix
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-release series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  This bug is for tracking the 3.19.0-10.10 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:Monday, 23. March 2015 18:13 UTC
  kernel-Package-testing-start:Tuesday, 24. March 2015 01:00 UTC
  kernel-Prepare-package-end:Tuesday, 24. March 2015 01:00 UTC
  kernel-Promote-to-release-end:Tuesday, 24. March 2015 20:00 UTC
  kernel-phase:Released
  kernel-phase-changed:Tuesday, 24. March 2015 21:01 UTC

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

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


[Kernel-packages] [Bug 1117325] Re: CVE-2013-0216

2015-03-24 Thread Mathew Hodson
** Changed in: linux (Ubuntu)
   Status: Fix Committed = Invalid

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

Title:
  CVE-2013-0216

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-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Invalid
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Invalid
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Oneiric:
  Fix Released
Status in linux-armadaxp source package in Oneiric:
  Invalid
Status in linux-ec2 source package in Oneiric:
  Invalid
Status in linux-fsl-imx51 source package in Oneiric:
  Invalid
Status in linux-lts-backport-maverick source package in Oneiric:
  Invalid
Status in linux-lts-backport-natty source package in Oneiric:
  Invalid
Status in linux-lts-backport-oneiric source package in Oneiric:
  Invalid
Status in linux-lts-quantal source package in Oneiric:
  Invalid
Status in linux-mvl-dove source package in Oneiric:
  Invalid
Status in linux-ti-omap4 source package in Oneiric:
  Fix Released
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-fsl-imx51 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Fix Released
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 Quantal:
  Fix Released
Status in linux-armadaxp source package in Quantal:
  Fix Released
Status in linux-ec2 source package in Quantal:
  Invalid
Status in linux-fsl-imx51 source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux-mvl-dove source package in Quantal:
  Invalid
Status in linux-ti-omap4 source package in Quantal:
  Fix Released
Status in linux source package in Raring:
  Won't Fix
Status in linux-armadaxp source package in Raring:
  Invalid
Status in linux-ec2 source package in Raring:
  Invalid
Status in linux-fsl-imx51 source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-quantal source package in Raring:
  Invalid
Status in linux-mvl-dove source package in Raring:
  Invalid
Status in linux-ti-omap4 source package in Raring:
  Fix Released
Status in linux source package in Hardy:
  Invalid
Status in linux-armadaxp source package in Hardy:
  Invalid
Status in linux-ec2 source package in Hardy:
  Invalid
Status in linux-fsl-imx51 source package in Hardy:
  Invalid
Status in linux-lts-backport-maverick source package in Hardy:
  Invalid
Status in linux-lts-backport-natty source package in Hardy:
  Invalid
Status in linux-lts-backport-oneiric source package in Hardy:
  Invalid
Status in linux-lts-quantal source package in Hardy:
  Invalid
Status in linux-mvl-dove source package in Hardy:
  Invalid
Status in linux-ti-omap4 source package in Hardy:
  Invalid

Bug description:
  The Xen netback functionality in the Linux kernel before 3.7.8 allows
  guest OS users to cause a denial of service (loop) by triggering ring
  pointer corruption.

  Break-Fix: - b9149729ebdcfce63f853aa54a404c6a8f6ebbf3
  Break-Fix: - 

  1   2   3   >