Disk locks and weird things
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 majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Disk locks and weird things
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 error 1) wd0: wdtimeout() DMA status 1 wd0: interrupt timeout (status 50 error 1) wd0: wdtimeout() DMA status 1 wd0: Last time I say: interrupt timeout. Probably a portable PC. (status 50 error 1) wd0: wdtimeout() DMA status 1 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): , 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): , 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): , 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): , 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 majord...@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 majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Disk locks and weird things
Shouldn't a make world take about 10 hours on a P100 ?? -depends on the speed of your disks. You should probably remove all the junk in /usr/obj from previous make worlds, then run "make cleandir" in /usr/src and then try a make world again. The messages about no such user 'tty' indicate your /etc files are out of date. Use the "mergemaster" port to keep your /etc files up to date but you'll need to be carefull when adding the new users to /etc/passwd (hint: run vipw after editing /etc/passwd so the password databases are re-created). One last hint: READ THE CURRENT AND CVS-ALL MAILING LISTS IF YOU'RE GOING TO RUN CURRENT! - if you cant be botherred spending the time to do this dont run CURRENT! P.S. If your existing CURRENT system is too old, you may need to try installing a snapshot first you may have to try a few different snapshots before you find one that works... there were some problems a while back with boot disks I think. On Sun, 14 Feb 1999, 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 majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > > /=\ |Work: matthew.th...@dsto.defence.gov.au | Home: thy...@camtech.net.au| \=/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Disk locks and weird things
On Sun, 14 Feb 1999, 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. But you didn't look in /var/log/messages? For shame! > > 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. What you should have said is "It doesn't appear to be a problem with the actual disk, since rebooting with a different brand disk of the same capabilities doesn't work." or vice versa. > > 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. Look in src/etc/master.passwd. vipw and add the lines for users you don't have. > > I'm also getting messages from de0 and lo0 that say: > > de0 XXX: driver didn't set ifq_maxlen That's mostly harmless. It's a warning to driver maintainers that was just put in recently; the driver hasn't ever set ifq_maxlen, no doubt. > > 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.. Yes it is, but the proper order is to make th world and then make the kernel. > > 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 majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Disk locks and weird things
: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). :... It sounds to me like you may have IDE drives and are hitting an IDE bug. Look at /usr/src/sys/i386/conf/LINT carefully and try using less sophisticated flags if you are using flags for your ide drive. Example: controller wdc0at isa? port "IO_WD1" bio irq 14 flags 0x00ff8004 these flags If you are using 0xa0ffa0ff try backing off to 0x00ff8004. Or even back all the way off to 0x00040004. If you have softupdates enabled, try disabling it - not because of any bug in softupdates, but because it will hit the disk much harder then if it is off. If you can get everything working then try reenabling features slowly until you figure out which one is causing the disk lockups. :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. Yes, you have to add a few more dummy users to passwd. :I'm also getting messages from de0 and lo0 that say: : :de0 XXX: driver didn't set ifq_maxlen Ignore this. :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.. Right. don't worry about it until you get buildworld working. -Matt Matthew Dillon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Disk locks and weird things
Matthew Thyer writes: > On Sun, 14 Feb 1999, Erik Funkenbusch wrote: > > 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). > Shouldn't a make world take about 10 hours on a P100 ?? -depends on > the speed of your disks. More like five or six. But he wasn't saying his make world took ten minutes, he was saying it died after ten minutes. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
XXX: driver didn't set ifq_maxlen (was Re: Disk locks and weird things)
On Sun, 14 Feb 1999, Brian Feldman wrote: > > I'm also getting messages from de0 and lo0 that say: > > > > de0 XXX: driver didn't set ifq_maxlen > > That's mostly harmless. It's a warning to driver maintainers that was just > put in recently; the driver hasn't ever set ifq_maxlen, no doubt. I see this on lo0 every time I boot - is this a problem in 3.1 as well, or just -current? It's probably not good to leave these messages in 3.1 as it ships, if the former. Kris - (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: XXX: driver didn't set ifq_maxlen (was Re: Disk locks and weird things)
On Mon, 15 Feb 1999, Kris Kennaway wrote: > I see this on lo0 every time I boot - is this a problem in 3.1 as well, or > just -current? It's probably not good to leave these messages in 3.1 as it > ships, if the former. FWIW I'm seeing this at bootup now: ep0 XXX: driver didn't set ifq_maxlen lo0 XXX: driver didn't set ifq_maxlen changing root device to wd0s1a link_elf: symbol grow undefined Ahh well guess I get to buildworld now... - alex To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
