Hello,
The 4.3.3 kernel has been pushed to updates-testing for F23. As of right now, it has a +12 karma score. Given that it is a major release rebase, we're going to wait at least a few days to see how it fares.
If you are so inclined, testing would be appreciated. As usual, please give karma as appropriate but we would appreciate it if you only give negative karma for new, not reported issues and with a bug link associated. If a bug is fixed, we have marked it as such. If it isn't, we haven't and giving negative karma for those known issues simply prevents fixes from getting into the hands of other users.
Of particular note with this update is the improved Skylake Intel graphics support. If you have a new machine, you might find it works better with 4.3 than the previous F23 kernels. (You may also find it breaks something, which is also interesting. YMMV.)
Thanks.
josh
Am 07.01.2016 um 19:33 schrieb Josh Boyer:
Hello,
The 4.3.3 kernel has been pushed to updates-testing for F23. As of right now, it has a +12 karma score. Given that it is a major release rebase, we're going to wait at least a few days to see how it fares
thank you for the fast kernel updates in Fedora over the last years!
compared with times of Fedora 9 and a endless internal "release-numbers" that's a big win given the HW support improvements and very few regressions over the time
On Thu, Jan 07, 2016 at 01:33:22PM -0500, Josh Boyer wrote:
Hello,
The 4.3.3 kernel has been pushed to updates-testing for F23. As of right now, it has a +12 karma score. Given that it is a major release rebase, we're going to wait at least a few days to see how it fares.
If you are so inclined, testing would be appreciated. As usual, please give karma as appropriate but we would appreciate it if you only give negative karma for new, not reported issues and with a bug link associated. If a bug is fixed, we have marked it as such. If it isn't, we haven't and giving negative karma for those known issues simply prevents fixes from getting into the hands of other users.
Please note there seem to be a btrfs regression in since 4.3: namely fstrim could discard beginning of the disk, removing the bootloader. This commit fixes the issue:
http://git.kernel.org/cgit/linux/kernel/git/fdmanana/linux.git/commit/?h=int...
Il 07/01/2016 20:30, Tomasz Torcz ha scritto:
On Thu, Jan 07, 2016 at 01:33:22PM -0500, Josh Boyer wrote:
Hello,
The 4.3.3 kernel has been pushed to updates-testing for F23. As of right now, it has a +12 karma score. Given that it is a major release rebase, we're going to wait at least a few days to see how it fares.
If you are so inclined, testing would be appreciated. As usual, please give karma as appropriate but we would appreciate it if you only give negative karma for new, not reported issues and with a bug link associated. If a bug is fixed, we have marked it as such. If it isn't, we haven't and giving negative karma for those known issues simply prevents fixes from getting into the hands of other users.
Please note there seem to be a btrfs regression in since 4.3: namely fstrim could discard beginning of the disk, removing the bootloader. This commit fixes the issue:
http://git.kernel.org/cgit/linux/kernel/git/fdmanana/linux.git/commit/?h=integration-4.5&id=7b6cb6618b45bb383f9336ec89df5f1f31f9935b
So, is it safe to install kernel 4.3.3-300? I see it's now in stable repo, but I think it doesn't carry the commit above...
On Tue, Jan 12, 2016 at 2:08 PM, Mattia Verga mattia.verga@tiscali.it wrote:
Il 07/01/2016 20:30, Tomasz Torcz ha scritto:
On Thu, Jan 07, 2016 at 01:33:22PM -0500, Josh Boyer wrote:
Hello,
The 4.3.3 kernel has been pushed to updates-testing for F23. As of right now, it has a +12 karma score. Given that it is a major release rebase, we're going to wait at least a few days to see how it fares.
If you are so inclined, testing would be appreciated. As usual, please give karma as appropriate but we would appreciate it if you only give negative karma for new, not reported issues and with a bug link associated. If a bug is fixed, we have marked it as such. If it isn't, we haven't and giving negative karma for those known issues simply prevents fixes from getting into the hands of other users.
Please note there seem to be a btrfs regression in since 4.3: namely fstrim could discard beginning of the disk, removing the bootloader. This commit fixes the issue:
http://git.kernel.org/cgit/linux/kernel/git/fdmanana/linux.git/commit/?h=int...
So, is it safe to install kernel 4.3.3-300? I see it's now in stable repo, but I think it doesn't carry the commit above...
The commit above isn't in any released kernel, Fedora or upstream or otherwise. It was only added to the main btrfs maintainer's tree about a day ago.
As far as I understand the bug, it only happens if you have the bootloader installed in the root partition (not a separate /boot) and you run an fstrim on the whole partition (fstrim /) either manually or from a system script or such. I suppose it would possibly happen if you have the bootloader installed in a btrfs /boot partition and ran fstrim on that too. However, Fedora doesn't support booting from a btrfs filesystem at the moment and typical installs create a separate /boot partition that is ext4. I may have some details wrong and would gladly be corrected if so.
We'll pick up the fix once it lands in Linus' tree. Until then, the safety is mostly determine by that of btrfs in general. Opinions vary.
josh
On Jan 12, 2016 15:03, "Josh Boyer" jwboyer@fedoraproject.org wrote:
On Tue, Jan 12, 2016 at 2:08 PM, Mattia Verga mattia.verga@tiscali.it
wrote:
Il 07/01/2016 20:30, Tomasz Torcz ha scritto:
On Thu, Jan 07, 2016 at 01:33:22PM -0500, Josh Boyer wrote:
Hello,
The 4.3.3 kernel has been pushed to updates-testing for F23. As of right now, it has a +12 karma score. Given that it is a major release rebase, we're going to wait at least a few days to see how it fares.
If you are so inclined, testing would be appreciated. As usual, please give karma as appropriate but we would appreciate it if you only give negative karma for new, not reported issues and with a bug link associated. If a bug is fixed, we have marked it as such. If it isn't, we haven't and giving negative karma for those known issues simply prevents fixes from getting into the hands of other users.
Please note there seem to be a btrfs regression in since 4.3: namely fstrim could discard beginning of the disk, removing the bootloader. This commit fixes the issue:
http://git.kernel.org/cgit/linux/kernel/git/fdmanana/linux.git/commit/?h=int...
So, is it safe to install kernel 4.3.3-300? I see it's now in stable
repo,
but I think it doesn't carry the commit above...
The commit above isn't in any released kernel, Fedora or upstream or otherwise. It was only added to the main btrfs maintainer's tree about a day ago.
As far as I understand the bug, it only happens if you have the bootloader installed in the root partition (not a separate /boot) and you run an fstrim on the whole partition (fstrim /) either manually or from a system script or such. I suppose it would possibly happen if you have the bootloader installed in a btrfs /boot partition and ran fstrim on that too. However, Fedora doesn't support booting from a btrfs filesystem at the moment and typical installs create a separate /boot partition that is ext4. I may have some details wrong and would gladly be corrected if so.
Can confirm. Just head to reinstall an F23 system. Automatically generated partitions (Encrypted btrfs raid0) gave me an ext4 /boot
We'll pick up the fix once it lands in Linus' tree. Until then, the safety is mostly determine by that of btrfs in general. Opinions vary.
josh
devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
On Wed, Jan 13, 2016 at 8:33 AM, Eric Griffith egriffith92@gmail.com wrote:
On Jan 12, 2016 15:03, "Josh Boyer" jwboyer@fedoraproject.org wrote:
On Tue, Jan 12, 2016 at 2:08 PM, Mattia Verga mattia.verga@tiscali.it wrote:
Il 07/01/2016 20:30, Tomasz Torcz ha scritto:
On Thu, Jan 07, 2016 at 01:33:22PM -0500, Josh Boyer wrote:
Hello,
The 4.3.3 kernel has been pushed to updates-testing for F23. As of right now, it has a +12 karma score. Given that it is a major release rebase, we're going to wait at least a few days to see how it fares.
If you are so inclined, testing would be appreciated. As usual, please give karma as appropriate but we would appreciate it if you only give negative karma for new, not reported issues and with a bug link associated. If a bug is fixed, we have marked it as such. If it isn't, we haven't and giving negative karma for those known issues simply prevents fixes from getting into the hands of other users.
Please note there seem to be a btrfs regression in since 4.3: namely fstrim could discard beginning of the disk, removing the bootloader. This commit fixes the issue:
http://git.kernel.org/cgit/linux/kernel/git/fdmanana/linux.git/commit/?h=int...
So, is it safe to install kernel 4.3.3-300? I see it's now in stable repo, but I think it doesn't carry the commit above...
The commit above isn't in any released kernel, Fedora or upstream or otherwise. It was only added to the main btrfs maintainer's tree about a day ago.
As far as I understand the bug, it only happens if you have the bootloader installed in the root partition (not a separate /boot) and you run an fstrim on the whole partition (fstrim /) either manually or from a system script or such. I suppose it would possibly happen if you have the bootloader installed in a btrfs /boot partition and ran fstrim on that too. However, Fedora doesn't support booting from a btrfs filesystem at the moment and typical installs create a separate /boot partition that is ext4. I may have some details wrong and would gladly be corrected if so.
Can confirm. Just head to reinstall an F23 system. Automatically generated partitions (Encrypted btrfs raid0) gave me an ext4 /boot
It takes a lot of gymnastics to get Fedora into this situation, and it can't be done via the GUI installer and maybe not even with kickstart. Whereas on openSUSE, where the bug was found, it's their default layout at install time. First they don't step on the bootloader in LBA 0 by default, and new installs use parted's jump code. So no matter what, the MBR bootloader code jumps to the VBR of the partition with an active bit set. The Btrfs VBR is huge, 64KiB, which is why it's supported as a GRUB bootloader pad, and that's where openSUSE embeds GRUB whether on MBR or GPT disks.
So anyone with a 92 ways to boot Linux wall poster needs to update it to 93.
On Tue, Jan 12, 2016 at 3:02 PM, Josh Boyer jwboyer@fedoraproject.org wrote:
On Tue, Jan 12, 2016 at 2:08 PM, Mattia Verga mattia.verga@tiscali.it wrote:
Please note there seem to be a btrfs regression in since 4.3: namely fstrim could discard beginning of the disk, removing the bootloader. This commit fixes the issue:
http://git.kernel.org/cgit/linux/kernel/git/fdmanana/linux.git/commit/?h=int...
We'll pick up the fix once it lands in Linus' tree. Until then, the safety is mostly determine by that of btrfs in general. Opinions vary.
FYI, I added the highlighted patch to F23 git today. It will be in the next build.
josh
Running kernel-4.3.3-300.fc23.x86_64 I get thermal shutdown in a couple of minutes on a HP EliteBook 8530p Notebook. (http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c01554229)
It works with all kernels until 4.2.8-300.fc23.x86_64.
Should I file a bug?
Regards,