Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272527AbTHNQIA (ORCPT ); Thu, 14 Aug 2003 12:08:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272480AbTHNQGj (ORCPT ); Thu, 14 Aug 2003 12:06:39 -0400 Received: from fw.osdl.org ([65.172.181.6]:4805 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S272468AbTHNQGc (ORCPT ); Thu, 14 Aug 2003 12:06:32 -0400 Date: Thu, 14 Aug 2003 09:06:24 -0700 (PDT) From: Linus Torvalds To: Lincoln Durey cc: LKML , EmperorLinux Research Subject: Re: 2GB laptop has pcmcia_cs looking for _insane_ sockets In-Reply-To: <1060875427.15508.2438.camel@tori> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1271 Lines: 33 On 14 Aug 2003, Lincoln Durey wrote: > > There can't be that many laptops with 2GB RAM, but surely this report > indicates an error somewhere in the pcmcia_cs code (it is looking for > socket number e9b91000 !!) The socket number is just a random allocation (but useful to keep two different sockets separated - think of it as just a unique ID). That value actually looks reasonable, it's in the kernel virtual address space. However, the fact that it doesn't work clearly means that _something_ is wrong, and the memory size part is interesting: > This bug is a feature of having 2GB ram in > the system and has nothing to do with specific PC cards drop back to 1GB > and all is well It's almost certainly the Yenta PCI resource that got allocated in the wrong area, and instead of pointing to PCI memory-mapped space it just points to RAM. Can you show the results of "cat /proc/iomem" and "lspci -vvxxx", and also try this with a 2.6.0-test3 kernel just to see if the resource handling is fixed? Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/