From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261305AbTDQKoQ (ORCPT ); Thu, 17 Apr 2003 06:44:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261306AbTDQKoQ (ORCPT ); Thu, 17 Apr 2003 06:44:16 -0400 Received: from mx03.cyberus.ca ([216.191.240.24]:18181 "EHLO mx03.cyberus.ca") by vger.kernel.org with ESMTP id S261305AbTDQKoO (ORCPT ); Thu, 17 Apr 2003 06:44:14 -0400 Date: Thu, 17 Apr 2003 06:55:19 -0400 (EDT) From: jamal To: Catalin BOIE cc: Manfred Spraul , Tomas Szepe , "" , "" , "" Subject: Re: [PATCH] qdisc oops fix In-Reply-To: Message-ID: <20030417065352.S6710@shell.cyberus.ca> References: <20030415084706.O1131@shell.cyberus.ca> <20030416072952.E4013@shell.cyberus.ca> <3E9D755A.8060601@colorfullife.com> <20030416142802.E5912@shell.cyberus.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ok, I stand corrected. Tomas is right- same problem. You had htb loaded as a module, the other person had it compiled in ;-> Get yourself upgraded ;-> cheers, jamal On Thu, 17 Apr 2003, Catalin BOIE wrote: > > Catalin, Can you what kernel that is? > > 2.4.20pre10 works ok but 2.4.20 crash. > With traffic -> no crash with 2.4.20. Without traffic, on other machine, > no crash. > > > > > It's triggered, because someone does something like > > > spin_lock_bh(&my_lock); > > > p = kmalloc(,GFP_KERNEL); > > > > > > I don't like the proposed fix: usually code that calls > > > kmalloc(,GFP_KERNEL) assumes that it runs at process space, e.g. uses > > > semaphores, or non-bh spinlocks, etc. > > > slab just happens to contain a test that complains about illegal calls. > > > > ok. Nice. > > > > > > > > >>Trace; c0127e0f > > > >>Trace; c01d3cac > > > >>Trace; d081ecc7 > > > >>Trace; c01d5265 > > > >>Trace; d0820600 > > > >>Trace; c01d27e4 > > > >>Trace; c01d0605 <__neigh_event_send+89/1b4> > > > >>Trace; c01d7cd4 > > > >>Trace; c01d7730 > > > >>Trace; c01d7b73 > > > >>Trace; c01c79d5 > > > >>Trace; c01c8b48 > > > >>Trace; c0120010 > > > >> > > > >> > > > >> > > > >> > > > I don't understand the backtrace. Were any modules loaded? Perhaps > > > 0xd081ecc7 is a module. > > > > > > > Probably a module. Again Catalin, run no modules. > It's a production machine. I cannot test this. We plan to replace the > machine, so I can test then. > > > > I'd add a > > > if(in_interrupt()) show_stack(NULL); > > > into qdisc_create_dflt(), and try to reproduce the bug without modules. > > > > > > > Catalin - again instead of your fix can you please add this call? > See above. I cannot test now. I'm very sorry! > > > cheers, > > jamal > > > > --- > Catalin(ux) BOIE > catab@deuroconsult.ro > >