Xorg soft lockup using google maps (street view) in firefox under Nouveau

Bug #1449753 reported by b
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I can cause an Xorg soft lockup simply by using google street view for a few minutes under firefox 37.0.2.

Switched to Nouveau recently due to issues with NVIDIA proprietary driver for this GeForce 6600 AGP card.

Following is the lockup trace from kern.log:

Apr 28 11:31:59 insitu kernel: [ 849.902770] nouveau [Xorg[3892]] ib channel create, -22
Apr 28 11:31:59 insitu kernel: [ 849.998956] nouveau E[ PFIFO][0000:01:00.0] CACHE_ERROR - ch 3 [firefox[3757]] subc 0 mthd 0x0050 data 0x00000006
Apr 28 11:31:59 insitu kernel: [ 860.080030] BUG: soft lockup - CPU#0 stuck for 24s! [Socket Thread:3762]
Apr 28 11:31:59 insitu kernel: [ 860.080033] Modules linked in: cfg80211 cuse rfcomm bnep bluetooth binfmt_misc reiserfs dm_crypt snd_via82xx rc_winfast snd_via82xx_modem snd_mpu401_uart snd_ac97_codec gameport ac97_bus tuner_simple snd_pcm tuner_types snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi tda9887 tda8290 snd_seq tea5767 tuner snd_seq_device snd_timer amd64_edac_mod cx8800 snd edac_core serio_raw cx88xx btcx_risc edac_mce_amd k8temp tveeprom videobuf_dma_sg soundcore i2c_viapro rc_core v4l2_common videobuf_core videodev shpchp parport_pc ppdev visor usbserial mac_hid lp parport raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear raid1 pata_acpi hid_generic usbhid hid nouveau mxm_wmi wmi video i2c_algo_bit ttm drm_kms_helper drm pata_via firewire_ohci sata_via skge sata_promise firewire_core floppy crc_itu_t
Apr 28 11:31:59 insitu kernel: [ 860.080048] CPU: 0 PID: 3762 Comm: Socket Thread Not tainted 3.13.0-49-generic #83-Ubuntu
Apr 28 11:31:59 insitu kernel: [ 860.080048] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./A8V Deluxe, BIOS 1018.002 08/16/2007
Apr 28 11:31:59 insitu kernel: [ 860.080048] task: ffff8800a9703000 ti: ffff8800a45f4000 task.ti: ffff8800a45f4000
Apr 28 11:31:59 insitu kernel: [ 860.080048] RIP: 0010:[<ffffffff813797c2>] [<ffffffff813797c2>] ioread32+0x42/0x50
Apr 28 11:31:59 insitu kernel: [ 860.080048] RSP: 0018:ffff8800a45f5ab0 EFLAGS: 00000292
Apr 28 11:31:59 insitu kernel: [ 860.080048] RAX: 0000000000000005 RBX: ffff880124703000 RCX: 0000000000000036
Apr 28 11:31:59 insitu kernel: [ 860.080048] RDX: 000000000000e178 RSI: ffffc900007fe048 RDI: ffffc900007fe048
Apr 28 11:31:59 insitu kernel: [ 860.080048] RBP: ffff8800a45f5ab8 R08: 0000000000016260 R09: ffff88012b001b00
Apr 28 11:31:59 insitu kernel: [ 860.080048] R10: ffffffffa0187dce R11: ffff8801279a0210 R12: 00000000b0ac1540
Apr 28 11:31:59 insitu kernel: [ 860.080048] R13: ffffffff8164679f R14: ffff8800a45f5a50 R15: ffff8800b7e21200
Apr 28 11:31:59 insitu kernel: [ 860.080048] FS: 00007f95e70f0700(0000) GS:ffff88012fc00000(0000) knlGS:0000000000000000
Apr 28 11:31:59 insitu kernel: [ 860.080048] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 28 11:31:59 insitu kernel: [ 860.080048] CR2: 00007faaea457024 CR3: 00000000ab4c9000 CR4: 00000000000007f0
Apr 28 11:31:59 insitu kernel: [ 860.080048] Stack:
Apr 28 11:31:59 insitu kernel: [ 860.080048] ffffffffa015b1e5 ffff8800a45f5ac8 ffffffffa018febf ffff8800a45f5b00
Apr 28 11:31:59 insitu kernel: [ 860.080048] ffffffffa0187442 ffff88012839e000 0000000000000000 0000000000000000
Apr 28 11:31:59 insitu kernel: [ 860.080048] ffff8800a9703000 0000000000000000 ffff8800a45f5b58 ffffffffa0187a85
Apr 28 11:31:59 insitu kernel: [ 860.080048] Call Trace:
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffffa015b1e5>] ? _nouveau_fifo_channel_rd32+0x15/0x20 [nouveau]
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffffa018febf>] nv10_fence_read+0x1f/0x30 [nouveau]
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffffa0187442>] nouveau_fence_update+0x62/0x90 [nouveau]
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffffa0187a85>] nouveau_fence_wait+0xc5/0x1a0 [nouveau]
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffffa0187df8>] ? nouveau_fence_new+0x68/0xb0 [nouveau]
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffffa018601d>] nouveau_channel_idle+0x6d/0x90 [nouveau]
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffffa018ec52>] nouveau_abi16_chan_fini.isra.2+0x32/0x1d0 [nouveau]
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffffa018effe>] nouveau_abi16_fini+0x3e/0x80 [nouveau]
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffffa01850a2>] nouveau_drm_preclose+0x42/0xa0 [nouveau]
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffffa006fad3>] drm_release+0x73/0x630 [drm]
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff811bfb24>] __fput+0xe4/0x260
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff811bfcee>] ____fput+0xe/0x10
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff81088354>] task_work_run+0xc4/0xe0
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff81069d48>] do_exit+0x2b8/0xa50
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff8169452c>] ? inet_recvmsg+0x6c/0x80
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff8160d5fa>] ? sock_recvmsg+0x9a/0xd0
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff8106a55f>] do_group_exit+0x3f/0xa0
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff8107a200>] get_signal_to_deliver+0x1d0/0x6f0
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff81013458>] do_signal+0x48/0xa40
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff8160d7a7>] ? SYSC_recvfrom+0x127/0x160
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff810a02c5>] ? set_next_entity+0x95/0xb0
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff8101260b>] ? __switch_to+0x16b/0x4d0
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff81013eb9>] do_notify_resume+0x69/0xb0
Apr 28 11:31:59 insitu kernel: [ 860.080048] [<ffffffff8172a1a2>] retint_signal+0x48/0x86

Trying the daily build now...

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 x86_64
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue Apr 28 14:09:35 2015
DistUpgraded: 2014-12-31 22:27:02,135 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 NVIDIA Corporation NV43 [GeForce 6600] [10de:00f2] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:81b1]
InstallationDate: Installed on 2010-11-05 (1635 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log'
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=0ab4bde0-8376-4cbe-9bc0-af6c3a7936bd ro irqpoll=1 drm.debug=0xe plymouth:debug nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to trusty on 2015-01-01 (117 days ago)
dmi.bios.date: 08/16/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1018.002
dmi.board.name: A8V Deluxe
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1018.002:bd08/16/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnA8VDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
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.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Apr 28 13:59:01 2015
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.7
xserver.video_driver: nouveau

Tags: nouveau
Revision history for this message
b (ben-ekran) wrote :
Revision history for this message
b (ben-ekran) wrote :

This bug was not reproducible using yesterday’s daily build of Vivid.

Revision history for this message
penalvch (penalvch) wrote :

B. Bogart, thank you for reporting this and helping make Ubuntu better. Would you need a backport to a release prior to Vivid, or may this be closed as Status Invalid?

Changed in xorg (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
b (ben-ekran) wrote :

Christopher: What exactly do you mean by "Would you need a backport to a release prior to Vivid".

I plan to stick to 14.04 LTS until its end of life, so if a backport of xorg/nouveau is available it would help me avoid these very irritating soft-lockups.

Please advise.

Revision history for this message
penalvch (penalvch) wrote :

B. Bogart, to see if this is already resolved, could you please upgrade to the enablement stack as outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise if this is reproducible?

Revision history for this message
b (ben-ekran) wrote :

Christopher: The issue does seem resolved after installing the LTS enablement stacks. I'll test for a few days and mark this bug invalid if it does not return.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg (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.