|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-users
[Xen-users] fb0 - conflict?
 
Hi, all. I'm trying to track down some stability issues with my Xen 
system, and in the course of doing so, I've found a few things that are 
probably unrelated, but things I'd like to clean up nonetheless.
I have a Xen guest instance running my Xen0 kernel. When it boots I get:
Jul 29 01:31:37 loki kernel: fb0: VGA16 VGA frame buffer device
Jul 29 01:31:37 loki kernel: c48c9dd3
Jul 29 01:31:37 loki kernel:  [<c01b6ddc>] take_over_console+0x63/0x389
Jul 29 01:31:37 loki kernel:  [<c48c92f4>] fbcon_takeover+0x5c/0x8a [fbcon]
Jul 29 01:31:37 loki kernel:  [<c4853231>] init_module+0x56/0x5a [fbcon]
Jul 29 01:31:37 loki kernel:  [<c012b5ca>] sys_init_module+0xf1/0x1e9
Jul 29 01:31:37 loki kernel:  [<c0108c10>] syscall_call+0x7/0xb
Jul 29 01:31:37 loki kernel: PREEMPT
 Jul 29 01:31:37 loki kernel: Modules linked in: fbcon font bitblit 
vga16fb cfbcopyarea vgastate cfbimgblt cfbfillrect usbserial usbhid 
usbkbd ehci_hcd ohci_hcd usbcore sata_sil libata scsi_mod raid1 md unix
Jul 29 01:31:37 loki kernel: CPU:    0
Jul 29 01:31:37 loki kernel: EIP:    0061:[<c48c9dd3>]    Not tainted VLI
Jul 29 01:31:37 loki kernel: EFLAGS: 00010202   (2.6.11.10-xen0)
Jul 29 01:31:37 loki kernel: EIP is at fbcon_startup+0x1e3/0x2ab [fbcon]
 Jul 29 01:31:37 loki kernel: eax: 00000008   ebx: c4896fa0   ecx: 
00000000   edx: c489ae80
Jul 29 01:31:37 loki kernel: esi: 00000000   edi: c3c1fa2c   ebp: 
c3c1f9a0   esp: c073bf64
Jul 29 01:31:37 loki kernel: ds: 007b   es: 007b   ss: 0069
 Jul 29 01:31:37 loki kernel: Process modprobe (pid: 714, 
threadinfo=c073a000 task=c072faa0)
Jul 29 01:31:37 loki kernel: Stack: 00000000 c48cf900 00000001 c073a000 
c48cf700 c073a000 c01b6ddc ffffffff
Jul 29 01:31:37 loki kernel:        c48cf700 c073a000 00000010 c073a000 
c48c92f4 c48cd460 00000000 0000003e
Jul 29 01:31:37 loki kernel:        00000001 c4853231 00000000 c012b5ca 
b7eac000 fbffb000 08049470 c0108c10
Jul 29 01:31:37 loki kernel: Call Trace:
Jul 29 01:31:37 loki kernel:  [<c01b6ddc>] take_over_console+0x63/0x389
Jul 29 01:31:37 loki kernel:  [<c48c92f4>] fbcon_takeover+0x5c/0x8a [fbcon]
Jul 29 01:31:37 loki kernel:  [<c4853231>] init_module+0x56/0x5a [fbcon]
Jul 29 01:31:37 loki kernel:  [<c012b5ca>] sys_init_module+0xf1/0x1e9
Jul 29 01:31:37 loki kernel:  [<c0108c10>] syscall_call+0x7/0xb
 Jul 29 01:31:37 loki kernel: Code: 8d c4 00 74 11 68 60 14 8d c4 e8 49 
f2 fc ff 85 c0 89 c2 5e 75 0f ff 73 0c ff 73 08 e8 6e f2 fc ff 89 c2 58 
59 8b 42 08 8b 0c 24 <89> 41 5c 8b 42 0c 89 41 60 8b 42 10 8b 74 24 04 
89 46 04 89 41
 I'm guessing this is saying that the kernel tried to take over the frame 
buffer device, but either it doesn't have one, since no video cards are 
allocated to this system, or its somehow going after a device that the 
Dom0 has already taken over and is failing. Can anyone point me in the 
direction of solving this?
Thanks!
-sten
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
 
 |   
 
| <Prev in Thread] | 
Current Thread | 
[Next in Thread> |  
- [Xen-users] fb0 - conflict?,
sten <=
  
 |  
  
 | 
    | 
  
  
    |   | 
    |