| 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: <1304374374.3226.20.camel@work-vm> Date: Mon, 02 May 2011 15:12:54 -0700 From: john stultz <johnstul@...ibm.com> To: Christian Hoffmann <email@...istianhoffmann.info> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: Long timeout when booting >= 2.6.38 On Mon, 2011-05-02 at 23:10 +0200, Christian Hoffmann wrote: > >> Hrm. The delay in the dmesg logs doesn't really seem to correlate that > >> closely with the delayed tsc calibration. Hrmm.. > > I also ran it now with calltrace_debug: [snip] > [ 1.455253] calling pci_apply_final_quirks+0x0/0x105 @ 1 > [ 1.455259] pci 0000:00:01.0: MSI quirk detected; subordinate MSI > disabled > [ 146.830206] pci 0000:01:05.0: Boot video device > [ 146.830219] PCI: CLS 64 bytes, default 64 > [ 146.830224] initcall pci_apply_final_quirks+0x0/0x105 returned 0 > after 141967734 usecs Hrm.. Again, this looks more like something off with the MSI quirk bits. I'm a little stumped right off how the refined calibration would impact this. The only difference would be that the TSC clocksource isn't registered at that point (because the refined calibration pushed the registration back a bit), so you might be using the HPET at this point instead of the TSC. Let me know how the clocksource= boot bits changed things. thanks -john -- 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