Ubuntu
linux package

[Lenovo ThinkPad L520] Unable to boot 12.04 without 'noapic' flag enabled in GRUB

Bug #903558 reported by Stephen Rees-Carter on 2011-12-13

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Since Ubuntu 11.04 my Thinkpad L520 i7 has required the 'noapic' boot flag to be set in order to boot successfully. When I first upgraded to 12.04 on 2011-12-13 this flag was not required to boot into 12.04. But an update sometime in January 2012 has caused a regression somewhere and now the 'noapic' flag is again required.

This is quite frustraiting and will mean any new users who don't know anything about boot flags will be unable to install Ubuntu on their laptops.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-4-generic 3.2.0-4.10
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic 3.2.0-rc5
Uname: Linux 3.2.0-4-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: valorin 2353 F.... pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf0900000 irq 47'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,17aa21de,00100100 HDA:80862805,80860101,00100000'
   Controls : 29
   Simple ctrls : 12
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 8GHT22WW-1.040000'
   Mixer name : 'ThinkPad EC 8GHT22WW-1.040000'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
CheckboxSubmission: d98e517e10fca0c16089cb8e9d3fc2f7
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Tue Dec 13 16:42:16 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=2853d6a5-ed73-4e23-ba37-9f1aa39c3b15
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: LENOVO 7859CTO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-generic root=UUID=55f5d1a1-8ada-4f3e-8284-93be58c6d27d ro quiet splash noapic nomodeset vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-4-generic N/A
linux-backports-modules-3.2.0-4-generic N/A
linux-firmware 1.62
SourcePackage: linux
StagingDrivers: rts_pstor mei
UpgradeStatus: Upgraded to precise on 2011-12-13 (0 days ago)
dmi.bios.date: 06/07/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8GET33WW (1.10 )
dmi.board.name: 7859CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8GET33WW(1.10):bd06/07/2011:svnLENOVO:pn7859CTO:pvrThinkPadL520:rvnLENOVO:rn7859CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7859CTO
dmi.product.version: ThinkPad L520
dmi.sys.vendor: LENOVO
---
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: valorin 2586 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=20653816-c79a-43a2-bd96-aab0af013acf
InstallationDate: Installed on 2013-10-29 (7 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: LENOVO 7859CTO
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en_AU:en
TERM=screen
PATH=(custom, no user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=416f70c3-ac4e-4e00-a8aa-56a37d187587 ro quiet splash noapic vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-3.11.0-12-generic N/A
linux-backports-modules-3.11.0-12-generic N/A
linux-firmware 1.116
Tags: saucy
Uname: Linux 3.11.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/04/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8GET38WW (1.15 )
dmi.board.name: 7859CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn7859CTO:pvrThinkPadL520:rvnLENOVO:rn7859CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7859CTO
dmi.product.version: ThinkPad L520
dmi.sys.vendor: LENOVO

See original description

Tags:

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2011-12-13:

AcpiTables.txt Edit (276.4 KiB, text/plain; charset="utf-8")
AlsaDevices.txt Edit (657 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (469 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (60.4 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (2.3 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (8.7 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.3.txt Edit (3.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (508 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (12.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (385 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (620 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.6 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (141 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.6 KiB, text/plain; charset="utf-8")
PulseSinks.txt Edit (2.2 KiB, text/plain; charset="utf-8")
PulseSources.txt Edit (3.5 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (182 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (125.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (274.3 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (707.8 KiB, text/plain; charset="utf-8")

Brad Figg (brad-figg) on 2011-12-13

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

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2011-12-13:

I've installed the latest upstream kernel (linux-image-3.2.0-030200rc5-generic_3.2.0-030200rc5.201112091935_amd64.deb) and the problem still exists.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2011-12-13:

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

The bugzilla.kernel.org site may still be unavailable due to the recent break-in. If that is the case, please add the tag: kernel-needs-upstream-bug-report

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	Confirmed → Triaged

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2011-12-13:

I've had no luck getting to the Kernel Bugzilla, so I've just added the tag.

tags:

added: kernel-needs-upstream-bug-report

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2011-12-29:

I did some testing today and I no longer need the 'noapic' flag in the boot options, only the 'nomodeset' flag.
This is annoying because that flag forces the graphics to be 1024x768, which makes it very hard to use.
(I've updated the bug at the top).

Anyone have any ideas? What can I do to get this fixed?

description:

updated

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-01-21:

With a recent update, the 'noapic' flag is once again required to boot.
I assume this is a regression in the kernel?

Stephen Rees-Carter (valorin) on 2012-01-29

summary:

- Unable to boot 12.04 without 'nomodeset' and 'noapic' in boot options
+ Unable to boot 12.04 without 'noapic' flag enabled in GRUB

Stephen Rees-Carter (valorin) on 2012-01-29

description:

updated

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-02-06: Re: Unable to boot 12.04 without 'noapic' flag enabled in GRUB

I've updated my BIOS, but it made no difference.

I went through the mainline kernel images on http://kernel.ubuntu.com/~kernel-ppa/mainline/ and installed a couple of them and tested them, with interesting results:

v3.2-rc7-precise/ Works without 'noapic'
v3.2.1-precise/ Works without 'noapic'
v3.2.2-precise/ Requires 'noapic' flag
v3.2.4-precise/ Requires 'noapic' flag

So the regression must have happened between v3.2.1 and v3.2.2.

How can I further debug this?
I've heard mention of git bisect - is there a good tutorial somewhere that can teach me how to use this to find the bug?

I'm going to look for version history now, see if it can shed some light on what changed.

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-02-06:

I've started the 'git bisect' process, but I've found something interesting. Using the git repository at http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary , the v3.2.1 tag is broken on my system while the v3.2 tag works. So for some reason the v3.2.1-precise build is different to the tag...?

Anyway, I'll follow the bisect process and report back when I have a commit to point a finger at.

Revision history for this message

Sascha Marcel Schmidt (omnileet) wrote on 2012-02-06:

Keep it up, can't wait to see your results.

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-02-07:

#10

config-3.2.0-thinkpad520 Edit (94.3 KiB, text/plain)

I am really confused now... it looks like the kernel config file itself is the cause of my woes.

I was given a slimmed down copy of the kernel config optimized for a Thinkpad L520 to use when building the kernel to make it quicker, which I started using after my previous comment on this ticket when I went through the 'git bisect' process. I went through the whole thing without any errors - it reported the broken commit being the one creating the tag!

So I tested that config file generating on the latest/master from the git repo, and it worked.

This was weird, since I'd tested these builds before with no success. So I went back and used the config file for the stock kernel installed on ubuntu (/boot/config-3.2.0-14-generic), and now any build I try is broken.

I can only assume that there is something in the config file I was provided which enables something my laptop needs?
Being a configuration parameter it would explain why some builds worked and others didn't, it would depend on whatever kernel config I was booted into at the time (I was using 'cp /boot/config-`uname -r` .config' before to generate it for each compile).

So, how do I go about debugging the config file? I wouldn't know where to start!

Revision history for this message

Sascha Marcel Schmidt (omnileet) wrote on 2012-02-07:

#11

Could you please upload the working config?

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-02-07:

#12

The working config is the one I uploaded in comment #10: config-3.2.0-thinkpad520

Revision history for this message

Sascha Marcel Schmidt (omnileet) wrote on 2012-02-07:

#13

Is v3.2-rc7-precise also broken with the stock config?

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-02-07:

#14

Do you mean the version I can download from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc7-precise/ ?
That one isn't broken on my machine.

Revision history for this message

Sascha Marcel Schmidt (omnileet) wrote on 2012-02-10:

#15

Is it somehow possible to find aut which configuration options have been used for compiling the kernel in that package?

Revision history for this message

Sascha Marcel Schmidt (omnileet) wrote on 2012-02-10:

#16

It looks like the configuration is logged in BUILD.LOG, maybe this is a good start to find out which options are responsible for the noapic issue. I'm going to compare the configuration of the 3.2-rc7-precise to the ones of 3.2.2-precise. IF there are differences I'll try to compile 3.2.5 with the same options as 3.2-rc7-precise.

Revision history for this message

Sascha Marcel Schmidt (omnileet) wrote on 2012-02-10:

#17

I compared the 0003-default-configs.patch files of 3.2.1-precise and 3.2.2-precise with a diff viewer. The only difference seems to be that in the newer one CONFIG_SSB_B43_PCI_BRIDGE=y gets added. So this might be the option that's causing the problems.

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-02-11:

#18

That configuration line isn't present in the custom one I was using either.
I will do some tests compiling the Kernel to see if toggling this configuration line resolves the bug or not.

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-02-11:

#19

I built v3.2.5 with and without that parameter, using the config from config-3.2.0-15-generic as a template and it broke both times, but when I use the Thinkpad L520 config it works.

So it's not only that parameter which is causing it.

I'll keep doing more tests, as I have a couple other ideas I want to try.

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-02-11:

#20

Ok, ignore my last. I just realised that 'make oldconfig' is adding the line back in again.
I'll manually comment it after running that and then compile, see if that changes anything.

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-02-12:

#21

Fun times - I ran the 'make oldconfig' command, and then edited the .config file manually, but it comes back again when I run the compile command:
make-kpkg clean && CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers

Now I'm out of my depth and I don't really know what to do next.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2012-03-08:

#22

There is a newer version of the kernel than the one you tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not. You can upgrade just your kernel by running the following in a terminal:

sudo apt-get update
sudo apt-get install linux

If the bug still exists in the latest kernel, please change the status back to "Confirmed". If the bug is fixed, please change the status to "Fix Released".

Thanks in advance

Stephen Rees-Carter (valorin) on 2012-03-09

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

Revision history for this message

Brad Figg (brad-figg) wrote on 2012-03-09: Test with newer development kernel (3.2.0-18.28)

#23

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

sudo apt-get update
sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete
tags:	added: kernel-request-3.2.0-18.28

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-03-09: Re: Unable to boot 12.04 without 'noapic' flag enabled in GRUB

#24

Done this already...

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

Joseph Salisbury (jsalisbury) on 2012-03-09

tags:

added: kernel-bug-exists-upstream
removed: kernel-needs-upstream-bug-report

Revision history for this message

Brad Figg (brad-figg) wrote on 2012-03-10: Test with newer development kernel (3.2.0-18.29)

#25

Thank you for taking the time to file a bug report on this issue.

You can update to the latest development kernel by simply running the following commands in a terminal window:

sudo apt-get update
sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete
tags:	added: kernel-request-3.2.0-18.29

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-03-10: Re: Unable to boot 12.04 without 'noapic' flag enabled in GRUB

#26

Doesn't this bug need to be reported upstream?

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-03-10:

#27

ARGH!! Can you please stop it with the automated notices... Can someone with some Kernel debugging skills help me with this one please?

tags:	added: bot-stop-nagging
Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2012-03-12:

#28

@Stephen

Is this bug now fixed upstream? It appears it is in v3.3-rc7 according to comment #14. If so, there is no need to open an upstream report. Just add the tag: kernel-fixed-upstream

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2012-03-13:

#29

@Joseph

Comment #14 refers to v3.2-rc7 not v3.3-rc7. See comment #7 for more details on the tested versions.
I just checked v3.3-rc7 and it is still broken, so it's not fixed.

It appears to be related to the config file, as opposed to the actual kernel code... see comments #10 & #17.
The result changed depending on which config file I used to compile the kernel. I was given a custom one for my L520 which works fine with the kernel git, while the Ubuntu default kernel config was causing the issue to happen.

My assumption is that there was a change of config defaults when v3.2-rc7, etc, were compiled, compared with the newer kernel builds (i.e. v3.3-rc7). It would be great to find out what this was, and have it reversed if possible?
It's also worth nothing that older kernel builds, such as the ones with 11.04 & 11.10 also had this issue. So it was resolved for a couple of kernel builds and then broken again.

Does that give you more to work with?

Revision history for this message

penalvch (penalvch) wrote on 2013-08-18:

#30

Stephen Rees-Carter, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags:	added: bios-outdated-1.21 removed: kernel-request-3.2.0-18.28 kernel-request-3.2.0-18.29
Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-10-18:

#31

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05:

#32

The bug still exists in saucy, and I've tried it with the mainline kernel v3.12, and it still exists.

tags:	added: apport-collected saucy
description:	updated
tags:	added: kernel-bug-exists-upstream-v3.12 removed: apport-collected precise
tags:	added: apport-collected
description:	updated

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: AlsaInfo.txt

#33

apport information

description:

updated

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05:

#34

AlsaInfo.txt Edit (34.6 KiB, text/plain)

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: BootDmesg.txt

#35

BootDmesg.txt Edit (65.3 KiB, text/plain)

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: CRDA.txt

#36

CRDA.txt Edit (216 bytes, text/plain)

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: CurrentDmesg.txt

#37

CurrentDmesg.txt Edit (5.2 KiB, text/plain)

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: IwConfig.txt

#38

IwConfig.txt Edit (541 bytes, text/plain)

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: Lspci.txt

#39

Lspci.txt Edit (30.2 KiB, text/plain)

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: Lsusb.txt

#40

Lsusb.txt Edit (450 bytes, text/plain)

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: ProcCpuinfo.txt

#41

ProcCpuinfo.txt Edit (3.6 KiB, text/plain)

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: ProcInterrupts.txt

#42

ProcInterrupts.txt Edit (2.1 KiB, text/plain)

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: ProcModules.txt

#43

ProcModules.txt Edit (6.0 KiB, text/plain)

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: RfKill.txt

#44

RfKill.txt Edit (182 bytes, text/plain)

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: UdevDb.txt

#45

UdevDb.txt Edit (148.6 KiB, text/plain)

apport information

description:

updated

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: AlsaInfo.txt

#46

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: BootDmesg.txt

#47

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: CRDA.txt

#48

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: CurrentDmesg.txt

#49

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: IwConfig.txt

#50

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: Lspci.txt

#51

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: Lsusb.txt

#52

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: ProcCpuinfo.txt

#53

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: ProcInterrupts.txt

#54

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: ProcModules.txt

#55

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: RfKill.txt

#56

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: UdevDb.txt

#57

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: UdevLog.txt

#58

apport information

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-05: WifiSyslog.txt

#59

WifiSyslog.txt Edit (276.1 KiB, text/plain)

apport information

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

penalvch (penalvch) on 2013-11-06

description:	updated
tags:	added: precise
tags:	added: bios-outdated-1.23 removed: bios-outdated-1.21

Revision history for this message

penalvch (penalvch) wrote on 2013-11-06: Re: Unable to boot 12.04 without 'noapic' flag enabled in GRUB

#60

Stephen Rees-Carter, as per http://download.lenovo.com/express/ddfm.html an update is available for your BIOS (1.23). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete
summary:	- Unable to boot 12.04 without 'noapic' flag enabled in GRUB + [Lenovo ThinkPad L520] Unable to boot 12.04 without 'noapic' flag + enabled in GRUB
description:	updated
tags:	added: regression-update

Revision history for this message

Stephen Rees-Carter (valorin) wrote on 2013-11-19:

#61

Wow, Lenovo finally decided to put out a BIOS update!

Just installed it, and the flag is no longer needed to boot. Time to close this issue :-)

Thanks for all the help to everyone involved.

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

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntulinux package

[Lenovo ThinkPad L520] Unable to boot 12.04 without 'noapic' flag enabled in GRUB

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package