From owner-freebsd-hackers  Sat Mar  6  5:11:31 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12])
	by hub.freebsd.org (Postfix) with ESMTP id 65DF8151D0
	for <freebsd-hackers@FreeBSD.ORG>; Sat,  6 Mar 1999 05:10:59 -0800 (PST)
	(envelope-from nsouch@teaser.fr)
Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40])
	by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id OAA09535;
	Sat, 6 Mar 1999 14:10:29 +0100 (MET)
Received: (from nsouch@localhost)
	by teaser.fr (8.9.2/8.9.1) id MAA00799;
	Sat, 6 Mar 1999 12:33:55 +0100 (CET)
	(envelope-from nsouch)
Message-ID: <19990306123355.04328@breizh.teaser.fr>
Date: Sat, 6 Mar 1999 12:33:55 +0100
From: Nicolas Souchu <nsouch@teaser.fr>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: freebsd-hackers@FreeBSD.ORG, des@flood.ping.uio.no
Subject: Re: new ppbus driver problem
References: <199903052001.MAA51599@apollo.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <199903052001.MAA51599@apollo.backplane.com>; from Matthew Dillon on Fri, Mar 05, 1999 at 12:01:37PM -0800
X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT 
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Mar 05, 1999 at 12:01:37PM -0800, Matthew Dillon wrote:
>
>    This is with -current.
>
>    I've been getting crashes during boot with the new ppbus stuff and lpt0
>    enabled.

	Hmm, your the first reporting such problem.
>
>    It detects the parallel port just fine, but further on in the boot
>    sequence the system gets an RTC error and then it just locks up 
>    completely... it doesn't even get past the kernel config ( never gets
>    to execing init ).

	What's your hardware? Motherboard, and parallel port chipset?
	Parallel port is generaly handled by a superIO chip, but your
	system may rely on the PCI/ISA chip..
>
>    I was able to solve the problem by commenting out most of the probe code
>    in i386/isa/ppc.c, as shown below.  I don't know which port in the probe
>    code is causing the problem, but something in there is blowing up my
>    systems.
>
>    Maybe the probe code should be a little more conservative, with a
>    kernel config option to be less conservative ????

	A boot option is available for this. Undocumented :( flag 0x40
	for ppc at boot does it.
>
>					-Matt
>					Matthew Dillon 
>					<dillon@backplane.com>
>
>static int
>ppc_detect(struct ppc_data *ppc, int chipset_mode) {
>
>        int i, mode;
>
>        /* list of supported chipsets */
>        int (*chipset_detect[])(struct ppc_data *, int) = {
>#if 0
>                ppc_pc873xx_detect,
>                ppc_smc37c66xgt_detect,
>                ppc_w83877f_detect,
>#endif
>                ppc_generic_detect,
>                NULL
>        };
>
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-hackers" in the body of the message
>

-- 
nsouch@teaser.fr / nsouch@freebsd.org
FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message