09 Feb 1.2 hangs on partition check

09 Feb 1.2 hangs on partition check

[stevegt]

Hi All,

I built xen and xenolinux from this morning's 1.2 pull and attempted to
boot it on the same hardware where I've been running the 02 Feb 1.2
build.  It hangs in partition check.  Compiler for both builds is gcc
3.0.4.  BIOS settings etc. are the same -- this node reboots back into
the 02 Feb build just fine.

Xen is running well enough that help etc. works -- here're the boot
messages, followed by the output of several dump queries.  Let me know
what else you need.  

Steve



root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83
kernel /boot/xen-1.2-2.4.24-1076460062.gz  dom0_mem=32000 ser_baud=115200
   [Multiboot-elf, <0x100000:0x12cef4:0x1b68c>, shtab=0x249280, entry=0x100000]
module /boot/xenolinux-1.2-2.4.24-1076460062.gz  root=/dev/hda1 ro console=xenc
ons0
   [Multiboot-module @ 0x26b000, 0x16b92c bytes]

 __  __            _   ____
 \ \/ /___ _ __   / | |___ \
  \  // _ \ '_ \  | |   __) |
  /  \  __/ | | | | |_ / __/
 /_/\_\___|_| |_| |_(_)_____|

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 1.2 (stevegt@) (gcc version 3.0.4) Tue Feb 10 12:12:21 PST 2004

Initialised all memory on a 767MB machine
Reading BIOS drive-info tables at 0xfe761 and 0xfe401
CPU0: Before vendor init, caps: 0183f9ff 00000000 00000000, vendor = 0
CPU caps: 0183f9ff 00000000 00000000 00000000
Initialising domains
Initialising schedulers
Initializing CPU#0
Detected 398.777 MHz processor.
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
CPU0: Before vendor init, caps: 0183fbff 00000000 00000000, vendor = 0
CPU caps: 0183fbff 00000000 00000000 00000000
CPU0 booted
SMP motherboard not detected.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
Calibrating APIC timer for CPU0...
..... CPU speed is 398.7718 MHz.
..... Bus speed is 99.6927 MHz.
..... bus_scale = 0x00006617
ACT: Initialising Accurate timers
Time init:
.... System Time: 11921602ns
.... cpu_freq:    00000000:17C4DB0C
.... scale:       00000002:81F66F97
.... Wall Clock:  1076479559s 0us
Start schedulers
PCI: PCI BIOS revision 2.10 entry at 0xfcaee, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
Limiting direct PCI/PCI transfers.
Intel(R) PRO/1000 Network Driver - version 5.2.16
Copyright (c) 1999-2003 Intel Corporation.
PCI: Found IRQ 11 for device 00:11.0
PCI: Sharing IRQ 11 with 00:07.2
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
00:11.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xdc00. Vers LK1.1.16
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
hda: Maxtor 90640D4, ATA DISK drive
hdc: NEC CD-ROM DRIVE:28B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hdc: ATAPI 32X CD-ROM drive, 256kB Cache
Uniform CD-ROM driver Revision: 3.12
hda: 12594960 sectors (6449 MB) w/256KiB Cache, CHS=784/255/63, UDMA(33)
SCSI subsystem driver Revision: 1.00
Red Hat/Adaptec aacraid driver (1.1.2 Jan 31 2004 19:44:21)
Device eth0 opened and ready for use.
DOM0: Guest OS virtual load address is c0000000
DOM0: xen_console_init
DOM0: Linux version 2.4.24-xeno (stevegt@pathfinder) (gcc version 3.0.4) #18 Tue Feb 10 12:14:26 PST 2004
DOM0: On node 0 totalpages: 8000
DOM0: zone(0): 4096 pages.
DOM0: zone(1): 3904 pages.
DOM0: zone(2): 0 pages.
DOM0: Kernel command line: /boot/xenolinux-1.2-2.4.24-1076460062.gz  root=/dev/hda1 ro console=xencons0
DOM0: Initializing CPU#0
DOM0: Xen reported: 398.777 MHz processor.
DOM0: Console: colour VGA+ 80x25
DOM0: Calibrating delay loop... 3355.44 BogoMIPS
DOM0: Memory: 29908k/32000k available (1078k kernel code, 2092k reserved, 308k data, 52k init, 0k highmem)
DOM0: Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
DOM0: Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
DOM0: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
DOM0: Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
DOM0: Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
DOM0: CPU: L1 I cache: 16K, L1 D cache: 16K
DOM0: CPU: L2 cache: 512K
DOM0: CPU: Intel Pentium II (Deschutes) stepping 01
DOM0: POSIX conformance testing by UNIFIX
DOM0: Linux NET4.0 for Linux 2.4
DOM0: Based upon Swansea University Computer Society NET3.039
DOM0: Initializing RT netlink socket
DOM0: Starting kswapd
DOM0: Journalled Block Device driver loaded
DOM0: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
DOM0: Xeno console successfully installed
DOM0: Successfully installed virtual firewall/router interface
DOM0: Starting Xeno Balloon driver
DOM0: Detected PS/2 Mouse Port.
DOM0: pty: 256 Unix98 ptys configured
DOM0: Partition check:



Dumping ac_timer queues: NOW=0x0000020470020AF9
CPU[00]   1 : fc632640 ex=0x0000020470DDB0FD 0
  2 : fc632660 ex=0x000002048B99BD36 0
  3 : fc632254 ex=0x000002047283375E 2

Dumping block queue stats: nr_pending = 0 (prod=0,cons=0)
Pend0: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend1: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend2: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend3: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend4: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend5: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend6: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend7: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend8: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend9: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend10: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend11: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend12: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend13: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend14: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend15: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend16: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend17: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend18: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend19: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend20: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend21: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend22: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend23: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend24: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend25: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend26: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend27: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend28: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend29: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend30: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend31: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend32: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend33: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend34: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend35: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend36: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend37: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend38: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend39: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend40: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend41: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend42: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend43: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend44: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend45: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend46: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend47: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend48: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend49: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend50: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend51: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend52: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend53: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend54: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend55: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend56: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend57: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend58: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend59: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend60: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend61: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend62: dom=00000000, id=00000000, cnt=0, op=0, status=0
Pend63: dom=00000000, id=00000000, cnt=0, op=0, status=0

'd' pressed -> dumping registers
CPU:    0
EIP:    0819:[<c00ae44c>]
EFLAGS: 00201287
eax: 0000001f   ebx: 00000300   ecx: c018b5fc   edx: fbff9000
esi: c10db1e0   edi: 00000000   ebp: 00601788   esp: c1f23d44
ds: 0821   es: 0821   fs: 0821   gs: 0821   ss: 0821
Stack trace from ESP=fc502ff4:
c1f23d44 00000821 fc674040

Xen performance counters SHOW  (now = 0x00000215:37B70680)
#interrupts                       TOTAL[    241017]  CPU00[    241017]
cycles spent in irq handler       TOTAL[ 424944039]  CPU00[ 424944039]
apic timer interrupts             TOTAL[    143742]  CPU00[    143742]
ac_timer max error (ns)           TOTAL[         0]  CPU00[         0]
sched: timer                      TOTAL[     45701]  CPU00[     45701]
sched: runs through scheduler     TOTAL[     45701]  CPU00[     45701]
sched: context switches           TOTAL[         1]  CPU00[         1]
network hypercalls                TOTAL[         8]
net rx congestion drops           TOTAL[         0]
net rx capacity drops             TOTAL[     11881]
net rx delivered                  TOTAL[         0]
net rx tlb flushes                TOTAL[         0]
net tx transmitted                TOTAL[         0]
domain page tlb flushes           TOTAL[        11]  CPU00[        11]
PG_need_flush tlb flushes         TOTAL[         2]  CPU00[         2]
calls_to_mmu_update               TOTAL[        38]  CPU00[        38]
num_page_updates                  TOTAL[        88]  CPU00[        88]

'q' pressed -> dumping task queues
Xen: DOM -1, CPU 0 [has=F], state = Runnable, hyp_events = 00000000
Xen: DOM 0, CPU 0 [has=T], state = Runnable, hyp_events = 00000000
Guest: events = 00000000, events_mask = 8000017f
rx_prod=0 ,rx_cons=0, tx_prod=0, tx_cons=0
rx_req_cons=0, rx_resp_prod=0, tx_req_cons=0, tx_resp_prod=0
Notifying guest...
BVT: mcu=0x000186A0ns ctx_allow=0x004C4B40ns NOW=0x00000217B8CF2845
CPU[00] svt=0x0DB74618 QUEUE rq fc632240   n: fc6060bc, p: fc67407c
  0:  -1 has=F mcua=0x0000 ev=0xFFFFFFFF av=0xFFFFFFFF c=0x000000000
         l: fc6060bc n: fc67407c  p: fc632240
  1:   0 has=T mcua=0x000A ev=0x0DB74618 av=0x0DB74618 c=0x216C5AD2DAA
         l: fc67407c n: fc632240  p: fc6060bc


-- 
Stephen G. Traugott  (KG6HDQ)
UNIX/Linux Infrastructure Architect, TerraLuna LLC
stevegt@TerraLuna.Org 
http://www.stevegt.com -- http://Infrastructures.Org 


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: 09 Feb 1.2 hangs on partition check

[Keir Fraser]

> 
> Hi All,
> 
> I built xen and xenolinux from this morning's 1.2 pull and attempted to
> boot it on the same hardware where I've been running the 02 Feb 1.2
> build.  It hangs in partition check.  Compiler for both builds is gcc
> 3.0.4.  BIOS settings etc. are the same -- this node reboots back into
> the 02 Feb build just fine.

Any chance you could try with a different version of GCC? This sounds
possibly like an unexpected optimisation by the compiler (I saw a
problem with very similar symptoms a coupel of weeks ago that affected
mainly early GCC 3.x compilers).

Perhaps I should keep a suite of GCC installations lying around for
local testing of this kind of bug. :-)

 -- Keir
 
> Xen is running well enough that help etc. works -- here're the boot
> messages, followed by the output of several dump queries.  Let me know
> what else you need.  
> 
> Steve


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: 09 Feb 1.2 hangs on partition check

[Keir Fraser]

> > 
> > Hi All,
> > 
> > I built xen and xenolinux from this morning's 1.2 pull and attempted to
> > boot it on the same hardware where I've been running the 02 Feb 1.2
> > build.  It hangs in partition check.  Compiler for both builds is gcc
> > 3.0.4.  BIOS settings etc. are the same -- this node reboots back into
> > the 02 Feb build just fine.
> 
> Any chance you could try with a different version of GCC? This sounds
> possibly like an unexpected optimisation by the compiler (I saw a
> problem with very similar symptoms a coupel of weeks ago that affected
> mainly early GCC 3.x compilers).
> 
> Perhaps I should keep a suite of GCC installations lying around for
> local testing of this kind of bug. :-)

Okay, I've tried building Xen/Xenolinux with GCC 3.0.4. Although I
didn't see your bug, I saw enough other weirdness (e.g., the
start-of-day TSC skew calculations are broken) that I am convinced GCC
3.0.x is a bad choice!

Please move to a more recent GCC (e.g. GCC 3.2.2 seems to work, and
I've seen 3.3.x working in the past). 

 -- Keir


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: 09 Feb 1.2 hangs on partition check

[stevegt]

On Wed, Feb 11, 2004 at 11:03:26AM +0000, Keir Fraser wrote:
> > > I built xen and xenolinux from this morning's 1.2 pull and attempted to
> > > boot it on the same hardware where I've been running the 02 Feb 1.2
> > > build.  It hangs in partition check.  Compiler for both builds is gcc
> > > 3.0.4.  BIOS settings etc. are the same -- this node reboots back into
> > > the 02 Feb build just fine.
> > 
> > Any chance you could try with a different version of GCC? This sounds
> > possibly like an unexpected optimisation by the compiler (I saw a
> > problem with very similar symptoms a coupel of weeks ago that affected
> > mainly early GCC 3.x compilers).
> > 
> > Perhaps I should keep a suite of GCC installations lying around for
> > local testing of this kind of bug. :-)

Has anyone started work on a regression test infrastructure?  I'm
thinking either something local, or something distributed similar to the
cpan-testers pool...

> Okay, I've tried building Xen/Xenolinux with GCC 3.0.4. Although I
> didn't see your bug, I saw enough other weirdness (e.g., the
> start-of-day TSC skew calculations are broken) that I am convinced GCC
> 3.0.x is a bad choice!
> 
> Please move to a more recent GCC (e.g. GCC 3.2.2 seems to work, and
> I've seen 3.3.x working in the past). 

Will do.

Steve
-- 
Stephen G. Traugott  (KG6HDQ)
UNIX/Linux Infrastructure Architect, TerraLuna LLC
stevegt@TerraLuna.Org 
http://www.stevegt.com -- http://Infrastructures.Org 


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

Re: 09 Feb 1.2 hangs on partition check

[Ian Pratt]

> Has anyone started work on a regression test infrastructure?  I'm
> thinking either something local, or something distributed similar to the
> cpan-testers pool...

We've got a simple regression test that runs and measures the
performance of the following benchmarks running in domain 0:

 * linux builds
 * SPEC CINT 2000
 * PostgreSQL / OSDB (OLTP and IR)
 * lmbench
 * ttcp TCP test (mtu 1500 & 500)
 
We haven't got anything that tests domains other than domain 0.
There's also the issue that SPEC CINT 2000 is proprietary so we
can't give it away to other people to run. I'm planning on
putting the rest of the test harness and the file system its
installed on up for download, in the hope that people will
improve it.

In particular, the test suite is installed on a RH7.2 file
system. It would be nice to upgrade this to something newer, and
more relevant to what people are actually using XenoLinux on.

Cheers,
Ian


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

GCC 3.0.4 incompatible (FAQ?)

[stevegt]

It looks safe to say that gcc 3.0.4 is incompatible with xen and/or
xenolinux; this should probably be added to the FAQ.

I recompiled today's 1.2 with gcc 3.3.2 and that got rid of the hang at
partition check.

Steve


On Wed, Feb 11, 2004 at 08:18:27AM +0000, Keir Fraser wrote:
> > 
> > Hi All,
> > 
> > I built xen and xenolinux from this morning's 1.2 pull and attempted to
> > boot it on the same hardware where I've been running the 02 Feb 1.2
> > build.  It hangs in partition check.  Compiler for both builds is gcc
> > 3.0.4.  BIOS settings etc. are the same -- this node reboots back into
> > the 02 Feb build just fine.
> 
> Any chance you could try with a different version of GCC? This sounds
> possibly like an unexpected optimisation by the compiler (I saw a
> problem with very similar symptoms a coupel of weeks ago that affected
> mainly early GCC 3.x compilers).
> 
> Perhaps I should keep a suite of GCC installations lying around for
> local testing of this kind of bug. :-)
> 
>  -- Keir
>  
> > Xen is running well enough that help etc. works -- here're the boot
> > messages, followed by the output of several dump queries.  Let me know
> > what else you need.  
> > 
> > Steve
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel

-- 
Stephen G. Traugott  (KG6HDQ)
UNIX/Linux Infrastructure Architect, TerraLuna LLC
stevegt@TerraLuna.Org 
http://www.stevegt.com -- http://Infrastructures.Org 


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

Re: 09 Feb 1.2 hangs on partition check

[Steven Hand]

>I built xen and xenolinux from this morning's 1.2 pull and attempted to
>boot it on the same hardware where I've been running the 02 Feb 1.2
>build.  It hangs in partition check.  Compiler for both builds is gcc
>3.0.4.  BIOS settings etc. are the same -- this node reboots back into
>the 02 Feb build just fine.

This is odd - at least in the sense that there's been no changes to 
the block device stuff (either in xenolinux or xen) in that interval
of time. Only even plausible candidates are the gdt fix and the memory
fix, but neither of these 'should'  cause problems...

>Xen is running well enough that help etc. works -- here're the boot
>messages, followed by the output of several dump queries.  Let me know
>what else you need.  

So dumps show that domain 0 is running - presumably waiting for the 
response to its block requests - although it's tricky to see exactly
since the block prod/cons values aren't shown. 

>'q' pressed -> dumping task queues
>Xen: DOM -1, CPU 0 [has=F], state = Runnable, hyp_events = 00000000
>Xen: DOM 0, CPU 0 [has=T], state = Runnable, hyp_events = 00000000
>Guest: events = 00000000, events_mask = 8000017f
>rx_prod=0 ,rx_cons=0, tx_prod=0, tx_cons=0
>rx_req_cons=0, rx_resp_prod=0, tx_req_cons=0, tx_resp_prod=0
>Notifying guest...

Two things to try (in addition to Keir's suggestion of trying 
another gcc) 

  - press 'q' twice in succession so that we can see if the 
    guest event handlings is really broken (which it seems
    to be) 

  - press 'b' to dump the block queues so we can see the 
    event count values


cheers, 

S.



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: 09 Feb 1.2 hangs on partition check

[Steven Hand]

>  - press 'b' to dump the block queues so we can see the 
>    event count values
>

Duh - you'd already done this - the format has changed since I last
looked at it so didn't spot it :-(

Anyway, trying the 'q thing should be worthwhile anyhow


cheers, 

S.



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: GCC 3.0.4 incompatible (FAQ?)

[Jan van Rensburg]

> It looks safe to say that gcc 3.0.4 is incompatible with xen and/or
> xenolinux; this should probably be added to the FAQ.

Done.



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

Re: GCC 3.0.4 incompatible (FAQ?)

[Keir Fraser]

> 
> > It looks safe to say that gcc 3.0.4 is incompatible with xen and/or
> > xenolinux; this should probably be added to the FAQ.
> 
> Done.

A more comprehensive list of conclusions:

We have reason to doubt the integrity of 3.0.4 (definitely) and also
3.1.1 (quite possibly).

We've had nothing but success with 3.2.2 and 3.3.2.

 -- Keir


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click