Re: hpwdt oops in clflush_cache_range

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Thomas Gleixner
Date: Wednesday, February 27, 2008 - 12:48 pm

On Wed, 27 Feb 2008, Roland Dreier wrote:



This one has 36bit physical address space. You can verify that via
/proc/cpuinfo


While the physical address of your ioremap is 47000ee000.

2^ 36 == 1000000000
---->    47000ee000

So the fault is not very surprising. Unfortunately we do not check,
whether physaddr is inside the valid physical address space. I whip up
a patch to do that.

Can you please instrument the driver to figure out where this
information comes from ? Or maybe lspci tells already.

Thanks,

	tglx
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
hpwdt oops in clflush_cache_range, Roland Dreier, (Wed Feb 27, 10:08 am)
RE: hpwdt oops in clflush_cache_range, Mingarelli, Thomas, (Wed Feb 27, 10:37 am)
Re: hpwdt oops in clflush_cache_range, Thomas Gleixner, (Wed Feb 27, 11:14 am)
Re: hpwdt oops in clflush_cache_range, Roland Dreier, (Wed Feb 27, 11:38 am)
Re: hpwdt oops in clflush_cache_range, Thomas Gleixner, (Wed Feb 27, 12:48 pm)
Re: hpwdt oops in clflush_cache_range, Ingo Molnar, (Wed Feb 27, 1:36 pm)
Re: hpwdt oops in clflush_cache_range, Thomas Gleixner, (Wed Feb 27, 1:42 pm)
Re: hpwdt oops in clflush_cache_range, Ingo Molnar, (Wed Feb 27, 1:44 pm)
Re: hpwdt oops in clflush_cache_range, Thomas Gleixner, (Wed Feb 27, 1:59 pm)
Re: hpwdt oops in clflush_cache_range, Ingo Molnar, (Wed Feb 27, 2:14 pm)
Re: hpwdt oops in clflush_cache_range, Roland Dreier, (Wed Feb 27, 2:17 pm)
Re: hpwdt oops in clflush_cache_range, Roland Dreier, (Wed Feb 27, 2:35 pm)
RE: hpwdt oops in clflush_cache_range, Mingarelli, Thomas, (Wed Feb 27, 4:44 pm)
Re: hpwdt oops in clflush_cache_range, Roland Dreier, (Wed Feb 27, 5:12 pm)
RE: hpwdt oops in clflush_cache_range, Mingarelli, Thomas, (Wed Feb 27, 8:09 pm)