Bug 87553 - system boot hangs at drm initialization
Summary: system boot hangs at drm initialization
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-21 14:16 UTC by d.lecardez
Modified: 2019-11-19 08:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
full /var/log/messages (245.24 KB, text/plain)
2014-12-21 14:33 UTC, d.lecardez
no flags Details

Description d.lecardez 2014-12-21 14:16:53 UTC

    
Comment 1 d.lecardez 2014-12-21 14:33:20 UTC
Created attachment 111108 [details]
full /var/log/messages
Comment 2 d.lecardez 2014-12-21 14:36:08 UTC
HP Laptop hp dv6 with ATI Mobility Radeon HD 5000 Series

When I boot fc21, 90% of the times, it hangs at screen mmessage:

[drm] Loading REDWOOD microcode

For the remaining 10% everything works fine.

This sympthom appeared in fc19 starting with kernels 3.10.X and has always been present in fc20 inany versions.

One of the workaround is to boot in 'nomodeset' then manualy perform a 'modprobe radeon modeset=1'

Full trace as attachment.

Most of the time this solves the problem, but sometimes it also fails.
In this situation, as I'm already booted, I can get traces in /var/log/messages
ThiDec 19 20:05:19 localhost kernel: [  153.615554] Call Trace:
Dec 19 20:05:19 localhost kernel: [  153.615799]  [<f9e7312e>] ? radeon_ring_lock+0x2e/0x50 [radeon]
Dec 19 20:05:19 localhost kernel: [  153.616047]  [<f9f1f66e>] uvd_v1_0_ring_test+0x4e/0x150 [radeon]
Dec 19 20:05:19 localhost kernel: [  153.616272]  [<c06e258e>] ? __const_udelay+0x1e/0x20
Dec 19 20:05:19 localhost kernel: [  153.616520]  [<f9f1f21a>] ? uvd_v1_0_start+0x1ea/0x380 [radeon]
Dec 19 20:05:19 localhost kernel: [  153.616770]  [<f9f1f44a>] uvd_v1_0_init+0x9a/0x190 [radeon]
Dec 19 20:05:19 localhost kernel: [  153.617024]  [<f9eb385e>] evergreen_startup+0x1b0e/0x1b20 [radeon]
Dec 19 20:05:19 localhost kernel: [  153.617278]  [<f9eb3ad5>] evergreen_init+0x1c5/0x370 [radeon]
Dec 19 20:05:19 localhost kernel: [  153.617525]  [<f9e42184>] radeon_device_init+0x924/0xaf0 [radeon]
Dec 19 20:05:19 localhost kernel: [  153.617769]  [<f9e40400>] ? cail_mc_write+0x20/0x20 [radeon]
Dec 19 20:05:19 localhost kernel: [  153.618010]  [<f9e4468a>] radeon_driver_load_kms+0x8a/0x1f0 [radeon]
Dec 19 20:05:19 localhost kernel: [  153.618359]  [<f7ce377e>] drm_dev_register+0x8e/0xd0 [drm]
Dec 19 20:05:19 localhost kernel: [  153.618599]  [<f7ce60c9>] drm_get_pci_dev+0x79/0x1c0 [drm]
Dec 19 20:05:19 localhost kernel: [  153.618821]  [<c05793e5>] ? kmem_cache_alloc_trace+0x195/0x1c0
Dec 19 20:05:19 localhost kernel: [  153.619068]  [<f9e4034e>] ? radeon_pci_probe+0x6e/0xa0 [radeon]
Dec 19 20:05:19 localhost kernel: [  153.619309]  [<f9e4035c>] radeon_pci_probe+0x7c/0xa0 [radeon]
Dec 19 20:05:19 localhost kernel: [  153.619533]  [<c07177ff>] pci_device_probe+0x6f/0xd0
Dec 19 20:05:19 localhost kernel: [  153.619755]  [<c05f3195>] ? sysfs_create_link+0x25/0x50
Dec 19 20:05:19 localhost kernel: [  153.619975]  [<c07cfbe3>] driver_probe_device+0x93/0x3b0
Dec 19 20:05:19 localhost kernel: [  153.620198]  [<c05f2ea7>] ? sysfs_create_dir_ns+0x37/0x90
Dec 19 20:05:19 localhost kernel: [  153.620421]  [<c0717741>] ? pci_match_device+0xc1/0xe0
Dec 19 20:05:19 localhost kernel: [  153.620638]  [<c07cffb9>] __driver_attach+0x79/0x80
Dec 19 20:05:19 localhost kernel: [  153.620859]  [<c07cff40>] ? __device_attach+0x40/0x40
Dec 19 20:05:19 localhost kernel: [  153.621075]  [<c07cde57>] bus_for_each_dev+0x57/0xa0
Dec 19 20:05:19 localhost kernel: [  153.621322]  [<c07cf6ee>] driver_attach+0x1e/0x20
Dec 19 20:05:19 localhost kernel: [  153.621548]  [<c07cff40>] ? __device_attach+0x40/0x40
Dec 19 20:05:19 localhost kernel: [  153.621769]  [<c07cf337>] bus_add_driver+0x167/0x240
Dec 19 20:05:19 localhost kernel: [  153.621990]  [<f9f92000>] ? 0xf9f92000
Dec 19 20:05:19 localhost kernel: [  153.622210]  [<f9f92000>] ? 0xf9f92000
Dec 19 20:05:19 localhost kernel: [  153.622428]  [<c07d06cd>] driver_register+0x5d/0xf0
Dec 19 20:05:19 localhost kernel: [  153.622650]  [<c0716063>] __pci_register_driver+0x33/0x40
Dec 19 20:05:19 localhost kernel: [  153.622879]  [<f7ce62fd>] drm_pci_init+0xed/0x110 [drm]
Dec 19 20:05:19 localhost kernel: [  153.623100]  [<f9f92000>] ? 0xf9f92000
Dec 19 20:05:19 localhost kernel: [  153.623338]  [<f9f9208d>] radeon_init+0x8d/0xa8 [radeon]
Dec 19 20:05:19 localhost kernel: [  153.623555]  [<c0400496>] do_one_initcall+0xc6/0x200
Dec 19 20:05:19 localhost kernel: [  153.623778]  [<f9f92000>] ? 0xf9f92000
Dec 19 20:05:19 localhost kernel: [  153.623996]  [<c0564928>] ? lazy_max_pages+0x18/0x30
Dec 19 20:05:19 localhost kernel: [  153.624321]  [<c0566895>] ? __vunmap+0xa5/0xf0
Dec 19 20:05:19 localhost kernel: [  153.624553]  [<c0566895>] ? __vunmap+0xa5/0xf0
Dec 19 20:05:19 localhost kernel: [  153.624773]  [<c04caa2b>] load_module+0x1ebb/0x23f0
Dec 19 20:05:19 localhost kernel: [  153.624997]  [<c04cb00f>] SyS_init_module+0xaf/0x120
Dec 19 20:05:19 localhost kernel: [  153.625222]  [<c0a45c1f>] sysenter_do_call+0x12/0x12
Dec 19 20:05:19 localhost kernel: [  153.630317] Code: 90 66 90 66 90 90 55 89 e5 56 53 83 ec 0c 66 66 66 66 90 89 c3 8b 40 2c 85 c0 7e 2a 8b 43 1c 8b 4b 04 8d 70 01 8d 04 81 89 73 1c <89> 10 8b 43 4c 83 6b 2c 01 21 43 1c 83 6b 28 01 83 c4 0c 5b 5e
Dec 19 20:05:19 localhost kernel: [  153.638171] EIP: [<f9e72ce5>] radeon_ring_write+0x25/0x60 [radeon] SS:ESP 0068:f3ba5b50
Dec 19 20:05:19 localhost kernel: [  153.638744] CR2: 00000000ff846000
Dec 19 20:05:19 localhost kernel: [  153.638959] ---[ end trace 4f07e3ff097194e7 ]---
s is a kernel stack  extract of what happens after performing 'modprobe'
Comment 3 d.lecardez 2015-05-27 19:54:21 UTC
Just installed fedora 4.0.4-301.fc22 and I'm still getting the same problem.
Tried 64 bits version ---> same
Comment 4 Martin Peres 2019-11-19 08:59:09 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/562.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.