This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 490] 32-bit calls lock x86-64 system hard

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 490] 32-bit calls lock x86-64 system hard
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sun, 29 Jan 2006 09:26:21 +0000
Delivery-date: Sun, 29 Jan 2006 09:43:14 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From grantma@xxxxxxxxxxxxxxx  2006-01-29 09:26 
Tried investigating it a little further.

Xen hypervisor has console=vga, and kernel has console=tty0

Took machine single user (no X11) under Xen unstable hypervisor and
linux-2.6-xen.hg tip.

Executing 32-bit bash shell locked machine solid, no console output at all,
after the disk went for about half a second. Rebooted and repeated with doing
the same command from strace, and the machine hung solid while reading the bash
start up files.

Machine is a shuttle AMD64, with Nforce3 chip set and sataII HD, running Ubuntu
Breezy Badger AMD64, and Debian sarge in a 32-bit chroot.

Can't get you any more than that.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>