similar to: Freebsd 7.0-RELEASE-p3 panics

I've got a HP dv8000 laptop. Setting up the wpi driver for wireless freezes the system on boot with the following error: wpi0 requested unsupported memory range wpi0: could not allocate memory resource It lists a pcbi device (pcbi4 i think) and an actual memory range, but since I have to reboot using kernel.old the /var/run/dmesg.boot is wiped with the info. Is there anyway to grab the

Sorry if this is a known problem... I've been tracking RELENG_4 on my Toshiba laptop for a while now; a couple of months ago (not sure when) my sound stopped working. More specifically, when it gets to the pcm probe, the boot hangs. I dual-boot with WinXP and figured that somehow XP had hosed the hardware, so I wrote it off. Today, I made world with RELENG_4_8, and voila, my sound's

Hello list, I have been fighting this problem for a few days now. I have changed memory and opened the case and monitored for heat. I have been getting the same panic about every 12 to 24 hours. I can let the system sit idle, or run it under a heavy load (cpu and disk), but the panics dont seem to be related to system load. It looks to me like a dangling pointer in softdep_update_inodeblock,

Box with fresh RELENG_7 panic under heavy network load (more than 50k connections). This panics seems to be senfile(2) related, because when sendfile disabled in nginx, I can't reproduce the problem. Backtrace in all cases like this: # kgdb kernel /spool/crash/vmcore.1 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General

Hello, I've met some quite strange reboots recently on my home gateway. I'm trying to reduce its power consumption, so I've loaded the cpufreq(4) driver, and enabled powerd. After this the box started to reboot randomly all over the place. I started to think what can cause the trouble, removing the cpufreq(4) support would be too trivial, so I've removed the ALTQ references from

Hi, After kernel panic I couldn't get gdb work properly. msi$ uname -sr FreeBSD 4.7-RELEASE msi$ gdb -k /usr/src/sys/compile/MSINW/kernel.debug vmcore.0 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show

Hello, There it is, all my computers on FreeBSD 9.1-RELEASE had panic. I can just say there is a problem in the 9.1-RELEASE because I had no panic before. What afraid me is that my production server also panic'ed a few days ago, fortunately it does not appears so often. This is a panic that happened on my desktop computer, with a graphic card. The crash usually appears when X starts. GNU

After about a day and a half or so of uptime, I'm getting the aforementioned panic on the server ... better then having it hang solid, but right now I'm not sure if this is replacing it, or just one being triggered earlier then the other ... First scan through Google, I came across some posts talking about NMBCLUSTERS ... since its at the same settings as my other server (the default)

Hello. I'm having a 4.7Rp9 server which is since months quite unstable, so I've compiled a debug kernel and got a crash dump. I'm a programmer and I know a little how to use gdb, I'm not so expert about FreeBSD kernel insides however, so I can't get much from it. Any kind of help is appreciated. This is the crash message: IdlePTD at phsyical address 0x0032f000 initial pcb

Hello, Since FreeBSD 9.1 I have strange problems with the distribution. Some servers are rebooting without any kernel panic, instanly. First i thought it's a problem with my KVM system, but one of my FreeBSD under a Dell R210 have the same problem. The servers concerned are now: - Monitoring server - LDAP test server - Some other servers, randomly (not in production). First i thought it's

this is 6.0-STABLE as for Mar 17. KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-PRERELEASE #2: Fri Mar 17 11:05:32 UTC 2006 vlad@host:/usr/src/sys/amd64/compile/DEF_WEB Timecounter

On Tue, Apr 15, 2008 at 12:20 PM, Roland Smith <rsmith@xs4all.nl> wrote: > On Tue, Apr 15, 2008 at 11:34:31AM -0700, Steve Franks wrote: > > Being a naturally curious guy, with your pointers, I've located the following: > > > > [steve@dystant /var/crash]$ sudo cat info.2 > > Yep. This is what you need. > > > > Dump header from device

Some more crashes of 4.8-RELEASE. Lets see what do I have today: # ls -l /var/crash total 1576676 -rw-r--r-- 1 root wheel 2 Jul 30 13:31 bounds -rw-r--r-- 1 root wheel 2193252 Jun 25 17:30 kernel.0 -rw-r--r-- 1 root wheel 2193252 Jul 4 00:08 kernel.1 -rw-r--r-- 1 root wheel 2193252 Jul 15 19:28 kernel.2 -rw-r--r-- 1 root wheel 2193252 Jul 16 17:50 kernel.3

9.2 PRERELEASE (today) / amd64 Hello, I'm seeing a panic while trying to build a poudriere repository. As far I can see it always happens when gam_server is started (ie xfce is running) and under disk load (poudriere bulk build) : (That is something new, the box was pretty stable) the complete crash dump (core.0.txt) is here: http://user.lamaiziere.net/patrick/panic_gam_server.txt Fatal

Hi. I've recently borrowed a SuperMicro 6013P-8 from a vendor for the purposes of testing it to see if FreeBSD and these machines will make a good replacements for our current flock of 11 Netra T1s running solaris. Things are going very well with the tests, with the glaring exception of the following crash: While doing some significant disk operations: du, deleting a different part of the

Hello after upgrading to 9.2-release i can see periodical page faults. advises welcome. examples: 1. Fatal trap 12: page fault while in kernel mode cpuid = 5; apic id = 22 fault virtual address = 0x18 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff8051095c stack pointer = 0x28:0xffffff88a9d77800 frame pointer =

[FreeBSD 7-STABLE/i386] Hello, I've got a 100 % reproductible panic with ipsec when using a 'ping -s 4000'. It works without ipsec My ipsec setup is very simple, i just use setkey: /etc/ipsec.conf flush; spdflush; add 192.168.1.21 192.168.1.200 esp 1011 -E rijndael-cbc "0123456789012345"; add 192.168.1.200 192.168.1.21 esp 1012 -E rijndael-cbc

Hello folks, I have a panic at shutdown related to FUSE. #0 doadump (textdump=<value optimized out>) at pcpu.h:234 234 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt full #0 doadump (textdump=<value optimized out>) at pcpu.h:234 No locals. #1 0xffffffff8090d9a6 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:449 _ep = (struct

Hello, I'm running 6.4-PRELEASE, last built on 2008-10-05 with /usr/src updated on the same day. I had a panic that looks to me very similiar to the one described here (hence the subject): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045405.html What caught my curiosity is the message: Unread portion of the kernel message buffer: acd0: WARNING - TEST_UNIT_READY read

Getting the following panic on a new Dell Poweredge 1650. This machine is going to be a VPN server and has a large number of pptp links configured. The machine is stable if mpd is not running. (kgdb) where #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 #1 0xc0229a0f in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:316 #2 0xc0229e4d in panic (fmt=0xc042876c "%s") at