I had a similar problem and i changed system cases where i was getting a ICRC error and FreeBSD refused to load or even mount the root fs, it was also giving errors with something to do with the ATA something or other, it turned out to be the cable i used after rebuilding the system in the new case, i used a normal EIDE cable instead of a ATA cable :-/ hope that helps(probably not) Jay> >Tony Byrne wrote: > > > >>Hello Bob, >> >> >> >> >> >> >>>>can be hardware reasons for timeouts such as a dying disk or cable, >>>>but I think we've eliminated these in our case. [etc] >>>> >>>> >>>> >>>> >>BB> Don't ignore the possibility of failing controller hardware. We had >>BB> comparable mysterious problems on a client system, causing a lot of >>BB> head-scratching. Eventually the failure went hard and we had to replace the >>BB> motherboard. >> >>I hear ya! However, moving back to an older kernel changes the >>severity of the problem from a timeout every 2 to three minutes during >>heavy activity to about 4 or 5 in a 24 hour period. That doesn't >>sound like hardware to me. >> >>Regards, >> >>Tony. >> >> >> >> >> >i have these same errors on my VIA 823x series chipset. however, the >problem is only with the secondary device (acd0 in this case), and might >be stemming from some other problem. > > >
Hello Jayton, Monday, June 20, 2005, 3:46:20 PM, you wrote: JG> I had a similar problem and i changed system cases where i was getting a JG> ICRC error and FreeBSD refused to load or even mount the root fs, it was JG> also giving errors with something to do with the ATA something or other, JG> it turned out to be the cable i used after rebuilding the system in the JG> new case, i used a normal EIDE cable instead of a ATA cable :-/ In our case it's a SATA drive. Regards, Tony. -- Tony Byrne
Jayton Garnett wrote:> I had a similar problem and i changed system cases where i was getting > a ICRC error and FreeBSD refused to load or even mount the root fs, it > was also giving errors with something to do with the ATA something or > other, it turned out to be the cable i used after rebuilding the > system in the new case, i used a normal EIDE cable instead of a ATA > cable :-/ > > hope that helps(probably not)actually, that makes a lot of sense. my computer running FreeBSD is actually just an Eden 5000 V-series. the cable is trimmed to fit the 2.5" hard drive in the tiny case and i'm sure this is having something to do with the timeouts... however the harddrive is recognized as UDMA33 but the cdrom still times out. thanks for the input. note: this setup works fine in windows... maybe someone should take a look at this issue? i'm running the old 5.3-RELEASE (too lazy to update) with a VIA VT8231 SouthBridge (82xxxx ata controller).> > Jay > >> >> Tony Byrne wrote: >> >> >> >>> Hello Bob, >>> >>> >>> >>> >>> >>> >>>>> can be hardware reasons for timeouts such as a dying disk or cable, >>>>> but I think we've eliminated these in our case. [etc] >>>>> >>>>> >>>> >>> BB> Don't ignore the possibility of failing controller hardware. We had >>> BB> comparable mysterious problems on a client system, causing a lot of >>> BB> head-scratching. Eventually the failure went hard and we had to >>> replace the >>> BB> motherboard. >>> >>> I hear ya! However, moving back to an older kernel changes the >>> severity of the problem from a timeout every 2 to three minutes during >>> heavy activity to about 4 or 5 in a 24 hour period. That doesn't >>> sound like hardware to me. >>> >>> Regards, >>> >>> Tony. >>> >>> >>> >>> >> >> i have these same errors on my VIA 823x series chipset. however, the >> problem is only with the secondary device (acd0 in this case), and >> might be stemming from some other problem. >> >> >> > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
My laptop works fine with Fedora Core 4. I'm not sure it's a hardware issue, and I don't have an identical laptop to test. Do we know the last working stable version? ----------------------------------------- actually, that makes a lot of sense. my computer running FreeBSD is actually just an Eden 5000 V-series. the cable is trimmed to fit the 2.5" hard drive in the tiny case and i'm sure this is having something to do with the timeouts... however the harddrive is recognized as UDMA33 but the cdrom still times out. thanks for the input. note: this setup works fine in windows... maybe someone should take a look at this issue? i'm running the old 5.3-RELEASE (too lazy to update) with a VIA VT8231 SouthBridge (82xxxx ata controller).
Jayton Garnett <jay@codegurus.org> writes:>I had a similar problem and i changed system cases where i was getting a >ICRC error and FreeBSD refused to load or even mount the root fs, it was >also giving errors with something to do with the ATA something or other, >it turned out to be the cable i used after rebuilding the system in the >new case, i used a normal EIDE cable instead of a ATA cable :-/I've just encountered the same problem on 5.4-STABLE/i386. I rebuilt my kernel with SMP and enabled hyperthreading in loader.conf, because the security weakness doesn't really apply to my desktop machine. So, kernel got the DMA error at boot and couldn't mount the root fs. When I switched off HT in the BIOS, the system came up ok. I've cvsupped 5.4-STABLE just a few hours ago. mkb.