Re: [Intel-gfx] system freeze with kernel 3.2-rc7
Ben Widawsky b...@bwidawsk.net schrieb: On Mon, Dec 26, 2011 at 01:43:37AM +0100, Kai Krakow wrote: I found my system freeze mostly during starting up X and KDE. Sometimes it works for some minutes, sometimes it freezes immediatly. When the freeze happens, everything is dead (even the reset button does not work, I need to power cycle). [...] Can you please try this kernel: git://people.freedesktop.org/~bwidawsk/drm-intel context-support You probably need to manually enable rc6. We were given some hint that we may not be setting up contexts properly. The above branch should create a default context (amongst other stuff which won't happen in this case). Since that branch seems to be based off 3.2-rc6 I didn't need to enable RC6, it was on by default. But I'm sorry to inform you that this still makes my system board freeze during KDE login, sometimes early, sometimes late during loading of the desktop. My system freezes completely: Keyboard dead, SysRq shortcuts dead, screen goes blank (or shows funny lightshows before blanking), even the hard disk LED freezes. I need to power cycle to get back into a working state. If I only use the reset switch, the board behaves strange after reboot. The reset button sometimes takes a few seconds to make the system reboot when frozen. All this tells me that something really bad goes on within the CPU/GPU/chipset during freeze which even survives a board reset. Only power cycling helps. Keith got the specs of my system and wanted to mirror it for development. Maybe he could find out better what happens. I have no idea how to debug that because everything freezes so badly. Regards, Kai ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] system freeze with kernel 3.2-rc7
On 01/12/2012 02:57 PM, Kai Krakow wrote: Ben Widawskyb...@bwidawsk.net schrieb: On Mon, Dec 26, 2011 at 01:43:37AM +0100, Kai Krakow wrote: I found my system freeze mostly during starting up X and KDE. Sometimes it works for some minutes, sometimes it freezes immediatly. When the freeze happens, everything is dead (even the reset button does not work, I need to power cycle). [...] Can you please try this kernel: git://people.freedesktop.org/~bwidawsk/drm-intel context-support You probably need to manually enable rc6. We were given some hint that we may not be setting up contexts properly. The above branch should create a default context (amongst other stuff which won't happen in this case). Since that branch seems to be based off 3.2-rc6 I didn't need to enable RC6, it was on by default. But I'm sorry to inform you that this still makes my system board freeze during KDE login, sometimes early, sometimes late during loading of the desktop. Thanks. At least we can give this information back to our design team. My system freezes completely: Keyboard dead, SysRq shortcuts dead, screen goes blank (or shows funny lightshows before blanking), even the hard disk LED freezes. I need to power cycle to get back into a working state. If I only use the reset switch, the board behaves strange after reboot. The reset button sometimes takes a few seconds to make the system reboot when frozen. All this tells me that something really bad goes on within the CPU/GPU/chipset during freeze which even survives a board reset. Only power cycling helps. Keith got the specs of my system and wanted to mirror it for development. Maybe he could find out better what happens. I have no idea how to debug that because everything freezes so badly. Regards, Kai Jesse, would you care to update VPG with this info? Ben ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] system freeze with kernel 3.2-rc7
On Thu, Dec 29, 2011 at 23:13, Kevin kjs...@gmail.com wrote: Kevin kjslag at gmail.com writes: I'm not sure if mentioning this helps, but I think I'm experiencing the same problem. ... Nevermind, I got libdrm-2.4.27 to freeze. Everything (including capslock and sysrq) was frozen except my mouse, which would move just fine. It's possible I'm affected by this bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908335 I use brcmsmac Is there a way to setup a netconsole for your machine and check what happens during the hangs? The last dying words of the machine could be very helpful. Thanks! -- Eugeni Dodonov http://eugeni.dodonov.net/ ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] system freeze with kernel 3.2-rc7
Kevin kjslag at gmail.com writes: I'm not sure if mentioning this helps, but I think I'm experiencing the same problem. ... Nevermind, I got libdrm-2.4.27 to freeze. Everything (including capslock and sysrq) was frozen except my mouse, which would move just fine. It's possible I'm affected by this bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908335 I use brcmsmac ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] system freeze with kernel 3.2-rc7
I'm not sure if mentioning this helps, but I think I'm experiencing the same problem. My system will occasionally freeze completely (numlock and SysRq key don't work) with the image on the screen completely frozen (I don't get any artifacts). I then use the power button to reboot. I use Arch Linux. libdrm 2.4.27 works. 2.4.28 - 2.4.29 freezes. Freezes occur with catalyst-11.11 and 11.12 and with xorg-server-1.10 and 1.11 and with linux-3.1.5 and 3.1.4. $ uname -a Linux J 3.1.5-1-ARCH #1 SMP PREEMPT Sat Dec 10 14:43:09 CET 2011 x86_64 Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz GenuineIntel GNU/Linux ATI Mobility Radeon HD 5850 with catalyst driver (I need GPU opencl atm) laptop model: http://www.newegg.com/Product/Product.aspx?Item=N82E16834157515 ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] system freeze with kernel 3.2-rc7
On Mon, Dec 26, 2011 at 16:54:18 -0800, Keith Packard wrote: On Mon, 26 Dec 2011 11:59:04 +0100, Kai Krakow hurikha...@gmail.com wrote: North Bridge Configuration: VT-d This doesn't exist That's odd. I don't understand all of the SNB CPU variations; perhaps there's a desktop version that has VT-d fused out or something? The K variants of SandyBridge CPUs don't have VT-d. Here is the product page for the 2500K: http://ark.intel.com/products/52210/ Regards, Tino ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] system freeze with kernel 3.2-rc7
On Mon, Dec 26, 2011 at 16:54:18 -0800, Keith Packard wrote: On Mon, 26 Dec 2011 11:59:04 +0100, Kai Krakow hurikha...@gmail.com wrote: North Bridge Configuration: VT-d This doesn't exist That's odd. I don't understand all of the SNB CPU variations; perhaps there's a desktop version that has VT-d fused out or something? The K variants of SandyBridge CPUs don't have VT-d. Here is the product page for the 2500K: http://ark.intel.com/products/52210/ Regards, Tino ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] system freeze with kernel 3.2-rc7
Keith Packard kei...@keithp.com schrieb: You almost certainly don't need IOMMU/VT-d support though; that virtualizes devices for DMA by the guest OS, which generally no-one does. The BIOS manual for the Z68 board mentions two configuration options, CPU Configuration: Intel Virtualization Technology This exists... North Bridge Configuration: VT-d This doesn't... I'd love to see tests with these in the three possible combinations: VT enabled, VT-d enabled VT enabled, VT-d disabled VT disabled, VT-d disabled Since there's only VT in my BIOS, I tested both settings, and both failed. I can only reliably boot with RC6 disabled. Otherwise it reproducably hangs on a black screen either just before the boot splash or it never shows the boot splash from initramfs (but works, I see HD activity) and then hangs on loading the next boot splash from real_root. The monitor goes into idle when this happens. But usually the system gets past this and later fails to start or log in to X. The screen goes crazy (flickering or colorful stripes running down the left side of the screen) when this happens. System freezes completely, e.g. if I had HD activity the LED stays on forever, hw reset button dead. Meanwhile, I'll get a patch ready for 3.2 which disables RC6 again. If I should provide more info to identify my system, please tell me. Regards, Kai ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] system freeze with kernel 3.2-rc7
Keith Packard wrote: On Mon, 26 Dec 2011 11:59:04 +0100, Kai Krakow hurikha...@gmail.com wrote: North Bridge Configuration: VT-d This doesn't exist That's odd. I don't understand all of the SNB CPU variations; perhaps there's a desktop version that has VT-d fused out or something? If I should provide more info to identify my system, please tell me. # lspci -nn -vv 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0100] (rev 09) Subsystem: ASRock Incorporation Device [1849:0100] 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 [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0112] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:0112] 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 44 Region 0: Memory at fe00 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at c000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at f000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0100c Data: 4179 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- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) Subsystem: ASRock Incorporation Device [1849:1c3a] 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 11 Region 0: Memory at fe608000 (64-bit, non-prefetchable) [size=16] Capabilities: [50] 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- Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: Data: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) (prog-if 20 [EHCI]) Subsystem: ASRock Incorporation Device [1849:1c2d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at fe607000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI
Re: [Intel-gfx] system freeze with kernel 3.2-rc7
On Tue, 27 Dec 2011 04:18:21 +0100, Kai Krakow hurikha...@gmail.com wrote: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor ... Thanks. I'll see about duplicating this system here so we can try and make it work and still have RC6 enabled, either by fixing it for this platform or figuring out a likely combination of values that disable for this machine while leaving it enabled for most others. -- keith.pack...@intel.com pgpEt4Hc27vNM.pgp Description: PGP signature ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] system freeze with kernel 3.2-rc7
Hello! I found my system freeze mostly during starting up X and KDE. Sometimes it works for some minutes, sometimes it freezes immediatly. When the freeze happens, everything is dead (even the reset button does not work, I need to power cycle). I was using libdrm-2.4.27 before, system freeze showed some colorful lines running down at the left side of the screen after turning black, then some blue flicker in the top 10% of the the screen. System no longer reacts, network is dead too. Now, using libdrm-2.4.29, the system freeze shows other effects: Screen does not turn black but starts to flicker and occassionally moves some centimeters to the right (wrapping the right-most part to the left) for a very short time, then jumping back with some distortions. The rest is the same: Complete freeze, even reset button stops working. Before finding out about the libdrm difference, I tried other intel xorg driver versions to no avail, I tried with SNA support and without. No difference. I'm now back to intel xorg driver 2.17.0. I read about the semaphores feature, turned it off: No change. Sometimes the system even freezes before displaying the framebuffer splash. I didn't have such issues with early 3.2 rcs (afair), and not with 3.1 kernels. After some digging through google I've found you enabled RC6 in 3.2. I disabled it now, and my system runs wonderfully. Do you need any specs? I'd be happy to send these. The system is a Z68 Pro board with Sandybridge i5-2500K processor, 8 GB of RAM and UEFI firmware. Looks like RC6 is not ready for roll-out, at least on some mainboards. Regards, Kai ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] system freeze with kernel 3.2-rc7
On Mon, 26 Dec 2011 01:43:37 +0100, Kai Krakow hurikha...@gmail.com wrote: I didn't have such issues with early 3.2 rcs (afair), and not with 3.1 kernels. After some digging through google I've found you enabled RC6 in 3.2. I disabled it now, and my system runs wonderfully. Argh. Can you try building a kernel with VT-d support? I assume you can't turn VT-d off in the BIOS as it's UEFI? -- keith.pack...@intel.com pgpqvKlmvPKLt.pgp Description: PGP signature ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] system freeze with kernel 3.2-rc7
Keith Packard kei...@keithp.com schrieb: On Mon, 26 Dec 2011 01:43:37 +0100, Kai Krakow hurikha...@gmail.com wrote: I didn't have such issues with early 3.2 rcs (afair), and not with 3.1 kernels. After some digging through google I've found you enabled RC6 in 3.2. I disabled it now, and my system runs wonderfully. Argh. Can you try building a kernel with VT-d support? I assume you can't turn VT-d off in the BIOS as it's UEFI? kakra@jupiter ~ $ zgrep -i iommu /proc/config.gz CONFIG_GART_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_IOMMU_HELPER=y CONFIG_IOMMU_API=y CONFIG_IOMMU_SUPPORT=y # CONFIG_AMD_IOMMU is not set CONFIG_INTEL_IOMMU=y CONFIG_INTEL_IOMMU_DEFAULT_ON=y CONFIG_INTEL_IOMMU_FLOPPY_WA=y # CONFIG_IOMMU_DEBUG is not set # CONFIG_IOMMU_STRESS is not set So kernel vt-d support is on. Not sure what to look for in dmesg thou... I didn't look into the BIOS settings yet, but usually if there is such an option I turn it on because I use virtual machines. Regards, Kai ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] system freeze with kernel 3.2-rc7
On Mon, 26 Dec 2011 03:43:22 +0100, Kai Krakow hurikha...@gmail.com wrote: Keith Packard kei...@keithp.com schrieb: On Mon, 26 Dec 2011 01:43:37 +0100, Kai Krakow hurikha...@gmail.com wrote: I didn't have such issues with early 3.2 rcs (afair), and not with 3.1 kernels. After some digging through google I've found you enabled RC6 in 3.2. I disabled it now, and my system runs wonderfully. Argh. Can you try building a kernel with VT-d support? I assume you can't turn VT-d off in the BIOS as it's UEFI? kakra@jupiter ~ $ zgrep -i iommu /proc/config.gz CONFIG_GART_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_IOMMU_HELPER=y CONFIG_IOMMU_API=y CONFIG_IOMMU_SUPPORT=y # CONFIG_AMD_IOMMU is not set CONFIG_INTEL_IOMMU=y CONFIG_INTEL_IOMMU_DEFAULT_ON=y CONFIG_INTEL_IOMMU_FLOPPY_WA=y # CONFIG_IOMMU_DEBUG is not set # CONFIG_IOMMU_STRESS is not set So kernel vt-d support is on. Not sure what to look for in dmesg thou... I didn't look into the BIOS settings yet, but usually if there is such an option I turn it on because I use virtual machines. You almost certainly don't need IOMMU/VT-d support though; that virtualizes devices for DMA by the guest OS, which generally no-one does. The BIOS manual for the Z68 board mentions two configuration options, CPU Configuration: Intel Virtualization Technology When this option is set to [Enabled], a VMM (Virtual Machine Architecture) can utilize the additional hardware capabilities provided by Vanderpool Technology. This option will be hidden if the installed CPU does not support Intel Virtualization Technology. North Bridge Configuration: VT-d Use this to enable or disable Intel® VT-d technology (Intel® Virtualization Technology for Directed I/O). The default value of this feature is [Disabled]. I'd love to see tests with these in the three possible combinations: VT enabled, VT-d enabled VT enabled, VT-d disabled VT disabled, VT-d disabled Meanwhile, I'll get a patch ready for 3.2 which disables RC6 again. -- keith.pack...@intel.com pgp2RU01UNjv3.pgp Description: PGP signature ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
