From owner-freebsd-mobile  Mon Jun  3 07:44:30 1996
Return-Path: owner-mobile
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA20019
          for mobile-outgoing; Mon, 3 Jun 1996 07:44:30 -0700 (PDT)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA20002;
          Mon, 3 Jun 1996 07:44:23 -0700 (PDT)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id IAA12911; Mon, 3 Jun 1996 08:42:39 -0600
Date: Mon, 3 Jun 1996 08:42:39 -0600
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199606031442.IAA12911@rocky.sri.MT.net>
To: Michael Smith <msmith@atrad.adelaide.edu.au>
Cc: hardware@FreeBSD.org, mobile@FreeBSD.org
Subject: Re: Laptop hardware FOUND
In-Reply-To: <199606020811.RAA27031@genesis.atrad.adelaide.edu.au>
References: <199606020539.PAA26867@genesis.atrad.adelaide.edu.au>
	<199606020811.RAA27031@genesis.atrad.adelaide.edu.au>
Sender: owner-mobile@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Michael Smith writes:
> Michael Smith stands accused of saying:
> > 
> > APM status is unclear : the boot probe reports:
> 
> I should clarify this: (wrt. Sharp PC9000)
> 
> Close-the-lid snooze, and do-nothing snooze and wakeups work _perfectly_
> OK, it's just running 'apm' (I thought I got it to run once, but it 
> certainly doesn't now) that makes it unhappy.
> 
> Nate, if there's anything I can help you with on the mobile- front, I'm
> finally in posession of something to test it on 8)

Cool.  Hosokawa already responded to the unknown event code problems,
but the hang is a new one.  It may be the 'WD-interrupt' bug, which I
see quite often.  Basically, our IDE driver is single threaded, so if
you miss an interrupt it'll wait forever for it rather than timing out.

Unfortunately, because of this bug it's *really* hard to debug other
parts of the system since you never know which bug is triggered.


Nate