On Mon, 15 Jul 2002, Bill Huey wrote:
> I get a billion of these:
>
> failed to set signal flags proprly for ast()
> failed to set signal flags proprly for ast()
> failed to set signal flags proprly for ast()
> failed to set signal flags proprly for ast()
> failed to set signal flags proprly for ast()
> failed to set signal flags proprly for ast()
>
> Is this KSE related ?
Maybe. I got a few of these for my original ast() changes an instant
after I committed them (long before KSEIII), but haven't been able to
duplicate the problem (perhaps because they only occurred for SMP and
I rarely run SMP). I use the following change which prints more info
and fixes a spelling error (*blush*).
%%%
Index: subr_trap.c
===================================================================
RCS file: /home/ncvs/src/sys/kern/subr_trap.c,v
retrieving revision 1.221
diff -u -2 -r1.221 subr_trap.c
--- subr_trap.c 11 Jul 2002 02:18:33 -0000 1.221
+++ subr_trap.c 12 Jul 2002 22:05:44 -0000
@@ -82,6 +88,13 @@
mtx_lock_spin(&sched_lock);
if (SIGPENDING(p) && ((p->p_sflag & PS_NEEDSIGCHK) == 0 ||
- (ke->ke_flags & KEF_ASTPENDING) == 0))
- printf("failed to set signal flags proprly for ast()\n");
+ (ke->ke_flags & KEF_ASTPENDING) == 0)) {
+ printf("failed to set signal flags properly for ast()\n");
+ printf(
+ "proc %s sig %#x, sigmask %#x, sigflag %d, astflag %d\n",
+ p->p_comm, ((int *)&p->p_siglist)[0],
+ ((int *)&p->p_sigmask)[0],
+ (p->p_sflag & PS_NEEDSIGCHK) != 0,
+ (ke->ke_flags & KEF_ASTPENDING) != 0);
+ }
mtx_unlock_spin(&sched_lock);
PROC_UNLOCK(p);
%%%
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
