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

Re: [Xen-users] HOWTO about XEN on debian sarge

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
  • Date: Sun, 24 Apr 2005 00:51:03 +0000
  • Delivery-date: Sun, 24 Apr 2005 00:51:03 +0000
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Openpgp: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc

On Sat, Apr 23, 2005 at 12:36:10PM +0200, Christian Wicke wrote:
> With this howto you should avoid any traps like wrong kernels or wrong 
> network. But nothing is perfect. If you have any suggestions to improve it, 
> please let me know.

As I am interested in looking at Xen for the first time and I have a
debian sarge machine, I followed the first part of your howto.
Unfortunately on reboot I get the following:

Starting hotplug subsystem:
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel i875 Chipset.
agpgart: Maximum main memory to use for agp memory: 1797M
general protection fault: 0000 [#1]
Modules linked in: intel_agp agpgart w83627hf eeprom lm85 i2c_sensor i2c_isa 
i2c_i801 i2c_dev i2c_core genrtc
CPU:    0
EIP:    0061:[<f8f538f0>]    Not tainted VLI
EFLAGS: 00011202   (2.6.10curacaoxen0)
EIP is at global_cache_flush+0x0/0x10 [agpgart]
eax: f8f601a0   ebx: 00000000   ecx: 006d3fe0   edx: c16d4000
esi: f69c0000   edi: 369c0000   ebp: 00000006   esp: f71f9e7c
ds: 007b   es: 007b   ss: 0069
Process modprobe (pid: 1576, threadinfo=f71f8000 task=f7070580)
Stack: f8f533eb f8f59700 00000000 00010000 f69fffff 00000000 f8f59700 00000000
       00000100 f8f5112a c037a128 c037a148 c01d5800 00000000 00000000 f8f59700
       00000001 c06f3400 00000000 f8f51367 f8f59700 0034ae48 f8f60620 f8f60620
Call Trace:
 [<f8f533eb>] agp_generic_create_gatt_table+0xfb/0x240 [agpgart]
 [<f8f5112a>] agp_backend_initialize+0x6a/0x190 [agpgart]
 [<c01d5800>] pci_enable_device+0x40/0x50
 [<f8f51367>] agp_add_bridge+0x87/0x180 [agpgart]
 [<c01d7882>] pci_device_probe_static+0x52/0x70
 [<c01d78dc>] __pci_device_probe+0x3c/0x50
 [<c01d791c>] pci_device_probe+0x2c/0x50
 [<c01ffe0f>] driver_probe_device+0x2f/0x80
 [<c01fff5c>] driver_attach+0x5c/0xa0
 [<c02004ad>] bus_add_driver+0x9d/0xd0
 [<c0200acf>] driver_register+0x2f/0x40
 [<c01d7ba4>] pci_register_driver+0x64/0x90
 [<f8a8f00f>] agp_intel_init+0xf/0x11 [intel_agp]
 [<c0134ce2>] sys_init_module+0x182/0x230
 [<c0109658>] syscall_call+0x7/0xb
Code: 74 24 10 83 c4 14 c3 8d 74 26 00 83 ec 04 a1 e4 92 f5 f8 8b 50 38 85 d2 
75 02 58 c3 8b 50 04 8b 44 24 08 89 04 24 ff 52 24 eb ef <0f> 09 c3 8d b6 00 00 
00 00 8d bc 27 00 00 00 00 a1 e4 92 f5 f8
 ./pci.agent: line 156:  1576 Segmentation fault      $MODPROBE $MODULE 
>/dev/null 2>&1
     intel-agp: can't be loaded
missing kernel or user mode driver intel-agp
<6>USB Universal Host Controller Interface driver v2.2

and then nothing at all, boot does not continue.

Using versions of kernel and all xen packages from your howto.  Once
I get someone to go and reboot the machine I can get you the kernel
.config for dom0.

Any ideas what is wrong?  Should I just disable everything to do
with AGP in the meantime?

Also, I noticed this further up:

WARNING: Failed to register Xen virtual console driver as 'ttyS0'

I have a terminal server attached so normally my kernel lines in
grub would look like this:

kernel /vmlinuz-2.6.10 ro root=LABEL=/ console=tty0 console=ttyS0

so I added a console=ttyS0 on the end of the kernel line from your
howto.  Was that wrong?

> > > The optimum programming team size is 1.
Has Jurassic Park taught us nothing?
 -- pfilandr

Attachment: pgpan2ntfrvH1.pgp
Description: PGP signature

Xen-users mailing list



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