From: Mihai Moldovan <ionic@ionic.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Kernel BUG with i915 in intel_sdvo_ddc_proxy_func
Date: Tue, 17 May 2011 14:05:32 +0200 [thread overview]
Message-ID: <4DD2648C.6020309@ionic.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 3384 bytes --]
Hi,
I'm having trouble with an integrated i915 card, KMS and Linux >2.6.36.
The bug has been introduced somewhere between 2.6.36.1 (working) and
2.6.37 (bad) and is still happening on 2.6.38.6.
Kernel output (Images only, sorry):
http://ionic.de/gfx/Screenshots/Kernel/i915-BUG/Part1.jpg
http://ionic.de/gfx/Screenshots/Kernel/i915-BUG/Part2.jpg
http://ionic.de/gfx/Screenshots/Kernel/i915-BUG/Part3.jpg
http://ionic.de/gfx/Screenshots/Kernel/i915-BUG/Part4.jpg
lspci:
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller
(rev 03)
Subsystem: Intel Corporation Device 1003
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
Capabilities: [e0] Vendor Specific Information: Len=0c <?>
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
Subsystem: Intel Corporation Device 1003
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
Interrupt: pin A routed to IRQ 50
Region 0: Memory at e0000000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at f220 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0f00c Data: 41c1
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
00:02.1 Display controller: Intel Corporation 4 Series Chipset
Integrated Graphics Controller (rev 03)
Subsystem: Intel Corporation Device 1003
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
Region 0: Memory at e0400000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
PCI:IDs for those devices:
00:00.0 0600: 8086:2e10 (rev 03)
Subsystem: 8086:1003
00:02.0 0300: 8086:2e12 (rev 03) (prog-if 00 [VGA controller])
Subsystem: 8086:1003
00:02.1 0380: 8086:2e13 (rev 03)
Subsystem: 8086:1003
It only happens when I enable CONFIG_DRM_I915_KMS.
Also, as of 2.6.37, the video= Kernel parameter doesn't have any effect
anymore (set to video=1280x1024-24@75). It's working fine on 2.6.36.1.
Do you need anything else? Feel free to request additional information.
I'm looking forward to hearing from you.
Best regards,
Mihai
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 6111 bytes --]
next reply other threads:[~2011-05-17 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 12:05 Mihai Moldovan [this message]
2011-05-17 12:37 ` Kernel BUG with i915 in intel_sdvo_ddc_proxy_func Mihai Moldovan
2011-05-17 13:03 ` [PATCH] drm/i915/sdvo: Reorder i2c initialisation before ddc proxy Chris Wilson
2011-05-17 13:49 ` Mihai Moldovan
2011-05-18 1:22 ` Keith Packard
2011-05-18 8:04 ` Chris Wilson
2011-05-18 14:40 ` Keith Packard
2011-05-18 16:08 ` Mihai Moldovan
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=4DD2648C.6020309@ionic.de \
--to=ionic@ionic.de \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).