On Tue, Aug 23, 2011 at 6:13 PM, Bjorn Helgaas wrote:
> Your error is "SP5100 TCO timer: mmio address 0xbafe00 already in
> use". (Same error, but different address.) That looks like it's in
> the middle of your RAM, i.e., it looks completely bogus. Given the
> ugliness of the sp5100_tco driver
Hi,
> I don't know what's in the "watchdog" package. I would try the test
> program in the kernel sources:
> Documentation/watchdog/src/watchdog-simple.c.
>
> It looks like if you kill any other process that has /dev/watchdog
> open (use "lsof" to check), then start watchdog-simple, then suspend
On Fri, Aug 26, 2011 at 8:16 AM, Ralf Jung wrote:
> Hi Bjorn,
>
>> 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
Hi Bjorn,
> 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
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
Your error is "SP5100 TCO timer: mmio address 0xbafe00 already in
use". (Same error, but different address.) That looks like it's in
the middle of your RAM, i.e., it looks completely bogus. Given the
ugliness of the sp5100_tco driver, that doesn't surprise me. Possibly
the BIOS configured it di
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
Hi Bjorn,
> Ralf, can you attach your /proc/iomem contents, too? I looked at the
> "SP5100 TCO timer: mmio address 0xfec000f0 already in use" message,
> but I don't see why that address is in use.
Sure, you can find it attached.
I am getting some more kernel error messages during boot (that I pl
Ralf, can you attach your /proc/iomem contents, too? I looked at the
"SP5100 TCO timer: mmio address 0xfec000f0 already in use" message,
but I don't see why that address is in use.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? C
Thanks! These tests:
if ((dev->vendor == PCI_VENDOR_ID_AMD) || (dev->device ==
PCI_DEVICE_ID_AMD_GOLAM_7450))
are clearly wrong. I suspect "&&" was intended instead of "||", but
this code seems to have been that way since the beginning, s
Hi Ralf, can you attach the complete dmesg log to the bug report,
please? I see a snippet (starting with "Bluetooth: SCO socket layer
initialized"), but there's a lot of useful information before that.
The "dmesg" command only shows the most recent part of the log, so if
the kernel's buffer has wr
Hi list,
each time I start up my laptop (Debian testing, Linux 3.0 as provided in the
repositories), the following error (warning?) appears:
[5.083819] shpchp :00:01.0: Cannot reserve MMIO region
The system is working fine as far as I can tell. I observed that message for
quite a while
12 matches
Mail list logo
