linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ondřej Kučera" <ondrej.kucera@centrum.cz>
To: yi.zhu@intel.com, reinette.chatre@intel.com
Cc: linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net, jikos@suse.cz
Subject: PROBLEM: Led for wifi blinking all the time
Date: Fri, 31 Oct 2008 02:19:53 +0100	[thread overview]
Message-ID: <490A5D39.1090605@centrum.cz> (raw)

Hello,

this is my first kernel bug report ever so I'm not 100% sure about the=20
protocol but I'll try my best...

After upgrading to 2.6.27 the wifi led starts blinking right after=20
connecting to the network and then continues blinking even when there's=
=20
no network traffic at all. This wasn't happening before, the led used t=
o=20
be just "on" when I was connected but not generating any traffic.

Up to kernel 2.6.26.5 (the last 2.6.26.* kernel in my distribution -=20
ArchLinux) the behavior was correct, the problem first occurred with=20
2.6.27 and is present up to 2.6.27.4 (the last of 2.6.27.* I've tried).=
=20
The driver used is iwl3945, the corresponding line from lspci:
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG=20
Network Connection (rev 02)

If any other information is relevant, please tell me and I'll try to=20
provide it, too.

Ond=F8ej


--=20
Cheers,
Ond=F8ej Ku=E8era
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2008-10-31  1:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31  1:19 Ondřej Kučera [this message]
2008-10-31 14:54 ` PROBLEM: Led for wifi blinking all the time John W. Linville
2008-10-31 18:59   ` [ipw3945-devel] " Marcos Barbosa
2008-11-04  1:58     ` Ondřej Kučera
2008-11-04 17:35       ` reinette chatre
2008-11-03 20:14   ` Tino Keitel
2008-11-04 19:03     ` Tino Keitel
2008-11-05  0:58       ` Tomas Winkler
2008-11-05  1:04       ` Tomas Winkler

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=490A5D39.1090605@centrum.cz \
    --to=ondrej.kucera@centrum.cz \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=jikos@suse.cz \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --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 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).