From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Kernel mode fault at addr 0x48965000, ip0x400e51a4
Date: Tue, 13 Jan 2004 19:14:27 +0100 [thread overview]
Message-ID: <200401131914.27510.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <Pine.LNX.4.58.0401120702070.4503@silk.corp.fedex.com>
Alle 00:04, lunedì 12 gennaio 2004, Jeff Chua ha scritto:
> On Sun, 11 Jan 2004, BlaisorBlade wrote:
> > Also, Jeff, when you compiled LVM, did you compile it as module(as you
> > speak about initrd) or statically?
>
> LVM dm-mod (device mapper) is module.
>
> If I don't load this and not start vgscan, mount lvm devices, I don't see
> klog segmentation fault.
Probably building into the kernel that module would work-around your problem.
LVM is loaded at startup before klog, I guess, right?
In fact the bug is likely to be with handling of modules, as they go in a
different kernel memory area; *maybe* they are in vmalloc'ed memory.
Bye
--
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.23/2.6.0 on an i686; Linux registered user n. 292729
EOSIGN
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-01-13 18:13 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 16:32 [uml-devel] Kernel mode fault at addr 0x48965000, ip 0x400e51a4 Jeff Chua
[not found] ` <200401061718.i 06HILtd002620@ccure.user-mode-linux.org>
[not found] ` <200401060258.i 062wuFI023117@ccure.user-mode-linux.org>
[not found] ` <200401061718.i 06HILtd002620@ccure.user-mode-linux.org>
2003-12-30 18:06 ` 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 [this message]
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=200401131914.27510.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--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