From owner-freebsd-bugs Fri Aug 14 07:48:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05850 for freebsd-bugs-outgoing; Fri, 14 Aug 1998 07:48:08 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from post.mail.demon.net (post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA05765 for ; Fri, 14 Aug 1998 07:47:52 -0700 (PDT) (envelope-from neil@causality.com) Received: from (causality.com) [158.152.208.192] by post.mail.demon.net with esmtp (Exim 1.82 #2) id 0z7L8V-0000st-00; Fri, 14 Aug 1998 14:47:23 +0000 Message-ID: <35D447AD.946BB082@causality.com> Date: Fri, 14 Aug 1998 15:20:29 +0100 From: "Neil A. Carson" Organization: Causality Limited X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: bugs@FreeBSD.ORG Subject: Possible bugs in FreeBSD kernel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, While running FreeBSD no my laptop, I've come into the following problems. I'm using a slightly old -current source tree and possibly some of these issues may have been fixed---I can't see that they have though. As usual, be prepared to accept the possibility that I'm talking complete rubbish and have got everythign wrong :) I'm running ona Fujitsu Lifebook 900 laptop with P233 CPU. I have a plug-in 3Com Etherlink III PCMCIA card connected to a 10BaseT network. 1) Ethernet: This seems to pick up and use the zp driver, so my interface is zp0. - This driver, for some reason, eats system time for breakfast. On NFS ops my system regularly boosts to 70% of its time spent in the kernel... Don't know what doing. - During inward FTPs, I get around 100KB/sec xfer rates due to repeated stalls for around 1/2 sec. Wierd. - In intensive NFS ops (eg dd from /dev/zero to a file on an NFS mounted FS) I get very good xfer rates, but the thing occasionally hangs the kernel which then recovers 30-40 secs later. 2) APM: It seems a while ago in FreeBSD the APM `cpu lower clock rate on idle' option aws disabled. It used to use a #if NAPM>0 thing in there, but someone disabled this in favour of a function vector for the idle/hlt code instead. I can't see any evidence to suggest that this vector change was implemented in the general APM code, so it could be that most CPUs aren't saving power out there. I might have missed this, though. Sorry if this is a complete waste of time... Cheers, Neil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message