date:20190128

[Kernel-packages] [Bug 1812189] Re: test_bpf in net from ubuntu_kernel_selftests failed on KVM / Cosmic kernels

2019-01-28 Thread Po-Hsu Lin

Found on Xenial s390x as well. (only on s390x, passed on other
architectures)

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

Title:
  test_bpf in net from ubuntu_kernel_selftests failed on KVM / Cosmic
  kernels

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  This test will attempt to insert the test_bpf module, but this module
  does not exist in KVM kernels:

  $ sudo modprobe test_bpf
  modprobe: FATAL: Module test_bpf not found in directory 
/lib/modules/4.15.0-1028-kvm

  The script:
  $ sudo ./test_bpf.sh 
  test_bpf: [FAIL]

  $ cat test_bpf.sh 
  #!/bin/sh
  # SPDX-License-Identifier: GPL-2.0
  # Runs bpf test using test_bpf kernel module

  if /sbin/modprobe -q test_bpf ; then
/sbin/modprobe -q -r test_bpf;
echo "test_bpf: ok";
  else
echo "test_bpf: [FAIL]";
exit 1;
  fi

  This test_bpf module will need the CONFIG_TEST_BPF to be enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 08:29:29 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812189/+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 1813721] [NEW] SECURITY_SELINUX_DISABLE should be enable on X s390x

2019-01-28 Thread Po-Hsu Lin

Public bug reported:

This test from q-r-t has failed exclusively on Xenial s390x:
  ==
  FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
  Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
  --
  Traceback (most recent call last):
File "./test-kernel-security.py", line 2158, in 
test_081_config_security_selinux_disable
  self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
  self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: SECURITY_SELINUX_DISABLE option was expected to be set in the 
kernel config
  
  --

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-142-generic 4.4.0-142.168
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
CurrentDmesg:
 
Date: Tue Jan 29 02:30:42 2019
HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
 
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 
crashkernel=196M
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-142-generic N/A
 linux-backports-modules-4.4.0-142-generic  N/A
 linux-firmware 1.157.21
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: apport-bug package-from-proposed s390x third-party-packages xenial

** Also affects: ubuntu-kernel-tests
   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/1813721

Title:
  SECURITY_SELINUX_DISABLE should be enable on X s390x

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This test from q-r-t has failed exclusively on Xenial s390x:
==
FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2158, in 
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
  File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: SECURITY_SELINUX_DISABLE option was expected to be set in 
the kernel config

--

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-142-generic 4.4.0-142.168
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Tue Jan 29 02:30:42 2019
  HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit

[Kernel-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10)

2019-01-28 Thread Ivan Grigoryev

This problem is detected immediately after installing the system. I
tried to install third-party drivers to fix the problem, but it did not
help. Now all removed

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

Title:
  [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic
  4.18.17 (but none observed in kernel 4.18.0-10)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  Экран всегда мигает с частотой 75 ГГц на графическом процессоре AMD RX 580. 
На частотах 60 и 50 ГГц, если вы переключитесь на любую другую, кроме 75, 
мерцание исчезнет, пока дисплей не выключится. После включения мерцание 
возвращается. На ядре 4.18.0-10 также как на gpu AMD Radeon HD7970 проблема не 
видна. Подробнее в видео 
  https: //www.youtube. ком / смотреть? v = d_LXHqWKTbk

  ProblemType: Bug 
  DistroRelease: Ubuntu 18.10 
  Пакет: xorg 1: 7.7 + 19ubuntu8 
  ProcVersionSign ature: Ubuntu 4.18.0-13.14 -generic 4.18.17 
  Uname: Linux 4.18.0-13-generic x86_64 
  ApportVersion: 2.20.10-0ubuntu13.1 
  Архитектура : amd64 
  BootLog: Ошибка: [Errno 13] Отказано в доступе: '/var/log/boot.log' 
  CompositorRunning: Нет 
  CurrentDesktop: ubuntu: GNOME 
  Дата: Вт 29 января 13:13:19 2019 
  DistUpgraded: Свежая установка 
  DistroCodename: космический 
  Вариант: Ubuntu 
  GraphicsCard: 
   Advanced Micro Devices, Inc. [AMD / ATI] Ellesmere [Radeon RX 470/480/570 / 
570X /580 / 580X] [1002: 67df] (версия e7) (prog-if 00 [VGA-контроллер]) 
     Подсистема: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570 / 570X 
/ 580 / 580X] [1043: 0519] 
  InstallationDate: Установлен в 2019-01-22 (6 дней назад). 
  InstallationMedia: Ubuntu 18.10 "Космическая каракатица" - выпуск amd64 
(20181017.3) Тип машины 
  : MSI MS-7693 
  ProcEnviron: 
   TERM = xterm- 256color 
   PATH = (пользовательский, нет пользователя) 
   XDG_RUNTIME_ DIR =  
   LANG = ru_RU.UTF-8 
   SHELL = / bin / bash 
  ProcKernelCmdLine: BOOT_IMAGE = / boot / vmlinuz- 4.18.0- 13-универсальный 
корень = UUID = ad22bc6d- c4e8-4393- a30b-6c247159b9dd ro quiet splash 
vt.handoff = 1 
  SourcePackage: xorg 
  Симптом: отображение 
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) 
  dmi.bios.date: 
  08.08.2016 dmi.bios.vendor: American Megatrends Inc. 
  dmi.bios . версия: V10.6 
  dmi.board. asset.tag: Заполняется OEM 
  dmi.board.name: 970A-G43 (MS-7693) 
  dmi.board.vendor: MSI 
  dmi.board.version: 3.0 
  dmi.chassis. asset.tag: Заполняется OEM 
  dmi.chassis.type: 3 
  dmi.chassis.vendor: MSI 
  dmi.chassis. версия: 3.0 
  dmi.modalias: dmi: bvnАмериканские MegatrendsInc. : bvrV10. 6: bd01 / 
08/2016: svnMSI:pnMS-7693: pvr3.0: rvnMSI: rn970A- G43 (MS- 7693): rvr3. 0: 
cvnMSI: ct3: cvr3. 0: 
  dmi.product.family: заполняется OEM 
  dmi.product.name: MS-7693 
  dmi.product.sku: заполняется OEM 
  dmi.product. версия: 3.0 
  dmi.sys.vendor: MSI 
  version.compiz: compiz Н / Д 
  version.libdrm2: libdrm2 2.4.97+ git1901221830. b7a7a9 ~ oibaf ~ c 
  версия. libgl1- mesa-dri: libgl1-mesa-dri 19.0 ~ git1901280 730.d1d2bb ~ 
oibaf ~ c 
  версия. libgl1- mesa-glx: libgl1-mesa-glx N / A 
  версия. xserver-xorg-core: xserver-xorg-core 2: 
  версия 1.20.1-3ubuntu2.1 . xserver- xorg-input- evdev: xserver- xorg-input- 
evdev N / A 
  версия. xserver- xorg-video- ati: версия xserver- xorg- video- ati 1: 
18.1.0-1 
  . xserver- xorg-video- intel: xserver- xorg-video- intel 2: 2.99. 917 + 
git20171229 -1ubuntu1 
  версия. xserver- xorg-video- nouveau: xserver- xorg-video- nouveau 1: 1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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 1813701] Re: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10)

2019-01-28 Thread Ivan Grigoryev

third-party PPA removed, packages updated

** Attachment added: "allpackages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1813701/+attachment/5233430/+files/allpackages.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/1813701

Title:
  [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic
  4.18.17 (but none observed in kernel 4.18.0-10)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  Экран всегда мигает с частотой 75 ГГц на графическом процессоре AMD RX 580. 
На частотах 60 и 50 ГГц, если вы переключитесь на любую другую, кроме 75, 
мерцание исчезнет, пока дисплей не выключится. После включения мерцание 
возвращается. На ядре 4.18.0-10 также как на gpu AMD Radeon HD7970 проблема не 
видна. Подробнее в видео 
  https: //www.youtube. ком / смотреть? v = d_LXHqWKTbk

  ProblemType: Bug 
  DistroRelease: Ubuntu 18.10 
  Пакет: xorg 1: 7.7 + 19ubuntu8 
  ProcVersionSign ature: Ubuntu 4.18.0-13.14 -generic 4.18.17 
  Uname: Linux 4.18.0-13-generic x86_64 
  ApportVersion: 2.20.10-0ubuntu13.1 
  Архитектура : amd64 
  BootLog: Ошибка: [Errno 13] Отказано в доступе: '/var/log/boot.log' 
  CompositorRunning: Нет 
  CurrentDesktop: ubuntu: GNOME 
  Дата: Вт 29 января 13:13:19 2019 
  DistUpgraded: Свежая установка 
  DistroCodename: космический 
  Вариант: Ubuntu 
  GraphicsCard: 
   Advanced Micro Devices, Inc. [AMD / ATI] Ellesmere [Radeon RX 470/480/570 / 
570X /580 / 580X] [1002: 67df] (версия e7) (prog-if 00 [VGA-контроллер]) 
     Подсистема: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570 / 570X 
/ 580 / 580X] [1043: 0519] 
  InstallationDate: Установлен в 2019-01-22 (6 дней назад). 
  InstallationMedia: Ubuntu 18.10 "Космическая каракатица" - выпуск amd64 
(20181017.3) Тип машины 
  : MSI MS-7693 
  ProcEnviron: 
   TERM = xterm- 256color 
   PATH = (пользовательский, нет пользователя) 
   XDG_RUNTIME_ DIR =  
   LANG = ru_RU.UTF-8 
   SHELL = / bin / bash 
  ProcKernelCmdLine: BOOT_IMAGE = / boot / vmlinuz- 4.18.0- 13-универсальный 
корень = UUID = ad22bc6d- c4e8-4393- a30b-6c247159b9dd ro quiet splash 
vt.handoff = 1 
  SourcePackage: xorg 
  Симптом: отображение 
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) 
  dmi.bios.date: 
  08.08.2016 dmi.bios.vendor: American Megatrends Inc. 
  dmi.bios . версия: V10.6 
  dmi.board. asset.tag: Заполняется OEM 
  dmi.board.name: 970A-G43 (MS-7693) 
  dmi.board.vendor: MSI 
  dmi.board.version: 3.0 
  dmi.chassis. asset.tag: Заполняется OEM 
  dmi.chassis.type: 3 
  dmi.chassis.vendor: MSI 
  dmi.chassis. версия: 3.0 
  dmi.modalias: dmi: bvnАмериканские MegatrendsInc. : bvrV10. 6: bd01 / 
08/2016: svnMSI:pnMS-7693: pvr3.0: rvnMSI: rn970A- G43 (MS- 7693): rvr3. 0: 
cvnMSI: ct3: cvr3. 0: 
  dmi.product.family: заполняется OEM 
  dmi.product.name: MS-7693 
  dmi.product.sku: заполняется OEM 
  dmi.product. версия: 3.0 
  dmi.sys.vendor: MSI 
  version.compiz: compiz Н / Д 
  version.libdrm2: libdrm2 2.4.97+ git1901221830. b7a7a9 ~ oibaf ~ c 
  версия. libgl1- mesa-dri: libgl1-mesa-dri 19.0 ~ git1901280 730.d1d2bb ~ 
oibaf ~ c 
  версия. libgl1- mesa-glx: libgl1-mesa-glx N / A 
  версия. xserver-xorg-core: xserver-xorg-core 2: 
  версия 1.20.1-3ubuntu2.1 . xserver- xorg-input- evdev: xserver- xorg-input- 
evdev N / A 
  версия. xserver- xorg-video- ati: версия xserver- xorg- video- ati 1: 
18.1.0-1 
  . xserver- xorg-video- intel: xserver- xorg-video- intel 2: 2.99. 917 + 
git20171229 -1ubuntu1 
  версия. xserver- xorg-video- nouveau: xserver- xorg-video- nouveau 1: 1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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 1811094] Re: iptables connlimit allows more connections than the limit when using multiple CPUs

2019-01-28 Thread Stefan Bader

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

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

** Changed in: linux (Ubuntu Trusty)
   Status: New => 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/1811094

Title:
  iptables connlimit allows more connections than the limit when using
  multiple CPUs

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

Bug description:
  [Impact]

   * The iptables connection count/limit rules can be breached
     with multithreaded network driver/server/client (common)
     due to a race in the conncount/connlimit code.

   * For example:

     # iptables -A INPUT -p tcp -m tcp --syn --dport  \
   -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
   -j DROP

   * The fix is a backport from an upstream commit that resolves
     the problem (plus dependencies for a cleaner backport) that
     address the race condition:

     commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
     collection confirm race").

  [Test Case]

   * Server-side: (relevant kernel side)
     (limit TCP port  to only 2000 connections)

     # iptables -A INPUT -p tcp -m tcp --syn --dport  \
   -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
   -j DROP

     # ulimit -SHn 65000   # increase number of open files
     # ruby server.rb  # multi-threaded server

   * Client-side:

     # ulimit -SHn 65000
     # ruby client.rb<# threads>
     

   * Results with Original kernel:
     (client achieves target of 6000 connections > limit of 2000 connections)

     # ruby client.rb 10.230.56.100  6000 3
     1
     2
     3
     <...>
     6000
     Target reached. Thread finishing
     6001
     Target reached. Thread finishing
     6002
     Target reached. Thread finishing
     Threads done. 6002 connections
     press enter to exit

   * Results with Modified kernel:
     (client is limited to 2000 connections, and times out afterward)

     # ruby client.rb 10.230.56.100  6000 3
     1
     2
     3
     <...>
     2000
     <... blocks for a few minutes ...>
     failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
     failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
     failed to create connection: Connection timed out - connect(2) for 
"10.230.56.100" port 
     Threads done. 2000 connections
     press enter to exit

   * Test cases possibly available upon request,
     depending on original author's permission.

  [Regression Potential]

   * The patchset has been reviewed by a netfilter maintainer [1] in
     stable mailing list, and was considered OK for 4.14, and that's
     essentially the same backport for 4.15 and 4.4.

   * The changes are limited to netfilter connlimit/conncount (names
     change between older/newer kernel versions).

  [Other Info]

   * The backport for 4.14 [2] is applied as of 4.14.92.

  [1] https://www.spinics.net/lists/stable/msg276883.html
  [2] https://www.spinics.net/lists/stable/msg276910.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811094/+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 1813701] Re: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10)

2019-01-28 Thread Daniel van Vugt

Yes, please remove both of those from your system and follow the steps
in comment #3. The drivers you installed seem to be causing problems so
we can't really see the original problem right now.

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

Title:
  [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic
  4.18.17 (but none observed in kernel 4.18.0-10)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  Экран всегда мигает с частотой 75 ГГц на графическом процессоре AMD RX 580. 
На частотах 60 и 50 ГГц, если вы переключитесь на любую другую, кроме 75, 
мерцание исчезнет, пока дисплей не выключится. После включения мерцание 
возвращается. На ядре 4.18.0-10 также как на gpu AMD Radeon HD7970 проблема не 
видна. Подробнее в видео 
  https: //www.youtube. ком / смотреть? v = d_LXHqWKTbk

  ProblemType: Bug 
  DistroRelease: Ubuntu 18.10 
  Пакет: xorg 1: 7.7 + 19ubuntu8 
  ProcVersionSign ature: Ubuntu 4.18.0-13.14 -generic 4.18.17 
  Uname: Linux 4.18.0-13-generic x86_64 
  ApportVersion: 2.20.10-0ubuntu13.1 
  Архитектура : amd64 
  BootLog: Ошибка: [Errno 13] Отказано в доступе: '/var/log/boot.log' 
  CompositorRunning: Нет 
  CurrentDesktop: ubuntu: GNOME 
  Дата: Вт 29 января 13:13:19 2019 
  DistUpgraded: Свежая установка 
  DistroCodename: космический 
  Вариант: Ubuntu 
  GraphicsCard: 
   Advanced Micro Devices, Inc. [AMD / ATI] Ellesmere [Radeon RX 470/480/570 / 
570X /580 / 580X] [1002: 67df] (версия e7) (prog-if 00 [VGA-контроллер]) 
     Подсистема: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570 / 570X 
/ 580 / 580X] [1043: 0519] 
  InstallationDate: Установлен в 2019-01-22 (6 дней назад). 
  InstallationMedia: Ubuntu 18.10 "Космическая каракатица" - выпуск amd64 
(20181017.3) Тип машины 
  : MSI MS-7693 
  ProcEnviron: 
   TERM = xterm- 256color 
   PATH = (пользовательский, нет пользователя) 
   XDG_RUNTIME_ DIR =  
   LANG = ru_RU.UTF-8 
   SHELL = / bin / bash 
  ProcKernelCmdLine: BOOT_IMAGE = / boot / vmlinuz- 4.18.0- 13-универсальный 
корень = UUID = ad22bc6d- c4e8-4393- a30b-6c247159b9dd ro quiet splash 
vt.handoff = 1 
  SourcePackage: xorg 
  Симптом: отображение 
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) 
  dmi.bios.date: 
  08.08.2016 dmi.bios.vendor: American Megatrends Inc. 
  dmi.bios . версия: V10.6 
  dmi.board. asset.tag: Заполняется OEM 
  dmi.board.name: 970A-G43 (MS-7693) 
  dmi.board.vendor: MSI 
  dmi.board.version: 3.0 
  dmi.chassis. asset.tag: Заполняется OEM 
  dmi.chassis.type: 3 
  dmi.chassis.vendor: MSI 
  dmi.chassis. версия: 3.0 
  dmi.modalias: dmi: bvnАмериканские MegatrendsInc. : bvrV10. 6: bd01 / 
08/2016: svnMSI:pnMS-7693: pvr3.0: rvnMSI: rn970A- G43 (MS- 7693): rvr3. 0: 
cvnMSI: ct3: cvr3. 0: 
  dmi.product.family: заполняется OEM 
  dmi.product.name: MS-7693 
  dmi.product.sku: заполняется OEM 
  dmi.product. версия: 3.0 
  dmi.sys.vendor: MSI 
  version.compiz: compiz Н / Д 
  version.libdrm2: libdrm2 2.4.97+ git1901221830. b7a7a9 ~ oibaf ~ c 
  версия. libgl1- mesa-dri: libgl1-mesa-dri 19.0 ~ git1901280 730.d1d2bb ~ 
oibaf ~ c 
  версия. libgl1- mesa-glx: libgl1-mesa-glx N / A 
  версия. xserver-xorg-core: xserver-xorg-core 2: 
  версия 1.20.1-3ubuntu2.1 . xserver- xorg-input- evdev: xserver- xorg-input- 
evdev N / A 
  версия. xserver- xorg-video- ati: версия xserver- xorg- video- ati 1: 
18.1.0-1 
  . xserver- xorg-video- intel: xserver- xorg-video- intel 2: 2.99. 917 + 
git20171229 -1ubuntu1 
  версия. xserver- xorg-video- nouveau: xserver- xorg-video- nouveau 1: 1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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 1813701] Re: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10)

2019-01-28 Thread Daniel van Vugt

The correct "free" drivers come built into Ubuntu automatically.

If you install unofficial drivers like
"https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers; then we
cannot help 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/1813701

Title:
  [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic
  4.18.17 (but none observed in kernel 4.18.0-10)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  Экран всегда мигает с частотой 75 ГГц на графическом процессоре AMD RX 580. 
На частотах 60 и 50 ГГц, если вы переключитесь на любую другую, кроме 75, 
мерцание исчезнет, пока дисплей не выключится. После включения мерцание 
возвращается. На ядре 4.18.0-10 также как на gpu AMD Radeon HD7970 проблема не 
видна. Подробнее в видео 
  https: //www.youtube. ком / смотреть? v = d_LXHqWKTbk

  ProblemType: Bug 
  DistroRelease: Ubuntu 18.10 
  Пакет: xorg 1: 7.7 + 19ubuntu8 
  ProcVersionSign ature: Ubuntu 4.18.0-13.14 -generic 4.18.17 
  Uname: Linux 4.18.0-13-generic x86_64 
  ApportVersion: 2.20.10-0ubuntu13.1 
  Архитектура : amd64 
  BootLog: Ошибка: [Errno 13] Отказано в доступе: '/var/log/boot.log' 
  CompositorRunning: Нет 
  CurrentDesktop: ubuntu: GNOME 
  Дата: Вт 29 января 13:13:19 2019 
  DistUpgraded: Свежая установка 
  DistroCodename: космический 
  Вариант: Ubuntu 
  GraphicsCard: 
   Advanced Micro Devices, Inc. [AMD / ATI] Ellesmere [Radeon RX 470/480/570 / 
570X /580 / 580X] [1002: 67df] (версия e7) (prog-if 00 [VGA-контроллер]) 
     Подсистема: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570 / 570X 
/ 580 / 580X] [1043: 0519] 
  InstallationDate: Установлен в 2019-01-22 (6 дней назад). 
  InstallationMedia: Ubuntu 18.10 "Космическая каракатица" - выпуск amd64 
(20181017.3) Тип машины 
  : MSI MS-7693 
  ProcEnviron: 
   TERM = xterm- 256color 
   PATH = (пользовательский, нет пользователя) 
   XDG_RUNTIME_ DIR =  
   LANG = ru_RU.UTF-8 
   SHELL = / bin / bash 
  ProcKernelCmdLine: BOOT_IMAGE = / boot / vmlinuz- 4.18.0- 13-универсальный 
корень = UUID = ad22bc6d- c4e8-4393- a30b-6c247159b9dd ro quiet splash 
vt.handoff = 1 
  SourcePackage: xorg 
  Симптом: отображение 
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) 
  dmi.bios.date: 
  08.08.2016 dmi.bios.vendor: American Megatrends Inc. 
  dmi.bios . версия: V10.6 
  dmi.board. asset.tag: Заполняется OEM 
  dmi.board.name: 970A-G43 (MS-7693) 
  dmi.board.vendor: MSI 
  dmi.board.version: 3.0 
  dmi.chassis. asset.tag: Заполняется OEM 
  dmi.chassis.type: 3 
  dmi.chassis.vendor: MSI 
  dmi.chassis. версия: 3.0 
  dmi.modalias: dmi: bvnАмериканские MegatrendsInc. : bvrV10. 6: bd01 / 
08/2016: svnMSI:pnMS-7693: pvr3.0: rvnMSI: rn970A- G43 (MS- 7693): rvr3. 0: 
cvnMSI: ct3: cvr3. 0: 
  dmi.product.family: заполняется OEM 
  dmi.product.name: MS-7693 
  dmi.product.sku: заполняется OEM 
  dmi.product. версия: 3.0 
  dmi.sys.vendor: MSI 
  version.compiz: compiz Н / Д 
  version.libdrm2: libdrm2 2.4.97+ git1901221830. b7a7a9 ~ oibaf ~ c 
  версия. libgl1- mesa-dri: libgl1-mesa-dri 19.0 ~ git1901280 730.d1d2bb ~ 
oibaf ~ c 
  версия. libgl1- mesa-glx: libgl1-mesa-glx N / A 
  версия. xserver-xorg-core: xserver-xorg-core 2: 
  версия 1.20.1-3ubuntu2.1 . xserver- xorg-input- evdev: xserver- xorg-input- 
evdev N / A 
  версия. xserver- xorg-video- ati: версия xserver- xorg- video- ati 1: 
18.1.0-1 
  . xserver- xorg-video- intel: xserver- xorg-video- intel 2: 2.99. 917 + 
git20171229 -1ubuntu1 
  версия. xserver- xorg-video- nouveau: xserver- xorg-video- nouveau 1: 1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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 1813701] Re: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10)

2019-01-28 Thread Ivan Grigoryev

To get rid of the problem, I tried to install the amdgpu-pro driver
18.50, but it is supported only in ubuntu 18.04. Then I installed the
free driver https://launchpad.net/~oibaf/+archive/ubuntu/graphics-
drivers. but unfortunately the problem is not solved.

** Description changed:

- The screen flickers always at a frequency of 75 GHz on GPU AMD RX 580. At 
frequencies of 60 and 50 GHz, if you change to any other except 75, the flicker 
disappears until the display is turned off. After switching on, flicker 
returns. On kernel 4.18.0-10 also as on gpu AMD HD7970 the problem is not seen. 
More in the video
- https://www.youtube.com/watch?v=d_LXHqWKTbk
+ Экран всегда мигает с частотой 75 ГГц на графическом процессоре AMD RX 580. 
На частотах 60 и 50 ГГц, если вы переключитесь на любую другую, кроме 75, 
мерцание исчезнет, пока дисплей не выключится. После включения мерцание 
возвращается. На ядре 4.18.0-10 также как на gpu AMD Radeon HD7970 проблема не 
видна. Подробнее в видео 
+ https: //www.youtube. ком / смотреть? v = d_LXHqWKTbk
  
- ProblemType: Bug
- DistroRelease: Ubuntu 18.10
- Package: xorg 1:7.7+19ubuntu8
- ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
- Uname: Linux 4.18.0-13-generic x86_64
- ApportVersion: 2.20.10-0ubuntu13.1
- Architecture: amd64
- BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
- CompositorRunning: None
- CurrentDesktop: ubuntu:GNOME
- Date: Tue Jan 29 13:13:19 2019
- DistUpgraded: Fresh install
- DistroCodename: cosmic
- DistroVariant: ubuntu
- GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
-    Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0519]
- InstallationDate: Installed on 2019-01-22 (6 days ago)
- InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
- MachineType: MSI MS-7693
- ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1
- SourcePackage: xorg
- Symptom: display
- UpgradeStatus: No upgrade log present (probably fresh install)
- dmi.bios.date: 01/08/2016
- dmi.bios.vendor: American Megatrends Inc.
- dmi.bios.version: V10.6
- dmi.board.asset.tag: To be filled by O.E.M.
- dmi.board.name: 970A-G43 (MS-7693)
- dmi.board.vendor: MSI
- dmi.board.version: 3.0
- dmi.chassis.asset.tag: To Be Filled By O.E.M.
- dmi.chassis.type: 3
- dmi.chassis.vendor: MSI
- dmi.chassis.version: 3.0
- dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0:
- dmi.product.family: To be filled by O.E.M.
- dmi.product.name: MS-7693
- dmi.product.sku: To be filled by O.E.M.
- dmi.product.version: 3.0
- dmi.sys.vendor: MSI
- version.compiz: compiz N/A
- version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c
- version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c
- version.libgl1-mesa-glx: libgl1-mesa-glx N/A
- version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
- version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
- version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
- version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
- version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
+ ProblemType: Bug 
+ DistroRelease: Ubuntu 18.10 
+ Пакет: xorg 1: 7.7 + 19ubuntu8 
+ ProcVersionSign ature: Ubuntu 4.18.0-13.14 -generic 4.18.17 
+ Uname: Linux 4.18.0-13-generic x86_64 
+ ApportVersion: 2.20.10-0ubuntu13.1 
+ Архитектура : amd64 
+ BootLog: Ошибка: [Errno 13] Отказано в доступе: '/var/log/boot.log' 
+ CompositorRunning: Нет 
+ CurrentDesktop: ubuntu: GNOME 
+ Дата: Вт 29 января 13:13:19 2019 
+ DistUpgraded: Свежая установка 
+ DistroCodename: космический 
+ Вариант: Ubuntu 
+ GraphicsCard: 
+  Advanced Micro Devices, Inc. [AMD / ATI] Ellesmere [Radeon RX 470/480/570 / 
570X /580 / 580X] [1002: 67df] (версия e7) (prog-if 00 [VGA-контроллер]) 
+    Подсистема: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570 / 570X 
/ 580 / 580X] [1043: 0519] 
+ InstallationDate: Установлен в 2019-01-22 (6 дней назад). 
+ InstallationMedia: Ubuntu 18.10 "Космическая каракатица" - выпуск amd64 
(20181017.3) Тип машины 
+ : MSI MS-7693 
+ ProcEnviron: 
+  TERM = xterm- 256color 
+  PATH = (пользовательский, нет пользователя) 
+  XDG_RUNTIME_ DIR =  
+  LANG = ru_RU.UTF-8 
+  SHELL = / bin / bash 
+ ProcKernelCmdLine: BOOT_IMAGE = / boot / vmlinuz- 4.18.0- 13-универсальный 
корень = UUID = ad22bc6d- c4e8-4393- a30b-6c247159b9dd ro quiet splash 
vt.handoff = 1 
+ SourcePackage: xorg 
+ Симптом: отображение 
+ UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) 
+

[Kernel-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10)

2019-01-28 Thread Daniel van Vugt

Oh, it appears you have at least one unsupported PPA installed that has
replaced some graphics packages:

version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c

Please:

1. Remove that PPA from the system using 'ppa-purge'.

2. Reboot.

3. If the problem still occurs then run:

   dpkg -l > allpackages,txt

   and send us the file 'allpackages.txt'.


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

** Changed in: xserver-xorg-video-amdgpu (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/1813701

Title:
  [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic
  4.18.17 (but none observed in kernel 4.18.0-10)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  Экран всегда мигает с частотой 75 ГГц на графическом процессоре AMD RX 580. 
На частотах 60 и 50 ГГц, если вы переключитесь на любую другую, кроме 75, 
мерцание исчезнет, пока дисплей не выключится. После включения мерцание 
возвращается. На ядре 4.18.0-10 также как на gpu AMD Radeon HD7970 проблема не 
видна. Подробнее в видео 
  https: //www.youtube. ком / смотреть? v = d_LXHqWKTbk

  ProblemType: Bug 
  DistroRelease: Ubuntu 18.10 
  Пакет: xorg 1: 7.7 + 19ubuntu8 
  ProcVersionSign ature: Ubuntu 4.18.0-13.14 -generic 4.18.17 
  Uname: Linux 4.18.0-13-generic x86_64 
  ApportVersion: 2.20.10-0ubuntu13.1 
  Архитектура : amd64 
  BootLog: Ошибка: [Errno 13] Отказано в доступе: '/var/log/boot.log' 
  CompositorRunning: Нет 
  CurrentDesktop: ubuntu: GNOME 
  Дата: Вт 29 января 13:13:19 2019 
  DistUpgraded: Свежая установка 
  DistroCodename: космический 
  Вариант: Ubuntu 
  GraphicsCard: 
   Advanced Micro Devices, Inc. [AMD / ATI] Ellesmere [Radeon RX 470/480/570 / 
570X /580 / 580X] [1002: 67df] (версия e7) (prog-if 00 [VGA-контроллер]) 
     Подсистема: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570 / 570X 
/ 580 / 580X] [1043: 0519] 
  InstallationDate: Установлен в 2019-01-22 (6 дней назад). 
  InstallationMedia: Ubuntu 18.10 "Космическая каракатица" - выпуск amd64 
(20181017.3) Тип машины 
  : MSI MS-7693 
  ProcEnviron: 
   TERM = xterm- 256color 
   PATH = (пользовательский, нет пользователя) 
   XDG_RUNTIME_ DIR =  
   LANG = ru_RU.UTF-8 
   SHELL = / bin / bash 
  ProcKernelCmdLine: BOOT_IMAGE = / boot / vmlinuz- 4.18.0- 13-универсальный 
корень = UUID = ad22bc6d- c4e8-4393- a30b-6c247159b9dd ro quiet splash 
vt.handoff = 1 
  SourcePackage: xorg 
  Симптом: отображение 
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) 
  dmi.bios.date: 
  08.08.2016 dmi.bios.vendor: American Megatrends Inc. 
  dmi.bios . версия: V10.6 
  dmi.board. asset.tag: Заполняется OEM 
  dmi.board.name: 970A-G43 (MS-7693) 
  dmi.board.vendor: MSI 
  dmi.board.version: 3.0 
  dmi.chassis. asset.tag: Заполняется OEM 
  dmi.chassis.type: 3 
  dmi.chassis.vendor: MSI 
  dmi.chassis. версия: 3.0 
  dmi.modalias: dmi: bvnАмериканские MegatrendsInc. : bvrV10. 6: bd01 / 
08/2016: svnMSI:pnMS-7693: pvr3.0: rvnMSI: rn970A- G43 (MS- 7693): rvr3. 0: 
cvnMSI: ct3: cvr3. 0: 
  dmi.product.family: заполняется OEM 
  dmi.product.name: MS-7693 
  dmi.product.sku: заполняется OEM 
  dmi.product. версия: 3.0 
  dmi.sys.vendor: MSI 
  version.compiz: compiz Н / Д 
  version.libdrm2: libdrm2 2.4.97+ git1901221830. b7a7a9 ~ oibaf ~ c 
  версия. libgl1- mesa-dri: libgl1-mesa-dri 19.0 ~ git1901280 730.d1d2bb ~ 
oibaf ~ c 
  версия. libgl1- mesa-glx: libgl1-mesa-glx N / A 
  версия. xserver-xorg-core: xserver-xorg-core 2: 
  версия 1.20.1-3ubuntu2.1 . xserver- xorg-input- evdev: xserver- xorg-input- 
evdev N / A 
  версия. xserver- xorg-video- ati: версия xserver- xorg- video- ati 1: 
18.1.0-1 
  . xserver- xorg-video- intel: xserver- xorg-video- intel 2: 2.99. 917 + 
git20171229 -1ubuntu1 
  версия. xserver- xorg-video- nouveau: xserver- xorg-video- nouveau 1: 1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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 1813701] Re: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10)

2019-01-28 Thread Daniel van Vugt

It looks like a problem with the Xorg graphics driver:

[44.332] (EE) amdgpu: module ABI major version (23) doesn't match the 
server's version (24)
[44.332] (EE) Failed to load module "amdgpu" (module requirement mismatch, 
0)

so your system then falls back to using the 'modeset' Xorg driver with
the 'amdgpu' kernel driver.

** Tags added: amdgpu

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

Title:
  [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic
  4.18.17 (but none observed in kernel 4.18.0-10)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  Экран всегда мигает с частотой 75 ГГц на графическом процессоре AMD RX 580. 
На частотах 60 и 50 ГГц, если вы переключитесь на любую другую, кроме 75, 
мерцание исчезнет, пока дисплей не выключится. После включения мерцание 
возвращается. На ядре 4.18.0-10 также как на gpu AMD Radeon HD7970 проблема не 
видна. Подробнее в видео 
  https: //www.youtube. ком / смотреть? v = d_LXHqWKTbk

  ProblemType: Bug 
  DistroRelease: Ubuntu 18.10 
  Пакет: xorg 1: 7.7 + 19ubuntu8 
  ProcVersionSign ature: Ubuntu 4.18.0-13.14 -generic 4.18.17 
  Uname: Linux 4.18.0-13-generic x86_64 
  ApportVersion: 2.20.10-0ubuntu13.1 
  Архитектура : amd64 
  BootLog: Ошибка: [Errno 13] Отказано в доступе: '/var/log/boot.log' 
  CompositorRunning: Нет 
  CurrentDesktop: ubuntu: GNOME 
  Дата: Вт 29 января 13:13:19 2019 
  DistUpgraded: Свежая установка 
  DistroCodename: космический 
  Вариант: Ubuntu 
  GraphicsCard: 
   Advanced Micro Devices, Inc. [AMD / ATI] Ellesmere [Radeon RX 470/480/570 / 
570X /580 / 580X] [1002: 67df] (версия e7) (prog-if 00 [VGA-контроллер]) 
     Подсистема: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570 / 570X 
/ 580 / 580X] [1043: 0519] 
  InstallationDate: Установлен в 2019-01-22 (6 дней назад). 
  InstallationMedia: Ubuntu 18.10 "Космическая каракатица" - выпуск amd64 
(20181017.3) Тип машины 
  : MSI MS-7693 
  ProcEnviron: 
   TERM = xterm- 256color 
   PATH = (пользовательский, нет пользователя) 
   XDG_RUNTIME_ DIR =  
   LANG = ru_RU.UTF-8 
   SHELL = / bin / bash 
  ProcKernelCmdLine: BOOT_IMAGE = / boot / vmlinuz- 4.18.0- 13-универсальный 
корень = UUID = ad22bc6d- c4e8-4393- a30b-6c247159b9dd ro quiet splash 
vt.handoff = 1 
  SourcePackage: xorg 
  Симптом: отображение 
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) 
  dmi.bios.date: 
  08.08.2016 dmi.bios.vendor: American Megatrends Inc. 
  dmi.bios . версия: V10.6 
  dmi.board. asset.tag: Заполняется OEM 
  dmi.board.name: 970A-G43 (MS-7693) 
  dmi.board.vendor: MSI 
  dmi.board.version: 3.0 
  dmi.chassis. asset.tag: Заполняется OEM 
  dmi.chassis.type: 3 
  dmi.chassis.vendor: MSI 
  dmi.chassis. версия: 3.0 
  dmi.modalias: dmi: bvnАмериканские MegatrendsInc. : bvrV10. 6: bd01 / 
08/2016: svnMSI:pnMS-7693: pvr3.0: rvnMSI: rn970A- G43 (MS- 7693): rvr3. 0: 
cvnMSI: ct3: cvr3. 0: 
  dmi.product.family: заполняется OEM 
  dmi.product.name: MS-7693 
  dmi.product.sku: заполняется OEM 
  dmi.product. версия: 3.0 
  dmi.sys.vendor: MSI 
  version.compiz: compiz Н / Д 
  version.libdrm2: libdrm2 2.4.97+ git1901221830. b7a7a9 ~ oibaf ~ c 
  версия. libgl1- mesa-dri: libgl1-mesa-dri 19.0 ~ git1901280 730.d1d2bb ~ 
oibaf ~ c 
  версия. libgl1- mesa-glx: libgl1-mesa-glx N / A 
  версия. xserver-xorg-core: xserver-xorg-core 2: 
  версия 1.20.1-3ubuntu2.1 . xserver- xorg-input- evdev: xserver- xorg-input- 
evdev N / A 
  версия. xserver- xorg-video- ati: версия xserver- xorg- video- ati 1: 
18.1.0-1 
  . xserver- xorg-video- intel: xserver- xorg-video- intel 2: 2.99. 917 + 
git20171229 -1ubuntu1 
  версия. xserver- xorg-video- nouveau: xserver- xorg-video- nouveau 1: 1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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 1813701] Re: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10)

2019-01-28 Thread Daniel van Vugt

** Summary changed:

- the screen flickers. Ubuntu 18 + AMD RX580
+ [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 
4.18.17 (but none observed in kernel 4.18.0-10)

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Also 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/1813701

Title:
  [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic
  4.18.17 (but none observed in kernel 4.18.0-10)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  Экран всегда мигает с частотой 75 ГГц на графическом процессоре AMD RX 580. 
На частотах 60 и 50 ГГц, если вы переключитесь на любую другую, кроме 75, 
мерцание исчезнет, пока дисплей не выключится. После включения мерцание 
возвращается. На ядре 4.18.0-10 также как на gpu AMD Radeon HD7970 проблема не 
видна. Подробнее в видео 
  https: //www.youtube. ком / смотреть? v = d_LXHqWKTbk

  ProblemType: Bug 
  DistroRelease: Ubuntu 18.10 
  Пакет: xorg 1: 7.7 + 19ubuntu8 
  ProcVersionSign ature: Ubuntu 4.18.0-13.14 -generic 4.18.17 
  Uname: Linux 4.18.0-13-generic x86_64 
  ApportVersion: 2.20.10-0ubuntu13.1 
  Архитектура : amd64 
  BootLog: Ошибка: [Errno 13] Отказано в доступе: '/var/log/boot.log' 
  CompositorRunning: Нет 
  CurrentDesktop: ubuntu: GNOME 
  Дата: Вт 29 января 13:13:19 2019 
  DistUpgraded: Свежая установка 
  DistroCodename: космический 
  Вариант: Ubuntu 
  GraphicsCard: 
   Advanced Micro Devices, Inc. [AMD / ATI] Ellesmere [Radeon RX 470/480/570 / 
570X /580 / 580X] [1002: 67df] (версия e7) (prog-if 00 [VGA-контроллер]) 
     Подсистема: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570 / 570X 
/ 580 / 580X] [1043: 0519] 
  InstallationDate: Установлен в 2019-01-22 (6 дней назад). 
  InstallationMedia: Ubuntu 18.10 "Космическая каракатица" - выпуск amd64 
(20181017.3) Тип машины 
  : MSI MS-7693 
  ProcEnviron: 
   TERM = xterm- 256color 
   PATH = (пользовательский, нет пользователя) 
   XDG_RUNTIME_ DIR =  
   LANG = ru_RU.UTF-8 
   SHELL = / bin / bash 
  ProcKernelCmdLine: BOOT_IMAGE = / boot / vmlinuz- 4.18.0- 13-универсальный 
корень = UUID = ad22bc6d- c4e8-4393- a30b-6c247159b9dd ro quiet splash 
vt.handoff = 1 
  SourcePackage: xorg 
  Симптом: отображение 
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) 
  dmi.bios.date: 
  08.08.2016 dmi.bios.vendor: American Megatrends Inc. 
  dmi.bios . версия: V10.6 
  dmi.board. asset.tag: Заполняется OEM 
  dmi.board.name: 970A-G43 (MS-7693) 
  dmi.board.vendor: MSI 
  dmi.board.version: 3.0 
  dmi.chassis. asset.tag: Заполняется OEM 
  dmi.chassis.type: 3 
  dmi.chassis.vendor: MSI 
  dmi.chassis. версия: 3.0 
  dmi.modalias: dmi: bvnАмериканские MegatrendsInc. : bvrV10. 6: bd01 / 
08/2016: svnMSI:pnMS-7693: pvr3.0: rvnMSI: rn970A- G43 (MS- 7693): rvr3. 0: 
cvnMSI: ct3: cvr3. 0: 
  dmi.product.family: заполняется OEM 
  dmi.product.name: MS-7693 
  dmi.product.sku: заполняется OEM 
  dmi.product. версия: 3.0 
  dmi.sys.vendor: MSI 
  version.compiz: compiz Н / Д 
  version.libdrm2: libdrm2 2.4.97+ git1901221830. b7a7a9 ~ oibaf ~ c 
  версия. libgl1- mesa-dri: libgl1-mesa-dri 19.0 ~ git1901280 730.d1d2bb ~ 
oibaf ~ c 
  версия. libgl1- mesa-glx: libgl1-mesa-glx N / A 
  версия. xserver-xorg-core: xserver-xorg-core 2: 
  версия 1.20.1-3ubuntu2.1 . xserver- xorg-input- evdev: xserver- xorg-input- 
evdev N / A 
  версия. xserver- xorg-video- ati: версия xserver- xorg- video- ati 1: 
18.1.0-1 
  . xserver- xorg-video- intel: xserver- xorg-video- intel 2: 2.99. 917 + 
git20171229 -1ubuntu1 
  версия. xserver- xorg-video- nouveau: xserver- xorg-video- nouveau 1: 1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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 1680349] Re: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng.

2019-01-28 Thread bugproxy

** Tags removed: targetmilestone-inin1704
** 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/1680349

Title:
  Kdump fails to capture dump on Firestone NV when machine crashes while
  running stress-ng.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-03-10 02:43:10 ==
  ---Problem Description---

  Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine
  crashes while running stress-ng. Machine hangs.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Install stress-ng
  # apt-get install stress-ng
  3. Run stress-ng
  # stress-ng - a 0

  
  Logs:
  
  root@ltc-firep3:~# kdump-config load
  Modified cmdline:root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet 
splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0 elfcorehdr=155200K 
   * loaded kdump kernel
  root@ltc-firep3:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.10.0-11-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.10.0-11-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash 
irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz
  root@ltc-firep3:~# stress-ng -a 0
  stress-ng: info:  [3900] defaulting to a 86400 second run per stressor
  stress-ng: info:  [3900] dispatching hogs: 160 af-alg, 160 affinity, 160 aio, 
160 aiol, 160 apparmor, 160 atomic, 160 bigheap, 160 brk, 160 bsearch, 160 
cache, 160 cap, 160 chdir, 160 chmod, 160 chown, 160 chroot, 160 clock, 160 
clone, 160 context, 160 copy-file, 160 cpu, 160 cpu-online, 160 crypt, 160 
daemon, 160 dccp, 160 dentry, 160 dir, 160 dirdeep, 160 dnotify, 160 dup, 160 
epoll, 160 eventfd, 160 exec, 160 fallocate, 160 fanotify, 160 fault, 160 
fcntl, 160 fiemap, 160 fifo, 160 filename, 160 flock, 160 fork, 160 fp-error, 
160 fstat, 160 full, 160 futex, 160 get, 160 getdent, 160 getrandom, 160 
handle, 160 hdd, 160 heapsort, 160 hsearch, 160 icache, 160 icmp-flood, 160 
inotify, 160 io, 160 iomix, 160 ioprio, 160 itimer, 160 kcmp, 160 key, 160 
kill, 160 klog, 160 lease, 160 link, 160 locka, 160 lockbus, 160 lockf, 160 
lockofd, 160 longjmp, 160 lsearch, 160 madvise, 160 malloc, 160 matrix, 160 
membarrier, 160 memcpy, 160 memfd, 160 mergesort, 160 mincore, 160 mknod, 160 
mlock, 160 mmap, 160 mmapfork, 160 mmapmany, 160 mq, 160 mremap, 160 msg, 160 
msync, 160 netlink-proc, 160 nice, 160 nop, 160 null, 160 numa, 160 oom-pipe, 
160 opcode, 160 open, 160 personality, 160 pipe, 160 poll, 160 procfs, 160 
pthread, 160 ptrace, 160 pty, 160 qsort, 160 quota, 160 rdrand, 160 readahead, 
160 remap, 160 rename, 160 resources, 160 rlimit, 160 rmap, 160 rtc, 160 
schedpolicy, 160 sctp, 160 seal, 160 seccomp, 160 seek, 160 sem, 160 sem-sysv, 
160 sendfile, 160 shm, 160 shm-sysv, 160 sigfd, 160 sigfpe, 160 sigpending, 160 
sigq, 160 sigsegv, 160 sigsuspend, 160 sleep, 160 sock, 160 sockfd, 160 
sockpair, 160 spawn, 160 splice, 160 stack, 160 stackmmap, 160 str, 160 stream, 
160 switch, 160 symlink, 160 sync-file, 160 sysfs, 160 sysinfo, 160 tee, 160 
timer, 160 timerfd, 160 tlb-shootdown, 160 tmpfs, 160 tsc, 160 tsearch, 160 
udp, 160 udp-flood, 160 unshare, 160 urandom, 160 userfaultfd, 160 utime, 160 
vecmath, 160 vfork, 160 vforkmany, 160 vm, 160 vm-rw, 160 vm-splice, 160 wait, 
160 wcs, 160 xattr, 160 yield, 160 zero, 160 zlib, 160 zombie
  stress-ng: info:  [3900] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [3900] cache allocate: default cache size: 2048K
  stress-ng: info:  [3907] stress-ng-atomic: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [3955] stress-ng-exec: running as root, won't run test.
  stress-ng: info:  [3999] stress-ng-icache: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4040] stress-ng-lockbus: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4313] stress-ng-numa: system has 2 of a maximum 256 memory 
NUMA nodes
  stress-ng: info:  [4455] stress-ng-rdrand: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: fail:  [4558] stress-ng-rtc: ioctl RTC_ALRM_READ failed, errno=22 
(Invalid argument)
  stress-ng: fail:  [4017] stress-ng-key: keyctl KEYCTL_DESCRIBE failed,

[Kernel-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10)

2019-01-28 Thread Ivan Grigoryev

** Description changed:

- the screen flickers always at a frequency of 75 GHz. At frequencies of 60 and 
50 GHz, if you change to any other except 75, the flicker disappears until the 
display is turned off. After switching on, flicker returns. on kernel 
4.18.0-10, the problem is not seen. more in the video
+ The screen flickers always at a frequency of 75 GHz on GPU AMD RX 580. At 
frequencies of 60 and 50 GHz, if you change to any other except 75, the flicker 
disappears until the display is turned off. After switching on, flicker 
returns. On kernel 4.18.0-10 also as on gpu AMD HD7970 the problem is not seen. 
More in the video
  https://www.youtube.com/watch?v=d_LXHqWKTbk
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 13:13:19 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0519]
  InstallationDate: Installed on 2019-01-22 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: MSI MS-7693
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G43 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7693
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

Title:
  [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic
  4.18.17 (but none observed in kernel 4.18.0-10)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  Экран всегда мигает с частотой 75 ГГц на графическом процессоре AMD RX 580. 
На частотах 60 и 50 ГГц, если вы переключитесь на любую другую, кроме 75, 
мерцание исчезнет, пока дисплей не выключится. После включения мерцание 
возвращается. На ядре 4.18.0-10 также как на gpu AMD Radeon HD7970 проблема не 
видна. Подробнее в видео 
  https: //www.youtube. ком / смотреть? v = d_LXHqWKTbk

  ProblemType: Bug 
  DistroRelease: Ubuntu 18.10 
  Пакет: xorg 1: 7.7 + 19ubuntu8 
  ProcVersionSign ature: Ubuntu 4.18.0-13.14 -generic 4.18.17 
  Uname: Linux 4.18.0-13-generic x86_64 
  ApportVersion: 2.20.10-0ubuntu13.1 
  Архитектура : amd64 
  BootLog: Ошибка: [Errno 13] Отказано в доступе: '/var/log/boot.log' 
  CompositorRunning: Нет 
  CurrentDesktop: ubuntu: GNOME 
  Дата: Вт 29 января 13:13:19 2019 
  DistUpgraded: Свежая установка 
  DistroCodename: космический 
  Вариант: Ubuntu 
  GraphicsCard: 
   Advanced Micro Devices, Inc. [AMD / ATI] Ellesmere [Radeon RX 470/480/570 / 
570X /580 / 580X] [1002: 67df] (версия e7) (prog-if 00 [VGA-контроллер]) 
     Подсистема: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570 / 570X 
/ 580 / 580X] [1043: 0519] 
  InstallationDate: Установлен в 2019-01-22 (6 дней назад). 
  InstallationMedia: Ubuntu 18.10 "Космическая каракатица" - выпуск amd64 
(20181017.3) Тип машины 
  : MSI MS-7693

[Kernel-packages] [Bug 1813532] Re: x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a0000

2019-01-28 Thread Khaled El Mously

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

Title:
  x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New

Bug description:
  == SRU Justification ==

  Booting an i386 Bionic kernel in a VM with a 64-bit CPU leads to:

  [1.074702] Freeing unused kernel memory: 1092K
  [1.084027] Write protecting the kernel text: 8836k
  [1.085115] Write protecting the kernel read-only data: 3480k
  [1.086361] NX-protecting the kernel data: 7548k
  [1.087457] [ cut here ]
  [1.088400] x86/mm: Found insecure W+X mapping at address 
(ptrval)/0xc00a
  [1.089738] WARNING: CPU: 0 PID: 1 at 
/build/linux-bnzN1b/linux-4.15.0/arch/x86/mm/dump_pagetables.c:266 
note_page+0x670/0x860
  [1.091893] Modules linked in:
  [1.092522] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-43-generic 
#46-Ubuntu
  [1.094362] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.11.1-1ubuntu1 04/01/2014
  [1.096279] EIP: note_page+0x670/0x860
  [1.097012] EFLAGS: 00010282 CPU: 0
  [1.097807] EAX: 0041 EBX: df4fbf44 ECX: 01ba EDX: 
  [1.099083] ESI: 8000 EDI:  EBP: df4fbf10 ESP: df4fbee4
  [1.100328]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [1.101418] CR0: 80050033 CR2: b7d99092 CR3: 0ce16000 CR4: 06f0
  [1.102693] DR0:  DR1:  DR2:  DR3: 
  [1.103928] DR6: fffe0ff0 DR7: 0400
  [1.104733] Call Trace:
  [1.105316]  ptdump_walk_pgd_level_core+0x2ac/0x2e0
  [1.106266]  ptdump_walk_pgd_level_checkwx+0x18/0x20
  [1.107207]  mark_rodata_ro+0xf5/0x117
  [1.107947]  ? rest_init+0xa0/0xa0
  [1.108627]  kernel_init+0x33/0xf0
  [1.109300]  ret_from_fork+0x2e/0x38
  [1.110016] Code: cc e9 0c fb ff ff f7 c6 00 10 00 00 74 8c 68 fe ae ae cc 
e9 16 fe ff ff 52 52 68 ac af ae cc c6 05 a8 a8 cb cc 01 e8 40 74 00 00 <0f> 0b 
8b 53 0c 83 c4 0c e9 38 fa ff ff 50 6a 08 52 6a 08 68 ae
  [1.113395] ---[ end trace 0dce1996d96c40bb ]---
  [1.114324] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found.

  
  == Fix ==

  Backport commit c200dac78fec ("x86/mm: Do not warn about PCI BIOS W+X
  mappings").

  
  == Regression Potential ==

  Low. The patch only modifies debugging output.

  
  == Test Case ==

  To reproduce, boot an i386 kernel in QEMU with '-cpu qemu64' and check
  the kernel logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813532/+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 1811093] Re: Bogus "Out of Memory" compiz invoked oom-killer

2019-01-28 Thread Craig

No oom-killer event with v5.0 kernel.
Linux version 5.0.0-05rc1-generic (kernel@tangerine) (gcc version 8.2.0
(Ubuntu 8.2.0-12ubuntu1)) #201901062130 SMP Mon Jan 7 02:32:47 UTC 2019

Possible explanations:

Scenario #1) There was a kernel bug and it is fixed in v5.0. Or,

Scenario #2) Compiz requests a large chunk of memory in certain
situations that did not occur when testing with the v5.0 kernel. All
of the oom-killer events here were compiz. They may not have occurred
when testing with the v5.0 kernel either because testing was limited
in duration, or because of differences between the testing environment
and the production environment. Our testing with the v5.0 kernel was
done at 800x600 resolution, no proprietary graphics driver. The
oom-killer events described in this bug report occurred at 1920 x 1080
resolution with proprietary nvidia graphics driver. There may or may
not be a kernel bug and it may or may not be fixed in v5.0.

Moving forward we will most likely switch production to open source
nouveau graphics driver and/or Xenial LTS HWE and/or fully upgrade to
18.04.1 Bionic.

I am going to leave this bug marked "Incomplete" due to the
differences between our v5.0 kernel test environment and our
production environment.

Attached are some notes that will be useful to me if I ever come back
here.

** Attachment added: "Notes on how to install latest upstream kernel."

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811093/+attachment/5233365/+files/HowTo.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/1811093

Title:
Bogus "Out of Memory" compiz invoked oom-killer

Status in linux package in Ubuntu:
Incomplete

Bug description:
This has happened five times in the past week (four times in the past
36 hours):

kernel: compiz invoked oom-killer:

There is plenty of free core memory and almost no swap in use when it
happens. This is Xenial with kernel version is 4.4.0-141, which
contains fix to previously reported bug #1655842 "Out of Memory"
oom-killer bug. I only have one week of logs to go by, which contain
five occurrences. It has happened four times in the past 36 hours.
Sometimes it happens right after logging into the unity / lighdm
desktop (three out of five times), but not always. In four out of
five occurrences a postgres job was running and oom-killer killed
postgres. In the one other instance, postgres was quietly idle in the
background and oom-killer killed Thunderbird. Kernel messages in
syslog from five occurrences:

compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0

Additional info:

$> lsb_release -rd
Description: Ubuntu 16.04.5 LTS
Release: 16.04

$> cat /proc/version_signature
Ubuntu 4.4.0-141.167-generic 4.4.162

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811093/+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 284 matches

Mail list logo