All of lore.kernel.org
 help / color / mirror / Atom feed
From: "D. Bahi" <dbahi@enterasys.com>
To: uml devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] UML 2.4 shmem.c changes? panic w/ backtrace
Date: Tue, 23 Nov 2004 11:01:57 -0500	[thread overview]
Message-ID: <41A35EF5.4080302@enterasys.com> (raw)

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

hello uml folks,

i know things are hot and heavy in 2.6 but i hope
somebody can spare a thought about this panic i'm
struggling to understand.

i know UML touches shmem.c - lightly and i'd like
to think it's a kernel bug w/ shmem but we run this
2.4.20 kernel on hardware with the same applications
and do not see this failure.

host is RH9 2.4.20-31.9 + skas
guest is UML 2.4.26-3um
backported to 2.4.20-montavista 3.1 pro

(gdb) bt
#0  0x08167aca in nanosleep () at proc_fs.h:154
#1  0x081679cb in sleep () at proc_fs.h:154
#2  0x080e3bc1 in stop () at user_util.c:52
#3  0x080e37ec in panic_waitonerr (self=0x81f77cc, unused1=0, 
unused2=0x8206120) at um_arch.c:457
#4  0x0805eeb2 in notifier_call_chain (n=0xfffffffc, val=0, v=0x8206120) 
at sys.c:131
#5  0x08053bb3 in panic (fmt=0x81c99c0 "Kernel mode fault at addr 0x%lx, 
ip 0x%lx") at panic.c:69
#6  0x080e2efd in segv (address=0, ip=1078054417, is_write=0, is_user=0, 
sc=0x30da82a4) at trap_kern.c:149
#7  0x080e31cd in segv_handler (sig=11, regs=0x30da82a4) at trap_user.c:74
#8  0x080e5611 in sig_handler_common_skas (sig=11, sc_ptr=0x58) at 
trap_user.c:35
#9  0x080e31ee in sig_handler (sig=11, sc={gs = 0, __gsh = 0, fs = 0, 
__fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 49168, edi = 336, esi = 
818643476, ebp = 819657132, esp = 819657124, ebx = 0, edx = 42, ecx = 
818643560, eax = 0, trapno = 14, err = 4, eip = 134682879, cs = 35, 
__csh = 0, eflags = 2163270, esp_at_signal = 819657124, ss = 43, __ssh = 
0, fpstate = 0x0, oldmask = 134217728, cr2 = 0}) at trap_user.c:109
#10 <signal handler called>
#11 shmem_block (index=42, page=0x0, direct=0x0, indirect=0x30cb8268) at 
shmem.c:149
#12 0x08071984 in shmem_swp_entry (info=0x0, index=42, page=0x0) at 
shmem.c:182
#13 0x08071aa5 in shmem_truncate (inode=0x30cb8100) at shmem.c:349
#14 0x08064772 in vmtruncate (inode=0x30cb8100, offset=172368) at 
memory.c:1128
#15 0x080898b9 in inode_setattr (inode=0x30cb8100, attr=0x30dafb24) at 
attr.c:67
#16 0x08071c16 in shmem_notify_change (dentry=0x0, attr=0x30dafb24) at 
shmem.c:398
#17 0x08089a3d in notify_change (dentry=0x30ed4878, attr=0x30dafb24) at 
attr.c:132
#18 0x08073f4a in do_truncate (dentry=0x30ed4878, length=172368) at 
open.c:113
#19 0x080751bf in do_sys_ftruncate (fd=0, length=172368, small=1) at 
open.c:220
#20 0x08073f8f in sys_ftruncate (fd=21, length=172368) at open.c:229
#21 0x080e5162 in execute_syscall_skas (r=0x2a) at syscall_kern.c:28
#22 0x080e5192 in handle_syscall (regs=0x30da82a4) at syscall_user.c:26
#23 0x080e43c1 in handle_trap (pid=5308, regs=0x30da82a4) at process.c:85
#24 0x080e4693 in userspace (regs=0x30da82a4) at process.c:160
#25 0x080e4dae in fork_handler (sig=10) at process_kern.c:104
#26 <signal handler called>
#27 0x0815a631 in kill () at proc_fs.h:154
#28 0x080e8708 in os_usr1_process (pid=5304) at process.c:98
#29 0x080e4706 in new_thread (stack=Cannot access memory at address 0x8
) at process.c:197

-- 
db


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

             reply	other threads:[~2004-11-23 16:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 16:01 D. Bahi [this message]
2004-11-23 20:13 ` [uml-devel] UML 2.4 shmem.c changes? panic w/ backtrace Blaisorblade
2004-11-24  2:42 ` Jeff Dike
2005-02-24 23:13   ` D. Bahi
2005-02-28 19:44     ` Jeff Dike
2005-03-02 14:07       ` Blaisorblade
2005-03-02 17:01         ` Blaisorblade
2005-03-02 17:03           ` D. Bahi

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=41A35EF5.4080302@enterasys.com \
    --to=dbahi@enterasys.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.