[Kernel-packages] [Bug 1831940] Re: hibernation support for linux-aws
** Changed in: linux-aws (Ubuntu Disco) Status: New => 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/1831940 Title: hibernation support for linux-aws Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Xenial: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux-aws source package in Disco: Fix Committed Bug description: Additional AWS-specific and mainline patches are required to support hibernation across the various types of AWS instances. The following patch sets for linux-aws-xenial and linux-aws-bionic provide the necessary functionality, and should only impact the hibernation and resume paths. [linux-aws-xenial] UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. radix-tree: delete radix_tree_locate_item() mm: rid swapoff of quadratic complexity sched/wait: Fix abort_exclusive_wait(), it should pass TASK_NORMAL to wake_up() sched/wait: Avoid abort_exclusive_wait() in ___wait_event() sched/wait: Avoid abort_exclusive_wait() in __wait_on_bit_lock() sched/wait: Introduce init_wait_entry() sched/wait: Standardize wait_bit_queue naming sched/wait: Introduce wait_var_event() mm: swapoff: shmem_unuse() stop eviction without igrab() UBUNTU SAUCE [aws]: mm: aggressive swapoff UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled NVMe: Allow request merges PM / hibernate: Do not free preallocated safe pages during image restore PM / hibernate: Recycle safe pages after image restoration PM / hibernate: Simplify mark_unsafe_pages() UBUNTU: [Config] aws: disable CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS UBUNTU SAUCE [aws] PM / hibernate: set image_size to total RAM size by default UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing UBUNTU SAUCE [aws] mm, page_alloc: disable fair zone allocation policy on hibernate [linux-aws-bionic] UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. mm: rid swapoff of quadratic complexity sched/wait: Introduce wait_var_event() mm: swapoff: shmem_unuse() stop eviction without igrab() UBUNTU SAUCE [aws]: mm: aggressive swapoff netlink: Don't shift on 64 for ngroups [linux-aws-edge-bionic] UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake UBUNTU SAUCE [aws]: PM / hibernate: set image_size to 0 by default UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled UBUNTU SAUCE [aws]: mm: swap: improve swap readahead heuristic UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing PM / hibernate: memory_bm_find_bit(): Tighten node optimisation mm: rid swapoff of quadratic complexity mm: refactor swap-in logic out of shmem_getpage_gfp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1831940/+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 1858618] Re: linux-aws: swapoff optimization
** Changed in: linux-aws-5.0 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-aws (Ubuntu Disco) Status: New => 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/1858618 Title: linux-aws: swapoff optimization Status in linux-aws package in Ubuntu: New Status in linux-aws-5.0 package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-aws-5.0 source package in Bionic: Fix Committed Status in linux-aws source package in Disco: Fix Committed Status in linux-aws-5.0 source package in Disco: Invalid Bug description: [Impact] When an instance in the AWS EC2 infrastructure is successfully hibernated and resumed we want to deactivate the swap file as fast as possible in order to make the instance available again for the user. By default the kernel doesn't really optimize swapoff performance, it tries to keep the whole system still usable and responsive while swapoff is running. However, in our specific use case, swapoff needs to complete as fast as possible, so we may want to give swapoff I/O a higher priority and use different heuristics in order to optimize the I/O and page readahead generated by swapoff. [Test Case] Run the hibernation test on the AWS EC2 instances. [Fix] Apply a more aggressive swapin readahead policy that allows to improve swapoff performance. [Regression Potential] Minimal, this change is only affecting the swapoff-related code and it has been tested extensively with positive test results. The only downside is that this different heuristic makes the system more unresponsive during swapoff, but this is not a problem in the AWS scenario, because (by explicit requirement) the user shouldn't be able to use the instance during this swapoff phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1858618/+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 1863072] Re: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem - phase: Promote to Proposed - phase-changed: Thursday, 13. February 2020 10:16 UTC + phase: Testing + phase-changed: Friday, 14. February 2020 08:06 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff variant: debs -- 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/1863072 Title: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Friday, 14. February 2020 08:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863072/+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 1863072] Re: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress -- 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/1863072 Title: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Friday, 14. February 2020 08:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863072/+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 1862252] Re: focal/linux-gcp-5.4: 5.4.0-1001.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 -- kernel-stable-master-bug: 1862255 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 phase: Holding before Promote to Proposed phase-changed: Friday, 14. February 2020 04:11 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:building,signed:building + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait 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/1862252 Title: focal/linux-gcp-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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 -- kernel-stable-master-bug: 1862255 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 phase: Holding before Promote to Proposed phase-changed: Friday, 14. February 2020 04:11 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862252/+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 1863072] Re: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1863072 Title: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Friday, 14. February 2020 08:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863072/+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 1862865] Card0.Codecs.codec.2.txt
apport information
** Attachment added: "Card0.Codecs.codec.2.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328129/+files/Card0.Codecs.codec.2.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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
[Kernel-packages] [Bug 1862865] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328127/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2
[Kernel-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
apport information
** Tags added: apport-collected focal
** Description changed:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:15 dharkan kernel: [71070.591932] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:17 dharkan kernel: [71072.575930] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:19 dharkan kernel: [71074.591922] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:21 dharkan kernel: [71076.575911] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:23 dharkan kernel: [71078.591901] i915 :00:02.0: Resetting
rc
[Kernel-packages] [Bug 1862865] Card0.Codecs.codec.0.txt
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328128/+files/Card0.Codecs.codec.0.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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
[Kernel-packages] [Bug 1862865] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328131/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
[Kernel-packages] [Bug 1862865] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328133/+files/Lsusb-v.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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
|
[Kernel-packages] [Bug 1862865] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328132/+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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb
[Kernel-packages] [Bug 1862865] PciMultimedia.txt
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328134/+files/PciMultimedia.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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang
[Kernel-packages] [Bug 1862865] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328135/+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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on r
[Kernel-packages] [Bug 1862865] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328130/+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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on
[Kernel-packages] [Bug 1862865] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328137/+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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on r
[Kernel-packages] [Bug 1862865] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328136/+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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0
[Kernel-packages] [Bug 1862865] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328142/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => New
** Changed in: linux (Ubuntu Focal)
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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:0
[Kernel-packages] [Bug 1862865] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328140/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
[Kernel-packages] [Bug 1862865] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328139/+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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on r
[Kernel-packages] [Bug 1862865] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328138/+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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for han
[Kernel-packages] [Bug 1833905] Re: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels
Passed with: * 4.15 KVM * 5.3 KVM * 4.4 KVM with the fix to turn timesyncd off: https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/ubuntu_ltp_syscalls?id=2ee96043fde8ba46658f1ef89d10365bfd9457bb Thanks! ** Changed in: linux-kvm (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1833905 Title: settimeofday01 in ubuntu_ltp_syscalls failed on KVM kernels Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Invalid Bug description: Issue found on C-KVM, from the test case content, these two tests are: * Call settimeofday and verify the time was changed. * Call settimeofday with invalid Args and verify that the call fails. <<>> tag=settimeofday01 stime=1561358482 cmdline="settimeofday01" contacts="" analysis=exit <<>> settimeofday011 TFAIL : settimeofday01.c:124: Test condition 1 failed settimeofday012 TPASS : Test condition 2 successful <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1015-kvm 4.18.0-1015.15 ProcVersionSignature: User Name 4.18.0-1015.15-kvm 4.18.20 Uname: Linux 4.18.0-1015-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 Date: Mon Jun 24 06:41:26 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1833905/+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 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver
I am confused.
Patch ("mtd: spi-nor: Fix the writing of the Status Register on micron flashes")
fixes 39d1e3340c73 ("mtd: spi-nor: Fix clearing of QE bit on lock()/unlock()")
which depends on more patches if we want to cherry-pick them.
spi-nor provides 2 export functions but are not used in spi-hisi-sfc-
v3xx driver.
$ grep EXPORT drivers/mtd/spi-nor/spi-nor.c
EXPORT_SYMBOL_GPL(spi_nor_restore);
EXPORT_SYMBOL_GPL(spi_nor_scan);
I am building kernel with "spi: Add HiSilicon v3xx SPI NOR flash controller
driver"
only for test.
--
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/1860401
Title:
[sfc-0121]enable the HiSilicon v3xx SFC driver
Status in kunpeng920:
In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
In Progress
Status in kunpeng920 ubuntu-20.04 series:
In Progress
Status in kunpeng920 upstream-kernel series:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Bug description:
[Bug Description]
enable the HiSilicon v3xx SFC driver
[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 a maintainer for the HiSilicon v3xx SFC driver
spi: Add HiSilicon v3xx SPI NOR flash controller driver
mtd: spi-nor: Fix the writing of the Status Register on micron flashes
To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1860401/+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 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
| [Fri Feb 14 18:55:37 2020] i915 :00:02.0: GPU HANG: ecode 9:1:0x,
hang on rcs0
| [Fri Feb 14 18:55:37 2020] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
| [Fri Feb 14 18:55:37 2020] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
| [Fri Feb 14 18:55:37 2020] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
| [Fri Feb 14 18:55:37 2020] The GPU crash dump is required to analyze GPU
hangs, so please always attach it.
| [Fri Feb 14 18:55:37 2020] GPU crash dump saved to /sys/class/drm/card0/error
| [Fri Feb 14 18:55:37 2020] i915 :00:02.0: Resetting rcs0 for hang on rcs0
| [Fri Feb 14 18:55:45 2020] i915 :00:02.0: Resetting rcs0 for hang on rcs0
So included saved crash dump from /sys/class/drm/card0/error.
** Attachment added: "/sys/class/drm/card0/error"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1862865/+attachment/5328143/+files/drm-error.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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[435
[Kernel-packages] [Bug 1862865] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328141/+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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb
[Kernel-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
Also, I even tried disabling the power saving feature
(i915.enable_psr=0) but it still seems to lock up or hang.
--
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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:15 dharkan k
[Kernel-packages] [Bug 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver
Please test kernel debs at https://kernel.ubuntu.com/~ikepanhc/lp1860401.1/ If it works fine, I will submit patch "spi: Add HiSilicon v3xx SPI NOR flash controller driver". ** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => Incomplete ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Incomplete ** Changed in: kunpeng920 Status: In Progress => Incomplete ** Changed in: kunpeng920 Assignee: Ike Panhc (ikepanhc) => (unassigned) ** Changed in: kunpeng920/ubuntu-18.04-hwe Assignee: Ike Panhc (ikepanhc) => (unassigned) ** Changed in: kunpeng920/ubuntu-20.04 Assignee: Ike Panhc (ikepanhc) => (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/1860401 Title: [sfc-0121]enable the HiSilicon v3xx SFC driver Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] enable the HiSilicon v3xx SFC driver [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 a maintainer for the HiSilicon v3xx SFC driver spi: Add HiSilicon v3xx SPI NOR flash controller driver mtd: spi-nor: Fix the writing of the Status Register on micron flashes To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860401/+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 1862252] Re: focal/linux-gcp-5.4: 5.4.0-1001.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 -- kernel-stable-master-bug: 1862255 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 phase: Holding before Promote to Proposed phase-changed: Friday, 14. February 2020 04:11 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait 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/1862252 Title: focal/linux-gcp-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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 -- kernel-stable-master-bug: 1862255 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 phase: Holding before Promote to Proposed phase-changed: Friday, 14. February 2020 04:11 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862252/+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 1863222] [NEW] Please update to hwdata 0.332
Public bug reported: Please update hwdata to 0.332, and update the homepage and watch file to better track newer versions. https://github.com/vcrhonek/hwdata/releases ** Affects: hwdata (Ubuntu) Importance: Undecided Status: New ** Tags: focal upgrade-software-version -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1863222 Title: Please update to hwdata 0.332 Status in hwdata package in Ubuntu: New Bug description: Please update hwdata to 0.332, and update the homepage and watch file to better track newer versions. https://github.com/vcrhonek/hwdata/releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1863222/+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 1862806] Re: bionic/linux-aws-fips: 4.15.0-2009.9 -proposed tracker
4.15.0-2009.9 - aws-fips Regression test CMPL, RTB. Issue to note in x86_64 (aws): tsc - failed on c5.metal, i3.metal, r5.metal ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) apic-split (bug 1821390) vmx (bug 1821394) vmx_apic_passthrough_thread (bug 1822309) vmx_hlt_with_rvi_test (bug 1822308) vmx_apicv_test (bug 1827866) on i3.metal ubuntu_ltp - proc01 (bug 1829849) pty03 (bug 1862114) cpuset_hotplug (bug 1834006) memcg_usage_in_bytes (bug 1829984) memcg_stat (bug 1829983) memcg_usage_in_bytes (bug 1829984) memcg_use_hierarchy (bug 1829989) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) cve-2017-17053 failures caused by pty03 ubuntu_ltp_syscalls - msgstress03 (bug 1783881) Skipped / blacklisted: * libhugetlbfs Note: * ubuntu_ltp test must be reviewed on Jenkins directly, probably pty03 is causing this issue ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Tags added: regression-testing-passed -- 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/1862806 Title: bionic/linux-aws-fips: 4.15.0-2009.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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: 1862808 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Updates phase-changed: Friday, 14. February 2020 09:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862806/+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 1862806] Re: bionic/linux-aws-fips: 4.15.0-2009.9 -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: 1862808 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips - phase: Testing - phase-changed: Thursday, 13. February 2020 18:07 UTC + phase: Holding before Promote to Updates + phase-changed: Friday, 14. February 2020 09:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- cycle not ready to release 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/1862806 Title: bionic/linux-aws-fips: 4.15.0-2009.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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: 1862808 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Updates phase-changed: Friday, 14. February 2020 09:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862806/+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 1845677] Re: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen
** Also affects: linux (Ubuntu Focal) Importance: High Assignee: Hui Wang (hui.wang) Status: Confirmed ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-oem-osp1 (Ubuntu Eoan) Status: New => Invalid ** Changed in: linux-oem-osp1 (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845677 Title: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen Status in linux package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [Impact] There are 2 physical speakers on the X1 7th, and one is Bass speaker and connect to a DAC which doesn't have volume control on it. [Fix] adjust that speaker to connect to a DAC which has volume control capability. [Test Case] adjust the output volume from UI and play sound from speaker. [Regression Risk] Low, these change is specific to 2 lenovo machines. On my Lenovo ThinkPad X1 Carbon 7th generation using the built-in speakers, the volume is either off or on, there's no gradation in volume when I move the slider up or down. If I enable Over-Amplification than there's gradation in volume when I turn the volume up past 100%, but not for 0-100%. This problem does not occur with a headset plugged into the 3.5mm jack. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC0: jik3746 F pulseaudio  /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:07:44 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-5.3.0-12-generic N/A  linux-backports-modules-5.3.0-12-generic N/A  linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/+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 1861109] Re: xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Assignee: Jesse Sung (wenchien) => Shrirang Bagul (shrirang-bagul) ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Jesse Sung (wenchien) => Shrirang Bagul (shrirang-bagul) ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Jesse Sung (wenchien) => Shrirang Bagul (shrirang-bagul) -- 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/1861109 Title: xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid 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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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 -- kernel-stable-master-bug: 1861122 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Packaging phase-changed: Wednesday, 05. February 2020 08:01 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: xenial/linux-cascade/cascade-kernel: bug 1861108 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861109/+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 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver
thank you! I will test it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860401 Title: [sfc-0121]enable the HiSilicon v3xx SFC driver Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] enable the HiSilicon v3xx SFC driver [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 a maintainer for the HiSilicon v3xx SFC driver spi: Add HiSilicon v3xx SPI NOR flash controller driver mtd: spi-nor: Fix the writing of the Status Register on micron flashes To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1860401/+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 1861976] Re: [acc-0205]sync mainline kernel 5.5rc6 acc patchset into ubuntu HWE kernel branch
** Summary changed: - [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch + [acc-0205]sync mainline kernel 5.5rc6 acc patchset into ubuntu HWE kernel branch -- 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/1861976 Title: [acc-0205]sync mainline kernel 5.5rc6 acc patchset into ubuntu HWE kernel branch Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] acc patchset have merged into mainline 5.5rc6 kernel. [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 - fix spelling mistake "disgest" -> "digest" crypto: hisilicon - add branch prediction macro crypto: hisilicon - adjust hpre_crt_para_get crypto: hisilicon - Fixed some tiny bugs of HPRE crypto: hisilicon - Bugfixed tfm leak crypto: hisilicon - Add aead support on SEC2 crypto: hisilicon - redefine skcipher initiation crypto: hisilicon - Add branch prediction macro crypto: hisilicon - Add callback error check crypto: hisilicon - Adjust some inner logic crypto: hisilicon - Update QP resources of SEC V2 crypto: hisilicon - Update some names on SEC V2 crypto: hisilicon - fix print/comment of SEC V2 crypto: hisilicon - Update debugfs usage of SEC V2 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1861976/+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 1774815] Re: Add bpftool to linux-tools-common
** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1774815 Title: Add bpftool to linux-tools-common Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Bug description: bpftool is a debugging and introspection tool actively developed by the BPF kernel community. It's developed as part of the kernel source tree under tools/: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/bpf/bpftool It would be really great and appreciated if Ubuntu folks could package this as part of linux-tools-common. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774815/+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 1861238] Re: Root can lift kernel lockdown via USB/IP
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1861238 Title: Root can lift kernel lockdown via USB/IP Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Invalid 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: In Progress Bug description: [Impact] It's possible to turn off kernel lockdown by emulating a USB keyboard via USB/IP and sending an Alt+SysRq+X key combination through it. Ubuntu's kernels have USB/IP enabled (CONFIG_USBIP_VHCI_HCD=m and CONFIG_USBIP_CORE=m) with signed usbip_core and vhci_hcd modules provided in the linux-extra-modules-* package. See the PoC here: https://github.com/xairy/unlockdown#method-1-usbip [Test Case] $ git clone https://github.com/xairy/unlockdown.git $ cd unlockdown/01-usbip/ $ sudo ./run.sh $ dmesg # Ensure there are no log entries talking about lifting lockdown: sysrq: SysRq : Disabling Secure Boot restrictions Lifting lockdown # You should see a SysRq help log entry because the Alt+SysRq+X # combination should be disabled sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) dump-ftrace-buffer(z) [Regression Potential] Some users may see a usability regression due to the Lockdown lift sysrq combination being removed. Some users are known to disable lockdown, using the sysrq combination, in order to perform some "dangerous" operation such as writing to an MSR. It is believed that this is a small number of users but it is impossible to know for sure. Users that rely on this functionality may need to permanently disable secure boot using 'mokutil --disable-validation'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861238/+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 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit
I can not find "treewide: Use sizeof_member() macro but found a similiar. Do you mean this patch? commit c593642c8be046915ca3a4a300243a68077cd207 Author: Pankaj Bharadiya Date: Mon Dec 9 10:31:43 2019 -0800 treewide: Use sizeof_field() macro Replace all the occurrences of FIELD_SIZEOF() with sizeof_field() except at places where these are defined. Later patches will remove the unused definition of FIELD_SIZEOF(). you can ignore this patchset -- 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/1859261 Title: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe 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 Committed Bug description: [Bug Description]  hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce]   1)   2)   3) [Actual Results] [Expected Results] [Reproducibility] [Additional information]   (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: support tx-scatter-gather-fraglist feature net: hns3: add support for configuring VF MAC from the host net: hns3: add support for configuring bandwidth of VF on the host net: hns3: add support for setting VF trust net: hns3: add support for spoof check setting net: hns3: add support for setting VF link status on the host net: hns3: make array tick_array static, makes object smaller net: hns3: fix a wrong reset interrupt status mask net: hns3: cleanup of stray struct hns3_link_mode_mapping net: hns3: fix ETS bandwidth validation bug net: hns3: reallocate SSU' buffer size when pfc_en changes net: hns3: add compatible handling for MAC VLAN switch parameter configuration net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE net: hns3: remove unused macros net: hns3: Use the correct style for SPDX License Identifier net: hns3: cleanup byte order issues when printed net: hns3: cleanup some print format warning net: hns3: add or modify some comments net: hns3: optimize local variable initialization net: hns3: cleanup a format-truncation warning net: hns3: cleanup some coding style issues net: hns3: cleanup some magic numbers net: hns3: add struct netdev_queue debug info for TX timeout net: hns3: dump some debug information when reset fail treewide: Use sizeof_member() macro net: hns3: log and clear hardware error after reset complete net: hns3: do not allocate linear data for fraglist skb net: hns3: minor cleanup for hns3_handle_rx_bd() net: hns3: make struct hns3_enet_ring cacheline aligned net: hns3: introduce ring_to_netdev() in enet module net: hns3: minor optimization for barrier in IO path net: hns3: optimized MAC address in management table. net: hns3: remove struct hns3_nic_ring_data in hns3_enet module net: hns3: fix mis-counting IRQ vector numbers issue   net: hns3: fix VF ID issue for setting VF VLAN net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() net: hns3: fix for TX queue not restarted problem  net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure in hns3_nic_uninit_vector_data() net: hns3: add some VF VLAN information for command "ip link show" net: hns3: implement ndo_features_check ops for hns3 driver net: hns3: get FD rules location before dump in debugfs net: hns3: optimization for CMDQ uninitialization net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev net: hns3: check FE bit before calling hns3_add_frag() net: hns3: do not schedule the periodic task when reset fail net: hns3: allocate WQ with WQ_MEM_RECLAIM flag net: hns3: remove unnecessary work in hclgevf_main net: hns3: remove mailbox and reset work in hclge_main net: hns3: schedule hclgevf_service by using delayed workqueue net: hns3: refactor the notification scheme of PF reset net: hns3: refactor the procedure of VF FLR net: hns3: modify hclge_func_reset_sync_vf()'s return type to void net: hns3: enlarge HCLGE_RESET_WAIT_CNT net: hns3: refactor the precedure of PF FLR net: hns3: split hclgevf_reset() into preparing and rebuilding part net: hns3: split hclge_reset() into preparing and rebuilding part net: hns3: modify an unsuitable reset level for hardware error net: hns3: replace an unsuitable variable type in hclge_inform_reset_assert_to_vf() net: hns3: add protection when get SFP speed as 0 net: hns3: modify the IRQ name of misc vectors net: hns3: modify an unsuitable log in hclge_map_ring_to_vector() net: hns3: modify the IRQ name of TQP vec
[Kernel-packages] [Bug 1862252] Re: focal/linux-gcp-5.4: 5.4.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-focal ** Tags added: 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: 1862255 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 - phase: Holding before Promote to Proposed - phase-changed: Friday, 14. February 2020 04:11 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 14. February 2020 10:46 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait + promote-to-proposed: Pending -- ready for review 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/1862252 Title: focal/linux-gcp-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: 1862255 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 phase: Ready for Promote to Proposed phase-changed: Friday, 14. February 2020 10:46 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Expired ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: Expired => In Progress ** Changed in: linux (Ubuntu Eoan) Status: New => Fix Committed ** Changed in: linux (Ubuntu Disco) 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/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in linux package in Ubuntu: In Progress 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: In Progress Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859407] Re: peripheral devices on Dell WD19TB cannot be detected after suspend resume
** 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/1859407
Title:
peripheral devices on Dell WD19TB cannot be detected after suspend
resume
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-osp1 package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Won't Fix
Status in linux-oem-osp1 source package in Bionic:
Fix Committed
Status in linux 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-osp1 source package in Eoan:
New
Bug description:
[SRU Justification]
[Impact]
If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell
WD19TB into the laptop during suspend state, peripheral devices on the
docking station cannot be re-probed after the system resumes.
[Fix]
Upstream commit 56b991849009f ("PM: sleep: Simplify suspend-to-idle control
flow") along with its dependencies are required to fix this issue:
* 56b991849009f PM: sleep: Simplify suspend-to-idle control flow
* 41275eb5c7181 ACPI: PM: Set s2idle_wakeup earlier and clear it later
* 9089f16e053af ACPI: EC: Return bool from acpi_ec_dispatch_gpe()
* 6921de898ba8f ACPICA: Return u32 from acpi_dispatch_gpe()
* 3a79bc63d9075 PCI: irq: Introduce rearm_wake_irq()
And 56b991849009f takes an additional fix as we've done for bug
1858424:
* 016b87ca5c8c6 ACPI: EC: Rework flushing of pending work
[Test Case]
1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop
2. Suspend the system
3. Un-plug the TBT 3 cable of WD19 docking station from laptop
4. Re-plug the TBT 3 cable of WD19 docking station into the laptop
5. Press the Enter key or power button to wake up the system
6. Connect an Ethernet cable to a Ethernet port of WD19 docking station
7. Check if the Ethernet interface is available and networking connection is
up.
[Regression Potential]
Medium. The first four patches should not affect original functionalities. The
last two mostly simplify the process and resolve a regression.
== original bug description ==
[Summary]
If user un-plugs and then re-plugs the thunderbolt 3 cable of Dell WD19TB
into the laptop during suspend state, peripheral devices on the docking station
cannot be re-probed after the system resumes.
[Steps to reproduce]
1. Please make sure that the WD19 (TBT 3 cable) connects to the laptop
2. Suspend the system
3. Un-plug the TBT 3 cable of WD19 docking station from laptop
4. Re-plug the TBT 3 cable of WD19 docking station into the laptop
5. Press the Enter key or power button to wake up the system
6. Connect an Ethernet cable to a Ethernet port of WD19 docking station
7. Check if the Ethernet interface is available and networking connection is
up.
[Expected result]
The Ethernet interface can be detected
[Actual result]
The Ethernet cannot be detected
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1859407/+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 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit
net: hns3: refactor the notification scheme of PF reset net: hns3: refactor the procedure of VF FLR net: hns3: modify hclge_func_reset_sync_vf()'s return type to void net: hns3: enlarge HCLGE_RESET_WAIT_CNT net: hns3: refactor the precedure of PF FLR net: hns3: split hclgevf_reset() into preparing and rebuilding part net: hns3: schedule hclgevf_service by using delayed workqueue net: hns3: modify an unsuitable reset level for hardware error net: hns3: replace an unsuitable variable type in hclge_inform_reset_assert_to_vf() net: hns3: add protection when get SFP speed as 0 net: hns3: modify the IRQ name of misc vectors net: hns3: modify an unsuitable log in hclge_map_ring_to_vector() net: hns3: modify the IRQ name of TQP vector net: hns3: re-organize vector handle net: hns3: add trace event support for HNS3 driver net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure in hns3_nic_uninit_vector_data() net: hns3: add some VF VLAN information for command "ip link show" net: hns3: implement ndo_features_check ops for hns3 driver net: hns3: get FD rules location before dump in debugfs net: hns3: optimization for CMDQ uninitialization net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev net: hns3: check FE bit before calling hns3_add_frag() net: hns3: do not schedule the periodic task when reset fail net: hns3: allocate WQ with WQ_MEM_RECLAIM flag net: hns3: remove unnecessary work in hclgevf_main net: hns3: remove mailbox and reset work in hclge_main net: hns3: schedule hclgevf_service by using delayed workqueue pls ensuring this aboving patchset will merge into ubuntu 20.04 kernel verison. thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859261 Title: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe 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 Committed Bug description: [Bug Description]  hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 18.04.5 kernel version [Steps to Reproduce]   1)   2)   3) [Actual Results] [Expected Results] [Reproducibility] [Additional information]   (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: support tx-scatter-gather-fraglist feature net: hns3: add support for configuring VF MAC from the host net: hns3: add support for configuring bandwidth of VF on the host net: hns3: add support for setting VF trust net: hns3: add support for spoof check setting net: hns3: add support for setting VF link status on the host net: hns3: make array tick_array static, makes object smaller net: hns3: fix a wrong reset interrupt status mask net: hns3: cleanup of stray struct hns3_link_mode_mapping net: hns3: fix ETS bandwidth validation bug net: hns3: reallocate SSU' buffer size when pfc_en changes net: hns3: add compatible handling for MAC VLAN switch parameter configuration net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE net: hns3: remove unused macros net: hns3: Use the correct style for SPDX License Identifier net: hns3: cleanup byte order issues when printed net: hns3: cleanup some print format warning net: hns3: add or modify some comments net: hns3: optimize local variable initialization net: hns3: cleanup a format-truncation warning net: hns3: cleanup some coding style issues net: hns3: cleanup some magic numbers net: hns3: add struct netdev_queue debug info for TX timeout net: hns3: dump some debug information when reset fail treewide: Use sizeof_member() macro net: hns3: log and clear hardware error after reset complete net: hns3: do not allocate linear data for fraglist skb net: hns3: minor cleanup for hns3_handle_rx_bd() net: hns3: make struct hns3_enet_ring cacheline aligned net: hns3: introduce ring_to_netdev() in enet module net: hns3: minor optimization for barrier in IO path net: hns3: optimized MAC address in management table. net: hns3: remove struct hns3_nic_ring_data in hns3_enet module net: hns3: fix mis-counting IRQ vector numbers issue   net: hns3: fix VF ID issue for setting VF VLAN net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() net: hns3: fix for TX queue not restarted problem  net: hns3: only print misc interrupt status when handling fails net: hns3: add a log for getting chain failure i
[Kernel-packages] [Bug 1863234] [NEW] Disabling bpf() syscall on kernel lockdown break apps when secure boot is on
Public bug reported: In disco and eoan, lockdown is automatically enforced when secure boot is on [0]. Because lockdown was not in the mailine kernel at the time, some disto-specific patches were added to the kernel, including one that drastically restricts BPF usage by completely disabling the use of the `bpf()` system call when lockdown is on [1]. A consequence of that decision is that no application relying on eBPF can run on 19.04/19.10, unless secure boot / lockdown is disabled. For example, Cilium (cilium.io) strongly relies on BPF programs to implement its datapath and securing network connectivity between containers. Other applications like Suricata or Sysdig also rely on BPF to some extent. None of which will work by default on a EFI machine with secure boot activated. If I understand correctly, kernel 5.4 (to be used in focal) will have a different, lighter restricton (comming from mainline Linux kernel) [2], so `bpf()` for networking use cases should mostly work on 20.04. Is my understanding correct? If so, could this patch be backported to 19.10 (and 19.04, if still supported) instead of completely disabling the syscall on lockdown? Links: [0] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=d0db99473fc3bb8a5d03f99ed454ac7ca5e7d517 [1] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=2a68c65abae66d28e2acb3245cb156ae2ea6eb1d [2] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?id=9d1f8be5cf42b497a3bddf1d523f2bb142e9318c ** 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/1863234 Title: Disabling bpf() syscall on kernel lockdown break apps when secure boot is on Status in linux package in Ubuntu: New Bug description: In disco and eoan, lockdown is automatically enforced when secure boot is on [0]. Because lockdown was not in the mailine kernel at the time, some disto-specific patches were added to the kernel, including one that drastically restricts BPF usage by completely disabling the use of the `bpf()` system call when lockdown is on [1]. A consequence of that decision is that no application relying on eBPF can run on 19.04/19.10, unless secure boot / lockdown is disabled. For example, Cilium (cilium.io) strongly relies on BPF programs to implement its datapath and securing network connectivity between containers. Other applications like Suricata or Sysdig also rely on BPF to some extent. None of which will work by default on a EFI machine with secure boot activated. If I understand correctly, kernel 5.4 (to be used in focal) will have a different, lighter restricton (comming from mainline Linux kernel) [2], so `bpf()` for networking use cases should mostly work on 20.04. Is my understanding correct? If so, could this patch be backported to 19.10 (and 19.04, if still supported) instead of completely disabling the syscall on lockdown? Links: [0] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=d0db99473fc3bb8a5d03f99ed454ac7ca5e7d517 [1] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=2a68c65abae66d28e2acb3245cb156ae2ea6eb1d [2] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?id=9d1f8be5cf42b497a3bddf1d523f2bb142e9318c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863234/+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 1863234] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1863234 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863234 Title: Disabling bpf() syscall on kernel lockdown break apps when secure boot is on Status in linux package in Ubuntu: Incomplete Bug description: In disco and eoan, lockdown is automatically enforced when secure boot is on [0]. Because lockdown was not in the mailine kernel at the time, some disto-specific patches were added to the kernel, including one that drastically restricts BPF usage by completely disabling the use of the `bpf()` system call when lockdown is on [1]. A consequence of that decision is that no application relying on eBPF can run on 19.04/19.10, unless secure boot / lockdown is disabled. For example, Cilium (cilium.io) strongly relies on BPF programs to implement its datapath and securing network connectivity between containers. Other applications like Suricata or Sysdig also rely on BPF to some extent. None of which will work by default on a EFI machine with secure boot activated. If I understand correctly, kernel 5.4 (to be used in focal) will have a different, lighter restricton (comming from mainline Linux kernel) [2], so `bpf()` for networking use cases should mostly work on 20.04. Is my understanding correct? If so, could this patch be backported to 19.10 (and 19.04, if still supported) instead of completely disabling the syscall on lockdown? Links: [0] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=d0db99473fc3bb8a5d03f99ed454ac7ca5e7d517 [1] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=2a68c65abae66d28e2acb3245cb156ae2ea6eb1d [2] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?id=9d1f8be5cf42b497a3bddf1d523f2bb142e9318c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863234/+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 1862808] Re: bionic/linux-aws: 4.15.0-1060.62 -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: 1862824 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Thursday, 13. February 2020 18:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-aws-fips: bug 1862806 bionic/linux-aws/aws-kernel: bug 1862805 xenial/linux-aws-hwe: bug 1862807 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1862808 Title: bionic/linux-aws: 4.15.0-1060.62 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1862824 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Thursday, 13. February 2020 18:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-aws-fips: bug 1862806 bionic/linux-aws/aws-kernel: bug 1862805 xenial/linux-aws-hwe: bug 1862807 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862808/+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 1862824] Re: bionic/linux: 4.15.0-88.88 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 12. February 2020 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-aws: bug 1862808 bionic/linux-fips: bug 1861152 bionic/linux-gke-4.15: bug 1862810 bionic/linux-ibm-gt: bug 1862812 bionic/linux-kvm: bug 1862811 bionic/linux-oem: bug 1863072 bionic/linux-oracle: bug 1862814 bionic/linux-raspi2: bug 1861134 bionic/linux-snapdragon: bug 1861136 bionic/linux/pc-kernel: bug 1862803 bionic/linux/pc-lowlatency-kernel: bug 1862804 xenial/linux-azure: bug 1862818 xenial/linux-gcp: bug 1862821 xenial/linux-hwe: bug 1862823 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/1862824 Title: bionic/linux: 4.15.0-88.88 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 12. February 2020 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff trackers: bionic/linux-aws: bug 1862808 bionic/linux-fips: bug 1861152 bionic/linux-gke-4.15: bug 1862810 bionic/linux-ibm-gt: bug 1862812 bionic/linux-kvm: bug 1862811 bionic/linux-oem: bug 1863072 bionic/linux-oracle: bug 1862814 bionic/linux-raspi2: bug 1861134 bionic/linux-snapdragon: bug 1861136 bionic/linux/pc-kernel: bug 1862803 bionic/linux/pc-lowlatency-kernel: bug 1862804 xenial/linux-azure: bug 1862818 xenial/linux-gcp: bug 1862821 xenial/linux-hwe: bug 1862823 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862824/+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 1862811] Re: bionic/linux-kvm: 4.15.0-1053.53 -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: 1862824 packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Thursday, 13. February 2020 18:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1862811 Title: bionic/linux-kvm: 4.15.0-1053.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1862824 packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Thursday, 13. February 2020 18:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862811/+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 1860969] Re: ipsec interfaces: fix sending with bpf_redirect() / AF_PACKET sockets
** 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/1860969
Title:
ipsec interfaces: fix sending with bpf_redirect() / AF_PACKET sockets
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
Packets sent to a vti[6]/xfrm interface via bpf_redirect() or via an
AF_PACKET socket are dropped (no carrier).
This has been fixed in v5.5 by the following upstream commits
 - 95224166a903 ("vti[6]: fix packet tx through bpf_redirect()")
 - f042365dbffe ("xfrm interface: fix packet tx through bpf_redirect()")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=95224166a903
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f042365dbffe
The bug exists since the beginning of each driver.
== Fix ==
Backport the requested patches to Focal (5.4), Eoan (5.3), Bionic (4.15) and
Xenial (4.4).
== Risk of Regression ==
This patch affects only the cases described above (when no dst is
attached to the skb), thus the risk should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860969/+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 1858988] Re: USB key cannot be detected by hotplug on Sunix USB Type-A 3.1 Gen 2 card [1b21:2142]
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Fix Committed ** Also affects: linux-oem-osp1 (Ubuntu Focal) Importance: Undecided Status: Fix Released ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Eoan) 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/1858988 Title: USB key cannot be detected by hotplug on Sunix USB Type-A 3.1 Gen 2 card [1b21:2142] Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: Fix Released Bug description: [Impact] Hotplug USB key to Sunix USB Type-A 3.1 Gen 2 card can't be detected [Fix] ASMedia XHCI USB controller PME# doesn't work under D0, so remove its cap by quirk. [Test] Verified on the target machine, USB 3 storage works. [Regression Potential] Low, it only affects target chip. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858988/+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 1863234] Re: Disabling bpf() syscall on kernel lockdown break apps when secure boot is on
Not adding kernel logs but changing to 'Confirmed'. ** 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/1863234 Title: Disabling bpf() syscall on kernel lockdown break apps when secure boot is on Status in linux package in Ubuntu: Confirmed Bug description: In disco and eoan, lockdown is automatically enforced when secure boot is on [0]. Because lockdown was not in the mailine kernel at the time, some disto-specific patches were added to the kernel, including one that drastically restricts BPF usage by completely disabling the use of the `bpf()` system call when lockdown is on [1]. A consequence of that decision is that no application relying on eBPF can run on 19.04/19.10, unless secure boot / lockdown is disabled. For example, Cilium (cilium.io) strongly relies on BPF programs to implement its datapath and securing network connectivity between containers. Other applications like Suricata or Sysdig also rely on BPF to some extent. None of which will work by default on a EFI machine with secure boot activated. If I understand correctly, kernel 5.4 (to be used in focal) will have a different, lighter restricton (comming from mainline Linux kernel) [2], so `bpf()` for networking use cases should mostly work on 20.04. Is my understanding correct? If so, could this patch be backported to 19.10 (and 19.04, if still supported) instead of completely disabling the syscall on lockdown? Links: [0] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=d0db99473fc3bb8a5d03f99ed454ac7ca5e7d517 [1] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=2a68c65abae66d28e2acb3245cb156ae2ea6eb1d [2] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?id=9d1f8be5cf42b497a3bddf1d523f2bb142e9318c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863234/+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 1863245] [NEW] Disable CONFIG_MODVERSIONS
Public bug reported: [Impact] Having CONFIG_MODVERSIONS enabled means that modules compiled for a different kernel can potentially be loaded. We don't really want that. In addition, all the master kernels since Zesty have it turned off, plus all their derivatives as well, expect for the few that are listed as affected in this bug report. [Test Case] $ grep CONFIG_MODVERSIONS /boot/config-$(uname -r): CONFIG_MODVERSIONS=y [Regression Potential] Low. This only prevents loading of modules compiled for a different kernel. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi2-5.3 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi2-5.4 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi2-5.3 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: linux-raspi2-5.4 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-raspi2-5.3 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-raspi2-5.3 (Ubuntu Eoan) ** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-raspi2-5.3 (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux-raspi2 (Ubuntu Bionic) ** Also affects: linux-raspi2-5.4 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-raspi2-5.3 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-raspi2-5.4 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux-raspi2 (Ubuntu Focal) ** No longer affects: linux-raspi2-5.3 (Ubuntu Focal) -- 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/1863245 Title: Disable CONFIG_MODVERSIONS Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2-5.3 package in Ubuntu: New Status in linux-raspi2-5.4 package in Ubuntu: New Status in linux-raspi2-5.3 source package in Bionic: New Status in linux-raspi2 source package in Eoan: New Status in linux-raspi2-5.4 source package in Focal: New Bug description: [Impact] Having CONFIG_MODVERSIONS enabled means that modules compiled for a different kernel can potentially be loaded. We don't really want that. In addition, all the master kernels since Zesty have it turned off, plus all their derivatives as well, expect for the few that are listed as affected in this bug report. [Test Case] $ grep CONFIG_MODVERSIONS /boot/config-$(uname -r): CONFIG_MODVERSIONS=y [Regression Potential] Low. This only prevents loading of modules compiled for a different kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1863245/+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 1858988] Re: USB key cannot be detected by hotplug on Sunix USB Type-A 3.1 Gen 2 card [1b21:2142]
** 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/1858988 Title: USB key cannot be detected by hotplug on Sunix USB Type-A 3.1 Gen 2 card [1b21:2142] Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed 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: New Status in linux source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: Fix Released Bug description: [Impact] Hotplug USB key to Sunix USB Type-A 3.1 Gen 2 card can't be detected [Fix] ASMedia XHCI USB controller PME# doesn't work under D0, so remove its cap by quirk. [Test] Verified on the target machine, USB 3 storage works. [Regression Potential] Low, it only affects target chip. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858988/+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 1863248] [NEW] Intel display driver cannot read EDID from VGA monitor
Public bug reported: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 ** 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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: New Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%)
[Kernel-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Edwin, Do you happen to notice any IPv6 or LLDP or other link-local traffic on the interfaces? (including backup interface). The MTR loss % is purely a capture of their packets xmitted and responses received, so for that UDP MTR test, this is saying that UDP packets were lost, somewhere. The NIC does not have any drops showing via ethtool -S stats but I'm hunting down which are the right pair of before/afters. Other than the tpa_abort counts, there were no errors that I saw. I can't tell what the tpa_abort means for the frame - is it purely a failure only to coalesce, or does it end up dropping packets at some point in that functionality? I'm assuming not, as whatever the reason, those would be counted as drops, I hope, and printed in the interface stats. I'll attach all the stats here once I get them sorted out, I thought I had a clean diff of before and after from the tester, but after looking through, I don't think the file I have is from before/after the mtr test, as there was negligible UDP traffic. I'll try and get clarification from the reporter. Note that when the provision of primary= is used to configure which interface is primary, and when the primary port is used as the active interface for the bond, no problems are seen (and that works deterministically to set the correct active interface). -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected
[Kernel-packages] [Bug 1862567] Re: [SRU][B/OEM-B] Fix multitouch support on some devices
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862567 Title: [SRU][B/OEM-B] Fix multitouch support on some devices Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Bug description: [Impact] Some LG touchscreens reported themselves as generic touch devices, actually it is multitouch devices. Even after adding IDs in hid-multitouch, hid-generic will bind the device still. multitouch features are not supported. [Fix] commit e04a0442 make hid-generic work nicely with other drivers like hid-multitouch. If other drivers match the devices, hid-generic will step back. This patch will benefit many devices to support their own drivers without adding IDs. [Test] Verified on LG/ELAN/RAYDIUM touchscreens with positive results. [Regression Potential] Medium. commit e04a0442 is included by 4.16 kernel, only bionic kernel should be applied. This commit is based on the other 3 patches, mostly changes are moving codes to hid-quirk.c. Backports are during to the other backports patches, these changes are moved to hid-quirk.c too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862567/+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 1837828] Re: alsa/sof: let legacy hda driver and sof driver co-exist
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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) Status: New => Fix Released ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** 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/1837828 Title: alsa/sof: let legacy hda driver and sof driver co-exist Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] So far, if we want the sof driver to work, we need to blacklist snd_hda_intel.ko, but on some paltforms with nv hdmi or amd hdmi, we need these two driver co-exist. [Fix] Intel sent the patches to fix this issue, although it is not merged yet, but I guess they will pass the review and be merged. So i backported them first. [Test Case] remove snd_hda_intel.ko from blacklist, the two drivers (sof and hda) worked well. [Regression Risk] Low. We already tested these patches on some Dell machines. and comunity including endlessm and goole all tested these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837828/+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 1859126] Re: Reduce s2idle power consumption when ethernet cable is connected on e1000e
** 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/1859126 Title: Reduce s2idle power consumption when ethernet cable is connected on e1000e Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix 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: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] When ethernet cable is connected, power consumption is quite high under suspend-to-idle. [Fix] Enable s0ix support for e1000e. [Test] When ethernet cable is connected, the power consumption is ~2.5w. After applying the patch, it can be lowered to ~1.8w. [Regression Potential] Low. This fix is limited to fairly recent I219 hardwares. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859126/+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 1863248] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1863248 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter
Hi Daniel, hope you're doing well! Thanks for reporting this regression. I worked a bit with qla2xxx back in IBM LTC, so I can try to help. There are indeed a few 'stable' fixes for qla2xxx between 4.15.0-72 and -73 (none on -74). Well, apparently not so stable. And none of their upstream commit IDs are marked in Fixes commits on mainline, sadly; so no immediate indicators of the culprit. There are more fixes in Ubuntu-4.15.0-88.88 (yes) currently in bionic-proposed. And a few more fixes in master-next (just in git, not yet released.) So, 1) Could you please try the kernel packages from bionic-proposed first ? 2) And if doesn't help, build the packages from master-next ? (or I can give you test packages) Hopefully either may help. Otherwise, we can check more recent kernel versions. Thanks, Mauricio $ git log --oneline Ubuntu-4.15.0-72.81..Ubuntu-4.15.0-73.82 -- drivers/scsi/qla2xxx/ 8fe9110fefd8 scsi: qla2xxx: Fix port speed display on chip reset 0b693aca8824 scsi: qla2xxx: Fix deadlock between ATIO and HW lock 51313cd70fe2 scsi: qla2xxx: Terminate Plogi/PRLI if WWN is 0 18dd3502aa79 scsi: qla2xxx: Fix dropped srb resource. 4af79e867720 scsi: qla2xxx: Defer chip reset until target mode is enabled c41bc5e5c6bb scsi: qla2xxx: Fix iIDMA error c0579128d7b8 scsi: qla2xxx: stop timer in shutdown path 3bf89d9345a5 scsi: qla2xxx: Initialized mailbox to prevent driver load failure 725ec645a843 scsi: qla2xxx: fixup incorrect usage of host_byte 7616c2489f28 scsi: qla2xxx: fix a potential NULL pointer dereference $ git log --oneline Ubuntu-4.15.0-73.82..Ubuntu-4.15.0-74.84 -- drivers/scsi/qla2xxx/ $ $ git log --oneline Ubuntu-4.15.0-73.82..Ubuntu-4.15.0-88.88-- drivers/scsi/qla2xxx/ 1803d2ecfe61 scsi: qla2xxx: Send Notify ACK after N2N PLOGI c531496eb731 scsi: qla2xxx: Fix PLOGI payload and ELS IOCB dump length 374f839d0f64 scsi: qla2xxx: Drop superfluous INIT_WORK of del_work 3e74574ced98 scsi: qla2xxx: Don't call qlt_async_event twice 8c30c08b2648 nvme_fc: add module to ops template to allow module references 1c20b1a30c12 scsi: qla2xxx: Change discovery state before PLOGI 175f007da89a scsi: qla2xxx: Fix message indicating vectors used by driver 1221bd3c290f scsi: qla2xxx: Always check the qla2x00_wait_for_hba_online() return value 87237677ef42 scsi: qla2xxx: Fix qla24xx_process_bidir_cmd() 1bc7062548ad scsi: qla2xxx: Fix session lookup in qlt_abort_work() 6f8b7559c514 scsi: qla2xxx: Fix DMA unmap leak 437b5663a092 scsi: qla2xxx: Fix driver unload hang 09cca2e026e4 scsi: qla2xxx: deadlock by configfs_depend_item $ git log --oneline Ubuntu-4.15.0-88.88..origin/master-next-- drivers/scsi/qla2xxx/ c135532d2507 scsi: qla2xxx: Fix error handling in qlt_alloc_qfull_cmd() 5c3b3f0e5131 scsi: qla2xxx: Avoid that qlt_send_resp_ctio() corrupts memory 7455f405f8bd scsi: qla2xxx: Fix a format specifier 8bb67105d5cb scsi: qla2xxx: Unregister chrdev if module initialization fails 3d381f9bd4e8 scsi: qla2xxx: fix rports not being mark as lost in sync fabric scan e02de738c644 scsi: qla2xxx: Fix qla2x00_request_irqs() for MSI ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- 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/1863044 Title: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter Status in linux package in Ubuntu: Incomplete Bug description: We have an IBM BladeCentre Hx5 with a number of blades running Ubuntu 18.04.3. Storage is attached over Fiber Channel. They all boot fine with 4.15.0-72 - the qla2xxx detects all the LUNs. On 4.15.0-74 and 4.15.0-76, the qla2xxx driver loads but the LUNs are not detected. This breaks the boot. rescan-scsi-bus.sh is also unable to find the LUNs. Reverting to the 4.15.0-72 kernel works. lspci reports: 06:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA Flags: bus master, fast devsel, latency 0, IRQ 24, NUMA node 0 I/O ports at 2c00 [size=256] Memory at 903fc000 (64-bit, non-prefetchable) [size=16K] Expansion ROM at 9030 [disabled] [size=256K] Capabilities: [44] Power Management version 3 Capabilities: [4c] Express Endpoint, MSI 00 Capabilities: [88] MSI: Enable- Count=1/32 Maskable- 64bit+ Capabilities: [98] Vital Product Data Capabilities: [a0] MSI-X: Enable+ Count=2 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [138] Power Budgeting Kernel driver in use: qla2xxx Kernel modules: qla2xxx Let me know if you need any more details. I attach a version.log and lspci-vnvn.log from a working -72 boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscripti
[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
Andrew absolutely right, problem introduced by commit https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe&id=5613773b6f576de155c39a7b7a04e45f9f6eaf46 I will try to dive into overlayfs internals and find solution. -- 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 1863248] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328169/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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 1863248] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328165/+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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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/ListH
[Kernel-packages] [Bug 1863248] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328171/+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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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 1863248] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328160/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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 1863248] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328164/+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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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 1863248] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328170/+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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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 1863248] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328166/+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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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 1863248] Re: Intel display driver cannot read EDID from VGA monitor
apport information ** Tags added: apport-collected tricia ** Description changed: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: psl1661 F pulseaudio + /dev/snd/controlC0: psl1661 F pulseaudio + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 19.3 + InstallationDate: Installed on 2019-04-29 (290 days ago) + InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 + IwConfig: + lono wireless extensions. + + eno1 no wireless extensions. + MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-28-generic N/A + linux-backports-modules-5.3.0-28-generic N/A + linux-firmware1.173.14 + RfKill: + + Tags: tricia + Uname: Linux 5.3.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/04/2018 + dmi.bios.vendor: Hewlett-Packard + dmi.bios.version: L01 v02.75 + dmi.board.asset.tag: CZC611B2GK + dmi.board.name: 18E5 + dmi.board.vendor: Hewlett-Packard + dmi.chassis.asset.tag: CZC611B2GK + dmi.chassis.type: 3 + dmi.chassis.vendor: Hewlett-Packard + dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: + dmi.product.family: 103C_53307F G=D + dmi.product.name: HP EliteDesk 800 G1 USDT + dmi.product.sku: C8N28AV + dmi.sys.vendor: Hewlett-Packard ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328159/+files/AlsaInfo.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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC
[Kernel-packages] [Bug 1863248] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328161/+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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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 1863248] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328162/+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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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 1863248] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328167/+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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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 1863248] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328168/+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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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 1863248] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1863248/+attachment/5328163/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863248/+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 1863248] Re: Intel display driver cannot read EDID from VGA monitor
In the old good times of Windows 98 I was able to disable Plug&Play and select my monitor from DB of known models or select generic configuration to match my resolution. I miss such option in modern Linux distributions, it could be useful fallback when Plug&Play for some reason doesn't work. When it works, it is great but when Plug&Play is broken, it is very difficult to configure Linux to use correct display resolution. -- 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/1863248 Title: Intel display driver cannot read EDID from VGA monitor Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 Report if from Linux Mint 19.3 but the same situation is with Ubuntu 18.04 Linux cannot access EDID information from VGA port and it offers maximum resolution of 1024x768, that is not too much for 24" monitor. When I connect VGA monitor to other PC with Nvidia card (cuda driver, GPU for games), it works OK. When I run Windows in this PC, it is OK, monitor is properly detected and resolution set correctly. Problem is only with boards with Intel video chips, those are Linux unfriendly. This is report from nice mini PC, HP EliteDesk 800 G1 USDT. Until this bug is fixed you cannot expect that people will use these office PCs with Linux... $ sudo inxi -F System: Host: elite Kernel: 5.3.0-28-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: Hewlett-Packard product: HP EliteDesk 800 G1 USDT v: N/A serial: CZC611B2GK Mobo: Hewlett-Packard model: 18E5 serial: CZCxxx UEFI: Hewlett-Packard v: L01 v02.75 date: 05/04/2018 CPU: Topology: Quad Core model: Intel Core i5-4590S bits: 64 type: MCP L2 cache: 6144 KiB Speed: 799 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-28-generic Network: Device-1: Intel Ethernet I217-LM driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: ec:b1:d7:72:ea:cd Drives: Local Storage: total: 232.89 GiB used: 37.68 GiB (16.2%) ID-1: /dev/sda vendor: SanDisk model: SDSSDH3250G size: 232.89 GiB Partition: ID-1: / size: 227.74 GiB used: 37.68 GiB (16.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 19m Memory: 15.53 GiB used: 1.29 GiB (8.3%) Shell: bash inxi: 3.0.32 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psl1661 F pulseaudio /dev/snd/controlC0: psl1661 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 InstallationDate: Installed on 2019-04-29 (290 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Hewlett-Packard HP EliteDesk 800 G1 USDT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=ff586528-825b-4ee5-b08e-bc363013c7a5 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 RfKill: Tags: tricia Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.75 dmi.board.asset.tag: CZC611B2GK dmi.board.name: 18E5 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC611B2GK dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.75:bd05/04/2018:svnHewlett-Packard:pnHPEliteDesk800G1USDT:pvr:rvnHewlett-Packard:rn18E5:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 USDT dmi.product.sku: C8N28AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launc
[Kernel-packages] [Bug 1861070] Re: Raspberry Pi 4B: USB OTG is not working
** Also affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Eoan) Importance: Undecided => High ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: New => In Progress -- 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/1861070 Title: Raspberry Pi 4B: USB OTG is not working Status in linux-raspi2 package in Ubuntu: Triaged Status in linux-raspi2 source package in Eoan: In Progress Bug description: [Impact] On the RPI4B board, the usb-c power port could also work as a USB OTG mode, but we set the dwc2 driver to the host mode unconditionally, now set it to dual_role mode, then it could work in host/otg/peripheal mode. [Fix] Set USB_DWC2_DUAL_ROLE=y, USB_DWC2_HOST=n [Test Case] set the dtoverlay=dwc2,dr_mode=[otg|peripheral] in the config.txt, and isnmod the g_ether or g_cdc, on the host machine, we could see RPI4B work as a usb device. Because physical port limitation, could test dr_mode=host. [Regression Risk] Low, our eoan kernel choose dwc_otg driver for this port by default, very very few users will choose dwc2 driver, and the dwc2 driver is not enabled by default in our kernel. And bug reporter and I already tested that the peripheral mode works after this change. I am using Raspberry Pi 4B (4GB) and want to make use of the OTG functionality (g_ether). I cross checked with Raspbian to make sure it is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with latest updates applied as of Jan 26th, 2020 via "apt-get update" and "apt-get full-upgrade": ... [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [1.517365] dwc_otg: FIQ enabled [1.517376] dwc_otg: NAK holdoff enabled [1.517386] dwc_otg: FIQ split-transaction FSM enabled [1.517399] Module dwc_common_port init ... [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host [6.409098] dwc2 fe98.usb: DWC OTG Controller [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98 ... [ 111.796714] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I think it is that "Configuration mismatch. dr_mode forced to host" log entry telling me that the port is acting as HOST mode instead of OTG mode. I have try putting these in usercfg.txt "dtoverlay=dwc2" "dtoverlay=dwc2,dr_mode=otg" "dtoverlay=dwc2,dr_mode=peripheral" and it will give the same result, no OTG functionality. On the same hardware running Raspbian Buster, it initialise successfully. Corresponding dmesg: ... [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [0.570391] dwc_otg: FIQ enabled [0.570400] dwc_otg: NAK holdoff enabled [0.570409] dwc_otg: FIQ split-transaction FSM enabled [0.570421] Module dwc_common_port init ... [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0 [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1 [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1 [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [2.752511] dwc2 fe98.usb: DWC OTG Controller [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98 ... [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [2.851601] g_ether gadget: g_ether ready [2.854580] dwc2 fe98.usb: bound driver g_ether [2.998525] dwc2 fe98.usb: new device is high-speed [3.075025] dwc2 fe98.usb: new device is high-speed [3.139338] dwc2 fe98.usb: new address 10 [3.154010] g_ether gadget: high-speed config #1: CDC Ethernet (ECM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861070/+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 1862814] Re: bionic/linux-oracle: 4.15.0-1033.36 -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: 1862824 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 12. February 2020 14:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff trackers: xenial/linux-oracle: bug 1862813 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1862814 Title: bionic/linux-oracle: 4.15.0-1033.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1862824 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 12. February 2020 14:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff trackers: xenial/linux-oracle: bug 1862813 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862814/+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 1862813] Re: xenial/linux-oracle: 4.15.0-1033.36~16.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: 1862814 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Signoff phase-changed: Friday, 14. February 2020 07:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1862813 Title: xenial/linux-oracle: 4.15.0-1033.36~16.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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1862814 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Signoff phase-changed: Friday, 14. February 2020 07:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862813/+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
Quick fix (not sure that it's fully correct)
diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
index 943733d86da3..fa30b615076e 100644
--- a/fs/overlayfs/file.c
+++ b/fs/overlayfs/file.c
@@ -24,13 +24,16 @@ static char ovl_whatisit(struct inode *inode, struct inode
*realinode)
static struct file *ovl_open_realfile(const struct file *file,
struct inode *realinode)
{
+ struct path realpath;
struct inode *inode = file_inode(file);
struct file *realfile;
const struct cred *old_cred;
int flags = file->f_flags | O_NOATIME | FMODE_NONOTIFY;
old_cred = ovl_override_creds(inode->i_sb);
- realfile = open_with_fake_path(&file->f_path, flags, realinode,
+ ovl_path_real(file->f_path.dentry, &realpath);
+ realpath.mnt = file->f_path.mnt; // important!
+ realfile = open_with_fake_path(&realpath, flags, realinode,
current_cred());
revert_creds(old_cred);
--
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 1863086] Re: unkillable process (kernel NULL pointer dereference)
After previous comment I checked my system settings and find what affect to this bug. I usually disable system core dump in all linux distributions using kernel.core_pattern=| in sysctl.conf When kernel.core_pattern has default all ok. So kernel.core_pattern=| cause this bug. It occurs since kernel 5.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863086 Title: unkillable process (kernel NULL pointer dereference) Status in linux package in Ubuntu: Confirmed Bug description: If process that listens socket on any port crashes (segmentation fault) it becomes unkillable. Kill command does not kill this process. Port that listen crashed process never be freed. journalctl shows error: Feb 13 13:28:09 vbun04 kernel: socktest[1359]: segfault at 21 ip 55ec3a6bf11e sp 7ffd88899fb0 error 6 in socktest[55ec3a6bf000+1000] Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 ff ff ff 04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18 Feb 13 13:28:09 vbun04 kernel: BUG: kernel NULL pointer dereference, address: 0020 Feb 13 13:28:09 vbun04 kernel: #PF: supervisor read access in kernel mode Feb 13 13:28:09 vbun04 kernel: #PF: error_code(0x) - not-present page Feb 13 13:28:09 vbun04 kernel: PGD 0 P4D 0 Feb 13 13:28:09 vbun04 kernel: Oops: [#1] SMP NOPTI Feb 13 13:28:09 vbun04 kernel: CPU: 1 PID: 1359 Comm: socktest Tainted: G OE 5.3.0-29-generic #31-Ubuntu Feb 13 13:28:09 vbun04 kernel: Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30 Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 05 00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246 Feb 13 13:28:09 vbun04 kernel: RAX: RBX: 9d4b76995100 RCX: 1afc Feb 13 13:28:09 vbun04 kernel: RDX: RSI: b464c2c5fc68 RDI: Feb 13 13:28:09 vbun04 kernel: RBP: b464c2c5fdd8 R08: 0400 R09: b464c2c5fbe0 Feb 13 13:28:09 vbun04 kernel: R10: 9d4b75d01170 R11: R12: 9d4b7b3df540 Feb 13 13:28:09 vbun04 kernel: R13: 0001 R14: R15: b9f15920 Feb 13 13:28:09 vbun04 kernel: FS: 7f6c91911540() GS:9d4b7db0() knlGS: Feb 13 13:28:09 vbun04 kernel: CS: 0010 DS: ES: CR0: 80050033 Feb 13 13:28:09 vbun04 kernel: CR2: 0020 CR3: 723ac003 CR4: 000606e0 Feb 13 13:28:09 vbun04 kernel: Call Trace: Feb 13 13:28:09 vbun04 kernel: ? wake_up_state+0x10/0x20 Feb 13 13:28:09 vbun04 kernel: ? __send_signal+0x1eb/0x3f0 Feb 13 13:28:09 vbun04 kernel: get_signal+0x159/0x880 Feb 13 13:28:09 vbun04 kernel: do_signal+0x34/0x280 Feb 13 13:28:09 vbun04 kernel: ? bad_area+0x47/0x50 Feb 13 13:28:09 vbun04 kernel: exit_to_usermode_loop+0xbf/0x160 Feb 13 13:28:09 vbun04 kernel: prepare_exit_to_usermode+0x77/0xa0 Feb 13 13:28:09 vbun04 kernel: retint_user+0x8/0x8 Feb 13 13:28:09 vbun04 kernel: RIP: 0033:0x55ec3a6bf11e Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 ff ff ff 04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18 Feb 13 13:28:09 vbun04 kernel: RSP: 002b:7ffd88899fb0 EFLAGS: 00010217 Feb 13 13:28:09 vbun04 kernel: RAX: RBX: RCX: 7f6c918424eb Feb 13 13:28:09 vbun04 kernel: RDX: 0010 RSI: 000a RDI: 0003 Feb 13 13:28:09 vbun04 kernel: RBP: 0003 R08: R09: 7f6c919331f0 Feb 13 13:28:09 vbun04 kernel: R10: R11: 0217 R12: 55ec3a6bf150 Feb 13 13:28:09 vbun04 kernel: R13: 7ffd8889a0b0 R14: R15: Feb 13 13:28:09 vbun04 kernel: Modules linked in: vboxsf(OE) nls_utf8 isofs vboxvideo(OE) intel_rapl_msr intel_rapl_common crct10dif_pclmul vmwgfx crc32_pclmul ghash_clmulni_intel aesni_intel ttm drm_kms_helper a Feb 13 13:28:09 vbun04 kernel: CR2: 0020 Feb 13 13:28:09 vbun04 kernel: ---[ end trace 278d665c8727286a ]--- Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30 Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 05 00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246
[Kernel-packages] [Bug 1863269] [NEW] linux-raspi2: -proposed tracker
Public bug reported: 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 -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-raspi2 (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2020.02.17-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-updates Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: (unassigned)
[Kernel-packages] [Bug 1863272] [NEW] linux-aws: -proposed tracker
Public bug reported: 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 -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2020.02.17-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux-aws (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lrm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Impor
[Kernel-packages] [Bug 1863274] [NEW] linux-azure: -proposed tracker
Public bug reported: 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 -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2020.02.17-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux-azure (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel
[Kernel-packages] [Bug 1863285] [NEW] linux-azure: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1863297 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1863297 kernel-sru-cycle-2020.02.17-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: ker
[Kernel-packages] [Bug 1863289] [NEW] linux-gcp: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1863297 variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-gcp (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1863297 kernel-sru-cycle-2020.02.17-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Bionic) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lrm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: (unassigne
[Kernel-packages] [Bug 1863283] [NEW] linux-kvm: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1863294 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-kvm (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2020.02.17-1 kernel-sru-derivative-of-1863294 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux-kvm (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sr
[Kernel-packages] [Bug 1863276] [NEW] linux-hwe-5.0: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1863297 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1863297 kernel-sru-cycle-2020.02.17-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lrm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-met
[Kernel-packages] [Bug 1863280] [NEW] linux-gcp: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1863294 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-gcp (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2020.02.17-1 kernel-sru-derivative-of-1863294 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux-gcp (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lrm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: (unassigned)
[Kernel-packages] [Bug 1863297] [NEW] disco/linux: -proposed tracker
Public bug reported: 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: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Packaging phase-changed: Friday, 14. February 2020 16:10 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-hwe-5.0: bug 1863276 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Disco) Importance: Medium Status: Confirmed ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2020.02.17-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: disco kernel-release-tracking-bug ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lrm
[Kernel-packages] [Bug 1863294] [NEW] eoan/linux: -proposed tracker
Public bug reported: 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: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Packaging phase-changed: Friday, 14. February 2020 16:06 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-hwe: bug 1863292 eoan/linux-aws: bug 1863272 eoan/linux-azure: bug 1863274 eoan/linux-gcp: bug 1863280 eoan/linux-kvm: bug 1863283 eoan/linux-oracle: bug 1863290 eoan/linux-raspi2: bug 1863269 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2020.02.17-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Cha
[Kernel-packages] [Bug 1863297] Re: disco/linux: -proposed tracker
** Summary changed: - linux: -proposed tracker + disco/linux: -proposed tracker -- 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/1863297 Title: disco/linux: -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: Confirmed Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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 Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Packaging phase-changed: Friday, 14. February 2020 16:10 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-hwe-5.0: bug 1863276 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863297/+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 1863285] Re: linux-azure: -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 -- + kernel-stable-master-bug: 1863297 variant: debs ** Tags added: kernel-sru-backport-of-1863297 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Tags removed: kernel-sru-backport-of-1863297 ** Tags added: kernel-sru-backport-of-1863297 ** Tags removed: kernel-sru-backport-of-1863297 ** Tags added: kernel-sru-backport-of-1863297 -- 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/1863285 Title: linux-azure: -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: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863297 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863285/+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 1863280] Re: eoan/linux-gcp: -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 -- kernel-stable-master-bug: 1863294 + packages: + lrm: linux-restricted-modules-gcp + main: linux-gcp + meta: linux-meta-gcp + signed: linux-signed-gcp + phase: Holding before Packaging + phase-changed: Friday, 14. February 2020 16:05 UTC + reason: + prepare-package: Holding -- waiting for master bug + trackers: + bionic/linux-gcp-5.3: bug 1863275 + bionic/linux-gke-5.3: bug 1863278 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/1863280 Title: eoan/linux-gcp: -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: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863294 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Friday, 14. February 2020 16:05 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-gcp-5.3: bug 1863275 bionic/linux-gke-5.3: bug 1863278 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863280/+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 1863283] Re: eoan/linux-kvm: -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + eoan/linux-kvm: -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 -- kernel-stable-master-bug: 1863294 + packages: + main: linux-kvm + meta: linux-meta-kvm + phase: Holding before Packaging + phase-changed: Friday, 14. February 2020 16:05 UTC + reason: + prepare-package: Holding -- waiting for master bug variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1863283 Title: eoan/linux-kvm: -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: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New 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-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863294 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Packaging phase-changed: Friday, 14. February 2020 16:05 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863283/+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 1863280] Re: linux-gcp: -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 -- + kernel-stable-master-bug: 1863294 variant: debs ** Tags added: kernel-sru-derivative-of-1863294 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Tags removed: kernel-sru-derivative-of-1863294 ** Tags added: kernel-sru-derivative-of-1863294 -- 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/1863280 Title: eoan/linux-gcp: -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: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863294 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Friday, 14. February 2020 16:05 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-gcp-5.3: bug 1863275 bionic/linux-gke-5.3: bug 1863278 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863280/+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 1863280] Re: eoan/linux-gcp: -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + eoan/linux-gcp: -proposed tracker -- 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/1863280 Title: eoan/linux-gcp: -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: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863294 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Friday, 14. February 2020 16:05 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-gcp-5.3: bug 1863275 bionic/linux-gke-5.3: bug 1863278 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863280/+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 1863283] Re: linux-kvm: -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 -- + kernel-stable-master-bug: 1863294 variant: debs ** Tags added: kernel-sru-derivative-of-1863294 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1863283 Title: eoan/linux-kvm: -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: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New 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-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863294 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Packaging phase-changed: Friday, 14. February 2020 16:05 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863283/+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 1863269] Re: eoan/linux-raspi2: -proposed tracker
** Summary changed: - linux-raspi2: -proposed tracker + eoan/linux-raspi2: -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 -- kernel-stable-master-bug: 1863294 + packages: + main: linux-raspi2 + meta: linux-meta-raspi2 + phase: Holding before Packaging + phase-changed: Friday, 14. February 2020 16:03 UTC + reason: + prepare-package: Holding -- waiting for master bug + trackers: + bionic/linux-raspi2-5.3: bug 1863268 + eoan/linux-raspi2/pi-kernel: bug 1863266 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1863269 Title: eoan/linux-raspi2: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863294 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Packaging phase-changed: Friday, 14. February 2020 16:03 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-raspi2-5.3: bug 1863268 eoan/linux-raspi2/pi-kernel: bug 1863266 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863269/+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 1863272] Re: eoan/linux-aws: -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + eoan/linux-aws: -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 -- kernel-stable-master-bug: 1863294 + packages: + lrm: linux-restricted-modules-aws + main: linux-aws + meta: linux-meta-aws + phase: Holding before Packaging + phase-changed: Friday, 14. February 2020 16:03 UTC + reason: + prepare-package: Holding -- waiting for master bug + trackers: + bionic/linux-aws-5.3: bug 1863270 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1863272 Title: eoan/linux-aws: -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: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863294 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Packaging phase-changed: Friday, 14. February 2020 16:03 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-aws-5.3: bug 1863270 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863272/+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 1863274] Re: eoan/linux-azure: -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + eoan/linux-azure: -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 -- kernel-stable-master-bug: 1863294 + packages: + lrm: linux-restricted-modules-azure + main: linux-azure + meta: linux-meta-azure + signed: linux-signed-azure + phase: Holding before Packaging + phase-changed: Friday, 14. February 2020 16:04 UTC + reason: + prepare-package: Holding -- waiting for master bug + trackers: + bionic/linux-azure-5.3: bug 1863273 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1863274 Title: eoan/linux-azure: -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: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863294 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Friday, 14. February 2020 16:04 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-azure-5.3: bug 1863273 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863274/+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
