similar to: 7.1 panic "vm_page_startup: inconsistent page counts"

Working on the Dell R420 today, got most of it working, even the broadcom ethernet cards! However, I get the following when I reboot the system: Syncing disks, vnodes remaining...4 Sleeping thread (tid 100107, pid 9) owns a non-sleepable lock KDB: stack backtrace of thread 100107: sched_switch() at sched_switch+0x19f mi_switch() at mi_switch+0x208 sleepq_switch() at sleepq_switch+0xfc

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"

I'm running a few servers sitting on top of a NetAPP file server ? everything runs great, but periodically I'm getting: nfs_getpages: error 13 vm_fault: pager read error, pid 11355 (https) errors on my screen ? not always same pid ? the annoying part is that it seems to always affect the same jail that is running .. if I shutdown all jails on that physical server, everything shuts down

In order to support the eventual MFC of a limited and experimental acpi(4) driver from -CURRENT, I have merged a few changes from -CURRENT to -STABLE including: - Power management interface (subr_power.c) - pmtimer(4) driver. Unlike -CURRENT this driver does not require 'device pmtimer' in the kernel config so that existing kernel configs do not have to be changed. - Updated

Hi, How can I load the alpm(4) module for SMBus support on my ASUS Vintage AH-1 system? It appears the I/O range it uses is claimed by the acpi(4) driver. Can I override the mapping in some way i.e. tell ACPI not to claim the range? I don't see anything obvious about this in the acpi(4) man page. thanks, BMS

after rebooting I get very often: ... mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 659 SECONDS mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 689 SECONDS mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 719 SECONDS ... another reboot usualy fixes this. danny

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

I'm getting the following warning, and then the system locks: ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 0x29, should be 0x48 Here's a pic: http://db.tt/O6dxONzI System is on a SuperMicro C7X58 motherboard that I just upgraded to BIOS 2.0a, which I would like to stay on if possible. I tried adjusting all the ACPI related BIOS settings without success. Bryce

Hi all, A recent thread inspired me to try getting a proper serial console working on a Supermicro X9SCL motherboard with IPMI. However I find that while I see loader messages and the getty I enabled after boot I don't get any kernel messages which does somewhat limit the utility.. The BMC creates COM3 (/dev/cuau2) which works with getty. I modified /boot/loader.conf like so..

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 =

Sorry for the repost... I don't think the first one posted.. posted to freebsd.stable, freebsd-current, Freebsd-hardware I checked the hardware in the online documentation manual/hardware It only lists the bits and peices of the machine say the hard drive controller and so forth. but doesn't give you a particular system to look at as a working machine with FreeBSD 6.2 does anybody

Hi all, I moved from 8.0-RELEASE to last week's -STABLE: $ uname -v FreeBSD 8.1-STABLE #0: Thu Sep 2 16:38:02 SAST 2010 root@XXXXX:/usr/obj/usr/src/sys/GENERIC and all seems well except my network card is unusable. On boot up: em0: <Intel(R) PRO/1000 Network Connection 7.0.5> port 0x3040-0x305f mem 0xe3200000-0xe321ffff,0xe3220000-0xe3220fff irq 10 at device 25.0 on pci0 em0: Setup

I upgraded my 7.0 system to 7.1-RELEASE with freebsd-update only to find that it no longer boots correctly, instead crashing with a BTX backtrace. If I break to the loader prompt and use 'ls /boot', I also get a backtrace. A new install of 7.1 on this hardware using a separate SCSI card and drive array also leads to a BTX backtrace. I have copied this below as the first (most

when booting stable/9 under a debug kernel with WITNESS enabled and verbose I get the following panic.. It seems very much like the discussion from a year back on current: http://lists.freebsd.org/pipermail/freebsd-current/2012-January/031375.html Any ideas? uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1 uhub0: 2 ports with 2 removable, self powered uhub1: 2

I have an on-going problem with DigiBoard Xem boards causing interrupt storms (since 4.x days). The FreeBSD driver polls the board and doesn't have a functional interrupt handler (and Linux behaves in the same way). It seems that under some conditions, the board will assert its interrupt line and, since there's no interrupt handler to clear whatever triggered the interrupt, the IRQ is

Hi, Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled This is stripped down kernel with everything possible loaded from modules. Any ideas? Did not see any warnings in UPDATING... ./danfe

Hi. On one of my fresh installed servers I am seeing the following output during boot: gptzfsboot: error 4 lba 30 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 30 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot:

> On 28/10/2011 04:14, Jan Mikkelsen wrote: > >/ Hi, > />/ > />/ There is a patch linked to from this PR, which seems very similar: > />/ > />/ http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/140416 > />/ > />/ http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html > />/ > />/ The problem is also consistent with running

Hi. I got this on today's RELENG_6 with Broadcom BCM5722 A0, ASIC rev. 0xa200. >From dmesg (bge related): bge0: <Broadcom BCM5722 A0, ASIC rev. 0xa200> mem 0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2 bge0: firmware handshake timed out, found 0x4b657654 bge0: firmware handshake timed out, found 0x4b657654 bge0: EEPROM read timed out bge0: failed to read EEPROM device_attach:

Well this is new. I haven't a clue what Dell has done on this R620, but this popped up today after I did a boat load of BIOS updates and tried to install stable/9 from our yahoo tree. If anyone sees the obvious solution here, I'd love to figure it out. found-> vendor=0x14e4, dev=0x165f, revid=0x00 domain=0, bus=2, slot=0, func=1 class=02-00-00, hdrtype=0x00, mfdev=1