From owner-freebsd-current Tue Jul 11 10: 1:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 8621E37C016 for ; Tue, 11 Jul 2000 10:01:24 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.15 #1) id 13C3Ov-0000Ci-00; Tue, 11 Jul 2000 19:00:53 +0200 From: Sheldon Hearn To: Eric Anholt Cc: current@FreeBSD.ORG Subject: Re: syscons hangs with -current In-reply-to: Your message of "Mon, 10 Jul 2000 11:14:16 MST." Date: Tue, 11 Jul 2000 19:00:52 +0200 Message-ID: <787.963334852@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Jul 2000 11:14:16 MST, Eric Anholt wrote: > I am getting freezes on -current as of my last two updates, Jul. 9 > and today, Jul. 10. My previous update was around Jun 14. I can > boot the kernel from the last update just fine, though ppp doesn't > work due to net changes. Just as a datapoint, I'm getting reboots and hard locks shortly after reboot (no more than 20 minutes) using a kernel built from sources from around 22H30 last night. A kernel from around the same time on Friday last week does not exhibit the problem. > sc1: at flags 0x100 on isa0 Note, though, that my box _does_ make it _well_ past the kernel probe stage and doesn't show the peculiar sc1 device at probe time. Any idea what that is, by the way? You haven't perhaps got ``device sc 2'' or something crazy in your kernel config file? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message