Hello Martin,
Monday, June 20, 2005, 9:09:15 PM, you wrote:
M> I just compiled the kernel from May 26th. Works fine. It looks like
M> for me it's broken between May 26th and May 30th.
M> I tried these kernels:
M> 2005-06-16 broken
M> 2005-05-31 broken
M> 2005-05-30 (00:00:00) broken
M> 2005-05-2
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
At 11:09 20/06/2005, Tony Byrne wrote:
[...]
Of course, there
can be hardware reasons for timeouts such as a dying disk or cable,
but I think we've eliminated these in our case. [etc]
Don't ignore the possibility of failing controller hardware. We had
comparable mysterious problems on a client
Hello twesky,
t> atapci0: port
t> 0x1860-0x186f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on
t> pci0
t> ata0: channel #0 on atapci0
t> ata1: channel #1 on atapci0
t> The last known good stable version for me was aprox April 25, my next
t> cvsup was May 17, but I have problems with 5.4 R
