Hi! > > >> OK, - and now we are looking forward to *your* ideas how to solve this. > > > > > > After four days playing games around git bisect - real winner is > > > debian gcc-8.2.0-9. Upgrade it to 8.2.0-10 or use 7.3.0-30 version for > > > same kernel + config - does not exhibit ext4 corruption. > > > > > > I think I hit this https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87859 > > > with 8.2.0-9 version. > > > > > Good that it works for you. But others used gcc 5.4.0 or 6.3.0 and were > > hit anyway: https://bugzilla.kernel.org/show_bug.cgi?id=201685#c165 > > Depends on workload pattern. 4.19.5 built with 8.2.0-10 and 7.3.0-30 - > crashed after 4 hours of usage (previous build crash in 5 min). > So my assumption about broken gcc is wrong. Would it be possible to try vanilla 4.19? (Not stable?) I test vanilla and -next kernels every week or two, and did not have ext4 problems recently. I guess many kernel developers test mainline but not stable... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
