Re: HDD Problem
On Wed, Dec 27, 2000 at 03:21:33PM -0800, Kent Stewart wrote: "David W. Chapman Jr." wrote: I have a KT7 with an athlon 1.1, no problems with ATA66, don't have a 100 drive though. Works fine, does make worlds in a little over an hour with 384mb of pc133, but I do have to downclock the pc133 to 100 because these via chips have some problem with agp and pc133 at the moment. I'm also running the slow end on the bios memory setting. The wz beta bios is supposed to deal with some memory timing questions. I have downloaded wz but haven't flashed the bios yet. I am running uz, which became w? (their www server is overloaded and can't see what they called the uz when it was released). Abit is also up to KT7a and 686B. I have both Maxtor's (30 GB and 40 GB - ATA100's) set to do only UDMA 33 using Maxtor's udmaupdt.exe program. That didn't help FreeBSD. Windows 2000 didn't have any problems at the UDMA66 setting and just slowed down a little bit at the UDMA33 setting. I have three other systems based on the bx chipset that don't have problems doing UDMA33. I also have an AbitKT7 with a Duron 650 and a Western Digital UDMA66 7200 rpm drive. I have never seen any ata problem on this machine. Yes it runs pc133 memory with the least conservative settings: "turbo" memory, 2 cycles wait etc. This machine also runs Win98 and Linux and has no problem with any of these systems. Make buildworld takes an hour. We have received similar machines at work but with 1.1 Ghz Athlons. Does not make big difference on speed except on very compute intensive things. Apparently most of the time is spent accessing memory or the disks. The only problem this machine had, and only under FreeBSD, is that floppy formatting did not work. Fortunately, since upgrade to 4.2, this is solved. Also the loader dies doing lsdev, but this is apparently due to the presence of a dvdrom. -- Michel Talon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
On Wed, 27 Dec 2000, Soren Schmidt wrote: It seems David W. Chapman Jr. wrote: You guys are not overclocking are you ?? I've recently seen the same problem on 4.2-stable, probably a early version of it, I go to make my kernel and it locks up for a few mins, then I get some ata error and then it says resetting devices and it all runs ok, it resets the ata devices during boot also. - Original Message - From: "Ben Jackson" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, December 27, 2000 2:28 PM Subject: Re: HDD Problem I've heard tell that there are problems with the VIA chipset and UDMA on FreeBSD. Is this true, and if so, what is the problem with? FreeBSD 4.2-STABLE #0: Fri Dec 8 01:52:44 EST 2000 atapci0: VIA 82C686 ATA66 controller port 0xe000-0xe00f at device 7.1 on pci0 ad0: 19546MB FUJITSU MPF3204AT [39714/16/63] at ata0-master UDMA66 Sounds similar to the problem I've had with the HPT controller on my Abit BP6. If you look at the -stable archives from the last few days you'll see some suggestions. I should really move this drive to one of the ATA33 controllers since the drive itself only (??) does about 30M/s sustained anyway. atapci1: HighPoint HPT366 ATA66 controller port 0xd800-0xd8ff,0xd400-0xd403,0xd000-0xd007 irq 18 at device 19.0 on pci0 ata2: at 0xd000 on atapci1 ad4: 29311MB Maxtor 53073U6 [59554/16/63] at ata2-master UDMA66 The drive has enough space and I have 512MB RAM. If I hit the system hard, lets say, rm -rf /usr/ports, the system locks up. I have to hit mine harder. The more I upgrade FreeBSD, the more times it successfully resets the devices after a read timeout, but eventually it hangs while resetting. With 4.2 (or maybe it's softupdates) it manages to save some of the errors in /var/log/messages. No page faults. Haven't had a persistant kernel "page not present" problem since FreeBSD 1.1.5. Also, my UDMA66 problem is happening on a machine with ECC mem. Another datapoint: my desktop machine (until yesterday running 3.4) has an IBM disk in it which likes to spin down on its own, causing timeouts on the first access afterwards. It's irritating (though not enough that I've investigated jumpering it for always-on) but it has never hung the system. --Ben To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
You guys are not overclocking are you ?? No! Just because I have a BP6 doesn't mean I'm overclocking it. The HPT controller has always done this. Would more messages help, eg bootverbose? I tried DDB on 4.0 and ctrl-esc didn't get out of this state. --Ben To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
I've got two mobos with VIA MVP3 chipsets on-board. As these systems (until recently) had only SCSI peripherals, I didn't notice any problem. However, when I added an IDE CDRW drive, I got these very strange system lock-ups/hangs. Specifically, this was an FIC VA-503+ mobo, with a 450MHz K6-2 CPU. I saw on a FreeBSD mailing list a suggestion to go into the BIOS setup, and disable "PCI Dynamic Bursting". At least that's what it's called in my Award BIOS. This seemed to have "fixed" the problem for me (or at least hidden it sufficiently well :-); perhaps it might be of some help in other situations? louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
On Wed, 27 Dec 2000, Louis A. Mamakos wrote: I've got two mobos with VIA MVP3 chipsets on-board. As these systems (until recently) had only SCSI peripherals, I didn't notice any problem. However, when I added an IDE CDRW drive, I got these very strange system lock-ups/hangs. Specifically, this was an FIC VA-503+ mobo, with a 450MHz K6-2 CPU. From earlier this year: - Begin included text From [EMAIL PROTECTED] Thu Aug 24 10:35:34 2000 Date: Wed, 23 Aug 2000 19:31:26 -0700 (PDT) From: Jeff Wyman [EMAIL PROTECTED] To: Janko van Roosmalen [EMAIL PROTECTED] Cc: Robert Augustine [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Random Reboots On Wed, 23 Aug 2000, Janko van Roosmalen wrote: Check your powersupply. If it is 250 Watt throw it out and get at least a 300 Watt. We import and export computer cases by container and sell a lot of separate 300 Watt PSU's to customers for ATHLON users. 250 Watt is just not enough for this cpu. If this is an FIC SD-11 board, it should be known that this board is a very picky one when it comes to voltages - FIC released this board in a hurry when it was still a prototype, leaving many things in error on this board. One thing was the voltage regulators. There are very few on this board compared to other Athlon boards (including other FIC models) and this can make for rather dirty voltages being supplied to your CPU when combined with a culprit PS. However, 2 days is kind of a long time for these problems to arise. There's just too much crap that happens these days to rule it out though. - End included text It could be that the UDMA controller is another "[thing] in error" on this motherboard. -- Chris BeHanna Software Engineer [EMAIL PROTECTED] Remove "bogus" before responding. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
Soren Schmidt wrote: It seems Justin W. Pauler wrote: I've heard tell that there are problems with the VIA chipset and UDMA on FreeBSD. Is this true, and if so, what is the problem with? Hmm, there are no open problems as far as I'm aware... FreeBSD 4.2-STABLE #0: Fri Dec 8 01:52:44 EST 2000 CPU: Pentium III/Pentium III Xeon/Celeron (601.37-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 atapci0: VIA 82C686 ATA66 controller port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 19546MB FUJITSU MPF3204AT [39714/16/63] at ata0-master UDMA66 The drive has enough space and I have 512MB RAM. If I hit the system hard, lets say, rm -rf /usr/ports, the system locks up. It doesn't just stop responding for a little bit. It locks up tight. It kills all network connections, doesn't respond to the console and doesn't respond to any network activity. A hard reboot is the only thing that can bring it back to life. One time, someone was able to see the console when this happened, and they said something about a page fault. Trying to solve this, we ordered two brand new 256MB modules and installed them. It is still happening. This is a production environment type of server. I've had no other problems with FreeBSD 4.2-S, and i'm hoping maybe this is something that has been fixed. Hmm, my main devbox is based on the VIA '686 although with an athlon CPU, and there is no problems at all with it. I also dont belive that this is the disk drivers fault, as in almost all cases you would get error messages en-masse from the ATA driver I have an Abit KT7 with PC-133 memory and an Athlon 900 that doesn't like FreeBSD 4.2-stable and Maxtor ATA100 drives. Right now, it is running in PIO mode and that makes it less than half fast doing a system build. The first install of FreeBSD resulted in a trashed Win98se primary partition. There were timing issues in the bios that were supposed to fix the ATA100 Maxtor drives. The bios was flashed to include those fixes. I used sysctl and turned UDMA back on last night and it didn't help the ata-disk. It went back to PIO mode in a hurry. Kent -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
I have a KT7 with an athlon 1.1, no problems with ATA66, don't have a 100 drive though. Works fine, does make worlds in a little over an hour with 384mb of pc133, but I do have to downclock the pc133 to 100 because these via chips have some problem with agp and pc133 at the moment. I have an Abit KT7 with PC-133 memory and an Athlon 900 that doesn't like FreeBSD 4.2-stable and Maxtor ATA100 drives. Right now, it is running in PIO mode and that makes it less than half fast doing a system build. The first install of FreeBSD resulted in a trashed Win98se primary partition. There were timing issues in the bios that were supposed to fix the ATA100 Maxtor drives. The bios was flashed to include those fixes. I used sysctl and turned UDMA back on last night and it didn't help the ata-disk. It went back to PIO mode in a hurry. Kent -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
"David W. Chapman Jr." wrote: I have a KT7 with an athlon 1.1, no problems with ATA66, don't have a 100 drive though. Works fine, does make worlds in a little over an hour with 384mb of pc133, but I do have to downclock the pc133 to 100 because these via chips have some problem with agp and pc133 at the moment. I'm also running the slow end on the bios memory setting. The wz beta bios is supposed to deal with some memory timing questions. I have downloaded wz but haven't flashed the bios yet. I am running uz, which became w? (their www server is overloaded and can't see what they called the uz when it was released). Abit is also up to KT7a and 686B. I have both Maxtor's (30 GB and 40 GB - ATA100's) set to do only UDMA 33 using Maxtor's udmaupdt.exe program. That didn't help FreeBSD. Windows 2000 didn't have any problems at the UDMA66 setting and just slowed down a little bit at the UDMA33 setting. I have three other systems based on the bx chipset that don't have problems doing UDMA33. If I time my upworld script, I see user times of 18xx seconds and 1.5-1.8 hours wall clock. I figure the difference between doing an update (cvsup of RELENG_4 to installworld) in 40 minutes wall-clock and what I have now is disk transfer speed related. Setiathome runs at ~40% cpu in the background (niced to 19). Because it is only using available cpu time, killing setiathome before I started the builds didn't change the build time significantly. I have a Promise ATA66 card that I am going to try but will have to move one of the HD's and CDROM before the 80-pin cable will reach. The main drive is all by itself on the ide1 controller. Kent I have an Abit KT7 with PC-133 memory and an Athlon 900 that doesn't like FreeBSD 4.2-stable and Maxtor ATA100 drives. Right now, it is running in PIO mode and that makes it less than half fast doing a system build. The first install of FreeBSD resulted in a trashed Win98se primary partition. There were timing issues in the bios that were supposed to fix the ATA100 Maxtor drives. The bios was flashed to include those fixes. I used sysctl and turned UDMA back on last night and it didn't help the ata-disk. It went back to PIO mode in a hurry. Kent -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
