Re: System reboots while booting with Logitech mouse
When it got to the USB controller in the boot sequence, it paused then printed a message and then it rebooted all over again. Yes, it works just fine on WInblows 2000, which is why it was plugged in when I rebooted to FreeBSD. I forgot to unplug it, and thats when I noticed the problem. I just cvsup'd and saw some USB changes in the code. I am going to reboot to see if it still happens. later Michael Mercer Daniel O'Connor wrote: On Fri, 2003-01-10 at 06:58, Michael E Mercer wrote: I just bought a Logitech TrackMan Wheel Optical Mouse. It was plugged into the USB port when I booted FreeBSD, and the system kept rebooting until I unplugged the mouse from the USB port. Weird.. I have a Logitech USB TrackMan+ trackball, Logitech Dual Eye Optical, and Logitech Wireless Optical mice and they all work fine.. When you say 'kept rebooting' what exactly do you mean? Did it reboot before booting FreeBSD, after, or both? Does it work on another OS and/or PC? -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ATA corruption in DMA mode
Janet Sullivan wrote: [..] I broke the mirror and tested each drive separately on the HPT controller in DMA mode - there were no problems. I recreated the mirror and the corruption of large files came back. The problem only occurs when the two drives are in a RAID1 array on the HPT controller and DMA is enabled. I would think that if this was a hardware problem, one of the two drives in the RAID1 array would have had some corruption problems when it was taken out of the array and addressed as a single drive. Suggestions? It could be a problem with your power supply: in mirror mode both drives are active at the same time. You could try to give one drive some constant work while you test the other drive. Wolfgang To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
ATA problems (still)
Hi, Back in October, I sent out an email with respect to problems I have been having with my 4.7 based FreeBSD system since I swapped out the SCSI drives for a large capacity IDE drive. I never got much help with that request so I am reposting with some additional information I have collected since then. My system is currently running FreeBSD 4.7-STABLE from Dec 4. The system is a ASUS TUSL2-C motherboard with a Pentium III-1.133ghz. This motherboard has the Intel ICH2 chipset on it for the IDE controller. I purchased a WD 180GB hard drive (2MB cache -- non-special edition): ATA/ATAPI revision6 device model WDC WD1800BB-00DAA0 serial number WD-WMACK1027562 firmware revision 63.13F63 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 351651888 sectors dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes dma queued no no 0/00 SMART yes yes microcode download yes yes security yes yes power management yes yes advanced power management no no 0/00 automatic acoustic management yes no 254/FE 128/80 At first, I attached this to the onboard ICH2-based controller and I was seeing hard hangs about every 1-2 days that required a power-off to correct. On the console I would see: ad4: READ command timeout tag=0 serv=0 - resetting something about removing the drive from the config then the system slowly grinded to a halt. If I just hit the reset button then the system will not find the hard drive on the reboot. I have to hit the power button to make it find the hard drive again. The hard drive also came with a free ATA100 controller made by promise that supoported the ATA6 command-set so I then tried this controller: atapci0: Promise TX2 ATA100 controller port 0xb400-0xb40f,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 mem 0xf380-0xf3803fff irq 9 at device 10.0 on pci2 With this controller the system lasts longer than 1-2 days but still crashes in the same way after about 1 week. In the original setup (on the onboard controller) I had the hard drive on channel 0 configured as an only drive and had an LS-120 and DVD-ROM on channel 1. When I moved the hard drive over to the Promise PCI card, I left the LS-120 and CD-ROM drive on the onbaord controller and moved only the hard drive. Next, I tried swapping out the hard drive for a another one. This one was a WD 200GB special edition (8MB cache): ATA/ATAPI revision6 device model WDC WD2000JB-00DUA0 serial number WD-WMACK1058547 firmware revision 63.13F63 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 390721968 sectors dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes dma queued no no 0/00 SMART yes no microcode download yes yes security yes no power management yes yes advanced power management no no 0/00 automatic acoustic management yes no 254/FE 128/80 With this drive I tried both controllers as above and got the same results. Then i saw some thread about how bad cables could potentially contribute to this problem so I tried three different new cables I had. None of these worked either so I went to the local computer parts store and purchased a ATA100/ATA133 cable and that didn't work either. So then I tried disable DMA, tags, etc: hw.ata.ata_dma: 0 hw.ata.wc: 0 hw.ata.tags: 0 hw.ata.atapi_dma: 0 This still didn't work. I should also mention that I have two other FreeBSD boxes here with similar configurations to this box (same mb, same processor) but use a Seagate ATAV drive. Both of those systems work fine. So I'm not sure if the problem has something to do with the WD drives or if it has something to do with the ATA6 support (for larger than 137GB hard drives). For reference the info on the two segate drives (both of these are configured as master drives on chanell 0 of the onboard controller -- like wise a LS-120 and CD-ROM/DVD-ROM are on channel 1) in their respective computers: ATA/ATAPI revision5 device model ST360021A serial number 3HR02PJF firmware revision 3.05 cylinders 16383 heads 16 sectors/track 63 lba supported 117231408 sectors lba48 not supported dma supported overlap not supported Feature Support EnableValue
Re: System reboots while booting with Logitech mouse
On Sat, 2003-01-11 at 02:37, Michael E Mercer wrote: When it got to the USB controller in the boot sequence, it paused then printed a message and then it rebooted all over again. What kind of message? Yes, it works just fine on WInblows 2000, which is why it was plugged in when I rebooted to FreeBSD. I forgot to unplug it, and thats when I noticed the problem. Did it happen when the mouse was not plugged in? Did it happen with any other kind of mouse? More information could be useful. - James -- James Pole ICQ: 21721828 AIM: kiwijames1986 MSN: [EMAIL PROTECTED] SMS: +64-210-455-139 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ATA problems (still)
On Sat, 2003-01-11 at 03:25, Keith Mitchell wrote: Then i saw some thread about how bad cables could potentially contribute to this problem so I tried three different new cables I had. None of these worked either so I went to the local computer parts store and purchased a ATA100/ATA133 cable and that didn't work either. Have you tried using a good cable that you know works, from a different setup to see if it makes a difference? Maybe the cable you bought was a bad cable -- rare, but it could happen. Also, make sure you've connected the cables properly. So then I tried disable DMA, tags, etc: hw.ata.ata_dma: 0 hw.ata.wc: 0 hw.ata.tags: 0 hw.ata.atapi_dma: 0 This still didn't work. Eek, thats no good. It should work fine with PIO mode since its not as stressful as DMA mode. I should also mention that I have two other FreeBSD boxes here with similar configurations to this box (same mb, same processor) but use a Seagate ATAV drive. Both of those systems work fine. So I'm not sure if the problem has something to do with the WD drives or if it has something to do with the ATA6 support (for larger than 137GB hard drives). For reference the info on the two segate drives (both of these are configured as master drives on chanell 0 of the onboard controller -- like wise a LS-120 and CD-ROM/DVD-ROM are on channel 1) in their respective computers: snip When I took the 180GB out of the FreeBSD box and replace it with the 200GB drive, I put the 180GB drive in my Mac and it has been working flawlessly over there since the middle of november. Has anyone had any luck with large hard drives or these WD drives? I can't think of anything else to try. Have you tried a different motherboard? Perhaps the motherboard you were trying the WD HDDs on has a faulty IDE and/or PCI controller or maybe the motherboard itself is faulty. The fact it works on one computer but has problems on another seems to somewhat support my theory. Perhaps you could swap in your WD HDD onto one of your Seagate computers and see what happens then. It might also be intresting to put the Seagate on the computer that was running the WD HDDs and see if it shows the same problem as the WD HDD. I hope you find my suggestions useful. - James -- James Pole ICQ: 21721828 AIM: kiwijames1986 MSN: [EMAIL PROTECTED] SMS: +64-210-455-139 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Telling AMR controller to rebuild RAID5 through FreeBSD ...
We've just been informed that one of our drives has to be replaced, but in order to do so, the machine has to be rebooted, since they can't initiate the rebuild from FreeBSD ... its using one of the MegaRAID controllers ... is this, in fact, correct, or do they just not know how to do it? I'd rather have them hot-swap the drive and rebuild it without having to shutdown the machine ... Thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Dell PowerEdge 2600 and PERC4/Di
On Thu, 9 Jan 2003, Andrew Tulloch wrote:
Does anyone know if the PERC4/Di as found in the PE 2600 is supported on
FreeBSD 4.7-REL or -STABLE, I assume it would come under the aac driver like
the other Di PERC devices, but I can't find any mention of it anywhere.
mike@eng{mike}$ grep PERC /var/run/dmesg.boot
aac0: Dell PERC 3/Di mem 0xf000-0xf7ff irq 11 at device 8.1 on
pci1
It works great. A list of supported RAID controllers is also here,
http://people.freebsd.org/~msmith/RAID/index.html#adaptec
(Thanks Mr. SCSI.)
--
Mike HoskinsThis message is RFC 1855 compliant,
[EMAIL PROTECTED] www.adept.org/pub/rfcs/rfc1855.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: Telling AMR controller to rebuild RAID5 through FreeBSD ...
On Fri, 10 Jan 2003, Marc G. Fournier wrote: We've just been informed that one of our drives has to be replaced, but in order to do so, the machine has to be rebooted, since they can't initiate the rebuild from FreeBSD ... its using one of the MegaRAID controllers ... is this, in fact, correct, or do they just not know how to do it? I'd rather have them hot-swap the drive and rebuild it without having to shutdown the machine ... This may be related to afaapps*.rpm/afacli. (At least I've ran into this before. Dell originally released binary drivers to get RH to support the PERC arrays, and also released afaappss/afacli to interface with the arrays.) The unofficial Dell PERC/afaapps page is here, http://www.domsch.com/linux/ This post, http://www.geocrawler.com/archives/3/168/2002/2/0/7903628/ Indicates afacli will run under Linux emulation, so that may be an option. (Haven't tried it myself.) -- Mike HoskinsThis message is RFC 1855 compliant, [EMAIL PROTECTED] www.adept.org/pub/rfcs/rfc1855.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Dell PowerEdge 2600 and PERC4/Di
On Fri, 10 Jan 2003, Mike Hoskins wrote:
On Thu, 9 Jan 2003, Andrew Tulloch wrote:
Does anyone know if the PERC4/Di as found in the PE 2600 is supported on
mike@eng{mike}$ grep PERC /var/run/dmesg.boot
aac0: Dell PERC 3/Di mem 0xf000-0xf7ff irq 11 at device 8.1 on
I somehow missed the 4 in your post. Dell's site seems to indicate the
controllers are very similar, but I'd wait for Mike Smith's input. :)
--
Mike HoskinsThis message is RFC 1855 compliant,
[EMAIL PROTECTED] www.adept.org/pub/rfcs/rfc1855.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
