linux-kernel - Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080218050056.fb0fc0bf.akpm@linux-foundation.org>
Date:	Mon, 18 Feb 2008 05:00:56 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Chris Rankin <rankincj@...oo.com>
Cc:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Linux 2.6.24.1  - kernel does not boot; IRQ trouble?

On Sun, 17 Feb 2008 00:54:08 +0000 (GMT) Chris Rankin <rankincj@...oo.com> wrote:

> [Try this again, except this time I'll force the attachment as inline text!]
> 
> Hi,
> 
> I have managed to boot 2.6.24.1 on this machine, with the NMI watchdog enabled, by using the
> "acpi=noirq" option. (There does seem to be some unhappiness with bridge symlinks in sysfs,
> though.)
> 

Is this a regression?  If so, which was the latest kernel version which
worked OK?

> NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
> NFSD: starting 90-second grace period
> [drm] Initialized drm 1.1.0 20060810
> [drm] Initialized mga 3.2.1 20051102 on minor 0
> agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
> agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
> agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
> [drm] Initialized card for AGP DMA.
> 

and here it hangs, I assume?

Please add initcall_debug to the kernel boot command line so we can see if
we can get a more precise idea of where it went wrong.

Do you believe that this hang is somehow caused by x86 NMI?  If so, why?

Thanks.
--
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/