similar to: fxp0: device timeout

On Thu, 5 Jun 2003, Shaun Jurrens wrote: > On Wed, Jun 04, 2003 at 06:32:46PM +0200, Palle Girgensohn wrote: > #> Hi Shaun, > #> > #> Thanks for the input! Glad to hear I'm not the only one > #> > #> In my case, both the SCSI and NIC are integrated on the motherboard, so I > #> cannot really move them around... :) > #> > #> Also, as I

Hi, Whilst doing some QA work on XORP on my desktop, which has fxp0 and msk0, fxp0 got totally hosed. I was running PIM-SM and IGMPv2 router-mode on the box at the time. I wonder if this is related to the problems with fxp multicast transmission I saw back in April. I'm a bit concerned about this as fxp is still a very widespread and useful network chip. I am running

I've spent the past four days or so updating machines here to 4.8/9-stable via cvsup, and have done a complete make buildworld/kernel on each machine (some SMP, some single processor). It seems something is broken with the latest fxp driver, on each machine (different mobos and hardware configs) heavy network traffic with fxp NICs causes timeouts and random kernel panics. First machine to

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:

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've spent the past four days or so updating machines here to 4.8/9-stable via cvsup, and have done a complete make buildworld/kernel on each machine (some SMP, some single processor). It seems something is broken with the latest fxp driver, on each machine (different mobos and hardware configs) heavy network traffic with fxp NICs causes timeouts and random kernel panics. First machine to

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

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

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

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

I'm running OS X 10.3.9/Samba 3.0.10. When I try to connect to my Windows 2000 machine from my user account, I enter the correct workgroup/user/password and then get the message 'The Finder cannot complete the operation because some data in "smb://machinename" could not be read or written. (Error code -36).' (Error code -36 in OS X is "i/O error (bummers)".) I

I'm fond of the "-a" (archive) option of cp, and I'm a heavy user of scp, so I guess it's inevitable that I would eventually add support for "-a" to scp. :-) Actually, it's a "-L" flag for preserving symlinks, and a "-a" flag that is shorthand for "-Lpr". Please let me know if I'm not doing this right.... I made a great

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