All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniele C." <legolas558@users.sourceforge.net>
To: Zhu Yi <yi.zhu@intel.com>, linux-wireless@vger.kernel.org
Subject: Re: RF killswitch (or worse) is enabled after resume from suspend
Date: Mon, 22 Feb 2010 22:17:14 +0100	[thread overview]
Message-ID: <4B82F45A.3020100@users.sourceforge.net> (raw)
In-Reply-To: <1266730789.16986.21.camel@debian>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -------- Original Message  --------
Subject: Re: RF killswitch (or worse) is enabled after resume from suspend
From: Zhu Yi <yi.zhu@intel.com>
To: Daniele C. <legolas558@users.sourceforge.net>
Date: Sun Feb 21 2010 06:39:49 GMT+0100 (CET)

> On Thu, 2010-02-11 at 01:58 +0800, Daniele C. wrote:
>> I am using kernel 2.6.33-rc7-00064-gac73fdd (latest git of linus'
>> tree) and I have been experiencing an issue for more than a month now.
>>
>> When the computer resumes from suspend (not hibernation), the RF
>> killswitch seems ON (although dmesg does not say this, so it is just a
>> deduction of mine). If I unload ipw2100 and reload it, the killswitch
>> is disabled and wifi can work regularly.
> 
> Can you read the ipw2100 sysfs entry "rf_kill" to confirm the rf kill
> state when this happens? Please also attach your dmesg.
> 
It's always zero.

A recent dmesg is here:
http://bugzilla.kernel.org/attachment.cgi?id=25047
sudo lspci -v:
http://bugzilla.kernel.org/attachment.cgi?id=25021

>> Now I am experiencing a worse issue: the 2nd time I do this, reloading
>> the module doesn't work anymore, and neither using my modified version
>> of fsam7400 which did the trick in the past.
>>
>> It appears to be an issue of 2.6.33 kernels. Shall I contact some
>> kernel list? 
> 
> You can include linux-wireless@vger.kernel.org if you want. If you can
> do some git bisect, that would be very helpful to identify the
> regression.
> 
OK, I will go along the git bisect path if possible, but problem is really strange, since only reboots seem to fix it.
Nobody else experiencing issues with ipw2100?

Best regards.
- --
  Daniele C.

> Thanks,
> -yi  	
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLgvRaAAoJEON28As9epPA/TgH/Ru50uzYZyTJxg/74OySxAJy
8T2uNFKyUit+sGpXLdCJMAstgnKyjMHuYX7xOPr4q+RrOPxJUfnY9mFcEL09DH5Z
GLxGeh4FWwaQl8gpsFFYxGQ5l1QpoCclYgRdzx5/SdqtXnwryLIEeP8ejUY+54Zp
BdcGLmIjhV9MMCrVRFn6Erf/5UBnJ1JkR2NJf30cwRymvhjcCWFK72tAzNZ7rSrm
q0+WxbSWIyDUT2It+8+a6UTqhvUI6DwuJfDmH6OGMfZV+DlskSoV9Zst5xAqgltt
O+0uXa4p20b87Ed3N303B7Zxc/Vx1nfm6WOBWuYoln+DgBrBzqQAMP8HJe2cSlk=
=Dx9Q
-----END PGP SIGNATURE-----

           reply	other threads:[~2010-02-22 21:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1266730789.16986.21.camel@debian>]

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=4B82F45A.3020100@users.sourceforge.net \
    --to=legolas558@users.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yi.zhu@intel.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 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.