Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

2005-08-17 Thread Pertti Kosunen
Mark Kane wrote: I do have a tall Antec case, and have both 200's and the 160 in 5 1/4 inch trays so the cables for those are long (36 inches IIRC). Would it be OK to have that setup, or would it be better to isolate them all on their own cables/channels and get a Promise card or something

BTX failure [Was: Re: pxeboot problems with BETA2]

2005-08-17 Thread Emanuel Strobl
Am Dienstag, 16. August 2005 19:52 CEST schrieb Brooks Davis: On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote: Hello, I just wanted to ask if somebody had success with providing pxe boot service under 6-BETA2. I have two clients, one NET4501 wich just reboots after

Re: Xorg monopolizes CPU after switching away with KVM

2005-08-17 Thread darren david
Stephen Montgomery-Smith wrote: Darren David wrote: Hi all- So I've just encountered a new issue ( for me ) with Xorg, and i'm having a heck of a time tracking down the source and/or the actual nature of the issue. When i switch to another computer using my KVM, Xorg immediately begins to

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

2005-08-17 Thread Mark Kane
Mark Kirkwood wrote: Mark Kane wrote: I do have a tall Antec case, and have both 200's and the 160 in 5 1/4 inch trays so the cables for those are long (36 inches IIRC). Hmm - 36 inch cable, makes me wonder if that is what is causing the problem in UDMA133 mode. IIRC the ATA spec says 18

Re: BTX failure [Was: Re: pxeboot problems with BETA2]

2005-08-17 Thread John Baldwin
On Wednesday 17 August 2005 10:43 am, Emanuel Strobl wrote: Am Dienstag, 16. August 2005 19:52 CEST schrieb Brooks Davis: On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote: Hello, I just wanted to ask if somebody had success with providing pxe boot service under

August Monthly Snapshots Available

2005-08-17 Thread Ken Smith
Sorry for the delay getting this message out. The August Monthly Snapshots are available. Due to the activity being done for the 6.0-RELEASE we did not bother building HEAD snapshots this month, if that is what you are interested in please give the 6.0-BETA builds a try. The MD5s for the

5.4-STABLE freezing without hints in verbose mode

2005-08-17 Thread Jose Hidalgo Herrera
Using: 5.4-STABLE FreeBSD 5.4-STABLE #1: Tue Aug 16 16:45:31 CST 2005 with this kernel config: include SMP ident IDS options NETGRAPH having 3 network interfaces: One with ip address(fxp0), the other two (xl0 and xl1) are just to sniff traffic on different networks, at the begining unplugged,

Re: BTX failure [Was: Re: pxeboot problems with BETA2]

2005-08-17 Thread Emanuel Strobl
Am Mittwoch, 17. August 2005 21:29 CEST schrieb John Baldwin: On Wednesday 17 August 2005 10:43 am, Emanuel Strobl wrote: [*schnip*] Relocating the loader and the BTX Starting the BTX loader int=0006 err= efl=00010202 eip=00023c21 eax= ebx=000384e0 ecx=000384e0

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

2005-08-17 Thread Mark Kane
Mark Kane wrote: I'm glad that it looks like running it at 100 will solve this. Thanks for the replies. I was probably going to go through all the hassle of getting an Asus board to replace this because I was almost certain it was hardware, but I don't think it's worth it as long as this works

Re: DELL SC430 ahd0: Adaptec 39320A Ultra320 SCSI adapter

2005-08-17 Thread Justin T. Gibbs
My dell Sc430 Server with Freebsd 5.4 gives soon after a reboot and minimal harddisk actions (erase a file or directory) strange messages concerning Adaptec SCSI adapter: From what I can tell from the full card dump state, the 39320 attempted to send 77 transactions to your drive during a

acc Monitor error message

2005-08-17 Thread Huang wen hui
hi, I have DELL PE4600 server with acc driver , running 5.4 Release. when system boot, got this message: Mounting root from ufs:/dev/aacd0s1a aac0: **Monitor** ID(0:02:0); Error Event [command:0x2a] aac0: **Monitor** ID(0:02:0); Hardware Error [k:0x4,c:0x19,q:0x0] aac0: **Monitor** ID(0:02:0);

Re: Too short ethernet frame...

2005-08-17 Thread Iva Hesy
On 8/16/05, Brooks Davis [EMAIL PROTECTED] wrote: Sounds like someone introduced a bug in the nic driver or the ethernet code, but I'm not seeing anything obvious between those dates. If you could narrow the date range further that would help. -- Brooks OK, now, I get the result: