Haveged and rng-tools5 or rng-tools didn't help me too.
I reported my problem to near topic
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1767782/comments/13
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1739107
Title:
linux-cloud-tools-common: Ensure hv-kvp-
Okay, I went back through the kernel PPAs and in fact the most recent
one that I can get to boot under 32-bit PV mode Xen is 4.13.16. 4.14-rc1
does not boot.
I realised then that it was possible that I had never tested any version
of 32-bit Ubuntu 18.04 under Xen. It is possible that I only ever t
The bug is indeed fixed in the latest v4.15 stable kernel:
$ uname -a
Linux apol1 4.15.18-041518-generic #201804190330 SMP Thu Apr 19 07:34:21 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Pa
I no longer own this laptop (Thinkpad T440p), so I am not in a position
to do further testing.
--
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/1722478
Title:
Two-finger scrolling no longe
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Also affects: stress-ng
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.launchpa
Hi, please remove psmouse.synaptics_intertouch=0" add comment out
"blacklist i2c_i801" in /etc/modprobe.d/blacklist.conf, and see if this
helps.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
*** This bug is a duplicate of bug 1595765 ***
https://bugs.launchpad.net/bugs/1595765
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1595765, so it is being marked as such. Please look
Tested on 17.10 server d-i install, it would be screen blur too during
installation, the kernel is 4.13.0.
--
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/1762940
Title:
Ubuntu 18.04 d-i
Tested with 18.04.1 Desktop, it wouldn't screen blur. The kernel log are
enclosed.
** Attachment added: "18.04.1 desktop install kernel log (no screen blur)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5181977/+files/kern.log-18.04.1-desktop-noblur.txt
--
You rec
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: hwe-next
Status: New => Triaged
--
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/1789358
Title:
Can you please:
1. Remove radeon.dpm=0 and reproduce the bug at least once; then
2. Add radeon.dpm=0 and collect the log from the previous faulty boot:
journalctl -b-1 > previous_boot.txt
3. Attach the file previous_boot.txt here.
** Tags added: radeon
** Changed in: gnome-shell (Ubuntu)
I don't seem to have access to change the tag, but I can confirm that
4.15.0-34-generic from -proposed solves the problem. So the tag should
be verification-done-bionic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
Further Details on Problem:
Typical syslog output:
Aug 28 16:48:34 Inspiron-3847 kernel: [ 62.424273] Corrupted low
memory at a78dba88 (1000 phys) = 6110
Aug 28 16:48:34 Inspiron-3847 kernel: [ 62.424282] Corrupted low memory at
d190a321 (1008 phys) = 1000
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181961/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181957/+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/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181960/+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/1789492
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181956/+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
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181959/+files/RfKill.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/1789492
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181953/+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/b
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181955/+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/b
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181952/+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/1789492
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181954/+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.l
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181958/+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/
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181947/+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/1789492
Ti
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181951/+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/1789492
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181950/+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/17
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181949/+files/Dependencies.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
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1789492/+attachment/5181948/+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
apport information
** Tags added: apport-collected bionic
** Description changed:
Whenever I close the lid of my laptop or hit the power button, my PC is
unable to suspend correctly. The system shutdowns with no indication
that it ever enters the suspension state (no blinking power LED) an
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/1789519
Title:
Low Memory corruption logged i
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 1789492
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Dell Inspiron 3847 Desktop running Ubuntu 18.04.1 LTS
kernel: 4.15.0-33-generic
Corrupted low memory messages logged in syslog
Can be reproduced with script:
#!/bin/bash
# log to syslog...
logger -st low_mem_corruption.sh "Checking for low memory corruption with
kernel $(
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/1789518
Title:
automounting MTP or USB storag
** Also 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/1789492
Title:
suspending system causes full shutdown
Status i
Public bug reported:
After upgrading from xenial to bionic, USB (both MTP and mass storage)
devices will not automount.
syslog shows the usb device is found and recognized as a storage device:
Aug 28 16:49:18 insitu kernel: [ 4412.072025] usb 1-8: new high-speed USB
device number 18 using ehci-
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
--
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/1788750
Title:
linux-aws: 4.15.0-1021.21
For me, the same issue remains but I suspect it is related to Nvidia
driver, since after I removed nvidia driver, both suspend and hibernate
work normal with this new kernel. I used the proprietary tested
Nvidia-390.48 driver on Nvidia 1080.
With this new kernel, I tested hibernate with the open
Kai-Heng Feng,
Success, I tried #63 and it worked.
This is great, thanks.
--
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/1779817
Title:
r8169 no internet after suspending
Status in li
Kai-Heng Feng,
Success, I tried #1779817:63 and it worked.
This is great, thanks.
--
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/1752772
Title:
r8169 ethernet card don't work after retu
Verification:
ubuntu@d06-3:~$ cat /proc/version
Linux version 4.15.0-34-generic (buildd@bos02-arm64-002) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #37-Ubuntu SMP Mon Aug 27 15:22:18 UTC 2018
ubuntu@d06-3:~$ lsmod | grep hinic
hinic 94208 0
ubuntu@d06-3:~$ grep eth /proc
I upgraded the kernel from 4.15.0-33 to 4.17.14 and it did not help
much. Now, after opening the lid the screen works for a second before
its getting dark again.
Its a HP Probook 470 with i7 8550 CPU, 250GB SSDdrive and Intel UHD
Graphics 620. Ubuntu 18.04
--
You received this bug notification b
** Description changed:
[Impact]
Interfaces associated with Huawei "hinic" PCI adapters will not be assigned
predictable names[*] and instead remain using the kernel names (e.g. eth0).
This can lead to races where the interface names are not the same on every
boot. For example, in a system
I can confirm that
Package: linux-image-4.15.0-34-generic
Architecture: amd64
Version: 4.15.0-34.37
fixes the problem for me.
Both suspend and hibernate have been tested on an Acer Travelmate B115M
(with Intel Pentium N3540 CPU)
** Tags removed: verification-needed-bionic
** Tags added: verific
I ran the test case on the 4.19.0-041900rc1-generic kernel and it also
has the bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788623
Title:
regression: IPv6 PMTU discovery fails wi
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for trackin
If I omit ddb457c6993b "net/smc: Replace ib_query_gid with
rdma_get_gid_attr" all the rest of the commits listed in comment #2
cherry pick cleanly. That commit is later reverted, though intermediate
changes make it not a direct revert, but that does make think we can
probably just omit it. If I do
Thx! With the test kernel from
http://kernel.ubuntu.com/~jsalisbury/lp1788997 according to #21 wifi of
the laptop HP 1S-af023ngof works again. So reverting commit
af8a41cccf8f469165c6debc8fe07c5fd2ca501a seems to fix the bug.
--
You received this bug notification because you are a member of Kern
This bug was fixed in the package linux - 4.17.0-9.10
---
linux (4.17.0-9.10) cosmic; urgency=medium
* linux: 4.17.0-9.10 -proposed tracker (LP: #1787988)
* Cosmic update to 4.17.17 stable release (LP: #1787973)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
-
This bug was fixed in the package linux - 4.17.0-9.10
---
linux (4.17.0-9.10) cosmic; urgency=medium
* linux: 4.17.0-9.10 -proposed tracker (LP: #1787988)
* Cosmic update to 4.17.17 stable release (LP: #1787973)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
-
This bug was fixed in the package linux - 4.17.0-9.10
---
linux (4.17.0-9.10) cosmic; urgency=medium
* linux: 4.17.0-9.10 -proposed tracker (LP: #1787988)
* Cosmic update to 4.17.17 stable release (LP: #1787973)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
-
This bug was fixed in the package linux - 4.17.0-9.10
---
linux (4.17.0-9.10) cosmic; urgency=medium
* linux: 4.17.0-9.10 -proposed tracker (LP: #1787988)
* Cosmic update to 4.17.17 stable release (LP: #1787973)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
-
This bug was fixed in the package linux - 4.17.0-9.10
---
linux (4.17.0-9.10) cosmic; urgency=medium
* linux: 4.17.0-9.10 -proposed tracker (LP: #1787988)
* Cosmic update to 4.17.17 stable release (LP: #1787973)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
-
This bug was fixed in the package linux - 4.17.0-9.10
---
linux (4.17.0-9.10) cosmic; urgency=medium
* linux: 4.17.0-9.10 -proposed tracker (LP: #1787988)
* Cosmic update to 4.17.17 stable release (LP: #1787973)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
-
*** This bug is a duplicate of bug 1787988 ***
https://bugs.launchpad.net/bugs/1787988
This bug was fixed in the package linux - 4.17.0-9.10
---
linux (4.17.0-9.10) cosmic; urgency=medium
* linux: 4.17.0-9.10 -proposed tracker (LP: #1787988)
* Cosmic update to 4.17.17 stable
This bug was fixed in the package linux - 4.17.0-9.10
---
linux (4.17.0-9.10) cosmic; urgency=medium
* linux: 4.17.0-9.10 -proposed tracker (LP: #1787988)
* Cosmic update to 4.17.17 stable release (LP: #1787973)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
-
This bug was fixed in the package linux - 4.17.0-9.10
---
linux (4.17.0-9.10) cosmic; urgency=medium
* linux: 4.17.0-9.10 -proposed tracker (LP: #1787988)
* Cosmic update to 4.17.17 stable release (LP: #1787973)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
-
This bug was fixed in the package linux - 4.17.0-9.10
---
linux (4.17.0-9.10) cosmic; urgency=medium
* linux: 4.17.0-9.10 -proposed tracker (LP: #1787988)
* Cosmic update to 4.17.17 stable release (LP: #1787973)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
-
This bug was fixed in the package linux - 4.17.0-9.10
---
linux (4.17.0-9.10) cosmic; urgency=medium
* linux: 4.17.0-9.10 -proposed tracker (LP: #1787988)
* Cosmic update to 4.17.17 stable release (LP: #1787973)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
-
https://www.spinics.net/lists/linux-bcache/msg04869.html
https://www.spinics.net/lists/linux-bcache/msg05774.html
On Tue, Aug 28, 2018 at 2:30 PM Ryan Harper wrote:
>
> It's always been a locking issue, so either misuse (or missing) locks
> in the bcache attach/detach path, or generic locking cha
These do not apply cleanly for me. I don't see git getting confused
about deletions, rather I see that we have two or more branches which
have merged and have conflicting changes, which doesn't make for easy
cherry picks. I'll try to resolve this, but in the mean time I have a
couple of questions.
** 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
** 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
** 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
https://patchwork.kernel.org/patch/10094201/
diff --git a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
index d4f80786e7c2..3890468678ce 100644
--- a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dt
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that up
It's always been a locking issue, so either misuse (or missing) locks
in the bcache attach/detach path, or generic locking changes to block
layer path I'd think.
I'll see if I can find any hits on those oops tracebacks too
On Tue, Aug 28, 2018 at 2:29 PM Ryan Harper wrote:
>
> https://patchwork.
Since work already started to upgrade the cosmic kernel to 4.18 and the above
commit is from 4.18,
I change 'linux (Ubuntu)' to Fix Committed, too.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committe
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
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/1788753
Title:
linux-kvm: 4.15.0-1021.21 -p
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787058
Title:
ThinkPad systems have no HDMI sound when
The bisect reported the following commit as the first bad commit:
bc631943faba ("arm64: dts: rockchip: limit rk3328-rock64 gmac speed to
100MBit for now")
It's strange that this is an arm64 commit. I'll investigate a bit and
see why the bisect came back with this result.
--
You received this b
** 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 => In Progress
** Changed in: kernel-sr
** Tags added: architecture-s39064 bugnameltc-170918 severity-high
targetmilestone-inin1804
--
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/1788432
Title:
4.15 s390x kernel BUG at /build/
Good evening!
I can give feedback right away from the last 2 notes.
The other workaround proposed (in askubuntu.com) of adding a kernel
parameter intel_idle.max_cstate=1 seems to work well (max uptime tested
is 6h 45min so far).
Regarding the indication to use 4.18.3-041803-generic, I downloaded
The following commit introduced the exception table in v4.15-rc1:
35732d01fe31 ipv6: introduce a hash table to store dst cache
This commit does not revert easily. Before I contact upstream
regarding this regression, can you test the v4.19-rc1 kernel to see if
any other commits may have helped th
FAILED: Kernel 4.15-rc1 up to bc631943faba6fc3f755748091ada31798fb7d50
Attached is the oops of the failure.
** Attachment added: "rc1-bisect7-oops.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5181823/+files/rc1-bisect7-oops.txt
--
You received this bug notif
According to comment #2 fix was verified by IBM-
Setting the tag accordingly ...
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
** Changed in: kernel-sru-workflow/automated-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
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
--
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/1788755
Title:
linux-azure: 4.15.0-1023.24~16
Thanks for testing, Sarah. I'll submit an SRU request to have this
commit included in Trusty.
This regression was introduced by the following mainline commit:
7dac4a1726a9 ("ext4: add validity checks for bitmap block numbers")
This commit was added to mainline in version v4.17-rc1. However, the
** Changed in: linux
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1247723
Title:
[Samsung NP900X3C-A02US] Lid state changes not detected
Status
** Summary changed:
- linux-azure: -proposed tracker
+ linux-azure: 4.15.0-1023.24~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canoni
I built a test kernel with a revert of commit
af8a41cccf8f469165c6debc8fe07c5fd2ca501a. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
* If the test kernel is p
sorry that I thought I have already sent this patch upstream, but
apparently I didn't.
(In reply to Francisco Cribari from comment #263)
> Has this been fixed upstream? Despite what we read at
>
> https://www.systutorials.com/linux-kernels/59801/acpi-ec-fix-regression-
> related-to-triggering-
Thank you for looking into logs!
> so, when you say normal boot, you mean a cold boot, say, in 4.17.0 kernel,
> shutdown the machine, and then power on the machine manually to boot into
> 4.9.3 kernel, right?
Yes.
> If this is true, we are still able to confirm the good and bad kernel, by do
> c
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated
for Linux 4.9.3 normal boot
7: 4945 1476 1820275 IR-IO-APIC 7-fasteoi
INT3432:00, INT3433:00
for Linux 4.9.3 boot after Linux 4.17.0
7: 327339 48015 802942 21344 IR-IO-APIC 7-fasteoi
INT3432:00, INT3433:00
yes. there is indeed an interrup
** Changed in: kernel-sru-workflow/automated-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
On 08/28/2018 09:49 AM, Joseph Salisbury wrote:
> This is probably the fix:
> 22be37acce25 ext4: fix bitmap position validation
>
> I built a test kernel with commit 22be37acce25. The test kernel can be
> downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1789131
>
> Can you test this ke
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788744
Title:
linux: 4.15.0-34.37 -proposed tr
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/1789465
Title:
BUG: scheduling while atomic:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
1 - 100 of 226 matches
Mail list logo
