From: "Bernard Johnson" <bjohnson-dated-1082612068.17fb8c@symetrix.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Kernel mode fault 2.4.26-um1
Date: Mon, 17 May 2004 12:45:20 -0600 [thread overview]
Message-ID: <c8b184$u2g$1@sea.gmane.org> (raw)
In-Reply-To: c840cm$o89$1@sea.gmane.org
I was asked in email for more information... Here is additional
information...
I'm using ttmode (have been unable to integrate the skas3 patch into a
Fedora Core kernel RPM). The host system is a Fedora Core 1 system, fully
updated, standard kernel.
The crash is completely reproducible, when I start a particular application
(behemoth ColdFusion MX 6.1). The crash happens when the guest OS is either
Fedora Core 1 or RedHat 8, so I don't believe it's related to the guest OS.
I have a kernel linux-2.4.22-um6+fedoraseg
(http://toast.debian.net/~may/umlproject/unpackaged/fedoraseg.patch) that
will run this application under guest Fedora Core 1, although, it seems to
not run under RedHat 8 guest OS.
"Bernard Johnson" <bjohnson-dated-1082612068.17fb8c@symetrix.com> wrote in
message news:c840cm$o89$1@sea.gmane.org...
> I'm getting this crash on 2.4.26-um1
>
> Breakpoint 1, panic (
> fmt=0xa01d8b00 "Kernel mode fault at addr 0x%lx, ip 0x%lx, ip 0x%lx") at
> panic.c:60
> 60 bust_spinlocks(1);
> (gdb) bt
> #0 panic (fmt=0xa01d8b00 "Kernel mode fault at addr 0x%lx, ip 0x%lx")
> at panic.c:60
> #1 0xa00d1019 in segv (address=8, ip=2685769919, is_write=0, is_user=0,
> sc=0xa4a44274) at trap_kern.c:149
> #2 0xa00d1416 in segv_handler (sig=11, regs=0xa4a44274) at trap_user.c:67
> #3 0xa00d4b3c in sig_handler_common_tt (sig=11, sc_ptr=0xa4a47d28)
> at trap_user.c:43
> #4 0xa00d14f3 in sig_handler (sig=0, sc=
> {gs = 0, __gsh = 0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh
=
> 0, edi = 2762227712, esi = 2762235236, ebp = 2762235212, esp = 2762235188,
> ebx = 0, edx = 4294901759, ecx = 2685202592, eax = 4, trapno = 14, err =
4,
> eip = 2685769919, cs = 35, __csh = 0, eflags = 66182, esp_at_signal =
> 2762235188, ss = 43, __ssh = 0, fpstate = 0x0, oldmask = 134285824, cr2 =
> 8}) at trap_user.c:101
> #5 <signal handler called>
> #6 rwsem_down_failed_common (sem=0x0, waiter=0xa4a45d64,
adjustment=-65537)
> at list.h:40
> Previous frame inner to this frame (corrupt stack?)
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-05-17 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 2:47 [uml-devel] Kernel mode fault 2.4.26-um1 Bernard Johnson
2004-05-17 18:45 ` Bernard Johnson [this message]
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='c8b184$u2g$1@sea.gmane.org' \
--to=bjohnson-dated-1082612068.17fb8c@symetrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox