Re: Google Chrome cause locks held in system (kernel 4.15 rc2)

mikhail
2017-12-10T21:49:39Z

On Sat, 2017-12-09 at 23:14 +0900, Tetsuo Handa wrote:
> Under OOM lockup situation, kernel messages can unlikely be saved to
> syslog
> files, for writing to files involves memory allocation. Can you set
> up
> netconsole or serial console explained at
> http://events.linuxfoundation.org/sites/events/files/slides/LCJ2014-e
> n_0.pdf ?
> If neither console is possible, it would become difficult to debug.

netconsole works only within local network? destination ip may be from
another network?

[11415.184163] netpoll: netconsole: local port 6665
[11415.184168] netpoll: netconsole: local IPv4 address 0.0.0.0
[11415.184169] netpoll: netconsole: interface 'enp2s0'
[11415.184171] netpoll: netconsole: remote port 6666
[11415.184173] netpoll: netconsole: remote IPv4 address 213.136.82.171
[11415.184174] netpoll: netconsole: remote ethernet address
ff:ff:ff:ff:ff:ff
[11415.184179] netpoll: netconsole: local IP 192.168.1.85
[11415.184738] console [netcon0] enabled
[11415.184741] netconsole: network logging started

But on remote host nothing happens when I do SysRq-t

Of course I compiled and launched ./udplogger on remote host under
tmux. And add udp port 6666 to firewalld rule.
# firewall-cmd --permanent --add-port=6666/udp && systemctl restart
firewalld