Bug 3676 - Device 'i823650' does not have a release() function
Summary: Device 'i823650' does not have a release() function
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: PCMCIA (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Dominik Brodowski
URL:
Keywords:
: 4302 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-10-31 07:39 UTC by Damir Perisa
Modified: 2005-12-06 23:43 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.9-mm1
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
patch for 2.6.14-git-current (2.17 KB, patch)
2005-11-10 07:12 UTC, Dominik Brodowski
Details | Diff

Description Damir Perisa 2004-10-31 07:39:22 UTC
Distribution: ArchLinux 
Hardware Environment: Thinkpad A31p 
Software Environment: i686 
 
since upgrade to 2.6.9-mm1 PCMCIA is broken ("0 sockets found") 
 
dmesg says this: 
 
Device 'i823650' does not have a release() function, it is broken and must be 
fixed.
Comment 1 Damir Perisa 2004-10-31 08:53:06 UTC
i found that 2.6.10-rc1-mm2 is out ... compiling it right now ... hope it 
solves this 
Comment 2 Damir Perisa 2004-12-13 08:18:02 UTC
rc3-mm1 ... still the same trouble! 
 
this bug must be solved for 2.6.10, as PCMCIA is very essential for some users 
(like me) 
Comment 3 Damir Perisa 2004-12-13 08:18:47 UTC
the config used for 2.6.10-rc3-mm1 can be found here: 
http://daperi.freelinuxhost.com/archlinux/lns/kernel26mm/config 
Comment 4 Dominik Brodowski 2004-12-13 12:37:09 UTC
please try a "modprobe yenta_socket" before starting the pcmcia init script. It
seems to me you're using the wrong PCMCIA socket driver. Possibly the PCIC
setting in the pcmcia init script configuration file needs updating.
Comment 5 Dominik Brodowski 2004-12-13 12:37:54 UTC
Addendum: I'll take a look at the release function, but that doesn't seem to be
critical.
Comment 6 Damir Perisa 2004-12-13 15:21:56 UTC
on comment #4:  
  
i'll try yenta_socket on next reboot ... 
Comment 7 Damir Perisa 2004-12-13 15:35:21 UTC
yenta_socket works fine ... on pcmcia-start the i82365 complains on a 
non-existent device and the nonexistent release() but this is now does not 
concern me much, as pcmcia works again (note: under 2.6.9, it worked without 
having to load yenta_socket --- so most probably you are right about the script 
conf that needs to be upgraded ... archlinux is using pcmcia-cs 3.2.7 atm ) 
Comment 8 Dominik Brodowski 2005-03-07 05:57:32 UTC
*** Bug 4302 has been marked as a duplicate of this bug. ***
Comment 9 Russell King 2005-03-07 12:56:27 UTC
This warning is a reminder to developers that i82365 is doing something which
may be a problem in some circumstances with the driver model.  However, there
is no clean way at present to resolve this (and merely quietening down the
warning by providing an empty release function is not acceptable.)

Brodo: essentially, the i82365 platform device must not be statically allocated.
There's a function (platform_device_register_simple) which dynamically allocates
the device structure, but unfortunately you can't attach anything other than
resources to it.
Comment 10 Damir Perisa 2005-03-07 13:27:57 UTC
an alternative to loading yenta_socket by hand is editing /etc/conf.d/pcmcia 
and changing the "PCIC=i82365" line to be "PCIC=yenta_socket"  
 
(kernel >2.6.9) 
Comment 11 Andris Pavenis 2005-10-04 12:07:53 UTC
Additionally, when i82365.ko fails to load, 2 port area at i365_base may remain 
allocted (it is allocted in isa_probe, but not deallocated when isa_probe
does not find anything).

The result is kernel OOPSes later when accessing /proc/ioports. 
Comment 12 Dominik Brodowski 2005-11-10 07:12:10 UTC
Created attachment 6525 [details]
patch for 2.6.14-git-current
Comment 13 Dominik Brodowski 2005-12-05 21:34:09 UTC
*** Bug 5657 has been marked as a duplicate of this bug. ***
Comment 14 Adrian Bunk 2005-12-06 03:25:17 UTC
Dominik, could you submit your patch for 2.6.14.4?
Comment 15 Dominik Brodowski 2005-12-06 23:43:10 UTC
No, not this one -- in fact, it was another bug which was triggered, and I sent
that one (instead of this mostly harmless bug) to the stable team.

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