From: D. B. <db...@en...> - 2004-08-06 19:17:13
|
ok - i have skas hosts - and i'm tired of this occasional hang. BEGIN HACK ALERT -- i have 'can_do_skas()' return 1 -- END HACK ALERT and now the kernel fails to pass control to init ? why ? (run_init_process is called with /sbin/init - but it just hangs...) any ideas? D. Bahi wrote: > seems like there is a race condition around this > sometimes i get this printout - sometimes i don't > and sometimes it's fine - gets worse with higher > system load here's the console output: > > Checking for the skas3 patch in the host...found > Checking for /proc/mm...found > CONFIG_HIGHMEM not enabled - physical memory shrunk to 499122176 bytes > Kernel virtual memory size shrunk to 32505856 bytes > capture_stack : Expected SIGSTOP, got status = 0x1c7f > > best backtrace i could get: > > #4 0xa000a2b0 in main (argc=12, argv=0xbfffdb24, envp=0xbfffdb58) at > arch/um/main.c:146 > #3 0xa009c2e2 in linux_main (argc=12, argv=0xbfffdb24) at um_arch.c:351 > #2 0xa0097124 in can_do_skas () at process.c:265 > #1 0xa0097028 in stop_ptraced_child (pid=32285, stack=0x40001000, > exitcode=1) at process.c:192 > #0 0xa000f387 in panic (fmt=0xa018db00 "check_ptrace : child exited > with status 0x%x") at panic.c:111 > > -- > db -- There are two kinds of people in this world: Those that enter a room and turn the television set on, and those that enter a room and turn the television set off. -- Raymond Shaw, The Manchurian Candidate (1962). |