lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1268458676.28444.9.camel@dc7800.home>
Date:	Fri, 12 Mar 2010 22:37:56 -0700
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Pete Zaitcev <zaitcev@...hat.com>
Cc:	dri-devel@...ts.sourceforge.net, airlied@...ux.ie,
	jbarnes@...tuousgeek.org, linux-kernel@...r.kernel.org
Subject: Re: Regression in i915 on 2.6.34-rc1

On Fri, 2010-03-12 at 18:25 -0700, Pete Zaitcev wrote:
> On Thu, 11 Mar 2010 00:33:58 -0700, Pete Zaitcev <zaitcev@...hat.com> wrote:
> 
> I apologise for answering to myself, but while there was no answer,
> git bisect found the offending commit and I verified that it was
> the culprit. Also, I am adding Bjorn and Jesse to cc:.
> 
> > I seem to hit a sudden regression in 2.6.34-rc1: the modeset fails.
> > On this box it also means, no way to start X, which is unfortunate.

Thanks for the report.  Would you mind posting the entire dmesg
log, /proc/iomem contents, and "lspci -vv" output somewhere (maybe in
bugzilla)?

The quote below isn't enough for me to see the problem, but
http://bugzilla.kernel.org/show_bug.cgi?id=15480 is another regression
related to this commit.  There are some patches for that one here:
http://lkml.org/lkml/2010/3/11/512, but without knowing more about the
problem you're seeing, I don't want to waste your time trying them.

Bjorn

> > Here's a quote from bad dmesg (truncated front and back for brievity):
> > 
> > Linux agpgart interface v0.103
> > agpgart-intel 0000:00:00.0: Intel HD Graphics Chipset
> > agpgart-intel 0000:00:00.0: detected 131068K stolen memory
> > agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
> > tpm_tis 00:09: 1.2 TPM (device-id 0xB, rev-id 16)
> > Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> > ................
> > udev: starting version 151
> > [drm] Initialized drm 1.1.0 20060810
> > i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> > i915 0000:00:02.0: setting latency timer to 64
> >   alloc irq_desc for 33 on node -1
> >   alloc kstat_irqs on node -1
> > i915 0000:00:02.0: irq 33 for MSI/MSI-X
> > [drm] set up 127M of stolen space
> > [drm:i915_gem_init_ringbuffer] *ERROR* Ring head not reset to zero ctl ffffffff head ffffffff tail ffffffff start ffffffff
> > [drm:i915_gem_init_ringbuffer] *ERROR* Ring head forced to zero ctl ffffffff head ffffffff tail ffffffff start ffffffff
> > [drm:i915_gem_init_ringbuffer] *ERROR* Ring initialization failed ctl ffffffff head ffffffff tail ffffffff start ffffffff
> > [drm:i915_driver_load] *ERROR* failed to init modeset
> > i915: probe of 0000:00:02.0 failed with error -5
> > dracut: Starting plymouth daemon
> > 
...
> 
> The commit follows appended.
> 
> It's possible that the BIOS on this motherboard is not up to snuff,
> but the 2.6.33-rc8 worked fine, so clearly Linux can do it... right?
> 
> Cheers,
> -- Pete
> 
> commit 7bc5e3f2be32ae6fb0c74cd0f707f986b3a01a26
> Author: Bjorn Helgaas <bjorn.helgaas@...com>
> Date:   Tue Feb 23 10:24:41 2010 -0700
> 
>     x86/PCI: use host bridge _CRS info by default on 2008 and newer machines
...

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ