On Mon, 2011-09-05 at 11:33 +0200, Stanislaw Gruszka wrote:
> On Sun, Sep 04, 2011 at 10:28:35AM +0200, Paul Bolle wrote:
> > 1) After a few days of normal usage (with quite a bit of suspend and
> > resume cycles) this error was again triggered. So avoiding
> > check_plcp_health() doesn't seem to help.
> >
> > 2) I never send you the debug output (ie, output after doing "modprobe
> > iwl4965 debug=0x47ffffff"), did I?
>
> No, but if error show up after few days, gathering and analyzing few
> days of debug logs in impractical.
I see.
> Does wifi stop working after an
> error, or there is some other negative impact? Or only that messages
> are printed and driver recover itself?
There doesn't seem to be any impact (ie, it might have some impact but
I'm too insensitive to notice). The driver does recover itself and I do
not have to mess with rfkill or "modprobe -r" or whatever. I actually
discovered this because I tend to regularly do
dmesg -r | grep "^<[123]>"
to keep myself informed of any kernel errors (or worse). And then these
few dozen lines can't go unnoticed.
Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
