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
I wrote:
>So, kernel got the DMA error at boot and couldn't mount the root fs.
Ah, btw.. it's a SATA disk, on an ICH6 SATA150 controller.
mkb.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsub
Jayton Garnett <[EMAIL PROTECTED]> 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
twesky wrote:
> 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?
I just compiled the kernel from May 26th. Works fine. It looks like
for me it's broken between May 26th and M
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
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
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
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
At 13:19 20/06/2005, Tony Byrne wrote:
Hello Bob,
BB> It didn't to me either. Note the use of 'mysterious' :-)
BB> I'd eliminated drives and cables, and then did it all over again when the
BB> failure went hard, leaving the controller (or something else on the mobo).
BB> With a new mobo all the
Hello Bob,
BB> It didn't to me either. Note the use of 'mysterious' :-)
BB> I'd eliminated drives and cables, and then did it all over again when the
BB> failure went hard, leaving the controller (or something else on the mobo).
BB> With a new mobo all the annoying timeouts which I'd put down to d
At 12:12 20/06/2005, 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
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, cau
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-scratc
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
Here is my controller:
atapci0: port
0x1860-0x186f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on
pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
The last known good stable version for me was aprox April 25, my next
cvsup was May 17, but I have problems with 5.4 Release so I
twesky wrote:
> I am having ATA_DMA errors on 5.4R and 5 STABLE up to June 16 (haven't
> done a cvsup again). It doesn't happen on 5.3R or lower.
I have got same problem. I tried yesterday's kernel and I got lots of
ATA DMA errors. A question: do you have a VIA IDE controller like mine?
atapci0:
17 matches
Mail list logo
