Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: Re. 2.6.15-mm1
Date: Thu, 5 Jan 2006 18:05:03 -0800
Message-ID: <01EF044AAEE12F4BAAD955CB7506494305977CC4@scsmsx401.amr.corp.intel.com>
Thread-Topic: Re. 2.6.15-mm1
Thread-Index: AcYSV2UpfQWfykebQDKTI2NUy/r9WAADUsbg
From: "Seth, Rohit" <rohit.seth@intel.com>
To: "Andrew Morton" <akpm@osdl.org>,
       "Alexander Gran" <alex@zodiac.dnsalias.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
       "Brown, Len" <len.brown@intel.com>, <ambx1@neo.rr.com>,
       <reiserfs-dev@namesys.com>, <airlied@linux.ie>, <vs@namesys.com>,
       "Dave Jones" <davej@codemonkey.org.uk>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 932
Lines: 30

From: Andrew Morton Thursday, January 05, 2006 4:22 PM

>> 8b 1d 10 00 00 0
>> 0 0f b6 c0 8d 48 04 8d 6c 24
>>  <3>[drm:drm_release] *ERROR* Device busy: 1 0
>> EDAC PCI- Detected Parity Error on 0000:00:1e.0
>
>OK.  I've been assuming that this is a DRM bug but I note that the AGP
tree
>has been dinking with agp_collect_device_status(), so perhaps I had the
>wrong David.
>
>> Additionally every second or so I got these console (and kernel of
>cource)
>> message:
>> EDAC PCI- Detected Parity Error on 0000:00:1e.0
>
>Alan, Rohit: do we expect that the EDAC fixes which you're cooking up
will
>address this?  I think not?
>

Nops.  That one patch does not address this issue.

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