BUG: soft lockup - CPU#1 stuck for 22s! [kworker/u16:5:142]

Bug #1460284 reported by lvm
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Kernel has been upgraded from 3.13.0-49 to 3.13.0-53, several minutes after the first reboot with the new kernel I noticed high wio while syslog was filling with messages listed below. When I tried to reboot (shutdown -r) it posted reboot messages to all console windows and then locked up - no reaction to keyboard, no ping response, had to powercycle it. After the reboot back to 3.13.0-49 system works fine, although filesystems were dirty. Didn't try it the second time - this system is too important for experiments. It has been running on the same hardware for a couple of years with no prior issues.

May 30 10:55:06 server kernel: [ 1702.612692] BUG: soft lockup - CPU#1 stuck for 22s! [kworker/u16:5:142]
May 30 10:55:06 server kernel: [ 1702.612704] Modules linked in: snd_hrtimer pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) cuse dm_crypt bnep rfcomm bluetooth mxm_wmi snd_hda_codec_hdmi kvm_amd kvm serio_raw k10temp snd_hda_codec_realtek snd_hda_intel snd_hda_codec nvidia(POX) snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer drm snd soundcore i2c_piix4 shpchp wmi binfmt_misc mac_hid parport_pc ppdev xfs lp libcrc32c parport raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq pata_acpi hid_generic usbhid hid usb_storage tg3 sata_sil24 pata_atiixp firewire_ohci ptp firewire_core pps_core ahci pata_via crc_itu_t libahci ati_agp
May 30 10:55:06 server kernel: [ 1702.612833] CPU: 1 PID: 142 Comm: kworker/u16:5 Tainted: P OX 3.13.0-53-generic #89-Ubuntu
May 30 10:55:06 server kernel: [ 1702.612839] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./990FX Extreme4, BIOS P1.30 09/13/2011
May 30 10:55:06 server kernel: [ 1702.612854] Workqueue: writeback bdi_writeback_workfn (flush-9:1)
May 30 10:55:06 server kernel: [ 1702.612863] task: efa0ce00 ti: f6030000 task.ti: f6030000
May 30 10:55:06 server kernel: [ 1702.612871] EIP: 0060:[<c165e148>] EFLAGS: 00000286 CPU: 1
May 30 10:55:06 server kernel: [ 1702.612880] EIP is at _raw_spin_unlock_irqrestore+0x18/0x40
May 30 10:55:06 server kernel: [ 1702.612887] EAX: 00000286 EBX: 00000286 ECX: 00000019 EDX: 00000286
May 30 10:55:06 server kernel: [ 1702.612893] ESI: e17b5560 EDI: f26c14a0 EBP: f6031c10 ESP: f6031c0c
May 30 10:55:06 server kernel: [ 1702.612898] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
May 30 10:55:06 server kernel: [ 1702.612903] CR0: 8005003b CR2: b77ca000 CR3: 01aa6000 CR4: 000007f0
May 30 10:55:06 server kernel: [ 1702.612908] Stack:
May 30 10:55:06 server kernel: [ 1702.612911] e17b5550 f6031c28 c112bd7e 00000286 f26c14a0 009c8000 f26c14a0 f6031c34
May 30 10:55:06 server kernel: [ 1702.612927] c112be0d cef88540 f6031cc4 f8910331 f6031c9c 00000003 00000001 00000000
May 30 10:55:06 server kernel: [ 1702.612941] c29b3200 00000001 01674000 00000000 00000000 f6031e08 009c9000 00000000
May 30 10:55:06 server kernel: [ 1702.612956] Call Trace:
May 30 10:55:06 server kernel: [ 1702.612969] [<c112bd7e>] __set_page_dirty_nobuffers+0x6e/0xe0
May 30 10:55:06 server kernel: [ 1702.612979] [<c112be0d>] redirty_page_for_writepage+0x1d/0x20
May 30 10:55:06 server kernel: [ 1702.613046] [<f8910331>] xfs_vm_writepage+0xa1/0x590 [xfs]
May 30 10:55:06 server kernel: [ 1702.613058] [<c112af40>] __writepage+0x10/0x40
May 30 10:55:06 server kernel: [ 1702.613067] [<c112af30>] ? global_dirtyable_memory+0xa0/0xa0
May 30 10:55:06 server kernel: [ 1702.613075] [<c112b8b3>] write_cache_pages+0x1a3/0x3c0
May 30 10:55:06 server kernel: [ 1702.613084] [<c112af30>] ? global_dirtyable_memory+0xa0/0xa0
May 30 10:55:06 server kernel: [ 1702.613094] [<c10b9c99>] ? tick_program_event+0x29/0x30
May 30 10:55:06 server kernel: [ 1702.613104] [<c112bb03>] generic_writepages+0x33/0x60
May 30 10:55:06 server kernel: [ 1702.613164] [<f890f3fa>] xfs_vm_writepages+0x3a/0x50 [xfs]
May 30 10:55:06 server kernel: [ 1702.613173] [<c112ca1a>] do_writepages+0x1a/0x40
May 30 10:55:06 server kernel: [ 1702.613182] [<c119e90c>] __writeback_single_inode+0x3c/0x1f0
May 30 10:55:06 server kernel: [ 1702.613191] [<c119f6fd>] writeback_sb_inodes+0x1bd/0x2e0
May 30 10:55:06 server kernel: [ 1702.613201] [<c119f89c>] __writeback_inodes_wb+0x7c/0xb0
May 30 10:55:06 server kernel: [ 1702.613209] [<c119fac2>] wb_writeback+0x1f2/0x270
May 30 10:55:06 server kernel: [ 1702.613219] [<c11a0cc7>] bdi_writeback_workfn+0x177/0x370
May 30 10:55:06 server kernel: [ 1702.613228] [<c165ace8>] ? __schedule+0x358/0x770
May 30 10:55:06 server kernel: [ 1702.613238] [<c106eeab>] process_one_work+0x11b/0x3b0
May 30 10:55:06 server kernel: [ 1702.613246] [<c106fae9>] worker_thread+0xf9/0x380
May 30 10:55:06 server kernel: [ 1702.613254] [<c106f9f0>] ? rescuer_thread+0x380/0x380
May 30 10:55:06 server kernel: [ 1702.613262] [<c1075391>] kthread+0xa1/0xc0
May 30 10:55:06 server kernel: [ 1702.613271] [<c1665877>] ret_from_kernel_thread+0x1b/0x28
May 30 10:55:06 server kernel: [ 1702.613280] [<c10752f0>] ? kthread_create_on_node+0x140/0x140
May 30 10:55:06 server kernel: [ 1702.613285] Code: 83 e8 01 75 f2 89 c8 89 f2 8d b6 00 00 00 00 eb e1 66 90 55 89 e5 53 3e 8d 74 26 00 89 d3 3e 8d 74 26 00 f0 80 00 02 89 d8 50 9d <8d> 74 26 00 5b 5d c3 90 0f b7 10 f0 80 00 02 f6 40 01 01 74 e7

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: i386
CurrentDesktop: KDE
Date: Sat May 30 13:25:15 2015
InstallationDate: Installed on 2011-08-18 (1380 days ago)
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2014-10-18 (224 days ago)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: lvm 3131 F.... pulseaudio
 /dev/snd/controlC0: lvm 3131 F.... pulseaudio
 /dev/snd/seq: timidity 2289 F.... timidity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=d22ce633-8298-47af-bd3b-b2f2c011e08f
InstallationDate: Installed on 2011-08-18 (1598 days ago)
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
IwConfig:
 lo no wireless extensions.

 eth2 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic root=UUID=b9992d14-0c4b-44a9-9946-b900b6a6eb73 ro libata.dma=5 quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-74-generic N/A
 linux-backports-modules-3.13.0-74-generic N/A
 linux-firmware 1.127.19
RfKill:

Tags: trusty
Uname: Linux 3.13.0-74-generic i686
UpgradeStatus: Upgraded to trusty on 2014-10-18 (442 days ago)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 09/13/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: 990FX Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd09/13/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
lvm (lvm-royal) wrote :
lvm (lvm-royal)
affects: xorg (Ubuntu) → linux-lts-trusty (Ubuntu)
Revision history for this message
penalvch (penalvch) wrote :

lvm, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1460284

affects: linux-lts-trusty (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
lvm (lvm-royal) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
lvm (lvm-royal) wrote : BootDmesg.txt

apport information

Revision history for this message
lvm (lvm-royal) wrote : CRDA.txt

apport information

Revision history for this message
lvm (lvm-royal) wrote : CurrentDmesg.txt

apport information

Revision history for this message
lvm (lvm-royal) wrote : Lspci.txt

apport information

Revision history for this message
lvm (lvm-royal) wrote : Lsusb.txt

apport information

Revision history for this message
lvm (lvm-royal) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
lvm (lvm-royal) wrote : ProcEnviron.txt

apport information

Revision history for this message
lvm (lvm-royal) wrote : ProcInterrupts.txt

apport information

Revision history for this message
lvm (lvm-royal) wrote : ProcModules.txt

apport information

Revision history for this message
lvm (lvm-royal) wrote : UdevDb.txt

apport information

Revision history for this message
lvm (lvm-royal) wrote : UdevLog.txt

apport information

Revision history for this message
lvm (lvm-royal) wrote : WifiSyslog.txt

apport information

Revision history for this message
penalvch (penalvch) wrote :

lvm, as per http://www.asrock.com/mb/AMD/990FX%20Extreme4/?cat=Download&os=BIOS an update to your computer's buggy and outdated BIOS is available (2.70). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) Please mark this report Status Confirmed. If it's not reproducible, please mark this as Invalid.

Thank you for your understanding.

tags: added: bios-outdated-2.70
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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