similar to: SCSI bus reset with Adaptec 29320ALP and Eonstor RAID

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 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

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

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

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

On reboot, one out of 10 times, reboot (from hardware initialization) stops. Referring to this portion of the dmesg -v output, of a successful boot, where i have marked ">>>HERE<<<" is where the boot freezes on an unsuccessful boot. This is a constnat problem, on 6.2 as well as 6.3 unchanged. ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting

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 have a Supermicro SuperServer 6013P-8 system which features a X5DPR-8G2 motherboard with embedded Adaptec AIC-7902 dual-Ultra320 SCSI controller. Said system boots and runs fine with 4.8-RELEASE (with a slight cosmetic problem during boot that can be cured by building a kernel without eisa support). With STABLE (as of 19 June) the system locks up hard (no response to the keboard) during the

I have a Solaris 11 build server with build 58 and a zfs scratch filesystem. When trying to upgrade to build 63 using liveupgrade I get the following upon reboot. The machine never comes up. Just keeps giving the error/warning below. Is there something I am doing wrong? WARNING: /ssm at 0,0/pci at 1c,600000/scsi at 1 (mpt0): Received invalid reply frame address 0x480 WARNING: /ssm at

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

I have a new system which includes a Plextor PX-740a DVD+-R/RW CD-R/RW drive attached to an Asus A8V-MX motherboard. When I try to use burncd to burn a cd, it writes all of the data, says "fixating CD, please wait.." and then reports burncd: ioctl(CDRIOCFIXATE): Input/output error Oddly enough, the CD seems to be usable. I can successfully burn the same file if I use cdrecord. The

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

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

I am not too familiar with Cairo and RGtk2 and have the following problem: I have a container with two GTK drawing areas converted into Cairo devices. I know that I can set the current drawing context e.g. using dev.set(). But this is tedious. How can I set the context using the objects da1 or da2? w <- gtkWindow() w$setSizeRequest(400, 400) vbox <- gtkVBox() da1 <- gtkDrawingArea()