linux-kernel - Re: Possible hang inside interrupt handler on sata

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]

Date:	Wed, 12 Sep 2007 17:33:50 +0200
From:	Mikael Pettersson <mikpe@...uu.se>
To:	Robin Holt <holt@....com>
Cc:	Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org
Subject: Re: Possible hang inside interrupt handler on sata_promise.

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