Skip to content
Advertisement

Tag: crash

what is the . (dot) and + (plus) after the lock name in the kernel crash (task hung)?

I’ve found that there are dot and plus signs in the kernel crash when the kernel detected task hung. Showing all locks held in the system: 2 locks held by khungtaskd/737: #0: (rcu_read_lock){….}, at: [<00000000eaa2e968>] check_hung_uninterruptible_tasks kernel/hung_task.c:175 [inline] #0: (rcu_read_lock){….}, at: [<00000000eaa2e968>] watchdog+0x1c5/0xd60 kernel/hung_task.c:249 #1: (tasklist_lock){.+.+}, at: [<000000005ed461f9>] debug_show_all_locks+0xd3/0x400 kernel/locking/lockdep.c:4464 What is the dot and plus signs between the brackets

could not to setup crash dump on centos7 for debug kernel

I am trying to setup kdump to generate the vmcore for kernel-3.10.0-123.el7. For the perf kernel kernel-3.10.0-123.el7.x86_64.rpm i setup kdump and kdump is working fine too, generating vmcore. Then i installed kernel-debug-3.10.0-123.el7.x86_64.rpm using yum install kernel-debug-3.10.0-123.el7.x86_64.rpm and kdump worked fine. But then i didnt have vmlinux to read vmcore of debug kernel. Then I build source using rpmbuild from the

Crash when calling autoSizeColumn on worksheet, when run under Linux (Servicemix)

I’ve written module that generates excel, and deployed it under Servicemix. In Windows environment everything is fine, but under Linux Servicemix unexpectedly crashes on following call: I’m using POI version 4.2-FINAL, FuseESB 4.2, Java 5.0. There are, however, no hs_err*.pid files. Servicemix logs ends on first autoSizeColumn call. Did anyone met such behaviour and know, how it is caused and

Advertisement