Activity log for bug #1290370

Date Who What changed Old value New value Message
2014-03-10 13:46:32 prajeeth bug added bug
2014-03-10 13:48:01 prajeeth description This is a bug that i have noticed in qemu 1.7.50 as well as 1.1.50. It was the latter that forced me to clone the repository to check if this is the case with the resent version as well . The latest commit on which the bug is found is f53f3d0a00b6df39ce8dfca942608e5b6a9a4f71 on qemu.git configured with target list i386-softmmu and then make OS: FreeBSD 9.2 Text Install ISO Installed it to a qcow2 format image. ./i386-softmmu/qemu-system-i386 -hda <bsd-image> -m 2G -smp 4 -net nic -net user -monitor stdio (boot into multi-user mode)->(login to root account) I have the filebench benchmark installed on the image and when i run it the default root shell (csh) crashes with the error. [pid xxxx (csh) sigreturn eflag = 0xXXXX] Here is the piece of kernel code that is getting executed (i think) http://svnweb.freebsd.org/base/release/9.2.0/sys/i386/i386/machdep.c?view=markup#l1095 Here is a related bug https://www.virtualbox.org/ticket/458 The crash happens randomly. It is not just related with filebench. Here are a few scenarios: * When i run fileserver workload of filebench * After i issue the shutdown -h now shutdown -r now commands * Issuing mount -t linprocfs proc /proc Moreover it is not guaranteed that the above scenarios will reproduce it (reliably). Basically after running some commands and getting the CPU and the kernel worked up i think. This is a bug that i have noticed in qemu 1.7.50 as well as 1.1.50. It was the latter that forced me to clone the repository to check if this is the case with the resent version as well . The latest commit on which the bug is found is f53f3d0a00b6df39ce8dfca942608e5b6a9a4f71 on qemu.git configured with target list i386-softmmu and then make OS: FreeBSD 9.2 Text Install ISO Installed it to a qcow2 format image. ./i386-softmmu/qemu-system-i386 -hda <bsd-image> -m 2G -smp 4 -net nic -net user -monitor stdio (boot into multi-user mode)->(login to root account) I have the filebench benchmark installed on the image and when i run it the default root shell (csh) crashes with the error. [pid xxxx (csh) sigreturn eflag = 0xXXXX] Here is the piece of kernel code that is getting executed (i think) http://svnweb.freebsd.org/base/release/9.2.0/sys/i386/i386/machdep.c?view=markup#l1095 Here is a related bug https://www.virtualbox.org/ticket/458 The crash happens randomly. It is not just related with filebench. Here are a few scenarios: * When i run fileserver workload of filebench * After i issue the shutdown -h now shutdown -r now commands * Issuing mount -t linprocfs proc /proc Moreover it is not guaranteed that the above scenarios will reproduce it (reliably). Basically after running some commands and getting the CPU and the kernel worked up i think. NOTE: This bug does not occur in qemu-kvm
2014-03-10 13:49:25 prajeeth description This is a bug that i have noticed in qemu 1.7.50 as well as 1.1.50. It was the latter that forced me to clone the repository to check if this is the case with the resent version as well . The latest commit on which the bug is found is f53f3d0a00b6df39ce8dfca942608e5b6a9a4f71 on qemu.git configured with target list i386-softmmu and then make OS: FreeBSD 9.2 Text Install ISO Installed it to a qcow2 format image. ./i386-softmmu/qemu-system-i386 -hda <bsd-image> -m 2G -smp 4 -net nic -net user -monitor stdio (boot into multi-user mode)->(login to root account) I have the filebench benchmark installed on the image and when i run it the default root shell (csh) crashes with the error. [pid xxxx (csh) sigreturn eflag = 0xXXXX] Here is the piece of kernel code that is getting executed (i think) http://svnweb.freebsd.org/base/release/9.2.0/sys/i386/i386/machdep.c?view=markup#l1095 Here is a related bug https://www.virtualbox.org/ticket/458 The crash happens randomly. It is not just related with filebench. Here are a few scenarios: * When i run fileserver workload of filebench * After i issue the shutdown -h now shutdown -r now commands * Issuing mount -t linprocfs proc /proc Moreover it is not guaranteed that the above scenarios will reproduce it (reliably). Basically after running some commands and getting the CPU and the kernel worked up i think. NOTE: This bug does not occur in qemu-kvm This is a bug that i have noticed in qemu 1.7.50 as well as 1.1.50. It was the latter that forced me to clone the repository to check if this is the case with the resent version as well . The latest commit on which the bug is found is f53f3d0a00b6df39ce8dfca942608e5b6a9a4f71 on qemu.git configured with target list i386-softmmu and then make OS: FreeBSD 9.2 Text Install ISO (ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.2/FreeBSD-9.2-RELEASE-i386-disc1.iso) Installed it to a qcow2 format image. ./i386-softmmu/qemu-system-i386 -hda <bsd-image> -m 2G -smp 4 -net nic -net user -monitor stdio (boot into multi-user mode)->(login to root account) I have the filebench benchmark installed on the image and when i run it the default root shell (csh) crashes with the error. [pid xxxx (csh) sigreturn eflag = 0xXXXX] Here is the piece of kernel code that is getting executed (i think) http://svnweb.freebsd.org/base/release/9.2.0/sys/i386/i386/machdep.c?view=markup#l1095 Here is a related bug https://www.virtualbox.org/ticket/458 The crash happens randomly. It is not just related with filebench. Here are a few scenarios: * When i run fileserver workload of filebench * After i issue the shutdown -h now shutdown -r now commands * Issuing mount -t linprocfs proc /proc Moreover it is not guaranteed that the above scenarios will reproduce it (reliably). Basically after running some commands and getting the CPU and the kernel worked up i think. NOTE: This bug does not occur in qemu-kvm
2014-03-13 06:22:49 prajeeth description This is a bug that i have noticed in qemu 1.7.50 as well as 1.1.50. It was the latter that forced me to clone the repository to check if this is the case with the resent version as well . The latest commit on which the bug is found is f53f3d0a00b6df39ce8dfca942608e5b6a9a4f71 on qemu.git configured with target list i386-softmmu and then make OS: FreeBSD 9.2 Text Install ISO (ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.2/FreeBSD-9.2-RELEASE-i386-disc1.iso) Installed it to a qcow2 format image. ./i386-softmmu/qemu-system-i386 -hda <bsd-image> -m 2G -smp 4 -net nic -net user -monitor stdio (boot into multi-user mode)->(login to root account) I have the filebench benchmark installed on the image and when i run it the default root shell (csh) crashes with the error. [pid xxxx (csh) sigreturn eflag = 0xXXXX] Here is the piece of kernel code that is getting executed (i think) http://svnweb.freebsd.org/base/release/9.2.0/sys/i386/i386/machdep.c?view=markup#l1095 Here is a related bug https://www.virtualbox.org/ticket/458 The crash happens randomly. It is not just related with filebench. Here are a few scenarios: * When i run fileserver workload of filebench * After i issue the shutdown -h now shutdown -r now commands * Issuing mount -t linprocfs proc /proc Moreover it is not guaranteed that the above scenarios will reproduce it (reliably). Basically after running some commands and getting the CPU and the kernel worked up i think. NOTE: This bug does not occur in qemu-kvm This is a bug that i have noticed in qemu 1.7.50 as well as 1.1.50. It was the latter that forced me to clone the repository to check if this is the case with the resent version as well . The latest commit on which the bug is found is f53f3d0a00b6df39ce8dfca942608e5b6a9a4f71 on qemu.git configured with target list i386-softmmu and then make OS: FreeBSD 9.2 Text Install ISO (ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.2/FreeBSD-9.2-RELEASE-i386-disc1.iso) Installed it to a qcow2 format image. ./i386-softmmu/qemu-system-i386 -hda <bsd-image> -m 2G -smp 4 -net nic -net user -monitor stdio (boot into multi-user mode)->(login to root account) I have the filebench benchmark installed on the image and when i run it the default root shell (csh) crashes with the error. [pid xxxx (csh) sigreturn eflag = 0xXXXX] Here is the piece of kernel code that is getting executed (i think) http://svnweb.freebsd.org/base/release/9.2.0/sys/i386/i386/machdep.c?view=markup#l1095 Here is a related bug https://www.virtualbox.org/ticket/458 The crash happens randomly. It is not just related with filebench. Here are a few scenarios: * When i run fileserver workload of filebench * After i issue the shutdown -h now shutdown -r now commands * Issuing mount -t linprocfs proc /proc Moreover it is not guaranteed that the above scenarios will reproduce it (reliably). Basically after running some commands and getting the CPU and the kernel worked up i think. NOTE: This bug does not occur in qemu-kvm [X] EDIT: Confirmed. This happens on qemu-kvm as well.
2014-03-13 06:25:05 prajeeth description This is a bug that i have noticed in qemu 1.7.50 as well as 1.1.50. It was the latter that forced me to clone the repository to check if this is the case with the resent version as well . The latest commit on which the bug is found is f53f3d0a00b6df39ce8dfca942608e5b6a9a4f71 on qemu.git configured with target list i386-softmmu and then make OS: FreeBSD 9.2 Text Install ISO (ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.2/FreeBSD-9.2-RELEASE-i386-disc1.iso) Installed it to a qcow2 format image. ./i386-softmmu/qemu-system-i386 -hda <bsd-image> -m 2G -smp 4 -net nic -net user -monitor stdio (boot into multi-user mode)->(login to root account) I have the filebench benchmark installed on the image and when i run it the default root shell (csh) crashes with the error. [pid xxxx (csh) sigreturn eflag = 0xXXXX] Here is the piece of kernel code that is getting executed (i think) http://svnweb.freebsd.org/base/release/9.2.0/sys/i386/i386/machdep.c?view=markup#l1095 Here is a related bug https://www.virtualbox.org/ticket/458 The crash happens randomly. It is not just related with filebench. Here are a few scenarios: * When i run fileserver workload of filebench * After i issue the shutdown -h now shutdown -r now commands * Issuing mount -t linprocfs proc /proc Moreover it is not guaranteed that the above scenarios will reproduce it (reliably). Basically after running some commands and getting the CPU and the kernel worked up i think. NOTE: This bug does not occur in qemu-kvm [X] EDIT: Confirmed. This happens on qemu-kvm as well. This is a bug that i have noticed in qemu 1.7.50 as well as 1.1.50. It was the latter that forced me to clone the repository to check if this is the case with the resent version as well . The latest commit on which the bug is found is f53f3d0a00b6df39ce8dfca942608e5b6a9a4f71 on qemu.git qemu 1.7.50 configured with target list i386-softmmu. OS: FreeBSD 9.2 Text Install ISO (ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.2/FreeBSD-9.2-RELEASE-i386-disc1.iso) Installed it to a qcow2 format image. Command to run QEMU:: ./i386-softmmu/qemu-system-i386 -hda <bsd-image> -m 2G -smp 4 -net nic -net user -monitor stdio (boot into multi-user mode)->(login to root account) I have the filebench benchmark installed on the image and when i run it the default root shell (csh) crashes with the error. [pid xxxx (csh) sigreturn eflag = 0xXXXX] Here is the piece of kernel code that is getting executed (i think) http://svnweb.freebsd.org/base/release/9.2.0/sys/i386/i386/machdep.c?view=markup#l1095 Here is a related bug https://www.virtualbox.org/ticket/458 The crash happens randomly. It is not just related with filebench. Here are a few scenarios: * When i run fileserver workload of filebench * After i issue the shutdown -h now shutdown -r now commands * Issuing mount -t linprocfs proc /proc Moreover it is not guaranteed that the above scenarios will reproduce it (reliably). The bug manifests after running some commands and getting the CPU and the kernel worked up. NOTE: This bug does not occur in qemu-kvm [X] EDIT: Confirmed. This happens on qemu-kvm as well.
2017-10-25 15:18:15 Thomas Huth qemu: status New Incomplete
2017-12-25 04:17:37 Launchpad Janitor qemu: status Incomplete Expired