[Kernel-packages] [Bug 1880005] Re: Shutdown/Poweroff Failed with Kernel 5.0.3-53
I'm Sorry, the kernel version written in the title is wrong, the kernel version that fails is number 5.3.0-53. -- 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/1880005 Title: Shutdown/Poweroff Failed with Kernel 5.0.3-53 Status in linux package in Ubuntu: New Bug description: I have installed Linux Mint Mate 19.3 (Tricia, 64-bits). When I upgraded the Kernel to version 5.3.0-53, the on / off function failed, the screen is off but the laptop is still working, the light of manual shutdown button is still lit. There is no problem with the previous version of the kernel: 5.3.0-51. My laptop is Lenovo YOGA 530-14ARR with precessor AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx × 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880005] [NEW] Shutdown/Poweroff Failed with Kernel 5.0.3-53
Public bug reported: I have installed Linux Mint Mate 19.3 (Tricia, 64-bits). When I upgraded the Kernel to version 5.3.0-53, the on / off function failed, the screen is off but the laptop is still working, the light of manual shutdown button is still lit. There is no problem with the previous version of the kernel: 5.3.0-51. My laptop is Lenovo YOGA 530-14ARR with precessor AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx × 8 ** Affects: linux (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/1880005 Title: Shutdown/Poweroff Failed with Kernel 5.0.3-53 Status in linux package in Ubuntu: New Bug description: I have installed Linux Mint Mate 19.3 (Tricia, 64-bits). When I upgraded the Kernel to version 5.3.0-53, the on / off function failed, the screen is off but the laptop is still working, the light of manual shutdown button is still lit. There is no problem with the previous version of the kernel: 5.3.0-51. My laptop is Lenovo YOGA 530-14ARR with precessor AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx × 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861423] [NEW] The temperature rises when connected to electricity
Public bug reported: After the kernel update, I have noticed a huge temperature increase when connected to electricity in all my laptops ** Affects: linux (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/1861423 Title: The temperature rises when connected to electricity Status in linux package in Ubuntu: New Bug description: After the kernel update, I have noticed a huge temperature increase when connected to electricity in all my laptops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1388786] Re: TCP stale transfer with erroneous SACK information
** Changed in: linux (Ubuntu) Status: Expired => 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/1388786 Title: TCP stale transfer with erroneous SACK information Status in linux package in Ubuntu: In Progress Bug description: Cisco PIX/FWSM changes TCP sequence numbers but doesn't change numbers in SACK TCP options. When this erroneous information comes to Linux server there is some corruption in TCP stack in some circunstances with CUBIC TCP congestion algorithm and transfer stales. Problem can be reproduced in Ubuntu Server 14.04 when a Cisco FWSM is changing sequence numbers (default configuration) and a big file (30MB, for example) is being transfered. Can be solved deactivating SACK: sysctl -w net.ipv4.tcp_sack=0 We have solved it also with this configuration: sysctl -w net.ipv4.tcp_congestion_control=reno sysctl -w net.ipv4.tcp_frto=1 sysctl -w net.ipv4.tcp_early_retrans=1 We can also fix it by changing firewall configuration. Find attached a wireshark capture where you can see at 16613 frame how client requests segment 853521869 and server (158.42.250.128) resends again a previous segment for 87 seconds until it stops transfer. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1388786] Re: TCP stale transfer with erroneous SACK information
We have tested the kernel 3.19-rc7 and found some improvements. Communication does not stop and the file can be finally downloaded, but it still takes a long time. We have tested a 100 MB file in an Ubuntu server with kernel 3.19-rc7 across the Cisco firewall changing sequence numbers with following results: - With TCP SACK disabled (sysctl -w net.ipv4.tcp_sack=0) 62 seconds - With TCP SACK enabled (default configuration) 462 seconds It seems that, even though the communication is not completely stalled with this kernel version, the problem is not solved yet. ** Tags added: kernel-bug-exists-upstream -- 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/1388786 Title: TCP stale transfer with erroneous SACK information Status in linux package in Ubuntu: Incomplete Bug description: Cisco PIX/FWSM changes TCP sequence numbers but doesn't change numbers in SACK TCP options. When this erroneous information comes to Linux server there is some corruption in TCP stack in some circunstances with CUBIC TCP congestion algorithm and transfer stales. Problem can be reproduced in Ubuntu Server 14.04 when a Cisco FWSM is changing sequence numbers (default configuration) and a big file (30MB, for example) is being transfered. Can be solved deactivating SACK: sysctl -w net.ipv4.tcp_sack=0 We have solved it also with this configuration: sysctl -w net.ipv4.tcp_congestion_control=reno sysctl -w net.ipv4.tcp_frto=1 sysctl -w net.ipv4.tcp_early_retrans=1 We can also fix it by changing firewall configuration. Find attached a wireshark capture where you can see at 16613 frame how client requests segment 853521869 and server (158.42.250.128) resends again a previous segment for 87 seconds until it stops transfer. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1388786] Re: TCP stale transfer with erroneous SACK information
** 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/1388786 Title: TCP stale transfer with erroneous SACK information Status in “linux” package in Ubuntu: Confirmed Bug description: Cisco PIX/FWSM changes TCP sequence numbers but doesn't change numbers in SACK TCP options. When this erroneous information comes to Linux server there is some corruption in TCP stack in some circunstances with CUBIC TCP congestion algorithm and transfer stales. Problem can be reproduced in Ubuntu Server 14.04 when a Cisco FWSM is changing sequence numbers (default configuration) and a big file (30MB, for example) is being transfered. Can be solved deactivating SACK: sysctl -w net.ipv4.tcp_sack=0 We have solved it also with this configuration: sysctl -w net.ipv4.tcp_congestion_control=reno sysctl -w net.ipv4.tcp_frto=1 sysctl -w net.ipv4.tcp_early_retrans=1 We can also fix it by changing firewall configuration. Find attached a wireshark capture where you can see at 16613 frame how client requests segment 853521869 and server (158.42.250.128) resends again a previous segment for 87 seconds until it stops transfer. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
