date:20170221

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

2017-02-21 Thread bugproxy

--- Comment From laurent.duf...@fr.ibm.com 2017-02-21 02:51 EDT---
As discussed with Michal Hocko, I will write a larger patch which is delayed 
the soft limit's data as it is rarely used. This will extend the patch I 
already sent.

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

Title:
  [Ubuntu 17.04] Kernel panics when large number of hugepages is passed
  as an boot argument to kernel.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issue:
  ---
  Kernel unable to handle paging request and panic occurs when more number of 
hugepages is passed as a boot argument to the kernel .

  Environment:
  --
  Power NV : Habanaro Bare metal
  OS : Ubuntu 17.04
  Kernel Version : 4.9.0-11-generic

  Steps To reproduce:
  ---

  1 - When the ubuntu Kernel boots try to add the boot argument
  'hugepages = 1200'.

  The Kernel Panics and displays call traces like as below.

  [5.030274] Unable to handle kernel paging request for data at address 
0x
  [5.030323] Faulting instruction address: 0xc0302848
  [5.030366] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.030399] SMP NR_CPUS=2048 [5.030416] NUMA 
  [5.039443] PowerNV
  [5.039461] Modules linked in:
  [5.050091] CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 4.9.0-11-generic 
#12-Ubuntu
  [5.053266] Workqueue: events pcpu_balance_workfn
  [5.080647] task: c03c8fe9b800 task.stack: c03ffb118000
  [5.090876] NIP: c0302848 LR: c02709d4 CTR: 
c016cef0
  [5.094175] REGS: c03ffb11b410 TRAP: 0300   Not tainted  
(4.9.0-11-generic)
  [5.103040] MSR: 92009033 [
5.114466]   CR: 22424222  XER: 
  [5.124932] CFAR: c0008a60 DAR:  DSISR: 4000 
SOFTE: 1 
  GPR00: c02709d4 c03ffb11b690 c141a400 c03fff50e300 
  GPR04:  024001c2 c03ffb11b780 00219df5 
  GPR08: 003ffb09 c1454fd8   
  GPR12: 4400 c7b6 024001c2 024001c2 
  GPR16: 024001c2   0002 
  GPR20: 000c   024200c0 
  GPR24: c16eef48  c03fff50fd00 024001c2 
  GPR28:  c03fff50fd00 c03fff50e300 c03ffb11b820 
  NIP [c0302848] mem_cgroup_soft_limit_reclaim+0xf8/0x4f0
  [5.213613] LR [c02709d4] do_try_to_free_pages+0x1b4/0x450
  [5.230521] Call Trace:
  [5.230643] [c03ffb11b760] [c02709d4] 
do_try_to_free_pages+0x1b4/0x450
  [5.254184] [c03ffb11b800] [c0270d68] 
try_to_free_pages+0xf8/0x270
  [5.281896] [c03ffb11b890] [c0259b88] 
__alloc_pages_nodemask+0x7a8/0xff0
  [5.321407] [c03ffb11bab0] [c0282cd0] 
pcpu_populate_chunk+0x110/0x520
  [5.336262] [c03ffb11bb50] [c02841b8] 
pcpu_balance_workfn+0x758/0x960
  [5.351526] [c03ffb11bc50] [c00ecdd0] 
process_one_work+0x2b0/0x5a0
  [5.362561] [c03ffb11bce0] [c00ed168] worker_thread+0xa8/0x660
  [5.374007] [c03ffb11bd80] [c00f5320] kthread+0x110/0x130
  [5.385160] [c03ffb11be30] [c000c0e8] 
ret_from_kernel_thread+0x5c/0x74
  [5.389456] Instruction dump:
  [5.410036] eb81ffe0 eba1ffe8 ebc1fff0 ebe1fff8 4e800020 3d230001 e9499a42 
3d220004 
  [5.423598] 3929abd8 794a1f24 7d295214 eac90100  2fa9 
419eff74 3b20 
  [5.436503] ---[ end trace 23b650e96be5c549 ]---
  [5.439700] 

  This is purely a negative scenario where the system does not have
  enough memory as the hugepages is given a very large argument.

  Free output in a system:
  free -h
totalusedfree  shared  buff/cache   
available
  Mem:   251G2.1G248G5.2M502M
248G
  Swap:  2.0G159M1.8G

  The same scenario when tried after the linux is up like as,

  echo 1200 > /proc/sys/vm/nr_hugepages

  HugePages_Total:   15069
  HugePages_Free:15069
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB
  root@ltc-haba2:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   251G237G 13G5.6M311M 
13G
  Swap:  2.0G159M1.8G

  In this case the kernel is able to allocate around 237 Gb for hugetlb.

  But while the system is booting it gives us panic so please let know
  if this scenario  is expected  to be handled.

  I identified the root cause of the panic.
  When the system is running with low memory during mem cgroup initialisa

[Kernel-packages] [Bug 1666439] [NEW] Request: Add/backport this patch for stability with Bay Trail

2017-02-21 Thread Hanno

Public bug reported:

Hi,

please add and backport this patch to current Ubuntu kernel packages:

https://lists.freedesktop.org/archives/intel-
gfx/2017-February/120021.html

It is the result of a lengthy bug hunt described in

https://bugzilla.kernel.org/show_bug.cgi?id=109051#c683

There are several bug reports of stability problems with Bay Trail
devices on Launchpad where this patch should help make things better,
while the search for the root cause of the problem is still going on.

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


** Tags: patch xenial yakkety zesty

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

Title:
  Request: Add/backport this patch for stability with Bay Trail

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  please add and backport this patch to current Ubuntu kernel packages:

  https://lists.freedesktop.org/archives/intel-
  gfx/2017-February/120021.html

  It is the result of a lengthy bug hunt described in

  https://bugzilla.kernel.org/show_bug.cgi?id=109051#c683

  There are several bug reports of stability problems with Bay Trail
  devices on Launchpad where this patch should help make things better,
  while the search for the root cause of the problem is still going on.

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

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

[Kernel-packages] [Bug 1531865] Re: 4.2 (linux-generic-lts-wily) kernel hangs on Bay Trail based Asus X553MA

2017-02-21 Thread Hanno

There's progress for this bug which resulted in this patch:

https://lists.freedesktop.org/archives/intel-
gfx/2017-February/120021.html

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

Title:
  4.2 (linux-generic-lts-wily) kernel hangs on Bay Trail based Asus
  X553MA

Status in linux package in Ubuntu:
  Triaged
Status in linux package in Debian:
  New

Bug description:
  Kernels since 4.2-rc1 contain:

  [8fb55197e64d5988ec57b54e973daeea72c3f2ff] drm/i915: Agressive
  downclocking on Baytrail

  which causes hangs on my Bay Trail based Asus X553MA and likely on other Bay 
Trail based machines
  as well. The hangs occur between minutes and hours after booting and there is 
no information found
  related to them in kernel message buffer.

  I found the above commit by doing bisection between 4.1.0 and 4.2-rc1 and 
reported it to intel-gfx
  mailing list:

  http://lists.freedesktop.org/archives/intel-
  gfx/2016-January/084203.html

  I tested that these hangs occur with 14.04 LTS using latest 
linux-generic-lts-wily (4.2.0-23-generic) kernel
  exactly as with any kernel beginning from 4.2-rc1 up to 4.4-rc8.

  I'm now writing this bug report running 4.4-rc8 with patches from the above 
commit removed because
  4.2.0-23-generic just hanged while I was trying to send report.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jamse  2144 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg:
   [   20.017300] init: plymouth-upstart-bridge main process (1462) terminated 
with status 1
   [   20.017332] init: plymouth-upstart-bridge main process ended, respawning
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-17 (415 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04ca:3010 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=85bd44f0-e67f-450d-bfb5-0f87c90482cd ro quiet splash console=tty0 
console=ttyUSB0,115200n8 ignore_loglevel vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmware1.127.19
  Tags:  trusty
  Uname: Linux 4.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  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.:bvrX553MA.209:bd08/08/2014:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X553MA
  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/1531865/+subscriptions

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

[Kernel-packages] [Bug 1666439] Re: Request: Add/backport this patch for stability with Bay Trail

2017-02-21 Thread dino99

** Tags added: patch xenial yakkety zesty

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

Title:
  Request: Add/backport this patch for stability with Bay Trail

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  please add and backport this patch to current Ubuntu kernel packages:

  https://lists.freedesktop.org/archives/intel-
  gfx/2017-February/120021.html

  It is the result of a lengthy bug hunt described in

  https://bugzilla.kernel.org/show_bug.cgi?id=109051#c683

  There are several bug reports of stability problems with Bay Trail
  devices on Launchpad where this patch should help make things better,
  while the search for the root cause of the problem is still going on.

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

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

[Kernel-packages] [Bug 1664663] Re: [Hyper-V] kvp daemon start failure on Zesty

2017-02-21 Thread Chris Valean

The same error appears from KVP also on the test kernel
4.8.0-22_4.8.0-22.24~lp1664663.

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

Title:
  [Hyper-V] kvp daemon start failure on Zesty

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

Bug description:
  Hello,

  On Ubuntu Server 17.04 daily from Febr 14th we see that the KVP daemon
  although it is enabled in systemd, it fails to start at system boot.

  This is shown by error: "KVP: read failed; error:9 Bad file
  descriptor"

  I then manually ran the kvp binary, it returned the KVP data, and it's also 
automatically loading at boot. However, this is of course not the normal 
behavior.
  17.04 daily from Febr 14th is the first build we covered, so I cannot say if 
this is a regression introduced only at some point in 17.04 dailies.

  In syslog these are the only messages for KVP:
  Feb 14 08:01:22 ubuntu systemd[1]: Started Hyper-V KVP Protocol Daemon.
  Feb 14 08:01:22 ubuntu KVP: KVP starting; pid is:1837
  Feb 14 08:01:22 ubuntu KVP: KVP LIC Version: 3.1
  Feb 14 08:02:31 ubuntu KVP: read failed; error:9 Bad file descriptor

  
  systemd status:
  root@ubuntu:~# systemctl status hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
 Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Tue 2017-02-14 08:02:31 PST; 1min 
41s ago
   Main PID: 1837 (code=exited, status=1/FAILURE)
CPU: 4ms

  Feb 14 08:01:22 ubuntu systemd[1]: Started Hyper-V KVP Protocol Daemon.
  Feb 14 08:01:22 ubuntu KVP[1837]: KVP starting; pid is:1837
  Feb 14 08:01:22 ubuntu KVP[1837]: KVP LIC Version: 3.1
  Feb 14 08:02:31 ubuntu systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 14 08:02:31 ubuntu systemd[1]: hv-kvp-daemon.service: Unit entered failed 
state.
  Feb 14 08:02:31 ubuntu systemd[1]: hv-kvp-daemon.service: Failed with result 
'exit-code'.

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

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

[Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

2017-02-21 Thread dt9394

The latest version of xenial kernel, apparmor , lxd are now have the
fixes to run snap in lxd container. If it fail, please try to install
squashfuse or disable privileged mode.

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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

[Kernel-packages] [Bug 1579917] Re: Skylake processor never reaches low power states on X1 Carbon gen 4 with NVMe drive

2017-02-21 Thread Francois Thirioux

My Dell BIOS is up-to-date. The IMEI firmware is included in Dell's BIOS
updates, there is no separate package.
I'll try to check IMEI version anyway.

PS : I do use NVMe drive, before that my Skylake Xeon 1535M was eating
very few watts (~4.5W), now it's ~8.2W ; I don't know what to think
about that, NVMe missing APST for now or IMEI.

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

Title:
Skylake processor never reaches low power states on X1 Carbon gen 4
with NVMe drive

Status in linux package in Ubuntu:
Invalid

Bug description:
Reproducer
1. Find a skylake machine. - in my case Lenovo x1 carbon gen 4. In my case
with an NVME drive.
2. run powertop, and switch to idle stats tab
3. do nothing. *(as in let the machine idle till the cores regularly reach
low power states.
4. Watch the watts fly. On my machine the package never gets into any power
state other than PC2.

Expected results: PC3-PC10 power states should all show some usage.

I also tried the mainline build of 4.6-rc7 with no benefits.

Public conversations about the issue
https://mjg59.dreamwidth.org/42156.html
https://mjg59.dreamwidth.org/41713.html

As far as I can tell having the nvme drive is part of the overall
problem here. Please keep this case to skylake + nvme. Skylake +
sata appears to have a number of fixes in the 4.6 and newer kernels
that enable some of the higher sleep states, but I have not tested
with a sata drive. Those fixes as of testing 4.6-rc7 do not resolve
this issue with users who have nvme drives.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.39
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: chiluk 3139 F pulseaudio
CurrentDesktop: Unity
Date: Mon May 9 15:55:03 2016
HibernationDevice: RESUME=UUID=4f4ea88e-642e-4be5-bdf0-bbc7f47f5628
InstallationDate: Installed on 2016-04-25 (14 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f2:b531 Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FBCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed
root=UUID=249f91bb-7789-41cc-9cc0-8ba25d7f55bb ro quiet splash pcie_aspm=force
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-22-generic N/A
linux-backports-modules-4.4.0-22-generic N/A
linux-firmware1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET37W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FBCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN1FET37W(1.11):bd03/15/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20FBCTO1WW
dmi.product.version: ThinkPad X1 Carbon 4th
dmi.sys.vendor: LENOVO

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

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

1 2 3 >

1 - 100 of 228 matches

Mail list logo