From: Jeff Chua <jchua@fedex.com>
To: UserModeLinux <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] Kernel mode fault at addr 0x48965000, ip 0x400e51a4
Date: Tue, 30 Dec 2003 00:32:34 +0800 (SGT) [thread overview]
Message-ID: <Pine.LNX.4.58.0312300027110.24938@silk.corp.fedex.com> (raw)
uml-patch-2.4.22-5 works fine, but newer patches fail during boot
Starting daemons: syslogd klogd inetd namedKernel panic: Kernel mode fault
at addr 0x48965000, ip 0x400e51a4
The following works ...
uml-patch-2.4.22-5
host 2.4.24-pre2
The following doesn't work ...
uml-patch-2.4.23-1
uml-patch-2.4.22-6
uml-patch-2.4.22-7
The error is repeatable. If I don't mount lvm disks, and only uses initrd
ramdisk, the problem doesn't appear!
Thanks,
Jeff
[ jchua@fedex.com ]
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&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
next reply other threads:[~2003-12-29 16:34 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 16:32 Jeff Chua [this message]
[not found] ` <200401061718.i 06HILtd002620@ccure.user-mode-linux.org>
[not found] ` <200401061718.i 06HILtd002620@ccure.user-mode-linux.org>
[not found] ` <200401060258.i 062wuFI023117@ccure.user-mode-linux.org>
2003-12-30 18:06 ` [uml-devel] Kernel mode fault at addr 0x48965000, ip 0x400e51a4 BlaisorBlade
2004-01-01 6:14 ` Jeff Chua
2004-01-06 2:58 ` Jeff Dike
2004-01-06 15:57 ` Johannes Formann
2004-01-06 17:18 ` Jeff Dike
2004-01-06 18:11 ` Johannes Formann
2004-01-06 18:18 ` BlaisorBlade
2004-01-06 18:49 ` Johannes Formann
2004-01-06 16:33 ` [uml-devel] Kernel mode fault at addr 0x48965000, ip0x400e51a4 stian
2004-01-06 19:06 ` Johannes Formann
2004-01-06 19:40 ` Johannes Formann
2004-01-06 19:34 ` Jeff Chua
2004-01-06 21:00 ` Johannes Formann
2004-01-06 20:47 ` Jeff Chua
2004-01-06 21:47 ` Johannes Formann
2004-01-06 21:32 ` Jeff Chua
2004-01-06 21:55 ` Johannes Formann
2004-01-06 21:39 ` Jeff Chua
2004-01-07 5:53 ` Johannes Formann
2004-01-07 17:10 ` Jeff Chua
2004-01-07 19:18 ` Johannes Formann
2004-01-07 19:25 ` BlaisorBlade
2004-01-10 20:33 ` Johannes Formann
2004-01-11 12:34 ` BlaisorBlade
2004-01-11 15:25 ` Johannes Formann
2004-01-11 15:46 ` BlaisorBlade
2004-01-11 18:04 ` Johannes Formann
2004-02-21 11:23 ` Johannes Formann
2004-02-21 15:34 ` BlaisorBlade
2004-01-11 23:04 ` Jeff Chua
2004-01-13 18:14 ` BlaisorBlade
2004-01-06 20:55 ` Jeff Dike
2004-03-04 2:16 ` Jeff Dike
2004-03-04 22:46 ` [uml-devel] compile issue when removing CONFIG_MODE_TT roland
2004-01-06 19:07 ` [uml-devel] Kernel mode fault at addr 0x48965000, ip 0x400e51a4 BlaisorBlade
2004-01-06 18:00 ` Jeff Chua
2004-01-06 16:15 ` stian
2004-01-07 17:08 ` Jeff Chua
2004-01-07 19:18 ` Adam Heath
2004-01-08 17:34 ` [uml-devel] [tracked down] Kernel mode fault with /dev/kmem BlaisorBlade
2004-03-04 2:16 ` [uml-devel] Kernel mode fault at addr 0x48965000, ip 0x400e51a4 Jeff Dike
2004-03-04 2:19 ` Jeff Chua
2004-03-07 10:54 ` BlaisorBlade
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=Pine.LNX.4.58.0312300027110.24938@silk.corp.fedex.com \
--to=jchua@fedex.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.