-
Notifications
You must be signed in to change notification settings - Fork 15
Linux 6.4.2 #264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux 6.4.2 #264
Conversation
…flags BugLink: [Replace -fcf-protection=none patch with new version] The gcc -fcf-protection=branch option is not compatible with -mindirect-branch=thunk-extern. The latter is used when CONFIG_RETPOLINE is selected, and this will fail to build with a gcc which has -fcf-protection=branch enabled by default. Adding -fcf-protection=none when building with retpoline support to prevents such build failures. Signed-off-by: Seth Forshee <[email protected]>
Signed-off-by: Andy Whitcroft <[email protected]>
BugLink: http://bugs.launchpad.net/bugs/1585311 Signed-off-by: Andy Whitcroft <[email protected]> Acked-by: Tim Gardner <[email protected]> Acked-by: Brad Figg <[email protected]> Signed-off-by: Kamal Mostafa <[email protected]>
Ubuntu's mainline kernels have been missing config, this commit adds the missing configs set to the default recommended config from the kernel. Once Ubuntu's mainline kernels startbuilding correctly it is likely best to adopt their changes and drop this commit as well as `base packaging` commit and pull `base backaging` from their branch. Below is a lost of changes: `ANDROID_BINDER_IPC` that has changed to be mandatory, as such is is a `y`, but others are same as 6.0.6 fix decnet fix adp5588 fix cpia2 fix ZR364XX fix TM6000 fix vaio picturebook fix HEIUM fix siemens nixdorf fix SAA7146 DVB cards fix kselftests fix AV7110 cards fix syntek camera fix firewire serial fix supported serial port count add android binder ipc fix rave sp eeprom --- Add CONFIG_INET_TABLE_PERTURB_ORDER > The default is almost always what you want. Only change this if you know what you are doing. Kernel docs say to leave the default. We will do the same here, https://cateee.net/lkddb/web-lkddb/INET_TABLE_PERTURB_ORDER.html --- Add kernel config for Intel MAX10 BMC Secure Update driver Add CONFIG_TEST_MAPLE_TREE=n
My oryp9 also froze in Integrated graphics mode with my USB-C docking display plugged in. |
I wonder if any of our patches are causing this. I could open a separate branch without our patches. |
Also, I wonder if disabling system76-power would prevent this if it's something related to runtime power management. |
Sounds good, I can give it a go. I suppose it could also be my install though. I could throw in a second drive and see if it happens on a fresh install |
Updates packaging information to reflect that WireGuard kernel support is present. Co-authored-by: thomas-zimmerman <[email protected]>
Signed-off-by: Michael Aaron Murphy <[email protected]>
Signed-off-by: Michael Aaron Murphy <[email protected]>
The pin fixup is required to detect headset microphones on the oryp5. Fixes: 80690a2 ("ALSA: hda/realtek - Add quirk for Tuxedo XC 1509") Signed-off-by: Tim Crawford <[email protected]>
Asus released motherboard(s) with an alternate ALC4080 that lacks a SPDIF jack, and requires applying this map.
The Aorus Xtreme uses the same ID for audio controller, but the maps are very different. This successfully fixes all of the audio jacks on the back.
When plugging of unplugging an audio jack on this motherbaord, sometimes the audio jacks would stop appearing to pipewire/pulseaudio. Interestingly `cat`-ing out the file `/proc/asound/<card number>/codec#0`, and or restarting pipewire fixes the issue temporarily. This PR improves the current functionality by making hotplug with one 3.5mm jack work, it still breaks if hotplug is between multiple jacks though.
https://www.phoronix.com/news/MGLRU-Reaches-mm-stable By cummunity request #214 (comment)
This bug is tricky. To summarize what I've found so far:
For testing, I'm playing a video in Firefox, as well as adding a bit of load with |
mm interesting. My observations with completely different hw: Have a newer NV card (RTX3060 or 3090), it is enough to scroll wrong in firefox wth a video playing, and the whole sys frezes. This is annoying. The same with a GTX1660, no issue. All on AMD m/b, B550 or X570 with R9-3900X..R9-5950X. And this since at least 6.0. I am happy on the GTX1660 box, the others not so much. |
Any difference if using our 535 NVIDIA driver? |
Ah, forgot to mention that. 535 vs 525 doesn't seem to make any difference. The darp8 & darp9 didn't even have the Nvidia driver installed. |
One thing you might want to look at before releasing this is the possible bug related to PER_VMA_LOCK functionality - it appears to cause issues with user-land programs (crashing in bad ways) - see: https://bugzilla.kernel.org/show_bug.cgi?id=217624 They point to a mailing list with possible patches (possibly a combo of patches plus partial combo fixes |
I see a recommendation to revert 0bff0aa, we can try it |
Here is a simplified patch: https://lore.kernel.org/all/20230703182150.2193578-1-surenb%40google.com/ |
Hunting through the email chain on lore - I see this finally showed up: https://lore.kernel.org/all/[email protected]/ and I think the second patch in that set will do the proper disabling for that new feature. |
I wonder if it would be worth it to test the 6.3 rc kernels from https://kernel.ubuntu.com/~kernel-ppa/mainline/ to narrow the scope of when our i915 drm crash started happening with USB-C/docked displays. |
This reverts commit 86f4c65.
This reverts commit b38f2d5.
A memory corruption was reported in [1] with bisection pointing to the patch [2] enabling per-VMA locks for x86. Disable per-VMA locks config to prevent this issue until the fix is confirmed. This is expected to be a temporary measure. [1] https://bugzilla.kernel.org/show_bug.cgi?id=217624 [2] https://lore.kernel.org/all/[email protected] Reported-by: Jiri Slaby <[email protected]> Closes: https://lore.kernel.org/all/[email protected]/ Reported-by: Jacob Young <[email protected]> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217624 Fixes: 0bff0aa ("x86/mm: try VMA lock-based page fault handling first") Cc: [email protected] Signed-off-by: Suren Baghdasaryan <[email protected]>
63347f3
to
dc66530
Compare
When I was trying to test this a bit on Ubuntu, I was seeing issues with nvidia 525 dkms. Nvidia 535 seemed to be behaving though, and I haven't seen any issues with 525 ans 6.4.2 on Pop. |
I think we may not release our virtualbox package as part of our PPA for Ubuntu, which is causing DKMS failures during install/kernel upgrade. When it was initially tested, that wasn't an issue, as the build for virtualbox was explicitly added to the list of sources to pull from.
|
I got two SSDs with the same "MAXIO MAP1602" nvme controller chipset, I found the controller would not init or only init one SSD, After I update my kernel to latest 6.4.3 using After applying patch https://lore.kernel.org/lkml/[email protected]/, it works. Could we add this patch in the upcoming release? |
Thanks for all your hard work on pop os, Just to say that a lot of users are reporting problems with 7000 series amd gpus on kernel 6.4.x for example: cheers |
@ragardner That's probably pop-os/linux-firmware#36 rather than the kernel. |
The merge-base changed after approval.
Replaces #263
Related PRs