On Sun 2014-11-02 13:25:45, Stanislaw Gruszka wrote:
> On Tue, Oct 28, 2014 at 11:20:15PM +0100, Pavel Machek wrote:
> > > > It can be checked by "iw dev wlan0 get power_save" .
> >
> > So it seems I have power save on. I guess someone enabled it for me :-).
> >
> > root@duo:~# iwconfig wlan0
> >
On Tue, Oct 28, 2014 at 11:20:15PM +0100, Pavel Machek wrote:
> > > It can be checked by "iw dev wlan0 get power_save" .
>
> So it seems I have power save on. I guess someone enabled it for me :-).
>
> root@duo:~# iwconfig wlan0
> wlan0 IEEE 802.11abg ESSID:off/any
> Mode:Managed
On Sun 2014-10-26 12:05:54, Pavel Machek wrote:
> On Sun 2014-10-26 11:33:15, Stanislaw Gruszka wrote:
> > On Sat, Oct 25, 2014 at 01:42:46PM +0200, Pavel Machek wrote:
> > > > Since 3.17 we have only 2 minor iwlegacy changes on current linus tree.
> > > > If this is a regression it's probably caus
On Sun 2014-10-26 11:33:15, Stanislaw Gruszka wrote:
> On Sat, Oct 25, 2014 at 01:42:46PM +0200, Pavel Machek wrote:
> > > Since 3.17 we have only 2 minor iwlegacy changes on current linus tree.
> > > If this is a regression it's probably caused by different subsystem
> > > changes, most likely by
On Sat, Oct 25, 2014 at 01:42:46PM +0200, Pavel Machek wrote:
> > Since 3.17 we have only 2 minor iwlegacy changes on current linus tree.
> > If this is a regression it's probably caused by different subsystem
> > changes, most likely by PCI changes. If this is not regression, such
> > errors could
On Fri 2014-10-24 14:12:40, Stanislaw Gruszka wrote:
> On Thu, Oct 23, 2014 at 01:02:37PM +, Grumbach, Emmanuel wrote:
> > [Changed subject]
> > This is really iwlegacy and not iwlwifi.
> >
> >
> > >
> > > Hi!
> > >
> > > Full dmesg is in the attachment, I guess the troubles started with:
>
On Thu, Oct 23, 2014 at 01:02:37PM +, Grumbach, Emmanuel wrote:
> [Changed subject]
> This is really iwlegacy and not iwlwifi.
>
>
> >
> > Hi!
> >
> > Full dmesg is in the attachment, I guess the troubles started with:
> >
> > iwl3945 :03:00.0: Queue 4 stuck for 2004 ms.
> > iwl3945 00
[Changed subject]
This is really iwlegacy and not iwlwifi.
>
> Hi!
>
> Full dmesg is in the attachment, I guess the troubles started with:
>
> iwl3945 :03:00.0: Queue 4 stuck for 2004 ms.
> iwl3945 :03:00.0: On demand firmware reload
> iwl3945 :03:00.0: Master Disable Timed Out, 10
8 matches
Mail list logo