RE: Bus error: 10 (core dumped) on FreeBSD 7.0
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Vladimir Ch. Sent: Sunday, March 16, 2008 12:51 AM To: freebsd-questions@freebsd.org Subject: Bus error: 10 (core dumped) on FreeBSD 7.0 After upgrading to FreeBSD 7.0 some of the programs stopped working: when trying to launch emacs or sbcl I am getting Bus error: 10. Searching the internet revealed that this could be hardware problem - but 6.2, 6.3 ran the same box before without any errors. Windows XP also works on the same computer. I use GENERIC kernel. Did you recompile every program on your system after you upgraded to 7.0 or did you just assume that the 6.3 binaries would run unmodified? See: http://www.freebsd.org/releases/7.0R/announce.html ...Updating Existing Systems An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes a major version upgrade, so no matter which method you use to update an older system you should reinstall any ports you have installed on the machine. This will avoid binaries becoming linked to inconsistent sets of libraries when future port upgrades rebuild one port but not others that link to it. This can be done with: # portupgrade -faP after updating your system. Note some of the tools to help with this or the instructions below for FreeBSD Update are not installed by default (e.g. portupgrade, gpg, or similar tools like portmaster... Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bus error: 10 (core dumped) on FreeBSD 7.0
At 03:51 AM 3/16/2008, Vladimir Ch. wrote: After upgrading to FreeBSD 7.0 some of the programs stopped working: when trying to launch emacs or sbcl I am getting Bus error: 10. Searching the internet revealed that this could be hardware problem - but 6.2, 6.3 ran the same box before without any errors. Windows XP also works on the same computer. I use GENERIC kernel. You need to rebuild your ports if you have not done so. You will need to also rebuild any libraries the ports depend on as well. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bus error (core dumped)
Hello all i am tring to get apache13_modssl this on FreeeBSD ver 4.11 stable to work. apachectl start works ok but when i try to start apachectl startssl i get this on the command line tokyo.computerking.ca /usr/local/etc/apache #apachectl startssl Bus error (core dumped) I get nothing in /var/log/apache/httpd-error.log or /var/log/apache/sl.computerking.ca.ssl-httpd-error.log which is my log for the first and only virtual ssl host. i get this in my /var/log/apache/ssl_engine_log [06/Nov/2006 14:28:13 76200] [info] Server: Apache/1.3.37, Interface: mod_ssl/2.8.28, Library: OpenSSL/0.9.8a [06/Nov/2006 14:28:13 76200] [info] Init: 1st startup round (still not detached) [06/Nov/2006 14:28:13 76200] [info] Init: Initializing OpenSSL library [06/Nov/2006 14:28:13 76200] [info] Init: Loading certificate private key of SSL-aware server sl.computerking.ca:443:443 [06/Nov/2006 14:28:13 76200] [info] Init: Seeding PRNG with 136 bytes of entropy [06/Nov/2006 14:28:13 76200] [info] Init: Generating temporary RSA private keys (512/1024 bits) could this be that my self signed cert is 2048 bits it always seemed to work with apache2 please help. -- Computer King/CaNMail http://www.computerking.ca http://www.canmail.org Sales, Service, and Hosting Email, Data, and Web Packages Ask about web design specials Affiliates http://www.computerking.ca/pages/links/affiliates/affiliates.htm Maybe Computer Science should be in the College of Theology. -- R. S. Barton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Antwort: Re: bus error on build/ portupgrade is doing nothing
Hi, bus error I receive the following output on each port i try to upgrade. So, i thought it could be a problem of RAM, after changing the RAM twice, the problem ist still there, so what could be the problem? #portupgrade unzip --- Upgrading 'unzip-5.52_1' to 'unzip-5.52_2' (archivers/unzip) --- Building '/usr/ports/archivers/unzip' === Cleaning for unzip-5.52_2 === Extracting for unzip-5.52_2 = Checksum OK for unzip552.tar.gz. === Patching for unzip-5.52_2 === Applying FreeBSD patches for unzip-5.52_2 === Configuring for unzip-5.52_2 === Building for unzip-5.52_2 NOTE: use bsd target for non-Intel FreeBSD compiles (if any). make unzips CC=cc LD=cc AS=cc CF=-Wall -I. -DASM_CRC -DUNIX -DBSD -O -pipe -DUSE_UNSHRINK AF=-Di386 -O -pipe -DUSE_UNSHRINK CRC32=crc_gcc cc -c -Wall -I. -DASM_CRC -DUNIX -DBSD -O -pipe -DUSE_UNSHRINK unzip.c unzip.c: In function `unzip': unzip.c:1032: internal compiler error: Bus error Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Does it always die at the same place in the build? Typically when I've seen internal compiler error, bad hardware is the culprit. Especially if the build dies at different places each time. It is always the same place where the build dies. Also, trying to build the world, stops with a compiler error. Ah, FreeBSD 5.4-RELEASE-p6. (2) portupgrade does not build Trying to update amavisd-new or apache with portupgrade does not work. It just do nothing. So, other ports are working to update, others not. So what could be the problem? If you run portupgrade with -v, does it give any more detail? Hard to say what the problem might be without more details. Based on your first question, it's very likely to be a symptom of the same problem. Uh, my fault. -v says that the port is up-to-date, but it is not. Maybe a problem with the INDEX. I have this problem also on a machine which builds ports and world without any error, so i do not think it is based on the same problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FW: Re: BUS ERROR from freecolor
hi I have Compaq Deskpro 4000, Processor Celeron 400MHz # sysctl hw hw.machine: i386 hw.model: Pentium II/Pentium II Xeon/Celeron hw.ncpu: 1 hw.byteorder: 1234 hw.physmem: 527929344 hw.usermem: 424464384 hw.pagesize: 4096 hw.floatingpoint: 1 hw.machine_arch: i386 hw.realmem: 536870912 hw.aac.iosize_max: 65536 hw.an.an_dump: off hw.an.an_cache_mode: dbm hw.an.an_cache_mcastonly: 0 hw.an.an_cache_iponly: 1 hw.ata.ata_dma: 1 hw.ata.wc: 1 hw.ata.atapi_dma: 0 hw.cardbus.debug: 0 hw.cardbus.cis_debug: 0 hw.cs.debug: 0 hw.cs.ignore_checksum_failure: 0 hw.cs.recv_delay: 570 hw.firewire.try_bmr: 1 hw.firewire.hold_count: 3 hw.firewire.fwmem.eui64_hi: 0 hw.firewire.fwmem.eui64_lo: 0 hw.firewire.fwmem.speed: 2 hw.firewire.fwe.stream_ch: 1 hw.firewire.fwe.tx_speed: 2 hw.firewire.fwe.rx_queue_len: 128 hw.firewire.sbp.auto_login: 1 hw.firewire.sbp.max_speed: -1 hw.firewire.sbp.exclusive_login: 1 hw.firewire.sbp.login_delay: 1000 hw.firewire.sbp.scan_delay: 500 hw.firewire.sbp.use_doorbell: 0 hw.firewire.sbp.tags: 0 hw.pccard.debug: 0 hw.pccard.cis_debug: 0 hw.cbb.start_memory: 2281701376 hw.cbb.start_16_io: 256 hw.cbb.start_32_io: 4096 hw.cbb.debug: 0 hw.pcic.intr_mask: 57016 hw.pci.enable_io_modes: 1 hw.pci.do_powerstate: 0 hw.pci.host_mem_start: 2147483648 hw.pci.irq_override_mask: 57080 hw.wi.txerate: 0 hw.wi.debug: 0 hw.xe.debug: 0 hw.intr_storm_threshold: 500 hw.availpages: 128889 hw.bus.devctl_disable: 0 hw.dc_quick: 1 hw.ste.rxsyncs: 0 hw.kbd.keymap_restrict_change: 0 hw.syscons.saver.keybonly: 1 hw.syscons.bell: 1 hw.syscons.sc_no_suspend_vtswitch: 0 hw.busdma.total_bpages: 33 hw.busdma.zone0.total_bpages: 1 hw.busdma.zone0.free_bpages: 1 hw.busdma.zone0.reserved_bpages: 0 hw.busdma.zone0.active_bpages: 0 hw.busdma.zone0.total_bounced: 0 hw.busdma.zone0.total_deferred: 0 hw.busdma.zone0.lowaddr: 0x hw.busdma.zone0.alignment: 4096 hw.busdma.zone0.boundary: 0 hw.busdma.zone1.total_bpages: 32 hw.busdma.zone1.free_bpages: 32 hw.busdma.zone1.reserved_bpages: 0 hw.busdma.zone1.active_bpages: 0 hw.busdma.zone1.total_bounced: 0 hw.busdma.zone1.total_deferred: 0 hw.busdma.zone1.lowaddr: 0x hw.busdma.zone1.alignment: 2 hw.busdma.zone1.boundary: 65536 hw.clockrate: 399 hw.instruction_sse: 0 hw.em0.debug_info: -1 hw.em0.stats: -1 hw.em0.rx_int_delay: 0 hw.em0.tx_int_delay: 66 hw.em0.rx_abs_int_delay: 66 hw.em0.tx_abs_int_delay: 66 greetings piotr ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! ---BeginMessage--- On Thu, 2005-07-14 at 16:26 +0200, Simon Barner wrote: PK wrote: I have freeBSD 5.4 and newest ports tree update. I've installed freecolor from ports without errors, but if I try to start it, I get following error: Works fine here. Please report this to freecolor's maintainer (see the Makefile). This might be a 64bit issue, so tell him what platform you are seeing this error on. He already has :) It works for me also, and I even gave him a pre-compiled package that was known to work on my system. I hadn't thought about the 64 bit issue - PK, what platform are you running this on? That said - it works on my sparc64... Cheers, Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 ---End Message--- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bus error w/ mozilla or firefox
Does it segment fault when you start it from console ? If it does, just delete .gtk*, it should work after that. Le Dimanche 10 Avril 2005 21:36, Gary Kline a écrit : People, I need some clues as to *why* after the gnome update script has finished on my laptop neither mozilla nor firefox run. Note that on my laptop, there were not many files that needed to be rebuilt. One question seems apropos here: why can't the gnome (and kde) upgrades be handled thru Packages rather than by source rebuilding? (AFter 2+ days of running the script here on tao --a 750MHz platform--I the script may have succeeded; the laptop in a 400MHz ThinkPad. ... ) Help? Suggestions anybody? gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bus error w/ mozilla or firefox
On Mon, Apr 11, 2005 at 01:11:14AM +0200, Bachelier Vincent wrote: Does it segment fault when you start it from console ? If it does, just delete .gtk*, it should work after that. It wasn't a segv, it was a Bus error (core dumped). This was left in ~/. -rw--- 1 kline kline 3612672 Apr 10 17:50 mozilla-bin.core I believe that the update script will run to completion once I have ruby18 updated. But it dies on me too... :-( gary Le Dimanche 10 Avril 2005 21:36, Gary Kline a écrit : People, I need some clues as to *why* after the gnome update script has finished on my laptop neither mozilla nor firefox run. Note that on my laptop, there were not many files that needed to be rebuilt. One question seems apropos here: why can't the gnome (and kde) upgrades be handled thru Packages rather than by source rebuilding? (AFter 2+ days of running the script here on tao --a 750MHz platform--I the script may have succeeded; the laptop in a 400MHz ThinkPad. ... ) Help? Suggestions anybody? gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Gary Kline [EMAIL PROTECTED] www.thought.org Public service Unix ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Resolved: Re: bus error
On Thu, Jun 26, 2003 at 02:41:40PM -0400 David S. Jackson [EMAIL PROTECTED] wrote: On Wed, Jun 25, 2003 at 03:49:19PM -0700 Joshua Oreman [EMAIL PROTECTED] wrote: for xinit.core: #0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1 Cannot access memory at address 0xbfbfe6bc. As I feared. If you've got the developer mentality, forge ahead. If not, forget about it :-) You have to recompile those programs with debugging flags. make configure the port, take a look at the software Makefile (the one in work/portname-portversion/), and look for a line that starts with CFLAGS=. Add ` -g' (without the quotes, of course), to the end. Run make inside the software directory (/usr/ports/category/port/work/port-portversion/). Take the newly produced executable (it should be either in the directory you ran 'make' in, or one of the subdirectories) and run it under gdb (gdb myexecutable). Type `run' at the gdb prompt. When it crashes, type `bt'. Send us the output :-) Turns out make doesn't finish operating. pkg -r'ed another vim package, This time when I execute it: /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libXi.so.6: invalid file format. Strangely, this happened while in a tty, not an x window. (X won't start, still.) I wound up removing the XFree86 package and rebuilding the port from scratch. I guess I could have reinstalled the package, too. Anyway, that worked, so far. -- David S. Jackson[EMAIL PROTECTED] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Comedy, like Medicine, was never meant to be practiced by the general public. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bus error
Joshua Oreman suggested I try bt while in gdb looking at the core files. The output from that command was: for vim.core: #0 0x2815a26b in memset () from /usr/libexec/ld-elf.so.1 Cannot access memory at address 0xbfbfe6e0. for xinit.core: #0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1 Cannot access memory at address 0xbfbfe6bc. There is no /etc/malloc.conf file. Should there be? [Sorry about not including the post--I had to get this off the archives, since I tried Earthlink's Spaminator, and it deleted everything from freebsd.org Oops.] -- David S. Jackson[EMAIL PROTECTED] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I was in Vegas last week. I was at the roulette table, having a lengthy argument about what I considered an Odd number. -- Steven Wright ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bus error
Bill Moran [EMAIL PROTECTED] wrote: Can you rule out hardware problems? Possibly a disk going bad? I hope you've been making backups. You didn't run fsck while the partition was mounted, did you? If so, umount the partition and run fsck until it reports no errors and see if that fixes things. The slice seems to fsck just fine. No errors. But, /mnt/usr1 is a different story though... Oof. -- David S. Jackson[EMAIL PROTECTED] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Faster, faster, you fool, you fool! -- Bill Cosby ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bus error
On Wed, Jun 25, 2003 at 05:49:30PM -0400 or thereabouts, David S. Jackson wrote: Joshua Oreman suggested I try bt while in gdb looking at the core files. The output from that command was: for vim.core: #0 0x2815a26b in memset () from /usr/libexec/ld-elf.so.1 Cannot access memory at address 0xbfbfe6e0. for xinit.core: #0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1 Cannot access memory at address 0xbfbfe6bc. As I feared. If you've got the developer mentality, forge ahead. If not, forget about it :-) You have to recompile those programs with debugging flags. make configure the port, take a look at the software Makefile (the one in work/portname-portversion/), and look for a line that starts with CFLAGS=. Add ` -g' (without the quotes, of course), to the end. Run make inside the software directory (/usr/ports/category/port/work/port-portversion/). Take the newly produced executable (it should be either in the directory you ran 'make' in, or one of the subdirectories) and run it under gdb (gdb myexecutable). Type `run' at the gdb prompt. When it crashes, type `bt'. Send us the output :-) There is no /etc/malloc.conf file. Should there be? It's okay the way it is. -- Josh [Sorry about not including the post--I had to get this off the archives, since I tried Earthlink's Spaminator, and it deleted everything from freebsd.org Oops.] -- David S. Jackson[EMAIL PROTECTED] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I was in Vegas last week. I was at the roulette table, having a lengthy argument about what I considered an Odd number. -- Steven Wright ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bus error
David S. Jackson wrote: Hi, First, forgive me if this doesn't come through devoid of html. I'm normally a mutt user, but I'm trying evolution. We'll see how it goes. I'm on a $.%-STABLE system, and I've been experiencing some disk errors; I did an fsck -y on the slice where /usr lives. (I forgot it was /usr when I did this.) Since then, I've received various program terminated with signal 10. Bus error. problems. Examples are vim and xinit. As you can imagine, I'm eager to fix this so I can get X back. Looking at the core files left behind by X and by vim, I see the following: *** snip *** GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software ... blah blah ... This GDB was configured as i386-unknown-freebsd ... (no debugging symbols found)... Core was generated by 'vim'. Program terminated with signal 10. Bus error. Reading symbols from /usr/X11R6/lib/libgtk12.so.2... (no debugging symbols found)...done. Reading symbols from /usr/X11R6/lib/libgdk12.so.2... (no debugging symbols found)...done. Reading symbols from /usr/local/lib/libgmodule12.so.3... (no debugging symbols found)...done. Reading symbols from /usr/local/lib/libglib12.so.3... (no debugging symbols found)...done. Reading symbols from /usr/local/lib/compat/pkg/libintl.so.2... (no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. #0 0x2815a26b in memset () from /usr/libexec/ld-elf.so.1 (gdb) *** snip *** That was for vim. Here's for xinit: *** snip *** GNU gdb 4.18 blah blah blah Core was generated by 'xinit'. Program terminated with signal 10. Bus error. Reading symbols from /usr/X11R6/lib/libXmu.so.6... (no debugging symbols found)...done. Reading symbols from /usr/X11R6/lib/libXt.so.6... (no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found...done. #0 0x2805826b in memset () from /usr/libexec/ld-elf.so.1 (gdb) *** snip *** I typed all this by hand, so hopefully I have it correct. Notes: this problem is about 48 hours old. So far I've tried remaking ld-elf.so.1 from /usr/src/libexec/rtld-elf and copying ld-elf.so.1 from /usr/obj/usr/src/libexec/rtld-elf to /usr/libexec/, but even from single user runlevel, this was not allowed. I've thought about remaking the system, but I'm thinking that if ld-elf.so is broken, things probably wouldn't make correctly for a new system. Am I wrong on that? I've also thought about reinstalling a binary distribution on top of all this (upgrade from a new 4.8-stable CD), but that's an even bigger risk, I would think. So, what would you gurus do? What should be my next step for trying to salvage my system here? Can you rule out hardware problems? Possibly a disk going bad? I hope you've been making backups. You didn't run fsck while the partition was mounted, did you? If so, umount the partition and run fsck until it reports no errors and see if that fixes things. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bus error (core dumped) when running pkg_add
On Fri, 27 Sep 2002, Søren Neigaard wrote: Date: Fri, 27 Sep 2002 19:44:57 +0200 From: Søren Neigaard [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Bus error (core dumped) when running pkg_add If I try to run pkg_add on either a tbz file, tgz file or without specifying any file, it core dumps. Here is the message: Bus error (core dumped) Sep 27 21:41:06 neigaard /kernel: pid 110 (pkg_add), uid 0: exited on signal 10 (core dumped) What is this, is it a hardware error? I dont seem to have any other problems, and I have just installed this 4.6.2 on this machine without any problems. Please help, I don't know what to do. Since no-one jumped in on this... A bus error is similar to a segfault, I believe. It means an app tried to access some memory outside it's accessible range or tried to access an array element outside the array's dimensions - something of that sort. I believe a 'bus' error means accessing a stack frame not owned by the app, or a bad access inside an owned stack frame? The pkg_* tools are pretty widely used and tested. This being the case I'd guess this may be a hardware error, possibly bad RAM? This is speculation at best. Possibly re-compile pkg_add with debug support and run it in a debugger or try some different memory? Which FBSD version are you runnnig? Arent there issues with the pkg_* tools and the tbz/tgz file types at the moment? Dunno, maybe you found a bug ? ;-) Good luck! JB # John Bleichert # http://vonbek.dhs.org/latest.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
