Bug 11311

Summary: Squid 100% CPU (Skylake) on gigabit connection
Product: IPFire Reporter: Razvan Constantin <bepme>
Component: ---Assignee: Assigned to nobody - feel free to grab it and work on it <nobody>
Status: CLOSED FIXED QA Contact:
Severity: Minor Usability    
Priority: - Unknown - CC: arne.fitzenreiter, michael.tremer, peter.mueller
Version: 2   
Hardware: x86_64   
OS: All   
Bug Depends on: 11548    
Bug Blocks:    
Attachments: squid 100% CPU usage on one core

Description Razvan Constantin 2017-04-01 14:25:34 UTC 
Created attachment 509 [details]
squid 100% CPU usage on one core

IPFire forum topic with more details and tests:
http://forum.ipfire.org/viewtopic.php?f=27&t=18413

IPFire forum post with solution:
http://forum.ipfire.org/viewtopic.php?f=27&t=18413&start=15#p106363

Using IPFire Core 109 with Squid.
Machine info: http://fireinfo.ipfire.org/profile/6a9eef819f5d3cb868ca056e5cad466374526206

Downloading a 1 GB file over a gigabit connection results in squid using 100% CPU on one core and strace shows 99.73 2.059048 17 120166 epoll_wait.

Upgrading the kernel fixes the problem.
Steps taken to upgrade the kernel:
ssh into IPFire.
cd \
wget http://people.ipfire.org/~trikolon/kern ... 13.tar.bz2
tar xvf kernel-4.9.13.tar.bz2
grub-mkconfig -o /boot/grub/grub.cfg
Reboot. Done.

Idea and kernel from http://forum.ipfire.org/viewtopic.php?f=50&t=18372#p105975
Comment 1 Michael Tremer 2017-04-06 21:36:23 UTC 
This is not a release kernel so I have no idea what has changed there.

Could you please test Core Update 110 which is currently available for testing and includes a new version of squid.
Comment 2 Razvan Constantin 2017-04-07 08:45:39 UTC 
Update to 110. Exactly the same situation.
Updated the kernel again, problem fixed.
Comment 3 Peter Müller 2017-11-08 17:33:00 UTC 
Is this issue still valid?
Comment 4 Razvan Constantin 2017-11-10 18:34:13 UTC 
I have been using a different than stock kernel, version 4.9.24 and did not have any problems since.
But since the stock kernel has not changed, I am guessing the problem is still there.
Comment 5 Peter Müller 2017-12-13 19:39:24 UTC 
Okay, thanks. Kernel 4.14 is currently in development, this will be hopefully fixed with it (https://wiki.ipfire.org/devel/telco/2017-12-04).
Comment 6 Arne.F 2018-08-30 08:44:25 UTC 
we are on 4.14 now