New: WARNING: at arch/x86/mm/ioremap.c:137 __ioremap+0x1d5/0x1f0() during bootup
A message that is not in the archive (sent off-list or not yet received): [email protected]/
Quoted 18 lines · On Sat, 23 Feb 2008 09:09:25 -0800 (PST) [email protected] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=10072
Summary: WARNING: at arch/x86/mm/ioremap.c:137 __ioremap+0x1d5/0x1f0() during bootup Product: Memory Management Version: 2.5 KernelVersion: 2.6.25-rc2-00496-g39273b5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: low Priority: P1 Component: Other AssignedTo: [email protected] ReportedBy: [email protected]
Quoted 7 lines
Latest working kernel version:
Earliest failing kernel version:
Distribution: Slackware 12
Hardware Environment: AMD Duron 850MHz CPU, 512 MB RAM Software Environment:
Problem Description: WARNING section in bootup log (attached)
This is an acpi regression, I believe. And it was reported a week or two ago.
Quoted 28 lines · Andrew Morton
Quoted 18 lines · On Sat, 23 Feb 2008 09:09:25 -0800 (PST) [email protected] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=10072
Summary: WARNING: at arch/x86/mm/ioremap.c:137 __ioremap+0x1d5/0x1f0() during bootup Product: Memory Management Version: 2.5 KernelVersion: 2.6.25-rc2-00496-g39273b5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: low Priority: P1 Component: Other AssignedTo: [email protected] ReportedBy: [email protected]Quoted 7 lines
Latest working kernel version:
Earliest failing kernel version:
Distribution: Slackware 12
Hardware Environment: AMD Duron 850MHz CPU, 512 MB RAM Software Environment:
Problem Description: WARNING section in bootup log (attached)
Quoted 2 lines
This is an acpi regression, I believe. And it was reported a week or two ago.
It's the same thing as http://bugzilla.kernel.org/show_bug.cgi?id=10104 , already on the regressions list.
Thanks,
Rafael
Quoted 29 lines · On Tue, 26 Feb 2008 01:19:29 +0100 "Rafael J. Wysocki" <[email protected]> wrote:
Quoted 28 lines · Andrew Morton
Quoted 25 lines · On Sat, 23 Feb 2008 09:09:25 -0800 (PST) [email protected] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=10072
Summary: WARNING: at arch/x86/mm/ioremap.c:137 __ioremap+0x1d5/0x1f0() during bootup Product: Memory Management Version: 2.5 KernelVersion: 2.6.25-rc2-00496-g39273b5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: low Priority: P1 Component: Other AssignedTo: [email protected] ReportedBy: [email protected]Latest working kernel version:
Earliest failing kernel version:
Distribution: Slackware 12
Hardware Environment: AMD Duron 850MHz CPU, 512 MB RAM Software Environment:
Problem Description: WARNING section in bootup log (attached)
Quoted 6 lines
Quoted 2 lines
This is an acpi regression, I believe. And it was reported a week or two ago.
It's the same thing as http://bugzilla.kernel.org/show_bug.cgi?id=10104 , already on the regressions list.
my machine sees this.
BTW, what this warning does on my console is
ACPI: EC: Look up EC in DSDT
------------[ cut here ]------------ WARNING: at arch/x86/mm/ioremap.c:137 __ioremap+0xb1/0x16b() Modules linked in: .......................... VERY VERY LONG STACK DUMP ======================= ---[ end trace ca143223eefdc828 ]---
Final console image was
....
VERY VERY LONG STACK DUMP
=======================
---[ end trace ca143223eefdc828 ]---
...no information.
And nothing goes on (because the kernel is in very very slow path.) (takes several minutes.)
I have to remove stack dump to find this is just a warning. (I have no serial console.)
It seems show_stack() supports kstack=XX option.
Does it make sense to add same kind of option for limiting length of dump_trace() ?
Thanks,
-Kame