Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753973AbbKBPZB (ORCPT ); Mon, 2 Nov 2015 10:25:01 -0500 Received: from mail-pa0-f48.google.com ([209.85.220.48]:33515 "EHLO mail-pa0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751914AbbKBPZA (ORCPT ); Mon, 2 Nov 2015 10:25:00 -0500 Message-ID: <1446477897.23275.6.camel@edumazet-glaptop2.roam.corp.google.com> Subject: Re: kernel panic in 4.2.3, rb_erase in sch_fq From: Eric Dumazet To: Denys Fedoryshchenko Cc: Jamal Hadi Salim , "David S. Miller" , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Date: Mon, 02 Nov 2015 07:24:57 -0800 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 857 Lines: 25 On Mon, 2015-11-02 at 16:11 +0200, Denys Fedoryshchenko wrote: > Hi! > > Actually seems i was getting this panic for a while (once per week) on > loaded pppoe server, but just now was able to get full panic message. > After checking commit logs on sch_fq.c i didnt seen any fixes, so > probably upgrading to newer kernel wont help? I do not think we support sch_fq as a HTB leaf. If you want both HTB and sch_fq, you need to setup a bonding device. HTB on bond0 sch_fq on the slaves Sure, the kernel should not crash, but HTB+sch_fq on same net device is certainly not something that will work anyway. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/