Hello,
My kernal gets panick when I insert my kernel module inside. I have
with me same version of UML kernel compiled and running. I have read
many articles on how to debug kernel module using UML, but they all
work if your insmod is successful. Because if your insmod is
successful then only y
On Wed, 24 Oct 2007 11:04:03 -0400
Jeff Dike <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 23, 2007 at 02:08:16PM +0800, WANG Cong wrote:
> > $ ./linux ubd0=~/Download/Fedora7-x86-root_fs root=/dev/ubd0
> >
> > But it failed and the failure log was:
> >
> > Core dump limits :
> > soft - 0
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
fruity wrote:
> What do you mean more recent?
2.6.18 was released in September 2006.
> I'm using 2.6.18.8 for host and 2.6.18 for
> guest, the host kernel works fine(I should recompile it and put a bit
> more debug in it) is the 32bit guest that doe
On Tue, Oct 23, 2007 at 02:08:16PM +0800, WANG Cong wrote:
> $ ./linux ubd0=~/Download/Fedora7-x86-root_fs root=/dev/ubd0
>
> But it failed and the failure log was:
>
> Core dump limits :
> soft - 0
> hard - NONE
> Checking that ptrace can change system call numbers...check_ptrac
On Wed, Oct 24, 2007 at 03:22:50PM +0200, Dominique Quatravaux wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Steps to reproduce:
>
>1. at the shell prompt, type "gdb /bin/ls"
>2. type "run"
>
> The problem appears on 2.6.18.1-bb2 and 2.6.22.9 for amd64. i386
> 2.6.22.9 see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steps to reproduce:
1. at the shell prompt, type "gdb /bin/ls"
2. type "run"
The problem appears on 2.6.18.1-bb2 and 2.6.22.9 for amd64. i386
2.6.22.9 seems to be immune.
We get stacktrace:
[42949389.79] Kernel panic - not syncing: get_fp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
What do you mean more recent? I'm using 2.6.18.8 for host and 2.6.18 for
guest, the host kernel works fine(I should recompile it and put a bit
more debug in it) is the 32bit guest that does not wanna run.
Do you mean I should use a 2.6.16 as the gues
