On Mon, Apr 24, 2017 at 11:44:13AM -0400, Paul Gortmaker wrote:
> There are also some new fails around kernel/events/core.c in arm32/arm64
>
> include/linux/jump_label.h: In function
> ‘static_key_disable_cpuslocked.constprop.66’:
> include/linux/jump_label.h:260:20: error: inlining failed in call
On Mon, Apr 24, 2017 at 4:10 AM, Stephen Rothwell wrote:
> Hi all,
>
> News: there will be no linux-next release tomorrow.
>
> Changes since 20170421:
>
> The arm tree lost its build failure.
>
> The rdma tree lost its build failure.
>
> The tip tree gained a build failure for which I reverted a c
On Thu, 25 Apr 2013, Sedat Dilek wrote:
> > That also looks normal. Did you have CONFIG_USB_DEBUG enabled during
> > this test? If you did, you could try turning it back off to see if the
> > original problem returns while still doing a usbmon trace.
> >
>
> As my system works as "expected" aft
On Thu, 25 Apr 2013, Sedat Dilek wrote:
> You want me to send a patch against usb-next to clarify a bit on the
> kernel-config options to be enabled as prereqs in case of
> usbmon-tracing. If you think it's worth or not let me know.
It's up to you. Documentation patches are always welcome.
Alan
On Thu, Apr 25, 2013 at 5:49 PM, Alan Stern wrote:
> On Thu, 25 Apr 2013, Sedat Dilek wrote:
>
>> [ Run logging on USB-bus #1 ]
>>
>> # cat /sys/kernel/debug/usb/usbmon/1u > /tmp/usbmon-1u.txt <--- USB-bus #01
>>
>> [ Do suspend plus resume ]
>>
>> ...
>>
>> [ Check /tmp/usbmon-1u.txt file ]
>>
>>
On Thu, Apr 25, 2013 at 5:44 PM, Alan Stern wrote:
> On Wed, 24 Apr 2013, Sedat Dilek wrote:
>
>> With CONFIG_USB_DEBUG=y I do not see a PM/async line.
>>
>> Might you have a look at the logs?
>
> They look quite normal. Except for one thing: The built-in hubs appear
> to have gotten reset during
On Thu, 25 Apr 2013, Sedat Dilek wrote:
> [ Run logging on USB-bus #1 ]
>
> # cat /sys/kernel/debug/usb/usbmon/1u > /tmp/usbmon-1u.txt <--- USB-bus #01
>
> [ Do suspend plus resume ]
>
> ...
>
> [ Check /tmp/usbmon-1u.txt file ]
>
> ...
>
> File attached!
That also looks normal. Did you ha
On Wed, 24 Apr 2013, Sedat Dilek wrote:
> With CONFIG_USB_DEBUG=y I do not see a PM/async line.
>
> Might you have a look at the logs?
They look quite normal. Except for one thing: The built-in hubs appear
to have gotten reset during the suspend/resume, for no apparent reason.
That's probabl
On Wed, Apr 24, 2013 at 11:17 PM, Alan Stern wrote:
> On Wed, 24 Apr 2013, Sedat Dilek wrote:
>
>> > Did this work differently under earlier kernels?
>> >
>>
>> Unfortunately, s/r did not work for several Linux-Next releases as
>> there is missing tglx's patch pendinging in tip.git/timers/core.
>
On Wed, 24 Apr 2013, Sedat Dilek wrote:
> > Did this work differently under earlier kernels?
> >
>
> Unfortunately, s/r did not work for several Linux-Next releases as
> there is missing tglx's patch pendinging in tip.git/timers/core.
Have you tried testing under 3.8? Or earlier releases?
> >
On Wed, Apr 24, 2013 at 10:32 PM, Alan Stern wrote:
> On Wed, 24 Apr 2013, Sedat Dilek wrote:
>
>> > [ CC linux-pm and linux-usb (ehci) folks ]
>> >
>> > This happens with my external USB mouse after suspend/resume.
>> >
>> > Excerpt (full dmesg and kernel-config attached):
>> >
>> > $ dmesg | egr
On Wed, 24 Apr 2013, Sedat Dilek wrote:
> > [ CC linux-pm and linux-usb (ehci) folks ]
> >
> > This happens with my external USB mouse after suspend/resume.
> >
> > Excerpt (full dmesg and kernel-config attached):
> >
> > $ dmesg | egrep -i 'usb|async' | grep 1-1.2
> > [1.258602] usb 1-1.2: ne
On Wed, Apr 24, 2013 at 10:00 PM, Sedat Dilek wrote:
> On Wed, Apr 24, 2013 at 10:07 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> There will be no linux-next release tomorrow (April 25).
>>
>> Changes since 20130423:
>>
>> The net-next tree lost its build failure.
>>
>> The staging tree gained
13 matches
Mail list logo
