Date: Thu, 02 Oct 2008 10:31:15 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: 6-CORE Dunnington Message-ID: <gc20sh$1pa$1@ger.gmane.org> In-Reply-To: <1222877744.29968.76.camel@buffy.york.ac.uk> References: <f12f408a0810010836p55e39f52k23e79fc46024dab@mail.gmail.com> <1222877744.29968.76.camel@buffy.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig553FE7742F93993CA3C4CA0D Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Gavin Atkinson wrote: > On Wed, 2008-10-01 at 23:36 +0800, Mars G Miro wrote: >> Hiya >> >> Has anyone successfully tried installing and running FreeBSD on >> Intel's newest 6-CORE Dunnington? >> >> I was able to install 200809-CURRENT on it but after recompiling >> the kernel (taking out WITNESS, INVARIANTS KGDB et al) I found out >> that I could not boot it anymore. What's weird is that I could not >> boot the same 200809-CURRENT CD that I used the first time. Just hangs= >> on >> .... >> uhci0: [GIANT-LOCKED] >> uhci0: [ITHREAD] >> .... >> >> I've also tried installing via PXE and it always hangs on the above= >> spot, even using a -CURRENT from Sept 26 and PXE-booting it. No go :-(= >=20 > Firstly, does it seem to be detecting all six CPUs correctly? Are you > able to reboot with the old kernel and put a verbose dmesg and the > output of "acpidump -dt" up on the web somewhere? It would also be > interesting to know if anything else is printed after the above when it= > hangs on a verbose boot. >=20 > There was a report back in July about FreeBSD not discovering all the > CPUs on the board, but there was no mention of hanging on boot. That was me and I actually did discover a similar boot problem later. For me, it turned out that booting FreeBSD after booting Linux worked fine, but booting FreeBSD from cold-boot hung in a similar way. I didn't discover what the problem was with detecting all 6 cores but I might have been a buggy/development BIOS. --------------enig553FE7742F93993CA3C4CA0D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI5IbUldnAQVacBcgRAgcaAJ9QdmfpSskfhgaefp2bktKPWW3P5ACgkyxT 2j6//Z8HV/N8SObcZSjtJJI= =WMmS -----END PGP SIGNATURE----- --------------enig553FE7742F93993CA3C4CA0D--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?gc20sh$1pa$1>