> >> Hi, I'm back.
> >>
> >> This terriable bug occurs again in Linux 3.12. This time I've been
> >> prepared for it and wrote down the complete process of its apperance
> >> and my reacting, as attached.
> >
> > Thanks - was that with power save disabled?
>
> Yes, Linux 3.12 with "options iwlmvm power_scheme=1". (I did not touch
> that .conf file after the kernel upgrade)
>
> >
> >>
> >> IMHO they are quite similar with those errors in 3.11...
> >
> > Indeed. The only difference is that you don’t have PCI complain about not
> being able to disable L1.
>
> I see. But I still cannot figure out what is the "trigger" of this bug. Today (Nov
> 06 UTC+8) this bug occurs twice till now (14:30), they were at 12:31 and 13:30.
> At the first time I was about to do a system upgrade and at the second time I
> was using rsync to upload photos from my Android phone to my laptop.
>
> Sometimes I was not even using network (the traffic was near zero) when
> the bug occurs. So this bug seems to occur no matter of network traffic
> states?
>
> Could you think of a possible "trigger" of this bug so I could try to avoid it (I
> hate rebooting) before the final fix is released? For example, if there is
> something wrong with the "modules linked in" I could blacklist that module...
>
I don't know - I am trying to check with our HW guys here.
Can you please run lspci -xxx before and after it happens?
BTW - how do you recover? Reloading the module is enough?
��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
