From: Andrew Morton <akpm@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Greg KH <greg@kroah.com>
Cc: "bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
linux-kernel@vger.kernel.org, ktk@bigfoot.com
Subject: Re: [Bugme-new] [Bug 8187] New: 2.6.20 "PCI: Quirks" patch breaks X11 on I82801
Date: Mon, 12 Mar 2007 22:19:52 -0800 [thread overview]
Message-ID: <20070312221952.691adeea.akpm@linux-foundation.org> (raw)
In-Reply-To: <200703122030.l2CKU5ES022977@fire-2.osdl.org>
> On Mon, 12 Mar 2007 13:30:05 -0700 bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8187
>
> Summary: 2.6.20 "PCI: Quirks" patch breaks X11 on I82801
> Kernel Version: 2.6.20
> Status: NEW
> Severity: normal
> Owner: greg@kroah.com
> Submitter: ktk@bigfoot.com
>
>
> Most recent kernel where this bug did *NOT* occur:
> Any 2.6.20-pre prior to commit 368c73d4f689dae0807d0a2aa74c61fd2b9b075f
>
> Distribution: Slackware 11.0
> Hardware Environment: HP/Compaq dc5000S (P4, 82801, 82865)
> Software Environment: Xorg 6.9.0
> Problem Description:
>
> Alan Cox introduced a "PCI: Quirks" patch (git commit
> 368c73d4f689dae0807d0a2aa74c61fd2b9b075f) in 2.6.20 that breaks X11 on this
> I82801 platform. Specifically, it causes the PCI initialisation to become
> buggered; Xorg 6.9.0 dumps the following to the console:
> (EE) end of block range 0x177 < begin 0x3f0
> (EE) end of block range 0x177 < begin 0x3f0
> (WW) ****INVALID IO ALLOCATION**** b: 0x14d0 e: 0x14d7 correcting
> [...]
> Backtrace:
> 0: X(xf86SigHandler+0x8a) [0x8088b2a]
> 1: [0xb7f2b420]
> 2: /usr/X11R6/lib/modules/drivers/i810_drv.so [0xb797f592]
> 3: X(InitOutput+0xb83) [0x8072713]
> 4: X(main+0x226) [0x80d4496]
> 5: /lib/tls/libc.so.6(__libc_start_main+0xd4) [0xb7da7e14]
> 6: X [0x806ff61]
>
> Fatal server error:
> Caught signal 11. Server aborting
>
> Steps to reproduce:
>
> Reverting the git commit mentioned above fixes the issue. Apparently, this may
> be limited to certain combinations of on-motherboard chipsets, as I haven't seen
> many bug reports. Googling shows some people having X11 segfault issues with
> 2.6.20 (e.g. freedesktop.org bug #9956) but in most of those cases it's due to
> the evdev driver and not PCI initialisation.
>
> I wrote to Alan (cc'ed Greg as he signed off on the patch) nearly two weeks ago
> but have heard nothing, so I'm leaving a bug here instead.
>
argh.
Would we break more machines than we fix if we just revert that?
next parent reply other threads:[~2007-03-13 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703122030.l2CKU5ES022977@fire-2.osdl.org>
2007-03-13 6:19 ` Andrew Morton [this message]
2007-03-13 5:59 ` [Bugme-new] [Bug 8187] New: 2.6.20 "PCI: Quirks" patch breaks X11 on I82801 Greg KH
2007-03-13 11:18 ` Bartlomiej Zolnierkiewicz
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=20070312221952.691adeea.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=greg@kroah.com \
--cc=ktk@bigfoot.com \
--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).