similar to: Health check

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

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

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:

[ Asked on -questions on Friday; re-asking now on -stable without cross-post] I recently upgraded a 4.11-REL machine to 6.0-REL and have run into some snags. While the installation from CD went fine, after configuring and enabling my ed0 NIC, bad things start to happen. FWIW, this machine is an ancient (hardware circa 1991, BIOS circa 1994) dual-Pentium 133 MHz machine, with EISA/PCI and

Hello, I've an SCSI version of the IOMEGA REV drive (35 GB, like ZIP drive). How can I access this drive. FreeBSD detects the drive as CDROM: cd0 at ahc0 bus 0 target 4 lun 0 cd0: <Iomega RRD 89.B> Removable CD-ROM SCSI-4 device cd0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) cd0: cd present [17090880 x 2048 byte records] I'm using FreeBSD 6.1-RC. Kind regards, Thomas.

Use the proper modern API to transfer cache ownership for incoherent DMA. Note that this moves the DMA helpers to the main lib82596.c file, so that they can use virt_to_dma. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/net/ethernet/i825xx/lasi_82596.c | 11 +-- drivers/net/ethernet/i825xx/lib82596.c | 114 ++++++++++++++--------- drivers/net/ethernet/i825xx/sni_82596.c

Use the new non-coherent DMA API including proper ownership transfers. This includes moving the DMA helpers to lib82596 based of an ifdef to avoid include order problems. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/net/ethernet/i825xx/lasi_82596.c | 25 ++--- drivers/net/ethernet/i825xx/lib82596.c | 114 ++++++++++++++--------- drivers/net/ethernet/i825xx/sni_82596.c |

Use the new non-coherent DMA API including proper ownership transfers. This includes adding additional calls to dma_sync_desc_dev as the old syncing was rather ad-hoc. Thanks to Thomas Bogendoerfer for debugging the ownership transfer issues. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/net/ethernet/i825xx/lasi_82596.c | 25 ++--- drivers/net/ethernet/i825xx/lib82596.c

Hi, Currently we are running CentOS 4.x on a 2-way Opteron machine. This machine, through a SCSI host adapter (Adaptec), is connected to a 2TB storage unit (an external RAID-5 disk array) Until our recent unintentional power trip, everything was fine and smooth. We have been experiencing complication accessing the storage ( it could be either intermittent filesystem error, partition could not be

This allows us to get rid of the LIB82596_DMA_ATTR defined and prepare for untangling the coherent vs non-coherent DMA allocation API. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/net/ethernet/i825xx/lasi_82596.c | 24 ++++++++++------ drivers/net/ethernet/i825xx/lib82596.c | 36 ++++++++---------------- drivers/net/ethernet/i825xx/sni_82596.c | 19 +++++++++---- 3 files

This allows us to get rid of the LIB82596_DMA_ATTR defined and prepare for untangling the coherent vs non-coherent DMA allocation API. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/net/ethernet/i825xx/lasi_82596.c | 24 ++++++++++------ drivers/net/ethernet/i825xx/lib82596.c | 36 ++++++++---------------- drivers/net/ethernet/i825xx/sni_82596.c | 19 +++++++++---- 3 files

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

Graham Bentley wrote: > Recently swapped out my Sony for a HP DAT and > got this first time in dmesg > > (sa0:ahc0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 0 0 > (sa0:ahc0:0:6:0): CAM Status: SCSI Status Error > (sa0:ahc0:0:6:0): SCSI Status: Check Condition > (sa0:ahc0:0:6:0): UNIT ATTENTION asc:28,0 > (sa0:ahc0:0:6:0): Not ready to ready change, medium may

I am currently testing an Overland Tape storage unit with a LTO-3 drive on CentOS 4.4. After a random amount of time but usually when we have backed up about 0.5-1TB we get scsi errors which cause the backup to fail. I have rebuilt the box with Solaris 10 x86 and Windoze to prove the hardware and have successfully backed up over 3TB on each OS without error. Can anyone offer advice on how to find

Hi ... Can someone tell me whether or not this is indicative of a hardware, or software, problem? It happened a few times today, on two different drives, and it seem to "self-recover", since the server is still purring along without any noticeable problems: neptune# grep "timed out" /var/log/messages Jul 25 03:52:51 neptune /kernel: (da2:ahd1:0:2:0): SCB 0x40 - timed out

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

I?m running centos 4.3 (2.6.9-22.ELsmp) on a box ,and running windows XP on vmware 5.5.1. I have 3 scsi disk on this server,sda for linux system,sdb for vmware disk,and sdc for other. Resently I found that something wrong with the second disk,the guest os windowsxp copying files from a samba server(another box) to it?s disk,and for some time,maybe 5hours,3or1hours, the kernel said that sdb is

We're having a problem with Linux and/or the SCSI controller failing to access an external RAID device. Components are: SuperMicro 6025B-TR+V CentOS 5.0 with yum update as of a week or two ago (kernel 2.6.18-8.1.8.el5) Promise Vtrak M310p Adaptec 29320 LPE -- aic79xx module Sometimes this fails on the initial device probing (before the kernel even begins to boot); sometimes the device is

I have a Dell ASC-39230(B) U320 SCSI controller. If I use the linux-2.6-xen kernel I am getting an "Invalid Sequencer interrupt" and the system hangs after this. But if I use the linux-2.6-xen0 kernel it works well. Does anyone know why this is happening and how I can make it go away? Thanks, Aravindh Puthiyaparambil Xen Development Team Unisys, Tredyffrin PA ACPI: PCI Interrupt