Date: Sat, 19 May 2001 11:30:00 -0700 From: Doug Hardie <bc979@lafn.org> To: "Jeffrey J. Mountin" <jeff-ml@mountin.net> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Hardware Problem Message-ID: <f04330191b72c6b1e44cd@[10.0.1.100]> In-Reply-To: <4.3.2.20010519114538.0198c7c0@207.227.119.2> References: <4.3.2.20010518093939.02d8aad0@207.227.119.2> <4.3.2.20010517174928.02d75b00@207.227.119.2> <20010516014155.A19796@the-7.net> <20010516014155.A19796@the-7.net> <4.3.2.20010517174928.02d75b00@207.227.119.2> <4.3.2.20010518093939.02d8aad0@207.227.119.2> <4.3.2.20010519114538.0198c7c0@207.227.119.2>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:59 -0500 5/19/01, Jeffrey J. Mountin wrote: >At 10:33 AM 5/18/01 -0700, Doug Hardie wrote: > >>Unfortunately not possible for another 6 months. I get a lot of >>dissatisfied customers if I reboot. I try to keep it to once a >>year when I upgrade the OS. > >You upgraded from ??? to 4.3R? 3.5-Stable > > >>Custom, but only a couple of buffer size parameters have been >>changed and had to add the old ISA parameters to ep to get the 3Com >>NIC to work. > >My fix was to toss 'em or give them away. ;) Non-profit org with no money... > > >>No IDE at the moment. I will try that next year. > >Or just remove the bit that aren't needed from the kernel. > >Usually I leave one IDE drive set to "auto" in the BIOS to slow the >POST. Allows a little extra time to jump into the BIOS config at >least for some boards that come up too fast. > >>>Do you have 3 network cards? >> >>No just 2. I don't understand why the second one is ep1. >> >>> >>>As is dc0 and ep1 are trying to use the same IRQ. It would help >>>if you listed the hardware. >> >>Don't have a specific list. There are 2 SCSI disks 8 and 4 GB. 1 >>Adaptec SCSI controller, 1 Netgear 10/100 NIC, 1 3Com 10 NIC. 1 >>SCSI CDROM. The duplicate IRQs are fascinating. The dc0 was not >>on 5 for the next to last boot when I switched the 3Com ep >>definition to specify the ISA parameters. However, this delay >>problem has existed for at least 3 years. We don't boot the >>machine but about once a year for OS upgrades so its not a >>significant issue, but I don't want to have bad hardware bring me >>down at an inconvenient time. These machines are all remote and >>unattended. > >Guess it would be nice to have a 4th for upgrades and they were the >same. However, if only booting is slow and nothing else is wrong >then solving this would be a low priority. You say this has >happened for 3 years, what was the last release that didn't pause? It was doing that when I first got involved. That was on 2.2.8 or 2.2.5. We had both and I don't remember which one this specific machine has. Yes I have an upgrade machine and it does not do this. None of the others do. I believe I have 6 others at various locations now. Only the one has the problem. Thats why I believe I have some flakey hardware thats going to go really bad in the future. Then it will be easy to diagnose, but I was hoping to figure out early on what it is so I can get a replacement and schedule it rather than wait for the failure. > > >Jeff Mountin - jeff@mountin.net >Systems/Network Administrator >FreeBSD - the power to serve -- -- Doug 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?f04330191b72c6b1e44cd>