| 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
| ||
|
Date: Tue, 25 Aug 2009 23:43:00 -0400 From: Patrick <skibler@...il.com> To: linux-kernel@...r.kernel.org Subject: Boot hang after io scheduler registration http://lkml.indiana.edu/hypermail/linux/kernel/0812.3/00547.html The above archived post mimics my problem exactly, unfortunately it offers no solution. I have added initcall_debug to my boot string and I have transcribed the output below. I have an Intel Core 2 Quad Q6600 cpu on an Asus P5K SE (Intel P35 chipset) motherboard. I built a 64-bit kernel yesterday (08/24/09) from the git source, it reports itself as 2.6.31-rc7. Please note that if I boot with the noapic and nolapic options, the system will boot normally, but the kernel will only report a single cpu/core (cat /proc/cpuinfo, top, etc). The trouble happens with ubuntu 9.04 kernel, the latest weekly gentoo live cd, and the current arch linux core install cd. calling aes_init+0x0/0xc @ 1 initcall aes_init+0x0/0xc returned 0 after 61 usecs calling deflate_mod_init+0x0/0xc @ 1 initcall deflate_mod_init+0x0/0xc returned 0 after 224 usecs calling krng_mod_init+0x0/0xc @ 1 alg: No test for stdrng (krng) initcall krng_mod_init+0x0/0xc returned 0 after 134 usecs calling proc_genhd_init+0x0/0x3f @ 1 initcall proc_genhd_init+0x0/0x3f returned 0 after 2 usecs calling noop_init+0x0/0x17 @ 1 io scheduler noop registered initcall noop_init+0x0/0x17 returned 0 after 123 usecs calling as_init+0x0/0x17 @ 1 io scheduler anticipatory registered initcall as_init+0x0/0x17 returned 0 after 116 usecs calling deadline_init+0x0/0x18 @ 1 io scheduler deadline registered (default) initcall deadline_init+0x0/0x18 returned 0 after 118 usecs calling cfq_init+0x0/0xb0 @ 1 io scheduler cfq registered initcall cfq_init+0x0/0xb0 returned 0 after 138 usecs calling percpu_counter_startup+0x0/0x2d @ 1 initcall percpu_counter_startup+0x0/0x2d returned 0 after 0 usecs calling pci_init+0x0/0x38 @ 1 _ -- 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