Hi,
4.15 was released on Sunday. Fedora will be following the same rebase procedure that we have in the past: After a few stable releases, typically 4.15.2 or 4.15.3, F27 will be rebased to 4.15 with F26 rebased shortly there after. I would expect this to happen by the end of February.
Note this was a tricky kernel release because of all the Spectre/ Meltdown work but that should be settled at this point. More testing is always appreciated though.
Thanks, Laura
Am 29.01.2018 um 11:32 schrieb Laura Abbott:
4.15 was released on Sunday. Fedora will be following the same rebase procedure that we have in the past: After a few stable releases, typically 4.15.2 or 4.15.3, F27 will be rebased to 4.15 with F26 rebased shortly there after. I would expect this to happen by the end of February.
Note this was a tricky kernel release because of all the Spectre/ Meltdown work but that should be settled at this point. More testing is always appreciated though
given that most of the spectre/meltdown stuff is already backported to 4.14 in more or less hussle i would at least in that context assume that the new 4.15.x has less bugs in doubt
Am 29.01.2018 um 11:32 schrieb Laura Abbott:
4.15 was released on Sunday. Fedora will be following the same rebase procedure that we have in the past: After a few stable releases, typically 4.15.2 or 4.15.3, F27 will be rebased to 4.15 with F26 rebased shortly there after. I would expect this to happen by the end of February.
Note this was a tricky kernel release because of all the Spectre/ Meltdown work but that should be settled at this point. More testing is always appreciated though
given that most of the spectre/meltdown stuff is already backported to 4.14 in more or less hussle i would at least in that context assume that the new 4.15.x has less bugs in doubt
On 01/29/2018 02:32 AM, Laura Abbott wrote:
Hi,
4.15 was released on Sunday. Fedora will be following the same rebase procedure that we have in the past: After a few stable releases, typically 4.15.2 or 4.15.3, F27 will be rebased to 4.15 with F26 rebased shortly there after. I would expect this to happen by the end of February.
Note this was a tricky kernel release because of all the Spectre/ Meltdown work but that should be settled at this point. More testing is always appreciated though.
Thanks, Laura
Updates are now filed. Note that the kernel-tools split has happened as well so please test that as well
https://bodhi.fedoraproject.org/updates/FEDORA-2018-7336c2ba99 https://bodhi.fedoraproject.org/updates/kernel-tools-4.15.0-300.fc27
Thanks, Laura
Am 09.02.2018 um 17:53 schrieb Laura Abbott:
On 01/29/2018 02:32 AM, Laura Abbott wrote:
Hi,
4.15 was released on Sunday. Fedora will be following the same rebase procedure that we have in the past: After a few stable releases, typically 4.15.2 or 4.15.3, F27 will be rebased to 4.15 with F26 rebased shortly there after. I would expect this to happen by the end of February.
Note this was a tricky kernel release because of all the Spectre/ Meltdown work but that should be settled at this point. More testing is always appreciated though.
Updates are now filed. Note that the kernel-tools split has happened as well so please test that as well
https://bodhi.fedoraproject.org/updates/FEDORA-2018-7336c2ba99 https://bodhi.fedoraproject.org/updates/kernel-tools-4.15.0-300.fc27
4.15.2-300.fc27.x86_64 breaks my POE-switch with a DECT-phone booting with 4.14.18-300 and it immediatly comes back
when disconnect/reconnect the DECT device (Yealink W56P) i see a sequence of dhcpd-flood in the logs, IP not pingable while the dhcp-log talks about it hard-configured IP by MAC (192.168.2.15), handset says "line busy"
TV on the same port also not pingable while on the quad-port "01:00.0 Ethernet controller: Intel Corporation 82580 Gigabit Network Connection (rev 01)" it's reachable as usual
the software-switch is a dual-port PoE-card: 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) ___________________________
what goes wrong are the ethtool-settings of "ifcfg-poe-phone" comment them out and all is fine
hardware and config unchanged for around 12 months so there must be some regression in the network driver
[root@srv-rhsoft:~]$ ifup poe-phone Could not change any device features Cannot get device ring settings: Operation not supported [root@srv-rhsoft:~]$ ifdown poe-phone [root@srv-rhsoft:~]$ ifup poe-phone Could not change any device features Cannot get device ring settings: Operation not supported ___________________________
[root@srv-rhsoft:/etc/sysconfig/network-scripts]$ cat ifcfg-poe-phone ########################### # POE # ###########################
DEVICE=poe-phone HWADDR=00:e0:4c:80:5c:cb
TYPE=Ethernet BOOTPROTO=static ONBOOT=yes ARPCHECK=no NM_CONTROLLED=no USERCTL=no IPV6INIT=no MTU=1500
#ETHTOOL_OPTS="wol d; -K ${DEVICE} tso on rx on tx on gro on; -G ${DEVICE} rx 2048 tx 2048; -C ${DEVICE} rx-usecs 75"
kernel@lists.fedoraproject.org