Date: Mon, 17 Jan 2000 13:19:00 -0500 From: Mike Tancsa <mike@sentex.net> To: Conrad Sabatier <conrads@home.com>, stable@FreeBSD.ORG Subject: Re: Problems with 3.4-STABLE custom kernel Message-ID: <3.0.5.32.20000117131900.025a2710@staff.sentex.ca> In-Reply-To: <XFMail.000117121620.conrads@home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:16 PM 1/17/00 -0600, Conrad Sabatier wrote: >I've been trying to get a new kernel to work on a friend's >machine, but every time I install a new kernel and reboot, >we get this: > >changing root device to wd0s2a >wd0: interrupt timeout (status 50<rdy,seekdone> error 0) >wd0: wdtimeout() DMA status 4 >wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>) >wd0: wdtimeout() DMA status 4 >wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>) >wd0: wdtimeout() DMA status 4 >wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>) >wd0: wdtimeout() DMA status 4 >wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>) >wd0: wdtimeout() DMA status 4 >wd0: Last time I say: interrupt timeout. Probably a portable PC. >(status 50<rdy,seekdone> error 1<no_dam>) >wd0: wdtimeout() DMA status 4 > >His system worked just fine with a previous custom kernel with >exactly the same config as this one. I'm at a loss as to what >to do. On first glance, it would seem you have come across a bad sector on your hard drive. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.20000117131900.025a2710>