date:20191026

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 1849927

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

Title:
  Installation failed when choose iommu in VMware Player

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

Bug description:
  Host OS: Windows 10
  VMware Workstation Player version: 15.5.0 build-14665864
  Virtualization engine: Virtualize IOMMU (IO memory managment unit)
  Virtual OS: Ubuntu 19.10

  Step:

  1. Choose Virtualize IOMMU in virtualization engine of VMware
  2. Boot the virtual machine
  3. Stuck on Boot Animation

  And the log shows as the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1849927/+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 1840043] Re: bcache: Performance degradation when querying priority_stats

2019-10-26 Thread Heitor Alves de Siqueira

Verified on bionic with test case from description:
# uname -r  

4.15.0-67-generic

Write performance dropped from ~150MB/s to ~147MB/s, and the system is
still responsive.

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

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

Title:
  bcache: Performance degradation when querying priority_stats

Status in Linux:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  Querying bcache's priority_stats attribute in sysfs causes severe performance 
degradation for read/write workloads and occasional system stalls

  [Test Case]
  Note: As the sorting step has the most noticeable performance impact, the 
test case below pins a workload and the sysfs query to the same CPU. CPU 
contention issues still occur without any pinning, this just removes the 
scheduling factor of landing in different CPUs and affecting different tasks.

  1) Start a read/write workload on the bcache device with e.g. fio or dd, 
pinned to a certain CPU:
  # taskset 0x10 dd if=/dev/zero of=/dev/bcache0 bs=4k status=progress

  2) Start a sysfs query loop for the priority_stats attribute pinned to the 
same CPU:
  # for i in {1..10}; do taskset 0x10 cat 
/sys/fs/bcache/*/cache0/priority_stats > /dev/null; done

  3) Monitor the read/write workload for any performance impact

  [Fix]
  To fix CPU contention and performance impact, a cond_resched() call is 
introduced in the priority_stats sort comparison.

  [Regression Potential]
  Regression potential is low, as the change is confined to the priority_stats 
sysfs query. In cases where frequent queries to bcache priority_stats take 
place (e.g. node_exporter), the impact should be more noticeable as those could 
now take a bit longer to complete. A regression due to this patch would most 
likely show up as a performance degradation in bcache-focused workloads.

  --

  [Description]
  In the latest bcache drivers, there's a sysfs attribute that calculates 
bucket priority statistics in /sys/fs/bcache/*/cache0/priority_stats. Querying 
this file has a big performance impact on tasks that run in the same CPU, and 
also affects read/write performance of the bcache device itself.

  This is due to the way the driver calculates the stats: the bcache
  buckets are locked and iterated through, collecting information about
  each individual bucket. An array of nbucket elements is constructed
  and sorted afterwards, which can cause very high CPU contention in
  cases of larger bcache setups.

  From our tests, the sorting step of the priority_stats query causes
  the most expressive performance reduction, as it can hinder tasks that
  are not even doing any bcache IO. If a task is "unlucky" to be
  scheduled in the same CPU as the sysfs query, its performance will be
  harshly reduced as both compete for CPU time. We've had users report
  systems stalls of up to ~6s due to this, as a result from monitoring
  tools that query the priority_stats periodically (e.g. Prometheus Node
  Exporter from [0]). These system stalls have triggered several other
  issues such as ceph-mon re-elections, problems in percona-cluster and
  general network stalls, so the impact is not isolated to bcache IO
  workloads.

  An example benchmark can be seen in [1], where the read performance on
  a bcache device suffered quite heavily (going from ~40k IOPS to ~4k
  IOPS due to priority_stats). Other comparison charts are found under
  [2].

  [0] https://github.com/prometheus/node_exporter
  [1] 
https://people.canonical.com/~halves/priority_stats/read/4k-iops-2Dsmooth.png
  [2] https://people.canonical.com/~halves/priority_stats/

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1840043/+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 1840043] Re: bcache: Performance degradation when querying priority_stats

2019-10-26 Thread Heitor Alves de Siqueira

Verified on disco with test case from description:
# uname -r
5.0.0-33-generic

Write performance wasn't significantly affected in this test,
fluctuating between ~120MB/s and ~110MB/s.

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

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

Title:
  bcache: Performance degradation when querying priority_stats

Status in Linux:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  Querying bcache's priority_stats attribute in sysfs causes severe performance 
degradation for read/write workloads and occasional system stalls

  [Test Case]
  Note: As the sorting step has the most noticeable performance impact, the 
test case below pins a workload and the sysfs query to the same CPU. CPU 
contention issues still occur without any pinning, this just removes the 
scheduling factor of landing in different CPUs and affecting different tasks.

  1) Start a read/write workload on the bcache device with e.g. fio or dd, 
pinned to a certain CPU:
  # taskset 0x10 dd if=/dev/zero of=/dev/bcache0 bs=4k status=progress

  2) Start a sysfs query loop for the priority_stats attribute pinned to the 
same CPU:
  # for i in {1..10}; do taskset 0x10 cat 
/sys/fs/bcache/*/cache0/priority_stats > /dev/null; done

  3) Monitor the read/write workload for any performance impact

  [Fix]
  To fix CPU contention and performance impact, a cond_resched() call is 
introduced in the priority_stats sort comparison.

  [Regression Potential]
  Regression potential is low, as the change is confined to the priority_stats 
sysfs query. In cases where frequent queries to bcache priority_stats take 
place (e.g. node_exporter), the impact should be more noticeable as those could 
now take a bit longer to complete. A regression due to this patch would most 
likely show up as a performance degradation in bcache-focused workloads.

  --

  [Description]
  In the latest bcache drivers, there's a sysfs attribute that calculates 
bucket priority statistics in /sys/fs/bcache/*/cache0/priority_stats. Querying 
this file has a big performance impact on tasks that run in the same CPU, and 
also affects read/write performance of the bcache device itself.

  This is due to the way the driver calculates the stats: the bcache
  buckets are locked and iterated through, collecting information about
  each individual bucket. An array of nbucket elements is constructed
  and sorted afterwards, which can cause very high CPU contention in
  cases of larger bcache setups.

  From our tests, the sorting step of the priority_stats query causes
  the most expressive performance reduction, as it can hinder tasks that
  are not even doing any bcache IO. If a task is "unlucky" to be
  scheduled in the same CPU as the sysfs query, its performance will be
  harshly reduced as both compete for CPU time. We've had users report
  systems stalls of up to ~6s due to this, as a result from monitoring
  tools that query the priority_stats periodically (e.g. Prometheus Node
  Exporter from [0]). These system stalls have triggered several other
  issues such as ceph-mon re-elections, problems in percona-cluster and
  general network stalls, so the impact is not isolated to bcache IO
  workloads.

  An example benchmark can be seen in [1], where the read performance on
  a bcache device suffered quite heavily (going from ~40k IOPS to ~4k
  IOPS due to priority_stats). Other comparison charts are found under
  [2].

  [0] https://github.com/prometheus/node_exporter
  [1] 
https://people.canonical.com/~halves/priority_stats/read/4k-iops-2Dsmooth.png
  [2] https://people.canonical.com/~halves/priority_stats/

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1840043/+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 1849721] Re: Raydium Touchscreen on ThinkPad L390 does not work

2019-10-26 Thread Kai-Heng Feng

Can you please poweroff the system before booting into the custom
kernel?

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

Title:
  Raydium Touchscreen on ThinkPad L390 does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have bought new Lenovo ThinkPad L390 with touchscreen and it works fine on 
Windows, but not on Ubuntu.
  I've tried Ubuntu LTS 18.4, 19.4 and 19.10. I've tried installing Ubuntu and 
running Live USB image, and also other distributions (Manjaro i3, Kubuntu).
  There is an Ubuntu certification with the same touchscreen using Ubuntu 18.4: 
https://certification.ubuntu.com/hardware/201812-26720

  Other info:
  - `xinput` is showing touchscreen: "Raydium Touchscreen id=10 [slave pointer 
(2)]"
  - if I list device props using `xinput list-props 10`, I see device: `Device 
Node (277): "/dev/input/event9"`
  - `cat /dev/input/event9` does not produce anything
  - `xinput --test-xi2 --root` does not produce any touchscreen events, even 
though events from other devices are successfully shown

  Also, attached `ubuntu-bug` report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1821 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 24 18:32:07 2019
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20NRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R10ET39W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NRCTO1WW:pvrThinkPadL390:rvnLENOVO:rn20NRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L390
  dmi.product.name: 20NRCTO1WW
  dmi.product.sku: LENOVO_MT_20NR_BU_Think_FM_ThinkPad L390
  dmi.product.version: ThinkPad L390
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849721/+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 1840043] Re: bcache: Performance degradation when querying priority_stats

2019-10-26 Thread Heitor Alves de Siqueira

Verified on eoan with test case from description:
# uname -r
5.3.0-20-generic 

Performance kept steady throughout the priority_stat sysfs query.

** Tags removed: 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/1840043

Title:
  bcache: Performance degradation when querying priority_stats

Status in Linux:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  Querying bcache's priority_stats attribute in sysfs causes severe performance 
degradation for read/write workloads and occasional system stalls

  [Test Case]
  Note: As the sorting step has the most noticeable performance impact, the 
test case below pins a workload and the sysfs query to the same CPU. CPU 
contention issues still occur without any pinning, this just removes the 
scheduling factor of landing in different CPUs and affecting different tasks.

  1) Start a read/write workload on the bcache device with e.g. fio or dd, 
pinned to a certain CPU:
  # taskset 0x10 dd if=/dev/zero of=/dev/bcache0 bs=4k status=progress

  2) Start a sysfs query loop for the priority_stats attribute pinned to the 
same CPU:
  # for i in {1..10}; do taskset 0x10 cat 
/sys/fs/bcache/*/cache0/priority_stats > /dev/null; done

  3) Monitor the read/write workload for any performance impact

  [Fix]
  To fix CPU contention and performance impact, a cond_resched() call is 
introduced in the priority_stats sort comparison.

  [Regression Potential]
  Regression potential is low, as the change is confined to the priority_stats 
sysfs query. In cases where frequent queries to bcache priority_stats take 
place (e.g. node_exporter), the impact should be more noticeable as those could 
now take a bit longer to complete. A regression due to this patch would most 
likely show up as a performance degradation in bcache-focused workloads.

  --

  [Description]
  In the latest bcache drivers, there's a sysfs attribute that calculates 
bucket priority statistics in /sys/fs/bcache/*/cache0/priority_stats. Querying 
this file has a big performance impact on tasks that run in the same CPU, and 
also affects read/write performance of the bcache device itself.

  This is due to the way the driver calculates the stats: the bcache
  buckets are locked and iterated through, collecting information about
  each individual bucket. An array of nbucket elements is constructed
  and sorted afterwards, which can cause very high CPU contention in
  cases of larger bcache setups.

  From our tests, the sorting step of the priority_stats query causes
  the most expressive performance reduction, as it can hinder tasks that
  are not even doing any bcache IO. If a task is "unlucky" to be
  scheduled in the same CPU as the sysfs query, its performance will be
  harshly reduced as both compete for CPU time. We've had users report
  systems stalls of up to ~6s due to this, as a result from monitoring
  tools that query the priority_stats periodically (e.g. Prometheus Node
  Exporter from [0]). These system stalls have triggered several other
  issues such as ceph-mon re-elections, problems in percona-cluster and
  general network stalls, so the impact is not isolated to bcache IO
  workloads.

  An example benchmark can be seen in [1], where the read performance on
  a bcache device suffered quite heavily (going from ~40k IOPS to ~4k
  IOPS due to priority_stats). Other comparison charts are found under
  [2].

  [0] https://github.com/prometheus/node_exporter
  [1] 
https://people.canonical.com/~halves/priority_stats/read/4k-iops-2Dsmooth.png
  [2] https://people.canonical.com/~halves/priority_stats/

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1840043/+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 1849953] [NEW] Kernel Oops: 0002 [#1] SMP PTI - kernel NULL pointer dereference; RIP is at 0010:queue_work_on+0x1b/0x50

2019-10-26 Thread David

Public bug reported:

The kernel oops seems to happen when the laptop is left idle. It doesn't
appear every time, so it is hard to reproduce. System is completely
unresponsive after it and hard reboot is needed. I also observed
identical freezes on Ubuntu 19.04, but never bothered to fill a bug
report. I haven't observed this error on Ubuntu 18.04.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-19-generic 5.3.0-19.20
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  david  1625 F pulseaudio
 /dev/snd/pcmC0D0p:   david  1625 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 26 13:53:07 2019
InstallationDate: Installed on 2019-10-24 (1 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20LW0010GE
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=20db2748-18f3-45cc-b013-010ae1b24637 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-19-generic N/A
 linux-backports-modules-5.3.0-19-generic  N/A
 linux-firmware1.183.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/03/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET57W (1.34 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LW0010GE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET57W(1.34):bd06/03/2019:svnLENOVO:pn20LW0010GE:pvrThinkPadL580:rvnLENOVO:rn20LW0010GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L580
dmi.product.name: 20LW0010GE
dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580
dmi.product.version: ThinkPad L580
dmi.sys.vendor: LENOVO

** Affects: linux (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 linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849953

Title:
  Kernel Oops: 0002 [#1] SMP PTI  - kernel NULL pointer dereference; RIP
  is at 0010:queue_work_on+0x1b/0x50

Status in linux package in Ubuntu:
  New

Bug description:
  The kernel oops seems to happen when the laptop is left idle. It
  doesn't appear every time, so it is hard to reproduce. System is
  completely unresponsive after it and hard reboot is needed. I also
  observed identical freezes on Ubuntu 19.04, but never bothered to fill
  a bug report. I haven't observed this error on Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-19-generic 5.3.0-19.20
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1625 F pulseaudio
   /dev/snd/pcmC0D0p:   david  1625 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 13:53:07 2019
  InstallationDate: Installed on 2019-10-24 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20LW0010GE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=20db2748-18f3-45cc-b013-010ae1b24637 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET57W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LW0010GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET57W(1.34):bd06/03/2019:svnLENOVO:pn20LW0010GE:pvrThinkPadL580:rvnLENOVO:rn20LW0010GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L580
  dmi.product.name: 20LW0010GE
  dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580
  dmi.product.version: ThinkPad L580
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849953/+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 1849953] Re: Kernel Oops: 0002 [#1] SMP PTI - kernel NULL pointer dereference; RIP is at 0010:queue_work_on+0x1b/0x50

2019-10-26 Thread David

** Attachment added: "bug_dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849953/+attachment/5300355/+files/bug_dmesg.txt

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

Title:
  Kernel Oops: 0002 [#1] SMP PTI  - kernel NULL pointer dereference; RIP
  is at 0010:queue_work_on+0x1b/0x50

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel oops seems to happen when the laptop is left idle. It
  doesn't appear every time, so it is hard to reproduce. System is
  completely unresponsive after it and hard reboot is needed. I also
  observed identical freezes on Ubuntu 19.04, but never bothered to fill
  a bug report. I haven't observed this error on Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-19-generic 5.3.0-19.20
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1625 F pulseaudio
   /dev/snd/pcmC0D0p:   david  1625 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 13:53:07 2019
  InstallationDate: Installed on 2019-10-24 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20LW0010GE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=20db2748-18f3-45cc-b013-010ae1b24637 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET57W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LW0010GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET57W(1.34):bd06/03/2019:svnLENOVO:pn20LW0010GE:pvrThinkPadL580:rvnLENOVO:rn20LW0010GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L580
  dmi.product.name: 20LW0010GE
  dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580
  dmi.product.version: ThinkPad L580
  dmi.sys.vendor: LENOVO

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

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

Title:
  Kernel Oops: 0002 [#1] SMP PTI  - kernel NULL pointer dereference; RIP
  is at 0010:queue_work_on+0x1b/0x50

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel oops seems to happen when the laptop is left idle. It
  doesn't appear every time, so it is hard to reproduce. System is
  completely unresponsive after it and hard reboot is needed. I also
  observed identical freezes on Ubuntu 19.04, but never bothered to fill
  a bug report. I haven't observed this error on Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-19-generic 5.3.0-19.20
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1625 F pulseaudio
   /dev/snd/pcmC0D0p:   david  1625 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 13:53:07 2019
  InstallationDate: Installed on 2019-10-24 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20LW0010GE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=20db2748-18f3-45cc-b013-010ae1b24637 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET57W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LW0010GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET57W(1.34):bd06/03/2019:svnLENOVO:pn20LW0010GE:pvrThinkPadL580:rvnLENOVO:rn20LW0010GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L580
  dmi.product.name: 20LW0010GE
  dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580
  dmi.product.version: ThinkPad L580
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849953/+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 1849953] Re: Kernel Oops: 0002 [#1] SMP PTI - kernel NULL pointer dereference; RIP is at 0010:queue_work_on+0x1b/0x50

2019-10-26 Thread David

Attachment which contains kernel oops.

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

Title:
  Kernel Oops: 0002 [#1] SMP PTI  - kernel NULL pointer dereference; RIP
  is at 0010:queue_work_on+0x1b/0x50

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel oops seems to happen when the laptop is left idle. It
  doesn't appear every time, so it is hard to reproduce. System is
  completely unresponsive after it and hard reboot is needed. I also
  observed identical freezes on Ubuntu 19.04, but never bothered to fill
  a bug report. I haven't observed this error on Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-19-generic 5.3.0-19.20
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1625 F pulseaudio
   /dev/snd/pcmC0D0p:   david  1625 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 13:53:07 2019
  InstallationDate: Installed on 2019-10-24 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20LW0010GE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=20db2748-18f3-45cc-b013-010ae1b24637 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET57W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LW0010GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET57W(1.34):bd06/03/2019:svnLENOVO:pn20LW0010GE:pvrThinkPadL580:rvnLENOVO:rn20LW0010GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L580
  dmi.product.name: 20LW0010GE
  dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580
  dmi.product.version: ThinkPad L580
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849953/+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 1848212] Re: Optane PM access times are much longer than they should be

2019-10-26 Thread steve heller

https://lore.kernel.org/linux-nvdimm/CAPcyv4gi--MyxXOt-
vb4Tw+ku=juymo4y+ysv+6ujf24bcd...@mail.gmail.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/1848212

Title:
  Optane PM access times are much longer than they should be

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have 4 128GB Optane DC Persistent Memory devices in my server,
  assigned to AppDirect access (i.e., accessed via memory-mapping at the
  cache line level), and have run into a severe performance issue with
  the latest kernel 5.0.0-31.

  I realize that not many people have this storage type as yet, but it
  is becoming increasingly important in the server world, so I think
  this bug is pretty important.

  Bug details:

  When running with kernel 5.0.0-29, write access times to the Optane PM
  devices are in the sub-microsecond range, as they should be.

  When running with kernel 5.0.0-31, write access times are much slower,
  averaging in the 30 microsecond range, until a large number of writes
  (see below) have been executed. Then they return to normal speed.

  My application is a hash table implementation optimized for the Optane
  PM devices (see webpage at www.threemisses.com). Since it is a hash
  table, it has very poor locality of reference, and is filled
  "randomly", so I don't know exactly what the sequence of writes is.

  However, I can say that the speed is very slow until the fill ratio of
  the hash table is about 50%, then it returns to the normal sub-
  microsecond range.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Tue Oct 15 09:01:06 2019
  InstallationDate: Installed on 2019-09-02 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   lono wireless extensions.

   eno0  no wireless extensions.

   enp181s0f1  no wireless extensions.
  MachineType: Supermicro SYS-7039A-I
  ProcEnviron:
   LD_LIBRARY_PATH=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=3239f211-86a3-44bb-8251-62037ebea848 ro transparent_hugepage=always 
quiet splash nomodeset vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: ZM193S000653
  dmi.board.name: X11DAi-N
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd03/06/2019:svnSupermicro:pnSYS-7039A-I:pvr123456789:rvnSupermicro:rnX11DAi-N:rvr1.02:cvnSupermicro:ct1:cvr123456789:
  dmi.product.family: SMC X11
  dmi.product.name: SYS-7039A-I
  dmi.product.sku: 097A15D9
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848212/+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 1848987] Re: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker

** Description changed:

  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: 1848989
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 24. October 2019 14:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-edge: bug 1848986
bionic/linux-azure/azure-kernel: bug 1848985
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1024.25~18.04.1 -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:
  Invalid
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 stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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: 1848989
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 24. October 2019 14:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-edge: bug 1848986
bionic/linux-azure/azure-kernel: bug 1848985
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848987/+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 1848212] Re: Optane PM access times are much longer than they should be

2019-10-26 Thread steve heller

Is there an estimate as to when you are likely to pick up this fix?

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

Title:
  Optane PM access times are much longer than they should be

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have 4 128GB Optane DC Persistent Memory devices in my server,
  assigned to AppDirect access (i.e., accessed via memory-mapping at the
  cache line level), and have run into a severe performance issue with
  the latest kernel 5.0.0-31.

  I realize that not many people have this storage type as yet, but it
  is becoming increasingly important in the server world, so I think
  this bug is pretty important.

  Bug details:

  When running with kernel 5.0.0-29, write access times to the Optane PM
  devices are in the sub-microsecond range, as they should be.

  When running with kernel 5.0.0-31, write access times are much slower,
  averaging in the 30 microsecond range, until a large number of writes
  (see below) have been executed. Then they return to normal speed.

  My application is a hash table implementation optimized for the Optane
  PM devices (see webpage at www.threemisses.com). Since it is a hash
  table, it has very poor locality of reference, and is filled
  "randomly", so I don't know exactly what the sequence of writes is.

  However, I can say that the speed is very slow until the fill ratio of
  the hash table is about 50%, then it returns to the normal sub-
  microsecond range.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Tue Oct 15 09:01:06 2019
  InstallationDate: Installed on 2019-09-02 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   lono wireless extensions.

   eno0  no wireless extensions.

   enp181s0f1  no wireless extensions.
  MachineType: Supermicro SYS-7039A-I
  ProcEnviron:
   LD_LIBRARY_PATH=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=3239f211-86a3-44bb-8251-62037ebea848 ro transparent_hugepage=always 
quiet splash nomodeset vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: ZM193S000653
  dmi.board.name: X11DAi-N
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd03/06/2019:svnSupermicro:pnSYS-7039A-I:pvr123456789:rvnSupermicro:rnX11DAi-N:rvr1.02:cvnSupermicro:ct1:cvr123456789:
  dmi.product.family: SMC X11
  dmi.product.name: SYS-7039A-I
  dmi.product.sku: 097A15D9
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848212/+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 1849947] [NEW] Dell XPS 13 (7390) Display Flickering - 19.10

You have been subscribed to a public bug:

Hi there,
I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to 
replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, 
there is one issue which occurs frequently whereby the display flickers and 
becomes unusable. The best way to describe the appearance is that the image 
becomes heavily distorted. 

Sometimes it only happens for a split second, other times it is
permanently distorted. When this happens, simply closing the laptop lip
and re-opening seems to put the display back into it's correct state.

I didn't experience this issue on 18.04 LTS which is why I believe it's
a Software Bug within 19.10.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 26 11:11:43 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0962]
InstallationDate: Installed on 2019-10-25 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Dell Inc. XPS 13 7390
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.3
dmi.board.name: 0G2D0W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390
dmi.product.sku: 0962
dmi.sys.vendor: Dell Inc.
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 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan ubuntu
-- 
Dell XPS 13 (7390) Display Flickering - 19.10 
https://bugs.launchpad.net/bugs/1849947
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10

2019-10-26 Thread Timo Aaltonen

please test with latest drm-tip kernel from

https://kernel.ubuntu.com/~kernel-ppa/mainline/

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

Title:
  Dell XPS 13 (7390) Display Flickering - 19.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi there,
  I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to 
replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, 
there is one issue which occurs frequently whereby the display flickers and 
becomes unusable. The best way to describe the appearance is that the image 
becomes heavily distorted. 

  Sometimes it only happens for a split second, other times it is
  permanently distorted. When this happens, simply closing the laptop
  lip and re-opening seems to put the display back into it's correct
  state.

  I didn't experience this issue on 18.04 LTS which is why I believe
  it's a Software Bug within 19.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 11:11:43 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2019-10-25 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  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 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849947/+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 1849057] Re: eoan/linux-aws: 5.3.0-1005.5 -proposed tracker

** Description changed:

  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: 1849064
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 24. October 2019 14:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-aws: 5.3.0-1005.5 -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:
  Invalid
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 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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Eoan:
  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: 1849064
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 24. October 2019 14:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-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/1849057/+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 1848995] Re: disco/linux-gcp: 5.0.0-1024.24 -proposed tracker

** Description changed:

  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: 1849003
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 24. October 2019 15:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp: bug 1848992
bionic/linux-gke-5.0: bug 1848994
  variant: debs

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

Title:
  disco/linux-gcp: 5.0.0-1024.24 -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:
  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:
  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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1849003
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 24. October 2019 15:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-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-gcp: bug 1848992
bionic/linux-gke-5.0: bug 1848994
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848995/+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 1849061] Re: eoan/linux-kvm: 5.3.0-1005.5 -proposed tracker

** Description changed:

  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: 1849064
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Thursday, 24. October 2019 15:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-kvm: 5.3.0-1005.5 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  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-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Eoan:
  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: 1849064
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Thursday, 24. October 2019 15:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-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/1849061/+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 1849056] Re: eoan/linux-raspi2: 5.3.0-1009.10 -proposed tracker

** Description changed:

  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: 1849064
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Thursday, 24. October 2019 15:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1009.10 -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:
  Confirmed
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 Eoan:
  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: 1849064
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Thursday, 24. October 2019 15:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  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
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849056/+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 1848992] Re: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -proposed tracker

** Description changed:

  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: 1848995
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 24. October 2019 14:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-edge: bug 1848991
bionic/linux-gcp/gcp-kernel: bug 1848990
  variant: debs

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

Title:
  bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -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:
  Invalid
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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1848995
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 24. October 2019 14:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-edge: bug 1848991
bionic/linux-gcp/gcp-kernel: bug 1848990
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848992/+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 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

2019-10-26 Thread Emmanuel Schmidbauer

im having the exact same problem on fresh install of 19.04
solution is to run this command (in terminal) after the machine boots:

xrandr --output eDP-1 --rotate normal

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

Title:
  [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

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

Bug description:
  On the 19.04 daily image (2019-03-24), the screen on my laptop is
  completely upside down, from the moment the GUI loads. This does not
  happen on 18.04 and 18.10.

  It appears to be an accelerometer issue since holding the laptop
  upside down flips the image to its correct orientation - basically the
  functionality of the accelerometer is suddenly inverted.

  Please contact me if you want me to help testing the issue on my hardware. 
Thanks!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sharper1380 F pulseaudio
   /dev/snd/controlC1:  sharper1380 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-30 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190330)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=1e4bdc5f-0616-42f3-8da2-4ec27df3fc55 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/12/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.44
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: 5CG4430MGN
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.44:bd04/12/2018:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.sku: D1F44AV
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821641/+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 1849064] Re: eoan/linux: 5.3.0-20.21 -proposed tracker

** Description changed:

  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, 24. October 2019 16:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1849063
eoan/linux-aws: bug 1849057
eoan/linux-azure: bug 1849058
eoan/linux-gcp: bug 1849060
eoan/linux-kvm: bug 1849061
eoan/linux-oracle: bug 1849062
eoan/linux-raspi2: bug 1849056
  variant: debs

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

Title:
  eoan/linux: 5.3.0-20.21 -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:
  Confirmed
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 Eoan:
  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, 24. October 2019 16:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
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-hwe-edge: bug 1849063
eoan/linux-aws: bug 1849057
eoan/linux-azure: bug 1849058
eoan/linux-gcp: bug 1849060
eoan/linux-kvm: bug 1849061
eoan/linux-oracle: bug 1849062
eoan/linux-raspi2: bug 1849056
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849064/+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 1845716] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returne

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bcmwl (Ubuntu)
   Status: New => Confirmed

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

Title:
  package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to
  install/upgrade: installed bcmwl-kernel-source package post-
  installation script subprocess returned error exit status 10

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Sep 27 23:20:40 2019
  ErrorMessage: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2017-10-07 (720 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to 
install/upgrade: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1845716/+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 1849751] Re: [i915] doesn't boot after 19.10 upgrade

2019-10-26 Thread Tessa

Oh damn, didn't realize nomodeset disables *everything* these days.

in any case, I'm on an optimus laptop with both intel and nvidia, and I
can switch between nvidia only, or optimus (both cards active) mode in
the bios. prior to 19.10, things worked fine. but after 19.10, things
have been an utter mess. no combination of drivers / bios will boot
without nomodeset, period. so something has seriously fucked up the
modeset drivers in this release. and with nomodeset, the only things
that work is straight intel driver in optimus mode, or straight nouveau
in discrete mode. the nv binary drivers do not work no matter what I do.

note that this is consistent when booted off a 19.10 live usb too, so it
does seem to be a pretty major regression since 19.04. as well, when I
can actually at least get a terminal console (which is not possible in
discrete bios mode + nv binary drivers), it seems like gpu-manager is
doing some odd things. even if the nv binary drivers are installed, it
always says something like "desktop system or open drivers, nothing to
do", which is clearly inaccurate.

I'll definitely try some of the newer kernel packages listed here and
get back to you, because my system is a mess right now.

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

Title:
  [i915] doesn't boot after 19.10 upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after upgrading to ubuntu 19.10, vulkan support when using the intel
  card in my laptop is broken. running any of my example vulkan apps
  shows the following error:

  $ vkcube
  vkcube: 
/build/vulkan-tools-IZAxVX/vulkan-tools-1.1.114.0+dfsg1/cube/cube.c:3175: 
demo_init_vk: Assertion `!err' failed.
  Aborted (core dumped)

  note that since the update I can no longer boot my system at all
  without adding "nomodeset" the kernel params, something is broken in
  the intel modeset driver since 19.04. so this may very well be
  related.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mesa-vulkan-drivers 19.2.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 24 20:04:54 2019
  DistUpgraded: 2019-10-23 18:54:04,373 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: zfs, 0.8.1, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer HD Graphics 630 [1558:65a1]
   NVIDIA Corporation GP104BM [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GP104BM [GeForce GTX 1070 Mobile] 
[1558:65a3]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd Chicony USB 
2.0 Camera
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. EgisTec_ES603
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Oryx Pro
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=ZFS=rpool/root 
ro root=ZFS=rpool/root quiet nomodeset
  SourcePackage: mesa
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (1 days ago)
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76
  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 19.2.1-1ubuntu1
  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 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go t

[Kernel-packages] [Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20

2019-10-26 Thread mm_202

HP Spectre x360 affected with kernel 5.3.0-19-generic.

Is there  a way to turn this sensor off??

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

Title:
  hid-sensor-hub spamming dmesg in 4.20

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

Bug description:
  === SRU Justification ===
  [Impact]
  [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called 
with n (192) > 32! (kworker/5:1)

  [Fix]
  Let HID core allow longer input report length.

  [Test]
  User confirmed the fix works.

  [Regression Potential]
  Low. Longer input report length is now considered valid, shorter input
  report length doesn't get touched.

  === Original Bug Report ===

  Dmesg is a constant barrage of the same error:
  ```
  [  406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called 
with n (192) > 32! (kworker/5:1)
  ```

  This does not occur in 4.19 but does occur in all mainline 4.20
  releases including 4.20.13 (linux-image-unsigned-4.20.13-042013).
  Tested with both Ubuntu's included libinput 1.10 and an updated
  libinput 1.12.

  Hardware (from lspci) includes a synaptic touchpad. Having the xorg
  synaptic driver installed makes no difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+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 1849981] [NEW] package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

2019-10-26 Thread elevenfive

Public bug reported:

Was upgrading to 19.10 and encountered this

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: zfs-dkms 0.8.1-1ubuntu14
ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Sat Oct 26 10:28:20 2019
ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
InstallationDate: Installed on 2013-06-08 (2331 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
PackageArchitecture: all
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: zfs-linux
Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)

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


** Tags: amd64 apport-package eoan

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

Title:
  package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed
  zfs-dkms package post-installation script subprocess returned error
  exit status 10

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Was upgrading to 19.10 and encountered this

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfs-dkms 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sat Oct 26 10:28:20 2019
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2013-06-08 (2331 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: zfs-linux
  Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849981/+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 1849981] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

2019-10-26 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 zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849981

Title:
  package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed
  zfs-dkms package post-installation script subprocess returned error
  exit status 10

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Was upgrading to 19.10 and encountered this

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfs-dkms 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sat Oct 26 10:28:20 2019
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2013-06-08 (2331 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: zfs-linux
  Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849981/+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 1849982] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

2019-10-26 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 zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849982

Title:
  package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed
  zfs-dkms package post-installation script subprocess returned error
  exit status 10

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Package is really zfs-dkms but bug tool no have

  upgrading 19.04 - 19.10 mac Mini

     Processing triggers for initramfs-tools (0.133ubuntu10) ...
     This system doesn't support Secure Boot
     Secure Boot not enabled on this system.
     Errors were encountered while processing:
  zfs-dkms

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfs-dkms 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zlua zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sat Oct 26 12:22:09 2019
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2019-06-20 (128 days ago)
  InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 
(20190416.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: zfs-linux
  Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849982/+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 1849982] [NEW] package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

2019-10-26 Thread Roy

Public bug reported:

Package is really zfs-dkms but bug tool no have

upgrading 19.04 - 19.10 mac Mini

   Processing triggers for initramfs-tools (0.133ubuntu10) ...
   This system doesn't support Secure Boot
   Secure Boot not enabled on this system.
   Errors were encountered while processing:
zfs-dkms

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: zfs-dkms 0.8.1-1ubuntu14
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zlua zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Sat Oct 26 12:22:09 2019
ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
InstallationDate: Installed on 2019-06-20 (128 days ago)
InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 
(20190416.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: zfs-linux
Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)

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


** Tags: amd64 apport-package eoan

** Description changed:

+ Package is really zfs-dkms but bug tool no have
+ 
  upgrading 19.04 - 19.10 mac Mini
  
-Processing triggers for initramfs-tools (0.133ubuntu10) ...
-This system doesn't support Secure Boot
-Secure Boot not enabled on this system.
-Errors were encountered while processing:
- zfs-dkms
+    Processing triggers for initramfs-tools (0.133ubuntu10) ...
+    This system doesn't support Secure Boot
+    Secure Boot not enabled on this system.
+    Errors were encountered while processing:
+ zfs-dkms
  
  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfs-dkms 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zlua zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sat Oct 26 12:22:09 2019
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2019-06-20 (128 days ago)
  InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 
(20190416.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
-  dpkg 1.19.7ubuntu2
-  apt  1.9.4
+  dpkg 1.19.7ubuntu2
+  apt  1.9.4
  SourcePackage: zfs-linux
  Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)

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

Title:
  package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed
  zfs-dkms package post-installation script subprocess returned error
  exit status 10

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Package is really zfs-dkms but bug tool no have

  upgrading 19.04 - 19.10 mac Mini

     Processing triggers for initramfs-tools (0.133ubuntu10) ...
     This system doesn't support Secure Boot
     Secure Boot not enabled on this system.
     Errors were encountered while processing:
  zfs-dkms

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfs-dkms 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zlua zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sat Oct 26 12:22:09 2019
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2019-06-20 (128 days ago)
  InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 
(20190416.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: zfs-linux
  Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms p

[Kernel-packages] [Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20

2019-10-26 Thread Mark Borgerding

This is blasting 3.45 million messages into my dmesg per day ( at least
no longer in syslog thanks to @incognito666 )


Dell XPS 13 7390 2-in-1 Ubuntu 19.10 kernel 5.3.0-19-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/1818547

Title:
  hid-sensor-hub spamming dmesg in 4.20

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

Bug description:
  === SRU Justification ===
  [Impact]
  [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called 
with n (192) > 32! (kworker/5:1)

  [Fix]
  Let HID core allow longer input report length.

  [Test]
  User confirmed the fix works.

  [Regression Potential]
  Low. Longer input report length is now considered valid, shorter input
  report length doesn't get touched.

  === Original Bug Report ===

  Dmesg is a constant barrage of the same error:
  ```
  [  406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called 
with n (192) > 32! (kworker/5:1)
  ```

  This does not occur in 4.19 but does occur in all mainline 4.20
  releases including 4.20.13 (linux-image-unsigned-4.20.13-042013).
  Tested with both Ubuntu's included libinput 1.10 and an updated
  libinput 1.12.

  Hardware (from lspci) includes a synaptic touchpad. Having the xorg
  synaptic driver installed makes no difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+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 1849993] Re: DualShock 4 over Bluetooth does not work

2019-10-26 Thread Lastique

The problem exists in the mainline kernel 5.3.7 and does NOT exist with
5.2.21. I cannot test 5.4-rc4 because Nvidia driver doesn't compile for
this kernel.

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

Title:
  DualShock 4 over Bluetooth does not work

Status in linux package in Ubuntu:
  New

Bug description:
  Connecting Sony DualShock 4 over Bluetooth does not work on kernel
  5.3. After pressing the PS button on the gamepad, the LED blinks for a
  few seconds while connecting and then stays constantly lit when
  Bluetooth connection is established. However, while "connected", lsusb
  doesn't show the gamepad and it doesn't work in games.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-lowlatency 5.3.0.19.22
  ProcVersionSignature: Ubuntu 5.3.0-19.20-lowlatency 5.3.1
  Uname: Linux 5.3.0-19-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lastique   2092 F pulseaudio
   /dev/snd/controlC0:  lastique   2092 F pulseaudio
   /dev/snd/controlC2:  lastique   2092 F pulseaudio
   /dev/snd/controlC1:  lastique   2092 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 26 23:55:45 2019
  HibernationDevice:
   # Prevents "gave up waiting for suspend/resume device" timeout on boot
   RESUME=none
  InstallationDate: Installed on 2015-05-01 (1639 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-lowlatency 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-lowlatency N/A
   linux-backports-modules-5.3.0-19-lowlatency  N/A
   linux-firmware   1.183.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  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.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849993/+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 1849993] [NEW] DualShock 4 over Bluetooth does not work

2019-10-26 Thread Lastique

Public bug reported:

Connecting Sony DualShock 4 over Bluetooth does not work on kernel 5.3.
After pressing the PS button on the gamepad, the LED blinks for a few
seconds while connecting and then stays constantly lit when Bluetooth
connection is established. However, while "connected", lsusb doesn't
show the gamepad and it doesn't work in games.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-lowlatency 5.3.0.19.22
ProcVersionSignature: Ubuntu 5.3.0-19.20-lowlatency 5.3.1
Uname: Linux 5.3.0-19-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  lastique   2092 F pulseaudio
 /dev/snd/controlC0:  lastique   2092 F pulseaudio
 /dev/snd/controlC2:  lastique   2092 F pulseaudio
 /dev/snd/controlC1:  lastique   2092 F pulseaudio
CurrentDesktop: KDE
Date: Sat Oct 26 23:55:45 2019
HibernationDevice:
 # Prevents "gave up waiting for suspend/resume device" timeout on boot
 RESUME=none
InstallationDate: Installed on 2015-05-01 (1639 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-lowlatency 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-19-lowlatency N/A
 linux-backports-modules-5.3.0-19-lowlatency  N/A
 linux-firmware   1.183.1
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)
dmi.bios.date: 11/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V PRO
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.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: linux (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 linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849993

Title:
  DualShock 4 over Bluetooth does not work

Status in linux package in Ubuntu:
  New

Bug description:
  Connecting Sony DualShock 4 over Bluetooth does not work on kernel
  5.3. After pressing the PS button on the gamepad, the LED blinks for a
  few seconds while connecting and then stays constantly lit when
  Bluetooth connection is established. However, while "connected", lsusb
  doesn't show the gamepad and it doesn't work in games.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-lowlatency 5.3.0.19.22
  ProcVersionSignature: Ubuntu 5.3.0-19.20-lowlatency 5.3.1
  Uname: Linux 5.3.0-19-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lastique   2092 F pulseaudio
   /dev/snd/controlC0:  lastique   2092 F pulseaudio
   /dev/snd/controlC2:  lastique   2092 F pulseaudio
   /dev/snd/controlC1:  lastique   2092 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 26 23:55:45 2019
  HibernationDevice:
   # Prevents "gave up waiting for suspend/resume device" timeout on boot
   RESUME=none
  InstallationDate: Installed on 2015-05-01 (1639 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-lowlatency 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-lowlatency N/A
   linux-backports-modules-5.3.0-19-lowlatency  N/A
   linux-firmware   1.183.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset

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

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

Title:
  DualShock 4 over Bluetooth does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Connecting Sony DualShock 4 over Bluetooth does not work on kernel
  5.3. After pressing the PS button on the gamepad, the LED blinks for a
  few seconds while connecting and then stays constantly lit when
  Bluetooth connection is established. However, while "connected", lsusb
  doesn't show the gamepad and it doesn't work in games.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-lowlatency 5.3.0.19.22
  ProcVersionSignature: Ubuntu 5.3.0-19.20-lowlatency 5.3.1
  Uname: Linux 5.3.0-19-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lastique   2092 F pulseaudio
   /dev/snd/controlC0:  lastique   2092 F pulseaudio
   /dev/snd/controlC2:  lastique   2092 F pulseaudio
   /dev/snd/controlC1:  lastique   2092 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 26 23:55:45 2019
  HibernationDevice:
   # Prevents "gave up waiting for suspend/resume device" timeout on boot
   RESUME=none
  InstallationDate: Installed on 2015-05-01 (1639 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-lowlatency 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-lowlatency N/A
   linux-backports-modules-5.3.0-19-lowlatency  N/A
   linux-firmware   1.183.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  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.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849993/+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 1842173] Re: ubuntu 18.04.3 install /dev/sda1 could not boot up

2019-10-26 Thread Seiichi Nakashima

I test to install ubuntu-18.04.2 and 18.04.2 at UEFI PC using CMS.
upload syslog file


ubuntu-18.04.3-UEFI-syslog : install /dev/sda1 boot from pbr, but could not 
start up
ubuntu-18.04.2-UEFI-syslog : install /dev/sda1 boot from pbr, could start up


I found to delete kernel parameter splash, then could start up

ubunut-18.04.3-UEFI-grub-syslog : update /etc/default/grub and update-grub, 
could start up
grub : update GRUB_CMDLINE_LINUX_DEFAULT="quiet"

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

Title:
  ubuntu 18.04.3 install /dev/sda1 could not boot up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My PC use ASrock H110M-HVD mother(version P7.60).
  CPU is intel i3-7100, and Geforece 1050i.
  Geforce only use CUDA sysytem, not to use VGA. VGA use onboard chip.
  I use CSM to use mbr.

  This PC /dev/sda disk has four partitions for primary partition to use mbr.
  I install ubuntu-18.04.3 Japanese edition to /dev/sda to use mount point /.
  boot loader install /dev/sda1 named pbr.

  My PC mbr use mbm039 that is multi-boot-loader for mbr.
  boot from /dev/sda1, but could not start.
  purple screen dots that are change red to white for ever.

  I boot from /dev/sda4, that is installed ubuntu-18.04.2.
  and get syslog in /dev/sda1. upload syslog.
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842173/+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 1847892] Re: large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel

2019-10-26 Thread arQon

I expect so. I don't usually have a machine available to run as a server
though, hence the preference for rsync.

If you're concerned that the NAS might be the bottleneck, don't be.
That's a sensible point to raise, but it's GbE and saturates it wired.
(To say nothing of the months during which the rsync consistenly hit
80+).

If you think iperf might narrow the scope of where to look though, let me know 
and I'll try it next time I can dedicate a machine to it: shouldn't be more 
than a week.
(hmm - I could run one up in a VM at will, which would still have more than 
enough network performance for this, but I'm not sure I'd fully trust the 
results from that until I've got a baseline to compare against. I'll try to 
remember it when I boot the client off an older kernel).

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

Title:
  large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Probably relevant:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795116

  Card is an RTL8723BE.

  On 16.04 with the HWE stack, after 1795116 was fixed performance was a
  stable 75-80Mb/s.

  Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
  Fri 26-Jul-19 12:28
  sent 459,277,171 bytes  received 35 bytes  9,278,327.39 bytes/sec

  Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
  Sat 27-Jul-19 01:23
  sent 459,277,171 bytes  received 35 bytes  10,320,836.09 bytes/sec

  On 18.04, performance was still a stable 75-80Mb/s.

  After updating to 19.10, performance is typically ~50Mb/s, or about a
  37% regression.

  $ iwconfig wlan0
  wlan0 IEEE 802.11  ESSID:"**"  
Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB  
 
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=59/70  Signal level=-51 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:315   Missed beacon:0

  $ ./wifibench.sh 
  Linux 5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
  Sat 12-Oct-19 20:30
  sent 459,277,171 bytes  received 35 bytes  5,566,996.44 bytes/sec

  $ iwconfig wlan0 
  wlan0 IEEE 802.11  ESSID:"**"  
Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB  
 
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=68/70  Signal level=-42 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:315   Missed beacon:0

  So no corrupted packets or etc during that transfer.

  $ ifconfig wlan0
  wlan0: flags=4163  mtu 1500
  inet 192.168.1.33  netmask 255.255.255.0  broadcast 192.168.1.255
  ether dc:85:de:e4:17:a3  txqueuelen 1000  (Ethernet)
  RX packets 56608204  bytes 79066485957 (79.0 GB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 21634510  bytes 8726094217 (8.7 GB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  No issues of any kind in the week that it's been up. Just terrible
  performance.

  I'm painfully aware of all the module's parameters etc, and have tried
  them all, with no change in the results outside of typical wifi
  variance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847892/+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 1848964] Re: ubuntu-18.04.3 iso boot up, but hung up few minutes leater

2019-10-26 Thread Seiichi Nakashima

I checked ubuntu-18.04.3 Japanese edition at UEFI PC(i3-7100 CPU),
but same situation not occur.
perhaps this problem is older pc only.

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

Title:
  ubuntu-18.04.3 iso boot up, but hung up few minutes leater

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I boot up ubuntu-18.04.3 iso from grub2.
  I write 40_custom file to this.

  menuentry "Ubuntu 18.04.3 Remix ISO" {
  set isoimg="/homesv/module/iso/ubuntu-ja-18.04.3-desktop-amd64.iso"
  loopback loop (hd1,1)$isoimg
  linux (loop)/casper/vmlinuz boot=casper toram iso-scan/filename=$isoimg
  initrd (loop)/casper/initrd.lz
  }

  boot up normal, then nautilus and terminal start up.
  few minutes later(perhaps 2 or 3 minutes), Dock(icom displayed) earse from 
screen,
  I can not move mouse, and key input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848964/+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 1837688] Re: Ubuntu won't boot on Dell Inspiron 7375

2019-10-26 Thread Agustin-ferrario

Flickr free boot on Eoan! I'll need it to test it in Disco

** Tags removed: 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/1837688

Title:
  Ubuntu won't boot on Dell Inspiron 7375

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is unable to boot from the installation USB on a Dell Inspiron 7375, 
with a Ryzen CPU. This affects Ubuntu 19.10 (latest daily), 19.04 and 18.04.2 
(videos of each unsuccessful boot will be attached).
  I was able to boot using a workaround, by adding to the kernel line:

  amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2

  You can see it here:
  https://askubuntu.com/questions/1036357/ubuntu-18-04-wont-boot-on-
  dell-inspiron-7375

  I used this workaround to run the apport-bug tool.

  The problem should be in an ubuntu specific vendor patch or configuration 
since I was able to boot successfully in:
  * CentOS 7 (kernel 3.10)
  * OpenSUSE Leap 15.1 (kernel 4.12.14)
  * OpenSUSE tumbleweed (kernel 5.1.16)
  * Fedora 30 (kernel 5.0.9)
  * Manjaro (kernel 4.19)
  * SystemRescueCd (kernel 4.19.34)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.0.0-20-generic 5.0.0-20.21
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2186 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2186 F pulseaudio
  CasperVersion: 1.411
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 23 21:14:36 2019
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
  MachineType: Dell Inc. Inspiron 7375
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed amd_iommu=on ivrs_ioapic[4]=00:14.0 
ivrs_ioapic[5]=00:00.2 ---
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.180
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0GTNWX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.5.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd07/09/2018:svnDellInc.:pnInspiron7375:pvr1.5.0:rvnDellInc.:rn0GTNWX:rvrA00:cvnDellInc.:ct10:cvr1.5.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7375
  dmi.product.sku: 0884
  dmi.product.version: 1.5.0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837688/+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 1840650] Re: System crashes under nfs heavy load

[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/1840650

Title:
  System crashes under nfs heavy load

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi all.

  We have an NFSv4 server hosted in GCP with relative heavy load (read
  over nfs and write over ssh/rsync). After upgrade from 14.04 to 18.04
  this server started to crash approx. once a day or two. We have
  similar box with same configuration but without nfs load (cold spare)
  and this problem does not affect it.

  I've tried multiple kernels listed below, this did not help.
  linux-image-4.15.0-1026-gcp
  linux-image-4.15.0-55-generic
  linux-image-4.18.0-1008-gcp
  linux-image-4.18.0-1015-gcp
  linux-image-4.19.36
  linux-image-5.0.0-1011-gcp
  linux-image-5.2.5

  NFS packages:
  ii  libnfsidmap2:amd640.25-5.1
amd64NFS idmapping library
  ii  nfs-common1:1.3.4-2.1ubuntu5.2
amd64NFS support files common to client and server
  ii  nfs-kernel-server 1:1.3.4-2.1ubuntu5.2
amd64support for NFS kernel server

  Crash info:

KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-55-generic
  DUMPFILE: /var/crash_/201908190304/dump.201908190304  [PARTIAL DUMP]
  CPUS: 32
  DATE: Mon Aug 19 03:04:28 2019
UPTIME: 06:05:53
  LOAD AVERAGE: 7.56, 6.82, 6.77
 TASKS: 627
  NODENAME: storage-gce-be-1.project.domain.net
   RELEASE: 4.15.0-55-generic
   VERSION: #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019
   MACHINE: x86_64  (2300 Mhz)
MEMORY: 120 GB
 PANIC: "BUG: unable to handle kernel paging request at 
9e9119d39b78"
   PID: 112
   COMMAND: "ksoftirqd/17"
  TASK: 9e96bfcc8000  [THREAD_INFO: 9e96bfcc8000]
   CPU: 17
 STATE: TASK_RUNNING (PANIC)

  A part of crash log:

  [86915.179808] WARNING: CPU: 17 PID: 3917 at 
/build/linux-aAn8fZ/linux-4.15.0/lib/radix-tree.c:783 delete_node+0x87/0x1f0
  [86915.179810] Modules linked in: tcp_diag inet_diag binfmt_misc 
ip6table_filter ip6_tables iptable_filter sch_fq_codel ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
nls_iso8859_1 sb_edac intel_rapl_perf input_leds mac_hid serio_raw pvpanic nfsd 
auth_rpcgss nfs_acl lockd grace sunrpc netconsole ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helper cryptd psmouse virtio_net virtio_scsi i2c_piix4
  [86915.179859] CPU: 17 PID: 3917 Comm: kworker/u64:3 Not tainted 
4.15.0-55-generic #60-Ubuntu
  [86915.179860] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [86915.179877] Workqueue: nfsd4_callbacks nfsd4_run_cb_work [nfsd]
  [86915.179880] RIP: 0010:delete_node+0x87/0x1f0
  [86915.179881] RSP: 0018:b97087e0fd78 EFLAGS: 00010206
  [86915.179882] RAX: 9e81839df6d8 RBX: 9e81839df6c0 RCX: 

  [86915.179883] RDX:  RSI: 9e9119d39b60 RDI: 
9e9119d39b78
  [86915.179884] RBP: b97087e0fda0 R08:  R09: 
0034
  [86915.179884] R10: 9e9119d39b88 R11: 0035 R12: 
9e96b6304840
  [86915.179885] R13:  R14: 84583630 R15: 

  [86915.179887] FS:  () GS:9e96c724() 
knlGS:
  [86915.179887] CS:  0010 DS:  ES:  CR0: 80050033
  [86915.179888] CR2: 7fdbe3df9ba8 CR3: 0002fba0a006 CR4: 
001606e0
  [86915.179893] DR0:  DR1:  DR2: 

  [86915.179894] DR3:  DR6: fffe0ff0 DR7: 
0400
  [86915.179895] Call Trace:
  [86915.179901]  __radix_tree_delete+0x7f/0xa0
  [86915.179903]  radix_tree_delete_item+0x6a/0xc0
  [86915.179910]  nfs4_put_stid+0x3d/0x90 [nfsd]
  [86915.179915]  nfsd4_cb_recall_release+0x15/0x20 [nfsd]
  [86915.179920]  nfsd4_run_cb_work+0xd4/0xf0 [nfsd]
  [86915.179924]  process_one_work+0x1de/0x410
  [86915.179926]  worker_thread+0x32/0x410
  [86915.179928]  kthread+0x121/0x140
  [86915.179930]  ? process_one_work+0x410/0x410
  [86915.179932]  ? kthread_create_worker_on_cpu+0x70/0x70
  [86915.179935]  ret_from_fork+0x35/0x40
  [86915.179936] Code: c2 41 8b 04 24 a9 00 00 00 02 75 09 25 ff ff ff 03 41 89 
04 24 49 c7 44 24 08 00 00 00 00 48 8b 46 18 48 39 f8 0f 84 2d 01 00 00 <0f> 0b 
4c 89 f6 e8 2f

[Kernel-packages] [Bug 1687130] Re: NFS client input/output-error on kernel >=4.9

[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/1687130

Title:
  NFS client input/output-error on kernel >=4.9

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

Bug description:
  I'm experiencing input/output errors on mounting NFS-shares, starting
  from kernel 4.9 and above.

  No errors logged to syslog, but the system reports IO-errors when
  reading from the mount after only a few seconds. Doesn't matter which
  program that are accessing the disk.

  My problems started after upgrading to ubuntu 17.04, but I have
  narrowed it down to being present from ubuntu kernel 4.9 and above by
  installing kernels from the ubuntu kernel ppa - i.e. when downgrading
  to latest 4.8-kernel from the PPA, NFS starts working as expected even
  on ubuntu 17.04. So it's definetely kernel related.

  Probably not a hardware error either as the bug is present when NFS is
  mounted over both eth0 and wlan0.

  Only special thing in my setup is that NFS is mounted over an ssh-
  tunnel.

  The NFS server runs an completely up to date ubuntu 16.04 LTS install.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-11 (991 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Package: linux (not installed)
  Tags:  zesty
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (12 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687130/+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 1687130] Re: NFS client input/output-error on kernel >=4.9

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

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

Title:
  NFS client input/output-error on kernel >=4.9

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

Bug description:
  I'm experiencing input/output errors on mounting NFS-shares, starting
  from kernel 4.9 and above.

  No errors logged to syslog, but the system reports IO-errors when
  reading from the mount after only a few seconds. Doesn't matter which
  program that are accessing the disk.

  My problems started after upgrading to ubuntu 17.04, but I have
  narrowed it down to being present from ubuntu kernel 4.9 and above by
  installing kernels from the ubuntu kernel ppa - i.e. when downgrading
  to latest 4.8-kernel from the PPA, NFS starts working as expected even
  on ubuntu 17.04. So it's definetely kernel related.

  Probably not a hardware error either as the bug is present when NFS is
  mounted over both eth0 and wlan0.

  Only special thing in my setup is that NFS is mounted over an ssh-
  tunnel.

  The NFS server runs an completely up to date ubuntu 16.04 LTS install.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-11 (991 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Package: linux (not installed)
  Tags:  zesty
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (12 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True

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

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

@Hui Wang,
But if I can't use the keyborad by USB, how can I type in those cmd?

-- 
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&s=01a0c4b0cb4c05e605cbf9d41f660e08&p=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 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

@reply #21,

The simplest workaround is to plug the sd card into a cardreader and
connect the cardreader to computer, then edit $mount_folder/system-
boot/config.txt

Add total_mem=3072 in the section [pi4], just like below:

[pi4]
kernel=uboot_rpi_4.bin
max_framebuffers=2
total_mem=3072

Then reboot, you could you the usb keyboard now, after installing the
testing kernel, you could remove total_mem=3072.

And another way to login is to use ssh.

--
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&s=01a0c4b0cb4c05e605cbf9d41f660e08&p=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 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

And for me, I run commands through serial console, and if you have the
uart->usb converter, you could use serial console too.

--
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&s=01a0c4b0cb4c05e605cbf9d41f660e08&p=13898142#post13898142

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

[Kernel-packages] [Bug 1847980] Re: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work

2019-10-26 Thread Timo Aaltonen

great, then try 5.4-rc1 hoping that it's broken there, then a fix would
be fairly easy to spot

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

Title:
  Lightdm is just a black screen when booting kernel 5.3 on an i5-6500,
  but kernels 5.0/5.2 work

Status in lightdm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Xorg freeze at boot on Intel Corporation HD Graphics 530 with 
linux-image-5.3.0-17 after upgraded to the development release Ubuntu Eoan 
Ermine (development branch).
  If i boot with linux-image-5.0.0-31-generic the Xorg works well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Oct 14 11:15:23 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring
   Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteDesk 800 G2 SFF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro 
resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.42
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.36
  dmi.chassis.asset.tag: CZC64082W1
  dmi.chassis.type: 4
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G2 SFF
  dmi.product.sku: X3J10ET#ABZ
  dmi.sys.vendor: HP
  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 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring
   Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteDesk 800 G2 SFF
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-17-generic 
root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro nomodeset 
resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.42
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.36
  dmi.chassis.asset.tag: CZC64082W1
  dmi.chassis.type: 4
  dmi.chassis.vendor:

[Kernel-packages] [Bug 1846539]

2019-10-26 Thread kernelbugs

Removing SND_SOC_SOF_BROADWELL_SUPPORT fixes Pixel 2015 audio on Arch
default kernel config

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.929629] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  irina   818 F pulseaudio
   /dev/snd/controlC0:  irina   818 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct  4 01:22:54 2019
  InstallationDate: Installed on 2019-02-12 (233 days ago)
  InstallationMedia: Ubuntu 18.10 "Co

[Kernel-packages] [Bug 1850019] [NEW] zfs-linux 0.7.5-1ubuntu16.6 ADT test failure with linux-hwe-edge 5.3.0-19.20~18.04.2

2019-10-26 Thread Khaled El Mously

Public bug reported:

Testing failed on:
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20191025_102120_32b45@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  zfs-linux 0.7.5-1ubuntu16.6 ADT test failure with linux-hwe-edge
  5.3.0-19.20~18.04.2

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20191025_102120_32b45@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850019/+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 1849682] Re: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting

2019-10-26 Thread Khaled El Mously

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

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

Title:
  [REGRESSION]  md/raid0: cannot assemble multi-zone RAID0 with
  default_layout setting

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Incomplete
Status in linux source package in Eoan:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  Users of RAID0 arrays are susceptible to a corruption issue if:
   - The members of the RAID array are not all the same size[*]
   - Data has been written to the array while running kernels < 3.14 *and* >= 
3.14.

  This is because of an change in v3.14 that accidentally changed how data was 
written - as described in the upstream commit message:
  
https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9

  To summarize, upstream is dealing with this by adding a versioned
  layout in v5.4, and that is being backported to stable kernels - which
  is why we're now seeing it. Layout version 1 is the pre-3.14 layout,
  version 2 is post 3.14. Mixing version 1 & version 2 layouts can cause
  corruption. However, unless a layout-version-aware kernel *created*
  the array, there's no way for the kernel to know which version(s) was
  used to write the existing data. This undefined mode is considered
  "Version 0", and the kernel will now refuse to start these arrays w/o
  user intervention.

  The user experience is pretty awful here. A user upgrades to the next
  SRU and all of a sudden their system stops at an (initramfs) prompt. A
  clueful user can spot something like the following in dmesg:

  Here's the message which , as you can see from the log in Comment #1,
  is hidden in a ton of other messages:

  [ 72.720232] md/raid0:md0: cannot assemble multi-zone RAID0 with 
default_layout setting
  [ 72.728149] md/raid0: please set raid.default_layout to 1 or 2
  [ 72.733979] md: pers->run() failed ...
  mdadm: failed to start array /dev/md0: Unknown error 524

  What that is trying to say is that you should determine if your data -
  specifically the data toward the end of your array - was most likely
  written with a pre-3.14 or post-3.14 kernel. Based on that, reboot
  with the kernel parameter raid0.default_layout=1 or
  raid0.default_layout=2 on the kernel command line. And note it should
  be *raid0.default_layout* not *raid.default_layout* as the message
  says - a fix for that message is now queued for stable:

  
https://github.com/torvalds/linux/commit/3874d73e06c9b9dc15de0b7382fc223986d75571)

  IMHO, we should work with upstream to create a web page that clearly
  walks the user through this process, and update the error message to
  point to that page. I'd also like to see if we can detect this problem
  *before* the user reboots (debconf?) and help the user fix things.
  e.g. "We detected that you have RAID0 arrays that maybe susceptible to
  a corruption problem", guide the user to choosing a layout, and update
  the mdadm initramfs hook to poke the answer in via sysfs before
  starting the array on reboot.

  Note that it also seems like we should investigate backporting this to
  < 3.14 kernels. Imagine a user switching between the trusty HWE kernel
  and the GA kernel.

  References from users of other distros:
  https://blog.icod.de/2019/10/10/caution-kernel-5-3-4-and-raid0-default_layout/
  
https://www.linuxquestions.org/questions/linux-general-1/raid-arrays-not-assembling-4175662774/

  [*] Which surprisingly is not the case reported in this bug - the user
  here had a raid0 of 8 identically-sized devices. I suspect there's a
  bug in the detection code somewhere.

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

And this bug will be fixed with
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849623

-- 
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&s=01a0c4b0cb4c05e605cbf9d41f660e08&p=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 1848790] Re: USB not working under arm64 on Pi4

And also Pi 3 Model A Plus is not in the all.db.

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

Title:
  USB not working under arm64 on Pi4

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
  which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
  armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
  keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the
  keyboard worked successfully.

  Output of lsusb under arm64 on a Pi 3:

  ubuntu@ubuntu:~$ lsusb
  Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
  Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under armhf on a Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under arm64 on the same Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  The fact even the VIA Labs hub doesn't show up (which is built in)
  suggests the kernel is (for some reason) unable to enumerate anything
  against the USB hubs.

  
  == Temporary Workaround ==

  As noted by various people below, the following line can be added to
  the "usercfg.txt" file on the boot partition:

  total_mem=3072

  This will limit the available RAM to 3Gb, but otherwise things should
  operate normally. Note that this bug does not affect Pi 4Bs with less
  than 4Gb of RAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1848075] Re: eoan server image does not boot on RPI3-A+

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

About the root cause and fix for this bug, please refer to:

https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/comments/9
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/comments/10

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

Title:
  eoan server image does not boot on RPI3-A+

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  I've tried with both the  20191010.1 and  20191012 image, and it boots
  on all other pi devices I have, but not on the rpi3-a+.  On the serial
  console, it only gets as far as "Starting kernel..." but over hdmi,
  there are some more details reported. I'll try to attach a screenshot
  in a moment.

  After talking to Dave Jones about this, it sounds like some dtb files
  are missing to make this work on a+

  From the 20191012 image:
  ii  linux-raspi25.3.0.1007.3arm64
Complete Linux kernel for the BCM2709 architecture.
  ii  linux-firmware-raspi2   1.20190819-0ubuntu2 arm64
Raspberry Pi 2/3/4 GPU firmware and bootloaders

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

This problem is fixed by this commit, it is in the
https://github.com/raspberrypi/linux.git

(the data structure does not match the firmware definition)


commit 26f64fa81357f4b18192432eb8023f99c7eb5cf7 (HEAD -> 
26f64fa81357f4b18192432eb8023f99c7eb5cf7)
Author: Michael Brown 
Date:   Sun Sep 22 21:51:29 2019 +0100

bcm2708_fb: Fix layout of struct vc4_display_settings_t

The display parameters returned by the VC4 firmware in response to the
RPI_FIRMWARE_FRAMEBUFFER_GET_DISPLAY_SETTINGS tag do not match the
layout of struct vc4_display_settings_t: the colour depth and row
pitch are erroneously swapped in the kernel definition.  This can
trigger a kernel warning from pixel_to_pat(), such as:

  pixel_to_pat(): unsupported pixelformat 7296

Fix by adjusting the layout of struct vc4_display_settings_t to match
the layout as used by the VC4 firmware.

Signed-off-by: Michael Brown 

diff --git a/drivers/video/fbdev/bcm2708_fb.c b/drivers/video/fbdev/bcm2708_fb.c
index 4da577c8a0d8..59443f79f228 100644
--- a/drivers/video/fbdev/bcm2708_fb.c
+++ b/drivers/video/fbdev/bcm2708_fb.c
@@ -88,8 +88,8 @@ struct vc4_display_settings_t {
u32 display_num;
u32 width;
u32 height;
-   u32 pitch;
u32 depth;
+   u32 pitch;
u32 virtual_width;
u32 virtual_height;
u32 virtual_width_offset;

-- 
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:
  New

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 1847596] Re: rpi3b+: corrupted screen on hdmi