From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267930AbUJNWTp (ORCPT ); Thu, 14 Oct 2004 18:19:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267306AbUJNWRv (ORCPT ); Thu, 14 Oct 2004 18:17:51 -0400 Received: from rproxy.gmail.com ([64.233.170.192]:58258 "EHLO mproxy.gmail.com") by vger.kernel.org with ESMTP id S268025AbUJNWEL (ORCPT ); Thu, 14 Oct 2004 18:04:11 -0400 Message-ID: <9625752b04101415043a078b93@mail.gmail.com> Date: Thu, 14 Oct 2004 15:04:11 -0700 From: Danny Reply-To: Danny To: linux-kernel@vger.kernel.org Subject: Re: mm kernel oops with r8169 & named, PREEMPT Cc: netdev@oss.sgi.com, Francois Romieu In-Reply-To: <9625752b04101314595f72f84a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <9625752b041012230068619e68@mail.gmail.com> <9625752b041013091772e26739@mail.gmail.com> <9625752b04101309182a96fbd2@mail.gmail.com> <200410131129.05657.jdmason@us.ltcfwd.linux.ibm.com> <20041013181840.GA30852@electric-eye.fr.zoreil.com> <9625752b04101313417be4cf90@mail.gmail.com> <20041013205433.GC30761@electric-eye.fr.zoreil.com> <9625752b04101314595f72f84a@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org I wasn't able to get the kernel to compile with just the reiser4 patches from the broken-out dir on the ftp. The patching itself seemed to go well though. I tried to apply the patches in the order they were listed in "series" but some had to go out of order anyway, such as reiser4-only.patch had to go first. However I was able to verify it's not a problem with the r8169 driver. I copied over the r8169 driver to a fresh linux-2.6.8.1-mm4 and was able to compile and run fine with the latest r8169 driver from the linux-2.6.9-rc4-mm1 release. I also tested it in reverse, bringing over r8169.c to a fresh linux-2.6.9-rc4-mm1 and it still gave me the oops. I'm not sure where this leaves me now. Perhaps I should repost my oops and my proc info in the lkml with a different subject to draw the attention of others, since I now know this subject to be entirely missleading.