From: Alexander Hoogerhuis <alexh@ihatent.com>
To: Andrew Morton <akpm@digeo.com>
Cc: rmk@arm.linux.org.uk, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.65-mm1
Date: 19 Mar 2003 09:12:48 +0100 [thread overview]
Message-ID: <87fzpjepvj.fsf@lapper.ihatent.com> (raw)
In-Reply-To: <20030318162601.78f11739.akpm@digeo.com>
Andrew Morton <akpm@digeo.com> writes:
> Alexander Hoogerhuis <alexh@ihatent.com> wrote:
> >
> > I'm not suspecting the PCI in particular for the PCIC-bits, only
> > making X and the Radeon work again. But here you are:
>
> Something bad has happened to the Radeon driver in recent kernels. I've seen
> various reports with various syptoms and some suspicion has been directed at
> the AGP changes.
>
> But as far as I know nobody has actually got down and done the binary search
> to find out exactly when it started happening.
Just got my machine out and booted up, this time I did enable my
chipset into 4x AGP, instead of 1x as last night:
alexh@lapper ~ $ dmesg | grep -i agp
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected Intel i845 chipset
agpgart: Maximum main memory to use for agp memory: 690M
agpgart: AGP aperture is 256M @ 0xa0000000
agpgart: Putting AGP V2 device at 00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 01:00.0 into 4x mode
alexh@lapper ~ $
mvh,
A
--
Alexander Hoogerhuis | alexh@ihatent.com
CCNP - CCDP - MCNE - CCSE | +47 908 21 485
"You have zero privacy anyway. Get over it." --Scott McNealy
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Hoogerhuis <alexh@ihatent.com>
To: Andrew Morton <akpm@digeo.com>
Cc: rmk@arm.linux.org.uk, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.65-mm1
Date: 19 Mar 2003 09:12:48 +0100 [thread overview]
Message-ID: <87fzpjepvj.fsf@lapper.ihatent.com> (raw)
In-Reply-To: <20030318162601.78f11739.akpm@digeo.com>
Andrew Morton <akpm@digeo.com> writes:
> Alexander Hoogerhuis <alexh@ihatent.com> wrote:
> >
> > I'm not suspecting the PCI in particular for the PCIC-bits, only
> > making X and the Radeon work again. But here you are:
>
> Something bad has happened to the Radeon driver in recent kernels. I've seen
> various reports with various syptoms and some suspicion has been directed at
> the AGP changes.
>
> But as far as I know nobody has actually got down and done the binary search
> to find out exactly when it started happening.
Just got my machine out and booted up, this time I did enable my
chipset into 4x AGP, instead of 1x as last night:
alexh@lapper ~ $ dmesg | grep -i agp
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected Intel i845 chipset
agpgart: Maximum main memory to use for agp memory: 690M
agpgart: AGP aperture is 256M @ 0xa0000000
agpgart: Putting AGP V2 device at 00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 01:00.0 into 4x mode
alexh@lapper ~ $
mvh,
A
--
Alexander Hoogerhuis | alexh@ihatent.com
CCNP - CCDP - MCNE - CCSE | +47 908 21 485
"You have zero privacy anyway. Get over it." --Scott McNealy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-03-19 8:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 11:11 2.5.65-mm1 Andrew Morton
2003-03-18 11:11 ` 2.5.65-mm1 Andrew Morton
2003-03-18 13:15 ` 2.5.65-mm1 Helge Hafting
2003-03-18 13:15 ` 2.5.65-mm1 Helge Hafting
2003-03-18 13:29 ` 2.5.65-mm1 small nfs umount problem, also in 64-mm8 Helge Hafting
2003-03-18 13:56 ` Andreas Haumer
2003-03-18 15:08 ` 2.5.65-mm1 Alexander Hoogerhuis
2003-03-18 15:08 ` 2.5.65-mm1 Alexander Hoogerhuis
2003-03-18 15:51 ` 2.5.65-mm1 Alexander Hoogerhuis
2003-03-18 15:51 ` 2.5.65-mm1 Alexander Hoogerhuis
2003-03-18 16:09 ` 2.5.65-mm1 Russell King
2003-03-18 16:09 ` 2.5.65-mm1 Russell King
2003-03-19 0:14 ` 2.5.65-mm1 Alexander Hoogerhuis
2003-03-19 0:14 ` 2.5.65-mm1 Alexander Hoogerhuis
2003-03-19 0:26 ` 2.5.65-mm1 Andrew Morton
2003-03-19 0:26 ` 2.5.65-mm1 Andrew Morton
2003-03-19 6:16 ` 2.5.65-mm1 Alexander Hoogerhuis
2003-03-19 6:16 ` 2.5.65-mm1 Alexander Hoogerhuis
2003-03-19 8:12 ` Alexander Hoogerhuis [this message]
2003-03-19 8:12 ` 2.5.65-mm1 Alexander Hoogerhuis
2003-03-19 8:20 ` 2.5.65-mm1 Alexander Hoogerhuis
2003-03-19 8:20 ` 2.5.65-mm1 Alexander Hoogerhuis
2003-03-18 19:49 ` Re[2]: 2.5.65-mm1 Ruslan U. Zakirov
2003-03-18 21:33 ` 2.5.65-mm1 Adam Belay
2003-03-18 21:33 ` 2.5.65-mm1 Adam Belay
2003-03-18 21:40 ` 2.5.65-mm1 William Lee Irwin III
2003-03-18 21:40 ` 2.5.65-mm1 William Lee Irwin III
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=87fzpjepvj.fsf@lapper.ihatent.com \
--to=alexh@ihatent.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rmk@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.