On Thu 2021-02-04 22:38:02, John Ogness wrote:
> On 2021-01-22, kernel test robot wrote:
> > FYI, we noticed the following commit (built with gcc-9):
> >
> > commit: b031a684bfd01d633c79d281bd0cf11c2f834ada ("printk: remove
> > logbuf_lock writer-protection of ringbuffer")
> >
On 2021-01-22, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: b031a684bfd01d633c79d281bd0cf11c2f834ada ("printk: remove logbuf_lock
> writer-protection of ringbuffer")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
So I
On 2021-01-22, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: b031a684bfd01d633c79d281bd0cf11c2f834ada ("printk: remove logbuf_lock
> writer-protection of ringbuffer")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
I am
On 2021-01-28, John Ogness wrote:
> [ 903.189448][ T356] [ 778.825864] [ 655.250559] [ 531.607066] [
> 407.120936] tasks-torture:torture_onoff task: online 0 failed: errno -5
So I at least found out what these multi-timestamp messages are (thanks
to reading /dev/kmsg). lkp is directing
On 2021-01-28, Petr Mladek wrote:
>> [ 903.189448][ T356] [ 778.825864] [ 655.250559] [ 531.607066] [
>> 407.120936] tasks-torture:torture_onoff task: online 0 failed: errno -5
>>
>> These multi-timestamp lines are odd. And they are almost exactly 124
>> seconds apart.
>
> Yup, this looks
On Thu 2021-01-28 16:48:29, John Ogness wrote:
> On 2021-01-28, Petr Mladek wrote:
> > If you are able to reproduce this, it might be interesting to see
> > backtraces from all CPUs when RCU stall gets detected. Or even
> > printing all processes, even the sleeping ones.
>
> OK, I now have lkp
On 2021-01-28, Petr Mladek wrote:
> If you are able to reproduce this, it might be interesting to see
> backtraces from all CPUs when RCU stall gets detected. Or even
> printing all processes, even the sleeping ones.
OK, I now have lkp running on my intel core i5 machine and it reliably
On Thu 2021-01-28 12:32:46, John Ogness wrote:
> On 2021-01-28, Sergey Senozhatsky wrote:
> >> # modprobe rcutorture onoff_interval=3 onoff_holdoff=30 torture_type=tasks
> >>
> >> (Those are the same modprobe parameters used by the lkp job.)
> >>
> >> After about a minute I see:
> >>
> >> [
On 2021-01-28, Sergey Senozhatsky wrote:
>> # modprobe rcutorture onoff_interval=3 onoff_holdoff=30 torture_type=tasks
>>
>> (Those are the same modprobe parameters used by the lkp job.)
>>
>> After about a minute I see:
>>
>> [ 47.268292] tasks-torture: rcu_torture_read_exit: Start of
On (21/01/27 22:28), John Ogness wrote:
>
> # modprobe rcutorture onoff_interval=3 onoff_holdoff=30 torture_type=tasks
>
> (Those are the same modprobe parameters used by the lkp job.)
>
> After about a minute I see:
>
> [ 47.268292] tasks-torture: rcu_torture_read_exit: Start of episode
> [
On 2021-01-27, John Ogness wrote:
> I was finally able to trigger this by using my workstation
Well, I don't know how reliably I can trigger this. I think my time will
be better spent getting lkp to trigger, since that shows to be reliable.
It took me an hour to trigger this one and I have the
On 2021-01-26, Sergey Senozhatsky wrote:
> AFAIU this is just 'modprobe rcutorture'
I was finally able to trigger this by using my workstation:
Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
Debian/buster
QEMU 3.1.0 (Debian 1:3.1+dfsg-8+deb10u8)
instead of my build server:
Intel(R)
On (21/01/22 17:21), Petr Mladek wrote:
[..]
> > [ 952.271861] ? firmware_map_remove
> > (kbuild/src/consumer/kernel/sched/core.c:4411)
> > [ 952.272870] ? ksys_write (kbuild/src/consumer/fs/read_write.c:661)
> > [ 952.273709] schedule (kbuild/src/consumer/include/linux/thread_info.h:84
> >
On (21/01/22 16:13), kernel test robot wrote:
[..]
>
> ++++
> || 6b916706f8 | b031a684bf |
> ++++
> |
On Fri 2021-01-22 16:13:11, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: b031a684bfd01d633c79d281bd0cf11c2f834ada ("printk: remove logbuf_lock
> writer-protection of ringbuffer")
>
15 matches
Mail list logo
