similar to: Anyone seen this scsi error before ?

Hello, I am trying to use a 1.5TB Eonstor raid array with FreeBSD 7.0, but I don't understand whether it is the raid or the scsi card or something else that is causing the computer problems when accessing the raid. My problem is that soon after recognizing the attached disk during boot, FreeBSD appears to hang for about 10 seconds and then says ahd0: Recovery Initiated - Card

Hi, I currently encounter spin lock 0xc0c83ba8 (sio) held by 0xc6337460 (tid 100005) too long panic: spin lock held too long cpuid=3 on hp server with two dual-core intel xeon (3.8GHz) and 3GB RAM. System is 7.1-PRELEASE last fetched 29.11.2008, 17:58 UTC. This happens with VSCom Card that was previously in use in a 5.3-STABLE system (also hp server, but older hardware) without problems. The

Hello lists, I,ve compaq ML350 with 2 Xeon 2.4 GHZ and FreeBSD 5.0 RELEASE installed and working very fine about 4 mounts. The machine running GENERIC kernel samba and firebird database server with no problems until at begining of this week, in morning machine freezes with no responce iven in conconsole, no responce from network (pinging) no responce on console (key pressing) the only way to get

Hi, Can someone please help me with this? I have just upgraded from 4.7 to 4.8-STABLE and this is what I am getting when I try a tape backup. Please CC as I am not in the list. It was working well before the upgrade (dump -0ua -f - / | gzip -c -9 | dd of=/dev/nsa0). Thank you, Lefteris Tsintjelis Jul 3 22:55:18 ene /kernel:

Hi all, is there a known issue with health monitoring on supermicro SuperServer 6010H? (Im primarily interested in temeperature monitoring) I have tried both mbmon and lmmon with the following results: stats# mbmon -d SMBus[ServerWorks(ServerSet Chipset)] found, but No HWM available on it!! No Hardware Monitor found!! InitMBInfo: Unknown error: 0 stats# lmmon IOCTL: Operation not supported by

Hi I have a quad processor Compaq Proliant 5500. The output from dmesg seems strange (I have also sent a copy to freebsd-smp to ask about smp issues) and there are also some performance issues which I suspect are smp related. Could anyone who fels so inclined please take a look at the output and let me have any comments. Thanks _______________________________ Copyright (c) 1992-2002 The

I put this to the smp list and to stable but have had no takers from wither. nThere are both smp and other system issues and I am just wondering if anyoe would be willing to take a look at this output from dmesg and let me have some advice Thanks david ----- Original Message ----- From: "vizion communication" <vizion@ixpres.com> To: <freebsd-smp@freebsd.org> Sent:

Hi, All. I'm trying to use HP Suresore 24e on FreeBSD 4.8-STABLE (Mon May 12 09:32:15 YEKST 2003). The system is installed on Asus P2b-DS motherboard with Adaptec aic7890 onboard scsi-controller. I have 2 SCSI-3 HDDs attached to it: da0: <IBM DDYS-T18350N S96H> Fixed Direct Access SCSI-3 device da1: <IBM DDYS-T09170N S80D> Fixed Direct Access SCSI-3 device and I'trying to

Can anyone help me here? ----- Forwarded message from Larry Rosenman <ler at lerctr.org> ----- Date: Sat, 9 Nov 2013 08:46:26 -0600 From: Larry Rosenman <ler at lerctr.org> To: freebsd-stable at freebsd.org Subject: 10-BETA3: Bad negotiation on AHD controller User-Agent: Mutt/1.5.22 (2013-10-16) Ever since I put 10 on this box (source upgrade from 8), I've been getting slow

I have same problem on same class machine, here is dmesg from failing boot (via serial console): -------------------- Copyright (c) 1992-2003 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 4.8-RELEASE-p7 #0: Sat Sep 20 17:07:38 EEST 2003

One of our FreeBSD boxes has a SCSI controller and disk, which showed problems earlier this week. There was a lot of of chatter from the SCSI driver in /var/log/messages and to the console. However, the console is unattended and we only discovered the problem subsequently because /var/log/console.log didn't show any of the chatter. console.log is otherwise working, and very helpful (e.g. it

I am getting these messages every 30 seconds or so. I searched around and found a few other post about this problem with other devices, but no answers to the problem. I didn't notice any of these message until I upgrade to 4.8-RELEASE the other day. This is a dual processor machine. It happens on all my machines that have em devices, which all happen to be dual processor machines. I

I've just had a 4.9p1 system partially deadlock for about 30 minutes and then spontaneously(?) recover. The "ps" results point at vinum. I've never seen this before and don't recall anything like this being mentioned here before. At the time, I had two find's running in a large NFS mounted filesystem and was doing a "cvs -d /usr/ncvs -R checkout -P ports" from

I've finally been able to capture the panic, as now it occurs even with DDB configured. Of the six machines I have running 6.1-RC (CVSupped today), this is the only one that does this. /boot/kernel/kernel text=0x30c488 data=0x3b6a0+0x3170c syms=[0x4+0x46430+0x4+0x58da4] no such file or directory - Hit [Enter] to boot immediately, or any other key for command prompt. Booting

Hello, My server is experiencing occasional kernel panics when under moderate load. I'm attaching a crash dump and the dmesg output. I'm not sure how to read the kernel backtrace but it looks like the Intel NIC (em0) caused the problem. Occasionally, I used to get a "em0: watchdog timeout -- resetting" error message, but I never had a kernel panic. The problem started last

Hi, I am running a Xeon with hyperthreading support. Until last week's HTT modifications, according to ps(1) and top(1) both logicals CPUs were in use. (Processes in CPU0 and CPU1 state; "C" column showing "0" or "1".) This has changed with a recent -STABLE kernel which includes last week's changes to HTT (removing "options HTT"). I am only seeing

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

FreeBSD 4.1.1-RELEASE #1: Tue Oct 10 18:09:51 CDT 2000 root@test-drive.tamu.edu:/usr/src/sys/compile/TEST-DRIVE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM

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:

Hi, We have a pretty serious problem with our news server crashing during the expire cronjob. This happened with 4.7-RELEASE, so we upgraded to 4.8-RELEASE recently, hoping that the problem might be fixed, but it isn't. The machine is a Compaq DL360-G2. I've searched the PR database as well as the mailing list archives for the panic string, but didn't find anything. What makes the