Andrew Morton wrote: > On Thu, 17 Jan 2008 11:22:19 -0800 "Pallipadi, Venkatesh" > <[EMAIL PROTECTED]> wrote: > >> >> The problem is >>>> modprobe:2584 conflicting cache attribute 50000000-50001000 >>>> uncached<->default >> >> Some address range here is being mapped with conflicting types. >> Somewhere the range was mapped with default (write-back). Later >> pci_iomap() is mapping that region as uncacheable which is basically >> aliasing. PAT code detects the aliasing and fails the second >> uncacheable request which leads in the failure.
its probably the e100 screaming interrupt disable quirk code doing the mapping? > It sounds to me like you need considerably more runtime debugging and > reporting support in that code. Ensure that it generates enough > output > both during regular operation and during failures for you to be able > to > diagnose things in a single iteration. > > We can always take it out later. FWIW (nothing) I agree. - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
