[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 802] New: SBCL build triggers BUG() in mm/mmap.c
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=802 Summary: SBCL build triggers BUG() in mm/mmap.c Product: Xen Version: 3.0.2 Platform: x86-64 OS/Version: Linux-2.6 Status: NEW Severity: normal Priority: P2 Component: Guest-OS AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx ReportedBy: piranha@xxxxxxxxxxxxxxx Building SBCL 0.9.17 destabilizes the domain that I build it in when "make-target-2.sh" is executed. (Tested only on an unprivileged domain.) The build process halts, with 0% CPU consumed. The system load is pegged at 1.0. Attempting to read certain information on the build process locks up that requesting process (ps, w). (top will report upon the process, with e.g. -b -n 1) I'm led to believe this is a Xen or Linux bug, because a non-root process shouldn't trigger a kernel BUG(). After attempting to build once, the problem can be reproduced with "sh make-target-2.sh" without having to rebuild from scratch. The script is trivial; the exact command, which fires up src/runtime/sbcl, is listed at the end of that file. Last bits on SBCL build: ---8<---8<--- [building initial core file in "output/cold-sbcl.core": writing 4096 bytes [1 page] from #<SB!FASL::GSPACE :READ-ONLY> writing 4096 bytes [1 page] from #<SB!FASL::GSPACE :STATIC> writing 41943040 bytes [10240 pages] from #<SB!FASL::GSPACE :DYNAMIC> /(DESCRIPTOR-BITS INITIAL-FUN)=#X10020FA8C9 done] Bye. //testing for consistency of first and second GENESIS passes //header files match between first and second GENESIS -- good real 37m53.413s user 32m4.892s sys 1m30.414s //entering make-target-2.sh //doing warm init This is SBCL 0.9.17, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. --->8--->8--- Kernel messages: ---8<---8<--- ----------- [cut here ] --------- [please bite here ] --------- Kernel BUG at mm/mmap.c:436 invalid opcode: 0000 [1] CPU 0 Modules linked in: ipv6 uhci_hcd ohci_hcd ehci_hcd Pid: 1701, comm: sbcl Tainted: GF 2.6.16.13-xen #1 RIP: e030:[<ffffffff8015ba86>] <ffffffff8015ba86>{vma_adjust+806} RSP: e02b:ffff880007d5bdf8 EFLAGS: 00010687 RAX: ffff880009c7fc38 RBX: ffff880001d4f298 RCX: ffff880007d5be40 RDX: 00000010027ff000 RSI: 0000001000184000 RDI: ffff880009c7fc68 RBP: ffff8800061b0978 R08: ffff880007d5be48 R09: ffff880009c7fc68 R10: ffff8800099a79c0 R11: ffff880000e4e4d8 R12: ffff880009c7fad8 R13: 0000000000000000 R14: 0000000000000000 R15: ffff88000aecb500 FS: 00002b618caac4a0(0000) GS:ffffffff804f1000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 Process sbcl (pid: 1701, threadinfo ffff880007d5a000, task ffff880007425140) Stack: 0000000040000017 0000000000000000 ffff880004f77dc0 ffff8800065d1e98 ffff8800065d1e78 0000000000004e0c 0000001002800000 00000010027ff000 ffff880007d5bf58 00002b618cef4c38 Call Trace: <ffffffff8015c76c>{split_vma+236} <ffffffff8015dcdf>{sys_mprotect+799} <ffffffff8010ac53>{sys_rt_sigreturn+579} <ffffffff8010ae15>{system_call+117} <ffffffff8010ada0>{system_call+0} Code: 0f 0b 68 16 8b 3a 80 c2 b4 01 48 8b 4c 24 48 48 8b 54 24 40 RIP <ffffffff8015ba86>{vma_adjust+806} RSP <ffff880007d5bdf8> --->8--->8--- Please let me know if I can provide more information that might be valuable. Thanks. -- Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ Xen-bugs mailing list Xen-bugs@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-bugs
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |