[Qemu-devel] QEMU fails with 2.6.0-test3-bk9 ...

[Qemu-devel] QEMU fails with 2.6.0-test3-bk9 ...

[Herbert Pötzl]

Hi Fabrice!

qemu 0.4.3 and the CVS version, both fail on
linux 2.6.0-test3-bk9 ...

the cvs version:

Program received signal SIGSEGV, Segmentation fault.
0xa801e76a in disas_insn (s=Cannot access memory at address 0x100050
) at /home/qemu/qemu.cvs/cpu-all.h:26
26	    return *(uint8_t *)ptr;
(gdb) where
#0  0xa801e76a in disas_insn (s=Cannot access memory at address 0x100050
) at /home/qemu/qemu.cvs/cpu-all.h:26
#1  0xbffff2e0 in ?? ()
Cannot access memory at address 0x100000

and the 0.4.3 release:

Program received signal SIGSEGV, Segmentation fault.
0xa83a86c0 in code_gen_buffer ()
(gdb) where
#0  0xa83a86c0 in code_gen_buffer ()
#1  0xa8004fac in cpu_x86_exec (env1=0x0) at cpu-exec.c:338
#2  0x00023800 in ?? ()
#3  0x1b7e847f in ?? ()
Cannot access memory at address 0xab1e93e2

kernel config:

CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_EXPERIMENTAL=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_EMBEDDED=y
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_MODULES=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_KMOD=y
CONFIG_X86_PC=y
CONFIG_MPENTIUMII=y
CONFIG_QEMU=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_NOHIGHMEM=y
CONFIG_MTRR=y
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_ELF=y
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_LBD=y
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IPV6_SCTP__=y
CONFIG_NETDEVICES=y
CONFIG_DUMMY=y
CONFIG_NET_ETHERNET=y
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_SOUND_GAMEPORT=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_JBD=y
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
CONFIG_JFS_FS=y
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_QUOTA=y
CONFIG_QFMT_V1=y
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
CONFIG_PROC_FS=y
CONFIG_DEVPTS_FS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_X86_BIOS_REBOOT=y

[Qemu-devel] Re: QEMU fails with 2.6.0-test3-bk9 ...

[Herbert Pötzl]

sorry, false alarm, although qemu/vl
error reporting could be a little bit 
more informative ;)

arch/i386/vmlinux.lds.S  was moved to
arch/i386/kernel/vmlinux.lds.S between
2.6.0-test3-bk6 and 2.6.0-test3-bk7 and
Rusty's patch needed an update ...

now everything is fine again ...

am I still subscribed to the qemu mailing
list? is the list down? didn't get a
message since Aug 11 ... 

best,
Herbert

On Fri, Aug 22, 2003 at 03:13:21AM +0200, Herbert Pötzl wrote:
> Hi Fabrice!
> 
> qemu 0.4.3 and the CVS version, both fail on
> linux 2.6.0-test3-bk9 ...
> 
> the cvs version:
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0xa801e76a in disas_insn (s=Cannot access memory at address 0x100050
> ) at /home/qemu/qemu.cvs/cpu-all.h:26
> 26	    return *(uint8_t *)ptr;
> (gdb) where
> #0  0xa801e76a in disas_insn (s=Cannot access memory at address 0x100050
> ) at /home/qemu/qemu.cvs/cpu-all.h:26
> #1  0xbffff2e0 in ?? ()
> Cannot access memory at address 0x100000
> 
> and the 0.4.3 release:
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0xa83a86c0 in code_gen_buffer ()
> (gdb) where
> #0  0xa83a86c0 in code_gen_buffer ()
> #1  0xa8004fac in cpu_x86_exec (env1=0x0) at cpu-exec.c:338
> #2  0x00023800 in ?? ()
> #3  0x1b7e847f in ?? ()
> Cannot access memory at address 0xab1e93e2
> 
> kernel config:
> 
> CONFIG_X86=y
> CONFIG_MMU=y
> CONFIG_UID16=y
> CONFIG_GENERIC_ISA_DMA=y
> CONFIG_EXPERIMENTAL=y
> CONFIG_SWAP=y
> CONFIG_SYSVIPC=y
> CONFIG_SYSCTL=y
> CONFIG_LOG_BUF_SHIFT=14
> CONFIG_EMBEDDED=y
> CONFIG_KALLSYMS=y
> CONFIG_FUTEX=y
> CONFIG_EPOLL=y
> CONFIG_IOSCHED_NOOP=y
> CONFIG_IOSCHED_AS=y
> CONFIG_IOSCHED_DEADLINE=y
> CONFIG_MODULES=y
> CONFIG_OBSOLETE_MODPARM=y
> CONFIG_KMOD=y
> CONFIG_X86_PC=y
> CONFIG_MPENTIUMII=y
> CONFIG_QEMU=y
> CONFIG_X86_CMPXCHG=y
> CONFIG_X86_XADD=y
> CONFIG_X86_L1_CACHE_SHIFT=5
> CONFIG_RWSEM_XCHGADD_ALGORITHM=y
> CONFIG_X86_WP_WORKS_OK=y
> CONFIG_X86_INVLPG=y
> CONFIG_X86_BSWAP=y
> CONFIG_X86_POPAD_OK=y
> CONFIG_X86_GOOD_APIC=y
> CONFIG_X86_INTEL_USERCOPY=y
> CONFIG_X86_USE_PPRO_CHECKSUM=y
> CONFIG_X86_TSC=y
> CONFIG_X86_MCE=y
> CONFIG_NOHIGHMEM=y
> CONFIG_MTRR=y
> CONFIG_KCORE_ELF=y
> CONFIG_BINFMT_ELF=y
> CONFIG_BLK_DEV_LOOP=m
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_RAM_SIZE=4096
> CONFIG_BLK_DEV_INITRD=y
> CONFIG_LBD=y
> CONFIG_IDE=y
> CONFIG_BLK_DEV_IDE=y
> CONFIG_BLK_DEV_IDEDISK=y
> CONFIG_NET=y
> CONFIG_PACKET=y
> CONFIG_UNIX=y
> CONFIG_INET=y
> CONFIG_IP_MULTICAST=y
> CONFIG_IPV6_SCTP__=y
> CONFIG_NETDEVICES=y
> CONFIG_DUMMY=y
> CONFIG_NET_ETHERNET=y
> CONFIG_INPUT=y
> CONFIG_INPUT_MOUSEDEV=y
> CONFIG_INPUT_MOUSEDEV_PSAUX=y
> CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
> CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
> CONFIG_SOUND_GAMEPORT=y
> CONFIG_INPUT_KEYBOARD=y
> CONFIG_SERIAL_8250=y
> CONFIG_SERIAL_8250_CONSOLE=y
> CONFIG_SERIAL_CORE=y
> CONFIG_SERIAL_CORE_CONSOLE=y
> CONFIG_UNIX98_PTYS=y
> CONFIG_UNIX98_PTY_COUNT=256
> CONFIG_EXT2_FS=y
> CONFIG_EXT2_FS_XATTR=y
> CONFIG_EXT2_FS_POSIX_ACL=y
> CONFIG_EXT3_FS=y
> CONFIG_EXT3_FS_XATTR=y
> CONFIG_EXT3_FS_POSIX_ACL=y
> CONFIG_JBD=y
> CONFIG_FS_MBCACHE=y
> CONFIG_REISERFS_FS=y
> CONFIG_JFS_FS=y
> CONFIG_FS_POSIX_ACL=y
> CONFIG_XFS_FS=y
> CONFIG_XFS_POSIX_ACL=y
> CONFIG_QUOTA=y
> CONFIG_QFMT_V1=y
> CONFIG_QFMT_V2=y
> CONFIG_QUOTACTL=y
> CONFIG_PROC_FS=y
> CONFIG_DEVPTS_FS=y
> CONFIG_TMPFS=y
> CONFIG_RAMFS=y
> CONFIG_MSDOS_PARTITION=y
> CONFIG_NLS=y
> CONFIG_NLS_DEFAULT="iso8859-1"
> CONFIG_DEBUG_SPINLOCK_SLEEP=y
> CONFIG_X86_BIOS_REBOOT=y
> 

[Qemu-devel] QEMU config

[Fabrice Bellard]

 > am I still subscribed to the qemu mailing
 > list? is the list down? didn't get a
 > message since Aug 11 ...

I made commits the last few days - you should have received them by the 
mailing list.

BTW, I plan to rename qemu to qemu-user[-i386] and vl to qemu before 
releasing 0.4.4. I also plan to remove most command line options to 'vl' 
and to force the use of a configuration file such as:

vl linux.qemu

with linux.qemu containing:

kernel=xxxx
hda=xxxx

It is needed now to have enough flexibility for full PC simulation and 
also to simplify vl usage for novice users.

Fabrice.

[Qemu-devel] Re: QEMU config

[Herbert Pötzl]

On Fri, Aug 22, 2003 at 08:45:15AM +0200, Fabrice Bellard wrote:
> > am I still subscribed to the qemu mailing
> > list? is the list down? didn't get a
> > message since Aug 11 ...
> 
> I made commits the last few days - you should have received them by the 
> mailing list.

L Aug 11  Fabrice Bellard    20 [Qemu-devel] qemu README
L Aug 11  Fabrice Bellard    20 [Qemu-devel] qemu Makefile
L Aug 20  Fabrice Bellard    29 [Qemu-devel] qemu cpu-exec.c cpu-i386.h e 138 N F Aug 22  Herbert Pötzl     133 [Qemu-devel] QEMU fails with 2.6.0-test3-

thats all I got recently ...

> BTW, I plan to rename qemu to qemu-user[-i386] and vl to qemu before 
> releasing 0.4.4. I also plan to remove most command line options to 'vl' 
> and to force the use of a configuration file such as:

no problem with that, but could you make the
qemu-doc.html optional, as I had to comment
it out several times in a no-texi2html env?

> vl linux.qemu
> 
> with linux.qemu containing:
> 
> kernel=xxxx
> hda=xxxx
> 
> It is needed now to have enough flexibility for full PC simulation and 
> also to simplify vl usage for novice users.

what about gdb ;) ... and ... :| ... breakpoints .... :(

best,
Herbert

> Fabrice.

Re: [Qemu-devel] QEMU config

[Rusty Russell]

In message <3F45BBFB.90409@free.fr> you write:
> releasing 0.4.4. I also plan to remove most command line options to 'vl' 
> and to force the use of a configuration file such as:
> 
> vl linux.qemu
> 
> with linux.qemu containing:
> 
> kernel=xxxx
> hda=xxxx

Please don't.  Writing YA config file is always a PITA, and just
invites you to add thousands of options in the future.  I'd really
prefer a .qemurc which gets overridden by cmdline options, though.

Or at least allow "vl -" so I can echo the options in...

Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

Re: [Qemu-devel] QEMU config

[Herbert Pötzl]

On Mon, Aug 25, 2003 at 01:57:41PM +1000, Rusty Russell wrote:

[reply to original posting, covered as follow up]
]In-reply-to: Your message of "Fri, 22 Aug 2003 08:45:15 +0200."
]       	<3F45BBFB.90409@free.fr> 

so even Rusty Russel does not honor threaded mailing?
maybe this is a sign, but I do not know for what yet ...

best,
Herbert

Re: [Qemu-devel] QEMU config

[Herbert Poetzl]

Hi Rusty!

On Sat, Aug 30, 2003 at 05:51:04PM +1000, Rusty Russell wrote:
> In message <20030825171232.GC23306@www.13thfloor.at> you write:
> > On Mon, Aug 25, 2003 at 01:57:41PM +1000, Rusty Russell wrote:
> > 
> > [reply to original posting, covered as follow up]
> > ]In-reply-to: Your message of "Fri, 22 Aug 2003 08:45:15 +0200."
> > ]       	<3F45BBFB.90409@free.fr> 
> > 
> > so even Rusty Russel does not honor threaded mailing?
> > maybe this is a sign, but I do not know for what yet ...
> 
> Please explain?  I use mh under emacs, BTW.

I have to apologize, it seems that my mail system or
mua got confused, or something strange happened ...

your reply referenced <3F45BBFB.90409@free.fr> where 
my thread started as <20030822011321.GA3105@www.13thfloor.at>,
<20030822021823.GA9811@www.13thfloor.at>, and here is the
strange change <20030822123152.GA13061@www.13thfloor.at> and
<3F45BBFB.90409@free.fr>, this is the point where both
threads seem to overlap, I have no explanation, but I'm
sorry that I misinterpreted this fact ...

asking for forgiveness,
Herbert

> Thanks,
> Rusty.
> --
>   Anyone who quotes me in their sig is an idiot. -- Rusty Russell.