The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: ACPI hangs at boot  w/ nForce motherboard
Date: 14 Oct 2004 15:41:10 -0400	[thread overview]
Message-ID: <1097782870.29329.34.camel@d845pe> (raw)
In-Reply-To: <1097777194.20778.8.camel@cog.beaverton.ibm.com>

On Thu, 2004-10-14 at 14:06, john stultz wrote:
> Hey Len,
>         Sorry for the lack of details here, but I figured I should at
> least let you know. On my box at home (nForce1 motherboard w/ voodoo3
> video) 2.6.9-rcX kernels hang on boot. Since its my personal system, I
> haven't had much time to debug or look into the issue, however I have
> found that acpi=off allows me to boot.
> 
> There are no strange error messages, the system just hangs (the
> framebuffer console looks to be locked at well - no blinking cursor).
> 
> Any suggestions?  I plan to try the standard acpi=noirq, and
> pci=noacpi, but I feel like I tried them awhile ago to no effect.


Hi John,
Did this break recently, or did a previous ACPI-mode kernel work
properly?

With ACPI enabled, try "acpi_skip_timer_override"
With ACPI enabled, try "noapic"
With ACPI enabled, try "nolapic"

If you can send me a serial console capture with "debug" for the failure
case, that would help.  With any successful boot, the dmesg might be
helpful, and the output from lspci -vv and acpidmp is also helpful.
acpidmp is in /usr/sbin or in pmtools here:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/

You can send this to me, and/or attach them into a bug report here:
http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
and assign it to me.

thanks,
-Len



  reply	other threads:[~2004-10-14 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 18:06 ACPI hangs at boot w/ nForce motherboard john stultz
2004-10-14 19:41 ` Len Brown [this message]
2004-10-14 19:54   ` john stultz

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=1097782870.29329.34.camel@d845pe \
    --to=len.brown@intel.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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