date:20150225

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


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

** Description changed:

  This bug is for tracking the version to be filled 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, 11. February 2015 01:02 UTC
  kernel-stable-master-bug:1419968
  kernel-stable-Certification-testing-end:Thursday, 12. February 2015 15:01 UTC
  kernel-stable-Prepare-package-end:Friday, 13. February 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 13. February 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 18. February 2015 23:41 UTC
  kernel-stable-Security-signoff-start:Thursday, 19. February 2015 01:01 UTC
  kernel-stable-Verification-testing-start:Thursday, 19. February 2015 01:01 UTC
  kernel-stable-Security-signoff-end:Thursday, 19. February 2015 23:00 UTC
  kernel-stable-Verification-testing-end:Tuesday, 24. February 2015 17:33 UTC
- kernel-stable-phase:CopyToUpdates
- kernel-stable-phase-changed:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Regression-testing-end:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Promote-to-updates-end:Wednesday, 25. February 2015 11:25 UTC
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Wednesday, 25. February 2015 13:00 UTC

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

Title:
  linux-ti-omap4: 3.2.0-1460.80 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow package-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released

Bug description:
  This bug is for tracking the version to be filled 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, 11. February 2015 01:02 UTC
  kernel-stable-master-bug:1419968
  kernel-stable-Certification-testing-end:Thursday, 12. February 2015 15:01 UTC
  kernel-stable-Prepare-package-end:Friday, 13. February 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 13. February 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 18. February 2015 23:41 UTC
  kernel-stable-Security-signoff-start:Thursday, 19. February 2015 01:01 UTC
  kernel-stable-Verification-testing-start:Thursday, 19. February 2015 01:01 UTC
  kernel-stable-Security-signoff-end:Thursday, 19. February 2015 23:00 UTC
  kernel-stable-Verification-testing-end:Tuesday, 24. February 2015 17:33 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Regression-testing-end:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Promote-to-updates-end:Wednesday, 25. February 2015 11:25 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Wednesday, 25. February 2015 13:00 UTC

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

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

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

This change was made by a bot.

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

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

Title:
  package linux-image-extra-3.16.0-31-generic 3.16.0-31.41 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I got an automatic pop-up that an error had occurred, which asked to
  be report the problem.  Apparently it was due to a failure in an
  automatic update to my system.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-extra-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shsentoff   2923 F pulseaudio
   /dev/snd/controlC0:  shsentoff   2923 F pulseaudio
  Date: Wed Feb 25 07:47:07 2015
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=6c868fdc-d446-41fd-a6e8-62beda07cbd4
  InstallationDate: Installed on 2014-12-20 (66 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 222
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-30-generic 
root=/dev/mapper/ubuntu--vg-root 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-15
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-3.16.0-31-generic 3.16.0-31.41 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/04/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 52KT43AUS
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr52KT43AUS:bd07/04/2008:svnLENOVO:pn222:pvrLENOVO:rvnLENOVO:rnLENOVO:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 222
  dmi.product.version: LENOVO 
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1410519] Re: [PowerVM] Kernel BUG @ kernel/irq_work.c:157! - 24x7 hw counters

2015-02-25 Thread bugproxy

** Tags removed: verification-done-utopic

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

Title:
  [PowerVM] Kernel BUG @ kernel/irq_work.c:157!  - 24x7 hw counters

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

Bug description:
  [Impact]
  Using perf with hv_24x7 events can cause a kernel BUG.

  [Fix]
  The following upstream commits:
   d658972
   48bee8a
   f34b6c7
   ec2aef5

  [Test Case]
  Steps to recreate the problem:

  1.  Install Ubuntu 15.04 as a PowerVM guest.
  2.  Install perf tool
  3.  Run following scripts to test 24/7 Power8 hardware counter event with 
perf. tool

  ===  Script 1
  #!/bin/bash

  count=0;

  offset=0x128
  PERF_ARGS=-r 10 -C 0
  while [ $count -lt 100 ]; do

  EVENT=hv_24x7/domain=0x2,offset=$offset,starting_index=10/

  perf stat $PERF_ARGS -x ' ' perf stat $PERF_ARGS -x ' ' -e
  $EVENT ls

  count=)
  done

   Script 2
  #!/bin/bash

  offset=0;

  PERF_ARGS=-r 10 -C 0
  while [ $offset -lt 8192 ]; do

  EVENT=hv_24x7/domain=0x2,offset=$offset,starting_index=10/

  perf stat $PERF_ARGS -x ' ' perf stat $PERF_ARGS -x ' ' -e
  $EVENT ls

  offset=)
  done

  After few iterations I hit the following BUG.

  tt2.sh  tt.sh
  tt2.sh  tt.sh
  tt2.sh  tt.sh
  275679187521558  hv_24x7/domain=0x2,offset=6848,starting_index=10/ 0.00%
  tt2.sh  tt.sh
  [ 4657.314709] softirq: huh, entered softirq 7 SCHED c010abc0 with 
preem
  pt_count 0100, exited with bfff?
  [ 4657.314727] kernel BUG at /build/buildd/linux-3.16.0/kernel/irq_work.c:157!
  [ 4657.314732] Oops: Exception in kernel mode, sig: 5 [#1]
  [ 4657.314740] Modules linked in: rtc_generic pseries_rng
  [ 4657.314749] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.16.0-25-generic 
#33-U
  [ 4657.314755] task: c1375e00 ti: c13d task.ti: 
c13d
  [ 4657.314759] NIP: c01e8ffc LR: c001fe70 CTR: 
c0002800ic)
  [ 4657.314770] MSR: 80029033 SF,EE,ME,IR,DR,RI,LE  CR: 28042024  
XER: 000a
  [ 4657.314782] CFAR: c001fe6c SOFTE: 0
  GPR04: 0010 009c c1424a98 0002
  GPR12: 80009033 ce9a 06a3fcd0 0060
  GPR16: 0020  c0e57c00 
  GPR20: c1595dca c1595478 0001 
  GPR28: c0e40380 c0e40300 c13d3590 c0e56f08
  [ 4657.314832] NIP [c01e8ffc] irq_work_run+0x1c/0x30
  [ 4657.314841] Call Trace:
  4000 (unreliable)
  [ 4657.314861] [c13d34f0] [c001ff90] timer_interrupt+0xa0/0xe0
  [ 4657.314871] [c13d3520] [c0002914] 
decrementer_common+0x114/0x180
  [ 4657.314884] --- Exception: 901 at arch_local_irq_restore+0x14/0x90
  [ 4657.314896] [c13d3810] [c012ed08] vprintk_emit+0x3b8/0x660 
(u
  [ 4657.314908] [c13d38e0] [c0a02650] printk+0x84/0x98
  [ 4657.314918] [c13d3910] [c00b51b4] __do_softirq+0x1e4/0x410
  [ 4657.314927] [c13d3a00] [c00b57b8] irq_exit+0xf8/0x1400
  [ 4657.314948] [c13d3a60] [c0002c14] 
doorbell_super_common+0x114/0x180
  [ 4657.314963] --- Exception: a01 at plpar_hcall_norets+0x8c/0xdc
  [ 4657.314963] LR = check_and_cede_processor+0x34/0x5020/0x50 (unreliable)
  [ 4657.314997] [c13d3df0] [c084077c] 
cpuidle_enter_state+0x6c/0x140c0
  [ 4657.315030] [c13d3f00] [c0d63ea8] start_kernel+0x500/0x51c
  [ 4657.315047] Instruction dump:
  [ 4657.315052] eba1ffe8 7c0803a6 ebc1fff0 ebe1fff8 4e800020 3c4c011f 3842c110 
78290464
  [ 4657.315068] 81290014 752a000f 7d380026 55291ffe 0b09 4bfffec8 
6000
  6000
  [ 4657.315090] ---[ end trace ee202cccd2211e5d ]---
  [ 4657.320224]
  [ 4657.362675] Unable to handle kernel paging request for data at address 
0xc000
  000b35515048
  [ 4657.362680] Faulting instruction address: 0xc006a37c
  [ 4657.362684] Oops: Kernel access of bad area, sig: 11 [#2]
  [ 4657.362686] SMP NR_CPUS=2048 NUMA pSeries
  [ 4657.362695] CPU: 12 PID: 7 Comm: rcu_sched Tainted: G  D   
3.16.0-25-
  [ 4657.362699] task: c000eb581540 ti: c000eb604000 task.ti: 
c000eb60
  [ 4657.362703] NIP: c006a37c LR: c00865a8 CTR: 
c006a340
  [ 4657.362706] REGS: c000eb607800 TRAP: 0300   Tainted: G  D
(3.16.0-25-generic)
  
  [ 4657.362718] CFAR: c00865a4 DAR: c00b35515048 DSISR: 4000 
SOFTE: 0
  GPR00: c00865a8 c000eb607a80 c13d50f0 013d30d0
  GPR08: 00cc c00b35515000 ce9a 
  GPR12: c006a340 ce9a6c00  0001
  GPR20:  c1389700

[Kernel-packages] [Bug 1400411] Re: Feature: cpuidle: Enable fastsleep and winkle in ubuntu 14.04.02 kernel

2015-02-25 Thread bugproxy

** Tags removed: verification-done-utopic

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

Title:
  Feature: cpuidle: Enable fastsleep and winkle in ubuntu 14.04.02
  kernel

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

Bug description:
  SRU Justification:

  [Impact]
  Users would like to be able to use fastsleep and winkle cpuidle states in the 
3.16 Ubuntu kernel when using powernv.

  [Fix]
  commits
  d6a4f70909d279004a2b3d539e240e07b1ecc1cb
  56548fc0e86cb9156af7a7e1f15ba78f251dafaf
  8117ac6a6c2fa0f847ff6a21a1f32c8d2c8501d0
  8eb8ac89a364305d05ad16be983b7890eb462cc3 *backported*
  7cba160ad789a3ad7e68b92bf20eaad6ed171f80 *backported*
  77b54e9f213f76a23736940cf94bcd765fc00f40
  upstream

  [Test Case]
  Testing fastsleep
  -
  With these patches cpuidle framework picks up fastsleep as one of the idle 
states. You can observe the cpus entering fastsleep by checking
  /sys/devices/system/cpu/cpuXX/cpuidle/state2/name. This should show FastSleep.
  Then while system is idle check 
/sys/devices/system/cpu/cpuXX/cpuidle/state2/time increment over time
  This shows the amount of time a particular cpu was in fastsleep.

  Testing Winkle
  --
  With these patches, offline cpus enter winkle. So test this by offlining and 
onlining cpus.
  ppc64_cpu --cores-on=1
  ppc64_cpu --cores-on=X where X is the total number of cores available in the 
machine.

  --

  This is a feature request to enable power management features
  fastsleep and winkle cpuidle states in ubuntu -14.04.02 kernel. The
  cpuidle state management patches have been posted to Linux Kernel
  Community.

  Mailing list:
  [PATCH 0/4] powernv: cpuidle: Redesign idle states management
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-November/122433.html

  Patchset:
  [1/4] powerpc: powernv: Switch off MMU before entering nap/sleep/rvwinkle mode
  https://patchwork.ozlabs.org/patch/406249/

  [2/4] powerpc/powernv: Enable Offline CPUs to enter deep idle states
  https://patchwork.ozlabs.org/patch/406250/

  [3/4] powernv: cpuidle: Redesign idle states management
  https://patchwork.ozlabs.org/patch/406256/

  [4/4] powernv: powerpc: Add winkle support for offline cpus
  https://patchwork.ozlabs.org/patch/406251/

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

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

[Kernel-packages] [Bug 1424261] Re: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card.

2015-02-25 Thread Jarl

First time I tried to use thsi SD card reader was about a year ago
(13.10) where I also had this problem (same hardware), and the situation
has not changed (i.e. all kernels through Ubuntu 14.04 and now 14.10.

The reason I have not repported this before is lack of time of root-
cause investigation. For quite some time I was mislead/confused by the
32GB limitation of the FAT file system and not-so-mature linux
implementation of the exFAT file system.

So this problem did not just start happening, it has never worked
correct for me.

 Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0].

Yes, I have try to use the v4.0-rc1 kernel downloaded from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/ with no
effect the behaviour is identical. Therefore I add the tag 'kernel-bug-
exists-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/1424261

Title:
  usb microSD card reader report incorrect size (32gb instead of 64GB)
  of microSD card.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using a 64GB microSDXC card in a usb sd card reader gives wrong SD
  card size (32GB). When putting the same microSDXC card in a a SD
  adapter it correctly gives 64GB size.

  Hardware:

  sdCard: SanDisk Extreme microSDXC UHS-I 
(http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB)
  USB card reader: Kingston FCR-MRG2 
(http://www.kingston.com/us/support/technical/products?model=fcr-mrg2)
  SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY)

  Here is the output from terminal:
  Accessing it through USB card reader:
  $ sudo fdisk -l /dev/sdb 

  Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x

  
  Accessing it through sd card adapter and the built-int sd card reader:
  $ sudo fdisk -l /dev/mmcblk0

  Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x


  
  My conclussion is that the driver for the usb card-reader.

  I will attach the output of lsusb -v -d 090c:6200

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarl   4339 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Feb 21 21:27:53 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2
  InstallationDate: Installed on 2013-11-27 (450 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP EliteBook 8730w
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=21aea9ee-02ab-46d0-8314-468f69a333c0 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-30-generic N/A
   linux-backports-modules-3.16.0-30-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2015-01-22 (30 days ago)
  dmi.bios.date: 12/03/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PAD Ver. F.13
  dmi.board.name: 30EC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.25
  dmi.chassis.asset.tag: CNU01143H6
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8730w
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1326885] Re: desktop start rotated

2015-02-25 Thread Daniel Holz

I wrote this guide because I had the same problem with my WeTab:

http://lackofalucidmind-en.blogspot.de/2014/06/wrong-screen-orientation-
at-greeter-and.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/1326885

Title:
  desktop start rotated

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after
  login the screen rotates to rightwards (no matter what direction the
  screen is actually at). I had to run this everytime:

  $ xrandr -o normal

  Note this is not gravity sensor at work. If gravity sensor is at work,
  and turned screen leftwards or rightwards, 'xrandr -o normal' will not
  have any effect.

  Expected behaviour: the desktop rotation should be decided by gravity sensor, 
or, without its input, defaults to normal. If it is intended that even without 
gravity sensor input the desktop should rotate anyway (because it consider 
itself running on a tablet) then it should do so since login screen, not to 
change orientation right after login.
  ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-28 (38 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.15.0-031500rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1425316] Re: ACPI battery code broken with kernel 3.19

2015-02-25 Thread Brian Murray

** Package changed: ubuntu = linux (Ubuntu)

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

Title:
  ACPI battery code broken with kernel 3.19

Status in linux package in Ubuntu:
  New

Bug description:
  In Ubuntu 14.04 (Kernel 3.13.*) acpi battery status info worked fine
  and presented info in

  /sys/class/power_supply/BAT0/

  I tested 15.04 (Kernel 3.19.*) and noticed that there isnt any BAT0 in the 
above said folder anymore. I did some reading at
  https://lkml.org/lkml/2014/12/28/94 and came to conlusion that I should do a

  sudo modprobe sbs_battery

  After that there is a 
  /sys/class/power_supply/BAT1

  which would be nice if only its information was updated at all. But all info 
read from 
  /sys/class/power_supply/BAT1/*
  will not change - it seems to get updated only once at boot time / first load 
of the module.

  
  uname -a:
  Linux notebook 3.19.0-031900-generic #201502091451 SMP Mon Feb 9 15:10:05 UTC 
2015 i686 i686 i686 GNU/Linux

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

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

[Kernel-packages] [Bug 1424261] Re: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card.

2015-02-25 Thread Jarl

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

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

Title:
  usb microSD card reader report incorrect size (32gb instead of 64GB)
  of microSD card.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using a 64GB microSDXC card in a usb sd card reader gives wrong SD
  card size (32GB). When putting the same microSDXC card in a a SD
  adapter it correctly gives 64GB size.

  Hardware:

  sdCard: SanDisk Extreme microSDXC UHS-I 
(http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB)
  USB card reader: Kingston FCR-MRG2 
(http://www.kingston.com/us/support/technical/products?model=fcr-mrg2)
  SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY)

  Here is the output from terminal:
  Accessing it through USB card reader:
  $ sudo fdisk -l /dev/sdb 

  Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x

  
  Accessing it through sd card adapter and the built-int sd card reader:
  $ sudo fdisk -l /dev/mmcblk0

  Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x


  
  My conclussion is that the driver for the usb card-reader.

  I will attach the output of lsusb -v -d 090c:6200

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarl   4339 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Feb 21 21:27:53 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2
  InstallationDate: Installed on 2013-11-27 (450 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP EliteBook 8730w
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=21aea9ee-02ab-46d0-8314-468f69a333c0 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-30-generic N/A
   linux-backports-modules-3.16.0-30-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2015-01-22 (30 days ago)
  dmi.bios.date: 12/03/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PAD Ver. F.13
  dmi.board.name: 30EC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.25
  dmi.chassis.asset.tag: CNU01143H6
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8730w
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1425576] [NEW] Occasional crash in APM xgene enet driver on kernels prior to v3.19

2015-02-25 Thread Craig Magina

Public bug reported:

This crash was submitted upstream and a fix was already present, but it
didn't land until the 3.19 kernel. This bug is to track getting that fix
into trusty and utopic.

Unable to handle kernel NULL pointer dereference at virtual address 00c0
pgd = ffc3e639a000
[00c0] *pgd=0043e629d003, *pud=0043e629d003, *pmd=
Internal error: Oops: 9606 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 6643 Comm: qemu-system-aar Not tainted 3.19.0-rc7+ #254
Hardware name: APM X-Gene Mustang board (DT)
task: ffc3ee3aee00 ti: ffc3c044c000 task.ti: ffc3c044c000
PC is at xgene_enet_process_ring+0x94/0x328
LR is at xgene_enet_process_ring+0x78/0x328
pc : [ffc0003f9058] lr : [ffc0003f903c] pstate: 8145
sp : ffc3c044fa00
x29: ffc3c044fa00 x28: ffc0fe8aa218
x27:  x26: 
x25: ffc3ee2b7000 x24: 0040
x23: ffc0fe8aa418 x22: 01ff
x21: 0001 x20: ffc0ff058380
x19: 001c x18: 007f82d1c1f0
x17: 007f84afbc90 x16: ffc0001a6a8c
x15: 007f84b805a0 x14: 
x13: d0d03820 x12: 
x11: 0024 x10: d0d30a20
x9 : ffc00031da28 x8 : ffbdc000
x7 : ffc3cae0285e x6 : 0040fec0
x5 : 0c08100801400148 x4 : 0040ff00
x3 : 000200d1 x2 : 0066
x1 : 0043cae0285e x0 : ffc3ee2bb818

Process qemu-system-aar (pid: 6643, stack limit = 0xffc3c044c058)
Stack: (0xffc3c044fa00 to 0xffc3c045)
fa00: c044fa70 ffc3 003f93d0 ffc0 fe8aa290 ffc0  
fa20: 0040  0078e000 ffc0 0016cac3 0001 c044fb20 ffc3
fa40: ff7d4000 0003 007825c0 ffc0 012c  fff565c0 ffc3
fa60: ffc0  ee2b7000 ffc3 c044faa0 ffc3 004a5cec ffc0
fa80: fe8aa290 ffc0   0040  84b805a0 007f
faa0: c044fb40 ffc3 000b5da0 ffc0 c044c000 ffc3 0078e000 ffc0
fac0: 0077faa0 ffc0 c044fb40 ffc3 0018  0101 
fae0: 0003  0078e0c0 ffc0 0078e0d8 ffc0  
fb00: 0008  006fbd90 ffc0 006fb9f0 ffc0 007e3d74 ffc0
fb20: c044fb20 ffc3 c044fb20 ffc3 c044fb30 ffc3 c044fb30 ffc3
fb40: c044fbc0 ffc3 000b6134 ffc0 0078 ffc0  
fb60:   2010 ff80 6145   
fb80: 011a  001d  0079e000 ffc0 c044c000 ffc3
fba0: 000a  0016cac2 0001 00570c08 ffc0 084040c0 000a
fbc0: c044fbe0 ffc3 000ecb2c ffc0 0078 ffc0 000ecafc ffc0
fbe0: c044fc20 ffc3 00082420 ffc0 00797000 ffc0 c044fc50 ffc3
fc00: 200c ff80 000fc014 ffc0 ee01 ffc3 000a253c 005c
fc20: c044fd70 ffc3 00085da8 ffc0   fd024c90 ffc0
fc40: c044fd70 ffc3 000d0938 ffc0 fd024c98 ffc0 ee3aee00 ffc3
fc60:     ae80   
fc80:   c7e8ed00 5df42439 001d  0092 
fca0:   001b    0092 
fcc0:   84b805a0 007f 001a6a8c ffc0 84afbc90 007f
fce0: 82d1c1f0 007f   fd024c90 ffc0  
fd00: feabe300 ffc0 ae80    011a 
fd20: 001d  0079e000 ffc0 c044c000 ffc3 c044fd70 ffc3
fd40: 0009c1d0 ffc0 c044fd70 ffc3 000d0938 ffc0 6145 
fd60: c044fd70 ffc3 0009c1a4 ffc0 c044fda0 ffc3 0009c2e0 ffc0
fd80: feabe300 ffc0 fd024c90 ffc0 0079e000 ffc0 c044c000 
fda0: c044fe10 ffc3 001a6824 ffc0 feabe300 ffc0  
fdc0: edc06f70 ffc3 000b  ae80  0015 
fde0: 011a  0040 ae80 c044fe20 ffc3 0019772c ffc0
fe00: edb3 ffc3 0001  c044fe90 ffc3 001a6b10 ffc0
fe20:   feabe301 ffc0 feabe300 ffc0  
fe40: c044fe70 ffc3 001b0a2c ffc0   ed3ea300 ffc3
fe60: c044fe80 000b feabe300 ffc0 c044fe80 ffc3 001b0a80 ffc0
fe80: c044fe90 ffc3 001a6acc ffc0 82d1c600 007f 00086430 ffc0
fea0:   15b1cea0    84afbc9c 007f
fec0: 6000  0015  000b  ae80 
fee0:   ff80  82d1c700 007f 0001 
ff00:   c7e8ed00 5df42439 001d  0092 
ff20:   001b    0092 
ff40:   84b805a0 007f 008bc3d0  84afbc90 007f
ff60: 82d1c1f0 007f 0092  15b1cea0

[Kernel-packages] [Bug 1304537] Re: USB Keyboard MM2 IBM - no input after Installation

2015-02-25 Thread Steffen Kupfer

I can confirm the same behavior with a LS21, kernel 3.16.0-31-generic
and the management modele with part number 39Y9659.

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

Title:
  USB Keyboard MM2 IBM - no input after Installation

Status in The Linux Kernel:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  After the installation is no interaction with the Keyboard of the IBM 
Bladecenter with Management Module MM2 possible.
  The Installation-Method is with no problem possible and all keyboard inputs 
are OK. With the old version 12.04 the keyboard inputs are also good.

  But after installation it isn't possible to do keyboard inputs. The
  inputs over the IPMI softkey works also not.

  After switching to another server on the IPMI tool and then switching
  back the server the first inputs are accepted, but after input an
  ENTER all other inputs are ignored - IPMI softkey too.

  ProblemType: Bug
  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 x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  8 18:20 seq
   crw-rw 1 root audio 116, 33 Apr  8 18:20 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Apr  8 18:22:42 2014
  HibernationDevice: RESUME=UUID=a323327a-a13f-4149-a6e3-6d8e85a88841
  InstallationDate: Installed on 2014-04-08 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Beta amd64 
(20140326)
  Lsusb:
   Bus 001 Device 003: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 
USB-2.0 TetraHub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 04b3:4002 IBM Corp. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: IBM BladeCenter LS22 -[790162G]-
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic 
root=UUID=87173c3f-0c0d-4147-b281-51a3bbeffb8c ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-23-generic N/A
   linux-backports-modules-3.13.0-23-generic  N/A
   linux-firmware 1.127
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2011
  dmi.bios.vendor: IBM
  dmi.bios.version: -[L8E164AUS-1.07]-
  dmi.board.name: Server Blade
  dmi.board.vendor: IBM
  dmi.chassis.type: 17
  dmi.chassis.vendor: IBM
  dmi.modalias: 
dmi:bvnIBM:bvr-[L8E164AUS-1.07]-:bd05/25/2011:svnIBM:pnBladeCenterLS22-[790162G]-:pvr:rvnIBM:rnServerBlade:rvr:cvnIBM:ct17:cvr:
  dmi.product.name: BladeCenter LS22 -[790162G]-
  dmi.sys.vendor: IBM

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

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

[Kernel-packages] [Bug 1425316] [NEW] ACPI battery code broken with kernel 3.19

You have been subscribed to a public bug:

In Ubuntu 14.04 (Kernel 3.13.*) acpi battery status info worked fine and
presented info in

/sys/class/power_supply/BAT0/

I tested 15.04 (Kernel 3.19.*) and noticed that there isnt any BAT0 in the 
above said folder anymore. I did some reading at
https://lkml.org/lkml/2014/12/28/94 and came to conlusion that I should do a

sudo modprobe sbs_battery

After that there is a 
/sys/class/power_supply/BAT1

which would be nice if only its information was updated at all. But all info 
read from 
/sys/class/power_supply/BAT1/*
will not change - it seems to get updated only once at boot time / first load 
of the module.


uname -a:
Linux notebook 3.19.0-031900-generic #201502091451 SMP Mon Feb 9 15:10:05 UTC 
2015 i686 i686 i686 GNU/Linux

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


** Tags: acpi bot-comment sbs vivid
-- 
ACPI battery code broken with kernel 3.19
https://bugs.launchpad.net/bugs/1425316
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1425576] Re: Occasional crash in APM xgene enet driver on kernels prior to v3.19

2015-02-25 Thread Craig Magina

Here is a direct link to the upstream submission of the crash:

http://www.spinics.net/lists/arm-kernel/msg399023.html

The upstream commit that fixes it is:

commit ecf6ba83d76e0c78e89401750dc527008e14faa2
Author: Iyappan Subramanian isubramanian@xxx
Date:   Thu Jan 29 14:38:23 2015 -0800
drivers: net: xgene: fix: Out of order descriptor bytes read

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

Title:
  Occasional crash in APM xgene enet driver on kernels prior to v3.19

Status in linux package in Ubuntu:
  New

Bug description:
  This crash was submitted upstream and a fix was already present, but
  it didn't land until the 3.19 kernel. This bug is to track getting
  that fix into trusty and utopic.

  Unable to handle kernel NULL pointer dereference at virtual address 00c0
  pgd = ffc3e639a000
  [00c0] *pgd=0043e629d003, *pud=0043e629d003, *pmd=
  Internal error: Oops: 9606 [#1] PREEMPT SMP
  Modules linked in:
  CPU: 0 PID: 6643 Comm: qemu-system-aar Not tainted 3.19.0-rc7+ #254
  Hardware name: APM X-Gene Mustang board (DT)
  task: ffc3ee3aee00 ti: ffc3c044c000 task.ti: ffc3c044c000
  PC is at xgene_enet_process_ring+0x94/0x328
  LR is at xgene_enet_process_ring+0x78/0x328
  pc : [ffc0003f9058] lr : [ffc0003f903c] pstate: 8145
  sp : ffc3c044fa00
  x29: ffc3c044fa00 x28: ffc0fe8aa218
  x27:  x26: 
  x25: ffc3ee2b7000 x24: 0040
  x23: ffc0fe8aa418 x22: 01ff
  x21: 0001 x20: ffc0ff058380
  x19: 001c x18: 007f82d1c1f0
  x17: 007f84afbc90 x16: ffc0001a6a8c
  x15: 007f84b805a0 x14: 
  x13: d0d03820 x12: 
  x11: 0024 x10: d0d30a20
  x9 : ffc00031da28 x8 : ffbdc000
  x7 : ffc3cae0285e x6 : 0040fec0
  x5 : 0c08100801400148 x4 : 0040ff00
  x3 : 000200d1 x2 : 0066
  x1 : 0043cae0285e x0 : ffc3ee2bb818

  Process qemu-system-aar (pid: 6643, stack limit = 0xffc3c044c058)
  Stack: (0xffc3c044fa00 to 0xffc3c045)
  fa00: c044fa70 ffc3 003f93d0 ffc0 fe8aa290 ffc0  
  fa20: 0040  0078e000 ffc0 0016cac3 0001 c044fb20 ffc3
  fa40: ff7d4000 0003 007825c0 ffc0 012c  fff565c0 ffc3
  fa60: ffc0  ee2b7000 ffc3 c044faa0 ffc3 004a5cec ffc0
  fa80: fe8aa290 ffc0   0040  84b805a0 007f
  faa0: c044fb40 ffc3 000b5da0 ffc0 c044c000 ffc3 0078e000 ffc0
  fac0: 0077faa0 ffc0 c044fb40 ffc3 0018  0101 
  fae0: 0003  0078e0c0 ffc0 0078e0d8 ffc0  
  fb00: 0008  006fbd90 ffc0 006fb9f0 ffc0 007e3d74 ffc0
  fb20: c044fb20 ffc3 c044fb20 ffc3 c044fb30 ffc3 c044fb30 ffc3
  fb40: c044fbc0 ffc3 000b6134 ffc0 0078 ffc0  
  fb60:   2010 ff80 6145   
  fb80: 011a  001d  0079e000 ffc0 c044c000 ffc3
  fba0: 000a  0016cac2 0001 00570c08 ffc0 084040c0 000a
  fbc0: c044fbe0 ffc3 000ecb2c ffc0 0078 ffc0 000ecafc ffc0
  fbe0: c044fc20 ffc3 00082420 ffc0 00797000 ffc0 c044fc50 ffc3
  fc00: 200c ff80 000fc014 ffc0 ee01 ffc3 000a253c 005c
  fc20: c044fd70 ffc3 00085da8 ffc0   fd024c90 ffc0
  fc40: c044fd70 ffc3 000d0938 ffc0 fd024c98 ffc0 ee3aee00 ffc3
  fc60:     ae80   
  fc80:   c7e8ed00 5df42439 001d  0092 
  fca0:   001b    0092 
  fcc0:   84b805a0 007f 001a6a8c ffc0 84afbc90 007f
  fce0: 82d1c1f0 007f   fd024c90 ffc0  
  fd00: feabe300 ffc0 ae80    011a 
  fd20: 001d  0079e000 ffc0 c044c000 ffc3 c044fd70 ffc3
  fd40: 0009c1d0 ffc0 c044fd70 ffc3 000d0938 ffc0 6145 
  fd60: c044fd70 ffc3 0009c1a4 ffc0 c044fda0 ffc3 0009c2e0 ffc0
  fd80: feabe300 ffc0 fd024c90 ffc0 0079e000 ffc0 c044c000 
  fda0: c044fe10 ffc3 001a6824 ffc0 feabe300 ffc0  
  fdc0: edc06f70 ffc3 000b  ae80  0015 
  fde0: 011a  0040 ae80 c044fe20 ffc3 0019772c ffc0
  fe00: edb3 ffc3 0001  c044fe90 ffc3 001a6b10 ffc0
  fe20:   feabe301 ffc0 feabe300 ffc0

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

2015-02-25 Thread bugproxy

--- Comment From cha...@us.ibm.com 2015-02-25 16:20 EDT---
*** Bug 122062 has been marked as a duplicate of this bug. ***

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

Title:
  ISST-LTE: Ubuntu 15.04 lpar crashes at iommu_free_table after adapter
  DLPAR operation

Status in linux package in Ubuntu:
  New

Bug description:
  Description:
  

  I have installed all packages required for DLPAR in Ubuntu 15.04. When
  i am trying to do network adapter DLPAR operation, lpar crashes.

  root@highlp1:/etc/network# [  454.482742] kernel BUG at 
/build/buildd/linux-3.18.0/arch/powerpc/kernel/iommu.c:732!
  cpu 0xa: Vector: 700 (Program Check) at [c0016e67f850]
  pc: c0040484: iommu_free_table+0x64/0x140
  lr: c004047c: iommu_free_table+0x5c/0x140
  sp: c0016e67fad0
 msr: 80029033
current = 0xc0016b4277e0
paca= 0xc7b35a00   softe: 0irq_happened: 0x01
  pid   = 3288, comm = drmgr
  kernel BUG at /build/buildd/linux-3.18.0/arch/powerpc/kernel/iommu.c:732!
  enter ? for help
  [c0016e67fb40] c0083428 iommu_reconfig_notifier+0x88/0x160
  [c0016e67fb70] c00dab38 notifier_call_chain+0x98/0x100
  [c0016e67fbc0] c00db244 __blocking_notifier_call_chain+0x74/0xe0
  [c0016e67fc10] c0877290 of_reconfig_notify+0x40/0xa0
  [c0016e67fc40] c0877cdc of_detach_node+0x8c/0xb0
  [c0016e67fc70] c00809b8 ofdt_write+0x1f8/0x7b0
  [c0016e67fd40] c03459f0 proc_reg_write+0xb0/0x110
  [c0016e67fd90] c02b950c vfs_write+0xdc/0x260
  [c0016e67fde0] c02ba0ac SyS_write+0x6c/0x110
  [c0016e67fe30] c000927c syscall_exit+0x0/0x7c
  --- Exception: c01 (System Call) at 101ba638
  SP (3fffdba63300) is in userspace
  a:mon
  a:mon
  a:mon
  a:mon t
  [c0016e67fb40] c0083428 iommu_reconfig_notifier+0x88/0x160
  [c0016e67fb70] c00dab38 notifier_call_chain+0x98/0x100
  [c0016e67fbc0] c00db244 __blocking_notifier_call_chain+0x74/0xe0
  [c0016e67fc10] c0877290 of_reconfig_notify+0x40/0xa0
  [c0016e67fc40] c0877cdc of_detach_node+0x8c/0xb0
  [c0016e67fc70] c00809b8 ofdt_write+0x1f8/0x7b0
  [c0016e67fd40] c03459f0 proc_reg_write+0xb0/0x110
  [c0016e67fd90] c02b950c vfs_write+0xdc/0x260
  [c0016e67fde0] c02ba0ac SyS_write+0x6c/0x110
  [c0016e67fe30] c000927c syscall_exit+0x0/0x7c
  --- Exception: c01 (System Call) at 101ba638
  SP (3fffdba63300) is in userspace

  a:mon e
  cpu 0xa: Vector: 700 (Program Check) at [c0016e67f850]
  pc: c0040484: iommu_free_table+0x64/0x140
  lr: c004047c: iommu_free_table+0x5c/0x140
  sp: c0016e67fad0
 msr: 80029033
current = 0xc0016b4277e0
paca= 0xc7b35a00   softe: 0irq_happened: 0x01
  pid   = 3288, comm = drmgr
  kernel BUG at /build/buildd/linux-3.18.0/arch/powerpc/kernel/iommu.c:732!

  
  Original patch posted 
https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-February/125068.html

  Updated patch posted as: https://lists.ozlabs.org/pipermail/linuxppc-
  dev/2015-February/125133.html

  Will update again once merged into mpe's tree.

  -Nish

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

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

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

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

apport-collect 1425576

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

Title:
  Occasional crash in APM xgene enet driver on kernels prior to v3.19

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This crash was submitted upstream and a fix was already present, but
  it didn't land until the 3.19 kernel. This bug is to track getting
  that fix into trusty and utopic.

  Unable to handle kernel NULL pointer dereference at virtual address 00c0
  pgd = ffc3e639a000
  [00c0] *pgd=0043e629d003, *pud=0043e629d003, *pmd=
  Internal error: Oops: 9606 [#1] PREEMPT SMP
  Modules linked in:
  CPU: 0 PID: 6643 Comm: qemu-system-aar Not tainted 3.19.0-rc7+ #254
  Hardware name: APM X-Gene Mustang board (DT)
  task: ffc3ee3aee00 ti: ffc3c044c000 task.ti: ffc3c044c000
  PC is at xgene_enet_process_ring+0x94/0x328
  LR is at xgene_enet_process_ring+0x78/0x328
  pc : [ffc0003f9058] lr : [ffc0003f903c] pstate: 8145
  sp : ffc3c044fa00
  x29: ffc3c044fa00 x28: ffc0fe8aa218
  x27:  x26: 
  x25: ffc3ee2b7000 x24: 0040
  x23: ffc0fe8aa418 x22: 01ff
  x21: 0001 x20: ffc0ff058380
  x19: 001c x18: 007f82d1c1f0
  x17: 007f84afbc90 x16: ffc0001a6a8c
  x15: 007f84b805a0 x14: 
  x13: d0d03820 x12: 
  x11: 0024 x10: d0d30a20
  x9 : ffc00031da28 x8 : ffbdc000
  x7 : ffc3cae0285e x6 : 0040fec0
  x5 : 0c08100801400148 x4 : 0040ff00
  x3 : 000200d1 x2 : 0066
  x1 : 0043cae0285e x0 : ffc3ee2bb818

  Process qemu-system-aar (pid: 6643, stack limit = 0xffc3c044c058)
  Stack: (0xffc3c044fa00 to 0xffc3c045)
  fa00: c044fa70 ffc3 003f93d0 ffc0 fe8aa290 ffc0  
  fa20: 0040  0078e000 ffc0 0016cac3 0001 c044fb20 ffc3
  fa40: ff7d4000 0003 007825c0 ffc0 012c  fff565c0 ffc3
  fa60: ffc0  ee2b7000 ffc3 c044faa0 ffc3 004a5cec ffc0
  fa80: fe8aa290 ffc0   0040  84b805a0 007f
  faa0: c044fb40 ffc3 000b5da0 ffc0 c044c000 ffc3 0078e000 ffc0
  fac0: 0077faa0 ffc0 c044fb40 ffc3 0018  0101 
  fae0: 0003  0078e0c0 ffc0 0078e0d8 ffc0  
  fb00: 0008  006fbd90 ffc0 006fb9f0 ffc0 007e3d74 ffc0
  fb20: c044fb20 ffc3 c044fb20 ffc3 c044fb30 ffc3 c044fb30 ffc3
  fb40: c044fbc0 ffc3 000b6134 ffc0 0078 ffc0  
  fb60:   2010 ff80 6145   
  fb80: 011a  001d  0079e000 ffc0 c044c000 ffc3
  fba0: 000a  0016cac2 0001 00570c08 ffc0 084040c0 000a
  fbc0: c044fbe0 ffc3 000ecb2c ffc0 0078 ffc0 000ecafc ffc0
  fbe0: c044fc20 ffc3 00082420 ffc0 00797000 ffc0 c044fc50 ffc3
  fc00: 200c ff80 000fc014 ffc0 ee01 ffc3 000a253c 005c
  fc20: c044fd70 ffc3 00085da8 ffc0   fd024c90 ffc0
  fc40: c044fd70 ffc3 000d0938 ffc0 fd024c98 ffc0 ee3aee00 ffc3
  fc60:     ae80   
  fc80:   c7e8ed00 5df42439 001d  0092 
  fca0:   001b    0092 
  fcc0:   84b805a0 007f 001a6a8c ffc0 84afbc90 007f
  fce0: 82d1c1f0 007f   fd024c90 ffc0  
  fd00: feabe300 ffc0 ae80    011a 
  fd20: 001d  0079e000 ffc0 c044c000 ffc3 c044fd70 ffc3
  fd40: 0009c1d0 ffc0 c044fd70 ffc3 000d0938 ffc0 6145 
  fd60: c044fd70 ffc3 0009c1a4 ffc0 c044fda0 ffc3 0009c2e0 ffc0
  fd80: feabe300 ffc0 fd024c90 ffc0 0079e000 ffc0 c044c000 
  fda0: c044fe10 ffc3 001a6824 ffc0 feabe300 ffc0  
  fdc0: edc06f70 ffc3 000b  ae80  0015 
  fde0: 011a  0040 ae80 c044fe20 ffc3 0019772c

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

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

apport-collect 1425316

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

Title:
  ACPI battery code broken with kernel 3.19

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 14.04 (Kernel 3.13.*) acpi battery status info worked fine
  and presented info in

  /sys/class/power_supply/BAT0/

  I tested 15.04 (Kernel 3.19.*) and noticed that there isnt any BAT0 in the 
above said folder anymore. I did some reading at
  https://lkml.org/lkml/2014/12/28/94 and came to conlusion that I should do a

  sudo modprobe sbs_battery

  After that there is a 
  /sys/class/power_supply/BAT1

  which would be nice if only its information was updated at all. But all info 
read from 
  /sys/class/power_supply/BAT1/*
  will not change - it seems to get updated only once at boot time / first load 
of the module.

  
  uname -a:
  Linux notebook 3.19.0-031900-generic #201502091451 SMP Mon Feb 9 15:10:05 UTC 
2015 i686 i686 i686 GNU/Linux

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

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

[Kernel-packages] [Bug 1425531] Re: package linux-image-extra-3.16.0-31-generic 3.16.0-31.41 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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

Title:
  package linux-image-extra-3.16.0-31-generic 3.16.0-31.41 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I got an automatic pop-up that an error had occurred, which asked to
  be report the problem.  Apparently it was due to a failure in an
  automatic update to my system.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-extra-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shsentoff   2923 F pulseaudio
   /dev/snd/controlC0:  shsentoff   2923 F pulseaudio
  Date: Wed Feb 25 07:47:07 2015
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=6c868fdc-d446-41fd-a6e8-62beda07cbd4
  InstallationDate: Installed on 2014-12-20 (66 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 222
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-30-generic 
root=/dev/mapper/ubuntu--vg-root 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-15
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-3.16.0-31-generic 3.16.0-31.41 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/04/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 52KT43AUS
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr52KT43AUS:bd07/04/2008:svnLENOVO:pn222:pvrLENOVO:rvnLENOVO:rnLENOVO:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 222
  dmi.product.version: LENOVO 
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1425453] Re: [Dell Inc. Latitude E6430] suspend/resume failure [non-free: nvidia]

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

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

Title:
  [Dell Inc. Latitude E6430] suspend/resume failure [non-free: nvidia]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error on resume from suspend

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-13-generic 3.18.0-13.14
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  NonfreeKernelModules: nvidia
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ed 3237 F pulseaudio
   /dev/snd/seq:timidity   1518 F timidity
  Date: Wed Feb 25 09:34:47 2015
  DuplicateSignature: suspend/resume:Dell Inc. Latitude E6430:A09
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=6051f154-4db2-4c44-ae10-778e5044d865
  InstallationDate: Installed on 2014-04-17 (313 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Dell Inc. Latitude E6430
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic 
root=UUID=145f3f5e-fb0b-49a8-9f7d-b930a2396d8a ro quiet splash
  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.18.0-13-generic N/A
   linux-backports-modules-3.18.0-13-generic  N/A
   linux-firmware 1.141
  SourcePackage: linux
  Title: [Dell Inc. Latitude E6430] suspend/resume failure [non-free: nvidia]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1412042] Re: [Toshiba Satellite P855-S5102] Fan too loud while CPU idle

2015-02-25 Thread jtd

Forget to mark confirmed when I responded to recent questions.

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

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

Title:
  [Toshiba Satellite P855-S5102] Fan too loud while CPU idle

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Windows 8.1, fan is NOT loud. On Ubuntu 14.04x64, fan is always too
  loud (30 minutes after boot and after). BIOS is already updated.
  Update: If battery power only, fan possibly quiet for more time.

  I was hoping it was my LCD cooling_device4, but that has current
  cooling state 100 even when fan is quiet.

  $ lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)

  $ sudo pwmconfig
  # pwmconfig revision 6166 (2013-05-01)
  /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed

  $ sudo fwts -r stdout fan
  PASSED: Test 1, Fan cooling_device0 of type Processor has max cooling state 3 
and current cooling state 0.
  PASSED: Test 1, Fan cooling_device1 of type Processor has max cooling state 3 
and current cooling state 0.
  PASSED: Test 1, Fan cooling_device2 of type Processor has max cooling state 3 
and current cooling state 0.
  PASSED: Test 1, Fan cooling_device3 of type Processor has max cooling state 3 
and current cooling state 0.
  PASSED: Test 1, Fan cooling_device4 of type LCD has max cooling state 100 and 
current cooling state 100.
  FAILED [MEDIUM] NoFanCurState: Test 1, Fan present but has no cur_state 
present.

  Loading CPUs for 20 seconds to try and get fan speeds to change.
  Fan cooling_device0 current state did not change from value 0 while CPUs were 
busy.
  Fan cooling_device1 current state did not change from value 0 while CPUs were 
busy.
  Fan cooling_device2 current state did not change from value 0 while CPUs were 
busy.
  Fan cooling_device3 current state did not change from value 0 while CPUs were 
busy.

  ProblemType: Bug
  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 x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jtd2207 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jan 17 14:31:46 2015
  HibernationDevice: RESUME=UUID=f155dbb3-50ae-4b36-bf29-dcd5021a5bd8
  InstallationDate: Installed on 2015-01-02 (14 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA Satellite P855
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-44-generic 
root=/dev/mapper/ubuntu-root ro quiet splash acpi_osi=Linux intel_pstate=enable 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-44-generic N/A
   linux-backports-modules-3.13.0-44-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/28/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 6.80
  dmi.board.asset.tag: *
  dmi.board.name: QFKAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: *
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr6.80:bd04/28/2014:svnTOSHIBA:pnSatelliteP855:pvrPSPKEU-062002:rvnTOSHIBA:rnQFKAA:rvr1.00:cvnTOSHIBA:ct10:cvr*:
  dmi.product.name: Satellite P855
  dmi.product.version: PSPKEU-062002
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1416601] Re: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343)

2015-02-25 Thread Mario Limonciello

It's been merged upstream.  Canonical, can you pull this in for vivid?

https://github.com/torvalds/linux/commit/6d00f37e49d95e640a3937a4a1ae07dbe92a10cb

** Tags added: kernel-fixed-upstream

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

Title:
  touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04
  on 2015 XPS 13 (9343)

Status in Dell Sputnik:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Invalid
Status in xserver-xorg-input-synaptics package in Fedora:
  Unknown

Bug description:
  Tap-to-click does not work unless I tap several times really fast
  (which is really hard to do), which also causes the cursor to move.
  This is a poor user experience.

  Relatedly, sometimes when using two-finger scrolling, the touchpad
  will get stuck such that I can let go and the cursor won't move. I can
  continue using two fingers to try scrolling, which works, but I can't
  get the cursor to move. If I tap the cursor several times really fast,
  I can eventually get the cursor unstuck so it moves again. I suspect
  that this is related to the tap-to-click issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-12-generic 3.18.0-12.13
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  3714 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jan 30 20:12:17 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (89 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-12-generic N/A
   linux-backports-modules-3.18.0-12-generic  N/A
   linux-firmware 1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (23 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1416601/+subscriptions

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

[Kernel-packages] [Bug 1425298] Re: usb in docking station thinkpad fails resume

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

Title:
  usb in docking station thinkpad fails resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  USB in docking station fails to work after resume from suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-extra-3.16.0-30-generic 3.16.0-30.40
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mastier4275 F pulseaudio
   /dev/snd/controlC0:  mastier4275 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb 24 22:51:57 2015
  HibernationDevice: RESUME=UUID=f6738183-910b-49b9-b769-898c55ff5967
  InstallationDate: Installed on 2012-10-25 (852 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MachineType: LENOVO 34352NG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-30-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-30-generic N/A
   linux-backports-modules-3.16.0-30-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET98WW (2.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34352NG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET98WW(2.58):bd03/12/2014:svnLENOVO:pn34352NG:pvrThinkPadX230Tablet:rvnLENOVO:rn34352NG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 34352NG
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 950129] Re: sudo halt won't cause halt

2015-02-25 Thread Rarylson Freitas

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

** This bug is no longer a duplicate of bug 880240
   system doesn't turn off if sudo halt is given
** This bug has been marked a duplicate of bug 991997
   Wrong comment in /etc/default/halt: Default behavior of halt changed to 
halt only instead of powering off

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

Title:
  sudo halt won't cause halt

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When typing sudo halt into a terminal, ubuntu shuts down completely, but 
won't turn off my hp compaq 6730s laptop. The hard disk makes a clicking sound 
(that means it's turned off), but power remains on, displaying a frozen ubuntu 
logo.
  I upgraded from 11.10 via update-manager.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 1.94.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sandro 1947 F pulseaudio
   /dev/snd/controlC1:  sandro 1947 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x9890 irq 49'
 Mixer name : 'Analog Devices AD1984A'
 Components : 'HDA:11d4194a,103c3614,00100400 
HDA:11c11040,103c1378,00100200'
 Controls  : 18
 Simple ctrls  : 11
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x807'/'USB Device 0x46d:0x807 at usb-:00:1d.7-1.3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0807'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 6144
 Mono: Capture 4608 [75%] [24.00dB] [on]
  CurrentDmesg:
   [   39.464297] CIFS VFS: cifs_mount failed w/return code = -113
   [   42.496065] wlan0: no IPv6 routers present
   [   45.464194] CIFS VFS: Error connecting to socket. Aborting operation
   [   45.464293] CIFS VFS: cifs_mount failed w/return code = -113
   [   54.987968] process `skype' is using obsolete setsockopt SO_BSDCOMPAT
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=d85b1d28-2ef4-4bd2-b2c2-88a768c1e4fb
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MachineType: Hewlett-Packard HP Compaq 6730s
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic 
root=UUID=e8d2876f-7ef9-4b1a-bc38-9e48f1db155a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-18-generic N/A
   linux-backports-modules-3.2.0-18-generic  N/A
   linux-firmware1.71
  Tags:  precise
  Uname: Linux 3.2.0-18-generic i686
  UpgradeStatus: Upgraded to precise on 2012-03-03 (6 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 12/06/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZU Ver. F.13
  dmi.board.name: 30E8
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 94.1D
  dmi.chassis.asset.tag: CNU91138XV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZUVer.F.13:bd12/06/2010:svnHewlett-Packard:pnHPCompaq6730s:pvrF.13:rvnHewlett-Packard:rn30E8:rvrKBCVersion94.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6730s
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1425445] Re: Regression: 3.16.0-31-generic breaks touchpad on Dell XPS13 (2015)

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

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

Title:
  Regression: 3.16.0-31-generic breaks touchpad on Dell XPS13 (2015)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today’s kernel update breaks the touchpad on the 2015 Dell XPS13. On
  3.16.0-30-generic the touchpad worked fine.

  Symptoms are that the touchpad stops responding at random times.

  A possible cause is this patch:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d1c7e29e8d276c669e8790bb8be9f505ddc4

  See also those two bug reports for a more detailed discussion of the I2C 
issues caused by the above patch and the XPS13:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416601
  https://bugzilla.redhat.com/show_bug.cgi?id=1188439

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jan2547 F pulseaudio
   /dev/snd/controlC1:  jan2547 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Feb 25 10:19:01 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-30 (25 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=e4431ecc-e85e-4e35-92af-58f455c46c2b ro kvm-intel.nested=1 
acpi_osi=!Windows 2013 psmouse.resetafter=0 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1386490] Re: HP ProLiant m400 nic doesn't work after trusty

2015-02-25 Thread Raghuram Kota

** No longer affects: santacruz

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

Title:
  HP ProLiant m400 nic doesn't work after trusty

Status in The Linux Kernel:
  New
Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Utopic:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in debian-installer source package in Vivid:
  Confirmed
Status in linux source package in Vivid:
  Confirmed

Bug description:
  Starting in 3.15, arm64 began defaulting to non-coherent dma_ops:

  commit c7a4a7658d689f664050c45493d79adf053f226e
  Author: Ritesh Harjani ritesh.harj...@gmail.com
  Date:   Wed Apr 23 06:29:46 2014 +0100

  arm64: Make default dma_ops to be noncoherent

  Firmware (dtb in the case of the m400) is responsible for telling the
  kernel when a device requires coherent dma_ops. However, as of utopic,
  this property is not being inherited by downstream devices.
  Specifically, the xgene-pcie device is marked as coherent, but the
  devices behind it (mellanox card) still get initialized with non-
  coherent ops.

  This results in the mlx4 driver bailing out with the following messages:
  [   18.703635] mlx4_core :01:00.0: command 0x23 timed out (go bit not 
cleared)
  [   18.710911] mlx4_core :01:00.0: Failed to initialize queue pair table, 
aborting

  
  There's an upstream discussion on the topic here:
http://www.spinics.net/lists/arm-kernel/msg362320.html

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

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

[Kernel-packages] [Bug 1416849] Re: Booted into blank screen after the security update

2015-02-25 Thread Aikawa Takuya

Hi,

I've just done the latest security update,
but the same problem exists with the newly installed(updated) v. 3.13.0-46 
kernel.
Also on ASUS X200MA. The hardware configurations are the same as reported above.

I expect further developments. Thank you.

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

Title:
  Booted into blank screen after the security update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 14.04 on ASUS X200MA laptop.
  After applying the security update to the linux kernel, the boot process 
failed.

  Summary:
  Grub load, empty purple screen appears and disappears,
  then the backlight turns off... it DOES NOT turn on and the log in drum sound 
rings.

  It is just like the former bug reported below:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/919350

  Now I am running on the previous kernel 3.13.0-44 #73-Ubuntu
  (with selecting from Grub menu), and have no problem on booting.

  I appreciate your help and cooperation. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aikawatakuya   1859 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  2 00:18:17 2015
  HibernationDevice: RESUME=UUID=1d9c88a7-1473-4d4e-917d-46fc21e38a98
  InstallationDate: Installed on 2014-11-09 (84 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic.efi.signed 
root=UUID=7ac07a5f-b038-40ac-a6a1-e0f4ccbb69c3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-44-generic N/A
   linux-backports-modules-3.13.0-44-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.500
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.500:bd05/04/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 944908] Re: After the command [sudo][halt] PC is still open.

2015-02-25 Thread Rarylson Freitas

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

** This bug is no longer a duplicate of bug 880240
   system doesn't turn off if sudo halt is given
** This bug has been marked a duplicate of bug 991997
   Wrong comment in /etc/default/halt: Default behavior of halt changed to 
halt only instead of powering off

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

Title:
  After the command [sudo][halt] PC is still open.

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed Ubuntu 11.10 for the first time in Jan-2012. Since the first 
moment was this problem, every time I used the command:
sudo apt-get update; sudo apt-get upgrade; sudo halt
  The PC does not turn off, instead reaches the Ubuntu logo with the five dots 
underneath and stays in that state in perpetual.
  I tried the simple command:
sudo halt
  but still the same problem.
  This problem is in both terminal window and the virtual console.
  One curious fact is that this problem was with the command:
sudo reboot
  too in the beginning but not anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,move,imgjpeg,zoom,shift,opacify,snap,imgpng,regex,cube,gnomecompat,resize,grid,mousepoll,place,scale,ezoom,switcher,unityshell]
  Date: Fri Mar  2 17:34:10 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 967049] Re: Ubuntu 12.04-beta2-i386 as guest on KVM no halt

2015-02-25 Thread Rarylson Freitas

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

** This bug is no longer a duplicate of bug 880240
   system doesn't turn off if sudo halt is given
** This bug has been marked a duplicate of bug 991997
   Wrong comment in /etc/default/halt: Default behavior of halt changed to 
halt only instead of powering off

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

Title:
  Ubuntu 12.04-beta2-i386  as guest on KVM no halt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On guest
  # halt
  but guest do not halted  (please, see attach vnc screenshot)

  KVM HN  - Centos 6.2

  Domain xml

  domain type='kvm'
namedragon-backup/name
uuid0cfea522-fed4-fa47-4b67-56184d5a17cd/uuid
memory1048576/memory
currentMemory1048576/currentMemory
vcpu1/vcpu
os
  type arch='x86_64' machine='rhel6.2.0'hvm/type
  boot dev='hd'/
/os
features
  acpi/
  apic/
  pae/
/features
clock offset='utc'/
on_poweroffdestroy/on_poweroff
on_rebootrestart/on_reboot
on_crashrestart/on_crash
devices
  emulator/usr/libexec/qemu-kvm/emulator
  disk type='file' device='disk'
driver name='qemu' type='raw' cache='writeback'/
source file='/var/lib/libvirt/images/backup.img'/
target dev='hda' bus='ide'/
address type='drive' controller='0' bus='0' unit='0'/
  /disk
  disk type='block' device='cdrom'
driver name='qemu' type='raw'/
target dev='hdc' bus='ide'/
readonly/
address type='drive' controller='0' bus='1' unit='0'/
  /disk
  controller type='ide' index='0'
address type='pci' domain='0x' bus='0x00' slot='0x01' 
function='0x1'/
  /controller
  interface type='network'
mac address='52:54:00:40:4b:c1'/
source network='default'/
model type='virtio'/
address type='pci' domain='0x' bus='0x00' slot='0x03' 
function='0x0'/
  /interface
  serial type='pty'
target port='0'/
  /serial
  console type='pty'
target type='serial' port='0'/
  /console
  input type='mouse' bus='ps2'/
  graphics type='vnc' port='5905' autoport='no' listen='10.0.0.1' 
passwd='123'
listen type='address' address='10.0.0.1'/
  /graphics
  video
model type='cirrus' vram='9216' heads='1'/
address type='pci' domain='0x' bus='0x00' slot='0x02' 
function='0x0'/
  /video
  memballoon model='virtio'
address type='pci' domain='0x' bus='0x00' slot='0x04' 
function='0x0'/
  /memballoon
/devices
  /domain
  --- 
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 1.95-0ubuntu1
  Architecture: i386
  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 12.04
  InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Beta i386 
(20120229)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae 
root=UUID=9e4e8818-880c-4009-94e3-d6f9752af1d9 ro
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.2.0-20-generic-pae i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.2.0PC:cvnRedHat:ct1:cvr:
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.2.0 PC
  dmi.sys.vendor: Red Hat

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

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

[Kernel-packages] [Bug 1353021] Re: USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04

2015-02-25 Thread Emanem

Apologies for this question, don't know where I can find the answer to it: when 
the above version of the kernel will be officially released?
Currently I have:

uname -a
Linux scv 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 UTC 2014 x86_64 
x86_64 x86_64 GNU/Linux

Cheers!

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

Title:
  USB HIDRAW Feature Report Implementation for HID devices not working
  correctly in Ubuntu 14.04

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

Bug description:
  With the release of Ubuntu 14.04 I've been investigating an issue with
  a software library I maintain to talk to USB based HID signature pads.
  I believe I've narrowed the issue down to the HIDRAW implementation
  released with Ubuntu 14.04. Essentially what  seems to be failing is
  the ioctl to get feature reports (HIDIOCGFEATURE). Any attempt to get
  a feature report results in a failure with a ENODEV error code.

  The devices I'm testing with are USB signature pads
  (http://www.scriptel.com). These signature pads use HID feature
  reports to communicate capabilities and to set up the device. I can
  provide further information along with USB/HID descriptors if it would
  be helpful.

  I have been testing with Ubuntu 14.04 Desktop (x64) with kernel version:
  Linux hostname 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

  This kernel exhibits the problematic behavior, but when testing with Ubuntu 
13.10 Desktop (x64):
  Linux hostname 3.11.0-23-generic #40-Ubuntu SMP Wed Jun 4 21:05:23 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  The 13.10 kernel's version of HIDRAW seems to work correctly. I've also 
tested with the vanilla kernel:
  Linux hostname 3.13.1-hidtest #1 SMP Tue Aug 5 09:14:28 EDT 2014 x86_64 
x86_64 x86_64 GNU/Linux

  The vanilla kernel appears to work correctly as well. Kernel source used was 
downloaded from:
  https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.13.1.tar.xz
  The configuration file used was from config-3.13.0-32-generic provided in 
linux-image-3.13.0-32-generic

  I believe the breaking change was made as part of commit
  aa6c390c4d59c9ff4fffd887e15783b2b793951b as part of ubuntu/ubuntu-
  trusty.git.

  I have attached a simple C program to demonstrate the problem. You'll
  need a USB HID device with known feature reports.

  Please let me know if I can provide any additional information or be
  of any assistance.

  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.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mpowers2863 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  5 13:51:39 2014
  HibernationDevice: RESUME=UUID=3a5a866c-6086-47d6-8080-70715896a719
  InstallationDate: Installed on 2014-04-17 (109 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=9b49575f-fb86-45d7-af5e-b3fde82f91ac ro 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: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1762II1.50U
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CZ-17
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1762II1.50U:bd12/07/2012:svn:pnCZ-17:pvrREV1.0:rvn:rnCZ-17:rvrREV1.0:cvnToBeFilledByO.E.M.:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.name: CZ-17
  dmi.product.version: REV:1.0

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

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

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

2015-02-25 Thread Mathew Hodson

** Description changed:

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

-- 
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:
  New
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:
  New
Status in linux-lts-raring source package in Precise:
  Won't Fix
Status in linux-lts-saucy source package in Precise:
  New
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 linux-mvl-dove source package in Trusty:
  Invalid
Status in

[Kernel-packages] [Bug 1417313] Re: [Hyper-V] vmbus: incorrect device name is printed when child device is unregistered

2015-02-25 Thread Stephen A. Zarkos

Thanks for this, we will take this kernel and test.  The issue is
intermittent and would likely only show up during stress tests, so it
may take a few days for results.

Thanks!

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

Title:
  [Hyper-V] vmbus: incorrect device name is printed when child device is
  unregistered

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

Bug description:
  This issue impacts Ubuntu 12.04.

  Whenever a device is unregistered in vmbus_device_unregister
  (drivers/hv/vmbus_drv.c), the device name in the log message may
  contain garbage as the memory has already been freed by the time
  pr_info is called.  Log example:

[ 3149.170475] hv_vmbus: child device àõsèè0_5 unregistered

  By logging the message just before calling device_unregister, the
  correct device name is printed:

[ 3145.034652] hv_vmbus: child device vmbus_0_5 unregistered

  
  This issue has been resolved with the upstream patch: 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/vmbus_drv.c?id=84672369ffb98a51d4ddf74c20a23636da3ad615

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

-- 
Mailing list: https://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 1353021] Re: USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04

2015-02-25 Thread Reilly Grant

3.13.0-36-generic is the first kernel version that includes the fix.

On Wed, Feb 25, 2015 at 11:30 AM Emanem em4...@gmail.com wrote:

 Apologies for this question, don't know where I can find the answer to it:
 when the above version of the kernel will be officially released?
 Currently I have:

 uname -a
 Linux scv 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 UTC 2014
 x86_64 x86_64 x86_64 GNU/Linux

 Cheers!

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

 Title:
   USB HIDRAW Feature Report Implementation for HID devices not working
   correctly in Ubuntu 14.04

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

 Bug description:
   With the release of Ubuntu 14.04 I've been investigating an issue with
   a software library I maintain to talk to USB based HID signature pads.
   I believe I've narrowed the issue down to the HIDRAW implementation
   released with Ubuntu 14.04. Essentially what  seems to be failing is
   the ioctl to get feature reports (HIDIOCGFEATURE). Any attempt to get
   a feature report results in a failure with a ENODEV error code.

   The devices I'm testing with are USB signature pads
   (http://www.scriptel.com). These signature pads use HID feature
   reports to communicate capabilities and to set up the device. I can
   provide further information along with USB/HID descriptors if it would
   be helpful.

   I have been testing with Ubuntu 14.04 Desktop (x64) with kernel version:
   Linux hostname 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08
 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

   This kernel exhibits the problematic behavior, but when testing with
 Ubuntu 13.10 Desktop (x64):
   Linux hostname 3.11.0-23-generic #40-Ubuntu SMP Wed Jun 4 21:05:23 UTC
 2014 x86_64 x86_64 x86_64 GNU/Linux

   The 13.10 kernel's version of HIDRAW seems to work correctly. I've also
 tested with the vanilla kernel:
   Linux hostname 3.13.1-hidtest #1 SMP Tue Aug 5 09:14:28 EDT 2014
 x86_64 x86_64 x86_64 GNU/Linux

   The vanilla kernel appears to work correctly as well. Kernel source used
 was downloaded from:
   https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.13.1.tar.xz
   The configuration file used was from config-3.13.0-32-generic provided
 in linux-image-3.13.0-32-generic

   I believe the breaking change was made as part of commit
   aa6c390c4d59c9ff4fffd887e15783b2b793951b as part of ubuntu/ubuntu-
   trusty.git.

   I have attached a simple C program to demonstrate the problem. You'll
   need a USB HID device with known feature reports.

   Please let me know if I can provide any additional information or be
   of any assistance.

   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.2
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  mpowers2863 F pulseaudio
   CurrentDesktop: Unity
   Date: Tue Aug  5 13:51:39 2014
   HibernationDevice: RESUME=UUID=3a5a866c-6086-47d6-8080-70715896a719
   InstallationDate: Installed on 2014-04-17 (109 days ago)
   InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64
 (20140417)
   ProcFB:
0 inteldrmfb
1 nouveaufb
   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic
 root=UUID=9b49575f-fb86-45d7-af5e-b3fde82f91ac ro 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: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/07/2012
   dmi.bios.vendor: American Megatrends Inc.
   dmi.bios.version: E1762II1.50U
   dmi.board.asset.tag: To be filled by O.E.M.
   dmi.board.name: CZ-17
   dmi.board.version: REV:1.0
   dmi.chassis.asset.tag: No Asset Tag
   dmi.chassis.type: 10
   dmi.chassis.vendor: To Be Filled By O.E.M.
   dmi.chassis.version: To be filled by O.E.M.
   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:
 bvrE1762II1.50U:bd12/07/2012:svn:pnCZ-17:pvrREV1.0:rvn:rnCZ-17:rvrREV1.0:
 cvnToBeFilledByO.E.M.:ct10:cvrTobefilledbyO.E.M.:
   dmi.product.name: CZ-17
   dmi.product.version: REV:1.0

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


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

Title:
  USB HIDRAW Feature Report Implementation for HID devices not working
  correctly in Ubuntu 14.04

Status in linux package in Ubuntu:
  Fix Released
Status in

[Kernel-packages] [Bug 1425636] [NEW] package linux-image-3.13.0-46-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2015-02-25 Thread trk-hun

Public bug reported:

The swap is not connected at startup. All times must be turned on
manually, but the command line is not possible. Only gparted or other
graphical screen.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-46-generic (not installed)
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.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  trk3825 F pulseaudio
 /dev/snd/controlC0:  trk3825 F pulseaudio
Date: Wed Feb 25 19:19:37 2015
DuplicateSignature: package:linux-image-3.13.0-46-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
HibernationDevice: RESUME=UUID=6cfa313d-b42b-4ec0-a910-dc09e83c354f
InstallationDate: Installed on 2014-09-01 (177 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
IwConfig:
 usb0  no wireless extensions.
 
 lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=75d43c4b-337c-48d7-b8aa-e67363909d28 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
RfKill:
 
SourcePackage: linux
Title: package linux-image-3.13.0-46-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/24/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A85-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6401:bd12/24/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-MPRO:rvrRevX.0x: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-package need-duplicate-check 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/1425636

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

Status in linux package in Ubuntu:
  New

Bug description:
  The swap is not connected at startup. All times must be turned on
  manually, but the command line is not possible. Only gparted or other
  graphical screen.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-46-generic (not installed)
  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.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trk3825 F pulseaudio
   /dev/snd/controlC0:  trk3825 F pulseaudio
  Date: Wed Feb 25 19:19:37 2015
  DuplicateSignature: package:linux-image-3.13.0-46-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=6cfa313d-b42b-4ec0-a910-dc09e83c354f
  InstallationDate: Installed on 2014-09-01 (177 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   usb0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=75d43c4b-337c-48d7-b8aa-e67363909d28 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
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-3.13.0-46-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6401
  dmi.board.asset.tag: To be filled by O.E.M.

[Kernel-packages] [Bug 1415562] Re: [Ubuntu 15.04] Support firmware assisted dump on ppc64le

2015-02-25 Thread Breno Leitão

Tested internally at IBM and the problem is solved in kernel 3.19 from
the ckt PPA.

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

Title:
  [Ubuntu 15.04] Support firmware assisted dump on ppc64le

Status in linux package in Ubuntu:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  Starting from POWER6, the firmware now has a capability to preserve
  the partition memory dump during system crash and boot into a fresh
  copy of the kernel with fully-reset system. This feature adds the
  necessary support to exploit the dump capture capability provided by
  Power firmware.  With this feature support, the production kernel will
  register for firmware-assisted dump using RTAS (Runtime Abstraction
  Service) calls and builds required ELF header which then gets exported
  through '/proc/vmcore' in the second kernel after crash.  This feature
  improves Power serviceability by making it more robust compared to
  current kdump mechanism on Linux.

  Ubuntu 15.04 kernel already includes the necessary code for fadump.
  The only kernel change needed is to enable CONFIG_FA_DUMP in the
  kernel configuration. In addition, an update is needed for a script in
  kdump-tools package.

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

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

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

This change was made by a bot.

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

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The swap is not connected at startup. All times must be turned on
  manually, but the command line is not possible. Only gparted or other
  graphical screen.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-46-generic (not installed)
  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.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  trk3825 F pulseaudio
   /dev/snd/controlC0:  trk3825 F pulseaudio
  Date: Wed Feb 25 19:19:37 2015
  DuplicateSignature: package:linux-image-3.13.0-46-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=6cfa313d-b42b-4ec0-a910-dc09e83c354f
  InstallationDate: Installed on 2014-09-01 (177 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   usb0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=75d43c4b-337c-48d7-b8aa-e67363909d28 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
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-3.13.0-46-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6401:bd12/24/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE

2015-02-25 Thread Seth Arnold

There's a chance this is the AppArmor cross profile IPC check; when
one process performs an IPC operation with a second process, in
different profiles, both profiles have to allow the operation.

If my guess is right, these ought to be silenced by changing:

  /dev/log wl,
to
  /dev/log rwl,

in the /etc/apparmor.d/usr.sbin.rsyslogd file and reloading the policy
with apparmor_parser --replace /etc/apparmor.d/usr.sbin.rsyslogd

Thanks

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

Title:
  Apparmor uses rsyslogd profile for different processes - utopic HWE

Status in apparmor package in Ubuntu:
  New
Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  Hi.

  I've noticed that apparmor loads /usr/sbin/rsyslogd profile for
  completely unrelated processes:

  Feb 25 08:36:19 emma kernel: [  134.796218] audit: type=1400 
audit(1424842579.429:245): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 25 08:36:23 emma kernel: [  139.330989] audit: type=1400 
audit(1424842583.965:246): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 25 08:35:42 emma kernel: [   97.912402] audit: type=1400 
audit(1424842542.565:241): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie 
requested_mask=r denied_mask=r fsuid=103 ouid=0
  Feb 25 08:34:43 emma kernel: [   38.867998] audit: type=1400 
audit(1424842483.546:226): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd 
requested_mask=r denied_mask=r fsuid=0 ouid=0

  
  I'm not sure how apparmor decides which profile to use for which task, but is 
shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc.

  
  I'm running:
  # lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  # dpkg -l | grep apparmor
  ii  apparmor2.8.95~2430-0ubuntu5.1   
amd64User-space parser utility for AppArmor
  ii  apparmor-profiles   2.8.95~2430-0ubuntu5.1   
all  Profiles for AppArmor Security policies
  ii  apparmor-utils  2.8.95~2430-0ubuntu5.1   
amd64Utilities for controlling AppArmor
  ii  libapparmor-perl2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Perl bindings
  ii  libapparmor1:amd64  2.8.95~2430-0ubuntu5.1   
amd64changehat AppArmor library
  ii  python3-apparmor2.8.95~2430-0ubuntu5.1   
amd64AppArmor Python3 utility library
  ii  python3-libapparmor 2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Python3 bindings

  # uname -a
  Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1424676] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)]

2015-02-25 Thread Rodrigo-vivi

Also change STATION_INFO_SIGNAL to BIT(NL80211_STA_INFO_SIGNAL)

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first
  use in this function)]

Status in bcmwl package in Ubuntu:
  New

Bug description:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.0.0-04rc1-generic
  Date: Mon Feb 23 18:14:07 2015
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20:
 error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)
  InstallationDate: Installed on 2014-11-22 (93 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141121)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu2
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

2015-02-25 Thread Kaare Baastrup

Its not the Kernel but the firmware :-( there is no firmware 2.1
existing for Linux yet :-(

Someone will have to write it or do some magic with a windows
firmware...

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1424676] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)]

2015-02-25 Thread Rodrigo-vivi

Try this:
-   sinfo-filled |= STATION_INFO_TX_BITRATE;
+   sinfo-filled |= BIT(NL80211_STA_INFO_TX_BITRATE);

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first
  use in this function)]

Status in bcmwl package in Ubuntu:
  New

Bug description:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.0.0-04rc1-generic
  Date: Mon Feb 23 18:14:07 2015
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20:
 error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)
  InstallationDate: Installed on 2014-11-22 (93 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141121)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu2
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1408972] Re: openvswitch: failed to flow_del (No such file or directory)

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

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

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

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

Title:
  openvswitch: failed to flow_del (No such file or directory)

Status in linux package in Ubuntu:
  In Progress
Status in openvswitch package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in openvswitch source package in Trusty:
  New

Bug description:
  As part of the investigation into bug 1336555, we've noticed a large
  number of these error messages being logged in 14.04 OpenStack
  deployments:

  2015-01-09T10:50:53.643Z|03976|dpif|WARN|system@ovs-system: failed to 
flow_del (No such file or directory) 
skb_priority(0),in_port(4),skb_mark(0),eth(src=ce:2b:3a:c3:d7:d1,dst=33:33:ff:50:c2:61),eth_type(0x86dd),ipv6(src=::,dst=ff02::1:ff50:c261,label=0,proto=58,tclass=0,hlimit=255,frag=no),icmpv6(type=135,code=0),nd(target=fe80::5ccd:caff:fe50:c261)
  2015-01-09T10:50:54.644Z|03977|dpif|WARN|system@ovs-system: failed to 
flow_del (No such file or directory) 
skb_priority(0),in_port(4),skb_mark(0),eth(src=ce:2b:3a:c3:d7:d1,dst=33:33:ff:50:c2:61),eth_type(0x86dd),ipv6(src=::,dst=ff02::1:ff50:c261,label=0,proto=58,tclass=0,hlimit=255,frag=no),icmpv6(type=135,code=0),nd(target=fe80::5ccd:caff:fe50:c261)
  2015-01-09T10:50:55.645Z|03978|dpif|WARN|system@ovs-system: failed to 
flow_del (No such file or directory) 
skb_priority(0),in_port(4),skb_mark(0),eth(src=ce:2b:3a:c3:d7:d1,dst=33:33:ff:50:c2:61),eth_type(0x86dd),ipv6(src=::,dst=ff02::1:ff50:c261,label=0,proto=58,tclass=0,hlimit=255,frag=no),icmpv6(type=135,code=0),nd(target=fe80::5ccd:caff:fe50:c261)
  2015-01-09T10:50:56.645Z|03979|dpif|WARN|system@ovs-system: failed to 
flow_del (No such file or directory) 
skb_priority(0),in_port(4),skb_mark(0),eth(src=ce:2b:3a:c3:d7:d1,dst=33:33:ff:50:c2:61),eth_type(0x86dd),ipv6(src=::,dst=ff02::1:ff50:c261,label=0,proto=58,tclass=0,hlimit=255,frag=no),icmpv6(type=135,code=0),nd(target=fe80::5ccd:caff:fe50:c261)
  2015-01-09T10:50:57.646Z|03980|dpif|WARN|system@ovs-system: failed to 
flow_del (No such file or directory) 
skb_priority(0),in_port(4),skb_mark(0),eth(src=ce:2b:3a:c3:d7:d1,dst=33:33:ff:50:c2:61),eth_type(0x86dd),ipv6(src=::,dst=ff02::1:ff50:c261,label=0,proto=58,tclass=0,hlimit=255,frag=no),icmpv6(type=135,code=0),nd(target=fe80::5ccd:caff:fe50:c261)
  2015-01-09T10:50:58.646Z|03981|dpif|WARN|system@ovs-system: failed to 
flow_del (No such file or directory) 
skb_priority(0),in_port(4),skb_mark(0),eth(src=ce:2b:3a:c3:d7:d1,dst=33:33:ff:50:c2:61),eth_type(0x86dd),ipv6(src=::,dst=ff02::1:ff50:c261,label=0,proto=58,tclass=0,hlimit=255,frag=no),icmpv6(type=135,code=0),nd(target=fe80::5ccd:caff:fe50:c261)
  2015-01-09T10:50:59.645Z|03982|dpif|WARN|system@ovs-system: failed to 
flow_del (No such file or directory) 
skb_priority(0),in_port(4),skb_mark(0),eth(src=ce:2b:3a:c3:d7:d1,dst=33:33:ff:50:c2:61),eth_type(0x86dd),ipv6(src=::,dst=ff02::1:ff50:c261,label=0,proto=58,tclass=0,hlimit=255,frag=no),icmpv6(type=135,code=0),nd(target=fe80::5ccd:caff:fe50:c261)
  2015-01-09T10:51:00.646Z|03983|dpif|WARN|system@ovs-system: failed to 
flow_del (No such file or directory) 
skb_priority(0),in_port(4),skb_mark(0),eth(src=ce:2b:3a:c3:d7:d1,dst=33:33:ff:50:c2:61),eth_type(0x86dd),ipv6(src=::,dst=ff02::1:ff50:c261,label=0,proto=58,tclass=0,hlimit=255,frag=no),icmpv6(type=135,code=0),nd(target=fe80::5ccd:caff:fe50:c261)
  2015-01-09T10:51:01.646Z|03984|dpif|WARN|system@ovs-system: failed to 
flow_del (No such file or directory) 
skb_priority(0),in_port(4),skb_mark(0),eth(src=ce:2b:3a:c3:d7:d1,dst=33:33:ff:50:c2:61),eth_type(0x86dd),ipv6(src=::,dst=ff02::1:ff50:c261,label=0,proto=58,tclass=0,hlimit=255,frag=no),icmpv6(type=135,code=0),nd(target=fe80::5ccd:caff:fe50:c261)

  this was fixed upstream in the datapath dkms module (see
  https://github.com/openvswitch/ovs/commit/3601bd879) and is fixed in
  the 3.16 kernel as well; please can this fix be backported to 3.13.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-generic 3.13.0.43.50
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 11 21:01 seq
   crw-rw 1 root audio 116, 33 Dec 11 21:01 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Jan  9 10:50:39 2015
  IwConfig: Error: [Errno 2] No such

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

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

apport-collect 1425699

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

Title:
  kernel panic on IBM Power8 PPC MAAS ephemeral image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel running on the 14.04 ephemeral image for MAAS when
  commissioning an IBM Power8 PPC server causes a periodic kernel panic.

  This happens intermittently and cannot be forcefully reproduced.

  The kernel version on the image is 3.13.0-27.50-generic according to
  the boot process.

  Attached is the boot process log with the kernel panics.

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

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

[Kernel-packages] [Bug 1425699] [NEW] kernel panic on IBM Power8 PPC MAAS ephemeral image

2015-02-25 Thread Mike Rushton

Public bug reported:

The kernel running on the 14.04 ephemeral image for MAAS when
commissioning an IBM Power8 PPC server causes a periodic kernel panic.

This happens intermittently and cannot be forcefully reproduced.

The kernel version on the image is 3.13.0-27.50-generic according to the
boot process.

Attached is the boot process log with the kernel panics.

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

** Attachment added: commission.log
   
https://bugs.launchpad.net/bugs/1425699/+attachment/4327589/+files/commission.log

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

Title:
  kernel panic on IBM Power8 PPC MAAS ephemeral image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The kernel running on the 14.04 ephemeral image for MAAS when
  commissioning an IBM Power8 PPC server causes a periodic kernel panic.

  This happens intermittently and cannot be forcefully reproduced.

  The kernel version on the image is 3.13.0-27.50-generic according to
  the boot process.

  Attached is the boot process log with the kernel panics.

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

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

[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE

Seth is correct,

when a message is sent across a unix based file socket their is a cross
check (one check for the sender, and another for the receiver). In this
case the receiving end of the message (rsyslogd) does not have the
correct permission (r perm).

The reason this is reported with the pid and comm of other processes is
that the check (for both sender and receiver) is done in the kernel
context of the sending process.

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

Title:
  Apparmor uses rsyslogd profile for different processes - utopic HWE

Status in apparmor package in Ubuntu:
  New
Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  Hi.

  I've noticed that apparmor loads /usr/sbin/rsyslogd profile for
  completely unrelated processes:

  Feb 25 08:36:19 emma kernel: [  134.796218] audit: type=1400 
audit(1424842579.429:245): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 25 08:36:23 emma kernel: [  139.330989] audit: type=1400 
audit(1424842583.965:246): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 25 08:35:42 emma kernel: [   97.912402] audit: type=1400 
audit(1424842542.565:241): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie 
requested_mask=r denied_mask=r fsuid=103 ouid=0
  Feb 25 08:34:43 emma kernel: [   38.867998] audit: type=1400 
audit(1424842483.546:226): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd 
requested_mask=r denied_mask=r fsuid=0 ouid=0

  
  I'm not sure how apparmor decides which profile to use for which task, but is 
shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc.

  
  I'm running:
  # lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  # dpkg -l | grep apparmor
  ii  apparmor2.8.95~2430-0ubuntu5.1   
amd64User-space parser utility for AppArmor
  ii  apparmor-profiles   2.8.95~2430-0ubuntu5.1   
all  Profiles for AppArmor Security policies
  ii  apparmor-utils  2.8.95~2430-0ubuntu5.1   
amd64Utilities for controlling AppArmor
  ii  libapparmor-perl2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Perl bindings
  ii  libapparmor1:amd64  2.8.95~2430-0ubuntu5.1   
amd64changehat AppArmor library
  ii  python3-apparmor2.8.95~2430-0ubuntu5.1   
amd64AppArmor Python3 utility library
  ii  python3-libapparmor 2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Python3 bindings

  # uname -a
  Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1370028] Re: CVE-2014-3182

** Also affects: linux (Ubuntu Vivid)
   Importance: Medium
   Status: New

** Also affects: linux-fsl-imx51 (Ubuntu Vivid)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Vivid)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ec2 (Ubuntu Vivid)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-armadaxp (Ubuntu Vivid)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Vivid)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Vivid)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Vivid)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-trusty (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided = Medium

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New = Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: linux-lts-trusty (Ubuntu Lucid)
   Status: New = Invalid

** Changed in: linux-lts-trusty (Ubuntu Lucid)
   Importance: Undecided = Medium

** Changed in: linux-lts-trusty (Ubuntu Vivid)
   Status: New = Invalid

** Changed in: linux-lts-trusty (Ubuntu Vivid)
   Importance: Undecided = Medium

** Changed in: linux-lts-trusty (Ubuntu Utopic)
   Status: New = Invalid

** Changed in: linux-lts-trusty (Ubuntu Utopic)
   Importance: Undecided = Medium

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

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

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Importance: Undecided = Medium

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: New = Invalid

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: linux-lts-utopic (Ubuntu Lucid)
   Status: New = Invalid

** Changed in: linux-lts-utopic (Ubuntu Lucid)
   Importance: Undecided = Medium

** Changed in: linux-lts-utopic (Ubuntu Vivid)
   Status: New = Invalid

** Changed in: linux-lts-utopic (Ubuntu Vivid)
   Importance: Undecided = Medium

** Changed in: linux-lts-utopic (Ubuntu Utopic)
   Status: New = Invalid

** Changed in: linux-lts-utopic (Ubuntu Utopic)
   Importance: Undecided = Medium

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: linux-lts-raring (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/1423757

Title:
  CVE-2015-1593

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 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 in Utopic:
  Invalid
Status in linux-lts-utopic

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

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

** Description changed:

  [incorrect data type in llc2_timeout_table]
  
- Break-Fix: - 6b8d9117ccb4f81b1244aafa7bc70ef8fa45fc49
+ Break-Fix: 590232a7150674b2036291eaefce085f3f9659c8
+ 6b8d9117ccb4f81b1244aafa7bc70ef8fa45fc49

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

[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

2015-02-25 Thread Roman

I checked it. The new ath10k is definitely merged into the v4.0-rc1. Why
do you need the firnware 2.1? Did you tried hw 3.0 from here:
https://github.com/kvalo/ath10k-firmware ?

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1425699] Re: kernel panic on IBM Power8 PPC MAAS ephemeral image

2015-02-25 Thread Mike Rushton

Sorry, due to the nature of the bug(kernel panic) I am not able to login
to or access the ephemeral image to grab any logs.

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

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

Title:
  kernel panic on IBM Power8 PPC MAAS ephemeral image

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel running on the 14.04 ephemeral image for MAAS when
  commissioning an IBM Power8 PPC server causes a periodic kernel panic.

  This happens intermittently and cannot be forcefully reproduced.

  The kernel version on the image is 3.13.0-27.50-generic according to
  the boot process.

  Attached is the boot process log with the kernel panics.

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

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

[Kernel-packages] [Bug 1420935] Re: Centrino Wireless-N 1030 randomly disconnecting

2015-02-25 Thread Viktor Pal

To workaround this bug.

Create a file named: /etc/modprobe.d/wifi_bug.conf

Add the following lines to the file:
options iwlmvm power_scheme=1
options iwlwifi bt_coex_active=N swcrypto=1 11n_disable=1

Set the file's ownership the same as other files in that folder.

Reboot.

Please note though that this fixes the issue, but prevents N mode from
working, so you are stick with B and G modes.

Otherwise I'm very disappointed that no one cares about this bug as I would be
glad to provide all the information I'm able to to get this fixed.
The other thing that makes me very sad is that this was already working
perfectly in the past with 12.04 and now it isn't.
This really sounds to me like a step backwards...

Sorry for being emotional.

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

Title:
Centrino Wireless-N 1030 randomly disconnecting

Status in linux-firmware package in Ubuntu:
New

Bug description:
1) The release of Ubuntu you are using:
Description: Linux Mint 17.1 Rebecca
Release: 17.1

Ubuntu version:
Ubuntu 14.04

2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
Maybe linux-image, linux-firmware or network-manager.

3) What you expected to happen
Permanent wifi connection.

4) What happened instead
Wireless is disconnecting randomly.

This wifi card was working for me with Ubuntu 12.04 for several years before
flawlessly.
Now I installed Linux Mint based on Ubuntu 14.04 and it is now randomly
disconnecting.
When it disconnects I disable wireless in the NM applet and enable it again
and wifi reconnects.
Logs regarding the disconnect and the reconnect are attached to the report.

The disconnect happens 10 to 60 minutes after it was connected or
reconnected.

The laptop I'm using is a Dell Inspiron N5110 which is officially supported
by Ubuntu:
http://www.ubuntu.com/certification/hardware/201012-6932/

It seems that I'm not the only one with this issue:
http://forums.linuxmint.com/viewtopic.php?f=53t=169633
http://ubuntuforums.org/showthread.php?t=2220377
http://ubuntuforums.org/showthread.php?t=2219014
http://forum.ubuntu-fr.org/viewtopic.php?id=1550761

http://askubuntu.com/questions/453156/wifi-connection-periodically-dropping-in-centrino-wireless-n-1030

http://askubuntu.com/questions/363126/slow-wifi-after-with-centrino-wireless-n-1030-rainbow-peak

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-firmware 1.127.11
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Wed Feb 11 20:14:39 2015
Dependencies:

PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1424676] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)]

2015-02-25 Thread Michael Leuchtenburg

This fixes the build issue and also silences a couple of warnings. I
suppose you could edit out the warning silencing if you hate clean
builds, or move it into a different patch.

Also needs to be added to dkms.conf:
PATCH[9]=0017-add-support-for-Linux-4.0.patch

** Patch added: 0017-add-support-for-Linux-4.0.patch
   
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1424676/+attachment/4327652/+files/0017-add-support-for-Linux-4.0.patch

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first
  use in this function)]

Status in bcmwl package in Ubuntu:
  New

Bug description:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.0.0-04rc1-generic
  Date: Mon Feb 23 18:14:07 2015
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20:
 error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)
  InstallationDate: Installed on 2014-11-22 (93 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141121)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu2
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 994931] Re: Altering use_tempaddr drops all IPv6 addresses

2015-02-25 Thread David Lawson

The test kernel works (and fixes the problem) on precise, on our trusty
test server we don't have any network devices (other than lo0) with the
test kernel booted, so we can't really test the IPv6 aspect.

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

Title:
  Altering use_tempaddr drops all IPv6 addresses

Status in The Linux Kernel:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Utopic:
  Invalid

Bug description:
  $ uname -a
  Linux expvr-alnilam 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59 
UTC 2012 i686 i686 i386 GNU/Linux

  $ sysctl net.ipv6.conf.eth2.use_tempaddr
  net.ipv6.conf.eth2.use_tempaddr = 2
  # (as per the default /etc/sysctl.d/10-ipv6-privacy.conf in 12.04)

  # Add a static IPv6 address:
  $ sudo ip addr add 2001:470:9321:f003::1122/64 dev eth2

  # Verify that it has been set up, and that a temporary address and a SLAAC 
address also exist:
  $ ip -6 addr list dev eth2
  4: eth2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000
  inet6 2001:470:9321:f003:74e3:aa2b:7ee5:c002/64 scope global temporary 
dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003:6c97:24ff:fe3f:263b/64 scope global dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003::1122/64 scope global 
 valid_lft forever preferred_lft forever
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link 
 valid_lft forever preferred_lft forever

  # Disable RFC 4941 temporary addresses:
  $ sudo sysctl net.ipv6.conf.eth2.use_tempaddr=0
  net.ipv6.conf.eth2.use_tempaddr = 0

  $ ip -6 addr list dev eth2
  4: eth2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link tentative 
 valid_lft forever preferred_lft forever

  I.e. on setting use_tempaddr=0, _all_ IPv6 addresses are removed,
  including statically-configured and non-temporary SLAAC-configured
  addresses.  (The link-local address reappears quickly but the
  'tentative' flag indicates that it has been newly re-added.  The SLAAC
  address reappears after a slightly longer interval as the kernel
  continues to undergo SLAAC, but the static address is gone forever
  unless manually reinstated.)

  The same happens if use_tempaddr is changed from 0 back to 2.

  The expected outcome is that only temporary addresses are affected by a 
change to use_tempaddr.
  --- 
  AcpiTables:
   
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 May  5 03:53 seq
   crw-rw---T 1 root audio 116, 33 May  5 03:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  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: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  DistroRelease: Ubuntu 12.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen.linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=b16ffd9c-a54a-4dd3-a839-16c382ea8787 ro  
console=hvc0
  ProcModules:
   lp 17455 0 - Live 0x
   parport 40930 1 lp, Live 0x
   xenfs 17877 1 - Live 0x
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic-pae N/A
   linux-backports-modules-3.2.0-24-generic-pae  N/A
   linux-firmware1.79
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.2.0-24-generic-pae i686
  UpgradeStatus: Upgraded to precise on 2012-05-05 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Kernel-packages] [Bug 1424394] Re: Suspend/Resume does not fully work on 14.10

2015-02-25 Thread Lepaffe Philippe

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

Title:
  Suspend/Resume does not fully work on 14.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using an Asus Zenbook UX301LA and it often doesn't suspend
  properly on 14.10.

  When the bug occurs, the fans keep going faintly even after the lid
  has been closed, and when I try to resume by opening the lid, the
  laptop is unresponsive to any input, the screen stays black nothing
  happens until I shut the machine down by holding the power key.

  I have recently tried to switch to the mainline kernel (3.19 stable),
  and couldn't reproduce this issue after about 20 suspend/resume
  (before the switch I could resume once every two tries at best), but
  unfortunately this particular release seemed to make my laptop
  overheat and I'm generally not too confortable running something else
  than the default Ubuntu Kernel so I switched back to
  3.16.0-30-generic.

  I'm not the most knowledgeable Ubuntu user but if more information is
  need I could try to provide it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elmagio2503 F pulseaudio
   /dev/snd/controlC0:  elmagio2503 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb 22 16:38:23 2015
  HibernationDevice: RESUME=UUID=d088c44e-dfc5-4708-9624-fac5ea539328
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 03eb:8a0c Atmel Corp. 
   Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=022477ea-14c8-4b51-8546-fa0fa2c6084f ro quiet acpi_osi= quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-30-generic N/A
   linux-backports-modules-3.16.0-30-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.204:bd09/11/2013:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

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

** Description changed:

  [incorrect data type in rds_sysctl_rds_table]
  
- Break-Fix: - db27ebb111e9f69efece08e4cb6a34ff980f8896
+ Break-Fix: 3e5048495c8569bfdd552750e0315973c61e7c93
+ db27ebb111e9f69efece08e4cb6a34ff980f8896

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

[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

2015-02-25 Thread Kaare Baastrup

hw3.0 will not work, I installed Linux kernel 4.0rc1 and in dmesg I can see it 
asking for hw2.1 :-(
also talked to the ath10k devs...

at irc.freenode.net #ath10k

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1424394] Re: Suspend/Resume does not fully work on 14.10

2015-02-25 Thread Christopher M. Penalver

Lepaffe Philippe, could you please test the latest upstream kernel
available from the very top line at the top of the page (the release
names are irrelevant for testing, and please do not test the daily
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will
allow additional upstream developers to examine the issue.

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

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

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

Thank you for your understanding.

** Tags removed: bios-outdated-209
** Tags added: latest-bios-209

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

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

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

Title:
  Suspend/Resume does not fully work on 14.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using an Asus Zenbook UX301LA and it often doesn't suspend
  properly on 14.10.

  When the bug occurs, the fans keep going faintly even after the lid
  has been closed, and when I try to resume by opening the lid, the
  laptop is unresponsive to any input, the screen stays black nothing
  happens until I shut the machine down by holding the power key.

  I have recently tried to switch to the mainline kernel (3.19 stable),
  and couldn't reproduce this issue after about 20 suspend/resume
  (before the switch I could resume once every two tries at best), but
  unfortunately this particular release seemed to make my laptop
  overheat and I'm generally not too confortable running something else
  than the default Ubuntu Kernel so I switched back to
  3.16.0-30-generic.

  I'm not the most knowledgeable Ubuntu user but if more information is
  need I could try to provide it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elmagio2503 F pulseaudio
   /dev/snd/controlC0:  elmagio2503 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb 22 16:38:23 2015
  HibernationDevice: RESUME=UUID=d088c44e-dfc5-4708-9624-fac5ea539328
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 03eb:8a0c Atmel Corp. 
   Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=022477ea-14c8-4b51-8546-fa0fa2c6084f ro quiet acpi_osi= quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-30-generic N/A
   linux-backports-modules-3.16.0-30-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.204:bd09/11/2013:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1369103] Re: brightness keys don't work after resume from hibernate

2015-02-25 Thread Christopher M. Penalver

Denis Prost, thank you for reporting this and helping make Ubuntu
better. Could you please test the latest upstream kernel available from
the very top line at the top of the page (the release names are
irrelevant for testing, and please do not test the daily folder)
following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional upstream developers to examine the issue.

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

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

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

Thank you for your understanding.

** Tags added: latest-bios-3.00

** Tags added: utopic

** Description changed:

- This is an hibernate specific problem. After resume from suspend to ram, 
brightness keys do work.
- So I guess this is a different problem than issue 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778.
- (I tried the different solutions described in this bug comments, such as 
modifying /etc/default/grub default command line, adding a script in 
/etc/pm/sleep.d, creating a special xorg.conf file, none worked).
- My computer is a Toshiba Tecra A10-11T laptop.
+ This is an hibernate specific problem.
+ 
+ WORKAROUND:  After resume from suspend to ram, brightness keys do work.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic i686
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep 13 16:47:21 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
-Subsystem: Toshiba America Info Systems Device [1179:0004]
-Subsystem: Toshiba America Info Systems Device [1179:0004]
+  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
+    Subsystem: Toshiba America Info Systems Device [1179:0004]
+    Subsystem: Toshiba America Info Systems Device [1179:0004]
  InstallationDate: Installed on 2014-06-20 (85 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: TOSHIBA TECRA A10
  PccardctlIdent:
-  Socket 0:
-no product info available
+  Socket 0:
+    no product info available
  PccardctlStatus:
-  Socket 0:
-no card
+  Socket 0:
+    no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=4854df34-2476-44dc-a6e1-0a69ef18a7ff ro quiet splash resume=/dev/sda7 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.00
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.00:bd09/08/2009:svnTOSHIBA:pnTECRAA10:pvrPTSB1E-01T009FR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: TECRA A10
  dmi.product.version: PTSB1E-01T009FR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1

[Kernel-packages] [Bug 1425803] Re: Driver problem with USB chipset VIA VL812-B2

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

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

Title:
Driver problem with USB chipset VIA VL812-B2

Status in linux package in Ubuntu:
Confirmed

Bug description:
Presuming the system info you need is in the automatically generated
collection from ubuntu-bug. Ubuntu 14.10, fully updated. Kernel
3.16.0-31-generic.

The problem described also exists in earlier kernels although I cannot
say when it first appeared.

I have a HooToo HT-UH005 4-Port USB 3.0 hub (VIA VL812-B2 chipset) .
I'm using it with a HP Pavilion 17-e049wm laptop. This computer has
two USB 3.0 ports.

When the computer is quiescent the CPU consumed is normally 0% to 1%.
That's the same whether there are USB 2.0 or 3.0 devices plugged into
its onboard USB 3.0 ports, or not.

As soon as I plug the HT-UH005 hub into one of those USB 3.0 ports, a
system process khubd appears and it takes about 7% of CPU. Also,
several kworker and ksoftirqd threads appear which between them
consume another 18% of CPU, for a total of 25% CPU load. That's just
because the HT-UH005 was plugged in. No peripherals attached to the
HT-UH005.

Stranger still, when I unplug the HT-UH005 the khubd, kworker, and
ksoftirqd threads *continue* to consume 25% CPU. That's with the HT-
UH005 disconnected after it was previously connected. This goes on
indefinitely. The only way I can get things back to normal is to
reboot or to manually stop and restart (unbind and then bind) the
xhci_hcd driver that's servicing the internal hub that runs the
computer's two USB 3.0 ports.

The listing from dmesg shows no apparent problems when the HT-UH005 is
connected or disconnected. Listing from lsusb shows the HT-UH005
successfully connected to a port on the internal USB 3.0 hub using
driver xhci_hcd.

This could be caused by some sort of incompatibility between the AMD
internal hub and the VIA external hub. But, that the condition
persists after the HT- UH005 is disconnected suggests it is almost
surely a linux driver problem.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-31-generic 3.16.0-31.41
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: warren 5539 F pulseaudio
/dev/snd/controlC0: warren 5539 F pulseaudio
CurrentDesktop: Unity
Date: Wed Feb 25 22:12:53 2015
HibernationDevice: RESUME=UUID=d6ce9a82-d272-4efa-bfe4-e13c883b2418
InstallationDate: Installed on 2012-05-23 (1008 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic
root=UUID=515bfe03-1a57-4762-9cc1-6896e081c4c5 ro quiet splash rootfstype=ext4
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.16.0-31-generic N/A
linux-backports-modules-3.16.0-31-generic N/A
linux-firmware 1.138.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/04/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1984
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 01.13
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.31:bd12/04/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr088013305B1620100:rvnHewlett-Packard:rn1984:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 17 Notebook PC
dmi.product.version: 088013305B1620100
dmi.sys.vendor: Hewlett-Packard

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

[Kernel-packages] [Bug 1424676] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)]

2015-02-25 Thread Ubuntu Foundations Team Bug Bot

The attachment 0017-add-support-for-Linux-4.0.patch seems to be a
patch.  If it isn't, please remove the patch flag from the attachment,
remove the patch tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first
  use in this function)]

Status in bcmwl package in Ubuntu:
  New

Bug description:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.0.0-04rc1-generic
  Date: Mon Feb 23 18:14:07 2015
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20:
 error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)
  InstallationDate: Installed on 2014-11-22 (93 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141121)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu2
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1424394] Re: Suspend/Resume does not fully work on 14.10

2015-02-25 Thread Lepaffe Philippe

The latest BIOS hasn't fixed it after all.

The bug seems to appear randomly, and it just happened to not occur for
the 15 times I suspended-resumed after the BIOS upgrade, but it has
since reappeared at the same frequency as before. It does seem to occur
more frequently after long sessions of usage without interruption.

It's still the exact same symptoms.

The output of sudo dmidecode -s bios-version  sudo dmidecode -s bios-
release-date is:

UX301LAA.209
05/08/2014

I have also updated to the latest Ubuntu kernel, 3.16.0-31-generic, with
the same results. I will try a full day on a later version of the Linux
kernel (3.18.6 or 3.19) tomorrow.

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

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

Title:
  Suspend/Resume does not fully work on 14.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using an Asus Zenbook UX301LA and it often doesn't suspend
  properly on 14.10.

  When the bug occurs, the fans keep going faintly even after the lid
  has been closed, and when I try to resume by opening the lid, the
  laptop is unresponsive to any input, the screen stays black nothing
  happens until I shut the machine down by holding the power key.

  I have recently tried to switch to the mainline kernel (3.19 stable),
  and couldn't reproduce this issue after about 20 suspend/resume
  (before the switch I could resume once every two tries at best), but
  unfortunately this particular release seemed to make my laptop
  overheat and I'm generally not too confortable running something else
  than the default Ubuntu Kernel so I switched back to
  3.16.0-30-generic.

  I'm not the most knowledgeable Ubuntu user but if more information is
  need I could try to provide it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elmagio2503 F pulseaudio
   /dev/snd/controlC0:  elmagio2503 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb 22 16:38:23 2015
  HibernationDevice: RESUME=UUID=d088c44e-dfc5-4708-9624-fac5ea539328
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 03eb:8a0c Atmel Corp. 
   Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=022477ea-14c8-4b51-8546-fa0fa2c6084f ro quiet acpi_osi= quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-30-generic N/A
   linux-backports-modules-3.16.0-30-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.204:bd09/11/2013:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1065840] Re: Suspend wakes right back up

2015-02-25 Thread Alexander

Hello dear Ubuntu users who suffer from this annoying bug.

I can't stay away from it since I use day by day my PC with Ubuntu 14 .04 LTS 
installed on it.
My config is based on the Asus Striker II Extreme MB which is concerned 
(Nvidia MCP).

So, the workaround is VERY SIMPLE:
http://sethdepot.org/site/DebianLinux

Can be automated with the following udev rule, put to the file 
/etc/udev/rules.d/86-async-scsi-disable.rules
# Workaround for broken/slow suspend by disabling async ata/scsi targets 
# https://sethdepot.org/site/DebianLinux 
ACTION==add, SUBSYSTEM==scsi, ENV{DEVTYPE}==scsi_target, 
ATTR{power/async}=disabled 


Thank you and good luck.

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

Title:
  Suspend wakes right back up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  in xubuntu 12.10, attempting to suspend causes the machine to attempt to 
suspend, but the fans never go off and after about 30 seconds, the screen comes 
back on:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065840/+attachment/3760398/+files/log

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

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

[Kernel-packages] [Bug 1369103] [NEW] [Toshiba Tecra A10-11T] brightness keys don't work after resume from hibernate

You have been subscribed to a public bug:

This is an hibernate specific problem.

WORKAROUND:  After resume from suspend to ram, brightness keys do work.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Sep 13 16:47:21 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Device [1179:0004]
   Subsystem: Toshiba America Info Systems Device [1179:0004]
InstallationDate: Installed on 2014-06-20 (85 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
MachineType: TOSHIBA TECRA A10
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=4854df34-2476-44dc-a6e1-0a69ef18a7ff ro quiet splash resume=/dev/sda7 
acpi_backlight=vendor vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/08/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 3.00
dmi.board.asset.tag: 00
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.00:bd09/08/2009:svnTOSHIBA:pnTECRAA10:pvrPTSB1E-01T009FR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: TECRA A10
dmi.product.version: PTSB1E-01T009FR
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sat Sep 13 16:11:20 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.15.1-0ubuntu2.1

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


** Tags: apport-bug compiz-0.9 i386 latest-bios-3.00 trusty ubuntu utopic
-- 
[Toshiba Tecra A10-11T] brightness keys don't work after resume from hibernate
https://bugs.launchpad.net/bugs/1369103
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1424293] Re: BYD trackpad detected as PS/2 mouse

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

** Changed in: linux-lts-utopic (Ubuntu)
   Status: New = Confirmed

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

Title:
  BYD trackpad detected as PS/2 mouse

Status in linux-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  Hi, The exact device is this: 
http://bydit.com/doce/products/microelectronics/2474.html
  Let me know if there is any further information you need that could help.

  Expected to be able to use as touchpad with two finger
  vertical/horizontal scrolling. Currently only able to use plainly.

  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14 UTC
  2015 x86_64 x86_64 x86_64 GNU/Linux

  Output of cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name=Lid Switch
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name=Power Button
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name=Sleep Button
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name=Power Button
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
  U: Uniq=
  H: Handlers=kbd event3
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name=AT Translated Set 2 keyboard
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input4
  U: Uniq=
  H: Handlers=sysrq kbd event4
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name=Video Bus
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
  U: Uniq=
  H: Handlers=kbd event5
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=058f Product=3821 Version=6025
  N: Name=USB 2.0 Camera 
  P: Phys=usb-:00:14.0-5/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-5/2-5:1.0/input/input9
  U: Uniq=
  H: Handlers=kbd event6
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name=HDA Intel HDMI HDMI/DP,pcm=3
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input10
  U: Uniq=
  H: Handlers=event7
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name=HDA Intel PCH Mic
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input11
  U: Uniq=
  H: Handlers=event8
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name=HDA Intel PCH Headphone
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input12
  U: Uniq=
  H: Handlers=event9
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus=0011 Vendor=0002 Product=0005 Version=
  N: Name=ImPS/2 Generic Wheel Mouse
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input7
  U: Uniq=
  H: Handlers=mouse0 event10
  B: PROP=0
  B: EV=7
  B: KEY=7 0 0 0 0
  B: REL=103

  Output of xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  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)]
  ↳ USB 2.0 Camera  id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]

  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

[Kernel-packages] [Bug 1360887] Re: ERROR @wl_cfg80211_get_tx_power : error (-1)

2015-02-25 Thread GuyS

I'll add my voice to this bug report as well. A MacBook (2nd gn white
cover model) with latest Kubuntu (Linux jstalnak-MacBook
3.18.3-031803-generic #201501161810 SMP Fri Jan 16 18:12:22 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux). This issue exists with all current
kernels (3.16.x) and with kernels 3.18.3-031803 and 3.19.0-031900 both
with the latest bwmc kernel source. Without the bwmc kernel source the
enet/wireless is dead. With the bwmc kernel source in 3.18.3 all works,
but the log entries continue. With kernel 3.19.0 networking works, but
sound is dead, and log entries continue. Using one of the commandline
ttys is impossible, as the error output interferes with entering
passwords at the login prompts.

The frequency is about an entry per second in the kern.log and
syslog.log. They begin at dmesg time point 150+ after boot concludes, so
quite quickly after start up.

dmesg
[  100.532832] nouveau W[PCE0][:02:00.0] disabled, PCE0=1 to enable
[  101.180152] nouveau W[PCE0][:02:00.0] disabled, PCE0=1 to enable
[  157.623413] ERROR @wl_dev_intvar_get : error (-1)
[  157.623432] ERROR @wl_cfg80211_get_tx_power : error (-1)
/dmesg

My present kern.log has 113,000+ wl_cfg80211 entries. Which also makes
using these logs for any purpose pragmatically impossible; given that
the wl_dev and wl_cfg occur in pairs, that's 226,000 lines of utterly
useless data.

How can I help?

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

Title:
  ERROR @wl_cfg80211_get_tx_power : error (-1)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.1 LTS
  Release:14.04
  Ubuntu 3.13.0-34.60-generic 3.13.11.4

  
  Packages:
  linux-headers-3.13.0-34  3.13.0-34.60
  linux-headers-3.13.0-34-generic  3.13.0-34.60
  linux-image-3.13.0-34-generic  3.13.0-34.60
  linux-image-extra-3.13.0-34-generic  3.13.0-34.60
  linux-libc-dev:amd64  3.13.0-34.60
  bcmwl-kernel-source  6.30.223.141+bdcom-0ubuntu2

  Error flooding syslog and dmesg:

  [  849.335833] ERROR @wl_dev_intvar_get : error (-1)
  [  849.335837] ERROR @wl_cfg80211_get_tx_power : error (-1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-34-generic 3.13.0-34.60
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  waver  3036 F pulseaudio
   /dev/snd/controlC0:  waver  3036 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Aug 24 21:08:12 2014
  HibernationDevice: RESUME=UUID=8c728597-f27b-4e83-a813-c25f6b076b7d
  InstallationDate: Installed on 2012-03-01 (906 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011)
  MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-34-generic 
root=/dev/mapper/jupiter-root ro quiet splash nomodeset ipv6.disable=1 
acpi_enforce_resources=lax crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-34-generic N/A
   linux-backports-modules-3.13.0-34-generic  N/A
   linux-firmware 1.127.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8a
  dmi.board.name: X58A-UD3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8a:bd05/16/2011:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: X58A-UD3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1404428] Re: System does not resume after suspend

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  System does not resume after suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  In linux-image-3.13.0-41 and -43, my system goes to sleep when the lid
  is closed, but does not resume when the lid is opened.  It's probably
  hardware specific (MacBook Pro running Trusty/14.04), but I saw that
  my hardware data was sent with this report.

  I noticed the problem in 3.13.0-43 and installed linux-images backward
  until I found one that does not suffer from this problem.
  Suspend/resume works in 3.13.0-40 and previous versions and does not
  work in 3.13.0-41 and later versions, reproducibly (I rebooted with
  different kernel versions several times to be sure).  Something was
  introduced in this version that breaks suspend/resume.

  For now, I'm using 3.13.0-40, but I'm hoping this gets resolved so
  that I can keep up to date with kernel versions again.  (Thanks!)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-41-generic 3.13.0-41.70
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pivarski   2310 F pulseaudio
   /dev/snd/controlC0:  pivarski   2310 F pulseaudio
  Date: Fri Dec 19 19:43:31 2014
  HibernationDevice: RESUME=UUID=c3b7c7b4-008d-4753-b205-63ab65db36e7
  InstallationDate: Installed on 2014-09-27 (83 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  MachineType: Apple Inc. MacBookPro6,2
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=e4ed6837-c7cd-42bf-8e63-e213f9b4681c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.127.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/11
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP61.88Z.0057.B0F.1112091028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22586C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22586C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B0F.1112091028:bd12/09/11:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
  dmi.product.name: MacBookPro6,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1404005] Re: backlight problem ubuntu 14-04

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  backlight problem ubuntu 14-04

Status in linux package in Ubuntu:
  Expired

Bug description:
  unless you decrease the value of the brighness, the screen stays at maximum 
brightness.
  I do not like to type all kind of unsure command line code from which my 
ubuntu crashes, so i report it this way.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-39-generic 3.13.0-39.66
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kees   2136 F pulseaudio
   /dev/snd/controlC0:  kees   2136 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 18 20:43:18 2014
  HibernationDevice: RESUME=UUID=f68b02a8-1195-4854-b575-f030bc5179cc
  InstallationDate: Installed on 2014-09-09 (100 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic 
root=UUID=b2358b56-bfb8-4787-b341-8dd2789fbe7b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-39-generic N/A
   linux-backports-modules-3.13.0-39-generic  N/A
   linux-firmware 1.127.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.43
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.43:bd10/08/2013:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1009C12:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1009C12
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1308152] Re: Cant boot from kernel 3.13.0.24 after upgrade to ubuntu 14.04 LTS but able to boot with Kernel 3.11.0.20

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Cant boot from kernel 3.13.0.24 after upgrade to ubuntu 14.04 LTS but
  able to boot with Kernel 3.11.0.20

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi,
  Today i have upgraded my PC from Ubuntu 13.10 to Ubuntu 14.04 LTS beta but 
after the Upgrade i am unable to boot with Linux 3.13.0-24-generic
  and i am getting this error Serious errors were found while checking the 
disk drive for Press I to ignore S to skip mount M to Manual intervention
  But i am able to Boot with the Old Linux Kernel 3.11.0-20-generic.

  I tried to do the following after checking the fourm
  fsck /dev/sda1
  fsck -Aa
  but it returned that file system is clean

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic i686
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Apr 15 22:06:55 2014
  InstallationDate: Installed on 2013-11-23 (143 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release i386 
(20130213)
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-04-15 (0 days ago)

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

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

[Kernel-packages] [Bug 1402172] Re: kernel 3.16.0-28-generic breaks Radeon HD 6310

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  kernel 3.16.0-28-generic breaks Radeon HD 6310

Status in linux package in Ubuntu:
  Expired

Bug description:
  When applying the updates on my Ubuntu Utopic installation I received the new 
3.16.0-28 kernel.
  The computer had no problems with the Utopic kernels before ( up to 
3.16.0-26), but now it suddenly won't give any output (via HDMI) when booting. 
I don't get X, I don't get a splah and I can't switch with ctrl+alt+fX to one 
of the terminals.

  When booting with the older kernels or the latest (3.18.0) kernel from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/ no problem appears. I
  also reinstalled the 3.16.0-28 kernel image and reran update-
  initramfs, but the problem stays. So something explicitly in this
  kernel is creating this issue.

  
  Below I paste the relevant messages i found in the dmesg/syslog:

  Dec 11 21:49:14 tolnedra kernel: [  240.144267] INFO: task kworker/0:0:4 
blocked for more than 120 seconds.
  Dec 11 21:49:14 tolnedra kernel: [  240.144419]   Not tainted 
3.16.0-28-generic #37-Ubuntu
  Dec 11 21:49:14 tolnedra kernel: [  240.144526] echo 0  
/proc/sys/kernel/hung_task_timeout_secs disables this message.
  Dec 11 21:49:14 tolnedra kernel: [  240.144677] kworker/0:0 D 
88014ec13840 0 4  2 0x
  Dec 11 21:49:14 tolnedra kernel: [  240.144889] Workqueue: events 
output_poll_execute [drm_kms_helper]
  Dec 11 21:49:14 tolnedra kernel: [  240.145011]  88014915bd40 
0046 8801490c9e90 00013840
  Dec 11 21:49:14 tolnedra kernel: [  240.145162]  88014915bfd8 
00013840 8801490c9e90 88014732ca08
  Dec 11 21:49:14 tolnedra kernel: [  240.145313]  88014732ca0c 
8801490c9e90  88014732ca10
  Dec 11 21:49:14 tolnedra kernel: [  240.145464] Call Trace:
  Dec 11 21:49:14 tolnedra kernel: [  240.145529]  [81785589] 
schedule_preempt_disabled+0x29/0x70
  Dec 11 21:49:14 tolnedra kernel: [  240.145658]  [81787b25] 
__mutex_lock_slowpath+0xd5/0x1f0
  Dec 11 21:49:14 tolnedra kernel: [  240.145782]  [81787c5f] 
mutex_lock+0x1f/0x30
  Dec 11 21:49:14 tolnedra kernel: [  240.154118]  [c044955b] 
output_poll_execute+0x4b/0x180 [drm_kms_helper]
  Dec 11 21:49:14 tolnedra kernel: [  240.162414]  [8108da32] 
process_one_work+0x182/0x4e0
  Dec 11 21:49:14 tolnedra kernel: [  240.170642]  [8108ddfb] 
worker_thread+0x6b/0x6a0
  Dec 11 21:49:14 tolnedra kernel: [  240.178795]  [8108dd90] ? 
process_one_work+0x4e0/0x4e0
  Dec 11 21:49:14 tolnedra kernel: [  240.186899]  [81094c6b] 
kthread+0xdb/0x100
  Dec 11 21:49:14 tolnedra kernel: [  240.194991]  [81094b90] ? 
kthread_create_on_node+0x1c0/0x1c0
  Dec 11 21:49:14 tolnedra kernel: [  240.203060]  [81789dfc] 
ret_from_fork+0x7c/0xb0
  Dec 11 21:49:14 tolnedra kernel: [  240.211078]  [81094b90] ? 
kthread_create_on_node+0x1c0/0x1c0
  Dec 11 21:49:14 tolnedra kernel: [  240.219183] INFO: task Xorg:2306 blocked 
for more than 120 seconds.
  Dec 11 21:49:14 tolnedra kernel: [  240.227291]   Not tainted 
3.16.0-28-generic #37-Ubuntu
  Dec 11 21:49:14 tolnedra kernel: [  240.235115] echo 0  
/proc/sys/kernel/hung_task_timeout_secs disables this message.
  Dec 11 21:49:14 tolnedra kernel: [  240.242738] XorgD 
88014ec13840 0  2306   2234 0x0040
  Dec 11 21:49:14 tolnedra kernel: [  240.250129]  8801414ab380 
0086 88008a301460 00013840
  Dec 11 21:49:14 tolnedra kernel: [  240.257257]  8801414abfd8 
00013840 88008a301460 88014732ca08
  Dec 11 21:49:14 tolnedra kernel: [  240.264153]  88014732ca0c 
88008a301460  88014732ca10
  Dec 11 21:49:14 tolnedra kernel: [  240.145464] Call Trace:
  Dec 11 21:49:14 tolnedra kernel: [  240.145529]  [81785589] 
schedule_preempt_disabled+0x29/0x70
  Dec 11 21:49:14 tolnedra kernel: [  240.145658]  [81787b25] 
__mutex_lock_slowpath+0xd5/0x1f0
  Dec 11 21:49:14 tolnedra kernel: [  240.145782]  [81787c5f] 
mutex_lock+0x1f/0x30
  Dec 11 21:49:14 tolnedra kernel: [  240.154118]  [c044955b] 
output_poll_execute+0x4b/0x180 [drm_kms_helper]
  Dec 11 21:49:14 tolnedra kernel: [  240.162414]  [8108da32] 
process_one_work+0x182/0x4e0
  Dec 11 21:49:14 tolnedra kernel: [  240.170642]  [8108ddfb] 
worker_thread+0x6b/0x6a0
  Dec 11 21:49:14 tolnedra kernel: [  240.178795]  [8108dd90] ? 
process_one_work+0x4e0/0x4e0
  Dec 11 21:49:14 tolnedra kernel: [  240.186899]  [81094c6b] 
kthread+0xdb/0x100
  Dec 11 21:49:14 tolnedra kernel: [  240.194991]

[Kernel-packages] [Bug 1403760] Re: Dell E7440 Cursor Jumping problem

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Dell E7440  Cursor Jumping problem

Status in linux package in Ubuntu:
  Expired

Bug description:
  Cursor jumping problem in Ubuntu 14.04 while using touch pad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-37-generic 3.13.0-37.64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sunil-0119   2350 F pulseaudio
sysadmin   8535 F pulseaudio
   /dev/snd/controlC0:  sunil-0119   2350 F pulseaudio
sysadmin   8535 F pulseaudio
  Date: Thu Dec 18 12:57:30 2014
  HibernationDevice: RESUME=UUID=71cf40ea-98e5-4ca2-91a3-dcc6fdffc166
  InstallationDate: Installed on 2014-10-13 (65 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E7440
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=857e9910-c4c3-4fc2-879a-396753004114 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-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 07F3F4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/28/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1402832] Re: No wifi after suspend/resume

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  No wifi after suspend/resume

Status in linux package in Ubuntu:
  Expired

Bug description:
  Similar to Bug #1154949 but occuring on release 14.04 LTS, after update from 
13.04
  Wireless connection will not resume after laptop has been reawakened from 
suspend mode on main Ubuntu start menu or closing laptop lid. 
  I have looked through and found several reports of a similar issue in earlier 
versions of Ubuntu, and believe it was patched?

  I have attempted using graphical menu neither switch operates - shows the 
airplane mode switch in ON and wireless switch in OFF.
  The laptop external wireless switch remains in ON position but no longer 
works.
  I have tried RFKILL commands - no effect.
  I have tried NMCLI  commands - no effect.

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  Version: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  apt-cache policy pkgname - N: Unable to locate package pkgname
  Ubuntu Software Centre 13.10

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-43-generic 3.13.0-43.72
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2288 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Dec 15 20:36:24 2014
  HibernationDevice: RESUME=UUID=2d481998-5d58-4df2-aa9b-6d36b52727dc
  InstallationDate: Installed on 2011-03-15 (1371 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MachineType: DIXONSXP DIXONSXP
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=1337a3da-0a56-4668-8a7e-6d6e0242c5fe ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-43-generic N/A
   linux-backports-modules-3.13.0-43-generic  N/A
   linux-firmware 1.127.10
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-12-13 (2 days ago)
  dmi.bios.vendor: DIXONSXP
  dmi.bios.version: 1.06.04.DIX
  dmi.board.name: DIXONSXP
  dmi.board.vendor: DIXONSXP
  dmi.chassis.type: 10
  dmi.chassis.vendor: DIXONSXP
  dmi.modalias: 
dmi:bvnDIXONSXP:bvr1.06.04.DIX:bd:svnDIXONSXP:pnDIXONSXP:pvr:rvnDIXONSXP:rnDIXONSXP:rvr:cvnDIXONSXP:ct10:cvr:
  dmi.product.name: DIXONSXP
  dmi.sys.vendor: DIXONSXP

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

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

[Kernel-packages] [Bug 1425803] [NEW] Driver problem with USB chipset VIA VL812-B2

2015-02-25 Thread Warren

Public bug reported:

Presuming the system info you need is in the automatically generated
collection from ubuntu-bug. Ubuntu 14.10, fully updated. Kernel
3.16.0-31-generic.

The problem described also exists in earlier kernels although I cannot
say when it first appeared.

I have a HooToo HT-UH005 4-Port USB 3.0 hub (VIA VL812-B2 chipset) . I'm
using it with a HP Pavilion 17-e049wm laptop. This computer has two USB
3.0 ports.

When the computer is quiescent the CPU consumed is normally 0% to 1%.
That's the same whether there are USB 2.0 or 3.0 devices plugged into
its onboard USB 3.0 ports, or not.

As soon as I plug the HT-UH005 hub into one of those USB 3.0 ports, a
system process khubd appears and it takes about 7% of CPU. Also, several
kworker and ksoftirqd threads appear which between them consume
another 18% of CPU, for a total of 25% CPU load. That's just because the
HT-UH005 was plugged in. No peripherals attached to the HT-UH005.

Stranger still, when I unplug the HT-UH005 the khubd, kworker, and
ksoftirqd threads *continue* to consume 25% CPU. That's with the HT-
UH005 disconnected after it was previously connected. This goes on
indefinitely. The only way I can get things back to normal is to reboot
or to manually stop and restart (unbind and then bind) the xhci_hcd
driver that's servicing the internal hub that runs the computer's two
USB 3.0 ports.

The listing from dmesg shows no apparent problems when the HT-UH005 is
connected or disconnected. Listing from lsusb shows the HT-UH005
successfully connected to a port on the internal USB 3.0 hub using
driver xhci_hcd.

This could be caused by some sort of incompatibility between the AMD
internal hub and the VIA external hub. But, that the condition persists
after the HT- UH005 is disconnected suggests it is almost surely a linux
driver problem.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-31-generic 3.16.0-31.41
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  warren 5539 F pulseaudio
 /dev/snd/controlC0:  warren 5539 F pulseaudio
CurrentDesktop: Unity
Date: Wed Feb 25 22:12:53 2015
HibernationDevice: RESUME=UUID=d6ce9a82-d272-4efa-bfe4-e13c883b2418
InstallationDate: Installed on 2012-05-23 (1008 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=515bfe03-1a57-4762-9cc1-6896e081c4c5 ro quiet splash rootfstype=ext4 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-31-generic N/A
 linux-backports-modules-3.16.0-31-generic  N/A
 linux-firmware 1.138.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/04/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1984
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 01.13
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd12/04/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr088013305B1620100:rvnHewlett-Packard:rn1984:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 17 Notebook PC
dmi.product.version: 088013305B1620100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: 3.0 amd64 apport-bug hub usb utopic

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

Title:
  Driver problem with USB chipset VIA VL812-B2

Status in linux package in Ubuntu:
  New

Bug description:
  Presuming the system info you need is in the automatically generated
  collection from ubuntu-bug. Ubuntu 14.10, fully updated. Kernel
  3.16.0-31-generic.

  The problem described also exists in earlier kernels although I cannot
  say when it first appeared.

  I have a HooToo HT-UH005 4-Port USB 3.0 hub (VIA VL812-B2 chipset) .
  I'm using it with a HP Pavilion 17-e049wm laptop. This computer has
  two USB 3.0 ports.

  When the computer is quiescent the CPU consumed is normally 0% to 1%.
  That's the same whether there are USB 2.0 or 3.0 devices plugged into
  its onboard USB 3.0 ports, or not.

  As soon as I plug the HT-UH005 hub into one of those USB 3.0 ports, a
  system process khubd appears and it takes about 7% of CPU. Also,
  several kworker and ksoftirqd threads appear which between them
  consume another 18% of CPU, for a total of 25% CPU load. That's just
  because the HT-UH005 was plugged in. No peripherals attached to the

[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE

2015-02-25 Thread Pavel Malyshev

First of all, Trusty kernel worked somehow differently. It didn't
complain for /dev/log.

Yes, my /etc/apparmor.d/usr.sbin.rsyslogd does not have 'r' for /dev/log:
/dev/log  wl,

So does it mean that the rsyslog profile has to be patched for trusty?
Or at least some kind of Utopic HWE release notes has to be updated?

I've updated /etc/apparmor.d/local/usr.sbin.rsyslogd and can confirm
that message is gone with Utopic kernel.

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

Title:
  Apparmor uses rsyslogd profile for different processes - utopic HWE

Status in apparmor package in Ubuntu:
  New
Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  Hi.

  I've noticed that apparmor loads /usr/sbin/rsyslogd profile for
  completely unrelated processes:

  Feb 25 08:36:19 emma kernel: [  134.796218] audit: type=1400 
audit(1424842579.429:245): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 25 08:36:23 emma kernel: [  139.330989] audit: type=1400 
audit(1424842583.965:246): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 25 08:35:42 emma kernel: [   97.912402] audit: type=1400 
audit(1424842542.565:241): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie 
requested_mask=r denied_mask=r fsuid=103 ouid=0
  Feb 25 08:34:43 emma kernel: [   38.867998] audit: type=1400 
audit(1424842483.546:226): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd 
requested_mask=r denied_mask=r fsuid=0 ouid=0

  
  I'm not sure how apparmor decides which profile to use for which task, but is 
shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc.

  
  I'm running:
  # lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  # dpkg -l | grep apparmor
  ii  apparmor2.8.95~2430-0ubuntu5.1   
amd64User-space parser utility for AppArmor
  ii  apparmor-profiles   2.8.95~2430-0ubuntu5.1   
all  Profiles for AppArmor Security policies
  ii  apparmor-utils  2.8.95~2430-0ubuntu5.1   
amd64Utilities for controlling AppArmor
  ii  libapparmor-perl2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Perl bindings
  ii  libapparmor1:amd64  2.8.95~2430-0ubuntu5.1   
amd64changehat AppArmor library
  ii  python3-apparmor2.8.95~2430-0ubuntu5.1   
amd64AppArmor Python3 utility library
  ii  python3-libapparmor 2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Python3 bindings

  # uname -a
  Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang

2015-02-25 Thread Øyvind Stegard

Same issue occured on Ubuntu 14.04 LTS after upgrading kernel to 3.16,
and Xorg (LTS hardware enablement program).  Screen was frozen, but I
was able to recover by switching to a VT and restarting X (switching
eventually worked after a long delay). Never any problems of this sort
with the 3.13-kernel. (Intel HD 4000 Ivy Bridge).

[79486.195054] WARNING: CPU: 0 PID: 1751 at /build/buildd/linux-lts-
utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324
intel_crtc_wait_for_pending_flips+0x171/0x180 [i915]()

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

Title:
  kernel messages intel_crtc_wait_for_pending_flips correlate to compiz
  hang

Status in The Linux Kernel:
  Unknown
Status in System76:
  New
Status in X.org xf86-video-intel:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown
Status in linux package in openSUSE:
  Unknown

Bug description:
  I am fairly frequently (maybe once every 2 days) seeing screen
  lockups.  The system is fine, and then screen locks up. mouse is still
  movable and even changes icon based on content under it (ie mouse over
  link changes to pointing hand).  Programs are still running (often
  this occurs during a google hangout, and the hangout, audio and mic
  seem to work fine).

  Today when this happened I had more patience and hit ctrl-alt-f1, and then 
subsequently saw that dmesg had:
  [82218.556025] [ cut here ]
  [82218.556074] WARNING: CPU: 0 PID: 8799 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 
intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]()
  [82218.556095] Modules linked in: xt_conntrack ipt_REJECT overlayfs pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter 
ip_tables x_tables rfcomm bnep binfmt_misc dm_crypt uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_core v4l2_common videodev media dm_multipath scsi_dh 
coretemp kvm_intel kvm arc4 joydev iwldvm mac80211 serio_raw btusb bluetooth 
pcmcia 6lowpan_iphc thinkpad_acpi snd_seq_midi snd_seq_midi_event nvram 
snd_hda_codec_conexant snd_hda_codec_generic r852 sm_common lpc_ich nand 
snd_rawmidi nand_ecc nand_bch snd_hda_intel bch nand_ids snd_hda_controller 
snd_hda_codec snd_hwdep mtd snd_seq iwlwifi r592 memstick snd_pcm
  [82218.556112]  yenta_socket pcmcia_rsrc pcmcia_core cfg80211 snd_seq_device 
shpchp snd_timer mei_me mei snd soundcore mac_hid parport_pc ppdev tp_smapi(OE) 
thinkpad_ec(OE) lp parport btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear 
hid_generic usbhid hid psmouse firewire_ohci ahci libahci firewire_core 
sdhci_pci sdhci crc_itu_t i915 wmi e1000e i2c_algo_bit drm_kms_helper video drm 
ptp pps_core pata_acpi [last unloaded: ipmi_msghandler]
  [82218.556114] CPU: 0 PID: 8799 Comm: kworker/0:1 Tainted: GW  OE 
3.16.0-23-generic #30-Ubuntu
  [82218.556115] Hardware name: LENOVO 7417CTO/7417CTO, BIOS 7UET94WW (3.24 ) 
10/17/2012
  [82218.556119] Workqueue: events console_callback
  [82218.556122]  0009 880016a3faf8 8177fcbc 

  [82218.556123]  880016a3fb30 8106fd8d  
880035a5a000
  [82218.556124]  880035948210 880035826800 880035826800 
880016a3fb40
  [82218.556125] Call Trace:
  [82218.556130]  [8177fcbc] dump_stack+0x45/0x56
  [82218.556133]  [8106fd8d] warn_slowpath_common+0x7d/0xa0
  [82218.556135]  [8106fe6a] warn_slowpath_null+0x1a/0x20
  [82218.556153]  [c015dffc] 
intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]
  [82218.556156]  [810b9590] ? prepare_to_wait_event+0x100/0x100
  [82218.556175]  [c0160ac3] intel_crtc_disable_planes+0x33/0x1c0 
[i915]
  [82218.556177]  [81784e5b] ? __ww_mutex_lock+0x1b/0xb0
  [82218.556196]  [c0160ca1] i9xx_crtc_disable+0x51/0x3f0 [i915]
  [82218.556220]  [c0162457] intel_crtc_update_dpms+0x67/0xa0 [i915]
  [82218.556237]  [c0166ac9] intel_connector_dpms+0x59/0x70 [i915]
  [82218.556245]  [c00c4901] drm_fb_helper_dpms.isra.5+0xc1/0x100 
[drm_kms_helper]
  [82218.556251]  [c00c4971] drm_fb_helper_blank+0x31/0x90 
[drm_kms_helper]
  [82218.556254]  [81415d47] fb_blank+0x57/0xc0
  [82218.556256]  [8140c87b] fbcon_blank+0xfb/0x300
  [82218.556258]  [8108b4a2] ? __queue_delayed_work+0x182/0x1c0
  [82218.556259]  [8108b7b9] ? try_to_grab_pending+0xa9/0x160
  [82218.556262]  [8107cbdb] ? lock_timer_base.isra.34+0x2b/0x50
  [82218.556264]  [8107dd1f] ? try_to_del_timer_sync+0x4f/0x70
  [82218.556266]

[Kernel-packages] [Bug 1418822] Re: AMD Radeon HD 8570A/8570M [1002:6663] Unable to resume from suspend with proprietary driver

2015-02-25 Thread Anthony Wong

** Changed in: hwe-next
   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/1418822

Title:
  AMD Radeon HD 8570A/8570M [1002:6663] Unable to resume from suspend
  with proprietary driver

Status in HWE Next Project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CID: 201309-14197 HP 242 G2 Notebook PC

  This is an I+A hybrid system:
  00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core 
Processor Integrated Graphics Controller [8086:0416] (rev 06)
  01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun 
PRO [Radeon HD 8570A/8570M] [1002:6663] (rev ff)

  With fglrx installed, it can't resume from suspend just like bug
  1308954

  Steps:
  1. Install 14.04.1 + update (3.13.0-45) + fglrx or fglrx-update, reboot.
  2. Suspend it.
  3. Wake it up

  Expected result:
  * Everything should works fine after S3.

  Actual result:
  * System freeze

  Note:
  With driver version 14.501 downloaded from AMD's website [1] installed.
  It will boot into low-graphic mode.
  Package that I installed:
  fglrx_14.501-0ubuntu1_amd64_UB_14.01.deb
  fglrx-amdcccle_14.501-0ubuntu1_amd64_UB_14.01.deb
  fglrx-core_14.501-0ubuntu1_amd64_UB_14.01.deb
  fglrx-dev_14.501-0ubuntu1_amd64_UB_14.01.deb

  [1] http://support.amd.com/en-us/download/desktop?os=Ubuntu%20x86%2064

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74
  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:  ubuntu 1632 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1632 F pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Fri Feb  6 00:55:53 2015
  HibernationDevice: RESUME=UUID=e4f99f18-f641-42cf-8870-1a6a8a8c741a
  InstallationDate: Installed on 2015-02-05 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP 242 G2 Notebook PC
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=a10c7f9d-8d0a-472e-a426-20b14015b1b2 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
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: B.0B
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 217B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 34.0E
  dmi.chassis.asset.tag: 738DIP105Y
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrB.0B:bd10/08/2013:svnHewlett-Packard:pnHP242G2NotebookPC:pvr099C200620100:rvnHewlett-Packard:rn217B:rvrKBCVersion34.0E:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 242 G2 Notebook PC
  dmi.product.version: 099C200620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1417363] Re: touchpad stops working after suspend/resume on XPS13 2015

2015-02-25 Thread Anthony Wong

** Changed in: hwe-next/utopic
   Status: Fix Committed = Fix Released

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

Title:
  touchpad stops working after suspend/resume on XPS13 2015

Status in HWE Next Project:
  Fix Released
Status in HWE Next utopic series:
  Fix Released
Status in HWE Next vivid series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Utopic:
  Fix Released

Bug description:
  The touchpad on XPS13 2015 would work in I2C mode with kernel 3.16+ and it 
would stop working after resume from suspend with an utopic kernel. This issue 
can be fixed by introducing two commits from upstream:
  109571c - HID: i2c-hid: call the hid driver's suspend and resume callbacks
  5b44c53 - HID: i2c-hid: Do not free buffers in i2c_hid_stop()

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

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

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

This change was made by a bot.

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

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

Title:
Driver problem with USB chipset VIA VL812-B2

Status in linux package in Ubuntu:
Confirmed

Bug description:
Presuming the system info you need is in the automatically generated
collection from ubuntu-bug. Ubuntu 14.10, fully updated. Kernel
3.16.0-31-generic.

The problem described also exists in earlier kernels although I cannot
say when it first appeared.

I have a HooToo HT-UH005 4-Port USB 3.0 hub (VIA VL812-B2 chipset) .
I'm using it with a HP Pavilion 17-e049wm laptop. This computer has
two USB 3.0 ports.

When the computer is quiescent the CPU consumed is normally 0% to 1%.
That's the same whether there are USB 2.0 or 3.0 devices plugged into
its onboard USB 3.0 ports, or not.

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

[Kernel-packages] [Bug 1396889] Re: [Lenovo ThinkPad T400] kexec reboot fails

2015-02-25 Thread MegaBrutal

Is there anything I can do to get the patch actually backported? Can I somehow 
backport it myself or something?
Even with the latest Utopic kernel which was published few days ago, I still 
don't have a kexec-able kernel.
I can imagine the Vivid release will happen earlier than I'll get a patched 
kernel in Utopic.

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

Title:
  [Lenovo ThinkPad T400] kexec reboot fails

Status in linux package in Ubuntu:
  Triaged

Bug description:
  After release upgrade to Utopic, when I reboot with kexec (simply with
  reboot command), my computer cold reboots after Starting new
  kernel (i.e. I need to get through the POST and GRUB), instead of the
  new kernel being loaded. Previously I didn't experience problems with
  Trusty.

  It matters which kernel I try to boot, while it doesn't matter what
  kernel I kexec from, and which version of kexec-tools I have.

  I can't boot 3.16.0-25, nor 3.18.0-031800rc6 from any installed
  kernels, while I can boot 3.13.0-39 from any kernels without any
  problems.

  I tried to downgrade kexec-tools from 1:2.0.7-1ubuntu2 (utopic) to
  1:2.0.6-0ubuntu2.1 (trusty), but it made no difference.

  I have a Lenovo Thinkpad T400. I didn't experience the same on my
  other machines, so I suspect some hardware-dependent issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-25-generic 3.16.0-25.33
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  megabrutal   2497 F pulseaudio
   /dev/snd/seq:timidity   1420 F timidity
  Date: Thu Nov 27 07:40:07 2014
  HibernationDevice: RESUME=UUID=3d113c6f-7cf8-477f-81e1-857aa62102c2
  InstallationDate: Installed on 2014-06-10 (169 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 6474B84
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   LANGUAGE=hu
   TERM=xterm
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic 
root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@
  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.16.0-25-generic N/A
   linux-backports-modules-3.16.0-25-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-11-11 (15 days ago)
  dmi.bios.date: 04/22/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET66WW (2.16 )
  dmi.board.name: 6474B84
  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:bvr7UET66WW(2.16):bd04/22/2009:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 6474B84
  dmi.product.version: ThinkPad T400
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1425445] Re: Regression: 3.16.0-31-generic breaks touchpad on Dell XPS13 (2015)

2015-02-25 Thread Jan Henke

N.B.: The two kernel parameters acpi_osi=!Windows 2013 and
psmouse.resetafter=0 as a temporary work around until this bug gets
fixed, the described bug happened without these parameters!

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

Title:
  Regression: 3.16.0-31-generic breaks touchpad on Dell XPS13 (2015)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today’s kernel update breaks the touchpad on the 2015 Dell XPS13. On
  3.16.0-30-generic the touchpad worked fine.

  Symptoms are that the touchpad stops responding at random times.

  A possible cause is this patch:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d1c7e29e8d276c669e8790bb8be9f505ddc4

  See also those two bug reports for a more detailed discussion of the I2C 
issues caused by the above patch and the XPS13:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416601
  https://bugzilla.redhat.com/show_bug.cgi?id=1188439

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jan2547 F pulseaudio
   /dev/snd/controlC1:  jan2547 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Feb 25 10:19:01 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-30 (25 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=e4431ecc-e85e-4e35-92af-58f455c46c2b ro kvm-intel.nested=1 
acpi_osi=!Windows 2013 psmouse.resetafter=0 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

This change was made by a bot.

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

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

Title:
  Regression: 3.16.0-31-generic breaks touchpad on Dell XPS13 (2015)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today’s kernel update breaks the touchpad on the 2015 Dell XPS13. On
  3.16.0-30-generic the touchpad worked fine.

  Symptoms are that the touchpad stops responding at random times.

  A possible cause is this patch:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d1c7e29e8d276c669e8790bb8be9f505ddc4

  See also those two bug reports for a more detailed discussion of the I2C 
issues caused by the above patch and the XPS13:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416601
  https://bugzilla.redhat.com/show_bug.cgi?id=1188439

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jan2547 F pulseaudio
   /dev/snd/controlC1:  jan2547 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Feb 25 10:19:01 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-30 (25 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=e4431ecc-e85e-4e35-92af-58f455c46c2b ro kvm-intel.nested=1 
acpi_osi=!Windows 2013 psmouse.resetafter=0 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1425288] Re: kernel NULL pointer dereference during bcache cache_set_flush call

2015-02-25 Thread Stefan Bader

James, can you please add a little more detail to the history (What was
that machine doing on the bcache device? How long was it roughly
operational before this issue happed?). Also this appears to be a meta-
data corruption that leads to some crash. That potentially now happens
on every reboot (yes or no)?

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

Title:
  kernel NULL pointer dereference during bcache cache_set_flush call

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  14.04 + HWE 3.16 kernel.

  RAID-0 (3 spindles) + bcache on SSD - ext4 filesystem

  I'm unable to access this system - this was taken from the iDRAC
  serial console.

  [4.559402] md: raid1 personality registered for level 1
  [4.568578] scsi 4:0:0:0: Direct-Access ATA  PLEXTOR PX-AG256 1.04 
PQ: 0 ANSI: 5
  [4.576976] sd 4:0:0:0: Attached scsi generic sg3 type 0
  [4.576987] sd 4:0:0:0: [sdd] 500118192 512-byte logical blocks: (256 
GB/238 GiB)
  [4.577334] md/raid1:md0: active with 3 out of 3 mirrors
  [4.577335] sd 4:0:0:0: [sdd] Write Protect is off
  [4.577363] md0: detected capacity change from 0 to 1073676288
  [4.577504] sd 4:0:0:0: [sdd] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [4.578855]  sdd: unknown partition table
  [4.579183]  md0: unknown partition table
  [4.579384] sd 4:0:0:0: [sdd] Attached SCSI disk
  [4.599312] random: nonblocking pool is initialized
  [4.668775] bcache: register_bdev() registered backing device md1
  [4.695459] bcache: error on eaa3d3fb-19b1-47a1-9184-1ac6e96c8593: 
unsupported bset version at bucket 3617, block 0, 0 keys, disabling caching
  [4.708278] bcache: register_cache() registered cache device sdd
  [4.714340] BUG: unable to handle kernel NULL pointer dereference at 
0018
  [4.722193] IP: [c01fdba2] journal_write_work+0x22/0x50 [bcache]
  [4.729083] PGD c198e6067 PUD c19fca067 PMD 0
  [4.733572] Oops:  [#1] SMP
  [4.736832] Modules linked in: bcache raid1 raid0 hid_generic e1000e 
usbhid ahci ptp psmouse hid libahci pata_acpi pps_core
  [4.748186] CPU: 23 PID: 385 Comm: kworker/23:1 Not tainted 
3.16.0-30-generic #40~14.04.1-Ubuntu
  [4.756956] Hardware name: Supermicro X8DTT-H/X8DTT-H, BIOS 2.1b   
10/28/2011
  [4.764433] Workqueue: events cache_set_flush [bcache]
  [4.769585] task: 880c1af33d20 ti: 880c1983c000 task.ti: 
880c1983c000
  [4.777056] RIP: 0010:[c01fdba2]  [c01fdba2] 
journal_write_work+0x22/0x50 [bcache]
  [4.786374] RSP: 0018:880c1983fdc8  EFLAGS: 00010246
  [4.791678] RAX:  RBX: 880c192acbf8 RCX: 
7fff
  [4.798801] RDX:  RSI: 7fff RDI: 
880c192acbb0
  [4.805935] RBP: 880c1983fdd8 R08:  R09: 
00018022
  [4.813068] R10: 81246186 R11: ea0030631e80 R12: 
880c192acbb0
  [4.820203] R13: 880c192a0ce8 R14: 880c192a0de8 R15: 
880c192a0c50
  [4.827336] FS:  () GS:880c3fd6() 
knlGS:
  [4.835422] CS:  0010 DS:  ES:  CR0: 8005003b
  [4.841159] CR2: 0018 CR3: 000c19d5e000 CR4: 
07e0
  [4.848282] Stack:
  [4.850311]  880c192acbf8 880c1d9a6098 880c1983fe10 
c0205088
  [4.857800]  880c1d99d200 880c3fd72c40 880c192a0ce8 

  [4.865253]  05c0 880c1983fe58 81089ef2 
3fd72c40
  [4.872706] Call Trace:
  [4.875185]  [c0205088] cache_set_flush+0x158/0x1c0 [bcache]
  [4.881707]  [81089ef2] process_one_work+0x182/0x450
  [4.887539]  [8108a663] worker_thread+0x123/0x5a0
  [4.893111]  [8108a540] ? rescuer_thread+0x380/0x380
  [4.898935]  [810912c2] kthread+0xd2/0xf0
  [4.903807]  [810911f0] ? kthread_create_on_node+0x1c0/0x1c0
  [4.910334]  [8176ac3c] ret_from_fork+0x7c/0xb0
  [4.915732]  [810911f0] ? kthread_create_on_node+0x1c0/0x1c0
  [4.922249] Code: fe ff ff 66 0f 1f 44 00 00 66 66 66 66 90 55 48 89 e5 41 
54 4c 8d 67 b8 53 48 89 fb 4c 89 e7 e8 95 cb 56 c1 48 8b 83 38 01 00 00 80 78 
18 00 75 10 4c 89 e7 e8 90 ca 56 c1 5b 41 5c 5d c3 0f 1f
  [4.942252] RIP  [c01fdba2] journal_write_work+0x22/0x50 [bcache]
  [4.949264]  RSP 880c1983fdc8
  [4.952749] CR2: 0018
  [4.956061] ---[ end trace c2f23bd1c3cc953e ]---

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

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

[Kernel-packages] [Bug 1425453] [NEW] [Dell Inc. Latitude E6430] suspend/resume failure [non-free: nvidia]

2015-02-25 Thread Ed Baker

Public bug reported:

Error on resume from suspend

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.18.0-13-generic 3.18.0-13.14
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic i686
NonfreeKernelModules: nvidia
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ed 3237 F pulseaudio
 /dev/snd/seq:timidity   1518 F timidity
Date: Wed Feb 25 09:34:47 2015
DuplicateSignature: suspend/resume:Dell Inc. Latitude E6430:A09
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=6051f154-4db2-4c44-ae10-778e5044d865
InstallationDate: Installed on 2014-04-17 (313 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
InterpreterPath: /usr/bin/python3.4
MachineType: Dell Inc. Latitude E6430
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic 
root=UUID=145f3f5e-fb0b-49a8-9f7d-b930a2396d8a ro quiet splash
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.18.0-13-generic N/A
 linux-backports-modules-3.18.0-13-generic  N/A
 linux-firmware 1.141
SourcePackage: linux
Title: [Dell Inc. Latitude E6430] suspend/resume failure [non-free: nvidia]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 12/13/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0H3MT5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6430
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-kerneloops i386 need-duplicate-check resume suspend vivid

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

Title:
  [Dell Inc. Latitude E6430] suspend/resume failure [non-free: nvidia]

Status in linux package in Ubuntu:
  New

Bug description:
  Error on resume from suspend

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-13-generic 3.18.0-13.14
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  NonfreeKernelModules: nvidia
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ed 3237 F pulseaudio
   /dev/snd/seq:timidity   1518 F timidity
  Date: Wed Feb 25 09:34:47 2015
  DuplicateSignature: suspend/resume:Dell Inc. Latitude E6430:A09
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=6051f154-4db2-4c44-ae10-778e5044d865
  InstallationDate: Installed on 2014-04-17 (313 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Dell Inc. Latitude E6430
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic 
root=UUID=145f3f5e-fb0b-49a8-9f7d-b930a2396d8a ro quiet splash
  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.18.0-13-generic N/A
   linux-backports-modules-3.18.0-13-generic  N/A
   linux-firmware 1.141
  SourcePackage: linux
  Title: [Dell Inc. Latitude E6430] suspend/resume failure [non-free: nvidia]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

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

This change was made by a bot.

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

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

Title:
  [Dell Inc. Latitude E6430] suspend/resume failure [non-free: nvidia]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error on resume from suspend

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-13-generic 3.18.0-13.14
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  NonfreeKernelModules: nvidia
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ed 3237 F pulseaudio
   /dev/snd/seq:timidity   1518 F timidity
  Date: Wed Feb 25 09:34:47 2015
  DuplicateSignature: suspend/resume:Dell Inc. Latitude E6430:A09
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=6051f154-4db2-4c44-ae10-778e5044d865
  InstallationDate: Installed on 2014-04-17 (313 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Dell Inc. Latitude E6430
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-13-generic 
root=UUID=145f3f5e-fb0b-49a8-9f7d-b930a2396d8a ro quiet splash
  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.18.0-13-generic N/A
   linux-backports-modules-3.18.0-13-generic  N/A
   linux-firmware 1.141
  SourcePackage: linux
  Title: [Dell Inc. Latitude E6430] suspend/resume failure [non-free: nvidia]
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1389077] Re: [HP ProBook 4530s] Intel Powerclamp is Slowing CPU

2015-02-25 Thread pcdummy

Had the same trouble, blacklisting intel_powerclamp and intel_rapl fixed
it. Thanks to @krzysdrewniak.

sudo sh -c 'cat EOF  /etc/modprobe.d/blacklist-power.conf
# See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389077
blacklist intel_powerclamp
blacklist intel_rapl
EOF'

Thanks.

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

Title:
  [HP ProBook 4530s] Intel Powerclamp is Slowing CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from KUbuntu 14.04 to 14.10. Immediately, while playing
  minecraft with my daughter, I noticed the game was running very
  slowly. Even after closing the game, my web browsing slowed to a
  crawl.

  Looking at the processes in top, I noticed there were 4 tasks called
  kidle_inject running at 50% CPU each. After spending a long time
  figuring out what caused this, I found out this is caused by the Intel
  Powerclamp driver. I never did anything to enable this, and haven't
  observed this slowdown before the upgrade.

  I found the powerclamp driver in the
  /sys/class/thermal/cooling_device5 directory:

  root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat type 
  intel_powerclamp
  root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat cur_state 
  -1
  root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat max_state 
  50

  I tried to echo 0 to cur_state, but it still reported -1 when I catted
  the value.

  There seems to be no obvious way to disable this, and this should not
  have been enabled in the first place.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bkat   2780 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Nov  3 23:16:04 2014
  HibernationDevice: RESUME=UUID=35e1d874-a3bd-4227-acab-16f3e929d993
  InstallationDate: Installed on 2012-04-22 (925 days ago)
  InstallationMedia: Kubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MachineType: Hewlett-Packard HP ProBook 4530s
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=743f1686-bfe7-4e32-911d-5371633ccec8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-11-03 (0 days ago)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SRR Ver. F.09
  dmi.board.name: 167C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 22.1A
  dmi.chassis.asset.tag: CNU1284V1X
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.09:bd05/13/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1A: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/1389077/+subscriptions

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

[Kernel-packages] [Bug 1425445] [NEW] Regression: 3.16.0-31-generic breaks touchpad on Dell XPS13 (2015)

2015-02-25 Thread Jan Henke

Public bug reported:

Today’s kernel update breaks the touchpad on the 2015 Dell XPS13. On
3.16.0-30-generic the touchpad worked fine.

Symptoms are that the touchpad stops responding at random times.

A possible cause is this patch:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d1c7e29e8d276c669e8790bb8be9f505ddc4

See also those two bug reports for a more detailed discussion of the I2C issues 
caused by the above patch and the XPS13:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416601
https://bugzilla.redhat.com/show_bug.cgi?id=1188439

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-31-generic 3.16.0-31.41
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jan2547 F pulseaudio
 /dev/snd/controlC1:  jan2547 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Feb 25 10:19:01 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-30 (25 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
MachineType: Dell Inc. XPS 13 9343
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=e4431ecc-e85e-4e35-92af-58f455c46c2b ro kvm-intel.nested=1 
acpi_osi=!Windows 2013 psmouse.resetafter=0 quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-31-generic N/A
 linux-backports-modules-3.16.0-31-generic  N/A
 linux-firmware 1.138.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/04/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: 0310JH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug utopic

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

Title:
  Regression: 3.16.0-31-generic breaks touchpad on Dell XPS13 (2015)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today’s kernel update breaks the touchpad on the 2015 Dell XPS13. On
  3.16.0-30-generic the touchpad worked fine.

  Symptoms are that the touchpad stops responding at random times.

  A possible cause is this patch:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d1c7e29e8d276c669e8790bb8be9f505ddc4

  See also those two bug reports for a more detailed discussion of the I2C 
issues caused by the above patch and the XPS13:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416601
  https://bugzilla.redhat.com/show_bug.cgi?id=1188439

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jan2547 F pulseaudio
   /dev/snd/controlC1:  jan2547 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Feb 25 10:19:01 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-30 (25 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=e4431ecc-e85e-4e35-92af-58f455c46c2b ro kvm-intel.nested=1 
acpi_osi=!Windows 2013 psmouse.resetafter=0 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13

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

2015-02-25 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

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

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

Status in linux package in Ubuntu:
  Invalid

Bug description:
  i can not update my system...  says will not allow..

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-43-generic 3.13.0-43.72
  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.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erik   1885 F pulseaudio
   /dev/snd/pcmC0D0p:   erik   1885 F...m pulseaudio
  Date: Wed Feb 25 01:30:59 2015
  DuplicateSignature: 
package:linux-image-3.13.0-43-generic:3.13.0-43.72:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=f7f614d0-9177-4090-b490-8873c62dd873
  InstallationDate: Installed on 2014-10-14 (134 days ago)
  InstallationMedia:
   
  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: Gateway MX6625
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=943a2719-567a-4a45-88fb-0ab1bd371961 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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-3.13.0-43-generic 3.13.0-43.72 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2005
  dmi.bios.vendor: Gateway
  dmi.bios.version: 70.01
  dmi.board.vendor: Gateway
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnGateway:bvr70.01:bd08/08/2005:svnGateway:pnMX6625:pvr3402282:rvnGateway:rn:rvrRev1.0:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: MX6625
  dmi.product.version: 3402282
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1393079] Re: Touchpad not working after suspend/resume

2015-02-25 Thread Dirk Seidel

The patch from #52 is implemented in today's new kernel 3.16.0-31.41!

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

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 14.10 on an Acer Laptop, model: Aspire E5-571G-941Y
  $ uname -a
  Linux Acer-Aspire-E5-571G 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 
13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  Every time I suspend, the trackpad no longer works when resuming.

  I see several other people have the same issue with the same laptop here:
  http://ubuntuforums.org/showthread.php?t=2250002
  (some people say it's a 14.10 specific problem)

  I realize this report is very poor but please don't hesitate to request data 
/ clarifications from me, I'll be happy to help.
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bod3942 F pulseaudio
   /dev/snd/controlC1:  bod3942 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=2e6e7d72-637c-4b16-8cda-0471dfb711d4
  InstallationDate: Installed on 2014-11-14 (15 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Acer Aspire E5-571G
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed 
root=UUID=94aa9203-873c-4dff-8207-4e6b33a6a3e7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-25-generic N/A
   linux-backports-modules-3.16.0-25-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-25-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-11-14 (15 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.04
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571G:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-571G
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1420560] Re: linux-ti-omap4: 3.2.0-1460.80 -proposed tracker

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

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

** Description changed:

  This bug is for tracking the version to be filled 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, 11. February 2015 01:02 UTC
  kernel-stable-master-bug:1419968
  kernel-stable-Certification-testing-end:Thursday, 12. February 2015 15:01 UTC
  kernel-stable-Prepare-package-end:Friday, 13. February 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 13. February 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 18. February 2015 23:41 UTC
  kernel-stable-Security-signoff-start:Thursday, 19. February 2015 01:01 UTC
  kernel-stable-Verification-testing-start:Thursday, 19. February 2015 01:01 UTC
  kernel-stable-Security-signoff-end:Thursday, 19. February 2015 23:00 UTC
- kernel-stable-phase:Testing
- kernel-stable-phase-changed:Tuesday, 24. February 2015 17:33 UTC
  kernel-stable-Verification-testing-end:Tuesday, 24. February 2015 17:33 UTC
+ kernel-stable-phase:CopyToUpdates
+ kernel-stable-phase-changed:Wednesday, 25. February 2015 11:17 UTC
+ kernel-stable-Promote-to-updates-start:Wednesday, 25. February 2015 11:17 UTC
+ kernel-stable-Regression-testing-end:Wednesday, 25. February 2015 11:17 UTC

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

Title:
  linux-ti-omap4: 3.2.0-1460.80 -proposed tracker

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

Bug description:
  This bug is for tracking the version to be filled 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, 11. February 2015 01:02 UTC
  kernel-stable-master-bug:1419968
  kernel-stable-Certification-testing-end:Thursday, 12. February 2015 15:01 UTC
  kernel-stable-Prepare-package-end:Friday, 13. February 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 13. February 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 18. February 2015 23:41 UTC
  kernel-stable-Security-signoff-start:Thursday, 19. February 2015 01:01 UTC
  kernel-stable-Verification-testing-start:Thursday, 19. February 2015 01:01 UTC
  kernel-stable-Security-signoff-end:Thursday, 19. February 2015 23:00 UTC
  kernel-stable-Verification-testing-end:Tuesday, 24. February 2015 17:33 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-phase-changed:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Regression-testing-end:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Promote-to-updates-end:Wednesday, 25. February 2015 11:25 UTC

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

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

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1460.80

---
linux-ti-omap4 (3.2.0-1460.80) precise; urgency=low

  * Release Tracking Bug
- LP: #1420560

  [ Paolo Pisati ]

  * rebased on Ubuntu-3.2.0-77.112

  [ Ubuntu: 3.2.0-77.112 ]

  * Release Tracking Bug
- LP: #1419968
  * [Packaging] force dpkg-source -I -i behavior
  * isofs: Fix unchecked printing of ER records
- LP: #1409808
- CVE-2014-9584
  * KEYS: close race between key lookup and freeing
- LP: #1409048
- CVE-2014-9529
  * vfs: new internal helper: mnt_has_parent(mnt)
- LP: #1383356
- CVE-2014-7970
  * vfs: more mnt_parent cleanups
- LP: #1383356
- CVE-2014-7970
  * mnt: Prevent pivot_root from creating a loop in the mount tree
- LP: #1383356
- CVE-2014-7970
  * netfilter: conntrack: disable generic tracking for known protocols
- LP: #1413109
- CVE-2014-8160
  * KVM: x86 emulator: reject SYSENTER in compatibility mode on AMD guests
- LP: #1414651
- CVE-2015-0239
  * KVM: x86: SYSENTER emulation is broken
- LP: #1414651
- CVE-2015-0239
  * x86_64, vdso: Fix the vdso address randomization algorithm
- LP: #1409811
- CVE-2014-9585
  * crypto: prefix module autoloading with crypto-
- LP: #1415507
- CVE-2013-7421
  * crypto: add missing crypto module aliases
- LP: #1415507
- CVE-2013-7421
  * crypto: include crypto- module prefix in template
- LP: #1415632
- CVE-2014-9644
 -- Paolo Pisati paolo.pis...@canonical.com   Wed, 11 Feb 2015 10:02:17 +0100

** 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/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:
  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:
  Fix Released
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

[Kernel-packages] [Bug 1413109] Re: CVE-2014-8160

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1460.80

---
linux-ti-omap4 (3.2.0-1460.80) precise; urgency=low

  * Release Tracking Bug
- LP: #1420560

  [ Paolo Pisati ]

  * rebased on Ubuntu-3.2.0-77.112

  [ Ubuntu: 3.2.0-77.112 ]

  * Release Tracking Bug
- LP: #1419968
  * [Packaging] force dpkg-source -I -i behavior
  * isofs: Fix unchecked printing of ER records
- LP: #1409808
- CVE-2014-9584
  * KEYS: close race between key lookup and freeing
- LP: #1409048
- CVE-2014-9529
  * vfs: new internal helper: mnt_has_parent(mnt)
- LP: #1383356
- CVE-2014-7970
  * vfs: more mnt_parent cleanups
- LP: #1383356
- CVE-2014-7970
  * mnt: Prevent pivot_root from creating a loop in the mount tree
- LP: #1383356
- CVE-2014-7970
  * netfilter: conntrack: disable generic tracking for known protocols
- LP: #1413109
- CVE-2014-8160
  * KVM: x86 emulator: reject SYSENTER in compatibility mode on AMD guests
- LP: #1414651
- CVE-2015-0239
  * KVM: x86: SYSENTER emulation is broken
- LP: #1414651
- CVE-2015-0239
  * x86_64, vdso: Fix the vdso address randomization algorithm
- LP: #1409811
- CVE-2014-9585
  * crypto: prefix module autoloading with crypto-
- LP: #1415507
- CVE-2013-7421
  * crypto: add missing crypto module aliases
- LP: #1415507
- CVE-2013-7421
  * crypto: include crypto- module prefix in template
- LP: #1415632
- CVE-2014-9644
 -- Paolo Pisati paolo.pis...@canonical.com   Wed, 11 Feb 2015 10:02:17 +0100

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

Title:
  CVE-2014-8160

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

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

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1460.80

---
linux-ti-omap4 (3.2.0-1460.80) precise; urgency=low

  * Release Tracking Bug
- LP: #1420560

  [ Paolo Pisati ]

  * rebased on Ubuntu-3.2.0-77.112

  [ Ubuntu: 3.2.0-77.112 ]

  * Release Tracking Bug
- LP: #1419968
  * [Packaging] force dpkg-source -I -i behavior
  * isofs: Fix unchecked printing of ER records
- LP: #1409808
- CVE-2014-9584
  * KEYS: close race between key lookup and freeing
- LP: #1409048
- CVE-2014-9529
  * vfs: new internal helper: mnt_has_parent(mnt)
- LP: #1383356
- CVE-2014-7970
  * vfs: more mnt_parent cleanups
- LP: #1383356
- CVE-2014-7970
  * mnt: Prevent pivot_root from creating a loop in the mount tree
- LP: #1383356
- CVE-2014-7970
  * netfilter: conntrack: disable generic tracking for known protocols
- LP: #1413109
- CVE-2014-8160
  * KVM: x86 emulator: reject SYSENTER in compatibility mode on AMD guests
- LP: #1414651
- CVE-2015-0239
  * KVM: x86: SYSENTER emulation is broken
- LP: #1414651
- CVE-2015-0239
  * x86_64, vdso: Fix the vdso address randomization algorithm
- LP: #1409811
- CVE-2014-9585
  * crypto: prefix module autoloading with crypto-
- LP: #1415507
- CVE-2013-7421
  * crypto: add missing crypto module aliases
- LP: #1415507
- CVE-2013-7421
  * crypto: include crypto- module prefix in template
- LP: #1415632
- CVE-2014-9644
 -- Paolo Pisati paolo.pis...@canonical.com   Wed, 11 Feb 2015 10:02:17 +0100

** 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/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:
  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:
  Fix Released
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

[Kernel-packages] [Bug 1409808] Re: CVE-2014-9584

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1460.80

---
linux-ti-omap4 (3.2.0-1460.80) precise; urgency=low

  * Release Tracking Bug
- LP: #1420560

  [ Paolo Pisati ]

  * rebased on Ubuntu-3.2.0-77.112

  [ Ubuntu: 3.2.0-77.112 ]

  * Release Tracking Bug
- LP: #1419968
  * [Packaging] force dpkg-source -I -i behavior
  * isofs: Fix unchecked printing of ER records
- LP: #1409808
- CVE-2014-9584
  * KEYS: close race between key lookup and freeing
- LP: #1409048
- CVE-2014-9529
  * vfs: new internal helper: mnt_has_parent(mnt)
- LP: #1383356
- CVE-2014-7970
  * vfs: more mnt_parent cleanups
- LP: #1383356
- CVE-2014-7970
  * mnt: Prevent pivot_root from creating a loop in the mount tree
- LP: #1383356
- CVE-2014-7970
  * netfilter: conntrack: disable generic tracking for known protocols
- LP: #1413109
- CVE-2014-8160
  * KVM: x86 emulator: reject SYSENTER in compatibility mode on AMD guests
- LP: #1414651
- CVE-2015-0239
  * KVM: x86: SYSENTER emulation is broken
- LP: #1414651
- CVE-2015-0239
  * x86_64, vdso: Fix the vdso address randomization algorithm
- LP: #1409811
- CVE-2014-9585
  * crypto: prefix module autoloading with crypto-
- LP: #1415507
- CVE-2013-7421
  * crypto: add missing crypto module aliases
- LP: #1415507
- CVE-2013-7421
  * crypto: include crypto- module prefix in template
- LP: #1415632
- CVE-2014-9644
 -- Paolo Pisati paolo.pis...@canonical.com   Wed, 11 Feb 2015 10:02:17 +0100

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

Title:
  CVE-2014-9584

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:
  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:
  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 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:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in

[Kernel-packages] [Bug 1420560] Re: linux-ti-omap4: 3.2.0-1460.80 -proposed tracker

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1460.80

---
linux-ti-omap4 (3.2.0-1460.80) precise; urgency=low

  * Release Tracking Bug
- LP: #1420560

  [ Paolo Pisati ]

  * rebased on Ubuntu-3.2.0-77.112

  [ Ubuntu: 3.2.0-77.112 ]

  * Release Tracking Bug
- LP: #1419968
  * [Packaging] force dpkg-source -I -i behavior
  * isofs: Fix unchecked printing of ER records
- LP: #1409808
- CVE-2014-9584
  * KEYS: close race between key lookup and freeing
- LP: #1409048
- CVE-2014-9529
  * vfs: new internal helper: mnt_has_parent(mnt)
- LP: #1383356
- CVE-2014-7970
  * vfs: more mnt_parent cleanups
- LP: #1383356
- CVE-2014-7970
  * mnt: Prevent pivot_root from creating a loop in the mount tree
- LP: #1383356
- CVE-2014-7970
  * netfilter: conntrack: disable generic tracking for known protocols
- LP: #1413109
- CVE-2014-8160
  * KVM: x86 emulator: reject SYSENTER in compatibility mode on AMD guests
- LP: #1414651
- CVE-2015-0239
  * KVM: x86: SYSENTER emulation is broken
- LP: #1414651
- CVE-2015-0239
  * x86_64, vdso: Fix the vdso address randomization algorithm
- LP: #1409811
- CVE-2014-9585
  * crypto: prefix module autoloading with crypto-
- LP: #1415507
- CVE-2013-7421
  * crypto: add missing crypto module aliases
- LP: #1415507
- CVE-2013-7421
  * crypto: include crypto- module prefix in template
- LP: #1415632
- CVE-2014-9644
 -- Paolo Pisati paolo.pis...@canonical.com   Wed, 11 Feb 2015 10:02:17 +0100

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-7421

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7970

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-8160

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-9529

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-9584

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-9585

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-9644

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-0239

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

Title:
  linux-ti-omap4: 3.2.0-1460.80 -proposed tracker

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

Bug description:
  This bug is for tracking the version to be filled 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, 11. February 2015 01:02 UTC
  kernel-stable-master-bug:1419968
  kernel-stable-Certification-testing-end:Thursday, 12. February 2015 15:01 UTC
  kernel-stable-Prepare-package-end:Friday, 13. February 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 13. February 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 18. February 2015 23:41 UTC
  kernel-stable-Security-signoff-start:Thursday, 19. February 2015 01:01 UTC
  kernel-stable-Verification-testing-start:Thursday, 19. February 2015 01:01 UTC
  kernel-stable-Security-signoff-end:Thursday, 19. February 2015 23:00 UTC
  kernel-stable-Verification-testing-end:Tuesday, 24. February 2015 17:33 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-phase-changed:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Regression-testing-end:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Promote-to-updates-end:Wednesday, 25. February 2015 11:25 UTC

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

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

[Kernel-packages] [Bug 1414651] Re: CVE-2015-0239

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1460.80

---
linux-ti-omap4 (3.2.0-1460.80) precise; urgency=low

  * Release Tracking Bug
- LP: #1420560

  [ Paolo Pisati ]

  * rebased on Ubuntu-3.2.0-77.112

  [ Ubuntu: 3.2.0-77.112 ]

  * Release Tracking Bug
- LP: #1419968
  * [Packaging] force dpkg-source -I -i behavior
  * isofs: Fix unchecked printing of ER records
- LP: #1409808
- CVE-2014-9584
  * KEYS: close race between key lookup and freeing
- LP: #1409048
- CVE-2014-9529
  * vfs: new internal helper: mnt_has_parent(mnt)
- LP: #1383356
- CVE-2014-7970
  * vfs: more mnt_parent cleanups
- LP: #1383356
- CVE-2014-7970
  * mnt: Prevent pivot_root from creating a loop in the mount tree
- LP: #1383356
- CVE-2014-7970
  * netfilter: conntrack: disable generic tracking for known protocols
- LP: #1413109
- CVE-2014-8160
  * KVM: x86 emulator: reject SYSENTER in compatibility mode on AMD guests
- LP: #1414651
- CVE-2015-0239
  * KVM: x86: SYSENTER emulation is broken
- LP: #1414651
- CVE-2015-0239
  * x86_64, vdso: Fix the vdso address randomization algorithm
- LP: #1409811
- CVE-2014-9585
  * crypto: prefix module autoloading with crypto-
- LP: #1415507
- CVE-2013-7421
  * crypto: add missing crypto module aliases
- LP: #1415507
- CVE-2013-7421
  * crypto: include crypto- module prefix in template
- LP: #1415632
- CVE-2014-9644
 -- Paolo Pisati paolo.pis...@canonical.com   Wed, 11 Feb 2015 10:02:17 +0100

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

Title:
  CVE-2015-0239

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

[Kernel-packages] [Bug 1409811] Re: CVE-2014-9585

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1460.80

---
linux-ti-omap4 (3.2.0-1460.80) precise; urgency=low

  * Release Tracking Bug
- LP: #1420560

  [ Paolo Pisati ]

  * rebased on Ubuntu-3.2.0-77.112

  [ Ubuntu: 3.2.0-77.112 ]

  * Release Tracking Bug
- LP: #1419968
  * [Packaging] force dpkg-source -I -i behavior
  * isofs: Fix unchecked printing of ER records
- LP: #1409808
- CVE-2014-9584
  * KEYS: close race between key lookup and freeing
- LP: #1409048
- CVE-2014-9529
  * vfs: new internal helper: mnt_has_parent(mnt)
- LP: #1383356
- CVE-2014-7970
  * vfs: more mnt_parent cleanups
- LP: #1383356
- CVE-2014-7970
  * mnt: Prevent pivot_root from creating a loop in the mount tree
- LP: #1383356
- CVE-2014-7970
  * netfilter: conntrack: disable generic tracking for known protocols
- LP: #1413109
- CVE-2014-8160
  * KVM: x86 emulator: reject SYSENTER in compatibility mode on AMD guests
- LP: #1414651
- CVE-2015-0239
  * KVM: x86: SYSENTER emulation is broken
- LP: #1414651
- CVE-2015-0239
  * x86_64, vdso: Fix the vdso address randomization algorithm
- LP: #1409811
- CVE-2014-9585
  * crypto: prefix module autoloading with crypto-
- LP: #1415507
- CVE-2013-7421
  * crypto: add missing crypto module aliases
- LP: #1415507
- CVE-2013-7421
  * crypto: include crypto- module prefix in template
- LP: #1415632
- CVE-2014-9644
 -- Paolo Pisati paolo.pis...@canonical.com   Wed, 11 Feb 2015 10:02:17 +0100

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

Title:
  CVE-2014-9585

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

[Kernel-packages] [Bug 1420560] Re: linux-ti-omap4: 3.2.0-1460.80 -proposed tracker

2015-02-25 Thread Adam Conrad

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed = Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Platform QA Team (canonical-platform-qa) = Paolo 
Pisati (p-pisati)

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

Title:
  linux-ti-omap4: 3.2.0-1460.80 -proposed tracker

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

Bug description:
  This bug is for tracking the version to be filled 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, 11. February 2015 01:02 UTC
  kernel-stable-master-bug:1419968
  kernel-stable-Certification-testing-end:Thursday, 12. February 2015 15:01 UTC
  kernel-stable-Prepare-package-end:Friday, 13. February 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 13. February 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 18. February 2015 23:41 UTC
  kernel-stable-Security-signoff-start:Thursday, 19. February 2015 01:01 UTC
  kernel-stable-Verification-testing-start:Thursday, 19. February 2015 01:01 UTC
  kernel-stable-Security-signoff-end:Thursday, 19. February 2015 23:00 UTC
  kernel-stable-Verification-testing-end:Tuesday, 24. February 2015 17:33 UTC
  kernel-stable-phase:CopyToUpdates
  kernel-stable-phase-changed:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Promote-to-updates-start:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Regression-testing-end:Wednesday, 25. February 2015 11:17 UTC
  kernel-stable-Promote-to-updates-end:Wednesday, 25. February 2015 11:25 UTC

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

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

[Kernel-packages] [Bug 1409048] Re: CVE-2014-9529

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1460.80

---
linux-ti-omap4 (3.2.0-1460.80) precise; urgency=low

  * Release Tracking Bug
- LP: #1420560

  [ Paolo Pisati ]

  * rebased on Ubuntu-3.2.0-77.112

  [ Ubuntu: 3.2.0-77.112 ]

  * Release Tracking Bug
- LP: #1419968
  * [Packaging] force dpkg-source -I -i behavior
  * isofs: Fix unchecked printing of ER records
- LP: #1409808
- CVE-2014-9584
  * KEYS: close race between key lookup and freeing
- LP: #1409048
- CVE-2014-9529
  * vfs: new internal helper: mnt_has_parent(mnt)
- LP: #1383356
- CVE-2014-7970
  * vfs: more mnt_parent cleanups
- LP: #1383356
- CVE-2014-7970
  * mnt: Prevent pivot_root from creating a loop in the mount tree
- LP: #1383356
- CVE-2014-7970
  * netfilter: conntrack: disable generic tracking for known protocols
- LP: #1413109
- CVE-2014-8160
  * KVM: x86 emulator: reject SYSENTER in compatibility mode on AMD guests
- LP: #1414651
- CVE-2015-0239
  * KVM: x86: SYSENTER emulation is broken
- LP: #1414651
- CVE-2015-0239
  * x86_64, vdso: Fix the vdso address randomization algorithm
- LP: #1409811
- CVE-2014-9585
  * crypto: prefix module autoloading with crypto-
- LP: #1415507
- CVE-2013-7421
  * crypto: add missing crypto module aliases
- LP: #1415507
- CVE-2013-7421
  * crypto: include crypto- module prefix in template
- LP: #1415632
- CVE-2014-9644
 -- Paolo Pisati paolo.pis...@canonical.com   Wed, 11 Feb 2015 10:02:17 +0100

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

Title:
  CVE-2014-9529

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:
  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:
  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 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:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in

[Kernel-packages] [Bug 1383356] Re: CVE-2014-7970

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1460.80

---
linux-ti-omap4 (3.2.0-1460.80) precise; urgency=low

  * Release Tracking Bug
- LP: #1420560

  [ Paolo Pisati ]

  * rebased on Ubuntu-3.2.0-77.112

  [ Ubuntu: 3.2.0-77.112 ]

  * Release Tracking Bug
- LP: #1419968
  * [Packaging] force dpkg-source -I -i behavior
  * isofs: Fix unchecked printing of ER records
- LP: #1409808
- CVE-2014-9584
  * KEYS: close race between key lookup and freeing
- LP: #1409048
- CVE-2014-9529
  * vfs: new internal helper: mnt_has_parent(mnt)
- LP: #1383356
- CVE-2014-7970
  * vfs: more mnt_parent cleanups
- LP: #1383356
- CVE-2014-7970
  * mnt: Prevent pivot_root from creating a loop in the mount tree
- LP: #1383356
- CVE-2014-7970
  * netfilter: conntrack: disable generic tracking for known protocols
- LP: #1413109
- CVE-2014-8160
  * KVM: x86 emulator: reject SYSENTER in compatibility mode on AMD guests
- LP: #1414651
- CVE-2015-0239
  * KVM: x86: SYSENTER emulation is broken
- LP: #1414651
- CVE-2015-0239
  * x86_64, vdso: Fix the vdso address randomization algorithm
- LP: #1409811
- CVE-2014-9585
  * crypto: prefix module autoloading with crypto-
- LP: #1415507
- CVE-2013-7421
  * crypto: add missing crypto module aliases
- LP: #1415507
- CVE-2013-7421
  * crypto: include crypto- module prefix in template
- LP: #1415632
- CVE-2014-9644
 -- Paolo Pisati paolo.pis...@canonical.com   Wed, 11 Feb 2015 10:02:17 +0100

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

Title:
  CVE-2014-7970

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

[Kernel-packages] [Bug 1383356] Re: CVE-2014-7970

This bug was fixed in the package linux-ti-omap4 - 3.2.0-1460.80

---
linux-ti-omap4 (3.2.0-1460.80) precise; urgency=low

  * Release Tracking Bug
- LP: #1420560

  [ Paolo Pisati ]

  * rebased on Ubuntu-3.2.0-77.112

  [ Ubuntu: 3.2.0-77.112 ]

  * Release Tracking Bug
- LP: #1419968
  * [Packaging] force dpkg-source -I -i behavior
  * isofs: Fix unchecked printing of ER records
- LP: #1409808
- CVE-2014-9584
  * KEYS: close race between key lookup and freeing
- LP: #1409048
- CVE-2014-9529
  * vfs: new internal helper: mnt_has_parent(mnt)
- LP: #1383356
- CVE-2014-7970
  * vfs: more mnt_parent cleanups
- LP: #1383356
- CVE-2014-7970
  * mnt: Prevent pivot_root from creating a loop in the mount tree
- LP: #1383356
- CVE-2014-7970
  * netfilter: conntrack: disable generic tracking for known protocols
- LP: #1413109
- CVE-2014-8160
  * KVM: x86 emulator: reject SYSENTER in compatibility mode on AMD guests
- LP: #1414651
- CVE-2015-0239
  * KVM: x86: SYSENTER emulation is broken
- LP: #1414651
- CVE-2015-0239
  * x86_64, vdso: Fix the vdso address randomization algorithm
- LP: #1409811
- CVE-2014-9585
  * crypto: prefix module autoloading with crypto-
- LP: #1415507
- CVE-2013-7421
  * crypto: add missing crypto module aliases
- LP: #1415507
- CVE-2013-7421
  * crypto: include crypto- module prefix in template
- LP: #1415632
- CVE-2014-9644
 -- Paolo Pisati paolo.pis...@canonical.com   Wed, 11 Feb 2015 10:02:17 +0100

** Changed in: linux-ti-omap4 (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/1383356

Title:
  CVE-2014-7970

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

[Kernel-packages] [Bug 1420560] Re: linux-ti-omap4: 3.2.0-1460.80 -proposed tracker