jcs@tarkus.UUCP (John C. Sucilla) (06/09/88)
In article <737@rush.cts.com> bob@rush.cts.com (Bob "Rush" Ames) writes: >In article <536@sialis.mn.org>, rjg@sialis.mn.org (Robert J. Granvin) writes: >> >Which kernel has the "net-at-large" found to be more reliable for a system >> >with heavy UUCP traffic? >> >> NOTE: These problems will _only_ occur if you are using the On Board >> Modem for UUCP type stuff. If you use a modem attached to any of the >> serial ports rather than use the OBM, you'll never see this problem. > > No. This is the second time I've read this on the net, so I'm speaking up. I've been running on 3.5 practically crash free for several months until I loaded the 3.5.1.4 upgrade about a week ago. I got up one morning and the machine was froze so I powered it down and went off to work. When I got home I powered it back up and got to execute about 4 times and it panic'ed on vector 4. I booted again and it ran a little longer but then I got some thing i've never seen before, it said: *hpte: 0x6028. Then it double panic'ed with an NMI (kernel parity). It's been up 24 hours now and is still running. I'm running a TrailBlazer + on tty001 and an AT&T PC6300 (which was powered down at the time) on tty002. The OBM and tty000 are unused. First of all, whats hpte? Second, is this just a fluke or are these some of the 3.51(a) symptoms? Am I better off with 3.50? How are the real 3.51(a) and the 3.5.1.4 upgrade related? I'm guessing that it's basically the same kernel but the rest of the stuff that changed isn't there. Am I right? -- John "C". Sucilla, A silicon based life form. {ihnp4,chinet,ddsw1}!tarkus!jcs You have a better idea? Now's the time..
rjg@sialis.mn.org (Robert J. Granvin) (06/10/88)
>How are the real 3.51(a) and the 3.5.1.4 upgrade related? I'm guessing that >it's basically the same kernel but the rest of the stuff that changed >isn't there. Am I right? Nope. 3.5 and 3.51 are two entirely different kernels complete with entirely different support programs. But in so many places they look so surprisingly similar, you'd believe they were the same... :-) 3.51 has superseded 3.5 for a long time now. As I understand it, all the support and fixes are now being directed to 3.51 only. The only time any fixes will be made available in the future for any other version level is to resolve a serious problem, but I hear that it still doesn't cover 3.0, which will no longer receive support... 3.5.1.4 and 3.51a are not related in any way (although there might be some similiarities. I'm not clear on the fixes included in 3.5.1.4). -- "I've been trying for some time to Robert J. Granvin develop a life-style that doesn't National Information Systems, Inc. require my presence." rjg@sialis.mn.org -Garry Trudeau ...uunet!{{amdahl,hpda}!bungia,rosevax}!sialis!rjg