Date: Thu, 19 Aug 2010 13:34:35 -0700
From: Greg KH <gregkh@suse.de>
To: Benjamin Gilbert <bgilbert@cs.cmu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.36-rc1 oopses at boot time in kobject allocation
Message-ID: <20100819203435.GA28508@suse.de>
References: <4C6D9289.4000702@cs.cmu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C6D9289.4000702@cs.cmu.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 855
Lines: 26

On Thu, Aug 19, 2010 at 04:22:33PM -0400, Benjamin Gilbert wrote:
> 2.6.36-rc1 and 2.6.36-rc1-127-g763008c fail to boot for me:

Can you run 'git bisect' to try to track this down?

> Other observations:
> 
> - Originally the backtrace originated from the yenta driver, so I
> disabled PCMCIA support and it switched to occurring during EHCI
> init.
> 
> - Disabling kmemleak at boot time prevents the "cannot insert" error
> but not the bad kernel paging request.
> 
> - The offending address is "pci:" in little-endian ASCII.

This sounds like a memory overwrite problem somewhere, wierd.

thanks,

greg k-h
--
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/