[Kernel-packages] [Bug 1858761] Re: Dell AIO can't adjust brightness
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: New Status in linux source package in Focal: New Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858761/+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 1858594] Re: xenial/linux: 4.4.0-172.201 -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 --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Tuesday, 07. January 2020 22:21 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
main:failed,meta:depwait,signed:depwait
+ promote-to-proposed: Pending -- builds not complete in ppa
main:failed,meta:depwait
trackers:
trusty/linux-aws: bug 1858591
trusty/linux-lts-xenial: bug 1858592
xenial/linux-aws: bug 1858581
xenial/linux-cascade: bug 1858583
xenial/linux-fips: bug 1858589
xenial/linux-kvm: bug 1858584
xenial/linux-raspi2: bug 1858586
xenial/linux-snapdragon: bug 1858588
xenial/linux/caracalla-kernel: bug 1858577
xenial/linux/pc-kernel: bug 1858578
xenial/linux/stlouis-kernel: bug 1858579
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/1858594
Title:
xenial/linux: 4.4.0-172.201 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
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:
New
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:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Tuesday, 07. January 2020 22:21 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Pending -- builds not complete in ppa
main:failed,meta:depwait
trackers:
trusty/linux-aws: bug 1858591
trusty/linux-lts-xenial: bug 1858592
xenial/linux-aws: bug 1858581
xenial/linux-cascade: bug 1858583
xenial/linux-fips: bug 1858589
xenial/linux-kvm: bug 1858584
xenial/linux-raspi2: bug 1858586
xenial/linux-snapdragon: bug 1858588
xenial/linux/caracalla-kernel: bug 1858577
xenial/linux/pc-kernel: bug 1858578
xenial/linux/stlouis-kernel: bug 1858579
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858594/+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 1858761] [NEW] Dell AIO can't adjust brightness
Public bug reported: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858761 Title: Dell AIO can't adjust brightness Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: New Status in linux source package in Focal: New Bug description: [Impact] Found on new platforms that UART require more than 1 second to respond commands in the first 10 seconds after booted. And the first command we send to scalar is dell_uart_get_scalar_status() to tell if scalar is in charge of the backlight, and it always fails to get response because of timeout. [Fix] Adding retry and increasing read timeout for dell_uart_get_scalar_status() [Test] Verified on the target Dell AIO, it can now read the response from scalar. [Regression Potential] Low, adding retry and increasing read timeout doesn't change the code flow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858761/+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 1858760] [NEW] KVM guest abnormal load after upgrade to 4.15.0-72
Public bug reported: a idle kvm guest system with 4.15.0-70 , load is good: load average : 0.00, 0.04, 0.05 after upgrade to 4.15.0-72 or 4.15.0-74, load become abnormal: load average : 0.65, 0.49, 0.41 when apply this patch, load good again: x86/timer: Force PIT initialization when !X86_FEATURE_ARAT https://github.com/torvalds/linux/commit/afa8b475c1aec185a8e106c48b3832e0b88bc2de could you pls apply this patch on upcoming kernel update ? ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858760 Title: KVM guest abnormal load after upgrade to 4.15.0-72 Status in linux package in Ubuntu: New Bug description: a idle kvm guest system with 4.15.0-70 , load is good: load average : 0.00, 0.04, 0.05 after upgrade to 4.15.0-72 or 4.15.0-74, load become abnormal: load average : 0.65, 0.49, 0.41 when apply this patch, load good again: x86/timer: Force PIT initialization when !X86_FEATURE_ARAT https://github.com/torvalds/linux/commit/afa8b475c1aec185a8e106c48b3832e0b88bc2de could you pls apply this patch on upcoming kernel update ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858760/+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 1858299] Re: This laptop contains a touchpadwhich is not recognized.
I have to correct me, it works with the kernel you linked. I plugged out my USB mouse and now the touchpad is recognized perfectly. Thank you very much, Kai-Heng! -- 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/1858299 Title: This laptop contains a touchpadwhich is not recognized. Status in linux package in Ubuntu: Confirmed Bug description: This laptop contains a touchpad which is not recognized. The laptop is the Trekstore Surfbook E11B. 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 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deathmetal 1119 F pulseaudio CurrentDesktop: LXQt Date: Sat Jan 4 23:09:34 2020 InstallationDate: Installed on 2020-01-04 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB Camera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TREKSTOR SURFBOOK E11B ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=c3bcb5e6-3626-422a-b348-dbdb31c269d9 ro quiet splash vt.handoff=7 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/30/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BIOS_V1.1.5 dmi.board.asset.tag: Default string dmi.board.name: Gemini_Lake_Celeron_V01 dmi.board.vendor: TS_EMDOOR dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBIOS_V1.1.5:bd08/30/2018:svnTREKSTOR:pnSURFBOOKE11B:pvrDefaultstring:rvnTS_EMDOOR:rnGemini_Lake_Celeron_V01:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Surfbook dmi.product.name: SURFBOOK E11B dmi.product.sku: NFCN4SW03 dmi.product.version: Default string dmi.sys.vendor: TREKSTOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858299/+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 1858751] [NEW] Fix throttled clock on AMD Oland
Public bug reported: [Impact] Running simple 3D apps like glxgears in 4K becomes really sluggish. [Fix] Update rlc microcode to its latest version. [Test] Run `glxgears -fullscreen` on 4K monitor. The issue disappears after this firmware update. [Regression Potential] Low. The firmware is already used by amdgpu.ko for a while, now we also use it for radeon.ko. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1856292 stella ** Also affects: linux-firmware (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-1856292 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1858751 Title: Fix throttled clock on AMD Oland Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware source package in Focal: New Bug description: [Impact] Running simple 3D apps like glxgears in 4K becomes really sluggish. [Fix] Update rlc microcode to its latest version. [Test] Run `glxgears -fullscreen` on 4K monitor. The issue disappears after this firmware update. [Regression Potential] Low. The firmware is already used by amdgpu.ko for a while, now we also use it for radeon.ko. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858751/+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 1853937] Re: [hns-1126] net: hns: add support for vlan TSO
** Changed in: kunpeng920/ubuntu-18.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-19.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853937 Title: [hns-1126] net: hns: add support for vlan TSO Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Fix Committed Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released 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 Released Status in linux source package in Focal: Fix Released Bug description: [Impact] hns hardware supports vlan TSO but driver does not set the flag. [Test Case] Performance run through vlan TSO shall reach limitation. [Fix] 0d581ba311a2 net: hns: add support for vlan TSO [Regression Risk] Patch restricted to hns3 driver. """[Bug Description] When add vlan to the net ports, the performance is almost 50% lower than no vlan. [Steps to Reproduce] 1.add vlan to net port(10G fibre); 2.add ip to this vlan; 3.run iperf to test the performance; [Actual Results] iperf result is about 5~6Gbp/s [Expected Results] iperf result is about 9.4Gbp/s [Reproducibility] Conditionally Recur [Additional information] Hardware: D05 Firmware: NA Kernel: NA [Resolution] The hip07 chip support vlan TSO, adds NETIF_F_TSO and NETIF_F_TSO6 flags to vlan_features.""" net: hns: add support for vlan TSO To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853937/+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 1853983] Re: [hns-1126]net: hns3: revert to old channel when setting new channel num fail
** Changed in: kunpeng920/ubuntu-19.10 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-19.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853983 Title: [hns-1126]net: hns3: revert to old channel when setting new channel num fail Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Won't Fix Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Fix Committed Status in kunpeng920 ubuntu-19.10 series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Released Bug description: [Impact] With specific ethtool commands, ethernet does not work [Test Case] run VF on VM with 3G memory and load VF driver ethtool -G eth0 tx 3 rx 3 ethtool -G eth0 tx 24 rx 24；ethtool -L eth0 combined 1 ethtool -G eth0 tx 32760 rx 32760 ethtool -L eth0 combined 32 ethernet shall still be functional after these commands [Fix] 3a5a5f06d4d2 net: hns3: revert to old channel when setting new channel num fail [Regression Risk] Patch restricted to hns3 driver. "[Bug Description] After setting new channel num, it needs free old ring memory and allocate new ring memory. If there is no enough memory and allocate new ring memory fail, the ring may initialize fail. To make sure the network interface can work normally, driver should revert the channel to the old configuration. [Steps to Reproduce] 1.run VF on VM with 3G memory 2.load VF driver 3.ethtool -G eth0 tx 3 rx 3 4.ethtool -G eth0 tx 24 rx 24；ethtool -L eth0 combined 1 5.ethtool -G eth0 tx 32760 rx 32760 6.ethtool -L eth0 combined 32 7.ping [Actual Results] netdevice can not work [Expected Results] ping ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] Revert the channel to the old configuration when allocate new ring memory fail." To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853983/+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 1853948] Re: [hns-1126]net: hns3: fix flow control configure issue for fibre port
** Changed in: kunpeng920/ubuntu-19.04 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853948 Title: [hns-1126]net: hns3: fix flow control configure issue for fibre port Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Fix Committed Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Flow control parameters of fibre port can not be set after enable flow control autoneg, as flow control autoneg is unsupported for fibre port [Test Case] Turning on/off tx pause and ethtool shall report status accordingly. [Fix] fb89629f2ecf net: hns3: fix flow control configure issue for fibre port [Regression Risk] Patch restricted to hns3 driver. "[Bug Description] Flow control parameters of fibre port can not be set after enable flow control autoneg, as flow control autoneg is unsupported for fibre port. [Steps to Reproduce] 1.link up fibre port and enable flow control autoneg 2.check status of tx pause and rx pause 3.turn off tx pause 4.checkout status of tx pause [Actual Results] tx pause is on [Expected Results] tx pause is off [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] This patch return -EOPNOTSUPP when user tries to enable flow control autoneg." net: hns3: fix flow control configure issue for fibre port To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853948/+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 1853984] Re: [hns-1126]net: hns3: fix port setting handle for fibre port
** Changed in: kunpeng920/ubuntu-19.10 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-19.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853984 Title: [hns-1126]net: hns3: fix port setting handle for fibre port Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Invalid Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Fix Committed Status in kunpeng920 ubuntu-19.10 series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Released Bug description: [Impact] For hardware doesn't support use specified speed and duplex to negotiate, it's unnecessary to check and modify the port speed and duplex for fibre port when autoneg is on. [Test Case] `sudo ethtool -s eno1 autoneg off speed 10 duplex full` `sudo ethtool -s eno1 autoneg on` commands shall return 0 [Fix] 24283ece5a0f net: hns3: fix port setting handle for fibre port [Regression Risk] Patch restricted to hns3 driver. "[Bug Description] For hardware doesn't support use specified speed and duplex to negotiate, it's unnecessary to check and modify the port speed and duplex for fibre port when autoneg is on. [Steps to Reproduce] 1.ethtool -s eth* autoneg off speed 10 duplex full 2.ethtool -s eth* autoneg on [Actual Results] set autoneg on fail [Expected Results] set autoneg on ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] Not check and modify the port speed and duplex for fibre port when autoneg on." net: hns3: fix port setting handle for fibre port To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853984/+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 1853995] Re: [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands
** Changed in: kunpeng920/ubuntu-19.10
Status: In Progress => Fix Committed
** Changed in: kunpeng920/ubuntu-19.04
Status: In Progress => Fix Committed
** Changed in: kunpeng920/ubuntu-18.04-hwe
Status: In Progress => Fix Committed
** Changed in: kunpeng920/ubuntu-18.04
Status: In Progress => Fix Committed
** Changed in: kunpeng920
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853995
Title:
[sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands
Status in kunpeng920:
Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
Fix Committed
Status in kunpeng920 ubuntu-19.04 series:
Fix Committed
Status in kunpeng920 ubuntu-19.10 series:
Fix Committed
Status in kunpeng920 ubuntu-20.04 series:
Fix Committed
Status in kunpeng920 upstream-kernel series:
Fix Released
Status in linux package in Ubuntu:
Fix Released
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
Status in linux source package in Focal:
Fix Released
Bug description:
[Impact]
I/O error on blank Samsung SSD
[Test Case]
mkfs.ext4 on SSDs generates no I/O error
[Fix]
435a05cf8c00 scsi: hisi_sas: Assign NCQ tag for all NCQ commands
[Regression Risk]
Patch restricted to hisi_sas driver.
"[Steps to Reproduce]
mkfs.ext4 to the special SAMSUNG M27LH960, and some IO error
[Actual Results]
Io error when the first time of mkfs.ext4
[ 745.809462] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=8
task=975f5cdf dev id=1 CQ hdr: 0x41d03 0x10008 0x1 0x446 Error
info: 0x0 0x0 0x1 0x0
[ 776.028794] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
[ 776.034612] sas: trying to find task 0x9656953a
[ 776.034613] sas: sas_scsi_find_task: aborting task 0x9656953a
[ 776.042785] sas: sas_scsi_find_task: task 0x9656953a is done
[ 776.042786] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
[ 776.049635] sas: trying to find task 0x975f5cdf
[ 776.049636] sas: sas_scsi_find_task: aborting task 0x975f5cdf
[ 776.056053] sas: sas_scsi_find_task: task 0x975f5cdf is done
[ 776.056054] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
[ 776.062900] sas: ata5: end_device-4:0: cmd error handler
[ 776.062914] sas: ata5: end_device-4:0: dev error handler
[ 776.062918] sas: ata6: end_device-4:1: dev error handler
[ 776.062920] ata5.00: exception Emask 0x0 SAct 0xc000 SErr 0x0 action
0x6 frozen
[ 776.062924] sas: ata7: end_device-4:2: dev error handler
[ 776.062926] sas: ata8: end_device-4:3: dev error handler
[ 776.070548] ata5.00: failed command: SEND FPDMA QUEUED
[ 776.075669] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 30 ncq
dma 512 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 776.090638] ata5.00: status: { DRDY }
[ 776.094290] ata5.00: failed command: SEND FPDMA QUEUED
[ 776.099410] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 31 ncq
dma 512 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 776.114399] ata5.00: status: { DRDY }
[ 776.118051] ata5: hard resetting link
[ 776.123198] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe
[ 776.129609] hisi_sas_v3_hw :74:02.0: ignore flutter phy0 down
[ 776.282642] hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=10(sata)
[ 776.289236] sas: sas_form_port: phy0 belongs to port0 already(1)!
[ 776.451784] ata5.00: configured for UDMA/133
[ 776.456043] ata5.00: device reported invalid CHS sector 0
[ 776.461423] ata5.00: device reported invalid CHS sector 0
[ 776.466807] ata5: EH complete
[ 776.469773] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 2 tries: 1
[ 776.498528] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=15
task=9656953a dev id=1 CQ hdr: 0x41d03 0x1000f 0x1 0x446 Error
info: 0x0 0x0 0x1 0x0
[ 806.740789] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
[ 806.746604] sas: trying to find task 0x975f5cdf
[ 806.746605] sas: sas_scsi_find_task: aborting task 0x975f5cdf
[ 806.754732] sas: sas_scsi_find_task: task 0x975f5cdf is done
[ 806.754733] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
[ 806.761582] sas: trying to find task 0x9656953a
[ 806.761584] sas: sas_scsi_find_task: aborting task 0x9656953a
[ 806.768002] sas: sas_scsi_find_task: task 0x9656953a is done
[ 806.768003] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
[ 806.774852] sas: ata5: end_device-4:0: cmd error handler
[Kernel-packages] [Bug 1855952] Re: scsi: hisi_sas: Check sas_port before using it
** Changed in: kunpeng920/ubuntu-19.10 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-19.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855952 Title: scsi: hisi_sas: Check sas_port before using it Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Fix Committed Status in kunpeng920 ubuntu-19.10 series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Fix Released 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 Status in linux source package in Focal: Fix Released Bug description: [Impact] Potential NULL-pointer dereference. [Test Case] No known test case, but the issue is clear from code reading. [Fix] 8c39673d5474b scsi: hisi_sas: Check sas_port before using it [Regression Risk] Patch restricted to hisi_sas driver. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1855952/+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 1853997] Re: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset
** Changed in: kunpeng920/ubuntu-19.10 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-19.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853997 Title: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Fix Committed Status in kunpeng920 ubuntu-19.10 series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released 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 Status in linux source package in Focal: Fix Released Bug description: [Impact] Some SAS devices is gone when recovering [Test Case] No known test case, stress test on SAS deivce. [Fix] e74006edd0d4 scsi: hisi_sas: Fix the conflict between device gone and host reset [Regression Risk] Patch restricted to hisi_sas driver. "[Steps to Reproduce] 1. Close all the PHYS; 2. Inject error; 3. Open one PHY; [Actual Results] Some disk will be lost [Expected Results] No disk will be lost [Reproducibility] occasionally [Additional information] Hardware: D06 CS Firmware: NA+I59 Kernel: NA [Resolution] When init device for SAS disks, it will send TMF IO to clear disks. At that time TMF IO is broken by some operations such as injecting controller reset from HW RAs event, the TMF IO will be timeout, and at last device will be gone. Print is as followed: hisi_sas_v3_hw :74:02.0: dev[240:1] found ... hisi_sas_v3_hw :74:02.0: controller resetting... hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11 hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11 hisi_sas_v3_hw :74:02.0: controller reset complete hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done hisi_sas_v3_hw :74:02.0: dev[240:1] is gone sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d, error:5 To improve the reliability, retry TMF IO max of 3 times for SAS disks which is the same as softreset does." scsi: hisi_sas: Fix the conflict between device gone and host reset To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853997/+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 1858307] Re: Dota2 Arcade mods lock up on first start
Cool. Have a link by chance? Thank in advance. -- 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/1858307 Title: Dota2 Arcade mods lock up on first start Status in linux package in Ubuntu: Confirmed Bug description: Dota2 crashes unless on the latest kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ryan 2297 F pulseaudio /dev/snd/controlC0: ryan 2297 F pulseaudio /dev/snd/controlC1: ryan 2297 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99X EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858307/+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 1853992] Re: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()
** Changed in: kunpeng920/ubuntu-19.10 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-19.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853992 Title: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset() Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Fix Committed Status in kunpeng920 ubuntu-19.10 series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released 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 Status in linux source package in Focal: Fix Released Bug description: [Impact] Potential NULL-pointer dereference. [Test Case] No known test case, but the issue is clear from code reading. [Fix] 445ee2de112a scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset() [Regression Risk] Patch restricted to hisi_sas driver. [Bug Description] sas kasan test will produce this out bounds in sas module [Steps to Reproduce] 1) enbale this kasn 2) 3) [Actual Results] 30293.504016] sas: ata464: end_device-2:2:6: dev error handler [30293.504041] sas: ata465: end_device-2:2:7: dev error handler [30293.504059] sas: ata466: end_device-2:2:8: dev error handler [30293.538746] == [30293.550672] BUG: KASAN: slab-out-of-bounds in hisi_sas_debug_I_T_nexus_reset+0xcc/0x250 [30293.558642] Read of size 8 at addr b72e47233540 by task kworker/u193:3/79165 [30293.566004] [30293.567498] CPU: 14 PID: 79165 Comm: kworker/u193:3 Tainted: GB O 5.1.0-rc1-g7a3fab8-dirty #1 [30293.577196] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B010.01 06/21/2019 [30293.586037] Workqueue: events_unbound async_run_entry_fn [30293.591331] Call trace: [30293.593770] dump_backtrace+0x0/0x1f8 [30293.597419] show_stack+0x14/0x20 [30293.600726] dump_stack+0xc4/0xfc [30293.604032] print_address_description+0x60/0x258 [30293.608716] kasan_report+0x164/0x1b8 [30293.612366] __asan_load8+0x84/0xa8 [30293.615842] hisi_sas_debug_I_T_nexus_reset+0xcc/0x250 [30293.620961] hisi_sas_I_T_nexus_reset+0xc4/0x170 [30293.625562] sas_ata_hard_reset+0x88/0x178 [30293.629646] ata_do_reset.constprop.6+0x80/0x90 [30293.634160] ata_eh_reset+0x71c/0x10e8 [30293.637897] ata_eh_recover+0x3d0/0x1a80 [30293.641804] ata_do_eh+0x50/0xd0 [30293.645020] ata_std_error_handler+0x78/0xa8 [30293.649273] ata_scsi_port_error_handler+0x288/0x930 [30293.654216] async_sas_ata_eh+0x68/0x90 [30293.658040] async_run_entry_fn+0x7c/0x1c0 [30293.662121] process_one_work+0x3c0/0x878 [30293.666115] worker_thread+0x70/0x670 [30293.669762] kthread+0x1b0/0x1b8 [30293.672978] ret_from_fork+0x10/0x18 [30293.676541] [30293.678027] Allocated by task 16690: [30293.681593] __kasan_kmalloc.isra.0+0xd4/0x188 [30293.686018] kasan_kmalloc+0xc/0x18 [30293.689496] __kmalloc_node_track_caller+0x5c/0x98 [30293.694270] devm_kmalloc+0x44/0xb8 [30293.697746] hisi_sas_v3_probe+0x2ec/0x698 [30293.701828] local_pci_probe+0x74/0xf0 [30293.705562] work_for_cpu_fn+0x2c/0x48 [30293.709300] process_one_work+0x3c0/0x878 [30293.713294] worker_thread+0x400/0x670 [30293.717027] kthread+0x1b0/0x1b8 [30293.720241] ret_from_fork+0x10/0x18 [30293.723801] [30293.725287] Freed by task 16227: [30293.728503] __kasan_slab_free+0x108/0x210 [30293.732583] kasan_slab_free+0x10/0x18 [30293.736318] kfree+0x74/0x150 [30293.739276] devres_free+0x34/0x48 [30293.742665] devres_release+0x38/0x60 [30293.746313] devm_pinctrl_put+0x34/0x58 [30293.750136] pinctrl_bind_pins+0x164/0x248 [30293.754214] really_probe+0xc0/0x3b0 [30293.75] driver_probe_device+0x70/0x138 [30293.761944] __device_attach_driver+0xc0/0xe0 [30293.766285] bus_for_each_drv+0xcc/0x150 [30293.770194] __device_attach+0x154/0x1c0 [30293.774101] device_initial_probe+0x10/0x18 [30293.778270] bus_probe_device+0xec/0x100 [30293.782178] device_add+0x5f8/0x9b8 [30293.785658] scsi_sysfs_add_sdev+0xa4/0x310 [30293.789825] scsi_probe_and_add_lun+0xe60/0x1240 [30293.794425] __scsi_scan_target+0x1ac/0x780 [30293.798591] scsi_scan_target+0x134/0x140 [30293.802586] sas_rphy_add+0x1fc/0x2c8 [30293.8
[Kernel-packages] [Bug 1857730] Re: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110).
Only the debs are needed. -- 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/1857730 Title: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110). Status in linux package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) GDM 3.34.1 3) Resume from standby without error and corrupt screen graphics. 4) Randomly there is an error after resuming from standby and corrupt screen graphics. 4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) 4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) 4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0) 4:37:02 PM kernel: [drm] ib test on ring 5 succeeded 4:37:02 PM kernel: [drm] ib test on ring 5 succeeded 4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs 4:37:02 PM kernel: [drm] UVD initialized successfully. 4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs 4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs 4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs 4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 0x0014C000). 4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) 4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) 4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0) 4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110). 4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait timed out. 4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs 4:36:01 PM kernel: [drm] UVD initialized successfully. 4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs 4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs 4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs 4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 0x0014C000). 4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) 4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) 4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0) 4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 failed: Permission denied 4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110). 4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait timed out. 4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs 4:34:45 PM kernel: [drm] UVD initialized successfully. 4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs 4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs 4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs 4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 0x0014C000). 4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 2:15:55 PM kernel: [drm] ib test on ring 5 succeeded 2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs 2:15:55 PM kernel: [drm] UVD initialized successfully. 2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs 2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs 2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs 2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 0x0014C000). 2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 7:53:47 AM kernel: [drm] ib test on ring 5 succeeded 7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs 7:53:47 AM kernel: [drm] UVD initialized successfully. 7:53:47 AM kernel: [drm] ring test on 5 succeeded in 1 usecs 7:53:47 AM kernel: [drm] r
[Kernel-packages] [Bug 1854549] Re: [acc-1130]sync mainline kernel 5.5rc1 acc patchset into ubuntu HWE kernel branch
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854549 Title: [acc-1130]sync mainline kernel 5.5rc1 acc patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Won't Fix Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Won't Fix Status in kunpeng920 ubuntu-19.10 series: Won't Fix Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: [Bug Description] enable 1620 acc function for kunpeng 920 [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] MAINTAINERS: Add maintainer for HiSilicon trng V2 driver hw_random: add HiSilicon TRNG driver support MAINTAINERS: Add maintainer for HiSilicon SEC V2 driver crypto: hisilicon - add DebugFS for HiSilicon SEC Documentation: add DebugFS doc for HiSilicon SEC crypto: hisilicon - add SRIOV for HiSilicon SEC crypto: hisilicon - add HiSilicon SEC V2 driver crypto: hisilicon - use sgl API to get sgl dma addr and len crypto: hisilicon - replace #ifdef with IS_ENABLED for CONFIG_NUMA crypto: hisilicon - no need to check return value of debugfs_create functions crypto: hisilicon - fix to return sub-optimal device when best device has no qps crypto: hisilicon - add vfs_num module param for zip crypto: hisilicon - fix endianness verification problem of QM crypto: hisilicon - fix param should be static when not external. crypto: hisilicon - Fix using plain integer as NULL pointer crypto: hisilicon - tiny fix about QM/ZIP error callback print crypto: hisilicon: Fix misuse of GENMASK macro crypto: hisilicon - select NEED_SG_DMA_LENGTH in qm Kconfig crypto: hisilicon - misc fix about sgl crypto: hisilicon - fix large sgl memory allocation problem when disable smmu crypto: hisilicon - add sgl_sge_nr module param for zip crypto: hisilicon - merge sgl support to hisi_qm module crypto: hisilicon - allow compile-testing on x86 crypto: hisilicon - select CRYPTO_LIB_DES while compiling SEC driver To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1854549/+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 1850117] Re: [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE kernel branch
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850117 Title: [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Won't Fix Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Won't Fix Status in kunpeng920 ubuntu-19.10 series: Won't Fix Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Bug Description] hpre patchset have merged into mainline 5.4rc3 kernel. Can use this hpre patchset to release UOSE basing this ubuntu 18.04.4 kernel branch, then merge into ubuntu 18.04.4 version. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon - add HiSilicon HPRE accelerator crypto: hisilicon - add SRIOV support for HPRE Documentation: Add debugfs doc for hisi_hpre crypto: hisilicon: Add debugfs for HPRE MAINTAINERS: Add maintainer for HiSilicon HPRE driver https://www.mail-archive.com/linux- cry...@vger.kernel.org/msg40969.html To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1850117/+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 1849276] Re: alfa-AWUS036ACH wifi usb adapter not working
Expired, but should have tried installing rtl8812au-dkms instead. See https://launchpad.net/ubuntu/+source/rtl8812au-dkms. -- 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/1849276 Title: alfa-AWUS036ACH wifi usb adapter not working Status in linux package in Ubuntu: Expired Bug description: My ALfa AWUS036ACH WiFi USB adapter ( https://www.alfa.com.tw/products_detail/1.htm ) doesn't work with the default drivers. WORKAROUND: Install the driver via: https://drive.google.com/file/d/1Vn4KzClyCQ0XeMrAGjE7OvEMeBZgg6Xb/view 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: azamet 2426 F pulseaudio /dev/snd/controlC0: azamet 2426 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 16:13:26 2019 InstallationDate: Installed on 2019-10-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. ROG Strix G731GV_G731GV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GV.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG731GV.306:bd08/16/2019:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GV_G731GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G731GV_G731GV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849276/+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 1858307] Re: Dota2 Arcade mods lock up on first start
Ok, 5.4.7 will be in Ubuntu's kernel soon. -- 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/1858307 Title: Dota2 Arcade mods lock up on first start Status in linux package in Ubuntu: Confirmed Bug description: Dota2 crashes unless on the latest kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ryan 2297 F pulseaudio /dev/snd/controlC0: ryan 2297 F pulseaudio /dev/snd/controlC1: ryan 2297 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99X EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858307/+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 1858307] Re: Dota2 Arcade mods lock up on first start
I belive it is https://github.com/ValveSoftware/Dota-2-Vulkan/issues/300#issuecomment-480419559 "update kernel to 5.0.x" I can't remember which exact version though. ** Bug watch added: github.com/ValveSoftware/Dota-2-Vulkan/issues #300 https://github.com/ValveSoftware/Dota-2-Vulkan/issues/300 -- 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/1858307 Title: Dota2 Arcade mods lock up on first start Status in linux package in Ubuntu: Confirmed Bug description: Dota2 crashes unless on the latest kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ryan 2297 F pulseaudio /dev/snd/controlC0: ryan 2297 F pulseaudio /dev/snd/controlC1: ryan 2297 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99X EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858307/+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 1804592] Re: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Jan 06 18:52:01 pacnow-envy kernel: usb usb8: We don't know the algorithms for LPM for this host, disabling LPM. Jan 06 18:52:01 pacnow-envy kernel: usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03 Jan 06 18:52:01 pacnow-envy kernel: usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Jan 06 18:52:01 pacnow-envy kernel: usb usb8: Product: xHCI Host Controller Jan 06 18:52:01 pacnow-envy kernel: usb usb8: Manufacturer: Linux 5.3.0-24-generic xhci-hcd Jan 06 18:52:01 pacnow-envy kernel: usb usb8: SerialNumber: :00:10.1 -- 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/1804592 Title: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. Status in linux package in Ubuntu: Confirmed Bug description: [0.876087] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [0.876099] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.18 [0.876100] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.876101] usb usb2: Product: xHCI Host Controller [0.876102] usb usb2: Manufacturer: Linux 4.18.0-10-generic xhci-hcd [0.876103] usb usb2: SerialNumber: :15:00.0 [0.876206] hub 2-0:1.0: USB hub found [0.876215] hub 2-0:1.0: 4 ports detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804592/+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 1857536] Re: Touch pad is not working - Lenovo G50
P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00 L: 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00 E: SUBSYSTEM=acpi E: MODALIAS= P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/ELAN1000:00 L: 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/ELAN1000:00 E: SUBSYSTEM=acpi E: MODALIAS= P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/ELAN1001:00 L: 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/ELAN1001:00 E: SUBSYSTEM=acpi E: MODALIAS= P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/ELAN1010:00 L: 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/ELAN1010:00 E: SUBSYSTEM=acpi E: MODALIAS= So you do have a i2c_designware device, but somehow it's not probed, neither do the i2c slaves attached to this host. -- 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/1857536 Title: Touch pad is not working - Lenovo G50 Status in linux package in Ubuntu: Incomplete Bug description: Laptop : Lenovo G50 I ran below command to check that touchpad package is available or not, and couldn't find the synaptic touchpad package. Command : cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kadinish 1720 F pulseaudio /dev/snd/controlC1: kadinish 1720 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 16:02:24 2019 InstallationDate: Installed on 2019-12-10 (15 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20351 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=6a5066c3-fbca-4e9c-be14-2af9e25b497b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-12-25 (0 days ago) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.family: IDEAPAD dmi.product.name: 20351 dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857536/+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 1858307] Re: Dota2 Arcade mods lock up on first start
@Kai, it's 5.4.7 or later. See comment 19 ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1858307 Title: Dota2 Arcade mods lock up on first start Status in linux package in Ubuntu: Confirmed Bug description: Dota2 crashes unless on the latest kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ryan 2297 F pulseaudio /dev/snd/controlC0: ryan 2297 F pulseaudio /dev/snd/controlC1: ryan 2297 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99X EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858307/+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 1849276] Re: alfa-AWUS036ACH wifi usb adapter not working
[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/1849276 Title: alfa-AWUS036ACH wifi usb adapter not working Status in linux package in Ubuntu: Expired Bug description: My ALfa AWUS036ACH WiFi USB adapter ( https://www.alfa.com.tw/products_detail/1.htm ) doesn't work with the default drivers. WORKAROUND: Install the driver via: https://drive.google.com/file/d/1Vn4KzClyCQ0XeMrAGjE7OvEMeBZgg6Xb/view 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: azamet 2426 F pulseaudio /dev/snd/controlC0: azamet 2426 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 16:13:26 2019 InstallationDate: Installed on 2019-10-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. ROG Strix G731GV_G731GV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GV.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG731GV.306:bd08/16/2019:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GV_G731GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G731GV_G731GV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849276/+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 1850986] Re: many problems:
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (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/1850986 Title: many problems: Status in apport package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850986/+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 1850986] Re: many problems:
[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/1850986 Title: many problems: Status in apport package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: 1st Neither ubuntu-bug linux nor sudo ubuntu-bug linux sudo cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log work! 2 Bug reporting is so hard! 3 Cannot find bug reporting section for Linuxmint so as to empart to Ubuntu that the problem is with the Kernels and not the drivers. 4. The bug is with 4K monitors and the Linuxmint OS is continuously trying to load drivers for the screen. Constantly failing. I would gladly report the bug properly if I knew how to. As information is so vague I can't help. Remember that if a novice can't find what he is looking for to fix a bug then there is a guarantee that the novice will never use that system again. Not all users are able to understand all commands if they are not in use every day. That is the case with me. Sadly, I want to use the system but the system is failing it's novices. It's not the fault of the novice if he/she cannot find the relevant information as there is seriously way too much information on any given subject out there. Deciphering it is a minefield of displeasure. Pity ain't it! That is why people are giving up computers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-11-03 (4 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: third-party-packages tina Uname: Linux 5.0.0-32-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1850986/+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 1857730] Re: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110).
I assume I need to install the following: linux-headers-5.5.0-994-generic_5.5.0-994.202001070537_amd64.deb linux-image-unsigned-5.5.0-994-generic_5.5.0-994.202001070537_amd64.deb linux-modules-5.5.0-994-generic_5.5.0-994.202001070537_amd64.deb Do I need to install the following: 0001-base-packaging.patch 0002-UBUNTU-SAUCE-add-vmlinux.strip-to-BOOT_TARGETS1-on-p.patch 0003-UBUNTU-SAUCE-tools-hv-lsvmbus-add-manual-page.patch 0004-debian-changelog.patch 0005-configs-based-on-Ubuntu-5.5.0-3.4.patch -- 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/1857730 Title: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110). Status in linux package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) GDM 3.34.1 3) Resume from standby without error and corrupt screen graphics. 4) Randomly there is an error after resuming from standby and corrupt screen graphics. 4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) 4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) 4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0) 4:37:02 PM kernel: [drm] ib test on ring 5 succeeded 4:37:02 PM kernel: [drm] ib test on ring 5 succeeded 4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs 4:37:02 PM kernel: [drm] UVD initialized successfully. 4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs 4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs 4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs 4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 0x0014C000). 4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) 4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) 4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0) 4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110). 4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait timed out. 4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs 4:36:01 PM kernel: [drm] UVD initialized successfully. 4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs 4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs 4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs 4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 0x0014C000). 4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) 4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0) 4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0) 4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 failed: Permission denied 4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110). 4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait timed out. 4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs 4:34:45 PM kernel: [drm] UVD initialized successfully. 4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs 4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs 4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs 4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 0x0014C000). 4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 2:15:55 PM kernel: [drm] ib test on ring 5 succeeded 2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs 2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs 2:15:55 PM kernel: [drm] UVD initialized successfully. 2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs 2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs 2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs 2:15:55 PM kernel: [drm] PCIE GART of 102
[Kernel-packages] [Bug 1858307] Re: Dota2 Arcade mods lock up on first start
I haven't played Dota 2 for a while, but I recall this issue occurred every time when I played Overthrow 2.0. Can you please share the version of the working 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/1858307 Title: Dota2 Arcade mods lock up on first start Status in linux package in Ubuntu: Incomplete Bug description: Dota2 crashes unless on the latest kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ryan 2297 F pulseaudio /dev/snd/controlC0: ryan 2297 F pulseaudio /dev/snd/controlC1: ryan 2297 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99X EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858307/+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 1858366] Re: My wireless card crashes on 5.4.8-050408-generic kernel installed via Ukuu
What's the output of `ls -a1 /lib/firmware/iwlwifi-9000-pu-b0-jf-b0-*.ucode`? It should contain following files, but your dmesg states "No such file or directory" for file rev >= 34. iwlwifi-9000-pu-b0-jf-b0-33.ucode iwlwifi-9000-pu-b0-jf-b0-34.ucode iwlwifi-9000-pu-b0-jf-b0-38.ucode iwlwifi-9000-pu-b0-jf-b0-41.ucode iwlwifi-9000-pu-b0-jf-b0-43.ucode iwlwifi-9000-pu-b0-jf-b0-46.ucode -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1858366 Title: My wireless card crashes on 5.4.8-050408-generic kernel installed via Ukuu Status in linux-firmware package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 lspci -nnk | grep 0280 -A3 00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:a370] (rev 10) Subsystem: Bigfoot Networks, Inc. Device [1a56:1552] Kernel driver in use: iwlwifi Kernel modules: iwlwifi dmesg | grep iwlwifi [3.938222] iwlwifi :00:14.3: enabling device ( -> 0002) [3.947221] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2 [3.947688] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2 [3.949266] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2 [3.949280] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-43.ucode failed with error -2 [3.949293] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-42.ucode failed with error -2 [3.949497] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-41.ucode failed with error -2 [3.949512] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-40.ucode failed with error -2 [3.949524] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-39.ucode failed with error -2 [3.949536] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-38.ucode failed with error -2 [3.949549] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-37.ucode failed with error -2 [3.949561] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-36.ucode failed with error -2 [3.949573] iwlwifi :00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-35.ucode failed with error -2 [3.956300] iwlwifi :00:14.3: loaded firmware version 34.0.0 op_mode iwlmvm [4.067040] iwlwifi :00:14.3: Detected Killer (R) Wireless-AC 1550i Wireless Network Adapter (9560NGW), REV=0x318 [5.089016] iwlwifi :00:14.3: Collecting data: trigger 15 fired. [5.337038] iwlwifi :00:14.3: Not valid error log pointer 0x for Init uCode [5.337049] iwlwifi :00:14.3: Fseq Registers: [5.337058] iwlwifi :00:14.3: 0x783B9DAA | FSEQ_ERROR_CODE [5.337066] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION [5.337075] iwlwifi :00:14.3: 0x73F12AC7 | FSEQ_CNVIO_INIT_VERSION [5.337083] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION [5.337091] iwlwifi :00:14.3: 0x9FB95405 | FSEQ_TOP_CONTENT_VERSION [5.337100] iwlwifi :00:14.3: 0x6D10B63E | FSEQ_ALIVE_TOKEN [5.337108] iwlwifi :00:14.3: 0xD21A013F | FSEQ_CNVI_ID [5.337115] iwlwifi :00:14.3: 0x5FEE2C7B | FSEQ_CNVR_ID [5.337125] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [5.337135] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP [5.337146] iwlwifi :00:14.3: 0x485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [5.337187] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [5.337253] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 0x2458 [5.337253] iwlwifi :00:14.3: Failed to start INIT ucode: -110 [5.337263] iwlwifi :00:14.3: Firmware not running - cannot dump error [5.349140] iwlwifi :00:14.3: Failed to run INIT ucode: -110 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.173.14 [modified: lib/firmware/iwlwifi-9000-pu-b0-jf-b0-34.ucode] PackageArchitecture: all Tags: bionic Uname: Linux 5.4.8-050408-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1858366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-p
[Kernel-packages] [Bug 1857536] Re: Touch pad is not working - Lenovo G50
Hello, can you give the latest mainline kernel a try to see if it works for you: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc5/ Refer to https://wiki.ubuntu.com/KernelMainlineBuilds Thanks ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857536 Title: Touch pad is not working - Lenovo G50 Status in linux package in Ubuntu: Incomplete Bug description: Laptop : Lenovo G50 I ran below command to check that touchpad package is available or not, and couldn't find the synaptic touchpad package. Command : cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kadinish 1720 F pulseaudio /dev/snd/controlC1: kadinish 1720 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 16:02:24 2019 InstallationDate: Installed on 2019-12-10 (15 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20351 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=6a5066c3-fbca-4e9c-be14-2af9e25b497b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-12-25 (0 days ago) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.family: IDEAPAD dmi.product.name: 20351 dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857536/+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 1858594] Re: xenial/linux: 4.4.0-172.201 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix Committed => Fix Released
** 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 --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Tuesday, 07. January 2020 22:21 UTC
reason:
- prepare-package: Pending -- package not yet uploaded
- prepare-package-meta: Pending -- package not yet uploaded
- prepare-package-signed: Pending -- package not yet uploaded
+ prepare-package: Ongoing -- {} package not yet fully built
+ promote-to-proposed: Pending -- builds not complete in ppa
main:failed,meta:depwait,signed:depwait
trackers:
trusty/linux-aws: bug 1858591
trusty/linux-lts-xenial: bug 1858592
xenial/linux-aws: bug 1858581
xenial/linux-cascade: bug 1858583
xenial/linux-fips: bug 1858589
xenial/linux-kvm: bug 1858584
xenial/linux-raspi2: bug 1858586
xenial/linux-snapdragon: bug 1858588
xenial/linux/caracalla-kernel: bug 1858577
xenial/linux/pc-kernel: bug 1858578
xenial/linux/stlouis-kernel: bug 1858579
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/1858594
Title:
xenial/linux: 4.4.0-172.201 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
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:
New
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:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Tuesday, 07. January 2020 22:21 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Pending -- builds not complete in ppa
main:failed,meta:depwait,signed:depwait
trackers:
trusty/linux-aws: bug 1858591
trusty/linux-lts-xenial: bug 1858592
xenial/linux-aws: bug 1858581
xenial/linux-cascade: bug 1858583
xenial/linux-fips: bug 1858589
xenial/linux-kvm: bug 1858584
xenial/linux-raspi2: bug 1858586
xenial/linux-snapdragon: bug 1858588
xenial/linux/caracalla-kernel: bug 1858577
xenial/linux/pc-kernel: bug 1858578
xenial/linux/stlouis-kernel: bug 1858579
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858594/+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 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react
** Attachment removed: "window.png" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1729389/+attachment/5196912/+files/window.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-firmware source package in Xenial: Fix Released Status in linux source package in Artful: Invalid Status in linux-firmware source package in Artful: Fix Released Bug description: SRU Justification Impact: Bluetooth peripherals work initially but stop working shortly with Linux 4.13. Fix: Updated firmware from Intel containing a fix for the issue. Regression Potential: Any firmware updates may bring regressions, however this is a bug fix update and therefore regression potential is expected to be minimal. --- After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1729389/+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 1858181] Re: System freeze with bluetooth mouse plugin, 19.10
Please also run 'uname -a' to confirm the new kernel version is active. ** Changed in: linux (Ubuntu) Assignee: Markian Hromiak (markiantheok) => (unassigned) -- 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/1858181 Title: System freeze with bluetooth mouse plugin, 19.10 Status in linux package in Ubuntu: Incomplete Bug description: Release: 19.10 Xorg Version: 1:7.7_19ubuntu12 Problem: After powering on my computer, grub's menu shows the options for starting Ubuntu, advanced Ubuntu options, etc. If I have my bluetooth mouse receiver plugged into the usb port, the menu freezes and a hard reboot is necessary as I cannot move my cursor; however, this continues only as long as the receiver is plugged in. Once it is removed and a hard reboot is done (reboot necessary to unfreeze), the menu allows me to select "Ubuntu" and access the OS. Plugging back in in the OS lets me use the mouse without problem, but relapses if I restart/shut down. Environment Details: New HP Spectre x360, 15-inch, freshly wiped from Windows 10 Home and installed with Ubuntu 19.10 Eoan Ermine after failing to dual-boot. My boot order in HP's bios is by usb drive first followed by the system boot option, the order of which does not seem to have an effect on the problem. The mouse is a Jelly Comb 2.4GHz wireless rechargeable mouse (not sure if important). There is no legacy mode, and safeboot is currently disabled; however, the parity of the option has not affected the problem. The mouse is solely what seems to cause the issue. I plan on testing with other USB dongles for debugging if you want more data on if it's all wireless mice, all usb dongles or what have you. Steps to replicate: 0 Put wireless mouse receiver in USB slot (Spectre has only 1 so test all of them) 1 Turn on computer with ubuntu 2 Try to select any option on the grub menu. Should be frozen and unresponsive 3 Unplugging mouse should not affect frozen state 4 Restart computer with free USB slots 5 Grub should be responsive ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 01:51:02 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:863f] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:863f] InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.13 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV31AV 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-cor
[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
My backlog is full too and this isn't a joke:). I am out of a context of overlayfs, so I will need to read its sources, then figure out what change in the ubuntu kernel has introduced this issue, learn how to compile and test the ubuntu kernel... All these could sound fun 10 years ago, but now there are too much fun around me to eat it all :). -- 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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1856084] Re: Livelock between ZFS evict and writeback threads
This bug was fixed in the package zfs-linux - 0.7.12-1ubuntu5.1
---
zfs-linux (0.7.12-1ubuntu5.1) disco; urgency=medium
* Fix livelock between ZFS evict and writeback threads (LP: #1856084)
- Upstream ZFS fix 41e1aa2a06f8 ("Break out of zfs_zget early if unlinked
znode")
- Upstream ZFS fix 0c46813805f4 ("Check for unlinked znodes after
igrab()")
-- Heitor Alves de Siqueira Thu, 12 Dec 2019
13:19:29 -0300
** Changed in: zfs-linux (Ubuntu Eoan)
Status: Fix Committed => Fix Released
--
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/1856084
Title:
Livelock between ZFS evict and writeback threads
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Bionic:
Fix Released
Status in zfs-linux source package in Disco:
Fix Released
Status in zfs-linux source package in Eoan:
Fix Released
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux package in Debian:
Fix Released
Bug description:
Livelock between ZFS evict and writeback threads
[Impact]
ZIO pipeline stalls, causing ZFS workloads to hang indefinitely
[Description]
For certain ZFS workloads, we start seeing hung task timeouts in the kernel
logs due to zil_commit() stalling. This is due to zfs_zget() not detecting
whether a znode has been marked for deletion before attempting to access it,
causing a constant "retry loop" in zfs_get_data() if that znode has been
unlinked already. An example of the stack traces follows:
[72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[72742.070429] mysqld D0 5713 2881 0x0320
[72742.073220] Call Trace:
[72742.075305] __schedule+0x24e/0x880
[72742.090436] schedule+0x2c/0x80
[72742.090438] schedule_preempt_disabled+0xe/0x10
[72742.090441] __mutex_lock.isra.5+0x276/0x4e0
[72742.090547] ? dmu_tx_destroy+0x105/0x130 [zfs]
[72742.090555] __mutex_lock_slowpath+0x13/0x20
[72742.115374] ? __mutex_lock_slowpath+0x13/0x20
[72742.132266] mutex_lock+0x2f/0x40
[72742.134207] zil_commit_impl+0x1b0/0x1b30 [zfs]
[72742.150428] ? spl_kmem_alloc+0x115/0x180 [spl]
[72742.152622] ? mutex_lock+0x12/0x40
[72742.154819] ? zfs_refcount_add_many+0x9a/0x100 [zfs]
[72742.171450] zil_commit+0xde/0x150 [zfs]
[72742.173687] zfs_fsync+0x77/0xe0 [zfs]
[72742.175044] zpl_fsync+0x80/0x110 [zfs]
[72742.191690] vfs_fsync_range+0x51/0xb0
[72742.193876] do_fsync+0x3d/0x70
[72742.195126] SyS_fsync+0x10/0x20
[72742.211059] do_syscall_64+0x73/0x130
[72742.214078] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
It's possible to hit this issue due to a race between the ZFS evict
and writeback threads. If the z_iput task is trying to evict a znode
that's currently sitting in the writeback thread, both will "livelock"
each other and stall the ZIO pipeline, causing other ZFS operations
(such as zil_commit) to hang indefinitely.
This has been documented and fixed upstream in PR#9583 [0]. We need to
pull two fixes from upstream: the first one fixes the zfs_zget() issue
in the writeback thread, while the second fixes a regression on
O_TMPFILE descriptors caused by the first one.
Upstream patches:
- Break out of zfs_zget early if unlinked znode (41e1aa2a06f8)
- Check for unlinked znodes after igrab() (0c46813805f4)
[Test Case]
Being a race condition, this issue has been hard to reproduce consistently.
The racing window between evict() and the ZFS writeback thread is quite strict,
but users have reported this to show up after some hours of running
LXD-containerized mySQL workloads.
[Regression Potential]
These patches have been tested both in the ZFS test suite and in production
environments, so the potential for further regressions should be low.
Additional regressions would likely cause issues with the ZFS
writeback/commit and IO pipeline, so they should be spotted fairly quickly.
[0] https://github.com/zfsonlinux/zfs/pull/9583
[1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
[2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+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 1856084] Re: Livelock between ZFS evict and writeback threads
This bug was fixed in the package zfs-linux - 0.8.1-1ubuntu14.3
---
zfs-linux (0.8.1-1ubuntu14.3) eoan; urgency=medium
* Fix livelock between ZFS evict and writeback threads (LP: #1856084)
- Upstream ZFS fix 41e1aa2a06f8 ("Break out of zfs_zget early if unlinked
znode")
- Upstream ZFS fix 0c46813805f4 ("Check for unlinked znodes after
igrab()")
-- Heitor Alves de Siqueira Thu, 12 Dec 2019
13:21:35 -0300
--
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/1856084
Title:
Livelock between ZFS evict and writeback threads
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Bionic:
Fix Released
Status in zfs-linux source package in Disco:
Fix Released
Status in zfs-linux source package in Eoan:
Fix Released
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux package in Debian:
Fix Released
Bug description:
Livelock between ZFS evict and writeback threads
[Impact]
ZIO pipeline stalls, causing ZFS workloads to hang indefinitely
[Description]
For certain ZFS workloads, we start seeing hung task timeouts in the kernel
logs due to zil_commit() stalling. This is due to zfs_zget() not detecting
whether a znode has been marked for deletion before attempting to access it,
causing a constant "retry loop" in zfs_get_data() if that znode has been
unlinked already. An example of the stack traces follows:
[72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[72742.070429] mysqld D0 5713 2881 0x0320
[72742.073220] Call Trace:
[72742.075305] __schedule+0x24e/0x880
[72742.090436] schedule+0x2c/0x80
[72742.090438] schedule_preempt_disabled+0xe/0x10
[72742.090441] __mutex_lock.isra.5+0x276/0x4e0
[72742.090547] ? dmu_tx_destroy+0x105/0x130 [zfs]
[72742.090555] __mutex_lock_slowpath+0x13/0x20
[72742.115374] ? __mutex_lock_slowpath+0x13/0x20
[72742.132266] mutex_lock+0x2f/0x40
[72742.134207] zil_commit_impl+0x1b0/0x1b30 [zfs]
[72742.150428] ? spl_kmem_alloc+0x115/0x180 [spl]
[72742.152622] ? mutex_lock+0x12/0x40
[72742.154819] ? zfs_refcount_add_many+0x9a/0x100 [zfs]
[72742.171450] zil_commit+0xde/0x150 [zfs]
[72742.173687] zfs_fsync+0x77/0xe0 [zfs]
[72742.175044] zpl_fsync+0x80/0x110 [zfs]
[72742.191690] vfs_fsync_range+0x51/0xb0
[72742.193876] do_fsync+0x3d/0x70
[72742.195126] SyS_fsync+0x10/0x20
[72742.211059] do_syscall_64+0x73/0x130
[72742.214078] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
It's possible to hit this issue due to a race between the ZFS evict
and writeback threads. If the z_iput task is trying to evict a znode
that's currently sitting in the writeback thread, both will "livelock"
each other and stall the ZIO pipeline, causing other ZFS operations
(such as zil_commit) to hang indefinitely.
This has been documented and fixed upstream in PR#9583 [0]. We need to
pull two fixes from upstream: the first one fixes the zfs_zget() issue
in the writeback thread, while the second fixes a regression on
O_TMPFILE descriptors caused by the first one.
Upstream patches:
- Break out of zfs_zget early if unlinked znode (41e1aa2a06f8)
- Check for unlinked znodes after igrab() (0c46813805f4)
[Test Case]
Being a race condition, this issue has been hard to reproduce consistently.
The racing window between evict() and the ZFS writeback thread is quite strict,
but users have reported this to show up after some hours of running
LXD-containerized mySQL workloads.
[Regression Potential]
These patches have been tested both in the ZFS test suite and in production
environments, so the potential for further regressions should be low.
Additional regressions would likely cause issues with the ZFS
writeback/commit and IO pipeline, so they should be spotted fairly quickly.
[0] https://github.com/zfsonlinux/zfs/pull/9583
[1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
[2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+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 1856084] Re: Livelock between ZFS evict and writeback threads
This bug was fixed in the package zfs-linux - 0.7.5-1ubuntu16.7
---
zfs-linux (0.7.5-1ubuntu16.7) bionic; urgency=medium
* Fix livelock between ZFS evict and writeback threads (LP: #1856084)
- Upstream ZFS fix 41e1aa2a06f8 ("Break out of zfs_zget early if unlinked
znode")
- Upstream ZFS fix 0c46813805f4 ("Check for unlinked znodes after
igrab()")
-- Heitor Alves de Siqueira Thu, 12 Dec 2019
12:51:35 -0300
** Changed in: zfs-linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: zfs-linux (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
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/1856084
Title:
Livelock between ZFS evict and writeback threads
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Bionic:
Fix Released
Status in zfs-linux source package in Disco:
Fix Released
Status in zfs-linux source package in Eoan:
Fix Released
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux package in Debian:
Fix Released
Bug description:
Livelock between ZFS evict and writeback threads
[Impact]
ZIO pipeline stalls, causing ZFS workloads to hang indefinitely
[Description]
For certain ZFS workloads, we start seeing hung task timeouts in the kernel
logs due to zil_commit() stalling. This is due to zfs_zget() not detecting
whether a znode has been marked for deletion before attempting to access it,
causing a constant "retry loop" in zfs_get_data() if that znode has been
unlinked already. An example of the stack traces follows:
[72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[72742.070429] mysqld D0 5713 2881 0x0320
[72742.073220] Call Trace:
[72742.075305] __schedule+0x24e/0x880
[72742.090436] schedule+0x2c/0x80
[72742.090438] schedule_preempt_disabled+0xe/0x10
[72742.090441] __mutex_lock.isra.5+0x276/0x4e0
[72742.090547] ? dmu_tx_destroy+0x105/0x130 [zfs]
[72742.090555] __mutex_lock_slowpath+0x13/0x20
[72742.115374] ? __mutex_lock_slowpath+0x13/0x20
[72742.132266] mutex_lock+0x2f/0x40
[72742.134207] zil_commit_impl+0x1b0/0x1b30 [zfs]
[72742.150428] ? spl_kmem_alloc+0x115/0x180 [spl]
[72742.152622] ? mutex_lock+0x12/0x40
[72742.154819] ? zfs_refcount_add_many+0x9a/0x100 [zfs]
[72742.171450] zil_commit+0xde/0x150 [zfs]
[72742.173687] zfs_fsync+0x77/0xe0 [zfs]
[72742.175044] zpl_fsync+0x80/0x110 [zfs]
[72742.191690] vfs_fsync_range+0x51/0xb0
[72742.193876] do_fsync+0x3d/0x70
[72742.195126] SyS_fsync+0x10/0x20
[72742.211059] do_syscall_64+0x73/0x130
[72742.214078] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
It's possible to hit this issue due to a race between the ZFS evict
and writeback threads. If the z_iput task is trying to evict a znode
that's currently sitting in the writeback thread, both will "livelock"
each other and stall the ZIO pipeline, causing other ZFS operations
(such as zil_commit) to hang indefinitely.
This has been documented and fixed upstream in PR#9583 [0]. We need to
pull two fixes from upstream: the first one fixes the zfs_zget() issue
in the writeback thread, while the second fixes a regression on
O_TMPFILE descriptors caused by the first one.
Upstream patches:
- Break out of zfs_zget early if unlinked znode (41e1aa2a06f8)
- Check for unlinked znodes after igrab() (0c46813805f4)
[Test Case]
Being a race condition, this issue has been hard to reproduce consistently.
The racing window between evict() and the ZFS writeback thread is quite strict,
but users have reported this to show up after some hours of running
LXD-containerized mySQL workloads.
[Regression Potential]
These patches have been tested both in the ZFS test suite and in production
environments, so the potential for further regressions should be low.
Additional regressions would likely cause issues with the ZFS
writeback/commit and IO pipeline, so they should be spotted fairly quickly.
[0] https://github.com/zfsonlinux/zfs/pull/9583
[1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
[2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+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 1856084] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1856084 Title: Livelock between ZFS evict and writeback threads Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Disco: Fix Released Status in zfs-linux source package in Eoan: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux package in Debian: Fix Released Bug description: Livelock between ZFS evict and writeback threads [Impact] ZIO pipeline stalls, causing ZFS workloads to hang indefinitely [Description] For certain ZFS workloads, we start seeing hung task timeouts in the kernel logs due to zil_commit() stalling. This is due to zfs_zget() not detecting whether a znode has been marked for deletion before attempting to access it, causing a constant "retry loop" in zfs_get_data() if that znode has been unlinked already. An example of the stack traces follows: [72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [72742.070429] mysqld D0 5713 2881 0x0320 [72742.073220] Call Trace: [72742.075305] __schedule+0x24e/0x880 [72742.090436] schedule+0x2c/0x80 [72742.090438] schedule_preempt_disabled+0xe/0x10 [72742.090441] __mutex_lock.isra.5+0x276/0x4e0 [72742.090547] ? dmu_tx_destroy+0x105/0x130 [zfs] [72742.090555] __mutex_lock_slowpath+0x13/0x20 [72742.115374] ? __mutex_lock_slowpath+0x13/0x20 [72742.132266] mutex_lock+0x2f/0x40 [72742.134207] zil_commit_impl+0x1b0/0x1b30 [zfs] [72742.150428] ? spl_kmem_alloc+0x115/0x180 [spl] [72742.152622] ? mutex_lock+0x12/0x40 [72742.154819] ? zfs_refcount_add_many+0x9a/0x100 [zfs] [72742.171450] zil_commit+0xde/0x150 [zfs] [72742.173687] zfs_fsync+0x77/0xe0 [zfs] [72742.175044] zpl_fsync+0x80/0x110 [zfs] [72742.191690] vfs_fsync_range+0x51/0xb0 [72742.193876] do_fsync+0x3d/0x70 [72742.195126] SyS_fsync+0x10/0x20 [72742.211059] do_syscall_64+0x73/0x130 [72742.214078] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 It's possible to hit this issue due to a race between the ZFS evict and writeback threads. If the z_iput task is trying to evict a znode that's currently sitting in the writeback thread, both will "livelock" each other and stall the ZIO pipeline, causing other ZFS operations (such as zil_commit) to hang indefinitely. This has been documented and fixed upstream in PR#9583 [0]. We need to pull two fixes from upstream: the first one fixes the zfs_zget() issue in the writeback thread, while the second fixes a regression on O_TMPFILE descriptors caused by the first one. Upstream patches: - Break out of zfs_zget early if unlinked znode (41e1aa2a06f8) - Check for unlinked znodes after igrab() (0c46813805f4) [Test Case] Being a race condition, this issue has been hard to reproduce consistently. The racing window between evict() and the ZFS writeback thread is quite strict, but users have reported this to show up after some hours of running LXD-containerized mySQL workloads. [Regression Potential] These patches have been tested both in the ZFS test suite and in production environments, so the potential for further regressions should be low. Additional regressions would likely cause issues with the ZFS writeback/commit and IO pipeline, so they should be spotted fairly quickly. [0] https://github.com/zfsonlinux/zfs/pull/9583 [1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8 [2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+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 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** 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: 1856985 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Promote to Updates - phase-changed: Tuesday, 07. January 2020 20:56 UTC + phase: Holding before Promote to Security + phase-changed: Wednesday, 08. January 2020 00:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- not ready for security (replication dwell) - promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-gcp/gcp-kernel: bug 1856982 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/1856983 Title: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Fix Released 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: 1856985 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Security phase-changed: Wednesday, 08. January 2020 00:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- not ready for security (replication dwell) trackers: bionic/linux-gcp/gcp-kernel: bug 1856982 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856983/+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 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
@kaihengfeng - sorry for the delay over the US holidays. I don't have physical access to the system myself, but I've made the request to a user who does. -- 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/1856608 Title: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Triaged 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: This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81. [Impact] USB port unusable and boot time takes ~5 minutes longer to complete. Kernel emits messages like: usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [Test Case] dmesg | grep "Cannot enable" [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+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 1858307] Re: Dota2 Arcade mods lock up on first start
Okay it just crashed and I restarted. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858307/+attachment/5318342/+files/syslog -- 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/1858307 Title: Dota2 Arcade mods lock up on first start Status in linux package in Ubuntu: Incomplete Bug description: Dota2 crashes unless on the latest kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ryan 2297 F pulseaudio /dev/snd/controlC0: ryan 2297 F pulseaudio /dev/snd/controlC1: ryan 2297 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rsu7l4@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_rsu7l4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99X EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858307/+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 1858487] Re: linux build and autopkg tests need to use python2 instead of python
my only information are the failing autopkg tests. s/python-dev/python2-dev/ probably will help. but then you have to make sure to call python2 instead of python. having that converted to python3 would be the preferred option. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858487 Title: linux build and autopkg tests need to use python2 instead of python Status in linux package in Ubuntu: Confirmed Bug description: linux build and autopkg tests need to use python2 instead of python. Even better, please use python3. debian/control debian/tests/control need the change, plus make sure that either python2 or python3 are used in the shebang. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858487/+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 1858594] Re: xenial/linux: 4.4.0-172.201 -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 -- packages: main: linux meta: linux-meta signed: linux-signed - phase: Ready for Packaging - phase-changed: Tuesday, 07. January 2020 03:39 UTC + phase: Packaging + phase-changed: Tuesday, 07. January 2020 22:21 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded trackers: trusty/linux-aws: bug 1858591 trusty/linux-lts-xenial: bug 1858592 xenial/linux-aws: bug 1858581 xenial/linux-cascade: bug 1858583 xenial/linux-fips: bug 1858589 xenial/linux-kvm: bug 1858584 xenial/linux-raspi2: bug 1858586 xenial/linux-snapdragon: bug 1858588 xenial/linux/caracalla-kernel: bug 1858577 xenial/linux/pc-kernel: bug 1858578 xenial/linux/stlouis-kernel: bug 1858579 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/1858594 Title: xenial/linux: 4.4.0-172.201 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Tuesday, 07. January 2020 22:21 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: trusty/linux-aws: bug 1858591 trusty/linux-lts-xenial: bug 1858592 xenial/linux-aws: bug 1858581 xenial/linux-cascade: bug 1858583 xenial/linux-fips: bug 1858589 xenial/linux-kvm: bug 1858584 xenial/linux-raspi2: bug 1858586 xenial/linux-snapdragon: bug 1858588 xenial/linux/caracalla-kernel: bug 1858577 xenial/linux/pc-kernel: bug 1858578 xenial/linux/stlouis-kernel: bug 1858579 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858594/+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 1858594] Re: xenial/linux: 4.4.0-172.201 -proposed tracker
** Summary changed: - xenial/linux: -proposed tracker + xenial/linux: 4.4.0-172.201 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) -- 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/1858594 Title: xenial/linux: 4.4.0-172.201 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Tuesday, 07. January 2020 22:21 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: trusty/linux-aws: bug 1858591 trusty/linux-lts-xenial: bug 1858592 xenial/linux-aws: bug 1858581 xenial/linux-cascade: bug 1858583 xenial/linux-fips: bug 1858589 xenial/linux-kvm: bug 1858584 xenial/linux-raspi2: bug 1858586 xenial/linux-snapdragon: bug 1858588 xenial/linux/caracalla-kernel: bug 1858577 xenial/linux/pc-kernel: bug 1858578 xenial/linux/stlouis-kernel: bug 1858579 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858594/+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 1856603] Re: fstrim on nvme / AMD CPU fails and produces kernel error messages
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: fstrim (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: fstrim (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: fstrim (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: fstrim (Ubuntu) ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Connor Kuehl (connork) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Connor Kuehl (connork) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Connor Kuehl (connork) ** No longer affects: fstrim (Ubuntu Xenial) ** No longer affects: fstrim (Ubuntu Bionic) ** No longer affects: fstrim (Ubuntu 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/1856603 Title: fstrim on nvme / AMD CPU fails and produces kernel error messages Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: /dev/nvme0n1 Sabrent Rocket 4.0 1TB firmware RKT401.1 on Ubuntu 19.10 with an ASRock 300 Deskmini motherboard and a Ryzen 3400G CPU. The filesystem is ext4: Linux elemental 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux UUID=c1812230-91be-4a18-8055-c3b7c82fbbd8 / ext4 defaults 0 0 /dev/nvme0n1p2 on / type ext4 (rw,relatime) When I run fstrim -v / as root, I get the following error message at the command line: seth@elemental:~$ sudo fstrim -v / fstrim: /: FITRIM ioctl failed: Input/output error and the following kernel messages are logged: [ 136.309115] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x0 flags=0x] [ 136.309129] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x700 flags=0x] [ 136.309139] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x680 flags=0x] [ 136.309150] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x300 flags=0x] [ 136.309162] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x200 flags=0x] [ 136.309171] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x580 flags=0x] [ 136.309180] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x100 flags=0x] [ 136.309189] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x400 flags=0x] [ 136.309198] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x380 flags=0x] [ 136.309207] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x780 flags=0x] [ 136.309216] amd_iommu_report_page_fault: 1 callbacks suppressed [ 136.309218] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x180 flags=0x] [ 136.309228] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x500 flags=0x] [ 136.309238] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x480 flags=0x] [ 136.309250] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x280 flags=0x] [ 136.309259] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x600 flags=0x] [ 136.309269] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x80 flags=0x] [ 136.309279] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x980 flags=0x] [ 136.309291] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x900 flags=0x] [ 136.309301] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x880 flags=0x] [ 136.309311] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0xa00 flags=0x] [ 136.309762] blk_update_request: I/O error, dev nvme0n1, sector 1141976 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0 I have tried setting iom
[Kernel-packages] [Bug 1854777] Re: disco/linux-gcp: 5.0.0-1027.28 -proposed tracker
*** This bug is a duplicate of bug 1856985 *** https://bugs.launchpad.net/bugs/1856985 This bug was fixed in the package linux-gcp - 5.0.0-1028.29~18.04.1 --- linux-gcp (5.0.0-1028.29~18.04.1) bionic; urgency=medium * bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker (LP: #1856983) [ Ubuntu: 5.0.0-1028.29 ] * disco/linux-gcp: 5.0.0-1028.29 -proposed tracker (LP: #1856985) * Enable GVE network driver for GCP kernels (LP: #1855992) - net: place xmit recursion in softnet data - gve: Add basic driver framework for Compute Engine Virtual NIC - gve: Add transmit and receive support - gve: Add workqueue and reset support - gve: Add ethtool support - gve: Fix u64_stats_sync to initialize start - gve: fix -ENOMEM null check on a page allocation - gve: Fix error return code in gve_alloc_qpls() - gve: fix unused variable/label warnings - gve: Remove the exporting of gve_probe - gve: replace kfree with kvfree - gve: Fix case where desc_cnt and data_cnt can get out of sync - gve: Copy and paste bug in gve_get_stats() - gve: Fixes DMA synchronization. - gve: Fix the queue page list allocated pages count - [config] Enable GVE driver linux-gcp (5.0.0-1027.28~18.04.1) bionic; urgency=medium * bionic/linux-gcp: 5.0.0-1027.28~18.04.1 -proposed tracker (LP: #1854774) [ Ubuntu: 5.0.0-1027.28 ] * disco/linux-gcp: 5.0.0-1027.28 -proposed tracker (LP: #1854777) * backport DIMLIB (lib/dim/) to pre-5.2 kernels (LP: #1852637) - gcp: [Config] CONFIG_DIMLIB=y * disco/linux: 5.0.0-38.41 -proposed tracker (LP: #1854788) * [Regression] Failed to boot disco kernel built from master-next (kernel kernel NULL pointer dereference) (LP: #1853981) - SAUCE: blk-mq: Fix blk_mq_make_request for mq devices * CVE-2019-14901 - SAUCE: mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame() * CVE-2019-14896 // CVE-2019-14897 - SAUCE: libertas: Fix two buffer overflows at parsing bss descriptor * CVE-2019-14895 - SAUCE: mwifiex: fix possible heap overflow in mwifiex_process_country_ie() * [CML] New device id's for CMP-H (LP: #1846335) - mmc: sdhci-pci: Add another Id for Intel CML - i2c: i801: Add support for Intel Comet Lake PCH-H - mtd: spi-nor: intel-spi: Add support for Intel Comet Lake-H SPI serial flash - mfd: intel-lpss: Add Intel Comet Lake PCH-H PCI IDs * Please add patch fixing RK818 ID detection (LP: #1853192) - SAUCE: mfd: rk808: Fix RK818 ID template * [SRU][B/OEM-B/OEM-OSP1/D] Enable new Elan touchpads which are not in current whitelist (LP: #1853246) - Input: elan_i2c - export the device id whitelist - HID: quirks: Refactor ELAN 400 and 401 handling * Lenovo dock MAC Address pass through doesn't work in Ubuntu (LP: #1827961) - r8152: Add macpassthru support for ThinkPad Thunderbolt 3 Dock Gen 2 * [CML-S62] Need enable turbostat patch support for Comet lake- S 6+2 (LP: #1847451) - SAUCE: tools/power turbostat: Add Cometlake support * External microphone can't work on some dell machines with the codec alc256 or alc236 (LP: #1853791) - SAUCE: ALSA: hda/realtek - Move some alc256 pintbls to fallback table - SAUCE: ALSA: hda/realtek - Move some alc236 pintbls to fallback table * Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection (LP: #1853197) - xfrm: Fix memleak on xfrm state destroy * CVE-2019-18660: patches for Ubuntu (LP: #1853142) // CVE-2019-18660 - powerpc/64s: support nospectre_v2 cmdline option - powerpc/book3s64: Fix link stack flush on context switch - KVM: PPC: Book3S HV: Flush link stack on guest exit to host kernel * Raydium Touchscreen on ThinkPad L390 does not work (LP: #1849721) - HID: i2c-hid: fix no irq after reset on raydium 3118 * Make Goodix I2C touchpads work (LP: #1853842) - HID: i2c-hid: Remove runtime power management - HID: i2c-hid: Send power-on command after reset * Touchpad doesn't work on Dell Inspiron 7000 2-in-1 (LP: #1851901) - Revert "UBUNTU: SAUCE: mfd: intel-lpss: add quirk for Dell XPS 13 7390 2-in-1" - lib: devres: add a helper function for ioremap_uc - mfd: intel-lpss: Use devm_ioremap_uc for MMIO * CVE-2019-19055 - nl80211: fix memory leak in nl80211_get_ftm_responder_stats * [CML-S62] Need enable intel_rapl patch support for Comet lake- S 6+2 (LP: #1847454) - powercap/intel_rapl: add support for CometLake Mobile - powercap/intel_rapl: add support for Cometlake desktop * [CML-S62] Need enable intel_pmc_core driver patch for Comet lake- S 6+2 (LP: #1847450) - SAUCE: platform/x86: intel_pmc_core: Add Comet Lake (CML) platform support to intel_pmc_core driver * update ENA driver for DIMLIB dynamic interrupt moderation (LP: #1853180) - net: ena: add intr_moder_rx_interval to struct ena_com_dev and use it - net: ena: switch to dim algorithm for rx adaptive interru
[Kernel-packages] [Bug 1854774] Re: bionic/linux-gcp: 5.0.0-1027.28~18.04.1 -proposed tracker
*** This bug is a duplicate of bug 1856983 *** https://bugs.launchpad.net/bugs/1856983 This bug was fixed in the package linux-gcp - 5.0.0-1028.29~18.04.1 --- linux-gcp (5.0.0-1028.29~18.04.1) bionic; urgency=medium * bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker (LP: #1856983) [ Ubuntu: 5.0.0-1028.29 ] * disco/linux-gcp: 5.0.0-1028.29 -proposed tracker (LP: #1856985) * Enable GVE network driver for GCP kernels (LP: #1855992) - net: place xmit recursion in softnet data - gve: Add basic driver framework for Compute Engine Virtual NIC - gve: Add transmit and receive support - gve: Add workqueue and reset support - gve: Add ethtool support - gve: Fix u64_stats_sync to initialize start - gve: fix -ENOMEM null check on a page allocation - gve: Fix error return code in gve_alloc_qpls() - gve: fix unused variable/label warnings - gve: Remove the exporting of gve_probe - gve: replace kfree with kvfree - gve: Fix case where desc_cnt and data_cnt can get out of sync - gve: Copy and paste bug in gve_get_stats() - gve: Fixes DMA synchronization. - gve: Fix the queue page list allocated pages count - [config] Enable GVE driver linux-gcp (5.0.0-1027.28~18.04.1) bionic; urgency=medium * bionic/linux-gcp: 5.0.0-1027.28~18.04.1 -proposed tracker (LP: #1854774) [ Ubuntu: 5.0.0-1027.28 ] * disco/linux-gcp: 5.0.0-1027.28 -proposed tracker (LP: #1854777) * backport DIMLIB (lib/dim/) to pre-5.2 kernels (LP: #1852637) - gcp: [Config] CONFIG_DIMLIB=y * disco/linux: 5.0.0-38.41 -proposed tracker (LP: #1854788) * [Regression] Failed to boot disco kernel built from master-next (kernel kernel NULL pointer dereference) (LP: #1853981) - SAUCE: blk-mq: Fix blk_mq_make_request for mq devices * CVE-2019-14901 - SAUCE: mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame() * CVE-2019-14896 // CVE-2019-14897 - SAUCE: libertas: Fix two buffer overflows at parsing bss descriptor * CVE-2019-14895 - SAUCE: mwifiex: fix possible heap overflow in mwifiex_process_country_ie() * [CML] New device id's for CMP-H (LP: #1846335) - mmc: sdhci-pci: Add another Id for Intel CML - i2c: i801: Add support for Intel Comet Lake PCH-H - mtd: spi-nor: intel-spi: Add support for Intel Comet Lake-H SPI serial flash - mfd: intel-lpss: Add Intel Comet Lake PCH-H PCI IDs * Please add patch fixing RK818 ID detection (LP: #1853192) - SAUCE: mfd: rk808: Fix RK818 ID template * [SRU][B/OEM-B/OEM-OSP1/D] Enable new Elan touchpads which are not in current whitelist (LP: #1853246) - Input: elan_i2c - export the device id whitelist - HID: quirks: Refactor ELAN 400 and 401 handling * Lenovo dock MAC Address pass through doesn't work in Ubuntu (LP: #1827961) - r8152: Add macpassthru support for ThinkPad Thunderbolt 3 Dock Gen 2 * [CML-S62] Need enable turbostat patch support for Comet lake- S 6+2 (LP: #1847451) - SAUCE: tools/power turbostat: Add Cometlake support * External microphone can't work on some dell machines with the codec alc256 or alc236 (LP: #1853791) - SAUCE: ALSA: hda/realtek - Move some alc256 pintbls to fallback table - SAUCE: ALSA: hda/realtek - Move some alc236 pintbls to fallback table * Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection (LP: #1853197) - xfrm: Fix memleak on xfrm state destroy * CVE-2019-18660: patches for Ubuntu (LP: #1853142) // CVE-2019-18660 - powerpc/64s: support nospectre_v2 cmdline option - powerpc/book3s64: Fix link stack flush on context switch - KVM: PPC: Book3S HV: Flush link stack on guest exit to host kernel * Raydium Touchscreen on ThinkPad L390 does not work (LP: #1849721) - HID: i2c-hid: fix no irq after reset on raydium 3118 * Make Goodix I2C touchpads work (LP: #1853842) - HID: i2c-hid: Remove runtime power management - HID: i2c-hid: Send power-on command after reset * Touchpad doesn't work on Dell Inspiron 7000 2-in-1 (LP: #1851901) - Revert "UBUNTU: SAUCE: mfd: intel-lpss: add quirk for Dell XPS 13 7390 2-in-1" - lib: devres: add a helper function for ioremap_uc - mfd: intel-lpss: Use devm_ioremap_uc for MMIO * CVE-2019-19055 - nl80211: fix memory leak in nl80211_get_ftm_responder_stats * [CML-S62] Need enable intel_rapl patch support for Comet lake- S 6+2 (LP: #1847454) - powercap/intel_rapl: add support for CometLake Mobile - powercap/intel_rapl: add support for Cometlake desktop * [CML-S62] Need enable intel_pmc_core driver patch for Comet lake- S 6+2 (LP: #1847450) - SAUCE: platform/x86: intel_pmc_core: Add Comet Lake (CML) platform support to intel_pmc_core driver * update ENA driver for DIMLIB dynamic interrupt moderation (LP: #1853180) - net: ena: add intr_moder_rx_interval to struct ena_com_dev and use it - net: ena: switch to dim algorithm for rx adaptive interru
[Kernel-packages] [Bug 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~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: 1856985 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Ready for Promote to Updates - phase-changed: Tuesday, 07. January 2020 18:36 UTC + phase: Promote to Updates + phase-changed: Tuesday, 07. January 2020 20:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-security: Holding -- not ready for security (replication dwell) + promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-gcp/gcp-kernel: bug 1856982 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/1856983 Title: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: In Progress Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Fix Released 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: 1856985 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Updates phase-changed: Tuesday, 07. January 2020 20:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- not ready for security (replication dwell) promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-gcp/gcp-kernel: bug 1856982 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856983/+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 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker
This bug was fixed in the package linux-gcp - 5.0.0-1028.29~18.04.1 --- linux-gcp (5.0.0-1028.29~18.04.1) bionic; urgency=medium * bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker (LP: #1856983) [ Ubuntu: 5.0.0-1028.29 ] * disco/linux-gcp: 5.0.0-1028.29 -proposed tracker (LP: #1856985) * Enable GVE network driver for GCP kernels (LP: #1855992) - net: place xmit recursion in softnet data - gve: Add basic driver framework for Compute Engine Virtual NIC - gve: Add transmit and receive support - gve: Add workqueue and reset support - gve: Add ethtool support - gve: Fix u64_stats_sync to initialize start - gve: fix -ENOMEM null check on a page allocation - gve: Fix error return code in gve_alloc_qpls() - gve: fix unused variable/label warnings - gve: Remove the exporting of gve_probe - gve: replace kfree with kvfree - gve: Fix case where desc_cnt and data_cnt can get out of sync - gve: Copy and paste bug in gve_get_stats() - gve: Fixes DMA synchronization. - gve: Fix the queue page list allocated pages count - [config] Enable GVE driver linux-gcp (5.0.0-1027.28~18.04.1) bionic; urgency=medium * bionic/linux-gcp: 5.0.0-1027.28~18.04.1 -proposed tracker (LP: #1854774) [ Ubuntu: 5.0.0-1027.28 ] * disco/linux-gcp: 5.0.0-1027.28 -proposed tracker (LP: #1854777) * backport DIMLIB (lib/dim/) to pre-5.2 kernels (LP: #1852637) - gcp: [Config] CONFIG_DIMLIB=y * disco/linux: 5.0.0-38.41 -proposed tracker (LP: #1854788) * [Regression] Failed to boot disco kernel built from master-next (kernel kernel NULL pointer dereference) (LP: #1853981) - SAUCE: blk-mq: Fix blk_mq_make_request for mq devices * CVE-2019-14901 - SAUCE: mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame() * CVE-2019-14896 // CVE-2019-14897 - SAUCE: libertas: Fix two buffer overflows at parsing bss descriptor * CVE-2019-14895 - SAUCE: mwifiex: fix possible heap overflow in mwifiex_process_country_ie() * [CML] New device id's for CMP-H (LP: #1846335) - mmc: sdhci-pci: Add another Id for Intel CML - i2c: i801: Add support for Intel Comet Lake PCH-H - mtd: spi-nor: intel-spi: Add support for Intel Comet Lake-H SPI serial flash - mfd: intel-lpss: Add Intel Comet Lake PCH-H PCI IDs * Please add patch fixing RK818 ID detection (LP: #1853192) - SAUCE: mfd: rk808: Fix RK818 ID template * [SRU][B/OEM-B/OEM-OSP1/D] Enable new Elan touchpads which are not in current whitelist (LP: #1853246) - Input: elan_i2c - export the device id whitelist - HID: quirks: Refactor ELAN 400 and 401 handling * Lenovo dock MAC Address pass through doesn't work in Ubuntu (LP: #1827961) - r8152: Add macpassthru support for ThinkPad Thunderbolt 3 Dock Gen 2 * [CML-S62] Need enable turbostat patch support for Comet lake- S 6+2 (LP: #1847451) - SAUCE: tools/power turbostat: Add Cometlake support * External microphone can't work on some dell machines with the codec alc256 or alc236 (LP: #1853791) - SAUCE: ALSA: hda/realtek - Move some alc256 pintbls to fallback table - SAUCE: ALSA: hda/realtek - Move some alc236 pintbls to fallback table * Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection (LP: #1853197) - xfrm: Fix memleak on xfrm state destroy * CVE-2019-18660: patches for Ubuntu (LP: #1853142) // CVE-2019-18660 - powerpc/64s: support nospectre_v2 cmdline option - powerpc/book3s64: Fix link stack flush on context switch - KVM: PPC: Book3S HV: Flush link stack on guest exit to host kernel * Raydium Touchscreen on ThinkPad L390 does not work (LP: #1849721) - HID: i2c-hid: fix no irq after reset on raydium 3118 * Make Goodix I2C touchpads work (LP: #1853842) - HID: i2c-hid: Remove runtime power management - HID: i2c-hid: Send power-on command after reset * Touchpad doesn't work on Dell Inspiron 7000 2-in-1 (LP: #1851901) - Revert "UBUNTU: SAUCE: mfd: intel-lpss: add quirk for Dell XPS 13 7390 2-in-1" - lib: devres: add a helper function for ioremap_uc - mfd: intel-lpss: Use devm_ioremap_uc for MMIO * CVE-2019-19055 - nl80211: fix memory leak in nl80211_get_ftm_responder_stats * [CML-S62] Need enable intel_rapl patch support for Comet lake- S 6+2 (LP: #1847454) - powercap/intel_rapl: add support for CometLake Mobile - powercap/intel_rapl: add support for Cometlake desktop * [CML-S62] Need enable intel_pmc_core driver patch for Comet lake- S 6+2 (LP: #1847450) - SAUCE: platform/x86: intel_pmc_core: Add Comet Lake (CML) platform support to intel_pmc_core driver * update ENA driver for DIMLIB dynamic interrupt moderation (LP: #1853180) - net: ena: add intr_moder_rx_interval to struct ena_com_dev and use it - net: ena: switch to dim algorithm for rx adaptive interrupt moderation - net: ena: reimplement set/get_coalesce() - net: ena: enable the inte
[Kernel-packages] [Bug 1856985] Re: disco/linux-gcp: 5.0.0-1028.29 -proposed tracker
This bug was fixed in the package linux-gcp - 5.0.0-1028.29~18.04.1 --- linux-gcp (5.0.0-1028.29~18.04.1) bionic; urgency=medium * bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker (LP: #1856983) [ Ubuntu: 5.0.0-1028.29 ] * disco/linux-gcp: 5.0.0-1028.29 -proposed tracker (LP: #1856985) * Enable GVE network driver for GCP kernels (LP: #1855992) - net: place xmit recursion in softnet data - gve: Add basic driver framework for Compute Engine Virtual NIC - gve: Add transmit and receive support - gve: Add workqueue and reset support - gve: Add ethtool support - gve: Fix u64_stats_sync to initialize start - gve: fix -ENOMEM null check on a page allocation - gve: Fix error return code in gve_alloc_qpls() - gve: fix unused variable/label warnings - gve: Remove the exporting of gve_probe - gve: replace kfree with kvfree - gve: Fix case where desc_cnt and data_cnt can get out of sync - gve: Copy and paste bug in gve_get_stats() - gve: Fixes DMA synchronization. - gve: Fix the queue page list allocated pages count - [config] Enable GVE driver linux-gcp (5.0.0-1027.28~18.04.1) bionic; urgency=medium * bionic/linux-gcp: 5.0.0-1027.28~18.04.1 -proposed tracker (LP: #1854774) [ Ubuntu: 5.0.0-1027.28 ] * disco/linux-gcp: 5.0.0-1027.28 -proposed tracker (LP: #1854777) * backport DIMLIB (lib/dim/) to pre-5.2 kernels (LP: #1852637) - gcp: [Config] CONFIG_DIMLIB=y * disco/linux: 5.0.0-38.41 -proposed tracker (LP: #1854788) * [Regression] Failed to boot disco kernel built from master-next (kernel kernel NULL pointer dereference) (LP: #1853981) - SAUCE: blk-mq: Fix blk_mq_make_request for mq devices * CVE-2019-14901 - SAUCE: mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame() * CVE-2019-14896 // CVE-2019-14897 - SAUCE: libertas: Fix two buffer overflows at parsing bss descriptor * CVE-2019-14895 - SAUCE: mwifiex: fix possible heap overflow in mwifiex_process_country_ie() * [CML] New device id's for CMP-H (LP: #1846335) - mmc: sdhci-pci: Add another Id for Intel CML - i2c: i801: Add support for Intel Comet Lake PCH-H - mtd: spi-nor: intel-spi: Add support for Intel Comet Lake-H SPI serial flash - mfd: intel-lpss: Add Intel Comet Lake PCH-H PCI IDs * Please add patch fixing RK818 ID detection (LP: #1853192) - SAUCE: mfd: rk808: Fix RK818 ID template * [SRU][B/OEM-B/OEM-OSP1/D] Enable new Elan touchpads which are not in current whitelist (LP: #1853246) - Input: elan_i2c - export the device id whitelist - HID: quirks: Refactor ELAN 400 and 401 handling * Lenovo dock MAC Address pass through doesn't work in Ubuntu (LP: #1827961) - r8152: Add macpassthru support for ThinkPad Thunderbolt 3 Dock Gen 2 * [CML-S62] Need enable turbostat patch support for Comet lake- S 6+2 (LP: #1847451) - SAUCE: tools/power turbostat: Add Cometlake support * External microphone can't work on some dell machines with the codec alc256 or alc236 (LP: #1853791) - SAUCE: ALSA: hda/realtek - Move some alc256 pintbls to fallback table - SAUCE: ALSA: hda/realtek - Move some alc236 pintbls to fallback table * Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection (LP: #1853197) - xfrm: Fix memleak on xfrm state destroy * CVE-2019-18660: patches for Ubuntu (LP: #1853142) // CVE-2019-18660 - powerpc/64s: support nospectre_v2 cmdline option - powerpc/book3s64: Fix link stack flush on context switch - KVM: PPC: Book3S HV: Flush link stack on guest exit to host kernel * Raydium Touchscreen on ThinkPad L390 does not work (LP: #1849721) - HID: i2c-hid: fix no irq after reset on raydium 3118 * Make Goodix I2C touchpads work (LP: #1853842) - HID: i2c-hid: Remove runtime power management - HID: i2c-hid: Send power-on command after reset * Touchpad doesn't work on Dell Inspiron 7000 2-in-1 (LP: #1851901) - Revert "UBUNTU: SAUCE: mfd: intel-lpss: add quirk for Dell XPS 13 7390 2-in-1" - lib: devres: add a helper function for ioremap_uc - mfd: intel-lpss: Use devm_ioremap_uc for MMIO * CVE-2019-19055 - nl80211: fix memory leak in nl80211_get_ftm_responder_stats * [CML-S62] Need enable intel_rapl patch support for Comet lake- S 6+2 (LP: #1847454) - powercap/intel_rapl: add support for CometLake Mobile - powercap/intel_rapl: add support for Cometlake desktop * [CML-S62] Need enable intel_pmc_core driver patch for Comet lake- S 6+2 (LP: #1847450) - SAUCE: platform/x86: intel_pmc_core: Add Comet Lake (CML) platform support to intel_pmc_core driver * update ENA driver for DIMLIB dynamic interrupt moderation (LP: #1853180) - net: ena: add intr_moder_rx_interval to struct ena_com_dev and use it - net: ena: switch to dim algorithm for rx adaptive interrupt moderation - net: ena: reimplement set/get_coalesce() - net: ena: enable the inte
[Kernel-packages] [Bug 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1856983 Title: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: In Progress Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Fix Released 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: 1856985 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Updates phase-changed: Tuesday, 07. January 2020 20:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- not ready for security (replication dwell) promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-gcp/gcp-kernel: bug 1856982 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856983/+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 1800566] Re: Make reset_devices parameter default for kdump
This bug was fixed in the package makedumpfile - 1:1.6.6-4ubuntu1 --- makedumpfile (1:1.6.6-4ubuntu1) focal; urgency=medium [ Thadeu Lima de Souza Cascardo ] * Merge from Debian unstable. Remaining changes: - Bump amd64 crashkernel from 384M-:128M to 512M-:192M. * Use reset_devices as a cmdline parameter. (LP: #1800566) * Use kdump-config reload after cpu or memory hotplug. (LP: #1828596) [ Guilherme G. Piccoli ] * Add a systemd-resolved service dependency in order kdump-tools is able to resolve DNS when in kdump boot. (LP: #1856323) makedumpfile (1:1.6.6-4) unstable; urgency=medium * Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860) * kdump-config: implement try-reload * udev: hotplug: use try-reload * Set Rules-Requires-Root to no makedumpfile (1:1.6.6-3) unstable; urgency=medium * Add a reload command. * Use kdump-config reload after cpu or memory hotplug. * Use reset_devices as a cmdline parameter. -- Thadeu Lima de Souza Cascardo Wed, 18 Dec 2019 14:38:51 -0300 ** Changed in: makedumpfile (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1800566 Title: Make reset_devices parameter default for kdump Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Trusty: Won't Fix Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: In Progress Status in makedumpfile source package in Eoan: In Progress Status in makedumpfile source package in Focal: Fix Released Bug description: [Impact] * Kdump does not configure by default the crash kernel to perform a device reset by default, by passing the "reset_devices" parameter. * Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they are booting from a non-healthy condition and needs to issue some form of reset to the adapter, like clearing DMA mapping in their firmware for example. Users currently (kernel v5.5-rc2) are: aacraid, hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus. This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions. [Test Case] 1) Deploy a Bionic VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'reset_devices' parameter: $ kdump-config test ... kexec command to be used: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crash kernel command-line. The risks are related with bad behavior with the kernel when using "reset_devices", like if the driver has bugs in this path. It's considered safer to have the option (and this way prevent problems for booting a unhealthy kernel with potential stuck DMAs in the devices) than not having it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+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 1856323] Re: kdump-tools is unable to resolve DNS when systemd-resolved is used
This bug was fixed in the package makedumpfile - 1:1.6.6-4ubuntu1
---
makedumpfile (1:1.6.6-4ubuntu1) focal; urgency=medium
[ Thadeu Lima de Souza Cascardo ]
* Merge from Debian unstable. Remaining changes:
- Bump amd64 crashkernel from 384M-:128M to 512M-:192M.
* Use reset_devices as a cmdline parameter. (LP: #1800566)
* Use kdump-config reload after cpu or memory hotplug. (LP: #1828596)
[ Guilherme G. Piccoli ]
* Add a systemd-resolved service dependency in order kdump-tools is able
to resolve DNS when in kdump boot. (LP: #1856323)
makedumpfile (1:1.6.6-4) unstable; urgency=medium
* Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860)
* kdump-config: implement try-reload
* udev: hotplug: use try-reload
* Set Rules-Requires-Root to no
makedumpfile (1:1.6.6-3) unstable; urgency=medium
* Add a reload command.
* Use kdump-config reload after cpu or memory hotplug.
* Use reset_devices as a cmdline parameter.
-- Thadeu Lima de Souza Cascardo Wed, 18 Dec
2019 14:38:51 -0300
** Changed in: makedumpfile (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1856323
Title:
kdump-tools is unable to resolve DNS when systemd-resolved is used
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Bionic:
In Progress
Status in makedumpfile source package in Disco:
In Progress
Status in makedumpfile source package in Eoan:
In Progress
Status in makedumpfile source package in Focal:
Fix Released
Bug description:
[Impact]
* Currently kdump is unable to handle domain name resolution due to
the lack of "resolved" service in the kdump environment; this happens
given the nature of reduced service load required in the kdump
scenario.
* Kdump currently relies on a systemd service approach - there are 2
services, one being a configuration/load entity (kdump-tools.service)
whereas the other is the crash dump service itself (kdump-tools-
dump.service). Due to the complexity and risk in booting a machine
after a kernel crash to collect kernel dump, it's expected kdump-
tools-dump to load the minimal possible amount of services. In order
to achieve that, kdump-tools-dump relies only in the sysinit and
network-online targets.
* The systemd DNS tool ("resolved") is not ready in the moment kdump-
tools-dump service is up to collect the kernel dump; also, "resolved"
depends on dbus.socket to work, so to have a fully functional DNS
resolution we are hereby adding both services as dependencies for
kdump-tools-dump, so the network dump functionality works with
hostnames (not requiring anymore that users set IP raw addresses).
* The attached SVG files (kdump.svg and regular_boot.svg) contains
"systemd-analyze plot" outputs from a kdump-tools-dump and regular
boot perspective. To collect the kdump data we manage to change the
kdump-tools-dump service to load SSHd and also that required disabling
the OneShot property of such service. With that data, one can check
the services started/completed in each environment - it's possible to
notice the absence of systemd-resolved when in kdump environment.
* Notice this modification is being worked concurrently with other
kdump-tools' changes in LP #1828596.
[Test Case]
1) Deploy a Bionic VM e.g. with uvt-kvm;
2) Set-up console output in the guest;
3) Install the kdump-tools package;
4) Configure a network dump (SSH or NFS) using hostnames for the target
machine;
5) Perform the test dump (with 'echo c> /proc/sysrq-trigger') and watch the
failure in name resolution,
[Regression Potential]
* The modifications hereby proposed are minimal and scope-constrained to
kdump-tools package; it'll only affect the services loaded before
kdump-tools-dump collecting service.
A regression would then potentially fails kdump completion if one of the new
services added to the kdump environment load (resolved and dbus.socket) fails
to load and stalls/prevents the kdump service complete load.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1856323/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
On Tue, Jan 07, 2020 at 07:07:36PM -, Andrew Vagin wrote: > The root cause of this fail is a wrong mount ID which is reported for > file mappings: If you have cycles to come up with a patch to fix this that would be appreciated. Otherwise this will end up lower in my priority queue since my backlog is quite full atm. -- 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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation
This bug was fixed in the package makedumpfile - 1:1.6.6-4ubuntu1 --- makedumpfile (1:1.6.6-4ubuntu1) focal; urgency=medium [ Thadeu Lima de Souza Cascardo ] * Merge from Debian unstable. Remaining changes: - Bump amd64 crashkernel from 384M-:128M to 512M-:192M. * Use reset_devices as a cmdline parameter. (LP: #1800566) * Use kdump-config reload after cpu or memory hotplug. (LP: #1828596) [ Guilherme G. Piccoli ] * Add a systemd-resolved service dependency in order kdump-tools is able to resolve DNS when in kdump boot. (LP: #1856323) makedumpfile (1:1.6.6-4) unstable; urgency=medium * Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860) * kdump-config: implement try-reload * udev: hotplug: use try-reload * Set Rules-Requires-Root to no makedumpfile (1:1.6.6-3) unstable; urgency=medium * Add a reload command. * Use kdump-config reload after cpu or memory hotplug. * Use reset_devices as a cmdline parameter. -- Thadeu Lima de Souza Cascardo Wed, 18 Dec 2019 14:38:51 -0300 ** Changed in: makedumpfile (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: In Progress Status in makedumpfile source package in Eoan: In Progress Status in makedumpfile source package in Focal: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+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 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
since last upgrade it works fine too : thanx a lot ! best regards -- 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/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Cor
[Kernel-packages] [Bug 1854842] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs
Hello Mohammad, The kernel team has reviewed the patches and they have received two acks from senior kernel developers: https://lists.ubuntu.com/archives/kernel-team/2019-December/106516.html https://lists.ubuntu.com/archives/kernel-team/2020-January/106624.html >From there, the patch was applied to bionic master-next branch, which means it will be included in this current SRU cycle: https://lists.ubuntu.com/archives/kernel-team/2020-January/106643.html The next steps is for the kernel team to build the kernel update and push it to -proposed. This will likely happen at the end of this week / early next week. Once this happens, I will write again and ask you to test the kernel in -proposed to make sure that it fixes the problem. If it does, we can tag this bug as verified, and wait for the kernel to be released. I'll keep you informed of all progress, and I'll write back soon when it is time to test the kernel in -proposed. Thanks, Matthew -- 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/1854842 Title: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1854842 [Impact] On machines equipped with Mellanox NIC's, in this particular case, Mellanox 5 series NICs using the mlx5_core driver, there is a kernel splat when sending large IP packets which have padding at the end. enp6s0f0: hw csum failure CPU: 19 PID: 0 Comm: swapper/19 Not tainted 4.15.0-72-generic Call Trace: dump_stack+0x63/0x8e netdev_rx_csum_fault+0x38/0x40 __skb_checksum_complete+0xbc/0xd0 nf_ip_checksum+0xc3/0xf0 icmp_error+0x27d/0x310 [nf_conntrack_ipv4] nf_conntrack_in+0x15a/0x510 [nf_conntrack] ? __skb_checksum+0x68/0x330 ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] nf_hook_slow+0x48/0xc0 ? skb_send_sock+0x50/0x50 ip_rcv+0x301/0x360 ? inet_del_offload+0x40/0x40 __netif_receive_skb_core+0x432/0xb80 __netif_receive_skb+0x18/0x60 ? __netif_receive_skb+0x18/0x60 netif_receive_skb_internal+0x45/0xe0 napi_gro_receive+0xc5/0xf0 mlx5e_handle_rx_cqe+0x48d/0x5e0 [mlx5_core] ? enqueue_task_rt+0x1b4/0x2e0 mlx5e_poll_rx_cq+0xd1/0x8c0 [mlx5_core] mlx5e_napi_poll+0x9d/0x290 [mlx5_core] net_rx_action+0x140/0x3a0 __do_softirq+0xe4/0x2d4 irq_exit+0xc5/0xd0 do_IRQ+0x86/0xe0 common_interrupt+0x8c/0x8c This bug is a further attempt to fix these splats, as there has been previous fixes in LP #1840854 and a series of commits which landed in 4.15.0-67 (LP #1847155) as a part of upstream -stable patches. This bug will also fix the same problems on the new Mellanox CX6 and Bluefield hardware, which has been enabled already via previous upstream -stable patches which landed in LP #1847155. [Fix] This particular issue was fixed for Mellanox series 5 drivers in the following commits: commit 0aa1d18615c163f92935b806dcaff9157645233a Author: Saeed Mahameed Date: Tue Mar 12 00:24:52 2019 -0700 Subject: net/mlx5e: Rx, Fixup skb checksum for packets with tail padding This commit required a minor backport. This commit was selected for upstream -stable in 4.19.76 and 5.0.10. This commit appears to be omitted from "Bionic update: upstream stable patchset 2019-10-07", which is LP #1847155, probably due to requiring a backport. commit db849faa9bef993a1379dc510623f750a72fa7ce Author: Saeed Mahameed Date: Fri May 3 13:14:59 2019 -0700 Subject: net/mlx5e: Rx, Fix checksum calculation for new hardware This commit required a minor backport. This commit was selected for upstream -stable in 5.1.21 and 5.2.4. This commit has already been applied to the disco kernel, as part of stable updates. [Testcase] The following scapy script will reproduce this issue. Run from the machine with the Mellanox series 5 NIC: 1) a=Ether(dst='ff:ff:ff:ff:ff:ff')/IP(dst='127.0.0.1')/ICMP()/Padding(load='\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe') 2) sendp(a, iface='enp6s0f0') 3) Check dmesg on the reciever side. The example uses localhost, so check dmesg. I have built some test kernels, which are available here: https://launchpad.net/~mruffell/+archive/ubuntu/lp1854842-test This kernel contains 0aa1d18615c163f92935b806dcaff9157645233a. and https://launchpad.net/~mruffell/+archive/ubuntu/lp1854842-test-2 This kernel contains db849faa9bef993a1379dc510623f750a72fa7ce. If you install the test kernels the issue is resolved. [
[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Confirmed Status in zram-config package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in zram-config source package in Bionic: Confirmed Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 16:12 seq crw-rw 1 root audio 116, 33 Oct 23 16:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Cannot stat file /proc/22822/fd/10: Permission denied Cannot stat file /proc/22831/fd/10: Permission denied DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none CRYPTSETUP=n IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S1200SP NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 panic=1 verbose console=tty0 console=ttyS0,115200n8 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/25/2018 dmi.bios.vendor: Intel Corporation dmi.bios.version: S1200SP.86B.03.01.1029.012520180838 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S1200SP dmi.board.vendor: Intel Corporation dmi.board.version: H57532-271 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rnS1200SP:rvrH57532-271:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S1200SP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notificatio
[Kernel-packages] [Bug 1858181] Re: System freeze with bluetooth mouse plugin, 19.10
Installed amd64 deb files successfully and rebooted to test. Bug still present; no changes. -- 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/1858181 Title: System freeze with bluetooth mouse plugin, 19.10 Status in linux package in Ubuntu: Incomplete Bug description: Release: 19.10 Xorg Version: 1:7.7_19ubuntu12 Problem: After powering on my computer, grub's menu shows the options for starting Ubuntu, advanced Ubuntu options, etc. If I have my bluetooth mouse receiver plugged into the usb port, the menu freezes and a hard reboot is necessary as I cannot move my cursor; however, this continues only as long as the receiver is plugged in. Once it is removed and a hard reboot is done (reboot necessary to unfreeze), the menu allows me to select "Ubuntu" and access the OS. Plugging back in in the OS lets me use the mouse without problem, but relapses if I restart/shut down. Environment Details: New HP Spectre x360, 15-inch, freshly wiped from Windows 10 Home and installed with Ubuntu 19.10 Eoan Ermine after failing to dual-boot. My boot order in HP's bios is by usb drive first followed by the system boot option, the order of which does not seem to have an effect on the problem. The mouse is a Jelly Comb 2.4GHz wireless rechargeable mouse (not sure if important). There is no legacy mode, and safeboot is currently disabled; however, the parity of the option has not affected the problem. The mouse is solely what seems to cause the issue. I plan on testing with other USB dongles for debugging if you want more data on if it's all wireless mice, all usb dongles or what have you. Steps to replicate: 0 Put wireless mouse receiver in USB slot (Spectre has only 1 so test all of them) 1 Turn on computer with ubuntu 2 Try to select any option on the grub menu. Should be frozen and unresponsive 3 Unplugging mouse should not affect frozen state 4 Restart computer with free USB slots 5 Grub should be responsive ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 01:51:02 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:863f] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:863f] InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.13 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV31AV 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserv
[Kernel-packages] [Bug 1858181] Re: System freeze with bluetooth mouse plugin, 19.10
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Markian Hromiak (markiantheok) -- 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/1858181 Title: System freeze with bluetooth mouse plugin, 19.10 Status in linux package in Ubuntu: Incomplete Bug description: Release: 19.10 Xorg Version: 1:7.7_19ubuntu12 Problem: After powering on my computer, grub's menu shows the options for starting Ubuntu, advanced Ubuntu options, etc. If I have my bluetooth mouse receiver plugged into the usb port, the menu freezes and a hard reboot is necessary as I cannot move my cursor; however, this continues only as long as the receiver is plugged in. Once it is removed and a hard reboot is done (reboot necessary to unfreeze), the menu allows me to select "Ubuntu" and access the OS. Plugging back in in the OS lets me use the mouse without problem, but relapses if I restart/shut down. Environment Details: New HP Spectre x360, 15-inch, freshly wiped from Windows 10 Home and installed with Ubuntu 19.10 Eoan Ermine after failing to dual-boot. My boot order in HP's bios is by usb drive first followed by the system boot option, the order of which does not seem to have an effect on the problem. The mouse is a Jelly Comb 2.4GHz wireless rechargeable mouse (not sure if important). There is no legacy mode, and safeboot is currently disabled; however, the parity of the option has not affected the problem. The mouse is solely what seems to cause the issue. I plan on testing with other USB dongles for debugging if you want more data on if it's all wireless mice, all usb dongles or what have you. Steps to replicate: 0 Put wireless mouse receiver in USB slot (Spectre has only 1 so test all of them) 1 Turn on computer with ubuntu 2 Try to select any option on the grub menu. Should be frozen and unresponsive 3 Unplugging mouse should not affect frozen state 4 Restart computer with free USB slots 5 Grub should be responsive ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 01:51:02 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:863f] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:863f] InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.13 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV31AV 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserv
[Kernel-packages] [Bug 1853044] Re: 5.3.0-23-generic causes fans to spin when idle
This also affects 5.4.0-9-generic - I see the same behavior on today's focal. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853044 Title: 5.3.0-23-generic causes fans to spin when idle Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to 5.3.0-23-generic the fans in my machine don't stop running. They always sound like something is utilizing CPU - even with no applications running after boot. If I boot back to 5.3.0-19-generic it's fine. My microcode version is reported as 0xd4 and iucode-tool reports: iucode-tool: system has processor(s) with signature 0x000506e3 Let me know if you need anything else. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 2898 F pulseaudio /dev/snd/pcmC2D0p: dean 2898 F...m pulseaudio /dev/snd/controlC0: dean 2898 F pulseaudio /dev/snd/controlC1: dean 2898 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 13:03:34 2019 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (482 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-07-19 (121 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853044/+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 1857040] Re: zfs: upstream support for hardware-accelerated encryption
Also should apply: commit 10fa254539ec41c6b043785d4e7ab34bce383b9f Author: Brian Behlendorf Date: Thu Oct 24 10:17:33 2019 -0700 Linux 4.14, 4.19, 5.0+ compat: SIMD save/restore but this also requires a rather tricky backport of: commit 006e9a40882468be68f276c946bae812b74ac35c Author: Matthew Macy Date: Thu Sep 5 09:34:54 2019 -0700 OpenZFS restructuring - move platform specific headers and also we are dependant on a backport of: commit 608f8749a1055e6769899788e11bd51fd396f9e5 Author: Brian Behlendorf Date: Tue Oct 1 12:50:34 2019 -0700 Perform KABI checks in parallel -- 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/1857040 Title: zfs: upstream support for hardware-accelerated encryption Status in linux package in Ubuntu: In Progress Bug description: I understand that in Linux 5.0+, certain encryption-related symbols have been marked GPL-only, making them unavailable for use by zfs. As a result, using encryption in zfs pools increases cpu load / decreases disk throughput. There are a pair of upstream pull requests that should improve the performance (with performance measurement done on x86-64). Can these be pulled into the Ubuntu kernel? https://github.com/zfsonlinux/zfs/pull/9515 https://github.com/zfsonlinux/zfs/pull/9296 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040/+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 1857257] 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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318314/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318310/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318316/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318312/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318309/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
apport information ** Tags added: apport-collected eoan uec-images ** Description changed: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux- image-5.0.0-32-generic still works and linux-image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jan 7 18:52 seq + crw-rw 1 root audio 116, 33 Jan 7 18:52 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + DistroRelease: Ubuntu 19.10 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: DigitalOcean Droplet + Package: linux (not installed) + PciMultimedia: + + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 + ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-26-generic N/A + linux-backports-modules-5.3.0-26-generic N/A + linux-firmwareN/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: eoan uec-images + Uname: Linux 5.3.0-26-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 12/12/2017 + dmi.bios.vendor: DigitalOcean + dmi.bios.version: 20171212 + dmi.chassis.type: 1 + dmi.chassis.vendor: Bochs + dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: + dmi.product.family: DigitalOcean_Droplet + dmi.product.name: Droplet + dmi.product.version: 20171212 + dmi.sys.vendor: DigitalOcean ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318308/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevi
[Kernel-packages] [Bug 1857257] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318311/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318315/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318313/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
** Changed in: linux (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: New Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
The root cause of this fail is a wrong mount ID which is reported for file mappings: Steps to reproduce: root@ubuntu-s-4vcpu-8gb-nyc1-01:~# uname -a Linux ubuntu-s-4vcpu-8gb-nyc1-01 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu-s-4vcpu-8gb-nyc1-01:~# docker run -it --rm --privileged busybox / # ls -l /proc/1/map_files/ total 0 lr1 root root64 Jan 7 18:59 40-401000 -> /bin/sh lr1 root root64 Jan 7 19:00 401000-4dd000 -> /bin/sh lr1 root root64 Jan 7 19:00 4dd000-514000 -> /bin/sh lr1 root root64 Jan 7 19:00 514000-516000 -> /bin/sh / # exec 50https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: New Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1853485] Re: Bionic kernel panic on Cavium ThunderX CN88XX
Tagging verification-failed due to bug 1857074. ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-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/1853485 Title: Bionic kernel panic on Cavium ThunderX CN88XX Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: Description: kernel panic while trying to deploy Bionic 18.04.3 Linux version 4.15.0-70-generic on Cavium ThunderX CN88XX (arm64) System: Board Model: gbt-mt30 Board name: MT30-GS0 System name:MT30-GS0 SKU: CN8890-2000BG2601-AAP-Y22-G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853485/+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 1854207] Re: Unrevert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2"
Marking verification failed, as that is blocked by bug 1857074. ** Description changed: We reverted a couple changes in 4.15.0-72.81 because they were causing a regression (bug 1853326) that was not understood at press time: b042ff6848684 Revert "arm64: Get rid of __smccc_workaround_1_hvc_*" 5f395b984282e Revert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2" This bug is to track the reapplication of these patches, once we've figured out the underlying issue. + + Update: The regression was believed to actually be caused by bug + 1853485, which has now been addressed. ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-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/1854207 Title: Unrevert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2" Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: We reverted a couple changes in 4.15.0-72.81 because they were causing a regression (bug 1853326) that was not understood at press time: b042ff6848684 Revert "arm64: Get rid of __smccc_workaround_1_hvc_*" 5f395b984282e Revert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2" This bug is to track the reapplication of these patches, once we've figured out the underlying issue. Update: The regression was believed to actually be caused by bug 1853485, which has now been addressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854207/+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 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** 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: 1856985 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Testing - phase-changed: Monday, 06. January 2020 15:31 UTC + phase: Ready for Promote to Updates + phase-changed: Tuesday, 07. January 2020 18:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-gcp/gcp-kernel: bug 1856982 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/1856983 Title: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1856985 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Updates phase-changed: Tuesday, 07. January 2020 18:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-gcp/gcp-kernel: bug 1856982 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856983/+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 1856603] Re: fstrim on nvme / AMD CPU fails and produces kernel error messages
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: fstrim (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Connor Kuehl (connork) ** No longer affects: fstrim (Ubuntu 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/1856603 Title: fstrim on nvme / AMD CPU fails and produces kernel error messages Status in fstrim package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: In Progress Bug description: /dev/nvme0n1 Sabrent Rocket 4.0 1TB firmware RKT401.1 on Ubuntu 19.10 with an ASRock 300 Deskmini motherboard and a Ryzen 3400G CPU. The filesystem is ext4: Linux elemental 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux UUID=c1812230-91be-4a18-8055-c3b7c82fbbd8 / ext4 defaults 0 0 /dev/nvme0n1p2 on / type ext4 (rw,relatime) When I run fstrim -v / as root, I get the following error message at the command line: seth@elemental:~$ sudo fstrim -v / fstrim: /: FITRIM ioctl failed: Input/output error and the following kernel messages are logged: [ 136.309115] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x0 flags=0x] [ 136.309129] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x700 flags=0x] [ 136.309139] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x680 flags=0x] [ 136.309150] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x300 flags=0x] [ 136.309162] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x200 flags=0x] [ 136.309171] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x580 flags=0x] [ 136.309180] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x100 flags=0x] [ 136.309189] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x400 flags=0x] [ 136.309198] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x380 flags=0x] [ 136.309207] nvme :01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x address=0x780 flags=0x] [ 136.309216] amd_iommu_report_page_fault: 1 callbacks suppressed [ 136.309218] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x180 flags=0x] [ 136.309228] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x500 flags=0x] [ 136.309238] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x480 flags=0x] [ 136.309250] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x280 flags=0x] [ 136.309259] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x600 flags=0x] [ 136.309269] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x80 flags=0x] [ 136.309279] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x980 flags=0x] [ 136.309291] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x900 flags=0x] [ 136.309301] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0x880 flags=0x] [ 136.309311] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x address=0xa00 flags=0x] [ 136.309762] blk_update_request: I/O error, dev nvme0n1, sector 1141976 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0 I have tried setting iommu passthrough on boot but this doesn’t seem to help: GRUB_CMDLINE_LINUX_DEFAULT="amd_iommu=pt avic=1” This is possibly related to: https://bugzilla.kernel.org/show_bug.cgi?id=202665 http://git.infradead.org/nvme.git/commitdiff/530436c45ef2e446c12538a400e465929a0b3ade?hp=400b6a7b13a3fd71cff087139ce45dd1e5fff444 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1856603/+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 1857626] Re: Kernel Linux version 5.3.0-24.26 et Realtek RTL822BE 802.11a/b/g/n/ac
Hmm that's no an Ubuntu kernel. But anyway... Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc5 -- 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/1857626 Title: Kernel Linux version 5.3.0-24.26 et Realtek RTL822BE 802.11a/b/g/n/ac Status in linux package in Ubuntu: Incomplete Bug description: No wifi connexion by using the kernels 5.3.0. A problem was solved with the kernel 5.0.0.21 avait été résolu (voir), but it starts again. Please find some information lspci -nnk | grep 0280 -A3 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] Subsystem: AzureWave RTL8822BE 802.11a/b/g/n/ac WiFi adapter [1a3b:2950] Kernel driver in use: rtw_pci Kernel modules: rtwpci dmesg -lerr | tail -50 [5.917496] rtw_pci :03:00.0: failed to send h2c command [6.558933] sep5_10: Driver loading... [ 10.219360] rtw_pci :03:00.0: failed to send h2c command [ 10.219401] rtw_pci :03:00.0: failed to send h2c command [ 18.674133] rtw_pci :03:00.0: failed to send h2c command [ 18.674221] rtw_pci :03:00.0: failed to send h2c command [ 18.674305] rtw_pci :03:00.0: failed to send h2c command [ 18.674719] rtw_pci :03:00.0: failed to send h2c command [ 19.197448] rtw_pci :03:00.0: failed to send h2c command [ 20.246203] rtw_pci :03:00.0: failed to send h2c command [ 23.507151] rtw_pci :03:00.0: failed to send h2c command [ 23.507189] rtw_pci :03:00.0: failed to send h2c command [ 31.958087] rtw_pci :03:00.0: failed to send h2c command [ 31.958176] rtw_pci :03:00.0: failed to send h2c command [ 31.958247] rtw_pci :03:00.0: failed to send h2c command [ 31.958374] rtw_pci :03:00.0: failed to send h2c command [ 32.561597] rtw_pci :03:00.0: failed to send h2c command dmesg reports also a problem with the driver [ 10.236063] rtw_pci :03:00.0: failed to send h2c command [ 10.236107] rtw_pci :03:00.0: failed to send h2c command [ 10.236112] rtw_pci :03:00.0: sta 54:64:d9:4e:01:df joined with macid 0 [ 10.738280] [ cut here ] [ 10.738300] purge skb(s) not reported by firmware [ 10.738392] WARNING: CPU: 2 PID: 0 at drivers/net/wireless/realtek/rtw88/tx.c:156 rtw_tx_report_purge_timer+0x25/0x60 [rtw88] [ 10.738395] Modules linked in: sep5(OE) socperf3(OE) pax(OE) cmac bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress ac97_bus x86_pkg_temp_thermal snd_hda_codec_generic intel_powerclamp ledtrig_audio snd_pcm_dmaengine coretemp kvm_intel snd_hda_intel snd_hda_codec kvm snd_hda_core irqbypass snd_hwdep snd_pcm mei_hdcp snd_seq_midi snd_seq_midi_event intel_rapl_msr snd_rawmidi crct10dif_pclmul crc32_pclmul joydev ghash_clmulni_intel i915 snd_seq aesni_intel rtwpci rtw88 aes_x86_64 uvcvideo btusb crypto_simd snd_seq_device snd_timer videobuf2_vmalloc drm_kms_helper btrtl cryptd glue_helper videobuf2_memops mac80211 videobuf2_v4l2 btbcm intel_cstate drm snd videobuf2_common btintel bluetooth intel_rapl_perf videodev cfg80211 asus_nb_wmi i2c_algo_bit processor_thermal_device spi_pxa2xx_platform fb_sys_fops asus_wmi [ 10.738473] input_leds mei_me syscopyarea intel_rapl_common idma64 mc ecdh_generic sysfillrect dw_dmac intel_xhci_usb_role_switch sparse_keymap serio_raw wmi_bmof soundcore mxm_wmi ecc libarc4 8250_dw dw_dmac_core hid_multitouch mei roles sysimgblt virt_dma intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_thermal_rel acpi_pad asus_wireless sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid_generic i2c_hid hid r8169 i2c_i801 ahci intel_lpss_pci realtek libahci intel_lpss video wmi pinctrl_sunrisepoint pinctrl_intel [ 10.738546] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G OE 5.3.0-24-generic #26-Ubuntu [ 10.738549] Hardware name: ASUSTeK COMPUTER INC. X705UDR/X705UDR, BIOS X705UDR.302 09/27/2017 [ 10.738568] RIP: 0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88] [ 10.738574] Code: 00 00 00 00 00 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 f0 bd c8 c0 e8 f6 0a 87 f2 <0f> 0b 4c 8d 6b d8 4c 89 ef e8 ed 4e 27 f3 48 8d 7b e0 49 89 c4 e8 [ 10.738577] RSP: 0018:b6c480170e48 EFLAGS: 00010286 [ 10.738582] RAX: RBX: 96afd3c8d848 RCX: 083f [ 10.738585] RDX: RSI: 00f6 RDI: 083f [ 10.738587] RBP: b6c480170e60 R08: 96afdea
[Kernel-packages] [Bug 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker
No ADT failures. ** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released -- 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/1856983 Title: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1856985 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Updates phase-changed: Tuesday, 07. January 2020 18:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-gcp/gcp-kernel: bug 1856982 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856983/+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 1857626] Re: Kernel Linux version 5.3.0-24.26 et Realtek RTL822BE 802.11a/b/g/n/ac
apport information ** Description changed: No wifi connexion by using the kernels 5.3.0. A problem was solved with the kernel 5.0.0.21 avait été résolu (voir), but it starts again. Please find some information lspci -nnk | grep 0280 -A3 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] Subsystem: AzureWave RTL8822BE 802.11a/b/g/n/ac WiFi adapter [1a3b:2950] Kernel driver in use: rtw_pci Kernel modules: rtwpci dmesg -lerr | tail -50 [5.917496] rtw_pci :03:00.0: failed to send h2c command [6.558933] sep5_10: Driver loading... [ 10.219360] rtw_pci :03:00.0: failed to send h2c command [ 10.219401] rtw_pci :03:00.0: failed to send h2c command [ 18.674133] rtw_pci :03:00.0: failed to send h2c command [ 18.674221] rtw_pci :03:00.0: failed to send h2c command [ 18.674305] rtw_pci :03:00.0: failed to send h2c command [ 18.674719] rtw_pci :03:00.0: failed to send h2c command [ 19.197448] rtw_pci :03:00.0: failed to send h2c command [ 20.246203] rtw_pci :03:00.0: failed to send h2c command [ 23.507151] rtw_pci :03:00.0: failed to send h2c command [ 23.507189] rtw_pci :03:00.0: failed to send h2c command [ 31.958087] rtw_pci :03:00.0: failed to send h2c command [ 31.958176] rtw_pci :03:00.0: failed to send h2c command [ 31.958247] rtw_pci :03:00.0: failed to send h2c command [ 31.958374] rtw_pci :03:00.0: failed to send h2c command [ 32.561597] rtw_pci :03:00.0: failed to send h2c command dmesg reports also a problem with the driver [ 10.236063] rtw_pci :03:00.0: failed to send h2c command [ 10.236107] rtw_pci :03:00.0: failed to send h2c command [ 10.236112] rtw_pci :03:00.0: sta 54:64:d9:4e:01:df joined with macid 0 [ 10.738280] [ cut here ] [ 10.738300] purge skb(s) not reported by firmware [ 10.738392] WARNING: CPU: 2 PID: 0 at drivers/net/wireless/realtek/rtw88/tx.c:156 rtw_tx_report_purge_timer+0x25/0x60 [rtw88] [ 10.738395] Modules linked in: sep5(OE) socperf3(OE) pax(OE) cmac bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress ac97_bus x86_pkg_temp_thermal snd_hda_codec_generic intel_powerclamp ledtrig_audio snd_pcm_dmaengine coretemp kvm_intel snd_hda_intel snd_hda_codec kvm snd_hda_core irqbypass snd_hwdep snd_pcm mei_hdcp snd_seq_midi snd_seq_midi_event intel_rapl_msr snd_rawmidi crct10dif_pclmul crc32_pclmul joydev ghash_clmulni_intel i915 snd_seq aesni_intel rtwpci rtw88 aes_x86_64 uvcvideo btusb crypto_simd snd_seq_device snd_timer videobuf2_vmalloc drm_kms_helper btrtl cryptd glue_helper videobuf2_memops mac80211 videobuf2_v4l2 btbcm intel_cstate drm snd videobuf2_common btintel bluetooth intel_rapl_perf videodev cfg80211 asus_nb_wmi i2c_algo_bit processor_thermal_device spi_pxa2xx_platform fb_sys_fops asus_wmi [ 10.738473] input_leds mei_me syscopyarea intel_rapl_common idma64 mc ecdh_generic sysfillrect dw_dmac intel_xhci_usb_role_switch sparse_keymap serio_raw wmi_bmof soundcore mxm_wmi ecc libarc4 8250_dw dw_dmac_core hid_multitouch mei roles sysimgblt virt_dma intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_thermal_rel acpi_pad asus_wireless sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid_generic i2c_hid hid r8169 i2c_i801 ahci intel_lpss_pci realtek libahci intel_lpss video wmi pinctrl_sunrisepoint pinctrl_intel [ 10.738546] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G OE 5.3.0-24-generic #26-Ubuntu [ 10.738549] Hardware name: ASUSTeK COMPUTER INC. X705UDR/X705UDR, BIOS X705UDR.302 09/27/2017 [ 10.738568] RIP: 0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88] [ 10.738574] Code: 00 00 00 00 00 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 f0 bd c8 c0 e8 f6 0a 87 f2 <0f> 0b 4c 8d 6b d8 4c 89 ef e8 ed 4e 27 f3 48 8d 7b e0 49 89 c4 e8 [ 10.738577] RSP: 0018:b6c480170e48 EFLAGS: 00010286 [ 10.738582] RAX: RBX: 96afd3c8d848 RCX: 083f [ 10.738585] RDX: RSI: 00f6 RDI: 083f [ 10.738587] RBP: b6c480170e60 R08: 96afdea97448 R09: 0004 [ 10.738591] R10: R11: 0001 R12: 96afdea9b600 [ 10.738594] R13: 96afd3c8d848 R14: c0c2a7d0 R15: 96afd3c8d848 [ 10.738598] FS: () GS:96afdea8() knlGS: [ 10.738602] CS: 0010 DS: ES: CR0: 80050033 [ 10.738605] CR2: 7fbec810500
[Kernel-packages] [Bug 1850195] Re: Update EFA driver to 1.5.0
** Changed in: linux-aws (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Eoan) Status: In Progress => Fix Committed -- 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/1850195 Title: Update EFA driver to 1.5.0 Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws source package in Disco: Fix Committed Status in linux-aws source package in Eoan: Fix Committed Bug description: Version 1.5.0 of the EFA driver has been tagged: https://github.com/amzn/amzn-drivers/releases/tag/efa_linux_1.5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1850195/+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 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react
On your iOS device, go to Settings > Bluetooth and make sure that Bluetooth is on. If you can't turn on Bluetooth or you see a spinning gear, restart your iPhone, iPad, or iPod touch. ... Make sure that your Bluetooth accessory and iOS device are close to each other. Turn your Bluetooth accessory off and back on again if anyone face issue click here https://www.epsonprintersupport247.com/fix-epson-printer-offline/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-firmware source package in Xenial: Fix Released Status in linux source package in Artful: Invalid Status in linux-firmware source package in Artful: Fix Released Bug description: SRU Justification Impact: Bluetooth peripherals work initially but stop working shortly with Linux 4.13. Fix: Updated firmware from Intel containing a fix for the issue. Regression Potential: Any firmware updates may bring regressions, however this is a bug fix update and therefore regression potential is expected to be minimal. --- After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1729389/+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 1858487] Re: linux build and autopkg tests need to use python2 instead of python
@doko, our 5.4 package in focal-release doesn't have any python shebangs for rebuild testing (which I think is all that is important here), though our autotests very likely do have them. We do have a build dep on python-dev, I'll look into that but I suspect that is for building python bindings for perf. If you're seeing some issue beyond this please provide some more detail. -- 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/1858487 Title: linux build and autopkg tests need to use python2 instead of python Status in linux package in Ubuntu: Confirmed Bug description: linux build and autopkg tests need to use python2 instead of python. Even better, please use python3. debian/control debian/tests/control need the change, plus make sure that either python2 or python3 are used in the shebang. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858487/+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 1855666] Re: alsa/sof: change to use hda hdmi codec driver to make hdmi audio on the docking station work
** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-oem-osp1 (Ubuntu Eoan) Status: New => Invalid ** Changed in: linux (Ubuntu Eoan) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855666 Title: alsa/sof: change to use hda hdmi codec driver to make hdmi audio on the docking station work Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] We have integrated the alsa sof driver in the oem-osp1 kernel, and when we tested the hdmi audio function on the docking station, we found if the machine use sof driver, the hdmi audio on the docking station can't work. [Fix] Intel wrote patches to let sof driver to choose hda hdmi codec driver, then both hdmi on the laptop and on the docking station worked. [Test Case] ran the kernel with these patches, and in the userspace, we used the intel updated ucm, then the hdmi audio on the docking station worked. [Regression Risk] Low, Intel wrote the patches and told us to backport these patches. In addition, we already tested these patches with 4 oem project bugs, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855666/+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 1858487] Re: linux build and autopkg tests need to use python2 instead of python
So I have changed shebangs in https://lists.ubuntu.com/archives/kernel- team/2019-December/106258.html And it was I who added the "wrong" package to the autopkgtests in https://lists.ubuntu.com/archives/kernel-team/2019-December/106376.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858487 Title: linux build and autopkg tests need to use python2 instead of python Status in linux package in Ubuntu: Confirmed Bug description: linux build and autopkg tests need to use python2 instead of python. Even better, please use python3. debian/control debian/tests/control need the change, plus make sure that either python2 or python3 are used in the shebang. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858487/+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 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install
I agree with Richard and we had the same discussion yesterday with Didier. We should expose zfs encryption in Ubiquity and align is on LVM. This would leave the decision to the user to use or not ZFS encryption and not force him to use it if he selects ZFS. Secondly, we don't have any sort of feedback and the measure of the impact of zfs encryption on our users is very limited. It seems to me very risky to enable it by default without any way to disable it, especially for an LTS and on a desktop where users are not necessarily familiar with the CLI. @Steve could you add a section with your vision of ZFS encryption to the "ZFS on root" specification so we can discuss and refine the approach there? Thanks. -- 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/1857398 Title: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install Status in ubiquity package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: zfs supports built-in encryption support, but the decision of whether a pool is encrypted or not must be made at pool creation time; it is possible to add encrypted datasets on top of an unencrypted pool but it is not possible to do an online change of a dataset (or a whole pool) to toggle encryption. We should therefore always install with encryption enabled on zfs systems, with a non-secret key by default, and allow the user to use 'zfs change-key -o keylocation=prompt' after install to take ownership of the encryption and upgrade the security. This is also the simplest way to allow users to avoid having to choose between the security of full-disk encryption, and the advanced filesystem features of zfs since it requires no additional UX work in ubiquity. We should make sure that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed first in the kernel so that enabling zfs encryption does not impose an unreasonable performance penalty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+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 1858650] Re: package zfsutils-linux 0.8.1-1ubuntu14.2 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
This bug is requesting that the pi kernel be shipped with zfs, so zfs- dkms is not needed: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852119 The pi4 can have up to 4Gb of RAM, that's a good start for zfs. I'm using the dkms package for now, but hoping that this request is addressed so I don't have to build the module each time a new kernel is released. -- 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/1858650 Title: package zfsutils-linux 0.8.1-1ubuntu14.2 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Won't Fix Bug description: cant install zfsutils-linux on headless nor desktop Jan 07 15:06:06 ubuntu zfs[3775]: The ZFS modules are not loaded. Jan 07 15:06:06 ubuntu zfs[3775]: Try running '/sbin/modprobe zfs' as root to lo ad them. Jan 07 15:06:06 ubuntu systemd[1]: zfs-mount.service: Main process exited, code= exited, status=1/FAILURE Jan 07 15:06:06 ubuntu systemd[1]: zfs-mount.service: Failed with result 'exit-c ode'. Jan 07 15:06:06 ubuntu systemd[1]: Failed to start Mount ZFS filesystems. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: zfsutils-linux 0.8.1-1ubuntu14.2 ProcVersionSignature: Ubuntu 5.3.0-1015.17-raspi2 5.3.13 Uname: Linux 5.3.0-1015-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Tue Jan 7 15:06:06 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.1-1ubuntu14.2 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1858650/+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 1857074] Re: Cavium ThunderX CN88XX Panic : Unknown reason
** Changed in: linux (Ubuntu Bionic) 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/1857074 Title: Cavium ThunderX CN88XX Panic : Unknown reason Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Series: Bionic Kernel: 4.15.0-74.84 linux-generic Steps to reproduce: Install 4.15.0-74.84 Kernel and boot the system. The following crash was observed while testing the proposed kernel for the 2019.12.02 SRU Cycle. This kernel was built to include fixes for the following bugs: * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX (LP: #1853326) - Revert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2" - Revert "arm64: Get rid of __smccc_workaround_1_hvc_*" * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and Kunpeng920 (LP: #1852723) - SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to correct place The following crash appears to be a NEW bug. not related to the prior bugs listed above. This bug DOES NOT APPEAR to be related to LP#1857073. This is another NEW BUG. Hostname: Starmie Probable Cause is unknown at this point and still under investigation. [ OK ] Found device WDC_WD5003ABYZ-011FA0 efi. Mounting /boot/efi... [ OK ] Mounted /boot/efi. [ OK ] Reached target Local File Systems. Starting AppArmor initialization... Starting Tell Plymouth To Write Out Runtime Data... Starting ebtables ruleset management... [ 20.942427] kernel BUG at /build/linux-pWET3k/linux-4.15.0/fs/buffer.c:1240! [ 20.951416] Internal error: Oops - BUG: 0 [#1] SMP [ 20.958153] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip cavium_rng_vf shpchp cavium_rng gpio_keys uio_pdrv_genirq ipmi_ssif uio ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 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 nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect aes_ce_blk sysimgblt fb_sys_fops aes_ce_cipher crc32_ce drm crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce ahci thunder_bgx libahci thunder_xcv i2c_thunderx mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 21.044326] Process systemd (pid: 1, stack limit = 0x5af6f18b) [ 21.053858] CPU: 1 PID: 1 Comm: systemd Not tainted 4.15.0-74-generic #84-Ubuntu [ 21.063931] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 5.11 12/12/2012 [ 21.074790] pstate: 20400085 (nzCv daIf +PAN -UAO) [ 21.082096] pc : __find_get_block+0x2e8/0x398 [ 21.088917] lr : __getblk_gfp+0x3c/0x2a8 [ 21.095379] sp : 099ab7e0 [ 21.101062] x29: 099ab7e0 x28: [ 21.108699] x27: x26: [ 21.116265] x25: 0001 x24: [ 21.123788] x23: 0008 x22: 801f26116c80 [ 21.131302] x21: 801f26116c80 x20: 245c [ 21.138808] x19: 1000 x18: a59c3a70 [ 21.146300] x17: x16: [ 21.153730] x15: 0020 x14: 0012 [ 21.161083] x13: 2f7374696e752f64 x12: 0101010101010101 [ 21.168397] x11: 7f7f7f7f7f7f7f7f x10: 0972d000 [ 21.175689] x9 : x8 : 801f7ba7e3c0 [ 21.183042] x7 : 801f7ba7e3e0 x6 : [ 21.190667] x5 : 0004 x4 : 0020 [ 21.197955] x3 : 0008 x2 : 1000 [ 21.205680] x1 : 245c x0 : 0080 [ 21.212918] Call trace: [ 21.217257] __find_get_block+0x2e8/0x398 [ 21.223160] __getblk_gfp+0x3c/0x2a8 [ 21.228644] ext4_getblk+0xcc/0x1b0 [ 21.233991] ext4_bread_batch+0x78/0x1c8 [ 21.239726] ext4_find_entry+0x2d4/0x598 [ 21.245416] ext4_lookup+0xac/0x278 [ 21.250612] lookup_slow+0xac/0x190 [ 21.255736] walk_component+0x228/0x340 [ 21.261151] link_path_walk+0x2f4/0x568 [ 21.266499] path_parentat+0x44/0x88 [ 21.271521] filename_parentat+0xa0/0x170 [ 21.276924] filename_create+0x60/0x168 [ 21.282082] SyS_symlinkat+0x80/0x128 [ 21.287013] el0_svc_naked+0x30/0x34 [ 21.291835] Code: 17e7 a90363b7 a9046bb9 f9002bbb (d421) [ 21.299191] ---[ end trace b07cecc329f07f48 ]--- [ 21.347488] systemd: 35 output lines suppressed due to ratelimiting [ 21.355094] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [ 21.355094]
[Kernel-packages] [Bug 1855312] Re: Fix unusable USB hub on Dell TB16 after S3
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1855312 Title: Fix unusable USB hub on Dell TB16 after S3 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: Won't Fix Status in linux-oem-osp1 source package in Eoan: Won't Fix Bug description: [Impact] Sometimes USB hub on Dell TB16 stop working after S3. [Fix] Attempt to power cycle USB device when a it's stuck at eSS.Disabled state, it's basically not recoverable. [Test] After applying the patch, USB ports and USB ethernet are still working after 100 times S3 stress test. Tested on other platforms and didn't observe any regression. However, I have never seen any other USB device stuck in eSS.Disabled state, so the code path wasn't executed at all. [Regression Potential] Low. This is a last resort attempt, in most cases this code path won't be reached. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855312/+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 1730924] Re: Wifi does down "crash" in Surface Pro 4
** Bug watch added: github.com/jakeday/linux-surface/issues #456 https://github.com/jakeday/linux-surface/issues/456 -- 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/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730924/+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 1730924]
Created attachment 286651 attachment-16293-0.html As of 6-DEC-2019, NXP has acquired Marvell’s Wireless business unit. You can now reach me at ganapathi.b...@nxp.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/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730924/+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 1730924]
Hi Verdre, >>but the "cmd timeout" issue is definitely still happening you could share the dmesg + firmware dump; also, we find below discussions; could you give a try with the script below: https://github.com/jakeday/linux-surface/issues/456 Regards, Ganapathi -- 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/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730924/+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 1858658] Re: WARNING: CPU: 3 PID: 33 at /build/linux-raspi2-LrAkG8/linux-raspi2-4.15.0/drivers/spi/spidev.c:730 spidev_probe+0x13c/0x200
Probably due to: commit c5d736105ab2d84096e35ecc71a265345d66a25c Author: Trent Piepho Date: Thu Sep 20 19:18:34 2018 + spi: spidev: Fix OF tree warning logic BugLink: https://bugs.launchpad.net/bugs/1854216 [ Upstream commit 605b3bec73cbd74b4ac937b580cd0b47d1300484 ] spidev will make a big fuss if a device tree node binds a device by using "spidev" as the node's compatible property. However, the logic for this isn't looking for "spidev" in the compatible, but rather checking that the device is NOT compatible with spidev's list of devices. This causes a false positive if a device not named "rohm,dh2228fv", etc. binds to spidev, even if a means other than putting "spidev" in the device tree was used. E.g., the sysfs driver_override attribute. Signed-off-by: Trent Piepho Reviewed-by: Jan Kundrát Tested-by: Jan Kundrát Reviewed-by: Geert Uytterhoeven Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Khalid Elmously -- 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/1858658 Title: WARNING: CPU: 3 PID: 33 at /build/linux-raspi2-LrAkG8/linux- raspi2-4.15.0/drivers/spi/spidev.c:730 spidev_probe+0x13c/0x200 Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Bionic: New Bug description: After upgrading from 4.15.0-1052-raspi2 to 4.15.0-1053-raspi2: ubuntu@ubuntu:~$ cat /proc/device-tree/model Raspberry Pi 3 Model B Rev 1.2 [3.129125] [ cut here ] [3.222394] random: fast init done [4.894369] /soc/spi@7e204000/spidev@0: buggy DT: spidev listed directly in DT [4.904121] WARNING: CPU: 0 PID: 35 at /build/linux-raspi2-LrAkG8/linux-raspi2-4.15.0/drivers/spi/spidev.c:730 spidev_probe+0x13c/0x200 [4.918910] Modules linked in: aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [4.929200] CPU: 0 PID: 35 Comm: kworker/0:1 Tainted: GW 4.15.0-1053-raspi2 #57-Ubuntu [4.941032] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT) [4.949434] Workqueue: events deferred_probe_work_func [4.957132] pstate: 4045 (nZcv daif +PAN -UAO) [4.964468] pc : spidev_probe+0x13c/0x200 [4.971010] lr : spidev_probe+0x13c/0x200 [4.977517] sp : 0814b7a0 [4.983301] x29: 0814b7a0 x28: [4.991117] x27: x26: [4.998917] x25: 256606df7000 x24: 0005 [5.006697] x23: 256606cb8a38 x22: [5.014466] x21: x20: c79d73473000 [5.022247] x19: 256606cb8a18 x18: 0001 [5.030015] x17: 0001 x16: 0001 [5.037762] x15: 256606269000 x14: 0020 [5.045496] x13: x12: [5.053210] x11: 0001 x10: 256606c09c40 [5.060900] x9 : ff00 x8 : 256605c14968 [5.068561] x7 : c79d79563d60 x6 : 0104 [5.076159] x5 : x4 : [5.083790] x3 : x2 : 256606c2a308 [5.091391] x1 : f9b69bb55a180d00 x0 : [5.098999] Call trace: [5.103646] spidev_probe+0x13c/0x200 [5.109523] spi_drv_probe+0x80/0xd0 [5.115290] driver_probe_device+0x2fc/0x468 [5.121757] __device_attach_driver+0xa0/0x138 [5.128397] bus_for_each_drv+0x74/0xd8 [5.134398] __device_attach+0xe0/0x160 [5.140347] device_initial_probe+0x24/0x30 [5.146669] bus_probe_device+0x9c/0xa8 [5.152636] device_add+0x3fc/0x618 [5.158215] spi_add_device+0xfc/0x1a0 [5.164082] of_register_spi_device+0x1e4/0x368 [5.170747] spi_register_controller+0x1e0/0x738 [5.177497] devm_spi_register_controller+0x4c/0xa0 [5.184513] bcm2835_spi_probe+0x2a8/0x3d0 [5.190674] platform_drv_probe+0x60/0xc0 [5.196734] driver_probe_device+0x2fc/0x468 [5.203056] __device_attach_driver+0xa0/0x138 [5.209563] bus_for_each_drv+0x74/0xd8 [5.215459] __device_attach+0xe0/0x160 [5.221346] device_initial_probe+0x24/0x30 [5.227580] bus_probe_device+0x9c/0xa8 [5.233443] deferred_probe_work_func+0x60/0x180 [5.240101] process_one_work+0x1d8/0x490 [5.246140] worker_thread+0x248/0x478 [5.251897] kthread+0x134/0x138 [5.257051] ret_from_fork+0x10/0x1c [5.262549] ---[ end trace c44065d7c3da2ac2 ]--- [5.269391] usb 1-1: New USB device found, idVendor=0424, idProduct=9514 [5.269672] [ cut here ]
[Kernel-packages] [Bug 1848739] Re: [linux] Patch to prevent possible data corruption
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1848739
Title:
[linux] Patch to prevent possible data corruption
Status in linux package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Invalid
Status in linux-azure source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux-azure source package in Bionic:
Invalid
Bug description:
There are three patches that prevent possible data corruption. The
three commits are:
aef1897cd36d ("blk-mq: insert rq with DONTPREP to hctx dispatch list when
requeue")
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
923218f6166a ("blk-mq: don't allocate driver tag upfront for flush rq")
18.04 has all three of these patches. 16.04 has two out of the three,
but it is missing commit c616cbee97ae.
We would like to request commit c616cbee97ae be included in the 16.04 kernel:
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848739/+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 1855952] Re: scsi: hisi_sas: Check sas_port before using it
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855952 Title: scsi: hisi_sas: Check sas_port before using it Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-19.04 series: In Progress Status in kunpeng920 ubuntu-19.10 series: In Progress Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Fix Released 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 Status in linux source package in Focal: Fix Released Bug description: [Impact] Potential NULL-pointer dereference. [Test Case] No known test case, but the issue is clear from code reading. [Fix] 8c39673d5474b scsi: hisi_sas: Check sas_port before using it [Regression Risk] Patch restricted to hisi_sas driver. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1855952/+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 1858658] Re: WARNING: CPU: 3 PID: 33 at /build/linux-raspi2-LrAkG8/linux-raspi2-4.15.0/drivers/spi/spidev.c:730 spidev_probe+0x13c/0x200
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1858658/+attachment/5318234/+files/dmesg ** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1858658 Title: WARNING: CPU: 3 PID: 33 at /build/linux-raspi2-LrAkG8/linux- raspi2-4.15.0/drivers/spi/spidev.c:730 spidev_probe+0x13c/0x200 Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Bionic: New Bug description: After upgrading from 4.15.0-1052-raspi2 to 4.15.0-1053-raspi2: ubuntu@ubuntu:~$ cat /proc/device-tree/model Raspberry Pi 3 Model B Rev 1.2 [3.129125] [ cut here ] [3.222394] random: fast init done [4.894369] /soc/spi@7e204000/spidev@0: buggy DT: spidev listed directly in DT [4.904121] WARNING: CPU: 0 PID: 35 at /build/linux-raspi2-LrAkG8/linux-raspi2-4.15.0/drivers/spi/spidev.c:730 spidev_probe+0x13c/0x200 [4.918910] Modules linked in: aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [4.929200] CPU: 0 PID: 35 Comm: kworker/0:1 Tainted: GW 4.15.0-1053-raspi2 #57-Ubuntu [4.941032] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT) [4.949434] Workqueue: events deferred_probe_work_func [4.957132] pstate: 4045 (nZcv daif +PAN -UAO) [4.964468] pc : spidev_probe+0x13c/0x200 [4.971010] lr : spidev_probe+0x13c/0x200 [4.977517] sp : 0814b7a0 [4.983301] x29: 0814b7a0 x28: [4.991117] x27: x26: [4.998917] x25: 256606df7000 x24: 0005 [5.006697] x23: 256606cb8a38 x22: [5.014466] x21: x20: c79d73473000 [5.022247] x19: 256606cb8a18 x18: 0001 [5.030015] x17: 0001 x16: 0001 [5.037762] x15: 256606269000 x14: 0020 [5.045496] x13: x12: [5.053210] x11: 0001 x10: 256606c09c40 [5.060900] x9 : ff00 x8 : 256605c14968 [5.068561] x7 : c79d79563d60 x6 : 0104 [5.076159] x5 : x4 : [5.083790] x3 : x2 : 256606c2a308 [5.091391] x1 : f9b69bb55a180d00 x0 : [5.098999] Call trace: [5.103646] spidev_probe+0x13c/0x200 [5.109523] spi_drv_probe+0x80/0xd0 [5.115290] driver_probe_device+0x2fc/0x468 [5.121757] __device_attach_driver+0xa0/0x138 [5.128397] bus_for_each_drv+0x74/0xd8 [5.134398] __device_attach+0xe0/0x160 [5.140347] device_initial_probe+0x24/0x30 [5.146669] bus_probe_device+0x9c/0xa8 [5.152636] device_add+0x3fc/0x618 [5.158215] spi_add_device+0xfc/0x1a0 [5.164082] of_register_spi_device+0x1e4/0x368 [5.170747] spi_register_controller+0x1e0/0x738 [5.177497] devm_spi_register_controller+0x4c/0xa0 [5.184513] bcm2835_spi_probe+0x2a8/0x3d0 [5.190674] platform_drv_probe+0x60/0xc0 [5.196734] driver_probe_device+0x2fc/0x468 [5.203056] __device_attach_driver+0xa0/0x138 [5.209563] bus_for_each_drv+0x74/0xd8 [5.215459] __device_attach+0xe0/0x160 [5.221346] device_initial_probe+0x24/0x30 [5.227580] bus_probe_device+0x9c/0xa8 [5.233443] deferred_probe_work_func+0x60/0x180 [5.240101] process_one_work+0x1d8/0x490 [5.246140] worker_thread+0x248/0x478 [5.251897] kthread+0x134/0x138 [5.257051] ret_from_fork+0x10/0x1c [5.262549] ---[ end trace c44065d7c3da2ac2 ]--- [5.269391] usb 1-1: New USB device found, idVendor=0424, idProduct=9514 [5.269672] [ cut here ] [5.278071] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [5.284598] /soc/spi@7e204000/spidev@1: buggy DT: spidev listed directly in DT [5.294158] hub 1-1:1.0: USB hub found [5.303012] WARNING: CPU: 0 PID: 35 at /build/linux-raspi2-LrAkG8/linux-raspi2-4.15.0/drivers/spi/spidev.c:730 spidev_probe+0x13c/0x200 [5.308736] hub 1-1:1.0: 5 ports detected [5.322971] Modules linked in: aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [5.322991] CPU: 0 PID: 35 Comm: kworker/0:1 Tainted: GW 4.15.0-1053-raspi2 #57-Ubuntu [5.322995] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT) [5.357822] Workqueue: events deferred_probe_work_func [5.364924] pstate: 4045 (nZcv daif +PAN -UAO) [5.371672] pc : spidev_probe+0x13c/0x200 [5.377622] lr : spidev_probe+0x13c
[Kernel-packages] [Bug 1853997] Re: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853997 Title: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-19.04 series: In Progress Status in kunpeng920 ubuntu-19.10 series: In Progress Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released 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 Status in linux source package in Focal: Fix Released Bug description: [Impact] Some SAS devices is gone when recovering [Test Case] No known test case, stress test on SAS deivce. [Fix] e74006edd0d4 scsi: hisi_sas: Fix the conflict between device gone and host reset [Regression Risk] Patch restricted to hisi_sas driver. "[Steps to Reproduce] 1. Close all the PHYS; 2. Inject error; 3. Open one PHY; [Actual Results] Some disk will be lost [Expected Results] No disk will be lost [Reproducibility] occasionally [Additional information] Hardware: D06 CS Firmware: NA+I59 Kernel: NA [Resolution] When init device for SAS disks, it will send TMF IO to clear disks. At that time TMF IO is broken by some operations such as injecting controller reset from HW RAs event, the TMF IO will be timeout, and at last device will be gone. Print is as followed: hisi_sas_v3_hw :74:02.0: dev[240:1] found ... hisi_sas_v3_hw :74:02.0: controller resetting... hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11 hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11 hisi_sas_v3_hw :74:02.0: controller reset complete hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done hisi_sas_v3_hw :74:02.0: dev[240:1] is gone sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d, error:5 To improve the reliability, retry TMF IO max of 3 times for SAS disks which is the same as softreset does." scsi: hisi_sas: Fix the conflict between device gone and host reset To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853997/+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 1853995] Re: [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853995
Title:
[sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands
Status in kunpeng920:
In Progress
Status in kunpeng920 ubuntu-18.04 series:
In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
In Progress
Status in kunpeng920 ubuntu-19.04 series:
In Progress
Status in kunpeng920 ubuntu-19.10 series:
In Progress
Status in kunpeng920 ubuntu-20.04 series:
Fix Committed
Status in kunpeng920 upstream-kernel series:
Fix Released
Status in linux package in Ubuntu:
Fix Released
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
Status in linux source package in Focal:
Fix Released
Bug description:
[Impact]
I/O error on blank Samsung SSD
[Test Case]
mkfs.ext4 on SSDs generates no I/O error
[Fix]
435a05cf8c00 scsi: hisi_sas: Assign NCQ tag for all NCQ commands
[Regression Risk]
Patch restricted to hisi_sas driver.
"[Steps to Reproduce]
mkfs.ext4 to the special SAMSUNG M27LH960, and some IO error
[Actual Results]
Io error when the first time of mkfs.ext4
[ 745.809462] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=8
task=975f5cdf dev id=1 CQ hdr: 0x41d03 0x10008 0x1 0x446 Error
info: 0x0 0x0 0x1 0x0
[ 776.028794] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
[ 776.034612] sas: trying to find task 0x9656953a
[ 776.034613] sas: sas_scsi_find_task: aborting task 0x9656953a
[ 776.042785] sas: sas_scsi_find_task: task 0x9656953a is done
[ 776.042786] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
[ 776.049635] sas: trying to find task 0x975f5cdf
[ 776.049636] sas: sas_scsi_find_task: aborting task 0x975f5cdf
[ 776.056053] sas: sas_scsi_find_task: task 0x975f5cdf is done
[ 776.056054] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
[ 776.062900] sas: ata5: end_device-4:0: cmd error handler
[ 776.062914] sas: ata5: end_device-4:0: dev error handler
[ 776.062918] sas: ata6: end_device-4:1: dev error handler
[ 776.062920] ata5.00: exception Emask 0x0 SAct 0xc000 SErr 0x0 action
0x6 frozen
[ 776.062924] sas: ata7: end_device-4:2: dev error handler
[ 776.062926] sas: ata8: end_device-4:3: dev error handler
[ 776.070548] ata5.00: failed command: SEND FPDMA QUEUED
[ 776.075669] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 30 ncq
dma 512 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 776.090638] ata5.00: status: { DRDY }
[ 776.094290] ata5.00: failed command: SEND FPDMA QUEUED
[ 776.099410] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 31 ncq
dma 512 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 776.114399] ata5.00: status: { DRDY }
[ 776.118051] ata5: hard resetting link
[ 776.123198] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe
[ 776.129609] hisi_sas_v3_hw :74:02.0: ignore flutter phy0 down
[ 776.282642] hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=10(sata)
[ 776.289236] sas: sas_form_port: phy0 belongs to port0 already(1)!
[ 776.451784] ata5.00: configured for UDMA/133
[ 776.456043] ata5.00: device reported invalid CHS sector 0
[ 776.461423] ata5.00: device reported invalid CHS sector 0
[ 776.466807] ata5: EH complete
[ 776.469773] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 2 tries: 1
[ 776.498528] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=15
task=9656953a dev id=1 CQ hdr: 0x41d03 0x1000f 0x1 0x446 Error
info: 0x0 0x0 0x1 0x0
[ 806.740789] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
[ 806.746604] sas: trying to find task 0x975f5cdf
[ 806.746605] sas: sas_scsi_find_task: aborting task 0x975f5cdf
[ 806.754732] sas: sas_scsi_find_task: task 0x975f5cdf is done
[ 806.754733] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
[ 806.761582] sas: trying to find task 0x9656953a
[ 806.761584] sas: sas_scsi_find_task: aborting task 0x9656953a
[ 806.768002] sas: sas_scsi_find_task: task 0x9656953a is done
[ 806.768003] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
[ 806.774852] sas: ata5: end_device-4:0: cmd error handler
[ 806.774864] sas: ata5: end_device-4:0: dev error handler
[ 806.774868] sas: ata6: end_device-4:1: dev error handler
[ 806.774870] ata5.00: exception Emask 0x0 SAct 0x3
