From owner-freebsd-hackers Mon Feb 10 05:48:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA03312 for hackers-outgoing; Mon, 10 Feb 1997 05:48:28 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA03227 for ; Mon, 10 Feb 1997 05:47:38 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id OAA25403; Mon, 10 Feb 1997 14:46:03 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id OAA12169; Mon, 10 Feb 1997 14:36:21 +0100 (MET) Message-Id: <3.0.32.19970210143621.00b00c10@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 10 Feb 1997 14:36:23 +0100 To: Charles Mott From: Eivind Eklund Subject: Re: Bus Errors Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 07:57 PM 2/9/97 -0700, you wrote: >On Sun, 9 Feb 1997, Jamie Bowden wrote: > >> On Sun, 9 Feb 1997, Charles Mott wrote: >> >> > What does "Bus error" mean? A 'bus error' is when a CPU tries to access something that is outside the bus specs. This usually involve some sort of illegal address; eg, on 68000 and 68010 processors, accessing a word or long (16- or 32-bit value) on an odd address could cause this. Under FreeBSD, I don't know what would cause this instead of a segmentation fault - the 486 (at least) hasn't got any such thing as a bus error. I would guess a stack overrun somewhere causing very very wrong code to be executed. >> Amazingly enough, a buss error is a memory allocation error. At least it >> was under SunOS. I am guessing FreeBSD is the same on this. >> >> Jamie Bowden > >I've seen it a few times with the ppp+pktAlias1.9. It doesn't appear to >be getting malloc() errors, though. I see the problem with an ISP >connection that is really unreliable. Is anyone working on lqr for ppp? I haven't been having any problems with the 1.9 version at all. I'm running with all extra options turned off, though - no use_sockets, no same_ports. Could you give me a core dump of this (you'll have to run the program as root, turning the setuid bit off, otherwise it won't dump core) with the corresponding executable (compiled with -g, and not stripped)? >Is this type of post too off-target for -hackers? Well, usually people like to get some more information right away, as that make it easier to give specific help at once. Eivind Eklund perhaps@yes.no http://maybe.yes.no/perhaps/ eivind@freebsd.org