Bug 709784

Summary:	kernel-rt-2.6.33.9-rt31-66.el6rt gives error with some ATI Radeon GPUs
Product:	Red Hat Enterprise MRG	Reporter:	David Sommerseth <davids>
Component:	realtime-kernel	Assignee:	Red Hat Real Time Maintenance <rt-maint>
Status:	CLOSED WONTFIX	QA Contact:	David Sommerseth <davids>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	bhu, lgoncalv, ovasik, williams
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-25 20:04:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description David Sommerseth 2011-06-01 15:55:11 UTC

When booting MRG RT kernel on RHEL 6.1 with MRG 2.0, it produces the following failure on some boxes which have ATI Radeon video cards.

------------------------------------------------------------------
[drm] Initialized drm 1.1.0 20060810 
[drm] radeon defaulting to kernel modesetting. 
[drm] radeon kernel modesetting enabled. 
radeon 0000:00:05.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 
[drm] radeon: Initializing kernel modesetting. 
[drm] register mmio base: 0xF3FE0000 
[drm] register mmio size: 65536 
[drm] GPU reset succeed (RBBM_STATUS=0x00000140) 
[drm] radeon: VRAM 64M 
[drm] radeon: VRAM from 0x00000000 to 0x03FFFFFF 
[drm] radeon: GTT 512M 
[drm] radeon: GTT from 0x20000000 to 0x3FFFFFFF 
[drm] radeon: irq initialized. 
[drm] Detected VRAM RAM=64M, BAR=128M 
[drm] RAM width 16bits DDR 
[TTM] Zone  kernel: Available graphics memory: 4131042 kiB. 
[TTM] Zone   dma32: Available graphics memory: 2097152 kiB. 
[drm] radeon: 16M of VRAM memory ready 
[drm] radeon: 512M of GTT memory ready. 
[drm] GART: num cpu pages 131072, num gpu pages 131072 
[drm] radeon: cp idle (0x00008080) 
[drm] Loading R100 Microcode 
platform radeon_cp.0: firmware: requesting radeon/R100_cp.bin 
[drm] radeon: ring at 0x0000000020000000 
[drm] ring test succeeded in 2 usecs 
[drm] radeon: ib pool ready. 
[drm] ib test succeeded in 0 usecs 
[drm] No valid Ext TMDS info found in BIOS 
[drm] Radeon Display Connectors 
[drm] Connector 0: 
[drm]   VGA 
[drm]   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 
[drm]   Encoders: 
[drm]     CRT1: INTERNAL_DAC1 
[drm] Connector 1: 
[drm]   DVI-D 
[drm]   HPD2 
[drm]   DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 
[drm]   Encoders: 
[drm]     DFP2: INTERNAL_DVO1 
[drm] fb mappable at 0xE8040000 
[drm] vram apper at 0xE8000000 
[drm] size 786432 
[drm] fb depth is 8 
[drm]    pitch is 1024 
[drm:radeon_i2c_sw_put_byte] *ERROR* i2c 0x08 0x30 write failed 
[drm:radeon_i2c_sw_put_byte] *ERROR* i2c 0x09 0x00 write failed 
BUG: work_for_cpu:762 RT task yield()-ing! 
Pid: 762, comm: work_for_cpu Not tainted 2.6.33.9-rt31.66.el6rt.x86_64 #1 
Call Trace: 
 [<ffffffff8135c633>] yield+0x4b/0x52 
 [<ffffffffa002b50d>] try_address+0x5c/0x7b [i2c_algo_bit] 
 [<ffffffffa002b6d4>] bit_xfer+0x1a8/0x3f7 [i2c_algo_bit] 
 [<ffffffffa001e5aa>] i2c_transfer+0x8a/0xc9 [i2c_core] 
 [<ffffffffa00bff2c>] radeon_i2c_sw_put_byte+0x45/0x6e [radeon] 
 [<ffffffffa00acdbb>] radeon_external_tmds_setup+0x74/0xaf [radeon] 
 [<ffffffffa00b7376>] radeon_legacy_tmds_ext_mode_set+0x147/0x24e [radeon] 
 [<ffffffffa007034c>] drm_crtc_helper_set_mode+0x29d/0x364 [drm_kms_helper] 
 [<ffffffffa0070ed3>] drm_crtc_helper_set_config+0x59b/0x778 [drm_kms_helper] 
 [<ffffffff810f0fc4>] ? __kmalloc+0x120/0x132 
 [<ffffffff811df201>] ? get_default_font+0x85/0x95 
 [<ffffffffa006e796>] drm_fb_helper_pan_display+0xa4/0xfc [drm_kms_helper] 
 [<ffffffff811d0e75>] fb_pan_display+0xbc/0xfd 
 [<ffffffff811de764>] bit_update_start+0x20/0x43 
 [<ffffffff811dbba6>] fbcon_switch+0x40e/0x413 
 [<ffffffff8122dcd2>] redraw_screen+0xce/0x182 
 [<ffffffff8123084b>] vc_do_resize+0x341/0x361 
 [<ffffffff812308d8>] vc_resize+0x1f/0x21 
 [<ffffffff811ddaa6>] fbcon_init+0x34f/0x3fe 
 [<ffffffff8122c092>] visual_init+0x9f/0xde 
 [<ffffffff8122df0b>] bind_con_driver+0x185/0x2b6 
 [<ffffffff8122e078>] take_over_console+0x3c/0x4a 
 [<ffffffff811dd1f1>] fbcon_takeover+0x5c/0x96 
 [<ffffffff811de11b>] fbcon_event_notify+0x223/0x4d8 
 [<ffffffff813607dc>] notifier_call_chain+0x32/0x5e 
 [<ffffffff81062619>] __blocking_notifier_call_chain+0x50/0x67 
 [<ffffffff81062644>] blocking_notifier_call_chain+0x14/0x16 
 [<ffffffff811d0b57>] fb_notifier_call_chain+0x1b/0x1d 
 [<ffffffff811d26cf>] register_framebuffer+0x29c/0x2b5 
 [<ffffffffa006ec78>] drm_fb_helper_single_fb_probe+0x38e/0x439 [drm_kms_helper] 
 [<ffffffffa00c1463>] radeonfb_probe+0x49/0x4b [radeon] 
 [<ffffffffa0071617>] drm_helper_initial_config+0x57/0x5d [drm_kms_helper] 
 [<ffffffffa00bf040>] radeon_modeset_init+0x6ad/0x6e5 [radeon] 
 [<ffffffffa00cc234>] ? r100_init+0x1f7/0x264 [radeon] 
 [<ffffffffa00a726d>] radeon_driver_load_kms+0x16c/0x1bb [radeon] 
 [<ffffffffa003b277>] drm_get_dev+0x3ba/0x4c6 [drm] 
 [<ffffffff81059d67>] ? do_work_for_cpu+0x0/0x2a 
 [<ffffffffa00eed5c>] radeon_pci_probe+0x15/0x269 [radeon] 
 [<ffffffff811c4c59>] local_pci_probe+0x17/0x1b 
 [<ffffffff81059d7f>] do_work_for_cpu+0x18/0x2a 
 [<ffffffff8105d619>] kthread+0x7f/0x87 
 [<ffffffff81003a54>] kernel_thread_helper+0x4/0x10 
 [<ffffffff8105d59a>] ? kthread+0x0/0x87 
 [<ffffffff81003a50>] ? kernel_thread_helper+0x0/0x10 
[drm:radeon_i2c_sw_put_byte] *ERROR* i2c 0x0a 0x90 write failed 
[drm:radeon_i2c_sw_put_byte] *ERROR* i2c 0x0c 0x89 write failed 
[drm:radeon_i2c_sw_put_byte] *ERROR* i2c 0x08 0x3b write failed 
------------------------------------------------------------------

When adding radeon.hw_i2c=0 to the kernel command line, these issues disappears.

It might be that some boxes will experience a non-working console when this happens.

Comment 4 Beth Uptagrafft 2014-09-25 20:04:04 UTC

This issue has not been updated in a while and is against an older, unsupported kernel. This BZ is being closed WONTFIX.  If you believe this is still an issue on our most recent MRG-2.5 3.10 Realtime kernel, please file a new issue for further investigation.