failed to set signal flags properly for ast()
Robert Watson
rwatson at freebsd.org
Sat Feb 28 16:31:10 PST 2004
On Sat, 28 Feb 2004, Robert Watson wrote:
>
> On Sat, 28 Feb 2004, Poul-Henning Kamp wrote:
>
> > On a -current kernel from this morning, I ran a "make -j 12 -s
> > buildworld".
> >
> > At some point I pressed ctrl-Z and it started spitting tons of
> > failed to set signal flags properly for ast() out on the serial
> > console, but after about a minute it stopped and the system continued.
>
> I just experienced something identical. I set up an NFS root box to try
> to reproduce what Alan Cox reported, and hit Ctrl-Z to check which
> version of the kernel I was running during the build. Immediatly got a
> lot of the following:
>
> failed to set signal flags properly for ast()
> failed to set signal flags properly for ast()
> failed to set signal flags properly for ast()
> failed to set signal flags properly for ast()
> failed to set signal flags properly for ast()
> failed to set signal flags properly for ast()
> failed to set signal flags properly for ast()
> failed to set signal flags properly for ast()
>
> It hasn't finished that here yet, but if it's going to stop it might
> take a bit as the serial console is 9600bps. This box was basically
> running a buildworld -j 6 with /usr/src in NFS, and /usr/obj in
> swap-backed md. No threaded applications running, etc.
As a follow-up, it kept spinning printing that message until I
foregrounded the build again, at which point it went away.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
robert at fledge.watson.org Senior Research Scientist, McAfee Research
More information about the freebsd-current
mailing list