linux-kernel - Re: 2.6.36-rc1 oopses at boot time in kobject allocation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100819203435.GA28508@suse.de>
Date:	Thu, 19 Aug 2010 13:34:35 -0700
From:	Greg KH <gregkh@...e.de>
To:	Benjamin Gilbert <bgilbert@...cmu.edu>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.36-rc1 oopses at boot time in kobject allocation

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/