Re: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

> Here's a test patch for the TCO timer issue.  That SP5100 watchdog
> driver is a mess -- it gropes around at hard-coded places in I/O port
> space -- so while I think this patch will fix the message, the
> watchdog itself still may not work.  If you can verify that the
> watchdog works, that would be great.
Currently I am figuring out how to get a 3.1-rc3 kernel compiled and running at 
all, as soon as that works, I will apply your patch.
I did a quick search on what a watchdog is (never heard of anything like that 
before, actually). Is it enough to SIGKILL the watchdogd and wait a minute to 
see if it works?

> > [    0.470960] pci_root PNP0A03:00: address space collision: host bridge
> > window [mem 0x000cc000-0x000cffff] conflicts with Video ROM [mem
> > 0x000c0000-0x000ce9ff]
> > [    0.471052] pci_root PNP0A03:00: address space collision: host bridge
> > window [mem 0x000ec000-0x000effff] conflicts with reserved [mem
> > 0x000ef000-0x000fffff]
> 
> These are unrelated and I'm doing some other work that addresses them.
Great :)


> > [    1.480097] pci 0000:00:04.0: ASPM: Could not configure common clock
> 
> I don't know about this one.  It looks like we tried a link retrain
> but it failed.  I would poke Shaohua Li <shaohua.li@xxxxxxxxx> about
> this since he submitted the original code for that.
Okay, if the issue persists with the 3.1 kernel, I will send that a separate 
report to linux-pci and CC him.

Kind regards,
Ralf
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux