Bug 76853 - ioctl SIOCGIFMAP failed in ifconfig when I load appletalk.o
ioctl SIOCGIFMAP failed in ifconfig when I load appletalk.o
Product: Red Hat Linux
Classification: Retired
Component: net-tools (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Radek Vokal
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-10-28 04:50 EST by Dennis Yang
Modified: 2007-04-18 12:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-04 09:25:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dennis Yang 2002-10-28 04:50:02 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Q312461)

Description of problem:
ifconfig will show interrupt and base address of interfaces 
using ioctl SIOCGIFMAP (the line is "ioctl(skfd, SIOCGIFMAP, &ifr)").
When I load appletalk.o (insmod appletalk), the ioctl will fail and 
can't show the interrupt and base address. And after unload the 
appletalk.o, the ioctl returns to normal. Is there any way to fix 
the ioctl when I load appletalk.o?

I have tried to use lan card rth8139, e100, eepro100 to test. 
And ioctl failed every time when I load appletalk.o.

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

How reproducible:

Steps to Reproduce:
1.insmod appletalk

Actual Results:  After insmod appletalk.o the line "interrupt: xx Base address: 
0xXXXX ..." disappear.

Expected Results:  ifconfig should show "interrupt: xx Base address: 
0xXXXX ..." of 
each interface.

Additional info:
Comment 1 Phil Knirsch 2002-11-04 11:08:01 EST
Very strange, but reproduced here! Will look into it. Although it's more likely
to be a kernel bug. :-)

Read ya, Phil
Comment 2 Radek Vokal 2004-11-04 09:25:28 EST
I didn't manage to reproduce this bug with net-tools-1.60-39 and 2.6.9
kernel. Closing this bug as CURRENTRELEASE. 

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