From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from puffin.external.hp.com (puffin.external.hp.com [192.25.206.4]) by dsl2.external.hp.com (Postfix) with ESMTP id EF536482C for ; Wed, 12 Dec 2001 17:41:08 -0700 (MST) Message-Id: <200112130036.RAA12216@puffin.external.hp.com> To: Sonny Cook Cc: parisc-linux@parisc-linux.org Subject: Re: [parisc-linux] tulip driver In-Reply-To: Message from Sonny Cook of "Wed, 12 Dec 2001 23:06:19 GMT." Date: Wed, 12 Dec 2001 17:36:03 -0700 From: Grant Grundler Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: Sonny Cook wrote: > What is the state of the tulip driver currently? Stable - I don't think tulip's your problem. > The kernel I used is 2.4.16-pa16. During > the boot process, the kernel just locks up after reporting that it has > freed some memory. Helge enabled freeing bootmem and it was disabled again because of such lock-ups. At least until all extra __init's get removed. I think it's disabled since 2.4.16-pa18 or -pa19. So tulip is just a victim here and not a culprit. > Any advice, or hint as to where to start looking would be appreciated. Pull newer kernel source or disable the #if 1 that was enabled in -pa14. See parisc-linux-cvs archive for details. grant