Xen users - Feb 2006 - RE: Xen 3.0.0 32bit-pae (testing changeset 8270) crashes(pgtable.c:284, kernel bug?)

> Both systems were running debian sarge (3.1) with xen 2.0.7 
> for a long time without any problems at all. Xen 3.0.0 also 
> seems to work fine, as long as the normal i386 mode is used. 
> With pae both systems crashes everytime I want to create a 
> domainU that needs to use some ram of last GB available. I 
> haven''t tested x86_64 on this machines at all.
You need 3.0.1 -- it works around the 3ware driver issue, though at a
performance cost (likely proportional to how much of your ram is mapped
above 4GB).

Ian

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Mittwoch, 1. Februar 2006 14:10 schrieben Sie:
> > Both systems were running debian sarge (3.1) with xen 2.0.7
> > for a long time without any problems at all. Xen 3.0.0 also
> > seems to work fine, as long as the normal i386 mode is used.
> > With pae both systems crashes everytime I want to create a
> > domainU that needs to use some ram of last GB available. I
> > haven''t tested x86_64 on this machines at all.
>
> You need 3.0.1 -- it works around the 3ware driver issue, though at a
> performance cost (likely proportional to how much of your ram is mapped
> above 4GB).
>
> Ian
thx for the hint... I will give it a try.

--Ralph

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Mittwoch, 1. Februar 2006 15:24 schrieb Ralph
Passgang:
> Am Mittwoch, 1. Februar 2006 14:10 schrieben Sie:
> > > Both systems were running debian sarge (3.1) with xen 2.0.7
> > > for a long time without any problems at all. Xen 3.0.0 also
> > > seems to work fine, as long as the normal i386 mode is used.
> > > With pae both systems crashes everytime I want to create a
> > > domainU that needs to use some ram of last GB available. I
> > > haven''t tested x86_64 on this machines at all.
> >
> > You need 3.0.1 -- it works around the 3ware driver issue, though at a
> > performance cost (likely proportional to how much of your ram is
mapped
> > above 4GB).
> >
> > Ian
>
> thx for the hint... I will give it a try.
>
> --Ralph
hmmm, or I would try it, if I could find the xen 3.0.1 source anywhere.

On xensource.com as well as on the site from the university of cambridge, 
there are just binaries, rpms, xen-3.0-testing source packages and so on. 

Should I take xen-3.0 testing instead or where can I find the released version 
as source?

--Ralph

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Mittwoch, 1. Februar 2006 14:10 schrieben Sie:
> > Both systems were running debian sarge (3.1) with xen 2.0.7
> > for a long time without any problems at all. Xen 3.0.0 also
> > seems to work fine, as long as the normal i386 mode is used.
> > With pae both systems crashes everytime I want to create a
> > domainU that needs to use some ram of last GB available. I
> > haven''t tested x86_64 on this machines at all.
>
> You need 3.0.1 -- it works around the 3ware driver issue, though at a
> performance cost (likely proportional to how much of your ram is mapped
> above 4GB).
Hi Ian,

3.0.1 seems to fix the bug I saw on my two machines, but now there is another 
(but somehow related) problem for me in 3.0.1-pae. I don''t know if
it''s still
related to the 3ware controller, but at least it only appears for domains 
that have memory above the 32bit adress-space again, so the first started 
domUs run fine. The big difference is that I don''t have any complete
freezes
of the xen machine anymore, just domUs are crashing this time.

the domU doesn''t always crash at the very same place, sometimes at the 
beginning of the init process, sometimes when it loads modules, sometimes 
when services gets started... Sometimes this crash happens more then once 
before the domU panics.

here is what I see in the domU console:

------------[ cut here ]------------
kernel BUG at <bad filename>:63723!
invalid operand: 0000 [#1]
SMP
Modules linked in: 8250 reiserfs efs isofs vfat fat ext3 jbd evdev pci_hotplug 
dm_mod sd_mod 3w_xxxx e1000 jedec_probe cfi_probe gen_probe chipreg mtdcore 
map_funcs i2c_i801 i2c_core parport_pc parport serial_core usbhid pcmcia 
yenta_socket rsrc_nonstatic pcmcia_core processor genrtc sbp2 ohci1394 
ieee1394 usb_storage ohci_hcd uhci_hcd 3w_9xxx scsi_mod unix
CPU:    0
EIP:    0061:[<c01182b6>]    Not tainted VLI
EFLAGS: 00010282   (2.6.12.6-xen)
EIP is at pgd_ctor+0x26/0x30
eax: fffffff4   ebx: 00000001   ecx: f577e000   edx: 00000000
esi: c118fd80   edi: c12bd258   ebp: c12bd240   esp: c864dd38
ds: 007b   es: 007b   ss: 0069
Process rcS (pid: 1041, threadinfo=c864c000 task=c06f8a40)
Stack: c77ae000 00000000 00000020 c014dd51 c77ae000 c118fd80 00000001 c12bd240
       c77ae000 c118fd80 00000000 c014decd c118fd80 c12bd240 00000001 000000d0
       c118fde0 00000001 000000d0 c119d980 0000000c 000000d0 00000000 c014e0db
Call Trace:
 [<c014dd51>] cache_init_objs+0x71/0x80
 [<c014decd>] cache_grow+0x10d/0x1a0
 [<c014e0db>] cache_alloc_refill+0x17b/0x220
 [<c014e39f>] kmem_cache_alloc+0x7f/0x90
 [<c011833d>] pgd_alloc+0x1d/0x310
 [<c01216fe>] mm_init+0xce/0x100
 [<c0121a14>] copy_mm+0xd4/0x3d0
 [<c0121fdf>] copy_files+0x1af/0x320
 [<c03f9d00>] parse_header+0xb0/0xe0
 [<c03f9d04>] parse_header+0xb4/0xe0
 [<c01225af>] copy_process+0x3df/0xd00
 [<c0166f4f>] fd_install+0x2f/0x60
 [<c0122fc9>] do_fork+0x69/0x18f
 [<c0130e4a>] sys_rt_sigprocmask+0xaa/0x110
 [<c0108f91>] sys_fork+0x31/0x40
 [<c010a65d>] syscall_call+0x7/0xb
Code: 00 f3 ab 5f c3 83 ec 0c b8 20 00 00 00 89 44 24 08 31 c0 89 44 24 04 8b 
44 24 10 89 04 24 e8 d2 2b 00 00 85 c0 75 04 83 c4 0c c3 <0f> 0b eb f8 8d
b6
00 00 00 00 83 ec 08 b8 f8 e3 36 c0 89 5c 24
 /etc/init.d/rcS: line 57:  1041 Segmentation fault      ( trap - INT QUIT 
TSTP; set start; . $i )

something I can do to help resolving that?

thx & regards,
-- Ralph
>
> Ian
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users