From: Thomas Richter <thor@math.tu-berlin.de>
To: "Chris Wilson" <chris@chris-wilson.co.uk>,
"Thomas Richter" <richter@rus.uni-stuttgart.de>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Broken suspend/resume on i830 (with debug information)
Date: Sun, 08 Jun 2014 23:20:21 +0200 [thread overview]
Message-ID: <5394D395.8060802@math.tu-berlin.de> (raw)
In-Reply-To: <17205_1401811442_538DF1F2_17205_16362_1_20140603160352.GA6129@nuc-i3427.alporthouse.com>
Dear intel experts,
just tried to debug the i830 resume on the S6010. With netconsole and
netcat, I found that the kernel locks up when trying to load the i915
module on suspend. Here is the output of the kernel:
[ 1772.867519] hid-generic 0003:046D:C05F.002B: input,hidraw0: USB HID
v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:1d.0-2/input0
[ 1800.068074] INFO: task modprobe:3321 blocked for more than 120 seconds.
[ 1800.068130] Not tainted 3.15.0-rc7+ #6
[ 1800.068150] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[ 1800.068177] modprobe D f86d6600 0 3321 2855 0x00000000
[ 1800.068436] f4102cb0 00000082 f41c88d4 f86d6600 00000000 f41c88d4
f41c8000 f6a27fec
[ 1800.069063] f4102cb0 00000000 00000000 f84a5885 f41c88d4 f86d6600
00000000 fffffffa
[ 1800.069682] f41c8000 f41c88d4 f86d66a8 00000000 f41c8ab0 f84a0038
00000000 00000000
[ 1800.070274] Call Trace:
[ 1800.070587] [<f86d6600>] ? set_clock+0x50/0x60 [i915]
[ 1800.070664] [<f84a5885>] ? bit_xfer+0x255/0x4c4 [i2c_algo_bit]
[ 1800.070772] [<f86d6600>] ? set_clock+0x50/0x60 [i915]
[ 1800.070907] [<f86d66a8>] ? intel_gpio_post_xfer+0x28/0x60 [i915]
[ 1800.070977] [<c13199e5>] ? schedule_preempt_disabled+0x5/0x10
[ 1800.071005] [<c131a640>] ? __ww_mutex_lock_slowpath+0x7c/0xec
[ 1800.071056] [<f8246dfa>] ? drm_modeset_lock+0x2a/0xb0 [drm]
[ 1800.071185] [<f86b6579>] ? intel_get_load_detect_pipe+0xa9/0x4b0 [i915]
[ 1800.071320] [<f86b83b6>] ? intel_modeset_setup_hw_state+0xab6/0xd40
[i915]
[ 1800.071448] [<f869ca90>] ? gen4_write64+0x50/0x50 [i915]
[ 1800.071513] [<f8246dfa>] ? drm_modeset_lock+0x2a/0xb0 [drm]
[ 1800.071614] [<f86b8dfd>] ? intel_modeset_init+0x7bd/0x12f0 [i915]
[ 1800.071676] [<c10c43d1>] ? kmem_cache_alloc+0x31/0x100
[ 1800.071744] [<f8232991>] ? drm_irq_install+0xa1/0x180 [drm]
[ 1800.071856] [<f86e2e41>] ? i915_driver_load+0x9d1/0xee0 [i915]
[ 1800.072023] [<f86e06e0>] ? i915_dma_init+0x2c0/0x2c0 [i915]
[ 1800.072157] [<c117c17b>] ? kobject_uevent_env+0xeb/0x4f0
[ 1800.072184] [<c117c17b>] ? kobject_uevent_env+0xeb/0x4f0
[ 1800.072239] [<c117bff0>] ? add_uevent_var+0xc0/0xc0
[ 1800.072271] [<c1224c1c>] ? get_device+0xc/0x20
[ 1800.072407] [<c1312643>] ? klist_node_init+0x33/0x50
[ 1800.072489] [<c13126f7>] ? klist_add_tail+0x17/0x40
[ 1800.072668] [<f8237a41>] ? drm_sysfs_device_add+0xb1/0x110 [drm]
[ 1800.072708] [<f823479e>] ? drm_dev_register+0x9e/0x100 [drm]
[ 1800.072803] [<f8236c39>] ? drm_get_pci_dev+0x79/0x1f0 [drm]
[ 1800.072889] [<c119db2f>] ? pci_device_probe+0x7f/0xd0
[ 1800.072976] [<c111e4ad>] ? sysfs_create_link+0x1d/0x40
[ 1800.073114] [<c12286ca>] ? driver_probe_device+0x6a/0x230
[ 1800.073202] [<c117b5b0>] ? kobject_add_internal+0x150/0x2c0
[ 1800.073366] [<c1228890>] ? driver_probe_device+0x230/0x230
[ 1800.073392] [<c1228909>] ? __driver_attach+0x79/0x80
[ 1800.073527] [<c12270c8>] ? bus_for_each_dev+0x38/0x70
[ 1800.073609] [<c1228296>] ? driver_attach+0x16/0x20
[ 1800.073771] [<c1228890>] ? driver_probe_device+0x230/0x230
[ 1800.073797] [<c1227f41>] ? bus_add_driver+0xe1/0x1e0
[ 1800.073932] [<c1228e61>] ? driver_register+0x51/0xd0
[ 1800.074020] [<f80d2000>] ? 0xf80d1fff
[ 1800.074101] [<f80d2000>] ? 0xf80d1fff
[ 1800.074235] [<c1000472>] ? do_one_initcall+0xe2/0x130
[ 1800.074316] [<c131a468>] ? mutex_lock+0x8/0x15
[ 1800.074400] [<c1095335>] ? jump_label_module_notify+0x155/0x1a0
[ 1800.074487] [<c104ecf0>] ? notifier_call_chain+0x40/0x60
[ 1800.074571] [<c104ef3b>] ? __blocking_notifier_call_chain+0x4b/0x70
[ 1800.074738] [<c107f082>] ? load_module+0x1a62/0x2180
[ 1800.074774] [<c102d4c0>] ? vmalloc_sync_all+0xd0/0xd0
[ 1800.074911] [<c107f831>] ? SyS_init_module+0x91/0xd0
[ 1800.075007] [<c131bc2f>] ? sysenter_do_call+0x12/0x26
Maybe that helps to find the issue with the broken resume on the S6010.
Greetings,
Thomas
prev parent reply other threads:[~2014-06-08 21:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 14:02 830GM still woes Thomas Richter
2014-05-16 14:41 ` Chris Wilson
2014-05-16 15:09 ` Daniel Vetter
2014-05-16 16:04 ` Ville Syrjälä
2014-05-16 16:50 ` Daniel Vetter
[not found] ` <23914_1400259040_537641E0_23914_9298_1_20140516165034.GT8790@phenom.ffwll.local>
2014-05-17 10:58 ` Thomas Richter
2014-05-29 14:10 ` Thomas Richter
2014-05-29 21:19 ` Breaking suspend/resume by the Pipe A quirk Thomas Richter
2014-06-02 8:27 ` Daniel Vetter
2014-06-02 10:34 ` [PATCH] Align i830 watermark to cache lines Thomas Richter
2014-06-02 10:41 ` Breaking suspend/resume by the Pipe A quirk Thomas Richter
2014-06-02 15:27 ` Daniel Vetter
2014-06-02 15:38 ` [Patch] Disabling the pipe A quirk for the Fujitsu S6010 Thomas Richter
2014-06-02 15:56 ` Daniel Vetter
2014-06-02 16:52 ` Thomas Richter
2014-06-02 17:39 ` Daniel Vetter
2014-06-02 18:44 ` Thomas Richter
[not found] ` <1027_1401722832_538C97D0_1027_15897_1_20140602152702.GU19050@phenom.ffwll.local>
2014-06-03 14:38 ` Breaking suspend/resume by the Pipe A quirk Thomas Richter
2014-06-03 14:45 ` Daniel Vetter
2014-06-03 15:04 ` Thomas Richter
2014-06-03 15:14 ` Chris Wilson
2014-06-03 15:19 ` Thomas Richter
2014-06-03 15:26 ` Chris Wilson
2014-06-03 15:50 ` Thomas Richter
2014-06-03 16:03 ` Chris Wilson
[not found] ` <17205_1401811442_538DF1F2_17205_16362_1_20140603160352.GA6129@nuc-i3427.alporthouse.com>
2014-06-04 22:43 ` Bug: Pipe A underrun on resolution switching on 830MG Thomas Richter
2014-06-08 21:20 ` Thomas Richter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5394D395.8060802@math.tu-berlin.de \
--to=thor@math.tu-berlin.de \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=richter@rus.uni-stuttgart.de \
--cc=ville.syrjala@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox