[6999] in testers
Re: 9.4.4 linux: panel, vts, etc.
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed May 18 12:40:16 2005
From: Greg Hudson <ghudson@MIT.EDU>
To: John Hawkinson <jhawk@mit.edu>
Cc: testers@mit.edu
In-Reply-To: <20050518054116.GX23850@multics.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Wed, 18 May 2005 12:39:49 -0400
Message-Id: <1116434389.3458.199.camel@egyptian-gods.mit.edu>
Mime-Version: 1.0
On Wed, 2005-05-18 at 01:41 -0400, John Hawkinson wrote:
> Here's the messages file, indicating frequency, etc.
> Not clear to me what the trigger was.
The following suggests a possible AFS problem:
May 17 17:42:43 opus kernel: post_create: no inode, dir (dev=afs, ino=723781499)
The first oops in the message log occurs four seconds later:
Unable to handle kernel NULL pointer dereference at virtual address 00000014
printing eip:
c01c023d
*pde = 1cb21067
Oops: 0000 [#1]
Modules linked in: md5 ipv6 libafs(U) i2c_dev i2c_core sunrpc dm_mod button battery ac joydev uhci_hcd snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore 3c59x floppy sg ext3 jbd aic7xxx sd_mod scsi_mod
CPU: 0
EIP: 0060:[<c01c023d>] Tainted: PF VLI
EFLAGS: 00010246 (2.6.9-5.0.5.EL)
EIP is at may_link+0xb2/0xd1
eax: 00000000 ebx: d2975a80 ecx: 00140000 edx: 00140000
esi: 00000400 edi: dc9d6f30 ebp: 00000001 esp: dc9d6ef0
ds: 007b es: 007b ss: 0068
Process wnck-applet (pid: 5125, threadinfo=dc9d6000 task=dcaed7d0)
Stack: 00000000 d2975a80 00000001 00000000 00000000 cef6ce90 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
de183400 de183480 fffffff0 de183400 d7f30800 cef6ce90 c0173d10 cef6ce90
Call Trace:
[<c0173d10>] vfs_unlink+0x181/0x1d8
[<c0173e1b>] sys_unlink+0xb4/0x13b
[<c0154a30>] unmap_vma_list+0xe/0x17
[<c0154ddf>] do_munmap+0x1c8/0x1d2
[<c0301d43>] syscall_call+0x7/0xb
Code: 83 fd 02 74 09 eb 0e be 00 04 00 00 eb 16 be 00 00 20 00 eb 0f 55 68 55 82 31 c0 e8 83 fd f5 ff 31 c0 eb 1c 8b 04 24 8b 5c 24 04 <8b> 50 14 0f b7 48 18 8b 43 0c 8d 5c 24 08 53 56 e8 d0 e8 ff ff
> This doesn't really explain the failure of xlogin to restart,
> since it had been oops-ing for quite a while before the
> test login of mine.
It's possible that the problems are unrelated, but corrupted kernel
memory can certainly interfere with processes getting started.
