Boot issues after running kernel 3.8.x
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | linux (Ubuntu) |
High
|
Unassigned | ||
Bug Description
PC fails to load BIOS after running the 3.8.x kernel until the power is completely cut off. It occurs in all 3.8.x versions and the mainline version as of 2/4. The issue does not occur with the 3.7.x builds.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.8.0-4-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDmesg:
Date: Tue Feb 5 20:30:26 2013
HibernationDevice: RESUME=
InstallationDate: Installed on 2010-09-25 (864 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
MachineType: System manufacturer System Product Name
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.100
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2012-11-17 (80 days ago)
dmi.bios.date: 08/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2801
dmi.board.
dmi.board.name: M3A78-CM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
| Timothy G. Rundle (tgrundle) wrote : | #1 |
| Timothy G. Rundle (tgrundle) wrote : | #2 |
| Timothy G. Rundle (tgrundle) wrote : | #3 |
| Timothy G. Rundle (tgrundle) wrote : | #4 |
| Changed in linux (Ubuntu): | |
| status: | New → Confirmed |
| Joseph Salisbury (jsalisbury) wrote : | #6 |
I'd like to perform a bisect to figure out what commit caused this regression. It would be very helpful to know the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:
v3.7 final: http://
v3.8-rc1: http://
v3.8-rc3: http://
You don't have to test every kernel, just up until the kernel that first has this bug.
Thanks in advance!
| Changed in linux (Ubuntu): | |
| importance: | Undecided → High |
| tags: | added: performing-bisect |
| Changed in linux (Ubuntu): | |
| status: | Confirmed → Incomplete |
| Timothy G. Rundle (tgrundle) wrote : | #7 |
v3.7 final works just fine as well as 3.7.6, which I am currently running.
v3.8-rc1 doesn't work, nor does anything since (I have checked the last 2 night's daily build)
I noticed sp5100_tco fails to load in 3.7, but does load on 3.8-rc1. I am not sure if it is related in any manner, it just caught my attention.
dmesg from v3.7:
[ 14.431032] sp5100_tco: SP5100 TCO WatchDog Timer Driver v0.01
[ 14.431096] sp5100_tco: mmio address 0xfec000f0 already in use
dmesg from v3.8-rc1:
[ 10.854230] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.03
[ 10.854294] sp5100_tco: PCI Revision ID: 0x3a
[ 10.854341] sp5100_tco: Using 0xfed45000 for watchdog MMIO address
[ 10.854349] sp5100_tco: Last reboot was triggered by watchdog.
[ 10.854388] sp5100_tco: initialized (0xffffc9000067
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Confirmed |
| Joseph Salisbury (jsalisbury) wrote : | #8 |
Can you see if blacklisting the sp5100_tco driver in v3.8-rc1 causes the bug to go away? If not, I'll start a kernel bisect between v3.7 and v3.8-rc1.
| Timothy G. Rundle (tgrundle) wrote : | #9 |
Yes blacklisting the sp5100_tco driver has resolved the issue.
Here is the command I ran:
sudo su -c 'echo "blacklist sp5100_tco" >> /etc/modprobe.
| Joseph Salisbury (jsalisbury) wrote : | #10 |
This may be relates up upstream commit:
740fbddf5c3f9ad
I'll build a test kernel with that commit reverted and post a link to the kernel shortly.
| Joseph Salisbury (jsalisbury) wrote : | #11 |
I built a test kernel with commit 740fbddf5c3f9ad
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not.
Thanks in advance!
| Timothy G. Rundle (tgrundle) wrote : | #12 |
The test build does not have the bug. Everything works as expected.
| Changed in linux (Ubuntu): | |
| status: | Confirmed → In Progress |
| assignee: | nobody → Joseph Salisbury (jsalisbury) |
| Joseph Salisbury (jsalisbury) wrote : | #13 |
Thanks for testing, Timothy. I sent a message to the patch author requesting feedback regarding this bug.
| Joseph Salisbury (jsalisbury) wrote : | #14 |
There are a couple of patches in upstream linux-next that may resolve this bug. Commits:
a6e26b1369b3476
adbdcc030be5f7b
I built a Raring test kernel with these two patches applied.
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not.
Thanks in advance!
| Timothy G. Rundle (tgrundle) wrote : | #15 |
The issue still occured in the test build with the patches.
| Joseph Salisbury (jsalisbury) wrote : | #16 |
Thanks for testing, Timothy. I reported the results of your testing upstream. It would be helpful if you could get a screen capture or digital picture of the panic and post it to the bug.
Thanks again for all your help.
| Timothy G. Rundle (tgrundle) wrote : | #17 |
The issue occurs before the bios loads. There is no text on the screen, simply a blank screen until I cut off all power to the PSU.
| Joseph Salisbury (jsalisbury) wrote : | #18 |
Hi Timothy,
I received another patch from upstream. I'm building a new test kernel now.
The patch author is interested in the I/O resource of PC in which the problem has occurred, He requested the result of 'cat /proc/iomem'. The sp5100_tco driver does not have to be loaded when you run'cat /proc/iomem'.
I will post a link to the new test kernel shortly.
| Joseph Salisbury (jsalisbury) wrote : | #19 |
I built a Raring test kernel with a new patch[0] from upstream applied.
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not.
Thanks in advance!
| Timothy G. Rundle (tgrundle) wrote : | #20 |
| Timothy G. Rundle (tgrundle) wrote : | #21 |
The latest test build resolves the issue as expected.
| Joseph Salisbury (jsalisbury) wrote : | #22 |
The upstream commit that introduced this regression will be revered upstream:
https:/
| Julian Wiedmann (jwiedmann) wrote : | #23 |
Timothy G. Rundle,
could you please test the latest kernel in -updates (3.8.0-19.30) and
see if this bug is still reproducible? Thanks.
Should be fixed in 3.8.5-stable with
commit 18e4321276fcf08
Author: Takahisa Tanaka <email address hidden>
Date: Sun Mar 3 14:52:07 2013 +0900
watchdog: sp5100_tco: Remove code that may cause a boot failure
| Changed in linux (Ubuntu): | |
| status: | In Progress → Incomplete |
| Changed in linux (Ubuntu): | |
| assignee: | Joseph Salisbury (jsalisbury) → nobody |
| Timothy G. Rundle (tgrundle) wrote : | #24 |
Looks good. I rebooted and powered off/on a couple times without issue after performing the following:
timothy@thomas:~$ uname -a
Linux thomas 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
timothy@thomas:~$ sudo vi /etc/modprobe.
timothy@thomas:~$ grep sp5100 /etc/modprobe.
#blacklist sp5100_tco
sudo update-initramfs -u
timothy@thomas:~$ sudo update-initramfs -u
[sudo] password for timothy:
update-initramfs: Generating /boot/initrd.
Here are the dmesg entries:
timothy@thomas:~$ dmesg |grep sp5100
[ 20.505566] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05
[ 20.505612] sp5100_tco: PCI Revision ID: 0x3a
[ 20.505629] sp5100_tco: failed to find MMIO address, giving up.
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Fix Released |


This change was made by a bot.