Hi Jan,
[auto build test ERROR on v4.3-rc4 -- if it's inappropriate base, please ignore]
config: arm64-allnoconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin/make.c
Vitaly Kuznetsov writes:
> Andrew Morton writes:
>
>> On Thu, 08 Oct 2015 12:03:25 +0200 Vitaly Kuznetsov
>> wrote:
>>
>>> > If we picked up patch "kernel: Avoid softlockups in
>>> > stop_machine() during heavy printing" from my series (it's completely
>>> > independent, I've attached the late
Andrew Morton writes:
> On Thu, 08 Oct 2015 12:03:25 +0200 Vitaly Kuznetsov
> wrote:
>
>> > If we picked up patch "kernel: Avoid softlockups in
>> > stop_machine() during heavy printing" from my series (it's completely
>> > independent, I've attached the latest version), the result would look l
Andrew Morton writes:
> On Thu, 08 Oct 2015 11:51:13 +0200 Vitaly Kuznetsov
> wrote:
>
>> > On Wed, 7 Oct 2015 19:02:22 +0200 Vitaly Kuznetsov
>> > wrote:
>> >
>> >> In some cases we may end up killing the CPU holding the console lock
>> >> while still having valuable data in logbuf. E.g. I'
On Thu, 08 Oct 2015 12:03:25 +0200 Vitaly Kuznetsov wrote:
> > If we picked up patch "kernel: Avoid softlockups in
> > stop_machine() during heavy printing" from my series (it's completely
> > independent, I've attached the latest version), the result would look less
> > hacky to me (attached). T
On Thu, 08 Oct 2015 11:51:13 +0200 Vitaly Kuznetsov wrote:
> > On Wed, 7 Oct 2015 19:02:22 +0200 Vitaly Kuznetsov
> > wrote:
> >
> >> In some cases we may end up killing the CPU holding the console lock
> >> while still having valuable data in logbuf. E.g. I'm observing the
> >> following:
> >
Jan Kara writes:
>> ---
>> a/kernel/panic.c~panic-release-stale-console-lock-to-always-get-the-logbuf-printed-out-fix
>> +++ a/kernel/panic.c
>> @@ -149,10 +149,10 @@ void panic(const char *fmt, ...)
>> bust_spinlocks(0);
>>
>> /*
>> - * We may have ended up killing the CPU holdi
Andrew Morton writes:
> (cc Jan)
>
> On Wed, 7 Oct 2015 19:02:22 +0200 Vitaly Kuznetsov
> wrote:
>
>> In some cases we may end up killing the CPU holding the console lock
>> while still having valuable data in logbuf. E.g. I'm observing the
>> following:
>> - A crash is happening on one CPU an
On Wed 07-10-15 15:34:08, Andrew Morton wrote:
> (cc Jan)
>
> On Wed, 7 Oct 2015 19:02:22 +0200 Vitaly Kuznetsov
> wrote:
>
> > In some cases we may end up killing the CPU holding the console lock
> > while still having valuable data in logbuf. E.g. I'm observing the
> > following:
> > - A cra
(cc Jan)
On Wed, 7 Oct 2015 19:02:22 +0200 Vitaly Kuznetsov wrote:
> In some cases we may end up killing the CPU holding the console lock
> while still having valuable data in logbuf. E.g. I'm observing the
> following:
> - A crash is happening on one CPU and console_unlock() is being called on
10 matches
Mail list logo
