Re: ata driver (again)
A dmesg to start with would be fine that way I may be able to reproduce it here pn semilar HW. wdc0: unit 0 (wd0): ST39140A, LBA, DMA, 32-bit, multi-block-16, sleep-hack wd0: 8693MB (17803440 sectors), 1108 cyls, 255 heads, 63 S/T, 512 B/S (sleep-hack I turned on last night) /kernel: wd0: wdtimeout() DMA status 4 Thats not the ata driver thats the wd driver :) Looks like interrupt lossage to me... yes it is, it happens to me with either driver. I keep suspecting it is something other than the disk or OS , like the motherboard or something but I have no idea how to find out. Thanks Luke --- To be sure of hitting the target, shoot first and, whatever you hit, call it the target. XFMail 1.3 FreeBSD-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ata driver (again)
The ata driver seems to be having problems staying in contact with my disks again. Let me know what details are needed to fix the problem, and I'll get in touch with you. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ata driver (again)
On Thu, 30 Sep 1999, Luke wrote: On 01-Oct-99 Kenneth Wayne Culver wrote: The ata driver seems to be having problems staying in contact with my disks again. Let me know what details are needed to fix the problem, and I'll get in touch with you. Hi I don't know if it is the same problem but I have a nagging problem with the ata driver as well. I am fairly sure my disk is ok but can't remove it and do any checking anytime soon. I see errors like this: /kernel: wd0: interrupt timeout (status59rdy,seekdone,drq,errerror40uncorr) /kernel: wd0: wdtimeout() DMA status 4 /kernel: swap_pager: indefinite wait buffer: device:0x20001, blkno: 22304, size: 8192 /kernel: wd0s1b: hard error reading fsbn 22304 of 22304- 22319 (wd0s1 bn 124704; cn 7 tn 194 sn 27) (status 59rdy,seekdone,drq,err erro r 40uncorr) --- what kind of errors do you see? I get this with 3.3R and many different -current's and with the wd and ata driver. it is always in a different location on the disk.. I get similar errors, but not with the wd driver, only the ata driver, and only the timeout error. sometimes the hard error. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata driver (again)
It seems Kenneth Wayne Culver wrote: On Thu, 30 Sep 1999, Luke wrote: On 01-Oct-99 Kenneth Wayne Culver wrote: The ata driver seems to be having problems staying in contact with my disks again. Let me know what details are needed to fix the problem, and I'll get in touch with you. A dmesg to start with would be fine that way I may be able to reproduce it here pn semilar HW. Hi I don't know if it is the same problem but I have a nagging problem with the ata driver as well. I am fairly sure my disk is ok but can't remove it and do any checking anytime soon. I see errors like this: /kernel: wd0: interrupt timeout (status59rdy,seekdone,drq,errerror40uncorr) /kernel: wd0: wdtimeout() DMA status 4 /kernel: swap_pager: indefinite wait buffer: device:0x20001, blkno: 22304, size: 8192 /kernel: wd0s1b: hard error reading fsbn 22304 of 22304- 22319 (wd0s1 bn 124704; cn 7 tn 194 sn 27) (status 59rdy,seekdone,drq,err erro r 40uncorr) Thats not the ata driver thats the wd driver :) Looks like interrupt lossage to me... -Soren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
