[Kernel-packages] [Bug 1560094] Re: Starting bluez service is denied

2020-08-06 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Starting bluez service is denied

Status in bluez package in Ubuntu:
  Expired

Bug description:
  If snappy core is updated in the background (on Raspberry Pi 2), and
  then bluez installed, starting the service is failing.

  
  Denials:

  [   45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0
  [   46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0
  [   46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2

  If trying to start bluetootctl:

  [  582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" 
operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" 
name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0
  [bluetooth]# 

  
  ubuntu@localhost:~$ snappy list
  NameDate   Version  Developer 
  bluez5  2016-02-04 5.37-2-armhf canonical 
  canonical-pi2   2016-02-02 3.0  canonical 
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical 
  ubuntu-core 2016-03-08 16.04.0-15.armhf canonical 
  ubuntu@localhost:~$ 

  ubuntu@localhost:~$ snappy info
  release: core/rolling
  architecture: armhf
  frameworks: bluez5.canonical
  apps:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+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 1812620] Re: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed

2020-08-06 Thread Po-Hsu Lin
I would like to note that although Eoan and Disco has already reached
their end-of-life, we still have 5.3 / 5.0 kernel for clouds.

Next is to check if this can be reproduced on those.

** No longer affects: linux-aws (Ubuntu)

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

Title:
  msg_zerocopy.sh in net from ubuntu_kernel_selftests failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Disco:
  Won't Fix
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix
Status in linux-aws source package in Eoan:
  Won't Fix
Status in linux-azure source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  New
Status in linux-aws source package in Focal:
  New
Status in linux-azure source package in Focal:
  New

Bug description:
  == SRU Justification [ FOCAL ] ==

  The msg_zerocopy.sh kernel self test will fail on machines that don't
  have 2 or 3 CPUs such as 1 CPU cloud instances since the C test
  program tries to set CPU affinity to CPUs 2 and 3 and bails out if it
  fails.

  == Fix ==

  Upstream linux-next commit

  commit 16f6458f2478b55e2b628797bc81a4455045c74e
  Author: Willem de Bruijn 
  Date:   Wed Aug 5 04:40:45 2020 -0400

  selftests/net: relax cpu affinity requirement in msg_zerocopy test

  The fix now just emits a warning that CPU affinity can't be set rather
  than cause an exit(1) termination.

  == Test cast ==

  Run the msg_zerocopy.sh test from the kernel net selftest on a 1 CPU
  system. Without the fix the test fails. With the fix it runs
  successfully as expected.

  == Regression Potential ==

  The original test pinned the CPUs for a benchmarking metric, for our
  testing we are using this to test to see if the operations in the test
  work successfully.  There is a potential that users using this test
  will not notice the warning if they are using this test as a benchmark
  on a 1 CPU system and may get more jittery timing in their benchmarks
  rather than a test failing and complaining they are not running it on
  a suitable multi-CPU system.  However, the likelyhood of a user using
  this test on a single CPU system for benchmarking is small and as it
  stands the test will now run and produce potentially jittery
  benchmarks on a 1 CPU system compared to previously where it never
  ran.

  

  This test will return 1

  $ sudo ./msg_zerocopy.sh
  ipv4 tcp -t 1
  ./msg_zerocopy: setaffinity 2
  ./msg_zerocopy: setaffinity 3
  $ echo $?
  1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 21 07:41 seq
   crw-rw 1 root audio 116, 33 Jan 21 07:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jan 21 07:50:33 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  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/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+subscriptions

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

[Kernel-packages] [Bug 1837810] Re: qemu instance gets paused with error: kvm run failed Bad address

2020-08-06 Thread Matthew Ruffell
Hello @pooja-9, @kphatak-pf9 and @vlee,

You wouldn't happen to have Kernel Samepage Merging (KSM) enabled on
your compute nodes would you?

You can check by looking at the value of:

$ cat /sys/kernel/mm/ksm/run

If it is 1, your nodes have it enabled, and if it is 0 or "missing", you
don't have it on.

We have just hit the problem, and I think I have found a fix for it. I
will fix the 4.15 kernel once I have analysed the problem a bit more.

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

Title:
  qemu instance gets paused with error: kvm run failed Bad address

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We are occasionally running into the below qemu error on our Ubuntu16
  KVM hypervisors managed using Openstack, where the qemu guest instance
  gets paused unexpectedly.

  pooja@kvm14:~$ sudo cat 
/var/log/libvirt/qemu/f8a20654-4c96-4446-95b3-24b8d28fab7f.log.1
  error: kvm run failed Bad address
  RAX= RBX=8d12ffc01b00 RCX= 
RDX=8d14d111c040
  RSI=000e RDI=8d15bffda000 RBP=8d156afbb898 
RSP=8d156afbb870
  R8 =001e R9 = R10=001d 
R11=ffd0
  R12=8d14d111c000 R13=f7de0d444700 R14=8d14d111c000 
R15=0001
  RIP=9ba1911b RFL=00010082 [--S] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =  000f 
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =   00c0
  DS =  000f 
  FS = 7f8c7e8ac700 000f 
  GS = 8d15bfd0 000f 
  LDT=  000f 
  TR =0040 8d15bfd04000 2087 8b00 DPL=0 TSS64-busy
  GDT= 8d15bfd0c000 007f
  IDT= ff528000 0fff
  CR0=80050033 CR2=1699e002 CR3=b0d54000 CR4=003606e0
  DR0= DR1= DR2= 
DR3=
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=44 39 f8 48 63 43 20 0f 8e e1 00 00 00 48 63 53 18 4c 01 e2 <49> 89 14 
04 41 0f b7 55 1a 48 63 43 18 41 83 c7 01 66 81 e2 ff 7f 49 01 c4 0f b7 c2 44 39
  2019-07-16T23:59:30.354240Z qemu-system-x86_64: terminating on signal 15 from 
pid 7487 (/usr/sbin/libvirtd)
  2019-07-16 23:59:31.549+: shutting down, reason=destroyed

  
  We also saw some swap related errors in /var/log/syslog previously:

  Jul  4 08:40:18 kvm14 kernel: \[8084318.769268] audit: type=1400
  audit(1562229618.904:4385): apparmor="STATUS"
  operation="profile_replace" profile="unconfined" name="libvirt-
  a89c8a67-24ae-45cb-a885-8880b49f86fd" pid=53770 comm="apparmor_parser"

  Jul  4 08:40:18 kvm14 libvirtd\[20274]: 2019-07-04 08:40:18.911+:
  20277: warning : AppArmorSetFDLabel:1164 : could not find path for
  descriptor /proc/self/fd/29, skippingJul  4 08:40:19 kvm13 kernel:
  \[8084318.930088] print_req_error: critical medium error, dev nvme0n1,
  sector 392710192

  Jul  4 08:40:19 kvm14 kernel: \[8084318.937754] Read-error on swap-
  device (259:0:392710200)

  Jul  4 08:40:19 kvm14 kernel: \[8084318.943157] Read-error on swap-
  device (259:0:392710208)

  Wondering if these swap read errors happening intermittently, cause
  qemu to pause the guest instance due to memory overcommitment issues.

  pooja@kvm14:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.6 LTS
  Release:16.04
  Codename:   xenial

  pooja@kvm14:~$ /usr/bin/qemu-system-x86_64 --version
  QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.10~cloud0)
  Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers

  pooja@kvm14:~$ dpkg -l | grep libvirt
  ii  libvirt-bin   4.0.0-1ubuntu8.8~cloud0 
  amd64programs for the libvirt library

  
  Sample qemu process args for an instance created using Openstack Nova (Newton 
release):

  pooja@kvm14:~$ sudo ps -ef | grep qemu | tail -1
  libvirt+ 52655 1 83 Jun27 ?22-23:37:19 qemu-system-x86_64 
-enable-kvm -name guest=157b8c3d-87c6-4a62-a05b-8d1aae47e890,debug-threads=on 
-S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-567-157b8c3d-87c6-4a62-a/master-key.aes
 -machine pc-i440fx-bionic,accel=kvm,usb=off,dump-guest-core=off -cpu 
Skylake-Server-IBRS -m 8192 -realtime mlock=off -smp 
2,sockets=2,cores=1,threads=1 -uuid 157b8c3d-87c6-4a62-a05b-8d1aae47e890 
-smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack 
Nova,version=2013.2.1,serial=1a2fd1a2-3df9-4ed9-ad7f-b4c2479a01ca,uuid=157b8c3d-87c6-4a62-a05b-8d1aae47e890,family=Virtual
 Machine -no-user-config -nodefaults -chardev 

[Kernel-packages] [Bug 1890436] Re: VGA signal is ghosted and stretched (Intel® HD Graphics 2500)

2020-08-06 Thread Daniel van Vugt
Yes I do understand why you might call that corruption.

Actually you didn't need to enable DRM debugging. It looks like there
are a few errors coming from the Intel kernel graphics driver 'i915'.
Those might be separate to the FIFO underrun errors, which other people
also report in bug 1550779.

The problems reported in your kernel log seem to relate to atomic mode
setting, which is what the 'modeset' Xorg driver uses. Wayland sessions
don't use that interface to Intel graphics so it's likely that logging
into 'Ubuntu on Wayland' will avoid some (or all) of the problem.

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

Title:
  VGA signal is ghosted and stretched (Intel® HD Graphics 2500)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  

[Kernel-packages] [Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found

2020-08-06 Thread Alex Hung
You can try "sync" to force writing cache to USB drive. It is easier to
remember.

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

Title:
  wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not
  found

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run the kernel 5.4.0-42-generic on a fully up-to-date Ubuntu "focal" on 
Dell Latitude E6440.
  While scrolling through the output of `journalctl -b` I came across a warning 
(marked yellow):

  [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query
  control method not found

  Now, since this is a warning, I get, ergo, warned.  What is it that I
  get warned about?  Is it just a printf or is some action required?  As
  every computer, the laptop suffers from various problems from time to
  time (e.g., boot or wakeup silently hangs up while the manufacturer
  splash screen is displayed), so, I don't know whether this message
  could be related to any of such problems.

  Here is the context of this warning in dmesg:

  # dmesg | grep -B 10 -A 5 "method not found"
  [0.518379] rtc_cmos 00:02: setting system clock to 2020-08-05T15:23:54 
UTC (1596641034)
  [0.519455] Freeing unused decrypted memory: 2040K
  [0.520119] Freeing unused kernel image memory: 2712K
  [0.531430] Write protecting the kernel read-only data: 22528k
  [0.532242] Freeing unused kernel image memory: 2008K
  [0.532805] Freeing unused kernel image memory: 1192K
  [0.540186] x86/mm: Checked W+X mappings: passed, no W+X pages found.
  [0.540514] x86/mm: Checking user space page tables
  [0.547468] x86/mm: Checked W+X mappings: passed, no W+X pages found.
  [0.547786] Run /init as init process
  [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control 
method not found
  [0.659921] ACPI Warning: SystemIO range 
0x1828-0x182F conflicts with OpRegion 
0x1800-0x183F (\_SB.PCI0.EHC2.E1PM) 
(20190816/utaddress-204)
  [0.661768] ACPI Warning: SystemIO range 
0x1828-0x182F conflicts with OpRegion 
0x1800-0x183F (\_SB.PCI0.EHC1.E1PM) 
(20190816/utaddress-204)
  [0.663121] ACPI Warning: SystemIO range 
0x1828-0x182F conflicts with OpRegion 
0x1800-0x187F (\PMIO) (20190816/utaddress-204)
  [0.664516] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver
  [0.666167] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k

  Some more info:

  # ls -la /sys/devices/platform/PNP0C14:00
  drwxr-xr-x  4 root root0 Aug  5 17:23 .
  drwxr-xr-x 29 root root0 Aug  5 17:23 ..
  lrwxrwxrwx  1 root root0 Aug  5 17:23 driver -> 
../../../bus/platform/drivers/acpi-wmi
  -rw-r--r--  1 root root 4096 Aug  5 18:09 driver_override
  lrwxrwxrwx  1 root root0 Aug  5 18:09 firmware_node -> 
../../LNXSYSTM:00/LNXSYBUS:00/PNP0C14:00
  -r--r--r--  1 root root 4096 Aug  5 18:09 modalias
  drwxr-xr-x  2 root root0 Aug  5 18:09 power
  lrwxrwxrwx  1 root root0 Aug  5 17:23 subsystem -> ../../../bus/platform
  -rw-r--r--  1 root root 4096 Aug  5 17:23 uevent
  drwxr-xr-x  3 root root0 Aug  5 17:23 wmi_bus
  #

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890467/+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 1886908] Re: Add support for Atlantic NIC firmware v4

2020-08-06 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   Status: Triaged => Fix Committed

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

Title:
  Add support for Atlantic NIC firmware v4

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Triaged
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  Atlantic NIC doesn't work.

  [Fix]
  Add firmware v4 support.

  [Test]
  With the patch applied, the driver probe success.
  Using iperf as a smoketest shows positive result.

  [Regression Potential]
  None. We were contacted by Marvell after I sent the patch to upstream,
  and they told us firmware v4 is created specifically for this upcoming
  platform. There are none firmware v4 in production.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1886908/+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 1888551] Re: perf vendor events s390: Add new deflate counters for IBM z15

2020-08-06 Thread Kelsey Margarete Skunberg
** Changed in: linux (Ubuntu Focal)
   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/1888551

Title:
  perf vendor events s390: Add new deflate counters for IBM z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters
  reported with lscpumf are not usable with 'perf stat -e'.

  * 'lscpumf -c' provides a list of available counters, but the
  following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC,
  DFLT_CCERROR

  * 'perf list' is also not offering these counters.

  * On the kernel side this is fixed with the following upstream
  accepted commit:

  [Fix]

  * e7950166e40271c025e0eec348cdf5c63ac734fa "perf vendor events s390:
  Add new deflate counters for IBM z15"

  [Test Case]

  * Requires the fix/patch of the kernel
  (d68d5d51dc898895b4e15bea52e5668ca9e76180 "s390/cpum_cf: Add new
  extended counters for IBM z15")

  * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in
  LPAR is needed where the counters are enabled in the activation
  profile.

  * Use 'perf list' to determine if the counters DFLT_ACCESS,
  DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed

  * Use 'perf stat -e' to enable amd make use of these counters.

  [Regression Potential]

  * The regression can be considered as low, since:

  * it's architecture specific (s390x)

  * limited to IBM z15 hardware

  * and only additional (s390x) hardware counters are defined and added.

  [Other]

  * Since these patches are upstream in kernel 5.7 they will
  automatically land in groovy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888551/+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 1559643] Re: kswapd0 high cpu

2020-08-06 Thread Kai Kasurinen
** Package changed: udev (Ubuntu) => systemd (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/1559643

Title:
  kswapd0 high cpu

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  kswapd0 high cpu load.
  System doesn't have swap partition / swap file.

  Using AWS t2.nano

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-34-generic 4.2.0-34.39
  ProcVersionSignature: User Name 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 07:35 seq
   crw-rw 1 root audio 116, 33 Mar 20 07:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  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:
  Date: Sun Mar 20 07:57:52 2016
  Ec2AMI: ami-b7443fc0
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 cirrusdrmfb
   1 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=b079c5f1-8fc8-4bb0-aa26-31610f9c5615 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-34-generic N/A
   linux-backports-modules-4.2.0-34-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-13 (127 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/07/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559643/+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 1856871] Re: i/o error if next unused loop device is queried

2020-08-06 Thread Kai Kasurinen
** Changed in: udev (Ubuntu)
   Status: New => Invalid

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

Title:
  i/o error if next unused loop device is queried

Status in linux package in Ubuntu:
  Incomplete
Status in parted package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while /dev/loop3 doesn't

  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0

  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.

  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.

  If I query loop3 with 'parted' right after, no errors.

  If I reboot, and query loop3 again, then no I'll have an error.

  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).

  This was tested with focal/systemd whic his very close to latest
  upstream code.

  This has been test with latest v5.5 mainline kernel as well.

  For now, I don't think it's a kernel problem, I'm more thinking of a
  userspace misbehaviour dealing with loop device (or block device) at
  boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+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 1890639] Missing required logs.

2020-08-06 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 1890639

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

Title:
  touchpad not working after login dell xps 13

Status in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My touchpad stops working after login.

  These are the props using xinput:

  Device 'DLL075B:01 06CB:76AF Touchpad':
Device Enabled (148):   1
Coordinate Transformation Matrix (150): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Tapping Enabled (302): 1
libinput Tapping Enabled Default (303): 0
libinput Tapping Drag Enabled (304):1
libinput Tapping Drag Enabled Default (305):1
libinput Tapping Drag Lock Enabled (306):   0
libinput Tapping Drag Lock Enabled Default (307):   0
libinput Tapping Button Mapping Enabled (308):  1, 0
libinput Tapping Button Mapping Default (309):  1, 0
libinput Natural Scrolling Enabled (286):   1
libinput Natural Scrolling Enabled Default (287):   0
libinput Disable While Typing Enabled (310):1
libinput Disable While Typing Enabled Default (311):1
libinput Scroll Methods Available (288):1, 1, 0
libinput Scroll Method Enabled (289):   1, 0, 0
libinput Scroll Method Enabled Default (290):   1, 0, 0
libinput Click Methods Available (312): 1, 1
libinput Click Method Enabled (313):1, 0
libinput Click Method Enabled Default (314):1, 0
libinput Middle Emulation Enabled (315):0
libinput Middle Emulation Enabled Default (316):0
libinput Accel Speed (293): 0.00
libinput Accel Speed Default (294): 0.00
libinput Left Handed Enabled (298): 0
libinput Left Handed Enabled Default (299): 0
libinput Send Events Modes Available (271): 1, 1
libinput Send Events Mode Enabled (272):1, 0
libinput Send Events Mode Enabled Default (273):0, 0
Device Node (274):  "/dev/input/event7"
Device Product ID (275):1739, 30383
libinput Drag Lock Buttons (300):   
libinput Horizontal Scroll Enabled (301):   1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1890639/+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 1890639] Re: touchpad not working after login dell xps 13

2020-08-06 Thread Uri
since this is hardware related, I added "linux" as affected package

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

Title:
  touchpad not working after login dell xps 13

Status in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My touchpad stops working after login.

  These are the props using xinput:

  Device 'DLL075B:01 06CB:76AF Touchpad':
Device Enabled (148):   1
Coordinate Transformation Matrix (150): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Tapping Enabled (302): 1
libinput Tapping Enabled Default (303): 0
libinput Tapping Drag Enabled (304):1
libinput Tapping Drag Enabled Default (305):1
libinput Tapping Drag Lock Enabled (306):   0
libinput Tapping Drag Lock Enabled Default (307):   0
libinput Tapping Button Mapping Enabled (308):  1, 0
libinput Tapping Button Mapping Default (309):  1, 0
libinput Natural Scrolling Enabled (286):   1
libinput Natural Scrolling Enabled Default (287):   0
libinput Disable While Typing Enabled (310):1
libinput Disable While Typing Enabled Default (311):1
libinput Scroll Methods Available (288):1, 1, 0
libinput Scroll Method Enabled (289):   1, 0, 0
libinput Scroll Method Enabled Default (290):   1, 0, 0
libinput Click Methods Available (312): 1, 1
libinput Click Method Enabled (313):1, 0
libinput Click Method Enabled Default (314):1, 0
libinput Middle Emulation Enabled (315):0
libinput Middle Emulation Enabled Default (316):0
libinput Accel Speed (293): 0.00
libinput Accel Speed Default (294): 0.00
libinput Left Handed Enabled (298): 0
libinput Left Handed Enabled Default (299): 0
libinput Send Events Modes Available (271): 1, 1
libinput Send Events Mode Enabled (272):1, 0
libinput Send Events Mode Enabled Default (273):0, 0
Device Node (274):  "/dev/input/event7"
Device Product ID (275):1739, 30383
libinput Drag Lock Buttons (300):   
libinput Horizontal Scroll Enabled (301):   1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1890639/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport

2020-08-06 Thread Brian Murray
I've uploaded this to the SRU queue for Bionic.

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

Title:
  missing hardware/runtime info when reporing linux-firmware bugs via
  apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Invalid
Status in linux-firmware source package in Eoan:
  Invalid
Status in apport source package in Focal:
  Fix Released
Status in linux-firmware source package in Focal:
  Invalid

Bug description:
  Updated Description to match SRU requirements for bionic

  [Impact]
  linux-firmware doesn't install any package hooks for apport, so it will only 
carry some default items leaving hardware list, kernel messages unattached. 
Suggest symlink /usr/share/apport/package-hooks/source_linux-firmware.py to 
source_linux.py as other linux image debs do in bug 1847967.

  [Test Case]
  1) On an Ubuntu 18.04 LTS system run 'apport-cli linux-firmware'.
  2) Choose 'View report'
  3) Observe that 'ProcFB' is not collected

  With the version of apport from -proposed 'ProcFB' will be in the
  report.

  
  [Regression Potential]
  Very limited, as we are just adding a symlink from linux-firmware to the 
linux source package hook. this change has been available in Focal and Groovy 
without problem


  Original Description
  
  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 10 19:15:15 2020
  Dependencies:

  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  PackageArchitecture: allSourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Dependencies:

  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux-firmware
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic 
root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet 
splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 156.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport

2020-08-06 Thread Matthieu Clemenceau
The attached deb diff will fix issue this on bionic as of today with
latest apport on bionic being 2.20.9-0ubuntu7.16

** Description changed:

- linux-firmware doesn't install any package hooks for apport, so it will
- only carry some default items leaving hardware list, kernel messages
- unattached. Suggest symlink /usr/share/apport/package-hooks
- /source_linux-firmware.py to source_linux.py as other linux image debs
- do in bug 1847967.
+ Updated Description to match SRU requirements for bionic
  
- Test Case
- -
- 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'.
+ [Impact]
+ linux-firmware doesn't install any package hooks for apport, so it will only 
carry some default items leaving hardware list, kernel messages unattached. 
Suggest symlink /usr/share/apport/package-hooks/source_linux-firmware.py to 
source_linux.py as other linux image debs do in bug 1847967.
+ 
+ [Test Case]
+ 1) On an Ubuntu 18.04 LTS system run 'apport-cli linux-firmware'.
  2) Choose 'View report'
  3) Observe that 'ProcFB' is not collected
  
  With the version of apport from -proposed 'ProcFB' will be in the
  report.
  
  
- Regression Potential
- 
- None, as we are just adding a symlink from linux-firmware to the linux source 
package hook.
+ [Regression Potential]
+ Very limited, as we are just adding a symlink from linux-firmware to the 
linux source package hook. this change has been available in Focal and Groovy 
without problem
+ 
  
  Original Description
  
  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 10 19:15:15 2020
  Dependencies:
  
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  PackageArchitecture: allSourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Dependencies:
  
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux-firmware
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic 
root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet 
splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 156.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

** Patch added: "apport_2.20.9-0ubuntu7.17.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1872059/+attachment/5399419/+files/apport_2.20.9-0ubuntu7.17.debdiff

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

Title:
  missing hardware/runtime info when reporing linux-firmware bugs via
  apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Invalid
Status in linux-firmware source package in Eoan:
  Invalid
Status in apport source package in Focal:
  Fix Released
Status in linux-firmware source package in Focal:
  Invalid

Bug description:
  Updated Description to match SRU requirements for bionic

  [Impact]
  linux-firmware doesn't install any package hooks for apport, so it will only 
carry some default items leaving hardware 

[Kernel-packages] [Bug 1890641] Re: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169

2020-08-06 Thread Brian Murray
The file is available on my 20.04 system.
[ 12:15PM 11013 ]  [ bdmurray@impulse:/tmp/bug-1890638 ]
 $ dpkg -L linux-firmware | grep "rtl_nic"
/lib/firmware/rtl_nic
/lib/firmware/rtl_nic/rtl8105e-1.fw
/lib/firmware/rtl_nic/rtl8106e-1.fw
/lib/firmware/rtl_nic/rtl8106e-2.fw
/lib/firmware/rtl_nic/rtl8107e-1.fw
/lib/firmware/rtl_nic/rtl8107e-2.fw
/lib/firmware/rtl_nic/rtl8125a-3.fw
/lib/firmware/rtl_nic/rtl8153a-2.fw
/lib/firmware/rtl_nic/rtl8153a-3.fw
/lib/firmware/rtl_nic/rtl8153a-4.fw
/lib/firmware/rtl_nic/rtl8153b-2.fw
/lib/firmware/rtl_nic/rtl8168d-1.fw
/lib/firmware/rtl_nic/rtl8168d-2.fw
/lib/firmware/rtl_nic/rtl8168e-1.fw
/lib/firmware/rtl_nic/rtl8168e-2.fw
/lib/firmware/rtl_nic/rtl8168e-3.fw
/lib/firmware/rtl_nic/rtl8168f-1.fw
/lib/firmware/rtl_nic/rtl8168f-2.fw
/lib/firmware/rtl_nic/rtl8168fp-3.fw
/lib/firmware/rtl_nic/rtl8168g-1.fw
/lib/firmware/rtl_nic/rtl8168g-2.fw
/lib/firmware/rtl_nic/rtl8168g-3.fw
/lib/firmware/rtl_nic/rtl8168h-1.fw
/lib/firmware/rtl_nic/rtl8168h-2.fw
/lib/firmware/rtl_nic/rtl8402-1.fw
/lib/firmware/rtl_nic/rtl8411-1.fw
/lib/firmware/rtl_nic/rtl8411-2.fw
[ 12:15PM 11014 ]  [ bdmurray@impulse:/tmp/bug-1890638 ]
 $ apt-cache policy linux-firmware
linux-firmware:
  Installed: 1.187.2
  Candidate: 1.187.2


** Package changed: ubuntu-release-upgrader (Ubuntu) => linux-firmware
(Ubuntu)

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

Title:
  Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for
  module r8169

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for
  module r8169

  after running sudo apt upgrade in ubuntu 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.38
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  6 22:38:31 2020
  InstallationDate: Installed on 2019-06-16 (417 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2020-03-08 22:54:00.439353
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1890641/+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 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

2020-08-06 Thread Uriel Tunn
The post 54 workaround fixed it for me, thanks much @khitschler.
(https://bugs.launchpad.net/ubuntu/+source/plasma-
desktop/+bug/1849084/comments/54)

Running Ubuntu 18.04.1 with latest stable kernel (5.4.0-42), but this
has been a problem since the upgrade from 16.04.

Since there are no issues with the workaround, it will remain in place
until the upgrade to 20.04.

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 

[Kernel-packages] [Bug 1890641] [NEW] Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module
r8169

after running sudo apt upgrade in ubuntu 18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.38
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  6 22:38:31 2020
InstallationDate: Installed on 2019-06-16 (417 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
 Log time: 2020-03-08 22:54:00.439353
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done

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


** Tags: amd64 apport-bug bionic dist-upgrade
-- 
Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
https://bugs.launchpad.net/bugs/1890641
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-firmware 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 1788097] Re: performance drop with ATS enabled

2020-08-06 Thread bugproxy
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin18042

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

Title:
  performance drop with ATS enabled

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:
  == Comment: #0 - Michael Ranweiler  - 2018-08-16
  09:58:02 ==

  Witherspoon cluster now has ATS enabled with driver 396.42, CUDA
  version 9.2.148. They are running the CORAL benchmark LULESH with and
  without ATS, and they see a significant performance drop with ATS
  enabled.

  
  Below is the run with ATS:

  Run completed:
  Problem size = 160
  MPI tasks = 8
  Iteration count = 100
  Final Origin Energy = 1.605234e+09
  Testing Plane 0 of Energy Array on rank 0:
  MaxAbsDiff = 2.384186e-07
  TotalAbsDiff = 5.300015e-07
  MaxRelDiff = 1.631916e-12

  Elapsed time = 153.00 (s)
  Grind time (us/z/c) = 0.37352393 (per dom) (0.046690491 overall)
  FOM = 21417.637 (z/s)

  
  Here is the run without ATS:
  Run completed:
  Problem size = 160
  MPI tasks = 8
  Iteration count = 100
  Final Origin Energy = 1.605234e+09
  Testing Plane 0 of Energy Array on rank 0:
  MaxAbsDiff = 2.384186e-07
  TotalAbsDiff = 5.300015e-07
  MaxRelDiff = 1.631916e-12

  
  Elapsed time = 13.27 (s)
  Grind time (us/z/c) = 0.032394027 (per dom) (0.0040492534 overall)
  FOM = 246959.11 (z/s)
  

  Using ATS on a single node slows down the OpenACC version more than 10
  times, and for the version with OpenMP 4.5 and managed memory, they
  observe a 2x slowdown.

  Last comment from NVIDIA (Javier Cabezas - 07/29/2018 11:30 AM):
  We think we have found where's the issue.

  This behavior reproduces for any two concurrent processes that create
  CUDA contexts on the GPUs and heavily unmap memory (no need to launch
  any work on the GPUs). When the problem repros, perf shows that most
  of the time is spent in mmio_invalidate. However, this only happens
  when processes register GPUs attached to the same NPU. Thus, if
  process A, initializes GPU 0 and/or 1, and process B, initializes GPU
  2 and/or 3, we don't see the slowdown. This makes sense, because ATSDs
  on different NPUs are issued independently.

  After some code inspection in npu-dma.c (powerpc backend in the Linux
  kernel), Mark noticed that the problem could be in the utilization of
  test_and_set_bit_lock in get_mmio_atsd_reg. The implementation of
  test_and_set_bit_lock in powerpc relies on the ldarx/stdcx
  instructions (PPC_LLARX/PPC_STLCX in the snippet below):

  #define DEFINE_TESTOP(fn, op, prefix, postfix, eh)\
  static __inline__ unsigned long fn(   \
  unsigned long mask,   \
  volatile unsigned long *_p)   \
  { \
  unsigned long old, t; \
  unsigned long *p = (unsigned long *)_p;   \
  __asm__ __volatile__ (\
  prefix\
  "1:"PPC_LLARX(%0,0,%3,eh) "\n"\
  stringify_in_c(op) "%1,%0,%2\n"   \
  PPC405_ERR77(0,%3)\
  PPC_STLCX "%1,0,%3\n" \
  "bne- 1b\n"   \
  postfix   \
  : "=" (old), "=" (t)  \
  : "r" (mask), "r" (p) \
  : "cc", "memory");\
  return (old & mask);  \
  }

  According to the PowerPC manual, ldarx creates a memory reservation
  and a subsequent stwcx instruction from the same processor ensures an
  atomic read-modify-write operation. However, the reservation can be
  lost if a different processor executes any store instruction on the
  same address. That's why "bne- 1b" checks wether stwcx was successful
  and jumps back to retry, otherwise. Since DEFINE_TESTOP doesn't
  implement any back-off mechanism, two different processors trying to
  get an ATSD register can starve each other.

  Mark compiled a custom kernel which surrounds the calls to
  test_and_set_bit_lock in get_mmio_atsd_reg with a spinlock and I
  verified that it solves the issue. These are the execution times for
  LULESH:

  ATS OFF
  Elapsed time =  16.87 (s)

  ATS ON
  Elapsed time = 215.56 (s)

  ATS ON + Spinlock
  Elapsed time =  18.14 (s)

  
  Fixed with the following patch in the powerpc tree:
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=9eab9901b015

  == Comment: #1 - Michael Ranweiler  - 2018-08-20 
14:56:52 ==
  This is now in 

[Kernel-packages] [Bug 1848193] Re: Fixup tlbie vs store ordering issue on POWER9

2020-08-06 Thread bugproxy
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1910

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

Title:
  Fixup tlbie vs store ordering issue on POWER9

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

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-10-07 01:52:38 ==
  On POWER9, under some circumstances, a broadcast TLB invalidation will fail 
to invalidate the ERAT cache on some threads when there are parallel 
mtpidr/mtlpidr happening on other threads of the same core.  This can cause 
stores to continue to go to a page after it's unmapped.

  The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie
  flush. This additional TLB flush will cause the ERAT cache
  invalidation. Since we are using PID=0 or LPID=0, we don't get
  filtered out by the TLB snoop filtering logic.

  We need to still follow this up with another tlbie to take care of
  store vs tlbie ordering issue explained in commit: a5d4b5891c2f
  ("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The
  presence of ERAT cache implies we can still get new stores and they
  may miss store queue marking flush.

  The upstream git commits to resolve the problem:

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=677733e296b5c7a37c47da391fc70a43dc40bd67

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=047e6575aec71d75b765c22111820c4776cd1c43

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1848193/+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 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

2020-08-06 Thread Dan Streetman
maybe it would be better to just switch to systemd-coredump for crash
handling.

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Confirmed
Status in bluez source package in Focal:
  Invalid

Bug description:
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1888570] Re: poweroff not working after apt upgrade

2020-08-06 Thread Günter Neiß
Today I had donloaded the ubuntu-20.04.1-desktop-amd64.io and do a fresh 
install.
unfortunaly the problem exist there too :-(
I will do some more tests and inform You about the findings..
(will take some time...)

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

Title:
  poweroff not working after apt upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System-Information:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  ##
  Working packages:
  - Kernel 5.3.0.61.114
  - linux-firmware 1.173.18

  Problem occurs when upgrading (anyone of) these packages
  - Kernel 5.3.0-62.56
  - linux-firmware 1.173.19

  I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 
18.04.
  Till the last upgrade everything works as expected.
  The last upgrade brings two new kernel versions (as mentioned above).
  Now the system stucks at the very end of the power down sequence.
  Even SysReq-O will not work (only SysReq-B will work).

  Because I use Systemback, I time shift to the previous system and then 
install package by package to see what will bring in the problem.
  If I install any of the mentioned kernel updates the problem will show up.

  I had ask the above question on "askubuntu.com".
  I was directed to upgrade the BIOS, But even after doing so the problem still 
persist.

  I am not sure if I do it right (APT pinning).
  I currently create a file /etc/apt/prefereces.d/kernel.

  I add an entry for every of the following packages to block the
  version mentioned above (Pin: version:  Pin-Priority: -1):

  linux-generic-hwe-18.04
  linux-headers-generic-hwe-18.04
  linux-image-generic-hwe-18.04
  linux-modules-nvidia-440-generic-hwe-18.04
  linux-firmware

  After doing so "apt list --upgradeable" will not list the packages in
  question and the PC will power down normally (and SysReq-O WILL work).

  In the meanwhile there are newer versions of the kernel online, so the above 
mentioned pinning will allow the newer kernels to get installed and the problem 
will show up again.
  So I block these versions too.

  BTW: Due to the stuck I am able to see some other error messages that are not 
reported in the journal. The very last 3-5 lines show:
  shutdown [1]: Failed to wait for process: Protocol error
  These lines are present although in the working kernels, but hard to see, 
because the system powers down some ms after these lines are displayed!
  This problem seams to be solved more than one year ago in the upstream kernel!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gneiss 1929 F pulseaudio
   /dev/snd/controlC0:  gneiss 1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-05-02 (448 days ago)
  InstallationMedia:
   
  MachineType: Acer Aspire E5-771G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic 
root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth 
resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee
  ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-61-generic N/A
   linux-backports-modules-5.3.0-61-generic  N/A
   linux-firmware1.173.18
  Tags:  bionic
  Uname: Linux 5.3.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/02/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA70_HB
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-771G
  dmi.product.sku: Aspire E5-771G_0884_1_23
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+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 1890634] Status changed to Confirmed

2020-08-06 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/1890634

Title:
  NFS Home Directories

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running with NFSv4 4.2 home directories with encryption enabled
  the machine froze hard. Reporting an exception in syslog.

  Aug  6 10:16:00 tars kernel: [1058579.764235] [ cut here 
]
  Aug  6 10:16:00 tars kernel: [1058579.764262] virt_to_cache: Object is not a 
Slab page!
  Aug  6 10:16:00 tars kernel: [1058579.764296] WARNING: CPU: 3 PID: 0 at 
mm/slab.h:409 kmem_cache_free+0x237/0x2b0
  Aug  6 10:16:00 tars kernel: [1058579.764298] Modules linked in: bluetooth 
ecdh_generic ecc ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs cpuid veth 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter 
vhost_net vhost tap xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter bpfilter aufs 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache overlay bridge stp 
llc joydev binfmt_misc uvcvideo v4l2_common videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 videobuf2_common snd_usb_audio videodev snd_usbmidi_lib mc 
intel_rapl_msr nls_iso8859_1 intel_rapl_common isst_if_common skx_edac 
snd_hda_codec_hdmi nfit x86_pkg_temp_thermal intel_powerclamp 
snd_hda_codec_realtek coretemp snd_hda_codec_generic kvm_intel ledtrig_audio 
kvm irqbypass snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm
  Aug  6 10:16:00 tars kernel: [1058579.764378]  snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer dell_wmi 
sparse_keymap dell_smm_hwmon snd dell_smbios video intel_cstate dcdbas mei_me 
input_leds intel_rapl_perf mei intel_wmi_thunderbolt dell_wmi_descriptor 
wmi_bmof soundcore serio_raw ioatdma dca nvidia_uvm(POE) mac_hid sch_fq_codel 
parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid 
hid uas usb_storage nvidia_drm(POE) nvidia_modeset(POE) crct10dif_pclmul 
crc32_pclmul nvidia(POE) ghash_clmulni_intel aesni_intel drm_kms_helper 
syscopyarea sysfillrect sysimgblt aes_x86_64 fb_sys_fops crypto_simd cryptd drm 
glue_helper ipmi_devintf ipmi_msghandler e1000e ahci i2c_i801 libahci wmi
  Aug  6 10:16:00 tars kernel: [1058579.764454] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: P   OE 5.3.0-62-generic #56-Ubuntu
  Aug  6 10:16:00 tars kernel: [1058579.764456] Hardware name: Dell Inc. 
Precision 5820 Tower/0X8DXD, BIOS 1.9.2 01/24/2019
  Aug  6 10:16:00 tars kernel: [1058579.764462] RIP: 
0010:kmem_cache_free+0x237/0x2b0
  Aug  6 10:16:00 tars kernel: [1058579.764466] Code: ff ff ff 80 3d b4 e3 56 
01 00 0f 85 39 ff ff ff 48 c7 c6 00 88 25 a0 48 c7 c7 68 cf 55 a0 c6 05 99 e3 
56 01 01 e8 44 d3 df ff <0f> 0b e9 18 ff ff ff 48 8b 57 58 49 8b 4f 58 48 c7 c6 
10 88 25 a0
  Aug  6 10:16:00 tars kernel: [1058579.764469] RSP: 0018:9e04c01d8d28 
EFLAGS: 00010282
  Aug  6 10:16:00 tars kernel: [1058579.764472] RAX:  RBX: 
8e5b8ef53534 RCX: 
  Aug  6 10:16:00 tars kernel: [1058579.764474] RDX: 00040400 RSI: 
00f6 RDI: 0300
  Aug  6 10:16:00 tars kernel: [1058579.764477] RBP: 9e04c01d8d50 R08: 
8e60ffed7448 R09: 0004
  Aug  6 10:16:00 tars kernel: [1058579.764479] R10:  R11: 
0001 R12: 8e5c0ef53534
  Aug  6 10:16:00 tars kernel: [1058579.764481] R13:  R14: 
8e60e7f81a10 R15: 
  Aug  6 10:16:00 tars kernel: [1058579.764484] FS:  () 
GS:8e60ffec() knlGS:
  Aug  6 10:16:00 tars kernel: [1058579.764486] CS:  0010 DS:  ES:  
CR0: 80050033
  Aug  6 10:16:00 tars kernel: [1058579.764488] CR2: 7f8f17c9fe98 CR3: 
0005a600a001 CR4: 003626e0
  Aug  6 10:16:00 tars kernel: [1058579.764491] DR0:  DR1: 
 DR2: 
  Aug  6 10:16:00 tars kernel: [1058579.764493] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Aug  6 10:16:00 tars kernel: [1058579.764494] Call Trace:
  Aug  6 10:16:00 tars kernel: [1058579.764497]  
  Aug  6 10:16:00 tars kernel: [1058579.764509]  ? 
sg_free_table_chained+0x30/0x30
  Aug  6 10:16:00 tars kernel: [1058579.764514]  mempool_free_slab+0x17/0x20
  Aug  6 10:16:00 tars kernel: [1058579.764517]  mempool_free+0x2f/0x80
  Aug  6 10:16:00 tars kernel: [1058579.764522]  sg_pool_free+0x4f/0x60
  Aug  6 

[Kernel-packages] [Bug 1890634] Re: NFS Home Directories

2020-08-06 Thread Rhian Resnick
I believe this may duplicate bug: 1886775.

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

Title:
  NFS Home Directories

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running with NFSv4 4.2 home directories with encryption enabled
  the machine froze hard. Reporting an exception in syslog.

  Aug  6 10:16:00 tars kernel: [1058579.764235] [ cut here 
]
  Aug  6 10:16:00 tars kernel: [1058579.764262] virt_to_cache: Object is not a 
Slab page!
  Aug  6 10:16:00 tars kernel: [1058579.764296] WARNING: CPU: 3 PID: 0 at 
mm/slab.h:409 kmem_cache_free+0x237/0x2b0
  Aug  6 10:16:00 tars kernel: [1058579.764298] Modules linked in: bluetooth 
ecdh_generic ecc ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs cpuid veth 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter 
vhost_net vhost tap xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter bpfilter aufs 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache overlay bridge stp 
llc joydev binfmt_misc uvcvideo v4l2_common videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 videobuf2_common snd_usb_audio videodev snd_usbmidi_lib mc 
intel_rapl_msr nls_iso8859_1 intel_rapl_common isst_if_common skx_edac 
snd_hda_codec_hdmi nfit x86_pkg_temp_thermal intel_powerclamp 
snd_hda_codec_realtek coretemp snd_hda_codec_generic kvm_intel ledtrig_audio 
kvm irqbypass snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm
  Aug  6 10:16:00 tars kernel: [1058579.764378]  snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer dell_wmi 
sparse_keymap dell_smm_hwmon snd dell_smbios video intel_cstate dcdbas mei_me 
input_leds intel_rapl_perf mei intel_wmi_thunderbolt dell_wmi_descriptor 
wmi_bmof soundcore serio_raw ioatdma dca nvidia_uvm(POE) mac_hid sch_fq_codel 
parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid 
hid uas usb_storage nvidia_drm(POE) nvidia_modeset(POE) crct10dif_pclmul 
crc32_pclmul nvidia(POE) ghash_clmulni_intel aesni_intel drm_kms_helper 
syscopyarea sysfillrect sysimgblt aes_x86_64 fb_sys_fops crypto_simd cryptd drm 
glue_helper ipmi_devintf ipmi_msghandler e1000e ahci i2c_i801 libahci wmi
  Aug  6 10:16:00 tars kernel: [1058579.764454] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: P   OE 5.3.0-62-generic #56-Ubuntu
  Aug  6 10:16:00 tars kernel: [1058579.764456] Hardware name: Dell Inc. 
Precision 5820 Tower/0X8DXD, BIOS 1.9.2 01/24/2019
  Aug  6 10:16:00 tars kernel: [1058579.764462] RIP: 
0010:kmem_cache_free+0x237/0x2b0
  Aug  6 10:16:00 tars kernel: [1058579.764466] Code: ff ff ff 80 3d b4 e3 56 
01 00 0f 85 39 ff ff ff 48 c7 c6 00 88 25 a0 48 c7 c7 68 cf 55 a0 c6 05 99 e3 
56 01 01 e8 44 d3 df ff <0f> 0b e9 18 ff ff ff 48 8b 57 58 49 8b 4f 58 48 c7 c6 
10 88 25 a0
  Aug  6 10:16:00 tars kernel: [1058579.764469] RSP: 0018:9e04c01d8d28 
EFLAGS: 00010282
  Aug  6 10:16:00 tars kernel: [1058579.764472] RAX:  RBX: 
8e5b8ef53534 RCX: 
  Aug  6 10:16:00 tars kernel: [1058579.764474] RDX: 00040400 RSI: 
00f6 RDI: 0300
  Aug  6 10:16:00 tars kernel: [1058579.764477] RBP: 9e04c01d8d50 R08: 
8e60ffed7448 R09: 0004
  Aug  6 10:16:00 tars kernel: [1058579.764479] R10:  R11: 
0001 R12: 8e5c0ef53534
  Aug  6 10:16:00 tars kernel: [1058579.764481] R13:  R14: 
8e60e7f81a10 R15: 
  Aug  6 10:16:00 tars kernel: [1058579.764484] FS:  () 
GS:8e60ffec() knlGS:
  Aug  6 10:16:00 tars kernel: [1058579.764486] CS:  0010 DS:  ES:  
CR0: 80050033
  Aug  6 10:16:00 tars kernel: [1058579.764488] CR2: 7f8f17c9fe98 CR3: 
0005a600a001 CR4: 003626e0
  Aug  6 10:16:00 tars kernel: [1058579.764491] DR0:  DR1: 
 DR2: 
  Aug  6 10:16:00 tars kernel: [1058579.764493] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Aug  6 10:16:00 tars kernel: [1058579.764494] Call Trace:
  Aug  6 10:16:00 tars kernel: [1058579.764497]  
  Aug  6 10:16:00 tars kernel: [1058579.764509]  ? 
sg_free_table_chained+0x30/0x30
  Aug  6 10:16:00 tars kernel: [1058579.764514]  mempool_free_slab+0x17/0x20
  Aug  6 10:16:00 tars kernel: [1058579.764517]  mempool_free+0x2f/0x80
  Aug  6 10:16:00 tars kernel: [1058579.764522]  sg_pool_free+0x4f/0x60
  Aug  6 10:16:00 tars kernel: [1058579.764529]  

[Kernel-packages] [Bug 1890634] [NEW] NFS Home Directories

2020-08-06 Thread Rhian Resnick
Public bug reported:

When running with NFSv4 4.2 home directories with encryption enabled the
machine froze hard. Reporting an exception in syslog.

Aug  6 10:16:00 tars kernel: [1058579.764235] [ cut here 
]
Aug  6 10:16:00 tars kernel: [1058579.764262] virt_to_cache: Object is not a 
Slab page!
Aug  6 10:16:00 tars kernel: [1058579.764296] WARNING: CPU: 3 PID: 0 at 
mm/slab.h:409 kmem_cache_free+0x237/0x2b0
Aug  6 10:16:00 tars kernel: [1058579.764298] Modules linked in: bluetooth 
ecdh_generic ecc ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs cpuid veth 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter 
vhost_net vhost tap xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter bpfilter aufs 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache overlay bridge stp 
llc joydev binfmt_misc uvcvideo v4l2_common videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 videobuf2_common snd_usb_audio videodev snd_usbmidi_lib mc 
intel_rapl_msr nls_iso8859_1 intel_rapl_common isst_if_common skx_edac 
snd_hda_codec_hdmi nfit x86_pkg_temp_thermal intel_powerclamp 
snd_hda_codec_realtek coretemp snd_hda_codec_generic kvm_intel ledtrig_audio 
kvm irqbypass snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm
Aug  6 10:16:00 tars kernel: [1058579.764378]  snd_seq_midi snd_seq_midi_event 
snd_rawmidi snd_seq snd_seq_device snd_timer dell_wmi sparse_keymap 
dell_smm_hwmon snd dell_smbios video intel_cstate dcdbas mei_me input_leds 
intel_rapl_perf mei intel_wmi_thunderbolt dell_wmi_descriptor wmi_bmof 
soundcore serio_raw ioatdma dca nvidia_uvm(POE) mac_hid sch_fq_codel parport_pc 
sunrpc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid uas usb_storage 
nvidia_drm(POE) nvidia_modeset(POE) crct10dif_pclmul crc32_pclmul nvidia(POE) 
ghash_clmulni_intel aesni_intel drm_kms_helper syscopyarea sysfillrect 
sysimgblt aes_x86_64 fb_sys_fops crypto_simd cryptd drm glue_helper 
ipmi_devintf ipmi_msghandler e1000e ahci i2c_i801 libahci wmi
Aug  6 10:16:00 tars kernel: [1058579.764454] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: P   OE 5.3.0-62-generic #56-Ubuntu
Aug  6 10:16:00 tars kernel: [1058579.764456] Hardware name: Dell Inc. 
Precision 5820 Tower/0X8DXD, BIOS 1.9.2 01/24/2019
Aug  6 10:16:00 tars kernel: [1058579.764462] RIP: 
0010:kmem_cache_free+0x237/0x2b0
Aug  6 10:16:00 tars kernel: [1058579.764466] Code: ff ff ff 80 3d b4 e3 56 01 
00 0f 85 39 ff ff ff 48 c7 c6 00 88 25 a0 48 c7 c7 68 cf 55 a0 c6 05 99 e3 56 
01 01 e8 44 d3 df ff <0f> 0b e9 18 ff ff ff 48 8b 57 58 49 8b 4f 58 48 c7 c6 10 
88 25 a0
Aug  6 10:16:00 tars kernel: [1058579.764469] RSP: 0018:9e04c01d8d28 
EFLAGS: 00010282
Aug  6 10:16:00 tars kernel: [1058579.764472] RAX:  RBX: 
8e5b8ef53534 RCX: 
Aug  6 10:16:00 tars kernel: [1058579.764474] RDX: 00040400 RSI: 
00f6 RDI: 0300
Aug  6 10:16:00 tars kernel: [1058579.764477] RBP: 9e04c01d8d50 R08: 
8e60ffed7448 R09: 0004
Aug  6 10:16:00 tars kernel: [1058579.764479] R10:  R11: 
0001 R12: 8e5c0ef53534
Aug  6 10:16:00 tars kernel: [1058579.764481] R13:  R14: 
8e60e7f81a10 R15: 
Aug  6 10:16:00 tars kernel: [1058579.764484] FS:  () 
GS:8e60ffec() knlGS:
Aug  6 10:16:00 tars kernel: [1058579.764486] CS:  0010 DS:  ES:  CR0: 
80050033
Aug  6 10:16:00 tars kernel: [1058579.764488] CR2: 7f8f17c9fe98 CR3: 
0005a600a001 CR4: 003626e0
Aug  6 10:16:00 tars kernel: [1058579.764491] DR0:  DR1: 
 DR2: 
Aug  6 10:16:00 tars kernel: [1058579.764493] DR3:  DR6: 
fffe0ff0 DR7: 0400
Aug  6 10:16:00 tars kernel: [1058579.764494] Call Trace:
Aug  6 10:16:00 tars kernel: [1058579.764497]  
Aug  6 10:16:00 tars kernel: [1058579.764509]  ? sg_free_table_chained+0x30/0x30
Aug  6 10:16:00 tars kernel: [1058579.764514]  mempool_free_slab+0x17/0x20
Aug  6 10:16:00 tars kernel: [1058579.764517]  mempool_free+0x2f/0x80
Aug  6 10:16:00 tars kernel: [1058579.764522]  sg_pool_free+0x4f/0x60
Aug  6 10:16:00 tars kernel: [1058579.764529]  __sg_free_table+0x6f/0x90
Aug  6 10:16:00 tars kernel: [1058579.764534]  sg_free_table_chained+0x27/0x30
Aug  6 10:16:00 tars kernel: [1058579.764544]  scsi_mq_free_sgtables+0x4b/0x50
Aug  6 10:16:00 tars kernel: [1058579.764549]  scsi_mq_uninit_cmd+0x13/0x60
Aug  6 10:16:00 tars kernel: [1058579.764553]  scsi_end_request+0x7e/0x160
Aug  6 10:16:00 tars 

[Kernel-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's

2020-08-06 Thread Edgars Piņķis
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  Invalid

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edgars 1716 F pulseaudio
   /dev/snd/pcmC0D0p:   edgars 1716 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-07 (195 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 2350BH1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETA7WW (2.67 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2350BH1
  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:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2350BH1
  dmi.product.sku: LENOVO_MT_2350
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888390/+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 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all

2020-08-06 Thread Kai-Heng Feng
The installation error should be harmless. Those kernels can be removed
safely.

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

Title:
  [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No sound output. Only a 'Dummy' audio output device is listed in the
  Gnome Sound application.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1205 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 12:12:49 2020
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1205 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CHAPLCEL.0048.2020.0225.1640
  dmi.board.name: NUC8CCHB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K44767-502
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: CH
  dmi.product.name: NUC8CCHK
  dmi.product.sku: BKNUC8CCHKR
  dmi.product.version: K44798-502
  dmi.sys.vendor: Intel(R) Client Systems
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1215 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Intel(R) Client Systems NUC8CCHK
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/25/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CHAPLCEL.0048.2020.0225.1640
  dmi.board.name: NUC8CCHB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K44767-502
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: CH
  dmi.product.name: NUC8CCHK
  dmi.product.sku: BKNUC8CCHKR
  dmi.product.version: K44798-502
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+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 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all

2020-08-06 Thread Kai-Heng Feng
Kamil Sztuke,
Can you please file a new bug? Thanks.

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

Title:
  [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No sound output. Only a 'Dummy' audio output device is listed in the
  Gnome Sound application.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1205 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 12:12:49 2020
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1205 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CHAPLCEL.0048.2020.0225.1640
  dmi.board.name: NUC8CCHB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K44767-502
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: CH
  dmi.product.name: NUC8CCHK
  dmi.product.sku: BKNUC8CCHKR
  dmi.product.version: K44798-502
  dmi.sys.vendor: Intel(R) Client Systems
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1215 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Intel(R) Client Systems NUC8CCHK
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/25/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CHAPLCEL.0048.2020.0225.1640
  dmi.board.name: NUC8CCHB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K44767-502
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: CH
  dmi.product.name: NUC8CCHK
  dmi.product.sku: BKNUC8CCHKR
  dmi.product.version: K44798-502
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+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 1850439] Re: No sound on ASUS UX534FT

2020-08-06 Thread Stéphane Gourichon
Following
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/185
here are instructions that provide a permanent fix.

> ## Next step: have a permanent fix
>
> Some copy-paste instructions as to how to make this fix permanent
> would be appreciated. Else I can figure out some and share,
> e.g. from
> https://askubuntu.com/questions/919054/how-do-i-run-a-single-command-at-startup-using-systemd

Hi all,

This fix works on our machine, where lshw says "ZenBook
UX534FAC_UX533FAC" or simply "UX534FAC".

What we did is start from
https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX534 and adjust for
our machine:

Create `/etc/systemd/system/audio-fix.service` with this content:



[Unit]
Description=Fix internal audio on ASUS Zenbook UX533/534
# The following options are needed to prevent the service from executing before 
the sound card is activated and thus failing
Requires=sys-devices-pci:00-:00:1f.3-sound-card0.device  # replace with 
the result of the previous command 
After=sys-devices-pci:00-:00:1f.3-sound-card0.device # same

[Service]
Type=oneshot
ExecStart=hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf ; hda-verb /dev/snd/hwC0D0 
0x20 0x400 0x7774 ; hda-verb /dev/snd/hwC0D0 0x20 0x500 0x45 ; hda-verb 
/dev/snd/hwC0D0 0x20 0x400 0x5289

[Install]
# Make it part of the sound initialization routine
WantedBy=sound.target




Then issue this commands:



systemctl start audio-fix
systemctl enable audio-fix



You can now reboot to check if the fix works. On our machine, sound
works on speakers and audio jack output, sound is good and we could not
find any trace of the bug.

Thanks in advance to all kernel hackers that can propagate towards
upstream a proper fix (without regression for other users). :-)

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

Title:
  No sound on ASUS UX534FT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  after instal Ubuntu in dual boot alongside Windows 10, I've realised
  there is no sound coming out of mine new ASUS Zenbook 15 UX534FT-
  AA024R in Ubuntu. In Windows there is no problem. Found this topic
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had
  the same problem with driver for Realtek ALC294 which is also mine
  sound card. But even with this fix it is not working on UX534FT. Can
  you please add fix also for this newer model?

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 15:11:25 2019
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1879401] Re: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound rarely works

2020-08-06 Thread Kai-Heng Feng
Probably file an upstream bug at intel graphics upstream:
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs

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

Title:
  [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound
  rarely works

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Ice Lake laptop (Dell 7390 2-in-one) which I am connecting
  to a TV over HDMI via a Novoo USB-C multiport adapter. This is not a
  Thunderbolt device, it is just USB-C.

  It seemed like things used to work fine before I upgraded this system
  from Ubuntu 19.10 to 20.04, although I couldn't say for certain at
  this point. But I'm having a ton of difficulty getting audio output
  over HDMI. Getting it to work requires a lot of retries to
  reinitialize the device (either by suspending/resuming the laptop, or
  plugging/unplugging the HDMI cable and/or the multiport adapter). It
  does work sometimes, but my success rate is very low at this point.

  Even when it does work, it's brittle: any change to the output port
  (to speaker and back to HDMI, or from stereo to surround and back)
  will often break the audio. This fact seems to suggest that the
  problem doesn't have anything to do with the low-level initialization
  of the HDMI port; I'd be looking at some mid-layer code.

  To be clear, there doesn't seem to be any particular symptom, or
  anything of interest in the logs, other than an absence of sound
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Uname: Linux 5.6.0-1010-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nbryant1510 F pulseaudio
   /dev/snd/pcmC0D9p:   nbryant1510 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 17:32:11 2020
  InstallationDate: Installed on 2020-01-31 (108 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog:
   May 18 16:36:42 atlantis dbus-daemon[633]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.41' (uid=124 pid=1116 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   May 18 16:36:53 atlantis systemd[1109]: pulseaudio.service: Succeeded.
   May 18 16:37:03 atlantis systemd[1109]: pulseaudio.socket: Succeeded.
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] fails 
after a while
  UpgradeStatus: Upgraded to focal on 2020-04-21 (27 days ago)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1
  dmi.board.name: 06CDVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd03/02/2020:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nbryant1510 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-31 (108 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 003: ID 8087:0026 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=caffa21a-82f2-4555-a416-67926241525a ro cma=64M 
pcie_aspm.policy=powersupersave drm.vblankoffdelay=1 video=1600x1200 
mem_sleep_default=deep
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1010-oem N/A
   linux-backports-modules-5.6.0-1010-oem  N/A
   

[Kernel-packages] [Bug 1890507] Re: touchad not working

2020-08-06 Thread Kai-Heng Feng
Was any kernel older than 5.4.0-42 in use?

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1890507

Title:
  touchad not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Touchpad stopped working about a week ago. Now using a bluetooth mouse
  which pauses somethimes.  Computer is a Acer Aspire 5.  Just bought it
  a month ago.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bandito1342 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 20:10:55 2020
  InstallationDate: Installed on 2020-07-06 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:0c03 Elan Microelectronics Corp. ELAN:Fingerprint
   Bus 001 Device 002: ID 0408:a061 Quanta Computer, Inc. HD User Facing
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-55
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=0db45a53-e15e-4543-b00b-357af7cbc296 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Doc_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd02/26/2020:svnAcer:pnAspireA515-55:pvrV1.04:rvnIL:rnDoc_IL:rvrV1.04:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-55
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890507/+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 1805670] Re: 18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues ex. suspend, touchpad

2020-08-06 Thread Kai-Heng Feng
Please try "safe graphics" boot option.

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

Title:
  18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues
  ex. suspend, touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Some background information:
  I have a new Ubuntu 18.04 installation that did not go too well.
  The Live-USB installation would hang with ACPi related errors.
  I finally installed (barring a GRUB install error) using the acpi=off kernel 
flag.
  I also tested with acpi=force and no acpi settings (only worked after the 
last kernel update).
  I report here with
  - no changes in the kernel parameters
  - no changes in BIOS except of graphics set to hybrid (Nvidia + Intel) 
otherwise I could not get it to work

  I am following the indications here:
  https://wiki.ubuntu.com/DebuggingACPI

  So here is the initial information I have (kernel version, kernel
  parameters, ACPI errors):

  ..

  uname -a
  Linux gandalf 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=82d8b6b9-1f12-4651--3639a6b76683 ro quiet splash vt.handoff=1

  dmesg | grep -i acpi | grep -i error
  [0.00] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup 
failure, AE_NOT_FOUND (20170831/dswload-210)
  [0.00] ACPI Error: 1 table load failures, 19 successful 
(20170831/tbxfload-246)
  [0.164845] ACPI Error: Field [CAP1] at bit offset/length 64/32 exceeds 
size of target Buffer (64 bits) (20170831/dsopcode-235)
  [0.164874] ACPI Error: Method parse/execution failed \_SB._OSC, 
AE_AML_BUFFER_LIMIT (20170831/psparse-550)
  [3.528032] ACPI Error: Method parse/execution failed 
\_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550)
  [3.528042] ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103)
  [3.529831] ACPI Error: Method parse/execution failed 
\_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550)
  [3.529840] ACPI Error: Method execution failed \_SB.PCI0.SPI2.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103)
  [4.610629] ACPI Error: Method parse/execution failed \_TZ.GETP, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.610635] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.611513] ACPI Error: Method parse/execution failed \_TZ.GETP, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.611518] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [8.206279] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
85bce4f4 (20170831/exresop-593)
  [8.206309] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.206315] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.210629] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
352a9487 (20170831/exresop-593)
  [8.210660] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.210666] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.214527] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
88ce12bb (20170831/exresop-593)
  [8.214555] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.214562] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.231122] ACPI Error: Attempt to CreateField of length zero 
(20170831/dsopcode-168)
  [8.231147] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPI, 
AE_AML_OPERAND_VALUE (20170831/psparse-550)
  [8.231154] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_VALUE (20170831/psparse-550)

  ..

  I have also added the following outputs:

  sudo lspci -vvnn >> report.txt

  sudo dmidecode > dmidecode.txt

  The kern.log after a suspend and resume.

  

  Some weird behavior I have noticed:

  . The Live-USB pendrive allowed me to use the touchpad when testing and 
installing Ubuntu
  . The current kernel does not allow me to use the touchpad
  . After I resume, the touchpad can be used
  . I cannot resume with the builtin At keyboard or touchpad
  . The dock (via Thunderbolt) gives me access to a mouse and keyboard that I 
use to resume
  . I have related graphics driver issue but do not know if they are related

  Is their anything 

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

2020-08-06 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 1890603

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

** Tags added: focal

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

Title:
  'Elantech Touchpad'  not detected in 'ASUS N61VN' after fresh install
  of focal fossa

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The subject says it all.

  I follow the instruction from
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  Thanks for reading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890603/+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 1890603] [NEW] 'Elantech Touchpad' not detected in 'ASUS N61VN' after fresh install of focal fossa

2020-08-06 Thread Humberto Pinto
Public bug reported:

The subject says it all.

I follow the instruction from
https://wiki.ubuntu.com/DebuggingTouchpadDetection

Thanks for reading.

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

** Attachment added: "devices"
   https://bugs.launchpad.net/bugs/1890603/+attachment/5399306/+files/devices

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

Title:
  'Elantech Touchpad'  not detected in 'ASUS N61VN' after fresh install
  of focal fossa

Status in linux package in Ubuntu:
  New

Bug description:
  The subject says it all.

  I follow the instruction from
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  Thanks for reading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890603/+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 1889780] UdevDb.txt

2020-08-06 Thread Dave Dave
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1889780/+attachment/5399303/+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/1889780

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: 

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

2020-08-06 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To 

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

2020-08-06 Thread Dave Dave
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1889780/+attachment/5399304/+files/WifiSyslog.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/1889780

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  

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

2020-08-06 Thread Dave Dave
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1889780/+attachment/5399301/+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/1889780

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  

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

2020-08-06 Thread Dave Dave
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1889780/+attachment/5399299/+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/1889780

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  

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

2020-08-06 Thread Dave Dave
apport information

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

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Kernel-packages] [Bug 1889780] ProcCpuinfo.txt

2020-08-06 Thread Dave Dave
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1889780/+attachment/5399297/+files/ProcCpuinfo.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/1889780

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  

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

2020-08-06 Thread Dave Dave
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1889780/+attachment/5399302/+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/1889780

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  

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

2020-08-06 Thread Dave Dave
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1889780/+attachment/5399300/+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/1889780

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  

[Kernel-packages] [Bug 1889780] Lsusb.txt

2020-08-06 Thread Dave Dave
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1889780/+attachment/5399287/+files/Lsusb.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/1889780

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To 

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

2020-08-06 Thread Dave Dave
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1889780/+attachment/5399283/+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/1889780

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be 

[Kernel-packages] [Bug 1889780] IwConfig.txt

2020-08-06 Thread Dave Dave
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1889780/+attachment/5399285/+files/IwConfig.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/1889780

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  

[Kernel-packages] [Bug 1889780] Re: Unable to change screen resolution after upgrade to 5.4.0-42-generic

2020-08-06 Thread Dave Dave
apport information

** Description changed:

   When booting using 5.4.0-42-generic kernel, screen resolution is fixed
  at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.
  
  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.
  
  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4
  
  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?
  
   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.15
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dave   2639 F pulseaudio
+  /dev/snd/controlC1:  dave   2639 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-02-27 (161 days ago)
+ InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
+ MachineType: System manufacturer System Product Name
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
+ ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-42-generic N/A
+  linux-backports-modules-5.4.0-42-generic  N/A
+  linux-firmware1.173.19
+ RfKill:
+  
+ Tags:  bionic
+ Uname: Linux 5.4.0-42-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/18/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 2801
+ dmi.board.asset.tag: Default string
+ dmi.board.name: ROG STRIX B450-F GAMING
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: System Product Name
+ dmi.product.sku: SKU
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1889780/+attachment/5399282/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

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

2020-08-06 Thread Dave Dave
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1889780/+attachment/5399284/+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/1889780

Title:
  Unable to change screen resolution after upgrade to 5.4.0-42-generic

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   When booting using 5.4.0-42-generic kernel, screen resolution is
  fixed at 640x480 and there is no way to change it. Booting using
  5.3.0-62-generic works fine.

  In "Displays", the dropdowns for Resolution only has 640x480 for
  selection. For Refresh Rate and Rotation there are no selections under
  dropdown.

  OS - 18.04 LTS
  Kernel - 5.4.0-42 previous 5.3.0-62-generic
  Dell Monitor
  NVIDIA GeForce GT 1030
  CPU is AMD Ryzen 5 2600 X Socket AM4

  Questions:
   How will I find out that this bug has been fixed?
   I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU 
work or are there specific video cards I should look at?
   Is there a site that recommends video cards for Linux?

   Thanks,
Dave
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2495 F pulseaudio
   /dev/snd/controlC1:  dave   2495 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (158 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-62-generic N/A
   linux-backports-modules-5.3.0-62-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2639 F pulseaudio
   /dev/snd/controlC1:  dave   2639 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-27 (161 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.173.19
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  

[Kernel-packages] [Bug 1890436] Re: VGA signal is ghosted and stretched (Intel® HD Graphics 2500)

2020-08-06 Thread Ioannis Barkas
Well this is a PC with onboard intel graphics. A memory issue would mean
RAM problem which is not the case here. I can see a visual corruption.
If you can't see it then there is nothing more to say here.

You are welcomed to see the dmesg and figure out what happens. There is
no hardware damage on my PC. This occurs with a specific BIOS setting as
I described above and it affects only ubuntu. Windows 10 2004 work fine
on my "damaged" PC. If you wish to get a screenshot from windows working
fine, I can upload it here.

I might test wayland at the evening but linux kernel detects the problem
and shouts about underrun error in FIFO A as the first attached image
with dmesg shows. So if you have anything usefull to write that is
related to this bug report, please do so. If you just continue to say
that my hardware is damaged you are free to close this bug right away. I
will try another distro and open another bug there...

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

Title:
  VGA signal is ghosted and stretched (Intel® HD Graphics 2500)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 

[Kernel-packages] [Bug 1885266] Re: Intel Wireless-AC 9260 [8086:2526] Subsystem [8086:0014] iwlwifi causes random UI freezes

2020-08-06 Thread d
I wish I could place a date on when the issues started. My guess is that
it was either late May or early June. The issue happens quite frequently
in the last updates and now I get sometimes a black screen on the laptop
while the external monitor remains working. A restart of the system
brings things back to work but the freezes quite happening maybe even
more frequently now.

I will try the mainline kernel and report results. The list of kernels I
had in the system as per your command is below.

I would say that version 5.4.0-29 was definitely working fine and that
it was one of the 5.4.0-3x release that started the problem.

Aug 03 22:01:02 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Aug 01 06:52:50 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 29 09:48:41 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 26 10:15:00 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 24 13:44:02 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 23 08:11:18 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 21 08:15:04 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 15 17:41:07 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 14 08:33:03 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 11 13:24:59 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 10 07:46:22 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 08 08:04:09 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 05 12:58:30 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 03 08:41:41 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jul 02 16:08:33 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-39-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jun 26 10:49:52 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-39-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro modprobe.blacklist=nouveau
Jun 26 09:57:03 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-39-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro
Jun 25 21:53:56 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-39-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro
Jun 20 18:15:04 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro
Jun 18 11:35:43 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro
Jun 16 18:26:37 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_dd5xf4@/vmlinuz-5.4.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_dd5xf4 ro
Jun 15 16:43:07 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_x13bv2@autozsys_1kiv8w/vmlinuz-5.4.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_x13bv2@autozsys_1kiv8w ro
Jun 15 06:45:14 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_x13bv2@/vmlinuz-5.4.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_x13bv2 ro
Jun 12 14:25:05 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_w5d0b7@autozsys_x65hvt/vmlinuz-5.4.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_w5d0b7@autozsys_x65hvt ro
Jun 11 13:14:30 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_w5d0b7@/vmlinuz-5.4.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_w5d0b7 ro
Jun 08 21:27:44 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_w5d0b7@/vmlinuz-5.4.0-33-generic 
root=ZFS=rpool/ROOT/ubuntu_w5d0b7 ro
Jun 01 20:50:11 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_w5d0b7@/vmlinuz-5.4.0-33-generic 
root=ZFS=rpool/ROOT/ubuntu_w5d0b7 ro
May 31 13:00:17 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_w5d0b7@/vmlinuz-5.4.0-33-generic 
root=ZFS=rpool/ROOT/ubuntu_w5d0b7 ro
May 28 10:52:58 kernel: Command line: 
BOOT_IMAGE=/BOOT/ubuntu_v46mn6@/vmlinuz-5.4.0-33-generic 

[Kernel-packages] [Bug 1885266] Re: Intel Wireless-AC 9260 [8086:2526] Subsystem [8086:0014] iwlwifi causes random UI freezes

2020-08-06 Thread d
The link you sent says:

>Note: If you are testing to isolate a bug or regression, please do not use the 
>daily folder.
>Instead, use the latest mainline kernel at the top from the link above. 

Could you clarify if you want me to test the latest mainline kernel
(5.8) or the latest in the 5.4?

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

Title:
  Intel Wireless-AC 9260 [8086:2526] Subsystem [8086:0014] iwlwifi
  causes random UI freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The GUI randomly freezes around every 10-15 minutes. This last for
  about 15-20 seconds before it gets back to normal.

  It started a few weeks ago. I can see entries in dmesg when this
  happens that make me suspect that it is caused by iwlwifi and/or a
  related driver of the Intel Wireless-AC 9260.

  
  [ 2313.312937] [ cut here ]
  [ 2313.312941] Timeout waiting for hardware access (CSR_GP_CNTRL 0x0c04000c)
  [ 2313.312995] WARNING: CPU: 4 PID: 1424 at 
drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2066 
iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi]
  [ 2313.312996] Modules linked in: ccm rfcomm xfrm_user xfrm_algo cmac 
algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi 
snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda 
snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek 
snd_compress snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine 
snd_hda_intel iwlmvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep 
mac80211 snd_pcm snd_seq_midi mei_hdcp libarc4 intel_rapl_msr 
snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp snd_rawmidi kvm_intel 
kvm uvcvideo snd_seq intel_cstate iwlwifi intel_rapl_perf videobuf2_vmalloc 
btusb btrtl videobuf2_memops snd_seq_device btbcm snd_timer videobuf2_v4l2 
joydev btintel serio_raw bluetooth ucsi_ccg wmi_bmof videobuf2_common 
rtsx_pci_ms videodev snd typec_ucsi cfg80211 mc input_leds mxm_wmi mei_me 
memstick typec ecdh_generic mei soundcore ecc
  [ 2313.313022]  processor_thermal_device intel_rapl_common intel_soc_dts_iosf 
intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal 
intel_hid mac_hid acpi_thermal_rel sparse_keymap acpi_pad nvidia_uvm(OE) 
nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common 
ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp sch_fq_codel 
xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c 
ip6table_filter coretemp parport_pc ip6_tables iptable_filter ppdev bpfilter lp 
parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) 
zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_apple hid_generic usbhid hid 
nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel i915 i2c_algo_bit rtsx_pci_sdmmc aesni_intel drm_kms_helper 
crypto_simd syscopyarea sysfillrect cryptd uas sysimgblt glue_helper 
fb_sys_fops psmouse intel_lpss_pci rtsx_pci r8169 intel_lpss drm i2c_i801 ahci 
ipmi_devintf usb_storage
  [ 2313.313053]  realtek idma64 libahci virt_dma ipmi_msghandler 
i2c_nvidia_gpu pinctrl_cannonlake wmi video pinctrl_intel
  [ 2313.313059] CPU: 4 PID: 1424 Comm: irq/149-iwlwifi Tainted: P   OE 
5.4.0-39-generic #43-Ubuntu
  [ 2313.313060] Hardware name: TUXEDO TUXEDO/P95_96_97Ex,Rx, BIOS 1.07.13RTR2 
10/16/2019
  [ 2313.313068] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1f9/0x230 [iwlwifi]
  [ 2313.313070] Code: e5 fb 49 8d 57 08 bf 00 20 00 00 e8 a1 f1 6c fa e9 30 ff 
ff ff 89 c6 48 c7 c7 30 91 61 c2 c6 05 15 e2 02 00 01 e8 02 f7 6a fa <0f> 0b e9 
eb fe ff ff 49 8b 7c 24 38 48 c7 c1 98 91 61 c2 31 d2 31
  [ 2313.313071] RSP: 0018:be8e67d4fc98 EFLAGS: 00010082
  [ 2313.313073] RAX:  RBX: be8e67d4fcd0 RCX: 
0006
  [ 2313.313073] RDX: 0007 RSI: 0082 RDI: 
96d9903178c0
  [ 2313.313074] RBP: be8e67d4fcc0 R08: 04bb R09: 
0004
  [ 2313.313075] R10:  R11: 0001 R12: 
96d95de38018
  [ 2313.313076] R13:  R14: 96d95de39e4c R15: 
0c04000c
  [ 2313.313077] FS:  () GS:96d99030() 
knlGS:
  [ 2313.313078] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2313.313079] CR2: 2d587263b000 CR3: 000387a0a006 CR4: 
003606e0
  [ 2313.313080] Call Trace:
  [ 2313.313089]  iwl_trans_pcie_read_mem+0x42/0xc0 [iwlwifi]
  [ 2313.313099]  iwl_mvm_dump_lmac_error_log+0xdd/0x570 [iwlmvm]
  [ 2313.313103]  ? __dev_printk+0x5c/0x6f
  [ 2313.313106]  ? _dev_err+0x6c/0x83
  [ 2313.313110]  ? stop_one_cpu+0x73/0xa0
  [ 2313.313118]  iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm]
  [ 2313.313124]  

[Kernel-packages] [Bug 1812620] Re: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed

2020-08-06 Thread Colin Ian King
Fix sent to mailing list:

https://lists.ubuntu.com/archives/kernel-team/2020-August/112505.html
https://lists.ubuntu.com/archives/kernel-team/2020-August/112506.html

** Description changed:

+ == SRU Justification [ FOCAL ] ==
+ 
+ The msg_zerocopy.sh kernel self test will fail on machines that don't
+ have 2 or 3 CPUs such as 1 CPU cloud instances since the C test program
+ tries to set CPU affinity to CPUs 2 and 3 and bails out if it fails.
+ 
+ == Fix ==
+ 
+ Upstream linux-next commit
+ 
+ commit 16f6458f2478b55e2b628797bc81a4455045c74e
+ Author: Willem de Bruijn 
+ Date:   Wed Aug 5 04:40:45 2020 -0400
+ 
+ selftests/net: relax cpu affinity requirement in msg_zerocopy test
+ 
+ The fix now just emits a warning that CPU affinity can't be set rather
+ than cause an exit(1) termination.
+ 
+ == Test cast ==
+ 
+ Run the msg_zerocopy.sh test from the kernel net selftest on a 1 CPU
+ system. Without the fix the test fails. With the fix it runs
+ successfully as expected.
+ 
+ == Regression Potential ==
+ 
+ The original test pinned the CPUs for a benchmarking metric, for our
+ testing we are using this to test to see if the operations in the test
+ work successfully.  There is a potential that users using this test will
+ not notice the warning if they are using this test as a benchmark on a 1
+ CPU system and may get more jittery timing in their benchmarks rather
+ than a test failing and complaining they are not running it on a
+ suitable multi-CPU system.  However, the likelyhood of a user using this
+ test on a single CPU system for benchmarking is small and as it stands
+ the test will now run and produce potentially jittery benchmarks on a 1
+ CPU system compared to previously where it never ran.
+ 
+ 
+ 
  This test will return 1
  
- $ sudo ./msg_zerocopy.sh 
+ $ sudo ./msg_zerocopy.sh
  ipv4 tcp -t 1
  ./msg_zerocopy: setaffinity 2
  ./msg_zerocopy: setaffinity 3
  $ echo $?
  1
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Jan 21 07:41 seq
-  crw-rw 1 root audio 116, 33 Jan 21 07:41 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Jan 21 07:41 seq
+  crw-rw 1 root audio 116, 33 Jan 21 07:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jan 21 07:50:33 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
-  
+ 
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
  RelatedPackageVersions:
-  linux-restricted-modules-4.18.0-13-generic N/A
-  linux-backports-modules-4.18.0-13-generic  N/A
-  linux-firmware 1.175.1
+  linux-restricted-modules-4.18.0-13-generic N/A
+  linux-backports-modules-4.18.0-13-generic  N/A
+  linux-firmware 1.175.1
  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/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

** Changed in: linux (Ubuntu Eoan)
   Status: New => Won't Fix

** Changed in: linux-aws (Ubuntu Eoan)
   Status: New => Won't Fix

** Changed in: linux-azure (Ubuntu Eoan)
   Status: New => Won't Fix

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

Title:
  msg_zerocopy.sh in net from ubuntu_kernel_selftests failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Disco:
  Won't Fix
Status in linux-aws source package in Disco:
  Won't Fix
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix
Status in linux-aws 

[Kernel-packages] [Bug 306003] Re: smartctl short test hangs at 90%

2020-08-06 Thread Aleksey Shcherbina
I confirm this bug for Ubuntu 20.04 LTS, gnome-disk-utility and Hitachi
HUH721010ALE604 10 TB HDD (FW ver. LHGNW384).

** Changed in: linux (Ubuntu)
   Status: Expired => 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/306003

Title:
  smartctl short test hangs at 90%

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It seems that after upgrading to 8.04 smartctl short test seems to
  hang at 90% (ie it never finishes).

  The following test hangs at 90%:

  sudo smartctl -t short /dev/sda

  Output from smartcrl -a /dev/sda
   

  Self-test execution status:  ( 249)   Self-test routine in progress...
90% of test remaining.

  according to this report
  http://smartmontools.markmail.org/message/afuajgivzxhjjgzd?q=test+90%25
  a recent kernel fixed it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/306003/+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 1805670] Re: 18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues ex. suspend, touchpad

2020-08-06 Thread Pierre
Hi!

Same problem with HP ZBook G6 15.
Latest BIOS 1.05
Ubuntu 20.04.1 LTS 
The problem occurs with kernel 5.4.0.42 but not with the previous version 
5.4.0.26.
Only workaround that works with me is acpi=off as boot parameter.

Regards

Pierre

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

Title:
  18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues
  ex. suspend, touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Some background information:
  I have a new Ubuntu 18.04 installation that did not go too well.
  The Live-USB installation would hang with ACPi related errors.
  I finally installed (barring a GRUB install error) using the acpi=off kernel 
flag.
  I also tested with acpi=force and no acpi settings (only worked after the 
last kernel update).
  I report here with
  - no changes in the kernel parameters
  - no changes in BIOS except of graphics set to hybrid (Nvidia + Intel) 
otherwise I could not get it to work

  I am following the indications here:
  https://wiki.ubuntu.com/DebuggingACPI

  So here is the initial information I have (kernel version, kernel
  parameters, ACPI errors):

  ..

  uname -a
  Linux gandalf 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=82d8b6b9-1f12-4651--3639a6b76683 ro quiet splash vt.handoff=1

  dmesg | grep -i acpi | grep -i error
  [0.00] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup 
failure, AE_NOT_FOUND (20170831/dswload-210)
  [0.00] ACPI Error: 1 table load failures, 19 successful 
(20170831/tbxfload-246)
  [0.164845] ACPI Error: Field [CAP1] at bit offset/length 64/32 exceeds 
size of target Buffer (64 bits) (20170831/dsopcode-235)
  [0.164874] ACPI Error: Method parse/execution failed \_SB._OSC, 
AE_AML_BUFFER_LIMIT (20170831/psparse-550)
  [3.528032] ACPI Error: Method parse/execution failed 
\_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550)
  [3.528042] ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103)
  [3.529831] ACPI Error: Method parse/execution failed 
\_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550)
  [3.529840] ACPI Error: Method execution failed \_SB.PCI0.SPI2.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103)
  [4.610629] ACPI Error: Method parse/execution failed \_TZ.GETP, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.610635] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.611513] ACPI Error: Method parse/execution failed \_TZ.GETP, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.611518] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [8.206279] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
85bce4f4 (20170831/exresop-593)
  [8.206309] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.206315] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.210629] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
352a9487 (20170831/exresop-593)
  [8.210660] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.210666] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.214527] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
88ce12bb (20170831/exresop-593)
  [8.214555] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.214562] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.231122] ACPI Error: Attempt to CreateField of length zero 
(20170831/dsopcode-168)
  [8.231147] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPI, 
AE_AML_OPERAND_VALUE (20170831/psparse-550)
  [8.231154] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_VALUE (20170831/psparse-550)

  ..

  I have also added the following outputs:

  sudo lspci -vvnn >> report.txt

  sudo dmidecode > dmidecode.txt

  The kern.log after a suspend and resume.

  

  Some weird behavior I have noticed:

  . The Live-USB pendrive allowed me to use the touchpad when testing and 
installing Ubuntu
  . The current kernel does not allow me to use the touchpad
  . After I resume, the touchpad can be used
  . I cannot resume with the builtin At keyboard or 

[Kernel-packages] [Bug 1890436] Re: VGA image is ghosted and stretched

2020-08-06 Thread Daniel van Vugt
"corruption" to me would mean a problem in graphics memory. That's not
what I am seeing in your photos. Your photos seem to show the graphics
memory fully intact and some kind of analog VGA signalling problem.
Which unfortunately means the Linux kernel might not be aware of the
problem.

Still, as a workaround please try selecting 'Ubuntu on Wayland' from the
login screen.

** Summary changed:

- VGA image is ghosted and stretched (LG L1953S)
+ VGA image is ghosted and stretched

** Summary changed:

- VGA image is ghosted and stretched
+ VGA signal is ghosted and stretched (Intel® HD Graphics 2500)

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

Title:
  VGA signal is ghosted and stretched (Intel® HD Graphics 2500)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Kernel-packages] [Bug 1890436] Re: VGA signal is ghosted and stretched (Intel® HD Graphics 2500)

2020-08-06 Thread Daniel van Vugt
It might be that there's some minor damage to the VGA port on the
machine. It might be so minor you can't even see it :(

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

Title:
  VGA signal is ghosted and stretched (Intel® HD Graphics 2500)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1835660] Re: initramfs unpacking failed

2020-08-06 Thread Pjotr12345
This is a simplified version of the means to work around this problem:

Step 1:
sudo sed -i 's/COMPRESS=lz4/COMPRESS=gzip/g' /etc/initramfs-tools/initramfs.conf

Step 2:
sudo update-initramfs -u

Step 3:
Reboot.

Now I wonder whether someone has already tried something other than gzip? 
Because initramfs.conf mentions no less than six options:
# COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz ]

Apparently gzip is slower than lz4, which might slow the boot process by
several seconds. One of the other alternatives might be faster.

Of course I could test that myself, but I'm too lazy today, so I'm
hoping somebody else has done the footwork already

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)

2020-08-06 Thread Ioannis Barkas
** Attachment added: "Cursor corruption at VGA#2(same seen at VGA#1)"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399180/+files/new-VGA-cursor-29.jpg

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

Title:
  VGA image is ghosted and stretched (LG L1953S)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1890436] Re: VGA image is ghosted and stretched (LG L1953S)

2020-08-06 Thread Ioannis Barkas
** Attachment added: "Corruption of welcoming screen at VGA#2"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399179/+files/new-VGA-50.jpg

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

Title:
  VGA image is ghosted and stretched (LG L1953S)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)

2020-08-06 Thread Ioannis Barkas
-- 
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/1890436

Title:
  VGA image is ghosted and stretched (LG L1953S)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)

2020-08-06 Thread Ioannis Barkas
** Attachment added: "Corrupted font display at VGA#1"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399175/+files/bad-VGA-22b.jpg

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

Title:
  VGA image is ghosted and stretched (LG L1953S)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)

2020-08-06 Thread Ioannis Barkas
** Attachment added: "X log with DP and VGA#2 monitors"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399181/+files/Xorg.log

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

Title:
  VGA image is ghosted and stretched (LG L1953S)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)

2020-08-06 Thread Ioannis Barkas
** Attachment added: "Corruption of home folder at VGA#2"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399178/+files/new-VGA-16.jpg

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

Title:
  VGA image is ghosted and stretched (LG L1953S)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)

2020-08-06 Thread Ioannis Barkas
** Attachment added: "Normal font display at DP"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399173/+files/good-DP-01b.jpg

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

Title:
  VGA image is ghosted and stretched (LG L1953S)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)

2020-08-06 Thread Ioannis Barkas
** Attachment added: "Corrupted font display at VGA#2"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890436/+attachment/5399176/+files/bad-VGA-48b.jpg

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

Title:
  VGA image is ghosted and stretched (LG L1953S)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)

2020-08-06 Thread Ioannis Barkas
Hello, thank you for your early reply! I am afraid that you haven't got
the big picture here. On my side, there is no doubt that I am getting a
visual corruption. Just take a look at the attached images.

The video signal is good since the monitor works normal when I enable
CSM setting in BIOS. As you have suggested, I used a different VGA cable
having double thickness than the initial one and I am still getting the
same behaviour. If it was a signalling issue the kernel would probably
not print any warning messages.

Since I have another VGA monitor on my desk, I went a step ahead and
connected this VGA monitor instead since I hadn't tested this case with
that monitor. As expected, I got exactly the same behaviour. That is
smooth display on VGA monitor when CSM is enabled and corruption when
CSM is disabled. As a proof of it, I am uploading images from the third
monitor. Take a closer look at the cursor as it has blank lines after
each horizontal line. As you can see, the same applies to fonts when
switching to console view. I am also uploading the X log with that
monitor.

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

Title:
  VGA image is ghosted and stretched (LG L1953S)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

  To get an idea about the hardware, the Lenovo machine isn't running
  the latest BIOS as its updater is broken and won't update it within
  win or its ISO image. It uses the previous version released by its
  manufacturer.

  The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
  Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

  As I have seen on other bug reports, I have enabled DRM debug,
  captured the dmesg using a huge buffer to get it and have uploaded it
  as well. I hope that it will help you track this issue down and fix it
  soon. Since I will be away some days for vacation, I will have
  physical access to it till this Friday and will get back to work at
  the 24th of August. In the mean time, I hope that someone will
  pinpoint the root cause of it and prepare a patch.

  Since this machine is running w10 2004, it should be noted that in win
  I do not get any corruption at all either in CSM mode or UEFI mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:30:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 3209C54
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9BAUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3209C54
  dmi.product.sku: LENOVO_MT_3209
  dmi.product.version: 

[Kernel-packages] [Bug 1890415] Re: Lenovo ThinkPad X390 won’t boot while plugged in

2020-08-06 Thread Matej
Thanks for your help. But I have installed Bios N2LET76W 1.76 (you can
see it in bug description too) and I have the same problem. :-(

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

Title:
  Lenovo ThinkPad X390 won’t boot while plugged in

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello. I’m using Lenovo ThinkPad X390 Yoga (model type: 20NN002NMC). I have 
been using dual boot of the preinstalled Windows 10 x64 and Linux. I have tried 
the latest versions of Ubuntu and Debian. About 6 weeks ago, after updating the 
BIOS to N2LET76W 1.75 (https://download.lenovo.com/pccbbs/mobiles/n2lur14w.txt) 
and the Intel Management Engine Firmware (12.0.67.1579), an issue arose.
  When I boot to Ubuntu 20.04.1 (kernel 5.4.0-42-generic) using the Grub 
bootloader with active Secure Boot (fully supported), and then I turn the 
notebook off or restart it in Ubuntu, it won’t turn back on – it won’t POST, 
the screen is black, etc. After that time, I need to unplug the notebook from 
the power adapter, or remove it from the dock, and it will boot on battery. But 
it won’t boot while plugged in until it boots into Windows and is turned 
off/restart from it. After booting to Windows, it works fine while plugged in, 
until it is turned off in Ubuntu again. I have tried install recommend drivers 
and software..
  It looks like a BIOS/Firmware error related to power management. I’m using 
the latest BIOS/Firmware updated via the official Lenovo software – Lenovo 
Vantage (bios version 1.76). Notebook was sent to Lenovo for repairs, the 
motherboard was replaced, yet the problem persists – hence thinking it’s 
BIOS/Firmware related.
  Lenovo claims it’s Linux’s issue, even though the list it as officially 
supported (https://support.lenovo.com/sk/en/solutions/pd031426) and there refer 
me to the community. Lenovo stuff inform me too, that this issue may be related 
to requirements Windows 10 v2004.
  Many thanks for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mato   1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:36:45 2020
  InstallationDate: Installed on 2020-08-02 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20NN002NMC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sk_SK.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ca486d67-1377-47fb-93c3-cfb279657f9d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2LET76W (1.76 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NN002NMC
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2LET76W(1.76):bd06/16/2020:svnLENOVO:pn20NN002NMC:pvrThinkPadX390Yoga:rvnLENOVO:rn20NN002NMC:rvr0B98417WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X390 Yoga
  dmi.product.name: 20NN002NMC
  dmi.product.sku: LENOVO_MT_20NN_BU_Think_FM_ThinkPad X390 Yoga
  dmi.product.version: ThinkPad X390 Yoga
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890415/+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 1890487] Re: rpi3b+ wifi doesn't get used if ethernet disconnected

2020-08-06 Thread Juerg Haefliger
** Package changed: linux-raspi2 (Ubuntu) => linux-raspi (Ubuntu)

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

** Changed in: linux-raspi (Ubuntu)
   Status: New => Invalid

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

Title:
  rpi3b+ wifi doesn't get used if ethernet disconnected

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Focal:
  New

Bug description:
  When testing 20.04.1, I noticed some different behavior on rpi3b+ that
  I didn't see on rpi3b or rpi4.  I have configured the device with
  ethernet, added netplan yaml for my wifi network, and rebooted. So
  both eth0 and wlan0 have an ip address.

  On all other devices (rpi3b, rpi4, etc), if I unplug eth0 wile pinging
  something, I'll miss maybe 1 ping and then it will continue to work
  and just switch over to wlan0.  However, on rpi3b+ it just stops being
  able to access the network completely.  If I re-run netplan apply, it
  will start using wifi again, but if I plug eth0 back in, then unplug
  it, it stops just like before.

  I am seeing this with the current 20.04.1 release:
  Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

  I also went back and tested the original 20.04 release and it happens there 
too, so this is not a regression:
  Linux ubuntu 5.4.0-1008-raspi #8-Ubuntu SMP Wed Apr 8 11:13:06 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

  I see this happen on both armhf and arm64. One difference I did note, is that 
I get a link down message in dmesg on rpi3b, but not rpi3b+.  When I disconnect 
eth0 on rpi3b I see this:
  [   82.203702] smsc95xx 1-1.1:1.0 eth0: link down

  ...but nothing on the 3b+.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1890487/+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 1890415] Re: Lenovo ThinkPad X390 won’t boot while plugged in

2020-08-06 Thread AaronMa
The changelog contains several fix for hang at BIOS post:

- (Fix) Fixed an issue where system might hang at POST when attach USB C to 
DisplayPort
Adapter cable.
- (Fix) Fixed an issue where WWAN device firmware update process might fail when
Thunderbolt BIOS Assist Mode is set to Enabled.
- (Fix) Fixed an issue where system might hang at POST when USB Type-C Dock 
Gen2 is attached.
- (Fix) Fixed an issue where Accelerometer initialization might fail.
- (Fix) Fixed an issue where warning message might display at POST when TPM is 
disabled.

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

Title:
  Lenovo ThinkPad X390 won’t boot while plugged in

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello. I’m using Lenovo ThinkPad X390 Yoga (model type: 20NN002NMC). I have 
been using dual boot of the preinstalled Windows 10 x64 and Linux. I have tried 
the latest versions of Ubuntu and Debian. About 6 weeks ago, after updating the 
BIOS to N2LET76W 1.75 (https://download.lenovo.com/pccbbs/mobiles/n2lur14w.txt) 
and the Intel Management Engine Firmware (12.0.67.1579), an issue arose.
  When I boot to Ubuntu 20.04.1 (kernel 5.4.0-42-generic) using the Grub 
bootloader with active Secure Boot (fully supported), and then I turn the 
notebook off or restart it in Ubuntu, it won’t turn back on – it won’t POST, 
the screen is black, etc. After that time, I need to unplug the notebook from 
the power adapter, or remove it from the dock, and it will boot on battery. But 
it won’t boot while plugged in until it boots into Windows and is turned 
off/restart from it. After booting to Windows, it works fine while plugged in, 
until it is turned off in Ubuntu again. I have tried install recommend drivers 
and software..
  It looks like a BIOS/Firmware error related to power management. I’m using 
the latest BIOS/Firmware updated via the official Lenovo software – Lenovo 
Vantage (bios version 1.76). Notebook was sent to Lenovo for repairs, the 
motherboard was replaced, yet the problem persists – hence thinking it’s 
BIOS/Firmware related.
  Lenovo claims it’s Linux’s issue, even though the list it as officially 
supported (https://support.lenovo.com/sk/en/solutions/pd031426) and there refer 
me to the community. Lenovo stuff inform me too, that this issue may be related 
to requirements Windows 10 v2004.
  Many thanks for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mato   1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:36:45 2020
  InstallationDate: Installed on 2020-08-02 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20NN002NMC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sk_SK.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ca486d67-1377-47fb-93c3-cfb279657f9d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2LET76W (1.76 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NN002NMC
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2LET76W(1.76):bd06/16/2020:svnLENOVO:pn20NN002NMC:pvrThinkPadX390Yoga:rvnLENOVO:rn20NN002NMC:rvr0B98417WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X390 Yoga
  dmi.product.name: 20NN002NMC
  dmi.product.sku: LENOVO_MT_20NN_BU_Think_FM_ThinkPad X390 Yoga
  dmi.product.version: ThinkPad X390 Yoga
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890415/+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 1890415] Re: Lenovo ThinkPad X390 won’t boot while plugged in

2020-08-06 Thread AaronMa
https://pcsupport.lenovo.com/sk/en/products/laptops-and-
netbooks/thinkpad-x-series-laptops/thinkpad-x390-yoga/downloads/DS539544

There is a update of n2lul15w, please try it.

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

Title:
  Lenovo ThinkPad X390 won’t boot while plugged in

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello. I’m using Lenovo ThinkPad X390 Yoga (model type: 20NN002NMC). I have 
been using dual boot of the preinstalled Windows 10 x64 and Linux. I have tried 
the latest versions of Ubuntu and Debian. About 6 weeks ago, after updating the 
BIOS to N2LET76W 1.75 (https://download.lenovo.com/pccbbs/mobiles/n2lur14w.txt) 
and the Intel Management Engine Firmware (12.0.67.1579), an issue arose.
  When I boot to Ubuntu 20.04.1 (kernel 5.4.0-42-generic) using the Grub 
bootloader with active Secure Boot (fully supported), and then I turn the 
notebook off or restart it in Ubuntu, it won’t turn back on – it won’t POST, 
the screen is black, etc. After that time, I need to unplug the notebook from 
the power adapter, or remove it from the dock, and it will boot on battery. But 
it won’t boot while plugged in until it boots into Windows and is turned 
off/restart from it. After booting to Windows, it works fine while plugged in, 
until it is turned off in Ubuntu again. I have tried install recommend drivers 
and software..
  It looks like a BIOS/Firmware error related to power management. I’m using 
the latest BIOS/Firmware updated via the official Lenovo software – Lenovo 
Vantage (bios version 1.76). Notebook was sent to Lenovo for repairs, the 
motherboard was replaced, yet the problem persists – hence thinking it’s 
BIOS/Firmware related.
  Lenovo claims it’s Linux’s issue, even though the list it as officially 
supported (https://support.lenovo.com/sk/en/solutions/pd031426) and there refer 
me to the community. Lenovo stuff inform me too, that this issue may be related 
to requirements Windows 10 v2004.
  Many thanks for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mato   1576 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  5 11:36:45 2020
  InstallationDate: Installed on 2020-08-02 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20NN002NMC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sk_SK.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ca486d67-1377-47fb-93c3-cfb279657f9d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2LET76W (1.76 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NN002NMC
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2LET76W(1.76):bd06/16/2020:svnLENOVO:pn20NN002NMC:pvrThinkPadX390Yoga:rvnLENOVO:rn20NN002NMC:rvr0B98417WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X390 Yoga
  dmi.product.name: 20NN002NMC
  dmi.product.sku: LENOVO_MT_20NN_BU_Think_FM_ThinkPad X390 Yoga
  dmi.product.version: ThinkPad X390 Yoga
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890415/+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 1890441] Re: Fix missing HDMI/DP Audio on an HP Desktop

2020-08-06 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Invalid => Confirmed

** 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-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1890441

Title:
  Fix missing HDMI/DP Audio on an HP Desktop

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Confirmed

Bug description:
  [Impact]
  There's an HP desktop doesn't claim to support HDMI audio.

  [Fix] 
  Use a quirk list to force HDMI audio connection to ignore Connectivity
  Bit, which is incorrectly set by BIOS.

  [Test]
  With the patch applied, we can find HDMI codec under /proc/asound/card0
  and audio playback through HDMI works. 

  [Regression Potential] 
  This fix doesn't bring any functional change other than the targeted
  platform. The platform in question is not on the market yet so the
  risk of regression is minimal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1890441/+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 1861284] Re: Build and ship a signed wireguard.ko

2020-08-06 Thread Stefan Bader
** Changed in: linux (Ubuntu Xenial)
   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/1861284

Title:
  Build and ship a signed wireguard.ko

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  ..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861284/+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 1890441] Re: Fix missing HDMI/DP Audio on an HP Desktop

2020-08-06 Thread Stefan Bader
** Changed in: linux (Ubuntu Focal)
   Importance: High => Medium

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

Title:
  Fix missing HDMI/DP Audio on an HP Desktop

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Confirmed

Bug description:
  [Impact]
  There's an HP desktop doesn't claim to support HDMI audio.

  [Fix] 
  Use a quirk list to force HDMI audio connection to ignore Connectivity
  Bit, which is incorrectly set by BIOS.

  [Test]
  With the patch applied, we can find HDMI codec under /proc/asound/card0
  and audio playback through HDMI works. 

  [Regression Potential] 
  This fix doesn't bring any functional change other than the targeted
  platform. The platform in question is not on the market yet so the
  risk of regression is minimal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1890441/+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 1889182] Re: Wifi problem - Microcode SW error detected. Restarting 0x0

2020-08-06 Thread Karen Cockerill
** Summary changed:

- Microcode SW error detected. Restarting 0x0
+ Wifi problem - Microcode SW error detected. Restarting 0x0

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

Title:
  Wifi problem - Microcode SW error detected. Restarting 0x0

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Ubuntu version 20.04.1 LTS (was previously running 18.04.4 LTS and upgraded 
to try to resolve this issue)
  Intel Corporation Wireless-AC 9260

  Problems with WiFi connection slowly grinding to a halt. From /var/syslog 
(see attachment for further info from the log):
  Microcode SW error detected. Restarting 0x200.

  This occurred first a couple of days ago presumably following an update. The 
logs /var/log/syslog and /var/log/kern.log filled up with the disk repeated 
attempts to restart the WiFi.
  I upgraded to the latest release of Ubuntu hoping to fix the problem. Also 
worth mentioning that I don't think its a hardware problem as wiFi works when I 
boot up from a USB pen drive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1889182/+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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

2020-08-06 Thread Hui Wang
OK, got it, will upload for G.
thx.

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

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  New
Status in alsa-lib source package in Groovy:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  New

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  ucm-substitute-OpenName.patch
  ucm-substitute-CardNumber.patch
  ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  ucm-substitute-device-modifier-names-too.patch
  ucm-substitute-device-strings-in-the-device-lists.patch
  ucm-substitute-component-sequence-string.patch
  ucm-substitute-verb-name-and-file-field.patch
  ucm-substitute-Comment-in-Transition-and-Device.patch
  ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch
  ucm-substitute-arguments-in-sequences-only-for-synta.patch
  ucm-shuffle-code-in-compound_merge.patch
  ucm-implement-CardIdByName-substitution.patch
  ucm-allow-to-ignore-errors-for-the-value-substitutio.patch
  ucm-allow-to-use-the-defined-variables-in-the-substi.patch
  ucm-implement-CardNumberByName-substitution.patch
  ucm-fix-the-possible-buffer-overflow-substitution.patch
  

[Kernel-packages] [Bug 1890222] Re: Enlarge hisi_sec2 capability

2020-08-06 Thread Ike Panhc
** Also affects: kunpeng920
   Importance: Undecided
   Status: New

** Also affects: kunpeng920/ubuntu-20.04
   Importance: Undecided
   Status: New

** Also affects: kunpeng920/ubuntu-18.04-hwe
   Importance: Undecided
   Status: New

** Also affects: kunpeng920/upstream-kernel
   Importance: Undecided
   Status: New

** Changed in: kunpeng920/ubuntu-18.04-hwe
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/ubuntu-20.04
 Assignee: (unassigned) => Ike Panhc (ikepanhc)

** Changed in: kunpeng920/upstream-kernel
   Status: New => Fix Released

** Changed in: kunpeng920/ubuntu-20.04
   Status: New => In Progress

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: New => In Progress

** Changed in: kunpeng920
   Status: New => In Progress

** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: None => ubuntu-20.04.1-sru-1

** Changed in: kunpeng920/ubuntu-20.04
Milestone: None => ubuntu-20.04.1-sru-1

** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: ubuntu-20.04.1-sru-1 => ubuntu-18.04.5-sru-1

** Changed in: kunpeng920/upstream-kernel
Milestone: None => linux-v5.9

** Tags added: ikeradar

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

Title:
  Enlarge hisi_sec2 capability

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Current hisi_sec2 driver only allows 2 threads for accelerator but cpu stress 
test requires more then 50 threads. We have disabled hisi_sec2 temporarily for 
20.04.1. Hisilicon proposes a simple patch on upstream mailing list to enlarge 
the capability.

  [Fix]
  commit 57b1aac1b426b7255afa195298ed691ffea204c6
  Author: Longfang Liu 
  Date: Mon Jun 8 22:01:11 2020 +0800
  Subject: crypto: hisilicon - update SEC driver module parameter

  [Test]
  $ lsmod | grep hisi_sec2 # make sure hisi_sec2 loaded
  $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz 
--times --af-alg 0
  $ echo $?

  [Regression Potential]
  This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other 
platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1890222/+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 1835660] Re: initramfs unpacking failed

2020-08-06 Thread gruberm
I'm watching this error since about 10 months hoping that this would be fixed 
before the 20.04 release.
Now we're almost 4 months past the release date and it's still there.
Given that the fix is quite easy, I'm wondering why this is still an unresolved 
issue.

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1764040] Re: Synaptics Touchpad not Detected

2020-08-06 Thread Avinash Sonawane
> Grub had somehow been changed to disable ACPI. Enabling that solved the
problem.

Imagine how great it would have been if you had mentioned how did
exactly you did that (enabling ACPI in grub)?

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

Title:
  Synaptics Touchpad not Detected

Status in linux package in Ubuntu:
  Expired

Bug description:
  Using Cinnamon on 18.04 Beta 2. (Description:   Ubuntu Bionic Beaver
  (development branch) Release: 18.04)

  Touchpad not detected. Was also not detected in 17.10 but I thought
  that this was a Wayland problem, but obviously not...

  $ cat /proc/bus/input/devices
  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/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=046d Product=c077 Version=0111
  N: Name="Logitech USB Optical Mouse"
  P: Phys=usb-:00:04.0-4/input0
  S: 
Sysfs=/devices/pci:00/:00:04.0/usb2/2-4/2-4:1.0/0003:046D:C077.0001/input/input1
  U: Uniq=
  H: Handlers=mouse0 event1 
  B: PROP=0
  B: EV=17
  B: KEY=ff 0 0 0 0
  B: REL=103
  B: MSC=10

  I: Bus=0003 Vendor=04f2 Product=b012 Version=0346
  N: Name="USB2.0 1.3M UVC WebCam : USB2.0"
  P: Phys=usb-:00:04.1-7/button
  S: Sysfs=/devices/pci:00/:00:04.1/usb1/1-7/1-7:1.0/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:08.0/sound/card0/input3
  U: Uniq=
  H: Handlers=event3 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:08.0/sound/card0/input4
  U: Uniq=
  H: Handlers=event4 
  B: PROP=0
  B: EV=21
  B: SW=4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-15-generic.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC663 Analog [ALC663 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1249 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfce78000 irq 15'
 Mixer name : 'Realtek ALC663'
 Components : 'HDA:10ec0663,10431903,0011 
HDA:10de0007,10de0101,00100100'
 Controls  : 31
 Simple ctrls  : 13
  CurrentDesktop: X-Cinnamon
  Date: Sun Apr 15 14:40:09 2018
  HibernationDevice: RESUME=UUID=5345d639-3d67-4cc1-89bc-acdc9546aa2c
  InstallationDate: Installed on 2017-12-06 (129 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 001 Device 004: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
   Bus 001 Device 003: ID 04f2:b012 Chicony Electronics Co., Ltd 1.3 MPixel UVC 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer Inc. F5GL
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=1ddea34f-fe1f-451d-b88a-5c54b8cafeec ro acpi=off quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)
  dmi.bios.date: 11/20/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: F5GL
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr213:bd11/20/2008:svnASUSTeKComputerInc.:pnF5GL:pvr1.0:rvnASUSTeKComputerInc.:rnF5GL:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: F5GL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

2020-08-06 Thread Daniel van Vugt
Yes, find the new packages' names:

  dpkg -l | grep 5.8.0-050800

and then purge them:

  sudo dpkg -P ...

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have a Toshiba radius 11 laptop which has a 4 k native screen. I
  have connected an Asus PB287Q 28" external monitor
  (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/)
  over HDMI which displays the full 4K resolution when running under
  windows10 but will only reach a maximum resolution of 1920x1080 under
  ubuntu 20.04, same hardware just dual booting. Under Monitor
  Preferences this monitor is detected as an "Ancor Communications inc
  28" and the monitor preferences provides a number of resolution steps
  up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this
  resolution is added to the monitor preferences pick list but
  attempting to apply it results in "the selected configuration for
  displays could not ..." message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

2020-08-06 Thread Leo Ramakersuca
Daniel I successfully ran the dpkg process as you illustrated but it
then failed to boot, so now I must manually selected the 5.4 version in
order to get to this boot. Is there a way to reverse that?

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have a Toshiba radius 11 laptop which has a 4 k native screen. I
  have connected an Asus PB287Q 28" external monitor
  (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/)
  over HDMI which displays the full 4K resolution when running under
  windows10 but will only reach a maximum resolution of 1920x1080 under
  ubuntu 20.04, same hardware just dual booting. Under Monitor
  Preferences this monitor is detected as an "Ancor Communications inc
  28" and the monitor preferences provides a number of resolution steps
  up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this
  resolution is added to the monitor preferences pick list but
  attempting to apply it results in "the selected configuration for
  displays could not ..." message

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