Alpha lockups with statfs changes

Kris Kennaway kris at obsecurity.org
Sat Nov 15 04:32:57 PST 2003


FYI, I accidentally ran a post-statfs alpha world inside a chroot on
the August-ish 5.1-C alpha machines, and it caused half of them to
lock up (no break to debugger possible from serial console, no console
messages - including the signal 12s that I'd expect to be there from
the binaries running inside the chroot).  It looks like they locked up
with the first incompatible binary they ran, instead of dying with
signal 12 - or perhaps they ran a binary that did not use the new
syscall, but did something else to cause the lockup.

The machines that didn't lock up have lots of sig12s on the console,
but they also became unresponsive for an hour or so while this was
going on (my heartbeat monitoring script could not connect to any of
the cluster machines, although half of them eventually started
allowing ssh connections again).

Kris



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-alpha/attachments/20031115/ed39a63d/attachment.bin


More information about the freebsd-alpha mailing list