From: Alexander Hoogerhuis <alexh@ihatent.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Dave Jones <davej@codemonkey.org.uk>,
Andrew Morton <akpm@digeo.com>, "" <linux-kernel@vger.kernel.org>,
"" <linux-mm@kvack.org>
Subject: Re: [OOPS] 2.5.69-mm6
Date: 19 May 2003 10:53:56 +0200 [thread overview]
Message-ID: <873cjbjp0b.fsf@lapper.ihatent.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0305190431130.28750-100000@montezuma.mastecende.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Zwane Mwaikambo <zwane@linuxpower.ca> writes:
> On Mon, 19 May 2003, Alexander Hoogerhuis wrote:
>
> > Once I compile DRM/AGP as non-modular all errors are gone:
>
> Aargh.. Can you try recompile inkernel and reproduce again?
>
That's the problem, I've rekompiled the whole thing, with AGO/DRM in
kernel (non-modular), and the errors are gone... I'm not even seeing
the the usual radeon error like this one:
[drm] Initialized radeon 1.8.0 20020828 on minor 0
[drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
[drm:radeon_unlock] *ERROR* Process 4793 using kernel context 0
> Zwane
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQE+yJuhCQ1pa+gRoggRAvb0AJ44hHuACwDfIcjKOu8bPUJhnvztGwCgvKsK
kZ7i7Sd+WImIwyP7D05vCSU=
=C1gX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-05-19 8:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 8:54 2.5.69-mm6 Andrew Morton
2003-05-16 10:04 ` 2.5.69-mm6 bert hubert
2003-05-16 10:13 ` 2.5.69-mm6 Andrew Morton
2003-05-16 10:16 ` 2.5.69-mm6 bert hubert
2003-05-16 15:37 ` 2.5.69-mm6 Alan Cox
2003-05-16 16:58 ` 2.5.69-mm6 Valdis.Kletnieks
2003-05-17 13:46 ` 2.5.69-mm6 Alan Cox
2003-05-16 11:26 ` [OOPS] 2.5.69-mm6 Alexander Hoogerhuis
2003-05-16 18:08 ` William Lee Irwin III
2003-05-16 18:56 ` Dave Jones
2003-05-16 19:17 ` William Lee Irwin III
2003-05-17 3:23 ` Zwane Mwaikambo
2003-05-17 14:16 ` Zwane Mwaikambo
2003-05-18 13:01 ` Alexander Hoogerhuis
2003-05-19 8:23 ` Alexander Hoogerhuis
2003-05-19 8:36 ` Zwane Mwaikambo
2003-05-19 8:45 ` Zwane Mwaikambo
2003-05-19 8:53 ` Alexander Hoogerhuis [this message]
2003-05-19 8:53 ` Zwane Mwaikambo
2003-05-19 9:23 ` Alexander Hoogerhuis
2003-05-19 10:18 ` Alexander Hoogerhuis
2003-05-19 11:03 ` Zwane Mwaikambo
2003-05-18 12:59 ` Alexander Hoogerhuis
2003-05-18 12:57 ` Alexander Hoogerhuis
2003-05-16 17:28 ` 2.5.69-mm6 Andreas Henriksson
2003-05-16 17:55 ` 2.5.69-mm6 Dave Jones
2003-05-16 18:10 ` 2.5.69-mm6 Andreas Henriksson
2003-05-16 18:30 ` 2.5.69-mm6 Dave Jones
2003-05-16 19:02 ` 2.5.69-mm6 Andreas Henriksson
2003-05-16 19:25 ` 2.5.69-mm6 Dave Jones
2003-05-17 22:06 ` 2.5.69-mm6 Diego Calleja García
2003-05-18 11:36 ` 2.5.69-mm6 Helge Hafting
2003-05-18 13:05 ` 2.5.69-mm6 Diego Calleja García
2003-05-18 13:58 ` 2.5.69-mm6 Rudmer van Dijk
[not found] <200306091819.48459.sami.nieminen@iki.fi>
2003-06-09 15:25 ` [OOPS] 2.5.69-mm6 Sami Nieminen
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=873cjbjp0b.fsf@lapper.ihatent.com \
--to=alexh@ihatent.com \
--cc=akpm@digeo.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.com \
--cc=zwane@linuxpower.ca \
/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