ad0: WRITE command timeout...

2004-11-04 Thread Are Bryne
Hello,
After upgrading a computer from FreeBSD 4.8-something to 4.10-RELEASE-p3, 
I'm getting lots of the following:

ad0: WRITE command timeout tag=0 serv=0 - resetting
ata0: resetting devices .. done
I cannot recall seeing these before.
Would anyone know what this implies? It's still doing an installworld in 
single user mode, so I cannot post the disk make and model yet...

And please CC me in your reply - I am not on the -questions list.
Best regards,
Are Bryne
--
Communiqué DAOffice:   +47 22 44 33 99
Postboks 9050 Grønland   Mobile:+47 900 22 009
NO-0133 Oslo URL: http://www.communique.no___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


ad0: WRITE command timeout...

2004-11-04 Thread Are Bryne
Hello,
After upgrading a computer from FreeBSD 4.8-something to 4.10-RELEASE-p3, 
I'm getting lots of the following:

ad0: WRITE command timeout tag=0 serv=0 - resetting
ata0: resetting devices .. done
I cannot recall seeing these before.
Would anyone know what this implies? It's still doing an installworld in 
single user mode, so I cannot post the disk make and model yet...

And please CC me in your reply - I am not on the -questions list.
Best regards,
Are Bryne
--
Communiqué DAOffice:   +47 22 44 33 99
Postboks 9050 Grønland   Mobile:+47 900 22 009
NO-0133 Oslo URL: http://www.communique.no___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ad0: WRITE command timeout...

2004-11-04 Thread Nelis Lamprecht
On Thu, 4 Nov 2004 14:10:42 +0100 (CET), Are Bryne
[EMAIL PROTECTED] wrote:
 
 
 Hello,
 
 After upgrading a computer from FreeBSD 4.8-something to 4.10-RELEASE-p3,
 I'm getting lots of the following:
 
 ad0: WRITE command timeout tag=0 serv=0 - resetting
 ata0: resetting devices .. done
 

Hi,

Seen this once before and in my case it was a faulty hard drive cable.
Check to see whether your cable is not loose or incorrectly inserted
and perhaps try a new one. It may also be caused by an incorrect DMA
setting if memory serves me correct.

Nelis
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ad0: WRITE command timeout...

2004-11-04 Thread Jan Christian Meyer
On Thu, 4 Nov 2004, Nelis Lamprecht wrote:

 On Thu, 4 Nov 2004 14:10:42 +0100 (CET), Are Bryne wrote:

 After upgrading a computer from FreeBSD 4.8-something to 
 4.10-RELEASE-p3, I'm getting lots of the following:
 
 ad0: WRITE command timeout tag=0 serv=0 - resetting
 ata0: resetting devices .. done
 
 Seen this once before and in my case it was a faulty hard drive 
 cable. [...] It may also be caused by an incorrect DMA setting if 
 memory serves me correct.

I've seen these come as symptoms of a worn-out drive.
Evidently that's not the only possible cause, but if I were you, 
I'd back up my stuff as soon as possible.

Cheers,
 -Jan Christian
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ad0: WRITE command timeout...

2004-11-04 Thread Are Bryne
On Thu, 4 Nov 2004, Nelis Lamprecht wrote:
On Thu, 4 Nov 2004 14:10:42 +0100 (CET), Are Bryne 
[EMAIL PROTECTED] wrote:
[...]
After upgrading a computer from FreeBSD 4.8-something to 4.10-RELEASE-p3,
I'm getting lots of the following:
ad0: WRITE command timeout tag=0 serv=0 - resetting
ata0: resetting devices .. done
The disk in question is a
FUJITSU MPC3043AT/6018 using ATA/ATAPI rev 3 according to atacontrol.
It is master on its controller and uses UDMA33 transfers, and has an idle 
PIO4 cd-rom player as a slave.

The controller is identified in dmesg as:
atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on 
pci0

[...]
Hi,
Seen this once before and in my case it was a faulty hard drive cable.
Check to see whether your cable is not loose or incorrectly inserted
and perhaps try a new one.
Thank you - I will check that.
It may also be caused by an incorrect DMA setting if memory serves me 
correct.
I might try turning DMA off to see if that helps...
Nelis
Again, please CC me to make sure I see the whole thread.
Regards,
Are Bryne
--
Communiqué DAOffice:   +47 22 44 33 99
Postboks 9050 Grønland   Mobile:+47 900 22 009
NO-0133 Oslo URL: http://www.communique.no___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]