http://bugzilla.kernel.org/show_bug.cgi?id=8801


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |acpi-
                   |                            |[EMAIL PROTECTED]
                   |                            |et
         AssignedTo|acpi_config-                |[EMAIL PROTECTED]
                   |[EMAIL PROTECTED]          |
                   |bugs.osdl.org               |
          Component|Config-Interrupts           |Page Allocator
            Product|ACPI                        |Memory Management
            Summary|Fatal exception in interrupt|2.6.21.5: kernel BUG at
                   |                            |arch/i386/mm/highmem.c:38! -
                   |                            |HP Proliant 110




------- Comment #9 from [EMAIL PROTECTED]  2007-07-24 08:22 -------
> Most recent kernel where this bug did not occur: 2.6.21.5

but your dmesg shows the failure in 2.6.21.5
What release does _not_have the issue?
did 2.6.20.stable work, does 2.6.22?

> Kernel command line: ... acpi=ht

This doesn't appear to be a bug in ACPI,
as "acpi=ht" effectively disables ACPI.
And I'm curious why you are running with ACPI disabled, is there a reason?
Sort of unusual to see these disabled on a modern machine:

# CONFIG_ACPI_BUTTON is not set
# CONFIG_ACPI_PROCESSOR is not set

> I have seen this problem only on machine which worked with Hyperthread only.

Does this problem go away when you disable HT in the BIOS,
or when you boot with "maxcpus=1"?

> kernel BUG at arch/i386/mm/highmem.c:38!

This doesn't looks like an ACPI/interrupt issue,
but rather a memory management issue....

/*
 * kmap_atomic/kunmap_atomic is significantly faster than kmap/kunmap because
 * no global lock is needed and because the kmap code must perform a global TLB
 * invalidation when the kmap pool wraps.
 *
 * However when holding an atomic kmap is is not legal to sleep, so atomic
 * kmaps are appropriate for short, tight code paths only.
 */
void *kmap_atomic(struct page *page, enum km_type type)
{
        enum fixed_addresses idx;
        unsigned long vaddr;

        /* even !CONFIG_PREEMPT needs this, for in_atomic in do_page_fault */
        pagefault_disable();

        idx = type + KM_TYPE_NR*smp_processor_id();
38:     BUG_ON(!pte_none(*(kmap_pte-idx)));


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to