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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



mikhail wrote:
> 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-en_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?

netconsole can work with another network.

(step 1) Verify that UDP packets are reachable. You can test with

         # echo test > /dev/udp/213.136.82.171/6666

         if you are using bash.

(step 2) Verify that you specified gateway's MAC address rather than
         target host's MAC address. "ff:ff:ff:ff:ff:ff" suggests that
         netconsole is unable to resolve correct MAC address.
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux