From: Andrew Morton <akpm@linux-foundation.org>
To: Chris Rankin <rankincj@yahoo.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?
Date: Mon, 18 Feb 2008 05:00:56 -0800 [thread overview]
Message-ID: <20080218050056.fb0fc0bf.akpm@linux-foundation.org> (raw)
In-Reply-To: <23590.97305.qm@web52910.mail.re2.yahoo.com>
On Sun, 17 Feb 2008 00:54:08 +0000 (GMT) Chris Rankin <rankincj@yahoo.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.
next prev parent reply other threads:[~2008-02-18 13:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 0:54 Linux 2.6.24.1 - kernel does not boot; IRQ trouble? Chris Rankin
2008-02-18 13:00 ` Andrew Morton
2008-02-18 13:16 ` Chris Rankin
2008-02-18 16:53 ` Stephen Hemminger
2008-02-18 19:42 ` Chris Rankin
2008-02-18 20:06 ` Stephen Hemminger
2008-02-19 8:47 ` Kay Sievers
2008-02-22 9:11 ` Kay Sievers
2008-02-22 9:41 ` Chris Rankin
2008-02-18 13:00 ` Andrew Morton [this message]
2008-02-18 13:13 ` Chris Rankin
2008-02-26 22:36 ` Chris Rankin
2008-02-26 23:40 ` Greg KH
2008-02-27 0:55 ` Chris Rankin
2008-02-27 2:52 ` Andrew Morton
2008-02-27 8:39 ` Chris Rankin
2008-03-02 2:43 ` Linux 2.6.24.1 - kernel does not boot; Solution! Chris Rankin
-- strict thread matches above, loose matches on Subject: below --
2008-02-08 23:31 Linux 2.6.24.1 - kernel does not boot; IRQ trouble? Chris Rankin
2008-02-09 6:48 ` Greg KH
2008-02-09 12:06 ` Chris Rankin
2008-02-09 18:06 ` Greg KH
2008-02-09 18:22 ` Chris Rankin
2008-02-09 19:03 ` Oliver Pinter
2008-02-09 19:26 ` Chris Rankin
2008-02-17 0:42 ` Chris Rankin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080218050056.fb0fc0bf.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rankincj@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox