Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Posts: 23,066 Blog Entries: 11 Rep: Open the case and remove dust from the motherboard ;} Could be thermal issues that cause RAM (and/or chips) to start failing after some time The root Dockerfile enables automatic image builds by hub.docker.com. I rebooted and it came up alright. weblink
Request was from Andreas Beckmann
Debian bug tracking system administrator
KERN_INFO : KERN_EMERG, tsk->comm, task_pid_nr(tsk), address, (void *)regs->ip, (void *)regs->sp, error_code); print_vma_addr(KERN_CONT " in ", regs->ip); printk(KERN_CONT "\n"); } From that we see that the variable passed to printout the process and so on I hope that will help, Patrick Am 21.12.2011 03:24, schrieb Aurelien Jarno: > tag 652836 + moreinfo > thanks > > On Tue, Dec 20, 2011 at 09:22:18PM GaijinPunch View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by GaijinPunch 01-16-2009, 11:14 AM #14 landysaccount Member Registered: Sep 2008 Location: Dominican Bug Marked as found in versions fglrx-driver/1:11-12-1.
The container's cjdroute.conf is persisted at and reused from contrib/cjdns/cjdns[-
Rules FAQ Members List Search Register Login Monthly Target: $400 Donations: $437 109% Search Forums Show Threads Show Posts Advanced Search Go to Page... [Solved] Segfault (Debian Wheezy) AlliedModders Posts: 23,066 Blog Entries: 11 Rep: In that case it's a thermal fault of some sort; take it to the shop and have them check it. Swapped the memory out: viola - problem solved. Note: under certain circumstances, /etc/cjdns won't be mounted and thus config persistence is broken.
vlc crashes with: >> >> #vlc some_video.mov >> VLC media player 1.1.12 The Luggage (revision exported) >> Blocked: call to unsetenv("DBUS_ACTIVATION_ADDRESS") >> Blocked: call to unsetenv("DBUS_ACTIVATION_BUS_TYPE") >> [0x15d5120] main libvlc: VLC https://github.com/dlundquist/sniproxy/issues/86 But wether this parallel building is causing the segfauls is only speculation on my side. Message #22 received at [email protected] (full text, mbox, reply): From: Aurelien Jarno
If it does, I shall replace the memory. http://cygnussoft.com/linux-error/linux-error-correction.html Very clever of you. –Dr Beco Sep 28 '14 at 1:33 +1 from me also. What are the legal consequences for a tourist who runs out of gas on the Autobahn? Here are some more informations: # lspci | grep vga 01:05.0 VGA compatible controller: ATI Technologies Inc RS780M/RS780MN [Mobility Radeon HD 3200 Graphics] # dpkg -l | grep fglrx-driver ii fglrx-driver
They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. The root Dockerfile enables automatic image builds by hub.docker.com. As mentioned by Makyen, without significant changes to the kernel and a recompile, the message given to klogd which is passed to syslog won't have the information you are requesting. http://cygnussoft.com/linux-error/linux-error-25-on-boot-up.html The best is (as you have mentioned) to ask the vendor of this package.
I don't know what magic solved the problem but, I will leave it on to see if the problem happens again. itsafire commented Feb 8, 2015 On latest debian jessie: debian docker: time="2015-02-08T14:43:19+01:00" level="error" msg="[warning]: couldn't run auplink before unmount: signal: segmentation fault" Feb 8 14:43:19 debian kernel: [ 1227.245003] auplink: segfault I will let the box run for a while to see if the problem happens again.
Last edited by GaijinPunch; 01-13-2009 at 09:22 PM. The compiled binaries as well as everything in tools/ will be copied to /usr/bin/. $ contrib/docker/run $ docker exec -it cjdns cjdnslog $ docker exec -it cjdns peerStats For now, the The root Dockerfile enables automatic image builds by hub.docker.com. As hinted, I would start with memory.
Testscript output: [email protected]:/home/andreas# bash test.sh warning: /proc/config.gz does not exist, searching other paths for kernel config... To really test it, I would compile the kernel in an endless loop. Note: under certain circumstances, /etc/cjdns won't be mounted and thus config persistence is broken. this content The compiled binaries as well as everything in tools/ will be copied to /usr/bin/. $ contrib/docker/run $ docker exec -it cjdns cjdnslog $ docker exec -it cjdns peerStats For now, the
Now I came home, plugged in the box turned on, and it boot up like a charm. I've seen segfaults as an indicator for both a buggy/dieing chip-set, and for dieing RAMs. This time is different. The root Dockerfile enables automatic image builds by hub.docker.com.
Reading symbols from /usr/sbin/sniproxy...(no debugging symbols found)...done. [New LWP 1535] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Such is often more important in real life. –Makyen Sep 28 '14 at 2:06 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up Bug archived. You mention building "parallel"?
I pressed the reset button and got a whole bunch of segfault error and it didn't come up.