date:20180517

--- Comment (attachment only) From ukri...@us.ibm.com 2018-05-17 17:03 
EDT---


** Attachment added: "diff between v2 and v3 of CXL (cxlflash) patches"
   
https://bugs.launchpad.net/bugs/1768431/+attachment/5141004/+files/0001-cxlflash-OCXL-diff-between-v2-and-v3.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/1768431

Title:
  Request to revert SAUCE patches in the 18.04 SRU and update with
  upstream version

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - UMA KRISHNAN  - 2018-04-30 14:41:30 ==
  ---Problem Description---
  Request to revert SAUCE patches from 18.04 and apply the patches from 
next/master.

  Below set of cxlflash patches were submitted to Canonical after they
  were sent to the community. Based on review comments, there has been
  minor changes from that version. This BZ is to request reverting those
  SAUCE patches with the ones that are queued in next/master tree for
  4.18.

  - SAUCE: cxlflash: Preserve number of interrupts for master contexts
  - SAUCE: cxlflash: Avoid clobbering context control register value
  - SAUCE: cxlflash: Add argument identifier names
  - SAUCE: cxlflash: Introduce OCXL backend
  - SAUCE: cxlflash: Hardware AFU for OCXL
  - SAUCE: cxlflash: Read host function configuration
  - SAUCE: cxlflash: Setup function acTag range
  - SAUCE: cxlflash: Read host AFU configuration
  - SAUCE: cxlflash: Setup AFU acTag range
  - SAUCE: cxlflash: Setup AFU PASID
  - SAUCE: cxlflash: Adapter context support for OCXL
  - SAUCE: cxlflash: Use IDR to manage adapter contexts
  - SAUCE: cxlflash: Support adapter file descriptors for OCXL
  - SAUCE: cxlflash: Support adapter context discovery
  - SAUCE: cxlflash: Support image reload policy modification
  - SAUCE: cxlflash: MMIO map the AFU
  - SAUCE: cxlflash: Support starting an adapter context
  - SAUCE: cxlflash: Support process specific mappings
  - SAUCE: cxlflash: Support AFU state toggling
  - SAUCE: cxlflash: Support reading adapter VPD data
  - SAUCE: cxlflash: Setup function OCXL link
  - SAUCE: cxlflash: Setup OCXL transaction layer
  - SAUCE: cxlflash: Support process element lifecycle
  - SAUCE: cxlflash: Support AFU interrupt management
  - SAUCE: cxlflash: Support AFU interrupt mapping and registration
  - SAUCE: cxlflash: Support starting user contexts
  - SAUCE: cxlflash: Support adapter context polling
  - SAUCE: cxlflash: Support adapter context reading
  - SAUCE: cxlflash: Support adapter context mmap and release
  - SAUCE: cxlflash: Support file descriptor mapping
  - SAUCE: cxlflash: Introduce object handle fop
  - SAUCE: cxlflash: Setup LISNs for user contexts
  - SAUCE: cxlflash: Setup LISNs for master contexts
  - SAUCE: cxlflash: Update synchronous interrupt status bits
  - SAUCE: cxlflash: Introduce OCXL context state machine
  - SAUCE: cxlflash: Register for translation errors
  - SAUCE: cxlflash: Support AFU reset
  - SAUCE: cxlflash: Enable OCXL operations

  Also, there are 3 additional patches added to end of this series that we 
would like to request being pulled into the SRU stream. These 3 patches address 
bug fixes.
  The commit ids for the patches queued in next/master tree are,

  768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of 
interrupts for master contexts
  6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering 
context control register value
  fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument 
identifier names
  863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL 
backend
  f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL
  1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function 
configuration
  ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag 
range
  f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU 
configuration
  c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range
  b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID
  de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context 
support for OCXL
  a76fc993e399f54b37f46107a31e817c779f2b82 scsi: cxlflash: Use IDR to manage 
adapter contexts
  09f35da5fe218baf73f7b4efd281e2c19490512c scsi: cxlflash: Support adapter file 
descriptors for OCXL
  17f9335bc59c1cf8f93617eee137e745abd71a3f scsi: cxlflash: Support adapter 
context discovery
  a5cfe355f23d4410d69af0e5b196b095463a0b4b scsi: cxlflash: Support image reload 
policy modification
  0c62e7c091a4e0a01a7c6027fe719625ab2f521e scsi: cxlflash: MMIO map the AFU
  f39bab766ea4f0b3d5888fdd7d66babd7bef3966 scsi: cxlflash: Support starting an 
adapter

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

--- Comment From ukri...@us.ibm.com 2018-05-17 17:02 EDT---
I'm attaching the diff patch that contains all the changes between the current 
version of SAUCE patches for latest cxlflash patches in bionic and the latest 
version accepted by the community. This only has the changes for the 3 
differences updated earlier. After applying this diff patch, please apply the 3 
additional new patches from the next/master tree. The 3 patches needed on top 
of this diff patch are,

a3feb6ef50def7c91244d7bd15a3625b7b49b81f scsi: cxlflash: Synchronize reset and 
remove ops
9a597cd4c0cebd61657f7449cb8bcb681f464500 scsi: cxlflash: Remove commmands from 
pending list on timeout
d2d354a606d5309fbfe81d5fca01122159e38c6e scsi: cxlflash: Handle spurious 
interrupts

Please let me know if you find issues applying them or if you have
questions.

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

Title:
  Request to revert SAUCE patches in the 18.04 SRU and update with
  upstream version

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - UMA KRISHNAN  - 2018-04-30 14:41:30 ==
  ---Problem Description---
  Request to revert SAUCE patches from 18.04 and apply the patches from 
next/master.

  Below set of cxlflash patches were submitted to Canonical after they
  were sent to the community. Based on review comments, there has been
  minor changes from that version. This BZ is to request reverting those
  SAUCE patches with the ones that are queued in next/master tree for
  4.18.

  - SAUCE: cxlflash: Preserve number of interrupts for master contexts
  - SAUCE: cxlflash: Avoid clobbering context control register value
  - SAUCE: cxlflash: Add argument identifier names
  - SAUCE: cxlflash: Introduce OCXL backend
  - SAUCE: cxlflash: Hardware AFU for OCXL
  - SAUCE: cxlflash: Read host function configuration
  - SAUCE: cxlflash: Setup function acTag range
  - SAUCE: cxlflash: Read host AFU configuration
  - SAUCE: cxlflash: Setup AFU acTag range
  - SAUCE: cxlflash: Setup AFU PASID
  - SAUCE: cxlflash: Adapter context support for OCXL
  - SAUCE: cxlflash: Use IDR to manage adapter contexts
  - SAUCE: cxlflash: Support adapter file descriptors for OCXL
  - SAUCE: cxlflash: Support adapter context discovery
  - SAUCE: cxlflash: Support image reload policy modification
  - SAUCE: cxlflash: MMIO map the AFU
  - SAUCE: cxlflash: Support starting an adapter context
  - SAUCE: cxlflash: Support process specific mappings
  - SAUCE: cxlflash: Support AFU state toggling
  - SAUCE: cxlflash: Support reading adapter VPD data
  - SAUCE: cxlflash: Setup function OCXL link
  - SAUCE: cxlflash: Setup OCXL transaction layer
  - SAUCE: cxlflash: Support process element lifecycle
  - SAUCE: cxlflash: Support AFU interrupt management
  - SAUCE: cxlflash: Support AFU interrupt mapping and registration
  - SAUCE: cxlflash: Support starting user contexts
  - SAUCE: cxlflash: Support adapter context polling
  - SAUCE: cxlflash: Support adapter context reading
  - SAUCE: cxlflash: Support adapter context mmap and release
  - SAUCE: cxlflash: Support file descriptor mapping
  - SAUCE: cxlflash: Introduce object handle fop
  - SAUCE: cxlflash: Setup LISNs for user contexts
  - SAUCE: cxlflash: Setup LISNs for master contexts
  - SAUCE: cxlflash: Update synchronous interrupt status bits
  - SAUCE: cxlflash: Introduce OCXL context state machine
  - SAUCE: cxlflash: Register for translation errors
  - SAUCE: cxlflash: Support AFU reset
  - SAUCE: cxlflash: Enable OCXL operations

  Also, there are 3 additional patches added to end of this series that we 
would like to request being pulled into the SRU stream. These 3 patches address 
bug fixes.
  The commit ids for the patches queued in next/master tree are,

  768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of 
interrupts for master contexts
  6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering 
context control register value
  fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument 
identifier names
  863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL 
backend
  f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL
  1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function 
configuration
  ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag 
range
  f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU 
configuration
  c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range
  b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID
  de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context 
support for

[Kernel-packages] [Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-17 Thread Kamal Mostafa

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

** Also affects: linux-aws (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** No longer affects: linux-aws (Ubuntu 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/1771679

Title:
  Kernel panic on boot (m1.small in cn-north-1)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress

Bug description:
  We're observing the following panic on boot when trying to boot an
  m1.small in cn-north-1 (which is a region in AWS China):

  [2.271681] Hardware name: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
  [2.271681] RIP: 0010:__xen_evtchn_do_upcall+0x24/0x80
  [2.271681] RSP: :8e21aa003ea0 EFLAGS: 00010046
  [2.271681] RAX: 9dd82920 RBX: ff20 RCX: 
8728b34e
  [2.271681] RDX: 8e21a3252800 RSI: 8e21a724e000 RDI: 
001c
  [2.271681] RBP: 8e21aa003eb8 R08: 9ea05040 R09: 

  [2.271681] R10: 8e21aa003f28 R11:  R12: 
0001
  [2.271681] R13:  R14: 0022 R15: 
8e21a3246900
  [2.271681] FS:  () GS:8e21aa00() 
knlGS:
  [2.271681] CS:  0010 DS:  ES:  CR0: 80050033
  [2.271681] CR2: ff20 CR3: 0b80a000 CR4: 
06f0
  [2.271681] Call Trace:
  [2.271681]  
  [2.271681]  xen_hvm_evtchn_do_upcall+0xe/0x10
  [2.271681]  do_hvm_evtchn_intr+0xe/0x20
  [2.271681]  __handle_irq_event_percpu+0x44/0x1a0
  [2.271681]  handle_irq_event_percpu+0x32/0x80
  [2.271681]  handle_irq_event+0x3b/0x60
  [2.271681]  handle_fasteoi_irq+0x75/0x130
  [2.271681]  handle_irq+0x20/0x30
  [2.271681]  do_IRQ+0x46/0xd0
  [2.271681]  common_interrupt+0x84/0x84
  [2.271681]  
  [2.271681] RIP: 0010:native_safe_halt+0x6/0x10
  [2.271681] RSP: :9ea03e28 EFLAGS: 0246 ORIG_RAX: 
ffdd
  [2.271681] RAX: 9e12fba0 RBX:  RCX: 

  [2.271681] RDX:  RSI:  RDI: 

  [2.271681] RBP: 9ea03e28 R08: 0002 R09: 
9ea03e18
  [2.271681] R10: 9ea03da0 R11: eb8a1d25 R12: 

  [2.271681] R13:  R14:  R15: 

  [2.271681]  ? __cpuidle_text_start+0x8/0x8
  [2.271681]  default_idle+0x20/0x100
  [2.271681]  arch_cpu_idle+0x15/0x20
  [2.271681]  default_idle_call+0x23/0x30
  [2.271681]  do_idle+0x17f/0x1b0
  [2.271681]  cpu_startup_entry+0x73/0x80
  [2.271681]  rest_init+0xae/0xb0
  [2.271681]  start_kernel+0x4dc/0x4fd
  [2.271681]  x86_64_start_reservations+0x24/0x26
  [2.271681]  x86_64_start_kernel+0x74/0x77
  [2.271681]  secondary_startup_64+0xa5/0xb0
  [2.271681] Code: 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 55 41 
54 53 65 48 8b 1d 92 dc 29 62 41 bc 01 00 00 00 65 44 8b 2d 8c 8c 29 62  03 
00 44 89 e0 65 0f c1 05 2e 96 2a 62 85 c0 75 3b 48 8b 05 
  [2.271681] RIP: __xen_evtchn_do_upcall+0x24/0x80 RSP: 8e21aa003ea0
  [2.271681] CR2: ff20
  [2.271681] ---[ end trace 956d0f4244642614 ]---
  [2.271681] Kernel panic - not syncing: Fatal exception in interrupt

  I've attached the full console log.

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

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

[Kernel-packages] [Bug 1758205] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-path (NVMe / Bolt ) (systemd?)

Actually commit 8a30ecc6e0ecbb9ae95daf499b2680b885ed0349 is in bionic as
of 4.15.0-13:

1a3abe0db677 Revert "nvme: create 'slaves' and 'holders' entries for
hidden controllers"

git describe --contains 1a3abe0db677
Ubuntu-4.15.0-13.14~323


Can you see if this bug still exists with the latest Bionic kernel, that should 
be neweter than -13?

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

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-
  path (NVMe / Bolt ) (systemd?)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  ---Problem Description---

  Bolt based NVMe disks (namespaces) are not displayed on lsblk and 
/dev/disk/by-path
  # nvme list 
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 1  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n10S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 10 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n11S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 11 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n12S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 12 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n13S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 13 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n14S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 14 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n15S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 15 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n16S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 16 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n17S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 17 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n18S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 18 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n19S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 19 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n2 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 2  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n20S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 20 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n21S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 21 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n22S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 22 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n23S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 23 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n24S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 24 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n25S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 25 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n26S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 26 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n27S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 27 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n28S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 28 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n29S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 29 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n3 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 3  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n30S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 30 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n31S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 31 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n32S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 32 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12

[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9

I started a kernel bisect between v4.15-rc6 and v4.15-rc7. The kernel
bisect will require testing of about 6 test kernels.

I built the first test kernel, up to the following commit:
d8887f1c7289848e74c92bd4322789a9cd7de699

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

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

Title:
  Rebooting bionic fails with hardware error on ProLiant DL360 Gen9

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  From an ephemeral environment in an HPGen9, the machine fails to
  reboot when the ephemeral environment is Bionic (it does not fail in
  Xenial).

  Full log from the moment the 'sudo reboot' was executed:
  https://pastebin.ubuntu.com/p/hyD6VY7CbW/

  The actual failure is:

  [  OK  ] Stopped Remount Root and Kernel File Systems.
  [  OK  ] Reached target Shutdown.
  [  OK  ] Reached target Final Step.
   Starting Reboot...
  [  OK  ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress 
polling.
   Stopping LVM2 metadata daemon...
  [  OK  ] Stopped LVM2 metadata daemon.
  [  257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware 
Error Source: 1
  [  257.160530] {1}[Hardware Error]: event severity: fatal
  [  257.160533] {1}[Hardware Error]:  Error 0, type: fatal
  [  257.160534] {1}[Hardware Error]:   section_type: PCIe error
  [  257.160536] {1}[Hardware Error]:   port_type: 4, root port
  [  257.160541] {1}[Hardware Error]:   version: 1.16
  [  257.160544] {1}[Hardware Error]:   command: 0x6010, status: 0x0143
  [  257.160546] {1}[Hardware Error]:   device_id: :00:01.0
  [  257.160547] {1}[Hardware Error]:   slot: 0
  [  257.160548] {1}[Hardware Error]:   secondary_bus: 0x03
  [  257.160550] {1}[Hardware Error]:   vendor_id: 0x8086, device_id: 0x6f02
  [  257.160552] {1}[Hardware Error]:   class_code: 040600
  [  257.160554] {1}[Hardware Error]:   bridge: secondary_status: 0x2000, 
control: 0x0003
  [  257.160556] {1}[Hardware Error]:  Error 1, type: fatal
  [  257.160557] {1}[Hardware Error]:   section_type: PCIe error
  [  257.160559] {1}[Hardware Error]:   port_type: 4, root port
  [  257.160560] {1}[Hardware Error]:   version: 1.16
  [  257.160562] {1}[Hardware Error]:   command: 0x6010, status: 0x0143
  [  257.160564] {1}[Hardware Error]:   device_id: :00:01.0
  [  257.160565] {1}[Hardware Error]:   slot: 0
  [  257.160566] {1}[Hardware Error]:   secondary_bus: 0x03
  [  257.160567] {1}[Hardware Error]:   vendor_id: 0x8086, device_id: 0x6f02
  [  257.160568] {1}[Hardware Error]:   class_code: 040600
  [  257.160569] {1}[Hardware Error]:   bridge: secondary_status: 0x2000, 
control: 0x0003
  [  257.160570] Kernel panic - not syncing: Fatal hardware error!
  [  257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [  257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116, 33 Apr  6 17:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed 
with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: 
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro 
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
 ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled 
cc:{datasource_list: [MAAS]}end_cc 
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
 apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 
BOOTIF=01-94:18:82:7a:82:c8
  ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No

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

2018-05-17 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 1771679

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

Title:
  Kernel panic on boot (m1.small in cn-north-1)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress

Bug description:
  We're observing the following panic on boot when trying to boot an
  m1.small in cn-north-1 (which is a region in AWS China):

  [2.271681] Hardware name: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
  [2.271681] RIP: 0010:__xen_evtchn_do_upcall+0x24/0x80
  [2.271681] RSP: :8e21aa003ea0 EFLAGS: 00010046
  [2.271681] RAX: 9dd82920 RBX: ff20 RCX: 
8728b34e
  [2.271681] RDX: 8e21a3252800 RSI: 8e21a724e000 RDI: 
001c
  [2.271681] RBP: 8e21aa003eb8 R08: 9ea05040 R09: 

  [2.271681] R10: 8e21aa003f28 R11:  R12: 
0001
  [2.271681] R13:  R14: 0022 R15: 
8e21a3246900
  [2.271681] FS:  () GS:8e21aa00() 
knlGS:
  [2.271681] CS:  0010 DS:  ES:  CR0: 80050033
  [2.271681] CR2: ff20 CR3: 0b80a000 CR4: 
06f0
  [2.271681] Call Trace:
  [2.271681]  
  [2.271681]  xen_hvm_evtchn_do_upcall+0xe/0x10
  [2.271681]  do_hvm_evtchn_intr+0xe/0x20
  [2.271681]  __handle_irq_event_percpu+0x44/0x1a0
  [2.271681]  handle_irq_event_percpu+0x32/0x80
  [2.271681]  handle_irq_event+0x3b/0x60
  [2.271681]  handle_fasteoi_irq+0x75/0x130
  [2.271681]  handle_irq+0x20/0x30
  [2.271681]  do_IRQ+0x46/0xd0
  [2.271681]  common_interrupt+0x84/0x84
  [2.271681]  
  [2.271681] RIP: 0010:native_safe_halt+0x6/0x10
  [2.271681] RSP: :9ea03e28 EFLAGS: 0246 ORIG_RAX: 
ffdd
  [2.271681] RAX: 9e12fba0 RBX:  RCX: 

  [2.271681] RDX:  RSI:  RDI: 

  [2.271681] RBP: 9ea03e28 R08: 0002 R09: 
9ea03e18
  [2.271681] R10: 9ea03da0 R11: eb8a1d25 R12: 

  [2.271681] R13:  R14:  R15: 

  [2.271681]  ? __cpuidle_text_start+0x8/0x8
  [2.271681]  default_idle+0x20/0x100
  [2.271681]  arch_cpu_idle+0x15/0x20
  [2.271681]  default_idle_call+0x23/0x30
  [2.271681]  do_idle+0x17f/0x1b0
  [2.271681]  cpu_startup_entry+0x73/0x80
  [2.271681]  rest_init+0xae/0xb0
  [2.271681]  start_kernel+0x4dc/0x4fd
  [2.271681]  x86_64_start_reservations+0x24/0x26
  [2.271681]  x86_64_start_kernel+0x74/0x77
  [2.271681]  secondary_startup_64+0xa5/0xb0
  [2.271681] Code: 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 55 41 
54 53 65 48 8b 1d 92 dc 29 62 41 bc 01 00 00 00 65 44 8b 2d 8c 8c 29 62  03 
00 44 89 e0 65 0f c1 05 2e 96 2a 62 85 c0 75 3b 48 8b 05 
  [2.271681] RIP: __xen_evtchn_do_upcall+0x24/0x80 RSP: 8e21aa003ea0
  [2.271681] CR2: ff20
  [2.271681] ---[ end trace 956d0f4244642614 ]---
  [2.271681] Kernel panic - not syncing: Fatal exception in interrupt

  I've attached the full console log.

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

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

[Kernel-packages] [Bug 1742502] Re: 108 and 109 kernel hangs

** Tags removed: kernel-key
** Tags added: kernel-da-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/1742502

Title:
  108 and 109 kernel hangs

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

Bug description:
  Overnight I had 2 of 12  16.04 servers brick with the 108 kernel. They
  also do not work with 109.  They work fine with 104. The other 10
  worked fine on both 108 and 109.

  All are hosted on VMWARE. The two broken ones stop at the same place.
  I was able to go back to the 104 kernel to get them working and pin
  the kernel version.

  Just for fun, I set zswap.enabled=0 and they both crashed with kthread
  starved for jiffies. They are both multi-processor with lots of ram
  and disk.

  I have a task from the Ubuntu Kernel team to try this with 'nopti'.
  I'll report back.

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

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

[Kernel-packages] [Bug 1752002] Re: [P9, POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:)

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

** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => 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/1752002

Title:
  [P9,POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is
  seen while running perf fuzzer (perf:)

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-02-02 
01:21:36 ==
  Problem Description :
  =

  Warn on message is seen while running perf fuzzer tests.

  Machine details :
  ==
  Hardware : Witherspoon (wsp12) + DD2.1
  OS : Ubuntu 1804
  uname -a : 4.13.0-32-generic #35~lp1746225 ( Kernel from the bug : 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7 )

  
  Steps to reproduce :
  
  Build Kernel :
  
  To avoid the kernel crash due to Perf fuzzer , use the kernel mentioned in 
the link : https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget http://9.114.13.132/repo/shriya/perf_regs.h
  cd ../../lib
  make
  sleep 10
  cd ../fuzzer
  make
  sleep 10

  echo 0 > /proc/sys/kernel/nmi_watchdog
  echo 2 > /proc/sys/kernel/perf_event_paranoid
  echo 10 > /proc/sys/kernel/perf_event_max_sample_rate
  ./perf_fuzzer -r 1492143527

  
  Call trace :
  ===
  [  329.228031] [ cut here ]
  [  329.228039] WARNING: CPU: 43 PID: 9088 at 
/home/jsalisbury/bugs/lp1746225/ubuntu-artful/kernel/events/core.c:3038 
perf_pmu_sched_task+0x170/0x180
  [  329.228040] Modules linked in: ofpart at24 uio_pdrv_genirq uio cmdlinepart 
powernv_flash mtd ipmi_powernv vmx_crypto ipmi_devintf ipmi_msghandler 
ibmpowernv opal_prd crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 
crc32c_vpmsum lpfc ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt mlx5_core fb_sys_fops ttm tg3 nvmet_fc drm ahci nvmet nvme_fc libahci 
nvme_fabrics mlxfw nvme_core devlink scsi_transport_fc
  [  329.228068] CPU: 43 PID: 9088 Comm: perf_fuzzer Not tainted 
4.13.0-32-generic #35~lp1746225
  [  329.228070] task: c03f776ac900 task.stack: c03f77728000
  [  329.228071] NIP: c0299b70 LR: c02a4534 CTR: 
c029bb80
  [  329.228073] REGS: c03f7772b760 TRAP: 0700   Not tainted  
(4.13.0-32-generic)
  [  329.228073] MSR: 9282b033 
  [  329.228079]   CR: 24008822  XER: 
  [  329.228080] CFAR: c0299a70 SOFTE: 0 
 GPR00: c02a4534 c03f7772b9e0 c1606200 
c03fef858908 
 GPR04: c03f776ac900 0001  
003fee73 
 GPR08:   c11220d8 
0002 
 GPR12: c029bb80 c7a3d900  
 
 GPR16:    
 
 GPR20:   c03f776ad090 
c0c71354 
 GPR24: c03fef716780 003fee73 c03fe69d4200 
c03f776ad330 
 GPR28: c11220d8 0001 c14c6108 
c03fef858900 
  [  329.228098] NIP [c0299b70] perf_pmu_sched_task+0x170/0x180
  [  329.228100] LR [c02a4534] __perf_event_task_sched_in+0xc4/0x230
  [  329.228101] Call Trace:
  [  329.228102] [c03f7772b9e0] [c02a0678] 
perf_iterate_sb+0x158/0x2a0 (unreliable)
  [  329.228105] [c03f7772ba30] [c02a4534] 
__perf_event_task_sched_in+0xc4/0x230
  [  329.228107] [c03f7772bab0] [c01396dc] 
finish_task_switch+0x21c/0x310
  [  329.228109] [c03f7772bb60] [c0c71354] __schedule+0x304/0xb80
  [  329.228111] [c03f7772bc40] [c0c71c10] schedule+0x40/0xc0
  [  329.228113] [c03f7772bc60] [c01033f4] do_wait+0x254/0x2e0
  [  329.228115] [c03f7772bcd0] [c0104ac0] kernel_wait4+0xa0/0x1a0
  [  329.228117] [c03f7772bd70] [c0104c24] SyS_wait4+0x64/0xc0
  [  329.228121] [c03f7772be30] [c000b184] system_call+0x58/0x6c
  [  329.228121] Instruction dump:
  [  329.228123] 3beafea0 7faa4800 409eff18 e8010060 eb610028 ebc10040 7c0803a6 
38210050 
  [  329.228127] eb81ffe0 eba1ffe8 ebe1fff8 4e800020 <0fe0> 4bbc 
6000 6042 
  [  329.228131] ---[ end trace 8c46856d314c1811 ]---
  [  375.755943] hrtimer: interrupt took 31601 ns

  == Comment: #4 - SEETEENA THOUFEEK  - 2018-02-05
  06:34:09 ==

  
  == Comment: #5 - SEETEENA THOUFEEK

[Kernel-packages] [Bug 1762468] Re: Cryptoswap not working in Bionic

** Tags removed: kernel-key
** Tags added: kernel-da-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/1762468

Title:
  Cryptoswap not working in Bionic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  I have cryptoswap set up both with the 2 GB default swap file and an 8
  GB swap partition with 8 GB of ram.  However, the system does not use
  this swap when it should.  For example, if I run a little test code
  which attempts to allocate 10 GB of memory in 1 GB chuncks, the system
  hangs with no obvious use of swap.  E.g. running top shows no swap use
  before the hang.  However, if I replace cryptoswap by standard swap,
  it works as expected: allocates the requested memory and exits, using
  swap.  Of course, my disk is slow, so this takes some time but it does
  work.

  I originally noticed this problem when compiling a very large
  application.  The system would hang on ld.  I've checked hardware
  using memtest and stress.  No problems.  This took me days to track
  down but I'm 99% certain now that the problem is with cryptoswap.  If
  I compile with cryptoswap: hang.  If I compile with standard swap: no
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  weinberg   2425 F pulseaudio
   /dev/snd/controlC0:  weinberg   2425 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 11:57:23 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113
  InstallationDate: Installed on 2018-03-12 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  MachineType: LENOVO 20ARA0S100
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

** Tags removed: kernel-key
** Tags added: kernel-da-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/1762940

Title:
  Ubuntu 18.04 install screen becomes blur on Huawei server

Status in linux package in Ubuntu:
  Triaged
Status in install-package source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged

Bug description:
  For all(as I know) Huawei servers, the vga adapter are embed in the
  iBMC chips. Those server can install from ISO manually for 16.04.4 and
  screen display normally. But for 18.04 ( tested both for daily and
  final beta)version, the install screen is blur. One of tested server
  is Huawei 2855 v5, the certification link for 16.04 are
  https://certification.ubuntu.com/hardware/201707-25596/.

  Below are key difference of dmesg. It seems might related with DRM.

  18.04 install screen is blur 
  dmesg
  ...
  [2.039009] fb0: EFI VGA frame buffer device
  ...
  [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.191435] [drm] No driver support for vblank timestamp query.
  [4.209338] checking generic (9000 30) vs hw (0 0)
  [4.209384] fbcon: hibmcdrmfb (fb1) is primary device
  [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63
  ...
  [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device
  [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on 
minor 0
  ...
  [5.636624] vga16fb: initializing
  [5.636627] vga16fb: mapped to 0x48a7a1d2
  [5.636630] checking generic (9000 30) vs hw (a 1)
  [5.636676] fb2: VGA16 VGA frame buffer device
  ...

  16.04.4 install screen is fine (no screen blur)
  dmesg
  ...
  [2.000419] fb0: EFI VGA frame buffer device
  
  [8.795065] vga16fb: initializing
  [8.795068] vga16fb: mapped to 0x880a
  [8.795071] checking generic (9800 30) vs hw (a 1)
  [8.795121] fb1: VGA16 VGA frame buffer device
  ...

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

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

[Kernel-packages] [Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-17 Thread Kamal Mostafa

This is documented and fixed by mainline commit:

commit d1ecfa9d1f402366b1776fbf84e635678a51414f
Author: van der Linden, Frank 
Date:   Fri May 4 16:11:00 2018 -0400

x86/xen: Reset VCPU0 info pointer after shared_info remap

This patch fixes crashes during boot for HVM guests on older (pre HVM
vector callback) Xen versions. Without this, current kernels will always
fail to boot on those Xen versions.

Sample stack trace:

   BUG: unable to handle kernel paging request at ff20
   IP: __xen_evtchn_do_upcall+0x1e/0x80
   PGD 1e0e067 P4D 1e0e067 PUD 1e10067 PMD 235c067 PTE 0
Oops: 0002 [#1] SMP PTI
   Modules linked in:
   CPU: 0 PID: 512 Comm: kworker/u2:0 Not tainted 4.14.33-52.13.amzn1.x86_64
 #1
   Hardware name: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
   task: 88002531d700 task.stack: c948
   RIP: 0010:__xen_evtchn_do_upcall+0x1e/0x80
   RSP: :880025403ef0 EFLAGS: 00010046
   RAX: 813cc760 RBX: ff20 RCX: c9483ef0
   RDX: 880020540a00 RSI: 880023c78000 RDI: 001c
   RBP: 0001 R08:  R09: 
   R10:  R11:  R12: 
   R13: 880025403f5c R14:  R15: 
   FS:  () GS:88002540() knlGS:0
000
   CS:  0010 DS:  ES:  CR0: 80050033
   CR2: ff20 CR3: 01e0a000 CR4: 06f0
Call Trace:
   
   do_hvm_evtchn_intr+0xa/0x10
   __handle_irq_event_percpu+0x43/0x1a0
   handle_irq_event_percpu+0x20/0x50
   handle_irq_event+0x39/0x60
   handle_fasteoi_irq+0x80/0x140
   handle_irq+0xaf/0x120
   do_IRQ+0x41/0xd0
   common_interrupt+0x7d/0x7d
   

During boot, the HYPERVISOR_shared_info page gets remapped to make it work
with KASLR. This means that any pointer derived from it needs to be
adjusted.

The only value that this applies to is the vcpu_info pointer for VCPU 0.
For PV and HVM with the callback vector feature, this gets done via the
smp_ops prepare_boot_cpu callback. Older Xen versions do not support the
HVM callback vector, so there is no Xen-specific smp_ops set up in that
scenario. So, the vcpu_info pointer for VCPU 0 never gets set to the proper
value, and the first reference of it will be bad. Fix this by resetting it
immediately after the remap.

Signed-off-by: Frank van der Linden 
Reviewed-by: Eduardo Valentin 
Reviewed-by: Alakesh Haloi 
Reviewed-by: Vallish Vaidyeshwara 
Reviewed-by: Boris Ostrovsky 
Cc: Juergen Gross 
Cc: Boris Ostrovsky 
Cc: xen-de...@lists.xenproject.org
Signed-off-by: Boris Ostrovsky 


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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

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

Title:
  Kernel panic on boot (m1.small in cn-north-1)

Status in linux package in Ubuntu:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress

Bug description:
  We're observing the following panic on boot when trying to boot an
  m1.small in cn-north-1 (which is a region in AWS China):

  [2.271681] Hardware name: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
  [2.271681] RIP: 0010:__xen_evtchn_do_upcall+0x24/0x80
  [2.271681] RSP: :8e21aa003ea0 EFLAGS: 00010046
  [2.271681] RAX: 9dd82920 RBX: ff20 RCX: 
8728b34e
  [2.271681] RDX: 8e21a3252800 RSI: 8e21a724e000 RDI: 
001c
  [2.271681] RBP: 8e21aa003eb8 R08: 9ea05040 R09: 

  [2.271681] R10: 8e21aa003f28 R11:  R12: 
0001
  [2.271681] R13:  R14: 0022 R15: 
8e21a3246900
  [2.271681] FS:  () GS:8e21aa00() 
knlGS:
  [2.271681] CS:  0010 DS:  ES:  CR0: 80050033
  [2.271681] CR2: ff20 CR3: 0b80a000 CR4: 
06f0
  [2.271681] Call Trace:
  [2.271681]  
  [2.271681]  xen_hvm_evtchn_do_upcall+0xe/0x10
  [2.271681]  do_hvm_evtchn_intr+0xe/0x20
  [

[Kernel-packages] [Bug 1762928] Re: [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest

** No longer affects: linux (Ubuntu Artful)

** No longer affects: linux (Ubuntu 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/1762928

Title:
  [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ---Problem Description---
  tm_trap_test failed on P8 compat mode [16.04.04 daily build as well bionic ] 
guests on a P9 host running bionic final beta version.
   
  Contact Information = srikanth/bssrika...@in.ibm.com 
   
  ---uname output---

  16.04.04 Guest running in P8compat mode:

  Linux guest 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:18:22 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  18.04 guest running in P8compat mode:
  Linux ubuntu 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Log into P9 Ubuntu 18.04 host, take console of guest 
`srikanth_ubuntu160404`
  2. Run TM selftests
  git clone --depth 1 https://github.com/torvalds/linux.git;cd 
linux/tools/testing/selftests/powerpc/;git log --oneline -1;make;make -C tm 
run_tests

  We will observe one of the tm tests failing, mentioned below:

  selftests: tm-trap
  
  test: tm_trap_test
  tags: git_version:c18bb39
  Little-Endian machine detected. Checking if endianness flips inadvertently on 
trap in TM... yes!
  failure: tm_trap_test
  not ok 1..11 selftests:  tm-trap [FAIL]

  
  Expected result: All tm selftests should have been pass on the P8 compat 
guest.. giventhat we had TM workaround patches in latest Ubuntu BIONIC host 
kernel
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for srikanth/bssrika...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.


  == Comment: #2 - SRIKANTH AITHAL  - 2018-04-10
  01:32:00 ==

  
  == Comment: #3 - SRIKANTH AITHAL  - 2018-04-10 
01:33:41 ==

  
  == Comment: #4 - SRIKANTH AITHAL  - 2018-04-10 
01:34:02 ==

  
  Please pick 

   `1c200e63d055 ("powerpc/tm: Fix endianness flip on trap")`

  ie. the commit that the test was written for

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

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

[Kernel-packages] [Bug 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

2018-05-17 Thread Tyler Hicks

** Also affects: crash (Ubuntu Cosmic)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: New

** Also affects: crash (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: crash (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

Title:
  Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid
  structure member offset" in crash prompt.

Status in The Ubuntu-power-systems project:
  Triaged
Status in crash package in Ubuntu:
  New
Status in crash source package in Xenial:
  New
Status in crash source package in Artful:
  New
Status in crash source package in Bionic:
  New
Status in crash source package in Cosmic:
  New

Bug description:
  [Impact]
  Some analysis won't be possible on new kernels (hwe-edge on xenial, for 
example; or the standard bionic kernel).

  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on a live 
amd64 system, with success.

  [Regression Potential]
  Analysis of crashed kernels will require that the crash file be moved to a 
system where crash doesn't have the regression. The patch, however, should 
touch only the broken command, and has been tested.

  -

  
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---

  Ubuntu 18.04: "ipcs" command fails with error "invalid structure
  member offset" in crash prompt.

  ---Environment--

  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to reproduce--

  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump

  ---Logs

  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#

  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.

  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03e56c7c600  [THREAD_INFO: c03e56cb]
   CPU: 41
     STATE: TASK_RUNNING (SYSRQ)

  crash> ?

  *  files  mach

[Kernel-packages] [Bug 1771238] Re: Not able to passthrough > 32 PCIe devices to a KVM Guest

2018-05-17 Thread Alex Williamson

Agreed with the initial analysis, there's nothing in device assignment
to limit to 32 devices except where downstream distros have
intentionally added a limit for support purposes.  The issue here is
that the host hit a PCIe Downstream Port Containment uncorrectable
error, apparently causing at least a sub-hierarchy of the PCIe topology
to go offline.  This is potentially more likely a hardware issue than a
software issue.  It may be possible to mask the issue by unbinding the
interconnect devices in the affected sub-hierarchy from the dpc driver.
It might also be interesting to test with a subset of devices to
understand if there are specific devices triggering spurious DPC errors,
it may only be a sub-set or single device triggering spurious errors, or
perhaps it's the succession of bus resets for GPU assignment that
trigger such a fault.  The system firmware logs may provide additional
information regarding the source(s) of the fault.

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

Title:
  Not able to passthrough > 32 PCIe devices to a KVM Guest

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  New

Bug description:
  Using an Ubuntu Server 16.04-based host with KVM hypervisor installed,
  we are unable to launch a vanilla Ubuntu Server 16.04.4 guest with >=
  32 PCIe devices. It is 100% reproducible. Using fewer PCIe devices
  works fine. We are using the vanilla kvm and qemu packages from the
  Canonical repos.

  The ultimate goal is to create a KVM Guest wherein I can passthrough
  44 PCI devices.

  When a KVM Guest launches, it also has some internal PCIe devices
  including host bridge, USB, IDE (for virtual disk), and virtual nic
  etc.

  Script used to launch all devices looks like this:

  #!/bin/bash 
  NAME=16gpuvm 

  sudo qemu-img create -f qcow2 /home/lab/kvm/images/${NAME}.img 40G && 
  sudo virt-install \ 
  --name ${NAME} \ 
  --ram 716800 \ 
  --vcpus 88 \ 
  --disk path=/home/lab/kvm/images/${NAME}.img,format=qcow2 \ 
  --network bridge=virbr0 \ 
  --graphics none \ 
  --host-device 34:00.0 \ 
  --host-device 36:00.0 \ 
  --host-device 39:00.0 \ 
  --host-device 3b:00.0 \ 
  --host-device 57:00.0 \ 
  --host-device 59:00.0 \ 
  --host-device 5c:00.0 \ 
  --host-device 5e:00.0 \ 
  --host-device 61:00.0 \ 
  --host-device 62:00.0 \ 
  --host-device 63:00.0 \ 
  --host-device 65:00.0 \ 
  --host-device 66:00.0 \ 
  --host-device 67:00.0 \ 
  --host-device 35:00.0 \ 
  --host-device 3a:00.0 \ 
  --host-device 58:00.0 \ 
  --host-device 5d:00.0 \ 
  --host-device 2e:00.0 \ 
  --host-device 2f:00.0 \ 
  --host-device 51:00.0 \ 
  --host-device 52:00.0 \ 
  --host-device b7:00.0 \ 
  --host-device b9:00.0 \ 
  --host-device bc:00.0 \ 
  --host-device be:00.0 \ 
  --host-device e0:00.0 \ 
  --host-device e2:00.0 \ 
  --host-device e5:00.0 \ 
  --host-device e7:00.0 \ 
  --host-device c1:00.0 \ 
  --host-device c2:00.0 \ 
  --host-device c3:00.0 \ 
  --host-device c5:00.0 \ 
  --host-device c6:00.0 \ 
  --host-device c7:00.0 \ 
  --host-device b8:00.0 \ 
  --host-device bd:00.0 \ 
  --host-device e1:00.0 \ 
  --host-device e6:00.0 \ 
  --host-device b1:00.0 \ 
  --host-device b2:00.0 \ 
  --host-device da:00.0 \ 
  --host-device db:00.0 \ 
  --console pty,target_type=serial \ 
  --location http://ftp.ubuntu.com/ubuntu/dists/xenial/main/installer-amd64 \ 
  --initrd-inject=/home/lab/kvm/images/preseed.cfg \ 
  --extra-args=" 
  console=ttyS0,115200 
  locale=en_US 
  console-keymaps-at/keymap=us 
  console-setup/ask_detect=false 
  console-setup/layoutcode=us 
  keyboard-configuration/layout=USA 
  keyboard-configuration/variant=USA 
  hostname=${NAME} 
  file=file:/preseed.cfg 
  "

  Passing > 32 device causes this issue:  32nd device hits a DPC error
  and the host/HV crashes:

  
  Apr 25 22:34:35 xpl-evt-16 kernel: [18125.977496] dpc :5b:10.0:pcie210: 
DPC containment event, status:0x0009 source:0x
  Apr 25 22:34:35 xpl-evt-16 kernel: [18125.977500] dpc :5b:10.0:pcie210: 
DPC unmasked uncorrectable error detected, remove downstream devices
  Apr 25 22:34:35 xpl-evt-16 kernel: [18125.994326] vfio-pci :5e:00.0: 
Refused to change power state, currently in D3
  Apr 25 22:34:35 xpl-evt-16 kernel: [18125.994427] iommu: Removing device 
:5e:00.0 from group 92

  
  From syslog (attached)

  Apr 25 22:37:13 xpl-evt-16 kernel: [2.194358] dpc :bb:04.0:pcie210: 
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+ 
RP PIO Log 0, DL_ActiveErr+
  Apr 25 22:37:13 xpl-evt-16 kernel: [2.194387] dpc :bb:10.0:pcie210: 
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+ 
RP PIO Log 0, DL_ActiveErr+
  Apr 25 22:37:13 xpl-evt-16 kernel: [2.194413] dpc :d9:00.0:pcie210: 
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+ 
RP PIO Log

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-05-17 Thread Agustin Barto

The commit was reverted
https://github.com/torvalds/linux/commit/82bf43b291888599b4079244d12195d214086fa4

** Changed in: linux (Ubuntu)
   Status: Fix Released => 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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)

2018-05-17 Thread Sebastiaan Breedveld

@info-erikkallen : did you try the solution proposed in post #26 ?

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

Title:
  USB stops working after a while (xhci_hcd :00:14.0: Timeout while
  waiting for setup device command)

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my laptop the kernel will sometimes drop the USB hub. After this,
  the laptop doesn't recognise any device plugged in to the USB ports -
  plugging and unplugging any device I've tried into any of the USB
  ports produces no response, not even dmesg entries.

  Strangely this also applies to bluetooth - it no longer works once USB
  has dropped (possibly the module is hung of the bus internally).

  Once this has happened only a reboot fixes it; I've not managed to
  find any combination of module unload/reload or suspend cycles to
  reinitialise things correctly.

  Relevant snippet of dmesg:
  [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe 
the host is dead
  [48838.079742] xhci_hcd :00:14.0: Abort command ring failed
  [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up
  [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079806] sched: RT throttling activated
  [48838.079981] usb 1-1: USB disconnect, device number 16
  [48838.079985] usb 1-1.2: USB disconnect, device number 18
  [48838.079987] usb 1-1.2.3: USB disconnect, device number 19
  [48838.080285] usb 1-1.2.4: USB disconnect, device number 20
  [48838.111892] usb 1-1.4: USB disconnect, device number 17
  [48838.191292] usb 1-4: USB disconnect, device number 6
  [48838.267550] usb 1-10: USB disconnect, device number 8
  [48838.282968] usb 2-1: device not accepting address 8, error -62
  [48838.282983] usb 2-1: USB disconnect, device number 8
  [48838.282986] usb 2-1.2: USB disconnect, device number 9

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  4255 F pulseaudio
   /dev/snd/controlC0:  chris  4255 F pulseaudio
  CRDA:
   country AU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (3, 23), (N/A)
(5250 - 5330 @ 40), (3, 23), (0 ms), DFS
(5735 - 5835 @ 40), (3, 30), (N/A)
  CurrentDesktop: Unity
  Date: Thu Jan 22 12:59:27 2015
  InstallationDate: Installed on 2013-08-06 (533 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Galago UltraPro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed 
root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd break=mount
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1759860] Re: Ubuntu MATE Bionic Beaver alpha - Hibernate/Resume Failure - ASUS P8H67-M PRO

2018-05-17 Thread Radu Axente

Finally found a solution for this issue => you have to add the kernel
parameter "resume=UUID=" to the
/etc/default/grub file: edit the file and afterwards sudo update-grub)
or use Grub Customizer.

Questions:
1. Why the heck is this kernel parameter suddenly required in Ubuntu 18.04 ?
It was definitely not necessary in Ubuntu 16.10, 17.04, 17.10.  No, it wasn't, 
on 3 PCs !!!

2. Why the heck is this kernel parameter not set automatically if it is 
required ?
It should be definitely set automatically.  Would make everything easier for a 
simple user like me :-)

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

Title:
  Ubuntu MATE Bionic Beaver alpha - Hibernate/Resume Failure - ASUS
  P8H67-M PRO

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Resume from hibernate failed

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mihai  1761 F pulseaudio
  Date: Thu Mar 29 15:35:03 2018
  DuplicateSignature: hibernate/resume:System manufacturer System Product 
Name:3904
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=21524dee-cba8-4f0e-8718-07509400c3f8
  InstallationDate: Installed on 2018-03-29 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  InterpreterPath: /usr/bin/python3.6
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=47373a65-7f17-4d2d-a006-c7eebce02df4 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  Title: [System manufacturer System Product Name] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/27/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3904
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3904:bd04/27/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1771844] Re: powerpc/livepatch: Implement reliable stack tracing for the consistency model

** Tags removed: targetmilestone-inin18041
** Tags added: targetmilestone-inin1804

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

Title:
  powerpc/livepatch: Implement reliable stack tracing for the
  consistency model

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Kamalesh Babulal - 2018-05-15 09:37:52 ==
  Livepatch has a consistency model which is a hybrid of kGraft and kpatch:  it 
uses kGraft's per-task consistency and syscall barrier switching combined with 
kpatch's stack trace switching. The current approach is stack checking of 
sleeping tasks.  If no affected functions are on the stack of a given task, the 
task is patched.  In most cases this will patch most or all of the tasks on the 
first try.  Otherwise, it'll keep trying periodically.  This patch implements 
the reliable stack tracing for consistency model a.k.a 
HAVE_RELIABLE_STACKTRACE. 

  This will help in switching livepatching implementation to basic per-
  task consistency model. It is the foundation, which will help us
  enable security patches changing function or data semantics. This is
  the biggest remaining piece needed on ppc64le to make livepatch more
  generally useful.

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac

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

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

[Kernel-packages] [Bug 1718293] Re: [Ubuntu 17.10] POWER9 - Base - Integrate P9 VAS (Virtual Accelerator Switchboard) support in kernel

** Tags removed: targetmilestone-inin1804
** Tags added: targetmilestone-inin1810

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

Title:
  [Ubuntu 17.10] POWER9 - Base - Integrate P9 VAS (Virtual Accelerator
  Switchboard) support in kernel

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  This feature request is used to submit kernel changes needed for
  adding VAS (Virtual Accelerator Switchboard) support. VAS interface
  allows kernel or user space to communicate with any accelerator (Ex:
  NX). kernel changes will be to open a window/ channel with accelerator
  and communicate with copy / paste facility.

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

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

[Kernel-packages] [Bug 1771844] Re: powerpc/livepatch: Implement reliable stack tracing for the consistency model

** Tags removed: targetmilestone-inin1804
** Tags added: targetmilestone-inin18041

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

Title:
  powerpc/livepatch: Implement reliable stack tracing for the
  consistency model

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Kamalesh Babulal - 2018-05-15 09:37:52 ==
  Livepatch has a consistency model which is a hybrid of kGraft and kpatch:  it 
uses kGraft's per-task consistency and syscall barrier switching combined with 
kpatch's stack trace switching. The current approach is stack checking of 
sleeping tasks.  If no affected functions are on the stack of a given task, the 
task is patched.  In most cases this will patch most or all of the tasks on the 
first try.  Otherwise, it'll keep trying periodically.  This patch implements 
the reliable stack tracing for consistency model a.k.a 
HAVE_RELIABLE_STACKTRACE. 

  This will help in switching livepatching implementation to basic per-
  task consistency model. It is the foundation, which will help us
  enable security patches changing function or data semantics. This is
  the biggest remaining piece needed on ppc64le to make livepatch more
  generally useful.

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac

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

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

[Kernel-packages] [Bug 1771859] [NEW] Cgroup swap support not working

2018-05-17 Thread Alberto

Public bug reported:

Hello everybody,

this is my first bug report, so I apologize for any mistakes.

I'm trying to install docker with swap support, but cgroups swap support
is missing. It works on ubuntu 17.10, but it breaks on ubuntu 18.04

Was cgroup swap support removed from default kernel in ubuntu 18.04?
Should I recompile the kernel to enable it?


This is what check configs report:

root@proxima:~# wget
https://raw.githubusercontent.com/moby/moby/master/contrib/check-
config.sh && bash check-config.sh


- CONFIG_MEMCG_SWAP_ENABLED: missing
(cgroup swap accounting is currently not enabled, you can enable it by 
setting boot option "swapaccount=1")


this is my /etc/default/grub

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="console=tty1 console=ttyS0 cgroup_enable=memory 
swapaccount=1"
GRUB_CMDLINE_LINUX=""

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Thu May 17 16:12:17 2018
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Cgroup swap support not working

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Hello everybody,

  this is my first bug report, so I apologize for any mistakes.

  I'm trying to install docker with swap support, but cgroups swap
  support is missing. It works on ubuntu 17.10, but it breaks on ubuntu
  18.04

  Was cgroup swap support removed from default kernel in ubuntu 18.04?
  Should I recompile the kernel to enable it?


  This is what check configs report:

  root@proxima:~# wget
  https://raw.githubusercontent.com/moby/moby/master/contrib/check-
  config.sh && bash check-config.sh

  
  - CONFIG_MEMCG_SWAP_ENABLED: missing
  (cgroup swap accounting is currently not enabled, you can enable it by 
setting boot option "swapaccount=1")

  
  this is my /etc/default/grub

  GRUB_DEFAULT=0
  GRUB_HIDDEN_TIMEOUT=0
  GRUB_HIDDEN_TIMEOUT_QUIET=true
  GRUB_TIMEOUT=10
  GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty1 console=ttyS0 cgroup_enable=memory 
swapaccount=1"
  GRUB_CMDLINE_LINUX=""

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 17 16:12:17 2018
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

2018-05-17 Thread Anthony Wong

** Description changed:

  Intel wireless driver and firmware require updates in order to meet the
  new ETSI regulation [1] for OEM machines shipped from factories.
  
  Intel provided us the following information for what are required to
  update:
  
  1. Kernel driver:
  
  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/
  
  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.
  
  2. linux-firmware
  Requires latest versions from linux-firmware.git
  
  3. wireless-regdb update
  
  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
+ 
+ ---
+ == SRU Justification for linux-firmware ==
+ [Impact]
+ Intel released these firmware updates to support the new ETSI 5GHz
+ Adaptivity Requirement, OEM has to meet it in order to ship.
+ 
+ [Test Case]
+ Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.
+ 
+ [Regression Potential]
+ It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
+ and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

** Description changed:

  Intel wireless driver and firmware require updates in order to meet the
  new ETSI regulation [1] for OEM machines shipped from factories.
  
  Intel provided us the following information for what are required to
  update:
  
  1. Kernel driver:
  
  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/
  
  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.
  
  2. linux-firmware
  Requires latest versions from linux-firmware.git
  
  3. wireless-regdb update
  
  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
  
  ---
  == SRU Justification for linux-firmware ==
  [Impact]
- Intel released these firmware updates to support the new ETSI 5GHz
- Adaptivity Requirement, OEM has to meet it in order to ship.
+ Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.
  
  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.
  
  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

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

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux-firmware source package in Xenial:
  In Progress
Status in linux-oem source package in Xenial:
  New
Status in wireless-regdb source package in Xenial:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  New
Status in wireless-regdb source package in Bionic:
  New

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

[Kernel-packages] [Bug 1768852] Re: Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host controller dead

2018-05-17 Thread cardonator

Just want to confirm that this fixed the problem for me as well. And
just to be absolutely clear, here are some of the problems I was having
when attaching/detaching Thunderbolt 3 on my XPS 13 9360:

1) Re-attaching the dock, USB would not function
2) Unable to suspend, reboot, or shutdown after detaching the dock
3) Eventual system hang/freeze
4) Occasional black screen in KDE

After running this kernel for a bit, it seems all of these problems are
gone. Looking forward to having the patch merged! For what it's worth, I
began having these issues on the KDE Neon distribution sometime after
the 4.10 kernel was 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/1768852

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  ===SRU Justification===
  [Impact]
  When unplugging the Thunderbolt 3 cable from the TBT controller, kernel
  oops.

  [Test]
  The user confirms this patch works.

  [Fix]
  tty_unregister_driver may be called more than 1 time in some
  hotplug cases,it will cause the kernel oops. This patch checked
  dbc_tty_driver to make sure it is unregistered only 1 time.

  [Regression Potential]
  Low. The change is to guard against null pointer, so it's the correct
  behavior.

  ===Original Bugreport===
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo 
Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device

[Kernel-packages] [Bug 1768526] Re: Include nfp driver in linux-modules

2018-05-17 Thread Seth Forshee

Committed to unstable, patch sent for bionic.

https://lists.ubuntu.com/archives/kernel-team/2018-May/092526.html

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

Title:
  Include nfp driver in linux-modules

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress

Bug description:
  SRU Justification:
  --

  [Impact]

   * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included 
in linux-moudles-extra.
     An implication of this is that on minimal installs, where the 
linux-modules but not linux-modules-extra
     packages are available, the nfp.ko module cannot be installed. In 
particular this means the driver for
     any VFs of Netronome Agilio SmartNICs which have been made available to 
guests using PCI pass-through
     cannot be used by those guests if they have installed using Canonical 
cloud images, a likely scenario.

     In contrast the driver for the i40e is provided in the linux-modules 
package and thus guests can
     access their VFs in the scenario described above.

     Thus we do not believe it is unreasonable to request that nfp.ko be 
included in linux-modules rather
     than linux-modules-extras. And we believe that this warrants SRU inclusion 
as it is the difference between
     users-of guests being able to use Netronome Agilio SmartNICs and not be 
able to use them.

     This is a packaging update request and included no request to change the 
kernel source code,
     thus no backports are requred.

  [Test Case]

   * Install system using Canonical cloud images

   * Observer that
  /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is
  missing;

   * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or 
otherwise,
     that the nfp driver is not loaded and no netdevs are present for the 
Netronome Agilio SmartNIC.

  [Regression Potential]

   * Any bugs present in the nfp.ko will now be exposted to guests. However as 
the same nfp.ko driver binary
     is already included in and available on installs that have access to 
linux-modules-extra, this does not
     seem an unreasonable burden.

  [Other Info]

   * None

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

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

[Kernel-packages] [Bug 1771844] Re: powerpc/livepatch: Implement reliable stack tracing for the consistency model

2018-05-17 Thread Frank Heimes

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Status: New => Triaged

** Tags added: triage-g

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  powerpc/livepatch: Implement reliable stack tracing for the
  consistency model

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Kamalesh Babulal - 2018-05-15 09:37:52 ==
  Livepatch has a consistency model which is a hybrid of kGraft and kpatch:  it 
uses kGraft's per-task consistency and syscall barrier switching combined with 
kpatch's stack trace switching. The current approach is stack checking of 
sleeping tasks.  If no affected functions are on the stack of a given task, the 
task is patched.  In most cases this will patch most or all of the tasks on the 
first try.  Otherwise, it'll keep trying periodically.  This patch implements 
the reliable stack tracing for consistency model a.k.a 
HAVE_RELIABLE_STACKTRACE. 

  This will help in switching livepatching implementation to basic per-
  task consistency model. It is the foundation, which will help us
  enable security patches changing function or data semantics. This is
  the biggest remaining piece needed on ppc64le to make livepatch more
  generally useful.

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac

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

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

[Kernel-packages] [Bug 1771844] [NEW] powerpc/livepatch: Implement reliable stack tracing for the consistency model

Public bug reported:

== Comment: #0 - Kamalesh Babulal - 2018-05-15 09:37:52 ==
Livepatch has a consistency model which is a hybrid of kGraft and kpatch: it
uses kGraft's per-task consistency and syscall barrier switching combined with
kpatch's stack trace switching. The current approach is stack checking of
sleeping tasks. If no affected functions are on the stack of a given task, the
task is patched. In most cases this will patch most or all of the tasks on the
first try. Otherwise, it'll keep trying periodically. This patch implements
the reliable stack tracing for consistency model a.k.a
HAVE_RELIABLE_STACKTRACE.

This will help in switching livepatching implementation to basic per-
task consistency model. It is the foundation, which will help us enable
security patches changing function or data semantics. This is the
biggest remaining piece needed on ppc64le to make livepatch more
generally useful.

https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac

** Affects: ubuntu-power-systems
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Triaged

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

** Tags: architecture-ppc64le bugnameltc-167879 severity-critical
targetmilestone-inin1804 triage-g

** Tags added: architecture-ppc64le bugnameltc-167879 severity-critical
targetmilestone-inin1804

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

Title:
powerpc/livepatch: Implement reliable stack tracing for the
consistency model

Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
New

Bug description:
== Comment: #0 - Kamalesh Babulal - 2018-05-15 09:37:52 ==
Livepatch has a consistency model which is a hybrid of kGraft and kpatch: it
uses kGraft's per-task consistency and syscall barrier switching combined with
kpatch's stack trace switching. The current approach is stack checking of
sleeping tasks. If no affected functions are on the stack of a given task, the
task is patched. In most cases this will patch most or all of the tasks on the
first try. Otherwise, it'll keep trying periodically. This patch implements
the reliable stack tracing for consistency model a.k.a
HAVE_RELIABLE_STACKTRACE.

This will help in switching livepatching implementation to basic per-
task consistency model. It is the foundation, which will help us
enable security patches changing function or data semantics. This is
the biggest remaining piece needed on ppc64le to make livepatch more
generally useful.

https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac

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

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

[Kernel-packages] [Bug 1768526] Re: Include nfp driver in linux-modules

2018-05-17 Thread Seth Forshee

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

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

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

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

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

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

Title:
  Include nfp driver in linux-modules

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

Bug description:
  SRU Justification:
  --

  [Impact]

   * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included 
in linux-moudles-extra.
     An implication of this is that on minimal installs, where the 
linux-modules but not linux-modules-extra
     packages are available, the nfp.ko module cannot be installed. In 
particular this means the driver for
     any VFs of Netronome Agilio SmartNICs which have been made available to 
guests using PCI pass-through
     cannot be used by those guests if they have installed using Canonical 
cloud images, a likely scenario.

     In contrast the driver for the i40e is provided in the linux-modules 
package and thus guests can
     access their VFs in the scenario described above.

     Thus we do not believe it is unreasonable to request that nfp.ko be 
included in linux-modules rather
     than linux-modules-extras. And we believe that this warrants SRU inclusion 
as it is the difference between
     users-of guests being able to use Netronome Agilio SmartNICs and not be 
able to use them.

     This is a packaging update request and included no request to change the 
kernel source code,
     thus no backports are requred.

  [Test Case]

   * Install system using Canonical cloud images

   * Observer that
  /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is
  missing;

   * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or 
otherwise,
     that the nfp driver is not loaded and no netdevs are present for the 
Netronome Agilio SmartNIC.

  [Regression Potential]

   * Any bugs present in the nfp.ko will now be exposted to guests. However as 
the same nfp.ko driver binary
     is already included in and available on installs that have access to 
linux-modules-extra, this does not
     seem an unreasonable burden.

  [Other Info]

   * None

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

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

[Kernel-packages] [Bug 1771844] [NEW] powerpc/livepatch: Implement reliable stack tracing for the consistency model

2018-05-17 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

== Comment: #0 - Kamalesh Babulal - 2018-05-15 09:37:52 ==
Livepatch has a consistency model which is a hybrid of kGraft and kpatch:  it 
uses kGraft's per-task consistency and syscall barrier switching combined with 
kpatch's stack trace switching. The current approach is stack checking of 
sleeping tasks.  If no affected functions are on the stack of a given task, the 
task is patched.  In most cases this will patch most or all of the tasks on the 
first try.  Otherwise, it'll keep trying periodically.  This patch implements 
the reliable stack tracing for consistency model a.k.a 
HAVE_RELIABLE_STACKTRACE. 

This will help in switching livepatching implementation to basic per-
task consistency model. It is the foundation, which will help us enable
security patches changing function or data semantics. This is the
biggest remaining piece needed on ppc64le to make livepatch more
generally useful.

https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac

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


** Tags: architecture-ppc64le bugnameltc-167879 severity-critical 
targetmilestone-inin1804
-- 
powerpc/livepatch: Implement reliable stack tracing for the consistency model
https://bugs.launchpad.net/bugs/1771844
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 1771813] Re: [Ubuntu 18.10 FEAT] new libocxl library

2018-05-17 Thread Steve Langasek

** Package changed: linux (Ubuntu) => 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/1771813

Title:
  [Ubuntu 18.10 FEAT] new libocxl library

Status in The Ubuntu-power-systems project:
  New
Status in Ubuntu:
  Incomplete

Bug description:
  Add new package for libocxl, which is the user library which allows to
  interact with the new ocxl  "generic" driver, used to interact with
  opencapi cards/accelerators.

  I submitted the package to Debian NEW queue.
  Waiting for ftpmasters review : 
https://ftp-master.debian.org/new/libocxl_1.0.0-1.html

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

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

[Kernel-packages] [Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)

Hi @mlx,

Could you please test any of the kernels in -proposed to check if they
fix the problem?

Thank you.

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

Title:
  sky2 gigabit ethernet driver sometimes stops working after lid-open
  resume from sleep (88E8055)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  sky2 ethernet stops working after system resume from suspend.

  [Fix]
  Increase the PCI D3 delay can workaround the issue.

  [Test]
  User responded that the D3 delay increase can solve the issue.

  [Regression Potential]
  Low. It only affects one device. The fix only increase the delay timer,
  without any functional change.

  ===Original Bug Report===
  After resuming from sleep using the lid-open event, OFTEN (60% replicable, 
usually after 2nd or later resume) the NIC is not functional, and reloading the 
sky2 module does not help. Relevant parts from dmesg:

  [  582.852065] sky2 :04:00.0: Refused to change power state, currently in 
D3
  ...
  [  827.613729] sky2 :04:00.0: ignoring stuck error report bit
  [  827.613748] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613750] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613752] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613754] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613756] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613759] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613761] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613763] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613765] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613767] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613769] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613772] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613774] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613776] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613778] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613780] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613782] sky2 :04:00.0: enp4s0: phy I/O error

  And after reloading the module:
  [ 1421.781480] sky2: driver version 1.30
  [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003)
  [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff
  [ 1421.782292] sky2: probe of :04:00.0 failed with error -95

  Possibly relevant:
  [ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID.

  Replicability: When it happens once, further suspend-resume cycles (tried ~5) 
don't fix it. Reboot fixes the NIC, and it often survives first resume after 
that, but 1-2 suspend-resume cycles later the issue WILL occur again.
  Per-boot chance of encountering the issue - so far 2/5.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-12-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Sat Mar 24 09:54:10 2018
  HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1
  InstallationDate: Installed on 2018-03-21 (3 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180319)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d 
consoleblank=300
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2008
  dmi.bios.vendor: Phoenix

[Kernel-packages] [Bug 1771813] Re: [Ubuntu 18.10 FEAT] new libocxl library

2018-05-17 Thread Manoj Iyer

Regarding introducing this new package in 18.04 (universe) here are the
next steps to consider.

1. This package would first need to make it into 18.10, this bug would 
accomplish that. 
2. Once it is introduced in 18.10, it needs to be tested, and tested to work 
with the 18.04 kernel.
3. Once it is tested and verified in 18.10 and with 18.04 kernel, *in a 
separate bug* request a backport of this package to 18.04.

It is my understanding that introducing this package in the 'universe'
archive would be the path of least resistance. Introducing this in the
'main' archive, have it included in the iso, and auto pre-installed etc
would be much harder.

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

Title:
  [Ubuntu 18.10 FEAT] new libocxl library

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Add new package for libocxl, which is the user library which allows to
  interact with the new ocxl  "generic" driver, used to interact with
  opencapi cards/accelerators.

  I submitted the package to Debian NEW queue.
  Waiting for ftpmasters review : 
https://ftp-master.debian.org/new/libocxl_1.0.0-1.html

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

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

[Kernel-packages] [Bug 1771813] Re: [Ubuntu 18.10 FEAT] new libocxl library

2018-05-17 Thread Steve Langasek

Packages cannot be downloaded from the Debian NEW queue.  Did you want
to provide the package directly to us for review or do you want to wait
for the package to pass review in Debian?

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

Title:
  [Ubuntu 18.10 FEAT] new libocxl library

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Add new package for libocxl, which is the user library which allows to
  interact with the new ocxl  "generic" driver, used to interact with
  opencapi cards/accelerators.

  I submitted the package to Debian NEW queue.
  Waiting for ftpmasters review : 
https://ftp-master.debian.org/new/libocxl_1.0.0-1.html

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

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

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

--- Comment From bren...@br.ibm.com 2018-05-17 10:29 EDT---
This package is very important for POWER9, since this is the default userspace 
way to access OpenCAPI accelerators.

Not having this package on Ubuntu LTS will impact the OpenCAPI
accelerators usage on Ubuntu on POWER9.

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

Title:
  [Ubuntu 18.10 FEAT] new libocxl library

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Add new package for libocxl, which is the user library which allows to
  interact with the new ocxl  "generic" driver, used to interact with
  opencapi cards/accelerators.

  I submitted the package to Debian NEW queue.
  Waiting for ftpmasters review : 
https://ftp-master.debian.org/new/libocxl_1.0.0-1.html

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

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

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

2018-05-17 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/1771826

Title:
  Creation of IMA file hashes fails when appraisal is enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a system that has IMA appraisal enabled it is impossible to create
  security.ima extended attribute files that contain IMA hash.

  For instance, consider the following use case:

  1) extract application files to a staging area as non root user
  2) verify that installation is correct
  3) create IMA extended attributes for the installed files
  4) move the files to their destination
  5) change the files ownership to root

  With kernel 4.4.x step 3 will fail.

  The issues is fixed in upstream kernels by the following commit [1]:

  commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b
  Author: Mimi Zohar 
  Date:   Wed Nov 2 09:14:16 2016 -0400

  Revert "ima: limit file hash setting by user to fix and log modes"

  [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i
  d=f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-124-generic 4.4.0-124.148
  ProcVersionSignature: User Name 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 17 14:07 seq
   crw-rw 1 root audio 116, 33 May 17 14:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu May 17 14:08:59 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=aef88a4e-dbea-4cc7-be8b-03cf8501cc8f ro biosdevname=0 net.ifnames=0 
console=tty1 console=ttyS0 crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-backports-modules-4.4.0-124-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.12
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.12
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1730331] Re: ath10k_pci: firmware crashed!

2018-05-17 Thread V-Mark

I face very similar problem, but I have v2.1 hardware of QCA6174 (I assume you 
do not have QCA6147 neither).
I installed Kubuntu Bionic Beaver (18.04) from fresh.

I still face the firmware crash IF (and only if) I switch off / hibernate my 
laptop with active WIFI connection.
If I switch off wifi before hibernate, everything is perfect.
Relevant syslog:
May 16 23:48:53 HU-NB058 kernel: [159310.466589] wlp2s0: deauthenticating from 
84:16:f9:7b:a6:88 by local choice (Reason: 3=DEAUTH_LEAVING)
May 16 23:48:53 HU-NB058 systemd[1]: Starting Load/Save RF Kill Switch Status...
May 16 23:48:53 HU-NB058 systemd[1]: Started Load/Save RF Kill Switch Status.
May 16 23:48:56 HU-NB058 wpa_supplicant[734]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=84:16:f9:7b:a6:88 reason=3 locally_generated=1
May 16 23:48:56 HU-NB058 kernel: [159313.534608] ath10k_pci :02:00.0: 
failed to install key for vdev 0 peer 84:16:f9:7b:a6:88: -110
May 16 23:48:56 HU-NB058 kernel: [159313.534616] wlp2s0: failed to remove key 
(0, 84:16:f9:7b:a6:88) from hardware (-110)
May 16 23:48:56 HU-NB058 kernel: [159313.540951] ath10k_pci :02:00.0: 
firmware crashed! (guid b84d150d-4ef6-4369-bcf1-e5f53f30e725)
May 16 23:48:56 HU-NB058 kernel: [159313.540968] ath10k_pci :02:00.0: 
qca6174 hw2.1 target 0x0501 chip_id 0x003405ff sub 11ad:0804
May 16 23:48:56 HU-NB058 kernel: [159313.540974] ath10k_pci :02:00.0: 
kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
May 16 23:48:56 HU-NB058 kernel: [159313.542103] ath10k_pci :02:00.0: 
firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features 
ignore-otp,no-4addr-pad crc32 10bf8e08
May 16 23:48:56 HU-NB058 kernel: [159313.542739] ath10k_pci :02:00.0: 
board_file api 2 bmi_id N/A crc32 ae2e275a
May 16 23:48:56 HU-NB058 kernel: [159313.542746] ath10k_pci :02:00.0: 
htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
May 16 23:48:56 HU-NB058 kernel: [159313.547609] ath10k_pci :02:00.0: 
firmware register dump:
May 16 23:48:56 HU-NB058 kernel: [159313.547612] ath10k_pci :02:00.0: [00]: 
0x0501 0x 0x0092E4DC 0x4E0C99B6
May 16 23:48:56 HU-NB058 kernel: [159313.547614] ath10k_pci :02:00.0: [04]: 
0x0092E4DC 0x00060130 0x0018 0x0041A760

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

Title:
  ath10k_pci: firmware crashed!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  ...
  Nov  4 18:35:50 akane kernel: [   10.216896] ath10k_pci :04:00.0: qca988x 
hw2.0 target 0x4100016c chip_id 0x043222ff sub :
  Nov  4 18:35:50 akane kernel: [   10.216908] ath10k_pci :04:00.0: kconfig 
debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
  Nov  4 18:35:50 akane kernel: [   10.217641] ath10k_pci :04:00.0: 
firmware ver 10.2.4.70.63-2 api 5 features 
no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d
  Nov  4 18:35:50 akane kernel: [   10.228600] kvm: Nested Virtualization 
enabled
  Nov  4 18:35:50 akane kernel: [   10.228611] kvm: Nested Paging enabled
  Nov  4 18:35:50 akane kernel: [   10.258913] ath10k_pci :04:00.0: 
board_file api 1 bmi_id N/A crc32 bebc7c08
  Nov  4 18:35:50 akane kernel: [   10.263535] MCE: In-kernel MCE decoding 
enabled.
  Nov  4 18:35:50 akane kernel: [   10.271401] EDAC amd64: Node 0: DRAM ECC 
enabled.
  Nov  4 18:35:50 akane kernel: [   10.271416] EDAC amd64: F16h_M30h detected 
(node 0).
  Nov  4 18:35:50 akane kernel: [   10.271491] EDAC MC: DCT0 chip selects:
  Nov  4 18:35:50 akane kernel: [   10.271494] EDAC amd64: MC: 0:  4096MB 1:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271523] EDAC amd64: MC: 2: 0MB 3:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271526] EDAC amd64: MC: 4: 0MB 5:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271528] EDAC amd64: MC: 6: 0MB 7:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271530] EDAC MC: DCT1 chip selects:
  Nov  4 18:35:50 akane kernel: [   10.271532] EDAC amd64: MC: 0: 0MB 1:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271534] EDAC amd64: MC: 2: 0MB 3:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271537] EDAC amd64: MC: 4: 0MB 5:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271539] EDAC amd64: MC: 6: 0MB 7:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271541] EDAC amd64: using x4 syndromes.
  Nov  4 18:35:50 akane kernel: [   10.271542] EDAC amd64: MCT channel count: 1
  Nov  4 18:35:50 akane kernel: [   10.271829] EDAC MC0: Giving out device to 
module amd64_edac controller F16h_M30h: DEV :00:18.3 (INTERRUPT)
  Nov  4 18:35:50 akane kernel: [   10.271892] EDAC PCI0: Giving out device to 
module amd64_edac controller EDAC PCI controller: DEV :00:18.2 (POLLED)
  Nov  4 18:35:50 akane kernel: [   10.271894] AMD64 EDAC driver v3.5.0
  Nov  4 18:35:50 akane kernel: [   10.532131] EXT4-fs (sdc1): mounted

[Kernel-packages] [Bug 1771813] Re: [Ubuntu 18.10 FEAT] new libocxl library

2018-05-17 Thread Manoj Iyer

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Foundations Team (canonical-foundations)

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

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

Title:
  [Ubuntu 18.10 FEAT] new libocxl library

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Add new package for libocxl, which is the user library which allows to
  interact with the new ocxl  "generic" driver, used to interact with
  opencapi cards/accelerators.

  I submitted the package to Debian NEW queue.
  Waiting for ftpmasters review : 
https://ftp-master.debian.org/new/libocxl_1.0.0-1.html

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

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

[Kernel-packages] [Bug 1771826] [NEW] Creation of IMA file hashes fails when appraisal is enabled

2018-05-17 Thread rppt

Public bug reported:

On a system that has IMA appraisal enabled it is impossible to create
security.ima extended attribute files that contain IMA hash.

For instance, consider the following use case:

1) extract application files to a staging area as non root user
2) verify that installation is correct
3) create IMA extended attributes for the installed files
4) move the files to their destination
5) change the files ownership to root

With kernel 4.4.x step 3 will fail.

The issues is fixed in upstream kernels by the following commit [1]:

commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b
Author: Mimi Zohar 
Date:   Wed Nov 2 09:14:16 2016 -0400

Revert "ima: limit file hash setting by user to fix and log modes"

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i
d=f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-124-generic 4.4.0-124.148
ProcVersionSignature: User Name 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 May 17 14:07 seq
 crw-rw 1 root audio 116, 33 May 17 14:07 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Thu May 17 14:08:59 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:

ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=aef88a4e-dbea-4cc7-be8b-03cf8501cc8f ro biosdevname=0 net.ifnames=0 
console=tty1 console=ttyS0 crashkernel=384M-:128M
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-124-generic N/A
 linux-backports-modules-4.4.0-124-generic  N/A
 linux-firmware 1.157.17
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.12
dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.12
dmi.sys.vendor: QEMU

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


** Tags: xenial

** Description changed:

- Further information:
  On a system that has IMA appraisal enabled it is impossible to create
  security.ima extended attribute files that contain IMA hash.
  
  For instance, consider the following use case:
  
  1) extract application files to a staging area as non root user
  2) verify that installation is correct
  3) create IMA extended attributes for the installed files
  4) move the files to their destination
  5) change the files ownership to root
  
- 
  With kernel 4.4.x step 3 will fail.
  
  The issues is fixed in upstream kernels by the following commit [1]:
  
  commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b
  Author: Mimi Zohar 
  Date:   Wed Nov 2 09:14:16 2016 -0400
  
- Revert "ima: limit file hash setting by user to fix and log modes"
+ Revert "ima: limit file hash setting by user to fix and log modes"
  
  [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i
  d=f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-124-generic 4.4.0-124.148
  ProcVersionSignature: User Name 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 May 17 14:07 seq
-  crw-rw 1 root audio 116, 33 May 17 14:07 timer
+  total 0
+  crw-rw 1 root audio 116,  1 May 17 14:07 seq
+  crw-rw 1 root audio 116, 33 May 17 14:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu May 17 14:08:59 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC

[Kernel-packages] [Bug 1627474] Re: ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)

2018-05-17 Thread V-Mark

I use Kubuntu 18.04 (Bionic Beaver) from fresh install.

I face very similar problem:
ath10k_pci :02:00.0: firmware crashed! (guid 
b84d150d-4ef6-4369-bcf1-e5f53f30e725)

EVERY TIME when I would like to switch off or hibernate laptop with working 
WIFI state.
If I switch off WIFI before hibernate, everything is OK.
Other than switch off/hibernate I did not experience firmware crash, but I have 
to admit I "disabled" wifi powersave functions.

Last crash:
May 16 23:47:20 HU-NB058 wpa_supplicant[734]: wlp2s0: WPA: Group rekeying 
completed with 84:16:f9:7b:a6:88 [GTK=CCMP]
May 16 23:48:53 HU-NB058 kernel: [159310.466589] wlp2s0: deauthenticating from 
84:16:f9:7b:a6:88 by local choice (Reason: 3=DEAUTH_LEAVING)
May 16 23:48:53 HU-NB058 systemd[1]: Starting Load/Save RF Kill Switch Status...
May 16 23:48:53 HU-NB058 systemd[1]: Started Load/Save RF Kill Switch Status.
May 16 23:48:56 HU-NB058 wpa_supplicant[734]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=84:16:f9:7b:a6:88 reason=3 locally_generated=1
May 16 23:48:56 HU-NB058 kernel: [159313.534608] ath10k_pci :02:00.0: 
failed to install key for vdev 0 peer 84:16:f9:7b:a6:88: -110
May 16 23:48:56 HU-NB058 kernel: [159313.534616] wlp2s0: failed to remove key 
(0, 84:16:f9:7b:a6:88) from hardware (-110)
May 16 23:48:56 HU-NB058 kernel: [159313.540951] ath10k_pci :02:00.0: 
firmware crashed! (guid b84d150d-4ef6-4369-bcf1-e5f53f30e725)
May 16 23:48:56 HU-NB058 kernel: [159313.540968] ath10k_pci :02:00.0: 
qca6174 hw2.1 target 0x0501 chip_id 0x003405ff sub 11ad:0804
May 16 23:48:56 HU-NB058 kernel: [159313.540974] ath10k_pci :02:00.0: 
kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
May 16 23:48:56 HU-NB058 kernel: [159313.542103] ath10k_pci :02:00.0: 
firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features 
ignore-otp,no-4addr-pad crc32 10bf8e08
May 16 23:48:56 HU-NB058 kernel: [159313.542739] ath10k_pci :02:00.0: 
board_file api 2 bmi_id N/A crc32 ae2e275a
May 16 23:48:56 HU-NB058 kernel: [159313.542746] ath10k_pci :02:00.0: 
htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
May 16 23:48:56 HU-NB058 kernel: [159313.547609] ath10k_pci :02:00.0: 
firmware register dump:
May 16 23:48:56 HU-NB058 kernel: [159313.547612] ath10k_pci :02:00.0: [00]: 
0x0501 0x 0x0092E4DC 0x4E0C99B6
May 16 23:48:56 HU-NB058 kernel: [159313.547614] ath10k_pci :02:00.0: [04]: 
0x0092E4DC 0x00060130 0x0018 0x0041A760


** Attachment added: "syslog which containing the firmware crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627474/+attachment/5140862/+files/syslog.1

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

Title:
  ath10k_pci :03:00.0: firmware crashed! (uuid n/a)

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

Bug description:
  The wireless card in my Acer V3-372-587T suffers from firmware crashes
  regularly (every 5-10mins approx).

  $ lsb_release -rd
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10

  Checking dmesg I see:

  $ dmesg | grep ath10k 
  [91/214]
  [7.773800] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [8.123875] request_firmware: ath10k/pre-cal-pci-:03:00.0.bin
  [8.126477] ath10k_pci :03:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:03:00.0.bin fa$
  led with error -2
  [8.126481] request_firmware: ath10k/cal-pci-:03:00.0.bin
  [8.126492] ath10k_pci :03:00.0: Direct firmware load for 
ath10k/cal-pci-:03:00.0.bin failed
  with error -2
  [8.126493] request_firmware: ath10k/QCA6174/hw3.0/firmware-5.bin
  [8.127095] ath10k_pci :03:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin fa$
  led with error -2
  [8.127098] ath10k_pci :03:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.$
  in': -2
  [8.127101] request_firmware: ath10k/QCA6174/hw3.0/firmware-4.bin
  [8.129458] ath10k_pci :03:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 105b:e09$
  [8.129460] ath10k_pci :03:00.0: kconfig debug 0 debugfs 0 tracing 0 
dfs 0 testmode 0
  [8.129954] ath10k_pci :03:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowla$
  ,ignore-otp,no-4addr-pad crc32 75dee6c5
  [8.195123] request_firmware: ath10k/QCA6174/hw3.0/board-2.bin
  [8.198141] ath10k_pci :03:00.0: board_file api 2 bmi_id N/A crc32 
6fc88fe7
  [   10.338326] ath10k_pci :03:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypt$
   1
  [   10.436186] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
  [  319.064117] ath10k_pci :03:00.0: firmware crashed! (uuid n/a)
  [  319.064164] ath10k_pci :03:00.0: qca6174 hw3.2 target 0x0503 
chip_id

[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb

2018-05-17 Thread Balint Reczey

There is no need for logs, the modules are missing from the udeb

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

Title:
  Please include ax88179_178a and r8152 modules in d-i udeb

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  r8152 is used in a thunderbolt-connected docking station and
  ax88179_178a by an external USB dongle.

  Despite having two nics connected i can't install Bionic. :-)

  This is probably a subset of the modules to be included when fixing
  LP: #1503218.

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

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

[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)

2018-05-17 Thread Jeff Veit

Yes, confirmed. It's the patch: 109.12Mbs on 5GHz with the stock kernel.

I guess the patch needs to take note of possible throughput too.

I've only looked at download speed in all these tests.

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

Title:
  Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
  1535)

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Update (2017-05-20):
  Kalle Valo suggested a hack which increased client -> AP TCP performance - so 
it does not look like a firmware issue as I thought originally, rather an 
ath10k driver issue:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11
  https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom)
  Tested here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17

  Update: added some forensics in the paste (a long read):
  http://paste.ubuntu.com/24118478/

  -

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535

  Original message:
  --
  I experience a very poor 802.11ac performance of a QCA6174 Wireless card 
(Killer Wireless 1535).

  This is a dev version of Zesty with a recently released 4.10 kernel:

  uname -r
  4.10.0-9-generic

  dpkg -l linux-firmware | grep ii
  ii  linux-firmware 1.163all  Firmware for Linux kernel drivers

  lspci -vvv:

  ...
  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: ath10k_pci
  Kernel modules: ath10k_pci

  -

  Testing wireless speed with RT-87U 802.11ac router shows that the
  speed is only 27.3 megabits per second which is very low for an
  802.11ac card:

  iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [  3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001
  [ ID] Interval   Transfer Bandwidth
  [  3]  0.0-10.0 sec  32.6 MBytes  27.3 Mbits/sec

  

  For comparison, on the same network (from the same distance to the
  router) I have the following result with an Intel's card (on a 4.8
  kernel, different laptop):

  UX32LN:~$ lspci | grep 7260
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  UX32LN:~$ iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001
  [ ID] Interval Transfer Bandwidth
  [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec
  administrator@UX32LN:~$ lsp
  lspci lspcmcia lspgpot

  200 Mbps is much better.

  ---

  Back to the problematic card:

  Booted 16.04.2 with the rolling HWE kernel 4.8:

  journalctl -k | grep -i ath
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( 
-> 0002)
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch 
firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 
debugfs 1 tracing 1 dfs 0 testmode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 
bmi_id N/A crc32 6fc88fe7
  Mar 04 18:28:34 ubuntu kernel: ath10k_pci

[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)

2018-05-17 Thread Jeff Veit

Joseph,

Yes, your kernel does resolve this bug. Measuring using speedtest.net,
before your kernel, using the current Bionic kernel, I get 8.64mbps on a
2.4Ghz network, with a max of around 10Mbs. Four minutes later, with
your kernel, 34.92Mbs with a max of around 50Mbs.

What is perhaps not so good, is that the performance of a 5Ghz network
has dropped dramatically from around 90 - 100 Mbs, down to 9.12 to
9.43mbps. Tested repeatedly over a few minutes to make sure it's not
just a one-off.

I'll install the stock kernel again, and check it's the patch, and not
some external factor.

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

Title:
  Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
  1535)

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Update (2017-05-20):
  Kalle Valo suggested a hack which increased client -> AP TCP performance - so 
it does not look like a firmware issue as I thought originally, rather an 
ath10k driver issue:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11
  https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom)
  Tested here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17

  Update: added some forensics in the paste (a long read):
  http://paste.ubuntu.com/24118478/

  -

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535

  Original message:
  --
  I experience a very poor 802.11ac performance of a QCA6174 Wireless card 
(Killer Wireless 1535).

  This is a dev version of Zesty with a recently released 4.10 kernel:

  uname -r
  4.10.0-9-generic

  dpkg -l linux-firmware | grep ii
  ii  linux-firmware 1.163all  Firmware for Linux kernel drivers

  lspci -vvv:

  ...
  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: ath10k_pci
  Kernel modules: ath10k_pci

  -

  Testing wireless speed with RT-87U 802.11ac router shows that the
  speed is only 27.3 megabits per second which is very low for an
  802.11ac card:

  iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [  3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001
  [ ID] Interval   Transfer Bandwidth
  [  3]  0.0-10.0 sec  32.6 MBytes  27.3 Mbits/sec

  

  For comparison, on the same network (from the same distance to the
  router) I have the following result with an Intel's card (on a 4.8
  kernel, different laptop):

  UX32LN:~$ lspci | grep 7260
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  UX32LN:~$ iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001
  [ ID] Interval Transfer Bandwidth
  [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec
  administrator@UX32LN:~$ lsp
  lspci lspcmcia lspgpot

  200 Mbps is much better.

  ---

  Back to the problematic card:

  Booted 16.04.2 with the rolling HWE kernel 4.8:

  journalctl -k | grep -i ath
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( 
-> 0002)
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch 
firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  Mar 04 18:28:31 ubuntu

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

2018-05-17 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 1771823

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

Title:
  Please include ax88179_178a and r8152 modules in d-i udeb

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  r8152 is used in a thunderbolt-connected docking station and
  ax88179_178a by an external USB dongle.

  Despite having two nics connected i can't install Bionic. :-)

  This is probably a subset of the modules to be included when fixing
  LP: #1503218.

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

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

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

2018-05-17 Thread Dimitri John Ledkov

Imho, we should ship all modules in udebs. Because missing a module in a
udeb is pain.

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

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

Status in linux package in Ubuntu:
  Triaged

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

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

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

[Kernel-packages] [Bug 1771823] [NEW] Please include ax88179_178a and r8152 modules in d-i udeb

2018-05-17 Thread Balint Reczey

Public bug reported:

r8152 is used in a thunderbolt-connected docking station and
ax88179_178a by an external USB dongle.

Despite having two nics connected i can't install Bionic. :-)

This is probably a subset of the modules to be included when fixing LP:
#1503218.

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

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

Title:
  Please include ax88179_178a and r8152 modules in d-i udeb

Status in linux package in Ubuntu:
  New

Bug description:
  r8152 is used in a thunderbolt-connected docking station and
  ax88179_178a by an external USB dongle.

  Despite having two nics connected i can't install Bionic. :-)

  This is probably a subset of the modules to be included when fixing
  LP: #1503218.

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

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

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140838/+files/WifiSyslog.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice:

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1771749/+attachment/5140837/+files/UdevDb.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  IfupdownConfig:
   #

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

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140836/+files/PulseList.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  IfupdownConfig:
   #

[Kernel-packages] [Bug 1771749] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140832/+files/ProcCpuinfoMinimal.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/1771749

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140835/+files/ProcModules.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  IfupdownConfig:

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140833/+files/ProcEnviron.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  IfupdownConfig:

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140834/+files/ProcInterrupts.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3

[Kernel-packages] [Bug 1771749] NetworkManager.conf.txt

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140831/+files/NetworkManager.conf.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/1771749

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3

[Kernel-packages] [Bug 1771749] NetDevice.lo.txt

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140830/+files/NetDevice.lo.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/1771749

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  IfupdownConfig:

[Kernel-packages] [Bug 1771749] NetDevice.enp0s7.txt

apport information

** Attachment added: "NetDevice.enp0s7.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140829/+files/NetDevice.enp0s7.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/1771749

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3

[Kernel-packages] [Bug 1771749] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140826/+files/Dependencies.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/1771749

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  IfupdownConfig:

[Kernel-packages] [Bug 1771749] IpAddr.txt

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1771749/+attachment/5140827/+files/IpAddr.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/1771749

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  IfupdownConfig:
   #

[Kernel-packages] [Bug 1771749] Re: Ethernet connection lost after few minutes since starting

apport information

** Tags added: apport-collected

** Description changed:

  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.
  
  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it is
  most everything Ok, but -I think that- the network-manager has a
  problem.
  
  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or hours,
  but several times per day.
  
  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.
  
  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.
  
  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the scanner:
  If I plug it in some USB port of the laptop once Kubuntu 18.04 is
  already running, it's not detected by Xsane. I have to plug it in before
  than pressing the power button or at the time of starting the OS, for
  the scanner to be detected by the scanning program (and then only works
  with Xsane, not if I use Simple Scan or Skanlite, even when it works
  under Xsane), as I said in the Bug #1771525 and, evenly, if I unplug the
  scanner cable from the USB port it is not detected anymore when plugging
  it again, and only restarting the laptop makes it to be detected.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  nosotros   1116 F pulseaudio
+  /dev/snd/controlC1:  nosotros   1116 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
+ InstallationDate: Installed on 2018-05-11 (6 days ago)
+ InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
+ IpRoute:
+  default via 192.168.1.1 dev enp0s7 proto static metric 100 
+  169.254.0.0/16 dev enp0s7 scope link metric 1000 
+  192.168.1.0/24 dev enp0s7 proto kernel scope

[Kernel-packages] [Bug 1771749] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1771749/+attachment/5140828/+files/Lspci.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/1771749

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  IfupdownConfig:
   #

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

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1771749/+attachment/5140824/+files/CRDA.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  IfupdownConfig:
   #

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1771749/+attachment/5140825/+files/CurrentDmesg.txt

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nosotros   1116 F pulseaudio
   /dev/snd/controlC1:  nosotros   1116 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bb1531db-e7c0-48eb-a5b7-5afe3df47ba3
  IfupdownConfig:

[Kernel-packages] [Bug 1771813] Re: [Ubuntu 18.10 FEAT] new libocxl library

2018-05-17 Thread Frank Heimes

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => Medium

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

Title:
  [Ubuntu 18.10 FEAT] new libocxl library

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Add new package for libocxl, which is the user library which allows to
  interact with the new ocxl  "generic" driver, used to interact with
  opencapi cards/accelerators.

  I submitted the package to Debian NEW queue.
  Waiting for ftpmasters review : 
https://ftp-master.debian.org/new/libocxl_1.0.0-1.html

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

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

[Kernel-packages] [Bug 1771813] [NEW] [Ubuntu 18.10 FEAT] new libocxl library

Public bug reported:

Add new package for libocxl, which is the user library which allows to
interact with the new ocxl  "generic" driver, used to interact with
opencapi cards/accelerators.

I submitted the package to Debian NEW queue.
Waiting for ftpmasters review : 
https://ftp-master.debian.org/new/libocxl_1.0.0-1.html

** Affects: ubuntu-power-systems
 Importance: Medium
 Status: New

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


** Tags: architecture-ppc64le bugnameltc-161265 severity-medium 
targetmilestone-inin1810

** Tags added: architecture-ppc64le bugnameltc-161265 severity-medium
targetmilestone-inin1810

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

Title:
  [Ubuntu 18.10 FEAT] new libocxl library

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Add new package for libocxl, which is the user library which allows to
  interact with the new ocxl  "generic" driver, used to interact with
  opencapi cards/accelerators.

  I submitted the package to Debian NEW queue.
  Waiting for ftpmasters review : 
https://ftp-master.debian.org/new/libocxl_1.0.0-1.html

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

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

[Kernel-packages] [Bug 1771813] [NEW] [Ubuntu 18.10 FEAT] new libocxl library

2018-05-17 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Add new package for libocxl, which is the user library which allows to
interact with the new ocxl  "generic" driver, used to interact with
opencapi cards/accelerators.

I submitted the package to Debian NEW queue.
Waiting for ftpmasters review : 
https://ftp-master.debian.org/new/libocxl_1.0.0-1.html

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


** Tags: architecture-ppc64le bugnameltc-161265 severity-medium 
targetmilestone-inin1810
-- 
[Ubuntu 18.10 FEAT] new libocxl library
https://bugs.launchpad.net/bugs/1771813
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 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

2018-05-17 Thread mrvanes

Fixed for me using the above mentioned PPA.
Thx!

And I agree with Guillaume that, for me, this was a major annoyance
nonetheless...

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Confirmed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Kernel-packages] [Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

2018-05-17 Thread Jeroen Evens

will this also be fixed in 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/1764194

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  This bug causes a Dell Latitude 5490/5590 with BIOS update 1.1.9 to get a
  black screen at boot. Specifying 'nomodeset' on the kernel command line works
  around the problem.

  Intel resolved the problem in upstream commit a3520b8992e5.  This commit
  is now in mainline as of 4.17.rc2.  It has also been cc'd to upstream
  stable.

  
  == Fix ==
  a3520b8992e5 ("drm/i915/bios: filter out invalid DDC pins from VBT child 
devices")

  == Regression Potential ==
  Low.  This commit was also cc'd to upstream stable, so it recieved
  additional upstream review.


  
  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
  laptops, originally running BIOS version 1.0.8. The install media and
  the installed OS was running linux-generic-hwe kernel 4.13.0.

  After upgrading BIOS to latest version 1.1.9, the kernel no longer
  boots: right after loading the i915 drm driver, the screen goes black,
  and the machine can only be reset or power cycled. This is true for
  both the installation media, and the OS instance previously installed
  to the disk and updated to the latest hwe kernel 4.13.0-38.

  Specifying 'nomodeset' on the kernel command line works around the
  problem by disabling the i915 drm driver functionality. In that case,
  several display driver function are obviously missing (eg GLX &
  xrandr).

  The problem manifested itself even when using the drm upstream latest 
git-head version. A custom built kernel was used to provide logs for this 
upstream bug report:
  https://bugs.freedesktop.org/show_bug.cgi?id=105549

  The upstream Intel developers provided a patch, which was successfully tested 
by both the original reporter and me.
  https://patchwork.freedesktop.org/patch/216371/
  
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde

  I backported this fix to ubuntu-xenial hwe git-head, and tested the
  result successfully. I'd like this fix to be added to the ubuntu-
  xenial linux-generic-hwe kernel.

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

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

[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume

2018-05-17 Thread Woodrow Shen

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

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

Title:
  Suspend to idle: Open lid didn't resume

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and 
then they can't resume the system from opening the lid.

  [Test Case]
  1. echo s2idle | sudo tee /sys/power/mem_sleep
  2. Close the lid
  3. Open the lid

  [Fix]
  According a patch sent to 4.17-rc1, which was not be included before 4.15 
EOL, so we cherry pick the patch to Ubuntu 4.15 kernel.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953

  [Regression Potential]
  Per commit, this change also allows Dells XPS13 9360 blacklisted by commit 
71630b7a832f to use the power button for waking up from suspend-to-idle, no 
regression could be happened

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

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

[Kernel-packages] [Bug 1771799] Re: package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-05-17 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Installed when prompted by Ubuntu. This seems to have been a failure
  owing to /boot being jam-packed with other kernels.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-signed-image-4.13.0-41-generic 4.13.0-41.46
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Thu May 17 11:48:04 2018
  DuplicateSignature:
   package:linux-signed-image-4.13.0-41-generic:4.13.0-41.46
   Setting up linux-signed-image-4.13.0-39-generic (4.13.0-39.44) ...
   cp: error writing '/boot/vmlinuz-4.13.0-39-generic.efi.signed': No space 
left on device
   dpkg: error processing package linux-signed-image-4.13.0-39-generic 
(--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-06-19 (332 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to artful on 2018-02-19 (86 days ago)

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

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

[Kernel-packages] [Bug 1770011] Re: linux: 4.4.0-125.150 -proposed tracker

2018-05-17 Thread Brad Figg

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => Fix Released

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

Title:
  linux: 4.4.0-125.150 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Incomplete
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  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

  backports: bug 1770013 (linux-aws), bug 1770015 (linux-lts-xenial)
  derivatives: bug 1770016 (linux-aws), bug 1770018 (linux-euclid), bug 1770019 
(linux-kvm), bug 1770020 (linux-raspi2), bug 1770023 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: 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/1770011/+subscriptions

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

[Kernel-packages] [Bug 1770294] Re: linux-azure: 4.15.0-1011.11 -proposed tracker

Hardware Certification is not run for cloud kernels. Setting
certification-testing to 'Invalid'.

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

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

Title:
  linux-azure: 4.15.0-1011.11 -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:
  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 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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1011.11 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 --
  boot-testing-requested: true
  bugs-spammed: 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/1770294/+subscriptions

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

[Kernel-packages] [Bug 1767403] Re: linux-aws: 4.15.0-1008.8 -proposed tracker

Hardware Certification is not run for cloud kernels. Setting
certification-testing to 'Invalid'.

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

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

Title:
  linux-aws: 4.15.0-1008.8 -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:
  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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1767397
  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/1767403/+subscriptions

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

[Kernel-packages] [Bug 1771799] [NEW] package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-05-17 Thread Ben Glanton

Public bug reported:

Installed when prompted by Ubuntu. This seems to have been a failure
owing to /boot being jam-packed with other kernels.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-signed-image-4.13.0-41-generic 4.13.0-41.46
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Thu May 17 11:48:04 2018
DuplicateSignature:
 package:linux-signed-image-4.13.0-41-generic:4.13.0-41.46
 Setting up linux-signed-image-4.13.0-39-generic (4.13.0-39.44) ...
 cp: error writing '/boot/vmlinuz-4.13.0-39-generic.efi.signed': No space left 
on device
 dpkg: error processing package linux-signed-image-4.13.0-39-generic 
(--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-06-19 (332 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: linux-signed
Title: package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to artful on 2018-02-19 (86 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Installed when prompted by Ubuntu. This seems to have been a failure
  owing to /boot being jam-packed with other kernels.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-signed-image-4.13.0-41-generic 4.13.0-41.46
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Thu May 17 11:48:04 2018
  DuplicateSignature:
   package:linux-signed-image-4.13.0-41-generic:4.13.0-41.46
   Setting up linux-signed-image-4.13.0-39-generic (4.13.0-39.44) ...
   cp: error writing '/boot/vmlinuz-4.13.0-39-generic.efi.signed': No space 
left on device
   dpkg: error processing package linux-signed-image-4.13.0-39-generic 
(--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-06-19 (332 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to artful on 2018-02-19 (86 days ago)

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

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

[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

2018-05-17 Thread Anthony Wong

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

** Changed in: linux-firmware (Ubuntu Xenial)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

** Changed in: linux-firmware (Ubuntu Bionic)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

** Changed in: hwe-next
   Status: New => In Progress

** Changed in: hwe-next
   Importance: Undecided => Critical

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

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux-firmware source package in Xenial:
  In Progress
Status in linux-oem source package in Xenial:
  New
Status in wireless-regdb source package in Xenial:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  New
Status in wireless-regdb source package in Bionic:
  New

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

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

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

[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume

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

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

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

Title:
  Suspend to idle: Open lid didn't resume

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and 
then they can't resume the system from opening the lid.

  [Test Case]
  1. echo s2idle | sudo tee /sys/power/mem_sleep
  2. Close the lid
  3. Open the lid

  [Fix]
  According a patch sent to 4.17-rc1, which was not be included before 4.15 
EOL, so we cherry pick the patch to Ubuntu 4.15 kernel.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953

  [Regression Potential]
  Per commit, this change also allows Dells XPS13 9360 blacklisted by commit 
71630b7a832f to use the power button for waking up from suspend-to-idle, no 
regression could be happened

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

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

[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

2018-05-17 Thread aljosa

Compared to other Linux distros, Fedora 28 Atomic Workstation kills our 
"ELAN1203:00 04F3:3043" touchpad too. After one year and a half, the good news 
is that Daniel reported that the Anaconda setup of Fedora 28 Atomic Workstation 
fully activates "ELAN1203:00 04F3:3043" touchpad!
I couldn't find the live image, so consequently without booting up the USB into 
the live session I was not able to try diagnostic commands. But I can confirm 
that the Anaconda setup of Fedora 28 Atomic Workstation fully activates 
"ELAN1203:00 04F3:3043" touchpad - even with multitouch and tap-to-click.

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

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

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

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

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

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

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

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0

[Kernel-packages] [Bug 1768663] Re: Fix initialization failure detection in SDEI for device-tree based systems

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

Title:
  Fix initialization failure detection in SDEI for device-tree based
  systems

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  A crash may occur on Device-tree based systems w/ SDEI support, because of an 
ignored initialization failure.

  [Test Case]
  No known test case.

  [Regression Risk]
  The code is limited to ARM systems, and the fix is obviously correct (IMO). 
I'm unaware of any such system in the field - most SDEI-based systems will 
likely be ACPI based.

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

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

[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume

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

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

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

Title:
  Suspend to idle: Open lid didn't resume

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and 
then they can't resume the system from opening the lid.

  [Test Case]
  1. echo s2idle | sudo tee /sys/power/mem_sleep
  2. Close the lid
  3. Open the lid

  [Fix]
  According a patch sent to 4.17-rc1, which was not be included before 4.15 
EOL, so we cherry pick the patch to Ubuntu 4.15 kernel.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953

  [Regression Potential]
  Per commit, this change also allows Dells XPS13 9360 blacklisted by commit 
71630b7a832f to use the power button for waking up from suspend-to-idle, no 
regression could be happened

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

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

[Kernel-packages] [Bug 1769899] Re: No driver for Huawei network adapters on arm64

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

Title:
  No driver for Huawei network adapters on arm64

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  It isn't possible to use the Huawei PCIe network adapters on arm64

  [Test Case]
  Boot a system with a Huawei PCIe network adapter, see if the devices appear.

  [Regression Risk]
  The driver has been tested on arm64 and is known to work, this is just making 
it available.

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

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

[Kernel-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial

2018-05-17 Thread Nicolas Dichtel

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

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

Title:
  iproute2: unable to add ip lwt mpls route on xenial

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  The following command does not work:

  $ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
  Error: "nexthop" or end of line is expected instead of "encap"

  In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
  $ ip -V
  ip utility, iproute2-ss151103

  =>
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4

  With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
  $ modprobe mpls_iptunnel
  $ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev 
ntfp2
  $ ./ip/ip r
  [snip]
  10.201.0.0/24  encap mpls  300 via 10.200.0.1 dev ntfp2

  At least, this patch is missing:
  1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02

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

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

[Kernel-packages] [Bug 1771783] [NEW] iproute2: frr route protocols are not converted to string on xenial

2018-05-17 Thread Nicolas Dichtel

Public bug reported:

FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

iproute2 defines some protocols, but not all:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

A patch has been pushed upstream so that external applications can define their 
protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

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

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

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

Title:
  iproute2: frr route protocols are not converted to string on xenial

Status in iproute2 package in Ubuntu:
  New

Bug description:
  FRR puts its own proto numbers when inserting a route, example:
  $ ip route
  [snip]
  2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

  iproute2 defines some protocols, but not all:
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

  A patch has been pushed upstream so that external applications can define 
their protocols numbers:
  719e331ff619 ("Add support for rt_protos.d")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

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

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

[Kernel-packages] [Bug 1771780] Re: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded

2018-05-17 Thread Andrew Cloke

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: ubuntu-power-systems
   Importance: Undecided => Critical

** Tags added: triage-g

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

Title:
  [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and
  stop5 idle states when all CORES are guarded

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2018-05-16 04:07:59 ==
  ---Problem Description---
  cpupower idle-info is not listing stop4 and stop5 idle states when all CORES 
are guarded
   
  ---uname output---
  Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P9 Open Power Hardware with Ubuntu 18.04 OS.

  root@ltc-wspoon11:~# uname -a
  Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  root@ltc-wspoon11:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  Then guard an entire processor and also guard all the CORES in the
  processor 0 except for 1 single core.

  root@ltc-wspoon11:~# opal-gard list
   ID   | Error| Type   | Path
  ---
   0001 |  | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core0
   0002 |  | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core1
   0003 |  | Manual | /Sys0/Node0/Proc1
   0004 |  | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core1
   0005 |  | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core0
   0006 |  | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core0
   0007 |  | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core1
   0008 |  | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core0
   0009 |  | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core1
   000a |  | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core0
   000b |  | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core1
   000c |  | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core0
   000d |  | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core1
   000e |  | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core0
   000f |  | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core1
   0010 |  | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core0
   0011 |  | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core1
   0012 |  | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core0
   0013 |  | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core1
   0014 |  | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core0
   0015 |  | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core1
   0016 |  | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core1
   0017 |  | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core0
  ===

  Then execute the cpupower idle-info command to check the idle states
  being shown in the OS.

  root@ltc-wspoon11:~# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 7
  Available idle states: snooze stop0_lite stop0 stop1_lite stop1 stop2_lite 
stop2
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 774653
  Duration: 7698954
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 1
  Usage: 2751
  Duration: 11363825
  stop0:
  Flags/Description: stop0
  Latency: 2
  Usage: 2343
  Duration: 915084
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 5
  Usage: 20
  Duration: 1533
  stop1:
  Flags/Description: stop1
  Latency: 5
  Usage: 1103
  Duration: 1016794
  stop2_lite:
  Flags/Description: stop2_lite
  Latency: 10
  Usage: 5
  Duration: 765
  stop2:
  Flags/Description: stop2
  Latency: 10
  Usage: 113729
  Duration: 2850877810

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

  Userspace rpm: linux-tools-common

  Userspace tool obtained from project website:  na 
   
  == Comment: #8 - Akshay Adiga  - 2018-05-16 13:29:55 ==
  Patch is posted on linux mailing list

[Kernel-packages] [Bug 1771780] dmesg log is attached