[Qemu-devel] [Bug 571432] Re: qemu-system-arm crashed with SIGSEGV in subpage_register()

2013-02-14 Thread Peter Maydell
Closing as invalid for QEMU because it's an Incomplete bug against an ancient QEMU version. ** Changed in: qemu Status: Incomplete => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/571

[Qemu-devel] [Bug 571432] Re: qemu-system-arm crashed with SIGSEGV in subpage_register()

2012-09-09 Thread Launchpad Bug Tracker
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qemu-kvm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/571

[Qemu-devel] [Bug 571432] Re: qemu-system-arm crashed with SIGSEGV in subpage_register()

2012-07-10 Thread Peter Maydell
This bug doesn't seem to have any reproduction instructions, and at least some of the command lines seem to be asking for 512MB of RAM on a versatilepb model, which isn't supported and will crash the guest unhelpfully. I'm marking it 'incomplete' for QEMU... ** Changed in: qemu Status: New

[Qemu-devel] [Bug 571432] Re: qemu-system-arm crashed with SIGSEGV in subpage_register()

2010-07-30 Thread cmchao
The base address is a little strange By your StackTrace.log, the base address, passed into smc91c111_init, is 0x40CC28C0. But this address should be 0x1001000, hard-coded in source code. -- qemu-system-arm crashed with SIGSEGV in subpage_register() https://bugs.launchpad.net/bugs/571432 You r

[Qemu-devel] [Bug 571432] Re: qemu-system-arm crashed with SIGSEGV in subpage_register()

2010-06-26 Thread sam tygier
i had a try with qemu 0.12.4+noroms-0ubuntu3 but it did not help -- qemu-system-arm crashed with SIGSEGV in subpage_register() https://bugs.launchpad.net/bugs/571432 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New St

[Qemu-devel] [Bug 571432] Re: qemu-system-arm crashed with SIGSEGV in subpage_register()

2010-06-26 Thread sam tygier
looks like i dont have much choice of nic on arm. s...@oberon:/data/beagleboard/ubuntu-lucid/build/qemu-test2$ qemu-system-arm -net nic,model=? qemu: Supported NIC models: smc91c111 s...@oberon:/data/beagleboard/ubuntu-lucid/build/qemu-test2$ qemu-system-x86_64 -net nic,model=? qemu: Supported N

[Qemu-devel] [Bug 571432] Re: qemu-system-arm crashed with SIGSEGV in subpage_register()

2010-06-26 Thread sam tygier
the actual qemu output from: qemu-system-arm -M versatilepb -cpu cortex-a8 -kernel qemu-vmlinuz -no-reboot -nographic -drive file=qemu-armel-201006261210.img,aio=native,cache=none -m 256 -net nic,model=rtl8139 -append "console=ttyAMA0,115200n8 root=/dev/sda rw mem=256M devtmpfs.mount=0 init=/bin

[Qemu-devel] [Bug 571432] Re: qemu-system-arm crashed with SIGSEGV in subpage_register()

2010-06-26 Thread sam tygier
that did not seem to help: I: linux-image-2.6.32.11-l13_1.0lucid_armel.deb download complete I: Setting up serial tty in image I: Getting Virtual Machine kernel from the server I: Switching to Virtual Machine for second stage processing Adding `local diversion of /usr/sbin/invoke-rc.d to /usr/sbi

[Qemu-devel] [Bug 571432] Re: qemu-system-arm crashed with SIGSEGV in subpage_register()

2010-06-24 Thread Serge Hallyn
** Changed in: qemu-kvm (Ubuntu) Status: New => Incomplete -- qemu-system-arm crashed with SIGSEGV in subpage_register() https://bugs.launchpad.net/bugs/571432 You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. Status in QEMU: New S

[Qemu-devel] [Bug 571432] Re: qemu-system-arm crashed with SIGSEGV in subpage_register()

2010-06-24 Thread Serge Hallyn
Does boot succeed if you add -net nic,model=rtl8139 to your qemu-system-arm arguments? ** Also affects: qemu Importance: Undecided Status: New -- qemu-system-arm crashed with SIGSEGV in subpage_register() https://bugs.launchpad.net/bugs/571432 You received this bug notification b