From: Thomas Richter <thor@math.tu-berlin.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: intel-drm-nightly: hang and black screen on i830
Date: Thu, 19 Dec 2013 15:01:56 +0100 [thread overview]
Message-ID: <52B2FC54.6090209@math.tu-berlin.de> (raw)
In-Reply-To: <26487_1385411456_5293B380_26487_2367_1_CAKMK7uFFZcf92XbzA9Mj2c0fdhDWZMKkZVNK9yy8Shc8pcLygg@mail.gmail.com>
Hi Daniel, hi folks,
back from a couple of business trips, so finally some time to look into
the i830 support on this old laptop.
Sorry to say that the current drm-nightly does not work at all. It just
generates a hang, resulting in a black screen and nothing else. All you
can do there is to turn the machine off the hard way.
Here is what I get in the kernel log: Probably
intel_modeset_setup_hw_state hangs? Hard to say.
Dec 19 14:38:50 tyleet kernel: [ 240.296074] INFO: task modprobe:439
blocked for more than 120 seconds.
Dec 19 14:38:50 tyleet kernel: [ 240.296091] Not tainted
3.13.0-rc3+ #2
Dec 19 14:38:50 tyleet kernel: [ 240.296097] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 19 14:38:50 tyleet kernel: [ 240.296104] modprobe D
f6145bc0 0 439 375 0x00000004
Dec 19 14:38:50 tyleet kernel: [ 240.296117] f60b0360 00000082
c1302256 f6145bc0 f6145ba6 00000002 00000000 f60b0360
Dec 19 14:38:50 tyleet kernel: [ 240.296132] f84c3771 f84c3771
f84c73a3 f84c73a4 c11803c1 00000001 00000000 c103ff02
Dec 19 14:38:50 tyleet kernel: [ 240.296147] 00004e0a f061ffff
f84affff f84c376e 00000000 f84c73a3 02145b48 f84c73c0
Dec 19 14:38:50 tyleet kernel: [ 240.296161] Call Trace:
Dec 19 14:38:50 tyleet kernel: [ 240.296181] [<c1302256>] ?
__schedule+0x166/0x410
Dec 19 14:38:50 tyleet kernel: [ 240.296218] [<c11803c1>] ?
vsnprintf+0xd1/0x5c0
Dec 19 14:38:50 tyleet kernel: [ 240.296233] [<c103ff02>] ?
do_sigaction+0x62/0x160
Dec 19 14:38:50 tyleet kernel: [ 240.296268] [<f84affff>] ?
drm_mode_gamma_get_ioctl+0xbf/0xe0 [drm]
Dec 19 14:38:50 tyleet kernel: [ 240.296285] [<c13026a5>] ?
schedule_preempt_disabled+0x5/0x10
Dec 19 14:38:50 tyleet kernel: [ 240.296296] [<c13035bb>] ?
__mutex_lock_slowpath+0x4b/0x7a
Dec 19 14:38:50 tyleet kernel: [ 240.296306] [<c1303123>] ?
mutex_lock+0x13/0x15
Dec 19 14:38:50 tyleet kernel: [ 240.296422] [<f8dc5b12>] ?
intel_get_load_detect_pipe+0x152/0x3e0 [i915]
Dec 19 14:38:50 tyleet kernel: [ 240.296515] [<f8de59a4>] ?
intel_update_watermarks+0x14/0x20 [i915]
Dec 19 14:38:50 tyleet kernel: [ 240.296585] [<f8dba9ee>] ?
i9xx_crtc_disable+0x19e/0x2f0 [i915]
Dec 19 14:38:50 tyleet kernel: [ 240.296658] [<f8dc79ef>] ?
intel_modeset_setup_hw_state+0xadf/0xb90 [i915]
Dec 19 14:38:50 tyleet kernel: [ 240.296676] [<c1300001>] ?
remove_waiter+0x9d/0xd3
Dec 19 14:38:50 tyleet kernel: [ 240.296759] [<f8df6d00>] ?
gen4_write16+0x20/0x20 [i915]
Dec 19 14:38:50 tyleet kernel: [ 240.296817] [<f8d92b40>] ?
i915_semaphore_is_enabled+0x50/0x50 [i915]
Dec 19 14:38:50 tyleet kernel: [ 240.296888] [<f8dc7ac6>] ?
intel_modeset_gem_init+0x26/0x30 [i915]
Dec 19 14:38:50 tyleet kernel: [ 240.296947] [<f8d95dea>] ?
i915_driver_load+0xcca/0xe60 [i915]
Dec 19 14:38:50 tyleet kernel: [ 240.297004] [<f8d932d0>] ?
i915_dma_init+0x2e0/0x2e0 [i915]
Dec 19 14:38:50 tyleet kernel: [ 240.297034] [<c1213709>] ?
device_add+0x159/0x510
Dec 19 14:38:50 tyleet kernel: [ 240.297071] [<f84a5f63>] ?
drm_dev_register+0x83/0x1b0 [drm]
Dec 19 14:38:50 tyleet kernel: [ 240.297095] [<f84a7b88>] ?
drm_get_pci_dev+0x88/0x140 [drm]
Dec 19 14:38:50 tyleet kernel: [ 240.297113] [<c111cf59>] ?
sysfs_do_create_link_sd.isra.5+0x99/0x1b0
Dec 19 14:38:50 tyleet kernel: [ 240.297126] [<c11a17ef>] ?
pci_device_probe+0x7f/0xd0
Dec 19 14:38:50 tyleet kernel: [ 240.297138] [<c1215e30>] ?
driver_probe_device+0x1f0/0x1f0
Dec 19 14:38:50 tyleet kernel: [ 240.297148] [<c111d08d>] ?
sysfs_create_link+0x1d/0x40
Dec 19 14:38:50 tyleet kernel: [ 240.297159] [<c1215e30>] ?
driver_probe_device+0x1f0/0x1f0
Dec 19 14:38:50 tyleet kernel: [ 240.297169] [<c1215c93>] ?
driver_probe_device+0x53/0x1f0
Dec 19 14:38:50 tyleet kernel: [ 240.297180] [<c1179ed8>] ?
kobject_add_internal+0x158/0x210
Dec 19 14:38:50 tyleet kernel: [ 240.297191] [<c1215ea9>] ?
__driver_attach+0x79/0x80
Dec 19 14:38:50 tyleet kernel: [ 240.297204] [<c1214698>] ?
bus_for_each_dev+0x38/0x70
Dec 19 14:38:50 tyleet kernel: [ 240.297214] [<c1215876>] ?
driver_attach+0x16/0x20
Dec 19 14:38:50 tyleet kernel: [ 240.297223] [<c1215e30>] ?
driver_probe_device+0x1f0/0x1f0
Dec 19 14:38:50 tyleet kernel: [ 240.297232] [<c1215521>] ?
bus_add_driver+0xe1/0x1e0
Dec 19 14:38:50 tyleet kernel: [ 240.297244] [<c1216401>] ?
driver_register+0x51/0xd0
Dec 19 14:38:50 tyleet kernel: [ 240.297266] [<f8e2d000>] ? 0xf8e2cfff
Dec 19 14:38:50 tyleet kernel: [ 240.297277] [<f8e2d000>] ? 0xf8e2cfff
Dec 19 14:38:50 tyleet kernel: [ 240.297287] [<c1000462>] ?
do_one_initcall+0xe2/0x130
Dec 19 14:38:50 tyleet kernel: [ 240.297297] [<c1303118>] ?
mutex_lock+0x8/0x15
Dec 19 14:38:50 tyleet kernel: [ 240.297308] [<c1093a55>] ?
jump_label_module_notify+0x155/0x1a0
Dec 19 14:38:50 tyleet kernel: [ 240.297322] [<c104e890>] ?
notifier_call_chain+0x40/0x60
Dec 19 14:38:50 tyleet kernel: [ 240.297335] [<c104eadb>] ?
__blocking_notifier_call_chain+0x4b/0x70
Dec 19 14:38:50 tyleet kernel: [ 240.297348] [<c107c988>] ?
load_module+0x1a18/0x2160
Dec 19 14:38:50 tyleet kernel: [ 240.297369] [<c102d920>] ?
vmalloc_sync_all+0xd0/0xd0
Dec 19 14:38:50 tyleet kernel: [ 240.297381] [<c107d161>] ?
SyS_init_module+0x91/0xd0
Dec 19 14:38:50 tyleet kernel: [ 240.297403] [<c130489e>] ?
sysenter_do_call+0x12/0x26
Dec 19 14:38:50 tyleet kernel: [ 240.297412] INFO: task modprobe:449
blocked for more than 120 seconds.
Dec 19 14:38:50 tyleet kernel: [ 240.297419] Not tainted
3.13.0-rc3+ #2
Dec 19 14:38:50 tyleet kernel: [ 240.297425] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 19 14:38:50 tyleet kernel: [ 240.297430] modprobe D
f6831c40 0 449 393 0x00000004
Dec 19 14:38:50 tyleet kernel: [ 240.297441] f61c0d80 00000086
c111bd5a f6831c40 f627e600 f627e600 c111c3ce f61c0d80
Dec 19 14:38:50 tyleet kernel: [ 240.297456] c111c2d6 f627e600
00000001 f609ca40 c111c553 f627e600 f6831c40 f627e600
Dec 19 14:38:50 tyleet kernel: [ 240.297470] f627e600 00000000
f6831c40 f62faea0 c111c653 00000000 f62faea0 00000000
Dec 19 14:38:50 tyleet kernel: [ 240.297484] Call Trace:
Dec 19 14:38:50 tyleet kernel: [ 240.297496] [<c111bd5a>] ?
sysfs_link_sibling+0x6a/0xb0
Dec 19 14:38:50 tyleet kernel: [ 240.297506] [<c111c3ce>] ?
__sysfs_add_one+0x4e/0xf0
Dec 19 14:38:50 tyleet kernel: [ 240.297516] [<c111c2d6>] ?
sysfs_new_dirent+0x46/0xe0
Dec 19 14:38:50 tyleet kernel: [ 240.297526] [<c111c553>] ?
sysfs_addrm_finish+0x13/0xb0
Dec 19 14:38:50 tyleet kernel: [ 240.297536] [<c111c653>] ?
create_dir+0x63/0xa0
Dec 19 14:38:50 tyleet kernel: [ 240.297546] [<c13026a5>] ?
schedule_preempt_disabled+0x5/0x10
Dec 19 14:38:50 tyleet kernel: [ 240.297556] [<c13035bb>] ?
__mutex_lock_slowpath+0x4b/0x7a
Dec 19 14:38:50 tyleet kernel: [ 240.297567] [<c1215e30>] ?
driver_probe_device+0x1f0/0x1f0
Dec 19 14:38:50 tyleet kernel: [ 240.297577] [<c1303123>] ?
mutex_lock+0x13/0x15
Dec 19 14:38:50 tyleet kernel: [ 240.297586] [<c1215e76>] ?
__driver_attach+0x46/0x80
Dec 19 14:38:50 tyleet kernel: [ 240.297598] [<c1214698>] ?
bus_for_each_dev+0x38/0x70
Dec 19 14:38:50 tyleet kernel: [ 240.297608] [<c1215876>] ?
driver_attach+0x16/0x20
Dec 19 14:38:50 tyleet kernel: [ 240.297617] [<c1215e30>] ?
driver_probe_device+0x1f0/0x1f0
Dec 19 14:38:50 tyleet kernel: [ 240.297626] [<c1215521>] ?
bus_add_driver+0xe1/0x1e0
Dec 19 14:38:50 tyleet kernel: [ 240.297638] [<c1216401>] ?
driver_register+0x51/0xd0
Dec 19 14:38:50 tyleet kernel: [ 240.297649] [<f8070000>] ? 0xf806ffff
Dec 19 14:38:50 tyleet kernel: [ 240.297659] [<c1000462>] ?
do_one_initcall+0xe2/0x130
Dec 19 14:38:50 tyleet kernel: [ 240.297668] [<c1303118>] ?
mutex_lock+0x8/0x15
Dec 19 14:38:50 tyleet kernel: [ 240.297678] [<c1093a55>] ?
jump_label_module_notify+0x155/0x1a0
Dec 19 14:38:50 tyleet kernel: [ 240.297689] [<c104e890>] ?
notifier_call_chain+0x40/0x60
Dec 19 14:38:50 tyleet kernel: [ 240.297702] [<c104eadb>] ?
__blocking_notifier_call_chain+0x4b/0x70
Dec 19 14:38:50 tyleet kernel: [ 240.297713] [<c107c988>] ?
load_module+0x1a18/0x2160
Dec 19 14:38:50 tyleet kernel: [ 240.297730] [<c102d920>] ?
vmalloc_sync_all+0xd0/0xd0
Dec 19 14:38:50 tyleet kernel: [ 240.297741] [<c107d161>] ?
SyS_init_module+0x91/0xd0
Dec 19 14:38:50 tyleet kernel: [ 240.297761] [<c130489e>] ?
sysenter_do_call+0x12/0x26
Greetings,
Thomas
prev parent reply other threads:[~2013-12-19 14:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1385093524-22276-1-git-send-email-keithp@keithp.com>
[not found] ` <20131122102632.GQ27344@phenom.ffwll.local>
[not found] ` <86d2lsem3m.fsf@miki.keithp.com>
2013-11-22 16:17 ` [Mesa-dev] [PATCH] dri3, i915, i965: Add __DRI_IMAGE_FOURCC_SARGB8888 Daniel Vetter
2013-11-22 17:46 ` Ville Syrjälä
2013-11-22 22:12 ` [Intel-gfx] " Kristian Høgsberg
2013-11-22 23:05 ` Ville Syrjälä
2013-11-22 23:43 ` Keith Packard
2013-11-23 1:10 ` Ville Syrjälä
2013-11-25 14:57 ` Geert Uytterhoeven
2013-11-22 23:36 ` [Intel-gfx] " Keith Packard
2013-11-25 8:57 ` [Mesa-dev] " Daniel Vetter
2013-11-25 14:15 ` Ville Syrjälä
[not found] ` <16967_1385369810_529310D2_16967_15891_1_20131125085723.GW27344@phenom.ffwll.local>
2013-11-25 15:14 ` i830 watermark problems - status? Thomas Richter
2013-11-25 15:23 ` Daniel Vetter
[not found] ` <26487_1385392973_52936B4D_26487_126_1_20131125152331.GB27344@phenom.ffwll.local>
2013-11-25 15:55 ` Thomas Richter
2013-11-25 20:30 ` Daniel Vetter
[not found] ` <26487_1385411456_5293B380_26487_2367_1_CAKMK7uFFZcf92XbzA9Mj2c0fdhDWZMKkZVNK9yy8Shc8pcLygg@mail.gmail.com>
2013-11-30 20:11 ` Thomas Richter
2013-12-19 14:01 ` 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=52B2FC54.6090209@math.tu-berlin.de \
--to=thor@math.tu-berlin.de \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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