Lockup with stacktrace (native_smp_send_reschedule)

Bug #588643 reported by Jean-Louis Dupond
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Having this error randomly on my computer.

On http://dupondje.be/DSCF1025.JPG you can find a stacktrace of the error.

Tried the mainline kernel 2.6.34, and this gives a 'BUG: soft lockup' error on all CPU's (quad core).

I can also reproduce this by for example build a package. Did it 4 times, and 4 times it locked.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfe020000 irq 20'
   Mixer name : 'Analog Devices AD1988B'
   Components : 'HDA:11d4198b,104381f6,00100200'
   Controls : 48
   Simple ctrls : 26
Date: Wed Jun 2 10:35:48 2010
HibernationDevice: RESUME=UUID=a22cf6aa-c83f-4a12-8bac-ba9e8bc1a3d3
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=82e2d193-fdd5-41c0-91b0-6848673d785f ro quiet splash
ProcEnviron:
 LANGUAGE=nl_BE:nl
 LANG=nl_BE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
WpaSupplicantLog:

dmi.bios.date: 03/18/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N32-SLI DELUXE ACPI BIOS Revision 5002
dmi.board.name: M2N32-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N32-SLIDELUXEACPIBIOSRevision5002:bd03/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N32-SLIDELUXE:rvr1.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
Jean-Louis Dupond (dupondje) wrote :
Revision history for this message
Jean-Louis Dupond (dupondje) wrote :

Oh btw, I have this issue from the day I replaced my CPU from a AMD Athlon 3800+ (single core) to a Phenom 2 945.

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

Hi Jean-Louis,

If you could also please 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: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
tags: removed: needs-upstream-testing
Revision history for this message
Jean-Louis Dupond (dupondje) wrote :

Seems like I have the same issue on 2.6.35-999-generic #201006021335.

Will try to make a screenshot of the error it gives on the screen!

Revision history for this message
Jean-Louis Dupond (dupondje) wrote :

Was able to get a full trace using the daily kernel.
The time it took to hit the bug was MUCH longer

Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
tags: added: kernel-uncat
Revision history for this message
Jean-Louis Dupond (dupondje) wrote :

Got a totally other result today ...
Seems like its more a hardware issue then Kernel issue.

We can close it with 'Invalid' ? :)

Revision history for this message
Jean-Louis Dupond (dupondje) wrote :

Sadly it seems the hardware/bios that is f00bar .. :(

Changed in linux (Ubuntu):
status: Triaged → 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.