| 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, 5 Jun 2007 02:24:11 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Ingo Molnar <mingo@...e.hu> Cc: linux-kernel@...r.kernel.org Subject: Re: 2.6.22-rc3-mm1 On Tue, 5 Jun 2007 11:11:51 +0200 Ingo Molnar <mingo@...e.hu> wrote: > hm, mm1 hangs during bootup on one of my boxes: > > Calling initcall 0xc0628d39: pci_mmcfg_late_insert_resources+0x0/0x44() > initcall 0xc0628d39: pci_mmcfg_late_insert_resources+0x0/0x44() returned 0. > initcall 0xc0628d39 ran for 0 msecs: > pci_mmcfg_late_insert_resources+0x0/0x44() > Calling initcall 0xc062abd1: tcp_congestion_default+0x0/0xf() > initcall 0xc062abd1: tcp_congestion_default+0x0/0xf() returned 0. > initcall 0xc062abd1 ran for 0 msecs: tcp_congestion_default+0x0/0xf() > > it usually hangs in different places. In my experience that means that it wedged in a timer tick. Often the first one. > Full bootlog below. Same kernel > bzImage boots fine on another box. > > the NMI watchdog warning is a bit weird: > > Calling initcall 0xc0613e4f: check_nmi_watchdog+0x0/0x1a8() > Testing NMI watchdog ... CPU#0: NMI appears to be stuck (0->0)! > CPU#1: NMI appears to be stuck (0->0)! > initcall 0xc0613e4f: check_nmi_watchdog+0x0/0x1a8() returned -1. > initcall 0xc0613e4f ran for 27 msecs: check_nmi_watchdog+0x0/0x1a8() > > i'll test it in a minute with that turned off. > hm. I haven't seen any similar reports. - 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