Date: Sat, 28 Aug 2004 12:19:18 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Jun Kuriyama <kuriyama@imgsrc.co.jp> Cc: Current <freebsd-current@freebsd.org> Subject: Re: Hang at probing on VMware installation Message-ID: <3181.1093688358@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 28 Aug 2004 19:14:35 %2B0900." <7mk6vj4lis.wl@black.imgsrc.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <7mk6vj4lis.wl@black.imgsrc.co.jp>, Jun Kuriyama writes: >> After using 3 floppy images, virtual machine is locked up at probing >> stage. Here is the last output with verbose boot: >> >> http://www.imgsrc.co.jp/~kuriyama/tmp/20040824-vmware.png > >I've confirmed which commit breaks this by using binary search from >{build,install}kernel on old (working) 5-current. > >Result is: > >2004-08-20 10:00:00+00 OK >2004-08-20 15:30:00+00 Bad > >so, we have phk's commit below between them. > >----- >phk 2004-08-20 15:14:25 UTC > > FreeBSD src repository > > Modified files: > sys/sys fdcio.h > usr.sbin/fdcontrol fdcontrol.c > usr.sbin/fdformat fdformat.c > usr.sbin/fdread fdutil.c > sys/dev/fdc fdc.c fdc_acpi.c fdc_isa.c fdc_pccard.c > fdcvar.h > Log: > Rewrite of the floppy driver to make it MPsafe & GEOM friendly: >----- > >VMware said "unrecoverable error" and "Exception 0xc0000005 {access >violation} has occured" and virtual machine has stopped. Is there any way to get mode detailed diagnostics ? Like the program counter or anything ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3181.1093688358>