BUG: soft lockup due to APIC being enabled in BIOS

Bug #565202 reported by Tony Mugan
32
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

This is a periodic lockup on this PC with all latest Lucid updates.

The machine is completely unresponsive and even the caps-lock does not work.
It eventually comes back if I wait.
I have also reported similar bugs previously as shown - so they could be marked as duplicate I suspect.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/560493

https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.32/+bug/560676

Happy to do some testing if anyone can direct me.

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: No
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: tony 1490 F.... pulseaudio
 /dev/snd/controlC0: tony 1490 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'VT82xx'/'HDA VIA VT82xx at 0xfbefc000 irq 17'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1043c603,00100002'
   Controls : 38
   Simple ctrls : 21
Card1.Amixer.info:
 Card hw:1 'U0x46d0x8d7'/'USB Device 0x46d:0x8d7 at usb-0000:00:10.1-1, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:08d7'
   Controls : 3
   Simple ctrls : 2
Date: Sat Apr 17 15:22:27 2010
Failure: oops
Frequency: I don't know.
HibernationDevice: RESUME=UUID=b832bb82-880d-4e72-9607-b12040855c55
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=459e14ec-8e51-497d-91c0-6bbf70c508b2 ro quiet splash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: BUG: soft lockup - CPU#0 stuck for 74s! [ksoftirqd/0:4]
dmi.bios.date: 09/14/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1005
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M2V-MX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1005:bd09/14/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2V-MX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Tony Mugan (tmugan) wrote :
Revision history for this message
Tony Mugan (tmugan) wrote :

I tried the ubuntu-packaged mainline kernels and found the same issue with soft lockups.

Current Kernel : Linux orac 2.6.34-020634rc5-generic #020634rc5 SMP Tue Apr 20 09:07:31 UTC 2010 x86_64 GNU/Linux

I then tried altering some BIOS settings and disabled ACPI and APIC.

I have not had an lockups since. Since the lockups were so regular, I am sure this was the issue.

For the record, here is the link to the kernel bug I raised

https://bugzilla.kernel.org/show_bug.cgi?id=15804

tags: added: kj-triage
Revision history for this message
Tony Mugan (tmugan) wrote :

The actual settings required in BIOS (M2v-MX Motherboard BIOS v1005 09/14/07) are as follows to avoid CPU soft lockups...

Under the "Power" menu

ACPI 2.0 Support [YES]
ACPI APIC Support [Disabled]

And the lockups go away :)

Have just confirmed with latest available mainline kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc6-lucid/) that the lockups will still happen if APIC support is enabled in BIOS

tony@orac:~$ uname -r
2.6.34-020634rc6-generic

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Tony,

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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

apport-collect -p linux 565202

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Tony Mugan (tmugan) wrote :

Have just confirmed with mainline kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/) that the lockups will still happen if APIC support is enabled in BIOS.

Just had a short lockup (5 secs) on the new 2.6.35-rc1 which only interrupted mouse and but not music that was playing at the time. (have not had audio playing before during a lockup so this may be common)

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc1-lucid/

I'll continue with this newer kernel until a longer lockup is demonstrated.

Revision history for this message
Tony Mugan (tmugan) wrote :

Ok, just had a longer lockup in the 2.6.35-rc1 mainline kernel.
I will remove the 'needs-upstream-testing' tag as requested.

tags: removed: needs-upstream-testing
Revision history for this message
Mihai Secasiu (mihai-patchlog) wrote :

I have a similar problem with latest kernel from 10.4 . My problem is more severe as I can't even boot because of it and it doesn't go away.
a few seconds after the "Starting up...." message I get:
BUG: soft lockup - CPU0 stuck for 61s! [events/0:6]
and It goes on like this for minutes till I get bored of waiting :)
I disabled ACPI APIC Support and I also tried with ACPI fully disabled but still no boot.

I don't have this problem with kenel 2.6.31

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Mihai,
  Please file a new bug for your issue.

Thanks!

~JFo

Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Tony Mugan (tmugan) wrote :

Have changed the title to better describe the issue here.

summary: - BUG: soft lockup - CPU#0 stuck for 74s! [ksoftirqd/0:4]
+ BUG: soft lockup due to APIC being enabled in BIOS
Revision history for this message
randallw (rwayth) wrote :

Question for Tony: if you disable APIC in your bios, how many CPUs does your system report?

I seem to be having a very similar bug to this. I can disable APIC in the bios and the system seems stable, but I only get one of my 4 CPU cores.

Cheers,
Randall

Revision history for this message
Tony Mugan (tmugan) wrote :

Randall,

Sorry, I only have one core :( so can't give you anything useful.

Regards,

Tony.

Revision history for this message
penalvch (penalvch) wrote :

Tony Mugan, 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 kernel 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.1

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.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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