You are not logged in.
RE: https://bbs.archlinux.org/viewtopic.php?id=125482
It seems to be back and I see no current references. *sigh*.
The fix suggested here:
http://bugs.debian.org/cgi-bin/bugrepor … =638863#35
has been applied to the kernel sources, but I've got the
(approximate) same symptom anyway:
[ 5.530004] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
[ 5.530054] SP5100 TCO timer: mmio address 0xbafe00 already in use
these messages are followed by a long delay and then a boot.
I've reported it to Debian, but last time it was first reported in 2009
and fixed in 2012. I'm hoping for a nearer term hackaround.
Suggestions, please? Thank you in advance!
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash
Offline
I have the answer: kernel 3.6 (3.5 actually).
Offline