Am Dienstag, 29. September 2015, 12:48:43 schrieb Andre Tomt: > On 29. sep. 2015 12:21, Andre Tomt wrote: > > Meanwhile I'll revert both the mentioned net patches and see how it goes. > > So that blew up as well, meaning it's not any of these two patches: > [PATCH 4.1 124/159] net: do not process device backlog during unregistration > [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog > > I'll be offline for a half+ day, I'll look into bisecting when back if > nobody has figured it out by then. > -- > To unsubscribe from this list: send the line "unsubscribe stable" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html We see these rcu hangs with 4.1.9 on one of our routers, too. 4.1.8 runs fine. The output I got the last time was: [ 6488.174578] igb 000:06:00.1 eth3: Reset adapter [ 6497.350183] INFO: rcu_preempt self-detected stall on CPU { 3} (t=6301 jiffies g=383330 c=383329 q=1323) [ 6497.350229] rcu_preempt kthread starved for 6007 jiffies! [ 6560.311093] INFO: rcu_preempt self-detected stall on CPU { 3} (t=25205 jiffies g=383330 c=383329 q=4479) [ 6560.311140] rcu_preempt kthread starved for 24911 jiffies! [ 6623.272005] INFO: rcu_preempt self-detected stall on CPU { 3} (t=44109 jiffies g=383330 c=383329 q=7107) [ 6623.272049] rcu_preempt kthread starved for 43815 jiffies! [ 6633.053892] igb 000:06:00.0 eth2: Reset adapter [ 6633.053892] rcu_preempt kthread starved for 62719 jiffies! [ 6486.232914] INFO: rcu_preempt self-detected stall on CPU { 3} (t=63013 jiffies g=383330 c=383329 q=8487) [ 6486.233204] rcu_preempt kthread starved for 6007 jiffies! All other hangs basically were the same, the cpu varies though. After that the router completely hangs: networking stops working and we need to restart it. Regards, -- Wolfgang Walter Studentenwerk München Anstalt des öffentlichen Rechts -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html