Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753384Ab3F3ALh (ORCPT ); Sat, 29 Jun 2013 20:11:37 -0400 Received: from mail-ve0-f182.google.com ([209.85.128.182]:57367 "EHLO mail-ve0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751672Ab3F3ALf (ORCPT ); Sat, 29 Jun 2013 20:11:35 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 29 Jun 2013 17:11:34 -0700 X-Google-Sender-Auth: Il5KvkIBXglNfwD13ackLq_TgMk Message-ID: Subject: Re: Linux 3.10-rc7 From: Linus Torvalds To: Sergey Meirovich Cc: David Airlie , Alex Deucher , Jerome Glisse , Linux Kernel Mailing List , DRI Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1447 Lines: 32 On Sat, Jun 29, 2013 at 4:52 PM, Sergey Meirovich wrote: > > There was overheating issue, that caused forced power off in the > middle of the first compile. Ok, then the thing is easily explained by simply the filesystem being shut down in an incomplete state. Sounds like the mkregtable binary had been created but not written out, and the kernel (or rather, shell) considers an empty executable to the same as "true", so after the machine came back, that counts as a "successful" binary, it just obviously doesn't write anything to stdout, which in turn then explains the empty r200_reg_safe.h file. So basically it boils down to: if the machine shuts down in the middle of a build, without "make" having time to clean up partially built files etc, you can get into strange inconsistent build trees and you might want to do a "git clean -dqfx" to get rid of everything generated. But in your case it was probably just that one file. Might be a good idea to do a clean rebuild anyway. (Side note: I've seen 'ccache' have odd stale caches too after unclean shutdowns, and then it's not sufficient to clean the build tree, you need to do "ccache -C" too). Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/