From owner-freebsd-current Thu Oct 7 8:48:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id BA7621522E; Thu, 7 Oct 1999 08:48:20 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id SAA16602; Thu, 7 Oct 1999 18:47:48 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Thu, 7 Oct 1999 18:47:47 +0300 (EEST) From: Adrian Penisoara To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, On Wed, 6 Oct 1999, Adrian Penisoara wrote: > hi again, > > On Tue, 5 Oct 1999, Matthew Dillon wrote: > > > : The problem is that the machine is completely locked, I can't get into > > :the debugger with CTR-ALT-ESC; no panics so there are no coredumps > > :catched. Any advise ? Could you escape in the debugger when you were hit > > :by these bugs ? > > > > If it's completely locked up and ctl-alt-esc doesn't work (and normally > > does work - try it on a working system to make sure that you've compiled > > in the appropriate DDB options), and you aren't in an X display > > (ctl-alt-esc isn't useful when done from an X display)... then your > > lockup problem is unrelated to mmap. > > No X on the machine, but CTRL-ALT-ESC doesn't work. > And another thing: I tried the MMAP "exploit"/test that has been floating > around at that time on another 3.2-STABLE machine SMP with 2 Pentiums and > it does lock the machine but you can switch consoles and escape to the > debugger; on the production server (K6-2 300) everything goes dead when > it happens (I haven't tried the MMAP test)... > > You're probably right, it's not the MMAP bug; but it's not faulty > hardware -- I'll have an undeniable proof in a few days, I have downgraded > to 3.1-STABLE as of 20th April... > Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault error (strange, it didn't look like a normal panic screen, just the message and the content of three registers, then the syncing disks message). It seems that I might be wrong about hardware not being the problem. I've changed the motherboard, CPU, memory and the video card and I'm waiting to see how much it's going to stay up (I have 1day 1hour uptime so far)... Thanks, Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message