kernel panic involving drbd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
High
|
Unassigned |
Bug Description
It was brought to my attention the following kernel panic:
SYSTEM MAP: /boot/System.
DEBUG KERNEL: /usr/lib/
DUMPFILE: ./dump.201503271156 [PARTIAL DUMP]
CPUS: 12
DATE: Fri Mar 27 12:56:49 2015
UPTIME: 13 days, 19:14:00
LOAD AVERAGE: 1.72, 0.67, 0.28
TASKS: 340
NODENAME: bluegrass3
RELEASE: 3.16.0-31-generic
VERSION: #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015
MACHINE: x86_64 (2397 Mhz)
MEMORY: 63.9 GB
PANIC: "Kernel panic - not syncing: hung_task: blocked tasks"
[1191751.738854] request: minor=1, resource=
[1191759.892350] drbd vm-database: peer( Secondary -> Unknown ) conn( Connected -> Disconnecting ) pdsk( UpToDate -> DUnknown )
[1191759.892359] drbd vm-database: asender terminated
[1191759.892362] drbd vm-database: Terminating drbd_a_vm-datab
[1191759.892471] drbd vm-database: Connection closed
[1191759.892480] drbd vm-database: conn( Disconnecting -> StandAlone )
[1191759.892481] drbd vm-database: receiver terminated
[1191759.892485] drbd vm-database: Terminating drbd_r_vm-datab
[1191759.892497] block drbd6: disk( UpToDate -> Failed )
[1191759.902311] block drbd6: bitmap WRITE of 0 pages took 0 jiffies
[1191759.902315] block drbd6: 0 KB (0 bits) marked out-of-sync by on disk bit-map.
[1191759.902322] block drbd6: disk( Failed -> Diskless )
[1191759.902565] block drbd6: drbd_bm_resize called with capacity == 0
[1191759.902585] drbd vm-database: Terminating drbd_w_vm-datab
[1191992.802513] INFO: task drbdsetup:20254 blocked for more than 120 seconds.
[1191992.834141] Not tainted 3.16.0-31-generic #41~14.04.1-Ubuntu
[1191992.862889] "echo 0 > /proc/sys/
[1191992.900367] drbdsetup D ffff88085fc53440 0 20254 1 0x00000004
[1191992.900371] ffff880845967ab8 0000000000000086 ffff880abe65c750 ffff880845967fd8
[1191992.900374] 0000000000013440 0000000000013440 ffff8808546d65e0 ffff8808b5365800
[1191992.900378] 0000000000001e00 0000000000000400 000000000000000e ffff8808b5365a30
[1191992.900388] Call Trace:
[1191992.900398] [<ffffffff81767
[1191992.900407] [<ffffffffc078f
[1191992.900413] [<ffffffff810b4
[1191992.900418] [<ffffffffc0787
[1191992.900422] [<ffffffffc0784
[1191992.900426] [<ffffffffc0787
[1191992.900431] [<ffffffff81692
[1191992.900432] [<ffffffff81692
[1191992.900434] [<ffffffff81692
[1191992.900436] [<ffffffff81690
[1191992.900438] [<ffffffff81691
[1191992.900439] [<ffffffff81690
[1191992.900441] [<ffffffff81690
[1191992.900448] [<ffffffff81333
[1191992.900452] [<ffffffff81646
[1191992.900456] [<ffffffff811d3
[1191992.900458] [<ffffffff811d4
[1191992.900461] [<ffffffff811d4
[1191992.900464] [<ffffffff8176b
[1191992.900465] sending NMI to all CPUs:
Dump at:
http://
Changed in linux (Ubuntu): | |
assignee: | nobody → Rafael David Tinoco (inaddy) |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
description: | updated |
description: | updated |
Changed in linux (Ubuntu): | |
assignee: | Rafael David Tinoco (rafaeldtinoco) → nobody |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1439872
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.