Linux 3.13.0-3-generic doesn't boot [HP Compaq Mini 700EW]

Bug #1269296 reported by Marcin Kralka
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
High
Unassigned
Trusty
Invalid
High
Unassigned

Bug Description

While Linux 3.12-0-7-generic boot normally like other older kernels, all versions of 3.13.0 doesn't boot.
---
ApportVersion: 2.13.1-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: marcin 6339 F.... pulseaudio
 /dev/snd/pcmC0D0p: marcin 6339 F...m pulseaudio
CurrentDesktop: LXDE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=7fa42e18-5e5e-4898-994e-92f7cd738046
InstallationDate: Installed on 2013-11-06 (69 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
MachineType: Hewlett-Packard COMPAQ MINI
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=c654f940-c5ce-467f-b5a3-1588fe04e7e8 ro persistent quiet splash
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
RelatedPackageVersions:
 linux-restricted-modules-3.12.0-7-generic N/A
 linux-backports-modules-3.12.0-7-generic N/A
 linux-firmware 1.121
Tags: trusty
Uname: Linux 3.12.0-7-generic i686
UpgradeStatus: Upgraded to trusty on 2014-01-06 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 04/30/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 361A0 Ver. F.16
dmi.board.name: 361A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 02.12
dmi.chassis.type: 10
dmi.chassis.vendor: Inventec
dmi.modalias: dmi:bvnHewlett-Packard:bvr361A0Ver.F.16:bd04/30/2010:svnHewlett-Packard:pnCOMPAQMINI:pvrF.15:rvnHewlett-Packard:rn361A:rvrKBCVersion02.12:cvnInventec:ct10:cvr:
dmi.product.name: COMPAQ MINI
dmi.product.version: F.15
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Marcin Kralka (marcink96) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1269296

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Marcin Kralka (marcink96) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
Marcin Kralka (marcink96) wrote : BootDmesg.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : CRDA.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : IwConfig.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : Lspci.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : Lsusb.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : ProcEnviron.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : ProcModules.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : PulseList.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : RfKill.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : UdevDb.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : UdevLog.txt

apport information

Revision history for this message
Marcin Kralka (marcink96) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I'd like to perform a bisect to figure out what commit caused this regression. We need to identify 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.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/
If v3.12 final does not exhibit the bug, we should move on to testing some of the v3.13 release candidates.

v3.13-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc3-trusty/

If v3.13-rc3 does not exhibit the bug then test v3.13-rc6:
v3.13-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc6-trusty/

If v3.13-rc3 does exhibit the bug then test v3.13-rc2:
v3.13-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc2-trusty

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 regression-update
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Also, can you follow the "Boot options" instructions on the following wiki to enable additional output on boot:

https://wiki.ubuntu.com/DebuggingKernelBoot

As mentioned on the wiki, it would be great if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Steve Langasek (vorlon)
tags: removed: regression-update trusty
tags: added: trusty
Revision history for this message
Marcin Kralka (marcink96) wrote :

It shows blackscreen after line: EXT4-fs (sda1): re-mounted. Opts: errors-remount-(something i didn't catch on video)
Video: http://youtu.be/iP8Gtr1aSnk

Revision history for this message
Marcin Kralka (marcink96) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Thanks for the video, Marcin. Can you test some of the kernels posted in comment #19? A bisect would allow us to identify the exact commit that introduced this regression.

Revision history for this message
vmc (vmclark) wrote :

Not sure if I have the same problem, but linux-generic 3.13.0-3.18 stops booting right after the kernel message:
 "Switched to clocksource tsc"

If I add nomodeset to the linux string it boots but with reduced solution, even after I install nvidia drivers.

Downgrading back to 3.12.0-7, everything works.

AMD Athlon(tm) II X2 250 Processor × 2 64-bit
GeForce 6150SE nForce 430/integrated/SSE2

Revision history for this message
Marcin Kralka (marcink96) wrote :

Linux 3.12 final, works
Linux 3.13-rc3, works but with message: tsc: Fast TSC calibration failed
I will test more kernels soon.

Revision history for this message
Marcin Kralka (marcink96) wrote :

Hello, kernel 3.13.0-4-generic is working properly.
But, hmm. I think I was wrong about it, linux 3.12 showed always text at boot about something, and 3.13 not, and I didn't wait too long it for boot, so I was probably wrong. 3.13.0-4-generic booted normally after waiting a while on black screen.

Changed in linux (Ubuntu Trusty):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.