[Kernel-packages] [Bug 1604443] onza (amd64) - tests ran: 20, failed: 0

[Brad Figg]

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-32.51/onza__4.4.0-32.51__2016-07-22_03-15-00/results-index.html

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

Title:
  linux: 4.4.0-32.51 -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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1537209] Re: Kernel doesn't load after kubuntu upgrade (from 15.04 to 15.10)

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernel doesn't load after kubuntu upgrade (from 15.04 to 15.10)

Status in linux package in Ubuntu:
  Expired

Bug description:
  After updrade my laptop Lenovo T430u from Kubuntu Vivid to Wily), I
  can not load the kernel 4.2.0-23 or 4.2.0-25 (not tested other
  versions).

  The only kernel I can use is 3.19.0-43 (from Kubuntu Vivid).

  If I choose 4.2.0-xx kernel, I just can see a black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-25-generic 4.2.0-25.30
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yamane 1879 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 22 19:13:09 2016
  HibernationDevice: RESUME=UUID=f11f0511-b75c-4a11-a486-9119d10ee8d7
  InstallationDate: Installed on 2014-03-08 (685 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140308)
  MachineType: LENOVO 33525SP
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic 
root=UUID=0575faf0-2a03-4d14-8eff-4e45024318f0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-43-generic N/A
   linux-backports-modules-3.19.0-43-generic  N/A
   linux-firmware 1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2016-01-15 (6 days ago)
  dmi.bios.date: 01/11/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ET90WW (2.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 33525SP
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD EM DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ET90WW(2.08):bd01/11/2013:svnLENOVO:pn33525SP:pvrThinkPadT430u:rvnLENOVO:rn33525SP:rvrWin8STDEMDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 33525SP
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1604443] onza (amd64) - tests ran: 26, failed: 0

[Brad Figg]

tests ran:  26, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-32.51/onza__4.4.0-32.51__2016-07-21_22-23-00/results-index.html

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

Title:
  linux: 4.4.0-32.51 -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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1579984] Re: Dell dock MAC Address pass through doesn't work in Ubuntu

[Phidias]

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

Title:
  Dell dock MAC Address pass through doesn't work in Ubuntu

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Dell systems with Type-C ports support a feature called "MAC address" pass 
through.
  This feature allows systems to set a persistent system MAC address to be used 
with the TB15, WD15 and Type-C ethernet adapter.

  More information is available here:
  http://www.dell.com/support/article/us/en/19/SLN301147/en

  This function works by a system specific MAC address (referred to as
  an auxiliary mac address) being programmed in the factory.  When the
  driver for the type-c ethernet (in dock or dongle) is loaded the MAC
  address is supposed to be overridden with this value.

  To enable this in Linux a kernel patch is needed.
  This has been submitted http://patchwork.ozlabs.org/patch/631759/

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

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

[Kernel-packages] [Bug 1523738] Re: [Dell Alienware 13 R2] touchpad not working

[adin]

I tried #24 but it didn't work for me. Same status as before. I'm on a
Alienware 17R3 under ubuntu 16.04, though.

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

Title:
  [Dell Alienware 13 R2] touchpad not working

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Installed ubuntu 15.10 on alienware 13, touchpad is showing up in xinput list 
as expected, but is totally unresponsive. Was working fine on 14.05
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sean   1610 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=ed54b297-8650-46ee-b615-6d543bb47b7a
  InstallationDate: Installed on 2015-12-07 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Alienware Alienware 13 R2
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=4c119f73-b6e4-4100-9d32-f6052a303bcf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/15/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.0
  dmi.board.name: Alienware 13 R2
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.0:bd10/15/2015:svnAlienware:pnAlienware13R2:pvr1.2.0:rvnAlienware:rnAlienware13R2:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 13 R2
  dmi.product.version: 1.2.0
  dmi.sys.vendor: Alienware

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

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

[Kernel-packages] [Bug 1579984] Re: Dell dock MAC Address pass through doesn't work in Ubuntu

[Anthony Wong]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Phidias (phidias-chiang)

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

Title:
  Dell dock MAC Address pass through doesn't work in Ubuntu

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Dell systems with Type-C ports support a feature called "MAC address" pass 
through.
  This feature allows systems to set a persistent system MAC address to be used 
with the TB15, WD15 and Type-C ethernet adapter.

  More information is available here:
  http://www.dell.com/support/article/us/en/19/SLN301147/en

  This function works by a system specific MAC address (referred to as
  an auxiliary mac address) being programmed in the factory.  When the
  driver for the type-c ethernet (in dock or dongle) is loaded the MAC
  address is supposed to be overridden with this value.

  To enable this in Linux a kernel patch is needed.
  This has been submitted http://patchwork.ozlabs.org/patch/631759/

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

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

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

[bugproxy]

--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/ 
and it worked fine for me

--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on 
http://people.canonical.com/~kamal/lp1573062/lp1573062.1/

But with my diff + 4.4.0 source from apt-source, I can always get the
the following command to succeed.

timeout -s 9 $end_time stress-ng --aggressive --verify --timeout
$runtime --brk 0

I've tried three times with my diff (all success) and twice with the
kernel @ ~kamal (one failure and one success). I've not tried the longer
7 hour run

--- Comment From balb...@au1.ibm.com 2016-07-19 01:37 EDT---
In the kern.log posted, it looks like the problem has moved to

rwsem_wake+0xcc/0x110
up_write+0x78/0x90
unlink_anon_vmas+0x15c/0x2c0

A bunch of threads are stuck on rwsem_wake -- spinning on the
sem->wait_lock. I can see a whole bunch of exiting  stress-ng-mmapf
stuck on this lock, spinning. I'll double check this. Can we get a build
with lockdep enabled? I am unable to reproduce this issue at my end with
the diff applied on my machine at the moment

--- Comment From balb...@au1.ibm.com 2016-07-19 19:51 EDT---
I am cloning the sources to debug further

--- Comment From balb...@au1.ibm.com 2016-07-19 23:52 EDT---
I cloned the kernel from 
https://git.launchpad.net/~kamalmostafa/ubuntu/+source/linux/+git/xenial/log/?h=lp1573062
 and built with the machine config specified from /boot/config. I also verified 
the diff matches my changes.

I ran

timeout -s 9 $end_time stress-ng --aggressive --verify --timeout
$runtime --brk 0

twice

Both the times, the test did the right thing. Could someone verify if

(a) The smaller subset works fine?
(b) The larger test fails, if so, can we get a run with lockdep

I was just testing for the command line above and I could see a
difference with those patches.

--- Comment From balb...@au1.ibm.com 2016-07-21 20:14 EDT---
No, the diff matches, sorry for the confusion, but here is what I said

"I also verified the diff matches my changes"

In summary, here is what I did

1. cloned the sources
2. built locally on my machine
3. Ran stress-ng with recommended parameters
4. The test succeeded, got back the console

Did four runs and I got back the console each time

However with the provided binaries

Step 3 (stress-ng) failed for me once in two runs

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

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

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

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

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

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

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

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

[bugproxy]

--- Comment From mauri...@br.ibm.com 2016-07-21 19:03 EDT---
Hi Canonical,

The vendor's developer reviewed the patch -- "Looks good."
Can it be applied?

Thanks

http://marc.info/?l=linux-scsi=146913719625306=2

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

Title:
  ISST-LTE:pVM:monklp5:Ubuntu16.04.1:system crashed at
  lpfc_sli4_scmd_to_wqidx_distr

Status in linux package in Ubuntu:
  Triaged

Bug description:
  ---Problem Description---
  We have Ubuntu16.04.1 installed on our system and run DLPAR test for ZR1 
adapter  after some time it crashes at lpfc_sli4_scmd_to_wqidx_distr+0x30/0x100

  Machine Type = 9119-MME*1085AE7 
   
  ---Debugger Data---
  e:mon> e
  cpu 0xe: Vector: 300 (Data Access) at [c003d45335a0]
  pc: d3a374e0: lpfc_sli4_scmd_to_wqidx_distr+0x30/0x100 [lpfc]
  lr: d39d749c: lpfc_sli_calc_ring.part.20+0xdc/0x100 [lpfc]
  sp: c003d4533820
 msr: 80019033
 dar: 0
   dsisr: 4000
current = 0xc003e06c2a20
paca= 0xc7af8500   softe: 0irq_happened: 0x01
  pid   = 17983, comm = scsi_eh_23
  e:mon> r
  R00 = d39d749c   R16 = 
  R01 = c003d4533820   R17 = c003d4533cd0
  R02 = d3a84160   R18 = c003d4533cb8
  R03 = c003ee76a000   R19 = c003d87e5088
  R04 = c003dad6a800   R20 = c003d4533cb0
  R05 = c003dad6a870   R21 = 001e
  R06 = 0001   R22 = c18aab78
  R07 = d3a84160   R23 = c003dad6a870
  R08 = d3a2f830   R24 = c003dad6a800
  R09 = 0004   R25 = c003d4533978
  R10 =    R26 = 0001
  R11 = d3a59a50   R27 = 
  R12 = 28533824   R28 = c003e841e000
  R13 = c7af8500   R29 = c003ee76a000
  R14 = c003d87e5000   R30 = c003dad6a800
  R15 = c003d4533cb8   R31 = c003ee76a000
  pc  = d3a374e0 lpfc_sli4_scmd_to_wqidx_distr+0x30/0x100 [lpfc]
  cfar= c0008468 slb_miss_realmode+0x50/0x78
  lr  = d39d749c lpfc_sli_calc_ring.part.20+0xdc/0x100 [lpfc]
  msr = 80019033   cr  = 28538828
  ctr = c0ae3cf0   xer = 2010   trap =  300
  dar =    dsisr = 4000
  e:mon> 
   
  Stack trace output:
   e:mon> t
  [c003d4533850] d39d749c lpfc_sli_calc_ring.part.20+0xdc/0x100 
[lpfc]
  [c003d4533890] d39df680 lpfc_sli_issue_iocb+0xf0/0x330 [lpfc]
  [c003d45338f0] d39e3824 lpfc_sli_issue_iocb_wait+0x264/0x680 
[lpfc]
  [c003d45339d0] d3a32944 lpfc_send_taskmgmt+0x2d4/0x7d0 [lpfc]
  [c003d4533aa0] d3a33564 lpfc_device_reset_handler+0x114/0x210 
[lpfc]
  [c003d4533b60] c075843c scsi_eh_ready_devs+0x68c/0xee0
  [c003d4533c50] c075a91c scsi_error_handler+0x6bc/0x9e0
  [c003d4533d80] c00e61e0 kthread+0x110/0x130
  [c003d4533e30] c0009538 ret_from_kernel_thread+0x5c/0xa4
  --- Exception: 0  at 
  e:mon>
   
  e:mon> dl
  [10194.079284] sd 13:0:3:0: [sdaf] tag#0 FAILED Result: 
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
  [10194.079293] sd 13:0:3:0: [sdaf] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 
00 80 00
  [10194.079297] blk_update_request: I/O error, dev sdaf, sector 41942912
  [10194.079313] device-mapper: multipath: Failing path 65:240.
  [10194.079351] sd 13:0:2:0: [sdab] tag#0 FAILED Result: 
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
  [10194.079360] sd 13:0:2:0: [sdab] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 
00 80 00
  [10194.079364] blk_update_request: I/O error, dev sdab, sector 41942912
  [10194.079375] device-mapper: multipath: Failing path 65:176.
  [10194.102832] scsi 13:0:1:0: alua: Detached
  [10194.110320] sd 13:0:1:1: [sdh] tag#0 FAILED Result: 
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
  [10194.110324] sd 13:0:1:1: [sdh] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 00 
80 00
  [10194.110326] blk_update_request: I/O error, dev sdh, sector 41942912
  [10194.110334] device-mapper: multipath: Failing path 8:112.
  [10194.110394] sd 13:0:2:1: [sdac] tag#0 FAILED Result: 
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
  [10194.110398] sd 13:0:2:1: [sdac] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 
00 80 00
  [10194.110401] blk_update_request: I/O error, dev sdac, sector 41942912
  [10194.110407] device-mapper: multipath: Failing path 65:192.
  [10194.110439] sd 13:0:3:1: [sdag] tag#0 FAILED Result: 
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
  [10194.110448] sd 13:0:3:1: [sdag] tag#0 CDB: Read(10) 28 00 02 7f ff 80 00 
00 80 00
  [10194.110452] blk_update_request: I/O error, dev sdag, sector 41942912
  [10194.110464] device-mapper: multipath: Failing path 66:0.
  [10194.118851] scsi 13:0:0:1: alua: Detached
  [10194.122868] sd 13:0:3:0: [sdaf] tag#0 FAILED Result: 

[Kernel-packages] [Bug 1605405] cxlflash patch for shutdown

[bugproxy]

Default Comment by Bridge

** Attachment added: "cxlflash patch for shutdown"
   
https://bugs.launchpad.net/bugs/1605405/+attachment/4704966/+files/0001-cxlflash-Verify-problem-state-area-is-mapped-before-.patch

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Backport cxlflash shutdown patch to Xenial SRU

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - UMA KRISHNAN - 2016-07-21 17:39:18 ==
  ---Problem Description---
  A patch is now in the process of upstream for the cxlflash driver. Can this 
be pulled into Xenial SRU ?

  I have attached the patch with this bug. The link to the mail sent to 
community is,
  http://marc.info/?l=linux-scsi=146913386924240=2

  cxlflash: Verify problem state area is mapped before notifying shutdown
   
  ---uname output---
  4.4.0-31.50
   
  ---Steps to Reproduce---
   Execute cxlflash FVT tests
   
  Stack trace output:
   [c00f1da03b60] c05eccfc pci_device_shutdown+0x6c/0x100
  [c00f1da03ba0] c06d67d4 device_shutdown+0x1b4/0x2c0
  [c00f1da03c40] c00ea30c kernel_restart_prepare+0x5c/0x80
  [c00f1da03c70] c00ea48c kernel_restart+0x2c/0xc0
  [c00f1da03ce0] c00ea970 SyS_reboot+0x1c0/0x2d0
  [c00f1da03e30] c0009204 system_call+0x38/0xb4
   
  Oops output:
   cpu 0xa: Vector: 300 (Data Access) at [c00f1da03840]
  pc: daaf0e64: notify_shutdown+0x84/0x220 [cxlflash]
  lr: c05eccfc: pci_device_shutdown+0x6c/0x100
  sp: c00f1da03ac0
 msr: 90009033
 dar: 2012328
   dsisr: 4000
current = 0xc00f1d94
paca= 0xcfb45f00   softe: 0irq_happened: 0x01
  pid   = 1, comm = systemd-shutdow
  enter ? for help
  [c00f1da03b60] c05eccfc pci_device_shutdown+0x6c/0x100
  [c00f1da03ba0] c06d67d4 device_shutdown+0x1b4/0x2c0
  [c00f1da03c40] c00ea30c kernel_restart_prepare+0x5c/0x80
  [c00f1da03c70] c00ea48c kernel_restart+0x2c/0xc0
  [c00f1da03ce0] c00ea970 SyS_reboot+0x1c0/0x2d0
  [c00f1da03e30] c0009204 system_call+0x38/0xb4
  --- Exception: c01 (System Call) at 3fffa4129bec
  SP (3fffce171820) is in userspace

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

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

[Kernel-packages] [Bug 1604443] onza (amd64) - tests ran: 30, failed: 0

[Brad Figg]

tests ran:  30, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-32.51/onza__4.4.0-32.51__2016-07-21_21-05-00/results-index.html

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

Title:
  linux: 4.4.0-32.51 -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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

[deb2014]

Here is in attachment the kernel logs with general protection fault on
resumes.

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+attachment/4704967/+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/1566302

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get  no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  macias 1770 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr  5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

[deb2014]

Upgrading to newer kernel did not solve the issue, I experience similar crashes 
with linux 4.6 from kernel-ppa.

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

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get  no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  macias 1770 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr  5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1605405] [NEW] Backport cxlflash shutdown patch to Xenial SRU

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - UMA KRISHNAN - 2016-07-21 17:39:18 ==
---Problem Description---
A patch is now in the process of upstream for the cxlflash driver. Can this be 
pulled into Xenial SRU ?

I have attached the patch with this bug. The link to the mail sent to community 
is,
http://marc.info/?l=linux-scsi=146913386924240=2

cxlflash: Verify problem state area is mapped before notifying shutdown
 
---uname output---
4.4.0-31.50
 
---Steps to Reproduce---
 Execute cxlflash FVT tests
 
Stack trace output:
 [c00f1da03b60] c05eccfc pci_device_shutdown+0x6c/0x100
[c00f1da03ba0] c06d67d4 device_shutdown+0x1b4/0x2c0
[c00f1da03c40] c00ea30c kernel_restart_prepare+0x5c/0x80
[c00f1da03c70] c00ea48c kernel_restart+0x2c/0xc0
[c00f1da03ce0] c00ea970 SyS_reboot+0x1c0/0x2d0
[c00f1da03e30] c0009204 system_call+0x38/0xb4
 
Oops output:
 cpu 0xa: Vector: 300 (Data Access) at [c00f1da03840]
pc: daaf0e64: notify_shutdown+0x84/0x220 [cxlflash]
lr: c05eccfc: pci_device_shutdown+0x6c/0x100
sp: c00f1da03ac0
   msr: 90009033
   dar: 2012328
 dsisr: 4000
  current = 0xc00f1d94
  paca= 0xcfb45f00   softe: 0irq_happened: 0x01
pid   = 1, comm = systemd-shutdow
enter ? for help
[c00f1da03b60] c05eccfc pci_device_shutdown+0x6c/0x100
[c00f1da03ba0] c06d67d4 device_shutdown+0x1b4/0x2c0
[c00f1da03c40] c00ea30c kernel_restart_prepare+0x5c/0x80
[c00f1da03c70] c00ea48c kernel_restart+0x2c/0xc0
[c00f1da03ce0] c00ea970 SyS_reboot+0x1c0/0x2d0
[c00f1da03e30] c0009204 system_call+0x38/0xb4
--- Exception: c01 (System Call) at 3fffa4129bec
SP (3fffce171820) is in userspace

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-144033 severity-high 
targetmilestone-inin---
-- 
Backport cxlflash shutdown patch to Xenial SRU
https://bugs.launchpad.net/bugs/1605405
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

Re: [Kernel-packages] [Bug 1603655] Re: After update, xorg will not boot

[Steve Langasek]

> I never heard of debconf before today. Google tells me that debconf is
> related to answering configuration questions while installing packages.
> Is that related? There weren't any questions when installing linux-
> signed-image-generic. Were there supposed to be?

Not when installing linux-signed-image-generic itself, but when installing
the shim-signed package or when the fglrx-updates-core package builds its
dkms module, yes there should be a series of questions asked about disabling
secureboot.

> Under 3.13.0-91, sudo modprobe fglrx-updates goes through without
comment.

> Under 3.13.0-92, sudo modprobe fglrx-updates fails with ERROR: could not
> insert fglrx_updates: required key not available.

> I don't know how this could be, since
> 3.13.0-92-generic/updates/dkms/fglrx_updates.ko is signed with the same
> key as 3.13.0-91-generic/updates/dkms/fglrx_updates.ko.

This is because 3.13.0-91-generic doesn't enforce kernel signature
verification, so it will load the module with a warning in dmesg about it
being unverified and the kernel being 'tainted', whereas 3.13.0-92-generic
does enforce kernel signature verification and rejects this module because
it's not signed by a *trusted* key.

To have the kernel trust the key you used for signing, you must enroll it in
the firmware in either the SecureBoot database or the MOK database.

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

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1603655] Re: After update, xorg will not boot

[dualBootLaptop]

Under 3.13.0-91, sudo modprobe fglrx-updates goes through without comment.
Under 3.13.0-92, sudo modprobe fglrx-updates fails with ERROR: could not insert 
fglrx_updates: required key not available.
I don't know how this could be, since 
3.13.0-92-generic/updates/dkms/fglrx_updates.ko is signed with the same key as 
3.13.0-91-generic/updates/dkms/fglrx_updates.ko.

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

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1604443] onza (i386) - tests ran: 10, failed: 10

[Brad Figg]

tests ran:  10, failed: 10;
  
http://kernel.ubuntu.com/testing/4.4.0-32.51/onza__4.4.0-32.51__2016-07-21_20-42-00/results-index.html

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

Title:
  linux: 4.4.0-32.51 -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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

[João Carlos Martins Teixeira]

Exactly the same here (as described by deb2014) with an ASUS UX31A

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

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get  no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  macias 1770 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr  5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1603655] Re: After update, xorg will not boot

[dualBootLaptop]

I signed the fglrx driver with
sudo /usr/src/linux-headers-$(uname --kernel-release)/scripts/sign-file sha256 
fglrx_private_key.priv fglrx_x509.der $(modinfo --filename fglrx-updates)

I then reinstalled 3.13.0-92 with 'sudo apt-get install 
linux-signed-image-generic' as instructed.
Since this created a new fglrx_updates.ko at 
/lib/modules/3.13.0-92-generic/updates/dkms/fglrx_updates.ko, I signed that 
too, with
sudo /usr/src/linux-headers-3.13.0-92-generic/scripts/sign-file sha256 
fglrx_private_key.priv fglrx_x509.der 
/lib/modules/3.13.0-92-generic/updates/dkms/fglrx_updates.ko

It appears the module is indeed signed:
$ hexdump -C /lib/modules/3.13.0-92-generic/updates/dkms/fglrx_updates.ko | 
tail -n 5
00f7c5b0  4d 6f 64 75 6c 65 20 73  69 67 6e 61 74 75 72 65  |Module signature|
00f7c5c0  20 61 70 70 65 6e 64 65  64 7e 0a | appended~.|
And the key is listed by mokutil --list-enrolled.

And yet, I still have the same symptom: if I boot to 3.13.0-92 rather
than 3.13.0-91, I can get tty1, but Ctrl+Alt+F7 gives me a black screen
with a blinking cursor.

I never heard of debconf before today. Google tells me that debconf is
related to answering configuration questions while installing packages.
Is that related? There weren't any questions when installing linux-
signed-image-generic. Were there supposed to be?

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

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1568211] Re: Unable to boot

[Charlie McMackin]

Is there a big difference between bug #1568429 and this one? If not,
I've attached all the apport data I know how to on that bug and am
willing to run commands / help debug if devs with more know-how can
point me in right direction...

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

Title:
  Unable to boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I upgraded overnight from Wily to Xenial. The system will not boot.
  Only a blank screen after grub loads the kernel.

  The recovery kernel loads fine and I was able to find the following
  messages:

  [drm] VGACON disable radeon kernel modesetting
  [drm:radeon_init [radeon]] *ERROR* no UMS support in radeon module!

  The recovery kernel command line had a nomodeset parameter that was
  not in the main kernel command line.

  Note: For what it's worth I reported a similar issue against several
  Utopic kernels (bug #1407505). There was a back and forth with
  jsalisbury until a kernel finally worked. I have had no problems until
  today.

  WORKAROUND: Adding the nomodeset parameter the main kernel command
  line finally booted the system.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Dragan S.]

Hi Talat-

any update on this issue?

Thanks

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1604036] Re: Upgrade printer-driver-ptouch to support Brother QL-570

[Alberto Salvia Novella]

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

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

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

** Changed in: ptouch-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Upgrade printer-driver-ptouch to support Brother QL-570

Status in hwdata package in Ubuntu:
  Confirmed
Status in libosinfo package in Ubuntu:
  Confirmed
Status in ptouch-driver package in Ubuntu:
  Fix Released
Status in usbutils package in Ubuntu:
  Confirmed

Bug description:
  Please, upgrade printer-driver-ptouch to support Brother QL-570
  P-touch Label Printer. See https://bitbucket.org/philpem/printer-
  driver-ptouch/issues/2/negativeprint-and-cutmedia-jobend-doesnt
  (motivate maintainers of printer-driver-ptouch to bump their version
  number and release a version that supports QL-570) and also upgrade
  usbutils to include https://usb-ids.gowdy.us/read/UD/04f9/2028

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

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

[Kernel-packages] [Bug 1604153] onza (i386) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-66.74/onza__3.19.0-66.74__2016-07-21_19-18-00/results-index.html

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

Title:
  linux: 3.19.0-66.74 -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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1603719] Re: [regression] NFS client: access problems after updating to kernel 4.4.0-31-generic

[Joseph Salisbury]

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

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

Title:
  [regression] NFS client: access problems after updating to kernel
  4.4.0-31-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am denied access to the subfilesystems exported by my nfs server
  (the top level filesystem itself is unaffected).

  The client is reporting that I do not have the necessary permissions.
  However, all was fine until the day before yesterday.

  When I revert my client to 4.4.0-28, everything is in working order again. I 
assume the permission problem is really a bug in kernel 4.4.0-31.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jurgen 1743 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=569da237-3a37-4fe3-b885-83213aae8b52
  InstallationDate: Installed on 2016-04-07 (101 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7514
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=f6f6bd51-4d4f-4547-b615-90319625d909 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/28/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7514
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.1:bd05/28/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7514:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7514:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7514
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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

[Kernel-packages] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu

[Joseph Salisbury]

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

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

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

Title:
  Broadwell ECRC Support missing in Ubuntu

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

Bug description:
  Here is the problem statement from the Dell team:

  When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel
  Quick Assist Card, the memory location that corresponds to ECRC is set
  to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot.
  This causes the card to not function unless we implement the following
  workaround using setpci.

  “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for
  the Intel Quick Assit Card.

  We’ve verified the memory location is correct when booting to other
  OSes, such as RHEL 7.2 and Windows Server 2012 R2.

  If there is any information you can give as to why this may be
  occurring in Ubuntu or where we may start to debug when the memory is
  changed, we would appreciate it.

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

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

[Kernel-packages] [Bug 1603719] Re: [regression] NFS client: access problems after updating to kernel 4.4.0-31-generic

[Andy Whitcroft]

** Tags added: regression-updates

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

Title:
  [regression] NFS client: access problems after updating to kernel
  4.4.0-31-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am denied access to the subfilesystems exported by my nfs server
  (the top level filesystem itself is unaffected).

  The client is reporting that I do not have the necessary permissions.
  However, all was fine until the day before yesterday.

  When I revert my client to 4.4.0-28, everything is in working order again. I 
assume the permission problem is really a bug in kernel 4.4.0-31.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jurgen 1743 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=569da237-3a37-4fe3-b885-83213aae8b52
  InstallationDate: Installed on 2016-04-07 (101 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7514
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=f6f6bd51-4d4f-4547-b615-90319625d909 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/28/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7514
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.1:bd05/28/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7514:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7514:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7514
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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

[Kernel-packages] [Bug 1605267] Re: Building kernel pachakges failed

[Sven]

There is no log

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

Title:
  Building kernel pachakges failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello!

  This command failed: make-kpkg --append-to-version=-test-12 --initrd 
kernel_image
  I tried to build a kernel packages with kernel 3.13.0-92.139 on Ubuntu 
14.04.4 LTS:

  WARNING: modpost: Found 3 section mismatch(es).
  To see full details build your kernel with:
  'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC  init/version.o
LD  init/built-in.o
KSYM.tmp_kallsyms1.o
KSYM.tmp_kallsyms2.o
LD  vmlinux
SORTEX  vmlinux
SYSMAP  System.map
VOFFSET arch/x86/boot/voffset.h
CC  arch/x86/boot/version.o
OBJCOPY arch/x86/boot/compressed/vmlinux.bin
GZIParch/x86/boot/compressed/vmlinux.bin.gz
MKPIGGY arch/x86/boot/compressed/piggy.S
AS  arch/x86/boot/compressed/piggy.o
LD  arch/x86/boot/compressed/vmlinux
  arch/x86/boot/compressed/head_64.o: In function `efi64_config':
  (.data+0x90): undefined reference to `efi_call6'
  make[3]: *** [arch/x86/boot/compressed/vmlinux] Error 1
  make[2]: *** [arch/x86/boot/compressed/vmlinux] Error 2
  make[1]: *** [bzImage] Error 2
  make[1]: Leaving directory `/usr/src/linux-source-3.13.0/linux-source-3.13.0'
  make: *** [debian/stamp/build/kernel] Error 2

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

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

[Kernel-packages] [Bug 1602717] Re: hw-detect modprobes blindly, ignoring blacklists

[bugproxy]

** Package changed: hw-detect (Ubuntu) => linux (Ubuntu)

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

Title:
  hw-detect modprobes blindly, ignoring blacklists

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
  ---Problem Description---
  modprobe does not honor blacklist options in kernel cmdline unless -b is used 
(at least on the installer)

  The modprobe.blacklist option is required as a work-around until a solution 
to a device-driver bug is found (IBM LTC bug 138273).
   
  I've gone through the code of the kmod src pkg, but didn't spot anything 
obvious.
  Passing along to the Ubuntu team.

  Contact Information = Mauricio Faria de Oliveira  / 
Lekshmi C. Pillai  

  ---Steps to Reproduce---
   Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes 
is not required, but is here just in case):
  modprobe.blacklist=scsi_dh_alua,scsi-dh-alua

  On the dialog for username/password, select Go Back, then Exit to
  shell:

  The blacklist is detected/present in the config:

  ~ # modprobe -c | grep alua
  blacklist scsi_dh_alua
  blacklist scsi-dh-alua

  But the module is insmod-ed anyway:

  ~ # modprobe -v -n scsi-dh-alua
  insmod 
/lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
 

  Unless -b is used:

  ~ # modprobe -v -n -b scsi-dh-alua
  ~ #

  Installer kernel:
  [0.00] Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 
18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)

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

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

[Kernel-packages] [Bug 1602717] [NEW] hw-detect modprobes blindly, ignoring blacklists

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
---Problem Description---
modprobe does not honor blacklist options in kernel cmdline unless -b is used 
(at least on the installer)

The modprobe.blacklist option is required as a work-around until a solution to 
a device-driver bug is found (IBM LTC bug 138273).
 
I've gone through the code of the kmod src pkg, but didn't spot anything 
obvious.
Passing along to the Ubuntu team.

Contact Information = Mauricio Faria de Oliveira  / 
Lekshmi C. Pillai  
  
---Steps to Reproduce---
 Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes is 
not required, but is here just in case):
modprobe.blacklist=scsi_dh_alua,scsi-dh-alua

On the dialog for username/password, select Go Back, then Exit to shell:

The blacklist is detected/present in the config:

~ # modprobe -c | grep alua
blacklist scsi_dh_alua
blacklist scsi-dh-alua

But the module is insmod-ed anyway:

~ # modprobe -v -n scsi-dh-alua
insmod 
/lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
 

Unless -b is used:

~ # modprobe -v -n -b scsi-dh-alua
~ #

Installer kernel:
[0.00] Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 
18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-143679 severity-high 
targetmilestone-inin16041
-- 
hw-detect modprobes blindly, ignoring blacklists
https://bugs.launchpad.net/bugs/1602717
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 1603655] Re: After update, xorg will not boot

[Steve Langasek]

>From the log file:

Setting up shim-signed (1.17~14.04.1+0.8-0ubuntu2) ...
Installing for x86_64-efi platform.
Installation finished. No error reported.
Use of uninitialized value $_[1] in join or string at 
/usr/share/perl5/Debconf/DbDriver/Stack.pm line 111,  line 12.
Use of uninitialized value $val in substitution (s///) at 
/usr/share/perl5/Debconf/Format/822.pm line 83,  line 8.
Use of uninitialized value $val in concatenation (.) or string at 
/usr/share/perl5/Debconf/Format/822.pm line 84,  line 8.
Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
Log ended: 2016-07-15  19:57:06

This does confirm some sort of debconf error.

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

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1602717] Re: hw-detect modprobes blindly, ignoring blacklists

[Adam Conrad]

Indeed, this is still a valid hw-detect bug/wishlist, I was just hoping
the driver updates would get you over your current hump, so please do
check that.

** Package changed: linux (Ubuntu) => hw-detect (Ubuntu)

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

Title:
  hw-detect modprobes blindly, ignoring blacklists

Status in hw-detect package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
  ---Problem Description---
  modprobe does not honor blacklist options in kernel cmdline unless -b is used 
(at least on the installer)

  The modprobe.blacklist option is required as a work-around until a solution 
to a device-driver bug is found (IBM LTC bug 138273).
   
  I've gone through the code of the kmod src pkg, but didn't spot anything 
obvious.
  Passing along to the Ubuntu team.

  Contact Information = Mauricio Faria de Oliveira  / 
Lekshmi C. Pillai  

  ---Steps to Reproduce---
   Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes 
is not required, but is here just in case):
  modprobe.blacklist=scsi_dh_alua,scsi-dh-alua

  On the dialog for username/password, select Go Back, then Exit to
  shell:

  The blacklist is detected/present in the config:

  ~ # modprobe -c | grep alua
  blacklist scsi_dh_alua
  blacklist scsi-dh-alua

  But the module is insmod-ed anyway:

  ~ # modprobe -v -n scsi-dh-alua
  insmod 
/lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
 

  Unless -b is used:

  ~ # modprobe -v -n -b scsi-dh-alua
  ~ #

  Installer kernel:
  [0.00] Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 
18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1602717/+subscriptions

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

[Kernel-packages] [Bug 1604153] onza (amd64) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-66.74/onza__3.19.0-66.74__2016-07-21_18-05-00/results-index.html

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

Title:
  linux: 3.19.0-66.74 -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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Joseph Salisbury]

@balbirs, are you saying the repo you cloned from
https://git.launchpad.net/~kamalmostafa/ubuntu/+source/linux/+git/xenial/log/?h=lp1573062
differs from your diffs?

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

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

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

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

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

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

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

[Kernel-packages] [Bug 1605142] Re: On timespect_trunc function issue.

[Joseph Salisbury]

Thank you for providing a patch, and making Ubuntu better.

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

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

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

Title:
  On timespect_trunc function issue.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  More info with perf report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu4583 F pulseaudio
  CurrentDesktop: LXDE
  Date: Thu Jul 21 12:07:37 2016
  InstallationDate: Installed on 2016-04-29 (82 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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

[Kernel-packages] [Bug 1605056] Re: On __internal_add_timer func issue.

[Joseph Salisbury]

Thank you for providing a patch, and making Ubuntu better.

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

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

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

Title:
  On  __internal_add_timer func issue.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  More info with perf report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu4534 F pulseaudio
  CurrentDesktop: LXDE
  Date: Thu Jul 21 07:50:47 2016
  InstallationDate: Installed on 2016-04-29 (82 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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

[Kernel-packages] [Bug 1605197] Re: On add_nr_running , sub_nr_running issue.

[Joseph Salisbury]

Thank you for providing a patch, and making Ubuntu better.

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

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

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

Title:
  On add_nr_running , sub_nr_running issue.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  For more info check perf report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu4489 F pulseaudio
  CurrentDesktop: LXDE
  Date: Thu Jul 21 14:28:19 2016
  InstallationDate: Installed on 2016-04-29 (82 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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

[Kernel-packages] [Bug 1605344] Re: Regression caused by `fuse: Add support for pid namespaces` in 4.4.0-6.21

[Seth Forshee]

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Regression caused by `fuse: Add support for pid namespaces` in
  4.4.0-6.21

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

Bug description:
  The discussion starts at
  http://thread.gmane.org/gmane.linux.kernel.cgroups/15960/focus=2269876

  Commit in the tree is:

  commit a166e6726c6e12e28ac8489ff4e2faff7065a856
  Author: Seth Forshee 
  Date:   Wed Jul 2 16:29:19 2014 -0500

  UBUNTU: SAUCE: fuse: Add support for pid namespaces

  Description of the issue(copied from my report of lkml):

  This patch caused a regression in our major container use case with
  FUSE in Ubuntu 16.04, as patch was checked in as Ubuntu Sauce in
  Ubuntu 4.4.0-6.21 kernel.

  The use case is:
  1. Create a Docker container.
  2. Inside the container, start the FUSE backend, and mounted fs.
  3. Following step 2 in the container, create a loopback device to map
  a file in the mounted fuse to create a block device, which will be
  available to the whole system.

  It works well before this commit.

  The use case is broken because no matter which namespace losetup runs,
  the real request from loopback device seems always come from init ns,
  thus it will be in different ns running fuse backend. So the request
  will got denied, because the ns running fuse won't able to see the
  things from higher level(level 0 in fact) pid namespace.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature:
   
  Tags:  trusty
  Uname: Linux 4.4.6 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1605344] Re: Regression caused by `fuse: Add support for pid namespaces` in 4.4.0-6.21

[Joseph Salisbury]

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

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

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

Title:
  Regression caused by `fuse: Add support for pid namespaces` in
  4.4.0-6.21

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

Bug description:
  The discussion starts at
  http://thread.gmane.org/gmane.linux.kernel.cgroups/15960/focus=2269876

  Commit in the tree is:

  commit a166e6726c6e12e28ac8489ff4e2faff7065a856
  Author: Seth Forshee 
  Date:   Wed Jul 2 16:29:19 2014 -0500

  UBUNTU: SAUCE: fuse: Add support for pid namespaces

  Description of the issue(copied from my report of lkml):

  This patch caused a regression in our major container use case with
  FUSE in Ubuntu 16.04, as patch was checked in as Ubuntu Sauce in
  Ubuntu 4.4.0-6.21 kernel.

  The use case is:
  1. Create a Docker container.
  2. Inside the container, start the FUSE backend, and mounted fs.
  3. Following step 2 in the container, create a loopback device to map
  a file in the mounted fuse to create a block device, which will be
  available to the whole system.

  It works well before this commit.

  The use case is broken because no matter which namespace losetup runs,
  the real request from loopback device seems always come from init ns,
  thus it will be in different ns running fuse backend. So the request
  will got denied, because the ns running fuse won't able to see the
  things from higher level(level 0 in fact) pid namespace.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature:
   
  Tags:  trusty
  Uname: Linux 4.4.6 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1605344] Re: Regression caused by `fuse: Add support for pid namespaces` in 4.4.0-6.21

[Sheng Yang]

Hi Brad,

I am running self-compiled Ubuntu 16.04 kernel in 14.04 because I need
to bisect the problematic commit. And I opened this bug per Seth's
request. He also said he want bug assigned to him.

Do I need to get a new Ubuntu 16.04 environment for reporting this bug?

** Tags added: apport-collected trusty

** Description changed:

  The discussion starts at
  http://thread.gmane.org/gmane.linux.kernel.cgroups/15960/focus=2269876
  
  Commit in the tree is:
  
  commit a166e6726c6e12e28ac8489ff4e2faff7065a856
  Author: Seth Forshee 
  Date:   Wed Jul 2 16:29:19 2014 -0500
  
  UBUNTU: SAUCE: fuse: Add support for pid namespaces
  
  Description of the issue(copied from my report of lkml):
  
  This patch caused a regression in our major container use case with
  FUSE in Ubuntu 16.04, as patch was checked in as Ubuntu Sauce in
  Ubuntu 4.4.0-6.21 kernel.
  
  The use case is:
  1. Create a Docker container.
  2. Inside the container, start the FUSE backend, and mounted fs.
  3. Following step 2 in the container, create a loopback device to map
  a file in the mounted fuse to create a block device, which will be
  available to the whole system.
  
  It works well before this commit.
  
  The use case is broken because no matter which namespace losetup runs,
  the real request from loopback device seems always come from init ns,
  thus it will be in different ns running fuse backend. So the request
  will got denied, because the ns running fuse won't able to see the
  things from higher level(level 0 in fact) pid namespace.
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.21
+ Architecture: amd64
+ DistroRelease: Ubuntu 14.04
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature:
+  
+ Tags:  trusty
+ Uname: Linux 4.4.6 x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

** Tags removed: apport-collected trusty
** Tags added: xenial

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

Title:
  Regression caused by `fuse: Add support for pid namespaces` in
  4.4.0-6.21

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The discussion starts at
  http://thread.gmane.org/gmane.linux.kernel.cgroups/15960/focus=2269876

  Commit in the tree is:

  commit a166e6726c6e12e28ac8489ff4e2faff7065a856
  Author: Seth Forshee 
  Date:   Wed Jul 2 16:29:19 2014 -0500

  UBUNTU: SAUCE: fuse: Add support for pid namespaces

  Description of the issue(copied from my report of lkml):

  This patch caused a regression in our major container use case with
  FUSE in Ubuntu 16.04, as patch was checked in as Ubuntu Sauce in
  Ubuntu 4.4.0-6.21 kernel.

  The use case is:
  1. Create a Docker container.
  2. Inside the container, start the FUSE backend, and mounted fs.
  3. Following step 2 in the container, create a loopback device to map
  a file in the mounted fuse to create a block device, which will be
  available to the whole system.

  It works well before this commit.

  The use case is broken because no matter which namespace losetup runs,
  the real request from loopback device seems always come from init ns,
  thus it will be in different ns running fuse backend. So the request
  will got denied, because the ns running fuse won't able to see the
  things from higher level(level 0 in fact) pid namespace.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature:
   
  Tags:  trusty
  Uname: Linux 4.4.6 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1604153] Re: linux: 3.19.0-66.74 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1604153

Title:
  linux: 3.19.0-66.74 -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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Steve Beattie]

USN Needed

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

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

Title:
  linux-lts-vivid: 3.19.0-66.74~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:
  Fix Released
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-66.74~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
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1604153
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1603719] Re: NFS client: access problems after updating to kernel 4.4.0-31-generic

[Bryan Quigley]

I also tried Upstream v4.4.15 (35467dc7630af60abacc330f64029d081f160530)
which does not have the issue.  Going to bisect shortly.

** Summary changed:

- NFS client: access problems after updating to kernel 4.4.0-31-generic
+ [regression] NFS client: access problems after updating to kernel 
4.4.0-31-generic

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

Title:
  [regression] NFS client: access problems after updating to kernel
  4.4.0-31-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am denied access to the subfilesystems exported by my nfs server
  (the top level filesystem itself is unaffected).

  The client is reporting that I do not have the necessary permissions.
  However, all was fine until the day before yesterday.

  When I revert my client to 4.4.0-28, everything is in working order again. I 
assume the permission problem is really a bug in kernel 4.4.0-31.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jurgen 1743 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=569da237-3a37-4fe3-b885-83213aae8b52
  InstallationDate: Installed on 2016-04-07 (101 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7514
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=f6f6bd51-4d4f-4547-b615-90319625d909 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/28/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7514
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.1:bd05/28/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7514:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7514:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7514
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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

[Kernel-packages] [Bug 1604134] Re: linux: 3.13.0-93.140 -proposed tracker

[Steve Beattie]

USN needed

** Changed in: kernel-sru-workflow/security-signoff
   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/1604134

Title:
  linux: 3.13.0-93.140 -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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Steve Beattie]

USN needed


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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-93.140~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
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1604134
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1604443] onibi (amd64) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-32.51/onibi__4.4.0-32.51__2016-07-21_17-08-00/results-index.html

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

Title:
  linux: 4.4.0-32.51 -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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Brad Figg]

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

apport-collect 1605344

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

Title:
  Regression caused by `fuse: Add support for pid namespaces` in
  4.4.0-6.21

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The discussion starts at
  http://thread.gmane.org/gmane.linux.kernel.cgroups/15960/focus=2269876

  Commit in the tree is:

  commit a166e6726c6e12e28ac8489ff4e2faff7065a856
  Author: Seth Forshee 
  Date:   Wed Jul 2 16:29:19 2014 -0500

  UBUNTU: SAUCE: fuse: Add support for pid namespaces

  Description of the issue(copied from my report of lkml):

  This patch caused a regression in our major container use case with
  FUSE in Ubuntu 16.04, as patch was checked in as Ubuntu Sauce in
  Ubuntu 4.4.0-6.21 kernel.

  The use case is:
  1. Create a Docker container.
  2. Inside the container, start the FUSE backend, and mounted fs.
  3. Following step 2 in the container, create a loopback device to map
  a file in the mounted fuse to create a block device, which will be
  available to the whole system.

  It works well before this commit.

  The use case is broken because no matter which namespace losetup runs,
  the real request from loopback device seems always come from init ns,
  thus it will be in different ns running fuse backend. So the request
  will got denied, because the ns running fuse won't able to see the
  things from higher level(level 0 in fact) pid namespace.

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

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

[Kernel-packages] [Bug 1604153] onza (i386) - tests ran: 20, failed: 1

[Brad Figg]

tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-66.74/onza__3.19.0-66.74__2016-07-21_16-17-00/results-index.html

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

Title:
  linux: 3.19.0-66.74 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1605344] [NEW] Regression caused by `fuse: Add support for pid namespaces` in 4.4.0-6.21

[Sheng Yang]

Public bug reported:

The discussion starts at
http://thread.gmane.org/gmane.linux.kernel.cgroups/15960/focus=2269876

Commit in the tree is:

commit a166e6726c6e12e28ac8489ff4e2faff7065a856
Author: Seth Forshee 
Date:   Wed Jul 2 16:29:19 2014 -0500

UBUNTU: SAUCE: fuse: Add support for pid namespaces

Description of the issue(copied from my report of lkml):

This patch caused a regression in our major container use case with
FUSE in Ubuntu 16.04, as patch was checked in as Ubuntu Sauce in
Ubuntu 4.4.0-6.21 kernel.

The use case is:
1. Create a Docker container.
2. Inside the container, start the FUSE backend, and mounted fs.
3. Following step 2 in the container, create a loopback device to map
a file in the mounted fuse to create a block device, which will be
available to the whole system.

It works well before this commit.

The use case is broken because no matter which namespace losetup runs,
the real request from loopback device seems always come from init ns,
thus it will be in different ns running fuse backend. So the request
will got denied, because the ns running fuse won't able to see the
things from higher level(level 0 in fact) pid namespace.

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

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

Title:
  Regression caused by `fuse: Add support for pid namespaces` in
  4.4.0-6.21

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The discussion starts at
  http://thread.gmane.org/gmane.linux.kernel.cgroups/15960/focus=2269876

  Commit in the tree is:

  commit a166e6726c6e12e28ac8489ff4e2faff7065a856
  Author: Seth Forshee 
  Date:   Wed Jul 2 16:29:19 2014 -0500

  UBUNTU: SAUCE: fuse: Add support for pid namespaces

  Description of the issue(copied from my report of lkml):

  This patch caused a regression in our major container use case with
  FUSE in Ubuntu 16.04, as patch was checked in as Ubuntu Sauce in
  Ubuntu 4.4.0-6.21 kernel.

  The use case is:
  1. Create a Docker container.
  2. Inside the container, start the FUSE backend, and mounted fs.
  3. Following step 2 in the container, create a loopback device to map
  a file in the mounted fuse to create a block device, which will be
  available to the whole system.

  It works well before this commit.

  The use case is broken because no matter which namespace losetup runs,
  the real request from loopback device seems always come from init ns,
  thus it will be in different ns running fuse backend. So the request
  will got denied, because the ns running fuse won't able to see the
  things from higher level(level 0 in fact) pid namespace.

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

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

[Kernel-packages] [Bug 1603655] Re: After update, xorg will not boot

[dualBootLaptop]

/var/log/apt/term.log

** Attachment added: "term.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603655/+attachment/4704824/+files/term.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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[bugproxy]

--- Comment From cdead...@us.ibm.com 2016-07-21 13:15 EDT---
 State: Working by: tgrobeck on 21 July 2016 12:07:44 
I have tested that with the 4.4.0-31 kernel (which I am told has the patch), an 
adapter in slot C9 will not cause the system to boot up to the operating system.

Cold IPLed the system twice with an adapter in the P1-C9 slot, and the
system IPLed to the operating system both times.

root@x1517p1:~# uname -a
Linux x1517p1 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

root@x1517p1:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.1 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.1 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
UBUNTU_CODENAME=xenial

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

Title:
  FlashGT - In Tuleta 8284-22A with card in card slot P1-C9, system
  Fails to boot operating system

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

Bug description:
  Placed card in card slot P1-C9
  After powering chassis on, system comes up to Petitboot and attempts to load 
operating system.
  "Ubuntu 16.04.  .  .  ." continues to print on the console for about 2 or 
more minutes, then system drops to an "(initramfs)" prompt.
  When attemped to "exit", message indicated:
  "Gave up waiting for root device.  Common problems:
   - Boot args (cat /proc/cmdline)
 - Check rootdelay= (did the system wait long enough?)
 - Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  UUID=4211fb0b-382d-4f3f-8fbd-47b57e24326d does not exist.  Dropping 
to a shell!

  BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)"

  
  In order to have this bug solved, we need to have the following patch 
integrated. Can Canonical please include it in 16.04 kernel?

  https://patchwork.ozlabs.org/patch/642920/

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

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

[Kernel-packages] [Bug 1604443] Re: linux: 4.4.0-32.51 -proposed tracker

[Steve Beattie]

USN Needed

** Changed in: kernel-sru-workflow/security-signoff
   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/1604443

Title:
  linux: 4.4.0-32.51 -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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1604314] Re: [Xenial] iommu/amd: Fix unity mapping initialization race

[Ganesh Lakshminarayana]

** Attachment added: "Screen shot of the error"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604314/+attachment/4704776/+files/Bug%20160314%20initramfs.jpg

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

Title:
  [Xenial] iommu/amd: Fix unity mapping initialization race

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

Bug description:
  == Xenial SRU Justification ==
  HP Gen8 servers were having kernel panics with the 4.2 and 4.4 kernel which 
is apparently resolved with the following commits.  HP would like to see these 
SRU'd for Xenial.

  commit 0caa7616a6aca449dd68b58cb29bd491d296c2d5
  Author: Aaron Campbell 
  Date:   Sat Jul 2 21:23:24 2016 -0300

  iommu/vt-d: Fix infinite loop in free_all_cpu_cached_iovas

  commit 522e5cb76d0663c88f96b6a8301451c8efa37207
  Author: Joerg Roedel 
  Date:   Fri Jul 1 16:42:55 2016 +0200

  iommu/amd: Fix unity mapping initialization race

  == Testing ==
  HP confirms their testing shows these patches resolves the issue on several 
test machines.

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

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

[Kernel-packages] [Bug 1604314] Re: [Xenial] iommu/amd: Fix unity mapping initialization race

[Ganesh Lakshminarayana]

** Attachment added: "Lock up error"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604314/+attachment/4704777/+files/Bug%20160314%20lock%20up.jpg

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

Title:
  [Xenial] iommu/amd: Fix unity mapping initialization race

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

Bug description:
  == Xenial SRU Justification ==
  HP Gen8 servers were having kernel panics with the 4.2 and 4.4 kernel which 
is apparently resolved with the following commits.  HP would like to see these 
SRU'd for Xenial.

  commit 0caa7616a6aca449dd68b58cb29bd491d296c2d5
  Author: Aaron Campbell 
  Date:   Sat Jul 2 21:23:24 2016 -0300

  iommu/vt-d: Fix infinite loop in free_all_cpu_cached_iovas

  commit 522e5cb76d0663c88f96b6a8301451c8efa37207
  Author: Joerg Roedel 
  Date:   Fri Jul 1 16:42:55 2016 +0200

  iommu/amd: Fix unity mapping initialization race

  == Testing ==
  HP confirms their testing shows these patches resolves the issue on several 
test machines.

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

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

[Kernel-packages] [Bug 1604314] Re: [Xenial] iommu/amd: Fix unity mapping initialization race

[Ganesh Lakshminarayana]

Please find the working below:

Installed Ubuntu 16.04 on AMD box with iommu disabled.

Installed the given kernel patches:

ubuntu@172-20-0-246:~/DL385p Gen8$ sudo dpkg -i 
linux-headers-4.4.0-32_4.4.0-32.51_all.deb
[sudo] password for ubuntu:
Selecting previously unselected package linux-headers-4.4.0-32.
(Reading database ... 59336 files and directories currently installed.)
Preparing to unpack linux-headers-4.4.0-32_4.4.0-32.51_all.deb ...
Unpacking linux-headers-4.4.0-32 (4.4.0-32.51) ...
Setting up linux-headers-4.4.0-32 (4.4.0-32.51) ...

ubuntu@172-20-0-246:~/DL385p Gen8$ sudo dpkg -i 
linux-headers-4.4.0-32-generic_4.4.0-32.51_amd64.deb
Selecting previously unselected package linux-headers-4.4.0-32-generic.
(Reading database ... 76213 files and directories currently installed.)
Preparing to unpack linux-headers-4.4.0-32-generic_4.4.0-32.51_amd64.deb ...
Unpacking linux-headers-4.4.0-32-generic (4.4.0-32.51) ...
Setting up linux-headers-4.4.0-32-generic (4.4.0-32.51) ...

ubuntu@172-20-0-246:~/DL385p Gen8$ sudo dpkg -i 
linux-libc-dev_4.4.0-32.51_amd64.deb
Selecting previously unselected package linux-libc-dev:amd64.
(Reading database ... 85965 files and directories currently installed.)
Preparing to unpack linux-libc-dev_4.4.0-32.51_amd64.deb ...
Unpacking linux-libc-dev:amd64 (4.4.0-32.51) ...
Setting up linux-libc-dev:amd64 (4.4.0-32.51) ...

ubuntu@172-20-0-246:~/DL385p Gen8$ sudo dpkg -i 
linux-image-4.4.0-32-generic_4.4.0-32.51_amd64.deb
Selecting previously unselected package linux-image-4.4.0-32-generic.
(Reading database ... 86776 files and directories currently installed.)
Preparing to unpack linux-image-4.4.0-32-generic_4.4.0-32.51_amd64.deb ...
Done.
Unpacking linux-image-4.4.0-32-generic (4.4.0-32.51) ...
Setting up linux-image-4.4.0-32-generic (4.4.0-32.51) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-32-generic 
/boot/vmlinuz-4.4.0-32-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-32-generic 
/boot/vmlinuz-4.4.0-32-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-32-generic
W: plymouth: The plugin label.so is missing, the selected theme might not work 
as expected.
W: plymouth: You might want to install the plymouth-themes and plymouth-label 
package to fix this.
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.4.0-32-generic /boot/vmlinuz-4.4.0-32-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-32-generic 
/boot/vmlinuz-4.4.0-32-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-32-generic 
/boot/vmlinuz-4.4.0-32-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-32-generic
Found initrd image: /boot/initrd.img-4.4.0-32-generic
Found linux image: /boot/vmlinuz-4.4.0-21-generic
Found initrd image: /boot/initrd.img-4.4.0-21-generic
done

ubuntu@172-20-0-246:~/DL385p Gen8$ sudo apt-get install plymouth-themes
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  fontconfig fontconfig-config fonts-dejavu-core libcairo2 libdatrie1 
libfontconfig1 libgraphite2-3 libharfbuzz0b libpango-1.0-0 libpangocairo-1.0-0 
libpangoft2-1.0-0 libpixman-1-0 libthai-data libthai0 libxcb-render0 libxcb-shm0
  libxrender1 plymouth plymouth-label plymouth-theme-ubuntu-text 
ttf-ubuntu-font-family
Suggested packages:
  desktop-base
The following NEW packages will be installed:
  fontconfig fontconfig-config fonts-dejavu-core libcairo2 libdatrie1 
libfontconfig1 libgraphite2-3 libharfbuzz0b libpango-1.0-0 libpangocairo-1.0-0 
libpangoft2-1.0-0 libpixman-1-0 libthai-data libthai0 libxcb-render0 libxcb-shm0
  libxrender1 plymouth-label plymouth-themes ttf-ubuntu-font-family
The following packages will be upgraded:
  plymouth plymouth-theme-ubuntu-text
2 upgraded, 20 newly installed, 0 to remove and 113 not upgraded.
Need to get 4,953 kB of archives.
After this operation, 14.3 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 fonts-dejavu-core 
all 2.35-1 [1,039 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 fontconfig-config 
all 2.11.94-0ubuntu1 [49.9 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 libfontconfig1 
amd64 2.11.94-0ubuntu1 [131 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 fontconfig amd64 
2.11.94-0ubuntu1 [178 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 plymouth 
amd64 0.9.2-3ubuntu13.1 [107 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
plymouth-theme-ubuntu-text amd64 0.9.2-3ubuntu13.1 [9,078 B]
Get:7 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 libpixman-1-0 amd64 
0.33.6-1 [231 kB]

[Kernel-packages] [Bug 1605276] Re: Please update linux-firmware to add 1.7 broxton firmware

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.159

---
linux-firmware (1.159) yakkety; urgency=medium

  * Rebase against 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
cccb6a0da98372bd66787710249727ad6b0aaf72 (LP: #1605276)
- linux-firmware: intel: Update Skylake audio firmware
- linux-firmware: update rt2860.bin, rt2800pci driver
- linux-firmware: update rt2870.bin, rt2800usb driver
- amdgpu: update firmware
- cxgb4: update firmware to revision 1.15.37.0
- qed: Add FW 8.10.5.0
- linux-firmware: intel: Add Broxton audio firmware
- linux-firmware: Update firmware patch for Intel Bluetooth 7260 (B3/B4)
- linux-firmware: Update firmware patch for Intel Bluetooth 7260 (B5/B6)
- linux-firmware: update audio firmware for Braswell platform
- radeon: add new CI smc firmware
- radeon: add new SI smc firmware
- linux-firmware: Update firmware patch for Intel Bluetooth 7265 (D1)
- linux-firmware: Update firmware patch for Intel Bluetooth 7265 (C0/D0)
- linux-firmware: Update firmware file for Intel Bluetooth 8260
- wl18xx: update firmware file
- linux-firmware: intel: Update Skylake audio firmware
- linux-firmware: Add firmware file for Intel Bluetooth 8265
- amdgpu: Update UVD firmware for Polaris
- amdgpu: update polaris ucode
- linux-firmware: intel: Update Broxton audio firmware
- linux-firmware: intel: Update Skylake audio firmware
- linux-firmware: New minor DMC release for Broxton - ver1_07
- linux-firmware: First DMC image for Kabylake.
- linux-firmware/i915: Step away from symbolic links and clean up repo.
- mediatek: Add mt8173 VPU firmware
- linux-firmware: Fix the filename for WsP to align with device HW_VARIANT
- nvidia: Add GP100 signed firmware
- iwlwifi: add new -17 firmware for iwlmvm devices
- iwlwifi: add new -22 firmware for 7265D and up
- amdgpu: update vce firmware for VI asics
- linux-firmware: intel: Add Kabylake audio firmware
- Add dptx firmware for rockchip rk3399

 -- Seth Forshee   Thu, 21 Jul 2016 09:55:19
-0500

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

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

Title:
  Please update linux-firmware to add 1.7 broxton firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  There was errata in the 1.6 Broxton DMC firmware currently in linux-
  firmware and it no longer loads on 4.7 and higher based systems, which
  includes i915_bpo now that it has been updated to a 4.7 based
  backport.

  This is the error:
  [2.470468] [drm] Refusing to load old DMC firmware v1.6, please upgrade 
to v1.7 or later [https://01.org/linuxgraphics/intel-linux-graphics-firmwares].
  [2.470476] i915 :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling 
runtime power management.

  Pleae cherry-pick http://git.kernel.org/cgit/linux/kernel/git/firmware
  /linux-
  firmware.git/commit/?id=5e976de9e02b55563c28555361a7763bc043f5ec for
  xenial

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 21 10:25:01 2016
  Dependencies:
   
  InstallationDate: Installed on 2016-01-06 (196 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[bugproxy]

--- Comment From mauri...@br.ibm.com 2016-07-21 12:08 EDT---
@adconrad,

> There were huge updates to the scsi_dh_alua driver in the 4.4.0-30 kernel.
> I can't see the LTC bug you referenced, so I can't tell if said updates
> address your issue, but I was hopeful. :P

Ok, I see. I'll ask if that helps w/ the other bug.

Nevertheless, having modprobe.blacklist working by default on the
installer would be interesting.

I passed around a sed line to use modprobe -b on hw-detect, a simple
workaround, but that definitely isn't  convenient (neither for preseed).
And since I don't know much of modprobe and its usage on the installer,
I decided to reach out for you guys first.

Now that is seems to be clear, can get hw-detect be updated to use
modprobe -b ?

Thanks!

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

Title:
  hw-detect modprobes blindly, ignoring blacklists

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
  ---Problem Description---
  modprobe does not honor blacklist options in kernel cmdline unless -b is used 
(at least on the installer)

  The modprobe.blacklist option is required as a work-around until a solution 
to a device-driver bug is found (IBM LTC bug 138273).
   
  I've gone through the code of the kmod src pkg, but didn't spot anything 
obvious.
  Passing along to the Ubuntu team.

  Contact Information = Mauricio Faria de Oliveira  / 
Lekshmi C. Pillai  

  ---Steps to Reproduce---
   Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes 
is not required, but is here just in case):
  modprobe.blacklist=scsi_dh_alua,scsi-dh-alua

  On the dialog for username/password, select Go Back, then Exit to
  shell:

  The blacklist is detected/present in the config:

  ~ # modprobe -c | grep alua
  blacklist scsi_dh_alua
  blacklist scsi-dh-alua

  But the module is insmod-ed anyway:

  ~ # modprobe -v -n scsi-dh-alua
  insmod 
/lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
 

  Unless -b is used:

  ~ # modprobe -v -n -b scsi-dh-alua
  ~ #

  Installer kernel:
  [0.00] Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 
18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)

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

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

[Kernel-packages] [Bug 1602717] Re: hw-detect modprobes blindly, ignoring blacklists

[bugproxy]

** Package changed: hw-detect (Ubuntu) => linux (Ubuntu)

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

Title:
  hw-detect modprobes blindly, ignoring blacklists

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
  ---Problem Description---
  modprobe does not honor blacklist options in kernel cmdline unless -b is used 
(at least on the installer)

  The modprobe.blacklist option is required as a work-around until a solution 
to a device-driver bug is found (IBM LTC bug 138273).
   
  I've gone through the code of the kmod src pkg, but didn't spot anything 
obvious.
  Passing along to the Ubuntu team.

  Contact Information = Mauricio Faria de Oliveira  / 
Lekshmi C. Pillai  

  ---Steps to Reproduce---
   Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes 
is not required, but is here just in case):
  modprobe.blacklist=scsi_dh_alua,scsi-dh-alua

  On the dialog for username/password, select Go Back, then Exit to
  shell:

  The blacklist is detected/present in the config:

  ~ # modprobe -c | grep alua
  blacklist scsi_dh_alua
  blacklist scsi-dh-alua

  But the module is insmod-ed anyway:

  ~ # modprobe -v -n scsi-dh-alua
  insmod 
/lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
 

  Unless -b is used:

  ~ # modprobe -v -n -b scsi-dh-alua
  ~ #

  Installer kernel:
  [0.00] Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 
18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)

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

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

[Kernel-packages] [Bug 1602785] Re: FlashGT - In Tuleta 8284-22A with card in card slot P1-C9, system Fails to boot operating system

[Kamal Mostafa]

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

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

Title:
  FlashGT - In Tuleta 8284-22A with card in card slot P1-C9, system
  Fails to boot operating system

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

Bug description:
  Placed card in card slot P1-C9
  After powering chassis on, system comes up to Petitboot and attempts to load 
operating system.
  "Ubuntu 16.04.  .  .  ." continues to print on the console for about 2 or 
more minutes, then system drops to an "(initramfs)" prompt.
  When attemped to "exit", message indicated:
  "Gave up waiting for root device.  Common problems:
   - Boot args (cat /proc/cmdline)
 - Check rootdelay= (did the system wait long enough?)
 - Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  UUID=4211fb0b-382d-4f3f-8fbd-47b57e24326d does not exist.  Dropping 
to a shell!

  BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)"

  
  In order to have this bug solved, we need to have the following patch 
integrated. Can Canonical please include it in 16.04 kernel?

  https://patchwork.ozlabs.org/patch/642920/

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

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

[Kernel-packages] [Bug 1602717] Re: hw-detect modprobes blindly, ignoring blacklists

[Steve Langasek]

** Package changed: linux (Ubuntu) => hw-detect (Ubuntu)

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

Title:
  hw-detect modprobes blindly, ignoring blacklists

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
  ---Problem Description---
  modprobe does not honor blacklist options in kernel cmdline unless -b is used 
(at least on the installer)

  The modprobe.blacklist option is required as a work-around until a solution 
to a device-driver bug is found (IBM LTC bug 138273).
   
  I've gone through the code of the kmod src pkg, but didn't spot anything 
obvious.
  Passing along to the Ubuntu team.

  Contact Information = Mauricio Faria de Oliveira  / 
Lekshmi C. Pillai  

  ---Steps to Reproduce---
   Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes 
is not required, but is here just in case):
  modprobe.blacklist=scsi_dh_alua,scsi-dh-alua

  On the dialog for username/password, select Go Back, then Exit to
  shell:

  The blacklist is detected/present in the config:

  ~ # modprobe -c | grep alua
  blacklist scsi_dh_alua
  blacklist scsi-dh-alua

  But the module is insmod-ed anyway:

  ~ # modprobe -v -n scsi-dh-alua
  insmod 
/lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
 

  Unless -b is used:

  ~ # modprobe -v -n -b scsi-dh-alua
  ~ #

  Installer kernel:
  [0.00] Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 
18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)

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

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

[Kernel-packages] [Bug 1602726] Re: nvme - reset_controller is not working after adapter's firmware upgrade (adapter quirk is needed)

[Kamal Mostafa]

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

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

Title:
  nvme - reset_controller is not working after adapter's firmware
  upgrade (adapter quirk is needed)

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

Bug description:
  == Comment: #16 - Guilherme Guaglianoni Piccoli  - 
2016-07-12 15:46:17 ==
  NVMe adapters provide an interface to reset the controller after a firmware 
(aka microcode) activation, so the new firmware can be used without rebooting 
the whole system, for example.

  To achieve this, firstly one activate the firmware with the command:
  "nvme fw-activate -a 2 -s 2 /dev/nvme0".

  And then, one can perform the reset right after the activate command succeed:
  "echo 1 > /sys/class/nvme/nvme0/reset_controller".

  
  The issue: in NVMe adapter from HGST vendor (PCI identification == 1c58:0003) 
this reset_controller feature does not work in recent kernels. The main reason 
is that the adapter is not dealing well with disabling the controller in the 
reset feature instead of shutdown it (as done in older kernels). To perform a 
successful reset, we need to delay 2 seconds before checking a specific bit 
during the reset process.

  This delay was implemented as a per-device quirk in the nvme driver,
  and is accepted upstream. Currently, it's present on Jens Axboe kernel
  tree, ready to be merged on upstream 4.8 merge window.

  We want to request the quirk's merge in Xenial's kernel. Below, the
  commit information on Axboe's tree:

  54adc01055b7 ("nvme/quirk: Add a delay before checking for adapter
  readiness")

  Link: https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  
block.git/commit/?h=for-4.8/drivers=54adc01055b75ec8769c5a36574c7a0895c0c0b2


  Thanks in advance,

  Guilherme

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

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

[Kernel-packages] [Bug 1603468] Re: ovs nat: conntrack netlink event are missing

[Kamal Mostafa]

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

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

Title:
  ovs nat: conntrack netlink event are missing

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

Bug description:
  Fixed upstream by this patch:
  d913d3a763a6 openvswitch: fix conntrack netlink event delivery

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

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

[Kernel-packages] [Bug 1603574] Re: Hotplug remove and re-add adds PCI adapter to next PCI domain (PCI)

[Kamal Mostafa]

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

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

Title:
  Hotplug remove and re-add adds PCI adapter to next PCI domain (PCI)

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

Bug description:
  == Comment: #26 - Guilherme Guaglianoni Piccoli  - 
2016-07-15 16:26:38 ==
  When performing hotplug operations in PowerPC currently, if we remove a PHB 
and re-add it later, its domain address is incremented. An example below (drmgr 
is the tool we use in PowerPC to perform this operation):

  
  (i) $>  lspci
  :60:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet
  :60:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet

  (ii) $>  drmgr -c phb -s "PHB 20" -r  # removing a PHB

  (iii) $>  lspci #empty

  (iv) $>  drmgr -c phb -s "PHB 20" -a  # re-adding the PHB

  (v) $>  lspci
  0001:60:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet
  0001:60:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet

  
  This behavior is harmful when kernel is using network predictable naming for 
interfaces, for example, since after the PHB re-add, the PCI address of NIC 
functions changes, and so the interfaces' naming also change. Recently, a patch 
was merged to powerpc-next to avoid this situation, by relating the PCI domain 
number with device-tree properties. With the patch, the above steps (i) and (v) 
present the same output for lspci.

  We want to ask Canonical to merge the patch in Ubuntu Xenial's kernel,
  since it will solve multiple bugs we've experienced by performing NIC
  hotplug - the commit is present on powerpc-next under the commit-id
  63a72284b15.

  A link to the patch:
  
https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?id=63a72284b159c569ec52f380c9

  Thanks in advance,


  Guilherme

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

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

[Kernel-packages] [Bug 1604153] onza (amd64) - tests ran: 20, failed: 0

[Brad Figg]

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-66.74/onza__3.19.0-66.74__2016-07-21_14-26-00/results-index.html

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

Title:
  linux: 3.19.0-66.74 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1602717] [NEW] hw-detect modprobes blindly, ignoring blacklists

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
---Problem Description---
modprobe does not honor blacklist options in kernel cmdline unless -b is used 
(at least on the installer)

The modprobe.blacklist option is required as a work-around until a solution to 
a device-driver bug is found (IBM LTC bug 138273).
 
I've gone through the code of the kmod src pkg, but didn't spot anything 
obvious.
Passing along to the Ubuntu team.

Contact Information = Mauricio Faria de Oliveira  / 
Lekshmi C. Pillai  
  
---Steps to Reproduce---
 Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes is 
not required, but is here just in case):
modprobe.blacklist=scsi_dh_alua,scsi-dh-alua

On the dialog for username/password, select Go Back, then Exit to shell:

The blacklist is detected/present in the config:

~ # modprobe -c | grep alua
blacklist scsi_dh_alua
blacklist scsi-dh-alua

But the module is insmod-ed anyway:

~ # modprobe -v -n scsi-dh-alua
insmod 
/lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
 

Unless -b is used:

~ # modprobe -v -n -b scsi-dh-alua
~ #

Installer kernel:
[0.00] Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 
18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-143679 severity-high 
targetmilestone-inin16041
-- 
hw-detect modprobes blindly, ignoring blacklists
https://bugs.launchpad.net/bugs/1602717
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 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

/etc/kernel/postinst.d/kdump-tools $(uname -r)

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

Title:
  makekdump should re-exec with cio_ignore on s390x

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress

Bug description:
  [SRU justification]
  kernel crash dump fails to work without the modification.

  [Impact]
  Broken functionality.

  [Fix]
  Add cio_ignore -k -y output to the kexec command.

  [Test Case]
  Follow indication in comment #2 to reproduce. With the fix, kdump will 
function as expected.

  [Regression]
  A regression situation is outlined in comment #16. Newer channel devices may 
not be visible because of the added cio_ignore output. This may be worked 
around with a single command. 

  The resolution outweights this limitation that can be easily worked
  around.

  [Original description of the problem]

  As per
  
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/comments/19

  We should re-exec with cio_ignore lines. As per report there, it
  should result in lowered required crashdump setting.

  Hypothetically, one should be able to test this imperially by lowering
  crashdump memory settings until kdump does not succeed anymore. And
  then generated and append `cio_ignore -k -u` to the
  KDUMP_CMDLINE_APPEND= and see that kdump starts working again with a
  lower memory usage.

  Once this is developed / verified / tested, we should probably SRU
  this back to xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1570775/+subscriptions

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

[Kernel-packages] [Bug 1602717] Re: hw-detect modprobes blindly, ignoring blacklists

[bugproxy]

** Package changed: hw-detect (Ubuntu) => linux (Ubuntu)

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

Title:
  hw-detect modprobes blindly, ignoring blacklists

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
  ---Problem Description---
  modprobe does not honor blacklist options in kernel cmdline unless -b is used 
(at least on the installer)

  The modprobe.blacklist option is required as a work-around until a solution 
to a device-driver bug is found (IBM LTC bug 138273).
   
  I've gone through the code of the kmod src pkg, but didn't spot anything 
obvious.
  Passing along to the Ubuntu team.

  Contact Information = Mauricio Faria de Oliveira  / 
Lekshmi C. Pillai  

  ---Steps to Reproduce---
   Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes 
is not required, but is here just in case):
  modprobe.blacklist=scsi_dh_alua,scsi-dh-alua

  On the dialog for username/password, select Go Back, then Exit to
  shell:

  The blacklist is detected/present in the config:

  ~ # modprobe -c | grep alua
  blacklist scsi_dh_alua
  blacklist scsi-dh-alua

  But the module is insmod-ed anyway:

  ~ # modprobe -v -n scsi-dh-alua
  insmod 
/lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
 

  Unless -b is used:

  ~ # modprobe -v -n -b scsi-dh-alua
  ~ #

  Installer kernel:
  [0.00] Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 
18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)

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

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

[Kernel-packages] [Bug 1605276] Re: Please update linux-firmware to add 1.7 broxton firmware

[Seth Forshee]

** Changed in: linux-firmware (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Please update linux-firmware to add 1.7 broxton firmware

Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  There was errata in the 1.6 Broxton DMC firmware currently in linux-
  firmware and it no longer loads on 4.7 and higher based systems, which
  includes i915_bpo now that it has been updated to a 4.7 based
  backport.

  This is the error:
  [2.470468] [drm] Refusing to load old DMC firmware v1.6, please upgrade 
to v1.7 or later [https://01.org/linuxgraphics/intel-linux-graphics-firmwares].
  [2.470476] i915 :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling 
runtime power management.

  Pleae cherry-pick http://git.kernel.org/cgit/linux/kernel/git/firmware
  /linux-
  firmware.git/commit/?id=5e976de9e02b55563c28555361a7763bc043f5ec for
  xenial

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 21 10:25:01 2016
  Dependencies:
   
  InstallationDate: Installed on 2016-01-06 (196 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1602717] [NEW] hw-detect modprobes blindly, ignoring blacklists

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
---Problem Description---
modprobe does not honor blacklist options in kernel cmdline unless -b is used 
(at least on the installer)

The modprobe.blacklist option is required as a work-around until a solution to 
a device-driver bug is found (IBM LTC bug 138273).
 
I've gone through the code of the kmod src pkg, but didn't spot anything 
obvious.
Passing along to the Ubuntu team.

Contact Information = Mauricio Faria de Oliveira  / 
Lekshmi C. Pillai  
  
---Steps to Reproduce---
 Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes is 
not required, but is here just in case):
modprobe.blacklist=scsi_dh_alua,scsi-dh-alua

On the dialog for username/password, select Go Back, then Exit to shell:

The blacklist is detected/present in the config:

~ # modprobe -c | grep alua
blacklist scsi_dh_alua
blacklist scsi-dh-alua

But the module is insmod-ed anyway:

~ # modprobe -v -n scsi-dh-alua
insmod 
/lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
 

Unless -b is used:

~ # modprobe -v -n -b scsi-dh-alua
~ #

Installer kernel:
[0.00] Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 
18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-143679 severity-high 
targetmilestone-inin16041
-- 
hw-detect modprobes blindly, ignoring blacklists
https://bugs.launchpad.net/bugs/1602717
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 1604443] onibi (i386) - tests ran: 3, failed: 0

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-32.51/onibi__4.4.0-32.51__2016-07-21_14-14-00/results-index.html

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

Title:
  linux: 4.4.0-32.51 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1567237] Re: Kernel 3.19.0-58 freezes Ubuntu 14.04 on Dell XPS 15 9530

[V B]

I could also build the commit [6957c68d1e9255a31d2d916b6a6451b736460761]
"nfs: Fix race in __update_open_stateid()" and I installed the kernel
built from it and it does not freeze the laptop. So the commit that
triggers the problem must be after the above commit and up to
(including) the tag "Ubuntu-3.19.0-53.59".

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

Title:
  Kernel 3.19.0-58 freezes Ubuntu 14.04 on Dell XPS 15 9530

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The latest security patch for  3.19.0 for Ubuntu 14.04 started
  freezing my laptop (Dell Inc. XPS 15 9530). All the patches before
  this one for the kernel 3.19.0 for Ubuntu 14.04 were OK. From log, the
  last message before freezing was "kernel: ...[drm] HPD interrupt storm
  detected on connector HDMI-A-1: switching from hotplug detection to
  polling", as you can see below:

  Apr 6 14:46:17 xxx-ubuntu dbus[1001]: [system] Activating service 
name='org.freedesktop.hostname1' (using servicehelper)
  Apr 6 14:46:17 xxx-ubuntu dbus[1001]: [system] Successfully activated service 
'org.freedesktop.hostname1'
  Apr 6 14:46:17 xxx-ubuntu kernel: [ 945.147481] systemd-hostnamed[11982]: 
Warning: nss-myhostname is not installed. Changing the local hostname might 
make it unresolveable. Plea
  se install nss-myhostname!
  Apr 6 14:50:36 xxx-ubuntu sudo: pam_ecryptfs: pam_sm_authenticate: /home/xxx 
is already mounted
  Apr 6 15:00:01 xxx-ubuntu CRON[12829]: (root) CMD (if [ -x 
/usr/sbin/backupninja ]; then /usr/sbin/backupninja; fi)
  Apr 6 15:02:29 xxx-ubuntu kernel: [ 1916.954839] sound hdaudioC0D0: HDMI: ELD 
buf size is 0, force 128
  Apr 6 15:02:29 xxx-ubuntu kernel: [ 1916.954877] sound hdaudioC0D0: HDMI: 
invalid ELD data byte 0
  Apr 6 15:07:35 xxx-ubuntu kernel: [ .796696] [drm] HPD interrupt storm 
detected on connector HDMI-A-1: switching from hotplug detection to polling

  This is the same symptom as described in the bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552333, which is
  a bug raised for 4.2 kernel running on Ubuntu 14.04 using the same
  laptop and the same Ubuntu installation as for this bug.

  At the moment I switched back to kernel 3.19.0-51 that does not cause this 
problem, but the possibility that from now on all future security patches for 
3.19.0 might freeze my laptop sounds very bad.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  valentinbrasov   3187 F pulseaudio
   /dev/snd/controlC2:  valentinbrasov   3187 F pulseaudio
   /dev/snd/controlC0:  valentinbrasov   3187 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (192 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. XPS 15 9530
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-51-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet 
splash crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-51-generic N/A
   linux-backports-modules-3.19.0-51-generic  N/A
   linux-firmware 1.127.20
  Tags:  trusty
  Uname: Linux 3.19.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: XPS 15 9530
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 15 9530
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1340461] Re: Nikon CoolPix 5600 camera not recognized

[Jean-Marc]

Hello Joseph,

Yes, I think this issue happened after an update/upgrade but I don't
remember the kernel version. The problem first appear with Ubuntu 14.04.

V4.7-rc7 is now installed on my computer and the bug is still present,
same error message in Shotwell.

Thank you

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

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

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

Title:
  Nikon CoolPix 5600 camera not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  My Nikon Coolpix 5600 camera is not automatically detected (no icon in the 
Launcher or in "Devices"). However it appears in Shotwell.
  I can import photos from Canon A1000 IS camera with Shotwell but not from the 
Nikon (error message: Could not claim the USB device (-53))
  All the other USB devices work (webcam, flash drives, external HDD, mouse and 
keyboard).

  Ubuntu 14.04 LTS
  shotwell 0.18.0-0ubuntu4.1
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eunice 1512 F pulseaudio
   /dev/snd/controlC0:  eunice 1512 F pulseaudio
   /dev/snd/controlC1:  eunice 1512 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=cc08f480-3f55-4795-913e-9d4e75362876
  InstallationDate: Installed on 2014-10-25 (624 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: HP-Pavilion WE277AA-ABF p6352fr
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=60a2137c-a8ce-4769-836b-2d1dbdd00d11 ro radeon.dpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.07
  dmi.board.name: EVANS
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd01/26/2010:svnHP-Pavilion:pnWE277AA-ABFp6352fr:pvr:rvnPEGATRONCORPORATION:rnEVANS:rvr1.02:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: WE277AA-ABF p6352fr
  dmi.sys.vendor: HP-Pavilion

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

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

[Kernel-packages] [Bug 1605276] Re: Please update linux-firmware to add 1.7 broxton firmware

[Seth Forshee]

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

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

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Xenial)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Please update linux-firmware to add 1.7 broxton firmware

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

Bug description:
  There was errata in the 1.6 Broxton DMC firmware currently in linux-
  firmware and it no longer loads on 4.7 and higher based systems, which
  includes i915_bpo now that it has been updated to a 4.7 based
  backport.

  This is the error:
  [2.470468] [drm] Refusing to load old DMC firmware v1.6, please upgrade 
to v1.7 or later [https://01.org/linuxgraphics/intel-linux-graphics-firmwares].
  [2.470476] i915 :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling 
runtime power management.

  Pleae cherry-pick http://git.kernel.org/cgit/linux/kernel/git/firmware
  /linux-
  firmware.git/commit/?id=5e976de9e02b55563c28555361a7763bc043f5ec for
  xenial

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 21 10:25:01 2016
  Dependencies:
   
  InstallationDate: Installed on 2016-01-06 (196 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1605276] Re: Please update linux-firmware to add 1.7 broxton firmware

[Seth Forshee]

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

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

Title:
  Please update linux-firmware to add 1.7 broxton firmware

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Xenial:
  New

Bug description:
  There was errata in the 1.6 Broxton DMC firmware currently in linux-
  firmware and it no longer loads on 4.7 and higher based systems, which
  includes i915_bpo now that it has been updated to a 4.7 based
  backport.

  This is the error:
  [2.470468] [drm] Refusing to load old DMC firmware v1.6, please upgrade 
to v1.7 or later [https://01.org/linuxgraphics/intel-linux-graphics-firmwares].
  [2.470476] i915 :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling 
runtime power management.

  Pleae cherry-pick http://git.kernel.org/cgit/linux/kernel/git/firmware
  /linux-
  firmware.git/commit/?id=5e976de9e02b55563c28555361a7763bc043f5ec for
  xenial

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 21 10:25:01 2016
  Dependencies:
   
  InstallationDate: Installed on 2016-01-06 (196 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Brad Figg]

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

apport-collect 1605267

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

Title:
  Building kernel pachakges failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  This command failed: make-kpkg --append-to-version=-test-12 --initrd 
kernel_image
  I tried to build a kernel packages with kernel 3.13.0-92.139 on Ubuntu 
14.04.4 LTS:

  WARNING: modpost: Found 3 section mismatch(es).
  To see full details build your kernel with:
  'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC  init/version.o
LD  init/built-in.o
KSYM.tmp_kallsyms1.o
KSYM.tmp_kallsyms2.o
LD  vmlinux
SORTEX  vmlinux
SYSMAP  System.map
VOFFSET arch/x86/boot/voffset.h
CC  arch/x86/boot/version.o
OBJCOPY arch/x86/boot/compressed/vmlinux.bin
GZIParch/x86/boot/compressed/vmlinux.bin.gz
MKPIGGY arch/x86/boot/compressed/piggy.S
AS  arch/x86/boot/compressed/piggy.o
LD  arch/x86/boot/compressed/vmlinux
  arch/x86/boot/compressed/head_64.o: In function `efi64_config':
  (.data+0x90): undefined reference to `efi_call6'
  make[3]: *** [arch/x86/boot/compressed/vmlinux] Error 1
  make[2]: *** [arch/x86/boot/compressed/vmlinux] Error 2
  make[1]: *** [bzImage] Error 2
  make[1]: Leaving directory `/usr/src/linux-source-3.13.0/linux-source-3.13.0'
  make: *** [debian/stamp/build/kernel] Error 2

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

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

[Kernel-packages] [Bug 1605276] [NEW] Please update linux-firmware to add 1.7 broxton firmware

[Robert Hooker]

Public bug reported:

There was errata in the 1.6 Broxton DMC firmware currently in linux-
firmware and it no longer loads on 4.7 and higher based systems, which
includes i915_bpo now that it has been updated to a 4.7 based backport.

This is the error:
[2.470468] [drm] Refusing to load old DMC firmware v1.6, please upgrade to 
v1.7 or later [https://01.org/linuxgraphics/intel-linux-graphics-firmwares].
[2.470476] i915 :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling 
runtime power management.

Pleae cherry-pick http://git.kernel.org/cgit/linux/kernel/git/firmware
/linux-firmware.git/commit/?id=5e976de9e02b55563c28555361a7763bc043f5ec
for xenial

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul 21 10:25:01 2016
Dependencies:
 
InstallationDate: Installed on 2016-01-06 (196 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Please update linux-firmware to add 1.7 broxton firmware

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  There was errata in the 1.6 Broxton DMC firmware currently in linux-
  firmware and it no longer loads on 4.7 and higher based systems, which
  includes i915_bpo now that it has been updated to a 4.7 based
  backport.

  This is the error:
  [2.470468] [drm] Refusing to load old DMC firmware v1.6, please upgrade 
to v1.7 or later [https://01.org/linuxgraphics/intel-linux-graphics-firmwares].
  [2.470476] i915 :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling 
runtime power management.

  Pleae cherry-pick http://git.kernel.org/cgit/linux/kernel/git/firmware
  /linux-
  firmware.git/commit/?id=5e976de9e02b55563c28555361a7763bc043f5ec for
  xenial

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 21 10:25:01 2016
  Dependencies:
   
  InstallationDate: Installed on 2016-01-06 (196 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1605267] [NEW] Building kernel pachakges failed

[Sven]

Public bug reported:

Hello!

This command failed: make-kpkg --append-to-version=-test-12 --initrd 
kernel_image
I tried to build a kernel packages with kernel 3.13.0-92.139 on Ubuntu 14.04.4 
LTS:

WARNING: modpost: Found 3 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
  GEN .version
  CHK include/generated/compile.h
  UPD include/generated/compile.h
  CC  init/version.o
  LD  init/built-in.o
  KSYM.tmp_kallsyms1.o
  KSYM.tmp_kallsyms2.o
  LD  vmlinux
  SORTEX  vmlinux
  SYSMAP  System.map
  VOFFSET arch/x86/boot/voffset.h
  CC  arch/x86/boot/version.o
  OBJCOPY arch/x86/boot/compressed/vmlinux.bin
  GZIParch/x86/boot/compressed/vmlinux.bin.gz
  MKPIGGY arch/x86/boot/compressed/piggy.S
  AS  arch/x86/boot/compressed/piggy.o
  LD  arch/x86/boot/compressed/vmlinux
arch/x86/boot/compressed/head_64.o: In function `efi64_config':
(.data+0x90): undefined reference to `efi_call6'
make[3]: *** [arch/x86/boot/compressed/vmlinux] Error 1
make[2]: *** [arch/x86/boot/compressed/vmlinux] Error 2
make[1]: *** [bzImage] Error 2
make[1]: Leaving directory `/usr/src/linux-source-3.13.0/linux-source-3.13.0'
make: *** [debian/stamp/build/kernel] Error 2

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

** Attachment added: "kernel config"
   https://bugs.launchpad.net/bugs/1605267/+attachment/4704678/+files/config

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

Title:
  Building kernel pachakges failed

Status in linux package in Ubuntu:
  New

Bug description:
  Hello!

  This command failed: make-kpkg --append-to-version=-test-12 --initrd 
kernel_image
  I tried to build a kernel packages with kernel 3.13.0-92.139 on Ubuntu 
14.04.4 LTS:

  WARNING: modpost: Found 3 section mismatch(es).
  To see full details build your kernel with:
  'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC  init/version.o
LD  init/built-in.o
KSYM.tmp_kallsyms1.o
KSYM.tmp_kallsyms2.o
LD  vmlinux
SORTEX  vmlinux
SYSMAP  System.map
VOFFSET arch/x86/boot/voffset.h
CC  arch/x86/boot/version.o
OBJCOPY arch/x86/boot/compressed/vmlinux.bin
GZIParch/x86/boot/compressed/vmlinux.bin.gz
MKPIGGY arch/x86/boot/compressed/piggy.S
AS  arch/x86/boot/compressed/piggy.o
LD  arch/x86/boot/compressed/vmlinux
  arch/x86/boot/compressed/head_64.o: In function `efi64_config':
  (.data+0x90): undefined reference to `efi_call6'
  make[3]: *** [arch/x86/boot/compressed/vmlinux] Error 1
  make[2]: *** [arch/x86/boot/compressed/vmlinux] Error 2
  make[1]: *** [bzImage] Error 2
  make[1]: Leaving directory `/usr/src/linux-source-3.13.0/linux-source-3.13.0'
  make: *** [debian/stamp/build/kernel] Error 2

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

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

[Kernel-packages] [Bug 1604153] onza (i386) - tests ran: 18, failed: 1

[Brad Figg]

tests ran:  18, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-66.74/onza__3.19.0-66.74__2016-07-21_07-25-00/results-index.html

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

Title:
  linux: 3.19.0-66.74 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting

[dann frazier]

@cjwatson: Ah, ok. I may have misread the history here. I had gleaned
that the xenial kernel (as a host) was more unstable - but for different
reasons.

Regardless, I have pulled the wily backport build I prepared, because it
was frequently triggering a WARN() condition. Looks like my backport
attempt was too naive and would need some work. But perhaps I should
pause that effort until we confirm if 4.4 is impacted by this same
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/1531768

Title:
  [arm64] lockups some time after booting

Status in Auto Package Testing:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
  want to use for armhf autopkgtesting in LXD). I started with wily as
  that has lxd available (it's not yet available in trusty nor the PPA
  for arm64).

  However, pretty much any LXD task that I do (I haven't tried much
  else) on this machine takes unbearably long. A simple "lxc profile set
  default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes.

  I see tons of

  [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0
  [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds.

  in dmesg (the attached apport info has the complete dmesg).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 09:18 seq
   crw-rw 1 root audio 116, 33 Jan  7 09:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Jan  7 09:24:01 2016
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  Lspci:
   00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008]
    Subsystem: Red Hat, Inc Device [1af4:1100]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  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/auto-package-testing/+bug/1531768/+subscriptions

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

[Kernel-packages] [Bug 1604443] onibi (amd64) - tests ran: 30, failed: 0

[Brad Figg]

tests ran:  30, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-32.51/onibi__4.4.0-32.51__2016-07-21_12-46-00/results-index.html

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

Title:
  linux: 4.4.0-32.51 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1604776] Re: package linux-image-3.19.0-59-generic 3.19.0-59.66 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Mätthi]

Did 
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

as suggested by joseph.salisb...@canonical.com. Problem persists.

I would ignore this problem and start upgrade to ubuntu 16.04. Any
concerns?

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

Title:
  package linux-image-3.19.0-59-generic 3.19.0-59.66 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ::
  version.log
  ::
  Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-59-generic 3.19.0-59.66
  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.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maetthi2113 F pulseaudio
   /dev/snd/pcmC1D0p:   maetthi2113 F...m pulseaudio
   /dev/snd/controlC1:  maetthi2113 F pulseaudio
  Date: Wed Jul 20 13:00:27 2016
  DpkgHistoryLog:
   Start-Date: 2016-07-20  13:00:11
   Commandline: aptdaemon role='role-commit-packages' sender=':1.189'
   Install: linux-headers-3.19.0-65:amd64 (3.19.0-65.73), 
linux-image-extra-3.19.0-65-generic:amd64 (3.19.0-65.73), 
linux-image-3.19.0-65-generic:amd64 (3.19.0-65.73), 
linux-headers-3.19.0-65-generic:amd64 (3.19.0-65.73), 
linux-signed-image-3.19.0-65-generic:amd64 (3.19.0-65.73)
   Upgrade: linux-headers-generic:amd64 (3.19.0.64.62, 3.19.0.65.63), 
linux-signed-generic:amd64 (3.19.0.64.62, 3.19.0.65.63), 
linux-signed-image-generic:amd64 (3.19.0.64.62, 3.19.0.65.63), 
linux-libc-dev:amd64 (3.19.0-64.72, 3.19.0-65.73), linux-image-generic:amd64 
(3.19.0.64.62, 3.19.0.65.63), linux-generic:amd64 (3.19.0.64.62, 3.19.0.65.63)
  DuplicateSignature: 
package:linux-image-3.19.0-59-generic:3.19.0-59.66:subprocess installed 
post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=0dce2622-ed94-4288-b770-2d1337a8ca99
  InstallationDate: Installed on 2015-05-24 (422 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BXCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root 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 N/A
  SourcePackage: linux
  Title: package linux-image-3.19.0-59-generic 3.19.0-59.66 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET47WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET47WW(1.12):bd03/10/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1605197] Re: On add_nr_running , sub_nr_running issue.

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  On add_nr_running , sub_nr_running issue.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For more info check perf report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu4489 F pulseaudio
  CurrentDesktop: LXDE
  Date: Thu Jul 21 14:28:19 2016
  InstallationDate: Installed on 2016-04-29 (82 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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

[Kernel-packages] [Bug 1605142] Re: On timespect_trunc function issue.

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  On timespect_trunc function issue.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  More info with perf report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu4583 F pulseaudio
  CurrentDesktop: LXDE
  Date: Thu Jul 21 12:07:37 2016
  InstallationDate: Installed on 2016-04-29 (82 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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

[Kernel-packages] [Bug 1604036] Re: Upgrade printer-driver-ptouch to support Brother QL-570

[Launchpad Bug Tracker]

This bug was fixed in the package ptouch-driver - 1.4-5-gf4ad445-1

---
ptouch-driver (1.4-5-gf4ad445-1) unstable; urgency=medium

  * New upstream snapshot
- Add support for Brother QL-570 (LP: #1604036)

 -- Didier Raboud   Thu, 21 Jul 2016 07:38:59 +0200

** Changed in: ptouch-driver (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Upgrade printer-driver-ptouch to support Brother QL-570

Status in hwdata package in Ubuntu:
  Confirmed
Status in libosinfo package in Ubuntu:
  Confirmed
Status in ptouch-driver package in Ubuntu:
  Fix Released
Status in usbutils package in Ubuntu:
  Confirmed

Bug description:
  Please, upgrade printer-driver-ptouch to support Brother QL-570
  P-touch Label Printer. See https://bitbucket.org/philpem/printer-
  driver-ptouch/issues/2/negativeprint-and-cutmedia-jobend-doesnt
  (motivate maintainers of printer-driver-ptouch to bump their version
  number and release a version that supports QL-570) and also upgrade
  usbutils to include https://usb-ids.gowdy.us/read/UD/04f9/2028

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

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

[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting

[Colin Watson]

@dannf, this bug seems to be *worse* in xenial than in wily, so I don't
think backporting a change from xenial to wily is going to help matters?

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

Title:
  [arm64] lockups some time after booting

Status in Auto Package Testing:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
  want to use for armhf autopkgtesting in LXD). I started with wily as
  that has lxd available (it's not yet available in trusty nor the PPA
  for arm64).

  However, pretty much any LXD task that I do (I haven't tried much
  else) on this machine takes unbearably long. A simple "lxc profile set
  default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes.

  I see tons of

  [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0
  [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds.

  in dmesg (the attached apport info has the complete dmesg).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 09:18 seq
   crw-rw 1 root audio 116, 33 Jan  7 09:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Jan  7 09:24:01 2016
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  Lspci:
   00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008]
    Subsystem: Red Hat, Inc Device [1af4:1100]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  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/auto-package-testing/+bug/1531768/+subscriptions

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

[Kernel-packages] [Bug 1604100] Re: linux-ti-omap4: 3.2.0-1485.112 -proposed tracker

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the 3.2.0-1485.112 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1604099
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 21. July 2016 12:00 UTC

** Description changed:

  This bug is for tracking the 3.2.0-1485.112 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1604099
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Thursday, 21. July 2016 12:00 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-ti-omap4: 3.2.0-1485.112 -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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1604099
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1604153] Automated-Testing regression

[Brad Figg]

Here's the relevant information:

vivid linux 3.19.0-66.74 REGR summary

Please verify test results in http://people.canonical.com/~kernel/status
/adt-matrix/overall.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/1604153

Title:
  linux: 3.19.0-66.74 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1604443] Automated-Testing regression

[Brad Figg]

Here's the relevant information:

xenial linux 4.4.0-32.51 REGR summary

Please verify test results in http://people.canonical.com/~kernel/status
/adt-matrix/overall.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/1604443

Title:
  linux: 4.4.0-32.51 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1604814] Re: Newest kernel update disables wireless and touchpad

[Katona Janos]

Suggested link showed me that I should run sudo apt-get upgrade -s
command and it stated that I shouldn't see upgradeable packages, but I
did see. Then, I unchecked trusty-proposed packages and updated the
listed packages. It revealed that a window asks for a password for
disable uefi secure boot during the update. I suppose, I missed that
window during the previous update, or it was somehow hidden since I
did't notice it. Leaving secure boot enabled may have prevented the
loading of closed sourced drivers (maybe wireless and touchpad in my
case). I disabled secure boot using this prompt, and now I can see a
temporary screen during ubuntu boot with "booting in insecure mode". New
kernel (3.13.0-92-generic) loads fine, wireless and touchpad works now
as expected. Secure boot in computer's original "BIOS" is seems to be
left enabled, so I can still boot Windows 8 as well without problems.
This issue can be closed.

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

Title:
  Newest kernel update disables wireless and touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue: 
  kernel 3.13.0-91: both wireless and touchpad worked as expected (report was 
generated using this kernel)
  after updating to kernel 3.13.0-92: neither wireless nor touchpad work. 
Network does not even show to enable wifi, so no SSID-s are seen. Touchpad 
simply not reacts, no mouse symbol.

  Computer: Lenovo Flex 2 14"

  Wireless card: Broadcom Corporation BCM43142 802.11b/g/n, 
  Driver: using Broadcom 802.11 Linux STA wireless driver source from 
bcmwl-kernel-source (proprietary)

  Touchpad:
  I: Bus=0011 Vendor=0002 Product=000e Version=
  N: Name="ETPS/2 Elantech Touchpad"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input18
  U: Uniq=
  H: Handlers=mouse0 event4 
  B: PROP=5
  B: EV=b
  B: KEY=e420 1 0 0 0 0
  B: ABS=66180001103

  OS: Ubuntu 14.04 x64 
  /proc/version_signature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-91-generic 3.13.0-91.138
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-91-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kj 1726 F pulseaudio
   /dev/snd/controlC0:  kj 1726 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 20 14:49:43 2016
  HibernationDevice: RESUME=UUID=c434037e-9055-4781-9625-3f59f90ef7bd
  InstallationDate: Installed on 2014-12-07 (591 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0446 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 105b:e065 Foxconn International, Inc. BCM43142A0 
Bluetooth module
   Bus 001 Device 002: ID 0bda:579c Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20404
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=774a220e-0926-4480-84aa-32c562f2062b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Flex 2-14
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Flex 2-14
  dmi.modalias: 
dmi:bvnLENOVO:bvrA0CN31WW:bd10/08/2014:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoFlex2-14:
  dmi.product.name: 20404
  dmi.product.version: Lenovo Flex 2-14
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1604099] Automated-Testing regression

[Brad Figg]

Here's the relevant information:

precise linux 3.2.0-107.148 REGR summary

Please verify test results in http://people.canonical.com/~kernel/status
/adt-matrix/overall.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/1604099

Title:
  linux: 3.2.0-107.148 -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-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-107.148 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  On add_nr_running , sub_nr_running issue.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For more info check perf report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu4489 F pulseaudio
  CurrentDesktop: LXDE
  Date: Thu Jul 21 14:28:19 2016
  InstallationDate: Installed on 2016-04-29 (82 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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

[Kernel-packages] [Bug 1605197] [NEW] On add_nr_running , sub_nr_running issue.

[asu]

Public bug reported:

For more info check perf report.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  asu4489 F pulseaudio
CurrentDesktop: LXDE
Date: Thu Jul 21 14:28:19 2016
InstallationDate: Installed on 2016-04-29 (82 days ago)
InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
IwConfig:
 lono wireless extensions.
 
 enp1s0no wireless extensions.
MachineType: Olidata S.p.A. ALABAMA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-31-generic N/A
 linux-backports-modules-4.4.0-31-generic  N/A
 linux-firmware1.157.2
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: S0101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: ALABAMA
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: Olidata S.p.A.

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


** Tags: amd64 apport-bug xenial

** Patch added: "Tested on linux-4.6.2"
   
https://bugs.launchpad.net/bugs/1605197/+attachment/4704618/+files/0001-Corect-issue-on-sub_nr_running-add_nr_running.patch

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

Title:
  On add_nr_running , sub_nr_running issue.

Status in linux package in Ubuntu:
  New

Bug description:
  For more info check perf report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu4489 F pulseaudio
  CurrentDesktop: LXDE
  Date: Thu Jul 21 14:28:19 2016
  InstallationDate: Installed on 2016-04-29 (82 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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

[Kernel-packages] [Bug 1604153] dwalin (amd64) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-66.74/dwalin__3.19.0-66.74__2016-07-21_10-25-00/results-index.html

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

Title:
  linux: 3.19.0-66.74 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1604443] Re: linux: 4.4.0-32.51 -proposed tracker

[Andy Whitcroft]

** Tags removed: block-proposed

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

Title:
  linux: 4.4.0-32.51 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1604099] Automated-Testing regression

[Brad Figg]

Here's the relevant information:

precise linux 3.2.0-107.148 REGR summary

Please verify test results in http://people.canonical.com/~kernel/status
/adt-matrix/overall.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/1604099

Title:
  linux: 3.2.0-107.148 -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-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-107.148 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1604153] Automated-Testing regression

[Brad Figg]

Here's the relevant information:

vivid linux 3.19.0-66.74 REGR summary

Please verify test results in http://people.canonical.com/~kernel/status
/adt-matrix/overall.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/1604153

Title:
  linux: 3.19.0-66.74 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1604443] Automated-Testing regression

[Brad Figg]

Here's the relevant information:

xenial linux 4.4.0-32.51 REGR summary

Please verify test results in http://people.canonical.com/~kernel/status
/adt-matrix/overall.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/1604443

Title:
  linux: 4.4.0-32.51 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1570775] Re: makekdump should re-exec with cio_ignore on s390x

[Louis Bouchard]

** Description changed:

+ [SRU justification]
+ kernel crash dump fails to work without the modification.
+ 
+ [Impact]
+ Broken functionality.
+ 
+ [Fix]
+ Add cio_ignore -k -y output to the kexec command.
+ 
+ [Test Case]
+ Follow indication in comment #2 to reproduce. With the fix, kdump will 
function as expected.
+ 
+ [Regression]
+ A regression situation is outlined in comment #16. Newer channel devices may 
not be visible because of the added cio_ignore output. This may be worked 
around with a single command. 
+ 
+ The resolution outweights this limitation that can be easily worked
+ around.
+ 
+ [Original description of the problem]
+ 
  As per
  
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/comments/19
  
  We should re-exec with cio_ignore lines. As per report there, it should
  result in lowered required crashdump setting.
  
  Hypothetically, one should be able to test this imperially by lowering
  crashdump memory settings until kdump does not succeed anymore. And then
  generated and append `cio_ignore -k -u` to the KDUMP_CMDLINE_APPEND= and
  see that kdump starts working again with a lower memory usage.
  
  Once this is developed / verified / tested, we should probably SRU this
  back to xenial.

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

Title:
  makekdump should re-exec with cio_ignore on s390x

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress

Bug description:
  [SRU justification]
  kernel crash dump fails to work without the modification.

  [Impact]
  Broken functionality.

  [Fix]
  Add cio_ignore -k -y output to the kexec command.

  [Test Case]
  Follow indication in comment #2 to reproduce. With the fix, kdump will 
function as expected.

  [Regression]
  A regression situation is outlined in comment #16. Newer channel devices may 
not be visible because of the added cio_ignore output. This may be worked 
around with a single command. 

  The resolution outweights this limitation that can be easily worked
  around.

  [Original description of the problem]

  As per
  
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/comments/19

  We should re-exec with cio_ignore lines. As per report there, it
  should result in lowered required crashdump setting.

  Hypothetically, one should be able to test this imperially by lowering
  crashdump memory settings until kdump does not succeed anymore. And
  then generated and append `cio_ignore -k -u` to the
  KDUMP_CMDLINE_APPEND= and see that kdump starts working again with a
  lower memory usage.

  Once this is developed / verified / tested, we should probably SRU
  this back to xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1570775/+subscriptions

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

[Kernel-packages] [Bug 1604153] onibi (i386) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-66.74/onibi__3.19.0-66.74__2016-07-21_09-42-00/results-index.html

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

Title:
  linux: 3.19.0-66.74 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1599561] Re: Ubuntu 16.04.01 kdump: IP prefix is missing in the directory name after first dump during kdump over ssh.

[Louis Bouchard]

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

** Description changed:

+ [SRU justification]
+ HOSTTAG=ip is unusable without this fix on some platforms
+ 
+ [Impact]
+ HOSTTAG functionality works as expected.
+ 
+ [Fix]
+ Loop on hostname -I for five seconds. Revert to HOSTTAG=hostname if IP 
address not found.
+ 
+ [Test Case]
+ The race condition is difficult to run into but the bug reporter has been 
able to confirm the change from a PPA (see comment #5).
+ 
+ [Regression]
+ Minimal, as the code path is only enhanced by one loop. Exit path remains the 
same.
+ 
+ [Original description of the problem]
+ 
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-06-30 07:12:40 ==
  ---Problem Description---
  
  During kdump over ssh IP prefix will be present only in first dump,
  subsequent dumps will not have IP in directory name.
  
  ---Steps to Reproduce---
  
  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg
  
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-
  4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
  
  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show # should show "ready to dump"
  6) ssh-keygen -t rsa
  7) Edit below parameters in /etc/default/kdump-tools
  SSH="root@"
  SSH_KEY=/root/.ssh/id_rsa
  8)  kdump-config propagate
  9)  kdump-config show
  10) reboot
  11) echo "c" > /proc/sysrq-trigger
  12) verify dump is created in ssh server.
  13) trigger the crash again.
  
  Logs
  =
  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.4.0-26-generic #45-Ubuntu SMP Mon Jun 20 17:27:01 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  
  dumps on ssh server when 3 crashes are triggered
  
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523  -201606300524
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523  -201606300524  -201606300525
  [root@ltc-fire5 crash]# cd -201606300524
  -bash: cd: -2: invalid option
  cd: usage: cd [-L|[-P [-e]]] [dir]
  [root@ltc-fire5 crash]# cd -- -201606300524
  [root@ltc-fire5 -201606300524]# ls
  dmesg.201606300524  dump.201606300524
  
- 
  == Comment: #8 - Kevin W. Rudd - 2016-07-05 18:23:01 ==
  
  Canonical,
  
  The behavior appears to be somewhat intermittent, and it looks as if
  define_stampdir() might be getting called before the network init has
  completed.  If delaying this function is not practical, it might be
  helpful to have define_stampdir() fall back to using just "hostname" if
  "hostname -I" doesn't return any useful information for setting
  THIS_HOST.

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

Title:
  Ubuntu 16.04.01 kdump: IP prefix is missing in the directory name
  after first dump during kdump over ssh.

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress

Bug description:
  [SRU justification]
  HOSTTAG=ip is unusable without this fix on some platforms

  [Impact]
  HOSTTAG functionality works as expected.

  [Fix]
  Loop on hostname -I for five seconds. Revert to HOSTTAG=hostname if IP 
address not found.

  [Test Case]
  The race condition is difficult to run into but the bug reporter has been 
able to confirm the change from a PPA (see comment #5).

  [Regression]
  Minimal, as the code path is only enhanced by one loop. Exit path remains the 
same.

  [Original description of the problem]

  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-06-30 07:12:40 ==
  ---Problem Description---

  During kdump over ssh IP prefix will be present only in first dump,
  subsequent dumps will not have IP in directory name.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show # should show "ready to dump"
  6) ssh-keygen -t rsa
  7) Edit below parameters in /etc/default/kdump-tools
  SSH="root@"
  SSH_KEY=/root/.ssh/id_rsa
  8)  kdump-config propagate
  9)  kdump-config show
  10) reboot
  11) echo "c" > /proc/sysrq-trigger
  12) verify dump is created in ssh server.
  13) trigger the crash again.

  Logs
  =
  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.4.0-26-generic #45-Ubuntu SMP Mon Jun 20 17:27:01 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  dumps on ssh server when 3 crashes are triggered
  

[Kernel-packages] [Bug 1568952] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1" in kdump-tools

[Louis Bouchard]

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: makedumpfile (Ubuntu Xenial)
   Importance: Undecided => Low

** Description changed:

+ [SRU justification]
+ Use a more restrictive kernel boot option to limit CPU numbers to 1
+ 
+ [Impact]
+ Will significantly lower crashkernel memory usage on some architectures 
(namely ppc64el)
+ 
+ [Fix]
+ Change the maxcpus boot parameter used in the kexec command by nr_cpus.
+ 
+ [Test Case]
+ kexec-config show will display maxcpus=1 without the change. It will show 
nr_cpus=1 with the proposed change.
+ 
+ [Regression]
+ None expected, nr_cpus is a more generic parameter and is more restrictive 
than the previous parameter.
+ 
+ [Original Problem Description of the problem]
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.
-  
+ 
  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
-  
- Userspace tool: kdump-tools  version 1:1.5.9-5 
+ 
+ Userspace tool: kdump-tools  version 1:1.5.9-5
  
  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
- > 
+ >
  > Would you please validate that nr_cpus is consistent across architectures
  > and should become the new default?
- > 
+ >
  > Thanks.
  
  Hi Kevin,
  
  I know nr_cpus=1 is supported on x86 based on this patch
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=14cb6dcf0a023f5977461c94d8d5a163c937979b
  
  About other architectures, I am not really sure.
  
  But looking at the kdump-tools source package, it seems like other 
architectures
  are using maxcpus=1 to boot kdump kernel unless there is architecture specific
  overrides that are missing in the source. Canonical might be able to answer 
better.
  
  If other aren't using or willing to use nr_cpus=1, we may need a patch
  of this kind:
  
  diff --git a/kdump-config b/kdump-config
  index 0ff0e6f..aba300e 100755
  --- a/kdump-config
  +++ b/kdump-config
  @@ -48,7 +48,11 @@ KDUMP_COREDIR=${KDUMP_COREDIR:=/var/crash}
-  KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
-  KDUMP_DIR="/var/lib/kdump"
-  MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
+  KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
+  KDUMP_DIR="/var/lib/kdump"
+  MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
  -KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +if [ "$ARCH" = "ppc64le" ]; then
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +else
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +fi
-  KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
-  [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;
+  KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
+  [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;
  
  == Comment: #4 - Kevin W. Rudd - 2016-04-11 11:08:16 ==
  Mirroring to Canonical for their review and feedback.

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

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1"
  in kdump-tools

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  Use a more restrictive kernel boot option to limit CPU numbers to 1

  [Impact]
  Will significantly lower crashkernel memory usage on some architectures 
(namely ppc64el)

  [Fix]
  Change the maxcpus boot parameter used in the kexec command by nr_cpus.

  [Test Case]
  kexec-config show will display maxcpus=1 without the change. It will show 
nr_cpus=1 with the proposed change.

  [Regression]
  None expected, nr_cpus is a more generic parameter and is more restrictive 
than the previous parameter.

  [Original Problem Description of the problem]
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.

  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Userspace tool: kdump-tools  version 1:1.5.9-5

  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
  >
  > Would you please validate that nr_cpus is 

[Kernel-packages] [Bug 1571590] Re: pVM:pinelp2:ubuntu 16.04: Network is unreachable when using ssh in kdump

[Louis Bouchard]

** Description changed:

- Problem Description
+ [SRU justification]
+ Without this fix, networked enabled kernel dump will fail to complete.
+ 
+ [Impact]
+ Broken networked functionality
+ 
+ [Fix]
+ Add a Wants target to the systemd unit.
+ 
+ [Test Case]
+ Follow "Test to reproduce" in Original Problem description.
+ 
+ [Regression]
+ None expected, the existing systemd unit setup remains but is improved by 
proposed fix.
+ 
+ [Description of the problem]
+ 
+ Original problem Description
  
  When dumping to ssh target , kdump failed:
  
-  Starting Kernel crash dump capture service...
+  Starting Kernel crash dump capture service...
  [   18.542292] kdump-tools[2748]: Starting kdump-tools: ssh: connect to host 
10.33.31.113 port 22: Network is unreachable
  [   18.542894] kdump-tools[2748]:  * kdump-tools: Unable to reach remote 
server root@10.33.31.113. No reason to continue
  [   18.613376] kdump-tools[2748]: Mon, 11 Apr 2016 01:23:55 -0500
  [   19.310893] kdump-tools[2748]: Rebooting.
  [   19.652714] reboot: Restarting system
  
  But the weired thing is that nfs target works on the same system.
-  
+ 
  ---uname output---
  Linux pinelp2 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:00:30 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
-  
+ 
  Steps to Reproduce
  ===
  1. install latest ubuntu 16.04 on pinelp2
  2. config kdump to use ssh:
  SSH="root@10.33.31.113"
- 3. run "kdump-config propagate" as root 
+ 3. run "kdump-config propagate" as root
  4. trigger kdump
  
-  
- Userspace tool common name: kdump-tools 
-  
- The userspace tool has the following bit modes: 64-bit 
+ Userspace tool common name: kdump-tools
+ 
+ The userspace tool has the following bit modes: 64-bit
  
  Userspace rpm: version 1:1.5.9-5
  
  == Comment: #8 - Ping Tian Han  - 2016-04-17 21:58:52 ==
  (In reply to comment #6)
- > I am able to reproduce this issue as well. 
+ > I am able to reproduce this issue as well.
  > Ping, what is you try to dump on some other machine with ssh ? Does it still
  > complain the same ? Is the ssh failing to connect to the network ?
  
  I saw the same problem when dumping to medlp4 with ssh:
  
-  Starting Kernel crash dump capture service...
+  Starting Kernel crash dump capture service...
  [   17.293028] kdump-tools[2733]: Starting kdump-tools: ssh: connect to host 
10.33.7.181 port 22: Network is unreachable
  [   17.293692] kdump-tools[2733]:  * kdump-tools: Unable to reach remote 
server root@10.33.7.181. No reason to continue
  [   17.405333] kdump-tools[2733]: Sun, 17 Apr 2016 20:56:59 -0500
  [   18.536587] kdump-tools[2733]: Rebooting.
  [   18.903280] reboot: Restarting system
  
  but I can ssh log noto medlp4 before triggering kdump.

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

Title:
  pVM:pinelp2:ubuntu 16.04: Network is unreachable when using ssh in
  kdump

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress

Bug description:
  [SRU justification]
  Without this fix, networked enabled kernel dump will fail to complete.

  [Impact]
  Broken networked functionality

  [Fix]
  Add a Wants target to the systemd unit.

  [Test Case]
  Follow "Test to reproduce" in Original Problem description.

  [Regression]
  None expected, the existing systemd unit setup remains but is improved by 
proposed fix.

  [Description of the problem]

  Original problem Description
  
  When dumping to ssh target , kdump failed:

   Starting Kernel crash dump capture service...
  [   18.542292] kdump-tools[2748]: Starting kdump-tools: ssh: connect to host 
10.33.31.113 port 22: Network is unreachable
  [   18.542894] kdump-tools[2748]:  * kdump-tools: Unable to reach remote 
server root@10.33.31.113. No reason to continue
  [   18.613376] kdump-tools[2748]: Mon, 11 Apr 2016 01:23:55 -0500
  [   19.310893] kdump-tools[2748]: Rebooting.
  [   19.652714] reboot: Restarting system

  But the weired thing is that nfs target works on the same system.

  ---uname output---
  Linux pinelp2 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:00:30 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Steps to Reproduce
  ===
  1. install latest ubuntu 16.04 on pinelp2
  2. config kdump to use ssh:
  SSH="root@10.33.31.113"
  3. run "kdump-config propagate" as root
  4. trigger kdump

  Userspace tool common name: kdump-tools

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: version 1:1.5.9-5

  == Comment: #8 - Ping Tian Han  - 2016-04-17 21:58:52 ==
  (In reply to comment #6)
  > I am able to reproduce this issue as well.
  > Ping, what is you try to dump on some other machine with ssh ? Does it still