Re: "sigreturn: eflags = 0x80283" after medium-to-high load

Ralf S. Engelschall wrote:
Just FYI: When I compile lots of C++ code under 8.0 or 7.0 (both as of
2007-10-27 and running on ZFS inside a virtual machine) I'm still able
to regularily bring the system into an unusable state. The effect is
that first on the console the following kernel messages occur:

sigreturn: eflags = 0x80283
sigreturn: eflags = 0x80297

Then after I type e.g. CTRL-C in my C++ compile session over SSH more
such "sigreturn: eflags = 0x80283" occur on the console (and without
bringing back a shell prompt on the SSH session). At this stage I also
no longer can login via SSH through a new second SSH connection. Only on
the console I still can perform a "sync; sync; sync; reboot" to rescue.
In this situation even a regular "shutdown -r now" often just causes
more "sigreturn: eflags = 0x80297" outputs but isn't really able to
finally reboot the system.

Sounds like you need to do some debugging with DDB to identify the system state when it hangs.

Kris

_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Error message: inetd[667]: ssh/tcp: bind: Address already in use
    ... Can anyone please help me with this error message which pops up at regular ... intervals on the console and in the log? ... ssh is usually started as a daemon via /etc/rc.d/sshd, ...
    (freebsd-questions)
  • Re: xinetd.conf | SSH telnet
    ... > While this works fine for preventing 'regular' telnet access to the ... > connections. ... SSH is a seperate service, so if you're going to be running the SSH ...
    (comp.os.linux.security)