linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Thomas Schlichter <schlicht@uni-mannheim.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test8-mm1
Date: Mon, 20 Oct 2003 14:48:36 -0700	[thread overview]
Message-ID: <20031020144836.331c4062.akpm@osdl.org> (raw)
In-Reply-To: <200310201811.18310.schlicht@uni-mannheim.de>

Thomas Schlichter <schlicht@uni-mannheim.de> wrote:
>
> On Monday 20 October 2003 11:05, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test8/2
> >.6.0-test8-mm1
> >
> >
> > . Included a much updated fbdev patch.  Anyone who is using framebuffers,
> >   please test this.
> >
> > . Quite a large number of stability fixes.
> 
> I've got a problem with NFS!
> If the kernel NFS server (nfs-utils 1.0.6) is started I get following Oops:
> 
> Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
>  printing eip:
> c0163c36
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT
> CPU:    0
> EIP:    0060:[invalidate_list+37/211]    Not tainted VLI

A colleague here has discovered that this crash is repeatable, but goes
away when the radeon driver is disabled.  

Are you using that driver?
--
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>

  reply	other threads:[~2003-10-20 21:48 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   ` Andrew Morton [this message]
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         ` 2.6.0-test8-mm1 Thomas Schlichter
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=20031020144836.331c4062.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=schlicht@uni-mannheim.de \
    /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