From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753526AbYIUVpj (ORCPT ); Sun, 21 Sep 2008 17:45:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752831AbYIUVpd (ORCPT ); Sun, 21 Sep 2008 17:45:33 -0400 Received: from relay2.globalproof.net ([194.146.153.25]:49691 "EHLO relay2.globalproof.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752806AbYIUVpc (ORCPT ); Sun, 21 Sep 2008 17:45:32 -0400 From: Denys Fedoryshchenko Organization: Virtual ISP To: Evgeniy Polyakov Subject: Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmware restart. Date: Mon, 22 Sep 2008 00:43:07 +0300 User-Agent: KMail/1.9.9 Cc: Arjan van de Ven , Johannes Berg , 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 References: <20080921182835.GA11473@2ka.mipt.ru> <20080921140203.4698a2ee@infradead.org> <20080921210554.GA2135@2ka.mipt.ru> In-Reply-To: <20080921210554.GA2135@2ka.mipt.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809220043.07345.denys@visp.net.lb> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday 22 September 2008, Evgeniy Polyakov wrote: > On Sun, Sep 21, 2008 at 02:02:03PM -0700, Arjan van de Ven (arjan@infradead.org) wrote: > > > That allows to dump whatever number of warnings you want. The more we > > > have, the louder will be customers scream. > > > > artificially increasing numbers isn't going to do that; it just shows > > you're more interested in making a stink than in getting something > > improved ;( > > As practice shows, I'm the only one who is interested in getting > something improved, and Intel, as we see right now, is not interested in > it at all, since you ask me not only decrease error verbosity, but also > do not work towards fixing the bug by trying to understand where it > lives. 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. Don't be negative and prepare yourself for giving long debug outputs. Patience and only patience.