Bug 173805 - frequent dmesg entries: "eth0: freeing mc frame."
Summary: frequent dmesg entries: "eth0: freeing mc frame."
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-11-21 14:27 UTC by John Ellson
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2005-12-07 14:44:49 UTC

Attachments (Terms of Use)
output of sysreport (570.39 KB, application/octet-stream)
2005-12-01 23:13 UTC, John Ellson
no flags Details

Description John Ellson 2005-11-21 14:27:50 UTC
Description of problem:
Odd messages showing up in dmesg:
  eth0: freeing mc frame. 

ifconfig shows:
 eth0     Link encap:Ethernet  HWaddr 00:D0:B7:81:CB:A8
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::2d0:b7ff:fe81:cba8/64 Scope:Link
          RX packets:931 errors:0 dropped:0 overruns:0 frame:0
          TX packets:270 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:59502 (58.1 KiB)  TX bytes:295047 (288.1 KiB)

lspci shows:
  02:04.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100]
(rev 05)

Version-Release number of selected component (if applicable):

How reproducible:
Occuring at about 1 per sec

Steps to Reproduce:
1. dmesg
Actual results:
eth0: freeing mc frame.

Expected results:

Additional info:

Comment 1 John Ellson 2005-11-21 14:46:59 UTC
Stopping avahi-daemon stops the messages.   

Comment 2 John W. Linville 2005-12-01 15:47:58 UTC
Please try using the e100 driver instead of the eepro100.  
Edit /etc/modprobe.conf and change all references to "eepro100" to reference 
"e100" instead. 
Please give that a try and post the results...thanks! 

Comment 3 John Ellson 2005-12-01 18:43:01 UTC
There were no references to eepro100 that I could find.
It alread had "alias eth0 e100" in /etc/modprobe.conf

I can't recreate the problem today, with or without avahi-daemon running.


Comment 4 John Ellson 2005-12-01 18:47:26 UTC
CORRECTION  I *can* recreate the problem today with the packages.

(I was checking /var/log/messages instead of dmesg.  I should read my own bug
reports!  )

With avahi-daemon running, dmesg is getting "eth0: freeing mc frame" messages.

With avahi-daemon stopped, the dmesg messages stop.

There are no relevant messages in /var/log/messages.

Comment 5 John W. Linville 2005-12-01 22:44:32 UTC
Very strange...the text for "freeing mc frame" is only in the eepro100 driver, 
not the e100 driver. 
Please attach the output from running sysreport...thanks! 

Comment 6 John Ellson 2005-12-01 23:13:14 UTC
Created attachment 121720 [details]
output of sysreport

sysreport generated with avahi-daemon running

Comment 7 John W. Linville 2005-12-02 14:46:21 UTC
Your lsmod output shows that you are loading both the eepro100 and e100  
drivers.  It would appear that eepro100 is loading first and claiming the  
Unfortunately, I don't see anything else in the sysreport that explains to me  
how/why eepro100 is getting loaded at all.  The e100 driver should work with  
your hardware.  
Can you find-out how/why eepro100 is getting loaded on your box?  If nothing  
else, please attach the output of this command:  
   find /etc -type f -exec grep -l eepro100 {} \;  
You might also try this (as root): 
   mv /lib/modules/`uname -r`/kernel/drivers/net/eepro100.ko /root 
Hopefully that will prevent eepro100 from loading... :-) 

Comment 8 John W. Linville 2005-12-02 14:49:23 UTC
You might try this is an a nicer alternative to the 'mv' command above: 
   echo eepro100 >> /etc/hotplug/blacklist 
Please try that and reboot, and post the results here...thanks! 

Comment 9 John Ellson 2005-12-02 15:24:23 UTC
    find /etc -type f -exec grep -l eepro100 {} \; 
returned nothing.

    echo eepro100 >> /etc/hotplug/blacklist 
and rebooting didn't prevent eepro100 from being loaded   !!!
lsmod shows both e100 and eepro100 as loaded.

Is it significant that the two interfaces are on a single PCI card?

I have:
    alias eth0 e100
    alias eth1 e100
in /etc/modprobe.conf .   Is it possible that this file is being ignored in
favor of /etc/modprobe.d/modprobe.conf.dist ?

I tried:
    mv /lib/modules/`uname -r`/kernel/drivers/net/eepro100.ko /root
and that worked: eepro100 module not loaded, starting avahi-daemon doesn't
produce error messages in dmesg.

But this is just hiding the problem under the rug.
I have other systems that are also loading both drivers for no apparent reason.

Comment 10 John Ellson 2005-12-02 15:38:56 UTC
I've put back the module so that I can test.

    alias eth0 e100
    alias eth1 e100
to /etc/modprobe.d/modprobe.conf.dist and the rebooting did not fix the problem.

Comment 11 John Ellson 2005-12-02 15:48:16 UTC
I tried
   rmmod eepro100
and I've lost remote access to the system, so I won't be able to test further
until I get home this afternoon.

I was wondering if the eepro100 module was getting installed via mkinitrd and
just getting carried through from one version of the kernel to the next.  I was
going to:
    rmmod eepro100
    mkinitrd .....
then reboot to see if that avoided reloading it.    I'll try the experiment
later unless you have other ideas.

Comment 12 Dave Jones 2005-12-02 23:58:17 UTC
Hmm, we could probably just disable the EEPRO100 driver for fc5. The only thing
it does that e100 doesn't afaik is work on some wierdo ARM platform which we
don't build for in Fedora anyway.

Comment 13 John Ellson 2005-12-03 01:15:21 UTC
Its being loaded by mkinitrd but not getting carried forward that way.

With the eepro100.ko file in out of the way I rebooted the system
so that only e100 was loaded.  Then I did a mkinitrd  and then put
eepro100.ko back in its normal place.   The I rebooted and 
lsmod showed no eepro100 loaded.

I then upgraded to kernel-2.6.14-1.1735_FC5 and rebooted
and the eepro100 module was loaded again.

There are lots of references to eepro100 in /lib/modules/2.6.14-1.1735_FC5/module*
so my guess is that /sbin/depmod is not creating the right module dependencies
during kernel installs.

Comment 14 John W. Linville 2005-12-05 15:51:48 UTC
I'm kinda leaning towards Dave's suggestion from comment 12...  Dave, do you 
want a patch? 

Comment 15 Dave Jones 2005-12-06 22:02:56 UTC
I've just disabled eepro100 in the config. After this, everything should just
pick up the e100 driver and 'just work'.  hwdata already has the eepro100 ->
e100 migration, so upgrades should be fine.  Adding Bill to cc as a sanity check :-)

Comment 16 Bill Nottingham 2005-12-07 06:50:31 UTC
Should work fine to remove it.

Note You need to log in before you can comment on or make changes to this bug.