From: Thomas Schlichter <schlicht@uni-mannheim.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test8-mm1
Date: Tue, 21 Oct 2003 00:30:39 +0200 [thread overview]
Message-ID: <200310210030.41121.schlicht@uni-mannheim.de> (raw)
In-Reply-To: <20031020151713.149bba88.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
On Tuesday 21 October 2003 00:17, Andrew Mortonwrote:
> Thomas Schlichter <schlicht@uni-mannheim.de> wrote:
> > On Monday 20 October 2003 23:48, Andrew Morton wrote:
> > > A colleague here has discovered that this crash is repeatable, but goes
> > > away when the radeon driver is disabled.
> > >
> > > Are you using that driver?
> >
> > No, I'm not... I use the vesafb driver. Do you think disabling this could
> > cure the Oops?
>
> It might. Could you test it please?
I will, but currently I compile 2.6.0-test8. I want to try if this works...
I also want to try test8-mm1 without the -Os patch, you never know... ;-)
> There's nothing in -mm which touches the inode list management code, so a
> random scribble or misbehaving driver is likely.
Yes, or some part of the kernel compiled false...
(After some problems with erlier gcc's I don't trust my curent 3.3.1 that
much...)
> > Btw. a similar Oops at the same place occours when the uhci-hcd module is
> > unloaded...
>
> How similar?
Very similar (I think it came from deactivate_super(), too), but it seems not
to be logged...
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-20 22:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 9:05 2.6.0-test8-mm1 Andrew Morton
2003-10-20 11:18 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-20 15:32 ` 2.6.0-test8-mm1 John Cherry
2003-10-20 16:11 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-20 21:48 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-20 22:01 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-20 22:17 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-20 22:30 ` Thomas Schlichter [this message]
2003-10-21 0:43 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 0:14 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21 0:27 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-21 0:46 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21 1:56 ` 2.6.0-test8-mm1 Andrew Morton
2003-10-21 2:54 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21 3:49 ` 2.6.0-test8-mm1 Jeremy Fitzhardinge
2003-10-21 8:39 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 17:47 ` 2.6.0-test8-mm1 James Simmons
2003-10-21 20:23 ` 2.6.0-test8-mm1 Helge Hafting
2003-10-21 20:36 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 20:42 ` 2.6.0-test8-mm1 James Simmons
2003-10-21 22:53 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 23:27 ` 2.6.0-test8-mm1 Robert Love
2003-10-22 2:46 ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-20 19:21 ` [BUG] 2.6.0-test8-mm1 Ramón Rey Vicente
2003-10-20 20:10 ` Andrew Morton
2003-10-20 21:53 ` Ramón Rey Vicente
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=200310210030.41121.schlicht@uni-mannheim.de \
--to=schlicht@uni-mannheim.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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