Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754845Ab0L3ChO (ORCPT ); Wed, 29 Dec 2010 21:37:14 -0500 Received: from mail-qy0-f181.google.com ([209.85.216.181]:50172 "EHLO mail-qy0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754593Ab0L3ChM (ORCPT ); Wed, 29 Dec 2010 21:37:12 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=PWT+uZL3t3K4jZoDGusk5KYwy4yRNtj/1Qo4MfJj2bEy3YNSu0Ji7+2TncPUwPsxNy CNgk26PC4kWxSrvqf62n6NcU5rbCkWdTJslBYeRcEr0h9/1vq/k9t8MZOCJCOG4w+9tT rndKSesusYeWVIsg6vWNUrtVNynuK64vSVaLg= Message-ID: <4D1BF056.3060909@lwfinger.net> Date: Wed, 29 Dec 2010 20:37:10 -0600 From: Larry Finger User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101125 SUSE/3.0.11 Thunderbird/3.0.11 MIME-Version: 1.0 To: "Mario 'BitKoenig' Holbe" , LKML , wireless , b43-dev Subject: Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register() References: <4D1A8200.4010609@lwfinger.net> <20101229195440.GD5838@darkside.kls.lan> <4D1BD2B0.4020101@lwfinger.net> <20101230012003.GA2665@darkside.kls.lan> In-Reply-To: <20101230012003.GA2665@darkside.kls.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1118 Lines: 27 On 12/29/2010 07:20 PM, Mario 'BitKoenig' Holbe wrote: > > It will surely not matter: if CONFIG_B43_HWRNG would not have been > defined, hwrng_register() would not have been reached in the dump from > my first mail. > > If you really like me to try that patch, I'll do so when I'm awake again > and will then answer you that nothing has changed :) No, don't bother. I do have a different request. The byte counts for my 32-bit system do not match yours. Could you please use the following command to find the instructions that are failing? objdump -l -d drivers/char/hw_random/core.o | less Use the search to find the start of hwrng_register, then add 0x4c to the starting address. Once I see hte instruction that is failing, I should be able to find where the failure occurs. The order in which things are registered should not cause an error, but who knows? Larry -- 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/