date:20191124

5.0.0-1008.13 - oracle
Regression test CMPL, RTB.

Issue to note in oracle (amd64):
  ubuntu_kernel_selftests - test_bpf in net (bug 1812189) trace_printk in 
ftrace (bug 1830084)
  ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) apic-split (bug 1821390) 
pmu (bug 1853797) port80 (bug 1845688) vmx (bug 1821394)
  ubunut_ltp - proc01 (bug 1829849) memcg_max_usage_in_bytes (bug 1829979) 
memcg_stat (bug 1829983) memcg_subgroup_charge (bug 1847982) 
memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) 
getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) umip_basic_test (bug 
1853798)
  ubuntu_ltp_syscalls - pivot_root01 (bug 1852966)

Skipped / blacklisted:
 * libhugetlbfs

* Note the ubuntu_kernel_selftests must be reviewed on the jenkins
directly


** Changed in: kernel-sru-workflow/regression-testing
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  disco/linux-oracle: 5.0.0-1008.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852253
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Friday, 15. November 2019 15:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oracle-5.0: bug 1852247
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852248/+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 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]

2019-11-24 Thread You-Sheng Yang

Verified version 7906-0ubuntu2~19.10.1 against following kernel headers:

  $ dkms status
  backport-iwlwifi, 7906, 4.15.0-1059-oem, x86_64: installed
  backport-iwlwifi, 7906, 5.0.0-1025-oem-osp1, x86_64: installed
  backport-iwlwifi, 7906, 5.3.0-23-generic, x86_64: installed

** Tags removed: verification-needed verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-
  branch’ and ‘-fcf-protection’ are not compatible]

Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in gcc-9 package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Won't Fix
Status in xtables-addons package in Ubuntu:
  Won't Fix
Status in backport-iwlwifi-dkms source package in Eoan:
  Fix Committed
Status in gcc-9 source package in Eoan:
  Won't Fix
Status in linux source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Eoan:
  Fix Released
Status in virtualbox source package in Eoan:
  Won't Fix
Status in xtables-addons source package in Eoan:
  Won't Fix

Bug description:
  [SRU Justification for backport-iwlwifi-dkms]

  [Impact]
  FTBFS against v5.3 kernels on Eoan/Focal.

  [Fix]
  * Backport fix from upstream commit f47729b94e11 (backport: rename 
ktime_get_boot_ns for v5.3+).
  * Also updates -fcf-protection=none usage for bug 
  1830961.

  [Test Case]
  Verified DKMS module build on linux-oem/linux-oem-osp1/linux-generic >= 4.10 
kernels on series Xenial/Bionic/Cosmic/Disco/Eoan and Focal.

  [Regression Risk]
  Low. There is no functional changes in comparison to 7906-0ubuntu1.

   original bug description 

  Compiling kernels & kernel modules fails due to these errors:

  ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and
  ‘-fcf-protection’ are not compatible

  (This happens with any kernel modules.)

  This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf-
  protection by default on 19.10's gcc-9.

  Switching to gcc-8 allows compilation to proceed.

  WORKAROUND:

  sudo ln -fs gcc-8 /usr/bin/gcc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1830961/+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 1847982] Re: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D-Azure

Can be found on D-Oracle as well.

** Tags added: oracle

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

** Summary changed:

- memcg_subgroup_charge from controllers in ubuntu_ltp failed on D-Azure
+ memcg_subgroup_charge from controllers in ubuntu_ltp failed on D

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

Title:
  memcg_subgroup_charge from controllers in ubuntu_ltp failed on D

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  New
Status in linux-kvm source package in Disco:
  New
Status in linux-oracle source package in Disco:
  New

Bug description:
  Issue found on Azure Disco kernel 5.0.0-1023.24

  Failed on instance:
* Standard_GS2
* Standard_D16s_v3

  Passed on instance:
* Standard_F32s_v2
* Standard_L8s_v2
* Standard_L4s
* Standard_L8s_v2

  (Although it has passed on these instances, but they all have the same
  test output, just the pids are different)

  
  Test failed with:
    /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error

   tag=memcg_subgroup_charge stime=1570239843 dur=3 exit=exited stat=1 core=no 
cu=7 cs=11
   startup='Sat Oct 5 01:44:03 2019'
   memcg_subgroup_charge 1 TINFO: Starting test 1
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 1 TINFO: Warming up pid: 119041
   memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 119041
   memcg_subgroup_charge 1 TPASS: rss is 135168 as expected
   memcg_subgroup_charge 2 TPASS: rss is 0 as expected
   memcg_subgroup_charge 3 TINFO: Starting test 2
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 3 TINFO: Warming up pid: 119071
   memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 119071
   memcg_subgroup_charge 3 TFAIL: rss is 0, 135168 expected
   memcg_subgroup_charge 4 TPASS: rss is 0 as expected
   memcg_subgroup_charge 5 TINFO: Starting test 3
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 5 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 5 TINFO: Warming up pid: 119094
   memcg_subgroup_charge 5 TINFO: Process is still here after warm up: 119094
   memcg_subgroup_charge 5 TPASS: rss is 135168 as expected
   memcg_subgroup_charge 6 TPASS: rss is 0 as expected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1847982/+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 1853758] Re: Forcing incompatible Nvidia drivers

2019-11-24 Thread Diggy Smitty

** Package changed: ubuntu => nvidia-graphics-drivers-418 (Ubuntu)

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

Title:
  Forcing incompatible Nvidia drivers

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  On Ubuntu 18.0.4.3 and 19.10, The driver installer keeps forcing
  incompatible drivers for my Nvidia GPU. If I add the PPA it only gives
  me the incompatible drivers. My Nvidia Card is a GTX 770m which
  requires the 418 driver. Even if I install 18.0.4.2 and 19.04 Ubuntu
  then upgrade, the system automatically installs the 430 drivers over
  the 418 one and the 430 drivers do not work at all with all cards.
  Driver number is not the same as being the newest driver, the 418
  drivers are constantly being updated and that's the newest for my GPU.
  Please fix this mess.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1853758/+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 1853758] [NEW] Forcing incompatible Nvidia drivers

2019-11-24 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

On Ubuntu 18.0.4.3 and 19.10, The driver installer keeps forcing
incompatible drivers for my Nvidia GPU. If I add the PPA it only gives
me the incompatible drivers. My Nvidia Card is a GTX 770m which requires
the 418 driver. Even if I install 18.0.4.2 and 19.04 Ubuntu then
upgrade, the system automatically installs the 430 drivers over the 418
one and the 430 drivers do not work at all with all cards. Driver number
is not the same as being the newest driver, the 418 drivers are
constantly being updated and that's the newest for my GPU. Please fix
this mess.

** Affects: nvidia-graphics-drivers-418 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
Forcing incompatible Nvidia drivers
https://bugs.launchpad.net/bugs/1853758
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-418 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 1853798] [NEW] umip_basic_test in kernel_misc from ubuntu_ltp failed on D-Oracle

Public bug reported:

<<>>
tag=umip_basic_test stime=1574662675
cmdline="umip_basic_test"
contacts=""
analysis=exit
<<>>
tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1005-oracle'
incrementing stop
tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
umip_basic_test.c:158: INFO: cpuinfo contains umip, CPU supports umip
umip_basic_test.c:40: INFO: TEST sgdt, sgdt result save at [0x7ffdd514086e]
umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4
umip_basic_test.c:135: PASS: Got SIGSEGV
umip_basic_test.c:50: INFO: TEST sidt, sidt result save at [0x7ffdd514086e]
umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4
umip_basic_test.c:135: PASS: Got SIGSEGV
umip_basic_test.c:59: INFO: TEST sldt, sldt result save at [0x7ffdd5140860]
umip_basic_test.c:135: PASS: Got SIGSEGV
umip_basic_test.c:68: INFO: TEST smsw, smsw result save at [0x7ffdd5140860]
umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4
umip_basic_test.c:139: FAIL: Didn't receive SIGSEGV, child exited with exited 
with 0
umip_basic_test.c:77: INFO: TEST str, str result save at [0x7ffdd5140860]
umip_basic_test.c:135: PASS: Got SIGSEGV

Summary:
passed   4
failed   1
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<>>

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9
ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21
Uname: Linux 5.0.0-1005-oracle x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
Date: Mon Nov 25 06:18:04 2019
SourcePackage: linux-signed-oracle
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: 5.0 amd64 apport-bug disco oracle sru-2019 ubuntu-ltp uec-images

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: 5.0 oracle sru-2019 ubuntu-ltp

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

Title:
  umip_basic_test in kernel_misc from ubuntu_ltp failed on D-Oracle

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

Bug description:
  <<>>
  tag=umip_basic_test stime=1574662675
  cmdline="umip_basic_test"
  contacts=""
  analysis=exit
  <<>>
  tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1005-oracle'
  incrementing stop
  tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
  umip_basic_test.c:158: INFO: cpuinfo contains umip, CPU supports umip
  umip_basic_test.c:40: INFO: TEST sgdt, sgdt result save at [0x7ffdd514086e]
  umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4
  umip_basic_test.c:135: PASS: Got SIGSEGV
  umip_basic_test.c:50: INFO: TEST sidt, sidt result save at [0x7ffdd514086e]
  umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4
  umip_basic_test.c:135: PASS: Got SIGSEGV
  umip_basic_test.c:59: INFO: TEST sldt, sldt result save at [0x7ffdd5140860]
  umip_basic_test.c:135: PASS: Got SIGSEGV
  umip_basic_test.c:68: INFO: TEST smsw, smsw result save at [0x7ffdd5140860]
  umip_basic_test.c:131: INFO: Linux kernel version is before than v5.4
  umip_basic_test.c:139: FAIL: Didn't receive SIGSEGV, child exited with exited 
with 0
  umip_basic_test.c:77: INFO: TEST str, str result save at [0x7ffdd5140860]
  umip_basic_test.c:135: PASS: Got SIGSEGV

  Summary:
  passed   4
  failed   1
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9
  ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21
  Uname: Linux 5.0.0-1005-oracle x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Mon Nov 25 06:18:04 2019
  SourcePackage: linux-signed-oracle
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853798/+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 1853797] [NEW] pmu in ubuntu_kvm_unit_tests failed with 4 unexpected failures on D-Oracle

Public bug reported:

4 failures:
 FAIL: rdpmc: fixed cntr-0
 FAIL: rdpmc: fixed cntr-1
 FAIL: rdpmc: fixed cntr-2
 FAIL: all counters


Test log:
 Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/pmu'
 BUILD_HEAD=e2c275c4
 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.UfviUpwSjB -smp 1 
-cpu host # -initrd /tmp/tmp.7jA5GK5kyl
 enabling apic
 paging enabled
 cr0 = 80010011
 cr3 = 45a000
 cr4 = 20
 PMU version: 2
 GP counters: 4
 GP counter width: 48
 Mask length: 7
 Fixed counters: 3
 Fixed counter width: 48
 PASS: core cycles-0
 PASS: core cycles-1
 PASS: core cycles-2
 PASS: core cycles-3
 PASS: instructions-0
 PASS: instructions-1
 PASS: instructions-2
 PASS: instructions-3
 PASS: ref cycles-0
 PASS: ref cycles-1
 PASS: ref cycles-2
 PASS: ref cycles-3
 PASS: llc refference-0
 PASS: llc refference-1
 PASS: llc refference-2
 PASS: llc refference-3
 PASS: llc misses-0
 PASS: llc misses-1
 PASS: llc misses-2
 PASS: llc misses-3
 PASS: branches-0
 PASS: branches-1
 PASS: branches-2
 PASS: branches-3
 PASS: branch misses-0
 PASS: branch misses-1
 PASS: branch misses-2
 PASS: branch misses-3
 PASS: fixed-0
 PASS: fixed-1
 PASS: fixed-2
 PASS: rdpmc: cntr-0
 PASS: rdpmc: fast-0
 PASS: rdpmc: cntr-1
 PASS: rdpmc: fast-1
 PASS: rdpmc: cntr-2
 PASS: rdpmc: fast-2
 PASS: rdpmc: cntr-3
 PASS: rdpmc: fast-3
 FAIL: rdpmc: fixed cntr-0
 PASS: rdpmc: fixed fast-0
 FAIL: rdpmc: fixed cntr-1
 PASS: rdpmc: fixed fast-1
 FAIL: rdpmc: fixed cntr-2
 PASS: rdpmc: fixed fast-2
 FAIL: all counters
 PASS: overflow: cntr-0
 PASS: overflow: status-0
 PASS: overflow: status clear-0
 PASS: overflow: irq-0
 PASS: overflow: cntr-1
 PASS: overflow: status-1
 PASS: overflow: status clear-1
 PASS: overflow: irq-1
 PASS: overflow: cntr-2
 PASS: overflow: status-2
 PASS: overflow: status clear-2
 PASS: overflow: irq-2
 PASS: overflow: cntr-3
 PASS: overflow: status-3
 PASS: overflow: status clear-3
 PASS: overflow: irq-3
 PASS: overflow: cntr-4
 PASS: overflow: status-4
 PASS: overflow: status clear-4
 PASS: overflow: irq-4
 PASS: cmask
 SUMMARY: 67 tests, 4 unexpected failures
 FAIL pmu (67 tests, 4 unexpected failures)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9
ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21
Uname: Linux 5.0.0-1005-oracle x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
Date: Mon Nov 25 04:29:43 2019
SourcePackage: linux-signed-oracle
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: 5.0 amd64 apport-bug disco oracle sru-2019 uec-images

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: 5.0 oracle sru-2019

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

Title:
  pmu in ubuntu_kvm_unit_tests failed with 4 unexpected failures on
  D-Oracle

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

Bug description:
  4 failures:
   FAIL: rdpmc: fixed cntr-0
   FAIL: rdpmc: fixed cntr-1
   FAIL: rdpmc: fixed cntr-2
   FAIL: all counters

  
  Test log:
   Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/pmu'
   BUILD_HEAD=e2c275c4
   timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel 
/tmp/tmp.UfviUpwSjB -smp 1 -cpu host # -initrd /tmp/tmp.7jA5GK5kyl
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 45a000
   cr4 = 20
   PMU version: 2
   GP counters: 4
   GP counter width: 48
   Mask length: 7
   Fixed counters: 3
   Fixed counter width: 48
   PASS: core cycles-0
   PASS: core cycles-1
   PASS: core cycles-2
   PASS: core cycles-3
   PASS: instructions-0
   PASS: instructions-1
   PASS: instructions-2
   PASS: instructions-3
   PASS: ref cycles-0
   PASS: ref cycles-1
   PASS: ref cycles-2
   PASS: ref cycles-3
   PASS: llc refference-0
   PASS: llc refference-1
   PASS: llc refference-2
   PASS: llc refference-3
   PASS: llc misses-0
   PASS: llc misses-1
   PASS: llc misses-2
   PASS: llc misses-3
   PASS: branches-0
   PASS: branches-1
   PASS: branches-2
   PASS: branches-3
   PASS: branch misses-0
   PASS: branch misses-1
   PASS: branch misses-2
   PASS: branch misses-3
   PASS: fixed-0
   PASS: fixed-1
   PASS: fixed-2
   PASS: rdpmc: cntr-0
   PASS: rdpmc: fast-0
   PASS: rdpmc: cntr-1
   PASS: rdpmc: fast-1

[Kernel-packages] [Bug 1845186] Re: nfs Input/output error

2019-11-24 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Expired

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: FUJITSU //

[Kernel-packages] [Bug 1739386] Re: [xhci_hcd] HC died · USB controller died, reboot necessary

2019-11-24 Thread You-Sheng Yang

@bp0, thanks for sharing. Maybe you'll also feel like to file a new bug
and provide more information so that we may have a chance to work out an
appropriate fix for that hw.

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

Title:
  [xhci_hcd] HC died · USB controller died, reboot necessary

Status in linux package in Ubuntu:
  Expired

Bug description:
  * Ubuntu release: 17.04
  * uname -r: 4.10.0-42-generic
  * Expected behaviour: the USB ports run well
  * What happens: the USB ports are randomly killed from time to time

  * Explanation:
  The xhci_hcd driver reports that the xHCI host is not responding to a stop 
endpoint command. The USB host controller is then shut down and all USB ports 
are left dead until a reboot is performed. This is not immediate nor 
predictable --- sometimes, it can be days before it happens; sometimes it is 
just hours.

  If I understood correctly, there is no way to reload the kernel module
  of the USB driver, because it is baked into the kernel at compile
  time. Something like that? :)

  When rebooting, the shutdown process completes (it reports a "shutdown
  target achieved" or similar), but is unable to unmount the /home/user
  partition. Therefore, the system does not shutdown unless I press the
  power button (hard shutdown). I do not know if there is a way to get a
  TTY at that point to manually unmount the partition. The home folder
  is encrypted... I do not know if this has something to do with it, but
  this error only occurs when the USB HC is killed.

  I suspect the USB problem has to do with an external USB hub by TP-
  LINK. It seems to only fail when this device is connected. The hub
  model is UH400, by TP-LINK.

  Anything I can add, just ask for it!
  Thanks a lot!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739386/+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 1852723] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and Kunpeng920

2019-11-24 Thread Ike Panhc

Find another 2 patches depends on the arm64 patchset in #18

fc4eb08e5edc hanjun@linaro.org 2019-11-13 18:47:34 -0500 arm64: kpti: 
Whitelist HiSilicon Taishan v110 CPUs
31140a50f228 marc.zyng...@arm.com 2019-11-12 19:04:57 +0100 arm64: Enable 
workaround for Cavium TX2 erratum 219 when running SMT

To revert everything included kpti and erratum from stable update is not
a good idea.

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

Title:
  [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and
  Kunpeng920

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

Bug description:
  [Impact]
  4.15.0-71-generic can not boot on ThunderX2 and Kunpeng920. Kernel oops 
durning SMP init

  console logs are available here
  https://pastebin.ubuntu.com/p/By4m3PtKsG/
  https://pastebin.ubuntu.com/p/vN2c3CFVXR/

  [Test Case]
  Boot kernel with earlycon. See if kernel oops while booting.

  [Regression Risk]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852723/+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 1852723] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and Kunpeng920

2019-11-24 Thread Ike Panhc

The patchset is bigger then I expected. There are 45 patches is a
patchset for several vulnerability fix.

$ git log --format=oneline 22a4045c5c58..f2549319bd62 | wc -l
45

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

Title:
  [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and
  Kunpeng920

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

Bug description:
  [Impact]
  4.15.0-71-generic can not boot on ThunderX2 and Kunpeng920. Kernel oops 
durning SMP init

  console logs are available here
  https://pastebin.ubuntu.com/p/By4m3PtKsG/
  https://pastebin.ubuntu.com/p/vN2c3CFVXR/

  [Test Case]
  Boot kernel with earlycon. See if kernel oops while booting.

  [Regression Risk]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852723/+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 1821394] Re: vmx tests fail in kvm_unit_tests

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

** Tags added: sru-2019

** Tags added: 5.3

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

Title:
  vmx tests fail in kvm_unit_tests

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-oracle package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved

[Kernel-packages] [Bug 1853791] Re: External microphone can't work on some dell machines with the codec alc256 or alc236

** Description changed:

- tracking purpose
+ [Impact]
+ The external microphone can't work on some dell machines with the
+ codec alc256 or alc236
+ 
+ [Fix]
+ Need to apply the ALC255_FIXUP_DELL1_MIC_NO_PRESENCE, instead of
+ adding a new pintbl in the quirk table, we use fallback table this
+ time.
+ 
+ [Test Case]
+ tested the kernel with these patches, the external mic worked well.
+ 
+ [Regression Risk]
+ Low, just make the quirk applying more generic.

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

Title:
  External microphone can't work on some dell machines with the codec
  alc256 or alc236

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

Bug description:
  [Impact]
  The external microphone can't work on some dell machines with the
  codec alc256 or alc236

  [Fix]
  Need to apply the ALC255_FIXUP_DELL1_MIC_NO_PRESENCE, instead of
  adding a new pintbl in the quirk table, we use fallback table this
  time.

  [Test Case]
  tested the kernel with these patches, the external mic worked well.

  [Regression Risk]
  Low, just make the quirk applying more generic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1853791/+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 1847596] Re: rpi3b+: corrupted screen on hdmi

** Changed in: linux-raspi2 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  rpi3b+: corrupted screen on hdmi

Status in linux-raspi2 package in Ubuntu:
  Fix Committed

Bug description:
  Eoan daily: 20191010
  Ubuntu Server arm64+raspi3
  HW: Raspberrypi 3 B+

  Initial boot ok but as soon as changing to the high resolution
  framebuffer, the whole screen consists mostly of bright yellow and
  darker yellow vertical stipes. Further boot messages are visible but
  barely readable. Device is accessible via ssh. The dmesg there shows
  some kernel warnings:

  [1.450650] bcm2708_fb soc:fb: FB found 1 display(s)
  [1.452916] WARNING: CPU: 2 PID: 1 at mm/page_alloc.c:4696 
__alloc_pages_nodemask+0x284/0x2c8
  [1.460096] Modules linked in:
  [1.467227] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.3.0-1005-raspi2 
#6-Ubuntu
  [1.474549] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT)
  [1.481908] pstate: 2045 (nzCv daif +PAN -UAO)
  [1.489237] pc : __alloc_pages_nodemask+0x284/0x2c8
  [1.496499] lr : __dma_direct_alloc_pages+0x100/0x1e8
  ...
  [1.761649] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 
1824x984
  [1.850950] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
  [1.859009] bcm2835-rng 3f104000.rng: hwrng registered
  [1.865102] vc-mem: phys_addr:0x mem_base=0x3ec0 
mem_size:0x4000(1024 MiB)
  ...
  [2.909823] WARN::dwc_otg_hcd_init:1043: FIQ DMA bounce buffers: virt = 
10616000 dma = 0xfad1 len=9024
  ...
  [2.946722] WARN::hcd_init_fiq:496: MPHI regs_base at 10075000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/+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 1848490] Re: eoan: alsa/sof: Enable SOF_HDA link and codec

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

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

Title:
  eoan: alsa/sof: Enable SOF_HDA link and codec

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:

  [Impact]
  We tested the EOAN kernel on the LENOVO or Dell machines which have
  dmic directly connnected to PCH, the dmic didn't work.

  [Fix]
  We need to enable SOF_HDA link and codec, then the sof driver
  and Legacy HDA driver work together to make the dmic work.

  [Test Case]
  Install the latest 19.10 image, build a new kernel with this
  patch and replace the existing kernel, After installing the blacklist
  package (blacklist snd_hda_intel and snd_soc_skl) and ucm package,
  the dmic and all output devices (speaker/hdmi) work.

  [Regression Risk]
  Low, these configs are already enabled in the oem-b-osp1 kernel
  for a long time, and we tested it on many lenovo/dell machines witch
  have or have no dmic, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848490/+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 1853791] Re: External microphone can't work on some dell machines with the codec alc256 or alc236

** Tags added: originate-from-1852542 somerville

** Tags added: originate-from-1849286

** Tags added: originate-from-1849075

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

Title:
  External microphone can't work on some dell machines with the codec
  alc256 or alc236

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

Bug description:
  tracking purpose

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1853791/+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 1849623] Re: linux-raspi2: rebase the Eoan kernel to the latest rpi-5.3.y branch (2a085c9b42ea)

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

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

Title:
  linux-raspi2: rebase the Eoan kernel to the latest rpi-5.3.y branch
  (2a085c9b42ea)

Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-raspi2 source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  https://bugs.launchpad.net/bugs/1848790
  https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703
  Recently we had 2 bugs about the usb host on rpi4 with 4G ram, and I found
  the kernel in the github already had the fix for this issue, and besides this
  fix, it also had 106 more patches than our eoan kernel, those patches were
  merged during or after we prepared our eoan kernel, now let us pick those
  patches to our eoan too. 

  [Fix]
  For the usb host issue, it adds a fix by setting the usb dma bounce buffer
  under 1G.

  [Test Case]
  some users and I alreaady tested the armhf and arm64 kernel on pi4 and pi3
  boards, the usb host worked well and no other regressions introduced.

  [Regression Risk]
  Low, these patches are from the github which is the pi official kernel
  repository. And we already tested armhf and arm64 kernel on pi4/3 boards.
   


  The rpi kernel of https://github.com/raspberrypi/linux.git has been
  updated, for the branch of rpi-5.3.y (Eoan kernel base on this
  branch), there are 107 new patches merged, we also need to merge those
  patches to Eoan kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849623/+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 1853789] Re: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel

** Changed in: linux-raspi2 (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  We enabled this driver in the linux-image-5.3.0-1013-raspi2 proposed
  kernel, then we got lots of reports from users that this driver is not
  stable, it will crash randomly, so let us disable this driver again
  and wait for the upstream branch rpi-5.3.y has the fixes for it.

  Users report crash of this driver via: #1852035 and #1850876

  This bug is for tracking the reverting the fix of #1850876.

  [Impact]
  According to the #1852035 and #1850876, users reported that the driver
  v3d will crash under desktop, then I checked the upstream kernel, the
  branch rpi-5.3.y was merged some fixes for v3d driver on Nov 11, I
  tested this branch myself, found the driver still has some problem.
  I also applied those patches to eoan kernel and built a testing
  kernel, users reported similar problems with this testing kernel.

  So the safest way is to disable this driver in the kernel agian, until
  the branch rpi-5.3.y has the fixes for this driver. Or we could
  investigate and backport fixes from rpi-4.19.y later.

  [Fix]
  Revert a patch in the 1013 kernel.

  
  [Test Case]
  Users tested 1012 kernel a lot, they didn't report the unstable issues,
  and before the 1013, this driver was always disabled.

  [Regression Risk]
  Low, just revert a new enabled driver in the 1013 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853789/+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 1842998] Re: alsa/hda/realtek: The microphone and mic of headset are uesless on a ThinkCentre

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

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

Title:
  alsa/hda/realtek: The microphone and mic of headset are uesless on a
  ThinkCentre

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  [Impact]
  This machine user a new realtek codec and has two
  front mics, the PA can't handle two front mics, then it
  can't record sound via these two mics.

  [Fix]
  Apply an existing fixup to fix this issue.

  [Test Case]
  After applying the patch, plug an external mic or headset-mic
  to the mic jack or headset jack, system can detect them and can
  record the sound from it too.

  
  [Regression Risk]
  Low. just add an existing fixup to this new machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1842998/+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 1853791] Missing required logs.

2019-11-24 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 1853791

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

Title:
  External microphone can't work on some dell machines with the codec
  alc256 or alc236

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

Bug description:
  tracking purpose

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1853791/+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 1853789] Re: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel

** Description changed:

  We enabled this driver in the linux-image-5.3.0-1013-raspi2 proposed
  kernel, then we got lots of reports from users that this driver is not
  stable, it will crash randomly, so let us disable this driver again and
  wait for the upstream branch rpi-5.3.y has the fixes for it.
  
  Users report crash of this driver via: #1852035 and #1850876
  
  This bug is for tracking the reverting the fix of #1850876.
+ 
+ [Impact]
+ According to the #1852035 and #1850876, users reported that the driver
+ v3d will crash under desktop, then I checked the upstream kernel, the
+ branch rpi-5.3.y was merged some fixes for v3d driver on Nov 11, I
+ tested this branch myself, found the driver still has some problem.
+ I also applied those patches to eoan kernel and built a testing
+ kernel, users reported similar problems with this testing kernel.
+ 
+ So the safest way is to disable this driver in the kernel agian, until
+ the branch rpi-5.3.y has the fixes for this driver. Or we could
+ investigate and backport fixes from rpi-4.19.y later.
+ 
+ [Fix]
+ Revert a patch in the 1013 kernel.
+ 
+ 
+ [Test Case]
+ Users tested 1012 kernel a lot, they didn't report the unstable issues,
+ and before the 1013, this driver was always disabled.
+ 
+ [Regression Risk]
+ Low, just revert a new enabled driver in the 1013 kernel.

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

Title:
  Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  We enabled this driver in the linux-image-5.3.0-1013-raspi2 proposed
  kernel, then we got lots of reports from users that this driver is not
  stable, it will crash randomly, so let us disable this driver again
  and wait for the upstream branch rpi-5.3.y has the fixes for it.

  Users report crash of this driver via: #1852035 and #1850876

  This bug is for tracking the reverting the fix of #1850876.

  [Impact]
  According to the #1852035 and #1850876, users reported that the driver
  v3d will crash under desktop, then I checked the upstream kernel, the
  branch rpi-5.3.y was merged some fixes for v3d driver on Nov 11, I
  tested this branch myself, found the driver still has some problem.
  I also applied those patches to eoan kernel and built a testing
  kernel, users reported similar problems with this testing kernel.

  So the safest way is to disable this driver in the kernel agian, until
  the branch rpi-5.3.y has the fixes for this driver. Or we could
  investigate and backport fixes from rpi-4.19.y later.

  [Fix]
  Revert a patch in the 1013 kernel.

  
  [Test Case]
  Users tested 1012 kernel a lot, they didn't report the unstable issues,
  and before the 1013, this driver was always disabled.

  [Regression Risk]
  Low, just revert a new enabled driver in the 1013 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853789/+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 1853791] [NEW] External microphone can't work on some dell machines with the codec alc256 or alc236

Public bug reported:

tracking purpose

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: New

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

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

Title:
  External microphone can't work on some dell machines with the codec
  alc256 or alc236

Status in linux package in Ubuntu:
  New

Bug description:
  tracking purpose

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853791/+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 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker

Hardware Certification have begun testing this -proposed kernel.

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  disco/linux: 5.0.0-37.40 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 14. November 2019 18:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1853116
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
unknown/unknown: bug 1852245
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+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 1852262] Re: bionic/linux-raspi2: 4.15.0-1051.55 -proposed tracker

Hardware Certification have begun testing this -proposed kernel.

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  bionic/linux-raspi2: 4.15.0-1051.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852289
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Friday, 15. November 2019 10:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1852261
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852262/+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 1852300] Re: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker

Hardware Certification have begun testing this -proposed kernel.

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852306
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Wednesday, 20. November 2019 02:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1852299
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852300/+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 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker

Hardware Certification have begun testing this -proposed kernel.

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  xenial/linux: 4.4.0-170.199 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 14. November 2019 18:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1852304
trusty/linux-lts-xenial: bug 1852305
xenial/linux-aws: bug 1852296
xenial/linux-cascade: bug 1852297
xenial/linux-fips: bug 1852303
xenial/linux-kvm: bug 1852298
xenial/linux-raspi2: bug 1852300
xenial/linux-snapdragon: bug 1852302
xenial/linux/caracalla-kernel: bug 1852291
xenial/linux/pc-kernel: bug 1852292
xenial/linux/stlouis-kernel: bug 1852293
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+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 1852264] Re: bionic/linux-snapdragon: 4.15.0-1068.75 -proposed tracker

Hardware Certification have begun testing this -proposed kernel.

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  bionic/linux-snapdragon: 4.15.0-1068.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852289
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Friday, 15. November 2019 11:31 UTC
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1852263
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852264/+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 1852302] Re: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker

Hardware Certification have begun testing this -proposed kernel.

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852306
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Wednesday, 20. November 2019 07:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1852301
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852302/+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 1852266] Re: bionic/linux-oem: 4.15.0-1065.75 -proposed tracker

Hardware Certification have begun testing this -proposed kernel.

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  bionic/linux-oem: 4.15.0-1065.75 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852289
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Thursday, 21. November 2019 15:15 UTC
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852266/+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 1852289] Re: bionic/linux: 4.15.0-71.80 -proposed tracker

Hardware Certification have begun testing this -proposed kernel.

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  bionic/linux: 4.15.0-71.80 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 14. November 2019 18:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1852270
bionic/linux-fips: bug 1852278
bionic/linux-gke-4.15: bug 1852272
bionic/linux-ibm-gt: bug 1853265
bionic/linux-kvm: bug 1852273
bionic/linux-oem: bug 1852266
bionic/linux-oracle: bug 1852277
bionic/linux-raspi2: bug 1852262
bionic/linux-snapdragon: bug 1852264
bionic/linux/pc-kernel: bug 1852259
bionic/linux/pc-lowlatency-kernel: bug 1852260
unknown/unknown: bug 1852288
xenial/linux-azure: bug 1852282
xenial/linux-gcp: bug 1852285
xenial/linux-hwe: bug 1852288
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852289/+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 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan

2019-11-24 Thread Ian Pitt

Yes, the Gentoo image is running 4.19.67.

Thanks,  I can wait for a more stable version.

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

Title:
  CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan

Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Fix Committed

Bug description:
  We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the
  DRM_V3D.

  In fact the DRM_V3D is crucial for graphical applications (such as
  ubuntu-desktop :) as it removes the graphical overhead from the cpu to
  the gpu, making the applications work much faster.

  Please refer to https://bugs.launchpad.net/ubuntu/+source/linux-
  raspi2/+bug/1848703/comments/32

  
  [Impact]
  Users reported that we should enable the DRM_V3D, then the GPU will
  be fully used when running "ubuntu-desktop"

  [Fix]
  Enable the DRM_V3D, the v3d.ko will be built

  [Test Case]
  Users already tested it, it worked well.
  
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36

  [Regression Risk]
  Low, I already did building test for arm64 and armhf, all passed.
  And uers already tested the kernel module, it worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+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 1853789] [NEW] Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel

Public bug reported:

We enabled this driver in the linux-image-5.3.0-1013-raspi2 proposed
kernel, then we got lots of reports from users that this driver is not
stable, it will crash randomly, so let us disable this driver again and
wait for the upstream branch rpi-5.3.y has the fixes for it.

Users report crash of this driver via: #1852035 and #1850876

This bug is for tracking the reverting the fix of #1850876.

** Affects: linux-raspi2 (Ubuntu)
 Importance: Undecided
 Assignee: Hui Wang (hui.wang)
 Status: New

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

Title:
  Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  We enabled this driver in the linux-image-5.3.0-1013-raspi2 proposed
  kernel, then we got lots of reports from users that this driver is not
  stable, it will crash randomly, so let us disable this driver again
  and wait for the upstream branch rpi-5.3.y has the fixes for it.

  Users report crash of this driver via: #1852035 and #1850876

  This bug is for tracking the reverting the fix of #1850876.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853789/+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 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H

*** This bug is a duplicate of bug 1850876 ***
https://bugs.launchpad.net/bugs/1850876

Got it, thanks,

We will disable the driver v3d again in the kernel until the branch
rpi-5.3.y has the perfect fix for this driver.

And set this bug duplicated to #1850876.


** This bug has been marked a duplicate of bug 1850876
   CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan

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

Title:
  Cannot use full resolution (2560x1440) of Dell U2715H

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  While using Ubuntu 19.10 with either MATE or GNOME, I can use only
  1920x1080 resolution instead of the full 2560x1440.  If extra pixels
  are configured, they fall off the right side or bottom of the display
  and are not visible.  Reproduced on Raspberry Pi 4  with 3GB max
  workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: User Name 5.3.0-1008.9-raspi2 5.3.1
  Uname: Linux 5.3.0-1008-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 10 18:18:23 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M 
video=HDMI-A-1:1920x1080@60 smsc95xx.macaddr=DC:A6:32:38:DF:15 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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-raspi2/+bug/1852035/+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 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan

@Ian,

"rock solid WITH acceleration when using Gentoo", could you please tell
me what is the kernel version for Gentoo? Or could you paste the output
of 'uname -a' under Gentoo?

I tested the branch rpi-5.3.y of upstream kernel
(https://github.com/raspberrypi/linux.git), the v3d driver is better
now, but still has some problems. So I guess the Gentoo uses 4.19
kernel?

BTW, we have another bug to track this issue
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852035,
from the comment #14 and #15 of that bug, we could see even applying the
latest patches of v3d, the driver still has some problems.

So we need to disable the driver v3d in the kernel until the branch
rpi-5.3.y has the perfect fix for this driver.

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

Title:
  CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan

Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Fix Committed

Bug description:
  We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the
  DRM_V3D.

  In fact the DRM_V3D is crucial for graphical applications (such as
  ubuntu-desktop :) as it removes the graphical overhead from the cpu to
  the gpu, making the applications work much faster.

  Please refer to https://bugs.launchpad.net/ubuntu/+source/linux-
  raspi2/+bug/1848703/comments/32

  
  [Impact]
  Users reported that we should enable the DRM_V3D, then the GPU will
  be fully used when running "ubuntu-desktop"

  [Fix]
  Enable the DRM_V3D, the v3d.ko will be built

  [Test Case]
  Users already tested it, it worked well.
  
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36

  [Regression Risk]
  Low, I already did building test for arm64 and armhf, all passed.
  And uers already tested the kernel module, it worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+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 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790

@Avio,

I could see "mmc-bcm2835 fe30.mmcnr: could not get clk, deferring
probe" too, but didn't meet your problem.

After the system boot up, it will mount the mmcblk0p2 as rootfs and mount
mmcblk0p1 as /boot/firmware. I don't know why you couldn't see mmcblk0p1/2.
Could you use ethernent, if yes, you could upgrade the kernel to 1012, to do so:
sudo apt-get update
sudo apt install linux-image-5.3.0-1012-raspi2
sudo reboot

If you still can't see mmcblk0p1/p2, could you please upload the
complete dmesg to lp?

thx.

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

Title:
Raspberry Pi 4 - USB Bus not detecting any devices

Status in linux-raspi2 package in Ubuntu:
Confirmed

Bug description:
Pi 4 new install. System boots up but USB bus is not working.

Tried 3 keyboards no key presses detected, 2 usb memory drives don't
show up in lsblk.

output of $lspci
00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10)
01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller
(rev 01)

output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or
attached to this bug report.

Not the only one experiencing bug. Another user created a post on the ubuntu
forums:

https://ubuntuforums.org/showthread.php?t=2429396=01a0c4b0cb4c05e605cbf9d41f660e08=13898142#post13898142

64bit raspberry pi 4&4 image pulled from
https://ubuntu.com/download/iot/raspberry-pi page. Specifically
http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10
-preinstalled-server-arm64+raspi3.img.xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+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 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

2019-11-24 Thread Michael

I, the original reporter, can confirm that this problem persists with
current BIOS and 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/1612916

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

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

Bug description:
  On initial boot, sound on internal speakers is working. After standby
  it doesn work anymore, but a analog headset does. Switching around in
  pavucontrol doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.

  Toshiba/Dynabook Portege Z20T-C:
  
https://support.dynabook.com/support/modelHome?freeText=1200015981=785

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612916/+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 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan

2019-11-24 Thread Ian Pitt

Thanks for the new kernel.  I booted it and noted that the right drivers
were now being used ( Accelerated video and glxinfo showing it was using
VC4 rather than the original llvmpipe.   However:

1) On Mate, the Pi locked up within a few seconds of resizing windows
2) On Ubuntu,  it took a few minutes but again the machine locked up after 
using applications. 

Ahead of failures, areas of the screens were flashing/jittering.   Once
locked, only a reboot would gain control of the console.

4GB Pi 4, all 64bit kernels - rock solid without acceleration on the
former kernel,  rock solid WITH acceleration when using Gentoo.

I reverted to the older kernel and the machine is back to being stable,
albeit with out the acceleration.

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

Title:
  CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan

Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Fix Committed

Bug description:
  We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the
  DRM_V3D.

  In fact the DRM_V3D is crucial for graphical applications (such as
  ubuntu-desktop :) as it removes the graphical overhead from the cpu to
  the gpu, making the applications work much faster.

  Please refer to https://bugs.launchpad.net/ubuntu/+source/linux-
  raspi2/+bug/1848703/comments/32

  
  [Impact]
  Users reported that we should enable the DRM_V3D, then the GPU will
  be fully used when running "ubuntu-desktop"

  [Fix]
  Enable the DRM_V3D, the v3d.ko will be built

  [Test Case]
  Users already tested it, it worked well.
  
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36

  [Regression Risk]
  Low, I already did building test for arm64 and armhf, all passed.
  And uers already tested the kernel module, it worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+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 1853030] Re: No connection through SSH over WIfi after kernel update

2019-11-24 Thread Stefan

Tried this, but I cannot find anything that means something to me with
respect to the problem.

The log is attached.

Row 1: Here the RPI starts with ethernet cable attached and wlan0
configured. Both adapters seem to take their IPs. -> I can estasblish
SSH to both.

Row 743: I'm removing the ethernet cable and at this moment the eth0
goes down. I'm trying to establish SSH to wlan0 IP a couple of times
without success. After that I'm switching off the RPi, plug in the
ethernet cable and switch on again.

Row 761: This the boot after power on.


** Attachment added: "Syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+attachment/5307578/+files/syslog_1.txt

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

Title:
  No connection through SSH over WIfi after kernel update

Status in linux-raspi2 package in Ubuntu:
  Incomplete

Bug description:
  After updating from kernel "linux-image-5.3.0-1007-raspi2" to "linux-
  image-5.3.0-1012-raspi2" I no longer can establish SSH connection to
  Raspberry over Wifi.

  When it is on wired connection, SSH works and initial screen shows
  that both adapters (eth0 and wlan0) are connected and have their IPs.
  "ifconfig" confirms that both adapters are up and have their IPs.
  Establishing SSH session with both IPs is successful.

  When I disconnect the network cable, SSH is no longer possible
  (connection time out). In the same time the router is showing that the
  Raspberry is connected to the Wifi network.

  Plugging back the wire does not make the SSH possible. A restart of
  the Raspberry is required with plugged in network cable in order to
  establish SSH again.

  The system is Raspberry Pi 4, 4GB with Ubuntu server X64 image - clean
  install.

  Wifi was enabled by editing /etc/netplan/50-cloud-init.yaml and
  running "sudo netplan apply"

  Reference info for what is done so far:
  https://answers.launchpad.net/ubuntu/+question/685941

  Output of "ubuntu-bug linux":

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  Date: Mon Nov 18 16:46:39 2019
  Dependencies:
   adduser 3.118ubuntu1
   apt 1.9.4
   apt-utils 1.9.4
   binutils 2.33-2ubuntu1
   binutils-aarch64-linux-gnu 2.33-2ubuntu1
   binutils-common 2.33-2ubuntu1
   busybox-initramfs 1:1.30.1-4ubuntu4
   ca-certificates 20190110
   coreutils 8.30-3ubuntu2
   cpio 2.12+dfsg-9ubuntu0.1
   debconf 1.5.73
   debconf-i18n 1.5.73
   device-tree-compiler 1.4.7-3ubuntu2
   devio 1.2-1.2
   dpkg 1.19.7ubuntu2
   e2fsprogs 1.45.3-4ubuntu2
   fdisk 2.34-0.1ubuntu2
   flash-kernel 3.98ubuntu5.1
   gcc-9-base 9.2.1-9ubuntu2
   gpgv 2.2.12-1ubuntu3
   initramfs-tools 0.133ubuntu10
   initramfs-tools-bin 0.133ubuntu10
   initramfs-tools-core 0.133ubuntu10
   klibc-utils 2.0.6-1ubuntu3
   kmod 26-1ubuntu1
   libacl1 2.2.53-4
   libapt-pkg5.90 1.9.4
   libattr1 1:2.4.48-4
   libaudit-common 1:2.8.5-2ubuntu1
   libaudit1 1:2.8.5-2ubuntu1
   libbinutils 2.33-2ubuntu1
   libblkid1 2.34-0.1ubuntu2
   libbz2-1.0 1.0.6-9.2
   libc6 2.30-0ubuntu2
   libcap-ng0 0.7.9-2
   libcom-err2 1.45.3-4ubuntu2
   libdb5.3 5.3.28+dfsg1-0.6ubuntu1
   libext2fs2 1.45.3-4ubuntu2
   libfdisk1 2.34-0.1ubuntu2
   libffi6 3.2.1-9
   libgcc1 1:9.2.1-9ubuntu2
   libgcrypt20 1.8.4-5ubuntu2
   libgmp10 2:6.1.2+dfsg-4
   libgnutls30 3.6.9-5ubuntu1
   libgpg-error0 1.36-7
   libgpm2 1.20.7-5
   libhogweed4 3.4.1-1
   libidn2-0 2.2.0-2
   libklibc 2.0.6-1ubuntu3
   libkmod2 26-1ubuntu1
   liblocale-gettext-perl 1.07-3build3
   liblz4-1 1.9.1-1
   liblzma5 5.2.4-1
   liblzo2-2 2.10-0.1
   libmount1 2.34-0.1ubuntu2
   libncursesw6 6.1+20190803-1ubuntu1
   libnettle6 3.4.1-1
   libp11-kit0 0.23.17-2
   libpam-modules 1.3.1-5ubuntu1
   libpam-modules-bin 1.3.1-5ubuntu1
   libpam-runtime 1.3.1-5ubuntu1
   libpam0g 1.3.1-5ubuntu1
   libpcre2-8-0 10.32-5
   libseccomp2 2.4.1-0ubuntu0.19.10.3
   libselinux1 2.9-2
   libsemanage-common 2.9-3
   libsemanage1 2.9-3
   libsepol1 2.9-2
   libsmartcols1 2.34-0.1ubuntu2
   libss2 1.45.3-4ubuntu2
   libssl1.1 1.1.1c-1ubuntu4
   libstdc++6 9.2.1-9ubuntu2
   libsystemd0 242-7ubuntu3
   libtasn1-6 4.14-3
   libtext-charwidth-perl 0.04-9
   libtext-iconv-perl 1.7-6
   libtext-wrapi18n-perl 0.06-9
   libtinfo6 6.1+20190803-1ubuntu1
   libudev1 242-7ubuntu3
   libunistring2 0.9.10-2
   libuuid1 2.34-0.1ubuntu2
   libzstd1 1.4.3+dfsg-1
   linux-base 4.5ubuntu2
   linux-modules-5.3.0-1012-raspi2 5.3.0-1012.14
   login 1:4.5-1.1ubuntu4
   logsave 1.45.3-4ubuntu2
   lsb-base 11.0.1ubuntu1
   lz4 1.9.1-1
   mtd-utils 1:2.0.1-1ubuntu3
   openssl 1.1.1c-1ubuntu4
   passwd 1:4.5-1.1ubuntu4
   perl-base 5.28.1-6build1
   sensible-utils 0.0.12
   tar 1.30+dfsg-6
   u-boot-tools 2019.07+dfsg-1ubuntu3
   ubuntu-keyring 2018.09.18.1
   ucf 3.0038+nmu1
   udev 242-7ubuntu3
   util-linux 2.34-0.1ubuntu2
   uuid-runtime 2.34-0.1ubuntu2
   zlib1g

[Kernel-packages] [Bug 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

2019-11-24 Thread apsaras

Thank you for the reply.

Are you saying that you need confirmation from the original bug reporter
(Michael) that his problem still exists with the latest BIOS and latest
Ubuntu, and that confirmation from other people won't do because we
might have a different problem?

I can understand the reasoning behind that policy, but I think in this
case it's reasonably clear that we all have the same problem here. If we
were all to create separate bug reports describing exactly the same
symptoms then that would create confusing distractions and dilute the
good efforts of people like you, would it not?

Of course, if it's the only way to proceed then we can create a new
report. (Can we be sure that it won't immediately get closed as a
duplicate?)

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

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

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

Bug description:
  On initial boot, sound on internal speakers is working. After standby
  it doesn work anymore, but a analog headset does. Switching around in
  pavucontrol doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.

  Toshiba/Dynabook Portege Z20T-C:
  
https://support.dynabook.com/support/modelHome?freeText=1200015981=785

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

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

2019-11-24 Thread cinemaapk.in

watch pinoy tv channel and pinoy tv shows free
https://pinoytvz.su

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

Title:
  [Samsung NP530U3C-A01] LID close, AC, and battery status events not
  produced anymore

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery
  status events not produced anymore. The situation is the same (tested
  with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where
  I can put all the information related to this bug here:
  http://zenstep.com.ar/samsung-linux/

  In summary, after a suspend sleep with many events (8 plug/unplug, or
  battery dropping or increasing about 16%, maybe less), the Embedded
  Controller accumulates those events and stops producing GPE 0x17.
  Neither Windows nor Linux query those accumulated events, because the
  EC doesn't produce GPE 0x17 anymore. The issue persists between
  restarts and shutdowns, and even after re-suspending/re-resuming.
  Hitting the reset button through the hole in the back fixes the
  problem temporarily. That is, until the next unlucky suspend.

  IMPORTANT: if the laptop is never ever suspended, the issue never
  comes back.

  To force the issue to happen, you can either:
  1) Sleep the computer in linux (by closing the lid or any other means).
  2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 
actions or more).
  3) Resume from sleep. You'll note that the battery icon is fixed, and 
unplugging or plugging doesn't update battery status anymore. Also note that 
the ability to suspend by closing the LID is lost.

  OR:
  1) echo disable > /sys/firmware/acpi/interrupts/gpe17
  2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions)
  3) echo enable > /sys/firmware/acpi/interrupts/gpe17

  WORKAROUND: Turn off the computer, unplug it, hit the reset button in
  the back of the laptop, and then plug it again.

  WORKAROUND (kernel patch 1):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133

  BETTER WORKAROUND (kernel patch 2):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-11-generic 3.13.0-11.31
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2546 F pulseaudio
  CasperVersion: 1.337
  Date: Sat Feb 22 22:57:34 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed 
boot=casper  quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-11-generic N/A
   linux-backports-modules-3.13.0-11-generic  N/A
   linux-firmware 1.125
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

2019-11-24 Thread cinemaapk.in

watch your loving colors tv show online
https://biggboss13tvs.com

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

Title:
  [Samsung NP530U3C-A01] LID close, AC, and battery status events not
  produced anymore

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery
  status events not produced anymore. The situation is the same (tested
  with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where
  I can put all the information related to this bug here:
  http://zenstep.com.ar/samsung-linux/

  In summary, after a suspend sleep with many events (8 plug/unplug, or
  battery dropping or increasing about 16%, maybe less), the Embedded
  Controller accumulates those events and stops producing GPE 0x17.
  Neither Windows nor Linux query those accumulated events, because the
  EC doesn't produce GPE 0x17 anymore. The issue persists between
  restarts and shutdowns, and even after re-suspending/re-resuming.
  Hitting the reset button through the hole in the back fixes the
  problem temporarily. That is, until the next unlucky suspend.

  IMPORTANT: if the laptop is never ever suspended, the issue never
  comes back.

  To force the issue to happen, you can either:
  1) Sleep the computer in linux (by closing the lid or any other means).
  2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 
actions or more).
  3) Resume from sleep. You'll note that the battery icon is fixed, and 
unplugging or plugging doesn't update battery status anymore. Also note that 
the ability to suspend by closing the LID is lost.

  OR:
  1) echo disable > /sys/firmware/acpi/interrupts/gpe17
  2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions)
  3) echo enable > /sys/firmware/acpi/interrupts/gpe17

  WORKAROUND: Turn off the computer, unplug it, hit the reset button in
  the back of the laptop, and then plug it again.

  WORKAROUND (kernel patch 1):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133

  BETTER WORKAROUND (kernel patch 2):
  https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-11-generic 3.13.0-11.31
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2546 F pulseaudio
  CasperVersion: 1.337
  Date: Sat Feb 22 22:57:34 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed 
boot=casper  quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-11-generic N/A
   linux-backports-modules-3.13.0-11-generic  N/A
   linux-firmware 1.125
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1283589/+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 1838154] Re: Scrolling and responsiveness is artificially low (a few ideas: syntax, window manager logic)

2019-11-24 Thread klfytklfyt

An absurd idea is that something prints new lines somewhere.

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

Title:
  Scrolling and responsiveness is artificially low (a few ideas: syntax,
  window manager logic)

Status in NULL Project:
  New
Status in wayland:
  New
Status in Xfwm4:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xfwm4 package in Fedora:
  Unknown

Bug description:
  In XFCE4 is a trick to make temperatures cooler
  and win back simple responsiveness like scrolling
  or typing.

  Pls look at images.

  Settings: snapping top 1 and bottom 1

  Unix message trick: leave recipient empty type "idiot :))  "

  Additional info:
  two spaces bug  -  
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716
  https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2

  Templates bug  -  
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462
  https://bugzilla.redhat.com/show_bug.cgi?id=1729666

  :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1838154/+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 1853762] Re: Headphones stop working until pairing again

2019-11-24 Thread Guillaume Michaud

Full syslog : boot + unable to connect headphones + re-pairing and using
headphones

** Attachment added: "full_syslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+attachment/5307528/+files/full_syslog.txt

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

Title:
  Headphones stop working until pairing again

Status in bluez package in Ubuntu:
  New

Bug description:
  I'm using Marshall MID ANC headphones with Ubuntu 19.10.
  Every now and then, I won't be able to use them without re-pairing first 
(like today - see logs).
  After re-pairing, everything works again for a while : I can switch off and 
on the headphones, reboot... Until it breaks again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 24 19:13:40 2019
  InstallationDate: Installed on 2018-07-28 (483 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:AB:C5:7E:41:26  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:319948 acl:71 sco:0 events:45583 errors:0
TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+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 1853762] Re: Headphones stop working until pairing again

2019-11-24 Thread Guillaume Michaud

guillaume@massada:~$ bluetoothctl --version
bluetoothctl: 5.50
guillaume@massada:~$ hciconfig -a
hci0:   Type: Primary  Bus: USB
BD Address: 14:AB:C5:7E:41:26  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:319956 acl:71 sco:0 events:45584 errors:0
TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0
Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'massada'
Class: 0x1c010c
Service Classes: Rendering, Capturing, Object Transfer
Device Class: Computer, Laptop
HCI Version: 4.2 (0x8)  Revision: 0x100
LMP Version: 4.2 (0x8)  Subversion: 0x100
Manufacturer: Intel Corp. (2)

guillaume@massada:~$ bluetoothctl
Agent registered
[MID ANC]# show
Controller 14:AB:C5:7E:41:26 (public)
Name: massada
Alias: massada
Class: 0x001c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
UUID: Vendor specific   (5005--1000-8000-0002ee01)
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no
[MID ANC]# devices
Device 2C:4D:79:46:E7:5D MID ANC
Device CC:B8:A8:2D:B9:49 Somfy One B0F1EC0CE412
[MID ANC]# info 2C:4D:79:46:E7:5D
Device 2C:4D:79:46:E7:5D (public)
Name: MID ANC
Alias: MID ANC
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)

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

Title:
  Headphones stop working until pairing again

Status in bluez package in Ubuntu:
  New

Bug description:
  I'm using Marshall MID ANC headphones with Ubuntu 19.10.
  Every now and then, I won't be able to use them without re-pairing first 
(like today - see logs).
  After re-pairing, everything works again for a while : I can switch off and 
on the headphones, reboot... Until it breaks again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 24 19:13:40 2019
  InstallationDate: Installed on 2018-07-28 (483 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.308
  dmi.board.asset.tag:

[Kernel-packages] [Bug 1853762] [NEW] Headphones stop working until pairing again

2019-11-24 Thread Guillaume Michaud

Public bug reported:

I'm using Marshall MID ANC headphones with Ubuntu 19.10.
Every now and then, I won't be able to use them without re-pairing first (like 
today - see logs).
After re-pairing, everything works again for a while : I can switch off and on 
the headphones, reboot... Until it breaks again.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Nov 24 19:13:40 2019
InstallationDate: Installed on 2018-07-28 (483 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX410UAK
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago)
dmi.bios.date: 11/08/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX410UAK.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX410UAK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX410UAK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 14:AB:C5:7E:41:26  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:319948 acl:71 sco:0 events:45583 errors:0
TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0

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


** Tags: amd64 apport-bug eoan

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

Title:
  Headphones stop working until pairing again

Status in bluez package in Ubuntu:
  New

Bug description:
  I'm using Marshall MID ANC headphones with Ubuntu 19.10.
  Every now and then, I won't be able to use them without re-pairing first 
(like today - see logs).
  After re-pairing, everything works again for a while : I can switch off and 
on the headphones, reboot... Until it breaks again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 24 19:13:40 2019
  InstallationDate: Installed on 2018-07-28 (483 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:AB:C5:7E:41:26  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:319948 acl:71

[Kernel-packages] [Bug 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H

2019-11-24 Thread Bryon Nevis

$ uname -a
Linux bnevis-pi 5.3.0-1013-raspi2 #15+v3d SMP Sun Nov 24 13:41:44 CST 2019 
aarch64 aarch64 aarch64 GNU/Linux

[  219.338309] raspberrypi-firmware soc:firmware: Request 0x00048019 returned 
status 0x8001
[  219.373813] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI 
infoframe
[  219.381581] raspberrypi-firmware soc:firmware: Request 0x00048019 returned 
status 0x8001
[  225.633560] rfkill: input handler disabled
[  310.783944] v3d fec0.v3d: MMU error from client L2T (0) at 0x4b01000, 
pte invalid
[  310.815954] v3d fec0.v3d: MMU error from client L2T (0) at 0x62e1000, 
pte invalid
[  310.846816] v3d fec0.v3d: MMU error from client L2T (0) at 0x6601000, 
pte invalid
[  310.875666] v3d fec0.v3d: MMU error from client L2T (0) at 0x62e1000, 
pte invalid
[  310.896849] v3d fec0.v3d: MMU error from client L2T (0) at 0x6601000, 
pte invalid
[  310.947578] v3d fec0.v3d: MMU error from client L2T (0) at 0x6581000, 
pte invalid
[  310.982421] v3d fec0.v3d: MMU error from client L2T (0) at 0x7241000, 
pte invalid
[  316.647853] v3d fec0.v3d: MMU error from client L2T (0) at 0x1121000, 
pte invalid
[  316.661628] v3d fec0.v3d: MMU error from client L2T (0) at 0x65a1000, 
pte invalid
[  316.694090] v3d fec0.v3d: MMU error from client L2T (0) at 0x65c1000, 
pte invalid
[  316.718344] v3d fec0.v3d: MMU error from client L2T (0) at 0x6401000, 
pte invalid
[  316.742765] v3d fec0.v3d: MMU error from client L2T (0) at 0x6681000, 
pte invalid


glxinfo now reports the Broadcom rendering driver is being used (previously was 
VMware driver)
viewport issue still not fixed (but maybe in better shape to debug it)
kernel panic is resolved
pte invalid errors above occur when moving moving a foreground window that 
obscures a background window: noticable flickering and bleedthrough of 
background window while repainting.

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

Title:
  Cannot use full resolution (2560x1440) of Dell U2715H

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  While using Ubuntu 19.10 with either MATE or GNOME, I can use only
  1920x1080 resolution instead of the full 2560x1440.  If extra pixels
  are configured, they fall off the right side or bottom of the display
  and are not visible.  Reproduced on Raspberry Pi 4  with 3GB max
  workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: User Name 5.3.0-1008.9-raspi2 5.3.1
  Uname: Linux 5.3.0-1008-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 10 18:18:23 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M 
video=HDMI-A-1:1920x1080@60 smsc95xx.macaddr=DC:A6:32:38:DF:15 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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-raspi2/+bug/1852035/+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 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

2019-11-24 Thread Avio

*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790

I'm testing this new 5.3.0-1008-raspi2 kernel, USB works as expected but
I get a lot of

> mmc-bcm2835 fe30.mmcnr: could not get clk, deferring probe

in dmesg and /dev/mmcblk0p1 and /dev/mmcblk0p2 don't show up after
booting. Any workarounds for this? Thanks.

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

Title:
  Raspberry Pi 4 - USB Bus not detecting any devices

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Pi 4 new install.  System boots up but USB bus is not working.

  Tried 3 keyboards no key presses detected, 2 usb memory drives don't
  show up in lsblk.

  output of $lspci
  00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10)
  01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller 
(rev 01) 

  output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or
  attached to this bug report.

  Not the only one experiencing bug.  Another user created a post on the ubuntu 
forums: 
  
https://ubuntuforums.org/showthread.php?t=2429396=01a0c4b0cb4c05e605cbf9d41f660e08=13898142#post13898142


  64bit raspberry pi 4&4 image pulled from
  https://ubuntu.com/download/iot/raspberry-pi page.  Specifically
  http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10
  -preinstalled-server-arm64+raspi3.img.xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+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 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

2019-11-24 Thread Christopher M. Penalver

apsaras, it's helpful for developers if folks report their own bug so logs may 
be obtained from the hardware, regardless of similarities, via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

To do otherwise risks issues being ignored as unconfirmable noise.

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

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

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

Bug description:
  On initial boot, sound on internal speakers is working. After standby
  it doesn work anymore, but a analog headset does. Switching around in
  pavucontrol doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.

  Toshiba/Dynabook Portege Z20T-C:
  
https://support.dynabook.com/support/modelHome?freeText=1200015981=785

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

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

Re: [Kernel-packages] [Bug 1852884] Re: Qualcomm Atheros AR9227 wifi pci did not work

2019-11-24 Thread Pankaj

I did. I had a DVD of v14.04. it worked on it. Now, I have updated to 19.10
gradually. It is working fine.

On Thu, 21 Nov 2019, 10:31 pm Kai-Heng Feng, 
wrote:

> Would it be possible for you to do a reverse kernel bisection?
>
> First, find the first -rc kernel works and the last -rc kernel doesn’t
> work from http://kernel.ubuntu.com/~kernel-ppa/mainline/
>
> Then,
> $ sudo apt build-dep linux
> $ git clone git://
> git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> $ cd linux
> $ git bisect start
> $ git bisect new $(the working version you found)
> $ git bisect old $(the non-working version found)
> $ make localmodconfig
> $ make -j`nproc` deb-pkg
> Install the newly built kernel, then reboot with it.
> If it doesn’t work,
> $ git bisect old
> Otherwise,
> $ git bisect new
> Repeat to "make -j`nproc` deb-pkg" until you find the commit fixes the
> issue.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1852884
>
> Title:
>   Qualcomm Atheros AR9227 wifi pci did not work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852884/+subscriptions
>

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

Title:
  Qualcomm Atheros AR9227 wifi pci did not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Qualcomm Atheros AR9227 wifi pci did not work after upgrade.

  dmesg output:

 90.875175] ath: phy0: Mac Chip Rev 0xfffc0.f is not supported by this 
driver
  [   90.875179] ath: phy0: Unable to initialize hardware; initialization 
status: -95
  [   90.875182] ath9k :04:05.0: Failed to initialize device
  [   90.875338] ath9k: probe of :04:05.0 failed with error -95

  lspci -nnk output:

  04:05.0 Unclassified device [0080]: Qualcomm Atheros AR9227 Wireless Network 
Adapter [168c:002d] (rev 01)
Subsystem: Qualcomm Atheros AR9227 Wireless Network Adapter [168c:0101]
Kernel modules: ath9k

  It worked earlier.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-23-generic 5.3.0-23.25
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pks2321 F pulseaudio
   /dev/snd/controlC1:  pks2321 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 17 09:54:51 2019
  HibernationDevice: RESUME=UUID=36751e84-b0bc-4f92-93db-1e4b5ced3979
  InstallationDate: Installed on 2017-04-02 (958 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  IwConfig:
   enp0s22f2u3  no wireless extensions.

   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=99c76891-c019-4681-afee-0266d099d50b ro persistent splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-11-14 (2 days ago)
  dmi.bios.date: 05/01/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A88-M
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1702:bd05/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A88-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852884/+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 1739386] Re: [xhci_hcd] HC died · USB controller died, reboot necessary

2019-11-24 Thread bp0

My xhci_hcd bluetooth dies on Ubuntu 19.10 after about 2 days. I can't figure 
out at all why, so here's a workaround for novices like me to google.
The specific commands I use are

sudo su
echo -n ":00:14.0" | tee /sys/bus/pci/drivers/xhci_hcd/unbind
echo -n ":00:14.0" | tee /sys/bus/pci/drivers/xhci_hcd/bind

Then my bluetooth mouse worked again without having to reboot - hooray!

(sorry for abusing this bug)

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

Title:
  [xhci_hcd] HC died · USB controller died, reboot necessary

Status in linux package in Ubuntu:
  Expired

Bug description:
  * Ubuntu release: 17.04
  * uname -r: 4.10.0-42-generic
  * Expected behaviour: the USB ports run well
  * What happens: the USB ports are randomly killed from time to time

  * Explanation:
  The xhci_hcd driver reports that the xHCI host is not responding to a stop 
endpoint command. The USB host controller is then shut down and all USB ports 
are left dead until a reboot is performed. This is not immediate nor 
predictable --- sometimes, it can be days before it happens; sometimes it is 
just hours.

  If I understood correctly, there is no way to reload the kernel module
  of the USB driver, because it is baked into the kernel at compile
  time. Something like that? :)

  When rebooting, the shutdown process completes (it reports a "shutdown
  target achieved" or similar), but is unable to unmount the /home/user
  partition. Therefore, the system does not shutdown unless I press the
  power button (hard shutdown). I do not know if there is a way to get a
  TTY at that point to manually unmount the partition. The home folder
  is encrypted... I do not know if this has something to do with it, but
  this error only occurs when the USB HC is killed.

  I suspect the USB problem has to do with an external USB hub by TP-
  LINK. It seems to only fail when this device is connected. The hub
  model is UH400, by TP-LINK.

  Anything I can add, just ask for it!
  Thanks a lot!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739386/+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 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)

2019-11-24 Thread Charles Wilkins

To Robie Basak, specifically #22,

You said, "I don't see how we created another problem. We changed the default,
that's all."

You seem to have concluded that merely a change of default functionally
was made at some point.

Perhaps that is the case. If so, what specifically was the default
setting that was changed? For example, was it a kernel compilation time
option? If so, can you please specify what setting can be changed back
in order to re-enable Console blanking using DPMS (console display in
power saving mode) for Ubuntu server 18.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/869017

Title:
  Ubuntu server enables screenblanking, concealing crashdumps (DPMS is
  not used)

Status in kbd package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in kbd source package in Zesty:
  Invalid
Status in linux source package in Zesty:
  Fix Released
Status in kbd package in Debian:
  Fix Released

Bug description:
  James Rice of Jump Networks noticed that there is a screen-blanker
  enabled on Ubuntu Server.

  James notes that this blanking is not enabling DPMS power saving
  (thereby negating any power-saving benefit), and is simply turning the
  screen content blank.   This means that the crash output is invisible
  which is unhelpful on a server (virtual or otherwise).

  Ideally the screen should (at a minimum) be turned on and unblanked at
  the point of an OOPs/crash being printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+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 1852581] Re: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO

2019-11-24 Thread Adil Hussain

I got hit too...

This is a Precision 5520; had to revert kernel to 5.3.0-19-generic to
boot system.

I see segfaults in /dev/mapper/control and /dev/pts/ptmx when I'm dropped to 
initramfs shell.
My /etc/fstab is empty. /dev doesn't contain any device files of my hard drive.

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

Title:
  hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-hwe-edge source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-hwe-edge source package in Eoan:
  Invalid

Bug description:
  SRU Justification

  Impact: The fix for bug 1850234 does not function as intended in
  bionic, as a result of modinfo not knowing about module signatures.
  This results in no modules being signed in hwe kernels based on 5.3,
  rendering systems with secure boot enabled unbootable.

  Fix: Check for the module signature at the end of modules instead of
  relying on modinfo. This can be done without any external tools
  needing to be aware of module signatures.

  Test Case: Check that all built modules contain signatures, except for
  those in staging which have not been whitelisted.

  Regression Potential: I can think of two possible regression
  situations. We could regress to the behavior prior to the fix for bug
  1850234, or the eoan 5.3 kernel could also end up with all modules
  unsigned. I've done test builds of both the eoan 5.3 kernel and the
  bionic 5.3 hwe-edge kernel with this patch and checked that the
  results are as intended. We should also check this again once new
  kernels have been built, before copying them out to -proposed.

  ---

  The latest hwe-edge kernel 5.3.0-23.25 fails to boot with the message
  that it cannot find the UUID associated with the root partition. The
  user gets dropped to a busybox shell with an initramfs prompt. The
  standard hwe kernel does not have this issue and the last hwe-edge
  kernel that does work is 5.3.0-19.20.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic-hwe-18.04-edge 5.3.0.23.90
  ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 14 08:19:57 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-09-01 (73 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852581/+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 1852581] Re: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO

2019-11-24 Thread Adil Hussain

missed adding another comment...

I don't have hwe-edge installed.

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

Title:
  hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-hwe-edge source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-hwe-edge source package in Eoan:
  Invalid

Bug description:
  SRU Justification

  Impact: The fix for bug 1850234 does not function as intended in
  bionic, as a result of modinfo not knowing about module signatures.
  This results in no modules being signed in hwe kernels based on 5.3,
  rendering systems with secure boot enabled unbootable.

  Fix: Check for the module signature at the end of modules instead of
  relying on modinfo. This can be done without any external tools
  needing to be aware of module signatures.

  Test Case: Check that all built modules contain signatures, except for
  those in staging which have not been whitelisted.

  Regression Potential: I can think of two possible regression
  situations. We could regress to the behavior prior to the fix for bug
  1850234, or the eoan 5.3 kernel could also end up with all modules
  unsigned. I've done test builds of both the eoan 5.3 kernel and the
  bionic 5.3 hwe-edge kernel with this patch and checked that the
  results are as intended. We should also check this again once new
  kernels have been built, before copying them out to -proposed.

  ---

  The latest hwe-edge kernel 5.3.0-23.25 fails to boot with the message
  that it cannot find the UUID associated with the root partition. The
  user gets dropped to a busybox shell with an initramfs prompt. The
  standard hwe kernel does not have this issue and the last hwe-edge
  kernel that does work is 5.3.0-19.20.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic-hwe-18.04-edge 5.3.0.23.90
  ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 14 08:19:57 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-09-01 (73 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852581/+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 1767568] Re: Console DPMS is not enabled by default in Ubuntu Server 18.04

2019-11-24 Thread Charles Wilkins

To Robie Basak, specifically with regards to #37.

The title of this bug already specified particularly that Console DPMS
is not working. This bug report already was not about simply console
blanking.

I understand that the original reporter said that he got it working with
setterm, but as by convention these bug reports often require
verification from others in order to get any attention, it seems only
reasonable that after many have said that the DPMS power saving is what
is not working, while simple blanking and leaving the monitor on is what
is currently happening, that this bug should not have been marked
invalid.

As many others have pointed out, Console DPMS power saving is not
working in 18.04. It is clear after reading this thread as well as a few
basic tests with setterm that nobody has working Console DPMS power
saving at all in Ubuntu 18.04.

If this is only a matter of default settings as you seem to have
concluded that it is, then please specify which optional setting re-
enables Console DPMS power saving, because the following does NOT work
on any of my Ubuntu 18.04 installations (as well as several others in
this bug report) beyond mere blanking and leaving the monitor on:

in grub.cfg
consoleblank=600

setterm --powersave powerdown
setterm --powerdown 10

If this is just a kernel option that is no longer the default setting,
then it should be specified here, in this bug report, what the
appropriate change is to revert back to a very mature working
functionality.

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

Title:
  Console DPMS is not enabled by default in Ubuntu Server 18.04

Status in linux package in Ubuntu:
  Invalid

Bug description:
  My console display is DPMS capable, i.e., power management functions
  worked before upgrading from Ubuntu Server 16.0.4.4.  Currently the
  display stays on 24x7 with idle keyboard input.

  1) My release information is as follows:

  Description:Ubuntu 18.04 LTS
  Release:18.04

  2) I am not sure what package this issue is tied to.  The current
  kernel appears to have DPMS support enabled, per the configuration
  file in /boot.  If the kernel is responsible, below is the version I
  am running.

  linux-generic:
  Installed: 4.15.0.20.23

  3) I expected to have DPMS support for my console as in the previous
  release of Ubuntu Server.

  4) What happened instead is my monitor stays on all the time, without DPMS 
controlling it.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-20-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
'/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11
  InstallationDate: Installed on 2014-07-23 (1378 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Gigabyte Technology Co., Ltd. X58A-UD5
  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 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 03/11/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5

[Kernel-packages] [Bug 1853738] Re: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

2019-11-24 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu mate

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.4.0-96 4.4.0-96.119
  ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
  Uname: Linux 4.4.0-166-generic i686
  ApportVersion: 2.20.1-0ubuntu2.21
  AptOrdering:
   libdjvulibre-text: Install
   linux-headers-4.4.0-96: Configure
   libdjvulibre-text: Configure
   NULL: ConfigurePending
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johnnyreb   2460 F pulseaudio
  Date: Sun Nov 24 09:32:00 2019
  DpkgTerminalLog:
   Preparing to unpack .../libdjvulibre-text_3.5.27.1-5ubuntu0.1_all.deb ...
   Unpacking libdjvulibre-text (3.5.27.1-5ubuntu0.1) over (3.5.27.1-5) ...
   dpkg: error processing package linux-headers-4.4.0-96 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature:
   package:linux-headers-4.4.0-96:4.4.0-96.119
   Unpacking libdjvulibre-text (3.5.27.1-5ubuntu0.1) over (3.5.27.1-5) ...
   dpkg: error processing package linux-headers-4.4.0-96 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=6783c982-9133-4a7b-b7fb-a98cc9f16216
  InstallationDate: Installed on 2016-09-06 (1173 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-166-generic 
root=UUID=f010cd2c-4c9f-4785-b4ce-c0df263752d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.23
  SourcePackage: linux
  Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1221
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1221:bd11/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

2019-11-24 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/1853738

Title:
  package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu mate

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.4.0-96 4.4.0-96.119
  ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
  Uname: Linux 4.4.0-166-generic i686
  ApportVersion: 2.20.1-0ubuntu2.21
  AptOrdering:
   libdjvulibre-text: Install
   linux-headers-4.4.0-96: Configure
   libdjvulibre-text: Configure
   NULL: ConfigurePending
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johnnyreb   2460 F pulseaudio
  Date: Sun Nov 24 09:32:00 2019
  DpkgTerminalLog:
   Preparing to unpack .../libdjvulibre-text_3.5.27.1-5ubuntu0.1_all.deb ...
   Unpacking libdjvulibre-text (3.5.27.1-5ubuntu0.1) over (3.5.27.1-5) ...
   dpkg: error processing package linux-headers-4.4.0-96 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature:
   package:linux-headers-4.4.0-96:4.4.0-96.119
   Unpacking libdjvulibre-text (3.5.27.1-5ubuntu0.1) over (3.5.27.1-5) ...
   dpkg: error processing package linux-headers-4.4.0-96 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=6783c982-9133-4a7b-b7fb-a98cc9f16216
  InstallationDate: Installed on 2016-09-06 (1173 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-166-generic 
root=UUID=f010cd2c-4c9f-4785-b4ce-c0df263752d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.23
  SourcePackage: linux
  Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1221
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1221:bd11/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853738/+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 1853738] [NEW] package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

2019-11-24 Thread John Hall

Public bug reported:

Ubuntu mate

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-headers-4.4.0-96 4.4.0-96.119
ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
Uname: Linux 4.4.0-166-generic i686
ApportVersion: 2.20.1-0ubuntu2.21
AptOrdering:
 libdjvulibre-text: Install
 linux-headers-4.4.0-96: Configure
 libdjvulibre-text: Configure
 NULL: ConfigurePending
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  johnnyreb   2460 F pulseaudio
Date: Sun Nov 24 09:32:00 2019
DpkgTerminalLog:
 Preparing to unpack .../libdjvulibre-text_3.5.27.1-5ubuntu0.1_all.deb ...
 Unpacking libdjvulibre-text (3.5.27.1-5ubuntu0.1) over (3.5.27.1-5) ...
 dpkg: error processing package linux-headers-4.4.0-96 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
DuplicateSignature:
 package:linux-headers-4.4.0-96:4.4.0-96.119
 Unpacking libdjvulibre-text (3.5.27.1-5ubuntu0.1) over (3.5.27.1-5) ...
 dpkg: error processing package linux-headers-4.4.0-96 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
HibernationDevice: RESUME=UUID=6783c982-9133-4a7b-b7fb-a98cc9f16216
InstallationDate: Installed on 2016-09-06 (1173 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
MachineType: System manufacturer System Product Name
PackageArchitecture: all
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-166-generic 
root=UUID=f010cd2c-4c9f-4785-b4ce-c0df263752d3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.23
SourcePackage: linux
Title: package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/01/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1221
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5B-Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1221:bd11/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: apport-package i386 xenial

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

Title:
  package linux-headers-4.4.0-96 4.4.0-96.119 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu mate

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.4.0-96 4.4.0-96.119
  ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
  Uname: Linux 4.4.0-166-generic i686
  ApportVersion: 2.20.1-0ubuntu2.21
  AptOrdering:
   libdjvulibre-text: Install
   linux-headers-4.4.0-96: Configure
   libdjvulibre-text: Configure
   NULL: ConfigurePending
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johnnyreb   2460 F pulseaudio
  Date: Sun Nov 24 09:32:00 2019
  DpkgTerminalLog:
   Preparing to unpack .../libdjvulibre-text_3.5.27.1-5ubuntu0.1_all.deb ...
   Unpacking libdjvulibre-text (3.5.27.1-5ubuntu0.1) over (3.5.27.1-5) ...
   dpkg: error processing package linux-headers-4.4.0-96 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature:
   package:linux-headers-4.4.0-96:4.4.0-96.119
   Unpacking libdjvulibre-text (3.5.27.1-5ubuntu0.1) over (3.5.27.1-5) ...
   dpkg: error processing package linux-headers-4.4.0-96 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=6783c982-9133-4a7b-b7fb-a98cc9f16216
  InstallationDate: Installed on 2016-09-06 (1173 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all

[Kernel-packages] [Bug 1853030] Re: No connection through SSH over WIfi after kernel update