Re: Mark IPW2100 as BROKEN: Fatal interrupt. Scheduling firmware restart.
Alan Cox <alan-qBU/[email protected]> Sun, 21 Sep 2008 23:38:19 +0100
| Newsgroups | gmane.linux.kernel.wireless.general,gmane.linux.network,gmane.linux.kernel,gmane.linux.drivers.ipw2100.devel |
|---|---|
| Organization | Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a Lloegr o'r rhif cofrestru 3798903 |
| Message-ID | <[email protected]> |
> > still more complex than needed; a WARN_ON_ONCE() will be enough. > > That allows to dump whatever number of warnings you want. The more we > have, the louder will be customers scream. But if Intel don't care then you can scream all you like 8) A WARN_ON_ONCE is sufficient to capture an idea of how many people it is effecting and maybe to figure out what the trigger is from their reports, at that point there is some chance to get it fixed (especially if its remotely triggerable ;)) Alan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html