linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Matt Mackall <mpm@selenic.com>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	Monakhov Dmitriy <dmonakhov@openvz.org>
Subject: Re: 2.6.21-rc4-mm1
Date: Fri, 23 Mar 2007 10:00:17 -0500	[thread overview]
Message-ID: <4603EB81.4050308@lwfinger.net> (raw)
In-Reply-To: <20070323111029.4089ccfb@gondolin.boeblingen.de.ibm.com>

Cornelia Huck wrote:
> On Thu, 22 Mar 2007 13:55:51 -0500,
> Larry Finger <larry.finger@lwfinger.net> wrote:
>> I applied the debug patch, but I don't see any error codes being returned. This time I also got the
>> General Protection Faults. An excerpt of the log is attached.
> 
> Hm, I think I have an idea about what happened.
> 
> The firmware class tried to suppress the first KOBJ_ADD uevent by
> returning -ENODEV in firmware_uevent if FW_STATUS_READY was not set.
> This only worked as long as the return code of kobject_uevent was not
> checked in device_add. hack-to-make-wireless-work.patch made that first
> uevent return successfully, but this possible triggered some udev rule
> too early, leading to firmware load failures.
> 
> The following (completely untested) patch uses uevent_suppress to stop
> the uevent from being generated during device_add. Does this work for
> you?

Yes it does. Good job. On my first reboot with the new code, the startup of X hung with the black
screen and the big X cursor, but that seems to have been a single occurrence. With the patch, the
bcm43xx firmware is loaded and the device is working.

Thanks,

Larry

  reply	other threads:[~2007-03-23 15:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070319205623.299d0378.akpm@linux-foundation.org>
     [not found] ` <1174433034.62033.16.camel@localhost>
2007-03-21  6:36   ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-21  9:52     ` 2.6.21-rc4-mm1 Edward Shishkin
2007-03-21 14:12     ` [Bluez-devel] 2.6.21-rc4-mm1 Marcel Holtmann
2007-03-21 16:13     ` 2.6.21-rc4-mm1 Larry Finger
2007-03-23 19:40       ` 2.6.21-rc4-mm1 Zan Lynx
2007-03-24  1:49         ` 2.6.21-rc4-mm1 Larry Finger
2007-03-21 18:14     ` 2.6.21-rc4-mm1 Larry Finger
2007-03-21 18:34       ` 2.6.21-rc4-mm1 Michael Buesch
2007-03-21 19:00         ` 2.6.21-rc4-mm1 John W. Linville
2007-03-21 18:59       ` 2.6.21-rc4-mm1 John W. Linville
2007-03-21 20:22         ` 2.6.21-rc4-mm1 Matt Mackall
2007-03-21 20:48           ` 2.6.21-rc4-mm1 Larry Finger
2007-03-21 21:03           ` 2.6.21-rc4-mm1 Larry Finger
2007-03-21 21:39             ` 2.6.21-rc4-mm1 Randy Dunlap
2007-03-21 21:45           ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-22  7:39           ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-22 11:35             ` 2.6.21-rc4-mm1 Cornelia Huck
     [not found]               ` <4602752A.5050109@lwfinger.net>
2007-03-22 17:10                 ` 2.6.21-rc4-mm1 Cornelia Huck
2007-03-22 18:55                   ` 2.6.21-rc4-mm1 Larry Finger
2007-03-23 10:10                     ` 2.6.21-rc4-mm1 Cornelia Huck
2007-03-23 15:00                       ` Larry Finger [this message]
2007-03-24  5:06                       ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-26  9:09                         ` 2.6.21-rc4-mm1 Cornelia Huck
2007-03-26  9:22                           ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-26 10:34                             ` 2.6.21-rc4-mm1 Eric Rannaud
2007-03-26 10:44                               ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-27  9:25                               ` 2.6.21-rc4-mm1 Kay Sievers
2007-03-27 17:17                                 ` 2.6.21-rc4-mm1 Cornelia Huck
2007-03-28  1:26                                   ` 2.6.21-rc4-mm1 Eric Rannaud
2007-03-28  8:25                                     ` 2.6.21-rc4-mm1 Cornelia Huck
2007-03-24 22:32             ` 2.6.21-rc4-mm1 Matt Mackall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4603EB81.4050308@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=akpm@linux-foundation.org \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dmonakhov@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mpm@selenic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).