Bug 8801 - 2.6.21.5: kernel BUG at arch/i386/mm/highmem.c:38! - HP Proliant 110
Summary: 2.6.21.5: kernel BUG at arch/i386/mm/highmem.c:38! - HP Proliant 110
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: Memory Management
Classification: Unclassified
Component: Page Allocator (show other bugs)
Hardware: All Linux
: P1 high
Assignee: Andrew Morton
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-24 01:54 UTC by Szabolcs Toth
Modified: 2009-03-23 11:24 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.21.5
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
The bug and the booting procedure (40.50 KB, text/plain)
2007-07-24 01:58 UTC, Szabolcs Toth
Details
Cpu info (1.08 KB, text/plain)
2007-07-24 02:16 UTC, Szabolcs Toth
Details
IOMEM (1.03 KB, text/plain)
2007-07-24 02:19 UTC, Szabolcs Toth
Details
Kernel configuration (43.30 KB, text/plain)
2007-07-24 02:26 UTC, Szabolcs Toth
Details
lspci info (11.22 KB, text/plain)
2007-07-24 02:51 UTC, Szabolcs Toth
Details
Software information (985 bytes, text/plain)
2007-07-24 02:52 UTC, Szabolcs Toth
Details

Description Szabolcs Toth 2007-07-24 01:54:27 UTC
Most recent kernel where this bug did not occur: 2.6.21.5
Distribution: Debian Sarge
Hardware Environment: HP Proliant 110
Software Environment:
Problem Description: The server freeze or reboot randomly tow or three times a week with the following error: Kernel panic - not syncing: Fatal exception in interrupt

Steps to reproduce:
Comment 1 Szabolcs Toth 2007-07-24 01:58:53 UTC
Created attachment 12112 [details]
The bug and  the booting procedure

The attachment show the bug and  the bootping procedure
Comment 2 Szabolcs Toth 2007-07-24 02:01:37 UTC
I use this kernel on machine which have really two CPU or two CPU core, but there I didn't see that kind of problem.
Comment 3 Szabolcs Toth 2007-07-24 02:11:11 UTC
I have seen this problem only on machine which worked with Hyperthread only.
Comment 4 Szabolcs Toth 2007-07-24 02:16:34 UTC
Created attachment 12113 [details]
Cpu info
Comment 5 Szabolcs Toth 2007-07-24 02:19:08 UTC
Created attachment 12114 [details]
IOMEM
Comment 6 Szabolcs Toth 2007-07-24 02:26:41 UTC
Created attachment 12115 [details]
Kernel configuration
Comment 7 Szabolcs Toth 2007-07-24 02:51:49 UTC
Created attachment 12116 [details]
lspci info
Comment 8 Szabolcs Toth 2007-07-24 02:52:36 UTC
Created attachment 12117 [details]
Software information
Comment 9 Len Brown 2007-07-24 08:22:57 UTC
> 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)));

Note You need to log in before you can comment on or make changes to this bug.