date:20151006

Just saw this new after updating to the 3.19.0-30-generic kernel in
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/1488719

Title:
  dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control
  interrupt lied (SDE)!"

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a recent intel NUC using i915 graphics, I get the following errors
  in dmesg:

  [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt
  lied (SDE)!

  There are two monitors connected to this box, one with mini-
  HDMI->HDMI, one with mini-DP->HDMI cable.

  Maybe related:

  https://bugs.freedesktop.org/show_bug.cgi?id=80896

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-generic 3.19.0.26.25
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Wed Aug 26 10:07:31 2015
  InstallationDate: Installed on 2015-08-01 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

--- Comment From ss...@in.ibm.com 2015-10-07 04:46 EDT---
The problem is fixed with latest crash tool.

root@ubuntu:/var/crash/201510070039# cat /etc/issue
Ubuntu 14.04.3 LTS \n \l

root@ubuntu:/var/crash/201510070039# uname -a
Linux ubuntu 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
root@ubuntu:/var/crash/201510070039# dpkg -l | grep crash
ii  apport   2.14.1-0ubuntu3.16   all   
   automatically generate crash reports for debugging
ii  crash7.0.3-3ubuntu4.3 
ppc64el  kernel debugging utility, allowing gdb like syntax

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

Title:
  crash subcommand bt -a displays incomplete information

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  ---Steps to Reproduce---
  1) Using latest daily ISO install 14.04.02 as a Power VM guest. The LPAR has 
vTPM functionality enabled.
  2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
  3) Configure kdump. A fix is required to configure kdump. Refer to defect 
(https://bugzilla.linux.ibm.com/show_bug.cgi?id=125712)
  4) Trigger a dump. Dump is captured successfully.
  5) Install dbgsym package for the kernel
  6) Use crash to analyze the dump.

  Crash tool is able to read the dump. But it fails to list back trace
  for CPUS using bt command.

  # crash /usr/lib/debug/boot/vmlinux-3.19.0-18-generic
  dump.201506040624

  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

KERNEL: /usr/lib/debug/boot/vmlinux-3.19.0-18-generic
  DUMPFILE: dump.201506040624  [PARTIAL DUMP]
  CPUS: 16
  DATE: Wed Dec 31 19:00:00 1969
UPTIME: 00:02:32
  LOAD AVERAGE: 0.01, 0.01, 0.01
 TASKS: 245
  NODENAME: alp9
   RELEASE: 3.19.0-18-generic
   VERSION: #18~14.04.1-Ubuntu SMP Wed May 20 09:40:36 UTC 2015
   MACHINE: ppc64le  (3724 Mhz)
MEMORY: 100 GB
 PANIC: "Oops: System Reset, sig: 6 [#1]" (check log for details)
   PID: 0
   COMMAND: "swapper/0"
  TASK: c13cca80  (1 of 16)  [THREAD_INFO: c1448000]
   CPU: 0
 STATE: TASK_RUNNING (PANIC)

  crash> bt -a
  PID: 0  TASK: c13cca80  CPU: 0   COMMAND: "swapper/0"

  PID: 0  TASK: c003dbf3b3c0  CPU: 1   COMMAND: "swapper/1"

  PID: 0  TASK: c003dbf39f00  CPU: 2   COMMAND: "swapper/2"

  PID: 0  TASK: c003dbf38a40  CPU: 3   COMMAND: "swapper/3"

  PID: 0  TASK: c003dbf37580  CPU: 4   COMMAND: "swapper/4"

  PID: 0  TASK: c003dbf360c0  CPU: 5   COMMAND: "swapper/5"

  PID: 0  TASK: c003dbf34c00  CPU: 6   COMMAND: "swapper/6"

  PID: 0  TASK: c003dbf33740  CPU: 7   COMMAND: "swapper/7"

  PID: 0  TASK: c003dbf32280  CPU: 8   COMMAND: "swapper/8"

  PID: 0  TASK: c003dbf30dc0  CPU: 9   COMMAND: "swapper/9"

  PID: 0  TASK: c003dbf2f900  CPU: 10  COMMAND: "swapper/10"

  PID: 0  TASK: c003dbf2e440  CPU: 11  COMMAND: "swapper/11"

  PID: 0  TASK: c003dbf2cf80  CPU: 12  COMMAND: "swapper/12"

  PID: 0  TASK: c003dbf2bac0  CPU: 13  COMMAND: "swapper/13"

  PID: 0  TASK: c003dbf2a600  CPU: 14  COMMAND: "swapper/14"

  PID: 0  TASK: c003dbf29140  CPU: 15  COMMAND: "swapper/15"
  crash> bt
  PID: 0  TASK: c13cca80  CPU: 0   COMMAND: "swapper/0"
  crash>

  == Comment: #5 - Hari Krishna Bathini  - 2015-06-08 
00:31:41 ==
  The fix patch is upstream in crash git repo
  git://github.com/crash-utility/crash.git
  commit id: dc4ea682a21567dd9d093862ec54eb8529199c05
  It is part

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

--- Comment From ss...@in.ibm.com 2015-10-07 05:18 EDT---
Tested with latest build for 14.04.03. The problem is fixed.

root@ubuntu:/var/crash/201510070111# ls
dmesg.201510070111  dump.201510070111
root@ubuntu:/var/crash/201510070111# cat /etc/issue
Ubuntu 14.04.3 LTS \n \l

root@ubuntu:/var/crash/201510070111# uname -a
Linux ubuntu 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
root@ubuntu:/var/crash/201510070111#

root@ubuntu:/var/crash/201510070111# cat dmesg.201510070111 | grep tpm
[0.376740] tpm_ibmvtpm 3003: CRQ initialization completed
root@ubuntu:/var/crash/201510070111#

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

Title:
  Kdump boot fails due to Kernel OOPS @tpm_ibmvtpm_probe (PowerVM)

Status in kexec-tools package in Ubuntu:
  New

Bug description:
  == Comment: #0 - SACHIN P. SANT  - 2015-06-04 06:03:17 ==
  ---Steps to Reproduce---
  1) Using latest daily ISO install 14.04.02 as a Power VM guest. The LPAR has 
vTPM functionality enabled.
  2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
  3) Configure kdump. A fix is required to configure kdump. Refer to defect 
(https://bugzilla.linux.ibm.com/show_bug.cgi?id=125712)

  # kdump-config load
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-3.19.0-18-generic 
root=UUID=3ea23bcf-7269-432f-bacc-f82c6cdd774e ro splash quiet vt.handoff=7 
irqpoll maxcpus=1 nousb elfcorehdr=155200K 
  segment[0].mem:0x800 memsz:24641536
  segment[1].mem:0x978 memsz:65536
  segment[2].mem:0x979 memsz:65536
  segment[3].mem:0x97a memsz:65536
  segment[4].mem:0x97b memsz:20971520
  segment[5].mem:0xec7 memsz:262144
   * loaded kdump kernel

  # cat /proc/cmdline 
  BOOT_IMAGE=/boot/vmlinux-3.19.0-18-generic 
root=UUID=3ea23bcf-7269-432f-bacc-f82c6cdd774e ro splash quiet 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=7
  #

  4) Trigger a crash. Kdump boot fails with a kernel panic

  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 0
   <- smp_release_cpus()
   <- setup_system()
  [0.877197] Unable to handle kernel paging request for data at address 
0x0010
  [0.877232] Faulting instruction address: 0xc863a044
  [0.877241] Oops: Kernel access of bad area, sig: 11 [#1]
  [0.877246] SMP NR_CPUS=2048 NUMA pSeries
  [0.877255] Modules linked in:
  [0.877264] CPU: 8 PID: 1 Comm: swapper/8 Not tainted 3.19.0-18-generic 
#18~14.04.1-Ubuntu
  [0.877273] task: c00086bc ti: c00086c0 task.ti: 
c00086c0
  [0.877280] NIP: c863a044 LR: c8639f54 CTR: 
003fd734
  [0.877288] REGS: c00086c03580 TRAP: 0300   Not tainted  
(3.19.0-18-generic)
  [0.877294] MSR: 80019033   CR: 24002022  
XER: 2010
  [0.877314] CFAR: c8639f60 DAR: 0010 DSISR: 4000 
SOFTE: 1 
  GPR00: 24002022 c00086c03800 c944c760 0100 
  GPR04: fff00500   0010 
  GPR08: 0008  0001  
  GPR12: fff0 ce7f4800 c800bdd8  
  GPR16:     
  GPR20:     
  GPR24:  c00086dece00 c8a86cb0 fff0 
  GPR28:  c000823c9848 c0008608ad00 c000823c9800 
  [0.877409] NIP [c863a044] tpm_ibmvtpm_probe+0x2e4/0x580
  [0.877417] LR [c8639f54] tpm_ibmvtpm_probe+0x1f4/0x580
  [0.877423] Call Trace:
  [0.877430] [c00086c03800] [c8639e6c] 
tpm_ibmvtpm_probe+0x10c/0x580 (unreliable)
  [0.877442] [c00086c038a0] [c8033a1c] vio_bus_probe+0x1bc/0x480
  [0.877451] [c00086c03940] [c864b15c] 
driver_probe_device+0xec/0x470
  [0.877461] [c00086c039d0] [c864b69c] 
__driver_attach+0x11c/0x120
  [0.877469] [c00086c03a10] [c864817c] 
bus_for_each_dev+0x9c/0x110
  [0.877478] [c00086c03a60] [c864a8fc] driver_attach+0x3c/0x60
  [0.877486] [c00086c03a90] [c864a2d8] 
bus_add_driver+0x208/0x320
  [0.877495] [c00086c03b20] [c864c31c] 
driver_register+0x9c/0x180
  [0.877504] [c00086c03b90] [c80322f8] 
__vio_register_driver+0x78/0xc0
  [0.877513] [c00086c03c10] [c8df6de8] 
ibmvtpm_module_init+0x2c/0x40
  [0.877523] [c00086c03c30] [c800b4bc] 
do_one_initcall+0x11c/0x270
  [0.877532] [c00086c03d00] [c8da4100] 
kernel_init_freeable+0x264/0x34c
  [0.877543] [c00086c03dc0] [c800bdfc] kernel_init+0x2c/0x130
  [

[Kernel-packages] [Bug 1487621] Re: Fails to boot on Macbook Air 2013 (Haswell) in SMP mode, needs nosmp to boot

2015-10-06 Thread Jeff Lane

How long will it take to get this into Trusty?  Or would I have a better
time installing the Wily Beta?

Since 4.2.0 seems to work in SMP mode, my only issue is lack of drivers
for wifi and such. (And trusty in UP mode seems to run very, very hot
and is working the fan to death).

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

Title:
  Fails to boot on Macbook Air 2013 (Haswell) in SMP mode, needs nosmp
  to boot

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

Bug description:
  I keep running into issues with booting on a 2013 Macbook Air.  After
  grub, the kernel and initrd load and the system then just hangs with a
  blinking cursor.

  Removing the "quiet" and "splash" options shows me that the kernel
  hangs bringing up SMP, just as in bug #1197451 which has been marked
  Fix Released already (some time ago, actually).

  I get exactly what was mentioned in the comments about SMP hanging and
  have had to manually inject nosmp into the boot command when I boot
  the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-40-generic 3.16.0-40.54~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-40.54~14.04.1-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 21 17:17:40 2015
  InstallationDate: Installed on 2015-06-11 (71 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64+mac 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

--- Comment From ss...@in.ibm.com 2015-10-07 04:50 EDT---
Problem is fixed with latest version of makedumpfile.

root@ubuntu:/var/crash/201510070039# dpkg -l | grep makedumpfile
ii  makedumpfile 1.5.5-2ubuntu1.4 
ppc64el  VMcore extraction tool
root@ubuntu:/var/crash/201510070039# cat /etc/issue
Ubuntu 14.04.3 LTS \n \l

root@ubuntu:/var/crash/201510070039#

* running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/201510070039/dump-incomplete
* Stopping Mount network filesystems[ OK ]
Copying data   : [100.0 %] /

The dumpfile is saved to /var/crash/201510070039/dump-incomplete.

makedumpfile Completed.
* kdump-config: saved vmcore in /var/crash/201510070039
* running makedumpfile --dump-dmesg /proc/vmcore 
/var/crash/201510070039/dmesg.201510070039

The dmesg log is saved to /var/crash/201510070039/dmesg.201510070039.

makedumpfile Completed.
* kdump-config: saved dmesg content in /var/crash/201510070039
Wed, 07 Oct 2015 00:39:52 -0400
[   30.881085] reboot: Restarting system

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

Title:
  Unsupported kernel warning while running makedumpfile

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Fix Released

Bug description:
  [SRU justification]
  Newer trusty kernels trigger a supportability message from makedumpfile.  The 
upstream version used on the release do not support those kernels.

  [Impact]
  Warning message when running makedumpfile on kernels higher than 3.11

  [Fix]
  Cherry-pick upstream commits that provide newer kernel support.

  [Test Case]
  1) Using latest daily ISO install 14.04.02 as a Power VM guest.
  2) Install linux-virtual-lts-vivid (hence upgrading kernel to 3.19)
  3) Configure kdump.
  4) Trigger a dump. Dump is captured successfully without the message
 "The kernel version is not supported." being displayed

  [Regression]
  Aside from cosmetic modification in README, the only sensible modification
  it to adapt to the CONFIG_RANDOMIZE_BASE=y kernel parameter to correctly
  fetch memory element. This config is enabled in new kernels.

  [Original description of the problem]

  ---Steps to Reproduce---
  1) Using latest daily ISO install 14.04.02 as a Power VM guest.
  2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
  3) Configure kdump. A fix is required to configure kdump. Refer to defect 
(https://bugzilla.linux.ibm.com/show_bug.cgi?id=125712)
  4) Trigger a dump. Dump is captured successfully.

  During collection of dump following warning is shown on the screen. It
  would be good to fix this warning.

  Starting kdump-tools:  * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/201506040624/dump-incomplete
  The kernel version is not supported.  <<
  The created dumpfile may be incomplete.
  Copying data   : [100.0 %] /

  The dumpfile is saved to /var/crash/201506040624/dump-incomplete.

  makedumpfile Completed.
   * kdump-tools: saved vmcore in /var/crash/201506040624
   * running makedumpfile --dump-dmesg /proc/vmcore 
/var/crash/201506040624/dmesg.201506040624
  The kernel version is not supported.  <<
  The created dumpfile may be incomplete.

  The dmesg log is saved to /var/crash/201506040624/dmesg.201506040624.

  makedumpfile Completed.
   * kdump-tools: saved dmesg content in /var/crash/201506040624

  == Comment: #1 - Hari Krishna Bathini  - 2015-06-04 
15:05:41 ==
  makedumpfile tool version, please?

  == Comment: #2 - SACHIN P. SANT  - 2015-06-05 01:30:23 ==
  (In reply to comment #1)
  > makedumpfile tool version, please?

  makedumpfile -v
  makedumpfile: version 1.5.5 (released on 18 Dec 2013)

  == Comment: #6 - SACHIN P. SANT  - 2015-06-24 06:25:13 ==
  Externalizing comment :

  Each makedumpfile version supports kernel versions ranging from OLDEST_VERSION
  till LATEST_VERSION (defined as macros in makedumpfile.h).
  For makedumpfile v1.5.5, the LATEST_VERSION version is defined as 3.11.3.
  As the makedumpfile tool currently shipped with ubuntu is based on v1.5.5 and
  as the kernel version is higher (v3.13/v3.16/v3.19), we see this warning.
  We can deal with this in a couple of ways:

  1. Suggest Canonical to spike the LATEST_VERSION macro to 3.19 reinforcing 
support for kernel version 3.19.
  2. Suggest Canonical to use the latest makedumpfile version (1.5.8) that 
supports kernel version 3.19

  Thanks
  Hari

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

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

[Kernel-packages] [Bug 1503005] Re: linux: 3.19.0-31.35 -proposed tracker

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

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.19.0-31.35 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 05. October 2015 18:56 UTC
- kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 05:02 UTC
- kernel-stable-phase-changed:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 03:02 UTC
+ kernel-stable-phase:Verification & Testing
+ kernel-stable-phase-changed:Wednesday, 07. October 2015 05:00 UTC
+ kernel-stable-Verification-testing-start:Wednesday, 07. October 2015 05:00 UTC
+ kernel-stable-Certification-testing-start:Wednesday, 07. October 2015 05:01 
UTC
+ kernel-stable-Security-signoff-start:Wednesday, 07. October 2015 05:01 UTC
+ proposed-announcement-sent:True
+ kernel-stable-Regression-testing-start:Wednesday, 07. October 2015 05:01 UTC

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

Title:
  linux: 3.19.0-31.35 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 05. October 2015 18:56 UTC
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 03:02 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 07. October 2015 05:00 UTC
  kernel-stable-Verification-testing-start:Wednesday, 07. October 2015 05:00 UTC
  kernel-stable-Certification-testing-start:Wednesday, 07. October 2015 05:01 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 07. October 2015 05:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 07. October 2015 05:01 UTC

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

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

[Kernel-packages] [Bug 1503541] [NEW] kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] ERROR The master control interrupt lied (SDE)!"

Public bug reported:

On an intel i5 toshiba laptop on vivid. Upgraded to the
3.19.0-30-generic kernel and started seeing this. Additionally, bootup
was slow.

kern.log/dmesg is flooded with this output

[   69.070503] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master
control interrupt lied (SDE)!

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-30-generic 3.19.0-30.34
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  wolsen 2493 F pulseaudio
 /dev/snd/controlC1:  wolsen 2493 F pulseaudio
CurrentDesktop: Unity
Date: Tue Oct  6 22:30:20 2015
HibernationDevice: RESUME=UUID=096b9e95-621b-4cc7-a10c-250149e1b48b
InstallationDate: Installed on 2015-07-15 (83 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: TOSHIBA Satellite E45-B
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-30-generic N/A
 linux-backports-modules-3.19.0-30-generic  N/A
 linux-firmware 1.143.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/12/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: CA10CU
dmi.board.vendor: TOSHIBA
dmi.board.version: 2.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.10:bd01/12/2015:svnTOSHIBA:pnSatelliteE45-B:pvrPSPNAU-001002:rvnTOSHIBA:rnCA10CU:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite E45-B
dmi.product.version: PSPNAU-001002
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug vivid

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

Title:
  kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The
  master control interrupt lied (SDE)!"

Status in linux package in Ubuntu:
  New

Bug description:
  On an intel i5 toshiba laptop on vivid. Upgraded to the
  3.19.0-30-generic kernel and started seeing this. Additionally, bootup
  was slow.

  kern.log/dmesg is flooded with this output

  [   69.070503] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master
  control interrupt lied (SDE)!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wolsen 2493 F pulseaudio
   /dev/snd/controlC1:  wolsen 2493 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct  6 22:30:20 2015
  HibernationDevice: RESUME=UUID=096b9e95-621b-4cc7-a10c-250149e1b48b
  InstallationDate: Installed on 2015-07-15 (83 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: TOSHIBA Satellite E45-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: CA10CU
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.10:bd01/12/2015:svnTOSHIBA:pnSatelliteE45-B:pvrPSPNAU-001002:rvnTOSHIBA:rnCA10CU:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite E45-B
  dmi.product.version: PSPNAU-001002
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503541/+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 1503541] Re: kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] ERROR The master control interrupt lied (SDE)!"

Hmm looks like this was showing up on Oct 3 in the kern.log.1 but I
didn't upgrade to the 3.19.0-30 kernel until today. So it must have
existed previously (though it seems much more readily apparent now).

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

Title:
  kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The
  master control interrupt lied (SDE)!"

Status in linux package in Ubuntu:
  New

Bug description:
  On an intel i5 toshiba laptop on vivid. Upgraded to the
  3.19.0-30-generic kernel and started seeing this. Additionally, bootup
  was slow.

  kern.log/dmesg is flooded with this output

  [   69.070503] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master
  control interrupt lied (SDE)!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wolsen 2493 F pulseaudio
   /dev/snd/controlC1:  wolsen 2493 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct  6 22:30:20 2015
  HibernationDevice: RESUME=UUID=096b9e95-621b-4cc7-a10c-250149e1b48b
  InstallationDate: Installed on 2015-07-15 (83 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: TOSHIBA Satellite E45-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: CA10CU
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.10:bd01/12/2015:svnTOSHIBA:pnSatelliteE45-B:pvrPSPNAU-001002:rvnTOSHIBA:rnCA10CU:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite E45-B
  dmi.product.version: PSPNAU-001002
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1503541] Re: kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] ERROR The master control interrupt lied (SDE)!"

** Attachment added: "kern.log in case its needed"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503541/+attachment/4486754/+files/kern.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/1503541

Title:
  kern.log flooded with "[drm:gen8_irq_handler [i915_bpo]] *ERROR* The
  master control interrupt lied (SDE)!"

Status in linux package in Ubuntu:
  New

Bug description:
  On an intel i5 toshiba laptop on vivid. Upgraded to the
  3.19.0-30-generic kernel and started seeing this. Additionally, bootup
  was slow.

  kern.log/dmesg is flooded with this output

  [   69.070503] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master
  control interrupt lied (SDE)!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wolsen 2493 F pulseaudio
   /dev/snd/controlC1:  wolsen 2493 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct  6 22:30:20 2015
  HibernationDevice: RESUME=UUID=096b9e95-621b-4cc7-a10c-250149e1b48b
  InstallationDate: Installed on 2015-07-15 (83 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: TOSHIBA Satellite E45-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: CA10CU
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.10:bd01/12/2015:svnTOSHIBA:pnSatelliteE45-B:pvrPSPNAU-001002:rvnTOSHIBA:rnCA10CU:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite E45-B
  dmi.product.version: PSPNAU-001002
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1253155] Re: Failure to validate module signature at boot time

2015-10-06 Thread Marc Vanhoomissen

In my case:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.3 LTS
Release:14.04
Codename:   trusty

$ uname -rv
3.13.0-65-generic #105-Ubuntu SMP Mon Sep 21 18:50:58 UTC 2015

$ dmesg | grep -i glacier
[1.764257] Loaded X.509 cert 'Magrathea: Glacier signing key: 
e1880bb8882cef95be763dfd1fabc4dc436c45ac'
[310783.576233] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11
[310783.577199] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11
[310783.583592] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11
[310783.587723] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11
[310783.589683] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11
[310783.591042] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11
[310783.592743] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11
[310783.594090] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11
[310783.595807] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11
[310783.596889] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11
[310783.598472] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11
[310783.676467] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11
[310783.881365] Request for unknown module key 'Magrathea: Glacier signing key: 
27cd636c818cdb452f9bcdff71219c6cf384f51a' err -11

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

Title:
  Failure to validate module signature at boot time

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Invalid
Status in linux-lts-raring source package in Quantal:
  Invalid
Status in linux source package in Saucy:
  Fix Released
Status in linux-lts-raring source package in Saucy:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-raring source package in Trusty:
  Invalid

Bug description:
  When booting under secureboot and using a signed kernel, it's expected
  that all modules shipped alongside the kernel should validate and load
  successfully without tainting the kernel.

  Unfortunately it doesn't seem to always be the case. Looking through
  my kernel logs, I see:

  Nov 15 10:35:24 castiana kernel: [1.635132] video: module
  verification failed: signature and/or required key missing - tainting
  kernel

  or

  Nov 12 12:58:48 castiana kernel: [213981.753326] Request for unknown
  module key 'Magrathea: Glacier signing key:
  f440a253eb498df923d438caa09b3b5d99308405' err -11

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-2-generic 3.12.0-2.7
  ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
  Uname: Linux 3.12.0-2-generic x86_64
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stgraber   2721 F pulseaudio
   /dev/snd/controlC0:  stgraber   2721 F pulseaudio
   /dev/snd/pcmC0D0c:   stgraber   2721 F...m pulseaudio
   /dev/snd/pcmC0D0p:   stgraber   2721 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 20 11:59:57 2013
  InstallationDate: Installed on 2013-04-21 (213 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130420)
  MachineType: LENOVO 2306CT0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic.efi.signed 
root=UUID=14de4e20-b139-488e-863f-ec710f776851 ro quiet splash 
"acpi_osi=!Windows 2012" vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-2-generic N/A
   linux-backports-modules-3.12.0-2-generic  N/A
   linux-firmware1.117
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CT0
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK

[Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting

** Attachment added: "Output of dmesg after next reboot"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396/+attachment/4486124/+files/dmesg-after-next-reboot.txt

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

Title:
  Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-
  lan setting

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  === Update: This bug was reported from BIOS version F13 of my board,
  in the meantime I upgraded to the most recent version F14, but this
  had no impact on the bug. ===

  Hello,

  using Suspend-to-RAM on my system has stopped working reliably on
  Vivid when booting with Systemd. When I try to suspend my PC the
  following happens:

  - PC turns off
  - PC unwantedly wakes up (turns on) by itself again. This time span until it 
turns on again can reach from a second (almost immediately) until two or three 
minutes.
  - In a few cases (<25%), the PC stays suspended properly.

  A way to workaround this problem is to boot my PC with Upstart instead
  of Systemd, then this problem never happens (and has never happened in
  any of the previous Ubuntu versions since 2008). Thus it seems to be a
  bug somehow related to Systemd.

  Other steps I have tried to solve the problem (without any success):

  - Checking BIOS settings, all options are set that way that the PC should 
never wake up by any event other than pressing the power button.
  - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device 
could cause wake up events. This lists my USB controller, but deactivating it 
(with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the 
problem. Also suspend while running Upstart works fine despite the USB 
controller listed as "enabled".

  In the system logs I could see no hint what causes the undesired wake-
  ups.

  Allthough there is one factor which seems to have a certain influence:
  If I close programs like Pidgin, Skype or Firefox that cause
  continuous network traffic, the chance is higher that my PC will stay
  suspened (while runinng Systemd).

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 11:24:46 2015
  InstallationDate: Installed on 2015-04-16 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1482343] Re: Trigger a checkstop on unrecoverable MCE/HMI errors to inform BMC/OCC about the error.

Submitted for Vivid: https://lists.ubuntu.com/archives/kernel-
team/2015-October/063607.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/1482343

Title:
  Trigger a checkstop on unrecoverable MCE/HMI errors to inform BMC/OCC
  about the error.

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  The current implementation of Machine Check handler and HMI handler in
  Linux, goes down kernel panic path for unrecoverable errors. On FSP
  based system FSP also gets notified about these errors which then
  forwards it to PRD (that runs on FSP) for error analysis and gard
  record creation.

  On OpenPower (BMC based system e.g. Habanero from TYAN) where PRD runs
  in Linux host, it never gets a chance to do error analysis at the time
  of Linux crash and no gard record is created for such errors. Since
  the faulty component never gets de-configured, the system is
  vulnerable to get hit by same HW error again.

  To fix this issue, a new OPAL call 'opal_cec_reboot2()' has been
  introduced to trigger a checkstop on BMC based system to inform
  BMC/OCC about this error, so that BMC can collect relevant data for
  error analysis and decide what component to de-configure before
  rebooting. Linux kernel should invoke this opal call for unrecoverable
  MCE and HMI instead before calling kernel panic so that OCC is
  informed about the error.

  The kernel changes has already been posted to upstream and are listed
  below:

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-May/128341.html
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-May/128342.html
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-August/132045.html
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-August/132114.html 

  Above patches needs to be included in ubuntu 14.04.3+

  We will update this bug with commit ids, once the above patches are
  accepted upstream.

  Contact Information = mahesh.salgaon...@in.ibm.com 
   
  ---uname output---
  Linux rcx2d403 3.19.0-26-generic #27 SMP Tue Aug 4 01:38:15 CDT 2015 ppc64le 
ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Habanero pass2 system 

   
  Machine Type = OpenPower, Habanero 
   
  ---System Hang---
   If system is hung, it can be recovered by sending ipmi power off/on command.
  $ ipmitool -H  -I lanplus -U  -P  power off
  $ ipmitool -H  -I lanplus -U  -P  power on

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

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

[Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting

Ok, I made a resume trace with my workaround deactivated on Kernel
4.3-rc4, while the bug (= waking up automatically) appeared.

I have attached two dmesg files: The first one contains the output
directly after resume. The second one contains the output directly after
the next reboot. I'm not sure which one is more useful in my case.

Kind regards,
Jan

** Attachment added: "Output of dmesg directly after resume"

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396/+attachment/4486123/+files/dmesg-directly-after-resume.txt

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

Title:
Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-
lan setting

Status in linux package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Triaged

Bug description:
=== Update: This bug was reported from BIOS version F13 of my board,
in the meantime I upgraded to the most recent version F14, but this
had no impact on the bug. ===

Hello,

using Suspend-to-RAM on my system has stopped working reliably on
Vivid when booting with Systemd. When I try to suspend my PC the
following happens:

- PC turns off
- PC unwantedly wakes up (turns on) by itself again. This time span until it
turns on again can reach from a second (almost immediately) until two or three
minutes.
- In a few cases (<25%), the PC stays suspended properly.

A way to workaround this problem is to boot my PC with Upstart instead
of Systemd, then this problem never happens (and has never happened in
any of the previous Ubuntu versions since 2008). Thus it seems to be a
bug somehow related to Systemd.

Other steps I have tried to solve the problem (without any success):

- Checking BIOS settings, all options are set that way that the PC should
never wake up by any event other than pressing the power button.
- Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device
could cause wake up events. This lists my USB controller, but deactivating it
(with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the
problem. Also suspend while running Upstart works fine despite the USB
controller listed as "enabled".

In the system logs I could see no hint what causes the undesired wake-
ups.

Allthough there is one factor which seems to have a certain influence:
If I close programs like Pidgin, Skype or Firefox that cause
continuous network traffic, the chance is higher that my PC will stay
suspened (while runinng Systemd).

Kind regards,
Jan

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-7ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 30 11:24:46 2015
InstallationDate: Installed on 2015-04-16 (13 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415)
MachineType: Gigabyte Technology Co., Ltd. P35-DS3
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/10/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F13
dmi.board.name: P35-DS3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-DS3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1346917] Re: Using KSM on NUMA capable machines can cause KVM guest performance and stability issues

2015-10-06 Thread Jim

This is NOT fixed by 3.13.0-33.58.  It continues to persist even with
3.13.0-65.106 (and 3.13.0-63.103).

I have around 10 VMs running but ONE in particular disconnects from the
network every hour or so.

I had this issue previously but it was initially gone on Ubuntu 14.04
LTS but had come back recently - perhaps some kernel regression ?

dmesg shows

[42524.196629] kvm: zapping shadow pages for mmio generation wraparound
[42538.140013] br0: port 2(vnet0) entered learning state
[42538.268017] br1: port 2(vnet1) entered learning state
[42553.180008] br0: topology change detected, propagating
[42553.180015] br0: port 2(vnet0) entered forwarding state
[42553.308008] br1: topology change detected, propagating
[42553.308014] br1: port 2(vnet1) entered forwarding state

(and NIC connection is gone)

It's not clear if this is just co-incidence or if this is a pointer to
the issue.

This VM is unusual in my VMs becuase it is the only one with 2 NIC
connections to br1 and br0.  All the others connect to just br0.  Those
others work OK.

Happy to try suggestions to track this down.

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

Title:
  Using KSM on NUMA capable machines can cause KVM guest performance and
  stability issues

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

Bug description:
  [Impact]

  When using KVM on NUMA machines, both Linux and Windows guests can
  exhibit very poor performance and potential crashes. Disabling KSM is
  a known workaround to fix this issue.

  [Fix]

  The following patch fixes the issue in our testing:
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=64a9a34e22896dad430e21a28ad8cb00a756fefc

  This patch is present in v3.14-rc1 and onwards.

  [Test Case]

  General test case:
  1) On a NUMA capable machine, setup the machine as a KVM hypervisor
    - lscpu should show more than 1 NUMA node
  2) Install 4 KVM VMs
  3) Run the following in another terminal to ensure that pages_shared and 
pages_sharing is increasing
   - watch 'tail /sys/kernel/mm/ksm/*'
  4) In another terminal run a program that continually pings each node and 
alerts on high latencies

  What we've observed is that in Linux guests, the ping latencies can go
  into the ~2 second range for a few pings, then return back to the <
  1ms range. (This is machine dependent.) In addition, occasionally when
  running this test with Windows guests we observe BSODs during this
  test.

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

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

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

** Tags removed: kernel-key

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

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

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-vivid package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  In Progress
Status in linux-lts-vivid source package in Vivid:
  Confirmed

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

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

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

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

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

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

[Kernel-packages] [Bug 1477466] Re: Low performance when using vlan over VxLan

2015-10-06 Thread Rafael David Tinoco

@gavin has cherry-picked some commits and we would like you to test and
provide feedback:

These are Gavin's comments:



@tinoco,

I've backported the 2 patches you mentioned in the bug description. Could 
you help to verify if the backported kernel can speed up the performance? 

The kernel source is in: 
http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=sf00088101 

The kernel package: 
http://kernel.ubuntu.com/~gavinguo/sf00088101/ 

- The first commit as following can be cleanly cherry-picked:

commit 9b174d88c257150562b0101fcc6cb6c3cb74275c 
Author: Jesse Gross  
Date: Tue Dec 30 19:10:15 2014 -0800 

net: Add Transparent Ethernet Bridging GRO support.

- The second has some conflict and I tried to fix that:

commit 66e5133f19e901a044fa5eaeeb6ecff4545839e5 
Author: Toshiaki Makita  
Date: Mon Jun 1 21:55:06 2015 +0900 

vlan: Add GRO support for non hardware accelerated vlan

- Despite I fixed the conflict, the kernel cannot be built and still need the 
commit: 

commit 0e82d0187ce8327aca20ec9e4e32ee10fbd229cb 
Author: David S. Miller  
Date: Mon Jun 1 14:56:09 2015 -0700 

net: Add priority to packet_offload objects.

Because in the Vivid kernel, there is no priority member in the 
packet_offload struct. 

Please tell me if you find anything wrong, sorry for not familiar with the 
network subsystem.



Thank you

Rafael Tinoco


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

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

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

Title:
  Low performance when using vlan over VxLan

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

Bug description:
  We see a performance issue when running traffic over vlan interface
  that created over VxLAN interface.

  We reach 24 Gbps over the VxLan interface while we reach only 4 Gbps
  over the VLAN interface.  Turned out that GRO isn't supported for VLAN
  over VxLAN.

  The following upstream commits fix this issue.

  commit 66e5133f19e901a044fa5eaeeb6ecff4545839e5
  Author: Toshiaki Makita 
  Date:   Mon Jun 1 21:55:06 2015 +0900

  vlan: Add GRO support for non hardware accelerated vlan

  Currently packets with non-hardware-accelerated vlan cannot be handled
  by GRO. This causes low performance for 802.1ad and stacked vlan, as their
  vlan tags are currently not stripped by hardware.

  This patch adds GRO support for non-hardware-accelerated vlan and
  improves receive performance of them.

  commit 9b174d88c257150562b0101fcc6cb6c3cb74275c
  Author: Jesse Gross 
  Date:   Tue Dec 30 19:10:15 2014 -0800

  net: Add Transparent Ethernet Bridging GRO support.

  Currently the only tunnel protocol that supports GRO with encapsulated
  Ethernet is VXLAN. This pulls out the Ethernet code into a proper layer
  so that it can be used by other tunnel protocols such as GRE and Geneve.

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

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

[Kernel-packages] [Bug 1502982] kern.log_bluefin_eeh

Default Comment by Bridge

** Attachment added: "kern.log_bluefin_eeh"
   
https://bugs.launchpad.net/bugs/1502982/+attachment/4486640/+files/kern.log_bluefin_eeh

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

Title:
  STCOP810:Firestone: frsfp6 EEH on Bluefin does not recover with Ubuntu

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Problem:
  ==
  Test Case Execution Record:

  95613: EEH_Firestone_Ubuntu 14.04.03_Bluefin_Standalone on frsfp6

  Error Injection Method: err_injct_inboundA

  Step 1. Start HTX (I used mdt.hdbuster & only ran htx on bluefin disks)
  Step 2. Inject EEH error

  bluefin is in slot P1-C4 (PCI0004)

   echo 0x8000 >
  /sys/kernel/debug/powerpc/PCI0004/err_injct_inboundA; sleep 1; echo
  0x0 > /sys/kernel/debug/powerpc/PCI0004/err_injct_inboundA

  Expected Result: Adapter/SAN disks to recover and htx still run

  Actual Result:  Adapter did not recover... continuous EEH errors until
  limit of 6 is reached in 1 hour

  There're two patches: one for skiboot firmware and another patch,
  which has been in upstream, was missed in ubuntu distro (at least
  15.04). The skiboot patch has been merged to upstream.

  c7192a4 PHB3: Fix wrong PE number in error injection (skiboot)
  2aa5cf9 powerpc/eeh: Fix missed PE#0 on P7IOC (linux)

  If I'm correct, I think this bug needs to be mirrored so that the
  Linux patch (commit 2aa5cf9) can be backported to ubuntu distro. With
  the patch backported to ubuntu 15.04, EEH works fine on Broadcom
  adapter (not exactly the one where the bug was reported initially):

  root@fstn2-p1:/# dmesg | grep EEH
  [0.216919] EEH: PowerNV platform initialized
  [0.570606] EEH: devices created
  [1.302482] EEH: PCI Enhanced I/O Error Handling Enabled
  [   90.566761] EEH: PHB location: Slot1
  [   90.567503] EEH: Frozen PHB#4-PE#0 detected
  [   90.567673] EEH: PE location: Slot1, PHB location: Slot1
  [   90.567930] EEH: Detected PCI bus error on PHB#4-PE#0
  [   90.567935] EEH: This PCI device has failed 1 times in the last hour
  [   90.567937] EEH: Notify device drivers to shutdown
  [   90.567985] EEH: Collect temporary log
  [   90.568971] EEH: Reset without hotplug activity
  [   94.585540] EEH: Notify device drivers the completion of reset
  [   94.585934] EEH: Notify device driver to resume

  

  The story about this bug is: Without commit 2aa5cf9 ("powerpc/eeh: Fix
  missed PE#0 on P7IOC"). PE#0 is regarded as invalid one. When kernel
  sees the frozen PE#0, the frozen state is cleared and dump the PHB
  diag-data, then try to recover it. When resetting the PE, the driver,
  which wasn't stopped by error_detected() completely, access the MMIO
  space and just causes another (recursive) EEH error. Eventually, the
  EEH recovery failed. During the PE reset, the I/O path for the PE
  should be frozen and MMIO access during the period should be dropped
  to avoid recursive EEH error.

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

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

[Kernel-packages] [Bug 1502982] syslog_bluefin_eeh

Default Comment by Bridge

** Attachment added: "syslog_bluefin_eeh"
   
https://bugs.launchpad.net/bugs/1502982/+attachment/4486639/+files/syslog_bluefin_eeh

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

Title:
  STCOP810:Firestone: frsfp6 EEH on Bluefin does not recover with Ubuntu

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Problem:
  ==
  Test Case Execution Record:

  95613: EEH_Firestone_Ubuntu 14.04.03_Bluefin_Standalone on frsfp6

  Error Injection Method: err_injct_inboundA

  Step 1. Start HTX (I used mdt.hdbuster & only ran htx on bluefin disks)
  Step 2. Inject EEH error

  bluefin is in slot P1-C4 (PCI0004)

   echo 0x8000 >
  /sys/kernel/debug/powerpc/PCI0004/err_injct_inboundA; sleep 1; echo
  0x0 > /sys/kernel/debug/powerpc/PCI0004/err_injct_inboundA

  Expected Result: Adapter/SAN disks to recover and htx still run

  Actual Result:  Adapter did not recover... continuous EEH errors until
  limit of 6 is reached in 1 hour

  There're two patches: one for skiboot firmware and another patch,
  which has been in upstream, was missed in ubuntu distro (at least
  15.04). The skiboot patch has been merged to upstream.

  c7192a4 PHB3: Fix wrong PE number in error injection (skiboot)
  2aa5cf9 powerpc/eeh: Fix missed PE#0 on P7IOC (linux)

  If I'm correct, I think this bug needs to be mirrored so that the
  Linux patch (commit 2aa5cf9) can be backported to ubuntu distro. With
  the patch backported to ubuntu 15.04, EEH works fine on Broadcom
  adapter (not exactly the one where the bug was reported initially):

  root@fstn2-p1:/# dmesg | grep EEH
  [0.216919] EEH: PowerNV platform initialized
  [0.570606] EEH: devices created
  [1.302482] EEH: PCI Enhanced I/O Error Handling Enabled
  [   90.566761] EEH: PHB location: Slot1
  [   90.567503] EEH: Frozen PHB#4-PE#0 detected
  [   90.567673] EEH: PE location: Slot1, PHB location: Slot1
  [   90.567930] EEH: Detected PCI bus error on PHB#4-PE#0
  [   90.567935] EEH: This PCI device has failed 1 times in the last hour
  [   90.567937] EEH: Notify device drivers to shutdown
  [   90.567985] EEH: Collect temporary log
  [   90.568971] EEH: Reset without hotplug activity
  [   94.585540] EEH: Notify device drivers the completion of reset
  [   94.585934] EEH: Notify device driver to resume

  

  The story about this bug is: Without commit 2aa5cf9 ("powerpc/eeh: Fix
  missed PE#0 on P7IOC"). PE#0 is regarded as invalid one. When kernel
  sees the frozen PE#0, the frozen state is cleared and dump the PHB
  diag-data, then try to recover it. When resetting the PE, the driver,
  which wasn't stopped by error_detected() completely, access the MMIO
  space and just causes another (recursive) EEH error. Eventually, the
  EEH recovery failed. During the PE reset, the I/O path for the PE
  should be frozen and MMIO access during the period should be dropped
  to avoid recursive EEH error.

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

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

[Kernel-packages] [Bug 1502982] dmesg_eeh_bluefin

Default Comment by Bridge

** Attachment added: "dmesg_eeh_bluefin"
   
https://bugs.launchpad.net/bugs/1502982/+attachment/4486638/+files/dmesg_eeh_bluefin

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

Title:
  STCOP810:Firestone: frsfp6 EEH on Bluefin does not recover with Ubuntu

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  Fix Released

Bug description:
  Problem:
  ==
  Test Case Execution Record:

  95613: EEH_Firestone_Ubuntu 14.04.03_Bluefin_Standalone on frsfp6

  Error Injection Method: err_injct_inboundA

  Step 1. Start HTX (I used mdt.hdbuster & only ran htx on bluefin disks)
  Step 2. Inject EEH error

  bluefin is in slot P1-C4 (PCI0004)

   echo 0x8000 >
  /sys/kernel/debug/powerpc/PCI0004/err_injct_inboundA; sleep 1; echo
  0x0 > /sys/kernel/debug/powerpc/PCI0004/err_injct_inboundA

  Expected Result: Adapter/SAN disks to recover and htx still run

  Actual Result:  Adapter did not recover... continuous EEH errors until
  limit of 6 is reached in 1 hour

  There're two patches: one for skiboot firmware and another patch,
  which has been in upstream, was missed in ubuntu distro (at least
  15.04). The skiboot patch has been merged to upstream.

  c7192a4 PHB3: Fix wrong PE number in error injection (skiboot)
  2aa5cf9 powerpc/eeh: Fix missed PE#0 on P7IOC (linux)

  If I'm correct, I think this bug needs to be mirrored so that the
  Linux patch (commit 2aa5cf9) can be backported to ubuntu distro. With
  the patch backported to ubuntu 15.04, EEH works fine on Broadcom
  adapter (not exactly the one where the bug was reported initially):

  root@fstn2-p1:/# dmesg | grep EEH
  [0.216919] EEH: PowerNV platform initialized
  [0.570606] EEH: devices created
  [1.302482] EEH: PCI Enhanced I/O Error Handling Enabled
  [   90.566761] EEH: PHB location: Slot1
  [   90.567503] EEH: Frozen PHB#4-PE#0 detected
  [   90.567673] EEH: PE location: Slot1, PHB location: Slot1
  [   90.567930] EEH: Detected PCI bus error on PHB#4-PE#0
  [   90.567935] EEH: This PCI device has failed 1 times in the last hour
  [   90.567937] EEH: Notify device drivers to shutdown
  [   90.567985] EEH: Collect temporary log
  [   90.568971] EEH: Reset without hotplug activity
  [   94.585540] EEH: Notify device drivers the completion of reset
  [   94.585934] EEH: Notify device driver to resume

  

  The story about this bug is: Without commit 2aa5cf9 ("powerpc/eeh: Fix
  missed PE#0 on P7IOC"). PE#0 is regarded as invalid one. When kernel
  sees the frozen PE#0, the frozen state is cleared and dump the PHB
  diag-data, then try to recover it. When resetting the PE, the driver,
  which wasn't stopped by error_detected() completely, access the MMIO
  space and just causes another (recursive) EEH error. Eventually, the
  EEH recovery failed. During the PE reset, the I/O path for the PE
  should be frozen and MMIO access during the period should be dropped
  to avoid recursive EEH error.

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

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

[Kernel-packages] [Bug 1503021] Re: linux: 3.13.0-66.107 -proposed tracker

2015-10-06 Thread Chris J Arges

Promoted to proposed:
 linux| 3.13.0-66.107 | trusty-proposed  | source
 linux-meta   | 3.13.0.66.72  | trusty-proposed  | source
 linux-signed | 3.13.0-66.107 | trusty-proposed  | source

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => 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/1503021

Title:
  linux: 3.13.0-66.107 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 05. October 2015 19:56 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 04:03 UTC
  kernel-stable-phase-changed:Tuesday, 06. October 2015 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 03:02 UTC

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

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

[Kernel-packages] [Bug 1501818] Re: linux: 4.2.0-14.16 -proposed tracker

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


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

** Description changed:

  This bug is for tracking the 4.2.0-14.16 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC
- kernel-phase-changed:Thursday, 01. October 2015 15:57 UTC
- kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC
  proposed-announcement-sent:True
  kernel-Promote-to-release-end:Wednesday, 07. October 2015 02:00 UTC
+ kernel-phase-changed:Wednesday, 07. October 2015 03:00 UTC
+ kernel-Prepare-package-end:Wednesday, 07. October 2015 03:00 UTC
+ kernel-Package-testing-start:Wednesday, 07. October 2015 03:00 UTC
+ kernel-phase:Released

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

Title:
  linux: 4.2.0-14.16 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Thursday, 01. October 2015 15:57 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 01. October 2015 16:00 UTC
  proposed-announcement-sent:True
  kernel-Promote-to-release-end:Wednesday, 07. October 2015 02:00 UTC
  kernel-phase-changed:Wednesday, 07. October 2015 03:00 UTC
  kernel-Prepare-package-end:Wednesday, 07. October 2015 03:00 UTC
  kernel-Package-testing-start:Wednesday, 07. October 2015 03:00 UTC
  kernel-phase:Released

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

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

[Kernel-packages] [Bug 1503005] Re: linux: 3.19.0-31.35 -proposed tracker

2015-10-06 Thread Chris J Arges

Promoted to proposed:
 linux| 3.19.0-31.35  | vivid-proposed   | source
 linux-meta   | 3.19.0.31.30  | vivid-proposed   | source
 linux-signed | 3.19.0-31.35  | vivid-proposed   | source

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => 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/1503005

Title:
  linux: 3.19.0-31.35 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 05. October 2015 18:56 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-phase-changed:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 03:02 UTC

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

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

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

** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-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/1499357

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

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

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

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

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

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

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

  -

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

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

  2) Here are all the 'ibm,msi-ranges' properties found:
  0 > showprops -i ibm,msi-ranges 
  /pci@8002014/ethernet@0 3be0 0001
  /pci@8002014/ethernet@0,1   3be1 0001
  /pci@8002014/ethernet@0,2   3be2 0001
  /pci@8002014/ethernet@0,3   3be3 0001
  /pci@8002015/pci1014,034A@0 3820 0001
  /pci@8002018/pci@0/pci@2/fibre-channel@01000 0001
  /pci@8002018/pci@0/pci@2/fibre-channel@0,1  1001 0001
  /pci@8002018/pci@0/pci@3/fibre-channel@01002 0001
  /pci@8002018/pci@0/pci@3/fibre-channel@0,1  1003 0001
  /pci@800201b/usb@0  1fa0 0001
  /pci@800201e/ethernet@0 1ce0 0001
  /pci@800201e/ethernet@0,1   1ce1 0001
  /pci@800201e/ethernet@0,2   1ce2 0001
  /pci@800201e/ethernet@0,3   1ce3 0001
  /pci@8002029/pci@0/pci@2/fibre-channel@02000 0001
  /pci@8002029/pci@0/pci@2/fibre-channel@0,1  2001 0001
  /pci@8002029/pci@0/pci@3/fibre-channel@02002 0001
  /pci@8002029/pci@0/pci@3/fibre-channel@0,1  2003 0001

  3) Here are all the 'interrupts' properties found:
  0 > showprops -i interrupts 
  /event-sources/epow-events  00090001 
  /vdevice/vty@3000   000a 
  /vdevice/vty@3001   000a0001 
  /vdevice/ibm,vmc@3002

[Kernel-packages] [Bug 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails

** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-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/1499869

Title:
  maas wily deployment to HP Proliant m400 arm64 server cartridge fails

Status in cloud-init:
  Confirmed
Status in curtin:
  New
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed
Status in cloud-init source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  This is the error seen on the console:

  [   64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: 
Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin
  [  124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - 
url_helper.py[WARNING]: Calling 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
[2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', 
port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id 
(Caused by 
ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect 
timeout=50.0)'))]
  [  124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - 
DataSourceEc2.py[CRITICAL]: Giving up on md from 
['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds
  [  124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - 
url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404]

  This times out eventually and the node is left at the login prompt. I
  can install wily via netboot without issue and some time back, wily
  was deployable to this node from MAAS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1499869/+subscriptions

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

[Kernel-packages] [Bug 1496073] Re: Request cherry-pick of upstream kernel patch which caps SECCOMP_RET_ERRNO to MAX_ERRNO

** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-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/1496073

Title:
  Request cherry-pick of upstream kernel patch which caps
  SECCOMP_RET_ERRNO to MAX_ERRNO

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

Bug description:
  The seccomp regression tests are failing due to SRU kernels not having
  the relevant commit:

  Author: Kees Cook 
  Date:   Tue Feb 17 13:48:00 2015 -0800

  seccomp: cap SECCOMP_RET_ERRNO data to MAX_ERRNO

  The value resulting from the SECCOMP_RET_DATA mask could exceed MAX_ERRNO
  when setting errno during a SECCOMP_RET_ERRNO filter action.  This makes
  sure we have a reliable value being set, so that an invalid errno will not
  be ignored by userspace.

  Signed-off-by: Kees Cook 
  Reported-by: Dmitry V. Levin 
  Cc: Andy Lutomirski 
  Cc: Will Drewry 
  Signed-off-by: Andrew Morton 
  Signed-off-by: Linus Torvalds 

  SRU Justification

  Impact:
  Upstream regression tests are reporting errors.

  Test Case:
  Run the upstream regression tests and verify they are passing
  cleanly.

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

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

[Kernel-packages] [Bug 1494357] Re: [SRU] Add X-Gene EDAC Driver

** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-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/1494357

Title:
  [SRU] Add X-Gene EDAC Driver

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

Bug description:
  [Impact]
  APM's X-Gene Mustang board supports EDAC, which is unsupported by all 
versions of Ubuntu prior to wily.

  [Test Case]
  Look in /var/log/kern.log for messages from the loading of the EDAC driver.

  [Regression Risk]
  The changes contain some core EDAC cleanup that affects all architectures, 
but not functionally, just build time and the X-Gene EDAC driver itself.

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

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

[Kernel-packages] [Bug 1503105] Re: linux-armadaxp: 3.2.0-1657.79 -proposed tracker

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

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.2.0-1657.79 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 03:02 UTC
  kernel-stable-master-bug:1500854
  kernel-stable-Certification-testing-end:Tuesday, 06. October 2015 06:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 06. October 2015 06:01 UTC
- kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 08:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 08:01 UTC
- kernel-stable-phase-changed:Tuesday, 06. October 2015 08:01 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 01:50 UTC
+ kernel-stable-phase:Verification & Testing
+ kernel-stable-phase-changed:Wednesday, 07. October 2015 03:03 UTC
+ kernel-stable-Verification-testing-start:Wednesday, 07. October 2015 03:03 UTC
+ proposed-announcement-sent:True
+ kernel-stable-Regression-testing-start:Wednesday, 07. October 2015 03:03 UTC

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

Title:
  linux-armadaxp: 3.2.0-1657.79 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 03:02 UTC
  kernel-stable-master-bug:1500854
  kernel-stable-Certification-testing-end:Tuesday, 06. October 2015 06:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 06. October 2015 06:01 UTC
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 08:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 08:01 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 01:50 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 07. October 2015 03:03 UTC
  kernel-stable-Verification-testing-start:Wednesday, 07. October 2015 03:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 07. October 2015 03:03 UTC

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

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

[Kernel-packages] [Bug 1493017] Re: [LTCTest][Opal][OP810] Need to have the patches for Inband IPMI HPM upgrade to work

** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-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/1493017

Title:
  [LTCTest][Opal][OP810] Need to have the patches for Inband IPMI HPM
  upgrade to work

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

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2015-08-11 
01:09:54 ==
  ---Problem Description---
  Need to have the patches for Inband IPMI HPM upgrade to work
   
  Contact Information = pavsu...@in.ibm.com 
   
  ---uname output---
  Linux p7pite26os 3.19.0-26-generic #27~14.04.1-Ubuntu SMP Wed Jul 29 16:50:33 
UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a PowerNV 8335-GTA Hardware with Ubuntu 14.04.3 Netboot images.
  We want to try out Inband IPMI HPM firmware upgrade using ipmitool.
  So for this to work we require the mentioned patches to be back-ported.

  1) 64c862a839a8db2c02bbaa88b923d13e1208919d
  Subject: devres: add kernel standard devm_k.alloc functions
  2) 6357882a38c5e5a78fb055aa932e1daa0bef47e0
  Subject: powerpc/powernv: Add OPAL IPMI interface
  2) 6a11e5c67a397e9a64cfde6961c83a7a64d7980c 
  Subject: drivers/char/ipmi: Add powernv IPMI driver") because the 
ipmi_register_smi  interface
  3) 8b80e2e4a7103ef900ff17169542de28bad6af9e 
  Subject: ipmi/powernv: Fix minor locking bug

  This bug is related to the original bug:
   https://bugzilla.linux.ibm.com/show_bug.cgi?id=128130

   
  Userspace tool common name: /usr/bin/ipmitool 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: ipmitool-1.8.13-1

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for pavsu...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  == Comment: #12 - Breno Henrique Leitao  - 2015-08-17 
06:02:36 ==
  I understand that the ubuntu 15.10 ipmitool package contains the hpm fixes as 
the USB feature enabled already. Can you confirm it?

  == Comment: #13 - PAVAMAN SUBRAMANIYAM  - 2015-08-25 
06:34:12 ==
  I have installed a Open Power P8 Hardware with Ubuntu 15.10 latest release.

  root@ltc-fire13:~# uname -a
  Linux ltc-fire13 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:23:44 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
  root@ltc-fire13:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="15.10 (Wily Werewolf)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Wily Werewolf (development branch)"
  VERSION_ID="15.10"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;

  
  root@ltc-fire13:~# which ipmitool
  /usr/bin/ipmitool
  root@ltc-fire13:~# dpkg -S /usr/bin/ipmitool
  ipmitool: /usr/bin/ipmitool
  root@ltc-fire13:~# dpkg --list | grep ipmitool
  ii  ipmitool  1.8.15-1ubuntu1 ppc64el 
 utility for IPMI control with kernel driver or LAN interface (daemon)

  
  root@ltc-fire13:~# ipmitool -I usb
  No command provided!
  Commands:
  raw   Send a RAW IPMI request and print response
  i2c   Send an I2C Master Write-Read command and print response
  spd   Print SPD info from remote I2C device
  lan   Configure LAN Channels
  chassis   Get chassis status and set power state
  power Shortcut to chassis power commands
  event Send pre-defined events to MC
  mcManagement Controller status and global enables
  sdr   Print Sensor Data Repository entries and readings
  sensorPrint detailed sensor information
  fru   Print built-in FRU and scan SDR for FRU locators
  gendevRead/Write Device associated with Generic Device 
locators sdr
  sel   Print System Event Log (SEL)
  pef   Configure Platform Event Filtering (PEF)
  sol   Configure and connect IPMIv2.0 Serial-over-LAN
  tsol  Configure and connect with Tyan IPMIv1.5 Serial-over-LAN
  isol  Configure IPMIv1.5 Serial-over-LAN
  user  Configure Management Controller users
  channel   Configure Management Controller channels
  session   Print session information
  dcmi  Data Center Management Interface
  sunoemOEM Commands for Sun servers
  kontronoemOEM Commands for Kontron devices
  picmg Run a PICMG/ATCA extended cmd
  fwum

[Kernel-packages] [Bug 1503021] Re: linux: 3.13.0-66.107 -proposed tracker

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

** Description changed:

  This bug is for tracking the 3.13.0-66.107 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 05. October 2015 19:56 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 04:03 UTC
  kernel-stable-phase-changed:Tuesday, 06. October 2015 04:03 UTC
+ kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 03:02 UTC

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

Title:
  linux: 3.13.0-66.107 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 05. October 2015 19:56 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 04:03 UTC
  kernel-stable-phase-changed:Tuesday, 06. October 2015 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 03:02 UTC

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

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

[Kernel-packages] [Bug 1500493] Re: Vivid update to 3.19.8-ckt7 stable release

** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-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/1500493

Title:
  Vivid update to 3.19.8-ckt7 stable release

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

Bug description:
  SRU Justification

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

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

  TEST CASE: TBD

     The following patches are in the 3.19.8-ckt7 stable release:

  x86/ldt: Make modify_ldt synchronous
  x86/ldt: Correct LDT access in single stepping logic
  x86/ldt: Correct FPU emulation access to LDT
  md: flush ->event_work before stopping array.
  ipv6: addrconf: validate new MTU before applying it
  virtio-net: drop NETIF_F_FRAGLIST
  RDS: verify the underlying transport exists before creating a connection
  xen/gntdev: convert priv->lock to a mutex
  xen/gntdevt: Fix race condition in gntdev_release()
  PCI: Restore PCI_MSIX_FLAGS_BIRMASK definition
  USB: qcserial/option: make AT URCs work for Sierra Wireless MC7305/MC7355
  USB: qcserial: Add support for Dell Wireless 5809e 4G Modem
  nfsd: Drop BUG_ON and ignore SECLABEL on absent filesystem
  usb: chipidea: ehci_init_driver is intended to call one time
  crypto: qat - Fix invalid synchronization between register/unregister sym algs
  crypto: ixp4xx - Remove bogus BUG_ON on scattered dst buffer
  mfd: arizona: Fix initialisation of the PM runtime
  xen-blkfront: don't add indirect pages to list when !feature_persistent
  xen-blkback: replace work_pending with work_busy in purge_persistent_gnt()
  usb: gadget: f_uac2: fix calculation of uac2->p_interval
  hwrng: core - correct error check of kthread_run call
  USB: sierra: add 1199:68AB device ID
  regmap: regcache-rbtree: Clean new present bits on present bitmap resize
  target/iscsi: Fix double free of a TUR followed by a solicited NOPOUT
  rbd: fix copyup completion race
  md/raid1: extend spinlock to protect raid1_end_read_request against 
inconsistencies
  target: REPORT LUNS should return LUN 0 even for dynamic ACLs
  MIPS: Fix sched_getaffinity with MT FPAFF enabled
  MIPS: Malta: Don't reinitialise RTC
  MIPS: do_mcheck: Fix kernel code dump with EVA
  MIPS: show_stack: Fix stack trace with EVA
  MIPS: Export get_c0_perfcount_int()
  rtlwifi: rtl8723be: Add module parameter for MSI interrupts
  MIPS: Flush RPS on kernel entry with EVA
  usb: udc: core: add device_del() call to error pathway
  xhci: fix off by one error in TRB DMA address boundary check
  drivers/usb: Delete XHCI command timer if necessary
  staging: vt6655: vnt_bss_info_changed check conf->beacon_rate is not NULL
  dm: fix dm_merge_bvec regression on 32 bit systems
  perf: Fix fasync handling on inherited events
  drm/dp-mst: Remove debug WARN_ON
  ALSA: fireworks/firewire-lib: add support for recent firmware quirk
  mm, vmscan: Do not wait for page writeback for GFP_NOFS allocations
  MIPS: Make set_pte() SMP safe.
  ipc: modify message queue accounting to not take kernel data structures into 
account
  ocfs2: fix BUG in ocfs2_downconvert_thread_do_work()
  fsnotify: fix oops in fsnotify_clear_marks_by_group_flags()
  KVM: x86: Use adjustment in guest cycles when handling MSR_IA32_TSC_ADJUST
  x86/xen: build "Xen PV" APIC driver for domU as well
  cpuset: use trialcs->mems_allowed as a temp variable
  drm/dp/mst: Remove port after removing connector.
  localmodconfig: Use Kbuild files too
  dm thin metadata: delete btrees when releasing metadata snapshot
  dm btree: add ref counting ops for the leaves of top level btrees
  drm/radeon: add new OLAND pci id
  libiscsi: Fix host busy blocking during connection teardown
  libfc: Fix fc_exch_recv_req() error path
  libfc: Fix fc_fcp_cleanup_each_cmd()
  sd: Fix maximum I/O size for BLOCK_PC requests
  EDAC, ppc4xx: Access mci->csrows array elements properly
  crypto: caam - fix memory corruption in ahash_final_ctx
  drm/vmwgfx: Fix execbuf locking issues
  mm/hwpoison: fix page refcount of unknown non LRU page
  ipc,sem: fix use after free on IPC_RMID after a task using same semaphore set 
exits
  ipc/sem.c: update/correct memory barriers
  MIPS: Fix seccomp syscall argument for MIPS64
  x86/ldt: Further fix FPU emulation
  drm/i915: Flag the execlists context object as dirty after every use
  fnic: Use the local variable instead of I/O flag to acquire io_req_lock in 
fnic_queuecommand() to avoid deadloack
  SCSI: Fix NULL

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

** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-vivid

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 05:00 UTC
  kernel-stable-master-bug:1503005
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 20:02 UTC
  kernel-stable-phase-changed:Tuesday, 06. October 2015 20:02 UTC

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

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

[Kernel-packages] [Bug 1503005] Re: linux: 3.19.0-31.35 -proposed tracker

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

** Description changed:

  This bug is for tracking the 3.19.0-31.35 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 05. October 2015 18:56 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-phase-changed:Tuesday, 06. October 2015 05:02 UTC
+ kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 03:02 UTC

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

Title:
  linux: 3.19.0-31.35 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 05. October 2015 18:56 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-phase-changed:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 03:02 UTC

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

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

[Kernel-packages] [Bug 1496430] Re: Docker-1.8.2 can't create container, due to apparmor denying 'disconnected path'

** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-vivid

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

Title:
  Docker-1.8.2 can't create container, due to apparmor denying
  'disconnected path'

Status in AppArmor:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Incomplete
Status in linux-lts-utopic source package in Wily:
  Invalid

Bug description:
  I'm trying to get docker-1.8.2-rc1 to work on snappy, while doing so I
  got this apparmor denial:

  Sep 10 09:12:35 localhost.localdomain audit[1320]: AVC
  apparmor="DENIED" operation="mount" info="Failed name lookup -
  disconnected path" error=-13 profile="docker_docker-
  daemon_IAUSSaDNVTJR" name="/run/docker/netns/6901f2b6dd4c/" pid=1320
  comm="exe" srcname="" flags="rw, bind"

  and trying to chase it I got:
  http://paste.ubuntu.com/12341612/

  so docker is trying to issue this mount: 
  syscall.Mount("/proc/self/ns/net", /var/run/docker/netns/5b9b1ba4437b, 
"bind", 4096 (syscall.MS_BIND), "")

  from https://golang.org/pkg/syscall/#Mount
  func Mount(source string, target string, fstype string, flags uintptr, data 
string) (err error)

  which is denied as if there wasn't a source?

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

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

[Kernel-packages] [Bug 1472843] Re: [O2Micro 1217:8621] MMC plus card failed to be inited

** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-vivid

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

Title:
  [O2Micro 1217:8621] MMC plus card failed to be inited

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-utopic package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  Actual result:
  MMC  plus card could not be auto-mounted.

  Expect result:
  MMC  plus card is mounted.

  Note: there is a way could mount MMC  plus card automatically.
  Power on and log in system -> plug in SD card -> SD card mounted -> eject SD 
card -> plug in MMC  plus card, system will mount MMC  plus card automatically.

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

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.2.0-92.130 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 29. September 2015 12:55 UTC
- kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 03:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 03:03 UTC
- kernel-stable-phase-changed:Tuesday, 06. October 2015 03:03 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 01:50 UTC
+ kernel-stable-phase:Verification & Testing
+ kernel-stable-phase-changed:Wednesday, 07. October 2015 03:01 UTC
+ kernel-stable-Verification-testing-start:Wednesday, 07. October 2015 03:01 UTC
+ kernel-stable-Certification-testing-start:Wednesday, 07. October 2015 03:01 
UTC
+ kernel-stable-Security-signoff-start:Wednesday, 07. October 2015 03:01 UTC
+ proposed-announcement-sent:True
+ kernel-stable-Regression-testing-start:Wednesday, 07. October 2015 03:01 UTC

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

Title:
  linux: 3.2.0-92.130 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 29. September 2015 12:55 UTC
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 03:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 03:03 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 01:50 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 07. October 2015 03:01 UTC
  kernel-stable-Verification-testing-start:Wednesday, 07. October 2015 03:01 UTC
  kernel-stable-Certification-testing-start:Wednesday, 07. October 2015 03:01 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 07. October 2015 03:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 07. October 2015 03:01 UTC

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

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

[Kernel-packages] [Bug 1498778] Re: cpu hot-remove fails with nvme device

** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-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/1498778

Title:
  cpu hot-remove fails with nvme device

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  Using cpu hotplug to disable (offline) a cpu:
  echo 0 > /sys/devices/system/cpu/cpu10/online
  does not return.

  Machine is usable, and cpu10 is marked as offline, but any test
  scripts hangs because the "echo 0" never returned.

  Doing bisect pointed to this commit id: a4aea5623d "NVMe: Convert to blk-mq"
  Indeed, the test machine in question has an NVMe card.
  Doing "rmmod nvme" and then disabling cpus works.

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

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

[Kernel-packages] [Bug 1485528] Re: perf probe: ppc64le/ABIv2 support

** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-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/1485528

Title:
  perf probe: ppc64le/ABIv2 support

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

Bug description:
  Problem Description
  
  perf probe does not work properly on ppc64le

  ---uname output---
  Linux ubuntu1504 3.19.0-22-generic #22-Ubuntu SMP Tue Jun 16 17:15:17 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = POWER 

  Steps to Reproduce
  
   'perf probe do_fork' adds the probe, but is not able to capture events on 
'perf record -e probe:do_fork -a'. This is because ppc64le ABIv2 uses local 
entry points at an offset from the global entry point where the probe is 
currently being placed.

  These issues have been fixed upstream with the below patch series:
  - http://thread.gmane.org/gmane.linux.kernel/1939488
  - http://thread.gmane.org/gmane.linux.kernel/1941352

  == Comment: #1 - Naveen N. Rao  - 2015-07-01 
07:03:19 ==
  I have backported the patches relevant for ppc64le and I am attaching them 
here. These fixes are needed for 15.04, 14.04.03 and 15.10 (depending on the 
kernel it gets based on). For reference, upstream commits in -tip for reference:
  - d4c537e6bf860c12262cb936eef663180d7a3d45: perf probe: Ignore tail calls to 
probed functions
  - 3099c026002e97b8c173d9d0bbdfc39257d14402: perf probe: Improve detection of 
file/function name in the probe pattern
  - 7b6ff0bdbf4f7f429c2116cca92a6d171217449e: perf probe ppc64le: Fixup 
function entry if using kallsyms lookup
  - d5c2e2c17ae1d630ddbceb53a264f24cc99703a4: perf probe ppc64le: Prefer symbol 
table lookup over DWARF
  - c50fc0a43e33a6c3257c5cbb954cd747d7b9a680: perf probe ppc64le: Fix ppc64 
ABIv2 symbol decoding
  - 031b84c407c3153ffbcb4f8f832edf48af988719: perf probe ppc: Enable matching 
against dot symbols automatically
  - fb6d59423115b10125f5db6acb8471f6f0af4ad7: perf probe ppc: Use the right 
prefix when ignoring SyS symbols on ppc
  - d2332098331fffe9358b50cebc8954ecd6560448: perf probe ppc: Fix symbol fixup 
issues due to ELF type

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

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

[Kernel-packages] [Bug 1503005] Re: linux: 3.19.0-31.35 -proposed tracker

Here's the relevant information:

vivid linux 3.19.0-31.35 REGR summary

Please verify test results in http://people.canonical.com/~kernel/status
/adt-matrix/overall.txt


** Changed in: kernel-sru-workflow/automated-testing
   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/1503005

Title:
  linux: 3.19.0-31.35 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 05. October 2015 18:56 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-phase-changed:Tuesday, 06. October 2015 05:02 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 03:02 UTC

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

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

[Kernel-packages] [Bug 1503021] Re: linux: 3.13.0-66.107 -proposed tracker

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

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.13.0-66.107 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 05. October 2015 19:56 UTC
- kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 04:03 UTC
- kernel-stable-phase-changed:Tuesday, 06. October 2015 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 03:02 UTC
+ kernel-stable-phase:Verification & Testing
+ kernel-stable-phase-changed:Wednesday, 07. October 2015 04:02 UTC
+ kernel-stable-Verification-testing-start:Wednesday, 07. October 2015 04:02 UTC
+ kernel-stable-Certification-testing-start:Wednesday, 07. October 2015 04:02 
UTC
+ kernel-stable-Security-signoff-start:Wednesday, 07. October 2015 04:02 UTC
+ proposed-announcement-sent:True
+ kernel-stable-Regression-testing-start:Wednesday, 07. October 2015 04:02 UTC

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

Title:
  linux: 3.13.0-66.107 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 05. October 2015 19:56 UTC
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 04:03 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 04:03 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 07. October 2015 03:02 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 07. October 2015 04:02 UTC
  kernel-stable-Verification-testing-start:Wednesday, 07. October 2015 04:02 UTC
  kernel-stable-Certification-testing-start:Wednesday, 07. October 2015 04:02 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 07. October 2015 04:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 07. October 2015 04:02 UTC

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

2015-10-06 Thread kashyap

We are in process of submit patches to upstream. We are waiting for few
older patch series to get committed, otherwise there will be a confusion
over series of patches and we may not see clean commit. Once we post
patch for this issue, I will update the BZ with commit id or link
pointing to upstream submit.

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1503399] [NEW] Fn+F2 is not working for activating/deactivating wifi.

2015-10-06 Thread Xorso

Public bug reported:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1277959

Solved thanks to:
http://ubuntuforums.org/showthread.php?t=2181558

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: 
boot/vmlinuz-3.19.0-15-generic]
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  xoran  1252 F pulseaudio
 /dev/snd/pcmC1D0p:   xoran  1252 F...m pulseaudio
 /dev/snd/controlC1:  xoran  1252 F pulseaudio
CurrentDesktop: Unity
Date: Tue Oct  6 19:21:32 2015
HibernationDevice: RESUME=UUID=cecf930e-9733-4ea4-9069-7fb8bde50e0b
InstallationDate: Installed on 2015-10-05 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: ASUSTeK COMPUTER INC. B451JA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic 
root=UUID=2d9badae-0172-4d9d-bd19-8e3bcafd55ad ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-15-generic N/A
 linux-backports-modules-3.19.0-15-generic  N/A
 linux-firmware 1.143
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/06/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: B451JA.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: B451JA
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.:bvrB451JA.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnB451JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnB451JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: B451JA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug 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/1503399

Title:
  Fn+F2 is not working for activating/deactivating wifi.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1277959

  Solved thanks to:
  http://ubuntuforums.org/showthread.php?t=2181558

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: 
boot/vmlinuz-3.19.0-15-generic]
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xoran  1252 F pulseaudio
   /dev/snd/pcmC1D0p:   xoran  1252 F...m pulseaudio
   /dev/snd/controlC1:  xoran  1252 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct  6 19:21:32 2015
  HibernationDevice: RESUME=UUID=cecf930e-9733-4ea4-9069-7fb8bde50e0b
  InstallationDate: Installed on 2015-10-05 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. B451JA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic 
root=UUID=2d9badae-0172-4d9d-bd19-8e3bcafd55ad ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B451JA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: B451JA
  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.:bvrB451JA.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnB451JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnB451JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: B451JA
  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/1503399/+subscriptions

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

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

Craig - shall I revert the arm64 NUMA patches ?

** Also affects: linux (Ubuntu Wily)
   Importance: Critical
   Status: Confirmed

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

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

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

Title:
  kernel crash on m400 arm64 server cartridge

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

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1501876] Re: Cisco Linksys AE1000 rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0500 with error -71

2015-10-06 Thread Jonathan Brier

I ran into the same issue with the latest mainline kernel
4.3.0-040300rc3-generic.

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

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

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

Title:
  Cisco Linksys AE1000 rt2x00usb_vendor_request: Error - Vendor Request
  0x07 failed for offset 0x0500 with error -71

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the University of Maryland College Park Campus I am experiencing
  wifi connectivity issues where I get an initial connection, but it
  will drop frequently and have difficulty reconnecting to this secured
  wifi. This is at multiple locations on campus, but not off campus that
  I've found at this time. My Android Phone and Tablet do not have wifi
  issues connecting. Today I tried to work around the build in WiFi by
  adding the USB adapter Linksys AE1000. It was working for a while
  until it lost connection like the build in wifi on this laptop.

  After the loss of connection I saw a repeated:
  ieee80211 phy1: rt2x00usb_regbusy_read: Error - Indirect register access 
failed: offset=0x0500, value=0x8804

  ieee80211 phy1: rt2x00usb_vendor_request: Error - Vendor Request 0x07
  failed for offset 0x0500 with error -71

  Before the wifi connection loss I saw repeated:
  ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status 
read failed -71

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.33
  ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jonathan   2145 F pulseaudio
   /dev/snd/controlC0:  jonathan   2145 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct  1 15:10:34 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-29 (244 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141015)
  MachineType: Hewlett-Packard HP ENVY TS 15 Notebook PC
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=1cc26cb0-3476-4abf-a12e-acac53ba8537 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-06 (177 days ago)
  dmi.bios.date: 01/26/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 198A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.14
  dmi.chassis.asset.tag: 5CG32129MN
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.19:bd01/26/2015:svnHewlett-Packard:pnHPENVYTS15NotebookPC:pvr088810305B032:rvnHewlett-Packard:rn198A:rvrKBCVersion03.14:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY TS 15 Notebook PC
  dmi.product.version: 088810305B032
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://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 1497494] Re: package linux-image-extra-3.13.0-54-generic 3.13.0-54.91 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2015-10-06 Thread Tom

Dear Mr. Salisbury,
 True problem I'm having: Kubuntu default install makes the /boot
partition TOO SMALL.
 My Kubuntu /boot partition is  only 243MiB. This was the default
Kubuntu install.  The /boot partition is too small. Now, the Kubuntu
"Software Updater" demands 403M free space. Below is quoted from an email I
sent to another about the problem:

BEGIN QUOTE
"2) Ran Software Updater;
Selected "Partial Update" as a message indicated a full update wouldn't
work because of partial install problem;
Received error message demanding 403 M of free space on the disk /boot:
"Not enough free disk space"
"The upgrade has aborted. The upgrade needs a total of 403 M free space on
disk '/boot'. Please free at least an additional 337 M of disk space on
'/boot'. Empty your trash and remove temporary packages of former
installations using 'sudo apt-get clean'."

The Partial updater wants "403 M" free space in /Boot.  Is that 403 MB?
The root /boot folder is only a folder of 3.1kB, but it contains files of
12.6kB, etc. ???

Question: what does 403 M mean?  403,000 ???
___
3) Launched KDE Partition Manager: requires pwrd:
It states that the
Partition= /dev/sda1/, Type= ext2, Mount Point= /boot, Size= 243.00 MiB,
Used= 159.64 MiB, Flags= boot
therefore has free space of (243.00 - 159.64) = 83.36 MiB.
If per the error message, we add 337 M = 420.36 MiB ???
___
4) In other words, the /boot partition at 243.00 MiB is too small for
updates even if empty???
END QUOTE

Thank you very much.  Tom Turner

On Mon, Sep 21, 2015 at 2:46 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1497494
>
> Title:
>   package linux-image-extra-3.13.0-54-generic 3.13.0-54.91 failed to
>   install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
>   exited with return code 1
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   >My /boot partition is full because it contains partially installed
> versions of linux. I have been using
>   == sudo apt-get update ;
>   == sudo-apt-get upgrade .
>   >Those need to be updated to delete old versions of Linux when
> installing a new one.  At least they could ask the user what to do.  In the
> future I will use:
>   == sudo apt-get autoclean
>   == sudo apt-get clean
>   == sudo apt-get autoremove
>   == sudo apt-get update
>   == sudo apt-get upgrade -f
>   == sudo apt-get autoclean
>   == sudo apt-get clean
>   == sudo apt-get autoremove
>   >In the meantime, I cannot install new software that uses the /boot
> partition. Linux isn't ready for prime time. It shoots itself in the foot.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-extra-3.13.0-54-generic 3.13.0-54.91
>   ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
>   Uname: Linux 3.13.0-48-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.8
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  lightdm1753 F pulseaudio
> rusty  2305 F pulseaudio
>   Date: Fri Sep 18 18:59:54 2015
>   DuplicateSignature:
> package:linux-image-extra-3.13.0-54-generic:3.13.0-54.91:run-parts:
> /etc/kernel/postinst.d/initramfs-tools exited with return code 1
>   ErrorMessage: subprocess installed post-removal script returned error
> exit status 1
>   HibernationDevice: RESUME=UUID=e0431ec2-ad1c-49a4-9c1c-8f751a6b06dd
>   InstallationDate: Installed on 2014-12-06 (286 days ago)
>   InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64
> (20140416.1)
>   MachineType: Dell Inc. Latitude D620
>   PccardctlIdent:
>Socket 0:
>  no product info available
>   PccardctlStatus:
>Socket 0:
>  no card
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic
> root=/dev/mapper/kubuntu--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-9ubuntu1
>   SourcePackage: linux
>   Title: package linux-image-extra-3.13.0-54-generic 3.13.0-54.91 failed
> to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
> exited with return code 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   WifiSyslog:
>Sep 18 16:47:10 rusty-Latitude-D620 kernel: [ 2078.698396] perf samples
> too long (2524 > 2500), lowering kernel.perf_event_max_sample_rate to 5
>Sep 18 17:35:56 rusty-Latitude-D620 kernel: [ 5004.337460] perf samples
> too long (5017 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
>Sep 18 18:57:50 rusty-Latitude-D620 NetworkManager[935]:  kernel
> firmware directory '/lib/firmware' changed
>   dmi.bios.date:

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

Can you see if the crash still occurs if you boot with the 4.2.0-12.14 kernel?  
It can be downloaded from:
https://launchpad.net/ubuntu/+source/linux/4.2.0-12.14

** Tags added: kernel-key

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

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1503016] Re: linux: 4.2.0-15.17 -proposed tracker

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

** Description changed:

  This bug is for tracking the 4.2.0-15.17 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Monday, 05. October 2015 19:36 UTC
  kernel-phase-changed:Monday, 05. October 2015 19:36 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Monday, 05. October 2015 20:00 UTC
+ proposed-announcement-sent:True

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

Title:
  linux: 4.2.0-15.17 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Monday, 05. October 2015 19:36 UTC
  kernel-phase-changed:Monday, 05. October 2015 19:36 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Monday, 05. October 2015 20:00 UTC
  proposed-announcement-sent:True

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

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

[Kernel-packages] [Bug 1503218] Re: debian-installer: review our d-i config in relation to generated modules

I've been thinking about writing a script that grovels all of the module
files in the ABI directory to check for superfluous module names in d-i
as well as missing dependencies.

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

Title:
  debian-installer: review our d-i config in relation to  generated
  modules

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We have not recently reviewed the modules included in the d-i udebs.
  Review them.

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

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

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

2015-10-06 Thread Luke Faraone

I am able to enter my passphrase (asterisks appear, boot continues on
"enter") on 3.19.0-29-generic #31~lp1500751Commit4b630e4e on my Dell
Latitude E7250.

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

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

Status in cryptsetup package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1473880] Re: Backport Intel 8260 Wifi/BT drivers

2015-10-06 Thread pdf

Is this still planned?  I have a Skylake system that locks up frequently
on more recent kernels, but works with the combination of patches
included in the Vivid 3.19 kernel, however there I have no wireless...

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

Title:
  Backport Intel 8260 Wifi/BT drivers

Status in linux package in Ubuntu:
  Expired

Bug description:
  The drivers are now available in mainline 4.1 kernel and has been
  tested. Vivid currently doesn't support Intel 8260 Wifi/BT, and need
  to backport the drivers.

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

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

[Kernel-packages] [Bug 1478623] Re: [4.1.0 regression] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test

2015-10-06 Thread Martin Pitt

This seems fixed in wily now with the latest kernel:
http://autopkgtest.ubuntu.com/packages/u/udisks2/wily/i386/ is happy
again \o/

** Also affects: linux via
   http://bugzilla.kernel.org/show_bug.cgi?id=101011
   Importance: Unknown
   Status: Unknown

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

Title:
  [4.1.0 regression] Kernel oops - blk_update_request: I/O error when
  running udisks2 force_test_removal test

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

Bug description:
  We noticed that the udisks2 autopkgtest is failing on i386 in the
  "forced removal" test, for example

https://jenkins.qa.ubuntu.com/job/wily-adt-
  udisks2/ARCH=i386,label=adt/55/console

  I reproduced this locally, on this kernel

  ubuntu@autopkgtest:~$ uname -a
  Linux autopkgtest 4.1.0-2-generic #2-Ubuntu SMP Wed Jul 22 18:17:34 UTC 2015 
i686 i686 i686 GNU/Linux

  and got the following spewed to console

  fs: forced removal ... [  303.782426] blk_update_request: I/O error, dev sdb, 
sector 0
  [  303.807400] BUG: unable to handle kernel paging request at 1afde000
  [  303.808010] IP: [] __percpu_counter_add+0x16/0x90
  [  303.808010] *pdpt = 0ee9b001 *pde =  
  [  303.808010] Oops:  [#1] SMP 
  [  303.808010] Modules linked in: scsi_debug btrfs xor raid6_pq ufs qnx4 
hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ppdev kvm_intel kvm joydev 
serio_raw 8250_fintek parport_pc parport i2c_piix4 mac_hid autofs4 psmouse 
pata_acpi floppy
  [  303.808010] CPU: 0 PID: 22573 Comm: umount Not tainted 4.1.0-2-generic 
#2-Ubuntu
  [  303.808010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.8.1-20150604_211837-tipua 04/01/2014
  [  303.808010] task: dc75e5e0 ti: ce85a000 task.ti: ce85a000
  [  303.808010] EIP: 0060:[] EFLAGS: 00010092 CPU: 0
  [  303.808010] EIP is at __percpu_counter_add+0x16/0x90
  [  303.808010] EAX: 0001 EBX: dbba9c08 ECX:  EDX: 0001
  [  303.808010] ESI:  EDI:  EBP: ce85be6c ESP: ce85be54
  [  303.808010]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [  303.808010] CR0: 8005003b CR2: 1afde000 CR3: 1e9c88c0 CR4: 07f0
  [  303.808010] Stack:
  [  303.808010]  c1aa7b40 0001  dbba9be8  decbfd60 
ce85be88 c115bca4
  [  303.808010]  0008 ddce5228 ddce5228 decbfd60 decbfd70 ce85bea4 
c11e47f9 
  [  303.808010]  0286 ddce5228 d559cbd0 cdd41400 ce85beb4 c11e496f 
d3cc2000 
  [  303.808010] Call Trace:
  [  303.808010]  [] account_page_dirtied+0x74/0xf0
  [  303.808010]  [] __set_page_dirty+0x39/0xc0
  [  303.808010]  [] mark_buffer_dirty+0x4f/0xb0
  [  303.808010]  [] ext4_commit_super+0x168/0x220
  [  303.808010]  [] ext4_put_super+0xc1/0x310
  [  303.808010]  [] ? dispose_list+0x32/0x40
  [  303.808010]  [] ? evict_inodes+0xda/0xf0
  [  303.808010]  [] generic_shutdown_super+0x64/0xe0
  [  303.808010]  [] ? unregister_shrinker+0x40/0x50
  [  303.808010]  [] kill_block_super+0x1f/0x70
  [  303.808010]  [] deactivate_locked_super+0x3d/0x70
  [  303.808010]  [] deactivate_super+0x57/0x60
  [  303.808010]  [] cleanup_mnt+0x39/0x90
  [  303.808010]  [] __cleanup_mnt+0x10/0x20
  [  303.808010]  [] task_work_run+0xb1/0xd0
  [  303.808010]  [] do_notify_resume+0x53/0x70
  [  303.808010]  [] work_notifysig+0x26/0x2b
  [  303.808010] Code: 24 8b 54 24 04 83 c4 08 5b 5e 5f 5d c3 90 8d b4 26 00 00 
00 00 55 89 e5 57 56 53 89 c3 89 d0 83 ec 0c 89 45 ec 89 4d f0 8b 7b 14 <64> 8b 
37 89 7d e8 89 f7 c1 ff 1f 01 c6 11 cf 8b 4d 08 c1 f9 1f
  [  303.808010] EIP: [] __percpu_counter_add+0x16/0x90 SS:ESP 
0068:ce85be54
  [  303.808010] CR2: 1afde000
  [  303.808010] ---[ end trace bd84bb1a9fa3ebd4 ]---
  [  304.463429] scsi 2:0:0:0: Direct-Access Linuxscsi_debug   0184 
PQ: 0 ANSI: 6
  [  304.468098] sd 2:0:0:0: Attached scsi generic sg2 type 0
  [  304.472038] sd 2:0:0:0: [sdc] 585728 512-byte logical blocks: (299 MB/286 
MiB)
  [  304.476079] sd 2:0:0:0: [sdc] Write Protect is off
  [  304.476661] sd 2:0:0:0: [sdc] Mode Sense: 73 00 10 08
  [  304.484045] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, 
supports DPO and FUA
  [  304.572090] sd 2:0:0:0: [sdc] Attached SCSI disk

  To reproduce, do something like this:

  $ adt-buildvm-ubuntu-cloud -r wily -a i386 # download a cloud image, fettle 
it a bit to be more useful
  $ qemu-system-i386 -m 2048 -net user -net nic,model=virtio -enable-kvm 
-nographic adt-wily*
  # login with ubuntu/ubuntu

  # apt-get update
  # apt-get dist-upgrade
  $ apt-get source udisks2
  $ cd udisks2-*
  $ cat debian/tests/control # install the test-deps
  # debian/tests/upstream-system # runs the testsuite, when it gets to 
test_force_removal you should see

[Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting

** Attachment added: "/proc/acpi/wakeup"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396/+attachment/4485485/+files/wakeup

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

Title:
  Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-
  lan setting

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  === Update: This bug was reported from BIOS version F13 of my board,
  in the meantime I upgraded to the most recent version F14, but this
  had no impact on the bug. ===

  Hello,

  using Suspend-to-RAM on my system has stopped working reliably on
  Vivid when booting with Systemd. When I try to suspend my PC the
  following happens:

  - PC turns off
  - PC unwantedly wakes up (turns on) by itself again. This time span until it 
turns on again can reach from a second (almost immediately) until two or three 
minutes.
  - In a few cases (<25%), the PC stays suspended properly.

  A way to workaround this problem is to boot my PC with Upstart instead
  of Systemd, then this problem never happens (and has never happened in
  any of the previous Ubuntu versions since 2008). Thus it seems to be a
  bug somehow related to Systemd.

  Other steps I have tried to solve the problem (without any success):

  - Checking BIOS settings, all options are set that way that the PC should 
never wake up by any event other than pressing the power button.
  - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device 
could cause wake up events. This lists my USB controller, but deactivating it 
(with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the 
problem. Also suspend while running Upstart works fine despite the USB 
controller listed as "enabled".

  In the system logs I could see no hint what causes the undesired wake-
  ups.

  Allthough there is one factor which seems to have a certain influence:
  If I close programs like Pidgin, Skype or Firefox that cause
  continuous network traffic, the chance is higher that my PC will stay
  suspened (while runinng Systemd).

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 11:24:46 2015
  InstallationDate: Installed on 2015-04-16 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1389675] Re: Function keys will not adjust brightness

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Chintana Prabhu (chintanarp98)

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

Title:
  Function keys will not adjust brightness

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just installed Ubuntu 14.04, and I cannot make the function
  keys adjust the brightness.  I have been trying to get a solution to
  the problem in this forum
  
http://ubuntuforums.org/showthread.php?t=2250862=2=13159626#post13159626
  .

  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.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul   1336 F pulseaudio
   /dev/snd/pcmC0D0p:   paul   1336 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov  5 13:31:30 2014
  HibernationDevice: RESUME=UUID=6357ccbf-2f39-4ca6-9cc1-65eb05bf30f6
  InstallationDate: Installed on 2014-10-29 (6 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 003: ID 04f2:b404 Chicony Electronics Co., Ltd 
   Bus 001 Device 006: ID 1c4f:0003 SiGma Micro HID controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X551MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed 
root=UUID=730dc0d2-8142-4bc0-a5ee-a2928da9bd65 ro quiet splash 
acpi_backlight=vendor 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.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551MA.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551MA
  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.:bvrX551MA.510:bd06/27/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551MA
  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/1389675/+subscriptions

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

[Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting

Christopher, yes, my workaround seems to work in both cases 1) and 2) (
=PC stays suspended properly and doesn't power itself on unwantedly).
Btw. it seems that which graphics driver is in use is completely
unrelated to this bug.

Regarding 3):
- It doesn't seem to matter if I suspend by pressing power button, session menu
in Unity or executing 'systemctl suspend'. As noted before, the bug never
appears when suspending with 'pm-suspend', because that implicitly does the
same thing as my workaround (=explicitly setting wol flag to 'g' on my network
card).

- Is it really necessary to provide a resume trace? As far as I
understand, this is for cases when resume fails/doesn't work properly,
but this bug is _not_ about that resume fails, but that it works
correctly, but is triggered automatically (and undesired) by wake-on-
lan.

Kind regards,
Jan

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

Title:
Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-
lan setting

Status in linux package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Triaged

Bug description:
=== Update: This bug was reported from BIOS version F13 of my board,
in the meantime I upgraded to the most recent version F14, but this
had no impact on the bug. ===

Hello,

using Suspend-to-RAM on my system has stopped working reliably on
Vivid when booting with Systemd. When I try to suspend my PC the
following happens:

Other steps I have tried to solve the problem (without any success):

In the system logs I could see no hint what causes the undesired wake-
ups.

Kind regards,
Jan

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

[Kernel-packages] [Bug 1435028] Re: Kernel does not detect already connected USB devices on boot

2015-10-06 Thread AmiG

I'm using 14.04.3 on Dell XPS 13. I just updated the kernal to 3.19 as
recommended on Dell's forum to try and solve my issue with the wifi not
turning on after suspend. I didn't have any boot issues with the
connected USBs (yet) but I did noticed an issue after returning from
suspend. Hope this helps in debugging this issue.

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

Title:
  Kernel does not detect already connected USB devices on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel does not always detect already connected USB devices on
  boot. I have an USB nic and an external mouse connected to my Laptop.
  Sometimes these devices are recognized after boot, sometimes they are
  missing.

  When they are not present after boot you have to unplug them and plug them 
again. This is inconvient and adds physical wear on the USB connectors.
  The kernel log shows no sign of a disconnect, so it seems the kernel does not 
recognize the devices as plugged in on boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-9-generic 3.19.0-9.9
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   jan1733 F...m pulseaudio
   /dev/snd/controlC1:  jan1733 F pulseaudio
   /dev/snd/controlC0:  jan1733 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Mar 22 17:07:16 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-30 (50 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=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic.efi.signed 
root=UUID=e4431ecc-e85e-4e35-92af-58f455c46c2b ro kvm-intel.nested=1 quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-9-generic N/A
   linux-backports-modules-3.19.0-9-generic  N/A
   linux-firmware1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  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.:bvrA02:bd03/12/2015: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/1435028/+subscriptions

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

[Kernel-packages] [Bug 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep

2015-10-06 Thread Samarth Mathur

Please fix this guys,

It's killed a work system for many.

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

Title:
  [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from
  sleep

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

Bug description:
  HOW TO REPRODUCE

  1. Suspend the device
  2. Wake it up

  EXPECTED BEHAVIOUR

  - The device to resume normally

  REAL BEHAVIOUR

  - The screen goes blank

  RELEVANT DETAILS

  - In the "/etc/default/grub" file; changing "quiet splash" option to
  "nomodeset" allows the wakeup, but the computer gets so slow it is
  unusable.

  WORKAROUND: Install fglrx.

  Unverified WORKAROUND: Revert commit
  6c7bccea390853bdec5b76fe31fc50f3b36f75d5 as per
  https://bugzilla.kernel.org/show_bug.cgi?id=76761#c3 .

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 24 12:58:07 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] 
(prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c660]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-02-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RAF.N93.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U4X-S01TH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U4C
  dmi.product.version: P06RAF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  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-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 24 12:54:54 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: radeon

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

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

[Kernel-packages] [Bug 1503105] Re: linux-armadaxp: 3.2.0-1657.79 -proposed tracker

2015-10-06 Thread Ike Panhc

** Summary changed:

- linux-armadaxp:  -proposed tracker
+ linux-armadaxp: 3.2.0-1657.79 -proposed tracker

** Description changed:

- This bug is for tracking the  upload package. This
- bug will contain status and testing results related to that upload.
+ This bug is for tracking the 3.2.0-1657.79 upload package. This bug will
+ contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 03:02 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 06. October 2015 03:02 UTC
  kernel-stable-master-bug:1500854

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New => In Progress

** Changed in: linux-armadaxp (Ubuntu Precise)
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Platform QA Team (canonical-platform-qa) => Ike Panhc 
(ikepanhc)

** Changed in: kernel-sru-workflow/verification-testing
 Assignee: Canonical Hardware Enablement ARM Kernel 
(canonical-hwe-arm-kernel) => Ike Panhc (ikepanhc)

** Changed in: kernel-sru-workflow
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

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

Title:
  linux-armadaxp: 3.2.0-1657.79 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-armadaxp source package in Precise:
  In Progress

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 03:02 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 06. October 2015 03:02 UTC
  kernel-stable-master-bug:1500854
  kernel-stable-Certification-testing-end:Tuesday, 06. October 2015 06:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 06. October 2015 06:01 UTC

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

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

[Kernel-packages] [Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness

2015-10-06 Thread ChristianEhrhardt

Hi AZ,
thanks for your feedback.

>> IMHO if something overloads your machine with disk I/O it has to stall it.
> This is a bit tricky, because overload means that the machine will be able 
> not complete all task in the time given, i.e. tasks will accumulate until the 
> resources are exhausted. Though, we usually do not have this situation on 
> desktop machines.

Excuse me - I didn't want to phrase it too hard - it is surely ok to assume 
that a system stays responsive :-)
But when you add an background indexer like in the initial example you add some 
serious load.
The system might add a few other things and somewhen it is this overloaded.
Would you agree to modify your "Though, we usually do not have this situation 
on desktop machines." to "Though, we usually *should* not have this situation 
on desktop machines."?

Because that is the point where my suggestion of "throttling the few
loads that cause these situations" kicks in.

> So this bug is mostly about having too big delays in applications
using only a small bit of the available resources (like when switching
back to a libreoffice window) when some other applications (like
background file indexing) are asking for the remaining disk io resource
capacities.

When I think of an overload case where e.g. a Process submits requests as fast 
as it can (especially with asynchronous I/O a process can quickly fill up 
hundreds of I/Os to the block device layer).
Now what should a process scheduler or I/O scheduler do?
1. handle them asap -> achieve good throughput, but might add some stalls to 
the system
2. throttle them -> improves responsiveness by avoiding overload, but this 
comes at certain prices
2a) if the process scheduler stalls it people start to ask "there is nothing 
else on the runqueue, why isn't it running? I want to get all I can from my HW".
2b) if the I/O scheduler stalls it people start to ask "hey my device could 
handle way more, why isn't it fully utilized with the request queue being 
filled" (remember all the "fun" people had with anticipatory scheduler)

Both 2a and 2b existed in various patches/tunings and almost every time
the decision was that "the default" can not be to stall too much because
there are different demands.

That was the reason why I personally didn't think about a cool new piece
of code (which surely someone could write), but instead of a good
mitigation of the most frequent cases with tools that are already there
(like the cgroup io throttling I suggested)

>> Code improves to mitigate effects but can never be perfect for *ALL* users 
>> at once (especially in the default config)
>I do not agree.

Long story short - a default configuration has to be a tradeoff trying
to make everyone happy but no one sad (hard job).

> Desktop responsiveness was achieved with older ubuntu versions on the
given hw and is achieved with other operating systems (windows) on a
broad range of hardware.

I'm coming from the server world, and there I/O throughput, I/O latency and 
even process latency and fairness clearly is superior compared to older 
releases as well as when compared well to other OSes.
But that doesn't negate your experience - it is just a different one.

> I believe desktop responsiveness is something sufficiently specific a
cpu and io scheduler can be tuned to.

You are right that probably cpu and io scheduler could be tuned, but
that gets to the point of the default having to be a trade-off between
different user groups demands - so the default might be right just
neither for you (wants more responsiveness) nor for me (wants more I/O).

> Using cgroups and alike might help, but should be configured by Ubuntu
by default if necessary.

And here I totally agree, we could really think about isolating the most 
obvious hogs. Especially those that people "didn't realize" they had.
So if one runs a huge database or an I/O benchmark he willingly chose a heavy 
I/O workload.
But if a background indexer causes the same, users might quite often not even 
know about its existence.
That is what I wanted to achieve with "open a separate bug requesting 
configurable throttling for each component applicable like trackerd and so many 
other I/O heavy background tasks"

Within those bugs it could be discussed and rated "per application" if
it makes sense to either isolate and throttle them by default or at
least to provide an easy method to do so.

Another way could be something like different "user/tuning profiles" to 
distinguish the need for different defaults.
But I guess we should strive to give the best out of the box experience so 
isolating the most obvious hogs first would surely be a good idea.

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

Title:
  Heavy Disk I/O harms desktop responsiveness

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: linux-source-2.6.22

[Kernel-packages] [Bug 1503105] Re: linux-armadaxp: 3.2.0-1657.79 -proposed tracker

** Description changed:

  This bug is for tracking the 3.2.0-1657.79 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 03:02 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 06. October 2015 03:02 UTC
  kernel-stable-master-bug:1500854
+ kernel-stable-Certification-testing-end:Tuesday, 06. October 2015 06:01 UTC
+ kernel-stable-Security-signoff-end:Tuesday, 06. October 2015 06:01 UTC

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

Title:
  linux-armadaxp: 3.2.0-1657.79 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-armadaxp source package in Precise:
  In Progress

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 03:02 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 06. October 2015 03:02 UTC
  kernel-stable-master-bug:1500854
  kernel-stable-Certification-testing-end:Tuesday, 06. October 2015 06:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 06. October 2015 06:01 UTC

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

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

[Kernel-packages] [Bug 1502552] Re: touchpad not working

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Chintana Prabhu (chintanarp98)

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad is not responding. External mouse is working.
  The touchpad is not listed in xinput.
  External mouse is listed twice in xinput as well as in 'cat 
/proc/bus/input/devices'  but touchpad driver isn't.

  What I expected to see in /proc/bus/input/devices file:

  I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
  N: Name="SynPS/2 Synaptics TouchPad"
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input8
  U: Uniq=
  H: Handlers=mouse2 event8
  B: EV=b
  B: KEY=420 0 7 0 0 0 0 0 0 0 0
  B: ABS=1103 

  What I saw instead:

  I: Bus=0003 Vendor=046d Product=c07e Version=0111
  N: Name="Logitech Gaming Mouse G402"
  P: Phys=usb-:00:14.0-1/input0
  S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-1/2-1:1.0/input/input15
  U: Uniq=6D9036795757
  H: Handlers=mouse0 event5 
  B: PROP=0
  B: EV=17
  B: KEY= 0 0 0 0
  B: REL=143
  B: MSC=10

  I: Bus=0003 Vendor=046d Product=c07e Version=0111
  N: Name="Logitech Gaming Mouse G402"
  P: Phys=usb-:00:14.0-1/input1
  S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-1/2-1:1.1/input/input16
  U: Uniq=6D9036795757
  H: Handlers=sysrq kbd event6 
  B: PROP=0
  B: EV=10001f
  B: KEY=4837fff072ff32d bf56 1 30f908b17c007 ffe77bfad941dfff 
febeffdfffef fffe
  B: REL=40
  B: ABS=1
  B: MSC=10

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.8.0-44-generic 3.8.0-44.66~precise1
  ProcVersionSignature: Ubuntu 3.8.0-44.66~precise1-generic 3.8.13.25
  Uname: Linux 3.8.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-44-generic.
  ApportVersion: 2.0.1-0ubuntu17.11
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sumit  2114 F pulseaudio
   /dev/snd/controlC0:  sumit  2114 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xf7a14000 irq 60'
 Mixer name : 'Intel Haswell HDMI'
 Components : 'HDA:80862807,80860101,0010'
 Controls  : 7
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xf7a1 irq 61'
 Mixer name : 'Realtek ALC255'
 Components : 'HDA:10ec0255,10280662,0012'
 Controls  : 18
 Simple ctrls  : 8
  Date: Sun Oct  4 10:01:29 2015
  HibernationDevice: RESUME=UUID=45998e30-d2b6-4037-96ff-63f405f9832d
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: Dell Inc. Vostro 3446
  MarkForUpload: True
  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.8.0-44-generic 
root=UUID=8def0356-8cf9-4e71-829f-03a59b5d259f ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-44-generic N/A
   linux-backports-modules-3.8.0-44-generic  N/A
   linux-firmware1.79.18
  SourcePackage: linux-lts-raring
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3446
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 607061] Re: screen brightness unchangable

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Chintana Prabhu (chintanarp98)

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

Title:
  screen brightness unchangable

Status in xf86-video-intel:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xorg

  Hello, I am using a Gateway NV5927U laptop and the screen brightness
  is unchangeable via the keyboard controls.  The brightness is stuck at
  100% and changing values inside of /proc/acpi/video/GFX0 have no
  effect on the brightness.  Please let me know what else you may need.
  If the brightness is changed inside of Microsoft Windows it will
  visually stay dim until GDM starts, at this point the screen raises to
  full brightness and is locked at that state.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xorg 1:7.5+5ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  Architecture: i386
  Date: Mon Jul 19 00:19:36 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100213)
  Lsusb:
   Bus 002 Device 003: ID 04f2:b044 Chicony Electronics Co., Ltd
   Bus 002 Device 002: ID 8087:0020
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gateway NV59
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-23-generic 
root=UUID=2e6f02f8-a269-473e-bdab-905fc6eb70a3 ro processor.max_cstate=2 
vga=0x317 quiet splash
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: xorg
  dmi.bios.date: 11/26/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.09
  dmi.board.name: NV59
  dmi.board.vendor: Gateway
  dmi.board.version: Rev
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.09:bd11/26/2009:svnGateway:pnNV59:pvrRev:rvnGateway:rnNV59:rvrRev:cvnGateway:ct10:cvrRev:
  dmi.product.name: NV59
  dmi.product.version: Rev
  dmi.sys.vendor: Gateway
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-23-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/607061/+subscriptions

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

[Kernel-packages] [Bug 117327] Re: Can't use the lowest brightness setting

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Chintana Prabhu (chintanarp98)

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

Title:
  Can't use the lowest brightness setting

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-source-2.6.22 package in Ubuntu:
  Won't Fix

Bug description:
  Sony TX series and possible many other Sony laptops couldn't use the lowest 
brightness setting because the default  sony_acpi.c restrict the lowest value 
to one instead of zero. This could save some energy so the difference between 
Linux and Windows isn't that high any more. I have always patched the 
sony_acpi.c on my own but since this module isn't integrated in linux.source 
anymore it is much more harder without recompiling the whole kernel. If there 
is any Sony laptop which haven't zero as the lowest value it should be no 
problem since a bug in /etc/acpi/sonybright.sh sets brightness on the lowest 
option to 33 (which is out of bound 0-8) instead of zero because of spicctrl 
which seems to have no impact.
  Of course the /etc/acpi/sonybright.sh of the acpi-support package have to be 
patched too.

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

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

[Kernel-packages] [Bug 1503016] Re: linux: 4.2.0-15.17 -proposed tracker

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

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

Title:
  linux: 4.2.0-15.17 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Monday, 05. October 2015 19:36 UTC
  kernel-phase-changed:Monday, 05. October 2015 19:36 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Monday, 05. October 2015 20:00 UTC
  proposed-announcement-sent:True

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

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

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

All builds are complete, packages in this bug can be copied to
-proposed.

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Fix Released

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.19.0-31.35~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 05:00 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 06. October 2015 05:00 UTC
  kernel-stable-master-bug:1503005
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 20:02 UTC
+ kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 20:02 UTC
+ kernel-stable-phase-changed:Tuesday, 06. October 2015 20:02 UTC

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 05:00 UTC
  kernel-stable-master-bug:1503005
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 20:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 20:02 UTC
  kernel-stable-phase-changed:Tuesday, 06. October 2015 20:02 UTC

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

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

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

@dann - check tip of Wily master-next to review my reverts.

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

Title:
  kernel crash on m400 arm64 server cartridge

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

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1502238] Re: bridge does not forward neighbor solicitation packets

2015-10-06 Thread Jay Vosburgh

I set up a similar configuration locally, and I see the bridge correctly
forwarding the IPv6 NS packets.  The ping functions as expected.  I have
different network cards, and used IPv6 ULA addresses (fc00:1234::/64)
but I'm not sure how that would affect the bridge forwarding decision.

I'm also not sure what exactly is meant by your statement "Adding a host
route for the 2001:: IP via the link IP"; I don't see any other
reference to a 2001:: address.  Could you clarify what this refers to?

Also, for completeness, can you insure that there are no bridge table
rules installed?  This would be in the output of

ebtables -t filter -L
ebtables -t nat -L
ebtables -t broute -L

I would also suggest disabling the bridge callouts to arptables,
ip6tables and iptables to see if that affects the behavior.  This would
be done via

sysctl -w net.bridge.bridge-nf-call-arptables=0
sysctl -w net.bridge.bridge-nf-call-ip6tables=0
sysctl -w net.bridge.bridge-nf-call-iptables=0

(all of the above sysctl and ebtables commands need to be done as root)

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

Title:
  bridge does not forward neighbor solicitation packets

Status in linux package in Ubuntu:
  Triaged

Bug description:
  3 hosts involved here:
  kailan is connected to a cisco switch, which is also connected to kurrat 
(eth3), which is running a bridge with tigernut connected to eth1.

  kurrat's controllers are 06:00.0 Ethernet controller: Intel
  Corporation 82574L Gigabit Network Connection, using the e1000e driver
  (3.13.0-65-generic kernel)

  (while kailan is doing a ping6
  2601:282:8100:3500:82ee:73ff:fe99:368d):

  +kurrat 324 : sudo tcpdump -eni eth3 ip6 and not tcp and not udp
  tcpdump: WARNING: eth3: no IPv4 address assigned
  tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
  listening on eth3, link-type EN10MB (Ethernet), capture size 65535 bytes
  10:39:16.080888 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 
(0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor 
solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32
  10:39:16.431484 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 
(0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router 
advertisement, length 56
  10:39:17.077446 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 
(0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor 
solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32
  10:39:18.077457 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 
(0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor 
solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32
  10:39:19.095034 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 
(0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor 
solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32
  10:39:20.093436 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 
(0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor 
solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32
  10:39:21.093425 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 
(0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor 
solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32
  10:39:21.43 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 
(0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router 
advertisement, length 56
  10:39:22.111042 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 
(0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor 
solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32
  ^C
  10 packets captured
  11 packets received by filter
  0 packets dropped by kernel
  +kurrat 325 : sudo tcpdump -eni eth1 ip6 and not tcp and not udp
  tcpdump: WARNING: eth1: no IPv4 address assigned
  tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
  listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
  10:39:28.201110 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 
(0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router 
advertisement, length 56
  10:39:31.552677 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 
(0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router 
advertisement, length 56
  10:39:38.103919 08:10:78:fc:b3:d2 > 33:33:00:00:00:01, ethertype IPv6 
(0x86dd), length 90: fe80::a10:78ff:fefc:b3d2 > ff02::1: HBH ICMP6, multicast 
listener query v2 [gaddr ::], length 28
  10:39:39.663357 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 
(0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router 
advertisement,

[Kernel-packages] [Bug 1501281] Re: Frequent freezes on 15.04 with kernel 3.19.0-29+

I uploaded a test kernel to:
http://kernel.ubuntu.com/~jsalisbury/lp1501281/

Can you test this kernel and see if it resolves the 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/1501281

Title:
  Frequent freezes on 15.04 with kernel 3.19.0-29+

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

Bug description:
  I am experiencing systematic freezes since my kernel was automatically
  upgraded to 3.19.0-29. Same problem happens if I use kernel 3.19.0-30.
  If I use kernel 3.19.0-28 it does not freeze any more.

  Behaviour is described with more details at

  http://askubuntu.com/questions/679212/frequent-freezes-on-15-04-with-
  kernel-3-19-0-29

  and at

  http://askubuntu.com/questions/673767/frequent-freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrea 3174 F pulseaudio
   /dev/snd/pcmC0D0p:   andrea 3174 F...m pulseaudio
   /dev/snd/controlC0:  andrea 3174 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 30 12:45:03 2015
  HibernationDevice: RESUME=UUID=7f029a53-8d17-4db1-b66f-d131578efe68
  InstallationDate: Installed on 2010-04-15 (1993 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  IwConfig:
   eth2  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic 
root=UUID=5d76a02d-2ed2-484a-81da-3cf5ce0ab3fb ro crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-30 (153 days ago)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0303
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E
  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.:bvr0303:bd04/18/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1502055] Re: Crypt password screen not responding

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

** This bug has been marked a duplicate of bug 1500751
   Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

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

Title:
  Crypt password screen not responding

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  During booting of system when the password screen for a encrypted device is 
presented there is no response.
  The screen is not accepting any input.
  I can switch to another screen using ctrl+alt+F# key and see blinking cursor.
  Switching back to ctrl+alt+F7 is showing message and all entered keys on 
screen.

  Rebooting by ctrl+alt+del or power button causes that the system boots
  to a text version of that screen where I can enter the password and
  system boots to OS.

  Not sure what could be gathered during this event to assist in
  identifying the problem since I have no possibility to get any logs
  and decrypt the disk :(

  Regards,
  Peter

  
  Just to add when the password screen is "hung" and I switch to different 
screen and back to F7 I see this message: 
  starting version 219

  The same is visible when second boot is going. However this time I'm pushed 
to text based version where no problem is visible
  --- 
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppiwonsk   1929 F pulseaudio
   /dev/snd/controlC1:  ppiwonsk   1929 F pulseaudio
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-06-03 (122 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: TOSHIBA TECRA Z40-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
  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.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  Tags:  vivid
  Uname: Linux 3.19.0-30-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-08-02 (62 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.1A
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA Z40-B
  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.1A:bd04/10/2015:svnTOSHIBA:pnTECRAZ40-B:pvrPT45GE-06S03C0V:rvnTOSHIBA:rnTECRAZ40-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: TECRA Z40-B
  dmi.product.version: PT45GE-06S03C0V
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

2015-10-06 Thread dann frazier

@Tim: Please do - the dtb interface for numa is still in discussion, so
I think we can expect the OS/fw interface to change anyway.

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

Title:
  kernel crash on m400 arm64 server cartridge

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

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1502598] Re: Boot hangs on encryption password prompt on 3.19.0-30

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

** This bug has been marked a duplicate of bug 1500751
   Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

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

Title:
  Boot hangs on encryption password prompt on 3.19.0-30

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Starting with kernel 3.19.0-30-generic, the password prompt for my
  disk encryption password hangs at boot.

  I can workaround the issue by booting with kernel 3.19.0-28-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mark   1788 F pulseaudio
   /dev/snd/controlC0:  mark   1788 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct  4 07:22:53 2015
  HibernationDevice: RESUME=UUID=4392843b-ec3d-442b-8159-f2e4bed58105
  InstallationDate: Installed on 2015-09-20 (14 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1503214] Re: Can't input password to decrypt disk at boot

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

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

** This bug has been marked a duplicate of bug 1500751
   Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

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

Title:
  Can't input password to decrypt disk at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Ever since I upgraded to kernel 3.19.0-30 i can't input the disk
  password at boot, in order to have the disk decrypted. The workaround
  it to boot with kernel-3.19.0-28 which works. When booting with
  3.19.0-30 whatever I type won't showup. CTRL+ALT+DEL would reboot the
  machine though.

  My machine is a Dell XPS 13" (2015).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  radu   1302 F pulseaudio
   /dev/snd/controlC0:  radu   1302 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Oct  6 13:06:11 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9221aee5-1069-4140-ae9f-623b4238fa4d
  InstallationDate: Installed on 2015-07-21 (77 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1502944] Re: Laptop built-in keyboard is not working after kernel upgrade

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

** This bug has been marked a duplicate of bug 1500751
   Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

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

Title:
  Laptop built-in keyboard is not working after kernel upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot enter my encryption password to unlock the hard drive because
  the keyboard does not work.

  Old working kernel: 3.19.0-28-generic
  Non-working kernel: 3.19.0-30-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robin  1800 F pulseaudio
   /dev/snd/controlC1:  robin  1800 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Oct  5 16:37:40 2015
  HibernationDevice: RESUME=UUID=805a7dda-9be7-4a44-aaed-bbd91cc56268
  InstallationDate: Installed on 2015-05-05 (152 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   tun0  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216c Broadcom Corp. 
   Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 3938:1031  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2293
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn2293:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard

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

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

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

I built the next test kernel, up to the following commit:
884feaefcd5a4b2a8ef10436f74077cef1330f6b

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

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

Thanks in advance

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

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

Status in cryptsetup package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1501281] Re: Frequent freezes on 15.04 with kernel 3.19.0-29+

Thanks for testing.  The results would indicate this is either fixed in
3.19.8-ckt7 or it is a bug introduced by a SAUCE patch.  I'll build and
Ubuntu kernel with the  3.19.8-ckt7 updates.  I'll post a link to the
kernel shortly.

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

Title:
  Frequent freezes on 15.04 with kernel 3.19.0-29+

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

Bug description:
  I am experiencing systematic freezes since my kernel was automatically
  upgraded to 3.19.0-29. Same problem happens if I use kernel 3.19.0-30.
  If I use kernel 3.19.0-28 it does not freeze any more.

  Behaviour is described with more details at

  http://askubuntu.com/questions/679212/frequent-freezes-on-15-04-with-
  kernel-3-19-0-29

  and at

  http://askubuntu.com/questions/673767/frequent-freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrea 3174 F pulseaudio
   /dev/snd/pcmC0D0p:   andrea 3174 F...m pulseaudio
   /dev/snd/controlC0:  andrea 3174 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 30 12:45:03 2015
  HibernationDevice: RESUME=UUID=7f029a53-8d17-4db1-b66f-d131578efe68
  InstallationDate: Installed on 2010-04-15 (1993 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  IwConfig:
   eth2  no wireless extensions.
   
   lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic 
root=UUID=5d76a02d-2ed2-484a-81da-3cf5ce0ab3fb ro crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-30 (153 days ago)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0303
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E
  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.:bvr0303:bd04/18/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1503432] Re: package linux-image-extra-3.19.0-15-generic 3.19.0-15.15 failed to install/upgrade: package linux-image-extra-3.19.0-15-generic is not ready for configuration canno

2015-10-06 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-3.19.0-15-generic 3.19.0-15.15 failed to
  install/upgrade: package linux-image-extra-3.19.0-15-generic is not
  ready for configuration  cannot configure (current status `half-
  installed')

Status in linux package in Ubuntu:
  New

Bug description:
  I ran a standard dist-upgrade on Ubuntu 15.04 and package installation
  failed.

  Related output from dpkg:

  dpkg: error processing package linux-image-extra-3.19.0-15-generic 
(--configure):
   package linux-image-extra-3.19.0-15-generic is not ready for configuration
   cannot configure (current status `half-installed')

  
  Setting up linux-image-extra-3.19.0-30-generic (3.19.0-30.34) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.19.0-30-generic /boot/vmlinuz-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
  update-initramfs: Generating /boot/initrd.img-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
3.19.0-30-generic /boot/vmlinuz-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/update-notifier 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/zz-extlinux 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-3.19.0-30-generic
  Found initrd image: /boot/initrd.img-3.19.0-30-generic
  Found linux image: /boot/vmlinuz-3.19.0-26-generic
  Found initrd image: /boot/initrd.img-3.19.0-26-generic
  Found linux image: /boot/vmlinuz-3.19.0-25-generic
  Found initrd image: /boot/initrd.img-3.19.0-25-generic
  Found linux image: /boot/vmlinuz-3.19.0-23-generic
  Found initrd image: /boot/initrd.img-3.19.0-23-generic
  Found linux image: /boot/vmlinuz-3.19.0-22-generic
  Found initrd image: /boot/initrd.img-3.19.0-22-generic
  Found linux image: /boot/vmlinuz-3.19.0-21-generic
  Found initrd image: /boot/initrd.img-3.19.0-21-generic
  Found linux image: /boot/vmlinuz-3.19.0-18-generic
  Found initrd image: /boot/initrd.img-3.19.0-18-generic
  Found linux image: /boot/vmlinuz-3.19.0-16-generic
  Found initrd image: /boot/initrd.img-3.19.0-16-generic
  Found linux image: /boot/vmlinuz-3.19.0-15-generic
  Found initrd image: /boot/initrd.img-3.19.0-15-generic
  Found linux image: /boot/vmlinuz-3.16.0-36-generic
  Found initrd image: /boot/initrd.img-3.16.0-36-generic
  Found linux image: /boot/vmlinuz-3.13.0-43-generic
  Found initrd image: /boot/initrd.img-3.13.0-43-generic
  Found linux image: /boot/vmlinuz-3.13.0-37-generic
  Found initrd image: /boot/initrd.img-3.13.0-37-generic
  Found linux image: /boot/vmlinuz-3.7.0-7-generic
  Found initrd image: /boot/initrd.img-3.7.0-7-generic
  Found linux image: /boot/vmlinuz-3.5.0-28-generic
  Found initrd image: /boot/initrd.img-3.5.0-28-generic
  Found linux image: /boot/vmlinuz-3.5.0-27-generic
  Found initrd image: /boot/initrd.img-3.5.0-27-generic
  Found memtest86+ image: /boot/memtest86+.elf
  Found memtest86+ image: /boot/memtest86+.bin
  Found Windows 7 (loader) on /dev/sdc1
  done

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: linux-image-extra-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cosmo  1999 F pulseaudio
   /dev/snd/controlC0:  cosmo  1999 F pulseaudio
   /dev/snd/seq:timidity   1104 F timidity
  Date: Tue Oct  6 23:54:05 2015
  DuplicateSignature: 
package:linux-image-extra-3.19.0-15-generic:3.19.0-15.15:package 
linux-image-extra-3.19.0-15-generic is not ready for configuration  cannot 
configure (current status `half-installed')
  ErrorMessage: package linux-image-extra-3.19.0-15-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  HibernationDevice: RESUME=UUID=645b6d8f-218c-4ac1-aab7-1cbfb3449d0f
  InstallationDate: Installed on 2013-04-06 (913 days ago)
  InstallationMedia: Linux Mint 14 "Nadia" - Release amd64 (20121120)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB:
   
  ProcKernelCmdLine:

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

2015-10-06 Thread dann frazier

fyi, though I do see this backtrace when booting up an X-Gene, in my
case it isn't fatal.

Rather, I'm hitting an issue later on where modules cannot load, and
*that* is fatal. It persists even w/ the numa patches removed.

Loading, please wait... 
[2.144740] systemd-udevd[128]: starting version 225 
[2.150901] random: systemd-udevd urandom read with 1 bits of entropy availae
[2.192721] module gpio_xgene_sb: unsupported RELA relocation: 275   
[2.193609] module xgene_enet: unsupported RELA relocation: 275  
[2.249402] module libahci: unsupported RELA relocation: 275 
[2.249628] module xgene_enet: unsupported RELA relocation: 275  
[2.359451] module xgene_enet: unsupported RELA relocation: 275  
[2.389444] module xgene_enet: unsupported RELA relocation: 275  
[3.473766] module linear: unsupported RELA relocation: 275  
[3.543252] module multipath: unsupported RELA relocation: 275   
[3.593268] module raid0: unsupported RELA relocation: 275   
[3.663695] module raid1: unsupported RELA relocation: 275   
[3.713964] module raid6_pq: unsupported RELA relocation: 275
[3.763983] module raid6_pq: unsupported RELA relocation: 275
[3.803975] module raid6_pq: unsupported RELA relocation: 275
[3.853881] module raid10: unsupported RELA relocation: 275  
[3.924962] module raid6_pq: unsupported RELA relocation: 275

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

Title:
  kernel crash on m400 arm64 server cartridge

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

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

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

Title:
  package linux-image-extra-3.19.0-15-generic 3.19.0-15.15 failed to
  install/upgrade: package linux-image-extra-3.19.0-15-generic is not
  ready for configuration  cannot configure (current status `half-
  installed')

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran a standard dist-upgrade on Ubuntu 15.04 and package installation
  failed.

  Related output from dpkg:

  dpkg: error processing package linux-image-extra-3.19.0-15-generic 
(--configure):
   package linux-image-extra-3.19.0-15-generic is not ready for configuration
   cannot configure (current status `half-installed')

  
  Setting up linux-image-extra-3.19.0-30-generic (3.19.0-30.34) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.19.0-30-generic /boot/vmlinuz-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
  update-initramfs: Generating /boot/initrd.img-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
3.19.0-30-generic /boot/vmlinuz-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/update-notifier 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/zz-extlinux 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-3.19.0-30-generic
  Found initrd image: /boot/initrd.img-3.19.0-30-generic
  Found linux image: /boot/vmlinuz-3.19.0-26-generic
  Found initrd image: /boot/initrd.img-3.19.0-26-generic
  Found linux image: /boot/vmlinuz-3.19.0-25-generic
  Found initrd image: /boot/initrd.img-3.19.0-25-generic
  Found linux image: /boot/vmlinuz-3.19.0-23-generic
  Found initrd image: /boot/initrd.img-3.19.0-23-generic
  Found linux image: /boot/vmlinuz-3.19.0-22-generic
  Found initrd image: /boot/initrd.img-3.19.0-22-generic
  Found linux image: /boot/vmlinuz-3.19.0-21-generic
  Found initrd image: /boot/initrd.img-3.19.0-21-generic
  Found linux image: /boot/vmlinuz-3.19.0-18-generic
  Found initrd image: /boot/initrd.img-3.19.0-18-generic
  Found linux image: /boot/vmlinuz-3.19.0-16-generic
  Found initrd image: /boot/initrd.img-3.19.0-16-generic
  Found linux image: /boot/vmlinuz-3.19.0-15-generic
  Found initrd image: /boot/initrd.img-3.19.0-15-generic
  Found linux image: /boot/vmlinuz-3.16.0-36-generic
  Found initrd image: /boot/initrd.img-3.16.0-36-generic
  Found linux image: /boot/vmlinuz-3.13.0-43-generic
  Found initrd image: /boot/initrd.img-3.13.0-43-generic
  Found linux image: /boot/vmlinuz-3.13.0-37-generic
  Found initrd image: /boot/initrd.img-3.13.0-37-generic
  Found linux image: /boot/vmlinuz-3.7.0-7-generic
  Found initrd image: /boot/initrd.img-3.7.0-7-generic
  Found linux image: /boot/vmlinuz-3.5.0-28-generic
  Found initrd image: /boot/initrd.img-3.5.0-28-generic
  Found linux image: /boot/vmlinuz-3.5.0-27-generic
  Found initrd image: /boot/initrd.img-3.5.0-27-generic
  Found memtest86+ image: /boot/memtest86+.elf
  Found memtest86+ image: /boot/memtest86+.bin
  Found Windows 7 (loader) on /dev/sdc1
  done

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: linux-image-extra-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cosmo  1999 F pulseaudio
   /dev/snd/controlC0:  cosmo  1999 F pulseaudio
   /dev/snd/seq:timidity   1104 F timidity
  Date: Tue Oct  6 23:54:05 2015
  DuplicateSignature: 
package:linux-image-extra-3.19.0-15-generic:3.19.0-15.15:package 
linux-image-extra-3.19.0-15-generic is not ready for configuration  cannot 
configure (current status `half-installed')
  ErrorMessage: package linux-image-extra-3.19.0-15-generic is not ready for 
configuration  cannot configure (current status `half-installed')
  HibernationDevice: RESUME=UUID=645b6d8f-218c-4ac1-aab7-1cbfb3449d0f
  InstallationDate: Installed on 2013-04-06 (913 days ago)
  InstallationMedia: Linux Mint 14 "Nadia" - Release amd64 (20121120)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.

[Kernel-packages] [Bug 1502946] Re: kernel crash on m400 arm64 server cartridge

2015-10-06 Thread dann frazier

This appears to be the regression. Rebuilding the kernel w/
CONFIG_ARM64_ERRATUM_843419=n works around it.

commit bf0cdf4bfb785129798bc42d6ee8e2558f0934da
Author: Will Deacon 
Date:   Tue Mar 17 12:15:02 2015 +

arm64: errata: add module build workaround for erratum #843419

commit df057cc7b4fa59e9b55f07ffdb6c62bf02e99a00 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/1502946

Title:
  kernel crash on m400 arm64 server cartridge

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

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1503417] Re: Cannot enter disk encryption password

2015-10-06 Thread Steve Langasek

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

** Package changed: plymouth (Ubuntu) => linux (Ubuntu)

** This bug has been marked a duplicate of bug 1500751
   Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

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

Title:
  Cannot enter disk encryption password

Status in linux package in Ubuntu:
  New

Bug description:
  When booting with an encrypted root partition, I'm unable to enter the
  password when prompted during boot. Rebooting by hitting Ctrl+Alt+Del
  twice, displays grub menu and then puts me in a degraded mode of some
  sort where I can enter the password and boot successfully. Disabling
  splash in grub options works too by using a text mode password input.

  This seems to have been introduced in some of the recent updates. It
  used to work fine after my initial installation of 15.04.

  Laptop model: Thinkpad X250
  Ubuntu version: 15.04
  Kernel version: 3.19.0-30
  Plymouth version: 0.9.0-0ubuntu9

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

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

[Kernel-packages] [Bug 1503432] [NEW] package linux-image-extra-3.19.0-15-generic 3.19.0-15.15 failed to install/upgrade: package linux-image-extra-3.19.0-15-generic is not ready for configuration can

2015-10-06 Thread Ville Ranki

Public bug reported:

I ran a standard dist-upgrade on Ubuntu 15.04 and package installation
failed.

Related output from dpkg:

dpkg: error processing package linux-image-extra-3.19.0-15-generic 
(--configure):
 package linux-image-extra-3.19.0-15-generic is not ready for configuration
 cannot configure (current status `half-installed')


Setting up linux-image-extra-3.19.0-30-generic (3.19.0-30.34) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
update-initramfs: Generating /boot/initrd.img-3.19.0-30-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
3.19.0-30-generic /boot/vmlinuz-3.19.0-30-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
run-parts: executing /etc/kernel/postinst.d/zz-extlinux 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.19.0-30-generic 
/boot/vmlinuz-3.19.0-30-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.19.0-30-generic
Found initrd image: /boot/initrd.img-3.19.0-30-generic
Found linux image: /boot/vmlinuz-3.19.0-26-generic
Found initrd image: /boot/initrd.img-3.19.0-26-generic
Found linux image: /boot/vmlinuz-3.19.0-25-generic
Found initrd image: /boot/initrd.img-3.19.0-25-generic
Found linux image: /boot/vmlinuz-3.19.0-23-generic
Found initrd image: /boot/initrd.img-3.19.0-23-generic
Found linux image: /boot/vmlinuz-3.19.0-22-generic
Found initrd image: /boot/initrd.img-3.19.0-22-generic
Found linux image: /boot/vmlinuz-3.19.0-21-generic
Found initrd image: /boot/initrd.img-3.19.0-21-generic
Found linux image: /boot/vmlinuz-3.19.0-18-generic
Found initrd image: /boot/initrd.img-3.19.0-18-generic
Found linux image: /boot/vmlinuz-3.19.0-16-generic
Found initrd image: /boot/initrd.img-3.19.0-16-generic
Found linux image: /boot/vmlinuz-3.19.0-15-generic
Found initrd image: /boot/initrd.img-3.19.0-15-generic
Found linux image: /boot/vmlinuz-3.16.0-36-generic
Found initrd image: /boot/initrd.img-3.16.0-36-generic
Found linux image: /boot/vmlinuz-3.13.0-43-generic
Found initrd image: /boot/initrd.img-3.13.0-43-generic
Found linux image: /boot/vmlinuz-3.13.0-37-generic
Found initrd image: /boot/initrd.img-3.13.0-37-generic
Found linux image: /boot/vmlinuz-3.7.0-7-generic
Found initrd image: /boot/initrd.img-3.7.0-7-generic
Found linux image: /boot/vmlinuz-3.5.0-28-generic
Found initrd image: /boot/initrd.img-3.5.0-28-generic
Found linux image: /boot/vmlinuz-3.5.0-27-generic
Found initrd image: /boot/initrd.img-3.5.0-27-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 7 (loader) on /dev/sdc1
done

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: linux-image-extra-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  cosmo  1999 F pulseaudio
 /dev/snd/controlC0:  cosmo  1999 F pulseaudio
 /dev/snd/seq:timidity   1104 F timidity
Date: Tue Oct  6 23:54:05 2015
DuplicateSignature: 
package:linux-image-extra-3.19.0-15-generic:3.19.0-15.15:package 
linux-image-extra-3.19.0-15-generic is not ready for configuration  cannot 
configure (current status `half-installed')
ErrorMessage: package linux-image-extra-3.19.0-15-generic is not ready for 
configuration  cannot configure (current status `half-installed')
HibernationDevice: RESUME=UUID=645b6d8f-218c-4ac1-aab7-1cbfb3449d0f
InstallationDate: Installed on 2013-04-06 (913 days ago)
InstallationMedia: Linux Mint 14 "Nadia" - Release amd64 (20121120)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=c4b14a2d-c1ec-475a-be26-1fa0ead2cf2d ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-22ubuntu1.1
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-extra-3.19.0-15-generic 3.19.0-15.15 failed to 
install/upgrade: package linux-image-extra-3.19.0-15-generic is not ready for 
configuration  cannot configure (current status `half-installed')
UpgradeStatus: Upgraded to vivid on

[Kernel-packages] [Bug 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

The patch author requested an acpidump.  Could you provide this?  It can be 
done by installing the acpidump package the running:
 sudo acpidump -o acpidump.txt

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

Title:
  kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

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

Bug description:
  On Fujitsu A544 laptop (and likely others) fitted with SSD, kworker
  takes 100% of one core of CPU due to GPE13 interrupt storm

  See upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=53071

  The bug can be identified by repeatedly running 
  cat /sys/firmware/acpi/interrupts/gpe13
  where a rapidly increasing count will be seen.

  Workaround:
  sudo sh -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe13'
  disables it until reboot
  Using 
  sudo crontab -e
  and adding the line
  @reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe13
  works around for subsequent boots.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-3-generic 4.1.0-3.3
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  colinl 1699 F pulseaudio
   /dev/snd/controlC1:  colinl 1699 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep  2 16:03:19 2015
  InstallationDate: Installed on 2014-10-21 (316 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.147
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-08-31 (1 days ago)
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.19
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd04/01/2015:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

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

All builds are complete, packages in this bug can be copied to
-proposed.

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Fix Released

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.16.0-51.68~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 11:00 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 06. October 2015 11:00 UTC
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 21:02 UTC
+ kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 21:02 UTC
+ kernel-stable-phase-changed:Tuesday, 06. October 2015 21:02 UTC

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 11:00 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 21:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 21:02 UTC
  kernel-stable-phase-changed:Tuesday, 06. October 2015 21:02 UTC

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

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

[Kernel-packages] [Bug 1499203] Re: memory leak in hv_storvsc (3.13.0-63-generic)

To see if it is the cause of this issue, I built a test kernel with a
revert of commit 97b2591.  The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1499203/

Can you test this kernel and see if it resolves this bug?  If it does
not, we would have to perform a kernel bisect to identify the commit
that caused this regression.

Thanks in advance!

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

Title:
  memory leak in hv_storvsc (3.13.0-63-generic)

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

Bug description:
  Slab and SUnreclaim values in /proc/meminfo keep increasing. On one
  servers it reached 85% of physical memory after 14 days - but on most
  other servers it increases more slowly. I checked /proc/slabinfo and
  almost all allocations were in kmalloc-512. So I enabled
  "slub_debug=U,kmalloc-512" on one server, and after only 24h of uptime
  11% of the memory was used by kmalloc-512 and unreclaimable. With
  debugging enabled I could see the following in
  /sys/kernel/slab/kmalloc-512/alloc_calls:

  521294 storvsc_queuecommand+0x359/0x790 [hv_storvsc]
  age=161922/955116/20882927 pid=1-41545

  All other counters were below 2000. In
  /sys/kernel/slab/kmalloc-512/free_calls I see the following:

  516823  age=4315783846 pid=0

  The hv_storvsc module is for Hyper-V. We are (unfortunately) running
  Hyper-V 6.3.9600.16384 with Microsoft System Center 2012 R2 Update
  rollup 3 for all the servers with this issue.

  Kernels are stock linux-image-3.13.0-63-generic, 3.13.0-63.103,
  x86_64, from Ubuntu 14.04 LTS . /proc/version_signature contains:

Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25

  No output from lspci -vnvn. The problem described above happens on
  both single and multicore virtual machines. CPU in hypervisors are
  E5-2630 v2 @ 2.60GHz. Let me know if you need more info or if I can do
  more debugging.

  Regards,

  Oskar Liljeblad
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 24 00:31 seq
   crw-rw 1 root audio 116, 33 Sep 24 00:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [59081.977909] systemd-udevd[26480]: starting version 204
   [59124.051974] init: systemd-logind main process (756) killed by TERM signal
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-09-09 (380 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic.efi.signed 
root=UUID=f4d228d6-2eee-40fc-bf3f-633e46fa8301 ro slub_debug=U,kmalloc-512
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   Sep 24 02:06:19 adm-backup1 dhclient: message repeated 1447 times: [ 
DHCPREQUEST of 10.40.128.9 on eth0 to 192.0.2.253 port 67 (xid=0x429dad4)]
   Sep 24 02:06:37 adm-backup1 dhclient: DHCPREQUEST of 10.40.128.9 on eth0 to 
255.255.255.255 port 67 (xid=0x429dad4)
   Sep 24 02:06:37 adm-backup1 dhclient: DHCPACK of 10.40.128.9 from 192.0.2.253
   Sep 24 02:06:37 adm-backup1 dhclient: bound to 10.40.128.9 -- renewal in 
44877 seconds.
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 6126-4244-1659-0314-3158-3955-44
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias:

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

Title:
  "Wi-fi disabled by hardware switch" permanently on Lenovo Yoga 2 13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've a Lenovo Yoga 2 13" and installed Wily from a thumb drive (no
  upgrade).

  Can't use wifi at all. The indicator panel says "Wi-fi disabled by
  hardware switch". Pressing the "airplane mode" key makes no
  difference.

  Once I blacklisted ideapad_laptop kernel module, I did get wi-fi back.
  But after a couple of minutes it would become slow and unreliable to
  be point of being unusable.

  It came as a surprise as I was previously using Vivid on this laptop
  and wi-fi worked out of the box with it, never giving me any problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dandrader   2057 F pulseaudio
   /dev/snd/controlC0:  dandrader   2057 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct  6 18:13:39 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=75aae517-7579-4767-950c-75b06face626
  InstallationDate: Installed on 2015-10-02 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150918)
  MachineType: LENOVO ZIVY0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=ede92ad6-f711-45c1-9c1a-68ba94618135 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.148
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 3192WIN8 PRO
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3192WIN8 PRO MBR IPG
  dmi.chassis.asset.tag: 3192WIN8 PRO
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: INVALID
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pnZIVY0:pvrINVALID:rvnLENOVO:rnINVALID:rvr3192WIN8PROMBRIPG:cvnLENOVO:ct10:cvrINVALID:
  dmi.product.name: ZIVY0
  dmi.product.version: INVALID
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1503438] [NEW] "Wi-fi disabled by hardware switch" permanently on Lenovo Yoga 2 13

2015-10-06 Thread Daniel d'Andrada

Public bug reported:

I've a Lenovo Yoga 2 13" and installed Wily from a thumb drive (no
upgrade).

Can't use wifi at all. The indicator panel says "Wi-fi disabled by
hardware switch". Pressing the "airplane mode" key makes no difference.

Once I blacklisted ideapad_laptop kernel module, I did get wi-fi back.
But after a couple of minutes it would become slow and unreliable to be
point of being unusable.

It came as a surprise as I was previously using Vivid on this laptop and
wi-fi worked out of the box with it, never giving me any problems.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-14-generic 4.2.0-14.16
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dandrader   2057 F pulseaudio
 /dev/snd/controlC0:  dandrader   2057 F pulseaudio
CurrentDesktop: Unity
Date: Tue Oct  6 18:13:39 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=75aae517-7579-4767-950c-75b06face626
InstallationDate: Installed on 2015-10-02 (4 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150918)
MachineType: LENOVO ZIVY0
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=ede92ad6-f711-45c1-9c1a-68ba94618135 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-14-generic N/A
 linux-backports-modules-4.2.0-14-generic  N/A
 linux-firmware1.148
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 96CN29WW(V1.15)
dmi.board.asset.tag: 3192WIN8 PRO
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 3192WIN8 PRO MBR IPG
dmi.chassis.asset.tag: 3192WIN8 PRO
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: INVALID
dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pnZIVY0:pvrINVALID:rvnLENOVO:rnINVALID:rvr3192WIN8PROMBRIPG:cvnLENOVO:ct10:cvrINVALID:
dmi.product.name: ZIVY0
dmi.product.version: INVALID
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug wily

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

Title:
  "Wi-fi disabled by hardware switch" permanently on Lenovo Yoga 2 13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've a Lenovo Yoga 2 13" and installed Wily from a thumb drive (no
  upgrade).

  Can't use wifi at all. The indicator panel says "Wi-fi disabled by
  hardware switch". Pressing the "airplane mode" key makes no
  difference.

  Once I blacklisted ideapad_laptop kernel module, I did get wi-fi back.
  But after a couple of minutes it would become slow and unreliable to
  be point of being unusable.

  It came as a surprise as I was previously using Vivid on this laptop
  and wi-fi worked out of the box with it, never giving me any problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dandrader   2057 F pulseaudio
   /dev/snd/controlC0:  dandrader   2057 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct  6 18:13:39 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=75aae517-7579-4767-950c-75b06face626
  InstallationDate: Installed on 2015-10-02 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150918)
  MachineType: LENOVO ZIVY0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=ede92ad6-f711-45c1-9c1a-68ba94618135 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.148
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 3192WIN8 PRO
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3192WIN8 PRO MBR IPG
  dmi.chassis.asset.tag: 3192WIN8 PRO
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: INVALID
  dmi.modalias:

[Kernel-packages] [Bug 1503417] [NEW] Cannot enter disk encryption password

You have been subscribed to a public bug:

When booting with an encrypted root partition, I'm unable to enter the
password when prompted during boot. Rebooting by hitting Ctrl+Alt+Del
twice, displays grub menu and then puts me in a degraded mode of some
sort where I can enter the password and boot successfully. Disabling
splash in grub options works too by using a text mode password input.

This seems to have been introduced in some of the recent updates. It
used to work fine after my initial installation of 15.04.

Laptop model: Thinkpad X250
Ubuntu version: 15.04
Kernel version: 3.19.0-30
Plymouth version: 0.9.0-0ubuntu9

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

-- 
Cannot enter disk encryption password
https://bugs.launchpad.net/bugs/1503417
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 1503164] [NEW] The size of the log files in /var/log gets out of hand

2015-10-06 Thread Abhilash

Public bug reported:

Thankfully it's a rare problem, but anyway: some errors create huge log
files, causing rapid loss of disk space.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Abhilash (abhilashkonnur1)
 Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Abhilash (abhilashkonnur1)

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

Title:
  The size of the log files in /var/log gets out of hand

Status in linux package in Ubuntu:
  New

Bug description:
  Thankfully it's a rare problem, but anyway: some errors create huge
  log files, causing rapid loss of disk space.

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

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

[Kernel-packages] [Bug 1500344] [NEW] Brightness HotKeys not Detected

You have been subscribed to a public bug:

The brightness can be changed through commands, however the brightness
keys fn+f6 (brighter) and fn+f5 (dimmer) are not detected by
acpi_listen, thus the hotkey functions do not activate.

Ubuntu 15.04, 3.19.0-28-generic

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

-- 
Brightness HotKeys not Detected
https://bugs.launchpad.net/bugs/1500344
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 1500344] Re: Brightness HotKeys not Detected

2015-10-06 Thread Martin Pitt

Thank you. This needs to be fixed in the kernel driver then, as without
a scan code there is nothing we can do in userspace.

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

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

** Summary changed:

- Brightness HotKeys not Detected
+ [ASUSTeK X555-50] Brightness hotkeys do not produce evdev event

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

Title:
  [ASUSTeK X555-50] Brightness hotkeys do not produce evdev event

Status in linux package in Ubuntu:
  New

Bug description:
  The brightness can be changed through commands, however the brightness
  keys fn+f6 (brighter) and fn+f5 (dimmer) are not detected by
  acpi_listen, thus the hotkey functions do not activate.

  Ubuntu 15.04, 3.19.0-28-generic

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

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

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

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

apport-collect 1500344

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

Title:
  [ASUSTeK X555-50] Brightness hotkeys do not produce evdev event

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The brightness can be changed through commands, however the brightness
  keys fn+f6 (brighter) and fn+f5 (dimmer) are not detected by
  acpi_listen, thus the hotkey functions do not activate.

  Ubuntu 15.04, 3.19.0-28-generic

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

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

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

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

apport-collect 1503164

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

Title:
  The size of the log files in /var/log gets out of hand

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Thankfully it's a rare problem, but anyway: some errors create huge
  log files, causing rapid loss of disk space.

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

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

[Kernel-packages] [Bug 1503105] Re: linux-armadaxp: 3.2.0-1657.79 -proposed tracker

All builds are complete, packages in this bug can be copied to
-proposed.

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Hardware Enablement ARM Kernel 
(canonical-hwe-arm-kernel) => Ike Panhc (ikepanhc)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Hardware Enablement ARM Kernel 
(canonical-hwe-arm-kernel) => Ike Panhc (ikepanhc)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.2.0-1657.79 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 03:02 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 06. October 2015 03:02 UTC
  kernel-stable-master-bug:1500854
  kernel-stable-Certification-testing-end:Tuesday, 06. October 2015 06:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 06. October 2015 06:01 UTC
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 08:01 UTC
+ kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 08:01 UTC
+ kernel-stable-phase-changed:Tuesday, 06. October 2015 08:01 UTC

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

Title:
  linux-armadaxp: 3.2.0-1657.79 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 03:02 UTC
  kernel-stable-master-bug:1500854
  kernel-stable-Certification-testing-end:Tuesday, 06. October 2015 06:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 06. October 2015 06:01 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 06. October 2015 08:01 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 06. October 2015 08:01 UTC
  kernel-stable-phase-changed:Tuesday, 06. October 2015 08:01 UTC

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

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

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

2015-10-06 Thread Luis Henriques

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 04:02 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 06. October 2015 04:02 UTC
  kernel-stable-master-bug:1503021

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

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

[Kernel-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

2015-10-06 Thread Tejal

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Tejal (tejalravih)

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

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

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

[Kernel-packages] [Bug 1502658] Re: unable to read xattr id index table

2015-10-06 Thread ShRev

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => ShRev (shradhavrevankar)

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

Title:
  unable to read xattr id index table

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  when we are updating the vmware tool for linux software it wil instal
  after that we get bugs(error)

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

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

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Fix Released

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 06. October 2015 11:00 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 06. October 2015 11:00 UTC

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

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

[Kernel-packages] [Bug 1495983] Re: [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32

The original patch is already in Trusty as the following commit:

commit 97b2591fbecaa0366939bb5fdfecd79fe914de22
Author: K. Y. Srinivasan 
Date:   Fri Mar 27 00:27:20 2015 -0700

scsi: storvsc: Set the tablesize based on the information given by the host


It was added to Trusty in the 3.13.0-60 kernel:
git describe --contains 97b2591
Ubuntu-3.13.0-60.99~189


The define for MAX_PAGE_BUFFER_COUNT is in include/linux/hyperv.h :

#define MAX_PAGE_BUFFER_COUNT   32
#define MAX_MULTIPAGE_BUFFER_COUNT  32 /* 128K */

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

Title:
  [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Incomplete
Status in linux source package in Vivid:
  Incomplete
Status in linux source package in Wily:
  In Progress

Bug description:
  Attempting to install the latest build of Ubuntu Server 15.10 (Wily
  Werewolf) x32 on Hyper-V, after beginning installation a kernel panic
  occurs. The console log from the serial output is attached.

  http://cdimage.ubuntu.com/ubuntu-server/daily/current/

  I tried with the builds from 14th and 15th of September with the same result. 
This bug does not affect x64 builds. 
  Tried to start the installation with different resources with no effect, 
kernel panic always occurs no matter the VM settings.

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

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

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