Bug 46591 - Matrox g200 driver mgag200 hangs on HP ProLiant Gen8 Platform
Summary: Matrox g200 driver mgag200 hangs on HP ProLiant Gen8 Platform
Status: RESOLVED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(Other) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-28 19:38 UTC by Narinder Gupta
Modified: 2013-11-19 23:25 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.6-rc
Tree: Mainline
Regression: No


Attachments

Description Narinder Gupta 2012-08-28 19:38:10 UTC
HP ProLiant Gen8 System have ilo4 chip which contains the Matrox device. After enabling the mgag200 driver on the platform we are seeing this disconnect from video device. here is the lspci output for the MAtrox.

u@ML350Gen8:~$ lspci -s 01:00
01:00.0 System peripheral: Hewlett-Packard Company Integrated Lights-Out Standard Slave Instrumentation & System Support (rev 05)
01:00.1 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200EH
01:00.2 System peripheral: Hewlett-Packard Company Integrated Lights-Out Standard Management Processor Support and Messaging (rev 05)
01:00.4 USB controller: Hewlett-Packard Company Integrated Lights-Out Standard Virtual USB Controller (rev 02)
u@ML350Gen8:~$ lspci -s 01:00.1 -xxvv 
01:00.1 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200EH (prog-if 00 [VGA controller])
	Subsystem: Hewlett-Packard Company iLO4
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 5
	Region 0: Memory at f9000000 (32-bit, prefetchable) [size=16M]
	Region 1: Memory at fbde0000 (32-bit, non-prefetchable) [size=16K]
	Region 2: Memory at fb000000 (32-bit, non-prefetchable) [size=8M]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
00: 2b 10 33 05 47 00 10 00 00 00 00 03 10 00 80 00
10: 08 00 00 f9 00 00 de fb 00 00 00 fb 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 3c 10 81 33
30: 00 00 00 00 a8 00 00 00 00 00 00 00 05 02 00 00

u@ML350Gen8:~$
Comment 1 Alan 2012-08-28 22:10:20 UTC
Updating version ("latest kernel" becomes inaccurate rather fast)

Does the Matrox DRI/KMS driver work ?

Note You need to log in before you can comment on or make changes to this bug.