From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Alexander Gran <alex@zodiac.dnsalias.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
len.brown@intel.com, ambx1@neo.rr.com, reiserfs-dev@namesys.com,
airlied@linux.ie, vs@namesys.com, "Seth,
Rohit" <rohit.seth@intel.com>
Subject: Re: Re. 2.6.15-mm1
Date: Thu, 5 Jan 2006 19:38:10 -0500 [thread overview]
Message-ID: <20060106003810.GA22051@redhat.com> (raw)
In-Reply-To: <20060105162151.6fc1716f.akpm@osdl.org>
On Thu, Jan 05, 2006 at 04:21:51PM -0800, Andrew Morton wrote:
> > Am Donnerstag, 5. Januar 2006 23:47 schrieb Andrew Morton:
> > > > Jan 5 16:22:47 t40 kernel: mtrr: 0xe0000000,0x8000000 overlaps existing
> > > > 0xe0000000,0x4000000
> > > > Jan 5 16:22:48 t40 last message repeated 2 times
> > >
> > > Is that new?
> >
> > Umm, no. I just thought it could be related to the X oops.
>
> OK. I don't know how common this is, nor whether it'll cause problems.
> David(s), do you know?
at worse, a video performance hit.
> > EIP is at agp_collect_device_status+0x14/0xd4
> 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.
I'm a moron. I'll fix it up.
I only tested the 'have no agp' case which this changed, and didn't test
the commoncase 'have agp'. Doh.
Dave
next prev parent reply other threads:[~2006-01-06 2:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 17:01 Re. 2.6.15-mm1 Alexander Gran
2006-01-05 22:47 ` Andrew Morton
2006-01-05 23:33 ` Alexander Gran
2006-01-06 0:21 ` Andrew Morton
2006-01-06 0:28 ` Dave Airlie
2006-01-06 0:38 ` Dave Jones [this message]
2006-01-06 9:30 ` Hans Reiser
2006-01-06 18:29 ` Alexander Zarochentsev
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 23:31 Etienne Lorrain
2006-01-06 0:15 ` Andrew Morton
2006-01-06 0:36 ` Linus Torvalds
2006-01-06 10:04 ` Etienne Lorrain
2006-01-06 2:05 Seth, Rohit
2006-01-06 5:36 Brown, Len
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=20060106003810.GA22051@redhat.com \
--to=davej@redhat.com \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=alex@zodiac.dnsalias.org \
--cc=ambx1@neo.rr.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.com \
--cc=rohit.seth@intel.com \
--cc=vs@namesys.com \
/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