[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] Xorg/radeon crashes on AMD64-xen0


  • To: "Robert Jaemmrich" <mail@xxxxxxxxxxxxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Mon, 6 Jun 2005 08:06:06 -0700
  • Delivery-date: Mon, 06 Jun 2005 15:05:13 +0000
  • List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcVo9BvG12//Sps/QLitXxVXIAOdkQBtQcAA
  • Thread-topic: [Xen-ia64-devel] Xorg/radeon crashes on AMD64-xen0

Hi Robert --

I think you sent this to the wrong list.  x86_64 issues are
discussed on the main xen-devel mailing list.

Dan 

> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Robert Jaemmrich
> Sent: Saturday, June 04, 2005 4:57 AM
> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-ia64-devel] Xorg/radeon crashes on AMD64-xen0
> 
> Hi,
> 
> Xorg crashes after booting into my unstable Xen0 kernel (today's
> xen-unstable). I get the following messages:
> 
> warning ----------- [cut here ] --------- [please bite here ] 
> ---------
> alert Kernel BUG at hypervisor:53
> emerg invalid operand: 0000 [1] 
> warning CPU 0
> warning Modules linked in: amd64_agp agpgart
> warning Pid: 10915, comm: Xorg Not tainted 2.6.11.11-xen0
> warning RIP: e030:[<ffffffff80118911>]
> <ffffffff80118911>{xen_l1_entry_update+113}
> warning RSP: e02b:ffff880004865da8  EFLAGS: 00010282
> warning RAX: 00000000ffffffea RBX: 0000000000170000 RCX: 
> ffffffff8011890d
> warning RDX: 0000000000000000 RSI: 0000000000000001 RDI: 
> ffff880004865da8
> warning RBP: 00000000000cff10 R08: 8000000000000027 R09: 
> ffff88000313b8d8
> warning R10: 0000000000007ff0 R11: 0000000000000202 R12: 
> 0000000002d7cb80
> warning R13: ffff88000221db80 R14: 00000000001d0000 R15: 
> 000000002b750000
> warning FS:  00002aaaab494b80(0000) GS:ffffffff80448d00(0000)
> knlGS:0000000000000000
> warning CS:  e033 DS: 0000 ES: 0000
> warning Process Xorg (pid: 10915, threadinfo ffff880004864000, task
> ffff8800053eaae0)
> warning Stack: 000000000a21db80 0000000002937027 ffff8800047a6b80
> ffffffff80146f57
> warning ffff880000abf500 00002aaaab7cffff 000000002b7d0000 
> 00002aaa80000000
> warning 00000000000a47a0 ffff8800047dbad8
> warning Call Trace:<ffffffff80146f57>{remap_pfn_range+887}
> <ffffffff802305ee>{mmap_kmem+62}
> warning <ffffffff8014b1d1>{do_mmap_pgoff+1329}
> <ffffffff80112636>{sys_mmap+150}
> warning <ffffffff8010d641>{system_call+125}
> <ffffffff8010d5c4>{system_call+0}
> warning
> warning
> warning Code: 0f 0b 1e 24 34 80 ff ff ff ff 35 00 66 66 90 48 
> 83 c4 18 c3
> alert RIP <ffffffff80118911>{xen_l1_entry_update+113} RSP 
> <ffff880004865da8>
> 
> The last messages in Xorg.0.log are
> 
> (II) Loading sub module "radeon"
> (II) LoadModule: "radeon"
> (II) Reloading /usr/lib64/modules/drivers/radeon_drv.o
> (II) resource ranges after probing:
>         [0] -1  0       0xffe00000 - 0xffffffff (0x200000) MX[B](B)
>         [1] -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
>         [2] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[B]
>         [3] -1  0       0x000c0000 - 0x000effff (0x30000) MX[B]
>         [4] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[B]
>         [5] -1  0       0xcfffed00 - 0xcfffedff (0x100) MX[B]
>         [6] -1  0       0xcfffe000 - 0xcfffe7ff (0x800) MX[B]
>         [7] -1  0       0xcffc0000 - 0xcffdffff (0x20000) MX[B]
>         [8] -1  0       0xcffff000 - 0xcfffffff (0x1000) MX[B]
>         [9] -1  0       0xcfffef00 - 0xcfffefff (0x100) MX[B]
>         [10] -1 0       0xd0000000 - 0xcfffffff (0x0) MX[B]O
>         [11] -1 0       0xcfee0000 - 0xcfeeffff (0x10000) MX[B](B)
>         [12] -1 0       0xb8000000 - 0xbfffffff (0x8000000) MX[B](B)
>         [13] -1 0       0xcfec0000 - 0xcfedffff (0x20000) MX[B](B)
>         [14] -1 0       0xcfef0000 - 0xcfefffff (0x10000) MX[B](B)
>         [15] -1 0       0xc0000000 - 0xc7ffffff (0x8000000) MX[B](B)
>         [16] 0  0       0x000a0000 - 0x000affff (0x10000) MS[B]
>         [17] 0  0       0x000b0000 - 0x000b7fff (0x8000) MS[B]
>         [18] 0  0       0x000b8000 - 0x000bffff (0x8000) MS[B]
>         [19] -1 0       0x0000ffff - 0x0000ffff (0x1) IX[B]
>         [20] -1 0       0x00000000 - 0x000000ff (0x100) IX[B]
>         [21] -1 0       0x0000b400 - 0x0000b4ff (0x100) IX[B]
>         [22] -1 0       0x0000c400 - 0x0000c41f (0x20) IX[B]
>         [23] -1 0       0x0000c000 - 0x0000c01f (0x20) IX[B]
>         [24] -1 0       0x0000bc00 - 0x0000bc1f (0x20) IX[B]
>         [25] -1 0       0x0000b800 - 0x0000b81f (0x20) IX[B]
>         [26] -1 0       0x0000fc00 - 0x0000fc0f (0x10) IX[B]
>         [27] -1 0       0x0000c800 - 0x0000c8ff (0x100) IX[B]
>         [28] -1 0       0x0000cc00 - 0x0000cc0f (0x10) IX[B]
>         [29] -1 0       0x0000d000 - 0x0000d003 (0x4) IX[B]
>         [30] -1 0       0x0000d400 - 0x0000d407 (0x8) IX[B]
>         [31] -1 0       0x0000d800 - 0x0000d803 (0x4) IX[B]
>         [32] -1 0       0x0000dc00 - 0x0000dc07 (0x8) IX[B]
>         [33] -1 0       0x0000e000 - 0x0000e07f (0x80) IX[B]
>         [34] -1 0       0x0000e800 - 0x0000e8ff (0x100) IX[B]
>         [35] -1 0       0x0000ec00 - 0x0000ec7f (0x80) IX[B]
>         [36] -1 0       0x0000e400 - 0x0000e4ff (0x100) IX[B]
>         [37] -1 0       0x0000a800 - 0x0000a8ff (0x100) IX[B](B)
>         [38] 0  0       0x000003b0 - 0x000003bb (0xc) IS[B]
>         [39] 0  0       0x000003c0 - 0x000003df (0x20) IS[B]
> (II) Setting vga for screen 0.
> (II) RADEON(0): MMIO registers at 0xcfef0000
> 
> 
> What am I doing wrong? ;-)
> 
> Robert
> 
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
> 

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.