** Changed in: linux-firmware (Ubuntu)
Importance: Undecided => Critical
** Changed in: linux-firmware (Ubuntu Bionic)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://lists.ubuntu.com/archives/kernel-team/2019-May/100831.html
** Description changed:
- LTP: starting af_alg06
- BUG: unable to handle kernel paging request at 9cbe
- IP: sha256_transform+0x28/0x1b20
- PGD 4d341067 P4D 4d341067 PUD 4d345067 PMD 4d346067 PTE 0
- Oops:
It should be safe.
Let's see if it's already fixed upstream, before bisecting between two
older kernel versions.
--
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/1826461
Title:
Suspend
Yes I am aware of the stale bug problem and have been on both ends.
But as the number of open bugs decreases (at least in some components),
the problem should happen less:
https://docs.google.com/spreadsheets/d/e/2PACX-
1vRDHPxGBHqM6XkT_S8ggtYfD0xchKSUD_z9PopNVE3G1rU05fVSnxDGcDsEstl7gu7N-
** Also affects: network-manager (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/1828134
Title:
Wifi not working after suspend/resume
Please confirm the issue doesn't happen on previous kernel versions.
--
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/1829679
Title:
Resolution stuck at 1024x768
Status in linux package
Laptops are almost always wired with only the Intel GPU connected to the
LCD. If there is an Nvidia GPU then it is not connected to the screen;
it only shares rendered frames with the Intel GPU via system memory.
This allows the Nvidia GPU to be completely turned off without losing
the screen or
The reason I ask this is that launchpad has an unfortunate approach to
issue management (these two that you have been communicating in are a
welcome change - thanks) where bugs go stale for years or are dropped
due to lack of engagement from maintainers.
--
You received this bug notification
Does the actually network speed affected by this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1830090
Title:
Cannot reach 1300Mbps using DW1830 (BCM943602BAED) with
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1818797
Title:
Xenial update: 4.4.172 upstream stable release
re:nomodeset: That's odd unless the drivers on the live usb media are
old; nomodeset is definitely needed to not lock up from the live usb on
this machine.
re:grubmenu: I'm not using UEFI, so AFAIU, shift should be the key
(though I tried both). Is it edge triggered? If not, I've had the key
held
** 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/1827822
Title:
kernel null pointer dereference
Status in linux
Passed with Cosmic i386 with proposed kernel.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages,
I think it's appropriate to stay Incomplete because this is essentially
just a kernel bug, in the nouveau driver.
Option (b) above isn't directly relevant, but might be a workaround,
even permanently. Any proper solution to this bug requires testing of
option (a) in comment #4. So still
Please undo the incomplete. The action that was asked for was performed
in the comment #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/1830029
Title:
nouveau driver for nvidia is
Your Intel GPU, which usually is the only GPU wired directly to the
laptop screen, requires modesetting to be enabled. I recall old versions
of the Nvidia driver did not like that, but current versions do. I think
"current" includes Ubuntu 18.04.
As for the grub menu, yes it might have become
I will give that a go. The nomodeset option was set during istall,
presumably because the live usb install media doesn't boot without it. I
vaguely recall altering that option at the grub menu, but it was a long
day yesterday, so I am not sure (as an aside, why does the grub menu not
come up with
** Tags added: sts
--
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/1779756
Title:
Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu
18.04)
Status in linux package in
** Tags added: sts
--
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/1814095
Title:
bnxt_en_po: TX timed out triggering Netdev Watchdog Timer
Status in linux package in Ubuntu:
** Tags added: sts
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic verification-done-cosmic
** Tags removed: verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: sts
--
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/1794232
Title:
Geneve tunnels don't work when ipv6 is disabled
Status in linux package in Ubuntu:
Fix Released
Please test this dkms under 5.0 kernel, if the sound changes better?
To install this deb:
sudo dpkg -i oem-audio-xxx.deb
reboot
check your sound
To remove this deb:
sudo dpkg -P oem-audio-hda-daily-dkms
reboot
** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb"
** Package changed: gdm3 (Ubuntu) => nvidia-graphics-drivers-390
(Ubuntu)
** Tags added: nvidia
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
Your kernel log in comment #2 is showing a lot of crashes in the nouveau
kernel driver. The best and only remedies for that are:
(a) Install a newer kernel or just install a newer version of Ubuntu.
Ubuntu 19.04: http://releases.ubuntu.com/19.04/ or kernel packages:
The same on Lenovo desktop, had to downgrade to 4.4.0-146.
Kernel driver in use: i915
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1829657
Title:
Ubuntu 16.04 with kernel
You appear to be using a kernel parameter ('nomodeset') which will
definitely break the nouveau driver and prevent it from working. To fix
this, please:
1. Edit /etc/default/grub and remove 'nomodeset'.
2. Run: sudo update-grub
3. Reboot
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
**
You have been subscribed to a public bug:
Installing the nvidia-driver-390 package and disabling (or not) the
nouveau drivers results in a system that superficially appears to busy
hang before reaching the login screen, leaving only the fsck
"/dev/sda1: clean,..." message on the screen.
The
It is likely this bug has already been fixed in a newer version of
Ubuntu.
Please try live booting these from USB to see if they have the same
problem (open the 'Cheese' app to test the camera):
* 18.04 LTS: http://releases.ubuntu.com/18.04.2/
* 19.04: http://releases.ubuntu.com/19.04/
--
Thanks. It appears the kernel doesn't detect/support your camera, so I
am reassigning this bug to the kernel.
** Summary changed:
- Getting raedon error when booting
+ Camera is not detected
** Summary changed:
- Camera is not detected
+ [HP ProBook 450 G0] Camera is not detected
** Package
You have been subscribed to a public bug:
I am trying to use the nouveau drivers on a recent (today) install of
18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work at
all.
What I am finding is that the sluggishness of the display is comparable
to the case when nouveau drivers
You have been subscribed to a public bug:
Camera is not detecting in my laptop
hp450
Ubuntu 16.04
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177
Uname: Linux 4.4.0-148-generic x86_64
Ubuntu 18.10 (which does not have the bug) uses kernel version 4.18 so
please start testing versions around there. If you find 4.18 fixes the
bug then next please find a version roughly halfway between 4.18 and
5.0.0 ...
--
You received this bug notification because you are a member of Kernel
Patch submitted upstream:
https://www.spinics.net/lists/netdev/msg571753.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829652
Title:
Kernel panic upon resetting ixgbe SR-IOV VFIO
With chance of regression quite low, we will not remove this particular
fix prior to release
--
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/1824259
Title:
Headphone jack switch sense is
Hello David, any new information on this problem?
--
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/1828134
Title:
Wifi not working after suspend/resume cycle
Status in linux package in
Do I have to downgrade my system from Dingo to Cosmic in order to test
this in Cosmic, to keep my bug from being closed?
May 20, 2019 7:02 AM, "Ubuntu Kernel Bot" wrote:
> This bug is awaiting verification that the kernel in -proposed solves
> the problem. Please test the kernel and update this
Hi Kai-Heng Feng, thanks for your time.
I would like to help but I have never installed mainline kernel before. Is it
safe? Is it necessary since we know that this bug appeared after upgrade from
Ubuntu 16.04 to 18.04 (so it didn't affect kernels before 4.15)? This is my
only laptop and it is
Chris, thanks for confirming which processor is in use.
To force downgrade the microcode package on bionic, do:
sudo apt install intel-microcode=3.20180312.0~ubuntu18.04.1
For other releases, you will need to replace the version with what
version(s) are available for your release; you can use
^^^ sorry this cpuinfo was off a ux433fn booted on an affected kernel
with dis_ucode_ldr
--
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/1829620
Title:
intel-microcode on ASUS makes
Steve, Mark, I've had bios version 302 installed since the 5th of April
and was booting fine until the apt-get upgrade run on the 21st of May
note in my proc/cpuinfo the microcode version is listed as 0x98
also how do you force a downgrade of the microcode package?
** Attachment added:
Intel microcode update definitely created same issue for me on Asus
Zenbook 14 (UX433F) on 18.04.2 LTS.
Can also confirm the instructions above "add dis_ucode_ldr to the kernel
command line (from GRUB if you cannot boot)" worked perfectly for
temporary workaround.
This is my fourth Asus, and
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 1830116
and then change the status of the bug to 'Confirmed'.
If, due to the
** Package changed: linux-meta (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/1830116
Title:
linux-generic: missing module intel_pmc_core
Status in linux
Public bug reported:
Description:
linux-5.0.0-15-generic has missing module named 'intel_pmc_core' for device:
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC
[8086:9d21] (rev 21)
Similar bug #1730770 ?
Release: 19.04
** Affects: linux (Ubuntu)
Importance:
Couldn't find a bug, but it's described as a known issue here:
https://blogs.gnome.org/uraeus/2019/04/03/preparing-for-fedora-
workstation-30/
Given the description above it seems to be waiting on a new nvidia
driver - still an issue on 430.14.
--
You received this bug notification because you
In
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826125/comments/53
it is mentioned that the same laptop with PCLinuxOS with 5.0.2 doesn't
flicker. Is it worth it getting some data from there perhaps?
--
You received this bug notification because you are a member of Kernel
Packages,
(In reply to Paulo J. Matos from comment #11)
> Created attachment 144319 [details]
> rc5+ kernel with enable_psr=0
The log was cut off so couldn't see that PSR was in fact disabled. You
can fix that by passing eg. log_buf_len=2M to the kernel cmdline.
Anyways, after a second glance at the logs
Hmm, yes 4.32 is what the BIOS uses, so this might even help:
[1.391106] [drm:intel_dump_pipe_config [i915]] port clock: 432000, pipe src
size: 3840x2160, pixel rate 533299
Hmm. That probably means this is a victim of commit f11cb1c19ad0
("drm/i915/dp: revert back to max link rate and lane
Timo, I have attached the dmesg with rc5+ kernel you asked me to 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/1826125
Title:
Dell XPS 13 9380 flickering (Whiskey Lake)
Status
Created attachment 144325
[PATCH] hack: Disable 5.4ghz link rate for skl
This should drop the link rate to 4.32ghz, which is the lowest we can go
with this panel. Please test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Created attachment 144319
rc5+ kernel with enable_psr=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/1826125
Title:
Dell XPS 13 9380 flickering (Whiskey Lake)
Status in Linux:
(In reply to Ville Syrjala from comment #9)
> [4.550517] [drm:intel_dp_hpd_pulse [i915]] ESI: 41 00 00 00 00 00 00 00
> 00 00 00 00 81 01
>
> According to that the sink thinks everything is fine, so no idea why
> generates short hpds.
>
> Could be some kind of PSR fail. Please try passing
[4.550517] [drm:intel_dp_hpd_pulse [i915]] ESI: 41 00 00 00 00 00 00
00 00 00 00 00 81 01
According to that the sink thinks everything is fine, so no idea why
generates short hpds.
Could be some kind of PSR fail. Please try passing i915.enable_psr=0 to
the kernel cmdline.
--
You received
Created attachment 144318
Timo rc5+ kernel dmesg
--
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/1826125
Title:
Dell XPS 13 9380 flickering (Whiskey Lake)
Status in Linux:
Incomplete
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Confirmed
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
**
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-certification-testing
Status: New => Confirmed
**
The attachment "kexec-tools_2.0.16-1ubuntu3.1.debdiff" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the
** 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
kernel bugs:
amd64
ubuntu_kvm_unit_tests: (1821390): apic-split will fail in kvm_units_tests,
(1821394): vmx tests fail in kvm_unit_tests, (1822308) vmx_hlt_with_rvi_test in
kvm_unit_tests fails
ubuntu_ltp_syscalls: (1819116): sync_file_range02 in ubuntu_ltp_syscalls fails
C/D
arm64
You might be experiencing an issue caused by the way Windows handles
powering off the sound card. Restarting from Windows yields a non-
functioning sound card in Linux. A full shutdown from Windows and
subsequent power-on will allow sound to work in Linux.
This bug report is for the UX391UA and
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-aws (Ubuntu)
--
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/1821152
Also, I'm still able to boot any kernel (with no extra boot params) when
I force-downgrade the intel-microcode to 2018 version (from bionic/main)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.17/
so I have tested with a kernel from this PPA and it did not help.
Tyler,
there's one strange thing I'd like to ask: the boot process behaves
stateful(?!), ie. I can get into a previous "clean"/"dirty" state (and at least
liquorix)
affects cosmic, AWS cloud, 4.18.0-1017.19-aws
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Cosmic)
Status: New => Incomplete
** Changed in: linux-aws (Ubuntu)
Status: New => Confirmed
** Changed in: linux-aws
** 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
Side note: the issue is fixed in nvidia-430.14
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1827944
Title:
Kernel 5.1 is unsupported (and nvidia-418.56 error) [error:
initialization
Testing Results:
monotonic_time: (1774959): clock test in monotonic_time will fail on Azure
Instances
ubuntu_kernel_selftests: (1829812): ubuntu_kernel_selftests [net] ubuntu_bpf
test case fails to build on disco, (1830084) :ubuntu_kernel_tests ftrace fails
on disco, linux-azure
As per upstream in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063038/comments/27
the device is rate limited in firmware intentionally. Hence, while it is
technically possible to override this from a firmware perspective (i.e.
Acer+Broadcom would release a firmware update), from a linux
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/1063038
** No longer affects: 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/1063038
Title:
Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.
Status in linux
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Remote watch: Email to netdev@vger # => None
--
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/1063038
Title:
affects linux-azure 5.0.0-1007.7
--
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/1821152
Title:
lxc-test-no-new-privs failed with Temporary failure resolving
'archive.ubuntu.com'
You have been subscribed to a public bug:
I've got a device with a Broadcom 57780 ethernet NIC. It uses the tg3.ko
driver module. The problem is that this NIC cannot connect at gigabit
(1000MBps) speed. In all cases connection works well at 100MBps.
Following are the tests I've completed:
-
** Tags added: sts
--
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/1824981
Title:
cifs set_oplock buffer overflow in strcat
Status in linux package in Ubuntu:
Fix Released
Bug
> or you've recently installed a BIOS update which contains the latest microcode
revision and the kernel microcode loader didn't do anything.
Asus published BIOS version 302 for your laptop on 2019-04-02
(https://www.asus.com/Laptops/ASUS-ZenBook-14-UX433FN/HelpDesk_BIOS/).
I really have
*** This bug is a duplicate of bug 1824981 ***
https://bugs.launchpad.net/bugs/1824981
** This bug is no longer a duplicate of bug 1813928
kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!
** This bug has been marked a duplicate of bug 1824981
cifs set_oplock buffer
*** This bug is a duplicate of bug 1824981 ***
https://bugs.launchpad.net/bugs/1824981
This LP is a duplicate for #1824981 - I'll mark it as dup.
Thanks,
Guilherme
** Tags added: sts
** This bug has been marked a duplicate of bug 1824981
cifs set_oplock buffer overflow in strcat
--
On 2019-05-22 17:13:02, Mark wrote:
> > This may be a bug in how the kernel is loading the microcode
>
> can you review the liquorix patches? Their kernel boots with said
> microcode.
I compared the arch/x86/ source code directories in the liquorix and
Ubuntu kernels. While there are a large
Please close. Does not reproduce on 19.04
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1063038
Title:
Broadcom
Update: the sound problem on UX430U is intermittent. Sometimes it works,
sometimes it is gone. I haven't been able to see a clear pattern so far.
This is definitely not a hardware problem since everything works rock
solid under Windows (I have a dual boot).
--
You received this bug notification
I have the same problem on Asus Zenbook UX430U. Upgrading to kernel
4.20.16 using ukuu did not fully solve the problem. It worked after the
first boot, but no longer works after restarting.
Should I open a separate bug?
--
You received this bug notification because you are a member of Kernel
Patch submitted for SRU:
https://lists.ubuntu.com/archives/kernel-team/2019-May/100825.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1827755
Title:
nx842 - CRB request time out
** 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.
> To avoid confusion, we need to be clear that the i7-8565U is a Whiskey
Lake processor (*not* a Kaby Lake)
yep, sorry, I got confused in the intel naming scheme, it's whiskey I'm
having problems with ;)
> This may be a bug in how the kernel is loading the microcode
can you review the
Mai 22 15:01:29 kevin335200 kernel: brcmfmac: brcmf_fw_map_chip_to_name: using
brcm/brcmfmac43602-pcie.bin for chip 0x00aa52(43602) rev 0x01
Mai 22 15:01:29 kevin335200 kernel: brcmfmac :03:00.0: Direct firmware load
for brcm/brcmfmac43602-pcie.txt failed with error -2
Mai 22 15:01:31
.debdiff attached to this comment for sponsorship consideration to
Bionic.
** Patch added: "kexec-tools_2.0.16-1ubuntu1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1828187/+attachment/5265778/+files/kexec-tools_2.0.16-1ubuntu1.1.debdiff
** Description changed:
+
.debdiff attached to this comment for sponsorship consideration to
Cosmic, adding SRU paperwork to original bug description.
** Patch added: "kexec-tools_2.0.16-1ubuntu3.1.debdiff"
** Description changed:
+ [Impact]
+ PowerPC 842 hardware compression support is currently broken, this effects
workloads like zswap and others that exploit 842 hardware compression on Power.
+
+ [Test]
+ - Install nx-compress and nx-842-powernv modules
+ - Initiate NX request
+ - Uninstall
Public bug reported:
I cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware, only
985Mbps maximum.
It works under win10.
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- I cannot reach 1300Mbps using DW1830
On Wed, May 22, 2019 at 8:41 AM Paolo Pisati <1823...@bugs.launchpad.net> wrote:
>
> I realize this is just a workaround (and the above 31M cma memory
> fragmentation is ugly), but we should definitely bump CMA allocation
> space: definitely 32M (since that's what upstream default to) but if 64M
>
affects disco, 5.0.0-1007.7 linux-azure
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "ltp_syscalls-azure-disco"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1819116/+attachment/5265775/+files/ltp_syscalls-azure-disco
I was able to speak with folks at Intel about this and got some good
info from them:
* To avoid confusion, we need to be clear that the i7-8565U is a Whiskey
Lake processor (*not* a Kaby Lake)
-
Hi,
I have upgraded to Ubuntu 19.04 and Kernel 5.0, The sound is still the same
with overamplification disabled.
Is the fix for the audio driver uploaded ??
Regards,
Phaneesh
On Wed, May 22, 2019 at 7:45 AM Hui Wang wrote:
> @Phaneesh,
>
> Could you please install the ubuntu 5.0 kernel, then
The attachment "bionic_d-i.debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and
@agiani, are you using in PCLinuxOS any kernel options?
--
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/1826125
Title:
Dell XPS 13 9380 flickering (Whiskey Lake)
Status in Linux:
affects , linux-azure 5.0.0-1007.7
** Tags added: 5.0.0
--
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
Status in
** 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 --
Affects: Disco, 5.0.0-1007.7 linux-azure
** Summary changed:
- Regression for ubuntu_bpf test case fails to build on disco
+ Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case fails to
build on disco
--
You received this bug notification because you are a member of Kernel
Here's my /proc/cpuinfo
** Attachment added: "cpuinfo.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/+attachment/5265773/+files/cpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This is coming up on the azure kernel as well. Various instance flavor
types:
05/20 14:12:08 DEBUG| utils:0153| [stdout] make[2]: Leaving directory
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/lib/bpf'
05/20 14:12:08 DEBUG| utils:0153| [stdout] gcc -Wall -O2
1 - 100 of 226 matches
Mail list logo
