[dvblast-devel] Crash dvblastctl

Georgi Chorbadzhiyski gf at unixsol.org
Wed May 16 15:27:58 CEST 2012


Around 05/16/2012 10:58 AM, Вячеслав Адаманов scribbled:
> Periodically comm socket does not give data.
> In dmesg:
> 
> [88105.871371] Pid: 2597, comm: dvblast Not tainted 3.2.12-gentoo #2
> [88105.871374] Call Trace:
> [88105.871385]  [<c154520b>] ? printk+0x18/0x1a
> [88105.871394]  [<c10aab38>] warn_alloc_failed+0xb8/0xf0
> [88105.871398]  [<c10aca40>] __alloc_pages_nodemask+0x430/0x5e0
> [88105.871403]  [<c10acc07>] __get_free_pages+0x17/0x30
> [88105.871407]  [<c10d8872>] kmalloc_order_trace+0x22/0x80
> [88105.871411]  [<c10dba61>] __kmalloc_track_caller+0x171/0x1a0
> [88105.871417]  [<c142f98b>] ? sock_alloc_send_pskb+0x16b/0x290
> [88105.871420]  [<c1432d5c>] __alloc_skb+0x4c/0x100
> [88105.871424]  [<c142f98b>] sock_alloc_send_pskb+0x16b/0x290
> [88105.871432]  [<c102c927>] ? __wake_up_sync_key+0x47/0x60
> [88105.871435]  [<c142fac8>] sock_alloc_send_skb+0x18/0x20
> [88105.871440]  [<c14d313f>] unix_dgram_sendmsg+0x1af/0x530
> [88105.871447]  [<c142c8f1>] sock_sendmsg+0xd1/0x100
> [88105.871451]  [<c105b163>] ? sched_clock_local+0xd3/0x1c0
> [88105.871455]  [<c105b163>] ? sched_clock_local+0xd3/0x1c0
> [88105.871468]  [<c1204e22>] ? _copy_from_user+0x32/0x50
> [88105.871474]  [<c142dbc2>] sys_sendto+0xb2/0xe0
> [88105.871477]  [<c10277d9>] ? kmap_atomic_prot+0x49/0xe0
> [88105.871483]  [<c10c50c3>] ? handle_mm_fault+0xa3/0x130
> [88105.871491]  [<c142e4e6>] sys_socketcall+0x1a6/0x2b0
> [88105.871496]  [<c154dd0c>] sysenter_do_call+0x12/0x22
> [88105.871503]  [<c1540000>] ? igb_probe+0x3cc/0xe51
> [88105.871506] Mem-Info:
> [88105.871509] DMA per-cpu:
> [88105.871512] CPU    0: hi:    0, btch:   1 usd:   0
> [88105.871515] CPU    1: hi:    0, btch:   1 usd:   0
> [88105.871519] Normal per-cpu:
> [88105.871521] CPU    0: hi:  186, btch:  31 usd:   0
> [88105.871525] CPU    1: hi:  186, btch:  31 usd:   0
> [88105.871531] active_anon:2232 inactive_anon:2247 isolated_anon:3
> [88105.871533]  active_file:48461 inactive_file:53179 isolated_file:29
> [88105.871536]  unevictable:0 dirty:47051 writeback:2367 unstable:0
> [88105.871538]  free:1396 slab_reclaimable:8014 slab_unreclaimable:1705
> [88105.871540]  mapped:1754 shmem:40 pagetables:138 bounce:0
> [88105.871548] DMA free:2064kB min:84kB low:104kB high:124kB
> active_anon:72kB inactive_anon:128kB active_file:2168kB
> inactive_file:9488kB unevictable:0kB isolated(anon):0kB
> isolated(file):0kB present:15800kB mlocked:0kB dirty:9000kB
> writeback:44kB mapped:0kB shmem:0kB slab_reclaimable:1764kB
> slab_unreclaimable:228kB kernel_stack:8kB pagetables:0kB unstable:0kB
> bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
> [88105.871560] lowmem_reserve[]: 0 491 491 491
> [88105.871574] Normal free:3520kB min:2792kB low:3488kB high:4188kB
> active_anon:8856kB inactive_anon:8860kB active_file:191676kB
> inactive_file:203228kB unevictable:0kB isolated(anon):12kB
> isolated(file):116kB present:502792kB mlocked:0kB dirty:179204kB
> writeback:9424kB mapped:7016kB shmem:160kB slab_reclaimable:30292kB
> slab_unreclaimable:6592kB kernel_stack:528kB pagetables:552kB
> unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0
> all_unreclaimable? no
> [88105.871588] lowmem_reserve[]: 0 0 0 0
> [88105.871596] DMA: 7*4kB 1*8kB 11*16kB 22*32kB 8*64kB 5*128kB 0*256kB
> 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2068kB
> [88105.871613] Normal: 812*4kB 30*8kB 2*16kB 0*32kB 0*64kB 0*128kB
> 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3520kB
> [88105.871631] 101907 total pagecache pages
> [88105.871634] 163 pages in swap cache
> [88105.871637] Swap cache stats: add 3248, delete 3085, find 943/997
> [88105.871641] Free swap  = 496488kB
> [88105.871644] Total swap = 506040kB
> [88105.873375] 130768 pages RAM
> [88105.873377] 0 pages HighMem
> [88105.873378] 3297 pages reserved
> [88105.873380] 103386 pages shared
> [88105.873381] 28473 pages non-shared

Your kernel oopses and kills dvblastctl. I don't think this is a dvblastctl bug.
Latest 3.2 stable is 3.2.17 try upgrading, this bug might be fixed.

-- 
Georgi Chorbadzhiyski
http://georgi.unixsol.org/


More information about the dvblast-devel mailing list