Ubuntu

WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x7b/0xa0()

Bug #563587 reported by Joan Mercadal on 2010-04-15

This bug report is a duplicate of: Bug #561125: 168c:002b WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90() [ath9k]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu	Confirmed	Undecided	Unassigned

Bug Description

Sorry I have no more info

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-20-generic 2.6.32-20.30
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic x86_64
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
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: joan 1499 F.... pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfe9f4000 irq 22'
   Mixer name : 'Intel G45 DEVCTG'
   Components : 'HDA:10ec0269,10431443,00100004 HDA:80862802,80860101,00100000'
   Controls : 17
   Simple ctrls : 9
Date: Thu Apr 15 01:04:43 2010
Failure: oops
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
MachineType: ASUSTeK Computer Inc. UL30A
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-20-generic root=UUID=fd62eb4c-1e7c-40a4-8890-88446ece62fe ro splash vga=789 quiet splash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x7b/0xa0()
dmi.bios.date: 08/20/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UL30A
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd08/20/2009:svnASUSTeKComputerInc.:pnUL30A:pvr1.0:rvnASUSTeKComputerInc.:rnUL30A:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UL30A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Tags:

Revision history for this message

Joan Mercadal (joan-mercadal) wrote on 2010-04-15:

AlsaDevices.txt Edit (517 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (265 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (44.3 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (8.2 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.1.txt Edit (974 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (384 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (20.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (687 bytes, text/plain; charset="utf-8")
OopsText.txt Edit (3.0 KiB, text/plain; charset="utf-8")
PciMultimedia.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.6 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (112 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (123.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (258.9 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (193.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Gabe Gorelick (gabegorelick) wrote on 2010-04-15:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 561125, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.