FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 10-07-2012, 10:31 AM
Javier Cantero
 
Default Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze

Sorry, I didn't receive the last 2 msgs in my mailbox, (especifically the
questions Ingo asks me). Here the answers:

a) Yes, I am using iceweasel.
b) my phisical RAM is 8 GB

The related kernel info is below, first kernel 3.5 related and then
standard wheezy 3.2 kernel related. Note that with kernel 3.5 I don't
have the "MTRR allocation failed" error.

My integrated graphics BIOS configuration:

Virtu Technology [Disabled]
Integrated Graphics Share Memory [64MB]
DVMT Memory [256MB]
IGD Multimonitor [Disabled]


--------------
Kernel 3.5
--------------

$ dmesg | grep mtrr
$

$ dmesg | grep drm
[ 3.749099] [drm] Initialized drm 1.1.0 20060810
[ 3.947156] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 3.947156] [drm] Driver supports precise vblank timestamp query.
[ 4.004585] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[ 4.373533] fbcon: inteldrmfb (fb0) is primary device
[ 4.554815] fb0: inteldrmfb frame buffer device
[ 4.554817] drm: registered panic notifier
[ 4.555909] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

$ dmesg | grep i915
[ 3.690617] i915 0000:00:02.0: setting latency timer to 64
[ 3.707470] i915 0000:00:02.0: irq 43 for MSI/MSI-X
[ 4.328751] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

$ dmesg | grep agp
[ 0.459118] Linux agpgart interface v0.103
[ 0.459169] agpgart-intel 0000:00:00.0: Intel Ivybridge Chipset
[ 0.459210] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
[ 0.459842] agpgart-intel 0000:00:00.0: detected 65536K stolen memory
[ 0.459931] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000


The memory info:

$ cat /proc/mtrr
reg00: base=0x000000000 ( 0MB), size= 8192MB, count=1: write-back
reg01: base=0x200000000 ( 8192MB), size= 512MB, count=1: write-back
reg02: base=0x0e0000000 ( 3584MB), size= 512MB, count=1: uncachable
reg03: base=0x0dc000000 ( 3520MB), size= 64MB, count=1: uncachable
reg04: base=0x0db800000 ( 3512MB), size= 8MB, count=1: uncachable
reg05: base=0x21f800000 ( 8696MB), size= 8MB, count=1: uncachable
reg06: base=0x21f600000 ( 8694MB), size= 2MB, count=1: uncachable

$ cat /proc/meminfo
MemTotal: 8081148 kB
MemFree: 7392304 kB
Buffers: 14852 kB
Cached: 280924 kB
SwapCached: 0 kB
Active: 395024 kB
Inactive: 214096 kB
Active(anon): 313884 kB
Inactive(anon): 42596 kB
Active(file): 81140 kB
Inactive(file): 171500 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 7811068 kB
SwapFree: 7811068 kB
Dirty: 12 kB
Writeback: 0 kB
AnonPages: 313372 kB
Mapped: 64608 kB
Shmem: 43120 kB
Slab: 26992 kB
SReclaimable: 11196 kB
SUnreclaim: 15796 kB
KernelStack: 1808 kB
PageTables: 10844 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 11851640 kB
Committed_AS: 1004672 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 366716 kB
VmallocChunk: 34359355879 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 55296 kB
DirectMap2M: 7192576 kB


--------------
Kernel 3.2
--------------

$ dmesg | grep mtrr
[ 5.001176] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining

$ cat /proc/mtrr
reg00: base=0x000000000 ( 0MB), size= 8192MB, count=1: write-back
reg01: base=0x200000000 ( 8192MB), size= 512MB, count=1: write-back
reg02: base=0x0e0000000 ( 3584MB), size= 512MB, count=1: uncachable
reg03: base=0x0dc000000 ( 3520MB), size= 64MB, count=1: uncachable
reg04: base=0x0db800000 ( 3512MB), size= 8MB, count=1: uncachable
reg05: base=0x21f800000 ( 8696MB), size= 8MB, count=1: uncachable
reg06: base=0x21f600000 ( 8694MB), size= 2MB, count=1: uncachable

$ dmesg | grep drm
[ 4.960827] [drm] Initialized drm 1.1.0 20060810
[ 5.001178] [drm] MTRR allocation failed. Graphics performance may suffer.
[ 5.001350] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 5.001351] [drm] Driver supports precise vblank timestamp query.
[ 5.344345] fbcon: inteldrmfb (fb0) is primary device
[ 5.523815] fb0: inteldrmfb frame buffer device
[ 5.523816] drm: registered panic notifier
[ 5.585070] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

$ dmesg | grep i915
[ 4.973200] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 4.973202] i915 0000:00:02.0: setting latency timer to 64
[ 5.001347] i915 0000:00:02.0: irq 43 for MSI/MSI-X
[ 5.585070] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

$ dmesg | grep agp
[ 0.977765] Linux agpgart interface v0.103
[ 0.977815] agpgart-intel 0000:00:00.0: Intel Ivybridge Chipset
[ 0.977882] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
[ 0.978505] agpgart-intel 0000:00:00.0: detected 65536K stolen memory
[ 0.978595] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000


--
Saludos de Javier <jcantero@escomposlinux.org>
 
Old 10-07-2012, 03:06 PM
Ingo
 
Default Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze

Interesting to see the differences between the 2 kernels. Compared to
my messages I found following lines in dmesg have disappeared with 3.5:

mtrr: type mismatch for e0000000,10000000 old: write-back new:
write-combining

[drm] MTRR allocation failed. Graphics performance may suffer.
[drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed

i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100,
writing 0x10b)
i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007,
writing 0x900407)
i915 0000:00:02.0: setting latency timer to 64

while enabling RC6 states has been added:

[drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off


Probably a hint to the root cause?

I also compared the BIOS settings:

Javier has these options/settings:
Integrated Graphics Share Memory [64MB]
DVMT Memory [256MB]

I only have:
IGD DVMT Memory [256MB]

(which I called previously "agp-aperture" - ancient name when PC's had
a dedicated AGP-Port). This is the setting which I did change from
"max" -> "256MB" and got my system stable - which still holds right now.

However the "mtrr" setups (/proc/mtrr) are still identical with both
kernels. Seems the "write-combining area" has become obsolete - or
still not implemented in i915?

Ingo


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 50719A71.8080202@gmx.net">http://lists.debian.org/50719A71.8080202@gmx.net
 
Old 10-07-2012, 04:01 PM
Ben Hutchings
 
Default Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze

On Sun, 2012-10-07 at 17:06 +0200, Ingo wrote:
> Interesting to see the differences between the 2 kernels. Compared to
> my messages I found following lines in dmesg have disappeared with 3.5:
>
> mtrr: type mismatch for e0000000,10000000 old: write-back new:
> write-combining
>
> [drm] MTRR allocation failed. Graphics performance may suffer.
> [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed
>
> i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100,
> writing 0x10b)
> i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007,
> writing 0x900407)
> i915 0000:00:02.0: setting latency timer to 64
>
> while enabling RC6 states has been added:
>
> [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
>
>
> Probably a hint to the root cause?

Don't think so.

> I also compared the BIOS settings:
>
> Javier has these options/settings:
> Integrated Graphics Share Memory [64MB]
> DVMT Memory [256MB]
>
> I only have:
> IGD DVMT Memory [256MB]
>
> (which I called previously "agp-aperture" - ancient name when PC's had
> a dedicated AGP-Port). This is the setting which I did change from
> "max" -> "256MB" and got my system stable - which still holds right now.
>
> However the "mtrr" setups (/proc/mtrr) are still identical with both
> kernels. Seems the "write-combining area" has become obsolete - or
> still not implemented in i915?

The driver calls ioremap_wc() which will enable write-combining through
the PAT in recent processors. An MTRR is not needed and in 3.5 the
driver doesn't even bother to allocate one:

commit 9e984bc1dffd405138ff22356188b6a1677c64c8
Author: Adam Jackson <ajax@redhat.com>
Date: Wed Mar 14 11:22:11 2012 -0400

drm/i915: Don't do MTRR setup if PAT is enabled

Ben.

--
Ben Hutchings
You can't have everything. Where would you put it?
 
Old 10-10-2012, 12:26 PM
Ingo
 
Default Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze

With 256MB of RAM assigned to graphics all is 100% stable here since
over 2 weeks. Also 512MB seem to be no problem, just if I enable
"Maximum DVMT".

I checked with the specifications of my MoBo (Intel DH77EB) and it says:

 Dynamic Video Memory Technology (DVMT) 5.0 support
 Support of up to 1.7 GB Video Memory with 4 GB and above system memory
configuration

So these 1.7GB probably exceeds what the driver (or PAT) is capable?

Regards,
Ingo


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 5075695E.7060406@gmx.net">http://lists.debian.org/5075695E.7060406@gmx.net
 
Old 10-10-2012, 06:43 PM
Jonathan Nieder
 
Default Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze

Hi Ingo,

Per Foreby wrote:
>> Per Foreby wrote:

>>> So far I'm running whith the default wheezy kernel but with the iGPU memory
>>> set to 256 MB. My plan was to run with this setting, and if I had another
>>> crash, try the experimental kernel.
[...]
> New freeze. Last entry in the debug log was more than 10 minutes before
> the freeze.

Ingo wrote:

> With 256MB of RAM assigned to graphics all is 100% stable here since
> over 2 weeks. Also 512MB seem to be no problem, just if I enable
> "Maximum DVMT".

There seem to be some differences in symptoms here, so please file a
separate bug. We can merge them later if they turn out to have the
same cause.

Thanks,
Jonathan


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20121010184321.GB3079@elie.Belkin
 

Thread Tools




All times are GMT. The time now is 06:56 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org