On Wed, Jul 26, 2017 at 12:11:31PM +0200, Martin Pieuchot wrote: > On 24/07/17(Mon) 23:41, Laurence Tratt wrote: > > On Sun, Jul 23, 2017 at 11:32:06PM +0100, Laurence Tratt wrote: > > > > > extsmaild (http://tratt.net/laurie/src/extsmail/) appears to be > > > causing > > > the final panic, but given that it's just in a "wake every 60 seconds > > > and see if new files have appeared in a directory" loop, I'm not sure > > > why. > > > > I've now triggered another crash, this time without extsmaild (or Iridium) > > running. The trace is here: > > > > https://imagebin.ca/v/3UWOneXfuSWQ > > > > The "culprit" process is now mutt, but the panic is still "out of space in > > kmem_map" and the trace seems to be in ufs_readdir. > > I have seen the same panic message while watching a movie fullscreen > with mplayer yesterday. > > However as soon as CPU0 tried to enter DDB, after typing mach ddbcpu 0, > the machine freeze.
Is the modesetting(4) or intel(4) driver being selected? Check in /var/log/Xorg.log. On my x201, I had stability issues with modesetting (display went dark, followed by a reboot after about 10 seconds) which disappeared after switching back to intel(4) with an xorg.conf: $ cat /etc/X11/xorg.conf Section "Device" Identifier "Device0" Driver "intel" EndSection If that fixes your problem, then it would seem likely that modesetting(4) triggers a memory leak.
