Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 Feb 2006 07:08:04 -0600
From:      "Donald J. O'Neill" <duncan.fbsd@gmail.com>
To:        Warner Losh <imp@bsdimp.com>
Cc:        freebsd-acpi@freebsd.org
Subject:   Re: Kernel panic with ACPI enabled
Message-ID:  <200602080708.04943.duncan.fbsd@gmail.com>
In-Reply-To: <20060207.205330.41703277.imp@bsdimp.com>
References:  <20060207203340.7C5F945041@ptavv.es.net> <200602071611.45274.duncan.fbsd@gmail.com> <20060207.205330.41703277.imp@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 07 February 2006 21:53, Warner Losh wrote:
> device isa is mandatory.  Remove eisa and add back isa and you'll be
> a heck of a lot happier.
>
> Warner
>

Isa is in DEFAULTS for 6.0 Stable, I left everything in DEFAULTS as is. 
I felt there were very good reasons for some devices being in there and 
they should stay there. Eisa was in 6.0 Release GENERIC, things 
appeared to be working, so when I immediately went to 6.0 Release, it 
wasn't changed, and again, things appeared to be working as expected. 

The only problem I had was with a USB mouse. If it was plugged in, the 
system would reach a point, on load up, and reboot. Removing the mouse 
would allow it to boot up fully and the mouse could be plugged in and 
was functioning. When I went back to using the PS-2 ball mouse the 
computer came with, I didn't have that problem at all. It was still 
there, I just avoided having to deal with it any further.

Do you think 'device eisa' could be what was causing the problem. As  
you suggested, I'll remove eisa from the conf file and run a buildworld 
sequence.

Thank you Warner, and everyone else. This thread has been a further 
education for me, I hope it has helped others also.

Don



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602080708.04943.duncan.fbsd>