Package: linux-source-3.2 Version: 3.2.51-1 Severity: important
* What led up to the situation?
I tried to boot
* What exactly did you do (or not do) that was effective?
I waited and waited until the command finally timed out.
* What was the outcome of this action?
It finally booted.
* What outcome did you expect instead?
A faster boot. I get these messages on the boot console:
[ 5.530004] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01 [ 5.530054] SP5100 TCO timer: mmio address 0xbafe00 already in use
and then a long pause and timeout messages that do not appear in the dmesg output. I guess I'll poison the watch dog timer, but I don't feel good about doing stuff like that. Thanks for any suggested fixes or hackarounds! -- 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 Versions of packages linux-source-3.2 depends on: ii binutils 2.22-8 ii bzip2 1.0.6-4 Versions of packages linux-source-3.2 recommends: ii gcc 4:4.7.2-1 ii libc6-dev [libc-dev] 2.13-38 ii make 3.81-8.2 Versions of packages linux-source-3.2 suggests: ii libncurses5-dev [ncurses-dev] 5.9-10 ii libqt4-dev 4:4.8.2+dfsg-11 ii pkg-config 0.26-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org