[Fujitsu M2010] Kernel 3.11 does not boot

Bug #1266024 reported by Master on 2014-01-04
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

Upgrading to saucy, the kernel 3.11 does not boot. I kept using the kernel 3.8 and it works fine. The problem does not change with any of noapic, nolapic, noirqpoll.

WORKAROUND: acpi=off

ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
 /dev/snd/controlC0: ops 1428 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=90acddf8-5cc3-4bcd-9185-ab0dcad0dd47
InstallationDate: Installed on 2013-03-16 (293 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130315)
MachineType: FUJITSU M2010
MarkForUpload: True
Package: linux (not installed)
 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=8b1686df-d55e-47f3-8b8b-6a27240a781a ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-33.48-generic
 linux-restricted-modules-3.8.0-33-generic N/A
 linux-backports-modules-3.8.0-33-generic N/A
 linux-firmware 1.116
Tags: saucy
Uname: Linux 3.8.0-33-generic i686
UpgradeStatus: Upgraded to saucy on 2013-11-11 (53 days ago)
UserGroups: adm debian-tor lpadmin sambashare sudo
dmi.bios.date: 09/16/2009
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.15
dmi.board.name: FJNBF08
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.15:bd09/16/2009:svnFUJITSU:pnM2010:pvr:rvnFUJITSU:rnFJNBF08:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: M2010
dmi.sys.vendor: FUJITSU

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

apport-collect 1266024

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

apport information

tags: added: apport-collected saucy
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changing the bug status to 'Confirmed' on Aureliano's behalf.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc7-trusty/

Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete

I did install the last kernel on the archive and headers as well.

It does not boot either.
Here is where is hangs when I boot removing quiet. irqpoll or not does not change anything.

It talks about IRQ9 (used by ACPI as far as I know). "nobody cared: try booting with irqpoll". No more success.

Fedora seems to have the same problem with bug 1030633. So it is definitely an upstream issue with the update on using the "common acpi", as the bug already reported (before I was told to create this one) turned out.



Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Aureliano, the next step is to fully commit bisect from Raring to Saucy in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

description: updated
tags: added: kernel-bug-exists-upstream- latest-bios-1.15 needs-bisect regression-release v3.13-rc7
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
summary: - Kernel 3.11 does not boot
+ [Fujitsu M2010] Kernel 3.11 does not boot

Hello, after installing different kernel packages directly from the deb downloaded, it turns out that:

 3.10.26-031026-generic #201401091635 SMP Thu Jan 9 21:45:36 UTC 2014 i686 i686 i686 GNU/Linux


I am not sure of the mapping I can read between Ubuntu & upstrem numbers, but one follows the other directly I believe.

I cannot use git since my connection here will not allow me to clone the repo.

Thank you

3.12 does not boot either.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream-3.13-rc7 needs-upstream-testing
removed: kernel-bug-exists-upstream- v3.13-rc7

3.13-rc8 still has the bug. Same symptoms with the IRQ9 issue stated on boot. And freeze after showing the added swap.
Quite late then since /local/premount is already executed. So in a module I guess.

I am trying to find logs of the failed boots. But nothing seems recorded.
Strange since it adds the swap (or tries) so should have mounted the root already, souldn't it ?
How to get logs of a kernel not booting until the end but already reached the initrd ?
I installed linux-crash but it doesn't either.
Let me know how to help...

I downloaded last Debian mini iso and it boots.
'uname -a' returns

Linux debian 3.12-1-486 #1 Debian 3.12.8 (2014-01-19) i686 GNU/Linux

So maybe a bad option in Ubuntu & Fedora that Debian does not compile ?
Maybe trying to see which options are compiled but with different versions it can be difficult I guess ?
And anyway the bisect already gave access to what is wrong, no ?
But I do not have knowledge to fix this...

And while booting, it still show an IRQ 9 error message but keeps going.

Once installed, Debian does not boot anymore this kernel. Thus likely it booted since the installer image does not enable acpi.

Eugene Romanenko (eros2) wrote :

Same issue on Fujitsu M2010.

Ubuntu 12.04 with saucy lts (3.11) kernet does not boot.

Kernels 3.2, 3.5, 3.8 boots ok.

eros2, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers