I have runned in situation wher SP5100 is also involved on a dual boot
solution with Quantal and Precise.
I have filed it very specific for this.
Anyway, those ones who are affected on Ubuntu12.04 may want to look at
this report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1055096
--
@semitones :
See Bug Description : the PC reboots every two seconds and never takes off.
This very serious bug is fixed. You can see a few lines in your dmesg (like in
comment #47), but that is not the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Is anyone still working on this bug? I've read through the last few
comments, and I still have this issue in 64bit 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the
My comment #46 was not accurate - the bug exits on my 64 bit partition
as well. It doesn't show at boot but it is in the dmsg log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty:
Boot stuck with same error.
Ubuntu 12.04 amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the driver sp5100_tco prevents PC startup
To manage notifications about this bug
I also have the issue in 12.04, but just the 32 bit version. This from
dmsg:
45.998733] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
[ 45.998803] SP5100 TCO timer: mmio address 0xb8fe00 already in use
It doesn't seem to be doing anything evil, but it should be fixed.
--
You
I also have this issue in 12.04, but for 64 bit version. I am able to
boot, but the warning appears in dmesg:
[8.035629] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
[8.035741] SP5100 TCO timer: mmio address 0xb8fe00 already in use
--
You received this bug notification
The problem persists in 12.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the driver sp5100_tco prevents PC startup
To manage notifications about this bug go to:
Been experiencing this bug for about a year, perhaps more at this point,
and in 11.10 it is still not fixed, thus fix is not confirmed (both the
SP5100 TCO timer: mmio address 0xb8fe00 already in use message and the
non-fancy splash/loading screen). Looking forward to if 12.04 fixes it.
--
You
3.2.0-9-generic-pae
I'd like to use this watchdog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the driver sp5100_tco prevents PC startup
To manage notifications about this
...ohh and I get the same warning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the driver sp5100_tco prevents PC startup
To manage notifications about this bug go to:
I upgraded my Kubuntu to 11.10, and the high resolution splash screen
shows as it should. Also the passphrase prompt when using LUKS. I did
not reinstall video driver, Ati fglx still used.
Can I recommend that, before closing this report, we wait for one more
report if this was resolved.
So to
#moglii: removing close source graphics driver solved the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the driver sp5100_tco prevents PC startup
To manage
#moglii: not yet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the driver sp5100_tco prevents PC startup
To manage notifications about this bug go to:
@mplichta: Did you try it? Did it restore the high-resolution splash?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the driver sp5100_tco prevents PC startup
To manage
By disabling I mean using the jockey-gtk/jockey-kde dialog:
http://imageshack.us/photo/my-images/580/snapshot1bp.png/
(screenshot taken in a VM, so no driver offered)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The behavior I reported 1st May (high-res splash screen broken and message
displayed) appears to be connected to fglrx.
On a netbook with AMD C-50 APU (Radeon 6250) I can reversibly (already tested
three times) restore the high-res splash by disabling the fglrx driver.
My theory (correct me if
#moglii: by disabling driver u mean:
https://help.ubuntu.com/community/RadeonDriver
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the driver sp5100_tco prevents PC startup
To
Running Ubuntu Natty 2.6.38-10-generic, 32 bit.
AMD Phenom II quad core CPU
ATI Radeon HD5750 dual DVI graphics card
DMESG shows:
[ 25.680539] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
[ 25.680610] SP5100 TCO timer: mmio address 0xfec000f0 already in use
[ 26.017930] fglrx:
Same problem for me with a 64bit ubuntu and the latest update to the kernel :
2.6.38-10-generic.
I have an AMD processor and a nvidia graphic card.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed in the Acer Aspire One 722 and latest fresh install of Kubuntu 11.04
64bit
dmesg:
[ 18.178665] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
[ 18.178937] SP5100 TCO timer: mmio address 0xb8fe00 already in use
--
You received this bug notification because you are a
Also happens on my HP g61 11.04 and newest kernel (2.6.38-10-generic) with only
the second message appearing.
I have noticed that most people that have this problem tend to have AMD
processors and ATI graphics cards.
Perhaps the problem is related to this (sorry if this is either obvious or
Confirmed the above on HP DM1
[ 12.014989] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
[ 12.015178] SP5100 TCO timer: mmio address 0xb8fe00 already in use
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same issue on HP Pavilion DM1.
$ uname -a
Linux GeertNetbook 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011
x86_64 x86_64 x86_64 GNU/Linux
dmesg
[ 14.051466] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
[ 14.051521] nf_conntrack version 0.5.0 (16384 buckets, 65536
$ uname -a
Linux home 2.6.38-8-generic-pae #42-Ubuntu SMP Mon Apr 11 05:17:09 UTC
2011 i686 athlon i386 GNU/Linux
$ dmseg (clipped)
[ 19.695606] ACPI: resource piix4_smbus [io 0x0b00-0x0b07] conflicts with
ACPI region SOR1 [io 0xb00-0xb0f]
[ 19.695608] ACPI: If an ACPI driver is available
same here on Dell Zino HD AMD Athlon 64 X2 6850E 2GB 1TB ATI
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the driver sp5100_tco prevents PC startup
--
ubuntu-bugs mailing
I'm using Natty 11.04 64bit on a Toshiba NB550D. All updates applied
after a fresh install. I'm running the kernel Linux ubuntu
2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64
x86_64 x86_64 GNU/Linux
dmesg shows the following error:
[8.330467] SP5100 TCO timer: SP5100
I get the address already in use message during plymouth splash:
[ 13.591205] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
[ 13.591470] SP5100 TCO timer: mmio address 0xb8fe00 already in use
Running on an Acer Aspire One 522 (AO522) with 2.6.38-8-generic
#42-Ubuntu.
Let me
Using Linux Desktop 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24
UTC 2011 x86_64 x86_64 x86_64 GNU/Linux in 11.04.
The message SP5100 TCO timer: mmio address 0xfec000f0 already in use
appears on the splash screen and breaks the high resolution.
Same deal. 64 bit 11.04 freah install. Found the udev problem:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622340 and this as
well. This does not show up in dmesg, but does break the boot screen.
KeithG
** Bug watch added: Debian Bug tracker #622340
oops, It is in the log. I just could not find it initially:
[ 22.818332] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
[ 22.818426] SP5100 TCO timer: mmio address 0xfec000f0 already in use
It is running on a Gigabyte GA-MA78LMT-S2 board with the latest V14
BIOS.
KeithG
--
You
I am having this problem with the beta2 live cd (64bit)
I started writing about the issue on the forum:
http://ubuntuforums.org/showthread.php?t=1733315
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011
x86_64 x86_64 x86_64 GNU/Linux
I was able
Using 2.6.38-8 kernel in lucid (https://launchpad.net/~kernel-
ppa/+archive/ppa?field.series_filter=lucid)
After updating to 2.6.38-8.42 i noticed following warning, that appeared in tty
console
16.370050 SP5100 TCO timer: mmio address 0xfec000f0 already in use
The only relevant boot problem was
I confirm. This bug was fixed on my PC after the last update : package
linux 2.6.38-8.41 to 2.6.38-8.42
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the driver sp5100_tco
This bug was fixed in the package linux - 2.6.38-8.42
---
linux (2.6.38-8.42) natty; urgency=low
[ David Henningsson ]
* SAUCE: (drop after 2.6.38) ALSA: HDA: Fix dock mic for Lenovo
X220-tablet
- LP: #751033
[ Gustavo F. Padovan ]
* SAUCE: Revert Bluetooth: Add
** Also affects: linux (Ubuntu Natty)
Importance: Undecided
Assignee: Herton R. Krzesinski (herton)
Status: In Progress
** Changed in: linux (Ubuntu Natty)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
After install of your parched kernel, the bug seems fixed.
1) first restart after install : I store dmesg (dmesg_1222.txt) and dmesg0
(dmesg0_1222.txt)
2) second restart : I store dmesg (dmesg_1234.txt) and dmesg0 (dmesg0_1234.txt)
I restart, restart and no more problem. All is solved.
**
** Attachment added: dmesg0_1222.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/740011/+attachment/1956150/+files/dmesg0_1222.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
** Attachment added: dmesg_1234.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/740011/+attachment/1956151/+files/dmesg_1234.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
** Attachment added: dmesg0_1234.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/740011/+attachment/1956152/+files/dmesg0_1234.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
I made the same on my wubi-install of natty (64bits) on the same PC because my
wubi-install also had the bug.
After install of your patched kernel (amd64), I store store dmesg
(dmesg_1339.txt) and dmesg0 (dmesg0_1339.txt)
The bug is also fixed for my wubi-install.
Bravo Herton.
** Attachment
** Attachment added: dmesg0_1339.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/740011/+attachment/1956300/+files/dmesg0_1339.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Thanks for the testing, indeed this is the case of a bios bug, with the
patched kernel we have now:
[ 16.213098] SP5100 TCO timer: mmio address 0xfec000f0 already in use
sp5100_tco sees the address is already used now and doesn't load. The
fix is on its way to stable, so should soon appear in
** Attachment added: dmesg0_833.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/740011/+attachment/1955675/+files/dmesg0_833.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
** Attachment added: dmesg_833.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/740011/+attachment/1955674/+files/dmesg_833.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
** Attachment added: dmesg0_819.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/740011/+attachment/1955673/+files/dmesg0_819.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Thanks Herton.
I hope the following can help :
1) start PC (driver sp5100_tco blacklisted)
2) driver sp5100_tco authorized
3) restart PC (no problem, no bug)
Just after restart, I store dmesg (dmesg_819.txt) and dmesg0 (dmesg0_819.txt)
4) restart PC (now the bug exist and I have to unplug the
** Attachment added: kernlog_201103300922.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/740011/+attachment/1955676/+files/kernlog_201103300922.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Herton,
You wrote : Can you install and test with sp5100_tco not blacklisted the
kernel I uploaded at http://people.canonical.com/~herton/lp740011/ ? Also
please attach the dmesg with this new kernel.
I don't realize that immediately because I have never made that and I will ask
for help in the
** Package changed: gnome-system-monitor (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the driver sp5100_tco prevents PC startup
--
ubuntu-bugs
It would be good to get the dmesg/kernel log when the system fails to
start, probably there is a warning/oops, so we can probably see exactly
what the problem is.
In any case, this may be a recent bug discovered with some bioses and
sp5100_tco, and a fix was made to sp5100_tco to avoid the
Debian has blacklisted this module.
:~$ uname -r
2.6.38-1-amd64
:~$ grep -i sp5100 /boot/config-`uname -r`
# CONFIG_SP5100_TCO is not set
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740011
Title:
Natty: the driver sp5100_tco prevents PC startup
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Previously, I was able to meet the dmesg file (
dmesg_liveCD_Natty_Alpha3.txt) obtained in session live-CD Ubuntu Natty
Alpha3. can be seen in this file the three lines for SP5100 TCO timer
who is the driver that is causing problems
** Attachment added: dmesg obtained in live-CD Session of Natty
54 matches
Mail list logo
