Your message dated Wed, 20 Apr 2005 22:53:36 GMT
with message-id <[EMAIL PROTECTED]>
and subject line xserver-xfree86: [savage] runs out of MTRRs on unknown chipset
(0x8c2e) rev 5
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 7 Nov 2002 16:04:35 +0000
>From [EMAIL PROTECTED] Thu Nov 07 10:04:35 2002
Return-path: <[EMAIL PROTECTED]>
Received: from sc-66-27-3-140.socal.rr.com (franzdoodle.com) [66.27.3.140]
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 189p90-00061c-00; Thu, 07 Nov 2002 10:04:34 -0600
Received: (qmail 19840 invoked by uid 8); 7 Nov 2002 15:49:48 -0000
Received: from pc-00075 (192.168.2.75, claiming to be "ginger")
by whitey.franzdoodle.com with SMTP id smtpdBjkZLz; Thu, 07 Nov 2002
10:49:46 EST
Date: Thu, 7 Nov 2002 08:05:51 -0800
From: Chad Carr <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: mtrr: no more MTRRs available/SAVAGE(0): Failed to set up
write-combining range (Linked?)
Message-Id: <[EMAIL PROTECTED]>
X-Mailer: Sylpheed version 0.7.4claws (GTK+ 1.2.10; i386-debian-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-0.1 required=5.0
tests=SPAM_PHRASE_01_02
version=2.41
X-Spam-Level:
Package: xserver-xfree86
Version: 4.2.1-3
Package from unstable. Toshiba Tecra 9100 with Savage IXc. I get the kernel
reporting
mtrr: no more MTRRs available
in blocks of exactly 232 messages. in kern.log. This is readily apparent at
about line 549.
(http://www.franzdoodle.com/xfree86/kern.log)
Also, XFree86.0.log reports the following two messages
SAVAGE(0): Splitting WC range: base: 0xec1f0000, size: 0xce0000
SAVAGE(0): Failed to set up write-combining range
in blocks of 236 and 232, respectively. There may be other problems shown in
this file as well, but I cannot connect them to the MTRR message.
(http://www.franzdoodle.com/xfree86/XFree86.0.log)
I have also seen this with previous versions of the savage driver on a Tecra
9000 with the same video (or nearly the same)
Thanks, guys. Let me know if I can help further.
---------------------------------------
Received: (at 168178-done) by bugs.debian.org; 20 Apr 2005 22:53:39 +0000
>From [EMAIL PROTECTED] Wed Apr 20 15:53:39 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 48.host.terra.es (tfdsmtp1.mail.isp) [213.4.129.48]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DOO4g-0001yz-00; Wed, 20 Apr 2005 15:53:38 -0700
Received: from teleline.es ([10.20.4.99]) by tfdsmtp1.mail.isp
(Netscape Messaging Server 4.15 tfdsmtp1 Mar 14 2002 21:29:48)
with ESMTP id IF9OXC00.R5B for <[EMAIL PROTECTED]>;
Thu, 21 Apr 2005 00:53:36 +0200
Disposition-Notification-To: ROBERTOJIMENOCA <[EMAIL PROTECTED]>
From: ROBERTOJIMENOCA <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 20 Apr 2005 22:53:36 GMT
X-Mailer: Netscape Webmail
MIME-Version: 1.0
Content-Language: es
Subject: Re: xserver-xfree86: [savage] runs out of MTRRs on unknown
chipset (0x8c2e) rev 5
X-Accept-Language: es
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-1.9 required=4.0 tests=BAYES_00,BLANK_LINES_70_80,
RCVD_IN_BL_SPAMCOP_NET,ROBERTOJIMENOCA autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 4
This bug is fixed. Reopen otherwise.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
