I'm running 16.04 and seeing the same problem on Linux 4.15.0-45. I can also confirm that when booting with 4.15.0-43 I no longer see the problem.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1814393 Title: "make: write error: stdout" on parallel builds Status in linux-signed package in Ubuntu: Confirmed Bug description: - Release of Ubuntu: 18.04.1 LTS (Kubuntu). - Package version: linux-image-4.15.0-44-generic, linux-image-4.15.0-45-generic. - Expected outcome: Large parallel make build completing properly. - What happened instead: Build stops with "make: write error: stdout". Full explanation: Since the update to kernel 4.15.0-44 (linux-image-4.15.0-44-generic) in Kubuntu Bionic I'm experiencing issues in my ThinkPad P52 laptop during large parallel builds of source code (eg: a buildroot full rebuild for a work project). Note that this reports isn't about kernel builds, but about large project builds in general. I don't think it's relevant, but I'm running those builds in an schroot with the same Ubuntu Bionic distro I'm also using as main host distro. The specific error I get is this (in Spanish): make[4]: error al escribir: stdout I call Buildroot's make like this from KDE Konsole with "infinite history buffer" enabled (uses a tmp file to store the logs): V=1 make ...some stuff... 2>&1 However, the error is reproducible in Konsole even if I call make without options and also if I use "limited (in-memory) history buffer" as well as "no history buffer". Buildroot autoselects a parallelization level (-j) automatically. In my case, I'm using a Xeon E-2176 CPU with 12 threads. Searching on the Internet I found a thread[1] where people from the GNU Make project say that the error may be coming from the C runtime library (and I suspect originating from the kernel). I can NOT reproduce the issue on linux-image-4.15.0-43-generic (selected from grub at boot), but I experience it with linux- image-4.15.0-44-generic and linux-image-4.15.0-45-generic. That's why I'm reporting this bug against the linux package. Interestingly enough, I can NOT reproduce the issue on linux- image-4.15.0-45-generic (haven't tried previous versions) when building from xterm instead of Konsole. Unfortunately, this laptop has a 4K screen and xterm isn't an option for me. If I build redirecting stdout and stderr to different files to avoid terminal output and then watching the stdout file with tail -f, the tail command eventually finishes although the build continues and I can keep watching it by running tail again. An infinite build loop never finishes with this redirection (error not reproducible). Same results with the 2>&1 redirection to a single file. All this looks a bit like a poltergeist, but the only thing I'm sure about is that it all started with the upgrade from 4.15.0-43 to -44 and it continues on -45. Thank you. [1] http://gnu-make.2324884.n4.nabble.com/Spurious-quot-write-error-quot-on-parallel-builds-td15695.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1814393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
