linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 20 Oct 2003 18:11:10 +0200	[thread overview]
Message-ID: <200310201811.18310.schlicht@uni-mannheim.de> (raw)
In-Reply-To: <20031020020558.16d2a776.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 3088 bytes --]

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
EFLAGS: 00010203
EIP is at invalidate_list+0x25/0xd3
eax: cded1e00   ebx: c13a80c0   ecx: c02e83a0   edx: cf35c000
esi: 00000000   edi: cf35df38   ebp: 00000000   esp: cf35df10
ds: 007b   es: 007b   ss: 0068
Process exportfs (pid: 1029, threadinfo=cf35c000 task=cefac0c0)
Stack: 00000000 00000000 cded1e00 cf35c000 cf35df38 cffe7c88 c0163d22 c02e8390
       cded1e00 cf35df38 cf35df38 cf35df38 cd584980 cded1e00 c02e8640 cffe7c88
       c01542f9 cded1e00 0000000e cf35c000 d1a2fde0 c0154bca cded1e00 cded1e00
Call Trace:
 [invalidate_inodes+62/162] invalidate_inodes+0x3e/0xa2
 [generic_shutdown_super+109/375] generic_shutdown_super+0x6d/0x177
 [kill_anon_super+14/56] kill_anon_super+0xe/0x38
 [deactivate_super+82/144] deactivate_super+0x52/0x90
 [__fput+228/235] __fput+0xe4/0xeb
 [sys_nfsservctl+257/267] sys_nfsservctl+0x101/0x10b
 [syscall_call+7/11] syscall_call+0x7/0xb

Code: fb ff 5b 5e 5f c3 55 31 ed 57 56 53 50 50 8b 44 24 1c 8b 7c 24 24 c7 04 
24
 <6>note: exportfs[1029] exited with preempt_count 2
bad: scheduling while atomic!
Call Trace:
 [schedule+60/1207] schedule+0x3c/0x4b7
 [unmap_vmas+336/471] unmap_vmas+0x150/0x1d7
 [exit_mmap+104/339] exit_mmap+0x68/0x153
 [mmput+123/184] mmput+0x7b/0xb8
 [do_exit+345/836] do_exit+0x159/0x344
 [do_divide_error+0/167] do_divide_error+0x0/0xa7
 [do_page_fault+784/1105] do_page_fault+0x310/0x451
 [update_process_times+41/47] update_process_times+0x29/0x2f
 [update_wall_time+11/51] update_wall_time+0xb/0x33
 [do_timer+76/193] do_timer+0x4c/0xc1
 [do_timer_interrupt+55/224] do_timer_interrupt+0x37/0xe0
 [timer_interrupt+40/71] timer_interrupt+0x28/0x47
 [rcu_process_callbacks+203/220] rcu_process_callbacks+0xcb/0xdc
 [tasklet_action+58/89] tasklet_action+0x3a/0x59
 [profile_hook+28/49] profile_hook+0x1c/0x31
 [do_page_fault+0/1105] do_page_fault+0x0/0x451
 [error_code+47/56] error_code+0x2f/0x38
 [invalidate_list+37/211] invalidate_list+0x25/0xd3
 [invalidate_inodes+62/162] invalidate_inodes+0x3e/0xa2
 [generic_shutdown_super+109/375] generic_shutdown_super+0x6d/0x177
 [kill_anon_super+14/56] kill_anon_super+0xe/0x38
 [deactivate_super+82/144] deactivate_super+0x52/0x90
 [__fput+228/235] __fput+0xe4/0xeb
 [sys_nfsservctl+257/267] sys_nfsservctl+0x101/0x10b
 [syscall_call+7/11] syscall_call+0x7/0xb


It just worked smoothly with 2.6.0-test7-mm1!

Regards
   Thomas

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-10-20 16:11 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 ` Thomas Schlichter [this message]
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         ` 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=200310201811.18310.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