linux-kernel - Re: 2.6.37-rc3-git installed modules zero bytes long

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] [day] [month] [year] [list]

Date:	Wed, 01 Dec 2010 14:48:46 +0000
From:	Sid Boyce <sboyce@...eyonder.co.uk>
To:	Américo Wang <xiyou.wangcong@...il.com>
CC:	LKML <linux-kernel@...r.kernel.org>,
	opensuse factory list <opensuse-factory@...nsuse.org>
Subject: Re: 2.6.37-rc3-git installed modules zero bytes long

On 01/12/10 06:07, Américo Wang wrote:
>
> (Please don't drop lkml, and I am not a subscriber of the opensuse list.)
>
OK. I built 2.6.37-rc3-git7-smp on the second box, checked the modules 
were OK. Rebooted and modules were still OK, built the NVidia module, 
rebooted and it's OK.
I didn't build VirtualBox-3.2-3.2.10_66523 modules this time to 
eliminate that as the problem previously appeared after I had rebuilt 
VBox as the last action before rebooting straight into X.

I'm now building 2.6.37-rc4-git1 and I shall repeat that sequence again.
Regards
Sid.

> On Tue, Nov 30, 2010 at 05:24:52PM +0000, Sid Boyce wrote:
>> On 30/11/10 15:48, AmÃ©rico Wang wrote:
>>> On Tue, Nov 30, 2010 at 02:59:55PM +0000, Sid Boyce wrote:
>>>> openSUSE 11.3 on one box and openSUSE 11.4 Milestone 4 on the other.
>>>> I have a message that says the built modules not found. When I check e.g
>>>> /lib/modules/2.7.37-rc3-git7-smp, most modules are zero bytes long.
>>>> I have to "make modules_install" and use modprobe on each.
>>>> To get the network up on the 11.3 box "modprobe r6189" then "rcnetwork
>>>> restart", "modprobe rtl8187", "/etc/init.d/network-remotefs start",
>>>> etc., etc.
>>>
>>> Confused, shouldn't we always run 'make modules_install'?
>>> What did you do before that?
>>>
>>
>> As usual a script that does the following and never had problems
>> before. It says it's installed the modules, but a check shows they
>> are all zero bytes long.
>> -------------------------------------------------------------------
>> #!/bin/sh
>> make -j 4 clean&&  make headers_install&&  make -j 4&&  make -j 4
>> modules_install
>> -------------------------------------------------------------------
>
> Hmm, nothing is wrong with this script.
>
> Sounds like a regression, but I don't recall we have any 'module_install'
> changes recently.
>
> What does 'make V=2 modules_install' output?
>
> Thanks.
>


-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

--
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/