Bug 4504

Summary:	Says "Warning" Prevents Module Loading
Product:	Other	Reporter:	Jennifer S. Case (jennifer755)
Component:	Modules	Assignee:	Keith Owens (kaos)
Status:	REJECTED INVALID
Severity:	high
Priority:	P2
Hardware:	i386
OS:	Linux
Kernel Version:	2.6.11.6 + 2.6.11.7	Subsystem:
Regression:	---	Bisected commit-id:

Description Jennifer S. Case 2005-04-16 11:05:55 UTC

Distribution:From the Kernel.org FTP Site
Hardware Environment:AMD K6-2 500 256MB System RAM 30GB HDD
SystemFormat reiserfs bare.i Kernel 2.4.29
Software Environment:Slackware 10.1 -current
Problem Description:Breaks Modules, does not allow system to properly make
modules_install after make command is initiated. intermodule.c Lists Void and
const void, and any modules made are not loaded properly.

Steps to reproduce:
Install Slackware 10.1 Fresh
FTP from kernel.org the latest Build 2.6.11.7
On my system I setup to no SMP and the AMD K6 processor.
Disabled IEEE1394 as it's not installed
Disabled ACPI as it's disabled in My BIOS
Anything not on the system is disabled.
No IEEE1394 No SCIS EG AHA 2940 AHA 1542B or DTC or anything that resembles an
SCSI Adaptor. Diables.
Modules Created are
Sound
Ext2 - Ext3
No other Modules
runs make
runs make install
runs make modules_install
copies BzImage/VmLinuz - Ststem.map to /boot edits Lilo to reflect changes, eg
VmLinuz-2.6.11.7 Linux 2 - System-2.6.11.7 Linux 2
When rebooting, something changes around the files, and still shows a Linux
2.4.29 loder. I have the read me, and several other sources of instruction on
how to make this happen. This is consistant and in 3 weeks has not changed.

Comment 1 Keith Owens 2005-04-16 21:50:24 UTC

Nothing to do with me. The problem description is very confusing. Part of it talks
about module loading 2.6.11 in kernels - 2.6 module loading is Rusty's problem,
not mine. The rest of the problem talks about being unable to switch lilo from
2.4 to 2.6 kernels - I do not support lilo.

Comment 2 Jennifer S. Case 2005-04-17 22:32:59 UTC

Ok, well can you send this to Rusty and ask about the intermodule.c file, it
seems to come up with 3 warnings of being Depreciated. From each Interm Release
Linux 2.6.11.5 Linux 2.6.11.6 and Linux 2.6.11.7. It has not veared from the
warnings, and once I tried taking off the Module information and a lot of
selections vanished, because no modules were allowed to be created. This is a
serious issue and should be dealt with.

Comment 3 Keith Owens 2005-04-18 00:03:01 UTC

Rusty knows that inter_module_* is deprecated, he made the change.  We are waiting
for one last user of inter_module_* to be recoded then the functions will be
deleted.  The messages are just warnings, and have no effect at all on whatever
problem you are really hitting.  Unfortunately you have provided no useful data
on your real problem.

I am rejecting this bug, it contaions no useful data.