Date: Fri, 26 Dec 2003 22:56:56 +0100 From: "Georg-W. Koltermann" <gwk@rahn-koltermann.de> To: Craig Boston <craig@xfoil.gank.org> Cc: "Georg-W. Koltermann" <gwk@rahn-koltermann.de> Subject: Re: vmware2 doesn't build Message-ID: <3FECAEA8.4000104@rahn-koltermann.de> In-Reply-To: <200312232329.13909.craig@xfoil.gank.org> References: <3FE8C3F6.7060804@rahn-koltermann.de> <200312232329.13909.craig@xfoil.gank.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Craig Boston wrote: >On Tuesday 23 December 2003 04:38 pm, Georg-W. Koltermann wrote: > > >>If I hack around these two by just using the non-SMP code even in #if >>SMP, it compiles. I didn't try to run it yet, but I think I might have >>a good chance it runs since I'm not on an SMP machine. >> >> > >I've been hacking around this pretty much the same way ever since the apic >changes -- it's a UP machine so I just disabled building the SMP module. > >This was working for me (post apic changes) until just before the 5.2 branch >point. Somewhere in there something changed and it now compiles and seems to >run, but as soon as the VM is turned on, the disks on the real system just go >dead. Can't access any files at all, get some messages about ata command >timeouts, and the system slowly dies as processes get hung one by one. It >seems to be killing interrupt delivery somehow. > > In the meantime I *did* run the port. It booted W2K ok, I could log in and open a Word document from my Unix fs via Samba. I haven't noticed any problems with the disc as you describe. I'll use VMWare more often when back in the office next year. -- Regards, Georg.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FECAEA8.4000104>