NetBSD Problem Report #36525

From  Fri Jun 22 18:28:21 2007
Return-Path: <>
Received: from ( [])
	by (Postfix) with ESMTP id 7222163B882
	for <>; Fri, 22 Jun 2007 18:28:21 +0000 (UTC)
Message-Id: <>
Date: Fri, 22 Jun 2007 14:28:20 -0400 (EDT)
From: "Greg A. Woods" <>
Sender: "Greg A. Woods" <>
Reply-To: "Greg A. Woods" <>
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
Planix, Inc.; Toronto, Ontario; Canada

System: NetBSD 4.0_BETA2
Architecture: i386
Machine: i386

	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

	(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


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


	don't crash!

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


NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.