From nobody  Wed Dec 25 01:26:15 1996
Received: (from nobody@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id BAA03453;
          Wed, 25 Dec 1996 01:26:15 -0800 (PST)
Message-Id: <199612250926.BAA03453@freefall.freebsd.org>
Date: Wed, 25 Dec 1996 01:26:15 -0800 (PST)
From: brian@mpress.com
To: freebsd-gnats-submit@freebsd.org
Subject: 2.2-BETA fails to boot on my laptop
X-Send-Pr-Version: www-1.0

>Number:         2277
>Category:       kern
>Synopsis:       2.2-BETA fails to boot on my laptop
>Confidential:   no
>Severity:       critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Dec 25 01:30:01 PST 1996
>Closed-Date:    Tue May 6 06:20:20 PDT 1997
>Last-Modified:  Tue May  6 06:23:30 PDT 1997
>Originator:     Brian Litzinger
>Release:        2.2-BETA
>Organization:
>Environment:
I can't boot in 2.2-BETA, 2.1.6 works fine though.

>Description:
2.1.6 works fine on my laptop. 2.2-ALPHA, 2.2-BETA crash just after
the kernel boot displays the last device (which is a disabled
apm0).  The top 3 lines of the display get messages up with the
crash happens and the machine is frozen.
system works fine with 2.1.6 abd a -current from about 9 months ago.
My system is a Chembook/Chicony 9750.  P5-133, 32MB with
C&T 65550 VGA controller driving 1024x768 LCD panel.
The crash happens if I install 2.2-BETA from scratch, or if I just run
a 2.2-BETA kernel under a 2.1.6 install.
>How-To-Repeat:
boot a 2.2-ALPHA, or 2.2-BETA kernel on my laptop.
>Fix:

>Release-Note:
>Audit-Trail:

From: root@uhf.wireless.net
To: freebsd-gnats-submit@freebsd.org, brian@mpress.com
Cc:  Subject: Re: kern/2277: 2.2-BETA fails to boot on my laptop (me too!)
Date: Sat, 28 Dec 1996 18:48:12 -0500 (EST)

 Same problem here on my TI Extensa 570CDT notebook.
 
 CPU: P100
 Memory: 16MB
 Crash and burn after displaying: apm0: disabled, not probed when using
 2.2-BETA boot disk or any 2.2-BETA kernel, but not with 2.1.6 kernels/boot disk.
 
 Please advice.
 
 Thanks.
 
 Bernie Doehner root@uhf.wireless.net
 

From: root@uhf.wireless.net
To: freebsd-gnats-submit@freebsd.org, root@uhf.wireless.net
Cc:  Subject: Re: kern/2277: 2.2-BETA fails... (still doesn't work in 2.2-GAMMA)
Date: Sat, 8 Feb 1997 13:47:25 -0500 (EST)

 Just tried the 2.2-GAMMA boot disk on my TI Extensa 570CDT. 
 Still hangs after displaying apm0 disabled, not probed.
 
 Bernie
 

From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: root@uhf.wireless.net, brian@mpress.com
Cc: freebsd-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: kern/2277: 2.2-BETA fails to boot on my laptop 
Date: Wed, 02 Apr 1997 19:07:01 +0900

 >From: root@uhf.wireless.net
 >To: freebsd-gnats-submit@freebsd.org, root@uhf.wireless.net
 >Cc:  Subject: Re: kern/2277: 2.2-BETA fails... (still doesn't work in 2.2-GAM
 M
 >A)
 >Date: Sat, 8 Feb 1997 13:47:25 -0500 (EST)
 >
 > Just tried the 2.2-GAMMA boot disk on my TI Extensa 570CDT. 
 > Still hangs after displaying apm0 disabled, not probed.
 > 
 > Bernie
 
 Have you tried 2.2-RELEASE? 
 
 If it doesn't work, would you try specifying the flag 0x01 to the
 `npx0' device and see how it fares?
 
 There have been many indications that the Pentium-optimized bcopy()
 routine in the kernel doesn't work when used to update display by the
 `syscons' device driver. There are reports that disabling the
 optimized bcopy() by specifying the above flag bit solved problems
 like yours.
 
 # Don't ask me why flag bits for the `npx0' device are used to control
 # Pentium optimized code.
 
 Hope this might help.
 
 Kazu
State-Changed-From-To: open->closed 
State-Changed-By: yokota 
State-Changed-When: Tue May 6 06:20:20 PDT 1997 
State-Changed-Why:  
Fixed in syscons.c 1.211 (-current) and 1.182.2.17 (RELENG_2_2). 
>Unformatted:
