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

Bug #562026 reported by Andrew Frank
130
This bug affects 30 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

happend the second time on restart. the bug may be the same as reported for the 2.6.31 kernel, but i did not experience it before (i.e. before the upgrade to the latest 2.6.32-20 kernel, it was not in the 2.6.32-19 kernel).
andrew

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-20-generic 2.6.32-20.29
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
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: frank 1450 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0a00000 irq 22'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,10cf0000,00100004 HDA:11c11040,10cf14a5,00100200'
   Controls : 12
   Simple ctrls : 7
Date: Tue Apr 13 07:35:58 2010
Failure: oops
HibernationDevice: RESUME=UUID=99eaaf42-f5da-41f6-bb5b-7a6d843b33e8
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
MachineType: FUJITSU LifeBook P1630
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-20-generic root=UUID=ed2639b4-f090-4f2a-a775-c821614f1b34 ro quiet splash
RelatedPackageVersions: linux-firmware 1.33
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90()
dmi.bios.date: 11/14/2008
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.07
dmi.board.name: FJNB1F8
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: A322H10305301010
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.07:bd11/14/2008:svnFUJITSU:pnLifeBookP1630:pvr:rvnFUJITSU:rnFJNB1F8:rvr:cvnA322H10305301010:ct10:cvr:
dmi.product.name: LifeBook P1630
dmi.sys.vendor: FUJITSU

Revision history for this message
Andrew Frank (frank-geoinfo) wrote :
Revision history for this message
Andrew Frank (frank-geoinfo) wrote :

it did positively not occur on 2.6.32-19 but also not on the next restart with the -20 kernel. it may be spurious ..
i will report if it happens again!
andrew

Revision history for this message
Andrew Frank (frank-geoinfo) wrote :

this time it did occur on waking up from suspend (which seems to work when i close the lid, but not when i do it from the menu).

Revision history for this message
Haggai Eran (haggai-eran) wrote :

I'm not sure its related, but I got this oops after upgrading to 2.6.32-20.30 today. I'm also having problems with my wireless lan connection. (connection seems dead a couple of seconds after connecting).
I'm using an Asus Eee 1005HA netbook.

Revision history for this message
animeman (animeman-1) wrote :

i thankfully am not having the wifi connection problem best luck to you eran

Revision history for this message
Haggai Eran (haggai-eran) wrote :

Yes, I guess it was unrelated. Anyway, I think the wifi problem was solved by installed the backport wireless modules package for lucid. I'll report in another bug if it returns.

Revision history for this message
Sean Fitzpatrick (sean-fitzpatrick) wrote :

I think this is the same as a bug I reported (561125). I get a crash report about 60 seconds after every reboot.
I'm also on an eeePC 1005HA. There wasn't any problem until I updated to the -20 kernel, but I tried booting with the -19 kernel and got the same result.

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.