date:20170901

[Kernel-packages] [Bug 940145] Re: USB analog only devices sometimes show up with digital profile as well

2017-09-01 Thread Lucas Magasweran

Does anyone know what the root cause of this digital in/out appearing?
Is it within ALSA or is there something wrong with the USB AudioControl
interface descriptor being returned by the USB audio device? I ask
because I have a custom USB audio device with this issue.

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

Title:
  USB analog only devices sometimes show up with digital profile as well

Status in alsa-lib package in Ubuntu:
  Fix Released

Bug description:
  Sometimes, (I have yet to figure out when!) 
  USB headsets and mics which are analog only show up with a digital profile as 
well. While this is probably not a 12.04 regression, with the revamp of the 
sound settings UI this becomes annoying, as seen in the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu10
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.93-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david 10269 F pulseaudio
   /dev/snd/controlC0:  david 10269 F pulseaudio
   /dev/snd/pcmC0D0c:   david 10269 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd490 irq 48'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:111d7605,103c1413,00100402 
HDA:80862804,80860101,0010'
 Controls  : 23
 Simple ctrls  : 11
  Card1.Amixer.info:
   Card hw:1 'Headset'/'Logitech Logitech USB Headset at usb-:00:1a.0-1.4, 
full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0a0c'
 Controls  : 6
 Simple ctrls  : 2
  Date: Fri Feb 24 10:06:13 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120103)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68AZZ Ver. F.08
  dmi.board.name: 1413
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 57.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68AZZVer.F.08:bd06/29/2010:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1413:rvrKBCVersion57.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4520s
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2012-02-09T11:15:19.592182

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/940145/+subscriptions

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

[Kernel-packages] [Bug 1002952] Re: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards

2017-09-01 Thread Lucas Magasweran

I'm curious what the root cause of this bug is because I have a custom
USB audio device with this issue. Is it within ALSA or is something
wrong with the USB audio device's AudioControl Interface descriptor?

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

Title:
  [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards

Status in alsa-lib package in Ubuntu:
  Confirmed

Bug description:
  === Read me first ===

  = Symptom =

  If you have a USB headset, or other USB device that does not have any
  S/PDIF output, but yet sometimes there is an extra device called
  "Digital Output (S/PDIF)" for that device, you're suffering from this
  bug.

  This bug is only for USB devices - if you have an invalid digital
  output for some other type of device, please file a separate bug
  instead.

  = Workaround =

  If you're affected, please try this workaround:

  first check the output of "aplay -l" (lowercase L), or "arecord -l" if
  it's an input device, and grab the first of two name in brackets:

  Example:
  card 3: Headset [Sennheiser USB Headset], device 0: USB Audio [USB Audio]
  here grab the name "Sennheiser USB Headset". Now edit the file 
/usr/share/alsa/cards/USB-Audio.conf (requires root permissions)
  Around line 40, you will find a line saying "Logitech USB Headset" 999
  Add a new line after this line, so that there is now a new line called
  "Sennheiser USB Headset" 999
  (including quotes, and replace "Sennheiser USB Headset" with whatever your 
particular card was named.)

  Save the file and reboot your computer for the changes to take effect.

  = Already known devices =

  These card names are already in 12.04:

  "Blue Snowball"
  "Logitech USB Headset"
  "Logitech Web Camera"

  These card names are on their way into 12.04:

  "Logitech Speaker Lapdesk N700"
  "Logitech Wireless Headset"
  "Plantronics USB Headset"
  "Sennheiser USB headset"

  If you have one of the above four, please help out by testing the
  proposed repository and report back in bug 987163.

  If your name is not listed above, please add a comment to this bug,
  including your alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo -
  they will be collected for a SRU later on, or at least make it into
  the next release of Ubuntu.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1002952/+subscriptions

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

[Kernel-packages] [Bug 1682644] Re: IPR driver causes multipath to fail paths/stuck IO on Medium Errors

2017-09-01 Thread bugproxy

--- Comment From mauri...@br.ibm.com 2017-09-01 20:30 EDT---
Likewise for Xenial.

http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=master-
next=6020175400028e2b5cdd8212a6b20d208a033973

Thanks.

** Tags added: verification-done-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/1682644

Title:
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: stuck I/O to multipath disks with medium errors (on IPR controllers)
  Fix: upstream commit for IPR driver to allow SCSI layer to handle the error
  Testcase: perform I/O to a failing disk which is multipathed (on IPR
controller), which returns SCSI Medium Errors (without the fix,
the I/O gets stuck). 
the commit message describes a test-case w/ sg_dd.

  
  ---Problem Description---
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

  This problem is resolved with this upstream accepted patch, scheduled for 
4.11.
  The detailed problem description and resolution are described in the commit 
message.

  > scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
  > 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=785a470496d8e0a32e3d39f376984eb2c98ca5b3

  Please apply to 17.04 (target 16.04.3 HWE kernel) and 16.04 (GA kernel).
  Patch already applied to 17.10.

  The business justification for the SRU is:

  Clients with a dual-controller multipathed IPR configuration that
  eventually runs into failing disk/sectors, will experience an I/O hang
  once the drive reports a Medium Error, which can hang an application
  or even the root filesystem (whatever is doing I/O to the failing
  drive), potentially hanging the system.

  Thanks.

  ---Additional Hardware Info---
  Dual (IPR) controller setup, multipath enabled

  ---Steps to Reproduce---
  1) Use a disk with bad sectors (or force such condition, via internal/special 
tools)
  2) Multipath that disk
  3) Run IO to the multipath device on the bad sectors
  4) Both paths will be failed, and IO is stuck due to queue_if_no_path 
(enabled by default for IPR)

  The detailed problem description and resolution are described in the
  commit message.

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

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

[Kernel-packages] [Bug 1682644] Re: IPR driver causes multipath to fail paths/stuck IO on Medium Errors

2017-09-01 Thread bugproxy

--- Comment From mauri...@br.ibm.com 2017-09-01 19:50 EDT---
Marking as verification done on Zesty.

Verified that the commit is applied in the zesty's kernel master-next
branch (cannot verify in hardware currently, but the code change is
trivial and has been tested on real hardware before in Ubuntu kernels
and upstream for upstream submission).

--- Comment From mauri...@br.ibm.com 2017-09-01 19:55 EDT---
(commit in zesty)
http://kernel.ubuntu.com/git/ubuntu/ubuntu-zesty.git/commit/?h=master-next=67317c9194ff46c043b10749b7ded3c2fed4be9a

** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-zesty

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

Title:
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: stuck I/O to multipath disks with medium errors (on IPR controllers)
  Fix: upstream commit for IPR driver to allow SCSI layer to handle the error
  Testcase: perform I/O to a failing disk which is multipathed (on IPR
controller), which returns SCSI Medium Errors (without the fix,
the I/O gets stuck). 
the commit message describes a test-case w/ sg_dd.

  
  ---Problem Description---
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

  This problem is resolved with this upstream accepted patch, scheduled for 
4.11.
  The detailed problem description and resolution are described in the commit 
message.

  > scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
  > 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=785a470496d8e0a32e3d39f376984eb2c98ca5b3

  Please apply to 17.04 (target 16.04.3 HWE kernel) and 16.04 (GA kernel).
  Patch already applied to 17.10.

  The business justification for the SRU is:

  Clients with a dual-controller multipathed IPR configuration that
  eventually runs into failing disk/sectors, will experience an I/O hang
  once the drive reports a Medium Error, which can hang an application
  or even the root filesystem (whatever is doing I/O to the failing
  drive), potentially hanging the system.

  Thanks.

  ---Additional Hardware Info---
  Dual (IPR) controller setup, multipath enabled

  ---Steps to Reproduce---
  1) Use a disk with bad sectors (or force such condition, via internal/special 
tools)
  2) Multipath that disk
  3) Run IO to the multipath device on the bad sectors
  4) Both paths will be failed, and IO is stuck due to queue_if_no_path 
(enabled by default for IPR)

  The detailed problem description and resolution are described in the
  commit message.

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

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

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2017-09-01 Thread Rafael David Tinoco

2 things for previous comment #75:

1)
I pasted wrong pastebin URL. I'll describe the fix: its a service unit file 
that runs at the end of shutdown, right before it, re-using /run (tmpfs). 
Service has a preparation script that copies binaries from initrd image - so 
there is a minimum execution environment available - and runs the second 
script. Second script initializes iscsid daemon and waits in a loop for all the 
portals to be ONLINE and existing sessions to be LOGGED. After that it does the 
logout on all existing sessions (this case this would be leftovers from my 
previous comment AND / root disks).

2)
I tested this approach and it works good for iscsi root disks because there is 
a network interface that stays connected all the time. In the case of leftovers 
from previous unsuccessful umount attempts, the network.target would be already 
gone (with networkd / ifupdown interfaces already shutdown). IF I keep my 
interfaces configured, then this approach works for root disks AND for 
leftovers. For this approach to be successful for this case, this "cleanup" 
service would have to raise existing interfaces up again for the iscsid to 
login and logout to work (OR the kernel hang be resolved, then leftovers would 
be just left there, without logouts).

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  In Progress

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Kernel-packages] [Bug 1696154] Re: [17.10 FEAT] Sign POWER host/NV kernels

2017-09-01 Thread Steve Langasek

Does IBM have any feedback for us regarding the test kernel Andy
provided?

We have generated an online signing key to be included in db for OPAL.
In the absence of feedback about whether 4096-bit keys are supported, we
have generated a 2048-bit key.

Our current plan for secure delivery of the public key to IBM is to
deliver the keys in person to George next month.  Does this timeline fit
IBM's needs for receipt of the public keys?  Does it meet your
expectations for a trust path for the keys, or is there another protocol
that should be used?

In your reply of August 1, you wrote:

> However, in order to add a certificate to DB, the certificate should be
> signed by any of the KEK entries. The PK will be used to authorize updates
> to the KEK certificate list.

Can you please clarify if this means you are expecting the db entry to
be delivered as an x509 certificate issued by the CA key listed in KEK,
or if it should be delivered according to the format defined in the UEFI
spec for authenticated variable updates?

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

Title:
  [17.10 FEAT] Sign POWER host/NV kernels

Status in Launchpad itself:
  Fix Committed
Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-signed package in Ubuntu:
  In Progress

Bug description:
  Feature Description:

  Sign POWER host and NV kernels with sign-file in anticipation of POWER
  secure boot.  Provide the  associated certificate.  Ideally it would
  be possible to reuse the UEFI shim private key and certificate used to
  sign and verify x86_64 kernels.  More details to follow.  Guest
  kernels will be addressed in a future separate feature request.

  Business Case: 

  As a system administrator I want to verify the integrity of my kernels
  so that I can prevent malicious kernels from being executed.

  Use Case:

  Signed POWER kernels will be validated by OPAL as OpenPOWER systems
  boot when keys are properly installed and the system is booted in
  secure mode.

  Test Case:

  Sign and install a POWER kernel on an OpenPOWER machine with a
  firmware level that supports secure boot.  Install a PK, distro KEK
  certificat, and distro DB certificate.  Boot the system and verify
  that it will boot the kernel.  Negative tests:  Separately remove the
  signature, install an usigned kernel, and modify the kernel image and
  test that the kernel will not boot.

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

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

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

2017-09-01 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1682410

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

Title:
  ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have two systems that have a Dropbox folder synced. One of the
  subfolders contains sensitive data encrypted using ecryptfs. Both were
  running linux kernel 4.4.0-53-generic.

  I have since upgraded one system to use linux kernel 4.8.0-41-generic.
  Now, the decrypted directory can no longer see groups and owners or
  read files. All permissions are replaced by questionmarks.

  4.8.0-41-generic

  $ ll
  ls: cannot access 'Contracts': No such file or directory
  ls: cannot access 'Documents': No such file or directory
  ls: cannot access 'Work': No such file or directory
  total 12K
  drwxr-x--- 5 redsandro redsandro 4.0K Mar 31 15:54 ./
  drwxr-xr-x 7 redsandro redsandro 4.0K Apr 13 13:24 ../
  d? ? ?  ? ?? Contracts/
  d? ? ?  ? ?? Documents/
  d? ? ?  ? ?? Work/

  The other machine still works fine.

  4.4.0-53-generic:

  $ ll
  total 56K
  drwxr-x---  5 redsandro redsandro  12K Apr  4 16:11 ./
  drwxr-xr-x  8 redsandro redsandro 4.0K Oct 18 13:25 ../
  drwxr-xr-x  3 redsandro redsandro 4.0K Nov  2 18:50 Contracts/
  drwxr-xr-x 11 redsandro redsandro 4.0K Mar  9 17:03 Documents/
  drwxr-xr-x  3 redsandro redsandro 4.0K Mar  4  2013 Work/

  For both machines:
  $ apt version ecryptfs-utils 
  111-0ubuntu1.1

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

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

[Kernel-packages] [Bug 1714367] Re: bcmwl-kernel-source no longer works on hwe kernel

2017-09-01 Thread Scott Testerman

Mistaken identification of affected package.  After reinstalling
16.04(.0) I have verified that bcmwl-kernel-source is not involved.
Marking this bug invalid.

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

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

Title:
  bcmwl-kernel-source no longer works on hwe kernel

Status in bcmwl package in Ubuntu:
  Invalid

Bug description:
  bcmwl-kernel-source worked correctly on the original 16.04 LTS kernel,
  but no longer works on the hwe kernel (4.10.0-33).  I am using the b43
  open source driver temporarily in order to file this report.

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  bcmwl-kernel-source:
Installed: 6.30.223.271+bdcom-0ubuntu1~1.1
Candidate: 6.30.223.271+bdcom-0ubuntu1~1.1
Version table:
   *** 6.30.223.271+bdcom-0ubuntu1~1.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  100 /var/lib/dpkg/status
   6.30.223.248+bdcom-0ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages

  04:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 
01)
Subsystem: Broadcom Corporation BCM4311 802.11b/g WLAN
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1714367/+subscriptions

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

[Kernel-packages] [Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic

2017-09-01 Thread Redsandro

I think the problem only exists for unencrypted filenames that would
previously pass (by default or) by passing the ecryptfs_passthrough
option.

Unencrypted filenames work as expected on kernels <=4.4, but are
inaccessable and listed as in kernels >=4.8.

I've tried the mount option ecryptfs_passthrough=yes,
ecryptfs_passthrough=y and ecryptfs_passthrough in the commandline:

sudo /bin/mount -it ecryptfs /tmp/.files /tmp/files -o
ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_enable_filename_crypto=yes,ecryptfs_passthrough,ecryptfs_sig=a1b2c3...,ecryptfs_fnek_sig=a1b2c3...)

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

Title:
ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic

Status in linux package in Ubuntu:
New

Bug description:
I have two systems that have a Dropbox folder synced. One of the
subfolders contains sensitive data encrypted using ecryptfs. Both were
running linux kernel 4.4.0-53-generic.

I have since upgraded one system to use linux kernel 4.8.0-41-generic.
Now, the decrypted directory can no longer see groups and owners or
read files. All permissions are replaced by questionmarks.

4.8.0-41-generic

$ ll
ls: cannot access 'Contracts': No such file or directory
ls: cannot access 'Documents': No such file or directory
ls: cannot access 'Work': No such file or directory
total 12K
drwxr-x--- 5 redsandro redsandro 4.0K Mar 31 15:54 ./
drwxr-xr-x 7 redsandro redsandro 4.0K Apr 13 13:24 ../
d? ? ? ? ?? Contracts/
d? ? ? ? ?? Documents/
d? ? ? ? ?? Work/

The other machine still works fine.

4.4.0-53-generic:

$ ll
total 56K
drwxr-x--- 5 redsandro redsandro 12K Apr 4 16:11 ./
drwxr-xr-x 8 redsandro redsandro 4.0K Oct 18 13:25 ../
drwxr-xr-x 3 redsandro redsandro 4.0K Nov 2 18:50 Contracts/
drwxr-xr-x 11 redsandro redsandro 4.0K Mar 9 17:03 Documents/
drwxr-xr-x 3 redsandro redsandro 4.0K Mar 4 2013 Work/

For both machines:
$ apt version ecryptfs-utils
111-0ubuntu1.1

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

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

[Kernel-packages] [Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic

2017-09-01 Thread Redsandro

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

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

Title:
  ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic

Status in linux package in Ubuntu:
  New

Bug description:
  I have two systems that have a Dropbox folder synced. One of the
  subfolders contains sensitive data encrypted using ecryptfs. Both were
  running linux kernel 4.4.0-53-generic.

  I have since upgraded one system to use linux kernel 4.8.0-41-generic.
  Now, the decrypted directory can no longer see groups and owners or
  read files. All permissions are replaced by questionmarks.

  4.8.0-41-generic

  $ ll
  ls: cannot access 'Contracts': No such file or directory
  ls: cannot access 'Documents': No such file or directory
  ls: cannot access 'Work': No such file or directory
  total 12K
  drwxr-x--- 5 redsandro redsandro 4.0K Mar 31 15:54 ./
  drwxr-xr-x 7 redsandro redsandro 4.0K Apr 13 13:24 ../
  d? ? ?  ? ?? Contracts/
  d? ? ?  ? ?? Documents/
  d? ? ?  ? ?? Work/

  The other machine still works fine.

  4.4.0-53-generic:

  $ ll
  total 56K
  drwxr-x---  5 redsandro redsandro  12K Apr  4 16:11 ./
  drwxr-xr-x  8 redsandro redsandro 4.0K Oct 18 13:25 ../
  drwxr-xr-x  3 redsandro redsandro 4.0K Nov  2 18:50 Contracts/
  drwxr-xr-x 11 redsandro redsandro 4.0K Mar  9 17:03 Documents/
  drwxr-xr-x  3 redsandro redsandro 4.0K Mar  4  2013 Work/

  For both machines:
  $ apt version ecryptfs-utils 
  111-0ubuntu1.1

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

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

[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

2017-09-01 Thread Scott Emmons

The commit for this in upstream Debian (0.123 version of initramfs-
tools) is here: https://anonscm.debian.org/cgit/kernel/initramfs-
tools.git/commit/?id=ac6d31fc2c707b72ff8af9944c9b4f8af303a6a3 - I would
be happy to make a patch for this commit to xenial (zesty and later has
0.125+, so should already include the fix).

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  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.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

2017-09-01 Thread Scott Emmons

Sorry, my previous comment was for another initramfs-tools related bug.
Please disregard #18.

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  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.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1708480] Re: Ubuntu 17.04/17.10 Screen Tearing on Intel KabyLake Graphics Cards

2017-09-01 Thread Owais Lone

I experience this as well on fully up to date XPS 13 (9560) on 17.10

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

Title:
  Ubuntu 17.04/17.10 Screen Tearing on Intel KabyLake Graphics Cards

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upon upgrading to 17.04 (also confirmed in 17.10), heavy, almost
  constant screen tearing presents itself immediately at the graphical
  or text splash page (i.e., before the operating system loads).  The
  tearing continues after reaching the lock screen and logging in.  The
  tearing is nearly constant, stopping only for certain actions like
  using the mouse or typing.

  The screen tearing can be "fixed" by issuing i915.enable_rc6=0 in the
  boot parameter.  However, this is a false fix as it turns off
  important power management functions and, as a consequence, the fan
  runs constantly and on high.

  NOTE: if booted using the i915.enable_rc6=0 boot parameter and allowed
  to run for a few hours, the computer becomes unstable and applications
  begin to freeze.

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

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

[Kernel-packages] [Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic

2017-09-01 Thread Redsandro

INTERESTING: In the new kernels, you can still write new files and read
them. You cannot read files written in 'old' kernels.

But when booting the old kernel, you can read ALL files, including the
one written using the newer kernel!

Booting back in 4.8, 4.10 or 4.12, and again you can only read the new
file, not the old files. Are there some kind of stricter options that
are backwards compatible since 4.8?

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

Title:
  ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have two systems that have a Dropbox folder synced. One of the
  subfolders contains sensitive data encrypted using ecryptfs. Both were
  running linux kernel 4.4.0-53-generic.

  I have since upgraded one system to use linux kernel 4.8.0-41-generic.
  Now, the decrypted directory can no longer see groups and owners or
  read files. All permissions are replaced by questionmarks.

  4.8.0-41-generic

  $ ll
  ls: cannot access 'Contracts': No such file or directory
  ls: cannot access 'Documents': No such file or directory
  ls: cannot access 'Work': No such file or directory
  total 12K
  drwxr-x--- 5 redsandro redsandro 4.0K Mar 31 15:54 ./
  drwxr-xr-x 7 redsandro redsandro 4.0K Apr 13 13:24 ../
  d? ? ?  ? ?? Contracts/
  d? ? ?  ? ?? Documents/
  d? ? ?  ? ?? Work/

  The other machine still works fine.

  4.4.0-53-generic:

  $ ll
  total 56K
  drwxr-x---  5 redsandro redsandro  12K Apr  4 16:11 ./
  drwxr-xr-x  8 redsandro redsandro 4.0K Oct 18 13:25 ../
  drwxr-xr-x  3 redsandro redsandro 4.0K Nov  2 18:50 Contracts/
  drwxr-xr-x 11 redsandro redsandro 4.0K Mar  9 17:03 Documents/
  drwxr-xr-x  3 redsandro redsandro 4.0K Mar  4  2013 Work/

  For both machines:
  $ apt version ecryptfs-utils 
  111-0ubuntu1.1

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

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

[Kernel-packages] [Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic

2017-09-01 Thread Redsandro

@jsalisbury I tried kernel 4.12.0 and the problem exists.

Can we re-open this? Something clearly changed between 4.4 and 4.8. And
it's not fixed in 4.10 or 4.12.

Does someone know what is going on? Using the same mount options, only kernel
4.4.0 and lower will mount the ecryptfs share. Newer kernels will display the
as mentioned in the original report.

/tmp/test1 on /tmp/test2 type ecryptfs
(rw,relatime,ecryptfs_fnek_sig=ab22c3d4e5ee,ecryptfs_sig=ab22c3d4e5ee,ecryptfs_cipher=aes,ecryptfs_key_bytes=32)

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

Title:
ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic

Status in linux package in Ubuntu:
Expired

Bug description:
I have two systems that have a Dropbox folder synced. One of the
subfolders contains sensitive data encrypted using ecryptfs. Both were
running linux kernel 4.4.0-53-generic.

I have since upgraded one system to use linux kernel 4.8.0-41-generic.
Now, the decrypted directory can no longer see groups and owners or
read files. All permissions are replaced by questionmarks.

4.8.0-41-generic

The other machine still works fine.

4.4.0-53-generic:

For both machines:
$ apt version ecryptfs-utils
111-0ubuntu1.1

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

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2017-09-01 Thread Rafael David Tinoco

Unrelated to systemd. Related to open-iscsi systemd unit files and
kernel iscsi transport logout during shutdown.

** Changed in: systemd (Ubuntu Artful)
   Importance: High => Medium

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

** Changed in: systemd (Ubuntu Artful)
 Assignee: Nish Aravamudan (nacc) => (unassigned)

** No longer affects: systemd (Ubuntu Xenial)

** No longer affects: systemd (Ubuntu Zesty)

** No longer affects: systemd (Ubuntu Artful)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Rafael David Tinoco (inaddy)

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Rafael David Tinoco (inaddy)

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Rafael David Tinoco (inaddy)

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  In Progress

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2017-09-01 Thread Rafael David Tinoco

Unrelated to systemd. Related to open-iscsi systemd unit files and
kernel iscsi transport logout during shutdown.

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

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

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  In Progress

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2017-09-01 Thread Rafael David Tinoco

Unrelated to systemd. Related to open-iscsi systemd unit files and
kernel iscsi transport logout during shutdown.

** Changed in: open-iscsi (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: open-iscsi (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: open-iscsi (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: open-iscsi (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: open-iscsi (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: open-iscsi (Ubuntu Artful)
   Status: New => In Progress

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

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

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

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

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

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

** No longer affects: systemd (Ubuntu)

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  In Progress

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

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

2017-09-01 Thread Ubuntu Kernel Bot

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

Title:
  Realtek RTL8822BE Support Coming To Linux 4.14

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Please... Add module RTL8822BE:
  * https://www.phoronix.com/scan.php?page=news_item=Linux-Realtek-RTL8822BE
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?h=staging-next=5b5ab4cb5cda824ef59e0511ac5d585f35f1a1a6

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-12-generic 4.12.0-12.13
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1807 F pulseaudio
   /dev/snd/pcmC1D0p:   caravena   1807 F...m pulseaudio
   /dev/snd/controlC1:  caravena   1807 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep  1 16:51:10 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-12-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-12-generic N/A
   linux-backports-modules-4.12.0-12-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2017-09-01 Thread Rafael David Tinoco

## SUMMARY 1

Affects open-iscsi (NOT systemd):

* ISCSID NEEDS TO BE UP & RUNNING (AND LOGGED TO PORTAL) FOR THE LOGOUT
TO WORK

https://pastebin.canonical.com/197359/

Daemon shutdown documentation in iscsiadm command says (about stopping iscsid 
daemon with iscsiadm -k): 
""" ... This will immediately stop all iscsid operations and shutdown iscsid. 
It does not logout any sessions. Running this command is the same as doing 
"killall iscsid". Neither should normally be used, because if iscsid is doing 
error recovery or if there is an error while iscsid is not running, the system 
may not be able to recover. This command and iscsid's SIGTERM handling are 
experimental. """

Basically meaning you're not able to shutdown the daemon in a clean
manner if you have connected sessions. And basically, checking the
pastebin, you see the need for running iscsid daemon to logout through
iscsiadm command.

So from:
 
(systemctl edit --full open-iscsi.service)
...
Wants=network-online.target remote-fs-pre.target iscsid.service
After=network-online.target iscsid.service
Before=remote-fs-pre.target
...
ExecStartPre=/bin/systemctl --quiet is-active iscsid.service
ExecStart=/sbin/iscsiadm -m node --loginall=automatic
ExecStart=/lib/open-iscsi/activate-storage.sh
ExecStop=/lib/open-iscsi/umountiscsi.sh
ExecStop=/bin/sync
ExecStop=/lib/open-iscsi/logout-all.sh
...

and

(systemctl edit --full iscsid.service)
...
Wants=network-online.target remote-fs-pre.target
Before=remote-fs-pre.target
After=network.target network-online.target
...
ExecStartPre=/lib/open-iscsi/startup-checks.sh
ExecStart=/sbin/iscsid
ExecStop=/sbin/iscsiadm -k 0 2
...

If umountiscsi.sh (it doesn't kill applications using a mount point)
can't umount a mount point (from fstab generator or a mount unit) that
is still being used, the logout-all.sh will fail for logging out the
session of the disk being used. But this service unit would be
considered stopped, allowing "iscsid.service" unit to also be shutdown
(killing the iscsid daemon and leaving an opened iscsi session).

This would be problematic for iscsi root disks AND for the kernel issue
(comment #73), and this is being taken care by Francis Ginther
(fginther) in the next iscsi SRU: https://pastebin.canonical.com/196463/
by creating an iscsi-cleanup.service that will run a script that logs
out all remaining iscsi sessions (including /) right before kernel
shutdown is called by systemd-shutdown like showed in comment #73.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  In Progress

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also

[Kernel-packages] [Bug 1714583] [NEW] Realtek RTL8822BE Support Coming To Linux 4.14

2017-09-01 Thread Cristian Aravena Romero

Public bug reported:

Hello,

Please... Add module RTL8822BE:
* https://www.phoronix.com/scan.php?page=news_item=Linux-Realtek-RTL8822BE
* 
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?h=staging-next=5b5ab4cb5cda824ef59e0511ac5d585f35f1a1a6

Regards,
--
Cristian

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.12.0-12-generic 4.12.0-12.13
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   1807 F pulseaudio
 /dev/snd/pcmC1D0p:   caravena   1807 F...m pulseaudio
 /dev/snd/controlC1:  caravena   1807 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Sep  1 16:51:10 2017
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2017-07-05 (58 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-12-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.12.0-12-generic N/A
 linux-backports-modules-4.12.0-12-generic  N/A
 linux-firmware 1.167
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug artful

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

Title:
  Realtek RTL8822BE Support Coming To Linux 4.14

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Please... Add module RTL8822BE:
  * https://www.phoronix.com/scan.php?page=news_item=Linux-Realtek-RTL8822BE
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?h=staging-next=5b5ab4cb5cda824ef59e0511ac5d585f35f1a1a6

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-12-generic 4.12.0-12.13
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1807 F pulseaudio
   /dev/snd/pcmC1D0p:   caravena   1807 F...m pulseaudio
   /dev/snd/controlC1:  caravena   1807 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep  1 16:51:10 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-12-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-12-generic N/A
   linux-backports-modules-4.12.0-12-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go

[Kernel-packages] [Bug 1714571] [NEW] [P9, POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice when perf stat is done (perf:)

2017-09-01 Thread bugproxy

Public bug reported:

== Comment: #0 - Sukadev Bhattiprolu  - 2017-09-01 12:56:47 ==

---Problem Description---
Problem description :
=
Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice , it is because 
two raw point to the same name.

[   
  {,
"EventCode": "0x20036", 
"EventName": "PM_BR_2PATH", 
"BriefDescription": "Branches that are not strongly biased",
"PublicDescription": "" 
  },
  {,
"EventCode": "0x40036", 
"EventName": "PM_BR_2PATH", 
"BriefDescription": "Branches that are not strongly biased",
"PublicDescription": "" 
  },


Ex :
===

[root@zzfp189p1 ~]#  perf stat -e pm_br_2path sleep 1

 Performance counter stats for 'sleep 1':

30,163  pm_br_2path 

   pm_br_2path 
  (0.00%)

   1.002046416 seconds time elapsed

[root@zzfp189p1 ~]# perf stat -e pm_ld_miss_l1 sleep 1

 Performance counter stats for 'sleep 1':

 9,217  pm_ld_miss_l1   

   pm_ld_miss_l1   
  (0.00%)

   1.001956110 seconds time elapsed


---Steps to Reproduce---
 Steps to reproduce :

1. Install perf (linux-tools)
2. Run
perf stat -e pm_ld_miss_l1 sleep 1
perf stat -e pm_br_2path sleep 1


== Comment: #1 - Sukadev Bhattiprolu  - 2017-09-01 12:58:16 ==
The fix for this bug was pulled into Arnaldo's tree:

https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core=828e291e2982a7c10a62aa32195d0cb501cedaae

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-158230 severity-medium 
targetmilestone-inin---

** Tags added: architecture-ppc64le bugnameltc-158230 severity-medium
targetmilestone-inin---

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

Title:
  [P9,POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is
  counted twice when perf stat is done (perf:)

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Sukadev Bhattiprolu  - 2017-09-01 12:56:47 ==

  ---Problem Description---
  Problem description :
  =
  Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice , it is 
because two raw point to the same name.

  [ 
  
{,  
  
  "EventCode": "0x20036",   
  
  "EventName": "PM_BR_2PATH",   
  
  "BriefDescription": "Branches that are not strongly biased",  
  
  "PublicDescription": ""   
  
},  
  
{,  
  
  "EventCode": "0x40036",   
  
  "EventName": "PM_BR_2PATH",   
  
  "BriefDescription": "Branches that are not strongly biased",  
  
  "PublicDescription": ""   
  
},

  
  Ex :
  ===

  [root@zzfp189p1 ~]#  perf stat -e pm_br_2path sleep 1

   Performance counter stats for 'sleep 1':

  30,163  pm_br_2path   
  
 pm_br_2path   
(0.00%)

 1.002046416 seconds time elapsed

  [root@zzfp189p1 ~]# perf stat -e pm_ld_miss_l1 sleep 1

   Performance counter stats for 'sleep 1':

   9,217  pm_ld_miss_l1 
  
 pm_ld_miss_l1

1 2 >

1 - 100 of 141 matches

Mail list logo