From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 12 Feb 2003 12:12:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 12 Feb 2003 12:12:38 -0500 Received: from packet.digeo.com ([12.110.80.53]:11485 "EHLO packet.digeo.com") by vger.kernel.org with ESMTP id ; Wed, 12 Feb 2003 12:12:36 -0500 Date: Wed, 12 Feb 2003 09:22:24 -0800 From: Andrew Morton To: root@chaos.analogic.com Cc: linux-kernel@vger.kernel.org Subject: Re: Panic `cat /proc/ioports` Message-Id: <20030212092224.27aa4723.akpm@digeo.com> In-Reply-To: References: <20030211154413.19a172f4.akpm@digeo.com> X-Mailer: Sylpheed version 0.8.9 (GTK+ 1.2.10; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Feb 2003 17:22:19.0034 (UTC) FILETIME=[4BB007A0:01C2D2BB] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org "Richard B. Johnson" wrote: > > On Tue, 11 Feb 2003, Andrew Morton wrote: > > > "Richard B. Johnson" wrote: > > > > > > Linux version 2.4.18, after it runs for a few days, will panic > > > if I do `cat /proc/ioports`. Has this been reported/fixed in > > > later versions? > > > > > > : Unable to handle kernel paging request at virtual address d48e2fa0 > > > > This means that some driver which was previously loaded forgot to do a > > release_region(). Later, the /proc code tries to read stuff from within the > > driver which isn't there any more and oopses. > > > > Yes. I just noticed that most network board drivers in version 2.4.18 > do not execute release_region() after they have done a request_region(), > if they fail to install because of some error. Fairly common error. > The error in this case was > the failure to allocate memory because I told the kernel I only had 4 > megabytes (exprimental ioremap() of the rest in another module). > > Is somebody fixing these drivers (do you know). There is ongoing janitorial work, and things are getting better. But I'm not aware of anyone specifically auditing for missing release_region()s. And given that it is a box-killer rather than just a memory leak, yes, it is worth an audit.