From owner-freebsd-current  Mon Jan 11 21:03:25 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA26329
          for freebsd-current-outgoing; Mon, 11 Jan 1999 21:03:25 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from poboxer.pobox.com (port7.prairietech.net [208.141.230.84])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26319
          for <current@freebsd.org>; Mon, 11 Jan 1999 21:03:08 -0800 (PST)
          (envelope-from alk@poboxer.pobox.com)
Received: (from alk@localhost)
	by poboxer.pobox.com (8.9.1/8.9.1) id XAA01754;
	Mon, 11 Jan 1999 23:01:07 -0600 (CST)
	(envelope-from alk)
From: Tony Kimball <alk@pobox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 11 Jan 1999 23:01:02 -0600 (CST)
X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.<li^!8ecK]}3L-
	6`ZQW3}kxy*5]B<KA"&iBl58"/$W-0PP`B7c%'XczR)8T0VN47L`rQlu8qBIX4TJ|v'D%:k7GO%v4A
	Os>Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO
	5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed
Reply-To: alk@pobox.com
To: current@FreeBSD.ORG
Subject: more psm problems, and an ide thingy
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <13978.54629.887665.309144@avalon.east>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


FYI, and a propos of the other recent mail on this subject,
I got this on my mode 0 mouse today:
  Jan 11 16:18:59 avalon /kernel: psmintr: out of sync (0080 != 0000).
and then it stopped working until reboot.

On another subject, I'm getting an increasing number of these:
  Jan 11 20:41:37 avalon /kernel: wd2: interrupt timeout (status 50<rdy,seekdone> error 0)
  Jan 11 20:41:37 avalon /kernel: wd2: wdtimeout() DMA status 1<active>

I will assume the device is just bad, and replace it, but this is a
new failure mode to me -- I've never seen this sort of behaviour for
failing IDE drives in the past.  In this case, the I/O always
completes *eventually* -- which seems suspiciously like a driver bug.

Here's the device boot info:
  Jan 11 11:38:45 avalon /kernel: wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
  Jan 11 11:38:45 avalon /kernel: wdc1: unit 0 (wd2): <WDC AC36400L>, DMA, 32-bit, multi-block-16
  Jan 11 11:38:45 avalon /kernel: wd2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S
 

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