amd64/67745: boot fails on compaq presario r3000z

Jung-uk Kim jkim at niksun.com
Sat Jun 26 00:17:38 GMT 2004


On Friday 25 June 2004 04:50 am, Jeff Connelly wrote:
> The following reply was made to PR amd64/67745; it has been noted
> by GNATS.
>
> From: Jeff Connelly <shellreef at yahoo.com>
> To: freebsd-gnats-submit at FreeBSD.org, newntrbr at ucla.edu
> Cc:
> Subject: Re: amd64/67745: boot fails on compaq presario r3000z
> Date: Fri, 25 Jun 2004 01:41:08 -0700 (PDT)
>
>  --0-1052444370-1088152868=:51949
>  Content-Type: text/plain; charset=us-ascii
>  Content-Id:
>  Content-Disposition: inline
>
>  >Loader succeeds, boot fails.  All boot options (safe
>  >mode, disable acpi) fail.  Fails immediately, with
>
>  nary a
>
>  >turn of the boot spinner (/-\|).  Fails with default
>  >modules loaded or unloaded.
>
>  Same problem occurs on Compaq Presario R3140US (which
>  is almost the same laptop), with FreeBSD amd64 5.2.1,
>  FreeBSD i386 5.2.1, and FreeBSD i386 4.10. Verbose
>  logging doesn't reveal any information. Debian amd64
>  sid and NetBSD 2.0-beta amd64 boot fine.
>
>  Any help greatly appreciated. Wish I could provide
>  more information, I'm open to suggestions on what to
>  try.
>
>  Attached is the dmesg of a successful boot of NetBSD
>  2.0 on the R3140US, I hope its helpful to FreeBSD
>  amd64 developers.

----- SNIP!!! -----

The last known bootable kernel is from FreeBSD 2.2.2-RELEASE(!).  With 
obvious reason, this is a bad choice.  2.2.5 panics with a different 
reason.  2.2.6, 2.2.7, and 2.2.8 boot kernels but shut down at the 
same place, i. e., probing sc0 -> kdbio test.  From FreeBSD-3, the 
symptom is basically the same as reported here.  DragonFlyBSD suffers 
the same problem because of the similarities in kernel init process.

Initially I thought loader is culprit but it doesn't seem so.  In 
-STABLE and -CURRENT, I traced it down to cninit() call from 
hammer_time() and init386() in src/sys/amd64/amd64/machdep.c and 
src/sys/i386/i386/machdep.c.  It seems one of hard-wired ISA hacks 
for vidconsole is responsible, probably keyboard hacks.  I am stuck 
at this point because of the tangled web of kludges. :-(

FYI, there is no serial port on the laptop, so comconsole is not an 
option.

I hope it helps,

Jung-uk Kim


More information about the freebsd-amd64 mailing list