Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762012AbXEZQbi (ORCPT ); Sat, 26 May 2007 12:31:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755655AbXEZQbb (ORCPT ); Sat, 26 May 2007 12:31:31 -0400 Received: from mail.gmx.net ([213.165.64.20]:41469 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753366AbXEZQba (ORCPT ); Sat, 26 May 2007 12:31:30 -0400 X-Authenticated: #8359428 X-Provags-ID: V01U2FsdGVkX18FiFhmPyYFmNugEkARGqkeTI6KyCdPPal8U3w+bI 40I6xk8utPJOjS From: Uwe Bugla To: Michael Buesch Subject: Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400) Date: Sat, 26 May 2007 18:26:06 +0200 User-Agent: KMail/1.9.5 References: <20070524195616.234280@gmx.net> <20070526091309.0af20971.akpm@linux-foundation.org> <200705261821.16355.mb@bu3sch.de> In-Reply-To: <200705261821.16355.mb@bu3sch.de> Cc: Andrew Morton , Maximilian Engelhardt , linux-wireless@vger.kernel.org, "linux-kernel" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705261826.06796.uwe.bugla@gmx.de> X-Y-GMX-Trusted: 0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1708 Lines: 47 Am Samstag, 26. Mai 2007 18:21 schrieben Sie: > On Saturday 26 May 2007 18:13:09 Andrew Morton wrote: > > > I already tried your -mm kernel, but it crashes on my machine > > > for other reasons. (Yeah, I should look into them, too :P ) > > > > err, please do. Just the oops trace would be a start. > > Yes, I will look into it. I think it was related to my > onboard RTL networking chip. When trying to bring it down, > it oopses the machine. But I'm not sure what happens exactly, yet. > I'll take a look at it. > > > > Andrew, is it possible that the breakage was introduced in the > > > merge process somehow? Didn't the patch apply cleanly? Are there > > > other changes to b44 I should know about in your tree? > > > > Only git-wireless.net modifies b44.c but if we're having IRQ assignment > > problems then we'd need to look elsewhere. > > I think we don't have IRQ assignment problems. Uwe simply disabled > b44-PCI support in his first bugreport (I guess). Yes! > So there was > no b44-PCI driver loaded. Well, not exactly: b44 plus ssb were in fact produced, but did not function, at least in that case, due to the misleading / superficial information in the Kconfig menu...... > Later on he said that it does magically work now... NO! Later on I said I did chose that b44-PCI driver, got the right dependencies, and there was no interrupt problem at all. So the driver got loaded as expected but simply did not work at all...... Cheers Uwe - 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/