From: "John W. Linville" <linville@tuxdriver.com>
To: "Ondřej Kučera" <ondrej.kucera@centrum.cz>
Cc: yi.zhu@intel.com, reinette.chatre@intel.com,
linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net, jikos@suse.cz
Subject: Re: PROBLEM: Led for wifi blinking all the time
Date: Fri, 31 Oct 2008 10:54:35 -0400 [thread overview]
Message-ID: <20081031145434.GB4310@tuxdriver.com> (raw)
In-Reply-To: <490A5D39.1090605@centrum.cz>
On Fri, Oct 31, 2008 at 02:19:53AM +0100, Ond=C5=99ej Ku=C4=8Dera wrote=
:
> Hello,
>
> this is my first kernel bug report ever so I'm not 100% sure about th=
e =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=
to =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.
I'm pretty sure this is how the iwlwifi team wants the LEDs to work...
John
--=20
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
--
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
next prev parent reply other threads:[~2008-10-31 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 1:19 PROBLEM: Led for wifi blinking all the time Ondřej Kučera
2008-10-31 14:54 ` John W. Linville [this message]
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=20081031145434.GB4310@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=jikos@suse.cz \
--cc=linux-wireless@vger.kernel.org \
--cc=ondrej.kucera@centrum.cz \
--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 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.