On Fri, Jun 10, 2016 at 2:54 PM, Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote: > On Fri, 10 Jun 2016, Dmitry Vyukov wrote: >> Here is the second log: >> https://gist.githubusercontent.com/dvyukov/dd7970a5daaa7a30f6d37fa5592b56de/raw/f29182024538e604c95d989f7b398816c3c595dc/gistfile1.txt >> >> I've hit only twice. The first time I tried hard to reproduce it, with >> no success. So unfortunately that's all we have. >> >> Re logs: my setup executes up to 16 programs in parallel. So for >> normal BUGs any of the preceding 16 programs can be guilty. But since >> this check is asynchronous, it can be just any preceding program in >> the log. > > Ok. > >> I would expect that it is triggered by some rarely-executing poorly >> tested code. Maybe mmap of some device? > > That's the mmap(dev) list which is common between the two log files: > > vcsn > ircomm > rfkill > userio > dspn > mice > midi > sndpcmc > hidraw0 > vga_arbiter > lightnvm > sr > > Dunno, if that's the right direction, but exposing these a bit more might be > worth to try. I am now running both of these logs for several hours (2.5M executions). No failures so far... -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>