similar to: KDB+DDB make interrupt storm on MSI motherboards go away it seems

Hi all, I have had this problem since day 1 on my new server. It has run since November 15th 2008, and serve approx. 10 GB worth of web traffic per month for the main site and then some 40 domains with mail and small web pages. (hence - it's NOT that busy yet) I started with 7.1-RELEASE-pX since I didn't have problems straight off - but it didn't last long. After a few days of

Hi All, I''m currently mid-project at the moment, and am scepticle in upgrading to Snow Leopard. If I do, will it affect my current Ruby on Rails set up on my machine?? Cheers -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

I've tested both 6.3 and 7.0-RC2, amd64 architecture, and have found the occurrence of an interrupt storm using an ASUS A8N-SLI Premium (nForce 4) motherboard with an AMD Opteron 175. Relevant dmesg output: atapci0: <nVidia nForce CK804 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 ata0: <ATA channel 0> on atapci0 ata1: <ATA

Colleagues, one of my servers had to be rebooted uncleanly and then I have backgrounded fsck locked for more than an our in snaplk: 742 root 1 -4 4 1320K 688K snaplk 0:02 0.00% fsck_ufs File system in question is 200G gmirror on SATA. Usually making a snapshot (e.g., for making dumps) consumes 3-4 minutes for that fs, so it seems to me that filesystem is in a deadlock. Any

Hi folks! I am currently involved in project which uses LLVM JIT and I have a couple of questions for you: 1) According to http://llvm.org/Features.html LLVM JIT supports only X86 and PowerPC, but LLVM code generator supports ARM too. Are there any plans for JIT to make support also for ARM backend? 2) Could LLVM JIT collect some hot traces from overall code and execute it separately (after

Hi, I have a LSI Logic sata/sas raid running, is there a way to see the state of the volume, like optimal, degraded or resyncing? I've tried several commands with camcontrol but I cant figure it out. -- Peter Ankerst?l peter@pean.org http://www.pean.org/

Hi, I've noticed some general instability with plugging in or removing USB devices with FreeBSD 7.x, even when the devices are not actively in use. I had this happen with umass and ucom devices 3 times today. The machine hangs solid, there are no obvious signs of a panic or trap to DDB. I can't provide backtraces unfortunately -- these hangs happen on both my laptop and desktop, and

i cannot read or write any disk inserted in my acd0 <PIONEER DVD-RW DVR-111D/1.29> when this device in udma mode. kernel endlessly repeat that acd0: setting up DMA failed and I can access my data on dvd or cd only if I set atacontrol mode acd0 pio4 Does anybody have such a problem too? is there any ways to bring this device into udma mode again? dmesg: ... atapci1: <ATI IXP600

Due to an issue I'm having with 7.x, and trying to track it down, I spent tonight getting my server setup to allow my to break into the debugger when it hangs, and hopefully dump core ... But, although I *think* I've got it all, I'm obviously missing something, as it isn't breaking ... First ... I'm running a proliant server, and when I connect via SSH to ILO on that

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

Hello A box of mine running RELENG_7_0 and ZFS over a couple of disks (6 disks, 3 mirrors) seems to have gotten stuck. From Ctrl-T: load: 0.50 cmd: zsh 40188 [zfs:&buf_hash_table.ht_locks[i].ht_lock] 0.02u 0.04s 0% 3404k load: 0.43 cmd: zsh 40188 [zfs:&buf_hash_table.ht_locks[i].ht_lock] 0.02u 0.04s 0% 3404k load: 0.10 cmd: zsh 40188 [zfs:&buf_hash_table.ht_locks[i].ht_lock]

Hi all I've very big problem with my nfsd server. I'm running FreeBSD-stable and sometime (one time/week) i've this kind of message on the console : bge0 watchdog timeout problems fxp1 watchdog timeout problems and all my network card is down. Nothing can make the network card work again (only reboot working). There are only one service I need on this server and

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

I have a zpool that consists for a two-drive mirror. The two times I took the zpool offline, I had to resilver one of the drives (the same drive both times) when I imported it back. All drives in the pool show no read, write, or checksum errors and are new, so I'm looking to a software problem before hardware. Both drives are encrypted geli devices. I tried to reproduce the error with 1GB

Hello! I was trying to build OpenOffice using all of my 4 CPUs. To be able to do other work on the machine comfortably, I ran the build under nice, and assigned real-time priority to the two Xorg processes. The build started at about 23:10 last night, and hung at 23:46. The procstat output for the make's process group is: PID PPID PGID SID TSID THR LOGIN WCHAN EMUL

A few hours ago I downloaded .../i386/ISO-IMAGES/4.9-RC1-i386-disc1.iso and made kern/mfsroot floppies from it. If I enable my ICH5R SATA controller in "native" mode, the 4.9-RC1 GENERIC kernel hangs solidly (only the system reset button can unwedge it) during device configuration. The last line of bootstrap monologue written by the kernel is: plip0" <PLIP network

Hello. I've got a quartet of IBM x3630 M3 with one that is frequently hard locking under heavy NFS load. I am running 9.0-RELEASE with all the patches from freebsd-update. My problem machine has 8 16 core clients, each doing IO intensive tasks connected to it via a Procurve and the onboard igb0 interface. Mostly network reads, typically 10MB read per MB written. When the machine locks

Hi Soeren, We encounter here a deadlock with a quite new ATA 120GB disk. The disk worked good for about 3 weeks, but now we have a strange problem. There seems to be one defective file on the disk. fsck doesn't find it, and if I do a cat file > /dev/null The machine locks completly. Serial console is dead, no remote DDB via ALTBREAK possible anymore, no panic message, just freezed. The

Is there any way (short of not patching it into the kernel) to turn KDB off on a given machine? There are some machines I do not want dropping into kdb when/if it oopses. Thanx, b.

Please give me some pointers... Thanks a lot!