On Thu, Nov 07, 2019 at 03:32:23PM -0500, Mark Johnston wrote: > On Thu, Nov 07, 2019 at 12:29:19PM -0800, Steve Kargl wrote: > > I haven't seen anyone post about an unkillable process > > (even by root), which consumes 100% cpu. > > > > last pid: 4592; load averages: 1.24, 1.08, 0.74 up 13+20:21:20 12:26:29 > > 68 processes: 2 running, 66 sleeping > > CPU: 0.1% user, 0.0% nice, 12.6% system, 0.0% interrupt, 87.2% idle > > Mem: 428M Active, 11G Inact, 138M Laundry, 2497M Wired, 1525M Buf, 2377M Free > > Swap: 16G Total, 24M Used, 16G Free > > > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > > 69092 kargl 2 45 0 342M 148M CPU2 2 12:51 100.07% chrome > > > > > > Neither of these have an effect. > > > > kill -1 69092 > > kill -9 69069 > > > > Attempts to attach gdb831 to -p 69092 leads to hung xterm. > > Could you please show us the output of "procstat -kk 69092"? Unfortunately, no. I just rebooted the system to kill 69092. During 'shutdown -r now', a message appeared on the console warning that some processes would not die. Then 'shutdown -r now' hung the console. :( Before rebooting I did try a number of ps and procstat commands, 69092 was chrome: --type=gpu-process --field-trial-handle=long-string-of-number --gpu-preferences=long-string-with-IAs So, it seems that drm-current-kmod may not be happy. For the record, uname gives FreeBSD 13.0-CURRENT r353571 -- SteveReceived on Thu Nov 07 2019 - 19:55:59 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:22 UTC