--- Comment From heinz-werner_se...@de.ibm.com 2019-04-11 02:47 EDT---
IBM Bugzilla status -> closed, this problem could not be reproduced . If such
situation will take place again a new LP will be opened. Many thx
--
You received this bug notification because you are a member of Ker
No, sorry.
** Attachment added: "dmesg_new"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813537/+attachment/5254881/+files/dmesg_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/
Just tested, the voice recorded is OK.
But there is some difference between 19.04 and 18.04, after installing
18.04, the aplay/arecord default device pulseaudio, while after
installing the 19.04, the aplay/arecord default device is hw sound card.
Please install 19.04 to a different machine (not x
Public bug reported:
# TESTNAME=realmode TIMEOUT=90s ACCEL= ./x86/run x86/realmode.flat -smp 1
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial
stdio -device pci-testdev -machine accel=kvm -k
No security relevant fixes, should not go to the trusty-security pocket.
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Public bug reported:
# TESTNAME=emulator TIMEOUT=90s ACCEL= ./x86/run x86/emulator.flat -smp 1
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial
stdio -device pci-testdev -machine accel=kvm -k
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Invalid
** 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:
htt
Public bug reported:
# TESTNAME=eventinj TIMEOUT=90s ACCEL= ./x86/run x86/eventinj.flat -smp 1
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial
stdio -device pci-testdev -machine accel=kvm -k
It's not a kernel bug. Multitouch works under Wayland but not under
Xorg.
The multitouch can work with libinput:
Section "InputClass"
Identifier "Wacom USB touchscreen class"
MatchUSBID "056a:490a"
MatchDevicePath "/dev/input/event*"
MatchIsTouchscreen "true"
Public bug reported:
# TESTNAME=ioapic TIMEOUT=90s ACCEL= ./x86/run x86/ioapic.flat -smp 1 -cpu
qemu64
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial
stdio -device pci-testdev -machine acc
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => In Progress
--
Y
** 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-testi
** Also affects: thermald (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1815214
Title:
Lenovo T480: throttling CPU issue
Status
Affects my Lenovo X1 6th gen as well
--
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/1815214
Title:
Lenovo T480: throttling CPU issue
Status in linux package in Ubuntu:
Confirmed
Bug
The Bluetooth controller wakes up early when USB Controller is trying to
suspend.
Please enable LE privacy before suspend, and see if it helps:
$ btmgmt power off
$ btmgmt privacy on
$ btmgmt power on
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Did this ever happen to kernel v4.4, which is kernel for 16.04?
--
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/1823346
Title:
SD card stays locked even when unlocked
Status in linux pac
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 1824259
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Most of the time you need only "linux-image-4.9.0+_4.9.0+-1_amd64.deb".
But if you have also some dkms based modules installed, you may want to
install linux-headers-* as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
This is actually a kernel bug, in Linux. The issue is the absence of
platform data for this particular board in the snd_soc_rt5645 module.
The issue can be worked around by creating
/etc/modprobe.d/hacksound.conf with the following contents:
# Invert jack detection (1) and use detection mode 2 (2
Ok, I have retried to bitsect under main kernel 4.8.0 for 16.04.02 LTS instead
installed on 4.9-rc8.
Using:
$ git bisect good v4.9-rc8
$ git bisect bad v4.10-rc8
I have built kernel under 4.8.0 with default (Enter) options becouse I don't
know nuances in them yet.
I have got many files from kerne
This may be a kernel driver bug, and a regression from 4.12. See
http://www.lattepanda.com/topic-p24689.html?sid=1fa88916eb19dd9d65e0abd3ecbf6210#p24689
This may be a missing piece of platform data in the kernel that would
tell it to invert jack detection on this particular board. I will try
testi
[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
--- Comment From mranw...@us.ibm.com 2019-04-10 23:12 EDT---
Hi Manoj,
Looks good, I think, here's some output:
mranweil@ltc-wspoon5:~$ cat /proc/version
Linux version 4.15.0-48-generic (buildd@bos02-ppc64el-015) (gcc version 7.3.0
(Ubuntu 7.3.0-27ubuntu1~18.04)) #51~lp1822870+build.2-Ubu
If I save the ALSA state with the headphones unplugged to a file:
sudo alsactl --file=settings-out.txt store
And then plug in the headphones and restore it:
sudo alsactl --file=settings-out.txt restore
I still get no sound. But then diffing the final state against the
unplugged state did find t
Suffering from this bug in a Dell XPS 9360 with Killer WiFi. It happened
in 18.10 and still happens in 19.04. :/
--
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/1799988
Title:
Missing wif
Public bug reported:
My machine is a LattePanda board, which uses a "chtrt5645" device as a
sound card. It has a single headphone output jack, which I think is a
TRRS jack, with a mic input, such as is normally used on phones.
When I don't have headphones plugged in, the system thinks headphones
Hmm, actually, if the problem did get worse or more common in 19.04 then
we should use bug 1822179 instead.
Certainly after July [1], Ubuntu 18.10 won't be relevant any more.
[1] https://wiki.ubuntu.com/Releases
** Summary changed:
- [nvidia] After resume the unlock screen is a black background
here's the bottom of journalctl -b -1 from a boot with
"usbcore.dyndbg=+p" that reproduced the issue (let me know if there's a
better way to get the kernel log you're looking for):
Apr 10 17:31:18 taplop systemd-sleep[8074]: Suspending system...
Apr 10 17:31:18 taplop kernel: PM: suspend entry (de
** Attachment added: "full kernel log from that boot extracted via: journalctl
-b-1 -k > kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823029/+attachment/5254820/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Michael,
I have test kernel with the patches cherry-picked/backported to 4.15
bionic. We do not have a dd2.3 hw in-house, could you please validate that
this kernel works for you and report back in the bug report?
https://launchpad.net/~ubuntu-power-triage/+archive/ubuntu/lp1822870/
Once I get
Running Ubuntu 18.04.1 LTS with Workstation 12.5.9 installed.
Encountered the dreaded error:
/usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
symbol `clock_gettime'
Following @iLugo directions exactly, VMware Works
** 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/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
Might be a duplicate of this bug?:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820
--
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/1824216
Title:
Linux 5.0 regression i915 mo
** 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/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/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/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
** Description chan
Here's a link to the Fedora bug report tracking the same issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1695275 which also includes
lots of useful information.
** Bug watch added: Red Hat Bugzilla #1695275
https://bugzilla.redhat.com/show_bug.cgi?id=1695275
--
You received this bug notif
Unfortunately due to the nature of this bug, it's very hard to get any
concrete logs (at least I'm not sure how to). If I boot with kernel
modesetting for i915, then I can't even get to the ttys to pull down a
dmesg. I'd rather not install 19.04 (wiping out my existing 18.10
installation) to trac
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** 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.
F
Public bug reported:
SRU Justification
Impact: Support for snapdragon was split out from the linux package into
a linux-snapdragon package, so linux-signed should no longer produce any
packages for snapdragon. They aren't causing problems currently but need
to be removed.
Fix: Remove the snapdra
** Tags added: aws azure bionic
** Tags removed: aws
** Tags added: kvm
** Summary changed:
- LXC test on KVM instances failed with Temporary failure resolving
'archive.ubuntu.com'
+ lxc-test-no-new-privs failed with Temporary failure resolving
'archive.ubuntu.com'
--
You received this bug n
** Changed in: kernel-sru-workflow/regression-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 se
** Tags added: regression-testing-passed
--
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/1822790
Title:
linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker
Status in Kernel SRU W
also affects bionic, linux-azure 4.18.0-1015.15~18.04.1
** Tags added: bionic
--
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/1824228
Title:
ept test fails in kvm_unit_tests
Statu
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** 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.
F
** 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-sta
** 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-sta
** 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
backports: bug 1823224 (bionic/li
appears to affect linux-azure: 4.18.0-1015.15, Standard_F2s_v2-ubuntu_lxc
04/05 16:42:33 DEBUG| utils:0153| [stdout] FAIL: lxc-tests:
lxc-test-no-new-privs (37s)
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/regression-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 se
** Tags added: regression-testing-passed
--
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/1822791
Title:
linux-azure: 4.18.0-1015.15 -proposed tracker
Status in Kernel SRU Workflow:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** 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.
F
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Fix Committed
** Tags adde
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Fix Committed
** Tags adde
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
**
Affected instances:
Standard_D2s_v3
Standard_D2_v3
Standard_DC2s
Standard_E2s_v3
Standard_F2s_v2
--
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/1824228
Title:
ept test fails in kvm
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
**
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Fix Committed
** Tags adde
Public bug reported:
Reproducible: Yes,
Series: cosmic
Kernel: "linux-azure 4.18.0-1015.15"
Steps:
1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib
2.) git clone --depth=1
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
3.) cd kvm-unit-tests; ./configure; m
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
**
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 1824216
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1821394
Title:
vmx tests fail in kvm_unit_tests
St
Public bug reported:
On my Dell XPS 9575, I get a black screen on boot when running the 19.04
live image, OR after updating from 18.10 to 19.04. It appears to be a
kernel related bug that was introduced in 5.0 that is affected by
certain laptop panels not conforming to their stated specifications
** 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/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(o
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** 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
On Wed, Apr 10, 2019 at 11:01 AM Ard Biesheuvel
wrote:
>
> On Tue, 9 Apr 2019 at 16:30, dann frazier wrote:
> >
> > Yeah, no crash anymore - thanks Ard!
> >
> > ubuntu@d06-4:~$ echo function | sudo tee
> > /sys/kernel/debug/tracing/current_tracer
> > function
> > [ 72.778123] ftrace: far branc
Ok, I meant "still present in Ubuntu 19.04" in the last comment :D
Also worth mentioning: the "sudo modprobe i2c-i801" fix also restores
the two-finger-tap right clicking behavior, which was also broken
alongside two-finger scrolling. But there was no three-finger-tapping
instead, so unlike the ca
For Robin (brobert420), who in comment #69:
> Commenting out blacklist i2c_i801 did end with mouse not working at all after
> wakeup […]. I got an L440. Ubuntu 18.04 4.19rc1
I had the same problem with a ThinkPad T440s on Ubuntu 19.10 beta. (Just
that there was no blacklist entry in /etc/modprob
** Bug watch added: freedesktop.org Bugzilla #110360
https://bugs.freedesktop.org/show_bug.cgi?id=110360
--
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/1747463
Title:
kernel crashes d
https://bugs.freedesktop.org/show_bug.cgi?id=110360
--
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/1747463
Title:
kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X
Stat
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
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/1822871
Title:
enabling ftrace on Hi1620 CS causes an Oop
Does booting with amdgpu.runpm=0 on the kernel command line help?
--
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/1747463
Title:
kernel crashes during boot unless IOMMU is disabled on Ryz
I searched a bit about the changes in the kernel. I've found that :
https://lore.kernel.org/patchwork/patch/1030491/
I don't know the C language but if it can help.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
This is probably a packaging problem on the nvidia drivers rather than a
bug in Ubiquiuty. Moving there for more ideas.
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubiquity (Ubuntu)
--
You received this bug notificati
This linux-nfs list member found the origin of the problem:
https://marc.info/?l=linux-nfs&m=155480197614448&w=2
--
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/1824050
Title:
access.W_OK
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** 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.
F
** 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-testi
** 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
** 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-testi
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
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/1823862
Title:
disco: unable to use iptables/enable ufw under -virtu
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** 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.
F
** 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
backports: bug 1822817 (xenial/li
On Tue, 9 Apr 2019 at 16:30, dann frazier wrote:
>
> Yeah, no crash anymore - thanks Ard!
>
> ubuntu@d06-4:~$ echo function | sudo tee
> /sys/kernel/debug/tracing/current_tracer
> function
> [ 72.778123] ftrace: far branches to multiple entry points unsupported
> inside a single module
>
> ^ I
** Description changed:
+ SRU Justification
+
+ Impact: iptables does not work in disco with linux-virtual.
+
+ Fix: Add bpfilter to the generic inclusion list.
+
+ Regression Potential: There are no code changes and thus minimal
+ potential for regressions.
+
+ Test Case: Verify that bpffilte
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Public bug reported:
[Impact]
Transmit errors may occur under load, resulting in device reset and an unusable
NIC.
[Test Case]
Server:
ethtool -K enp129s0f0 rx off
ethtool -K enp129s0f0 gro off
ifconfig enp129s0f0 mtu 1501
iperf -s
Client:
ethtool -K enp129s0f0 tx off
ethtool -K enp129s0f0 gso
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1822824
Title:
linux-aws: 4.4.0-1080
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 1823862
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Tested with the kernel+modules linked in #22
I can confirm I was able to enable ufw and query the installed iptables
rules:
$ uname -a
Linux juju-0f0cbd-disco-testing-38 5.0.0-10-generic #11+lp1823862v201904100938
SMP Wed Apr 10 14:40:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
$ sudo ufw enable
--- Comment From leona...@ibm.com 2019-04-10 12:08 EDT---
(In reply to comment #68)
> In comment #22 above, it states that "In a meeting with lagarcia, I was
> informed this patch is very important, and that it is already on kernel
> 4.18-15 onwards."
>
> So, I assume that the required patc
E
Date: Wed Apr 10 16:29:38 2019
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd quiet splash --- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190410)
ProcEnviron:
TERM=xterm-256color
allCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd quiet splash --- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190410)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UT
Hey. Cool.
Yea. I have a key board combination now which uses the xrander command, so
I have a work around. But the oled screen is not working on linux in
general because of the backlight issue. oled has no backlight.
What I find strange is that lenovo is not doing anything.
For example here. On
As i wrote i still use parameters.
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2
For me i couldn't boot with anything other then pci=noacpi before, but now ivrs
parameters work and i got a working touchpad.
"Things seem to work" is because i have only used the laptop for a day and i
haven't teste
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: New => Invalid
** 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:
** 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-testi
1 - 100 of 190 matches
Mail list logo
