i915_hotplug_work_func cause system crash

Bug #1230041 reported by databill
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
High
Unassigned

Bug Description

i915_hotplug_work_func cause system crash

NoteBook:X200
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 13.04
Release: 13.04
Codename: raring
 uname -a
Linux julien-X200 3.8.0-30-generic #44-Ubuntu SMP Thu Aug 22 20:54:42 UTC 2013 i686 i686 i686 GNU/Linux

Mostly the notebook crashes when it restore to work from "suspend" status. Occacionally it also stop work when I use firefox for some time.
When the problem happens, I can not use keyboard, mouse and I can not switch to terminal mode through ctl+alt+F1~F6.
I can ssh to the notebook from other pc, but I can not kill Xorg or reboot the notebook. The proc xorg in "uninterruptable sleep" staus.
It seems i915_hotplug_work_func has dead lock.

Information from dmesg:
[ 2520.564119] INFO: task kworker/u:3:225 blocked for more than 120 seconds.
[ 2520.564129] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2520.564135] kworker/u:3 D 00000000 0 225 2 0x00000000
[ 2520.564146] f6f59e90 00000046 f68659b0 00000000 f6f59e48 c1010c58 c19c9100 dcb5da4d
[ 2520.564165] 0000021d c19c9100 f7bc8100 f68659b0 00000002 a205ca2a 00000000 efbecfc0
[ 2520.564181] f6f59ed0 c1612d00 00000296 00000000 ed87c426 ef4cc000 c19c9100 00000001
[ 2520.564198] Call Trace:
[ 2520.564217] [<c1010c58>] ? __switch_to+0x2a8/0x330
[ 2520.564230] [<c1612d00>] ? __schedule+0x360/0x780
[ 2520.564242] [<c103ce48>] ? default_spin_lock_flags+0x8/0x10
[ 2520.564252] [<c161427d>] ? _raw_spin_lock_irqsave+0x2d/0x40
[ 2520.564269] [<c16133c3>] schedule+0x23/0x60
[ 2520.564278] [<c161360d>] schedule_preempt_disabled+0xd/0x10
[ 2520.564287] [<c1612366>] __mutex_lock_slowpath+0xc6/0x120
[ 2520.564295] [<c1611ef4>] mutex_lock+0x24/0x40
[ 2520.564344] [<f8b03948>] i915_hotplug_work_func+0x28/0x90 [i915]
[ 2520.564356] [<c1064b5b>] ? cwq_dec_nr_in_flight+0x5b/0x90
[ 2520.564366] [<c1065785>] process_one_work+0x135/0x3e0
[ 2520.564376] [<c161b973>] ? common_interrupt+0x33/0x38
[ 2520.564386] [<c1066c99>] worker_thread+0x119/0x3c0
[ 2520.564394] [<c1066b80>] ? manage_workers+0x240/0x240
[ 2520.564403] [<c106b6d4>] kthread+0x94/0xa0
[ 2520.564414] [<c1070000>] ? __hrtimer_start_range_ns+0x1f0/0x460
[ 2520.564424] [<c161b3b7>] ret_from_kernel_thread+0x1b/0x28
[ 2520.564432] [<c106b640>] ? kthread_create_on_node+0xc0/0xc0
[ 2520.564450] INFO: task Xorg:1283 blocked for more than 120 seconds.
[ 2520.564455] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2520.564459] Xorg D 00000000 0 1283 1275 0x00400004
[ 2520.564468] ef4cdc90 00203086 f34035c0 00000000 000007ff f6f58000 c19c9100 dcb4371d
[ 2520.564485] 0000021d c19c9100 f7bc8100 ed87c010 00000000 00000000 00000000 00000000
[ 2520.564509] 00000000 00000000 00000000 00000000 f344f700 ef4cdcf0 ef4cdcfc c10867f9
[ 2520.564525] Call Trace:
[ 2520.564537] [<c10867f9>] ? load_balance+0x99/0x670
[ 2520.564546] [<c16133c3>] schedule+0x23/0x60
[ 2520.564555] [<c1611b8d>] schedule_timeout+0x19d/0x240
[ 2520.564565] [<c1613241>] wait_for_common+0xa1/0x120
[ 2520.564575] [<c107c760>] ? try_to_wake_up+0x230/0x230
[ 2520.564584] [<c1613397>] wait_for_completion+0x17/0x20
[ 2520.564594] [<c1064ef7>] flush_workqueue+0xe7/0x330
[ 2520.564604] [<c1030000>] ? perf_ibs_start+0x10/0x120
[ 2520.564613] [<c1030101>] ? perf_ibs_start+0x111/0x120
[ 2520.564658] [<f8b299c7>] intel_crtc_page_flip+0x127/0x360 [i915]
[ 2520.564671] [<c114d953>] ? kmem_cache_alloc_trace+0x103/0x110
[ 2520.564715] [<f890c998>] drm_mode_page_flip_ioctl+0x238/0x310 [drm]
[ 2520.564732] [<c1611ee8>] ? mutex_lock+0x18/0x40
[ 2520.564766] [<f890c760>] ? drm_mode_gamma_get_ioctl+0xe0/0xe0 [drm]
[ 2520.564794] [<f88fceda>] drm_ioctl+0x42a/0x490 [drm]
[ 2520.564830] [<f890c760>] ? drm_mode_gamma_get_ioctl+0xe0/0xe0 [drm]
[ 2520.564861] [<f88fcab0>] ? drm_copy_field+0x80/0x80 [drm]
[ 2520.564871] [<c116fb90>] do_vfs_ioctl+0x80/0x580
[ 2520.564900] [<f88fd8f6>] ? drm_read+0xb6/0x160 [drm]
[ 2520.564917] [<c1050f33>] ? do_setitimer+0x123/0x210
[ 2520.564927] [<c1160505>] ? vfs_read+0xe5/0x160
[ 2520.564955] [<f88fd840>] ? drm_fasync+0x90/0x90 [drm]
[ 2520.564964] [<c11700fb>] sys_ioctl+0x6b/0x80
[ 2520.564974] [<c161b44d>] sysenter_do_call+0x12/0x28

stack Information from proc kworker/u:3:225
[<f8b03948>] i915_hotplug_work_func+0x28/0x90 [i915]
[<c1065785>] process_one_work+0x135/0x3e0
[<c1066c99>] worker_thread+0x119/0x3c0
[<c106b6d4>] kthread+0x94/0xa0
[<c161b3b7>] ret_from_kernel_thread+0x1b/0x28
[<ffffffff>] 0xffffffff

From the attached pictures,
I915 has about 1300 intertups per seconds, and i915_hotplug_work_func take about 734 ms/s.
---
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: julien 1823 F.... pulseaudio
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=0095ea5c-4c12-4d86-9f57-622f41bc3efe
InstallationDate: Installed on 2013-09-20 (4 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MachineType: LENOVO 7458CZ8
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=575022e0-3ec3-4d45-8a2c-03e88601e2d3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-30-generic N/A
 linux-backports-modules-3.8.0-30-generic N/A
 linux-firmware 1.106
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: raring
Uname: Linux 3.8.0-30-generic i686
UpgradeStatus: Upgraded to raring on 2013-09-20 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 09/17/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET60WW (3.10 )
dmi.board.name: 7458CZ8
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6DET60WW(3.10):bd09/17/2009:svnLENOVO:pn7458CZ8:pvrThinkPadX200:rvnLENOVO:rn7458CZ8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7458CZ8
dmi.product.version: ThinkPad X200
dmi.sys.vendor: LENOVO

Revision history for this message
databill (julienjut) wrote :
Revision history for this message
databill (julienjut) wrote :

The other attachment with this bug:

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1230041

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
databill (julienjut)
description: updated
Revision history for this message
databill (julienjut) wrote :

apport-collet runs failed.

julien@julien-X200:~$ apport-collect 1230041
ERROR: connecting to Launchpad failed: [Errno 2] No such file or directory
You can reset the credentials by removing the file "/home/julien/.cache/apport/launchpad.credentials"

I indeed find a .crash file. please refer to the attachment file.

When I use ubuntu-bug to report the crash file, I meet the problem like
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/538097

Revision history for this message
databill (julienjut) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected raring
description: updated
Revision history for this message
databill (julienjut) wrote : BootDmesg.txt

apport information

Revision history for this message
databill (julienjut) wrote : CRDA.txt

apport information

Revision history for this message
databill (julienjut) wrote : CurrentDmesg.txt

apport information

Revision history for this message
databill (julienjut) wrote : HookError_cloud_archive.txt

apport information

Revision history for this message
databill (julienjut) wrote : IwConfig.txt

apport information

Revision history for this message
databill (julienjut) wrote : Lspci.txt

apport information

Revision history for this message
databill (julienjut) wrote : Lsusb.txt

apport information

Revision history for this message
databill (julienjut) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
databill (julienjut) wrote : ProcEnviron.txt

apport information

Revision history for this message
databill (julienjut) wrote : ProcInterrupts.txt

apport information

Revision history for this message
databill (julienjut) wrote : ProcModules.txt

apport information

Revision history for this message
databill (julienjut) wrote : PulseList.txt

apport information

Revision history for this message
databill (julienjut) wrote : UdevDb.txt

apport information

Revision history for this message
databill (julienjut) wrote : UdevLog.txt

apport information

Revision history for this message
databill (julienjut) wrote : WifiSyslog.txt

apport information

Revision history for this message
databill (julienjut) wrote :
Download full text (4.2 KiB)

Even I set drm_kms_helper_poll to N, and disable gpe11, the problem can not be resolved.
Also I have installed the phc-intel(phc-intel_0.3.2.12.2~ppa1~loms~precise_all.deb).

cat /etc/modprobe.d/local.conf
options drm_kms_helper_poll=N

 grep . -r /sys/firmware/acpi/interrupts
/sys/firmware/acpi/interrupts/sci: 1655
/sys/firmware/acpi/interrupts/error: 0
/sys/firmware/acpi/interrupts/gpe00: 0 invalid
/sys/firmware/acpi/interrupts/gpe01: 0 enabled
/sys/firmware/acpi/interrupts/gpe02: 3 enabled
/sys/firmware/acpi/interrupts/gpe03: 0 disabled
/sys/firmware/acpi/interrupts/gpe04: 0 invalid
/sys/firmware/acpi/interrupts/gpe05: 0 invalid
/sys/firmware/acpi/interrupts/gpe06: 0 enabled
/sys/firmware/acpi/interrupts/gpe07: 0 invalid
/sys/firmware/acpi/interrupts/gpe08: 0 invalid
/sys/firmware/acpi/interrupts/gpe09: 0 disabled
/sys/firmware/acpi/interrupts/gpe10: 0 invalid
/sys/firmware/acpi/interrupts/gpe11: 1652 enabled
/sys/firmware/acpi/interrupts/gpe12: 0 invalid
/sys/firmware/acpi/interrupts/gpe13: 0 invalid
/sys/firmware/acpi/interrupts/gpe14: 0 invalid
/sys/firmware/acpi/interrupts/gpe15: 0 invalid
/sys/firmware/acpi/interrupts/gpe16: 0 invalid
/sys/firmware/acpi/interrupts/gpe0A: 0 invalid
/sys/firmware/acpi/interrupts/gpe17: 0 invalid
/sys/firmware/acpi/interrupts/gpe0B: 0 invalid
/sys/firmware/acpi/interrupts/gpe18: 0 enabled
/sys/firmware/acpi/interrupts/gpe0C: 0 invalid
/sys/firmware/acpi/interrupts/gpe19: 0 invalid
/sys/firmware/acpi/interrupts/gpe0D: 0 disabled
/sys/firmware/acpi/interrupts/gpe0E: 0 disabled
/sys/firmware/acpi/interrupts/gpe20: 0 disabled
/sys/firmware/acpi/interrupts/gpe0F: 0 invalid
/sys/firmware/acpi/interrupts/gpe21: 0 invalid
/sys/firmware/acpi/interrupts/gpe22: 0 invalid
/sys/firmware/acpi/interrupts/gpe23: 0 invalid
/sys/firmware/acpi/interrupts/gpe24: 0 invalid
/sys/firmware/acpi/interrupts/gpe25: 0 invalid
/sys/firmware/acpi/interrupts/gpe26: 0 invalid
/sys/firmware/acpi/interrupts/gpe1A: 0 invalid
/sys/firmware/acpi/interrupts/gpe27: 0 invalid
/sys/firmware/acpi/interrupts/gpe1B: 0 invalid
/sys/firmware/acpi/interrupts/gpe28: 0 invalid
/sys/firmware/acpi/interrupts/gpe1C: 0 invalid
/sys/firmware/acpi/interrupts/gpe29: 0 invalid
/sys/firmware/acpi/interrupts/gpe1D: 0 invalid
/sys/firmware/acpi/interrupts/gpe1E: 0 invalid
/sys/firmware/acpi/interrupts/gpe30: 0 invalid
/sys/firmware/acpi/interrupts/gpe1F: 0 invalid
/sys/firmware/acpi/interrupts/gpe31: 0 invalid
/sys/firmware/acpi/interrupts/gpe32: 0 invalid
/sys/firmware/acpi/interrupts/gpe33: 0 invalid
/sys/firmware/acpi/interrupts/gpe34: 0 invalid
/sys/firmware/acpi/interrupts/gpe35: 0 invalid
/sys/firmware/acpi/interrupts/gpe36: 0 invalid
/sys/firmware/acpi/interrupts/gpe2A: 0 invalid
/sys/firmware/acpi/interrupts/gpe37: 0 invalid
/sys/firmware/acpi/in...

Read more...

databill (julienjut)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc2-saucy/

Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
databill (julienjut) wrote : AlsaInfo.txt

apport information

description: updated
Revision history for this message
databill (julienjut) wrote : BootDmesg.txt

apport information

Revision history for this message
databill (julienjut) wrote : CRDA.txt

apport information

Revision history for this message
databill (julienjut) wrote : CurrentDmesg.txt

apport information

Revision history for this message
databill (julienjut) wrote : HookError_cloud_archive.txt

apport information

Revision history for this message
databill (julienjut) wrote : IwConfig.txt

apport information

Revision history for this message
databill (julienjut) wrote : Lspci.txt

apport information

Revision history for this message
databill (julienjut) wrote : Lsusb.txt

apport information

Revision history for this message
databill (julienjut) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
databill (julienjut) wrote : ProcEnviron.txt

apport information

Revision history for this message
databill (julienjut) wrote : ProcInterrupts.txt

apport information

Revision history for this message
databill (julienjut) wrote : ProcModules.txt

apport information

Revision history for this message
databill (julienjut) wrote : PulseList.txt

apport information

Revision history for this message
databill (julienjut) wrote : UdevDb.txt

apport information

Revision history for this message
databill (julienjut) wrote : UdevLog.txt

apport information

Revision history for this message
databill (julienjut) wrote : WifiSyslog.txt

apport information

Revision history for this message
databill (julienjut) wrote :

I update to the latest v3.12 kernel.
3.12.0-031200rc2-generic #201309231935 SMP Mon Sep 23 23:46:09 UTC 2013 i686 i686 i686 GNU/Linux

The X200 notebook has worked fine for 2 days, and the bug never show again. Even some other crashes happen, I still can use my notebook.

kernel-fixed-upstream

Revision history for this message
databill (julienjut) wrote :

kernel-fixed-upstream

penalvch (penalvch)
description: updated
Revision history for this message
penalvch (penalvch) wrote :

databill, as per http://download.lenovo.com/express/ddfm.html an update is available for your BIOS (3.22). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

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

Thank you for your understanding.

tags: added: bios-outdated-3.22
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
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.