** Changed in: kernel-package (Ubuntu Zesty)
Status: New => Invalid
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
As Vivid has reached its "End of Life", this bug can be safely closed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1496290
Title:
10de:0a3c System freeze due to "angry" nouveau
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
Didn't see test results coming in after several attempts, might be some issue
to the test infrastructure.
I will just let it through and work with Brad to resolve this.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Changed in:
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
--- Comment (attachment only) From martin.schwidef...@de.ibm.com 2017-08-18
06:51 EDT---
** Attachment added: "Fix race local TLB flushing vs. context switch"
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in:
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 1717897
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1684788
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1684789
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
*** This bug is a duplicate of bug 1716613 ***
https://bugs.launchpad.net/bugs/1716613
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing:
*** This bug is a duplicate of bug 1716613 ***
https://bugs.launchpad.net/bugs/1716613
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing:
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
Fedora's kernel version: 4.12.13-300.fc26.x86_64
Debian's kernel version: 4.9.0-3-amd64
Both are affected. Ubuntu LTS is not, though. I don't remember 17.04.
I can install the mainline 4.13 kernel for Fedora. If Ubuntu is really
needed, I don't mind installing it here.
--
You received this bug
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
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 1717884
and then change the status of the bug to 'Confirmed'.
If, due to the
Yo!
My dear friend I've got such a good news for you, just take a look at
http://www.phoenixicetheatre.org/sites/default/files/css/liberal.php?UE81MTg0N0BidWdzLmxhdW5jaHBhZC5uZXQ-
Paolo Grifa
From: 51847 [mailto:51...@bugs.launchpad.net]
Sent: Monday, September 18, 2017 4:48 AM
To:
Looks like the timeout for the capture occurs before sysdig manages to
start. Need to add a polling delay that checks if sysdig is up and ready
before we kick off the capture timeout.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
--- Comment (attachment only) From martin.schwidef...@de.ibm.com 2017-08-18
06:51 EDT---
** Attachment added: "Fix race local TLB flushing vs. context switch"
--- Comment (attachment only) From martin.schwidef...@de.ibm.com 2017-08-18
06:52 EDT---
** Attachment added: "Fix race on mm->context.flush_mm"
https://bugs.launchpad.net/bugs/1708399/+attachment/4952097/+files/0003-s390-mm-fix-race-on-mm-context.flush_mm.patch
--
You received
--- Comment From heinz-werner_se...@de.ibm.com 2017-09-18 06:32 EDT---
IBM bugzilla status -> closed. Fix Release in Zesty/Xenial.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
1. Test with Artful + 4.12 kernel deployed by MaaS, this one has passed.
2. Install 4.13 kernel from -proposed, retest, this one will fail
3. Reboot to 4.12 again, this will fail too.
09:44:44 INFO | LD_PRELOAD=libheapshrink.so HUGETLB_MORECORE_SHRINK=yes
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
*** This bug is a duplicate of bug 1716606 ***
https://bugs.launchpad.net/bugs/1716606
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing:
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux-gke - 4.4.0-1031.31
---
linux-gke (4.4.0-1031.31) xenial; urgency=low
* linux-gke: 4.4.0-1031.31 -proposed tracker (LP: #1716621)
[ Ubuntu: 4.4.0-96.119 ]
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
As Vivid has reached its "End of Life", this bug can be safely closed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1496290
Title:
10de:0a3c System freeze due to "angry" nouveau
--- Comment (attachment only) From martin.schwidef...@de.ibm.com 2017-08-18
06:52 EDT---
** Attachment added: "Fix race on mm->context.flush_mm"
https://bugs.launchpad.net/bugs/1708399/+attachment/4952057/+files/0003-s390-mm-fix-race-on-mm-context.flush_mm.patch
--
You received
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709352
Title:
Avoid spurious PMU interrupts after idle
@bdmurray, I'd like you to reconsider the notfixing tag, it's a real
issue for QA because qxl is the only driver that works with wayland. The
system falls back to X with the standard vga driver and does not boot
after installation with cirrus.
--
You received this bug notification because you
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in:
--- Comment From lekshmi.cpil...@in.ibm.com 2017-09-18 06:29 EDT---
Hi
Its is same config.Both lpars its multipath disks.With that we recreated
the issue
Thanks
Lekshmi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Overriding 2 outstanding verifications:
1. Address sanitizer regression (selected revert is part of upstream stable
anyway)
2. oops on s390x: changes requested and backported by maintainers. previously
tested in test kernel
** Changed in: kernel-sru-workflow/verification-testing
Status:
Overriding, only one outstanding and that is a customer requested arch
specific change.
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-zesty
** Tags removed: block-proposed
--
You received this bug notification because you
Public bug reported:
This issue can be reproduced on 4.12 and 4.13 kernel.
And it's only happening on node lodygin (AMD speedway).
== sysdig smoke test to trace dd, cat, read and writes ==
Limiting raw capture file to 16384 blocks
Try 1 of 10
Raw capture file is 0 Mbytes
Converted
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
my touchpad didnt work
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1708852
Title:
Touchpad not detected
Status in linux package in Ubuntu:
Fix Released
Status in linux source
4.13.0-11.12 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html
Issue to note in amd64:
hwclock - lodygin will have time changed to 2080, bug 1714229
libhugetlbfs - failed 1 (Heap did not shrink, bug 1717897), killed by signal
15, bad config 1
*** This bug is a duplicate of bug 1717963 ***
https://bugs.launchpad.net/bugs/1717963
Sorry, duplicate of Bug #1717963. My mistake.
** This bug has been marked a duplicate of bug 1717963
Cannot connect to PEAP-protected Wifi
--
You received this bug notification because you are a
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1717963
Title:
Cannot connect to
--- Comment From wenxi...@us.ibm.com 2017-09-18 11:03 EDT---
Nvme device is one of load source now. We need to support installation with T10
enable over nvme device. So we would like to drop this patch into installer
kernel for Ubuntu installation.
Let me know if you have any question.
*** This bug is a duplicate of bug 1717963 ***
https://bugs.launchpad.net/bugs/1717963
Public bug reported:
When I try to connect to my workplace's WiFi network with settings:
WP2
PEAP authentication
MSCHAPv2 Inner
It does not connect and I get a stack trace in dmesg. This happens
every
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Description changed:
[Impact]
Enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400. Where, control area
buffer address is greater than 32-bit.
[Test]
- Currently only built for X64 & ACPI.
+ Currently only built for X64 & ACPI. After building for arm64 validate using
tcg
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
You have been subscribed to a public bug:
Ubuntu 16.04
Linux Kernel 4.4.0-93-generic
Steps
-
1. Build chromium with address sanitizer
https://www.chromium.org/developers/testing/addresssanitizer
2. Received below mentioned error.
==6372==Shadow memory range interleaves with an existing
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1717656
Title:
Shadow memory range interleaves with an existing memory mapping. ASan
cannot
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 1717656
and then change the status of the bug to 'Confirmed'.
If, due to the
Wendy,
At this time you can use the installer in -proposed, once the kernel in
-proposed gets promoted to -updates (typically within ~5 weeks) you can
use the installer from -updates. Here is the link to the installer in
Xenial-updates:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
**
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
**
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) =>
Wendy, Could you please try the installer in -proposed ?
http://ports.ubuntu.com/dists/xenial-proposed/main/installer-
ppc64el/current/images/hwe-netboot/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Precise)
Importance: Undecided => Medium
**
1 - 100 of 236 matches
Mail list logo