mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@it.uu.se>
To: Robin Holt <holt@sgi.com>
Cc: Jeff Garzik <jeff@garzik.org>, linux-kernel@vger.kernel.org
Subject: Re: Possible hang inside interrupt handler on sata_promise.
Date: Wed, 12 Sep 2007 17:33:50 +0200	[thread overview]
Message-ID: <18152.1758.872864.7897@alkaid.it.uu.se> (raw)
In-Reply-To: <20070912131904.GW14474@lnx-holt.americas.sgi.com>

Robin Holt writes:
 > 
 > I have been experiencing hangs on a newly setup machine.  Unfortunately,
 > it appears to be hanging inside the interrupt handler as sysrq and
 > caps-lock led seem to stop working when the event occurs.  I am guessing
 > it is related to the sata_promise driver, but that is only a guess as
 > I don't get much for output.  I am running the debian unstable kernel
 > (2.6.22-1-686), but the problem also occurs with the debian stable kernel
 > (2.6.18-4-686).  I do need to boot with the acpi=off option, but am
 > not sure if that is related.  Unfortunately, I do not know much about
 > troubleshooting i386 when problems occur inside the interrupt handlers.

This is the first I've heard of a problem like this.
Since you boot with acpi=off and sysrq stops working,
I really have to suspect a mainboard interrupt problem.

 > What can I do to help troubleshoot this problem.

Unless the mainboard in question is known to be a totally
lost cause for ACPI, the first step should be to get ACPI
working.

If it's an older mainboard it might not need ACPI,
but then you should build and boot an ACPI-free kernel.
(I wouldn't trust acpi=off to be equivalent to CONFIG_ACPI=n.)

If the mainboard has an I/O-APIC then you should make sure
that the kernel can find and use it.

/Mikael

  reply	other threads:[~2007-09-12 15:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 13:19 Robin Holt
2007-09-12 15:33 ` Mikael Pettersson [this message]
2007-09-13 15:59 ` Chuck Ebbert
2007-09-13 17:13   ` Robin Holt
2007-09-13 17:20     ` Maciej W. Rozycki

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=18152.1758.872864.7897@alkaid.it.uu.se \
    --to=mikpe@it.uu.se \
    --cc=holt@sgi.com \
    --cc=jeff@garzik.org \
    --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

all inboxes | Powered by JetHome®