From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Marcel Holtmann <holtmann@linux.intel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ipw2100-devel@lists.sourceforge.net,
linux-wireless@vger.kernel.org, yi.zhu@intel.com,
reinette.chatre@intel.com, jgarzik@pobox.com,
linville@tuxdriver.com, davem@davemloft.net
Subject: Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmware restart.
Date: Mon, 22 Sep 2008 01:12:21 +0400 [thread overview]
Message-ID: <20080921211221.GD2135@2ka.mipt.ru> (raw)
In-Reply-To: <1222025731.6782.117.camel@californication>
Hi Marcel.
On Sun, Sep 21, 2008 at 09:35:31PM +0200, Marcel Holtmann (holtmann@linux.intel.com) wrote:
> I don't know if it is for this bug or a different one, but Matthew
> Garrett seem to have some pending patches. At least that is what he told
> me at PlumbersConf. Lets see if these patches do help. And please follow
> up with Arjan's suggestion and put a WARN_ON in the upstream code
> instead of waving CONFIG_BROKEN around.
I expect it is something new, since this bug exists at least from the
1.2 firmware version and .11 kernel. It was also reproduced (long ago
though) on 2.4.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-09-21 21:13 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 17:23 Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmware restart Evgeniy Polyakov
2008-09-21 17:36 ` Michael Buesch
2008-09-21 17:38 ` Evgeniy Polyakov
2008-09-21 18:04 ` Arjan van de Ven
2008-09-21 18:28 ` Evgeniy Polyakov
2008-09-21 18:35 ` Arjan van de Ven
2008-09-21 18:52 ` Wei Weng
2008-09-21 19:20 ` Arjan van de Ven
2008-09-21 19:00 ` Evgeniy Polyakov
2008-09-21 19:14 ` Johannes Berg
2008-09-21 19:38 ` Evgeniy Polyakov
2008-09-21 19:43 ` Arjan van de Ven
2008-09-21 20:20 ` Evgeniy Polyakov
2008-09-21 20:27 ` Arjan van de Ven
2008-09-21 20:57 ` Evgeniy Polyakov
2008-09-21 21:02 ` Arjan van de Ven
2008-09-21 21:05 ` Evgeniy Polyakov
2008-09-21 21:14 ` Arjan van de Ven
2008-09-21 21:43 ` Denys Fedoryshchenko
2008-09-21 22:07 ` Evgeniy Polyakov
2008-09-21 22:15 ` Denys Fedoryshchenko
2008-09-21 23:46 ` Evgeniy Polyakov
2008-09-21 23:27 ` Marcel Holtmann
2008-09-22 0:00 ` Evgeniy Polyakov
2008-09-21 22:38 ` Alan Cox
2008-09-21 23:44 ` Evgeniy Polyakov
2008-09-21 23:48 ` David Miller
2008-09-22 0:18 ` Evgeniy Polyakov
2008-09-21 20:05 ` Cyrill Gorcunov
2008-09-21 20:26 ` Evgeniy Polyakov
2008-09-21 20:35 ` Cyrill Gorcunov
2008-09-21 21:06 ` Evgeniy Polyakov
2008-09-21 19:57 ` Alan Cox
2008-09-21 21:10 ` Evgeniy Polyakov
2008-09-26 5:56 ` Evgeniy Polyakov
2008-09-21 19:35 ` Marcel Holtmann
2008-09-21 21:12 ` Evgeniy Polyakov [this message]
2008-09-21 22:45 ` Matthew Garrett
2008-09-21 22:42 ` Matthew Garrett
2008-09-21 23:45 ` Evgeniy Polyakov
2008-09-22 16:21 ` [Ipw2100-devel] " Kenneth Crudup
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=20080921211221.GD2135@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=davem@davemloft.net \
--cc=holtmann@linux.intel.com \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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).