On 2014/09/10 04:44, Ingo Schwarze wrote: > Sure. When i see ld(1) dying from signals, i'll bump limits. But > that's not what what i'm talking about. Memory allocation failure > in ld(1) is hopefully not going to cause a hard kernel lockup. > > Besides, almost all the kernel lockups i saw today happened while > trying to build either archivers/gtar or misc/fileutils. Those are > not going to hit any limits.
There are certainly some hard kernel lockups that are hit frequently on systems where memory is exhausted (limits or not), though a gtar build (with a 58MB maximum RSS on my laptop) is unlikely to trigger this unless the machine is otherwise under very high memory pressure.. > Anyway, i'm going to shut up now. As i can't even provide a > backtrace, tech@ is clearly the wrong list. Not necessarily, as some things are resistant to traditional debugging and people who don't have deep experience of the involved subsystems are unlikely to know where to start poking to get additional data points that might help track things down..
