Radeon HD 6310 (AMD Wrestler): [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
Am 11.07.2013 09:41, schrieb Paul Menzel: > Dear Linux folks, > > > using a Linux 3.10 with the drm-next-3.11 tree from Alex Deuscher merged > and built with `make deb-pkg`, it failed the last boot. > > [drm:evergreen_startup] *ERROR* radeon: error initializing UVD (-1). > > The strange thing is that it worked the last time I tried with the same > Linux kernel image as I posted to the list [1]. I just booted an old > 3.2.46 distribution Linux in between. (And it looked like the > modesetting did not work when doing so. But I did not look further into > it.) The most likely problem is that you don't have the current firmware installed, beside the new UVD firmware you also need to update the RLC firmware. Christian. > > $ uname -a > Linux myhostname 3.10.0+ #105 SMP Sat Jul 6 13:33:47 CEST 2013 i686 > GNU/Linux > $ lspci -s 01.0 > 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. > [AMD/ATI] Wrestler [Radeon HD 6310] > $ md5sum /lib/firmware/3.10.0+/radeon/SUMO_uvd.bin > 51d9e0e2247c313c5bfc8fa7bb5b213d > /lib/firmware/3.10.0+/radeon/SUMO_uvd.bin > $ cut -d " " -f 6- /var/log/kern.log > [...] > [0.152534] calling trace_init_flags_sys_exit+0x0/0xd @ 1 > [0.152540] initcall trace_init_flags_sys_exit+0x0/0xd returned 0 > after 0 usecs > [0.152545] calling trace_init_flags_sys_enter+0x0/0xd @ 1 > [0.152550] initcall trace_init_flags_sys_enter+0x0/0xd returned > 0 after 0 usecs > [0.152555] calling init_hw_perf_events+0x0/0x47e @ 1 > [0.152557] Performance Events: AMD PMU driver. > [0.152565] ... version:0 > [0.152567] ... bit width: 48 > [0.152569] ... generic registers: 4 > [0.152572] ... value mask: > [0.152575] ... max period: 7fff > [0.152577] ... fixed-purpose events: 0 > [0.152580] ... event mask: 000f > [0.152597] initcall init_hw_perf_events+0x0/0x47e returned 0 > after 0 usecs > [0.152603] calling register_trigger_all_cpu_backtrace+0x0/0xf @ > 1 > [0.152609] initcall register_trigger_all_cpu_backtrace+0x0/0xf > returned 0 after 0 usecs > [0.152615] calling spawn_ksoftirqd+0x0/0x1d @ 1 > [0.152657] initcall spawn_ksoftirqd+0x0/0x1d returned 0 after 0 > usecs > [0.152662] calling init_workqueues+0x0/0x289 @ 1 > [0.152800] initcall init_workqueues+0x0/0x289 returned 0 after 0 > usecs > [0.152805] calling check_cpu_stall_init+0x0/0x12 @ 1 > [0.152810] initcall check_cpu_stall_init+0x0/0x12 returned 0 > after 0 usecs > [0.152814] calling migration_init+0x0/0x55 @ 1 > [0.152820] initcall migration_init+0x0/0x55 returned 0 after 0 > usecs > [0.152826] calling cpu_stop_init+0x0/0x57 @ 1 > [0.152863] initcall cpu_stop_init+0x0/0x57 returned 0 after 0 > usecs > [0.152868] calling rcu_register_oom_notifier+0x0/0xd @ 1 > [0.152874] initcall rcu_register_oom_notifier+0x0/0xd returned 0 > after 0 usecs > [0.152879] calling rcu_scheduler_really_started+0x0/0xd @ 1 > [0.152883] initcall rcu_scheduler_really_started+0x0/0xd > returned 0 after 0 usecs > [0.152888] calling rcu_spawn_gp_kthread+0x0/0x6b @ 1 > [0.152936] initcall rcu_spawn_gp_kthread+0x0/0x6b returned 0 > after 0 usecs > [0.152941] calling relay_init+0x0/0xd @ 1 > [0.152946] initcall relay_init+0x0/0xd returned 0 after 0 usecs > [0.152950] calling tracer_alloc_buffers+0x0/0x18b @ 1 > [0.153030] initcall tracer_alloc_buffers+0x0/0x18b returned 0 > after 0 usecs > [0.153034] calling init_events+0x0/0x57 @ 1 > [0.153041] initcall init_events+0x0/0x57 returned 0 after 0 usecs > [0.153046] calling init_trace_printk+0x0/0xa @ 1 > [0.153051] initcall init_trace_printk+0x0/0xa returned 0 after 0 > usecs > [0.153055] calling event_trace_memsetup+0x0/0x4a @ 1 > [0.153067] initcall event_trace_memsetup+0x0/0x4a returned 0 > after 0 usecs > [0.153158] NMI watchdog: enabled on all CPUs, permanently > consumes one hw-PMU counter. > [0.153361] CPU 1 irqstacks, hard=f40ae000 soft=f40b > [0.153365] smpboot: Booting Node 0, Processors #1 OK > [0.163398] Initializing CPU#1 > [0.166591] Brought up 2 CPUs > [0.166596] smpboot: Total of 2 processors activated (6399.62 > BogoMIPS) > [0.168897] devtmpfs: initialized > [0.169277] calling ipc_ns_init+0x0/0xd @ 1 > [0.169284]
Radeon HD 6310 (AMD Wrestler): [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
Dear Linux folks, using a Linux 3.10 with the drm-next-3.11 tree from Alex Deuscher merged and built with `make deb-pkg`, it failed the last boot. [drm:evergreen_startup] *ERROR* radeon: error initializing UVD (-1). The strange thing is that it worked the last time I tried with the same Linux kernel image as I posted to the list [1]. I just booted an old 3.2.46 distribution Linux in between. (And it looked like the modesetting did not work when doing so. But I did not look further into it.) $ uname -a Linux myhostname 3.10.0+ #105 SMP Sat Jul 6 13:33:47 CEST 2013 i686 GNU/Linux $ lspci -s 01.0 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] $ md5sum /lib/firmware/3.10.0+/radeon/SUMO_uvd.bin 51d9e0e2247c313c5bfc8fa7bb5b213d /lib/firmware/3.10.0+/radeon/SUMO_uvd.bin $ cut -d " " -f 6- /var/log/kern.log [?] [0.152534] calling trace_init_flags_sys_exit+0x0/0xd @ 1 [0.152540] initcall trace_init_flags_sys_exit+0x0/0xd returned 0 after 0 usecs [0.152545] calling trace_init_flags_sys_enter+0x0/0xd @ 1 [0.152550] initcall trace_init_flags_sys_enter+0x0/0xd returned 0 after 0 usecs [0.152555] calling init_hw_perf_events+0x0/0x47e @ 1 [0.152557] Performance Events: AMD PMU driver. [0.152565] ... version:0 [0.152567] ... bit width: 48 [0.152569] ... generic registers: 4 [0.152572] ... value mask: [0.152575] ... max period: 7fff [0.152577] ... fixed-purpose events: 0 [0.152580] ... event mask: 000f [0.152597] initcall init_hw_perf_events+0x0/0x47e returned 0 after 0 usecs [0.152603] calling register_trigger_all_cpu_backtrace+0x0/0xf @ 1 [0.152609] initcall register_trigger_all_cpu_backtrace+0x0/0xf returned 0 after 0 usecs [0.152615] calling spawn_ksoftirqd+0x0/0x1d @ 1 [0.152657] initcall spawn_ksoftirqd+0x0/0x1d returned 0 after 0 usecs [0.152662] calling init_workqueues+0x0/0x289 @ 1 [0.152800] initcall init_workqueues+0x0/0x289 returned 0 after 0 usecs [0.152805] calling check_cpu_stall_init+0x0/0x12 @ 1 [0.152810] initcall check_cpu_stall_init+0x0/0x12 returned 0 after 0 usecs [0.152814] calling migration_init+0x0/0x55 @ 1 [0.152820] initcall migration_init+0x0/0x55 returned 0 after 0 usecs [0.152826] calling cpu_stop_init+0x0/0x57 @ 1 [0.152863] initcall cpu_stop_init+0x0/0x57 returned 0 after 0 usecs [0.152868] calling rcu_register_oom_notifier+0x0/0xd @ 1 [0.152874] initcall rcu_register_oom_notifier+0x0/0xd returned 0 after 0 usecs [0.152879] calling rcu_scheduler_really_started+0x0/0xd @ 1 [0.152883] initcall rcu_scheduler_really_started+0x0/0xd returned 0 after 0 usecs [0.152888] calling rcu_spawn_gp_kthread+0x0/0x6b @ 1 [0.152936] initcall rcu_spawn_gp_kthread+0x0/0x6b returned 0 after 0 usecs [0.152941] calling relay_init+0x0/0xd @ 1 [0.152946] initcall relay_init+0x0/0xd returned 0 after 0 usecs [0.152950] calling tracer_alloc_buffers+0x0/0x18b @ 1 [0.153030] initcall tracer_alloc_buffers+0x0/0x18b returned 0 after 0 usecs [0.153034] calling init_events+0x0/0x57 @ 1 [0.153041] initcall init_events+0x0/0x57 returned 0 after 0 usecs [0.153046] calling init_trace_printk+0x0/0xa @ 1 [0.153051] initcall init_trace_printk+0x0/0xa returned 0 after 0 usecs [0.153055] calling event_trace_memsetup+0x0/0x4a @ 1 [0.153067] initcall event_trace_memsetup+0x0/0x4a returned 0 after 0 usecs [0.153158] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. [0.153361] CPU 1 irqstacks, hard=f40ae000 soft=f40b [0.153365] smpboot: Booting Node 0, Processors #1 OK [0.163398] Initializing CPU#1 [0.166591] Brought up 2 CPUs [0.166596] smpboot: Total of 2 processors activated (6399.62 BogoMIPS) [0.168897] devtmpfs: initialized [0.169277] calling ipc_ns_init+0x0/0xd @ 1 [0.169284] initcall ipc_ns_init+0x0/0xd returned 0 after 0 usecs [0.169289] calling init_mmap_min_addr+0x0/0xd @ 1 [0.169294] initcall init_mmap_min_addr+0x0/0xd returned 0 after 0 usecs [0.169302] calling init_cpufreq_transition_notifier_list+0x0/0x14 @ 1 [0.169315] initcall init_cpufreq_transition_notifier_list+0x0/0x14 returned 0 after 0 usecs [0.169320] calling net_ns_init+0x0/0xca @ 1 [
Radeon HD 6310 (AMD Wrestler): [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
On Thu, Jul 11, 2013 at 3:41 AM, Paul Menzel wrote: > Dear Linux folks, > > > using a Linux 3.10 with the drm-next-3.11 tree from Alex Deuscher merged > and built with `make deb-pkg`, it failed the last boot. > > [drm:evergreen_startup] *ERROR* radeon: error initializing UVD (-1). > > The strange thing is that it worked the last time I tried with the same > Linux kernel image as I posted to the list [1]. I just booted an old > 3.2.46 distribution Linux in between. (And it looked like the > modesetting did not work when doing so. But I did not look further into > it.) Make sure you have the updated rlc and uvd ucode installed and that the correct ucode is being used in your initrd, etc. Alex
Re: Radeon HD 6310 (AMD Wrestler): [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
On Thu, Jul 11, 2013 at 3:41 AM, Paul Menzel paulepan...@users.sourceforge.net wrote: Dear Linux folks, using a Linux 3.10 with the drm-next-3.11 tree from Alex Deuscher merged and built with `make deb-pkg`, it failed the last boot. [drm:evergreen_startup] *ERROR* radeon: error initializing UVD (-1). The strange thing is that it worked the last time I tried with the same Linux kernel image as I posted to the list [1]. I just booted an old 3.2.46 distribution Linux in between. (And it looked like the modesetting did not work when doing so. But I did not look further into it.) Make sure you have the updated rlc and uvd ucode installed and that the correct ucode is being used in your initrd, etc. Alex ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
