NetBSD Problem Report #36525

From woods@building.weird.com  Fri Jun 22 18:28:21 2007
Return-Path: <woods@building.weird.com>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id 7222163B882
	for <gnats-bugs@gnats.netbsd.org>; Fri, 22 Jun 2007 18:28:21 +0000 (UTC)
Message-Id: <m1I1nro-002IwcC@building.weird.com>
Date: Fri, 22 Jun 2007 14:28:20 -0400 (EDT)
From: "Greg A. Woods" <woods@planix.com>
Sender: "Greg A. Woods" <woods@building.weird.com>
Reply-To: "Greg A. Woods" <woods@planix.com>
To: gnats-bugs@NetBSD.org
Subject: unsupported APM device ID now causes a uvm_fault()
X-Send-Pr-Version: 3.95

>Number:         36525
>Category:       port-i386
>Synopsis:       unsupported APM device ID now causes a uvm_fault()
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jun 22 18:30:00 +0000 2007
>Originator:     Greg A. Woods
>Release:        netbsd-4 2007/06/19
>Organization:
Planix, Inc.; Toronto, Ontario; Canada
>Environment:


System: NetBSD 4.0_BETA2
Architecture: i386
Machine: i386
>Description:

	I've got an old Celeron 466 machine of some sort that I use for
	testing install CDs, and after doing a test install of the
	latest netbsd-4 build, I tried a "poweroff -q" to see if it
	would power itself off, since there was an indication that the
	apm(4) driver had successfully attached and initialized
	everything.

	(hand copied from the screen)

APM set power state <2ff,3>: unrecognized device ID (0x907)
uvm_fault(0xc00e27e0, 0xc440f000, 1) -> 0xe

	a stack backtrace at that point was impossible as there were
	just more faults in DDB.

	see also PR# 30135 for the underlying APM unknown device problem

>How-To-Repeat:

	try "poweroff -q" on an APM-capable machine....

>Fix:

	don't crash!

	(apparently according to PR# 30135 this used to halt the box)

>Unformatted:

Home	PR Database Search