Dave, Yup. Had a feeling that you might be right about that one.
It seems that the computer will still crash, but certainly not as often. My guess: there is a bigger problem that is aggravated when the computer is under more stress; ie: tracking excessive amounts of kernel complaints, etc. I've also noticed difficulties with the sound system and have had the computer crash a number of times when playing music (could be the media player or the sound system itself, but I still think that the problem is bigger yet). Ideas for a next step? Is there more information that I can submit to <hopefully> throw out the possibility of a hardware problem, or to determine which piece of hardware is at fault? Thanks again for all of your help. Kris On Sunday 18 September 2005 21:09, Dave Nebinger wrote: > > Before the crash, the following three lines appeared (in this order) > > nearly > > > > 53,000 times for a total of 16MB of text: > >> Sep 17 13:45:51 kerwin [4314362.567000] ip_local_deliver: bad skb: > > > > PRE_ROUTING LOCAL_IN LOCAL_OUT POST_ROUTING > > > >> Sep 17 13:45:51 kerwin [4314362.567000] skb: pf=2 (unowned) dev=lo > >> len=60 Sep 17 13:45:51 kerwin [4314362.567000] PROTO=6 127.0.0.1:34134 > > > > 127.0.0.1:111 L=60 S=0x00 I=15872 F=0x4000 T=64 > > Don't assume this is your answer, Kris. This was a known problem on one of > the 2.6.12 kernels (2.6.12.4, I believe, but don't hold me to it). > > I had many of these in my logs also. It was a partial network patch > applied to the networking layer but missed some components. It was fixed > by the 2.6.13 kernel series. -- [email protected] mailing list
