| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20100209221349.GA19683@rhlx01.hs-esslingen.de> Date: Tue, 9 Feb 2010 23:13:49 +0100 From: Andreas Mohr <andi@...as.de> To: Thomas Gleixner <tglx@...utronix.de> Cc: Andreas Mohr <andi@...as.de>, linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>, John Stultz <johnstul@...ibm.com> Subject: Re: clocksource mutex deadlock, cat current_clocksource (2.6.33-rc6/7) On Tue, Feb 09, 2010 at 11:02:02AM +0100, Thomas Gleixner wrote: > Just verified, that there is no timekeeping related patch after > 2.6.33-rc4 except the kgdb lockup prevention patch, which is > not touching any code which is relevant at boot time. > > So bisecting between rc4 and now is probably the best thing to do. Despairing is the best thing to do methinks. -rc5 gcc 4.4 new .config: acpi_pm lockup -rc4 gcc 4.4 new .config: reboot (directly after unpacking kernel) -rc4 gcc 4.4 old (trusted) .config: reboot!! (dito) -rc4 gcc 4.3 old (trusted) .config: reboot!!! (dito) I'm currently zeroing in on the libgcc1 upgrade that I did on 2010-02-04 (which also made gcc-4.4 the default system compiler). I don't have any friggin' idea what else could have caused this. gcc 4.3 has been configured using CC=gcc-4.3 HOSTCC=gcc-4.3 , but as said, this also failed. Andreas Mohr -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists