All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Zimmerman <mdz@debian.org>
To: Jeff Dike <jdike@addtoit.com>
Cc: Bill Allombert <allomber@math.u-bordeaux.fr>,
	user-mode-linux-devel@lists.sourceforge.net,
	176485@bugs.debian.org
Subject: [uml-devel] Re: Panic with slirp transport and gcc 3.3
Date: Tue, 13 Jan 2004 10:51:57 -0800	[thread overview]
Message-ID: <20040113185156.GW1514@alcor.net> (raw)
In-Reply-To: <200401131730.i0DHUMhg002358@ccure.user-mode-linux.org>

On Tue, Jan 13, 2004 at 12:30:22PM -0500, Jeff Dike wrote:

> allomber@math.u-bordeaux.fr said:
> >  Kernel panic: Segfault with no mm
> > Without the eth0=slirp parameter, there are no kernel panic. 
> 
> Can someone get a stack trace from this?

Certainly (this is from 2.4.23-1um).  Seems like something goes weird with
procfs, but I've no idea why this only happens with slirp (and newer gcc for
that matter).

(gdb) bt
#0  panic (fmt=0x0) at panic.c:58
#1  0xa00d769b in segv (address=8, ip=2685922193, is_write=0, is_user=0, 
    sc=0x0) at trap_kern.c:144
#2  0xa00d7af5 in segv_handler (sig=11, regs=0xa0350274) at trap_user.c:67
#3  0xa00df411 in sig_handler_common_skas (sig=11, sc_ptr=0x58)
    at trap_user.c:33
#4  0xa00d7c05 in sig_handler (sig=0, sc=
      {gs = 0, __gsh = 0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 0, edi = 2687843188, esi = 2688540673, ebp = 2687843100, esp = 2687843028, ebx = 2687843188, edx = 2687843188, ecx = 2687827968, eax = 0, trapno = 14, err = 4, eip = 2684641864, cs = 35, __csh = 0, eflags = 2163202, esp_at_signal = 2687843028, ss = 43, __ssh = 0, fpstate = 0x0, oldmask = 0, cr2 = 8})
    at trap_user.c:103
#5  <signal handler called>
#6  0xa0046248 in link_path_walk (name=0xa03fe001 "dev", nd=0xa0353b74)
    at namei.c:462
#7  0xa004674e in path_walk (name=0x0, nd=0xa0353b74) at namei.c:659
#8  0xa0046919 in path_lookup (path=0xa03fe000 "/dev", flags=2687843188, 
    nd=0xa0353b74) at namei.c:748
#9  0xa0047754 in sys_mkdir (pathname=0x0, mode=448) at namei.c:1345
#10 0xa000eafa in prepare_namespace () at init/do_mounts.c:917
#11 0xa000e613 in init (unused=0x0) at init/main.c:580
#12 0xa00d22f9 in run_kernel_thread (fn=0xa000e600 <init>, arg=0x0, 
#13 0xa00de930 in new_thread_handler (sig=10) at process_kern.c:70
#14 <signal handler called>
(gdb) i sym 2685922193
kill + 17 in section .text
(gdb) i line *2685922193
Line 155 of "proc_fs.h" starts at address 0xa0178e94 <svc_proc_register+68>
   and ends at 0xa01c3913.
(gdb) up 6
#6  0xa0046248 in link_path_walk (name=0xa03fe001 "dev", nd=0xa0353b74)
    at namei.c:462
462             inode = nd->dentry->d_inode;
(gdb) print *nd
$1 = {dentry = 0x0, mnt = 0x0, last = {
    name = 0x8124 <Address 0x8124 out of bounds>, len = 1, hash = 2686526256}, 
  flags = 16, last_type = 1}

-- 
 - mdz


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2004-01-13 18:52 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-20  1:13 [uml-devel] 2.4.22-[67] problems Matt Zimmerman
2003-12-20 17:14 ` Jeff Dike
2003-12-21  0:47   ` Matt Zimmerman
2003-12-21 15:58     ` BlaisorBlade
2003-12-21 22:40       ` Matt Zimmerman
2003-12-21 23:16         ` Matt Zimmerman
2003-12-22  0:25           ` Jeff Dike
2003-12-22  4:08             ` Matt Zimmerman
2003-12-22  5:49               ` Daniel Jacobowitz
2003-12-22  9:08                 ` Matt Zimmerman
2004-01-05 17:51                   ` Adam Heath
2004-01-05 18:10                     ` Matt Zimmerman
2003-12-24 12:48         ` BlaisorBlade
2003-12-21  0:52   ` Matt Zimmerman
2003-12-21  1:06     ` Matt Zimmerman
2003-12-28  9:33       ` Matt Zimmerman
2003-12-28  9:51         ` Matt Zimmerman
2003-12-28  9:52           ` Matt Zimmerman
2004-01-06  2:59             ` Jeff Dike
2003-12-28 10:12           ` Matt Zimmerman
2003-12-28 11:30             ` Matt Zimmerman
2003-12-30 18:43               ` Resolution (Re: [uml-devel] 2.4.22-[67] problems) Matt Zimmerman
2004-01-06  2:58                 ` Jeff Dike
2004-01-06  7:41                   ` Nuno Silva
2004-01-06  8:02                     ` Matt Zimmerman
2004-01-06  8:20                       ` Nuno Silva
2004-01-06  8:47                         ` Nuno Silva
2004-01-06  9:20                     ` Nuno Silva
2004-01-06 17:13                       ` Matt Zimmerman
2004-01-09  7:22                         ` Nuno Silva
2004-01-08  7:07                   ` Matt Zimmerman
2004-01-12 18:36                     ` [uml-devel] Panic with slirp transport and gcc 3.3 Matt Zimmerman
2004-01-13 15:25                       ` [uml-devel] " Bill Allombert
2004-01-13 17:30                         ` Jeff Dike
2004-01-13 17:44                           ` Bill Allombert
2004-01-13 18:51                           ` Matt Zimmerman [this message]
2004-01-16  2:38                             ` Jeff Dike
2004-01-16  2:38                               ` Matt Zimmerman
2004-01-16 20:04                                 ` Jeff Dike
2004-01-16 19:49                                   ` Matt Zimmerman
2004-01-17  0:42                                     ` Matt Zimmerman
2003-12-21  1:29   ` [uml-devel] 2.4.22-[67] problems Matt Zimmerman
2003-12-20 19:05 ` Nick Craig-Wood

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=20040113185156.GW1514@alcor.net \
    --to=mdz@debian.org \
    --cc=176485@bugs.debian.org \
    --cc=allomber@math.u-bordeaux.fr \
    --cc=jdike@addtoit.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.