On Mon, Oct 15, 2018 at 11:23:11AM -0500, Jeff Rickman wrote: > > Should this be filed somewhere in Debian and if so which package? > See my comment at the end.
> FYI - No, the impacted system does not support "reportbug" because the > system is heavily firewalled for secuity reasons. > You can still install reportbug, use it to generate the report, save it to a file (this is one of the actions reportbug lets you take at the end instead of sending), then transfer the file to a system from which you can send the port. > > [ 6787.703456] list_add corruption. next->prev should be prev > (000000000533875c), but was 00000000c2b0df70. (next=00000000c2b0df70). > [ 6787.703475] ------------[ cut here ]------------ > [ 6787.703477] kernel BUG at > /build/linux-43CEzF/linux-4.16.12/lib/list_debug.c:25! > [ 6787.703578] invalid opcode: 0000 [#1] SMP PTI I am not an expert, but the file name (lib/list_debug.c) suggests that the problem exists in the actual kernel core itself, instead of in a module or something like that. I would start by searching the existing kernel bug reports in Debian for references to that file. If one exists, you can add your information there and perhaps it will help achieve resolution. If not, you can create a new bug report. Regards, -Roberto -- Roberto C. Sánchez