> I don't see mei_me_pci_suspend() calling mei_disable_interrupts() and
> pci_disable_msi().
Suspend calls mei_reset with request for disabling interrupts
I'm pretty sure I do free_irq and I do disable_msi in the suspend (Hope we are
looking at the same code)
I don't see a call to mei_enable
On 07/10/2013 09:18 AM, Winkler, Tomas wrote:
>>> suspend complete.
>>>
>>> I can start bi-sect of this problem on intel-display scope if you
>>> would like me to. Please let me know if the bisect scope should be larger.
>>>
>>> -- Shuah
>>
>> I got finally an older system where this reproduces con
> > suspend complete.
> >
> > I can start bi-sect of this problem on intel-display scope if you
> > would like me to. Please let me know if the bisect scope should be larger.
> >
> > -- Shuah
>
> I got finally an older system where this reproduces consistently, I'm trying
> to
> root cause that n
On Sun, Jul 7, 2013 at 8:31 PM, Sören Brinkmann
wrote:
> Hi,
>
> since I updated to 3.10 my system freezes occasionally. Googling the
> messages in my kernel log (attached) make me suspect, that my problem
> might be related to the issue Shuah reported.
>
> So, I just wanted to check in, what the
On Mon, Jul 1, 2013 at 5:54 PM, Shuah Khan wrote:
> On 06/26/2013 04:24 PM, Shuah Khan wrote:
>> On 06/26/2013 04:12 PM, Winkler, Tomas wrote:
>>>
>>>
>
>>> 42f132f mei: me: clear interrupts on the resume path
>>> 2753ff5 mei: nfc: fix nfc device freeing
>>> 5e85b36 mei: init: Flush scheduled work
On 06/26/2013 04:24 PM, Shuah Khan wrote:
> On 06/26/2013 04:12 PM, Winkler, Tomas wrote:
>>
>>
>> 42f132f mei: me: clear interrupts on the resume path
>> 2753ff5 mei: nfc: fix nfc device freeing
>> 5e85b36 mei: init: Flush scheduled work before resetting the device
>>
>> Are you sure you have the
On Sat, Jun 29, 2013 at 4:52 PM, Sergey Meirovich wrote:
>
> There was overheating issue, that caused forced power off in the
> middle of the first compile.
Ok, then the thing is easily explained by simply the filesystem being
shut down in an incomplete state. Sounds like the mkregtable binary
ha
On 30 June 2013 01:13, Linus Torvalds wrote:
> On Sat, Jun 29, 2013 at 2:07 PM, Sergey Meirovich
> wrote:
>>> (and possibly the
>>> mkregtable binary) and trying again might fix it.
>>
>> Removing mkregtable has indeed the compile issue for me. Thanks!
>
> Ok, so something failed at an earlier
On Sun, Jun 30, 2013 at 8:13 AM, Linus Torvalds
wrote:
> On Sat, Jun 29, 2013 at 2:07 PM, Sergey Meirovich
> wrote:
>>> (and possibly the
>>> mkregtable binary) and trying again might fix it.
>>
>> Removing mkregtable has indeed the compile issue for me. Thanks!
>
> Ok, so something failed at a
On Sat, Jun 29, 2013 at 2:07 PM, Sergey Meirovich wrote:
>> (and possibly the
>> mkregtable binary) and trying again might fix it.
>
> Removing mkregtable has indeed the compile issue for me. Thanks!
Ok, so something failed at an earlier build. That error is probably
long gone, though, since the
Hi Linus,
On 29 June 2013 21:11, Linus Torvalds wrote:
> On Sat, Jun 29, 2013 at 8:05 AM, Sergey Meirovich
> wrote:
>>
>> 3.10-rc7 doesn't compile for me
>>
>> rathamahata@piledriver /usr/local/src/linux-3.10-rc7 $ make -j1 bzImage
>> modules
>>
On Sat, Jun 29, 2013 at 8:05 AM, Sergey Meirovich wrote:
>
> 3.10-rc7 doesn't compile for me
>
> rathamahata@piledriver /usr/local/src/linux-3.10-rc7 $ make -j1 bzImage
> modules
> make[1]: Nothing to be done for `all'.
> make[1]: Nothing to be done for `relocs&
On 06/26/2013 04:12 PM, Winkler, Tomas wrote:
>
>
>>> Can you please send me the log part when this starts?
>>>
>>> Thanks
>>>
>>
>> It rolled over and I don't have prior messages. I tried reproducing twice and
>> didn't see it again. I will try a few more times and see if I can get it to
>> happe
> > Can you please send me the log part when this starts?
> >
> > Thanks
> >
>
> It rolled over and I don't have prior messages. I tried reproducing twice and
> didn't see it again. I will try a few more times and see if I can get it to
> happen
> again.
>
> This is what I could save before dm
On Tue, 25 Jun 2013 20:51:27 +
Shuah Khan wrote:
> On 06/25/2013 02:06 PM, Jesse Barnes wrote:
> > On Tue, 25 Jun 2013 19:59:28 +
> > Shuah Khan wrote:
> >
> >> On 06/25/2013 01:52 PM, Jesse Barnes wrote:
> >>> On Tue, 25 Jun 2013 21:37:37 +0200
> >>> Daniel Vetter wrote:
> >>>
> >>
> >
On 06/25/2013 02:57 PM, Tomas Winkler wrote:
> On Tue, Jun 25, 2013 at 11:51 PM, Shuah Khan wrote:
>>
>> With this patch warn_on went away. Resume worked. I started seeing:
>>
>> [ 78.733062] mei_me :00:16.0: unexpected reset: dev_state =
>> RESETTING
>> [ 78.733079] mei_me :00:16.0:
On Tue, Jun 25, 2013 at 11:51 PM, Shuah Khan wrote:
>
> On 06/25/2013 02:06 PM, Jesse Barnes wrote:
> > On Tue, 25 Jun 2013 19:59:28 +
> > Shuah Khan wrote:
> >
> >> On 06/25/2013 01:52 PM, Jesse Barnes wrote:
> >>> On Tue, 25 Jun 2013 21:37:37 +0200
> >>> Daniel Vetter wrote:
> >>>
> >>
> >
On 06/25/2013 02:06 PM, Jesse Barnes wrote:
> On Tue, 25 Jun 2013 19:59:28 +
> Shuah Khan wrote:
>
>> On 06/25/2013 01:52 PM, Jesse Barnes wrote:
>>> On Tue, 25 Jun 2013 21:37:37 +0200
>>> Daniel Vetter wrote:
>>>
>>
Adding more lists to cc + Jesse since he's the guilty one for the
On Tue, 25 Jun 2013 19:59:28 +
Shuah Khan wrote:
> On 06/25/2013 01:52 PM, Jesse Barnes wrote:
> > On Tue, 25 Jun 2013 21:37:37 +0200
> > Daniel Vetter wrote:
> >
>
> >>
> >> Adding more lists to cc + Jesse since he's the guilty one for the
> >> vt-switchless state restore stuff.
> >
> > Ye
On 06/25/2013 01:52 PM, Jesse Barnes wrote:
> On Tue, 25 Jun 2013 21:37:37 +0200
> Daniel Vetter wrote:
>
>>
>> Adding more lists to cc + Jesse since he's the guilty one for the
>> vt-switchless state restore stuff.
>
> Yeah, looks like we don't fetch the PLL state on resume from hibernate,
> lea
On Tue, 25 Jun 2013 21:37:37 +0200
Daniel Vetter wrote:
> On Tue, Jun 25, 2013 at 9:05 PM, Linus Torvalds
> wrote:
> > Adding the appropriate cc'd.. I'm not seeing why this would start
> > happening now, but there's been a number of commits that touch the
> > intel crtc 'active' state and hotplu
On Tue, Jun 25, 2013 at 9:05 PM, Linus Torvalds
wrote:
> Adding the appropriate cc'd.. I'm not seeing why this would start
> happening now, but there's been a number of commits that touch the
> intel crtc 'active' state and hotplug logic, so I'm assuming one of
> them is to blame.. Lots of small c
Adding the appropriate cc'd.. I'm not seeing why this would start
happening now, but there's been a number of commits that touch the
intel crtc 'active' state and hotplug logic, so I'm assuming one of
them is to blame.. Lots of small changes around
ironlake_crtc_mode_set() etc.
This warning seems
On 06/24/2013 09:27 AM, Linus Torvalds wrote:
> So this is hopefully the last -rc in the series, and things have
> indeed be calming down finally, so assuming that trend continues,
> we're all good.
>
> Which means that we still want more testing and people hollering if
> there are any regressions
On Sat, 22 Jun 2013 11:04:27 -1000 Linus Torvalds
wrote:
>
> So this is hopefully the last -rc in the series, and things have
> indeed be calming down finally, so assuming that trend continues,
> we're all good.
And you are all going to resist rebasing your trees (for no apparent
reason) this cl
move notifier from list before freeing it
Laurent Pinchart (1):
drm/prime: Honor requested file flags when exporting a buffer
Li Zhong (1):
nohz: Fix notifier return val that enforce timekeeping
Linus Torvalds (1):
Linux 3.10-rc7
Magnus Damm (1):
ARM: 7756/1: zImage/vi
26 matches
Mail list logo
