Re: hung task in 4.14 (syzbot bug from 2018 April 17)

2018-10-05 Thread Sebastian Kuzminsky
Another instance of the same problem (also on 4.14.67), this time with the hung task timeout restored to its 120 second default: [ 980.954129] INFO: task systemd:1 blocked for more than 120 seconds. [ 980.954132] Tainted: G OE 4.14.67-solidfire1 #1 [ 980.954133] "echo 0 >

Re: hung task in 4.14 (syzbot bug from 2018 April 17)

2018-10-05 Thread Sebastian Kuzminsky
Another instance of the same problem (also on 4.14.67), this time with the hung task timeout restored to its 120 second default: [ 980.954129] INFO: task systemd:1 blocked for more than 120 seconds. [ 980.954132] Tainted: G OE 4.14.67-solidfire1 #1 [ 980.954133] "echo 0 >

hung task in 4.14 (syzbot bug from 2018 April 17)

2018-10-03 Thread Sebastian Kuzminsky
I think i've run into the bug described here: https://lkml.org/lkml/2018/4/18/188 I've got a binder-free system that reports a hung task with this backtrace: [76800.726654] INFO: task systemd:1 blocked for more than 60 seconds. [76800.726657] Tainted: G OE 4.14.67-solidfire1

hung task in 4.14 (syzbot bug from 2018 April 17)

2018-10-03 Thread Sebastian Kuzminsky
I think i've run into the bug described here: https://lkml.org/lkml/2018/4/18/188 I've got a binder-free system that reports a hung task with this backtrace: [76800.726654] INFO: task systemd:1 blocked for more than 60 seconds. [76800.726657] Tainted: G OE 4.14.67-solidfire1