Messages in this thread | | | Date | Wed, 25 Jun 1997 13:44:44 -0400 (EDT) | From | David C Niemi <> | Subject | Re: oops in 2.1.pre-44 w. ipv6 installed |
| |
On Wed, 25 Jun 1997, Michael L. Galbraith wrote: > > I have been tracking down a fatal oops with very similar symptoms in > > 2.1.pre44-2 on a system with 2 tulips, one 21041 and one 21140. 2.1.43 > > seems OK, but 2.1.44-pre2 with the 0.76 driver gets the oops when the > > devices are ifconfig'd up. > > > > Oddly the machine seems very stable under 2.1.43. In my case ipv6 is *NOT* > > enabled but IP aliasing is; I suspect ipv6 and IP aliasing are just serving > > as scapegoats for a different problem. > > > > I can't figure out why ipv6 has anything to do with it. The module isn't > even loaded at oops time, and I'm not doing any ipv6 things to start it > loading(?). However, not including it removes the problem :-\ > > I tried disabling aliasing (and ISDN).. no such luck.
I really doubt ipv6 or aliasing really have anything to do with it.
> Is /proc/net/dev trashed in your case too? Non-killable processes?
The machine is too close to hung to look. All I can do is Alt-Control-Del.
> > Are you really sure the hardware is stable? > > > > Pretty sure about the hardware.. heavily tested under high load (100->200).
So are you using Tulip cards? If so, what type(s)?
David Niemi@erols.com 703-810-5538 Reston, Virginia, USA --- Most operating systems, sometimes even DOS, separate different --- types of files into different directories. The Windows philosophy: --- Throw everything into C:\WINDOWS and let God sort it out.
| |