Displaying 20 results from an estimated 500 matches similar to: "stopping amd causes a freeze"
2013 Aug 18
1
wpi fatal firmware error with country de
My system was built yesterday. I just figured I'm not using the entire
frequency range available in Europe. This is a potential problem when
AP frequencies are not under my control.
FreeBSD mobileKamikaze.norad 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254418: Fri Aug 16 22:15:55 CEST 2013 root at mobileKamikaze.norad:/usr/obj/HP6510b-91/amd64/usr/src/sys/HP6510b-91 amd64
Setting the
2012 Dec 08
3
nullfs changes MFC
Hi,
I am going to merge latest batch of the nullfs improvements into
stable/9. This will bring up significant performance enchancements due
to use of the shared locks for lookups if the lower layer supports it,
much better caching on the nullfs layer, and proper handling of the text
segments on the nullfs. Also, it should improve the error recovery and
some corner cases with locking.
2008 Dec 02
6
repeatable crash on RELENG7
While trying to speed up nanobsd builds, I mounted /usr/obj on a
ramdisk and found my box crashing. Thinking it might be hardware, I
tried a separate machine, but with the same results. I have 4G of
ram (i386). Am I just running out of some kernel memory ? If so, is
there anything I can adjust to prevent this, yet still use mfs in this way ?
mdconfig -a -t malloc -s 1800M
newfs /dev/md0
2009 Feb 28
2
devd question
I'm trying to make devd run an stty command whenever a USB serial device
is attached. Unfortunately, $device-name is ucom[0-9] and the device
names are /dev/cuaU[0-9] - how do I get the correct name in the device
action? I haven't found a way to extract the number by itself, so I'm
stuck with specifying a separate rule for each number, like so:
attach 100 {
device-name
2007 Oct 07
6
issetugid() for other procs
Any way to check if another proc has run or been run by a proc that
is setuid or seteuid?
2008 Nov 12
2
dlopen-ing a library with OpenMP by a non-OpenMP process
Hello!
Currently, when a program built without OpenMP (-fopenmp) is trying to
dlopen a library, built with the feature, the result is a crash from
"bad system call":
#0 0x00000008009a223c in ksem_init () from /lib/libc.so.7
#1 0x0000000800998a8f in sem_init () from /lib/libc.so.7
#2 0x00000008011a6537 in omp_get_nested () from /usr/lib/libgomp.so.1
#3
2006 Mar 02
1
Failing to understand getrusage()
I'm failing to understand how getrusage() works, which is a bit perplexing,
because it doesn't seem like it would be terribly complicated.
I've attached the code. My aim is to verify that I can use getrusage() to
do (admittedly crude) instrumentation of which functions in my program are
allocating lots of memory[1]. So I figure I can call getrusage() at various
points and look at
2013 Sep 27
1
9.2-RC4 amd64 panic: vm_page_unwire
I'm running 9.2-RC4 on a handful of desktop and server machines (both
i386 and amd64). I have seen three panics (all vm_page_unwire) on one
of those systems only (amd64 server) during the past week.
The first two panics were triggered when shutting down the ntpd daemon
(a recent development snapshot version of ntpd: 4.2.7p387). Exiting a
later release (p388) has not triggered the panic.
2008 Jun 04
1
mystery: lock up after fs dump
I wouldn't report this if not for one coincidence (which is described
below). I have too little facts, so this is more of a mystery problem
tale than a real problem report.
There are two systems:
1. old, slow, i386, UP, 7-STABLE
2. new, fast, amd64, MP, 6.3-RELEASE
Systems are located at different physical locations.
What is common between them:
1. they both have the same backup strategy
2008 Jul 22
4
"sleeping without queue" ?
Hello!
My attempt to build openoffice.org-3 seems to be hanging. Pressing
Ctrl-T produces:
load: 0.11 cmd: tcsh 79759 [sleeping without queue] 0.00u 0.00s 0% 0k
(tcsh is used by OOo's build-script). What is this "sleeping without
queue" state, and why is process in it for so long?
This is an 4-CPU amd64 system with 4Gb of RAM. Only 16% of the swap is
currently in use and
2008 Sep 08
3
OpenSSH 5.1p1 - trouble connecting to ILO board
Hello,
Recently, the FreeBSD base system OpenSSH was upgraded to
OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007
Before the upgrade, with
OpenSSH_4.5p1 FreeBSD-20061110, OpenSSL 0.9.7e-p1 25 Oct 2004
I had no troubles connecting to the ssh server built-in into the
HP Proliant G5 ILO management board, authenticating by id_dsa,
v2 protocol. On that board, ssh server greets with
2012 Jul 23
3
local APIC error 0x40
Running FreeBSD 8.3 -- and updating sources on a daily base and building everything -- I found a new APIC/ACPI problem introduced in the past week.
I have a Toshiba Satellite U205 with an Intel Core Duo (not a Core 2). It used to work fine with both cores but then sometime in on the road to BSD 8.0 the machine began hanging. So I added to /boot/loader.conf
hint.apic.0.disabled="1"
2017 Nov 13
2
Experiment on how to improve our temporary file handing.
On Mon, Nov 13, 2017 at 01:46:32PM -0800, Davide Italiano wrote:
> On Mon, Nov 13, 2017 at 11:48 AM, Rafael Avila de Espindola
> <rafael.espindola at gmail.com> wrote:
> > Davide Italiano <davide.italiano at gmail.com> writes:
> >
> >>> I couldn't find any support for this on FreeBSD.
> >>>
> >>
> >> AFAIK FreeBSD supports
2013 Nov 09
1
10.0 BETA 3 with redports kernel panic
The redbuild boxes for redports are doing a very good and reliable job
getting kernel panics out of 10.0:
http://people.freebsd.org/~sbruno/redbuild_panic.txt
Pretty frequent and pretty nasty. Happening on multiple machines under
load.
sean
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc:
2013 Jul 17
1
syncer causing latency spikes
Hello,
I'm trying to investigate and solve some postgres latency spikes that
I'm seeing as a result of some behaviour in the syncer. This is with
FreeBSD 8.2 (with some local modifications and backports, r231160 in
particular). The system has an LSI 9261-8i RAID controller (backed by
mfi(4)) and the database and WALs are on separate volumes, a RAID 6 and
a RAID 1 respectively. It has
2009 Apr 25
1
installing crossbuilds
Back before the 7.0 Release I used to install cross builds by
NFS-mounting /usr/src and /usr/obj of the build machine on the
target machine and running:
# cd /usr/src
# env MAKEOBJDIRPREFIX=/usr/obj/<stuff> make installkernel KERNCONF=<kernconf>
...
This doesn't work any more because all the installation tools
are built for the architecture of the build system.
The alternative
2008 Dec 19
2
Kernel not mounting root
Hi all,
I did cvsup to 7-STABLE yesterday, build, installed and booted a new
kernel then buildworld.
Then I noticed that my PS/2 keyboard is not working at the loader menu
so I booted multiuser and did the make installworld part from there.
Then I tried to reboot but now it hangs after the line
Trying to mount root from ufs:/dev/ad4s1a
It sits there for at least 10min. I tried so far:
-
2008 Nov 12
5
System deadlock when using mksnap_ffs
I've been playing around with snapshots lately but I've got a problem on
one of my servers running 7-STABLE amd64:
FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64
I run the mksnap_ffs command to take the snapshot and some time later
the system completely freezes up:
paladin# cd /u2/.snap/
paladin#
2012 Sep 30
2
rsync over NFSv4
Hi,
my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site
9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01
CEST 2012 lbo@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC
i386) crashes reproducibly when rsync-ing files to an NFSv4 share on
the FreeBSD machine. The crash makes the system reboot. The crash
creates files in /var/crash which may be obtained
2008 Jul 29
8
Upcoming ABI Breakage in RELENG_7
Normally the FreeBSD Project tries very hard to avoid ABI breakage in
"Stable Branches". However occasionally the fix for a bug can not be
implemented without ABI breakage, and it is decided that the fix
warrants the impact of the ABI breakage. We have one of those
situations coming along for RELENG_7 (what will become FreeBSD 7.1).
The ABI breakage should only impact kernel modules