Date: Sun, 14 Feb 1999 12:49:53 +0100 From: Alex Le Heux <alexlh@funk.org> To: Erik Funkenbusch <erikf@visi.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Disk locks and weird things Message-ID: <36C6B861.49337607@funk.org> References: <000701be5801$1d70dce0$0200a8c0@zeus>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm getting something similar. I thought it was my mainboard, as the one I currently have has some other problems (doesn't take the Nvidia TNT card) During heavy disk i/o the system freezes up for about 10 seconds or so, and then things continue. I'm getting these messages: wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>) wd0: wdtimeout() DMA status 1<active> wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>) wd0: wdtimeout() DMA status 1<active> wd0: Last time I say: interrupt timeout. Probably a portable PC. (status 50<rdy,seekdone> error 1<no_dam>) wd0: wdtimeout() DMA status 1<active> This is what gets probed: Feb 11 08:18:34 p /kernel: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa Feb 11 08:18:34 p /kernel: wdc0: unit 0 (wd0): <QUANTUM BIGFOOT_CY4320A>, DMA, 32-bit, multi-block-16 Feb 11 08:18:34 p /kernel: wd0: 4134MB (8467200 sectors), 8960 cyls, 15 heads, 63 S/T, 512 B/S Feb 11 08:18:34 p /kernel: wdc0: unit 1 (wd1): <QUANTUM FIREBALL ST4.3A>, DMA, 32-bit, multi-block-16 Feb 11 08:18:34 p /kernel: wd1: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S Feb 11 08:18:34 p /kernel: wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa Feb 11 08:18:34 p /kernel: wdc1: unit 0 (atapi): <IOMEGA ZIP 100 ATAPI/23.D>, removable, intr, iordis Feb 11 08:18:34 p /kernel: wfd0: medium type unknown (no disk) Feb 11 08:18:34 p /kernel: wfd0: buggy Zip drive, 64-block transfer limit set Feb 11 08:18:34 p /kernel: wdc1: unit 1 (atapi): <LTN301/ML25>, removable, intr, dma, iordis Alex Erik Funkenbusch wrote: > > Recently I've been trying to upgrade an early januarrry -current to > current -current. I've rebuilt the kernel several times over the last few > days (with new cvsup's) so i've eliminated any freak check-in mismatches. > > During a make world (usually about 10-20 minutes in on my P100) everything > just comes to a grinding halt. No disk activity, but the screen saver will > kick in (despite the shell being in the middle of said make world). > > If I switch to any alternate consoles and try to do anything, even an ls, it > accesses the disk for a brief second, then hangs as well. Other tasks that > don't need to access the disk keep running (such as natd and obviously the > screen saver). > > After waiting about a half hour, I hit the reset and get lots of UNREF > FILE's and SUMMARY INFORMATION BAD and BLK(S) MISSING IN BIT MAPS. They all > say slavaged or cleared. > > It doesn't appear to be a problem with the actual disk, since rebooting > works fine until I try and build again. Even building the kernel works > fine. but doing a make world does not (I don't know if anything else causes > this). It never fails in the same place twice either, but it's always the > same effect. > > Additionally, i've been getting No such user 'tty', service ignored messages > from ntalk and comsat. I'm sure these services were updated to make use of > some tty user or something, but i'd like to know what exactly I should do > here. > > I'm also getting messages from de0 and lo0 that say: > > de0 XXX: driver didn't set ifq_maxlen > > Finally, if I try and run top i get: > > top: cannot read swaplist: kvm_read: Bad address > kvm_open: proc size mismatch (11392 total, 680 chunks) > top: Out of memory. > > I assume this is from a newer kernel with older support files (such as top) > but since I can't get world to build, I'm kinda stuck.. > > One more thing. I figured I might try a complete reinstallation so I tried > to download the 4.0-snap of 2-11 and was able to successfully create a > kern.flp but when I tried to create mfsroot.flp it seems to sit in a loop > forever just moving the disk head back and forth. I tried it with several > floppies (including the one I was able to successfully create kern.flp on) > with the same results. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- "Ik zit op m'n kromme, akelige broertje te wachten. Die heeft zich opgesloten in de server ruimte, en die weigert eruit te komen." - Bart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36C6B861.49337607>