From: "Paul Rolland" <rol@witbe.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: rol@witbe.net
Subject: [2.6.37-rc1] drm:i195 errors
Date: Tue, 2 Nov 2010 15:58:13 +0100 [thread overview]
Message-ID: <20101102155813.09cb2c6e@tux.DEF.witbe.net> (raw)
Hello,
I was previously running 2.6.36, without noticing any messages related to
i915/DRM, but now I can see some :
Nov 2 14:21:53 tux kernel: [drm:i915_gem_mmap_gtt_ioctl] *ERROR* Attempting to mmap a purgeable buffer
and also :
Nov 2 15:45:35 tux kernel: [drm:intel_panel_get_max_backlight] *ERROR* fixme: max PWM is zero.
They seem to appear randomly, without any (yet) identified link to some
activity I can have on the machine.
The lspci output is :
[root@tux ~]# lspci -s 00:02.0 -vvv
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller])
Subsystem: Dell Device 02bc
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 40
Region 0: Memory at f6800000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at 1800 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0100c Data: 4159
Capabilities: [d0] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: i915
Regards,
Paul
next reply other threads:[~2010-11-02 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 14:58 Paul Rolland [this message]
2010-11-09 20:26 ` [2.6.37-rc1] drm:i195 errors Maciej Rutecki
2010-11-10 13:59 ` njin
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=20101102155813.09cb2c6e@tux.DEF.witbe.net \
--to=rol@witbe.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.