similar to: RELENG_8 kernel as of Apr 14 does not boot

Displaying 20 results from an estimated 400 matches similar to: "RELENG_8 kernel as of Apr 14 does not boot"

2006 Apr 28
1
link_elf: symbol cam_simq_alloc undefined
Hello, I'm trying to upgrade from 5-stable to 6-stable; after rebooting to the new kernel, the amr(4) module (amr.ko) refuses to load with this message: link_elf: symbol cam_simq_alloc undefined However, a quick nm(1) on /boot/kernel/cam.ko does show: ... 0000f0ac T cam_sim_set_path 0000efc4 T cam_simq_alloc 0000efd4 T cam_simq_free ... and cam.ko is already loaded before amr.ko.
2012 Dec 04
2
[releng_8 tinderbox] failure on sparc64/sparc64
TB --- 2012-12-04 23:10:18 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-12-04 23:10:18 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-12-04 23:10:18 - starting RELENG_8 tinderbox run for sparc64/sparc64 TB --- 2012-12-04 23:10:18 - cleaning
2008 Jan 29
1
kldload: Unsupported file type
Since updating to 6.3-RELEASE on two machines I see this message a lot. It is printed whenever a kernel module is loaded. The modules load OK. Nothing special or different about them. It seems to be harmless, but any idea why it's started happening since the release? Cheers BMS
2013 Nov 25
7
[releng_8 tinderbox] failure on i386/i386
TB --- 2013-11-25 17:30:12 - tinderbox 2.20 running on freebsd-legacy2.sentex.ca TB --- 2013-11-25 17:30:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-11-25 17:30:12 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2013-11-25 17:30:12 -
2013 Jul 08
0
[releng_8 tinderbox] source tree update failure
TB --- 2013-07-08 08:10:00 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca TB --- 2013-07-08 08:10:00 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-07-08 08:10:00 - starting RELENG_8 tinderbox run for none/none TB --- 2013-07-08 08:10:00 -
2010 Feb 04
1
plm issues: error for "within" or "random", but not for "pooling"
Dear all I am working on unbalanced panel data and I can readily fit a "pooling" model using plm(), but not a "within" or "random" model. Reproducing the examples in vignette("plm") and in the AER package I encountered no such issues. ##unfortunately I cannot disclose the data, and it is too big anyway > dim(ibes.kld.exp.p[x.subs , ]) [1] 13189 34
2013 Feb 14
2
i386: vm.pmap kernel local race condition
Hi! I've got FreeBSD 8.3-STABLE/i386 server that can be reliably panicked using just 'squid -k rotatelog' command. It seems the system suffers from the problem described here: http://cxsecurity.com/issue/WLB-2010090156 I could not find any FreeBSD Security Advisory containing a fix. My server has 4G physical RAM (about 3.2G available) and runs squid (about 110M VSS) with 500
2003 Aug 11
1
FreeBSD Security Advisory FreeBSD-SA-03:09.signal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:09.signal Security Advisory The FreeBSD Project Topic: Insufficient range checking of signal numbers Category: core Module: sys Announced:
2012 Nov 03
1
freebsd-update and surces of 9.1-RC3
Hi! I'm trying to use freebsd-update for first time. I have 9.0-RELEASE installed without sources and I have read Handbook chapter and manual page for freebsd-update. "freebsd-update -r 9.1-RC3 upgrade" downloaded updates, its "install" command installed kernel and after reboot second "install" invocation installed binaries but not source tree that is needed to
2008 Jul 16
3
named.conf: query-source address
Hi! I fully understand and second efforts on educating people how to configure BIND to be stong to attacks and keep them from using "query-source address" with "port" option but how about binding named to particular IP address when host has many of them? Using "query-source address" without "port" is the only solution (not speaking of jails here) and safe
2003 Aug 14
4
bin/55346: /bin/sh eats memory and CPU infinitely
Hi! It seems /bin/sh in 4.8-STABLE has problem with SIGCHLD processing. In short, it often fails to process it correctly, zombies float around, jobs are not marked as finished in jobtab[] that fills memory and takes much CPU to be processed. Run this one-liner using /bin/sh and see hundreds of zombies: #!/bin/sh while :; do : & done A kernel will halt this as soon as it reaches limits and
2008 Sep 23
2
RELENG_7: buildworld failed with MODULES_WITH_WORLD=
Hi! I've just tried to build NanoBSD from 7.0-STABLE sources with MODULES_WITH_WORLD knob enabled and it failed. Note that NanoBSD uses make -j3 by default and I have dualcore system. ===> sys/modules/nfslockd (depend) @ -> /usr/local/src/sys machine -> /usr/local/src/sys/i386/include echo "#define INET6 1" > opt_inet6.h awk -f @/tools/vnode_if.awk @/kern/vnode_if.src
2013 Nov 29
1
kernel "mismatch" on r256420
I installed FreeBSD 10 from a BETA cd-rom. I chose 'experimental ZFS on root - mirror'. The FreeBSD firewall will not load. Any suggestions? This is from 'dmesg': KLD ipfw.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type This is from 'ls -l' of /boot drwxr-xr-x 2 root wheel 1.5K Nov 28 21:55 kernel/ This is from
2013 Feb 17
1
RELENG_8: amdtemp module and newer CPUs not working. MFC?
Hello, I'm running FreeBSD 8.3-stable on a machine with an AMD A8-5600K cpu. tingo at kg-quiet$ uname -a FreeBSD kg-quiet.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #2: Fri Jan 4 19:18:15 CET 2013 root at kg-quiet.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 tingo at kg-quiet$ dmesg | grep CPU | head -1 CPU: AMD A8-5600K APU with Radeon(tm) HD Graphics (3618.02-MHz K8-class CPU)
2003 Aug 09
18
[releng_4 tinderbox] failure on i386/i386
TB --- 2003-08-09 16:00:11 - starting RELENG_4 tinderbox run for i386/i386 TB --- 2003-08-09 16:00:11 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-09 16:00:11 - /usr/bin/cvs returned exit code 1 TB --- 2003-08-09 16:00:11 - ERROR: unable to check out the source tree TB ---
2012 Aug 01
5
[Full-disclosure] nvidia linux binary driver priv escalation exploit
Hi all! I found this today on FD: http://seclists.org/fulldisclosure/2012/Aug/4
2003 Sep 16
2
buildworld tries to write to DESTDIR?
Hi! I'm trying to cross-compile 4.8-STABLE world to install it over NFS later. I have ./make.conf: # start of file CPUTYPE=i486 KERNCONF?=CONS MODULES_WITH_WORLD=true DESTDIR=/mnt/cons # end of file I run: dir=`pwd` make __MAKE_CONF=$dir/make.conf buildworld 2>&1 | tee $dir/bw.log It fails: ===> gnu/usr.bin/groff/contrib ===> gnu/usr.bin/groff/contrib/mm sh
2008 Jun 25
3
Problem with /boot/loader
Hello, I have a problem with loader. I recently upgraded from 6_rel to 7_rel. Now when I install world there is a problem booting. Here is what I do: cd /usr/src make buildworld make buildkernel KERNCONF=BLACK make installkernel KERNCONF=BLACK At this point I can reboot and all is good. After boot I install the new world: cd /usr/src mergemaster -p reboot into single user mode cd /usr/src make
2019 Jan 24
2
LLVM Kaleidoscope : Compiling to Object Code - Segmentation Fault
Hi David! Thanks for reaching out, the codegen part of the tutorial is fine, but when I try to generate the object code file, it throws segfault. Also please note that I'm using release build of llvm, actually I don't know whether that is the root cause or not. I also run through valgrind, it seems like a invalid read from stack. |||Error Summary: | |1 errors in context 1 of 1:
2012 Apr 17
4
top not restoring terminal echo/icanon correctly
(Please keep me CC'd as I'm not subscribed to the list) I'd like to request that folks running RELENG_8 (and RELENG_9, though I do not use it) please check the behaviour of their terminal after each of following commands are run (check terminal after each command): top -a (press "q" after 1 screen refresh) top -b If you find that your input characters in your shell