All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@bombadil.infradead.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: BUG at net/wireless/reg.c:2132 on PowerPC
Date: Mon, 08 Jun 2009 21:17:16 -0400	[thread overview]
Message-ID: <1244510236.28215.32.camel@mj> (raw)
In-Reply-To: <20090608231919.GC23972@bombadil.infradead.org>

On Mon, 2009-06-08 at 19:19 -0400, Luis R. Rodriguez wrote:

> Thank you for reporting this, try loading the system without ath5k present
> (mv ath5k.ko ath5k.ignore is an easy way) then prior to loadin git in a window
> get 'iw event' running.

I'm sorry, but I managed to "fix" the problem without having a way to
recreate it again.  I emptied /etc/udev/rules.d/70-persistent-net.rules
and removed /etc/sysconfig/network-scripts/ifcfg-wlan0, and the problem
is gone, but I didn't preserve the original files, and I cannot make the
crash happen again.

Also, it turns out that pciutils failed to upgrade to the Fedora 11
version, and "lspci -v" was crashing.  After upgrading pciutils the BUG
was gone, but downgrading it didn't make it reappear :-(

I tried what you said, and that's what I get:

# iw event
phy #0: regulatory domain change: set to US by a driver request on phy0
phy #1: regulatory domain change: set to US by a driver request on phy1

>  
> -		BUG_ON(request_wiphy->regd);
> +		/*
> +		 * Userspace could have sent two replies with only
> +		 * one kernel request.
> +		 */
> +		if (request_wiphy->regd)
> +			return -EALREADY;

I think it's a good idea.  Stupid userspace shouldn't cause kernel bugs.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2009-06-09  1:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 22:59 BUG at net/wireless/reg.c:2132 on PowerPC Pavel Roskin
2009-06-08 23:13 ` Larry Finger
2009-06-09  0:41   ` Pavel Roskin
2009-06-08 23:19 ` Luis R. Rodriguez
2009-06-09  1:17   ` Pavel Roskin [this message]
2009-06-09  1:50     ` Luis R. Rodriguez

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=1244510236.28215.32.camel@mj \
    --to=proski@gnu.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@bombadil.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.