From owner-freebsd-current Fri Dec 15 11:37:02 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA13005 for current-outgoing; Fri, 15 Dec 1995 11:37:02 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA12994 for ; Fri, 15 Dec 1995 11:36:49 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id UAA03732; Fri, 15 Dec 1995 20:28:57 +0100 Message-Id: <199512151928.UAA03732@ra.dkuug.dk> Subject: Re: -current kernel is *very* unusable To: nate@rocky.sri.MT.net (Nate Williams) Date: Fri, 15 Dec 1995 20:28:57 +0100 (MET) Cc: current@FreeBSD.ORG In-Reply-To: <199512151757.KAA16788@rocky.sri.MT.net> from "Nate Williams" at Dec 15, 95 10:57:06 am From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG Precedence: bulk In reply to Nate Williams who wrote: > > I just updated my laptop to -current so I could start playing with the > PC-Card stuff, and it's basically un-usable. > > I'm getting complete hangs, reboots with no core dumps, and I can't even > get into DDB. The box ran 2.0.5 until 2 days ago, and was able to do a > make world w/out rebooting, so I suspect it's the new code. I'd back up > to an older version of -current, but I'm not even sure which time is a > good time to bring it to. I'm seeing much of the same here, the matcd driver hangs solid on the first couble of reads, i get "strange" looking files when checking out of cvs (ie files with single to multiple chars changed). All in all I'd say -current is totally screwed at this point in time :( I also have seen the dreaded keyboard hang in syscons (so now I have the opportunity to fix it :) ) I get core dunps all over the place if I stress the system a little, ie a cvs update will produce multiple coredumps if I start a Xsession on another vty. It seems we have some really bad stuff in there somewhere. I've checked on my old system from about 28 september, and it doesn't have the above problems, even the atapi driver works there ;( > > In any case, I can't even provide anyone with a backtrace or other help > since I can't even get into the debuuger and apparently panic isn't > being called before it reboots. Same here... > > What can I do to help out? Hmm, I'll ask the same question (and go fix syscons & the atapi stuff :) ) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time.