Re: 2.6.8.1-mm4 [ls]trace freeze
From: Grant Wilson
Date: Mon Aug 23 2004 - 17:08:23 EST
I get similar results on amd64 running Debian unstable:
> strace rxvt
bad: scheduling while atomic!
Call Trace: <ffffffff8039d62e>{schedule+94}
<ffffffff8013f27c>{ptrace_notify_info+316}
<ffffffff8013f468>{get_signal_to_deliver+456}
<ffffffff8010e9c3>{do_signal+163}
<ffffffff8010f52f>{sysret_signal+28}
<ffffffff8010f81b>{ptregsyscall_common+103}
execve("/usr/bin/rxvt".....
rxvt[3639]: segfault @ 0000002a95556e60 ...
bad: scheduling while atomic!
Call Trace: <ffffffff8039d26e>{schedule+94}
<ffffffff8010faca>{retint_careful+13}
bad: scheduling while atomic!
Call Trace: <ffffffff8039d62e>{schedule+94}
<ffffffff8013f27c>{ptrace_notify_info+316}
<ffffffff8013f468>{get_signal_to_deliver+456}
<ffffffff8010e9c3>{do_signal+163}
<ffffffff8013360d>{printk+141} <ffffffff8039dc01>{thread_return+41}
<ffffffff8010fb1c>{retint_signal}
--- SIGSEV (Segmentation fault) @ 0 (0) ---
Kernel panic - not syncing: Aiee, killing interrupt handler!
Rgds,
Grant Wilson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/