BUG: soft lockup - CPU#0 stuck for 94s! [watchdog/0:5]

Bug #498844 reported by Muflone
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
transmission (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: transmission

I was running ubuntu karmic i386 guest inside a VMWare VM with a Ubuntu Jaunty amd64 host.

In the host system I tried to download a .torrent filename using Transmission 1.70 then the disk started to word really intensively, the whole machine seemed freezed.
It took at least 2 minutes to let me access from the VT-1 and over 5 minutes to stop the intense disk activity, which when ended the whole system resumed the normal activity.

On the guest OS I've found such report.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: AudioPCI [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3037 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'AudioPCI'/'Ensoniq AudioPCI ENS1371 at 0x2080, irq 19'
   Mixer name : 'Cirrus Logic CS4297A rev 3'
   Components : 'AC97a:43525913'
   Controls : 24
   Simple ctrls : 13
Date: Sun Dec 20 10:23:11 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=d26b096a-b316-4682-bc20-6fdf89597efd
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=7a4c54bf-9975-4e0d-bb5b-4a3bf392758c ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:

SourcePackage: linux
Tags: kernel-oops
Title: BUG: soft lockup - CPU#0 stuck for 94s! [watchdog/0:5]
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 08/15/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd08/15/2008:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

Revision history for this message
Muflone (il-muflone) wrote :
Revision history for this message
Charles Kerr (charlesk) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Does this problem persist in Transmission version 1.75? I don't think that 1.70 shipped with any Ubuntu release.

Revision history for this message
Muflone (il-muflone) wrote :

thank you charles for answering me
indeed you're right, transmission 1.70 came from the getdeb repository, I didn't noticed before.

I'm actually using Jaunty so the latest available version was 1.51-0ubuntu3.

Nevertheless this bug should be considered invalid because I'm still experiencing various soft lockup during intense disk activity even while Transmission's not running. I think they're caused from the 2.6.30 kernel from proposed jaunty repository.

Revision history for this message
Muflone (il-muflone) wrote :

The defect happens with heavy disk activity even with Transmission closed.
Please see comment #3

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