From: Srihari Vijayaraghavan <harisri@bigpond.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-pre10aa1 oops report (was Re: Linux-2.4.20-pre8-aa2 oops report. [solved])
Date: Wed, 16 Oct 2002 00:13:02 +1000 [thread overview]
Message-ID: <200210160013.02220.harisri@bigpond.com> (raw)
In-Reply-To: <200210152305.32641.harisri@bigpond.com>
Hello,
> That precisely is the reason. The bad news is that system crashes when
> agpgart and radeon are compiled as modules, and the good news is that I am
> unable to crash it when they are not.
My goodness, I have spoken too early I guess. The -aa kernel crashes whether
agpgart and radeon are modules or not.
> Mainline (2.4.20-pre10) is stable when agpgart and radeon are compiled as
> modules.
That holds true still.
> The problem is much easier to reproduce than I thought, just log in and log
> out of XFree86/Gnome few times (3 or more times in my case) is more than
> adequate to crash it.
That is still the case.
--
Hari
harisri@bigpond.com
next prev parent reply other threads:[~2002-10-15 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 1:08 2.4.20-pre10aa1 oops report (was Re: Linux-2.4.20-pre8-aa2 oops report. [solved]) harisri
2002-10-15 13:05 ` Srihari Vijayaraghavan
2002-10-15 14:13 ` Srihari Vijayaraghavan [this message]
2002-10-16 5:06 ` 2.4.20-pre10aa1 oops report (was Re: Linux-2.4.20-pre8-aa2 oops report. [solved]) [solved2? ac97] Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2002-10-05 2:47 Linux-2.4.20-pre8-aa2 oops report Srihari Vijayaraghavan
2002-10-10 1:26 ` Linux-2.4.20-pre8-aa2 oops report. [solved] Andrea Arcangeli
2002-10-10 10:17 ` Srihari Vijayaraghavan
2002-10-13 1:53 ` 2.4.20-pre10aa1 oops report (was Re: Linux-2.4.20-pre8-aa2 oops report. [solved]) Srihari Vijayaraghavan
2002-10-13 22:42 ` Andrea Arcangeli
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=200210160013.02220.harisri@bigpond.com \
--to=harisri@bigpond.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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