From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: Arjan van de Ven <arjan@infradead.org>,
Johannes Berg <johannes@sipsolutions.net>,
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 02:07:08 +0400 [thread overview]
Message-ID: <20080921220708.GA31413@2ka.mipt.ru> (raw)
In-Reply-To: <200809220043.07345.denys@visp.net.lb>
On Mon, Sep 22, 2008 at 12:43:07AM +0300, Denys Fedoryshchenko (denys@visp.net.lb) wrote:
> You are not right. I had totaly disfunctional Intel driver on two laptops and
> reported about issue to Intel. Yes it took time, they took all debugs and
> went coma mode (i was thinking that), but suddently i got mail from them, and
> next kernel/firmware release worked for me flawlessly. So they did perfect
> job.
I'm talking about current situation.
> Don't be negative and prepare yourself for giving long debug outputs. Patience
> and only patience.
Just to be clear, did it take 4 years? :)
Anyway, I already made conclusions, as probably others: I will
experiment with different 'workarounds' for this bug, maybe I will
succeed, maybe Intel will decided to fix it, maybe LHC will crash the
world. Verbose warning about the bug was frowned upon, so its up to uses
to make a progress here...
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-09-21 22:08 UTC|newest]
Thread overview: 42+ 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 [this message]
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-22 14:22 ` Bill Davidsen
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
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=20080921220708.GA31413@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=denys@visp.net.lb \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=jgarzik@pobox.com \
--cc=johannes@sipsolutions.net \
--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