Displaying 7 results from an estimated 7 matches for "blocked_task".
Did you mean:
blocked_tasks
2013 Oct 23
2
[virtio-net] BUG: sleeping function called from invalid context at kernel/mutex.c:616
...|
| INFO:task_blocked_for_more_than_seconds | 0 | 0 | 2 |
| INFO:NMI_handler(arch_trigger_all_cpu_backtrace_handler)took_too_long_to_run:msecs | 0 | 0 | 1 |
| Kernel_panic-not_syncing:hung_task:blocked_tasks | 0 | 0 | 1 |
| BUG:kernel_test_crashed | 0 | 0 | 3 |
| BUG:kernel_test_hang | 0...
2013 Oct 23
2
[virtio-net] BUG: sleeping function called from invalid context at kernel/mutex.c:616
...|
| INFO:task_blocked_for_more_than_seconds | 0 | 0 | 2 |
| INFO:NMI_handler(arch_trigger_all_cpu_backtrace_handler)took_too_long_to_run:msecs | 0 | 0 | 1 |
| Kernel_panic-not_syncing:hung_task:blocked_tasks | 0 | 0 | 1 |
| BUG:kernel_test_crashed | 0 | 0 | 3 |
| BUG:kernel_test_hang | 0...
2013 Oct 28
0
[virtio-net] BUG: sleeping function called from invalid context at kernel/mutex.c:616
...O:task_blocked_for_more_than_seconds | 0 | 0 | 2 |
> | INFO:NMI_handler(arch_trigger_all_cpu_backtrace_handler)took_too_long_to_run:msecs | 0 | 0 | 1 |
> | Kernel_panic-not_syncing:hung_task:blocked_tasks | 0 | 0 | 1 |
> | BUG:kernel_test_crashed | 0 | 0 | 3 |
> | BUG:kernel_test_hang...
2013 Nov 04
2
[virtio_blk] WARNING: CPU: 0 PID: 1 at fs/sysfs/dir.c:526 sysfs_add_one()
...664 | 3 |
| BUG:kernel_test_hang | 4422 | 1 |
| INFO:task_blocked_for_more_than_seconds | 118 | |
| Kernel_panic-not_syncing:hung_task:blocked_tasks | 15 | |
| BUG:kernel_test_crashed | 90 | |
| Out_of_memory:Kill_process | 30 |...
2013 Nov 04
2
[virtio_blk] WARNING: CPU: 0 PID: 1 at fs/sysfs/dir.c:526 sysfs_add_one()
...664 | 3 |
| BUG:kernel_test_hang | 4422 | 1 |
| INFO:task_blocked_for_more_than_seconds | 118 | |
| Kernel_panic-not_syncing:hung_task:blocked_tasks | 15 | |
| BUG:kernel_test_crashed | 90 | |
| Out_of_memory:Kill_process | 30 |...
2013 Oct 20
3
[virtio-net] BUG: sleeping function called from invalid context at kernel/mutex.c:616
Greetings,
I got the below dmesg and the first bad commit is
commit 3ab098df35f8b98b6553edc2e40234af512ba877
Author: Jason Wang <jasowang at redhat.com>
Date: Tue Oct 15 11:18:58 2013 +0800
virtio-net: don't respond to cpu hotplug notifier if we're not ready
We're trying to re-configure the affinity unconditionally in cpu hotplug
callback. This may lead the
2013 Oct 20
3
[virtio-net] BUG: sleeping function called from invalid context at kernel/mutex.c:616
Greetings,
I got the below dmesg and the first bad commit is
commit 3ab098df35f8b98b6553edc2e40234af512ba877
Author: Jason Wang <jasowang at redhat.com>
Date: Tue Oct 15 11:18:58 2013 +0800
virtio-net: don't respond to cpu hotplug notifier if we're not ready
We're trying to re-configure the affinity unconditionally in cpu hotplug
callback. This may lead the