Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270863AbUJUT3p (ORCPT ); Thu, 21 Oct 2004 15:29:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270852AbUJUT3o (ORCPT ); Thu, 21 Oct 2004 15:29:44 -0400 Received: from mail4.utc.com ([192.249.46.193]:24960 "EHLO mail4.utc.com") by vger.kernel.org with ESMTP id S270882AbUJUTZ1 (ORCPT ); Thu, 21 Oct 2004 15:25:27 -0400 Message-ID: <41780D17.20305@cybsft.com> Date: Thu, 21 Oct 2004 14:25:11 -0500 From: "K.R. Foley" Organization: Cybersoft Solutions, Inc. User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: tglx@linutronix.de CC: Ingo Molnar , LKML , Lee Revell , Rui Nuno Capela , Mark_H_Johnson@Raytheon.com, Bill Huey , Adam Heath , Florian Schmidt , Michal Schmidt , Fernando Pablo Lopez-Lezcano Subject: Re: [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U9 References: <20041013061518.GA1083@elte.hu> <20041014002433.GA19399@elte.hu> <20041014143131.GA20258@elte.hu> <20041014234202.GA26207@elte.hu> <20041015102633.GA20132@elte.hu> <20041016153344.GA16766@elte.hu> <20041018145008.GA25707@elte.hu> <20041019124605.GA28896@elte.hu> <20041019180059.GA23113@elte.hu> <20041020094508.GA29080@elte.hu> <20041021132717.GA29153@elte.hu> <4177FADC.6030905@cybsft.com> <1098384016.27089.42.camel@thomas> <41780687.8030408@cybsft.com> <1098385049.27089.51.camel@thomas> In-Reply-To: <1098385049.27089.51.camel@thomas> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1605 Lines: 49 Thomas Gleixner wrote: > On Thu, 2004-10-21 at 20:57, K.R. Foley wrote: > >>>I guess, you don't have a tulip network card in your box, as the module >>>is removed. >>> >>>The question is, if it got registered correctly before the removal. >> >>Actually I do have the tulip card in the box and I am pulling this stuff >>from the logs over that connection now. Here are the next lines from the >>log that might help. > > > Not really. We must figure out, why sys_delete_module is called. Understand. I did not mean the log would help figure it out, but that it would explain that the card really is present. :) My guess is that it is prematurely unloading the driver before it's fully registered, like you said. The question is why? Also I am not in front of the system right now so I can't unload the module to see if it generates the error again, but I will try it when I get home. > > [] tulip_cleanup+0x17/0x1b [tulip] (16) > [] sys_delete_module+0x121/0x150 (12) <<-------- > [] sys_munmap+0x51/0x60 (64) > [] do_page_fault+0x0/0x660 (16) > [] sysenter_past_esp+0x52/0x71 (16) > > >>Oct 21 12:33:22 porky kernel: tulip 0000:04:0a.0: Device was removed >>without pro >>perly calling pci_disable_device(). This may need fixing. > > > This one is a result of the BUG() > > tglx > > > - 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/