From owner-freebsd-hackers Wed Feb 5 11:27:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA04082 for hackers-outgoing; Wed, 5 Feb 1997 11:27:30 -0800 (PST) Received: from dawn.ww.net (root@dawn.ww.net [193.124.73.50]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA04070 for ; Wed, 5 Feb 1997 11:27:16 -0800 (PST) Received: (from alexis@localhost) by dawn.ww.net (8.7.5/alexis 2.5) id WAA02074 for freebsd-hackers@freebsd.org; Wed, 5 Feb 1997 22:26:32 +0300 (MSK) Message-Id: <199702051926.WAA02074@dawn.ww.net> Subject: sio11 64 events for device without tp related problem? To: freebsd-hackers@freebsd.org Date: Wed, 5 Feb 1997 22:26:31 +0300 (MSK) From: Alexis Yushin Reply-To: alexis@ww.net (Alexis Yushin) X-Office-Phone: +380 65 2 26.1410 X-Home-Phone: +380 65 2 27.0747 X-NIC-Handle: AY23 X-RIPE-Handle: AY6-RIPE X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Evening, It started with syslogd writes out initial kernel messages (those, generated before the first process starts) and stumbles into siobi state. Sometimes it does not. (I mean after some reboots) Sometimes other process end up like that. slattach and more often /usr/bin/su. Sometimes not. But always right after kernel boots two messages 'sio11 64 events for device without tp' is generated. (I can get them with dmesg) Someone told me it is something well known and obvious. Of course I am investigating, but if it is please let me know. Thanks in advance, alexis -- It's all the same, only the names will change