Bug 71351
Summary: | "INFO: rcu_sched detected stalls on CPUs/tasks" on high server load | ||
---|---|---|---|
Product: | Networking | Reporter: | Mirek Kratochvil (exa.exa) |
Component: | Other | Assignee: | Stephen Hemminger (stephen) |
Status: | NEW --- | ||
Severity: | normal | CC: | debiandev |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.10.22, 3.11, 3.13.5 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
dmesg on 3.10.25 kernel
dmesg from 3.13.3 dmesg from 3.13.5 |
Description
Mirek Kratochvil
2014-03-01 18:11:08 UTC
Created attachment 127751 [details]
dmesg on 3.10.25 kernel
Created attachment 127761 [details]
dmesg from 3.13.3
Created attachment 127771 [details]
dmesg from 3.13.5
I tracked down the issue a bit, happens on 3.7.0 but doesn't happen on 3.6.11. There were some RCU changes merged for 3.7, I hope I'll be able to bisect the one that caused the problem. More details: - falling back to a kernel with no NO_HZ set (e.g. rigid 1000Hz timer frequency) solves the issue, but CPU usage of the network cards gets around 20 times higher (which is unusuable for this setup, and just "too much") - preemption doesn't affect/cause this. Can you check if any of the recent kernels still have these issues? |