From owner-freebsd-current Wed Dec 2 04:13:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13843 for freebsd-current-outgoing; Wed, 2 Dec 1998 04:13:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pyrl.eye (ppp-115.isl.net [199.3.25.115]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA13836 for ; Wed, 2 Dec 1998 04:13:17 -0800 (PST) (envelope-from ortmann@sparc.isl.net) Received: (from ortmann@localhost) by pyrl.eye (8.9.1/8.9.1) id GAA01094; Wed, 2 Dec 1998 06:12:12 -0600 (CST) (envelope-from ortmann) From: Daniel Ortmann Message-Id: <199812021212.GAA01094@pyrl.eye> Subject: a problem tracked down (was "Re: sio breakage") In-Reply-To: <199812010450.PAA27337@godzilla.zeta.org.au> from Bruce Evans at "Dec 1, 1998 3:50:12 pm" To: bde@zeta.org.au (Bruce Evans), gurney_j@efn.org (John-Mark Gurney) Date: Wed, 2 Dec 1998 06:12:10 -0600 (CST) Cc: bde@zeta.org.au, kato@ganko.eps.nagoya-u.ac.jp, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG, geoffb@demon.net, johan@granlund.nu, mike@smith.net.au, ortmann@sparc.isl.net X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Fixes: > >> kernel: send a fatal signal to applications that do this. > > > >How to detect this? > > Near the beginning of trap(): > > if ((frame.tf_eflags & PSL_I) == 0) > fatal(...); > > but this is too strong, since the application may be in the middle > of changing hardware state. Returning to the application probably > won't make the problem (the application's problem of changing state > atomically) worse, so we should enable interrupts and print an error > message. > > PSI_I must be checked even in traps from kernel mode because the trap > may be nested. In kernel mode, just enable interrupts and continue. I found the problem with my slow-running clock! Here is the fix: 1) disable power management in the BIOS 2) remove apm from my kernel's config file Perhaps merely one of the above is sufficient. I did both 1 & 2. I recall that my sio silo overflow messages began to appear suddenly after a period of time ... as if a switch were thrown. Perhaps the above steps will also make those messages go away; this is probable since they seemed to appear at the same time. I will log a pr right away. -- Daniel Ortmann IBM Circuit Technology 2414 30 av NW, #D E315, bldg 040-2 Rochester, MN 55901 3605 Hwy 52 N 507.288.7732 (h) 507.253.6795 (w) ortmann@isl.net ortmann@us.ibm.com -- "The answers are so simple and we all know where to look, but it's easier just to avoid the question." -- Kansas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message