Re: Problem moving from Redhat 7.1 to RedHat 8.0
Ross Macintyre <[email protected]> Tue, 23 Sep 2003 15:27:40 +0100 (GMT Daylight Time)
| Newsgroups | gmane.linux.drivers.vortex.devel |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 22 Sep 2003 13:36:18 -0400 (EDT) Donald Becker <[email protected]> wrote: > On Mon, 22 Sep 2003, Ross Macintyre wrote: > > > I manage 2 groups of machines (as well as others) that are giving me > > horrendous problems trying to put RedHat 8.0 on them. > > [[ I'll skip the "why RH8?" question. ]] I'll answer anyway:-) I've got so many machines to administer I find it easier if they all run the same version of RedHat. When 8.0 came out I started a wholesale move to 8.0, servers and all. I'm too far down the line to do an about turn. ....see the end of this message .. > > > They are old Viglen machines. One group are Genie2 and the others are > > Contender2's. They contain 'Boomerang' and 'Cyclone' ethernet cards. > > > > I have left one machine at 7.1 and it still works fine, The other 30 > > machines have all had RedHat 8.0 installed on them and at first all > > seemed to be working fine but now I notice that they all lose their > > connections to the network after about 5 to 10 minutes after a > > reboot. > > That's a curious time period. Are you certain that they work at all? > > > NETDEV WATCHDOG: eth0: transmit timed out > > Which driver version are you using? > > > eth0: transmit timed out, tx_status 00 status e000. > > diagnostics: net 0cc0 media 8802 dma 00000000. > > Flags; bus-master 1, dirty 1(1) current 17(1) > > Transmit list 00000000 vs. c2462240. > > This looks as if no packets have been sent, and the IRQ is blocked. > > What is the interrupt count in /proc/interrupts? > > If it's an IRQ problem, check the kernel messages while setting up the > "APIC" (well before the driver is loaded) for warnings or problem reports. > > > I also tried updating the BIOS but also no joy. > > This had a better chance of fixing a problem than you might expect.. what I didn't say was that I had only tried updating the BIOS on one machine only. Trust me to pick a duff machines! I decide today, if I was going to get these machines up and running anyway, then they should all have the latest BIOS patch so I've just run round them all and done that. Guess what?.. they are now working!! thanks for your help and taking the time to reply. Ross > > -- > Donald Becker [email protected] > Scyld Computing Corporation http://www.scyld.com > 914 Bay Ridge Road, Suite 220 Scyld Beowulf cluster system > Annapolis MD 21403 410-990-9993 > > _______________________________________________ > vortex mailing list > [email protected] > http://www.scyld.com/mailman/listinfo/vortex -- Ross Macintyre Heriot-Watt University [email protected] _______________________________________________ vortex mailing list [email protected] http://www.scyld.com/mailman/listinfo/vortex